CN1914896A - Passive optical network unit management and control interface support for a digital subscriber line network - Google Patents
Passive optical network unit management and control interface support for a digital subscriber line network Download PDFInfo
- Publication number
- CN1914896A CN1914896A CN 200480041227 CN200480041227A CN1914896A CN 1914896 A CN1914896 A CN 1914896A CN 200480041227 CN200480041227 CN 200480041227 CN 200480041227 A CN200480041227 A CN 200480041227A CN 1914896 A CN1914896 A CN 1914896A
- Authority
- CN
- China
- Prior art keywords
- managed entity
- network
- data
- managed
- onu
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
Abstract
An optical network unit(22) for managing digital subscriber line(xDSL) connections to a passive optical network(12). According to one embodiment, the optical network unit(22) comprises data structures in the form of managed entities(200/204/206) that are issued by the optical network unit(22) for managing each of the xDSL connections(26/28). Each managed entity is associated with one or more network features and comprises one or more elements further comprising relationships to other managed entities, attributes, actions, and notifications. The passive optical network(12) provides a data connection between the individual xDSL subscriber connections(26/28) and external networks, such as the Internet(20) and a switched telephone network(20).
Description
The cross reference of related application
The application requires the rights and interests of following application: the application number that gives is 60/525,983 the temporary patent application of submitting on December 1st, 2003; The application number that gives is 60/540,990 the temporary patent application of submitting on February 2nd, 2004; And the application number that gives is 60/570,575 the temporary patent application of submitting on May 13rd, 2004.
Invention field
The present invention relates generally to management and the control of optical-fiber network, and particularly relate to management and the control of EPON, can operate described EPON provides digital subscriber line (DSL) professional (for example, Asymmetrical Digital Subscriber Line professional (ADSL) or Very High Speed Digital Subscriber Line professional (VDSL)).
Background of invention
Use the worldwide general sustainable growth of fiber optic cables carry information signals. Digital information signal is modulated at the light that transmits on the fiber optic cables between source node and the receiving node. As everyone knows, fiber optic cables have the information bearing capacity higher than copper cash, and this copper cash comprises the ubiquitous unscreened copper twisted pair that is usually used to provide the dial telephone business. Because optical fiber spreads all over communication network and continues to be used, so optical fiber brings advantage above copper to the user. Usually, optical fiber shows than the higher bandwidth of copper conductor and the lower loss of signal. Optical fiber is also more reliable than copper conductor and have longer service life. Because optical fiber is not launched any electromagnetic radiation, so optical fiber is the transmission medium more safer than copper.
The EPON (PON) that for example comprises B-PON (BPON) or G-PON (gigabit passive optical network) provides many data transfer paths, and every data transfer path can be sent to a plurality of users the data service of high bandwidth. Exemplary B-PON comprises that 32 maybe can expand to 64 such data paths, and every data paths comprises fiber optic cables. G-PON for example comprises 64 or 128 data paths. Standardization PON agreement control and management is crossed over transmission and the reception of the signal of EPON.
Except fiber optic cables, PON Optical Distribution Network (ODN) also comprises optical splitter and optical combiner, be used in reference to the fuse information signal optical line terminal (OLT) that network front end (head end) is located and be positioned at the customer location place or a plurality of optical network units (ONU) of next-door neighbour's customer location between propagate.
According to current standard, the fiber path on the PON network is with the data rate work of 155Mbps, 622Mbps, 1.25Gbps and 2.5Gbps. Distributing to each user's bandwidth from this total bandwidth (aggregate bandwidth) can be static or dynamically be assigned with, so that support voice, data, video and multimedia application.
Conventional PON topological structure comprises shared upstream signal path and broadcast downstream path. Comprise that the downlink data of address head is from OLT to all ONU broadcasting. Each ONU identifies the data that are intended to for it with the matching addresses process.
The broadcast mechanism of use upstream traffic need to be avoided the scheme of data collision. A kind of technology for the management upstream traffic has adopted TDMA (time division multiple acess) agreement, in this TDMA agreement, for each ONU has authorized special-purpose transmission time slot. All ONU are in time by synchronously, and each ONU the transmission of data during its time slot that distributes. The upstream data that is received from ONU by OLT is processed and be forwarded to its plan destination beyond PON.
Usually, the emitter emission wavelength that adopts in the optical fiber telecommunications system is the light of one of following three kinds of wavelength: 1310 millimicrons, 1490 millimicrons and 1550 millimicrons, wherein, the approximate central authorities that are positioned at signal bandwidth of specified wavelength. Therefore the signal that is in these wavelength places is subject to relatively low decay, because these signals are by spread fiber and show good selection for fiber optic communication.
The standard ITU-T of International Telecommunications Union (ITU) that is entitled as " Broadband Optical Access Systems Based on Passive Optical Networks (PON) " G.983.1 in, describe the network architecture reference model of a kind of B-PON, be incorporated herein this standard ITU-T G.983.1 as a reference. Additional information can be found in G.983.x in relevant ITU standard, introduce these standards G.983.x as a reference. G.984.1 to 984-4, the G-PON reference model has been described at international telecommunications union specifications ITU-T, also introduce this standard ITU-T G.984.1 to 984-4 as a reference.
Telephone operator provides the xDSL business being known in the art to the user. According to present standard, xDSL can provide the Traffic Channel up to four, and this business for example comprises telephone service, internet data business and video traffic. Be well known that equally the restriction of the distance between user and (the xDSL business that provides for telephone operator) telephone company central office is provided the data rate of xDSL business. Many users do not have the qualification of using the xDSL business, because the beeline that this distance is set up greater than provider, and therefore can not enjoy the wide bandwidth that the xDSL business brings/high-speed business.
Summary of the invention
According to an embodiment, the present invention includes for management and provide the method for the network of data service to the user, wherein, this network comprises OLT and is connected to the ONU of OLT via EPON, wherein ONU connects by xDSL and is connected with the user. The method comprises: a plurality of managed entities (managed entity) that are provided for managing ONU, wherein, described a plurality of managed entity also comprises ADSL managed entity and VDSL managed entity, the ADSL managed entity is used for management ONU and is connected with ADSL between the user, and the VDSL managed entity is used for managing ONU and is connected with VDSL between the user; Come supervising the network by the one or more managed entities in described a plurality of managed entities; And, in response to described managed entity, between OLT and ONU, transmit data and network management information.
According to another embodiment, the OLT management comprises the EPON of a plurality of ONU, and each ONU provides a plurality of xDSL links, and each link comprises a plurality of channels. OLT comprises controller, is used for by allotting a plurality of channels that managed entity is managed a plurality of xDSL links to ONU, and wherein, each managed entity comprises link identifier and Channel Identifier. OLT also comprises transceiver, is used for to ONU transmission data with from the ONU receive data.
The accompanying drawing summary
Aforementioned and other features of the present invention will display from following more detailed invention is described, and as shown in drawings, in these accompanying drawings, identical reference symbol refers to part identical in the different accompanying drawings. Accompanying drawing needn't be drawn in proportion, focuses on the contrary illustrating principle of the present invention.
Fig. 1 has illustrated that instruction of the present invention can be used to its FTTP (FTTP, fiber to the premises) network.
Fig. 2 has illustrated the control element of the network of Fig. 1, and these control elements are implemented OMCI agreement of the present invention.
Fig. 3 and 4 has illustrated the element of the ONU of Fig. 2 and 3.
Fig. 5 has illustrated information channel identifying schemes according to an embodiment of the invention.
Fig. 6 has illustrated the information channel that the xDSL modem provides.
Fig. 7 has illustrated the main element of the OLT of Fig. 2 and 3.
Fig. 8 has illustrated OMCI managed entity according to instruction of the present invention for the ADSL network.
Fig. 9 has illustrated OMCI managed entity according to instruction of the present invention for the VDSL network.
Detailed Description Of The Invention
Before describing in detail according to the ad hoc approach and equipment of supporting for the OMCI of ADSL, VDSL and xDSL subscriber line interface of the present invention, it should be noted that the present invention mainly is in the novel and non-obvious combination of element and process steps. Become obscure for fear of making those skilled in the art hold intelligible detailed content, the element that some is conventional and step are less at length to be described, and drawing and description are described other elements and the step relevant with understanding the present invention in more detail.
Fig. 1 has illustrated FTTP (FTTP) network 10, this FTTP network 10 comprises Optical Distribution Network 12 (also with reference to or have the attribute of EPON (PON), BPON (B-PON) or gigabit passive optical network (G-PON)), and this Optical Distribution Network 12 provides telecommunication supplier's central office 14 and the optical communication link between user or the subscriber. As described below, Optical Distribution Network 12 provides various types of business, for example, and FTTH (Fiber to the home), FTTBusiness (optical fiber is to the commercial user), FTTB/C (FTTB/roadside) and FTTCab (optical fiber is to commuting case).
According to an embodiment of FTTP network 10, information signal is carried on this network with the wavelength of 1310nm, 1490nm and 1550nm. The 1310nm signal is used for upstream traffic, and 1490 and the 1550nm signal be used for downstream traffic. Multimedia and vision signal are carried with 1490nm, and data and telephone service are provided at 1550nm.
Voice, data, video and multimedia broad band business are provided by the internet that is connected to central office 14 and exchange network 20, are used for being assigned to the user by PON or Optical Distribution Network 12. 20 representatives of internet and exchange network can send information and receive the diverse network of information from the user to the user. Usually these networks known to those skilled in the art comprise: video and multi-media network, TDM/PTN network, ATM net and IP network. Therefore, in user's position, FTTP network 10 provides a plurality of information services, and these information services comprise: video and multi-media signal transmission, telephone service and internet access.
Single family (single-family) optical network unit 21 (is also referred to as single home unit, SFU) be arranged on or be close on the guard station of single domestic household or single trade company place commercial building, be used to unique user that access to Optical Distribution Network 12 is provided. Because Optical Distribution Network (fiber optic cables) extends to the guard station of unique user, so this network is called as FTTP (FTTP) or FTTB/roadside (FTTB/C) network.
At each customer location place, user resident terminal device (CPTE, customer premises terminal equipment) 24 is connected to the suitable output port (channel) of ONU 21. According to an embodiment, ONU 21 provides video port and telephone service port, and this video port is used for being connected to the user resident terminal device relevant with video, and this telephone service port is used for being connected to the user resident telephone plant. ONU 21 also provides the Ethernet output port, is used for being connected to user resident data terminal equipment (such as computer). User's position can also comprise the network router (not shown), is used for allowing more than one user to access simultaneously Optical Distribution Network 12 via router and ONU 21.
Optical network unit (ONU) 22 (is also referred to as the multiple distribution unit, MDU) connects (being also referred to as port) via the ADSL to the ONU 22 of corresponding VDSL modem 26 or ADSL Modem 28 or VDSL and come to provide xDSL professional to a plurality of subscribers or user. ONU 22 also supports the connection (being commonly referred to as xDSL connects) of other DSL types. ONU 22 provides the access to Optical Distribution Network 12 that connects via the xDSL between ONU 22 and the VDSL/ADSL modem 26/28 as the access couple in multiplexer for a plurality of xDSL users. Therefore ONU provides the function relevant with digital subscriber line access modem (DSLAM).
According to the technical term that in some network and by some networking products manufacturer, adopts, ONU 21 is called as ONT (ONT Optical Network Terminal), also therefore is different from the ONU 22 that the xDSL connectedness is provided because the ability that provides xDSL to connect is provided this ONU 21.
Each ONU output port (in one embodiment, ONU 22 comprises 24 ports) a plurality of Traffic Channels are provided, these Traffic Channels comprise four channels (being also referred to as Bearer Channel) in one embodiment, and these Traffic Channels comprise the channel that video, phone and internet data business are provided. Be connected to CPTE 24 representative of VDSL/ADSL modem 26/28 in response to the equipment of channel signal, for example representative is used for the display of display video signal, the telephone plant that telephone channel is responded and the computer that the internet data Traffic Channel is responded.
As mentioned above, the connection of the xDSL between user and the telephone company central office is limited to the distance that can carry high-quality/high data rate signal thereon. As shown in fig. 1, by Optical Distribution Network 12 is extended to user's guard station, terminal network 12 in ONU 22, and Optical Distribution Network and relevant device thereof that control is supported according to the ONT of xDSL circuit as described herein management and control interface make than recommended distance and can obtain the xDSL business further from the user of central office. Utilize this configuration, the length of user's xDSL circuit be actually now the guard station ONU 22 and the distance between the CPTE 24 in the user resident space. Therefore, with regard to the providing of xDSL business, central office and relative function have in fact been relocated to user's guard station.
Connect for ADSL, the optical transceiver among the ONU 22 is called as the ATU-C transceiver unit, wherein " C " expression " central office ". Equally, connect for VDSL, the transceiver among the ONU 22 is called as VTU-C or VTU-O transceiver unit. The optical transceiver of far-end (being the optical transceiver in ADSL or VDSL modem 28 or 26) is called as far-end ADSL transceiver unit (ATU-R) or far-end VDSL transceiver unit (VTU-R).
Although fiber optic cables can extend to each user in the multi-user guard station in theory, and therefore utilize aforesaid single home light networks unit 21 to come terminated optical fiber, but commercially more practical is to the guard station with extension of optical fiber, utilize ONU 22 to come terminated optical fiber, and come to provide the xDSL between the user's space in ONU 22 and the guard station to be connected to each user with the existing copper wire in the guard station. Each user that fiber optic cables are installed in the guard station will be expensive, and be the work of large labour intensity.
Although only show single ONU 22 at Fig. 1, but those skilled in the art will recognize that, a plurality of ONU 22 are connected to Optical Distribution Network 12, in order to provide phone, multimedia and data service via the xDSL connection to xDSL modem (for example the VDSL/ADSL modem 26/28) to the user.
Exemplary system management architecture has been described among Fig. 2. NMS/component management system (NMS/EMS) 70 is as the high-level network manager, this high-level network manager uses simple NMP (SNMP), for example in order to communicate via the network processing unit 76 in data communication network 80 and the OLT 42 (comprising for application software and the data storage device of storage for network processing unit). In OLT 42, network processing unit 76 receives SNMP instruction (namely via link 81 from NMS/EMS 70 by data communication network 80, the network agent function that OLT 42 implements about the Network Management Function of implementing by NMS/EMS 70), instruction is converted into one or more managed entities according to OMC I of the present invention, and the management request of allotting with respect to specific managed entity example to the network processing units 78 in the ONU 22 via Optical Distribution Network or PON 12. OLT 42 also allots (with respect to the instantiation of concrete managed entity) management request to ONU 22, and need not encourage from NMS/EMS 70. OLT 42 is therefore as the network manager about ONU 22, and this ONU 22 is as network agent. Single OLT 42 adopts the Multi-instance of OMCI managed entity as described below to control a plurality of ONU.
Network management information is carried by the PON channel that is exclusively used in network management information. Other PON channel bearing data, video, telephone service etc. In one embodiment, the PON channel of bearer network management information adopts ATM (asynchronous transfer mode) network technology and standard, uses with ATM although the invention is not restricted to. Another embodiment (for example, GPON) in, utilized ATM or GEM standard. As shown here, double-head arrow 82 indication OMCI interfaces are the mechanisms that finish network management by it between OLT 42 and ONU 22.
Fig. 3 has described the details of ONU 22, and this ONU 22 comprises optical transceiver 110, is used for from ODN 12 receiving optical signals, and optical signal is converted to for the signal of telecommunication to 28/26 transmission of ADSL/VDSL modem. Optical transceiver 110 also decomposes vision signal, and in one embodiment, this vision signal comprises broadcasting and cable TV signal.
In one embodiment, PON MAC comprises 24 ports, and each port is used for connecting one of ADSL/VDSL modem 28/26. Each ONU output port provides a plurality of Traffic Channels, and in one embodiment, these Traffic Channels comprise four channels, for example, provides the channel of video, phone and internet data business to subscriber or user. A plurality of ports of ONU allow repeatedly to use simultaneously digital subscriber line.
Fig. 4 has described the backboard of the ONU that constructs according to one embodiment of present invention, and this backboard comprises slot 1,2 and 3, and each slot further comprises a plurality of n port one 22. User's ADSL/VDSL modem 28/26 is connected with a port one 22 by the ADSL/VDSL circuit, as mentioned above, utilizes each port (or circuit) to provide a plurality of Traffic Channels to the user.
Some managed entity described below is the channel special use, that is, managed entity is set forth one or more attributes of dedicated channel. Therefore, dedicated channel is must be in managed entity identified to be gone out, and then requires the sign of the relative slot of this channel and port. According to one embodiment of present invention, channel logo in the managed entity comprises that the right is used for the byte 200 (referring to Fig. 5) of sign port, and the byte 202 on the left side further comprises: six bit positions (coming mark by reference symbol 204) that are used for the sign slot; And two bit positions (coming mark by reference symbol 206) that are used for the sign channel.
Fig. 6 has illustrated the port 220 that is connected to xDSL modem 222 (for example, ADSL Modem 28 or VDSL modem 26) via circuit 226. Port 220 provides three Traffic Channels: the video channel on the wire 230, and when wire 230 was connected to suitable video reception apparatus (not shown), the user can pass through these wire 230 receiving video services; Telephone service channel on the wire 232, when wire 232 was connected to telephone plant, the user can receive telephone service by this wire 232; And the Ethernet service channel on the wire 234, when wire 234 was connected to data receiver such as computer/transmitter, it is professional that the user can receive Ethernet datas by this wire 234.
Fig. 7 has illustrated some details of exemplary OLT 42, and this OLT 42 comprises a plurality of optical transceivers 130, and each optical transceiver 130 is connected to the channel of the fiber optic cables 132 of ODN or PON 12. Although only show four optical transceivers 130, those skilled in the art recognize that OLT 42 can support the considerable optical fiber PON port required such as network installation. 130 couples of PON MAC 136 of each optical transceiver make two-way response, and this PON MAC 136 is further in response to network processing unit 140.
Network processing unit 140 receives the data that are intended to for the user from internet and exchange network 20, process this data, and supplies with data via data conductor 142 to suitable PON MAC 136. The data that PON MAC 136 configuration will be transmitted by PON 12 according to the PON procotol, and supply with data to the optical transceiver 130 that is used for converting to optical signal.
Be converted into the signal of telecommunication and be supplied to PON MAC 136 from user or the received data of subscriber by optical transceiver 130. PON MAC 136 becomes to be used for data transaction to the suitable procotol of internet and exchange network 20 transmission.
Network processing unit 140 is also controlled each PON MAC 136 via the control signal that is supplied to PON MAC 136 by pilot 144.
Such as known to those skilled in the art, have many must be designated and network characterization or the running parameters of control so that supervising the network effectively, and allow data communication device to cross network effectively to exchange. According to instruction of the present invention, this network control function is carried out by a plurality of managed entities, and is further as described below. The element of each managed entity comprises network attribute that is controlled, monitors etc.
ONT management according to instruction of the present invention provides management and the control of ONU 22 with control interface, and is provided to again user's xDSL connection in following field: configuration management, fault management, performance management and safety management. Configuration management provides function to supply (for example, create, arrange or change) and controls, identifies, collects from the data of ONU 22, and provides the control data to ONU 22. The OMCI agreement is supported limited mainly unsuccessfully to indicate relevant fault management with providing.
In order to manage ONU 22, no matter when create new xDSL subscribers' line, OLT creates the example of new managed entity, read the example of managed entity, so that the acquisition network performance information, and all change the example of managed entity when no matter when wishing to change the profile of network line or channel or configuration. These two OLT functions of back are the actions with respect to the instantiation of the managed entity that before was created (namely, when circuit or channel are activated).
According to the network control technology, management information bank (MIB) has defined network managed entity (managed object), is used for allowing network manager configuration and network resource administration. In one embodiment of the invention, Internet resources comprise with ONU 22 interactional xDSL and being connected, and manager comprises OLT 42. Each Internet resources has corresponding configuration object (managed entity) example, necessary all configurations of current state and running parameter and hardware interface that this configuration object example comprises configuration and management resource, operating resource, interacts and describe resource with network manager. The MIB managed entity also provides alarm and the notice that will be each Managed Resource report, and so that resource identification information (for example, sequence number or functional description) provided by Managed Resource. In response to some managed entity, Managed Resource is collected the stored resource operation information of wanting, and is used for the after a while retrieval of network manager.
Connect (Managed Resource) in case activated the xDSL of PON, connect illustration MIB for that xDSL. All controls between xDSL connects interact and are processed by manager (OLT 42). Network processing unit 78 in the ONU 22 disposes xDSL by some managed entity of processing MIB and connects. During operation, the xDSL connection is managed by other MIB managed entity.
The xDSL switching performance information that some managed entity is asked is collected and can be stored in the ONU 22 or is buffered among the OLT 42 by ONU 22. In one embodiment, the performance data of nearest 15 minute interim is buffered among the OLT 42, until rewritten by the performance data of upgrading. Performance data can be retrieved from OLT 42 by EMS/NMS 70, is used for the network performance evaluation of higher level.
Irrelevant with the device procedures that realizes managed entity and parts, any resource (such as modem) of support MIB and managed entity thereof can successfully be used in the network and be connected to other network equipments (such as network manager), because from netting the angle of whole management (network administration), all such equipment are identical. Therefore, if these equipment are supported MIB, the equipment of different vendor's manufacturing interoperability successfully then. As relevant with the present invention, support the ONT management of xDSL circuit of the present invention and the equipment of configuration interface successfully also can successfully be controlled by OLT 42 with other such equipment interoperability.
The present invention's instruction comprises the OMCI interface of a plurality of managed entities of PON, and this PON operation xDSL connects (for example, ADSL or VDSL connection) and comes service-user. Additional information can find in G.983.10 at the specification documents ITU-T that is entitled as " B-PON ONT Management and Control Interface (OMCI) Support for Digital Subscriber Line Interfaces ", hereby introduces the document as a reference. Be called as ITU-T G.983.2 and be entitled as in the international telecommunications union specifications document of " ONT Management and Control Interface Specification for ATM PON ", describe the OMCI managed entity of PON network, hereby introduced the document as a reference. G.948.4 set forth the managed entity of G-PON network at ITU-T, also introduced this ITU-T G.948.4 as a reference. The other list of references that is hereby incorporated by comprises: be entitled as the ITU-T of " Broadband Optical Access Systems Based on Passive Optical Networks " G.983.1; Be entitled as the ITU-T of " B-PON OMCI Support for IP, ISDN, Video VLAN Tagging, VC Cross-Connections, and Other Select Functions " G.983.8; Be entitled as the ITU-T of " Physical Layer Management for Digital Subscriber Line Transceivers " (comprising its revision 1) G.997.1; The IETF RFC 3728 that is entitled as " Definitions of Managed Objects for Very High Speed Digital Subscriber Lines "; The IETF RFC 2662 that is entitled as " Definition of Managed Objects for ADSL Lines "; The IETF RFC 3440 that is entitled as " Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines "; Be entitled as the ITU-T of " Asymmetric Digital Subscriber Line (ADSL) Transceivers " G.992.1; Be entitled as the ITU-T of " Splitterless Asymmetric Digital Subscriber Line (ADSL) Transceivers " G.992.2; Be entitled as the ITU-T of " Asymmetric Digital Subscriber Line (ADSL) Transceivers-2 (ADSL2) " G.992.3; Be entitled as the ITU-T of " Asymmetric Digital Subscriber Line (ADSL) Transceivers-Extended Bandwidth ADSL2 (ADSL2plus) " G.992.5; Be entitled as the ITU-T of " Handshake Procedure for Digital Subscriber Line (DSL) Transceivers " G.994.1; Be entitled as the ITU-T of " Procedure for the Allocation of CCITT Defined Codes for Non-Standard Facilities " T.35; The ietf draft that is entitled as " Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) line Coding "; The ietf draft that is entitled as " Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding "; The TR-057 of DSL forum that is entitled as " VDSL Network Element Management "; And the ITU-T proposed standard G.997.1.
Fig. 8 has illustrated the OMCI managed entity of adsl interface and hierarchical relationship each other thereof. Fig. 9 has illustrated the OMCI managed entity of VDSL interface and hierarchical relationship each other thereof. In Fig. 8 and 9, the numeral that the next-door neighbour connects every line of initial managed entity and destination managed entity has form x..y, namely has the example of an initial managed entity between x and the y in the managed entity of destination.
The various features of each managed entity of PON/ADSL interface and PON/VDSL interface (that is, relation, attribute, action, notice and alarm) are described in detail at this, but the implementation details that the application's claim is not limited to set forth. On the contrary, described details only is exemplary embodiment, can be used to various PON/ADSL and the PON/VDSL interface according to different implementation details because those skilled in the art recognize that managed entity. For example, some attribute of some managed entity is described to comprise the position of specified quantity among the MIB. To the application of specific PON/ADSL or PON/VDSL network interface, although may be weakened with the interoperability of other network equipments, this quantity still can be increased or be reduced according to the present invention.
In one embodiment of the invention, the size of data cell has limited the length of each managed entity, and for example, each managed entity (and packet) is limited to the cell size of 53 bytes.
In order to minimize the number that must communicate to realize by network the managed entity of Network Management Function, the various network attributes of managed entity is cut apart and combination like this, so that relevant attribute (namely, those attributes relevant with the related network feature) be included in the managed entity, to the degree of allowing size (being 53 bytes in one embodiment) based on managed entity. Be not enough to comprise the place of all so relevant attributes in the managed entity size, these property distribution are on a plurality of relevant managed entities, wherein, the association between such managed entity is indicated by the reference (such as part 1, part 2 etc.) to a part or the subset of managed entity. Adsl line configuration profile managed entity is such example, and it comprises part 1, part 2 and part 3, each part definition some attribute relevant with the configuration profile of adsl line. Equally, according to one embodiment of present invention, channel attribute is returned synthetic one or more managed entities relevant with channel, and line properties is returned synthetic one or more managed entities relevant with circuit.
Within OMGI agreement of the present invention, what managed entity was divided into the feature of managing network device and process complys with grade (compliance level). The network equipment of the managed entity that (in the table 1 below and 10 with " CR " identifier identify) realization is essential with also realize essential managed entity and thereby be considered to the compatible every other network equipment of OMCI can interoperability.
Optional managed entity also identifies with " 0 " identifier in below the table 1 and 10. These optional managed entities may be useful, and may be required for independent network operator, but be not for the operation compatibility between the OMCI compatible equipment necessary.
Following abbreviation is used to describe managed entity at this:
The ADSL Asymmetrical Digital Subscriber Line
ANI Access Network interface
The configuration of ARC switch fault report
The ATM asynchronous transfer mode
The ADSL transceiver unit of ATU-C ONU end or central local side
The ADSL transceiver unit of ATU-R long-range (user) terminal
The BER bit error rate
The B-PON BPON
The DSL digital subscriber line
CO central office
CR requires conditionally
The CRC Cyclic Redundancy Code
The FEC forward error correction
The error correction of HEC head
The ID identifier
The LSB least significant bit
The control of MAC medium access
The MCM multi-carrier modulation
The ME managed entity
The MIB management information bank
The MMPDU Medium Access Control (MAC) Management Protocol Data Unit
The MPDU Medium Access Control (MAC) Protocol Data Unit
The MSB highest significant position
The MSDU Medium Access Control (MAC) Service Data Unit
The NMS NMS
The numbering of the descending subcarrier of NSCds
The numbering of the up subcarrier of NSCus
O is optional
OAM operation, management and maintenance
OAMP operation, management, maintenance and supply
The OLT optical line terminal
OMCI ONT management and control interface
The ONT ONT Optical Network Terminal
The ONU optical network unit
The PHY Physical layer
The POTS plain-old telephone system
The PM performance monitoring
The transmission of PMS-TC physical medium special use is assembled
The PSD power spectral density
The RFI Radio frequency interference
The SCM single-carrier modulated
The SNR signal to noise ratio
TC transmits conversion
The UNI User Network Interface
VDSL ultrahigh speed DSL
The VDSL transceiver unit of VTU-O ONU end or central local side (also
Be called VTU-C)
The VDSL transceiver unit of VTU-R remote terminal
Managed entity of the present invention as described below has defined the technical specification of an embodiment of the PON OMCI (ONT management and control interface) of xDSL subscribers' line. Those skilled in the art will appreciate that managed entity can be added or from those listed and/or managed entity attribute or the elements that can make amendment according to the requirement of heterogeneous networks or option, delete. Therefore, scope of the present invention is not limited to technical specification described below, but is intended to cover by the defined whole technical specifications of appended claim.
ADSL managed entity according to the present invention is intended to use with various ADSL agreements known in the art, and these ADSL agreements comprise: for about 9000 to the 18000 feet distance of the central office of distance service provider with the downstream data rate of about 1.5 megabit per second to 6.1 megabit per seconds be connected the ADSL of upstream data rate work of 16 kbps to 832 kbps and connect; Up to about 18600 feet distance with the downstream data rate of about 12 megabit per seconds be connected the ADSL2 of upstream data rate work of 1 megabit per second and connect; For about 6000 to the 16000 feet distance of distance central office with up to the downstream data rate of about 25 megabit per seconds be connected the ADSL2+ of upstream data rate of about 1 megabit per second and connect. Equally, VDSL managed entity according to the present invention is intended to use with various VDSL agreements known in the art, and the VDSL that these VDSL agreements are included in up to the about 55 megabit per second work on the up direction with about 55 megabit per seconds on the down direction of about 13000 feet distance connects.
The OMCI agreement managed entity that is used for operating with the ADSL network PON (for example, B-PON or G-PON) has been listed in lower tabulation 1.
| Managed entity | Essential/optional | Explanation |
| ADSL ATU-C channel performance monitoring historical data | O | The performance monitoring data of ADSL ATU-C channel |
| ADSL ATU-C performance monitoring historical data | O | The performance monitoring data in ADSL ATU-C modem path |
| ADSL ATU-R channel performance monitoring historical data | O | The performance monitoring data of ADSL ATU-R channel |
| ADSL ATU-R performance monitoring historical data | O | The performance monitoring data in ADSL ATU-R modem path |
| ADSL channel configuration profile | CR | The configuration information of channel |
| ADSL channel downstream state data | CR | The status information of down channel |
| ADSL channel uplink status data | CR | The status information of up channel |
| The descending PSD mask of ADSL (mask) profile | CR | The shielding of down channel PSD (masking) information |
| The descending RF I of ADSL frequency band profile | CR | The information of down channel RFI frequency band |
| Adsl line configuration profile part 1 | CR | The parameter configuration of adsl line |
| Adsl line configuration profile part 2 | CR | The parameter configuration of adsl line |
| Adsl line configuration profile part 3 | CR | The parameter configuration of adsl line |
| Adsl line stock and status data part 1 | CR | The stock of adsl line and status information |
| Adsl line stock and status data part 2 | CR | The stock of adsl line and status information |
| The ADSL subcarrier shields descending profile | CR | The mask information of descending subcarrier |
| The ADSL subcarrier shields up profile | CR | The mask information of up subcarrier |
| Physical pathway tip node ADSL UNI part 1 | CR | The information of the physical pathway tip node at ADSL CO modem place |
| Physical pathway tip node ADSL UNI part 2 | CR | The information of the physical pathway tip node at ADSL CO modem place |
| TC adapter performance monitoring historical data ADSL | O | The performance monitoring data of ADSL ATM data path |
Table 1
Each managed entity according to instruction of the present invention is described below. Parenthetic item indication after each managed entity, managed entity attribute be readable (R) and/or (W) that can write whether, and whether enforceable or optional this attribute is. Also set forth the required byte number of attribute.
Managed entity: physical pathway tip node ADSL UNI part 1
This managed entity represents the point of the ADSL junction among the ONU, and physical pathway is at this some place termination ADSL Modem, and the function of physical pathway layer (for example, path cost function) is performed. In the establishment of the subscriber line cards of ADSL type/deletion (namely in case initialize the ADSL subscriber line cards), ONU creates/deletes one or more examples of this managed entity automatically. In case create, five the profile pointers (pointer) in the managed entity just are configured to its default value 0x00. Yet physical pathway tip node ADSL UNI part 1 managed entity must be with reference to five effective profiles before it can operate. These five essential profile values are described below.
Relation
One or more examples of this managed entity all are comprised in the example of the subscriber line cards managed entity that is classified as the ADSL type.
Attribute
Managed entity ID:
This attribute provides unique identifier for each example of managed entity. In one embodiment, identifier comprises the numeral of 2 bytes, and this numeral is directly related with the physical location of UNI. First byte is slot ID (as the PON standard is defined in G.983.2). Second byte is port id, and the value scope of this port id is that (that is, 1 to 255): 0x01 is used to Far Left/nethermost port on the subscriber line cards from 0x01 to 0xFF, and 0x02 is used to next the right/top port, etc. (R) (enforceable) (2 bytes).
Loopback configuration:
The loopback configuration of this attribute represents physical interface. There is not loopback for value 0x00; Value 0x01 indication loopback 2 (" Loopback2 "), this loopback 2 refers to ONU to the loopback of OLT. OLT can carry out the loopback test of Physical layer after loopback 2 is set up. In case spontaneous illustration then arranges default value 0x00. (R, W) (enforceable) (1 byte).
Controlled state:
This attribute is used to activate (unlatching value 0x00) and deactivates (lock value 0x01) by the performed function of example of this managed entity. (R, W) (enforceable) (1 byte).
Duty:
This attribute indicates this managed entity whether can carry out its task. Duty has reflected the perception that receives or produce useful signal. Virtual value is for enabling (0x00) and stop using (0x01). (R) (optionally) (1 byte).
Adsl line configuration profile:
This attribute comprises the managed entity ID (as described below) of adsl line configuration profile managed entity (part 1,2 and 3), and this managed entity ID comprises the necessary data of initialization ADSL Modem. Adsl line configuration profile is not pointed in value 0x00 indication, this managed entity. Value 0x00 is default value, and when automatically creating this managed entity, set should value. (R, W) (enforceable) (2 bytes).
The ADSL subcarrier shields descending profile:
This attribute provides pointer (as described below) to the example that the ADSL subcarrier shields descending profile managed entity, and this pointer comprises the necessary data of initialization ADSL Modem. Value 0x00 indication, this managed entity does not point to the ADSL subcarrier and shields descending profile. Value 0x00 is default value, and when automatically creating this managed entity, set should value. (R, W) (enforceable) (2 bytes).
The ADSL subcarrier shields up profile:
This attribute provides pointer (as described below) to the example that the ADSL subcarrier shields up profile managed entity, and this pointer comprises the necessary data of initialization ADSL Modem. Default value 0x00 indication, this managed entity does not point to the ADSL subcarrier and shields up profile, and when automatically creating this managed entity, set should value. (R, W) (enforceable) (2 bytes)
The descending PSD mask of ADSL profile:
This attribute provides pointer (as described below) to the example of the descending PSD mask of ADSL profile managed entity, and this pointer comprises the necessary data of initialization ADSL Modem. Default value 0x00 indication, this managed entity does not point to the descending PSD mask of ADSL profile. When automatically creating this managed entity, the set default value. (R, W) (enforceable) (2 bytes)
The descending RFI frequency band of ADSL profile:
This attribute provides pointer to the example of the descending RFI frequency band of ADSL profile managed entity, and this pointer comprises the necessary data of initialization ADSL Modem. Default value 0x00 indication, this managed entity does not point to the descending RFI frequency band of ADSL profile. When automatically creating this managed entity, set value 0x00. (R, W) (enforceable) (2 bytes)
Switch fault report configuration (ARC):
This property control from the switch fault report of this managed entity. Virtual value is " off " (allowing immediately switch fault report) and " on " (forbidding switch fault report). In case finish the initial installation of ONU and provide, by the specified time interval of ARC interval properties, this attribute just can be configured to " on " or " off " for as described below. If this attribute is configured to " on ", then switch fault report is under an embargo, until this managed entity is for detecting useful signal by " ARC1nterval " specified time interval. Default value is " on ". (R, W) (optionally) (1 byte).
The ARC interval:
This attribute provides the time span that can supply. Unit is minute. Default value is 2. (R, W) (optionally) (1 byte).
Action
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Property value changes:
This notice has been reported the spontaneous variation of the attribute of this managed entity. This notice has identified this attribute and new value thereof. Provide in the property value variation table 2 below for this managed entity.
| Numbering | AVC | Explanation |
| 1-2 | N/A | |
| 3 | OpState | Duty |
| 4-10 | N/A | |
| 11-16 | Reserve |
Table 2
Alarm:
When detecting or having eliminated fault, this notice informing network management system. In a preferred embodiment, ONU and OLT know alarm list, as described in following table 3.
| Numbering | | Explanation |
| Alarm | ||
| 0 | NE_LOF | Proximal frame is lost |
| 1 | NE_LOS | Near end signal is lost |
| 2 | NE_LOL | The near-end loss of link |
| 3 | NE_LPR | The near-end power loss |
| 4 | CARD_ALM | The card alarm |
| 5 | FE_LOF | Distal frame is lost |
| 6 | FE_LOS | Remote signaling is lost |
| 7 | FE_LOL | The far-end loss of link |
| 8 | FE_LPR | The distal power loss |
| 9 | DRT_UP | Partially alarm on the data |
| 10 | DRT_DOWN | Partially alarm under the data rate threshold value |
Table 3
Managed entity: physical pathway tip node ADSL UNI part 2
This managed entity has represented the point at the ATM UNI place among the ONU, and physical pathway is at this some place termination ADSL Modem. In case create/delete the subscriber line cards of ADSL type, just automatically create/delete one or more examples of this managed entity by ONU. In case created this managed entity, eight profile pointers in the managed entity just are configured to its default value 0x00. Yet managed entity must be with reference at least two effective profiles before it can operate.
Relation
One or more examples of this managed entity all are comprised in the example of the subscriber line cards managed entity that is classified as the ADSL type.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is (defined in G.983.2 in the PON standard) slot ID. Second byte is port id, and the value scope of this port id is that (1 to 255): 0x01 is used to Far Left/nethermost port on the subscriber line cards from 0x01 to 0xFF, and 0x02 is used to next the right/top port, etc. (R) (enforceable) (2 bytes)
(for downlink bearing channel 0～4) ADSL channel configuration profile
Each attribute (for each attribute of down channel 0～4) in four attributes provides pointer (as described below) for the example of ADSL channel configuration profile managed entity for downlink bearing channel 0～4, and this pointer comprises and initializes the necessary data of ADSL Modem. Default value 0x00 is used to indicate this managed entity not point to each attribute of ADSL channel configuration profile. When automatically creating this managed entity, this default value of set. (R, W) (optionally) (for each of four Bearer Channel profiles with 2 bytes)
(for up Bearer Channel 0～4) ADSL channel configuration profile
Each attribute (for each attribute of up channel 0～4) in four attributes provides pointer (as described below) for the example of ADSL channel configuration profile managed entity for up Bearer Channel 0～4, and this pointer comprises and initializes the necessary data of ADSL Modem. When the default value 0x00 indication that automatically creates the set of this managed entity time institute, this managed entity does not point to ADSL channel configuration profile. (R, W) (optionally) (for each of four Bearer Channel profiles with 2 bytes)
Action
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Managed entity: adsl line stock and status data part 1
This managed entity comprises the circuit stock of adsl line and the part 1 of status data. In case create/delete the subscriber line cards of ADSL type, just automatically create/delete one or more examples of this managed entity by ONU.
Relation
One or more examples of this managed entity all are comprised in the example of the subscriber line cards managed entity that is classified as the ADSL type. In a single day managed entity creates, and all properties of this managed entity except the managed entity identifier just defaults to zero.
Attribute
Managed entity ID:
This attribute provides unique identification number for each example of this managed entity. The numbering of distributing is identical with the identifier of physical pathway tip node ADSL UNI, and this adsl line inventory data is relevant with this physical pathway tip node ADSL UNI. (R) (enforceable) (2 bytes)
ATU-C is vendor id G.994.1:
ATU-C G.994.1 manufacturing ID is the manufacturing ID of inserting in CL message G.994.1 such as ATU-C. This ATU-C G.994.1 manufacturing ID is comprised of 8 binary system eight bit bytes, and this comprises country code, and the back is (distributing by the area) provider's code, as proposed standard is defined in T.35. (R) (enforceable) (8 bytes)
ATU-R is vendor id G.994.1:
ATU-R G.994.1 manufacturing ID is the manufacturing ID of inserting in CLR message G.994.1 such as ATU-R. This ATU-R G.994.1 manufacturing ID comprises 8 binary system eight bit bytes that G.994.1 the manufacturing ID form is identical with above-mentioned ATU-C. (R) (enforceable) (8 bytes)
ATU-C system manufacturer ID:
ATU-C system manufacturer identifier is the manufacturing ID as being inserted in Overhead Message by ATU-C. This ATU-C system manufacturer identifier comprises 8 binary system eight bit bytes that G.994.1 the manufacturing ID form is identical with ATU-C. (R) (enforceable) (8 bytes)
ATU-R system manufacturer ID:
ATU-R system manufacturer ID is the vendor id that inserts in embedded working channel and Overhead Message as by ATU-R. This ATU-R system manufacturer ID comprises 8 binary system eight bit bytes that G.994.1 the vendor id form is identical with ATU-C. (R) (enforceable) (8 bytes)
ATU-C version number:
ATU-C version number is the version number as being inserted in Overhead Message by ATU-C. This ATU-C version number is used to Version Control and is vendor specific information, and comprises up to 16 binary system eight bit bytes. (R) (enforceable) (16 bytes)
ATU-R version number:
ATU-R version number is the version number that inserts in embedded working channel and Overhead Message as by ATU-R. This ATU-R version number is used to Version Control, and is vendor specific information, and comprises up to 16 binary system eight bit bytes. (R) (enforceable) (16 bytes)
ATU-C sequence number part 1 and 2:
The ATU-C sequence number is the sequence number as being inserted in Overhead Message by ATU-C. This ATU-C sequence number is vendor specific information and comprises up to 32 ascii characters. The part 1 of attribute comprises the one 16 character, and part 2 comprises the 2 16 character. (R) (enforceable) (16 bytes of every part)
ATU-R sequence number part 1 and 2:
ATU-R version number is the version number that inserts in embedded working channel or Overhead Message as by ATU-R. This ATU-R version number is the vendor specific information that comprises up to 32 ascii characters. Part 1 comprises the one 16 character, and part 2 comprises next 16 character. (R) (enforceable) (16 bytes of every part)
The ATU-C self-detection result:
This parameter-definition be encoded as the ATU-C self-detection result of 32 integers. If this self check is passed through, then the highest effective eight bit byte of self-detection result is 00hex, and if fail self-test, then the highest effective eight bit byte of self-detection result is 01hex. The explanation of other eight bit byte be manufacturer discretionary and can with G.994.1 be combined to be explained with system manufacturer ID. (R) (enforceable) (4 bytes)
The ATU-R self-detection result:
This parameter-definition be encoded as the ATU-R self-detection result of 32 integers. If self check is passed through, then the highest effective eight bit byte of self-detection result is 00hex, and if fail self-test, then the highest effective eight bit byte of self-detection result is 01hex. The explanation of other eight bit bytes is that manufacturer is discretionary, and can with G.994.1 be combined to be explained with system manufacturer ID. (R) (mandatory) (4 bytes)
ATU-C transmission system ability:
The ATU-C transmission system capabilities list of this parameter-definition type of coding. Defined position is encoded into bitmap in the table 4 below this parameter utilization. (R) (enforceable) (7 bytes)
ATU-R transmission system ability:
The ATU-R transmission system capabilities list of this parameter-definition different coding type. Defined position is encoded into bitmap in the table 4 below this parameter utilization. (R) (enforceable) (7 bytes)
Initialize successfully/failure cause:
This parameter represents the last time of performed complete initialized successful or failure (and failure cause) on this circuit. This parameter is encoded as the integer in 0 to 5 scope, and this parameter is by following coding:
0 success
1 configuration error
For example, when circuit when ATU does not support to be initialised in the ADSL transmission system for the maximum delay that disposes of one or more Bearer Channels or the minimum that disposes or maximum data rate therein, this mistake occurs when inconsistent with configuration parameter.
2 be configured on this circuit unreasonable
If minimum data rate can't be realized with the minimal noise tolerance limit of one or more Bearer Channels, maximum PSD grade, maximum interest for delinquency and maximum bit error rate on this circuit, this mistake then occurs.
3 communication issues
If because wrong message or asyntactic message or in handshake procedure G.994.1, can not select commonality schemata or because overtime, this mistake occur then.
4 do not detect the ATU of equity
If the ATU of equity does not power up, connects, if perhaps circuit is oversize and do not allow to detect the ATU of equity, this mistake occurs then.
5 any other or unknown initialization failure causes. (R) (enforceable) (1 byte)
Action
Obtain: obtain one or more attributes.
Notice
Nothing.
Following table 4 has been explained the ATU transmission system capabilities attribute in the ADSL managed entity. Utilize following definition to be encoded into bitmap and represent (if do not allow then be 0, if allow then be 1):
| The position | Expression |
| Eight bit byte 1 | |
| 1 | ANSI T1.413 |
| 2 | The appendix C of TS 101 388 v1.3.1 |
| 3 | G.992.1 be operated in (appendix A G.992.1) on the non-overlapped frequency spectrum of POTS |
| 4 | G.992.1 be operated in (appendix A G.992.1) on the overlapping frequency spectrum of POTS |
| 5 | G.992.1 be operated in (appendix B G.992.1) on the non-overlapped frequency spectrum of ISDN |
| 6 | G.992.1 be operated in (appendix B G.992.1) on the overlapping frequency spectrum of ISDN |
| 7 | G.992.1 in conjunction with the non-overlapped frequency spectrum work of TCM-ISDN (appendix C G.992.1) |
| 8 | G.992.1 in conjunction with the overlapping frequency spectrum work of TCM-ISDN (appendix C G.992.1) |
| Eight bit byte 2 | |
| 9 | G.992.2 be operated in (appendix A G.992.2) on the non-overlapped frequency spectrum of POTS |
| 10 | G.992.2 be operated in (appendix B G.992.2) on the overlapping frequency spectrum of POTS |
| 11 | G.992.2 in conjunction with the non-overlapped frequency spectrum work of TCM-ISDN (appendix C G.992.2) |
| 12 | G.992.2 in conjunction with the overlapping frequency spectrum work of TCM-ISDN (appendix C G.992.2) |
| 13 | Reserve |
| 14 | Reserve |
| 15 | Reserve |
| 16 | Reserve |
| Eight bit byte 3 | |
| 17 | Reserve |
| 18 | Reserve |
| 19 | G.992.3 be operated in (appendix A G.992.3) on the non-overlapped frequency spectrum of POTS |
| 20 | G.992.3 be operated in (appendix A G.992.3) on the overlapping frequency spectrum of POTS |
| 21 | G.992.3 be operated in (appendix B G.992.3) on the non-overlapped frequency spectrum of ISDN |
| 22 | G.992.3 be operated in (appendix B G.992.3) on the overlapping frequency spectrum of ISDN |
| 23 | Reserve |
| 24 | Reserve |
| Eight bit byte 4 | |
| 25 | G.992.4 be operated in (appendix A G.992.4) on the non-overlapped frequency spectrum of POTS. |
| 26 | G.992.4 be operated in (appendix A G.992.4) on the overlapping frequency spectrum of POTS. |
| 27 | Reserve. |
| 28 | Reserve. |
| 29 | G.992.3 all figure patterns are with non-overlapped frequency spectrum work (appendix I G.992.3). |
| 30 | G.992.3 all figure patterns are with overlapping frequency spectrum work (appendix I G.992.3). |
| 31 | G.992.3 all figure patterns are with non-overlapped frequency spectrum work (appendix J G.992.3). |
| 32 | G.992.3 all figure patterns are with overlapping frequency spectrum work (appendix J G.992.3). |
| Eight bit byte 5 | |
| 33 | G.992.4 all figure patterns are with non-overlapped frequency spectrum work (appendix I G.992.4) |
| 34 | G.992.4 all figure patterns are with overlapping frequency spectrum work (appendix I G.992.4) |
| 35 | G.992.3 reach the work of expansion at POTS, pattern 1 (non-overlapped, wide up) (appendix L G.992.3) |
| 36 | G.992.3 reach the work of expansion at POTS, pattern 2 (non-overlapped, narrow up) (appendix L G.992.3) |
| 37 | G.992.3 reach the work of expansion at POTS, mode 3 (overlapping, wide up) (appendix L G.992.3) |
| 38 | G.992.3 reach the work of expansion at POTS, pattern 4 (overlapping, narrow up) (appendix L G.992.3) |
| 39 | G.992.3 the up work of the expansion on the non-overlapped frequency spectrum of POTS (appendix M G.992.3) |
| 40 | G.992.3 the up work of the expansion on the overlapping frequency spectrum of POTS (appendix M G.992.3) |
| Eight bit byte 6 | |
| 41 | G.992.5 be operated in (appendix A G.992.5) on the non-overlapped frequency spectrum of POTS |
| 42 | G.992.5 be operated in (appendix A G.992.5) on the overlapping frequency spectrum of POTS |
| 43 | G.992.5 be operated in (appendix B G.992.5) on the non-overlapped frequency spectrum of ISDN |
| 44 | G.992.5 be operated in (appendix B G.992.5) on the overlapping frequency spectrum of ISDN |
| 45 | Reserve |
| 46 | Reserve |
| 47 | G.992.5 all figure patterns are with non-overlapped frequency spectrum work (appendix I G.992.5) |
| 48 | G.992.5 all figure patterns are with overlapping frequency spectrum work (appendix I G.992.5) |
| Eight bit byte 7 | |
| 49 | G.992.5 all figure patterns are with non-overlapped frequency spectrum work (appendix J G.992.5) |
| 50 | G.992.5 all figure patterns are with overlapping frequency spectrum work (appendix J G.992.5) |
| 51 | G.992.5 the up work of the expansion on the non-overlapped frequency spectrum of POTS (appendix M G.992.5) |
| 52 | G.992.5 the up work of the expansion on the overlapping frequency spectrum of POTS (appendix M G.992.5) |
| 53 | Reserve |
| 54 | Reserve |
| 55 | Reserve |
| 56 | Reserve |
Table 4
Managed entity: adsl line stock and status data part 2
This managed entity comprises the circuit stock of adsl line and the part 2 of status data. In case create/delete the subscriber line cards of ADSL type, one or more examples of this managed entity are just automatically created/are deleted by ONU.
Relation
One or more examples of this managed entity all are comprised in the example of the subscriber line cards managed entity that is classified as the ADSL type.
Attribute
Managed entity ID:
This attribute provides unique identifier for each example of this managed entity. The numbering of distributing is identical with the ID of physical pathway tip node ADSL UNI, and this ATU-R physical data is relevant with this physical pathway tip node ADSL UNI. (R) (enforceable) (2 bytes)
The ADSL transmission system:
This parameter-definition the transmission system in using. Defined position is encoded into bitmap and represents in this table 4 above parameter utilization. (R) (enforceable) (7 bytes)
The line power controlled state:
This circuit has four kinds of possible power management states, is numbered 0～3, and corresponds respectively to:
The state that 0=L0-synchronously-this line status (L0) is when having complete transmittability for circuit (, working time (showtime)).
1=L1-power reduces transfer of data-when having transmission on the line but net data rate when reducing, and uses this line status (L1) (for example, only being used for OAM and more high-rise connection and session control). This state only is used for by the G.992.2 application of standardized administration.
2=L2-power reduces transfer of data-when having transmission on the line but net data rate when reducing, and uses this line status (L2) (for example, only being used for OAM and more high-rise connection and session control). G.992.3 and the G.992.4 application of standardized administration this state only is used for by.
3=L3-inactivity-when not having the power of transmission on the line, use this line status (L3). (R) (enforceable) (1 byte)
The downgoing line decay:
This parameter is poor with by the received general power of ATU-R of the general power of being transmitted by ATU-C on all subcarriers measured at diagnostic mode and during initializing. The downgoing line attenuation range is that wherein step-length is 0.1dB from 0 (0) to+127 (1270) dB. Particular value (0xFFFF) indication, Line Attenuation goes beyond the scope and can not represent with the usable levels of attribute. (R) (enforceable) (2 bytes)
The uplink decay:
This parameter is the general power of being transmitted by ATU-R and poor (unit is dB) by the received general power of ATU-C on all subcarriers measured at diagnostic mode and during initializing. The uplink attenuation range is that wherein step-length is 0.1dB from 0 (0) to+127 (1270) dB. Particular value (0xFFFF) indication, Line Attenuation goes beyond the scope and can not represent with the usable levels of attribute. (R) (enforceable) (2 bytes)
The downstream signal decay:
This parameter is that the general power of being transmitted by ATU-C on all measured during the working time (that is, the period when ATU-R and ATU-C can operate) subcarriers is the poor of dB with unit by the received general power of ATU-R. The downgoing line attenuation range is that wherein step-length is 0.1dB from 0 (0) to+127 (1270) dB. Particular value (0xFFFF) indication, Line Attenuation goes beyond the scope and can not be represented by the usable levels of attribute. (R) (enforceable) (2 bytes)
The upward signal decay:
This parameter is that the general power of being transmitted by ATU-R on all measured during working time subcarriers is the poor of dB with unit by the received general power of ATU-C. The uplink attenuation range is that wherein step-length is 0.1dB from 0 (0) to+127 (1270) dB. Particular value (0xFFFF) indication, Line Attenuation goes beyond the scope and can not be represented by the usable levels of attribute. (R) (enforceable) (2 bytes)
Descending Signal to Noise Ratio Margin:
Descending Signal to Noise Ratio Margin is the maximal increment take dB as unit of the noise power that receives in the ATU-R place, so that BER requires to satisfy all downlink bearing channels. The scope of descending SNR tolerance limit is from-64 (0) dB to+63 (1280) dB, and wherein step-length is 0.1dB. Particular value (0xFFFF) indication, this parameter goes beyond the scope and can not be expressed. (R) (enforceable) (2 bytes)
Up Signal to Noise Ratio Margin:
Up Signal to Noise Ratio Margin is the maximal increment take dB as unit of the noise power that receives in the ATU-C place, so that BER requires to satisfy all up Bearer Channels. Up SNR marginal range is from-64 (0) dB to+63 (1280) dB, and wherein step-length is 0.1dB. Particular value (0xFFFF) indication, parameter goes beyond the scope and can not be expressed. (R) (enforceable) (2 bytes)
The accessible data rate of descending maximum:
This parameter indication ATU-C emitter and the present accessible maximum downstream net data rate of ATU-R receiver. This speed is encoded take bps as unit. (R) (enforceable) (4 bytes)
The accessible data rate of up maximum:
This parameter indication ATU-R emitter and the up net data rate of the present accessible maximum of ATU-C receiver. This speed is encoded take bps as unit. (R) (enforceable) (4 bytes)
Descending actual power spectrum density:
This parameter be the used subcarrier (down user data is assigned to its subcarrier) that transmits of ATU-C upper ITU-T G.997.1 in the average down transmitting power spectrum density of defined U-C reference point place when measuring. This power spectral density rate range is that wherein step-length is 0.1dB from-90 (O) dBm/Hz to 0 (900) dBm/Hz. Particular value (0xFFFF) indication, parameter goes beyond the scope and can not be expressed. (R) (enforceable) (2 bytes)
Up actual power spectrum density:
The average uplink transmission power spectrum density of this parameter when to be that the used subcarrier (uplink user data is assigned to its subcarrier) that transmits of ATU-C is upper measure at U-C reference point place. This power spectral density rate range is that wherein step-length is 0.1dB from-90 (0) dBm/Hz to 0 (900) dBm/Hz. Particular value (0xFFFF) indication, this parameter goes beyond the scope and can't represent. (R) (enforceable) (2 bytes)
The total transmitting power of descending reality:
This parameter be transmitted by ATU-C, be in transmitting power total amount when measuring in the U-C reference point. The gross output level range is from-31 (0) dBm to+31 (620) dBm, and wherein step-length is 0.1dB. Particular value (0xFFFF) indication, parameter goes beyond the scope and can't represent. In one embodiment, descending specified total transmitting power best estimate that is this parameter. (R) (enforceable) (2 bytes)
The total transmitting power of up reality:
This parameter be transmitted by ATU-R, ITU-T G.997.1 in the transmitting power total amount of defined U-R reference point place when measuring. The gross output level range is from-31 (0) dBm to+31 (620) dBm, and wherein step-length is 0.1dB. Particular value (0xFFFF) indication, parameter goes beyond the scope and can't represent. In one embodiment, up specified total transmitting power can be taken as the best estimate of this parameter. (R) (enforceable) (2 bytes)
Initialization-the final state of downlink transfer:
The init state that the on the line last success on the performed last down direction in initializing fully of this parameter representative is transmitted. Init state is defined within the independent ADSL proposed standard, and since 0 (if adopting G.994.1) or 1 (if not adopting G.994.1) counting, until the working time. This parameter must be explained according to the ADSL transmission system.
Only have when after initializing failure fully, activating on the line the circuit diagnostic program, just available this parameter. The line diagnosis program can or spontaneously activate by ATU-C or ATU-R by operator's (by compulsory line configuring parameter of line status) of system. (R) (enforceable) (1 byte)
Initialization-the final state of uplink:
The init state that the on the line last success on the performed last up direction in initializing fully of this parameter representative is transmitted. Init state is defined within the independent ADSL proposed standard, and since 0 (if adopting G.994.1) or 1 (if not adopting G.994.1) counting, until the working time. This parameter must be explained according to the ADSL transmission system.
Only have when after initializing failure fully, activating diagnostic program on the line, just available this parameter. The line diagnosis program can or spontaneously activate by ATU-C or ATU-R by operator's (by compulsory line configuring parameter of line status) of system. (R) (enforceable) (1 byte)
Action
Obtain: obtain one or more attributes.
Notice
Nothing.
Managed entity: ADSL channel downstream state data
This managed entity comprises ADSL channel downstream state data. In case create/delete the subscriber line cards of ADSL type, one or more examples of this managed entity are just automatically created/are deleted by ONU.
Relation
One or more examples of this managed entity all are comprised in the example of the subscriber line cards managed entity that is classified as the ADSL type.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. Two highest significant position sign Bearer Channel ID of the first byte. Six least significant bit sign (defined in G.983.2) slot ID of the first byte. The second byte is port id, and the value scope of this port id is used to Far Left/nethermost port on the subscriber line cards for (1 to 255): 0x01 from 0x01 to 0xFF, and 0x02 is used to the port on next the right/top etc. (R) (enforceable) (2 bytes)
The actual delay that interweaves:
This parameter is the actual unidirectional delay that interweaves of being introduced by PMS-TC between α and the β reference point, does not comprise delay in L1 and the L2 state (as top described in " the line power controlled states of adsl line stock and status data part 2 managed entities "). In L1 and L2 state, this parameter comprises the delay that interweaves in the previous L0 state. This parameter from S and D parameter, be exported into
Wherein " S " is the code element of each code word, and " D " is interleave depth, and
Expression is rounded up to next higher integer. Actual interweaving postpones to encode as unit take ms, is rounded up to immediate ms. (R) (enforceable) (1 byte)
Actual data rate:
This parameter is reported actual net data rate to the work Bearer Channel, does not comprise the speed in L1 and the L2 state. In L1 or L2 state, this parameter comprises the net data rate in the previous L0 state. Data rate is encoded take bps as unit. (R) (enforceable) (4 bytes)
Previous data rate:
This parameter reported Bearer Channel before nearest rate variation event occurs just once with the previous net data rate of its work, do not comprise all transition between L0 state and L1 or the L2 state. When the power management state transition, for example, initializing fully or fast (short) initializations, high speed retraining, power down or during in dynamic rate adaptation, can the generation rate variation. Speed is encoded take bps as unit. (R) (enforceable) (4 bytes)
Action
Obtain: obtain one or more attributes.
Notice
Nothing.
Managed entity: ADSL channel uplink status data
This managed entity comprises ADSL channel uplink status data. In case create/delete the subscriber line cards of ADSL type, one or more examples of this managed entity just should automatically be created by ONU/delete.
Relation
One or more examples of this managed entity should all be comprised in the example of the subscriber line cards managed entity that is classified as the ADSL type.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. Two highest significant positions of the first byte are Bearer Channel ID. Six least significant bits of the first byte are (defined in G.983.2) slot ID. The second byte is port id, and the value scope of this port id is used to Far Left/nethermost port on the subscriber line cards for (1 to 255): 0x01 from 0x01 to 0xFF, and 0x02 is used to next the right/top port, etc. (R) (enforceable) (2 bytes)
The actual delay that interweaves:
This parameter is the actual unidirectional delay that interweaves of being introduced by PMS-TC between α and the β reference point, does not comprise the delay in L1 and the L2 state. In L1 and L2 state, this parameter comprises the delay that interweaves in the previous L0 state. This parameter from S and D parameter, be exported into
Wherein " S " is the code element of each code word, and " D " is " interleave depth ", and
Expression is rounded up to higher integer. Actual interweaving postpones to encode take ms as unit (being rounded up to immediate ms). (R) (enforceable) (1 byte)
Actual data rate:
This parameter has been reported the actual net data rate of Bearer Channel with its work, does not comprise the speed in L1 and the L2 state. In L1 or L2 state, this parameter comprises the net data rate in the previous L0 state. and this data rate is encoded take bps as unit. (R) (enforceable) (4 bytes)
Previous data rate:
This parameter reported Bearer Channel before nearest rate variation event occurs just once with the previous net data rate of its work, do not comprise all transition between L0 state and L1 or the L2 state. When the power management state transition, for example, when fully initialization or fast initialization, high speed retraining, power down or dynamic rate adaptation, can change by generation rate. This speed is encoded take bps as unit. (R) (enforceable) (4 bytes)
Action
Obtain: obtain one or more attributes.
Notice
Nothing.
Managed entity: adsl line configuration profile part 1
This managed entity comprises the part 1 of the line configuring profile of adsl line. The example of this managed entity is answered the request of OLT and is created/deletes.
Relation
Zero or the Multi-instance that have this managed entity, and zero or Multi-instance of this managed entity can be relevant with zero or the Multi-instance of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create (arranging by creating)) (enforceable) (2 bytes)
The ATU transmission system is enabled:
This configuration parameter has defined will be by (that is transmission system type of coding that, ATU-C) allows of the near-end ATU on this circuit. This parameter only is used for the reference of Q interface. This above parameter utilization in the table 4 defined position be encoded into bitmap and represent. (R, W, Set-by-create) (enforceable) (7 bytes)
Compulsory power management state:
This configuration parameter has defined and will come compulsory line status by the near-end ATU on this circuit. This configuration parameter is encoded as to have such as undefined integer value:
0 forces circuit to transit to the complete duty of L0 from the L3 idle condition. This transition requires described (fast) initialize routine. After reaching the L0 state, circuit can transit to the L2 low power state or withdraw from L2 low power state (if the L2 state is enabled). If do not arrive the L0 state (after the discretionary number of retries of manufacturer and/or manufacturer discretionary overtime in), then initialize unsuccessfully. No matter when circuit is in the L3 state, always attempts to transit to the L0 state, until force it to enter another state by this configuration parameter.
2 force circuit to transit to the L2 low power state from the full duty of L0. This transition requires to enter into the L2 pattern. This is professional outer (out-of-service) test value, is used for triggering the L2 pattern.
3 force this circuit to transit to the L3 idle condition from the full duty of L0 or L2 low power state. This transition requires (orderly) shutdown procedure. After arriving the L3 state, circuit remains in the L3 idle condition, until force it to enter another state by this configuration parameter. (R, W, Set-by-create) (enforceable) (1 byte)
Power management state is enabled:
This configuration parameter defined ATU-C or ATU-R can spontaneous transition line status to this circuit. Utilize as give a definition and this configuration parameter is encoded into bitmap represents (if do not allow then be 0, if allow then be 1):
Position 0:L3 state (idle condition)
Position 1:L1/L2 state (low power state)
(R, W, Set-by-create) (the pressure row) (1 byte)
Descending target noise margin:
To be the ATU-R receiver require the noise margin to initialize and should realize or better realize in order to be successfully completed with respect to the BER of each downlink bearing channel for this. The scope of target noise margin is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. (R, W, Set-by-create) (enforceable) (2 bytes)
Up target noise margin:
To be the ATU-C receiver require the noise margin to initialize and should realize or better realize in order to be successfully completed with respect to the BER of each up Bearer Channel for this. The scope of target noise margin is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. (R, W, Set-by-create) (enforceable) (2 bytes)
Descending maximum noise tolerance limit:
This is the maximum noise tolerance limit that the ATU-R receiver is attempted to keep. If noise margin is higher than this grade, then ATU-R request ATU-C reduces the ATU-C transmitting power, to obtain to be lower than the noise margin (if supporting this function) of this restriction. The scope of maximum noise tolerance limit is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. Particular value 0xFFFF is used to indicate and will use the restriction of maximum noise tolerance limit. (R, W, Set-by-create) (enforceable) (2 bytes).
Up maximum noise tolerance limit:
This is the maximum noise tolerance limit that the ATU-C receiver is attempted to keep. If this noise margin is higher than this grade, then ATU-C request ATU-R reduces the ATU-R transmitting power, in order to obtain to be lower than the noise margin (if supporting this function) of this restriction. The scope of maximum noise tolerance limit is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. Particular value 0xFFFF is used to indicate and will use the restriction of maximum noise tolerance limit. (R, W, Set-by-create) (enforceable) (2 bytes)
Descending minimal noise tolerance limit:
This is the minimal noise tolerance limit that the ATU-R receiver can be tolerated. If noise margin drops under this grade, then ATU-R request ATU-C increases the ATU-C transmitting power. If it is impossible to increase the ATU-C transmitting power, the defective of tolerance limit loss (LOM) then appears, and ATU-R failure and trial reinitialize and notify NMS/EMS 70. The scope of minimal noise tolerance limit is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. (R, W, Set-by-create) (enforceable) (2 bytes)
Up minimal noise tolerance limit:
This is the minimal noise tolerance limit that the ATU-C receiver should be tolerated. If noise margin drops under this grade, then ATU-C request ATU-R increases the ATU-R transmitting power. If increased power is impossible, the defective of tolerance limit loss (LOM) then appears, and ATU-C failure and trial reinitialize and notify NMS/EMS 70. The scope of minimal noise tolerance limit is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. (R, W, Set-by-create) (enforceable) (2 bytes)
The downstream rate adapt mode:
The adaptive ATU-C of this parameter schedule speed is in the mode of operation of transmission direction. This parameter can adopt three values.
1=pattern 1: manually-manually change speed.
During startup:
Descending minimum data rate parameter has been stipulated the ATU-C emitter for the data rate of each Bearer Channel with its work, and this data rate has at least the same large (with respect to the required BER of each downlink bearing channel) of descending target noise margin or the better descending noise margin with defined. If ATU-C fails to realize descending minimum data rate into one of Bearer Channel, then ATU-C fails to initialize, and NMS/EMS70 is notified. Although perhaps ATU-C and circuit can support higher data rate, ATU-C can't essential data rate be launched to be higher than each Bearer Channel.
During the working time:
The ATU-C emitter is kept the descending minimum data rate of the defined of each Bearer Channel.
This speed of 2=pattern 2:AT_INIT-is only selected when starting automatically, and does not change after that.
During startup:
Descending minimum speed limit parameter regulation ATU-C emitter is for the minimum data rate of each Bearer Channel with its work, and this minimum data rate has at least the same large (with respect to the required BER of each Bearer Channel) of descending target noise margin or the better descending noise margin with defined. If ATU-C fails to realize descending minimum data rate into one of Bearer Channel, then ATU-C fails to initialize, and NMS/ is notified. If the ATU-C emitter can be supported higher downstream data rate when initializing, then distribute the data rate (so being added to 100% at Bearer Channel) that exceeds according to the ratio (0 to 100%) of the rate adaptation rate parameter defined of each Bearer Channel and at the downlink bearing interchannel. When in one of Bearer Channel, reaching descending maximum data rate, still according to its relative rate adaptation rate parameter, remaining is exceeded bit rate allocation to other Bearer Channels. As long as downstream data rate is lower than the descending maximum data rate of one of Bearer Channel, just preferentially increase data rate than reducing transmitting power.
During the working time:
During the working time, do not allow downstream data rate adaptive. Keep the downstream data rate of during the initialization of each Bearer Channel, having fixed.
The 3=mode 3: dynamically-data rate selected when initializing automatically, and during work (working time) by continuous setup. The dynamic rate adaptation pattern is optional. All relevant configuration parameters also are optional.
During startup: in mode 3, ATU-C is as starting in the pattern 2.
During the working time:
During the working time, about fitting percentage, allow rate adaptation, be used between Bearer Channel, distributing exceeding data rate (referring to top pattern 2), and guarantee that descending minimum data rate can obtain at the required BER place of each Bearer Channel or better. Downstream data rate can change between descending minimum data rate and descending maximum data rate. When satisfying the condition that is given for descending inclined to one side noise margin and descending inclined to one side interval (or being used for descending lower inclined to one side noise margin and descending lower inclined to one side interval), it is adaptive to carry out downstream rate. This means:
● for upper inclined to one side action: during descending inclined to one side noise margin during descending noise margin is higher than descending minimum interval, inclined to one side rate adaptation in the permission (that is, when RAU is unusual).
● for lower inclined to one side action: during descending lower inclined to one side noise margin during descending noise margin is lower than descending minimum interval, allow lower inclined to one side rate adaptation (that is, when RAD is unusual).
As long as downstream data rate is lower than the descending maximum data rate of one of Bearer Channel, just preferentially increase data rate than reducing transmitting power. (R, W, Sct-by-create) (enforceable) (1 byte)
The upstream rate adapt mode:
This parameter has stipulated that the ATU-R of rate adaptation is in the mode of operation of transmission direction. Only have and when rate adaptation function is supported, just use this parameter, and this parameter can adopt three values:
1=is manual
2＝AT_INIT
3=is dynamic
The definition of each value is identical with above-mentioned its definition in the downstream rate adapt mode, just replaces ATU-C with ATU-R and with the up row of displacing. (R, W, Set-by-create) (enforceable) (1 byte)
Descending inclined to one side noise margin:
If descending noise margin is higher than descending inclined to one side noise margin and rests on the time that surpasses on the descending inclined to one side noise margin by inclined to one side rate adaptation interval defined on the descending minimum, then ATU-R increases descending net data rate. The scope of descending inclined to one side noise margin is from 0dB (0) to 31 (310) dB, and wherein step-length is 0.1dB. (R, W, Set-by-create) (optionally) (2 bytes)
Up inclined to one side noise margin:
If the upstream noise tolerance limit is higher than up inclined to one side noise margin and rests on the time that surpasses on the up inclined to one side noise margin by inclined to one side rate adaptation interval defined on the up minimum, then ATU-C increases up net data rate. Up inclined to one side noise margin scope is from 0dB (0) to 31 (310) dB, and wherein step-length is 0.1dB. (R, W, Set-by-create) (optionally) (2 bytes)
Up PSD mask is selected:
Which up PSD mask this configuration parameter defines is activated. This parameter only is used to appendix J and M G.992.3/5. Select parameter because in MIB, only defined one, so identical selective value is used for all associative modes that ATSE line configuring parameter is enabled. The scope of this configuration parameter is from 1 to 9 and utilizes as giving a definition to select mask.
Selected mask
Up PSD mask selective value appendix J G.992.3/5 appendix M G.992.3/5
1 ADLU-32 EU-32
2 ADLU-36 EU-36
3 ADLU-40 EU-40
4 ADLU-44 EU-44
5 ADLU-48 EU-48
6 ADLU-52 EU-52
7 ADLU-56 EU-56
8 ADLU-60 EU-60
9 ADLU-64 EU-64
(R, W, Set-by-create) (enforceable) (1 byte)
Up minimal-overhead speed:
This attribute definition the minimum speed limit of the message based expense kept at up direction by ATU. This attribute take bps represent and scope as from 4000 to 64000bps. This attribute only for according to standard G.992.3, G.992.4 and the system of G.992.5 working effective. (R, W, Set-by-create) (optionally) (2 bytes)
Descending minimal-overhead speed:
This attribute definition the minimum speed limit of the message based expense kept at down direction of ATU. This attribute take bps represent and scope as from 4000 to 64000bps. This attribute only for according to standard G.992.3, G.992.4 and the system of G.992.5 working effective. (R, W, Set-by-create) (optionally) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Nothing.
Managed entity: adsl line configuration profile part 2
This managed entity has comprised the part 2 of the line configuring profile of adsl line. The example of this managed entity is answered the request of OLT and is created/deletes.
Relation
Zero or more examples that should have this managed entity, and can this managed entity is relevant with zero or the more examples of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
The descending minimum interval of upper inclined to one side rate adaptation:
This parameter-definition descending noise margin before ATU-R attempts to increase descending net data rate, should rest on descending on time interval on the noise margin partially. The scope in this time interval is from 0 to 16383s. (R, W, Set-by-create) (optionally) (2 bytes)
The up minimum interval of upper inclined to one side rate adaptation:
This parameter-definition the upstream noise tolerance limit before ATU-C attempts to increase up net data rate, should rest on up on time interval on the noise margin partially. The scope in this time interval is from 0 to 16383s. (R, W, Set-by-create) (optionally) (2 bytes)
Descending lower inclined to one side noise margin:
If descending noise margin is lower than descending lower inclined to one side noise margin and rests on greater than under the value by the time of inclined to one side rate adaptation interval defined under the descending minimum, then ATU-R attempts to reduce descending net data rate. The scope of descending lower inclined to one side noise margin is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. (R, W, Set-by-create) (optionally) (2 bytes)
Up lower inclined to one side noise margin:
If the upstream noise tolerance limit is lower than up lower inclined to one side noise margin and rests on greater than under the value by the time of inclined to one side rate adaptation interval defined under the up minimum, then ATU-C attempts to reduce up net data rate. The scope of up lower inclined to one side noise margin is that wherein step-length is 0.1dB from 0 (0) to 31 (310) dB. (R, W, Set-by-create) (optionally) (2 bytes)
The descending minimum interval of lower inclined to one side rate adaptation:
This parameter-definition descending noise margin before ATU-R attempts to reduce descending net data rate, should rest on time interval under the descending lower inclined to one side noise margin. The scope in this time interval is from 0 to 16383s. (R, W, Set-by-create) (optionally) (2 bytes)
The up minimum interval of lower inclined to one side rate adaptation:
This parameter-definition the upstream noise tolerance limit before ATU-C attempts to reduce up net data rate, should rest on time interval under the up lower inclined to one side noise margin. The scope in this time interval is from 0 to 16383s. (R, W, Set-by-create) (optionally) (2 bytes)
Compulsory ATU impedance state:
This configuration parameter defined will be on near-end ATU compulsory impedance state. This configuration parameter only is applied to the T/S interface. This configuration parameter is only for G.992.3 (appendix A), G.992.4 (appendix A) and G.992.5 (appendix A) effectively. This parameter is encoded as to be had such as undefined integer value:
1 forces near-end ATU to enter dead status.
2 force near-end ATU to enter inactive state.
3 force near-end ATU to enter active state.
(R, W, Set-by-create) (enforceable) (1 byte)
The L0 time:
This parameter has represented from the L2 state and has been withdrawn into the minimum time (unit is second) that next time enters between the L2 state. This parameter is only for G.992.3, G.992.4 and G.992.5 effective. The scope of this parameter is from 0 to 255s. (R, W, Set-by-create) (enforceable) (1 byte)
The L2 time:
This parameter has represented from entering the L2 state to the minimum time the first power fine setting the L2 state (unit for second), and also represents the minimum time between twice continuous power fine setting in the L2 state. This parameter is only for G.992.3, G.992.4 and G.992.5 effective. The scope of this parameter is from 0 to 255s. (R, W, Set-by-create) (enforceable) (1 byte).
Descending maximum rated power spectrum density:
This parameter has represented the maximum rated emission PSD (unit is dBm/Hz) on initialization and the down direction during the working time. For each pattern of enabling in ATSE line configuring parameter has defined single descending maximum rated power spectrum density parameter. This parameter only for G.992.3, G.992.4 and G.992.5 effectively and this scope be that wherein step-length is 0.1dB from-60 (0) to-30 (900) dBm/Hz. (R, W, Set-by-create) (enforceable) (2 bytes)
Up maximum rated power spectrum density:
This parameter has represented the maximum rated emission PSD (unit is dBm/Hz) on initialization and the up direction during the working time. For each pattern of enabling in ATSE line configuring parameter defines single up maximum rated power spectrum density parameter. This parameter is only for G.992.3, G.992.4 and G.992.5 effective. The scope of this parameter is that wherein step-length is 0.1dB from-60 (0) to-30 (900) dBm/Hz. (R, W, Set-by-create) (enforceable) (2 bytes)
Descending maximum rated total transmitting power:
This parameter has represented the maximum rated total transmitting power (unit is dBm) on initialization and the down direction during the working time. This parameter only for G.992.3, G.992.4 and G.992.5 effectively and scope be that wherein step-length is 0.1dB from 0 (0) to 25.5 (255) dBm. (R, W, Set-by-create) (enforceable) (1 byte)
Up maximum rated total transmitting power:
This parameter has represented the maximum rated total transmitting power (unit is dBm) on initialization and the up direction during the working time. This parameter only for G.992.3, G.992.4 and G.992.5 effectively and scope be that wherein step-length is 0.1dB from 0 (0) to 25.5 (255) dBm. (R, W, Set-by-create) (enforceable) (1 byte)
Up maximum total received power:
This parameter has represented the maximum up total received power (unit is dBm) on one group of subcarrier, as defined in the relevant recommendation. ATU-C request ascending power reduces, so that the up total received power on that group subcarrier is in or is lower than the maximum that disposes. This parameter is only for G.992.3, G.992.4 and G.992.5 effective. This parameter area is that wherein step-length is 0.1dB from-25.5 (0) to 25.5 (510) dBm. Particular value 0xFFFF is used to indication will not apply up maximum total received power restriction. (R, W, Set-by-create) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Nothing.
Managed entity: adsl line configuration profile part 3
This managed entity comprises the part 3 of the line configuring profile of adsl line. The example of this managed entity is answered the request of OLT and is created/deletes.
Relation
The zero or the Multi-instance that have this managed entity, and can zero or the Multi-instance of this managed entity is relevant with zero or the Multi-instance of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
Compulsory loop diagnostics pattern:
Whether this configuration parameter has defined forces this circuit to enter the loop diagnostics pattern by the near-end ATU on this circuit. This configuration parameter is only for G.992.3, G.992.4 and G.992.5 effective. This attribute is encoded as to have such as undefined integer value:
0 forbids that near-end ATU carries out the loop diagnostics model program on the line. The loop diagnostics model program can also start by ATU at the Remote End (being ATU-R).
1 forces near-end ATU to carry out the loop diagnostics program.
Before this circuit can be forced into the loop diagnostics pattern, this circuit need to be forced into the L3 state. Only have when the line power controlled state is the L3 state, this circuit just can be forced into the loop diagnostics model program. When the loop diagnostics model program was successfully completed, access point was reset to 0 with the MIB element of compulsory loop diagnostics pattern, and circuit returns to the idle condition that remains on L3. The loop diagnostics data are at least until this circuit is forced to into the L0 state all is available. If the loop diagnostics program can not be successfully completed (after the discretionary number of retries of manufacturer and/or manufacturer discretionary overtime in), then initialize unsuccessfully. As long as the loop diagnostics program is not successfully completed, repay examination, until no longer force the loop diagnostics pattern by this configuration parameter at this circuit like this. (R, W, Set-by-create) (enforceable) (1 byte)
Compulsory automatic mode cold start-up:
This parameter is defined the performance test that improves the automatic mode of ATU support when enabling the automatic mode of ATU support in MIB. Virtual value is 0 and 1. The variation indication of this parameter value is applied to the variation of the loop condition of equipment under test. ATU reset automatic mode used and be used for to shorten and G.994.1 to shake hands and initialized any historical information.
Automatic mode is defined as this situation, wherein G.997.1 a plurality of mode of operations of enabling among the MIB in " the ATU transmission system is enabled (ATSE) " table, and the mode of operation of wherein selecting to be used to transmit not only depend on two ATU public performance (as G.994.1 exchange) also depend on equally the available data rate under the given loop condition. (R, W, Set-by-create) (enforceable) (1 byte)
L2-ATPR：
The maximum total transmitter power (dBm) reduction (unit is dB) that can carry out is finely tuned in this parameter representative L2 request (that is, transitting to the state of L2 from L0) or by the single power in the L2 state. This parameter only for G.992.3, G.992.4 and G.992.5 effectively and scope be 0 (0) dB to 31 (31) dBm. (R, W, Set-by-create) (enforceable) (1 byte)
L2-ATPRT：
The whole maximum total transmitter power (dBm) reduction (unit is dB) that this parameter representative can be carried out in the L2 state, this whole maximum total transmitter power (dBm) reduction comprises all reduction sums of L2 request (that is, transitting to the state of L2 from L0) and power fine setting. The scope of this parameter is from 0 (0) dB to 31 (31) dB. (R, W, Set-by-create) (enforceable) (1 byte)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Nothing.
Managed entity: ADSL channel configuration profile
This managed entity comprises the channel configuration profile of adsl line. The example of this managed entity is answered the request of OLT and is created/deletes.
Relation
Zero or the Multi-instance that should have this managed entity, and can zero or the Multi-instance of this managed entity is relevant with zero or the Multi-instance of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
Minimum data rate:
This parameter regulation is needed such as the Systems Operator, the minimum net data rate of Bearer Channel. This speed is encoded take bps as unit. (R, Set-by-create) (enforceable) (4 bytes)
Maximum data rate:
That this parameter has been stipulated is needed such as the Systems Operator, the maximum net data rate of Bearer Channel. This data rate is encoded take bps as unit. (R, Set-by-create) (enforceable) (4 bytes)
The rate adaptation ratio:
This parameter (representing with percentage) has been stipulated the ratio when the Bearer Channel that should consider when the direction of Bearer Channel is carried out rate adaptation. This ratio scope of being defined as is 0 to 100 percentage. Ratio 20% means that 20% available data rate (surpassing the minimum data rate of suing for peace at all Bearer Channels) will be assigned to this Bearer Channel, and 80% available data rate is assigned to remaining Bearer Channel. Rate adaptation ratio sum on all Bearer Channels on direction equals 100%. (R, Set-by-create) (optionally) (1 byte)
The maximum delay that interweaves:
This parameter is the maximum unidirectional delay that interweaves that the PMS-TC between α and the β reference point introduces on the Bearer Channel direction. This unidirectional interweaving postpones to be defined as in independent ADSL recommendsWherein " S " is the S factor, and " D " is interleave depth, andExpression is rounded up to higher integer.
ATU selects S and D value, so that the actual unidirectional delay that interweaves is less than or equal to the maximum that the disposes delay that interweaves. This delay is encoded as unit take ms, has the particular value of value 0 and 1. Delay bound is not forced in value 0 indication. Value 1 indication is used quick delay path, and is selected like this S and D under mode of operation G.992.1, thus under mode of operation G.992.2, G.992.3 and G.992.4 S≤1 and D=1. The scope of value is 2～255. (R, Set-by-create) (enforceable) (1 byte)
Upper inclined to one side data rate threshold value:
This parameter is the threshold value of the upper inclined to one side net data rate realized on one or more Bearer Channel data rate adaptations. When actual data rate exceeded data rate when entering the working time at last more than this threshold value, upper inclined to one side rate variation alarm (event) was triggered. The data rate threshold value is encoded take bps as unit. (R, Set-by-create) (enforceable) (4 bytes)
Lower inclined to one side data rate threshold value:
This parameter is the threshold value of the lower inclined to one side net data rate realized on one or more Bearer Channel data rate adaptations. When actual data rate was lower than data rate when entering the working time at last more than this threshold value, lower inclined to one side rate variation alarm (event) was triggered. The data rate threshold value is encoded take bps as unit. (R, Set-by-create) (enforceable) (4 bytes)
The minimum reservation data rate:
This parameter has been stipulated the minimum reservation net data rate required, Bearer Channel such as the Systems Operator. This speed is encoded take bps as unit. (R, Set-by-create) (enforceable) (4 bytes)
Minimum data rate under the low power state:
This parameter has been stipulated during low power state (L1/L2) such as Systems Operator's minimum net data rate required, Bearer Channel. G.992.2 and defined respectively power management low power state L1 and L2 G.992.3. Data rate is encoded take bps as unit. (R, Set-by-create) (enforceable) (4 bytes)
The protection of minimum pulse noise:
This parameter has been stipulated the minimum pulse noise protection of Bearer Channel. This parameter is only for G.992.3, G.992.4 and G.992.5 effective. This Impulse Noise Protection represents with code element and can adopt following integer value:
1=0 code element
2=1/2 code element
3=1 code element
4=2 code element
(R, Set-by-create) (enforceable) (1 byte)
Maximum bit error rate:
This parameter regulation is needed such as the Systems Operator, the maximum bit error rate of Bearer Channel. This parameter is only for G.992.3, G.992.4 and G.992.5 effective. This bit error rate can adopt following integer value:
1＝1E-3
2＝1E-5
3＝1E-7
(R, Set-by-create) (enforceable) (1 byte)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Nothing.
Managed entity: the ADSL subcarrier shields descending profile
The subcarrier that this managed entity comprises adsl line shields descending profile. The example of this managed entity answers the request of OLT to be created/to delete.
Relation
The zero or the Multi-instance that have this managed entity, and can zero or the Multi-instance of this managed entity is relevant with zero or the Multi-instance of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
Descending subcarrier mask 1:
This configuration parameter is the bitmap of the downstream mask value of vice carrier wave 1 to 128. The MSB of first byte is corresponding to subcarrier 1, and the LSB of last byte is corresponding to subcarrier 128. Each bit position has defined the whether conductively-closed on down direction on this circuit of corresponding subcarrier. If this subcarrier conductively-closed, then this subcarrier is encoded into 1, and if the not conductively-closed of this subcarrier, then this subcarrier is encoded into 0 (default).
The subcarrier of numbering 1 is minimum subcarrier, and the subcarrier of numbering NSCds is the highest subcarrier, and these subcarriers can be launched at down direction. For with standard relevant embodiment G.992.3 and G.992.4, the numbering of descending subcarrier (NSCds) is defined in the recommendation of correspondence. For G.992.1, NSCds=256, for G.992.2, NSCds=128, and for G.992.5, NSCds=512. (R, W, Set-by-create) (enforceable) (16 bytes)
Descending subcarrier mask 2:
This configuration parameter is the bitmap that represents the downstream mask value of subcarrier 129 to 256. The MSB of first byte is corresponding to subcarrier 129, and the LSB of last byte is corresponding to project (entry) 256. The whether conductively-closed on down direction on this circuit of subcarrier corresponding to each bit position definition. If this subcarrier conductively-closed, then this subcarrier is encoded into 1, and if the not conductively-closed of this subcarrier, then this subcarrier is encoded into 0 (default).
The subcarrier of numbering 1 is minimum subcarrier, and the subcarrier of numbering NSCds is the highest subcarrier, and these subcarriers can be launched at down direction. For with standard relevant embodiment G.992.3 and G.992.4, the numbering of descending subcarrier (NSCds) is defined in the recommendation of correspondence. For G.992.1, NSCds=256, for G.992.2, NSCds=128, and for G.992.5, NSCds=512. (R, W) (mandatory modem for supporting greater than 128 NSCds) (16 bytes)
Descending subcarrier mask 3:
This configuration parameter is the bitmap that represents the downstream mask value of subcarrier 257 to 384. The MSB of first byte is corresponding to subcarrier 257, and the LSB of last byte is corresponding to project subcarrier 384. Each bit position has defined the whether conductively-closed on down direction on this circuit of corresponding subcarrier. If this subcarrier conductively-closed, then this subcarrier is encoded into 1, and if the not conductively-closed of this subcarrier, then this subcarrier is encoded into 0 (default).
The subcarrier of numbering 1 is minimum subcarrier, and the subcarrier of numbering NSCds is the highest subcarrier, and these subcarriers can be launched at down direction. For with G.992.3 and G.992.4 relevant embodiment, the numbering of descending subcarrier (NSCds) is defined in the recommendation of correspondence. For G.992.1, NSCds=256, for G.992.2, NSCds=128, and for G.992.5, NSCds=512. (R, W) (mandatory modem for supporting NSCDs＞256) (16 bytes)
Descending subcarrier mask 4:
This configuration parameter is the bitmap that represents the downstream mask value of subcarrier 385 to 512. The MSB of first byte is corresponding to subcarrier 385, and the LSB of last byte is corresponding to project subcarrier 512. The whether conductively-closed on down direction on this circuit of subcarrier corresponding to each bit position definition. If this subcarrier conductively-closed, then this subcarrier is encoded into 1, and if the not conductively-closed of this subcarrier, then this subcarrier is encoded into 0 (default).
The subcarrier of numbering 1 is minimum subcarrier, and the subcarrier of numbering NSCds is the highest subcarrier, and these subcarriers can be launched at down direction. For with standard relevant embodiment G.992.3 and G.992.4, the numbering of descending subcarrier (NSCds) is defined in the recommendation of correspondence. For G.992.1, NSCds=256, for G.992.2, NSCds=128, and for G.992.5, NSCds=512. (R, W) (mandatory modem for supporting NSCds＞384) (16 bytes)
TableValid (effectively tabulation):
The duty of this boolean (Boolean) property control and this descending subcarrier mask attribute of report. If this attribute is true (being encoded as 0x01), then on dsl device, impressed descending subcarrier mask represented in this managed entity. If this attribute is false (being encoded as 0x00), then on dsl device, also do not impress descending subcarrier mask represented in this managed entity. Default value is false. The value of this attribute can be revised by ONU and OLT, and is as described below. If OLT has changed any in four mask attributes or TableValid has been arranged to false, then TableValid is configured to false. If TableValid is false and OLT is arranged to TableValid really, then ONU will be impressed into dsl device to descending subcarrier mask data. (R, W) (enforceable) (1 byte)
Action
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set. Note, because the attribute of TableValid arranges the mode of operation that the mask attribute does not directly change dsl device.
Notice
Nothing.
Managed entity: the ADSL subcarrier shields up profile
The subcarrier that this managed entity comprises adsl line shields up profile. The example of this managed entity answers the request of OLT to be created/to delete.
Relation
Zero or the Multi-instance that should have this managed entity, and can zero or the Multi-instance of this managed entity is relevant with zero or the Multi-instance of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
Up subcarrier mask:
This configuration parameter is the bitmap that represents the up mask value of subcarrier 1 to 64. The MSB of first byte is corresponding to subcarrier 1, and the LSB of last byte is corresponding to subcarrier 64. Each bit position has defined the whether conductively-closed on up direction on this circuit of corresponding subcarrier. If this subcarrier conductively-closed, then this subcarrier is encoded into 1, and if the not conductively-closed of this subcarrier, then this subcarrier is encoded into 0 (default).
The subcarrier of numbering 1 is minimum subcarrier, and the subcarrier of numbering NSCus is the highest subcarrier, and these subcarriers can be launched at up direction. For with standard relevant embodiment G.992.3 and G.992.4, the numbering of up subcarrier (NSCus) is defined in the recommendation of correspondence. For appendix A G.992.1 and G.992.2, NSCus=32, for appendix B G.992.1, NSCus=64, and for G.992.5, NSCus=64. (R, W, Set-by-create) (enforceable) (8 bytes)
Action
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set. Note, in this case, this attribute is set will cause impressing mask information at dsl device immediately.
Notice
Nothing.
The descending PSD mask of managed entity: ADSL profile
This managed entity comprises the descending PSD mask profile of adsl line. The example of this managed entity answers the request of OLT to be created/to delete.
Relation
Zero or the Multi-instance that should have this managed entity, and can zero or the Multi-instance of this managed entity is relevant with zero or the Multi-instance of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
Descending PSD mask:
This configuration parameter is a form, and wherein each project is comprised of bullets (1 byte is numbered the first project of 1) field, subcarrier subscript (2 bytes) field and MIB PSD mask grade (1 byte) field. This form definition can be used on the descending PSD mask at U-C2 reference point place. This MIB PSD mask can be forced the PSD restriction except the defined limit (limit) PSD mask in associated recommendation (for example G.992.5).
Descending PSD mask among the CO-MIB is stipulated by one group of breakpoint (breakpoint). Each breakpoint is comprised of subcarrier subscript i (using the definition identical with " i " given in the 8.1.10 joint) and the MIB PSD mask grade (representing with dBm/Hz) at that subcarrier place. This group breakpoint then can be represented as [(i1, PSD-1), (i2, PSD-2) ..., (iN, PSD-N)]. MIB PSD mask rank field should be encoded as expression MIB PSD mask grade 0 (0) dBm/Hz to the signless integer of-95 (190) dBm/Hz, and step-length is 0.5dBm/Hz. Maximum breakpoint number is 32. This attribute is only for G.992.5 effective.
In relevant recommendation (for example, G.992.5), defined the requirement of one group of effective breakpoint. Project has for target default value 0x00 under the subcarrier with for the default value 0x0 (that is, not having breakpoint) of MIB PSD mask grade. With the form project of adding or revise this attribute of moving is set. Utilizing non-zero subcarrier subscript and MIB PSD mask grade that project is set means and is inserted in this form. The subcarrier subscript of project and MIB PSD mask grade are arranged to 0 mean, if exist, then from this form, delete. (R, W) (enforceable) (N*4 byte, wherein N is breakpoint number)
TableValid：
The duty of this descending PSD mask attribute is controlled and reported to this boolean properties. If this attribute is true (being encoded as 0x01), then on dsl device, impressed descending PSD mask represented in this managed entity. If this attribute is false (being encoded as 0x00), then on dsl device, also do not impress descending PSD mask represented in this managed entity. Default value is false. The value of this attribute can be revised by ONU and OLT, and is as described below. If OLT has changed any in the PSD mask table project or TableValid has been arranged to false, then TableValid is configured to false. If TableValid is false and OLT is arranged to TableValid really, then ONU will be imposed to DSL equipment to descending PSD mask data. (R, W) (enforceable) (1 byte)
Action
Obtain: obtain one or more attributes. The snapshot (snapshot) (that is, copying) that locks current descending PSD mask also responds to the data size with four bytes, and this size of data should use " obtaining the next one " order to obtain.
Obtain the next one: the property value that locks that obtains the managed entity in the current snapshot.
Arrange: usually, this action is used to arrange one or more bulk properties values. When this action is used on the descending PSD mask attribute, action or interpolation are set, revise or delete the form project in the descending PSD mask. Singlely action is set adds/revise/delete maximum 7 form projects.
Notice
Nothing.
The descending RFI frequency band of managed entity: ADSL profile
This managed entity comprises the descending RFI frequency band profile of adsl line. The example of this managed entity answers the request of OLT to be created/to delete.
Relation
Zero or the Multi-instance that should have this managed entity, and can zero or the Multi-instance of this managed entity is relevant with zero or the Multi-instance of physical pathway tip node ADSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
Descending RFI frequency band:
This configuration parameter is a form, and wherein each project is comprised of bullets (1 byte is numbered the first project of 1) field, subcarrier subscript 1 (2 bytes) field and subcarrier subscript 2 (2 bytes) field. Be marked under the subcarrier in the 8.1.10 joint and be defined. This form definition the subset of descending RFI frequency band breakpoint, as defined in the descending PSD mask managed entity, these descending RFI frequency band breakpoints are used to bore a hole to the RFI frequency band. This subset is by belonging to breakpoint [i1; I2], corresponding to the many of the low level (level) in hole continuous subcarrier subscript is formed. The maximum number of RFI frequency band is 32. This attribute is only for G.992.5 effective.
Special-purpose interpolation method about these points is defined in relevant recommendation (for example G.992.5). CO-MIB should will define the RFI hole such as the breakpoint in the descending PSD mask of the such usefulness managed entity of defined in the associated recommendation (for example, G.992.5).
Project has the default value 0x00 for subcarrier subscript 1 and subcarrier subscript 2. With the form project of adding or revise this attribute of moving is set. Utilizing non-zero subcarrier subscript 1 and subcarrier subscript 2 that project is set means and is inserted in this form. The subcarrier subscript 1 of project and subcarrier subscript 2 are arranged to 0 mean, if exist, then from this form, delete. (R, W) (enforceable) (N*5 byte, wherein N is the RFI frequency band number)
TableValid：
The duty of this descending RFI frequency band attribute is controlled and reported to this boolean properties. If this attribute is true (being encoded as 0x01), then on this dsl device, impressed descending RFI frequency band represented in this managed entity. If this attribute is false (being encoded as 0x00), then on dsl device, also do not impress descending RF1 frequency band represented in this managed entity. Default value is false. The value of this attribute can be revised by ONU and OLT, and is as described below. If OLT has changed any in the RFI frequency band form project or TableValid has been arranged to false, then TableValid is configured to false. If TableValid is false and OLT is arranged to TableValid really, then ONU will impose on DSL equipment to descending RF1 frequency band data. (R, W) (enforceable) (1 byte)
Action
Obtain: obtain one or more attributes. Lock the snapshot (that is, copying) of current descending RFI frequency band and use 4 bytes that the data size is responded, this size of data should use " obtaining the next one " order to obtain.
Obtain the next one: the property value that locks that obtains the managed entity in the current snapshot.
Arrange: usually, this action is used to arrange one or more bulk properties values. When action being set when being used on the descending RFI frequency band attribute, this arranges action or adds, revises or delete form project in the descending RFI frequency band. Singlely action is set adds/revise/delete maximum 6 form projects.
Notice
Nothing.
Managed entity: ADSL ATU-C performance monitoring historical data
This managed entity representative as from ATU-C, for the 15 minute intervals of at last finishing of ATU-C to the collected performance monitoring data in ATU-R ADSL modem path. After the example of the physical pathway tip node ADSL of correspondence UNI managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT.
Relation
An example that can have for each example of physical pathway tip node ADSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of distributing is identical with the ID of physical pathway tip node ADSL UNI, and this ATU-C performance monitoring historical data is relevant with the ID of this physical pathway tip node ADSL UNI. (R, W, Set-by-create) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. The new interval of each end, cycle counter (modulus is 0xFF (256)) just increases progressively, and attribute counter is updated. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during first cycle after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at last interval of finishing. The actual count device of this managed entity directly begins counting. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute provides pointer (as defined G.983.2) to the example of threshold data B-PON managed entity, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
Frame loss second:
This attribute is the counting that has the second in the previous 15 minutes intervals that framing loses. (R) (enforceable) (2 bytes)
Blackout second:
This attribute is the counting that has the second in the previous 15 minutes intervals of dropout. (R) (enforceable) (2 bytes)
Loss of link second:
This attribute is the counting that has the second in the previous 15 minutes intervals of loss of link. (R) (enforceable) (2 bytes)
Power loss second:
This attribute is the counting that has the second in the previous 15 minutes intervals of power loss. (R) (enforceable) (2 bytes)
Make mistakes second:
This attribute is the previous 15 minutes countings of makeing mistakes second in the interval. (R) (enforceable) (2 bytes)
Seriously make mistakes second:
This attribute is the previous 15 minutes countings of seriously makeing mistakes second in the interval. (R) (enforceable) (2 bytes)
Circuit initializes:
This attribute is the previous 15 minutes initialized countings of circuit in the interval. (R) (enforceable) (2 bytes)
Failed circuit initializes:
This attribute is the counting of the complete initialized sum of the failure in the interval in previous 15 minutes. (R) (enforceable) (2 bytes)
Fast initialization:
This attribute be previous 15 minutes in the interval the high speed retraining of attempting on the line to carry out or the counting of the sum of fast initialization (success with failure). (R) (optionally) (2 bytes)
Failed fast initialization:
This attribute is the counting of the sum of the high speed retraining of the failure in the interval in previous 15 minutes or fast initialization. (R) (optionally) (2 bytes)
FEC second:
This attribute is the counting that has the second in the previous 15 minutes unusual intervals of forward error correction. (R) (enforceable) (2 bytes)
Invalid second:
This attribute is the counting of the second in the previous 15 minutes invalid intervals of ATU-C. (R) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to the informing network management system. TCA changes notice " on " and is sent out when the actual count device is out-of-limit; TCA changes notice " off " and is sent out when being reset 15 minutes end cycles that 0x00 begins from the actual count device. Provided the list of thing that is used for this entity in the table 5 below.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | Frame loss second | Frame loss second is out-of- | 1 |
| 1 | Dropout second | Dropout is out-of-limit second | 2 |
| 2 | Loss of link second | Loss of link is out-of-limit second | 3 |
| 3 | Power loss second | Power loss is out-of-limit second | 4 |
| 4 | Make mistakes second | It is second out-of-limit to make mistakes | 5 |
| 5 | Seriously make mistakes second | It is second out-of-limit seriously to make mistakes | 6 |
| 6 | Circuit initializes | Circuit initializes out-of-limit | 7 |
| 7 | Failed circuit initializes | Failed circuit initializes out-of-limit | 8 |
| 8 | Fast initialization | Fast initialization is out-of-limit | 9 |
| 9 | Failed fast initialization | Failed fast initialization is out-of- | 10 |
| 10 | FEC second | FEC is out-of-limit second | 11 |
| 11 | Invalid second | Invalid second out-of- | 12 |
| 12- 255 | Reserve |
* this numbering and relevant threshold dataR-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter etc.
Table 5ADSL performance monitoring historical data
Managed entity: ADSL ATU-R performance monitoring historical data
This managed entity represented as from ATU-R, ATU-C is to 15 minutes intervals of finishing at last of the collected performance monitoring data in ATU-R ADSL Modem path. After the example of the physical pathway tip node ADSL of correspondence UNI managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT.
Relation
An example that can have for each example of physical pathway tip node ADSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of distributing is identical with the ID of physical pathway tip node ADSL UNI, and this ATU-R performance monitoring historical data is relevant with the ID of physical pathway tip node ADSL UNI. (R, Set-by-create) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. Finish new interval, cycle counter (modulus is 0xFF (256)) just increases progressively, and this attribute counter is updated at every turn. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 etc. during first cycle after this. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute to the example of threshold data B-PON managed entity provide pointer (as list of references in G.983.2 set forth), this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
Frame loss second:
This attribute is the counting that has the second in the previous 15 minutes intervals that framing loses. (R) (enforceable) (2 bytes)
Dropout second:
This attribute is the counting that has the second in the previous 15 minutes intervals of dropout. (R) (enforceable) (2 bytes)
Power loss second:
This attribute is the counting that has the second in the previous 15 minutes intervals of power loss. (R) (enforceable) (2 bytes)
Make mistakes second:
This attribute is the previous 15 minutes countings of makeing mistakes second in the interval. (R) (enforceable) (2 bytes)
Seriously make mistakes second:
This attribute is the previous 15 minutes countings of seriously makeing mistakes second in the interval. (R) (enforceable) (2 bytes)
FEC second:
This attribute is the counting that has the second in the previous 15 minutes unusual intervals of forward error correction. (R) (enforceable) (2 bytes)
Invalid second:
This attribute is the counting of the second in the previous 15 minutes invalid intervals of ATU-R. (R) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to the informing network management system. TCA changes notice " on " and is sent out when the actual count device is out-of-limit; TCA changes notice " off " and is sent out when being reset 15 minutes end cycles that 0x00 begins from the actual count device. Provide the list of thing of this entity in the table 6 below.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | Frame loss second | Frame loss second is out-of- | 1 |
| 1 | Dropout second | Dropout is out-of-limit second | 2 |
| 2 | Power loss second | Power loss is out-of-limit second | 3 |
| 3 | Make mistakes second | It is second out-of-limit to make mistakes | 4 |
| 4 | Seriously make mistakes second | It is second out-of-limit seriously to make mistakes | 5 |
| 5 | FEC second | FEC is out-of-limit second | 6 |
| 6 | Invalid second | Invalid second out-of-limit | 7 |
| 5-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter etc.
Table 6ATU-R performance monitoring historical data
Managed entity: ADSL ATU-C channel performance monitoring historical data
This managed entity represented as from ATU-C, ATU-C is to 15 minutes intervals of finishing at last of the collected performance monitoring data of ATU-R ADSL channel. After the example of corresponding physical pathway tip node ADSL UNI managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT.
Relation
An example that can have for each example of physical pathway tip node ADSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. Two highest significant positions of the first byte are Bearer Channel ID. Six least significant bits of the first byte are slot ID (as defined G.983.2). Second byte is port id, and the value scope of this port id is used to Far Left/nethermost port on the subscriber line cards for (1 to 255): 0x01 from Ox01 to 0xFF, and 0x02 is used to next the right/top port, etc. (R) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. Finish new interval, cycle counter (modulus is 0xFF (256)) just increases progressively, and attribute counter is updated at every turn. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during first cycle after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute provides pointer to the example of threshold data B-PON managed entity, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
Correcting block:
This attribute is to receive the counting of all pieces of the mistake that has been corrected at this channel in previous 15 minutes intervals. (R) (enforceable) (4 bytes)
Correcting block not:
This attribute is to receive the counting of all pieces of the mistake that can't be corrected at this channel in previous 15 minutes intervals. (R) (enforceable) (4 bytes)
The piece that transmits:
This attribute is the counting of previous 15 minutes all pieces of having encoded that transmit on this channel in the interval. (R) (enforceable) (4 bytes)
The piece that receives:
This attribute is the counting of all pieces of having encoded that receive at this channel in previous 15 minutes intervals. (R) (enforceable) (4 bytes)
Code violation:
This attribute is the previous 15 minutes unusual countings of CRC-8 in the Bearer Channel in the interval. (R) (enforceable) (2 bytes)
Forward error correction:
This attribute is the previous 15 minutes unusual countings of FEC in the Bearer Channel in the interval. (R) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to the informing network management system. TCA changes notice " on " and will be sent out when the actual count device is out-of-limit; TCA changes notice " off " and will be sent out when being reset 15 minutes end cycles that 0x00 begins from the actual count device. In table 7, provided the list of thing of this entity.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | Correcting block | Correcting block is out-of- | 1 |
| 1 | Correcting block not | Correcting block is not out-of-limit | 2 |
| 2 | Code violation | Code violation is out-of-limit | 3 |
| 3 | Forward error correction | FEC is out-of-limit | 4 |
| 4-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter, etc.
Table 7ATU-C channel performance monitoring historical data
Managed entity: ADSL ATU-R channel performance monitoring historical data
The representative of this managed entity as from ATU-R, for the 15 minute intervals of at last finishing of ATU-C to the collected performance monitoring data of ATU-R ADSL channel. After the physical pathway tip node ADSL of correspondence UNI managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT.
Relation
An example that can have for each example of physical pathway tip node ADSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. Two highest significant positions of the first byte are Bearer Channel ID. Six least significant bits of the first byte are (defined in G.983.2) slot ID. Second byte is port id, and the value scope of this port id is used to Far Left/nethermost port on the subscriber line cards for (1 to 255): 0x01 from 0x01 to 0xFF, and 0x02 is used to next the right/top port, etc. (R) (enforceable) (2 bytes).
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. Finish new interval, cycle counter (modulus is 0xFF (256)) just increases progressively, and attribute counter is updated at every turn. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during first cycle after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute provides pointer to the example of threshold data B-PON managed entity, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
Correcting block:
This attribute is to receive the counting of all pieces of the mistake that has been corrected at this channel in previous 15 minutes intervals. (R) (enforceable) (4 bytes)
Correcting block not:
This attribute is to receive the counting of all pieces of the mistake that can't be corrected at this channel in previous 15 minutes intervals. (R) (enforceable) (4 bytes)
The piece that transmits:
This attribute is the counting at all pieces of having encoded of this channel in previous 15 minutes intervals. (R) (enforceable) (4 bytes)
The piece that receives:
This attribute is the counting of all pieces of having encoded that receive at this channel in previous 15 minutes intervals. (R) (enforceable) (4 bytes)
Code violation:
This attribute is the previous 15 minutes unusual countings of CRC-8 in the Bearer Channel in the interval. (R) (enforceable) (2 bytes)
Forward error correction:
This attribute is the previous 15 minutes unusual countings of FEC in the Bearer Channel in the interval. (R) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to notifying management system. TCA changes notice " on " and is sent out when the actual count device is out-of-limit; TCA changes notice " off " and is sent out when being reset 15 minutes end cycles that 0x00 begins from the actual count device. Provided the list of thing of this entity in the table 8 below.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | Correcting block | Correcting block is out-of- | 1 |
| 1 | Correcting block not | Correcting block is not out-of-limit | 2 |
| 2 | Code violation | Code violation is out-of-limit | 3 |
| 3 | Forward error correction | FEC is out-of-limit | 4 |
| 4-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter, etc.
Table 8ATU-R channel performance monitoring historical data
Managed entity: TC adapter performance monitoring historical data ADSL
This managed entity represents ATU-C to 15 minutes collected performance monitorings in interval finishing at last of ATU-R ATM data path. After the physical pathway tip node ADSL of correspondence UNI managed entity was created/deletes, the example of this managed entity was created/deletion by OLT.
Relation
An example that can have for each example of physical pathway tip node ADSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of distributing is identical with the ID of physical pathway tip node ADSL UNI, and this TC adapter performance monitoring historical data is relevant with this physical pathway tip node ADSL UNI. (R, Set-by-create) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. Finish new interval, cycle counter (modulus is 0xFF (256)) just increases progressively, and attribute counter is updated at every turn. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during first cycle after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute provides pointer to the example of threshold data B-PON managed entity, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
Proximal end H EC illegally counts:
The illegal counting properties parameter of proximal end H EC is the counting to the unusual occurrence number of proximal end H EC in the ATM data path. (R) (enforceable) (2 bytes)
(delineated) total unit (cell) counting (CD-P) of near-end delineation:
Total element count performance parameter of this near-end delineation is the counting of the total unit number by the unit delineation of working on the ATM data path and HEC function course when being in sync state. (R) (enforceable) (4 bytes)
The total element count of near-end user:
The total element count performance parameter of near-end user is to the counting of the unit sum in the ATM data path that send in (for ATU-C) V-C or (for ATU-R's) T-R interface place. (R) (enforceable) (4 bytes)
Near-end free cells error code counting:
The idle error code counting properties of near-end parameter is the counting to the number of bit errors in the free cells payload that receives in the ATM of proximal end data path. (R) (enforceable) (2 bytes)
The illegal HEC counting of far-end:
The illegal HEC counting properties of far-end parameter is the counting to the unusual occurrence number of the far-end HEC in the ATM data path. (R) (enforceable) (2 bytes)
Total element count of far-end delineation:
Total element count performance parameter of far-end delineation is the counting of the total unit number by the unit delineation process of working at the ATM data path and HEC function when being in the sync state. (R) (enforceable) (4 bytes)
The total element count of remote subscriber:
Far-end uses total element count performance parameter to the counting of the unit sum in the ATM data path that send in (for ATU-C) V-C or (for ATU-R's) T-R interface place. (R) (enforceable) (4 bytes)
Far-end free cells error code counting:
The idle error code counting properties of far-end parameter is the counting of the number of bit errors in the free cells payload that receives in the ATM data path to far-end. (R) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to notifying management system. TCA changes notice " on " " when the actual count device is out-of-limit, be sent out; TCA changes notice " off " and is sent out when being reset 15 minutes end cycles that 0x00 begins from the actual count device. Provided the list of thing of this entity in the table 9 below.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | The illegal HEC of near-end | The illegal HEC counting of near-end is out-of- | 1 |
| 1 | Near-end free cells error code counting | Near-end free cells error code counting is out-of-limit | 2 |
| 2 | The illegal HEC counting of far-end | The illegal HEC counting of far-end is out-of-limit | 3 |
| 3 | Far-end free cells error code counting | Far-end free cells error code counting is out-of-limit | 4 |
| 4-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter, etc.
Table 9TC adapter performance monitoring historical data ADSL
Below table 10 listed and be used for POIN and OMCI agreement managed entity according to the work of the VDSL network of instruction of the present invention.
| The VDSL managed entity | |||
| Managed entity | Essential/optional | Explanation | Joint |
| Physical pathway tip node VDSL UNI | CR | Be used to the physical pathway tip node of VDSL junction | 8.2.1 |
| VDSL band plan configuration profile | CR | Be used to dispose the parameter of VDSL band plan configuration profile | 8.2.7 |
| VDSL channel configuration profile | CR | Be used to dispose the parameter of VDSL channel configuration profile | 8.2.6 |
| The VDSL channel data | CR | Comprise VDSL fast and the channel parameter of slow channel | 8.2.4 |
| VDSL line configuring profile | CR | Be used to dispose the parameter of VDSL line configuring profile | 8.2.5 |
| VDSL VTU-O channel performance monitoring historical data | O | The performance monitoring data of VDSL VTU-O channel | 8.2.10 |
| VDSL VTU-O physical data | CR | The physical layer parameter that comprises VTU-O | 8.2.2 |
| VDSL VTU-O physical interface monitoring historical data | O | The data of monitoring VDSL VTU-O physical interface | 8.2.8 |
| VDSL VTU-R channel performance monitoring historical data | O | The performance monitoring data of VDSL VTU-R channel | 8.2.11 |
| VDSL VTU-R physical data | CR | The physical layer parameter that comprises VTU-R | 8.2.3 |
| VDSL VTU-R physical interface monitoring historical data | O | The data of monitoring VDSL VTU-R physical interface | 8.2.9 |
Table 10
Managed entity: physical pathway tip node VDSL UNI
This managed entity has represented VDSL and has been connected to point among the ONU, and wherein physical pathway is in this place's termination and carry out the function (for example, path cost function) of physical pathway layer. The subscriber line cards of one establishment/deletion VDSL type, the example of this managed entity is just automatically created/is deleted by ONU. If the subscriber line cards of VDSL type is plug-in unit, the number of the managed entity that then automatically creates is the supported maximum number of subscribers' line card slot of ONU. This allows to create these managed entities before the unit is inserted into. When the subscriber line cards of type VDSL was created, physical pathway tip node VDSL UNI was created automatically. In case automatically create, three profile pointers in the managed entity just are configured to its default value 0x00. Yet physical pathway tip node VDSL UNI must consult three effective profiles before it can operate.
Relation
One or more examples of this managed entity should be comprised in the example of the subscriber line cards managed entity that is classified as the VDSL type.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is (G.983.2/ saving among the 7.1.3 defined) slot ID. Second byte is port id, and the value scope of this port id is used to Far Left/nethermost port on the subscriber line cards for (1 to 255): 0x01 from 0x01 to 0xFF, and 0x02 is used to next the right/top port, etc. (R) (enforceable) (2 bytes)
Loopback configuration:
This attribute represents the loopback configuration of this physical interface. Value 0x00: do not have loopback; Value 0x01: loopback 2 (" Loopback2 " refers to the loopback at local VDSL modem place). OLT can carry out the Physical layer loopback test after loopback is set up. In case spontaneous example, value 0x00 just is set up. (R, W) (enforceable) (1 byte)
Controlled state:
Value 0x01) and deactivate and (lock: the performed function of example of value 0x01) passing through this managed entity this attribute activates (to be opened:. (R, W) (enforceable) (1 byte)
Duty:
This attribute has indicated this managed entity whether can carry out its task. Duty has reflected the reception that perceives or the ability that produces useful signal. Virtual value is for enabling (0x00) and stop using (0x01). (R) (optionally) (1 byte)
Usability status:
Whether this attribute has indicated the hardware of supporting this UNI available on the Line cards of inserting. Virtual value can be used (0), invalid (1) and uncertain (2). (R) (optionally) (1 byte).
VDSL line coding type:
This data type is used as the grammer of VDSL line coding. Have this grammer attribute-bit the line coding that adopts. These three values are: indication does not have other (1) of following situation; The mcm (2) of indication multi-carrier modulation; And the scm of instruction sheet carrier modulation (3). (R) (enforceable) (1 byte)
The VDSL circuit types:
Whether and how by channelizing, define the type of the VDSL physical circuit entity of existence by the definition circuit. If this circuit is by channelizing, then value will be the value except noChannel (1). This object definition which (a bit) channel type be supported. Defined value is: there is channel in noChanel (1)-not, there is Fast Channel in fastOnly (2)-only, there is slow channel in slowOnly (3)-only, fastOrSlow (4)-have Fast Channel or slow channel, but only have one in preset time; And fastAndSlow (5)-fast and slow channel and deposit. (R) (enforceable) (1 byte)
ARC：
This property control from the switch fault report of this managed entity. Virtual value is " off " (allowing immediately switch fault report) and " on " (forbidding switch fault report). In case finish the initial installation of ONU and provide, for by " ARClnterval " specified time interval, this attribute just can be configured to " on " or " off ". Equally, this attribute can be configured to " off ". If this attribute is configured to " on ", then switch fault report is under an embargo, until this managed entity detects for by " ARClnterval " useful signal in the specified time interval. Default value is " on ". (R, W) (optionally) (1 byte)
ARClnterval：
This attribute provides available time span. Unit is minute. Default value is 2. (R, W) (optionally) (1 byte)
VDSL line configuring profile ID:
This attribute provides pointer (as described below) to the example of VDSL line configuring profile managed entity, and this pointer comprises the necessary data of initialization VDSL modem. Employed default value 0x00 indication when creating managed entity, this managed entity does not point to the line configuring profile. (R, W) (enforceable) (2 bytes)
VDSL channel configuration profile ID:
This attribute provides pointer to the example of VDSL channel configuration profile managed entity, and this pointer comprises channelizing VDSL and connects necessary data. Default value 0x00 set when creating managed entity indicates, and this managed entity does not point to the channel configuration profile. (R, W) (enforceable) (2 bytes)
VDSL band plan configuration profile ID:
This attribute provides pointer to the example of VDSL band plan configuration profile managed entity, and this pointer comprises to be set up VDSL and connect necessary data. Default value 0x00 set when creating managed entity indicates, and this managed entity does not point to band plan configuration profile. (R, W) (enforceable) (2 bytes)
Action
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Property value changes:
This notice is used to report the spontaneous variation of the attribute of this managed entity. This notice this attribute of sign and new value thereof. Provide in the property value variation table 11 below for this managed entity.
| Numbering | Property value changes | Explanation |
| 1-2 | N/A | |
| 3 | OpState | Duty |
| 4-11 | N/A | |
| 12-16 | Reserve |
Table 11
Alarm:
When detecting or having eliminated fault, this notice is used to the informing network management system. ONU and OLT should know the employed alarm list of this entity. In table 11, provided the alarm of this entity.
| | Alarm | Explanation | |
| 0 | NE_LOF | Near-end (VTU-O) framing is lost | |
| 1 | NE_LOS | Near-end (VTU-O) dropout | |
| 2 | NE_LOP | Near-end (VTU-O) power loss | |
| 3 | NE_LOSQ | The loss of near-end (VTU-O) signal quality | |
| 4 | NE_LOL | Near-end (VTU-O) loss of link | |
| 5 | NE_LOF | Far-end (VTU-R) framing is lost | |
| 6 | NE_LOS | Far-end (VTU-R) dropout | |
| 7 | NE_LOP | Far-end (VTU-R) power loss | |
| 8 | NE_LOSQ | The loss of far-end (VTU-R) signal quality |
Table 12
Managed entity: VDSL VTU-O physical data
This managed entity represents the physical state of VDSL among the ONU VDSL terminal unit (ONU or VTU-O) in connecting. In case create/delete the subscriber line cards of VDSL type, the example of this managed entity is just automatically created/is deleted by ONU.
Relation
One or more examples of this managed entity all are comprised in the example of the subscriber line cards managed entity that is classified as the VDSL type.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is slot ID. Second byte is port id, and the value scope of this port id is from 0x01 to 0xFF (1 to 255). (R) (enforceable) (2 bytes)
Line speed:
The current VTU-O line speed of indication take kbps as unit. This value is less than or equal to current accessible speed. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
This attribute comprises the vendor specific character string that has identified equipment vendors. This attribute comprises up to 32 ascii characters. Part 1 comprises front 16 characters, and part 2 comprises rear 16 characters. (R) (enforceable) (16 bytes of every part)
Vendor id:
The vendor id coding is the copy of binary system identification of the manufacturer field, and this binary system identification of the manufacturer field is represented as readable hexadecimal character. (R) (enforceable) (16 bytes)
Version number:
Vendor specific version number is sent out as the part of initial message by this VTU. This vendor specific version number is the copy of binary version field, and this binary version field is represented as readable hexadecimal character. (R) (enforceable) (16 bytes)
Current state:
This attribute is with the current state of the form indication VTU-O of the bitmap of possible condition. Different bit positions are
0-is without detecting-not detecting on the line.
The 1-framing loses-and VTU-O is owing to the fault that does not receive valid frame and occur.
2-dropout-VTU-O is owing to the fault that does not receive signal and occur.
The fault that 3-power loss-VTU-O occurs owing to power loss.
When 4-signal quality loss-under noise margin drops to the minimal noise tolerance limit or the bit error rate surpass 107, the announcing signal mass loss.
5-loss of link-VTU-O is owing to the fault that can not link reciprocity VTU and occur. All arrange when no matter when transceiver is in " thermal starting " state.
6-data initialization fault-VTU-O starts the fault that swap data occurs owing to error code has destroyed during initializing.
7-configuration initializes fault-VTU-O during initializing because the fault that the configuration that reciprocity VTU (VTU-R, namely the equity of VTU-O is VTU-R) can not support to ask owing to the equity of VTU occurs.
The fault that 8-protocol initializing fault-VTU-O occurs because the used agreement of reciprocity VTU is incompatible during initializing.
9-do not exist reciprocity VTU-VTU-O during initializing owing to from reciprocity VTU, not detecting the fault that activation sequence occurs. (R) (enforceable) (2 bytes)
Present output power:
Measured, by the gross output that this VTU transmits, its step-length is 0.1dBm, as reporting during the last activation sequence. Effective range is 0 (0) to+16 (160) dBm. (R) (enforceable) (1 byte)
The current SNR tolerance limit:
As seen by this VTU, with respect to the noise margin of its signal that receives, its step-length is 0.25dB. Effective range is to+31.75 (127) dB from-31.75 (127). (R) (enforceable) (1 byte)
Current decay:
The measured difference of the general power that the general power of being transmitted by reciprocity VTU and this VTU receive. Effective range is 0 (0) to+63.75 (255) dB. (R) (enforceable) (1 byte)
Current accessible speed:
The present accessible maximum line speed of indication VTU-O, its unit is kbps. This value will be equal to or greater than current line speed. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
Current loop length is estimated:
Suppose the estimated loop length in the loop of 26AWG (0.4mm), unit is foot. (R) (enforceable) (2 bytes)
Action
Obtain: obtain one or more attributes.
Notice
Nothing.
Managed entity: VDSL VTU-R physical data
This managed entity has represented VDSL terminal unit (far-end) physical state (VTU-R) in the VDSL connection among the ONU. In case create/delete the subscriber line cards of VDSL type, the example of this managed entity is just automatically created/is deleted by ONU.
Relation
One or more examples of this managed entity all are comprised in the example of the subscriber line cards managed entity that is classified as the VDSL type.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is slot ID. Second byte is port id, and the value scope of this port id is from 0x01 to 0xFF (1 to 255). (R) (enforceable) (2 bytes)
Line speed:
Indicate the line speed of current VTU-R, unit is kbps. This value will be less than or equal to current accessible speed. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
This attribute comprises the vendor specific character string that identifies vendor equipment. The part 1 of this attribute comprises front 16 characters, and part 2 comprises ensuing 16 characters. (R) (enforceable) (16 bytes of every part)
Vendor id:
The vendor id coding is the copy of binary system identification of the manufacturer field, and this binary system identification of the manufacturer field is represented as readable hexadecimal character. (R) (enforceable) (16 bytes)
Version number:
Vendor specific version number is sent out as the part of initial message by this VTU. This vendor specific version number is the copy of binary version field, and this binary version field is represented as readable hexadecimal character. (R) (enforceable) (16 bytes)
Current state:
Indicate the current state of VTU circuit according to the bitmap of possible condition. Different bit positions are
0-is without detecting-not detecting on the line.
The 1-framing loses-and VTU is owing to the fault that does not receive valid frame and occur.
2-dropout-VTU is owing to the fault that does not receive signal and occur.
The fault that 3-power loss-VTU occurs owing to power loss.
4-signal quality loss-drop under the minimal noise tolerance limit or the bit error rate surpasses 10 when noise margin-7The time, the announcing signal mass loss. (R) (enforceable) (1 byte)
Present output power:
Measured, by the gross output of this VTU transmission, as reporting during the activation sequence in the end, its step-length is 0.1dBm. Effective range is 0 (0) to+16 (160) dBm. (R) (enforceable) (1 byte)
The current SNR tolerance limit:
As seen by this VTU, with respect to the noise margin of its signal that receives, its increment is 0.25dB. Effective range is that-31.75 (127) are to+31.75 (127) dB. (R) (enforceable) (1 byte)
Current decay:
Measured, by the difference of reciprocity the VTU general power of transmitting and the general power that is received by this VTU. Effective range is 0 (0) to+63.75 (255) dB. (R) (enforceable) (1 byte)
Current accessible speed:
The present accessible maximum line speed of indication VTU-R, its unit is kbps. This value will be equal to or greater than current line speed. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
Action
Obtain: obtain one or more attributes.
Notice
Nothing.
Managed entity: VDSL channel data
This managed entity represents VDSL among the ONU VDSL in connecting fast and the physical state of slow channel. In case create/delete the subscriber line cards of VDSL type, the example of this managed entity is just automatically created/is deleted by ONU.
Relation
One or more examples of this managed entity should all be comprised in the example of the subscriber line cards managed entity that is classified as the VDSL type.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is slot ID. Second byte is port id, and the value scope of this port id is from 0x01 to 0xFF (1 to 255). (R) (enforceable) (2 bytes).
The current descending delay that interweaves:
The descending delay that interweaves of this channel, unit is millisecond. Interweave and postpone to have defined the follow-up input byte of interleaver input and the mapping (relative spacing) between its position in the bit stream of interleaver output place. Larger numbering provides the larger interval between the continuous input byte of exporting in the bit stream, and this output bit stream allows to improve impulse immunity take the payload delay as cost. (R) (enforceable) (1 byte)
Current descending quick payload speed:
Actual Fast Channel downstream data rate, unit is kbps. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
Current descending at a slow speed payload speed:
Actual at a slow speed downstream data rate, unit is kbps. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
Current descending quick crc block length:
The length of indication CRC work descending Fast Channel data block thereon, unit is byte. (R) (enforceable) (2 bytes)
Current descending at a slow speed crc block length:
The length of indication CRC work descending slow channel data block thereon, unit is byte. (R) (enforceable) (2 bytes)
Current descending at a slow speed burst protection:
For the real standard that the downstream pulses noise (burst) of slow channel is protected, unit is microsecond. (R) (enforceable) (2 bytes)
Current descending quick FEC:
Actual downlink forward error correction (FEC) redundancy, unit is percentage, its expense with Fast Channel is relevant. (R) (enforceable) (1 byte)
Current uplink interlacing postpones:
The descending delay that interweaves of this channel, unit is millisecond. Interweave and postpone only to be applied to interweave (at a slow speed) channel and define the follow-up input byte of interleaver input and the mapping (relative spacing) between its position in the bit stream of interleaver output place. Larger numbering provides the larger interval between the continuous input byte of exporting in the bit stream, and this output bit stream allows to improve impulse immunity take the payload delay as cost. Interface type is fast in the situation therein, and this attribute is configured to null value. (R) (enforceable) (1 byte)
Current up quick payload speed:
Actual Fast Channel upstream data rate, unit is kbps. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
Current up at a slow speed payload speed:
Actual at a slow speed upstream data rate, unit is kbps. Attention: 1 kbps=1000 bps. (R) (enforceable) (4 bytes)
Current up quick crc block length:
The length of indication CRC work up Fast Channel data block thereon, unit is byte. (R) (enforceable) (2 bytes)
Current up at a slow speed crc block length:
The length of indication CRC work up slow channel data block thereon, unit is byte. (R) (enforceable) (2 bytes)
Current up at a slow speed burst protection:
For the real standard that the up impulsive noise (burst) of slow channel is protected, unit is microsecond. (R) (enforceable) (2 bytes)
Current up quick FEC:
For uplink forward error correction (FEC) redundancy of the reality of Fast Channel, unit is percentage, and it is relevant with expense. (R) (enforceable) (1 byte)
Action
Obtain: obtain one or more attributes.
Notice
Nothing.
Managed entity: VDSL line configuring profile
The example of this managed entity represents the VDSL line configuring profile of supporting on the ONU. Zero or a plurality of VDSL physical pathway tip nodes can be consulted the example of VDSL line configuring profile managed entity. The example of this managed entity answers the request of OLT to be created and deleted by ONU.
Relation
Zero or the Multi-instance of this managed entity all are comprised among the ONU. One or more examples of this managed entity should all be comprised among the ONU of the example that comprises physical pathway tip node VDSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, W, Set-be-create) (enforceable) (2 bytes)
The downstream rate pattern:
Stipulate the speed selectivity characteristic of this circuit on down direction: manually (1) forces speed to reach the speed that disposes, and adaptAtlnit (2) comes adaptive circuit based on line quality. (R, W, Set-by-Create) (enforceable) (1 byte)
The downstream rate pattern:
Stipulate the speed selectivity characteristic of this circuit on up direction: manually (1) forces speed to reach the speed that disposes, and adaptAtlnit (2) comes adaptive circuit based on line quality. (R, W, Set-by-Create) (enforceable) (1 byte)
Descending peak power:
In scope 0 (0) to 14.5dBm (58), stipulated maximum total downlink power level with the interval of 0.25dBm. (R, W, Set-by-Create) (enforceable) (1 byte)
Up peak power:
In scope 0 (0) to 14.5dBm (58), stipulated maximum total ascending power level with the interval of 0.25dBm. (R, W, Set-by-Create) (enforceable) (1 byte)
Descending maximum S/N R tolerance limit:
Stipulated maximum descending Signal to Noise Ratio Margin, unit is 0.25dB, and scope is 0 (0) to 31.75dB (127). (R, W, Set-by-Create) (enforceable) (1 byte)
Descending minimum SNR tolerance limit:
Stipulated minimum descending Signal to Noise Ratio Margin, unit is 0.25dB, and scope is 0 (0) to 31.75dB (127). (R, W, Set-by-Create) (enforceable) (1 byte)
Descending target SNR tolerance limit:
Stipulated the target downlink Signal to Noise Ratio Margin, unit is 0.25dB, and scope is 0 (0) to 31.75dB (127). This is that transceiver is take BER as 10-7Or more preferably be successfully completed the noise margin that initialization must reach. (R, W, Set-by-Create) (enforceable) (1 byte)
Up maximum S/N R tolerance limit:
Stipulated maximum up Signal to Noise Ratio Margin, unit is 0.25dB, and scope is 0 (0) to 31.75dB (127). (R, W, Set-by-Create) (enforceable) (1 byte)
Up minimum SNR tolerance limit:
Stipulated minimum up Signal to Noise Ratio Margin, unit is 0.25dB, and scope is 0 (0) to 31.75dB (127). (R, W, Set-by-Create) (enforceable) (1 byte)
Up target SNR tolerance limit:
Stipulated the up Signal to Noise Ratio Margin of target, unit is 0.25dB, and scope is 0 (0) to 31.75dB (127). This is that transceiver is take BER as 10-7Or more preferably be successfully completed the noise margin that initialization must reach. (R, W, Set-by-Create) (enforceable) (1 byte)
Descending PBO control:
Descending power compensation (PBO) control for this circuit. For the transceiver of not supporting descending PBO control, this object must be fixed to forbidding (1). If select automatically (2), then transceiver is adjusted this power back-off automatically. If select manually (3), then transceiver uses descending PBO level. (R, W, Set-by-Create) (enforceable) (1 byte)
Up PBO control:
This is to ascending power compensation (PBO) control of this circuit. For the transceiver of not supporting up PBO control, this object must be fixed to forbidding (1). If select automatically (2), then transceiver is adjusted this power back-off automatically. If select manually (3), then transceiver uses up PBO level. (R, W, Set-by-Create) (enforceable) (1 byte)
Descending PBO level:
Stipulated the descending compensation level that when descending PBO controlled attribute is configured to manually (3), will be used. Effective range is that 0dB (0) arrives 40dB (160), is spaced apart 0.25dB. (R, W, Set-by-Create) (enforceable) (1 byte)
Up PBO level:
Stipulated the up compensation level that when up PBO control is configured to manually (3), will be used. Effective range is that 0dB (0) arrives 40dB (160), is spaced apart 0.25dB. (R, W, Set-by-Create) (enforceable) (1 byte)
Circuit types:
And how whether by channelizing, namely which (a bit) channel type is supported by the definition circuit, the VDSL physical entity when this parameter has been stipulated to start. If this circuit is about to by channelizing, then this value will be the value except noChannel (1). Defined value is: there is channel in noChannel (1)-not, there is Fast Channel in fastOnly (2)-only, there is slow channel in slowOnly (3)-only, fastOrSlow (4)-have Fast Channel or slow channel, but once only have one; And fastAndSlow (5)-fast and slow channel and deposit. (R, W, Set-by-Create) (enforceable) (1 byte)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Nothing.
Managed entity: VDSL channel configuration profile
The example of this managed entity represents the VDSL channel configuration profile of supporting on the ONU. Zero or a plurality of VDSL physical pathway tip node can be consulted the example of VDSL channel configuration profile managed entity. The example of this managed entity answers the request of OLT to be created and deleted by ONU.
Relation
Zero or the Multi-instance of this managed entity all are comprised among the ONU. One or more examples of this managed entity should be comprised among the ONU of the example that comprises physical pathway tip node VDSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
The downstream rate ratio:
This attribute is the extra allotment ratio that dispose of downstream transmission bandwidth between quick and slow channel. Only have when supporting dual-channel mode and adaptAtlnit, just use this attribute (that is, in VDSL line configuring profile, the uplink/downlink rate mode being set). When these fields were configured to adaptAtlnit (2), two VDSL modems arranged line speed based on the line condition that initializes (training) distribution bandwidth on each channel to surpass corresponding minimum transfer bit rate, consequently:
Rate variation ratio=[fast/(fast+at a slow speed)] * 100
In other words, this value is Fast Channel percentage. Effective range is 0 to 100. (R, W, Set-by-Create) (optionally) (1 byte)
The upstream rate ratio:
This attribute is the extra allotment ratio that dispose of uplink bandwidth between quick and slow channel. Only have when supporting dual-channel mode and adaptAtlnit, just use this attribute. Distribute the bandwidth that surpasses on each channel of corresponding minimum transfer bit rate, consequently:
Rate variation ratio=[fast/(fast+at a slow speed)] * 100
In other words, this value is Fast Channel percentage. Effective range is 0 to 100. (R, W, Set-by-Create) (optionally) (1 byte)
Descending at a slow speed maximum data rate:
This attribute has been stipulated maximum downstream slow channel data rate, and step-length is the 64K bps. Maximum total downlink transfer speed of circuit can derive fast and the slow channel data rate sum from maximum downstream. (R, W, Set-by-Create) (enforceable) (2 bytes)
Descending at a slow speed minimum data rate:
Stipulated minimum descending slow channel data rate, step-length is the 64K bps. Minimum total downlink transfer speed of circuit can derive fast and the slow channel data rate sum from minimum is descending. (R, W, Set-by-Create) (enforceable) (2 bytes)
Up at a slow speed maximum data rate:
Stipulated maximum up slow channel data rate, step-length is the 64K bps. Maximum total uplink speed of circuit can derive fast and the slow channel data rate sum from maximum is up. (R, W, Set-by-Create) (enforceable) (2 bytes)
Up at a slow speed minimum data rate:
Stipulated minimum up slow channel data rate, step-length is the 64K bps. Minimum total uplink speed of circuit can derive fast and the slow channel data rate sum from minimum is up. (R, W, Set-by-Create) (enforceable) (2 bytes)
The delay that interweaves of descending maximum:
The delay that interweaves of the maximum of having stipulated descending slow channel, unit is millisecond. Effective range is 0 to 255ms. (R, W, Set-by-Create) (enforceable) (1 byte)
The delay that interweaves of up maximum:
The delay that interweaves of the maximum of having stipulated up slow channel, unit is millisecond. Effective range is 0 to 255ms. (R, W, Set-by-Create) (enforceable) (1 byte)
Descending target happens suddenly at a slow speed:
Stipulated the target level of impulsive noise (burst) protection of descending slow channel, unit is microsecond. Effective range is 0 to 1275 μ s. (R, W, Set-by-Create) (enforceable) (2 bytes)
Up target happens suddenly at a slow speed:
Stipulated the target level of impulsive noise (burst) protection of up slow channel, unit is microsecond. Effective range is 0 to 1275 μ s. (R, W, Set-by-Create) (enforceable) (2 bytes)
Descending quick maximum data rate:
Stipulated maximum downstream Fast Channel data rate, step-length is the 64K bps. (R, W, Set-by-Create) (enforceable) (2 bytes)
Descending quick minimum data rate:
Stipulated minimum descending Fast Channel data rate, step-length is the 64K bps. (R, W, Set-by-Create) (enforceable) (2 bytes)
Up quick maximum data rate:
Stipulated maximum up Fast Channel data rate, step-length is the 64K bps. (R, W, Set-by-Create) (enforceable) (2 bytes)
Up quick minimum data rate:
Stipulated minimum up Fast Channel data rate, step-length is the 64K bps. (R, W, Set-by-Create) (enforceable) (2 bytes)
The quick FEC of descending maximum:
This attribute has been stipulated the maximum horizontal of forward error correction (FEC) redundancy that the expense with keeping of descending Fast Channel is relevant with percentage. Effective range is 0 to 50%. (R, W, Set-by-Create) (optionally) (1 byte)
The quick FEC of up maximum:
This parameter has been stipulated the maximum horizontal of forward error correction (FEC) redundancy that the expense with keeping of up Fast Channel is relevant with percentage. Effective range is 0 to 50%. (R, W, Set-by-Create) (optionally) (1 byte)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Nothing.
Managed entity: VDSL band plan configuration profile
The example of this managed entity represents the VDSL band plan configuration profile of supporting on the ONU. Zero or a plurality of VDSL physical pathway tip node can be consulted the example of VDSL band plan configuration profile managed entity. The example of this managed entity answers the request of OLT to be created and deletion by ONU.
Relation
Zero or the Multi-instance of this managed entity all are comprised among the ONU. One or more examples of this managed entity are comprised among the ONU of the example that comprises physical pathway tip node VDSL UNI.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. Value 0x00 reserves. (R, Set-by-create) (enforceable) (2 bytes)
Band plan:
The VDSL band plan that is used to this circuit is stipulated by this entity. BandPlan997 (1) will be used to ITU-T G.993.1Bandplan-B, ETSI Bandplan, ANSI planning 997. BandPlan998 (2) will be used to G.993.1 Bandplan-A of ITU-T, ANSI planning 998. BandPlanFx (3) will be used to G.993.1 Bandplan-C of ITU-T. Other (4) will be used to off-gauge band plan. If this object is configured to bandPlanFx (3), then band plan FX must be set also. (R, W, Set-by-Create) (enforceable) (1 byte)
Band plan FX:
When band plan was configured to bandPlanFx (3), frequency limitation was between frequency band D2 and U2, and unit is kHz. Effective range is 3750 to 12000kHz. (R, W, Set-by-Create) (optionally) (2 bytes)
Frequency band Opt purposes:
Having defined selectable frequency scope [25kHz-138kHz] VDSL link (Opt) uses. Value does not use (1) indication not use opt, and up (2) indication opt purposes is up, and descending (3) indication opt purposes is descending. (R, W, Set-by-Create) (enforceable) (1 byte)
Up PSD template:
Up PSD template will be used to this circuit. Here, templateMask1 (1) refers to porose mask, and this porose mask is limited in the PSD that transmits in the ham radio wave band of International standardization, and the mask of templateMask2 (2) atret-. Mask itself depends on the applied code of using. (R, W, Set-by-Create) (enforceable) (1 byte)
Descending PSD template:
Descending PSD template will be used to this circuit. Here, templateMask1 (1) refers to porose mask, and this porose mask is limited in the PSD that transmits in hand-held (handheld) ham radio wave band of International standardization, and the mask of templateMask2 (2) atret-. Mask itself depends on the applied code of using. (R, W, Set-by-Create) (enforceable) (1 byte)
The amateur frequency band mask:
The transmit power spectral density mask is used to avoid conflicting with hand-held ham radio wave band by introducing power control (punching) in the one or more wavestrips in these wavestrips. In the VDSL frequency spectrum as the punching of ham radio wave band of giving a definition:
Frequency band begins frequency and stops frequency
30m 1810kHz 2000kHz
40m 3500kHz 3800kHz(ETSI)；4000
kHz(ANSI)
80m 7000kHz 7100kHz(ETSI)；7300
kHz(ANSI)
160m 10100kHz 10150kHz
The punching of each standard wave band can be enabled or stops using via this bit mask. Can stipulate two normal-stage punchings. If enabled customNotch1, then must open by regulation normal-stage punching 1, and normal-stage punching 2 stops. If enabled customNotch2, then must open by regulation normal-stage punching 2, and normal-stage punching 2 stops. Effectively place value is defined as foloows, and allows all combinations:
CustomNotch1 (0)-routine (area is special-purpose) perforation
CustomNotch2 (1)-routine (area is special-purpose) perforation
AmateurBand30m (2)-ham radio wave band perforation
AmateurBand40m (3)-ham radio wave band perforation
AmateurBand80m (4)-ham radio wave band perforation
AmateurBand160m (5)-ham radio wave band perforation
(R, W, Set-by-Create) (enforceable) (1 byte)
Normal-stage punching 1 beginning:
Stipulated the beginning frequency of conventional hand-held ham radio perforation 1, unit is kHz. This field must be less than or equal to normal-stage punching 1 and stop. Effective range is 0 to 65535kHz. (R, W, Set-by-Create) (optionally) (2 bytes)
Normal-stage punching 1 stops:
Stipulated the termination frequency of conventional hand-held ham radio perforation 1, unit is kHz. This field must be more than or equal to normal-stage punching 1 beginning. Effective range is 0 to 65535kHz. (R, W, Set-by-Create) (optionally) (2 bytes)
Normal-stage punching 2 beginnings:
Stipulated the beginning frequency of conventional hand-held ham radio perforation 2, unit is kHz. This field must be less than or equal to normal-stage punching 2 and stop. Effective range is 0 to 65535kHz. (R, W, Set-by-Create) (optionally) (2 bytes)
Normal-stage punching 2 stops:
Stipulated the termination frequency of conventional hand-held ham radio perforation 2, unit is kHz. This field must be more than or equal to normal-stage punching 2 beginnings. Effective range is 0 to 65535kHz. (R, W, Set-by-Create) (optionally) (2 bytes)
Dispose (deployment) situation:
VDSL circuit deployment scenario. When using fttCab (1), VTU-C is arranged in the rack in street. When using fttEx (2), VTU-C is positioned at central office. Becoming this value will be on not impact of transceiver. (R, W, Set-by-Create) (enforceable) (1 byte)
ADSL exists:
Indicated the existence of ADSL business in relevant bunch of cables/binding. Indicated in this intrafascicular ADSL of not having business without (1), adslOverPots (2) has indicated in this intrafascicular existence professional by the ADSL of POTS, and adslOverISDN (3) has indicated this intrafascicular existence professional by the ADSL of ISDN. (R, W, Set-by-Create) (enforceable) (1 byte)
Applied code:
The VDSL standard will be used to this circuit. Value ansi (1) has indicated ansi standard, and etsi (2) has indicated etsi standard, and itu (3) has indicated the ITU standard, and other (4) have indicated standard apart from the above. (R, W, Set-by-Create) (enforceable) (1 byte)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Arrange: one or more attributes are set.
Notice
Nothing.
Managed entity: VDSL VTU-O physical interface monitoring historical data
This managed entity comprises the statistics of the collected VDSL physical interface in 15 minutes intervals of last end. After the example of physical pathway tip node VDSL UNI managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT. Support the performance management of the physical interface that VDSL is used. Fault/notice should comprise the threshold value alarm of unacceptable performance (mistake) grade. Performance data should comprise make mistakes second (ES), the transmission counting of seriously makeing mistakes second (SES) and invalid second (UAS).
Relation
An example that can have for each example of physical pathway tip node VDSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is slot ID. Second byte is port id, and the value scope of this port id is from 0x01 to 0xFF (1 to 255). (R, W, Set-by-create) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. Finish new interval, cycle counter (modulus is 0xFF (256)) just increases progressively, and this attribute counter is updated at every turn. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during first cycle after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. This attribute counter is updated when finishing at the interval. (R) (enforceable) (1 byte)
Threshold dataR-PON ID：
This attribute is to threshold dataR-PONThe example of managed entity provides pointer, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set by-create) (enforceable) (2 bytes)
The group Frame loss second:
The counting that has the second of this interim that framing loses. (R) (enforceable) (2 bytes)
Dropout second:
Exist blackout this interim the second counting. (R) (enforceable) (2 bytes)
Power loss second:
Exist power loss this interim the second counting. (R) (enforceable) (2 bytes)
Loss of link second:
Exist loss of link this interim the second counting. (R) (enforceable) (2 bytes)
Make mistakes second:
The counting of makeing mistakes second of this interim. Makeing mistakes second is one second long interval, and this interval comprises the shortcoming that the unusual or one or more dropouts of one or more CRC or framing are lost. (R) (enforceable) (2 bytes)
Seriously make mistakes second:
The counting of seriously makeing mistakes second of this interim. (R) (enforceable) (2 bytes)
Invalid second:
Invalid second the counting of this interim. (R) (enforceable) (2 bytes) circuit initializes:
The circuit of this interim initializes the counting of attempting. This counting comprises the trial of success and failure. (R) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to the informing network management system. TCA changes notice " on " and is sent out when the actual count device is out-of-limit; TCA changes notice " off " and is sent out when being reset 15 minutes end cycles of 0x 00 beginning from the actual count device. ONU and OLT should know the employed list of thing of this entity. In table 13, provided the tabulation of the TCA of this entity.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | LOFS | Surpass | 1 |
| 1 | LOSS | Surpass threshold value | 2 |
| 2 | LOLS | Surpass threshold value | 3 |
| 3 | LOPS | Surpass threshold value | 4 |
| 4 | ES | Surpass threshold value | 5 |
| 5 | LI | Surpass threshold value | 6 |
| 6 | SES | Surpass threshold value | 7 |
| 7 | UAS | Surpass threshold value | 8 |
| 8-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter, etc.
Table 13
Managed entity: VDSL VTU-R physical interface monitoring historical data
This managed entity comprises the statistics of the collected VDSL physical interface in 15 minutes intervals of last end. After the example of physical pathway tip node VDSL UNI managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT. Support the performance management of the physical interface that VDSL is used. Fault/notice should comprise the threshold value alarm of unacceptable performance (mistake) grade. Performance data should comprise make mistakes second (ES), the transmission counting of seriously makeing mistakes second (SES) and invalid second (UAS).
Relation
An example that can have for each example of physical pathway tip node VDSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is slot ID. Second byte is port id, and the value scope of this port id is from 0x01 to 0xFF (1 to 255). (R, W, Set-by-create) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. Finish new interval, cycle counter (modulus is 0xFF (256)) just increases progressively, and attribute counter is updated at every turn. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during first cycle after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. This attribute counter is updated when finishing at the interval. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute is to threshold dataB-PONThe example of managed entity provides pointer, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
The group Frame loss second:
The counting of second that has this interim of framing loss. (R) (enforceable) (2 bytes)
Dropout second:
Exist dropout this interim the second counting. (R) (enforceable) (2 bytes)
Power loss second:
Exist power loss this interim the second counting. (R) (enforceable) (2 bytes)
Loss of link second:
Exist loss of link this interim the second counting. (R) (enforceable) (2 bytes)
Make mistakes second:
The counting of makeing mistakes second of this interim. Makeing mistakes second is one second long interval, and this interval comprises the shortcoming that the unusual or one or more dropouts of one or more CRC or framing are lost. (R) (enforceable) (2 bytes)
Seriously make mistakes second:
The counting of seriously makeing mistakes second of this interim. (R) (enforceable) (2 bytes)
Invalid second:
Invalid second the counting of this interim. (R) (enforceable) (2 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to the informing network management system. TCA changes notice " on " and will be sent out when the actual count device is out-of-limit; TCA changes notice " off " and will be sent out when being reset 15 minutes end cycles that 0x00 begins from this actual count device. ONU and OLT should know by the employed list of thing of this entity. In table 14, provided the tabulation of the TCA of this entity.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | LOFS | Surpass | 1 |
| 1 | LOSS | Surpass threshold value | 2 |
| 2 | LOLS | Surpass threshold value | 3 |
| 3 | LOPS | Surpass threshold value | 4 |
| 4 | ES | Surpass threshold value | 5 |
| 5 | SES | Surpass threshold value | 6 |
| 6 | UAS | Surpass threshold value | 7 |
| 7-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 has been indicated the first threshold counter, etc.
Table 14
Managed entity: VDSL VTU-O channel performance monitoring historical data
This managed entity comprise as from VTU-O, 15 minutes collected statistics in interval of the last end of VDSL channel fast and at a slow speed. After the example of physical pathway tip node VDSL UNI managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT.
Relation
An example that can have for each example of physical pathway tip node VDSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is slot ID. Second byte is port id, and the value scope of this port id is from 0x01 to 0xFF (1 to 255). (R, W, Set-by-create) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of finishing recently. Finish new interval, cycle counter (modulus is 0xFF (256)) just increases progressively, and attribute counter is updated at every turn. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during first cycle after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. This attribute counter is updated when finishing at the interval. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute is to threshold dataB-PONThe example of managed entity provides pointer, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
Fast Channel is correcting block:
This attribute is VTU-O received all pieces of the mistake that has been corrected in formerly 15 minutes on inherent this Fast Channel in interval counting. (R) (enforceable) (4 bytes)
Fast Channel damages piece:
This attribute is VTU-O received all pieces of uncorrectable error in formerly 15 minutes on inherent this Fast Channel in interval counting. (R) (enforceable) (4 bytes)
Fast Channel is transmission block:
This attribute is the counting of all pieces of transmitting on inherent this Fast Channel in formerly 15 minutes intervals of VTU-O. (R) (enforceable) (4 bytes)
Fast Channel has received piece:
This attribute is the counting of all pieces of receiving on inherent this Fast Channel in formerly 15 minutes intervals of VTU-O. (R) (enforceable) (4 bytes)
Slow channel is correcting block:
This attribute is VTU-O received all pieces of the mistake that has been corrected in formerly 15 minutes on inherent this slow channel in interval counting. (R) (enforceable) (4 bytes)
Slow channel is damaged piece:
This attribute is VTU-O received all pieces of uncorrectable error in formerly 15 minutes on inherent this slow channel in interval counting. (R) (enforceable) (4 bytes)
Slow channel is transmission block:
This attribute is the counting of all pieces of transmitting on inherent this slow channel in formerly 15 minutes intervals of VTU-O. (R) (enforceable) (4 bytes)
Slow channel has received piece:
This attribute is the counting of all pieces of receiving on inherent this slow channel in formerly 15 minutes intervals of VTU-O. (R) (enforceable) (4 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to the informing network management system. TCA changes notice " on " and will be sent out when the actual count device is out-of-limit; TCA changes notice " off " and will be sent out when being reset 15 minutes end cycles that 0x00 begins from the actual count device. ONU and OLT should know the employed list of thing of this entity. In table 15, provided the tabulation of the TCA of this entity.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | FCCB | Surpass | 1 |
| 1 | FCBB | Surpass threshold value | 2 |
| 2 | SCCB | Surpass threshold value | 3 |
| 3 | SCBB | Surpass threshold value | 4 |
| 4-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter, etc.
Table 15
Managed entity: VDSL VTU-R channel performance monitoring historical data
This managed entity comprised as from VTU-R, 15 minutes collected statistics in interval of the last end of VDSL channel fast and at a slow speed. After the example of physical pathway tip node VDSL UN I managed entity was created/deletes, the example of this managed entity was created/is deleted by OLT.
Relation
An example that can have for each example of physical pathway tip node VDSL UNI this managed entity.
Attribute
Managed entity ID:
This attribute provides unique numbering for each example of this managed entity. The numbering of these 2 bytes is directly related with the physical location of UNI. First byte is slot ID. Second byte is port id, and the value scope of this port id is from 0x01 to 0xFF (1 to 255). (R, W, Set-by-create) (enforceable) (2 bytes)
The interval concluding time:
This attribute-bit 15 minutes intervals of nearest end. Finish at each new interval, and cycle counter (modulus is 0xFF (256)) just increases progressively, and attribute counter is updated. The value of this attribute is 0x00 in first the 15 minute interim with reception " lock in time " action beginning. This value is 0x01 during the period 1 after this, etc. If this managed entity is created after receiving " lock in time " action, then the value of this attribute is configured to equal the numbering at the interval of end last time. The actual count device of this managed entity directly begins counting. This attribute counter is updated when finishing at the interval. (R) (enforceable) (1 byte)
Threshold dataB-PON ID：
This attribute is to threshold dataB-PONThe example of managed entity provides pointer, and this pointer comprises for the threshold value by the collected performance monitoring data of this managed entity. (R, W, Set-by-create) (enforceable) (2 bytes)
Fast Channel is correcting block:
This attribute is VTU-R received all pieces of the mistake that has been corrected in formerly 15 minutes on inherent this Fast Channel in interval counting. (R) (enforceable) (4 bytes)
Fast Channel damages piece:
This attribute is VTU-R received all pieces of uncorrectable error in formerly 15 minutes on inherent this Fast Channel in interval counting. (R) (enforceable) (4 bytes)
Fast Channel is transmission block:
This attribute is the counting of all pieces of transmitting on inherent this Fast Channel in formerly 15 minutes intervals of VTU-R. (R) (enforceable) (4 bytes)
Fast Channel has received piece:
This attribute is the counting of all pieces of receiving on inherent this Fast Channel in formerly 15 minutes intervals of VTU-R. (R) (enforceable) (4 bytes)
Slow channel is correcting block:
This attribute is VTU-R received all pieces of the mistake that has been corrected in formerly 15 minutes on inherent this slow channel in interval counting. (R) (enforceable) (4 bytes)
Slow channel is damaged piece:
This attribute is VTU-R received all pieces of uncorrectable error in formerly 15 minutes on inherent this slow channel in interval counting. (R) (enforceable) (4 bytes)
Slow channel is transmission block:
This attribute is the counting of all pieces of transmitting on inherent this slow channel in formerly 15 minutes intervals of VTU-R. (R) (enforceable) (4 bytes)
Slow channel has received piece:
This attribute is the counting of all pieces of receiving on inherent this slow channel in formerly 15 minutes intervals of VTU-R. (R) (enforceable) (4 bytes)
Action
Create: the example that creates this managed entity.
Deletion: the example of deleting this managed entity.
Obtain: obtain one or more attributes.
Obtain current data: the currency that obtains one or more attributes.
Arrange: one or more attributes are set.
Notice
Threshold Crossing Alert:
When Threshold Crossing Alert (TCA) had been detected or has been eliminated, this notice was used to the informing network management system. TCA changes notice " on " and will be sent out when the actual count device is out-of-limit; TCA changes notice " off " and will be sent out when being reset 15 minutes end cycles that 0x00 begins from this actual count device. ONU and OLT should know the employed list of thing of this entity. In table 16, provided the tabulation of the TCA of this entity.
| Numbering | Event | Explanation | Threshold data counter numbering * |
| | |||
| 0 | FCCB | Surpass | 1 |
| 1 | FCBB | Surpass threshold value | 2 |
| 2 | SCCB | Surpass threshold value | 3 |
| 3 | SCBB | Surpass threshold value | 4 |
| 4-255 | Reserve |
* this numbering and relevant threshold dataB-PONManaged entity uses together. Threshold data counter 1 indication first threshold counter, etc.
Table 16
A kind of equipment and process have been described to useful equipment and the process of PON ONT for management and control figure subscriber line interface. Specialized application of the present invention and exemplary embodiment are illustrated and discuss, and these are used and embodiment provides for using realization basis of the present invention in every way and at diverse network. Within the scope of the invention, multiple modification is possible. Feature and the element relevant with one or more described embodiment should not be understood to be the required element of all embodiment. The present invention is only limited by accompanying claim.
Claims (65)
1. one kind is used for management and provides the method for the network of data service to the user, and wherein, described network comprises OLT and be connected to the ONU of OLT via EPON, and wherein, described ONU connects by xDSL and is connected with the user, and described method comprises:
Be provided for managing a plurality of managed entities of ONU, wherein, described a plurality of managed entity also comprises ADSL managed entity and VDSL managed entity, described ADSL managed entity is used for management ONU and is connected with ADSL between the user, and described VDSL managed entity is used for the VDSL connection between management ONU and the user;
Manage described network by the one or more managed entities in described a plurality of managed entities; And
In response to described managed entity, between OLT and ONU, transmit data and network management information.
2. the step that the method for claim 1, wherein transmits data and network management information also comprises by described EPON and transmits described data and described network management information.
3. the method for claim 1, wherein each managed entity in described a plurality of managed entity also comprises one or more network attributes, and each network attribute is relevant with network characterization.
4. method as claimed in claim 3, wherein, the network attribute relevant with relevant network characterization is included in the single managed entity.
5. method as claimed in claim 4, wherein, be included in network attribute in the single ADSL managed entity, relevant with relevant network characterization and comprise one or more in the lower Column Properties: channel performance monitors historical data, ATU-C and ATU-R performance monitoring historical data, channel configuration profile, channel downstream state data, channel uplink status data, descending PSD mask profile, descending RFI frequency band profile, subcarrier shield descending profile, subcarrier shields up profile, out-of-limit (threshold crossing) adapter performance monitoring historical data.
6. method as claimed in claim 4, wherein, being included in network attribute in the single VDSL managed entity, relevant with relevant network characterization comprises: one or more physical pathway tip node VDSL UNI, band plan configuration profile, channel configuration profile, channel data, line configuring profile, VTU-O and VTU-R channel performance monitoring historical data, VTU-O and VTU-R physical data, VTU-O and VTU-R physical interface monitoring historical data.
7. method as claimed in claim 3, wherein, one or more running parameter during network attribute defines OLT, ONU, EPON, ADSL connects and VDSL is connected, and wherein, the network attribute relevant with relevant network characterization is included in the single managed entity.
8. method as claimed in claim 3, wherein, the network attribute relevant with relevant network characterization is included in a plurality of relevant managed entities.
9. method as claimed in claim 8, wherein, described a plurality of relevant managed entities comprise with adsl line configuration profile, adsl line stock and status data and physical pathway tip node ADSL UNI in one or more relevant managed entity.
10. the method for claim 1, wherein each managed entity is represented by the data byte of fixed qty.
11. method as claimed in claim 10, wherein, the data byte of described fixed qty comprises 53 data bytes.
12. the method for claim 1, wherein, each managed entity in described a plurality of managed entity represents and comprises the one or more network attributes that are selected from a plurality of network attributes by the data bit of fixed qty, and wherein, each network attribute is represented by data bit, and wherein, in order to be included in each managed entity in a plurality of managed entities and the network attribute of selecting comprises the network attribute relevant with relevant network characterization and the network attribute with data bit summation of the data bit that is less than or equal to described fixed qty.
13. the method for claim 1, wherein described data service comprises telephone service, internet data business, multimedia service and video traffic.
14. the method for claim 1, wherein described EPON comprises BPON or gigabit passive optical network.
15. the method for claim 1, wherein the described network network that comprises that Fiber to the home, optical fiber are to commercial user's network, FTTB network, Fiber To The Curb network, FTTP network or optical fiber to the commuting case network.
16. the method for claim 1 comprises that also from the request of NMS receiving network managing, wherein, the step of supervising the network is in response to described network management request.
17. the method for claim 1 also comprises, when the xDSL connection is activated, produces a plurality of managed entities.
18. the method for claim 1, wherein each managed entity comprises one or more in relationship elements, property element, action element and the notice element.
19. method as claimed in claim 18, wherein, described notice element comprises that also alarm, test result and property value change.
20. the method for claim 1, wherein, each managed entity in described a plurality of managed entity comprises network attribute, and wherein, some relevant network attribute is included in the managed entity, and some other relevant network attribute is included in two managed entities at least.
21. the method for claim 1, wherein described a plurality of managed entity also comprises essential managed entity and optional managed entity.
22. the method for claim 1, also comprise a plurality of users and a plurality of ONU, wherein, among described a plurality of ONU each is connected with the user by xDSL, and wherein, transfer step also comprises in response to described managed entity transmit data and network management information between described OLT and a plurality of ONU.
23. one kind is used for management provides method from the network of communication service to a plurality of users, wherein, described network comprises the EPON that contains OLT and the ONU that is connected to OLT via this EPON, wherein, each ONU also defines a plurality of slots, and each slot further defines a plurality of ports, and wherein, each port comprises a plurality of channels, and wherein, the user is connected by the XDSL of a port in described a plurality of ports by an ONU among a plurality of ONU and is connected to described EPON, and described method comprises:
Be provided for managing a plurality of managed entities that xDSL connects, wherein, one or more managed entities in the described managed entity are relevant with channel, and wherein, in described managed entity, identify described channel according to more than first bit of sign port, more than second bit of sign slot and more than the 3rd bit of sign channel;
Manage described network by the one or more managed entities in described a plurality of managed entities; And
In response to described managed entity, transmit data and network management information.
24. method as claimed in claim 23, wherein, described more than first bit comprises byte, and described second comprises byte with the combination of described more than the 3rd bit.
25. method as claimed in claim 24, wherein, described more than second bit comprises six bits, and described more than the 3rd bit comprises two bits.
26. one kind is used for management provides method from the network of data service to a plurality of users, wherein, described network comprises OLT and is connected to a plurality of ONU of OLT via EPON, wherein, each ONU further connects by xDSL and is connected with a plurality of users, and described method comprises:
Be provided for managing the managed entity of ONU, wherein, described managed entity also comprises ADSL managed entity and VDSL managed entity, and described ADSL managed entity is used for management ONU and is connected with ADSL between the user, and described VDSL managed entity is used for managing ONU and is connected with VDSL between the user;
Manage described network in response to one or more described managed entities; And
In response to described managed entity, between OLT and a plurality of ONU, transmit data and network management information.
27. an OLT who is used for the management EPON, described EPON comprises a plurality of ONU, and each ONU provides a plurality of xDSL links, and each link comprises a plurality of channels, and described OLT comprises:
Controller is used for by allotting a plurality of channels that managed entity is managed described a plurality of xDSL links to described ONU, and wherein, each managed entity comprises link identifier and Channel Identifier; And
Transceiver is used for to described ONU transmission data with from described ONU receive data.
28. OLT as claimed in claim 27, wherein, each ONU comprises a plurality of slots, and each slot also comprises a plurality of ports, and each port comprises a plurality of channels, and wherein, the port of user in a plurality of ports is connected with described ONU.
29. OLT as claimed in claim 28, wherein, some managed entity comprises slot identifier, port identifiers and Channel Identifier.
30. OLT as claimed in claim 29, wherein, described slot identifier comprises more than first bit, and described port identifiers comprises more than second bit, and described Channel Identifier comprises more than the 3rd bit.
31. OLT as claimed in claim 30, wherein, described more than second bit comprises byte, and described first comprise byte with the combination of described more than the 3rd bit.
32. OLT as claimed in claim 31, wherein, described more than first bit comprises six bits, and described more than the 3rd bit comprises two bits.
33. an ONU, it can be connected to a plurality of users and can be connected to OLT via EPON via the xDSL link, and described ONU comprises:
Network processing unit, this network processing unit are used for managing described xDSL link in response to the managed entity of being allotted by described OLT; And
Transceiver for the data by receiving from the user to described xDSL chain road direction OLT transmission, and is used for from the OLT receive data, and provides the data that receive by described xDSL chain road direction user.
34. ONU as claimed in claim 33, wherein, described EPON comprises BPON or gigabit passive optical network.
35. ONU as claimed in claim 33 also comprise a plurality of slots, and each slot also comprises a plurality of ports, and each port also comprises a plurality of channels, and wherein, described xDSL link is connected to a port in described a plurality of port.
36. ONU as claimed in claim 35, wherein, some managed entity comprises slot identifier, port identifiers and Channel Identifier.
37. ONU as claimed in claim 36, wherein, described slot identifier comprises more than first bit, and described port identifiers comprises more than second bit, and described Channel Identifier comprises more than the 3rd bit.
38. ONU as claimed in claim 37, wherein, described more than second bit comprises byte, and described first comprise byte with the combination of described more than the 3rd bit.
39. ONU as claimed in claim 38, wherein, described more than first bit comprises six bits, and described more than the 3rd bit comprises two bits.
40. a management information bank, it comprises a plurality of managed entities for supervising the network, and wherein, described network comprises EPON and be connected a plurality of users' xDSL link that described management information bank comprises:
More than first managed entity is used for disposing described xDSL link;
More than second managed entity is used for managing the operation of described xDSL link; And
More than the 3rd managed entity is used for the report of request xDSL link performance.
41. a management information bank that is used for supervising the network, wherein, described network comprises EPON and is connected to a plurality of users' xDSL link that described management information bank comprises:
More than first essential managed entity; And
More than second optional managed entity.
42. management information bank as claimed in claim 41, wherein, described more than first essential managed entities comprise and ADSL channel configuration profile, the ADSL channel is descending and uplink state data, the descending PSD mask of ADSL channel profile, the descending RFI frequency band of ADSL profile, adsl line configuration profile, adsl line stock and status data, ADSL the subcarrier descending and up profile of shielding and physical pathway tip node ADSL User Network Interface are relevant managed entity.
43. management information bank as claimed in claim 41, wherein, described more than second optional managed entities comprise the managed entity relevant with the out-of-limit adapter performance monitoring of ADSL historical data with ADSL ATU-C and ATU-R channel performance monitoring historical data, ATU-C and ATU-R performance monitoring historical data.
44. management information bank as claimed in claim 41, wherein, described more than first essential managed entities comprise the managed entity relevant with VDSL physical pathway tip node User Network Interface, VDSL band plan configuration profile, VDSL channel configuration profile, VDSL channel data, VDSL line configuring profile and VDSL VTU-O and VTU-R physical data.
45. management information bank as claimed in claim 41, wherein, described more than second optional managed entities comprise that monitoring historical data and VDSL VTU-O and VTU-R physical interface with VDSL VTU-O and VTU-R channel performance monitors the relevant managed entity of historical data.
46. communication network that is used for providing to a plurality of users communication service;
The first optic terminal unit;
A plurality of the second optic terminal unit, each second optic terminal unit is connected with same a plurality of users by many xDSL circuits;
The passive optical communications path, it is disposed between described the first optic terminal unit and described the second optic terminal unit, is used for carrying the information between described the first optic terminal unit and described the second optic terminal unit;
Wherein, described the first optic terminal unit is as network manager, be used for managing described the second optic terminal unit and described xDSL circuit with a plurality of managed entities, and wherein, the length of each managed entity in described a plurality of managed entities is limited to the bit of predetermined quantity.
47. communication network as claimed in claim 46, wherein, described xDSL circuit comprises adsl line or VDSL circuit.
48. communication network as claimed in claim 46, wherein, each managed entity in described a plurality of managed entity comprises be used to one or more attributes of managing described many xDSL circuits, and wherein, managed entity comprises relevant attribute, and wherein, the bit of predetermined quantity defines the quantity that can be included in an attribute in the managed entity, and wherein, some relevant attribute distributes between at least the first and second managed entities.
49. communication network as claimed in claim 48, wherein, described first and described the second managed entity comprise one of following managed entity: managed entity, adsl line stock and status data part 1 and the managed entity of part 2 and the managed entity of physical pathway tip node ADSL User Network Interface part 1 and part 2 of adsl line configuration profile part 1 and part 2.
50. communication network as claimed in claim 46, wherein, described the first optic terminal unit is connected to one or more external networks, and being used for provides communication service between described a plurality of users and described one or more external network.
51. communication network as claimed in claim 50, wherein, described one or more external networks comprise the internet, one or more in the network of video traffic and the telephone service network are provided.
52. goods, it comprises:
Computer-readable program product, this computer-readable program product comprises having the computer-readable medium that is stored in computer-readable code wherein, also comprise the management information bank that provides the network of data service to a plurality of xDSL users for managing, described goods comprise:
Computer readable program code module, this computer readable program code module comprise more than first essential managed entity; And
Computer readable program code module, this computer readable program code module comprise more than second optional managed entity.
53. memory, be used for storing the data of being accessed by the network manager program of carrying out in the first ONT Optical Network Terminal unit and store the data that are used for control xDSL link, described the first ONT Optical Network Terminal unit is connected to EPON, described xDSL link also is connected to EPON, and described memory comprises:
Data structure, described data structure are stored in this memory and comprise the employed information of described network manager program, and described data structure comprises:
Each has a plurality of managed entities of same predetermined length.
54. memory as claimed in claim 53, wherein, described network also is included in a plurality of the second ONT Optical Network Terminal unit that are connected between described EPON and the described xDSL link, and wherein, described the first ONT Optical Network Terminal unit provides managed entity to described the second ONT Optical Network Terminal unit, is used for the described xDSL link that control is connected with described the second ONT Optical Network Terminal unit.
55. memory as claimed in claim 54, wherein, each second ONT Optical Network Terminal unit in described a plurality of the second ONT Optical Network Terminal unit comprises a plurality of slots, and each slot also comprises a plurality of ports, and each port comprises a plurality of channels, and wherein, the port of xDSL link in described a plurality of ports is connected with described the second optic terminal unit.
56. memory as claimed in claim 55, wherein, some managed entity comprises slot identifier, port identifiers and Channel Identifier.
67. memory as claimed in claim 56, wherein, described slot identifier comprises more than first bit, and described port identifiers comprises more than second bit, and described Channel Identifier comprises more than the 3rd bit.
58. memory as claimed in claim 57, wherein, described more than second bit comprises byte, and described first comprise byte with the combination of described more than the 3rd bit.
59. memory as claimed in claim 58, wherein, described more than first bit comprises six bits, and described more than the 3rd bit comprises two bits.
60. memory as claimed in claim 53, wherein, described identical predetermined length comprises 53 bytes.
61. memory, be used for the data that storage is accessed by the network manager program that is used for the management EPON of carrying out in network manager device, wherein, described EPON comprises a plurality of optical network units, each optical network unit can connect by xDSL and be connected with a plurality of users, and described memory comprises:
Be stored in the data structure in the described memory, described data structure comprises the information that resides in the database, used by described network manager program, and described data structure comprises:
A plurality of managed entity data objects, each data object also comprise a plurality of attribute data objects, and each the attribute data object in a plurality of attribute data objects is relevant with the network running parameter.
62. memory as claimed in claim 61, wherein, described a plurality of managed entity data objects also comprise the line configuring profile managed entity data object that connects for ADSL.
63. memory as claimed in claim 62, wherein, described line configuring profile managed entity data object comprises one or more in following a plurality of attribute data object: managed entity ID, the ATU transmission system is enabled, force power management state, power management state is enabled, descending target noise margin, up target noise margin, descending maximum noise tolerance limit, up maximum noise tolerance limit, descending minimal noise tolerance limit, up minimal noise tolerance limit, the downstream rate adapt mode, the upstream rate adapt mode, descending inclined to one side noise margin, up inclined to one side noise margin, up PSD mask is selected, minimum up expense speed (overhead rate), minimum descending expense speed, the descending minimum interval that is used for upper inclined to one side rate adaptation, the up minimum interval that is used for upper inclined to one side rate adaptation, descending lower inclined to one side noise margin, up lower inclined to one side noise margin, the descending minimum interval that is used for lower inclined to one side rate adaptation, the up minimum interval that is used for lower inclined to one side rate adaptation, force the ATU impedance state, the L0 time, the L2 time, descending maximum rated power spectrum density, up maximum rated power spectrum density, descending maximum rated total transmitting power, up maximum rated total transmitting power, up maximum total received power, force the loop diagnostics pattern, force the automatic mode cold start-up, L2-ATPR, L2-ATPRT.
64. memory as claimed in claim 61, wherein, described a plurality of managed entity data objects also comprise the line configuring profile managed entity data object that connects for VDSL.
65. such as the described memory of claim 64, wherein, described line configuring profile managed entity data object comprises one or more in following a plurality of attribute data object: managed entity ID, downstream rate pattern, upstream rate pattern, descending peak power, up peak power, descending maximum S/N R tolerance limit, descending maximum S/N R tolerance limit, descending target SNR tolerance limit, up maximum S/N R tolerance limit, up minimum SNR tolerance limit, up target SNR tolerance limit, descending PBO control, up PBO control, descending PBO level, up PBO level, circuit types.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US52598303P | 2003-12-01 | 2003-12-01 | |
| US60/525,983 | 2003-12-01 | ||
| US60/540,990 | 2004-02-02 | ||
| US60/570,575 | 2004-05-13 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1914896A true CN1914896A (en) | 2007-02-14 |
Family
ID=37722694
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200480041227 Pending CN1914896A (en) | 2003-12-01 | 2004-11-19 | Passive optical network unit management and control interface support for a digital subscriber line network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1914896A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101719851A (en) * | 2009-11-26 | 2010-06-02 | 中兴通讯股份有限公司 | Method and device for realizing performance statistics of optical network unit |
| CN101344779B (en) * | 2007-07-13 | 2010-09-08 | 中华电信股份有限公司 | Network type remote monitoring management system for air-conditioner device |
| CN102983983A (en) * | 2012-12-13 | 2013-03-20 | 赵泽源 | Remote power supply adapter for home network equipment |
| CN106664344A (en) * | 2014-07-30 | 2017-05-10 | 英国电讯有限公司 | Method and apparatus for allocating power levels to a transmission in a digital subscriber line network |
| CN107196775A (en) * | 2016-03-14 | 2017-09-22 | 中兴通讯股份有限公司 | A kind of data statistical approach and device |
-
2004
- 2004-11-19 CN CN 200480041227 patent/CN1914896A/en active Pending
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101344779B (en) * | 2007-07-13 | 2010-09-08 | 中华电信股份有限公司 | Network type remote monitoring management system for air-conditioner device |
| CN101719851A (en) * | 2009-11-26 | 2010-06-02 | 中兴通讯股份有限公司 | Method and device for realizing performance statistics of optical network unit |
| CN102983983A (en) * | 2012-12-13 | 2013-03-20 | 赵泽源 | Remote power supply adapter for home network equipment |
| CN102983983B (en) * | 2012-12-13 | 2015-02-18 | 赵泽源 | Remote power supply adapter for home network equipment |
| CN106664344A (en) * | 2014-07-30 | 2017-05-10 | 英国电讯有限公司 | Method and apparatus for allocating power levels to a transmission in a digital subscriber line network |
| CN106664344B (en) * | 2014-07-30 | 2018-08-17 | 英国电讯有限公司 | For the method and apparatus of the transmission distribution power rank in digital subscriber line network |
| CN107196775A (en) * | 2016-03-14 | 2017-09-22 | 中兴通讯股份有限公司 | A kind of data statistical approach and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1568589A (en) | Method and system for processing downstream packets of an optical network | |
| CN100340067C (en) | Activation of multiple XDSL modems with implicit channel probe | |
| CN1499794A (en) | Method of processing data pack in third layer of communicating appts. | |
| CN1259814A (en) | Multiple transmission mode bus communication | |
| CN1682512A (en) | Method and apparatus for realizing multi-business branch on elastic package loop | |
| CN1751473A (en) | A method and system to implement policy-based network traffic management | |
| CN1152586C (en) | Base transceiver station and subscriber unit in wireless local loop system using personal handy-phone system and method for operating same | |
| CN1086877C (en) | Multi-point to point communication system | |
| CN1571304A (en) | An optical fibre transmission system and implementing method of optical fibre transmission thereof | |
| CN1350741A (en) | Wireless local loop system, supporting voice/IP | |
| CN1479979A (en) | High speed access system over copper cable plant | |
| CN1663267A (en) | Full-service broadband cable modem system | |
| CN1618223A (en) | Resilient multiple service ring | |
| CN1051278A (en) | Asynchronous optical communication system | |
| CN1767535A (en) | Data security level agreement unit, related device and method | |
| CN1431794A (en) | Multiplexer communication system and method thereof | |
| CN1238093A (en) | System and method for transporting call in telecommunication network | |
| CN1841989A (en) | Method and system for distributing high throughput bandwidth in a cable network | |
| CN1592259A (en) | Exchanger for network,route managing server,network interface device and its controlling method | |
| CN1013074B (en) | Time division multiplex (tdm) switching system especially for pulse code modulated (pcm) telephony signals | |
| CN1348664A (en) | Telecommunication services identification in a gateway | |
| CN1914896A (en) | Passive optical network unit management and control interface support for a digital subscriber line network | |
| CN101047459A (en) | Method for dynamic managing xDSL specturm and its device | |
| CN1408165A (en) | System and method for providing POTS servicesin DSL environment in event of failures | |
| CN1336057A (en) | Wireless local loop system and methods useful therefor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: NOKIA SIEMENS COMMUNICATION CO., LTD. Free format text: FORMER OWNER: SIEMENS AG Effective date: 20080425 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20080425 Address after: Munich, Germany Applicant after: Nokia Siemens Networks GmbH Address before: Munich, Germany Applicant before: Siemens AG |
|
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20070214 |