hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.1 Edge DEV (eDEV) / Edge System (eSYS) power | |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.1.1 Specification context | In order to limit current consumption over the cable medium, it is important that an eDEV, or an eSYS, operates within a bounded range of input voltage. In this respect, as described in Figure 4. • The eDEV (resp. eSYS) shall turn on at a voltage less than or equal to VONmax and greater than VOFFmin. • The eDEV (resp. ... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.1.2 Requirements | Table 11: eDEV Type-I / Type-I+ power E&PoC Edge Device (eDEV) Type-I / Type-I+ Requirement 6.1.1 The power supply of a Type-I eDEV shall operate within the characteristics in Table 13 hereafter. A Type-I eDEV shall ensure that the power supply of the eSYS it is part of operates within the characteristics in Table 13 h... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.1.3 Requirements | Table 12: eDEV Type-0 power E&PoC Edge Device (eDEV) Type-0 Requirement 6.1.2 The power supply of a Type-0 eDEV shall operate within the characteristics in Table 13 hereafter. A Type-0 eDEV may not ensure that the eSYS it is part of operates within the characteristics in Table 13 hereafter. Requirement 6.1.3 A Type-0 e... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.1.4 Requirements | Table 14: eDEV Type-I+ Hot-Plug support (Optional) E&PoC Edge Device (eDEV) Type-I+ Requirement 6.1.4 Adding a new eDEV/eSYS to an existing E&PoC BSS shall not cause any eDEV/eSYS already operated on this E&PoC BSS to interrupt its service due to a lack of power. ETSI ETSI TS 105 176-2 V1.1.1 (2019-06) 19 |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.2 Receiver Device (rDEV) per-port PoC | |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.2.1 Specification context | In order an rDEV to accommodate several eSYSs over a linear bus for one given rDEV port, relying on a cable type having significant resistance, it is required to have the rDEV generating a minimum output Power PrDEV, (i.e. a minimum output power per rDEV port) and associated voltage VrDEVOn on the line, according to on... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.2.2 Requirements | Table 15: rDEV power E&PoC Receiver Device (rDEV) Requirement 6.2.1 A Receiver Device (rDEV) shall be capable of supplying an output Power PrDEV and an output voltage VrDEVOn over any of its port, with PrDEV and VrDEVOn having the characteristics specified in Table 16. Requirement 6.2.2 The maximum power PrDEV of an rD... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.3 Receiver Device (rDEV) per-port PoC control (Optional) | |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.3.1 Specification context | One or more eSTA devices connected to one same port of an rDEV may experience some issues that require a reboot of such eSTA devices. Such reboot can be achieved by turning the power off on the rDEV port where such faulty device(s) is connected. In case the port of a manageable rDEV is set to off, the voltage VrDEVoff ... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 6.3.2 Requirements | Table 17: Receiver Device (rDEV) per-port PoC control (Conditional) E&PoC Receiver Device (rDEV) Requirement 6.3.1 A multi-port rDEV may provide either a User Interface (UI) or connectivity for a User Interface Station (UIS) that allows monitoring the value of the output voltage VrDEV (OR the level of PoC) on any of it... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.1 Receiver Station / Device throughput capability | |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.1.1 Specification context | An rDEV may embed a plurality of rSTAs (e.g. a 16-port PoC switch may embed 4 rSTAs), each rSTA being in charge of connecting one or more eSTAs arranged in a linear bus topology over one or more ports. Each connected eSTA should send video stream, to its connected rSTA. In this respect, some eSYS have the ability to ge... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.1.2 Requirements | Table 19: rSTA throughput capability E&PoC Receiver Station (rSTA) / Device (rDEV) Requirement 7.1.1 Each port of an rSTA shall be capable of handling a global stream bit rate per port that is at least equal to BrSTAPortmin1 for throughput class 1, 2 or 3 as defined in Table 20. Requirement 7.1.2 All ports of an rSTA s... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.2 Adapter eDEV throughput & streaming capability | |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.2.1 Specification context | An Adapter eDEV is in charge of forwarding the video stream it receives from a connected communication device, e.g. an IP camera, to an rSTA it is connected to through a coaxial cable. In this respect, some communication devices, e.g. multi-stream IP cameras, have the ability to generate several video streams simultane... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.2.2 Requirements | Table 23: Adapter eDEV throughput capability E&PoC Adapter Edge Device (Adapter eDEV) Requirement 7.2.1 The eSYS formed by the Adapter eDEV connected to a communication device (e.g. an IP camera), shall be capable of transmitting towards an rSTA a stream with a throughput up to BAdaptEDEV1 for throughput class 1, 2 or ... |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.3 Terminal eDEV throughput & streaming capability | |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.3.1 Specification context | A Terminal eDEV, e.g. a PoC camera, is in charge of sending video stream to an rSTA it is connected to through a coaxial cable. In this respect, some Terminal eDEVs have the ability to generate several video streams simultaneously (e.g. multi-stream IP cameras). |
78562718753e0d19d95686376ba8abd8 | 105 176-2 | 7.3.2 Requirements | Table 27: Terminal eDEV throughput capability E&PoC Terminal Edge Device (Terminal eDEV) Requirement 7.3.1 A Terminal eDEV shall be capable of transmitting a stream with a throughput up to BTerminalEDEV1 for throughput class 1, 2 or 3, as defined in Table 30, towards an rSTA when each port of the rSTA is connected to a... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 1 Scope | The present document provides a description of an OSI physical networking layer to communicate data over plastic optical fibre at 100 Mbit/s and 1 000 Mbit/s. A full duplex physical layer is described. Multi data type interface is proposed, as well as its encapsulation, coding and modulation needed to achieve 1 Gbit/s ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 2 References | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 3 Definitions and abbreviations | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: adaptive bit rate: capacity of PHY to adapt the bit rate as a function of the channel conditions and signal quality in coordination with the link partner bose, ray-chaudhurim hocquenghem: in coding theory the BCH codes form a class of ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABR Adaptive Bit Rate AC Alternate Current AOP Average Optical Power BCH bose, ray-chaudhurim hocquenghem BER Bit Error Rate BPSK Binary Phase Shift Keying CCRC CRC of current PDB CMB Physical Coding and Modulation Blocks ETSI ETSI TS 105 175-... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 4.1 Physical layer objectives | The following are the objectives of the PHY: • Provide 1 Gbit/s and 100 Mbit/s full duplex data transmission. • Provide speeds less than 1 Gbit/s and 100 Mbit/s with adaptive bit rate functionality if communication channel does not provide enough capacity. ETSI ETSI TS 105 175-1-2 V1.1.1 (2015-04) 10 • Support operatio... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 4.2 Coding and Modulation Blocks (CMB) | The PHY CMB couples the information in the data interface, to the Electro Optical interface (EO). The functions performed by the CMB comprise the generation of frames and the mapping of the bits in those frames to PAM symbols using the Multi-Level Cosset Coding technique, and to send them into a Tomlinson-Harashima Pre... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 4.3 Electro Optical Interface (EO) | The EO specifications detail the characteristics of the optical transmitter and receiver and also of the optical cabling. These are specific for each PHY and are defined in the annexes from A to D specifying each particular PHY. |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 4.4 Signalling | PHY signalling is performed by the CMB generating symbols to be transmitted on to the EO interface. The signalling scheme achieves a number of objectives including: a) Forward error correction (FEC) coded symbol mapping for data. b) Uncorrelated symbols in the transmitted symbol stream. ETSI ETSI TS 105 175-1-2 V1.1.1 ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 4.5 Data Interfaces | Several data interfaces can be implemented over the described PHY. The present document does not specify any interface. The present document assumes data transmitted through the data interface is packet oriented vs. continuous stream. On the other hand, there is no limitation on this aspect in the PHY description of th... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5 Coding Blocks (CMB) | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.1 CMB introduction | The CMB comprises two functions: CMB transmit and CMB receive. The CMB couples the data interface to the EO interface. The CMB is defined only in abstract terms and does not imply any particular implementation. Regardless of the implementation used, the optical specifications at the optical output described in clause 7... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2 CMB transmit function | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.1 Introduction to the CMB transmit function | The CMB transmit function maps the incoming data from the data interface onto PAM symbols that are sent to the THP precoder and to the power scaler. The transmission of data at the CMB is structured in frames. The CMB frames consist of pilots, a header and a payload that encodes the user data. All of them are of fixed ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.2 Frame structure | A frame comprises pilots, a header and a fixed payload of 225 792 symbols. The pilots and header are divided in sub- blocks and inserted in between the payload sub-blocks. Each header or pilot sub-block is composed of 160 symbols. For pilot and header sub-blocks, the first 16 symbols and the last 16 symbols take value ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3 Payload encoding | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.1 Introduction to payload encoding | The incoming data from the data interface is first encapsulated for transmission. Then the data is scrambled and mapped to PAM symbols using the MLCC technique. The parameters of the MLCC mapping depend on the speed and reach of the PHY. They are specified for each particular PHY in the corresponding annexes from A to ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.2 Data encapsulation | The incoming data is encapsulated using the two kinds of blocks illustrated in figure 6. The input data is segmented and encapsulated in blocks of 64 bits. One control bit is added at the beginning of each block to mark it as a control or data block. ETSI ETSI TS 105 175-1-2 V1.1.1 (2015-04) 15 Figure 6: Data encapsula... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.3 DCRC | The DCRC cyclic redundancy parity check bits for each data packet are generated using the following cyclic generator polynomial. 1+ x + x 3 + x 4 + x 7 + x 8 The DCRC implementation shall produce the same result as the implementation shown in figure 8. In figure 8, there are eight delay elements: S0 to S7. They shall b... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.4 CCRC | The CCRC cyclic redundancy parity check bits for PDB.CTRL are generated using the following cyclic generator polynomial. 1+ x + x 5 + x 6 + x 8 The CCRC implementation shall produce the same result as the implementation shown in figure 9. In figure 9 there are eight delay elements: S0 to S7. They shall be initialized t... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.5 Data packet encapsulation | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.5.1 Data packet transmit encapsulation | The physical layer device defined in the present document is able to optionally receive data packets from any generic data interface. Conditions in the PHY data interface Idle, Start, Terminate, Normal data transmission and Transmit Error propagation shall be considered by the PHY. The PHY shall propagate the Transmit ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.5.2 Rate matching | 5.2.3.5.2.1 Introduction to rate matching As defined in successive clauses, the PHYs defined in the present document and its annexes optionally support adaptive bit rate, being possible to have a PHY data rate greater or lower than the data interface. The PHY data rate shall depend on channel conditions and physical la... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.6 Binary Scrambler | The incoming data after encapsulation is scrambled using a Maximum Length Sequence (MLS) generator defined by the following polynomial 25 22 1 x x + + . The implementation shall produce the same result as the implementation in figure 12. The scrambler shall be initialized to 0x17C_9C58 (given in hexadecimal base repres... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7 Multi-Level Cosset Coding | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7.1 Introduction to Multi-Level Cosset Coding | The scrambled data is mapped to PAM symbols using the MLCC technique. The overall scheme is shown in figure 13. Depending on the configuration used by a particular PHY, the data bits are divided in up to three groups. The first group is coded with a (2 016, 1 664) BCH code. The second is coded with a (2 016, 1 994) or ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7.2 MLCC Demultiplexer | The MLCC encoder processes blocks of αMLCC bits. The size of the block depends on the particular configuration as shown in table 5. In the first step of processing those bits are divided into three MLCC levels. The number of bits assigned to each level are denoted as β(1), β(2) and β(3). Then for an input block x = [x0... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7.3 BCH Encoders | The sub-blocks y1 and y2 are encoded with BCH codes. For y1 the BCH encoding takes a 1 664 input block and shall generate a 2 016 bit code word c1. Prior to the BCH encoding 31 zeroes are added at the beginning of the input block. The resulting 1 695 bit block is then encoded. For both y1 and c1 the encoder shall follo... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7.4 Gray mapping | For each level, the nc (i) bits blocks are mapped to NMLCC / 2 = 1 008 two-dimensional symbols using a mapper. The mapper for the ith level (i = 1, 2 or 3) is defined in terms of the parameter kQAM (i) = 2 nb (i), where nb (i) is defined as the number of coded bits mapped per dimension. When kQAM is greater than one, t... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7.6 Lattice addition | After performing the first lattice transformations for each active level, the lattice transformed symbols from each of the three levels are added, performing the cosset partitioning over lattice Z2 and the final partitioning. In particular, the in- phase and the quadrature components from the three levels are added sep... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7.8 Mapping to PAM symbols | The in-phase and the quadrature components ) ( 2 a I t S Λ and ) ( 2 a Q t S Λ of the 2D symbols output from the second-step lattice transformation are then time domain multiplexed resulting in a sequence of 1D symbols belonging to a ⎡⎤ ξ 2 - PAM constellation. The multiplexing operation is illustrated in figure 23. A ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.3.7.9 Symbol scrambler | The PAM symbols are then scrambled to ensure that nonlinear distortion affects all PAM levels equally. Jointly with non-linear compensation that may be implemented by receiver, the symbol scrambler will provide the same symbol error probability for all the constellation points. The symbol scrambler is divided in two su... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4 Physical header encoding | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4.1 Introduction to physical header encoding | The header bits carry control information for the CMB. Those bits are arranged in a block of 720 bits as described in clause 5.2.4.2. The block is then encoded using a BCH code to obtain a block of 896 bits that are mapped to 1 792 PAM symbols with two levels. Then the symbols are divided in 14 groups of 128 and 16 zer... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4.2 Physical header data (PHD) | The Physical header data is divided in fields that are defined in table 6. The field PHD.TX.CODING.LEN specifies the code-word length of the MLCC, given in number of M-PAM symbols per MLCC code word. This configuration cannot change dynamically once the PHY has initiated the CMB transmission. This information shall be ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4.3 Physical Header CRC16 | The header is protected with a CRC16 cyclic redundancy parity check code. The CRC16 is described in figure 26. The 16 CRC bits are sent at the end of the 720 bits PHD block. The CRC16 shall be generated using the following generator polynomial: . The implementation shall produce the same result as that in figure 26. Th... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4.4 Physical Header scrambler | The header block is scrambled prior to transmission. The original bits are XORed with a pseudorandom sequence; this sequence shall be generated using a LFSR with polynomial: (MLS generator). The LFSR is initialized to a value of 0x0068_D332 at the beginning of the frame, where the left most digit corresponds to the ini... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4.5 Physical Header BCH encoding | A (896,720) BCH code is used to encode the header. The code is described by the generator polynomial G(x): 0x0001_A3E8_171D_BCA4_EE1E_7CDC_A7DA_FB8D_8F39_8072_8516_6007, being g(0) the rightmost bit. To obtain the parity bits, 1 151 zero bits are prepended to the 720 bits prior to the BCH encoding. The BCH encoder shal... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4.6 Physical Header mapping to PAM symbols | The incoming 896 bits are mapped into 1 792 2-PAM symbols. The mapping of BCH encoded bits in 2-PAM symbols based on a two-dimensional BPSK constellation is illustrated in figure 28. Figure 28: Physical Header PAM mapping |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.4.7 Physical Header Subframes (PHS) | The 1 792 symbols block is divided in 14 sub-blocks of 128 symbols each, denoted as Physical Header Subframe (PHS). Prior to transmission, 16 zero symbols are added at the beginning and the end of the PHS as it is illustrated in figure 29. Consecutive PHS blocks extended with zeroes are transmitted at the corresponding... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.5 Physical pilots encoding | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.5.1 Introduction to physical pilots | The pilot signals S1 and S2 carry information to aid the receiver initialization and continuous tracking. The S1 pilot signal is transmitted at the beginning of each frame as shown in figure 3 and is designed to facilitate frame and symbol synchronization. The S2 pilot signal is transmitted in sub-blocks that are distr... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.5.2 S1 pilot symbols generation | The S1 pilot signal is composed of 128 two level PAM symbols that are transmitted at the beginning of each frame. These symbols are generated after mapping a 128 bits sequence generated using a Linear Feedback Shift Register (LFSR). ETSI ETSI TS 105 175-1-2 V1.1.1 (2015-04) 35 The generator polynomial is . The implemen... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.5.3 S2 pilot symbols generation | The S2 pilot signal is composed of 1 664 symbols that are transmitted in 13 sub-blocks of 128 symbols each. The bits are generated using a Linear Feedback Shift Register (LFSR) and mapped to PAM symbols with 256 levels. A sequence of zero symbols is inserted at the beginning and end of each S2 pilot sub-block. The gene... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.6 Power scaling | Prior to transmission, the signal is scaled to ensure that the OMA is approximately the same across the entire frame. Power scaling for payload PAM symbols is implemented as illustrated in figure 34. 1+ x22 + x25 1+ x22 + x25 ETSI ETSI TS 105 175-1-2 V1.1.1 (2015-04) 36 Figure 34: Power scaling for PAM payload symbols ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.2.7 Tomlinson-Harashima Precoding (THP) | The PAM symbols to be transmitted, corresponding to the payload data of a frame, are precoded using THP as shown in figure 35. The coefficients b(i) are transmitted from the remote device in the Physical Header Data (PHD) of a previous frame as described in clause 5.2.4. The coefficient b(i) used for precoding correspo... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.3 CMB receive function | The CMB receive function shall map incoming PAM symbols from the EO interface. The CMB receive function shall indicate to the CMB the type of received PAM symbol by means of the CMB_DATATYPE.indication message. For CMB_DATATYPE.indication(PAYLOAD), the CMB receive function shall perform the symbol level descrambling, t... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.4 PHY Control function | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.4.1 Introduction to PHY control function | PHY Control function is in charge to enable the PHY for reliable communication with the link partner. PHY Control shall comply with the state diagram described by figure 36. PHY Control information is exchanged between link partners using bits contained in the physical headers of the frames. The format and use of those... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.4.2 Start up sequence | The start up sequence shall comply with the state diagram description given in figure 36. Upon power on, reset, or release from power down, the PHY shall carry out the clock recovery from the receive signal. The clock recovery is composed of two states. The first one is in charge of obtaining the symbol and frame synch... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.4.3 Continuous tracking sequences | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.4.3.1 Introduction to tracking functions | Upon the link_status being asserted OK, both PHY link partners are able for reliable transmission. Further, both link partners are able to properly use the PHD to carry out continuous adaptation of THP coefficients as well as to optionally implement continuous adaptive bit rate (ABR). The state diagrams defined in the ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.4.3.2 THP coefficients adaptation sequence | Figure 37 provides the state diagram that shall be implemented by a PHY to adapt the THP coefficients of the CMB Transmit function in response to the requests performed by the link partner. A PHY shall always announce the THP set-id in the previous frame to the one in which the THP coefficients according with the set-i... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.4.3.3 Adaptive Bit Rate sequence | Figure 39 provides the state diagram that shall be implemented by a PHY supporting Adaptive Bit Rate (ABR) to adapt the CMB Transmit function according to the requests performed by the link partner to change the MLCC encoder spectral efficiency. CMB Transmit function shall always announce the new MLCC spectral efficien... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.5 Link Monitor function | Link Monitor function uses the receive channel status of the local and remote PHYs to establish the status of the link and informs it via the link_status variable. When there is a failure of link the CMB stops normal operation. The Link Monitor function shall comply with the state diagram of figure 41. Upon power on, r... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.6 Clock Recovery function | The Clock Recovery function shall provide a clock suitable for signal sampling on the receiver so that the block error rate (PDB-ER) indicated in clause 5.3 is achieved. The received clock signal should be stable and ready for use when equalizer training is performed during start-up sequence and when it has been comple... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.7 Interface to the EO | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.7.1 Introduction to the EO interface | The interface between the CMB and the EO is defined in terms of signals for which no specific implementation is described. |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.7.2 Signals transmitted to the EO interface | Depending on the CMB_DATATYPE.request message the signals transmitted to the EO transmit are different each symbol time. However, all of them can be expressed in a general form as follows: x(n) = SF(n)× FM (a(n)− x(n −i −1)×b(i) i=0 Nb∑ ) ⎛ ⎝ ⎜ ⎞ ⎠ ⎟= SF(n)× a(n)+ 2M × m(n)− x(n −i −1)× b(i) i=0 Nb∑ ⎛ ⎝ ⎜ ⎞ ⎠ ⎟ ETSI ET... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 5.7.3 Signals received from EO | Signals received from the EO can be expressed as pulse-amplitude modulated signals that have been filtered by a non- linear channel and corrupted by noise as follows: ) ( ) ( ) ( ) ( ) , , ( ) ( ) ( ) , ( ) ( ) ( ) ( 0 0 0 2 1 2 1 0 0 2 1 2 1 2 0 1 1 1 0 1 2 1 2 1 n N l n x l n x l n x l l l w l n x l n x l l w l n x l... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6 PHY service messages and interfaces | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.1 Introduction to service interfaces | PHY transfers data and control messages across the following three service interfaces: a) Data Interface. b) CMB Service Interface. c) Connector Interface (Conn). |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.2 Data Interface | Data interface transmits and receives data to be transmitted and is being received. This interface is with external PHY components. The format and description of this interface is out of scope of the present document. Data interface may be different depending of the type of data to be transmitted by the PHY. |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.3 Monitor Interface | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.3.1 Message description | The following service messages are used by the PHY to exchange control and status signals across the Monitor Interface. {−M +1,−M + 3,L, M −3, M −1} FM (α) = mod(α + M,2M) −M −M ≤x(n) < M ETSI ETSI TS 105 175-1-2 V1.1.1 (2015-04) 45 |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.3.2 CMB_LINK.indication | The CMB generates this message showing the link status of the lower levels. This message is used mainly by the CMB PHY Control function. The possible values of the message are: CMB_LINK.indication (link_status) = FAIL, or OK. FAIL: Failed to establish a reliable link. • OK: A reliable link is established The CMB genera... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4 CMB Service Interface | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4.1 CMB service messages | PHY uses the following service messages to exchange symbols, status indications, and control signals across the service interfaces: • CMB_UNITDATA.request(tx_symb) • CMB_UNITDATA.indication(rx_symb) • CMB_DATATYPE.request(tx_type) • CMB_DATATYPE.indication(rx_type) • CMB_RXSTATUS.indication(loc_rcvr_status) • CMB_REMRX... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4.2 CMB_UNITDATA.request | CMB uses this message to transfer data in the form of PAM symbols (tx_symb). The PAM symbols are obtained in the CMB Transmit function using the coding rules defined in clause 5.2 for each of the frame data types indicated by tx_type parameter. The meaning of the message is: CMB_UNITDATA.request(tx_symb). During transm... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4.3 CMB_UNITDATA.indication | This message is used in the CMB Receive functions and defines the data to be transfer in the form of recovered PAM symbols to the CMB decoding blocks. The format of the message is: CMB_UNITDATA.indication(rx_symb). During reception, this message conveys to the CMB via the parameter rx_symb the value of PAM symbol recov... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4.4 CMB_DATATYPE.request | This message defines the type of data (tx_type) transferred in the form of PAM symbols from the CMB. The format of the message is: CMB_DATATYPE.request(tx_type). During transmission, this message conveys to the CMB via the parameter tx_type the type of PAM symbol to be sent over the optical link. The set of values that... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4.5 CMB_DATATYPE.indication | This message defines the type of data (rx_type) transferred in the form of PAM symbols. The format of this message is: CMB_DATATYPE.indication(rx_type). During reception, this message tells the CMB receive function the parameter rx_type the type of PAM symbol recovered from optical link. The set of values that this par... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4.6 CMB_RXSTATUS.indication | CMB Receive generates this message when there is a change in the status of the receive link. The information indicated by this message is the loc_rcvr_status parameter, which is sent to the CMB Transmit and Receive, the CMB PHY Control function, and the Link Monitor indicating the status of the receive link. How the lo... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.4.7 CMB_REMRXSTATUS.request | Local CMB Receive generates this message to indicate the remote PHY about the receive link status. The Local CMB Receive uses the loc_rcvr_status parameter to inform the remote PHY. When the loc_rcvr_status parameter is sent to the remote CMB, the parameter is redefined as rem_rcvr_status. The CMB PHY Control function ... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.5 EO service interface | |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.5.1 EO service messages | PHY uses the following service messages to exchange communication and control signals across the EO service interfaces. EO interface is described in an abstract manner and does not imply any particular implementation. The EO Service Interface supports the exchange of analogue electrical signals between CMB entities. Th... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.5.2 EO_UNITDATA.request | This message defines the transfer of data in the form of analogue signal from the CMB to the EO interface. The format of the message is EO_UNITDATA.request(tx_signal). During transmission, this message conveys to the EO via the parameter tx_signal the value of the discrete time analogue electrical signal to be converte... |
65f6ec82a1f2dba7e17c26a7e3a90b4f | 105 175-1-2 | 6.5.3 EO_UNITDATA.indication | This message defines the transfer of data in the form of continuous analogue electrical signal from the EO to the CMB. The format of the message is EO_UNITDATA.indication(rx_signal). During reception, this message conveys to the CMB via the parameter rx_signal the value of received signal converted by EO interface from... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.