hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.1.2 GSE transmitter processing | When sending a higher layer PDU, the hub puts the complete MAC24 address into a 3-byte label of the GSE- encapsulated PDU (label type 1). For unicast packets, this is the MAC24 address assigned to the corresponding SVN of the destination terminal, for multicast packets this is a multicast MAC24 address created via the selected multicast addressing method. Layer 2 M&C messages are labelled with either the MAC48 of the terminal address, if they are unicast (label type 0), or with no label, if they are broadcast (label type 2). |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.1.3 GSE receiver processing | After reassembly and decapsulation, the receiver filters the packets as follows: • If there is a 6-byte label and this matches a MAC48 assigned to the terminal and the protocol type is L2 M&C signalling, the packet is accepted and forwarded to the signalling handling function. • If there is no label and the protocol type is L2 M&C signalling, the packet is accepted and forwarded to the signalling handling. • If there is a three byte label and it matches one of the MAC24 addresses assigned to the satellite-side interfaces of the terminal, the packet is accepted. The SVN-number is extracted from the address by appropriate masking, extended to 16-bit by adding zero bits at the LSB (if necessary) and forwarded to the higher layer functions together with the corresponding SVN. • If the packet is associated with SVN 0, then the packet is passed to the HLS management function. • Otherwise the packet is dropped. Note that the filtering is conceptually performed after reassembly and decapsulation. It is possible to do the filtering before these steps by applying a cache technique to map fragment ids to labels. This is expected to have the same forwarding behaviour. An example of the forwarding to higher layers follows. Given that the MAC24 assignments in Figure 8.2 the processing shown in Table 8.1 takes place. Table 8.1: RLE receiver processing of labels Label on GSE packet SVN SVN passed to HLS 00000000 00000000 00010001 00000000 00000000 00000000 00000000 00000001 00000000 01010101 00000001 00000001 00000000 00000010 00010001 00000011 00000010 0001 00000010 00010000 11110001 00000001 00000011 1111 11110000 00000000 ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 63 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.1.4 RLE transmitter processing | The following processing takes place on the terminal sender side: • If the higher layer packet is a L2 M&C signalling packet, label type 3 is used and the packet is encapsulated with suppressed protocol type. • If the packet is another higher layer PDU, its SVN number is compared to the SVN numbers of the MAC24 addresses assigned to the terminal (the SVN prefixes padded to 16 bit with zero bytes at the LSB). - If there is no match between the SVN number of the higher layer PDU and the SVN numbers of the MAC24 addresses assigned to the terminal, the packet is dropped. - The matched SVN is compared to the default SVN signalled by the hub. If these match the PDU is encapsulated with label type 2 and no label. - If the SVN does not match the default SVN, the PDU is encapsulated using label type 0 and the most significant 8 bits of the MAC24 address are placed in the 1 byte ALPDU label. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.1.5 RLE receiver processing | The following processing takes place at the hub receiver after reassembly and decapsulation: • If a packet arrives with label type 3 and a protocol type of L2 M&C signalling, it is passed to the signalling entity in the hub with the terminal id attached. • If the packet arrives with no label, the default SVN (in extended form 16-bit) is attached to the PDU and the PDU together with the SVN number are passed to the higher layers. • If the packet arrived with one byte label, the MAC24 address assigned to the terminal is searched which has the label byte as its most significant byte. - If there is no match, the PDU is dropped. This event should be logged as it is a symptom of misconfiguration. - If there is a match, the PDU and the SVN number (in extended form of 16-bit) are passed to the higher layers. 8.2 Recommendations for VLAN support and Satellite Virtual Networks In this clause, usage examples of VLAN and SVN are described. The 3B VLAN (IEEE 802.1pQ [i.72]) tag contains three fields: a Priority Code Point, PCP (3 bits), a Canonical Format Indicator, CFI (1bit) and a VLAN identifier, VLAN_ID (12 bits). Ethernet frames that are received at a VLAN-enabled LAN interface at the GW or RCST may contain an IEEE 802.1pQ [i.72] tag or may be untagged. Untagged frames received at a VLAN-enabled LAN interface should be associated with a default VLAN_ID. In the rest of this clause, a "LAN interface" always refers to a VLAN-enabled LAN interface. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 64 VLAN and SVN support in DVB-RCS2 systems may be realized by two methods: a) In this method, each VLAN tag, which is associated with a LAN interface, is mapped to a specific MAC24 address. When an Ethernet frame is received with a given VLAN tag, the tag is removed, and the frame is mapped to a specific MAC24 address. This requires an explicit configuration of the VLAN_ID used at the ingress and egress LAN interfaces. The egress interface may use an untagged format or add an 802.1pQ [i.72] tag. If 802.1pQ tags are used at the egress LAN interface the VLAN PCP should also configured for this interface, since there is no PCP value in an untagged Ethernet frame In this case, the Ethernet PCP may be mapped from the IP DSCP. Thus configuration is needed to assign the traffic to VLANs and set the PCP codepoint (e.g. static configuration via the management plane, or a dynamic method using the control plane). b) Forwarding of an IP packet with an IEEE 802.1pQ [i.72] tag from/to an RCST that operates as a router. In this method, the RCST operates as a router, and it forwards IP packets with their IEEE 802.1pQ tags. In this case, a SVN interface may be configured so that RLE/GSE headers carry the value of the VLAN-ID as a tag. Multiple VLANs are implicitly identified by the encapsulation tag value and may use the same MAC24. This mode still requires configuring the VLAN-PCP at the egress LAN interface for the 802.1pQ tag. In method (a), the RCST LAN interface should be configured with a corresponding MAC24 address for each VLAN-ID that is supported. The Gateway should also be configured with a corresponding VLAN-ID or a separate interface for each VLAN. The RCST and Gateway VLAN-IDs for the same VLAN may be different. The possibility of maintaining different VLAN_IDs at RCST and GW LAN interfaces for the same VLAN enables the Gateway operator to separate traffic that is carried using the same VLAN-ID at two RCSTs, but where this value is intended to identify two independent networks. Frames with a VLAN-ID value that has not been configured, should be dropped at the ingress interface. In method (b), the RCST LAN interface is configured with the set of VLAN-ID it supports. In this method, a single MAC24 address may be used to forward more than one VLAN-IDs over the satellite interface. In this method, the Gateway operator should either enforce a policy on the use of VLAN-IDs at RCSTs (ensuring that each VLAN-ID identifies only one satellite VLAN), or use a separate interface for each separately managed set of VLANs. This follows normal practice for Ethernet-based VLANs. A VRF group may also be used for this purpose, since each VRF group is presented on a separate interface at the Gateway. If VLAN support is realized through method b), GSE/RLE encapsulation, clause 8.6.21 "VLAN configuration group" of the RCS2 specification [i.1] indicates that the following MIB table entries are needed: • A management parameter describing if an RCST is capable of supporting method-(b). • A management parameter for the NCC to control a specific LAN interface of the RCST. If the RCST enables VLAN method (b), the following MIB table entries need to be configured, for the LAN interface: • A set of allowed VLAN_IDs. The frames corresponding to the configured VLAN-IDs are mapped to the corresponding SVN. A default interface may be configured to forward frames received with a VLAN_ID not specified in this set of allowed VLAN-IDs. • A maximum Priority Code Point (PCP) value. A higher value indicated in the VLAN tag will be truncated to this value. This rule may be used to enforce operator-controlled use of the PCP values, for example to reserve the highest values for specific groups of customers or specific applications. Method (a) is the method used in a routed IP network. Method (b) extends the concept of a VLAN across the satellite network, forming a hybrid of a L2/L3 network that allows coordination of the VLAN-ID values used over the networks connected via the RCSTs. It is common for ISPs to offer a single LAN interface to the subscriber LAN. VLAN services to individual subscribers are not common. It is expected that multi-VLAN support at the LAN interface of the ST will be attractive where isolation between different LAN users is needed. Thus, the VLANs may be terminated at the RCST using IP routing over the satellite air interface, or extended across the satellite network using either method (a) or (b) to assign the VLAN_ID. From the point of view of the connectivity, transparent and regenerative architectures may be enabled. Examples of VLAN usage are described in the following clauses. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 65 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.1 Consumer/SOHO scenario | Consumer networking equipments usually do not support VLANs. It is common for ISPs to offer a single LAN interface to the subscriber LAN. VLAN services to individual subscribers are not common and are not required in this scenario. A RCST will likely be a part of only one traffic SVN. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.2 Corporate/Institutional (including Military) scenario | Corporate and Governmental networks frequently use VLANs to segregate traffic between user communities and often employ IP routing to connect VLAN-enabled LANs. VLAN support is therefore expected for this scenario, where the RCST may be part of one or more traffic SVNs. A range of configuration examples is given below. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.2.1 Configuration example 1 | Figure 8.3 shows example 1, the case of two RCSTs that belong to the same traffic SVN (SVN-1) with each RCST supporting one VLAN (VLAN-1). The LAN interfaces at each of the RCSTs should be configured to associate the traffic with the same VLAN_ID. The SVN for management (SVN-0) is also shown, as well as its respective VRF group (VRF-0). Figure 8.3: Example 1 - Two RCSTs in one SVN; each RCST supports one VLAN An example of a lookup table configured by the INAP/SVNO, when method a) is supported, for the topology of Figure 8.3 is shown in Table 8.2. An SVN_MASK length of 8 bits (e.g. 255 SVNs can be supported by the OVN) is considered, although other sizes are also applicable. In the topology of Figure 8.3, Ethernet frames (with no tag) from VLAN-1 of RCST-1 will be forwarded through the LAN interface 1, associated momentarily in the RCST with VLAN_ID 1 and, will then be assigned an MAC24 label of 0x1000A1 corresponding to SVN-1. Then, in this example, the LAN supported by RCST1 does not use VLAN tags (i.e. frames with IEEE 802.1pQ [i.72] tags). Tagged packets arriving to RCST1 will be dropped. In contrast, the LAN at RCST2 has been configured with VLAN support. Tagged frames with a VLAN_ID of 1 that are received by RCST2 will be assigned a MAC24 label of 0x1000B1 corresponding to SVN-1, and will be forward via the satellite (with prior removal of their 802.1pQ tag). Untagged packets arriving at the LAN interface of RCST2 will be dropped. All the traffic is carried in one VRF group, and hence could be presented at the Gateway using an interface with 802.1pQ to identify each VLAN. Packets received by the Gateway that correspond with SVN-1 will be mapped to the configured VLAN for the SVN, before being forwarded to the Gateway LAN interface. In this case, they are mapped to VLAN-1 (any other VLAN_ID may be mapped, including an untagged value). In this case, SVN-0 is mapped to a separate interface port for management data, because it belongs to a separate VRF group. The use of a separate VRF Group means that the addresses and any created VLANs in a single VRF Group are completely independent of any in other VRF Groups. (Hence, VLAN_ID 1 in VRF-0 (the management VRF Group) is entirely independent of VLAN_ID 1 in VRF-1 (the first traffic VRF Group). ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 66 SVN-1 is mapped to VLAN_ID 1 for traffic. RCST1 uses a non-tagged format at its LAN Interface, whereas RCST chooses to encapsulate the traffic sent on the LAN Interface using VLAN-tagging. In both cases the RCSTs will associate the traffic with VLAN_ID 1. Thus, this is an example of SVN/VLAN support using method (a), i.e. no implicit coordination of VLAN_IDs between the LAN interfaces of the STs and the Gateway. Table 8.2: Example of VLAN mapping to support SVN/VLAN using method a) for Figure 8.3 (default = with no tag on the Ethernet LAN interface; tagged = with a 802.1pQ tag) MAC24 VLAN_ID Interface Gateway SVN-0: 0x000001/8 SVN-1: 0x100081/8 VRF-0/VLAN-1 VRF-1/VLAN-1 LAN 0 (Mgmt) LAN 1, VLAN-1 RCST1 SVN-0: 0x000002/8 SVN-1: 0x1000A1/8 VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1,default RCST2 SVN-0: 0x000003/8 SVN-1: 0x1000B1/8 VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1, VLAN-1 Table 8.3 shows an example configuration with support of VLANs using method b). Untagged frames, received at RCST-1, will be tagged with a default VLAN_ID of VLAN-1 and the MAC24 of 0x1000A1. If their PCP field is lower or equal to 5, there will be no change to this value; otherwise the RCST will modify the PCP value reducing it to 5. For RCST2, tagged frames will be also tagged with the VLAN_ID of VLAN-1 but will use a MAC24 of 0x1000B1. The maximum PCP value for the traffic of this may be different, and in this case is 4. Note that a single SVN could be used to support multiple VLANs. Table 8.3: Example of VLAN mapping to support SVN/VLAN using method-b) (default = without tag on Ethernet LAN interface; tagged = with a 802.1pQ tag) MAC24 VLAN_ID Interface PCP Gateway SVN-0: 0x000001/8 SVN-1: 0x100081/8, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 LAN 0 (Mgmt), default LAN 1 7 7 RCST1 SVN-0: 0x000002/8 SVN-1: 0x1000A1/8, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1,default 7 5 RCST2 SVN-0: 0x000003/8 SVN-1: 0x1000B1/8, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1, VLAN-1 7 4 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.2.2 Configuration example 2 | Figure 8.4 shows configuration example 2, where two RCSTs belong to the same SVN (SVN-1). RCST1 supports three VLANs (VLAN-1, VLAN-2, VLAN-4) while RCST2 supports one VLAN (VLAN-1). An example configuration of the VLAN mapping is shown for this topology in Tables 8.4 and 8.5. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 67 Figure 8.4: Example 2: Two STs in one SVN; RCST1 supports three VLANs and RCST2 supports one VLAN In this example, Table 8.4 shows that the SVN_MASK of SVN-1 has a length of 12 bits, which allow the support of up to 4 095 SVNs. If VLAN support is realized using method a), Table 8.4 shows an example configuration table. In this case, all tagged frames received at RCST1 from VLAN-2 and VLAN-4 will be encapsulated with a MAC24 of 0x1000A2 and 0x1000A3, respectively, in SVN-1 (prior removal of their tags). For untagged frames from VLAN-1, the MAC24 label of 0x1000A1 will be used. NOTE: The RCST should discard any traffic that uses a VLAN_ID (or untagged default format) that is not explicitly listed in the table. In this case, the table does not configure RCST1 to support tagged frames with a VLAN_ID of 1, neither does it permit untagged frames to be forwarded by RCST2. For RCST2, untagged frames will have a MAC24 of 0x1000B1 while tagged frames will be dropped. Table 8.4: Example of VLAN mapping to support SVN/VLAN using method a) for Figure 8.4 (default = with no tag on the Ethernet LAN interface; tagged = with a 802.1pQ tag) MAC24 VLAN_ID Interface Gateway SVN-0: 0x00000F/12 SVN-1: 0x100081/12 SVN-2: 0x100082/12 SVN-4: 0x100083/12 VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-1/VLAN-2 VRF-1/VLAN-4 LAN 0 (Mgmt) LAN 1, VLAN-1 LAN 1, VLAN-2 LAN 1, VLAN-4 RCST1 SVN-0: 0x000001/12 SVN-1: 0x1000A1/12 SVN-1: 0x1000A2/12 SVN-1: 0x1000A3/12 VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-1/VLAN-2 VRF-1/VLAN-4 Internal (Mgmt) LAN 1, default LAN 1, VLAN-2 LAN 1, VLAN-4 RCST2 SVN-0: 0x000002/12 SVN-1: 0x1000B1/12 VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1, default An example VLAN mapping to support of SVN/VLAN through method b) is shown in Table 8.5. This indicates that all tagged frames received at RCST1 from VLAN-2 and VLAN-4 will be encapsulated with a MAC24 of 0x1000A1 in SVN-1. If their PCP field is lower or equal to 7 and 5, respectively, there will be no changes to this value; otherwise the ST will set the PCP value to 4.Untagged frames will be tagged with a default VLAN_ID of VLAN-1 and, also, the MAC24 of 0x1000A1. This use makes an untagged frame equivalent to one with a VLAN_ID of VLAN-1 (although the current configuration does not expose this internal VLAN_ID on any LAN Interface. If their PCP field is lower or equal to 4, there will be no changes to this value; otherwise the ST will set the PCP value to 4. For RCST2, untagged frames will be also tagged with the VLAN_ID of VLAN-1 but a MAC24 of 0x1000B1 and, a maximum PCP of 4. The Gateway is assumed to support 2 interfaces (0 and 1), used respectively for management and traffic, necessary because these use different VRF groups. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 68 Table 8.5: Example of VLAN mapping for Figure 8.4 for VLAN support (default = with no tag on LAN interface; tagged = with a 802.1pQ tag) MAC24 VLAN_ID Interface PCP Gateway SVN-0: 0x00000F/12 SVN-1: 0x100081/12, tagged SVN-2: 0x100082/12, tagged SVN-4: 0x100083/12, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-1/VLAN-2 VRF-1/VLAN-4 LAN 0 (Mgmt), default LAN 1 LAN 1 LAN 1 7 7 7 7 RCST1 SVN-0: 0x000001/12 SVN-1: 0x1000A1/12, tagged SVN-1: 0x1000A1/12, tagged SVN-1: 0x1000A1/12, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-1/VLAN-2 VRF-1/VLAN-4 Internal (Mgmt) LAN 1,default LAN 1, VLAN-2 LAN 1, VLAN-4 7 4 7 5 RCST2 SVN-0: 0x000002/12 SVN-1: 0x1000B1/12, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1,default 4 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.2.3 Configuration example 3 | Figure 8.5 shows the case of two STs that each belong to a different SVN, SVN-1 and SVN-2 and each supporting one VLAN (VLAN-1 and VLAN-2, respectively). Figure 8.5: Example 3: Two STs, each in one SVN and supporting one VLAN, respectively Table 8.6 shows an example VLAN Mapping for this topology using method a). In this case, the SVN_MASK has a length of 8 bits, which allows the support of up to 256 SVNs. Each ST appends a MAC24 corresponding to its VLAN_ID: 0x1000A1 for VLAN-1 (RCST1) and 0x1000B2 for VLAN-2 (RCST-2). Any tagged frame arriving at an RCST will be dropped, because frames with any unassigned VLAN_ID cannot be forwarded (including the default in this case). The Gateway uses a dedicated interface for management (0) and two traffic interfaces (1 and 2), since the traffic has been segregated into VRF groups. The Gateway interface 1 and 2 in this case enable the use of VLANs. (Since there is only one VLAN on each interface in this example this VLAN could have been mapped to a default interface with no VLAN tag). ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 69 Table 8.6: Example of VLAN mapping for Figure 8.5 for VLAN support method a) (default = without tag on Ethernet LAN interface) MAC24 VLAN_ID Interface Gateway SVN-0: 0x00000F/8 SVN-1: 0x100081/8 SVN-2: 0x100082/8 VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/VLAN-2 0 (Mgmt), default 1 VLAN-1 2 VLAN-2 RCST1 SVN-0: 0x000001/8 SVN-1: 0x1000A1/8 VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1,default RCST2 SVN-0: 0x000002/8 SVN-2: 0x1000B2/8 VRF-0/VLAN-1 VRF-2/VLAN-2 Internal (Mgmt) LAN 1, default Table 8.7 shows an example VLAN Mapping for this topology using method b). Each ST appends a MAC24 corresponding to its VLAN_ID: 0x1000A1 for VLAN-1 in SVN-1 (RCST1) and, 0x1000B1 for VLAN-2 in SVN-2 (RCST-2). The maximum PCP for the IEEE 802.1pQ [i.72] tag of packets arriving to RCST1 and RCST2 will set to 6 and 5, respectively. RCST2 has been configured to transport any VLAN-ID that arrives at the LAN interface, carried within VRF-2. This utilizes the ability of method (b) to transport a VLAN_ID across the satellite link. Table 8.7: Example of VLAN mapping for Figure 8.5 for VLAN support method b) (default = with no tag on Ethernet LAN interface; tagged = with a 802.1pQ tag) MAC24 VLAN_ID Interface PCP Gateway SVN-0: 0x00000F/8 SVN-1: 0x100081/8, tagged SVN-2: 0x100082/8, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/any 0 (Mgmt), default 1, tagged 2, tagged 7 7 7 RCST1 SVN-0: 0x000001/8 SVN-1: 0x1000A1/8, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 Internal (Mgmt) LAN 1,tagged 7 6 RCST2 SVN-0: 0x000002/8 SVN-2 0x1000B1/8, tagged VRF-0/VLAN-2 VRF-2/any Internal (Mgmt) LAN 1,tagged 5 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.2.4 Configuration example 4 | Figure 8.6 shows a configuration example 4, where RCST1 supports two SVNs (SVN-1 and SVN-2) and two VLANs (VLAN-1, and VLAN-2). An example VLAN Mapping for this topology using method (a) and (b) to support VLANs is shown in Tables 8.8 and 8.9, respectively. Figure 8.6: Example 4: One ST supporting two SVNs and two VLANs ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 70 Table 8.8 shows an example VLAN Mapping for this topology using method a). In this case, the SVN_MASK has a length of 10 bits, which allows the support of up to 1 023 SVNs. The ST uses a MAC24 label of 0x1000A1 to untagged packets (VLAN-1) while tagged packets are sent with a MAC24 of 0x1000A2 (VLAN-2). The Gateway uses a dedicated interface for management (0) and a tagged interface for the VLANs (1). In this case, the RCST VLANs are mapped to new values at the egress interface 1 of the Gateway (e.g. SVN-1 to VLAN-4 and SVN-2 to VLAN-5), to allow the operator to differentiate this traffic from other VLANs configured within the network. This flexibility allowing remapping is common when VLANs are used. Table 8.8: Example of VLAN mapping to support SVN/VLAN using method a) for Figure 8.6 (default = with no tag on Ethernet LAN interface; tagged = with a 802.1pQ tag) MAC24 VLAN_ID Interface Gateway SVN-0: 0x0000F/10 SVN-1: 0x100081/10 SVN-2: 0x100082/10 VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/VLAN-2 0 (Mgmt), default 1, VLAN-4 1, VLAN-5 RCST1 SVN-0: 0x000001/10 SVN-1: 0x1000A1/10 SVN-2: 0x1000A2/10 VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/VLAN-2 Internal (Mgmt) LAN 1,default LAN 1,tagged An example VLAN mapping using method b) is shown in Table 8.9. In this example, untagged frames, arriving to RCST1, are given a VLAN_ID of 1 and a maximum PCP of 3, corresponding to an MAC24 of 0x1000A1; while tagged frames will have a maximum PCP of 7 and a MAC24 of 0x1000A2. Table 8.9: Example of VLAN mapping to support SVN/VLAN using method b) for Figure 8.6 (default = without tag on Ethernet LAN interface; tagged = with a 802.1pQ tag) MAC24 VLAN_ID Interface PCP Gateway SVN-0: 0x00000F/10 SVN-1: 0x100081/10, tagged SVN-2: 0x100082/10, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/VLAN-2 0 (Mgmt), default 1, tagged 2, tagged 7 7 7 RCST1 SVN-0: 0x000001/10 SVN-1: 0x1000A1/10, tagged SVN-2: 0x1000A2/10, tagged VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/VLAN-2 Internal (Mgmt) LAN 1,default LAN1, tagged 3 7 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.3 Multi-dwelling scenario | It is expected that multi-VLAN support at the LAN interface of the RCST will be attractive for multi-dwelling users. In this scenario, two or more subscribers share a terminal, but not necessarily the same QoS services. Each subscriber may use a different VLAN, mapped to a different SVN. The presence of VLANs can provide isolation between different users (locations) connected to the multi-dwelling RCST LAN interface, (e.g. to support a VLAN switch including the ability to support additional untagged interface ports). Multiple SVNs may be managed by the SVNO. A use-case may support two sets of users via a single RCST, offering an independently managed SLA to each. At the RCST, both users are supported on a single LAN interface, through the use of dedicated VLANs. In this example, one uses an untagged VLAN and the second uses a tagged VLAN with a dedicated VLAN_ID value. The RCST may be connected to an external Ethernet switch that provides a dedicated (untagged) interface to the second user. For this case, method a) is implemented: all frames arriving at the RCST are tagged. Table 8.10 shows an example VLAN Mapping for this topology. In this case, the SVN_MASK has a length of 10 bits, which allow the support of up to 1 023 SVNs. The RCST appends a SVN_MASK label of 0x1000A1(SVN-1) to packets with IP addresses corresponding to the VRF-1 group while packets are sent with a MAC24 of 0x1000A2 (SVN-2) if their IP addresses are from the VRF-2 group. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 71 Table 8.10: Example of VLAN mapping for SVN/VLAN support in multi-dwelling scenarios (default = with no tag on LAN interface) MAC24 VLAN_ID Interface Gateway SVN-0: 0x00000F/10 SVN-1: 0x100081/10 SVN-2:: 0x100082/10 VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/VLAN-2 0 (Mgmt), default 1, default RCST1 SVN-0: 0x000001/10 SVN-1: 0x1000A1/10 SVN-2: 0x1000A2/10 VRF-0/VLAN-1 VRF-1/VLAN-1 VRF-2/VLAN-2 Internal (Mgmt) LAN 1,default LAN 2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.4 SCADA scenario | This scenario will not typically support VLANs. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.2.5 Backhauling scenario | For the backhauling scenario, VLAN support is not required and, usually, one SVN will be configured. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.3 Recommendations for VLAN management | Some recommendations are provided in this clause for management of VLANs in interactive DVB-RCS2 networks. The proposal is based on the current MIB objects existing in [i.1]. However, a new table is needed in the MIB for mapping user VLANs and satellite SVNs. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 8.3.1 Specifications of MIB objects | In the interfaces group of RCS2 MIB, there is an association of each interface with an MAC24 (parameter ifPhysAddress). One or several Ethernet interfaces may be used in the LAN of a RCST, each having its corresponding MAC24. Moreover, the same physical interface could correspond to several virtual (VLAN) interfaces. In the dvbRcs2NetworkConfig group, the NetworkConfigTable associates each interface with its L3 network address. It supports the management interface and also the user interfaces. Note that every interface can be assigned an IPv4 or IPv6 address type. Parameter NetworkConfigLANInetAddressIfIndex is a link to the interfaces group table, therefore this table allows to configure all the virtual interfaces. Table 8.11 is a new table that may be used to add VLAN support in the RCST. The objective of this table is to establish how to forward the VLAN frames received in the user interface. To achieve this, it is needed to map user VLAN and satellite SVNs (through the MAC24 address associated to each interface). ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 72 Table 8.11: RCST MIB objects for VLAN mapping Element Type Description VLANmode INTEGER 0: Default mode. For packets in the ingress LAN interface, the RCST should remove the VLAN tag and encapsulate IP packets (when needed, depending on context) using a MAC24 with an SVN Mask derived from VlanSvnMac parameter in this table. For packets in the egress interface, the RCST should tag the frame using the VLAN_ID associated to the MAC24 interface that has received the packet. Not tagging the frame for certain SVN interfaces is also possible, when VlanId = 0. 1: For packets in the ingress LAN interface, forward the IEEE 802.1pQ [i.72] tag through the satellite interface associated with the MAC24 address taken from the VLANMappingTable. Several or all of the VLAN_ID may be mapped to a single traffic MAC24 interface. For packets received from the satellite interfaces, forward the received 802.1Q frames to the egress LAN interface. VLANMappingTable SEQUENCE OF VLANMappingTable ENTRY Table that associates each VLAN_ID with an interface and set its properties. VLANMappingTableEntry SEQUENCE OF { VlanInterfaceIndex, VlanId, VlanSvnMac, VlanPcp, VlanRowStatus} VlanInterfaceIndex INTEGER ST Interface number, that links to the interfaces group ifNumber. VlanId INTEGER Corresponds to the 12-bit tag of a IEEE 802.1pQ [i.72] frame. VlanMAC24 OCTET STRING The only possible values for this parameter are the values populated in L3VirtualRoutingForwardingConfig group, obtained during RCST logon. For outgoing frames, this parameter is the MAC24 address of the satellite interface that will be used when the Ethernet frame comes with VLAN_ID equal to VlanId value of the same row. Untagged frames can also be mapped to a certain MAC24. For packets from the Satellite (egress interface), the VLAN_ID to be tagged by the RCST will depend on the MAC24 of the received PPDU frame. The SVN Mask of the received frame is used to infer the VLAN_ID tag. VlanPcp Maximum priority code point. A higher value of the PCP in the IEEE 802.1pQ [i.72] frame will be decremented to this value. Applicable for VLANmode = 1. This value is used by the ST QoS model for the PHB association with the VLAN. VlanRowStatus Row Status The row status, used according to row creation and removal conventions. A row entry cannot be modified when the status is marked as active(1). A row can be created either by createAndGo and automatically change to active state or createAndWait to add more parameters before becoming active. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 73 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 9 PEP session negotiation protocol | |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 9.1 State definitions | The following states (illustrated in Figures 9.1 and 9.2) are relevant in the context of PEP Session Negotiation: Off/Standby: This is the normal state immediately following power-on initialization, as well as a default state to which the RCST returns in some situations following loss of synchronization or upon being logged off. It is an implementation choice whether this state is absorbing; i.e. whether any external stimulus is required in order to initiate the processes that may cause a transition away from this state. The forward link should be kept operational in this state. When entering the Off/Standby state, the RCST should immediately cease transmission. It may keep dynamic identifiers if specifically allowed to do so as indicated for the assignment. The RCST should not transmit while in the Off/Standby state. Hold/Standby: When entering the Hold/Standby state, the RCST should immediately cease transmission. It may keep dynamic identifiers if specifically allowed to do so as indicated for the assignment. An RCST in the Hold/Standby state should remain there following restart and power cycling events until the NCC releases the conditions(s) that keep the RCST in the Hold/Standby state. The forward link should be kept operational in this state. The RCST should not transmit while in the Hold/Standby state. Ready for Logon: The RCST enters this state when the forward link has been successfully acquired and the configuration data required for issuing logon is up to date. It is an implementation choice whether this state is absorbing; i.e. whether any external stimulus is required to initiate the processes that may cause a transition away from this state. External triggers may include for example arrival of data on the terrestrial interface or reception of a "wake- up" message in the TIM-U. Transmission of logon bursts is allowed when the RCST is in this state. PEP Advertise Received: The RCST enters this state upon reception of the pep_control_advertise message. This message can be broadcast any time, or received right after the logon process. Upon reception of the message, the RCST can either send a pep_control_offer or reply with an error message aborting the process. Offering PEP: This state is entered once the pep_control_offer message has been sent by the RCST, This message is sent either upon reception of the pep_control_advertise message, or any time to force renegotiation of the PEP to be used for a given active SVN-MAC The terminal will wait for a response from the hub (pep_control_use), and if not received, after a number of retries and t/o expired, will abort the process. PEP Use Received: The RCST enters this state upon reception of the pep_control_use message that instructs the RCST to use one of the offered PEPs for the SVN-MAC on which it is received. A PEP Control Use Message may be sent at any time for any active SVN-MAC. In case the RCST cannot activate the required PEP configuration, it should return an error code to report the problem. Otherwise it will automatically transit to the next state. Use PEP on MACx: Successful processing of a PEP Control Use message causes the RCST to enter this state and to use the instructed PEP for the SVN-MAC on which it is received. PEP negotiation completion causes a transition away from this state. TDMA Sync: This is the normal operational state for the RCST. This is an absorbing state; the RCST should remain there until external events or loss of TDMA synchronization dictate transition to another state. The TDMA synchronization status should be supervised by the Sync Monitoring Process. Transmission of control bursts is allowed when the RCST is in this state. Transmission of traffic burst and traffic/control bursts may be allowed or these may be dynamically blocked even if assigned. NCR Recovery: The RCST enters this state when there is loss of TDMA synchronization or NCR loss when in TDMA Sync. This is a non-absorbing state; the RCST should autonomously transition to another state. The RCST should not transmit while in the NCR Recovery state. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 74 Figure 9.1: RCST State Transition Diagram for PEP Session Negotiation Protocol ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 75 Figure 9.2: Hub State Diagram for PEP Session Negotiation |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 9.2 PEP negotiation protocol parameters and MIB group | The PEP negotiation protocol makes use of the HLS agent control protocol (clause 9.2 in [i.1]). This protocol is used over the IPv4 address provisioned for a satellite interface and bound to a MAC24 label for management signalling. The PEP negotiation group in the RCST MIB from [i.1] compiles all the necessary information to perform PEP negotiation between the RCST and the NCC. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 9.3 Example use cases | An example of the message exchange during a normal progression of PEP negotiation is illustrated in Figure 9.3. The sequence illustrates the normal flow of events and signals. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 76 Figure 9.3: Normal PEP negotiation The RCST supports the current set of messages for TCP-PEP negotiation [i.1]. Each offer contains N descriptors for the offered TCP-PEPs. Each response contains M descriptors for the supported TCP-PEPs, where M=<N. The NCC finally selects one TCP-PEP. The transport of RCST Agent negotiation messages is explained below: 1) The IPv4 multicast group destination address and UDP port number are received via HLID descriptor in the TIM-U. 2) A PEP Advertise message is received on the forward link. This forward IP message is either unicast to the RCST IPv4 address or multicast to the multicast group address in step-1. The destination UDP port number for this forward IP message is as in step-1. 3) RCST sends a PEP Offer message with a destination IPv4 address that matches the IP source address of the PEP Advertise message and using the UDP destination port that was used in the PEP Advertise message. The IP packet is sent with the IP source of the RCST and using the same SVN on which the PEP Offer was received. 4) A PEP Use or PEP Error message is sent in response to a PEP Offer message. This has an IP source address that is identical to the IP destination address of the PEP Offer and a IPv4 destination address identical to the IP source address used for the PEP Offer. The UDP source port is identical to the UDP destination port of the PEP Offer message. The above exchange is used to configure the PEP used for a specific SVN. An RCST that supports multiple SVNs should repeat steps 3 & 4 of this negotiation for each SVN that is active. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 77 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 9.3.1 Consumer/SCADA/Backhauling scenarios | For these scenarios, an RCST will likely be part of only one traffic SVN. Figure 9.4 illustrates the message exchange that corresponds to this scenario. Figure 9.4: Normal PEP negotiation for one SVN |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 9.3.2 Corporate/Institutional/Multi-dwelling scenarios | The RCST may be part of one or more traffic SVNs It is expected that for multi-dwelling users multiple SVNs may be managed by the OVN. Steps 3 & 4 of the negotiation are repeated for each active SVN. In the next example the RCST issues a PEP Control Offer Message for two of its active MAC24s. The offer forces renegotiation of the PEP to be used for the MAC24s. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 78 Figure 9.5: Normal PEP negotiation for two SVNs |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 10 SNMP configuration | The recommended management reference network for RCS follows the TMN model of telecom network management to help the operators to configure and manage the RCS network in an easy way. In this architecture, the NMC performs all management functions, namely system configuration, fault management, system performances management and accounting data retrieval (FCAPS functions). The NMC and NCC could either be directly connected through a LAN interface, or via IP connection over terrestrial backhaul networks. The basic functionality of the NMC includes the manager of the elements of the network (RCST, GW, NCC). These functions support a SNMPv2c/SNMPv3 protocol and MIB data base (in the communication between NMC and network elements - Internal interface). The NMC is the SNMP manager and the RCST, NCC or Gateway are the SNMP agents. To comply with the recommended management architecture, the RCST will require a default or minimum SNMP configuration before a successful logon. This data should be provided by the installer or first configuration file. This clause provides the default and operational SNMP configuration for the different management actors/roles in the network. The RCST may use the following tables to provide the desired SNMP Access: • snmpCommunityTable [i.32] for SNMP community configuration • snmpTargetAddrTable [i.33] • snmpTargetAddrExtTable [i.32]: The table of mask and maximum message size (mms) value associated with the snmpTargetAddrTable • vacmAccessTable [i.34]: view access table configuration ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 79 Access to an SNMP server by an SNMP client is governed by a proprietary SNMP community table that identifies those communities that have access to MIB data. When an SNMP server receives a request, the server extracts the client's IP address and the community name. The SNMP community table is searched for a matching community. If a match is found, its access list name is used to validate the IP address. If the access list name is null, the IP address is accepted. A nonmatching community or an invalid IP address results in an SNMP authentication error. Each entry in the community table identifies: • SNMP community name: public / private or a new name • SNMP community security name: A human readable string representing the corresponding value of snmpCommunityName in a Security Model independent format • snmpCommunityContextEngineID • snmpCommunityContextName • snmpCommunityTransportTag: This object specifies a set of transport endpoints from which a command responder application will accept management requests. If a management request containing this community is received on a transport endpoint other than the transport endpoints identified by this object, the request is deemed unauthentic. The transports identified by this object are specified in the snmpTargetAddrTable. Entries in that table whose snmpTargetAddrTagList contains this tag value are identified. If the value of this object has zero-length, transport endpoints are not checked when authenticating messages containing this community string For a first default SNMP configuration, it is recommended to have only public / private communities, and to ensure a minimum level of protection only with the IP address of the primary NMC and mask 255.255.255.0. The default communities can be changed or additional ones can be added. The View Based Access Control Model (VACM) from [i.34] defines the necessary elements of procedure for controlling access to management information. To implement the View Based Access Control Model (VACM) an SNMP entity needs to retain information about access rights and policies. This information is part of the SNMP engine's Local Configuration Datastore (LCD). See [i.35] for the definition of LCD. In order to allow an SNMP entity's LCD to be remotely configured, portions of the LCD need to be accessible as managed objects. A MIB module, the View-based Access Control Model Configuration MIB, defines these managed object types. Figure 10.1 shows how the decision for access control is made by the view based access control model: ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 80 Figure 10.1: Access control decision by VACM How the decision for isAccessAllowed is made: 1) Inputs to the isAccessAllowed service are: a) securityModel -- SNMPv3 was designed for the use of multiple co-existing security models. The msgSecurityModel field specifies the security model that was used to generate the message. Therefore, the receiving entity knows which security model should be used to perform security processing upon message reception b) securityName -- principal who wants to access (as specified in the community table) c) securityLevel -- Level of Security: Different access rights for members of a group can be defined for different levels of security, i.e. noAuthNoPriv, authNoPriv, and authPriv. The securityLevel identifies the level of security that will be assumed when checking for access rights (see the SNMP Architecture document [i.35] for a definition of securityLevel). The View-based Access Control Model requires that the security Level is passed as input to the Access Control module when called to check for access rights. d) viewType -- read, write, or notify view e) contextName -- context containing variableName f) variableName -- OID for the managed object -- this is made up of: - object-type (m) - object-instance (n) 2) The partial "who" (1), represented by the securityModel (a) and the securityName (b), are used as the indices (a,b) into the vacmSecurityToGroupTable to find a single entry that produces a group, represented by groupName (x). 3) The "where" (2), represented by the contextName (e), the "who", represented by the groupName (x) from the previous step, and the "how" (3), represented by securityModel (a) and securityLevel (c), are used as indices (e,x,a,c) into the vacmAccessTable to find a single entry that contains three MIB views. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 81 4) The "why" (4), represented by the viewType (d), is used to select the proper MIB view, represented by a viewName (y), from the vacmAccessEntry selected in the previous step. This viewName (y) is an index into the vacmViewTreeFamilyTable and selects the set of entries that define the variableNames which are included in or excluded from the MIB view identified by the viewName (y). 5) The "what" (5) type of management data and "which" (6) particular instance, represented by the variableName (f), is then checked to be in the MIB view or not, e.g. the yes/no decision (z). As an example, the VACM configuration for SNO and SVNO basic access roles would be: The initial parameters that should be configured during installation for the View-based Access Control Model are: A security configuration: The choice of security configuration determines if initial configuration is implemented and if so how. One of three possible choices is selected: • initial-minimum-security-configuration • initial-semi-security-configuration • initial-no-access-configuration In the case of a initial-no-access-configuration, there is no initial configuration, and so the following steps are irrelevant. 6) Community table: Three entries in the snmpCommunityTable, "initial", "sno", & "svno" 7) A default context: One entry in the vacmContextTable with a contextName of "" (the empty string), representing the default context. Note that this table gets created automatically if a default context exists. vacmContextName "" 8) An initial group: One entry in the vacmSecurityToGroupTable to allow access to group "initial". vacmSecurityModel 3 (USM) vacmSecurityName "initial" vacmGroupName "initial" vacmSecurityToGroupStorageType anyValidStorageType vacmSecurityToGroupStatus active A SNO, and SVNO groups: vacmSecurityModel 3 (USM) vacmSecurityName "sno" vacmGroupName "sno" vacmSecurityToGroupStorageType anyValidStorageType vacmSecurityToGroupStatus active vacmSecurityModel 3 (USM) vacmSecurityName "svno" vacmGroupName "svno" vacmSecurityToGroupStorageType anyValidStorageType vacmSecurityToGroupStatus active ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 82 9) Initial access rights: Three entries in the vacmAccessTable as follows: - read-notify access for securityModel USM, securityLevel "noAuthNoPriv" on behalf of securityNames that belong to the group "initial" to the <restricted> MIB view in the default context with contextName "". - read-write-notify access for securityModel USM, securityLevel "authNoPriv" on behalf of securityNames that belong to the group "svno" to the <SNO> MIB view in the default context with contextName "". - read-write-notify access for securityModel USM, securityLevel "authNoPriv" on behalf of securityNames that belong to the group "sno" to the <SNO> MIB view in the default context with contextName "". - if privacy is supported, read-write-notify access for securityModel USM, securityLevel "authPriv" on behalf of securityNames that belong to the group "sno" to the <SNO> MIB view in the default context with contextName "". - That translates into the following entries in the vacmAccessTable. - One entry to be used for unauthenticated access (noAuthNoPriv): vacmGroupName "initial" vacmAccessContextPrefix "" vacmAccessSecurityModel 3 (USM) vacmAccessSecurityLevel noAuthNoPriv vacmAccessContextMatch exact vacmAccessReadViewName "restricted" vacmAccessWriteViewName "" vacmAccessNotifyViewName "restricted" vacmAccessStorageType anyValidStorageType vacmAccessStatus active • Two entries to be used for authenticated access (authNoPriv) with optional privacy (authPriv): vacmGroupName "svno" vacmAccessContextPrefix "" vacmAccessSecurityModel 3 (USM) vacmAccessSecurityLevel authNoPriv vacmAccessContextMatch exact vacmAccessReadViewName "SVNO" vacmAccessWriteViewName "SVNO" vacmAccessNotifyViewName "SVNO" vacmAccessStorageType anyValidStorageType vacmAccessStatus active ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 83 vacmGroupName "sno" vacmAccessContextPrefix "" vacmAccessSecurityModel 3 (USM) vacmAccessSecurityLevel authNoPriv vacmAccessContextMatch exact vacmAccessReadViewName "SNO" vacmAccessWriteViewName "SNO" vacmAccessNotifyViewName "SNO" vacmAccessStorageType anyValidStorageType vacmAccessStatus active 10) Two MIB views, of which the second one depends on the security configuration. • Two views, the <SNO> view, and the <SVNO> for authenticated access: - the <SNO> MIB view is the following subtree: "internet" (subtree 1.3.6.1) - the <SVNO> MIB view is the following subtree: "internet" (subtree 1.3.6.1) • A second view, the <restricted> view, for unauthenticated access. This view is configured according to the selected security configuration: - For the initial-no-access-configuration there is no default initial configuration, so no MIB views are pre- scribed. - For the initial-semi-secure-configuration: the <restricted> MIB view is the union of these subtrees: (a) "system" (subtree 1.3.6.1.2.1.1) [i.36] (b) "snmp" (subtree 1.3.6.1.2.1.11) [i.36] (c) "snmpEngine" (subtree 1.3.6.1.6.3.10.2.1) [i.35] (d) "snmpMPDStats" (subtree 1.3.6.1.6.3.11.2.1) [i.37] (e) "usmStats" (subtree 1.3.6.1.6.3.15.1.1) [i.38] • For the initial-minimum-secure-configuration: the <restricted> MIB view is the following subtree. "internet" (subtree 1.3.6.1) This translates into the "SNO" and "SVNO" entries in the vacmViewTreeFamilyTable. vacmViewTreeFamilyViewName "SNO vacmViewTreeFamilySubtree 1.3.6.1 vacmViewTreeFamilyMask "" vacmViewTreeFamilyType 1 (included) vacmViewTreeFamilyStorageType anyValidStorageType ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 84 vacmViewTreeFamilyStatus active vacmViewTreeFamilyViewName "SVNO vacmViewTreeFamilySubtree 1.3.6.1 vacmViewTreeFamilyMask "" vacmViewTreeFamilyType 1 (included) vacmViewTreeFamilyStorageType anyValidStorageType vacmViewTreeFamilyStatus active minimum-secure semi-secure vacmViewTreeFamilyViewName "restricted" "restricted" vacmViewTreeFamilySubtree 1.3.6.1 1.3.6.1.2.1.1 vacmViewTreeFamilyMask "" "" vacmViewTreeFamilyType 1 (included) 1 (included) vacmViewTreeFamilyStorageType anyValidStorageType anyValidStorageType vacmViewTreeFamilyStatus active active vacmViewTreeFamilyViewName "restricted" vacmViewTreeFamilySubtree 1.3.6.1.2.1.11 vacmViewTreeFamilyMask "" vacmViewTreeFamilyType 1 (included) vacmViewTreeFamilyStorageType anyValidStorageType vacmViewTreeFamilyStatus active vacmViewTreeFamilyViewName "restricted" vacmViewTreeFamilySubtree 1.3.6.1.6.3.10.2.1 vacmViewTreeFamilyMask "" vacmViewTreeFamilyType 1 (included) vacmViewTreeFamilyStorageType anyValidStorageType vacmViewTreeFamilyStatus active ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 85 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11 Terminal start-up phases | The objective of this clause is to show, step by step, the necessary functions, messages, and parameters required for the successful operation of a terminal in an RCS2 network; starting from the installation of the terminal and from there reach the operational status, understanding this status as the stage when the terminal is able to receive and transmit traffic. This analysis aims at putting together concepts coming from the LL [i.3] and HL [i.1] specification and going into the fine details of the messages used and values of the parameters exchanged. The following phases will be analyzed, from a first RCST power up to a successful network entry: • RCST installation • RCST forward link alignment • RCST return link alignment • RCST logon and first commissioning Three different actors may perform M&C operations on the RCST: • The SNO: responsible of RCST forward and return alignment and first logon into the network. The SNO is responsible for organizing the RCSTs in different Group_Ids and Logon_Ids and registering the non-volatile RCST HW addresses. Each RCST is given an SVN-MAC that can be used for management and control traffic from the SNO. • The SVNO: responsible for the RCST traffic functions, IP routing, QoS, etc. The SVNO would be considered with a role of ISP with management functions and access to NMC client. The system profile parameters are set by the SVNO. The SNO assigns a set of SVN-MACs per SVNO. The SVNO is responsible of the distribution of a given sub-set of SVN-MACs between its SVNs. One or more SVN-MACs may be assigned to each RCST for traffic interfaces. • The installer: responsible of the first set up of the installation parameters required for the RCST start up. The minimum set of parameters provided by the installer should be: - Operational forward link acquisition parameters - SNMP parameters for remote SNMP communication between the RCST and the SNO, and local SNMP from the installer - Fwd and Rtn alignment parameters (in case alignment is required) - Some of the System parameters (see table in clause 11.1.2) This clause will conclude on what are the parameters that should be remotely accessed by the remote management entities and how. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.1 RCST installation | After an RCST power on, and before connecting the RCST to the Operator Virtual Network (OVN), the RCST should count with an initial set of configuration parameters for the start-up. This set of parameters would allow the RCST to acquire the forward link, unless a pointing alignment process is required. Once the forward link is acquired, the combination of ONID (Original Network ID) and INID will determine the SNO domain where the RCST belongs to. In terms of RCST operation, the SNO domain is transparent to the RCST. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 86 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.1.1 Forward link acquisition parameters | The minimum set of parameters needed at initial installation for forward link acquisition is: • ODU parameters within the System group (as already included in [i.1]) • Flink configuration group set of parameters (as already included in [i.1]) The ODU parameters use the same format that is used in SatLabs MIB [i.39]. By default they are considered RW only for the Installer. Anyhow they are recommended to be RW parameters for the SNO also, to allow remote configuration in case there is any problem. Table 11.1: ODU parameters Functional Group dvbRcs2SystemConfig Element Type Unit Range Description Access Rights M&C Actor dvbRcs2SystemOduAntenna Size INTEGER32 cm - Diameter of the antenna. For supervision. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision dvbRcs2SystemOduSspa INTEGER32 0,1 W - Power level of the Solid State Power Amplifier. For supervision. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision dvbRcs2SystemOduGain INTEGER32 0,1 dBi - Antenna peak gain of the ODU. For supervision. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision dvbRcs2SystemOduTxType SnmpAdmin String - Type of transmitter installed in the ODU. For supervision. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision dvbRcs2SystemOduRxType SnmpAdmin String - Type of LNB installed in the ODU, with information such as vendor type, output type. For supervision. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision, only in RCST MIB dvbRcs2SystemOduRxBand INTEGER High- band (0), Low Band (1) LNB high band / Low band selector. High band corresponds to the emission of an 18-26 kHz tone with 0,4-0,8 Vpp in the Rx IFL cable. Required for forward link acquisition. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision, only in RCST MIB dvbRcs2SystemOduRxLO INTEGER32 - ODU reception local oscillator frequency. Required for forward link acquisition. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision, only in RCST MIB dvbRcs2SystemOduTxLO INTEGER32 In 100 Hz - ODU transmission Frequency of Block Up- Converter Local Oscillator. Required for forward link acquisition. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision, only in RCST MIB In [i.1], the Flink configuration group lists the forward link attachment points (e.g. different for installation and operation), in a similar way that was done in SatLabs MIB. This table describes the forward link parameters used for the start up stream of the NCC as the follows: • fwdStartPopId: population ID associated with the start up forward link. • fwdStartFrequency: frequency of the start transponder carrying a NIT to which any RCST should trigger to acquire forward link. • fwdStartPolar: polarization of the start transponder carrying the NIT. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 87 • fwdStartFormat: transmission format standard applied to the start up stream (only dvbs2ccm or dvbs2acm would be allowed). • fwdStartRolloff: roll-off applied on the start transponder (0.10, 0.20, 0.25, 0.35). Noted that in RCS2, the additional value of 0.10 has been added. • fwdStartSymbolRate: symbol rate on the start transponder carrying a NIT to which any RCST should trigger to acquire the forward link information. • fwdStartInnerFec: specifies the inner FEC on the start transponder. Only the fwdStartPopId (operational population ID), fwdStartFrequency (fwd link frequency), fwdStartPolar and fwdStartFormat are really required to acquire the forward link. The rest of parameters can be used to check the fwd link being acquired. If no match is produced the RCST could give a warning. The following parameters are also part of the Satellite Forward Link Descriptor [i.3]: • Polarization • Format • RollOff • SymbolRate • InnerFEC The Fwd Link Descriptor includes as well the satellite ID, beam ID, NCC ID, & local_multiplex ID that can be correlated with the Population ID through the RMT. The set of parameters already included in RCS2 MIB, under Flink configuration group, are based on SatLabs MIB. The Flink configuration parameters should be set by the installer in accordance to the RCST provisioning information kept in the SNO. They are recommended to be RW to allow remote reconfiguration in case there is any problem or provisioning change in the SNO for that particular RCST (e.g. change to a different frequency or coverage area). Table 11.2: FLink config parameters Functional Group dvbRcs2FwdConfiguration Element Type Unit Range Description Access Rights M&C Actor dvbRcs2FwdStartEntry SEQUENCE { dvbRcs2FwdStar tIndex, dvbRcs2FwdStar tPopID, dvbRcs2FwdStar tFrequency, dvbRcs2FwdStar tPolar, dvbRcs2FwdStar tFormat, dvbRcs2FwdStar tRolloff, dvbRcs2FwdStar tSymbolRate, dvbRcs2FwdStar tInnerFec, dvbRcs2FwdStar tRowStatus Fwd link configuration parameters Installer (RW) SNO (RW) SVNO (RO) SNO provisioning parameters as part of RCST profile The fwdStatus lists all the forward link status parameters, as RO parameters, for supervision. This group provides details on the forward link that the RCST has attached to. Right now this set of parameters is provided in the State group of RCS2 MIB. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 88 Table 11.3: FLink status parameters Functional Group dvbRcs2State Element Type Unit Range Description Access Rights M&C Actor dvbRcs2FwdLinkStatus INTEGER (0) notAcquired, (1) acquired Provides the status of the RCST forward link. RO dvbRcs2FwdStatusEntry SEQUENCE {dvbRcs2FwdSt atusIndex, dvbRcs2FwdSta tusIfReference, dvbRcs2FwdSta tusONetId, dvbRcs2FwdSta tusNetId, dvbRcs2FwdSta tusNetName, dvbRcs2FwdSta tusFormat, dvbRcs2FwdSta tusFrequency, dvbRcs2FwdSta tusPolar, dvbRcs2FwdSta tusInnerFec, dvbRcs2FwdSta tusSymbolRate, dvbRcs2FwdSta tusRolloff, dvbRcs2FwdSta tusModulation, dvbRcs2FwdSta tusFecFrame, dvbRcs2FwdSta tusPilot, dvbRcs2FwdSta tusBer, dvbRcs2FwdSta tusCnr, dvbRcs2FwdSta tusRxPower} An entry in the forward link status table. Each entry is associated with a physical interface. RO |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.1.2 RCST system parameters | As already introduced in the Management clause of [i.1] the RCST system profile is given by a set of parameters. These parameters are grouped as follows: • System profile map (Consumer, SOHO, Multi-dwelling, corporate, SCADA, Backhaul, Institutional) that identifies the terminal profile as given in [i.2]. • System option map (16QAM, 32APSK, waveformFlex, lowerCarrier Switch, slotterAlohaTraffic …) that maps the optional features supported by the terminal for supervision following the nomenclature provided in [i.2]. • Features supported by the terminal (FeaturesMap field in the table below). • Lower layer capabilities that are advertised during logon following the format of [i.3]. • Higher layer capabilities that are advertised during logon (to be reviewed against system features and system option map). • Network topology support: star transparent, mesh regenerative, mesh transparent or hybrid, an indication of the network topology modes supported by the terminal. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 89 • Transmission and reception encapsulation modes: GSE, RLE, ATM or MPEG. The encapsulation modes are given by the SNO, as a system configuration. Any terminal compatible with RCS2 should comply with RLE and GSE. The ATM and MPEG modes given are only set for backward compatibility purposes. Table 11.4 proposes modifications to the System Configuration MIB group as described in [i.1]. Table 11.4 Element Range Description Access Rights M&C Actor SystemProfileMap Cosumer(0), SOHO(1), Multi-dwelling (2), Corporate (3), SCADA (4), Backhaul (5), Institutional (6) Indicates RCST supported profiles as bit map flags, where: -0 not supported -1 supported. Installer (RO) SNO (RO) SVNO (RO) This field should represent the profiles that can be supported by the terminal from factory. The SNO/SVNO should be aware of the supported profiles. The SNO RCST template for provisioning (that specifies the RCST profile) should be in accordance to the RCST supported profiles given in this field. OptionMap 16QAMrtn (0), 32APSKfwd (1), waveformFlex (2), contentionSync(12), nomarclFec(13), multiTs(14), qsTs(15) Minimum list of system options, given for supervision. Installer (RO) SNO (RO) SVNO (RO) Options provided from factory. SNO/SVNO should be aware of these values. FeaturesMap qpsk_8psk_cpmRtn (0), refWaveforrms (1), customWaveforms (2), waveformBound (3), waveformToTimeslot (4), eirpPowerCtrol (5), constantPowerCtrl (6), fwdLinkDvbs2 (7), fwdLinkSingleGS (8), fwdLinkTSPacketStream (9), fwdLinkMultipleStreams (10), gseBBFrameCRC32 (11), damaTraffic (12), unsolicitedDATraffic (13), slottedAlohaLogon (14), recombinedDAMA (15), raReplicas (16), inbandSignalling (17), signallingDAtimeslots (18), SCPC (30), space3 (31), mobile (32) These are the features supported by the terminal, given to the NCC/NMC for information. Installer (RO) SNO (RO) SVNO (RO) Features provided from factory. SNO/SVNO should be aware of these values. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 90 Element Range Description Access Rights M&C Actor LowerLayerCapabilities multipleGS1(0), multipleGS2(1), reserved1(2), fullRangeFLMODCOD (3), fullRangeRLMODCOD(4), fastCarrierSwitching (5), carrierSwitchingClass1(6), carrierSwitchingClass2(7), EsN0powerCtrl(8), constantPowerSpectrumD ensity(9), slottedAlohaTraffic(10), crdsaTrafficSupport (11), reserved2(12), reserved3(13), reserved4(14), customCCCPMwaveform( 15), service1(16), service2(17), service3(18), service4(19), nbrofL2ifs(20), nbrofL2ifs(21), nbrofL2ifs(22), nbrofL2ifs(23), SWversion1(24), SWversion1(25), SWversion1(26), SWversion1(27), SWversion1(28), SWversion1(29), SWversion1(30), SWversion1(31) Lower layer capabilities following Table 8.5 from [i.3]. Each field is one flag. (bit). Information provided by the RCST to the NCC during logon. Installer (RW) SNO (RO) SVNO (RO) These flags should be set in accordance to the capabilities activated in the terminal LL capabilities information is provided by the RCST to the NCC during logon. This information is required by the NCC, to determine the operation parameters of the terminal. The SNO should configure the terminal in accordance to these flags and the RCST provisioning. HigherLayerCapabilities ipv4ipv6Support (0), multicastFwd (1), enhMulticast(2) dynamicMulticast (3), diffservQoS (4), mplsSupport (5), snmpv2c(6), snmpv3 (7), dynamicConnectivity(8), transecHooksSupport (9), dynamicRouting (10), ospfSupport (11), firewall (12), multiSVNO (13) VLAN(14), dhcpLAN (15), motorControl (16), sddp (17), pepNegotiationProtocol (18), authenticatedLogon (19), mesh (20), reserved (21), reserved (22), reserved (23) Higher layer capabilities. Information provided by the RCST to the NCC during logon. Installer (RW) SNO (RO) SVNO (RO) These flags should be set in accordance to the capabilities activated in the terminal. These capabilities should be known by the SNO and the SVNO, to be able to adjust the HL operation accordingly. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 91 Element Range Description Access Rights M&C Actor PointingAlignmentSupport 0 – Nominal CW EIRP in the pointing direction 1 – Supported pointing alignment methods - (1) Burst probe, and CW probe by fixed non- configurable EIRP - (2) Burst probe, and CW probe by configurable EIRP New proposed 2 byte field that indicates the support of pointing alignment probing. Parameter is proposed to be moved to the installation group together with the rest of the alignment parameters. Installer (RW) SVNO (RO) SNO (RO) Flag used to inform the NCC the kind of alignment procedure supported by the RCST. The type of alignment is selected during the alignment process. NetworkTopologySupport starTransparent (0), meshRegenerative (1), meshTrasnparent (2), hybrid (3) Network topology read-only parameter Installer (RO) SNO (RO) SVNO (RO) Flags that indicate the type of topologies supported by the terminal. A change of topology may be linked to a new software version. SNO/SVNO should be aware of this value. NetworkEncapsulationMode Tx ATM(1), MPEG(2), RLE(3), GSE(4) Encapsulation mode for transmission If the terminal is RCS2 compliant, it should be able to support the 4 different possibilities. Installer (RW) SNO (RW) SVNO (RO) Value configured by the installer. It can then be reconfigured by the SNO. NetworkEncapsulationMode Rx ATM(1), MPEG(2), RLE(3), GSE(4) Encapsulation mode for reception If the terminal is RCS2 compliant, it should be able to support the 4 different possibilities. Installer (RW) SNO (RW) SVNO (RO) Value configured by the installer. It can then be reconfigured by the SNO. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.1.3 SNMP initial configuration | The RCST first installation should include a set of SNMP parameters to allow the RCST reception of SNMP commands from the primary NMC even if a successful logon into the network has not been yet performed. This would require that: • The RCST accepts SNMP commands through the satellite interface. The RCST may have several interfaces. SNMP access filters are applied to RCST IfIndex 1. • The NMC sends SNMP commands using the Hardware ID (6 bytes) address that uniquely identifies the terminal in the network. Once the terminal has logon and has the SVN-MAC (3 bytes) for SVN0, the SNMP commands can use this SVN-MAC for SNMP traffic. • The NMC SNMPv2c community is configured in the terminal through the configuration of snmpCommunityTable as defined in the "SNMP Community MIB Module" clause of [i.32] and the snmpTargetAddrTable is defined in the "Definitions" clause of [i.33]. The RCST may create one row in snmpTargetAddrTable for each SNMPv2c Transport Address Access. SNMP access is controlled and specified by the MIB objects in [i.35] through [i.34], and [i.32]. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 92 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.2 RCST alignment | The RCST alignment process may include two different stages: • forward link (FL) acquisition prior to enabling transmission on the return link; • return link (RL) required only if FL pointing accuracy is achieved and to perform an initial MAC logon. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.2.1 RCST forward link antenna alignment configuration | Following the description of the forward link antenna alignment in [i.1], this process will require the following parameters: • MaxFwdAlignThrExcDuration: the duration of the time interval during which FL alignment accuracy should be achieved (part of the Installation MIB group). • Max Fail: Maximum number of alignment failures (part of the Installation MIB group). The corresponding counter is incremented every time the state machine re-visits the FwdAlignment state. • Fwd_link_snr_threshold (part of the Pointing Alignment Control Descriptor): the FL SNR threshold value to be reached to ensure FL successful alignment, value required for FL alignment accuracy. This parameter is proposed for inclusion in the Installation Group of the MIB. • Alignment Population ID: A different population ID to be used during the alignment process. This will be provided by the NCC while negotiating the alignment parameters. Could be saved in the RCST MIB for supervision, as for now, this parameter is not included in the MIB. • Start-up downlink TDM (administratively configured and selected by the RCST): The RCST should tune to the start-up in the operational TDM (Flink Configuration parameters). From there, the RCST can request the alignment process. [i.4] proposes several suitable mechanisms to ensure forward link accuracy: • manual procedure support by acoustic or visual feedback directly related to the power measurements of the received RF signal (CNR); • automated procedure via motorized antenna as detailed in clause 10 of HLS [i.1]. The type of FL alignment mechanism is linked to the flag motorControl(16), part of HL capabilities. If activated the RCST will inform the NCC whether it has or not a motorized antenna. To sum up these are the parameters that need to be set up by the installer to achieve forward link acquisition and alignment. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 93 Table 11.5 Functional Group dvbRcs2Installation Element Type Range Description Access Rights M&C Actor MaxFwdAlignThrExeDuration Unsigned 32 (0) notAcquired, (1) acquired The duration of the time interval during which FL alignment accuracy should be achieved Installer (RW) SNO/SVNO (RO) SNO system parameter, that applies to all SNO's terminals. MaxFail Counter Maximum number of alignment failures allowed Installer (RW) SNO/SVNO (RO) SNO system parameter, that applies to all SNO's terminals. Functional Group dvbRcs2SystemConfig HigherLayerCapabilities motorControl (16), 0 – manual 1 - motorized antenna Whether the terminal has or not a motorized antenna Installer (RW) SNO (RO) SVNO (RO) These flags should be set in accordance to the capabilities activated in the terminal. These capabilities should be known by the SNO and the SVNO, to be able to adjust the HL operation accordingly. OduRxBand INTEGER LNB high band / Low band selector. High band corresponds to the emission of an 18-26 kHz tone with 0,4-0,8 Vpp in the Rx IFL cable. Required for forward link acquisition. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision, only in RCST MIB OduRxLO INTEGER 32 ODU reception local oscillator frequency. Required for forward link acquisition. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision, only in RCST MIB OduTxLO INTEGER 32 ODU transmission Frequency of Block Up-Converter Local Oscillator. Required for forward link acquisition. Installer (RW) SNO/SVNO (RO) SNO/SVNO access for supervision, only in RCST MIB The FL alignment is performed with the operational population ID, taking the first valid entry in the forward link configuration from the Flink Configuration group. After FL alignment, the RCST is able to filter all the necessary control information related to the RCS network and can request a further Return link alignment. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.2.2 Return link alignment | After a successful forward link acquisition, the RCST is aware of the RCS2 network properties. At this point the terminal can start transmitting, and even require a return link alignment. The RL alignment can be done in two different ways: • Based on Installation Burst (IB) • Based on Continuous Wave (CW) transmission Both ways could be performed either automatically or manually. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 94 In [i.1] the type of pointing alignment support is defined in the System Configuration MIB group as. [i.3] also defines this parameter as a logon element type (passed to the NCC in the logon request), as follows: • Pointing Alignment support: the different ways that the RCST may support link alignment operations Table 11.6 MSB LSB Supported pointing alignment methods 128-255 User defined User defined 2-127 Reserved Reserved 1 Nominal CW EIRP in the pointing direction, in dBm Burst probe, and CW probe by fixed non-configurable EIRP 0 Reserved Burst probe, and CW probe by configurable EIRP However this table is incorrect. New proposed 2 byte field that indicates the support of pointing alignment probing: 0 – Nominal CW EIRP in the pointing direction 1 – Supported pointing alignment methods: • (1) Burst probe, and CW probe by fixed non-configurable EIRP • (2) Burst probe, and CW probe by configurable EIRP The type of pointing alignment support by the RCST is configured by the installer, and should be reflected in the RCST MIB for supervision. For a better organization of parameters, this configuration should be placed under the installation group. Table 11.7 Functional Group dvbRcs2SystemConfig Element Type Range Description Access Rights M&C Actor dvbRcs2PointingAlignment Support INTEGER32 0 – Nominal CW EIRP in the pointing direction (1 byte) 1 – Supported pointing alignment methods - (1) Burst probe, and CW probe by fixed non- configurable EIRP - (2) Burst probe, and CW probe by configurable EIRP New proposed 2 byte field that indicates the different ways that the RCST may support link alignment operations. Parameter is proposed to be moved to the installation MIB group together with the rest of the alignment parameters. Installer (RW) SNO/SVNO (RO) Flag used to inform the NCC of the kind of alignment procedure supported by the RCST. The type of alignment is selected during the alignment process. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 95 To complete the RL alignment configuration, and to allow any RCST to do a successful logon, the RCST would need: Table 11.8 Functional Group dvbRcs2SystemConfig Element Type Range Description Access Rights M&C Actor sysLocation DisplayString GPS position of the RCST ODU expressed as longitude, latitude and altitude. The string has 31 characters in the following format <xx.xxx>, <a>, <yyy.yyy>, <b>, <zzzz.z>, M, where x,y and z represent digits, a=N or S, b= E or W. Installer (RW) SNO (RW) SVNO (RO) SNO remote access for recovery Functional Group dvbRcs2RtnConfiguration RtnConfigMaxEirp Integer32 Maximum value of EIRP that the terminal can reach Installer (RW) SNO (RW) SVNO (RO) SNO remote access for recovery RtnConfigDefIfLevel Integer32 Starting power level for IF Installer (RW) SNO (RW) SVNO (RO) SNO remote access for recovery During logon, the RCST informs the NCC if it can support one or more of the RL alignment operations by means of the pointing alignment support indicator. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.3 RCST logon and first commissioning | If no Pointing Alignment Support descriptor is present in the TIM-B, the RCST can proceed normally with FL acquisition and logon attempt. After successful FL acquisition, the RCST should verify the status (dvbRcs2AlignmentStatus element of the State group) of earlier pointing alignment. If done, no alignment process is required and the RCST can continue with the logon. During FL acquisition, the RCST receives the NIT, RMT, NCR, SPT, FCT2, BCT, TIM-B, TBTP2, having all the necessary control information related to the operation in the RCS network. The RCST checks the Lowest Software Version descriptor matching its RCST HID. This information is included in the TIM-B. The RCST can only proceed with the MAC logon if its current operational SW version defined by implementation rules is considered sufficient. The descriptor contains the following information: • oui: indicates a group of RCSTs by reference to an OUI matching the OUI used in the RCST HID; • swdl_mcast_address/port: identifies the IPv4 multicast address and UDP destination port for a SW download multicast service; • sw_version: the field indicating the lowest SW version associated with the OUI. The following set of parameters is reflected in the SDDP configuration group of the RCST MIB: • Operational SW version • MinSwVersion • IP information for downloading an new SW version ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 96 - IPv4 address (of an IP multicast stream) and UDP port • A flag parameter to indicate to the RCST whether or not to ignore the SW version notified in the TIM-B. This flag needs to be included in the SDDP group • Additionally, there is a backup SWversion in the state group Table 11.9 Functional Group dvbRcs2SDDPconfiguration Element Type Range Description Access Rights M&C Actor SwVersion Unsigned32 Current SW version in the SW distribution carousel, respective to the manufID and vendor specific parameters RW MinSwVersion Unsigned32 Indicates the minimum SW version required for log-on, as received in the Lowest Software Version descriptor (TIM-B) RW MgroupType InetAddressType RW MgroupAddress InetAddress RW MgroupPrefixLength InetAddressPrefix Length RW Port InetPort RW Functional Group dvbRcs2State dvbRcs2RCSTAlternat eSoftwareVersion snmpAdminString Alternate (backup/new) RCST software version ([i.39]) RO If the current SW version is insufficient, the RCST cannot log on, but perform the necessary actions to automatically load or acquire another operational SW version. The HLS specification recommends the usage of SDDP to download the new SW version. The SVN mask used by the multicast stream dedicated to SW download can be located by the RCST through the MMT2 or the mapping method indicated in the Logon Response descriptor. After successful check of the correct RCST SW version, the RCST is ready to start a logon procedure. The LL specification [i.3] introduces two variants of the logon procedure: • basic logon • logon at large timing uncertainty The procedure and parameters required for the basic logon is analyzed hereafter. The RCST sends a logon request in a logon timeslot, either using random access or a logon timeslot dedicated to the RCST. This request includes: • indication of the type of logon (entry type = 0x1 binding user to HW and network, see Pointing Alignment Support descriptor in [i.3]) • indication of the network status of the RCST as it perceives it (LSB of access status is 1 indicating that NCC has confirmed pointing alignment, see Alignment Control Types in [i.3]) • RCST HID (concerns only random access) • a field indicating the lower layer capabilities of the RCST • in addition, a field indicating the higher layer capabilities of the RCST The higher layer capabilities field should follow the format already detailed in clause 11.1.2. For supervision, the last type of logon requested and the indication of the network status of the RCST should be reflected in the RCST MIB (state group). RCST HID may be included as part of the MIB, as a RO parameter, part of RCS2 System group (i.e. new element to be added).The last logon entry type should also be saved in the status RCST MIB group (need to be included). ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 97 Table 11.10 Functional Group dvbRcs2State Element Type Range Description Access Rights M&C Actor typeOfLogon INTEGER Basic (0), LargeTiming (1) Two variants of logon procedure exist, the basic procedure and a procedure extension called Logon at Large Timing. (RCS2) Installer (RW) SNO (RW) SVNO (RO) First value provided in the first installation. Could be changed by the SNO. dvbRcs2Align mentStatus INTEGER (0) not confirmed aligned, (1) confirmed aligned RCST flag that reflects the alignment status given by the NCC during logon. RCS2 Installer, SNO, SVNO (RO) dvbRcs2Subsc riptionStatus INTEGER (0) NotConfirmedS ubscription (1) ConfirmedSubs cription Flag to reflect the RCST subscription status given by the NCC at logon. (RCS2) Installer, SNO, SVNO (RO) The flag reflects the information provided during logon, it is saved in the MIB for supervision. dvbRcs2HLSini tialization INTEGER (0) HL not Initialized (1) HL initialized by the SNO (2) HL initialized by the SVNO HL should be initialized by the SNO during logon. The SVNO may afterwards modify/complete the HL configuration. For that it should change first this status to (0), and once finished change it to (2) Installer (RO) SNO (RW) SVNO (RW) This value reflects the status of HL configuration. Only the SNO or SVNO may modify this value. dvbRcs2Comis sionedStatus INTEGER (0) Not confirmed commissioned (1) NCC indicates the commissioning is completed RCST commissioned status. The flag can be raise by loading a new configuration file. At a change of NIT or RMT, the RCST changes this flag to "Not confirmed commissioned" (RCS2) Installer (RO) SNO (RW) SVNO (RW) This flag is set during the logon phase. But in order to allow remote configuration by other means (not only L2S but SNMP or configuration file from the SNO/SVNO), these flags are RW. The SNO and SVNO should change these flags following the similar rules as in the logon. The NCC TIM-U response includes: • logon response descriptor, initializing the RCST for normal operation in the network (see Table 6.11); • control assign descriptor, indicating the MF-TDMA sync thresholds; • correction message descriptor, indicating initial corrections in timing, frequency, and power relative to transmission of the logon request bursts; • lower layer service descriptor, that initializes the LL services; • a Network Layer Info descriptor (NLID) for additional information, by default provided in SNMP format; • conditionally, a Higher Layers Initialization descriptor; • optionally, a DHCP Option descriptor with the MTU for the return link, sent in TIM U or in TIM B. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 98 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.3.1 Higher layers initialization | This clause describes what information is needed for the HL to be initialized. As part of the logon response, the following fields are relevant for HL initialization: • RCST_access_status: This status can be used by the NCC to signal that the RCST is not commissioned or has its Higher Layers not initialized. - Access status = 0011 LSB of access status is 1 indicating that NCC has confirmed pointing alignment xx1x indicates that NCC confirms that the user is associated with the RCST (User ID indicated in the logon request) x0xx indicates that the HL have not been initialized 0xxx indicates that the NCC has not confirmed that the commissioning is complete • Unicast RCS-MAC addresses/SVN Mask for higher layers. unicast_rcsmac_count indicates the number of unicast RCS-MAC addresses that are assigned to the RCST; For each of them the logon response contains a: - svn_prefix_size: A 5 bit field that indicates the number of most significant bits of the associated unicast RCS-MAC that holds the SVN number - unicast_rcsmac A 24 bit field that assigns one unicast RCS-MAC to the RCST. The SVN bits constitute a bit field that holds the SVN number of the RCS-MAC The Higher Layers Initialization descriptor (if access status indicates that the HL are not initialized this descriptor is included) is used by the NCC to initialize each of the layer 2 RCST interfaces for IPv4 based M&C. This way the SNO, initializes each one of the RCST's SVN interfaces with a different IPv4 address, being, each one of them, an additional traffic interface. • sat_l2if_count: indicates the number of layer 2 interfaces that are initialized, and for each of them the HLID contains: - rcs_mac: A 24 bit field that provides a reference to one satellite side layer 2 interface by its dedicated RCS-MAC address - l2if_ipv4_m&c_address: A 32 bit field that indicates the IPv4 M&C address associated to a satellite side layer 2 interface; Overrides the initial SNMP configuration - hl_offer_stream_ipv4_mcast_identification: A 32 bit filed that indicates the IPv4 multicast stream to be used to discover the higher layer support offer. Used for PEP advertisement - hl_offer_stream_port_number: A 16 bit field that indicates the port number used for indicating the higher layer support offer. Used for PEP advertisement - higher_layer_ pep_switch_off: A flag that when set to '1' indicates that the RCST should switch off all higher layer interception PEPs for the respective satellite side layer 2 interface and apply the native protocols unmodified. After successful logon, PEP negotiation will be used to establish the PEP type per RCST interface The SVN_0 is the one used only for management from the SNO, and it should be the first entry of the loop. The RCST should support at least one traffic interface. The minimum number of entries in this loop should be two, the first one linked to SVN_0 for management from the SNO, and a second entry associated to traffic. More entries can be added, corresponding to the additional SVNs. The field "l2if_ipv4_m&c_address" really corresponds to the IPv4 address for traffic, but in addition, it can be used for management from the SVNO. The SVNO is free to select which traffic SVN to use for management, although, most likely, the decision would depend on the type of traffic that each SVN is carrying. The SVN-MAC and SVN mask allows an RCST to identify the corresponding SVN number. The svn_prefix_size provided in the logon response, indicates the number of most significant bits of the associated RCS-MAC that holds the SVN number. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 99 The HLS specification also mentions that: Within the OVN an RCST should be assigned one or more IPv4 address corresponding to the configured SVN-MAC labels. The IPv4 address should be unique within a VRF Group. In addition, the RCST should allow the SVN-MAC interface to be assigned an IPv6 address and may support other network addresses. NOTE: An RCST that is assigned multiple SVN-MAC labels corresponding to multiple traffic SVNs will normally also be assigned a separate IP address for each SVN-MAC (e.g. an IPv4 or IPv6 address). These addresses may be presented on separate physical LAN interfaces or separate VLAN sub-interfaces providing connectivity to multiple routed networks. Following [i.1] there should be one IPv4 or IPv6 address for traffic assigned per SVN-MAC label. Right now, IPv6 addresses are not considered in this descriptor. LL specification does not include any provision for IPv6 addresses as SVN interface address, even if it is required that the terminal should be capable of transmitting and receiving IPv6 traffic. This configuration could be solved by HLS new descriptors or other means of configuration. Higher layer initialization description information should be persistent across RCST restart and reboot. The Network Layer Info descriptor (if access status indicates that the HL are not initialized this descriptor may be included in the TIMU message) provides a mechanism by which network level information can be passed (transparently through the lower layers) to the Management Plane of the RCST during, or prior to, the start-up configuration phase of logon. The message body datagram will take the form of an SNMP message, and will be formatted according to [i.69] and [i.70], and the PDU type should be a SetRequestPDU. To complete the HL configuration and according to the HL capabilities, the NCC will use the NLID. The minimum set of NLID parameters should cover: • multicast mode: forwarding enabled/disabled, IGMP proxy, IGMP querier, MLD, etc., for each traffic interface. • QoS default configuration: default HL service, default IP classification table entries. • Default OSPF configuration for each VRF group. Alternatively these parameters could be sent by configuration file (SDDP) or using the multicast stream specified in the HLID (for the moment this stream is only used for PEP negotiation). These methods could also be used if additional HL configuration is required. After the terminal has been commissioned and its Higher Layers initialized, the SVNO could, at any given time, put the RCST "HL Maintenance" mode (i.e. set the HL initialized flag in the state MIB group to 0, will re-send the NLID with the new configuration, and when finished, set back the flag to HL initialized. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.3.1.1 NLID fields | |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.3.1.1.1 Multicast | In the HL capabilities, the RCST indicates whether it supports dynamic multicast or not: • dynamic multicast not supported. Enabling multicast reception in the SVN1 (in this example, the LAN interface only supports IPv4) of an RCST will imply creating a new row in the dynamic table vrfGroupTable: - vrfGroupIndex: 1 (1st row) - vrfGroupSVNnumber: 1 (configured by SNO in the NMC) - vrfSVNMAClabel: SVN1 (Octet string) - vrfGroupIfInterface: 1 (LAN interface number) - vrfGroupSVNMAC: RCST SVN-MAC of the LAN interface - vrfSVNmtu: 1500 - vrfGroupIfInterface: LAN interface number ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 100 - vrfOSPFrouting: Enabled - vrfOSPFrouterAddressType: IPv4 - vrfOSPFrouterAddress: DR Address (IP RCST-GW) - vrfOSPFrouterPrefix: DR IP prefix - vrfMulticastMappingMethod: MMT2 method - vrfMulticastFwd: Enabled - vrfMulticastRtn: Disabled - vrfIgmpVersion: IGMPv2 - vrfIgmpQuerierLAN: Enabled - vrfIgmpProxy: Disabled - vrfIgmpQuerierSAT: Disabled - vrfIgmpForward: Disabled - vrfPimSM: Disabled - vrfMldQuerierLAN: Disabled - vrfMldProxy: Disabled - vrfMldQuerierSAT: Disabled - vrfMldForward: Disabled - vrfGroupStatusRow: createAndGo • dynamic multicast supported: - flag vrfIgmpProxy needs to be enabled - vrfOSPFrouterAddress and vrfOSPFrouterPrefix can be left empty and values can be dynamically taken by OSPF |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.3.1.1.2 QoS default configuration | There are three QoS table in the RCST MIB: IPClassTable, HLServiceTable, and LLserviceTable. The NLID could configure, in the HL initialization phase, entries in the IPClassTable and in the HLServiceTable. It is important that the IPClassHLSAssociation value corresponding to the default (match-all) IP class entry matches one existing HLServiceIndex. The entry in the IPClassTable is used to compile all types of IP traffic: • IPClassTable • IPClassEntry • IPClassIndex: 1 • IPClassDscpLow: 0 • IPClassDscpHigh: 63 • IPClassDscpMarkValue: 0 • IPClassIPProtocol: 255 (match all) ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 101 • IPClassSrcInetAddressType: ipv4(1) • IPClassIPSrcInetAddress: 0.0.0.0 • IPClassSrcInetAddressPrefixLength: 0 • IPClassDstInetAddressType: ipv4(1) • IPClassIPDstInetAddress: 0.0.0.0 • IPClassIPDstInetAddressPrefixLength: 0 • IPClassSrcPortLow: 0 • IPClassSrcPortHigh: 65535 • IPClassDstPortLow: 0 • IPClassDstPortHigh: 65535 • IPClassVlanUserPri: -1 (selectivity is inactive) • IPClassVLANID: -1 (match any VLAN identifier) • IPClassHLSAssociation: 1 • IPClassAction: 1 (forward de packet) • IPClassOutOctets: Read-only • IPClassOutPkts: Read-only • IPClassRowStatus: createAndGo (the new row will become active after creation) Here follows an example of an HLServiceTable entry (the parameters followed by a question mark are for the SNO to decide): • HLServiceTable • HLServiceEntry • HLServiceIndex: 1 • HLserviceLLServiceAssociation: 1 (should be coherent with the LLServiceTable index) • HLservicediffPolicyPHBindex: 0 (default PHB) • HLservicePHBname: Default • HLservicePriority: 0 • HLserviceMinRate: 0 Kbps • HLserviceMaxRate: 2 000 Kbps • HLserviceMaxIngressBurst 4000 • HLlserviceMinIngressBurst 20 • HLserviceMaxEgressBurst 4000 • HLserviceMaxDelay 30 sec. • HLserviceQueueType: FIFO (0) • HLserviceL3IfNumber: 1 (RCST LAN/VLAN interface) ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 102 • MaxLatency: 5 sec. • LinkRetransmissionAllowed: packet retransmission not allowed (0) • HLServiceRowStatus: createAndGo (the new row will become active after creation) |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.3.2 RCST commissioning | The access status of the RCST for a first logon after antenna alignment would be '0001'. Not till the higher layers have been initialized, and minimum RCST configuration is set, the RCST should change its status to HL initialize and commissioned, i.e. access status = 1111. This status is firstly set by the NCC during the logon. The RCST commissioning and configuration is normally done during installation by RCST configuration file and is completed during logon thanks to the information provided in the TIM-U logon response message. However, if the commissioned-ok flag is not set, the RCST may block network forwarding of user traffic to/from the LAN interface. This allows further IP configuration. The RCST completes the configuration by enabling traffic forwarding when the commissioned-ok flag is set (e.g. by loading a new configuration or direct action to raise the flag). The RCST can indicate that the status is "confirmed-commissioned" to the NCC if that NCC has previously indicated that the RCST has been commissioned (e.g. in a restart scenario), and the RCST has not, in the meanwhile, been re- commissioned towards another system or it has lost the previous alignment. If any of the latter occurs, the RCST should indicate that it is "not confirmed commissioned" in the logon request sent to the NCC. This allows the NCC to consider commissioning before allowing the RCST into the network. The RCST commissioning status is reflected in the MIB state group. The status can remotely be checked by the SNO or SVNO. After a successful commissioning status, the SVNO could decide to change the configuration of the terminal. For this, the SVNO should first change the commissioning status and then update the configuration of the terminal (e.g. by means of SNMP commands or new configuration file). |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 11.3.3 Logon and commissioning example | More details on the logon procedure are provided in Figure 11.1. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 103 RCST NCC Physical layer acquisition Receive NIT, RMT, NCR, SPT, SCT, FCT2, BCT, TIM-B, TBTP2... Logon Request (CSC) TIM-U HLID Control Burst CMT TRF TIM-U Logon Rsp SDDP NCC RCST TIM-B with Lowest Software Version descriptor. RCST checks descriptor SW version against its operational SW version: if sufficient it can proceed with logon TIM-B with NO Pointing Alignemt Suppot descpritor entry_type == 0x1, binding user to HW and network, LSB of access_status is 1, indicating that the NCC has confirmed pointing alignment TIM-U with Logon Response descriptor including GrID, LogonID, SVN MACs, access status == 0011 indicating, pointing alignment confirmed, user associated with RCST, Higher Layers not initialised, not comissioned TIM-U with Higher Layers Initialisation descriptor including m&c_addresses and PEP negot info for the RCST SVNs TIM-U NLID TIM-U with Network Layer Info descriptor including multicast mode, QoS deffault configuration & OSPF deffault configuration RCST updates the State group of the MIB with HL initialised (dvbRcs2Comission edStatus field) TDMA Sync SDDP with new configuration file. Once the new configuration is loaded, the RCST updates the State group of the MIB with confirmed comissioned (dvbRcs2ComissionedStatus field) RCST updates the State group of the MIB with confirmed comissioned SVNO sets the HL flag to not initialised in the dvbRcs2ComissionedStatus field of the State group of the MIB SNMP TIM-U NLID TIM-U with Network Layer Info descriptor including multicast mode, QoS deffault configuration & OSPF deffault configuration SNMP SVNO sets the HL flag to not initialised in the dvbRcs2ComissionedStatus field of the State group of the MIB Figure 11.1: Logon and commissioning sequence ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 104 12 OSS-NMC interface and performance management guidelines Network operators are deploying a range of different sub-networks to meet different demands in the telecommunications market (e.g. a combination of fixed broadband networks and satcom networks to provide internet to both urban and remote locations including the maritime segment). At the same time, sub-networks serving more or less the same purpose are gradually replacing each other over time, still living in parallel for some time (e.g. GSM, WCDMA, and LTE networks serving mobile communication). On top of this, especially in more dynamic, new markets, operators are growing by acquiring competitor networks, thus adding sub-networks of the same technology, but from different vendors to its operations. In order to provide high-quality service at reasonable costs, operators will continuously aim to streamline an efficient and effective network operations organization. These will typically be organized with a Call Center (Level 1), 1st Line Technical Support (level 2), and Specialist Technical Support (Level 3). Ideally, these organizational units would be the same for all operated sub-networks. However, due to required skill- levels (technology- and tool-wise), the operator often runs parallel organizational units doing the same job on different sub-networks/technologies. This clause presents a methodology for standardized integration between OSS and the Network Management Center (NMC) of the satellite-based access network. The methodology makes use of existing 3GPP specifications. This may enable the re-use of the OSS applications that are already aligned with 3GPP in the terrestrial mobile networks. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.1 OSS applications in mobile network operations | OSS applications used for operating mobile networks (e.g. GSM, WCDMA, and LTE) closely follow the PLMN (Public Land Mobile Network) management architecture, which is defined by the 3GPP (see [i.40] and [i.41]). The 3GPP PLMN management architecture is based on ITU-T TMN (Telecommunications Management Network standard from the ITU-T) which again can be seen as a refinement of the ISO FCAPS model. The five management functions of FCAPS (Fault, Configuration, Accounting, Performance, and Security) are still visible among the list of management functions of the 3GPP PLMN management architecture: • Performance management • Roaming management • Fraud management • Fault management • Security management • Software management • Configuration management • Accounting management • Subscription management • Quality of Service (QoS) management A PLMN is often composed of equipment from a range of vendors. In order for integration to be successful, 3GPP proposes the use of Integration Reference Points (IRP) between Network Elements (NEs) and management functions. Figure 12.1 (from [i.41]) shows how Elements Manager (EM) and Network Manager (NM) should implement the IRP. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 105 NEs EM IRPAgent IRPManager NM management interface (e.g. Itf-N) Supported IRP(s) Figure 12.1: 3GPP IRPs used in network element management XML is commonly used to transfer measurement results from Network Elements to the OSS as part of the Performance Management (PM). 3GPP has specified a PM XML file format in [i.42]. The PLMN management architecture can be re-used to a large extent in network operations with DVB-RCS2 satellite access. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2 Performance management concept | Performance Management (PM) aims to evaluate network behaviour. The physical and logical states of Network Elements (NEs) are measured and reported in data collected by the Element Manager (EM) function. This may be done according to some pre-defined time schedule. Measurement data should be generated by NEs to meet the following purposes: • measure the amount of user data and signalling traffic; • verify the network configuration; • measure the Quality of Service perceived by the user (e.g. throughput, round-trip-time, set-up time, etc.); • measure resource availability and access control. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2.1 Measurement jobs | Measurement jobs executed in NEs are defined in the EM function. The definition includes scheduling the timing/frequency of measurement job execution, which specific data to measure/collect, and which (sub) components of the NE the measurement is valid for. It should be possible to manage the measurement jobs in the EM. This entails the ability to start/stop/suspend/resume measurement jobs, and to view measurement jobs and their current status. It should be possible to practically manage easily the many different measurement jobs in the network. This includes the ability to schedule the same measurement job "for all" NEs of a certain group or category (e.g. define the same measurement job to take place in all RCSTs). |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2.2 Measurement results generation and storage | Each measurement job produces a number of results. The results should be contained in a measurement report associated with the measurement job. Measurement result data needs to be kept in local storage in the NE or EM until it has been received by the NMC and OSS. Storage capacity and the duration for which data will be available locally at the NE or EM is implementation and operator dependent. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 106 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2.3 Measurement results transfer | Measurement results are transferred from the NE to the EM and NMC for storage, post-processing, and presentation in the OSS. There may be more than one OSS monitoring the same network, and serving multiple Satellite Network Operators (SNOs) and/or Satellite Virtual Network Operators (SVNOs). Therefore, results may need to be transferred to multiple destinations. Measurement reports may be transferred from the NE to the EM in one of two ways: a) notification-based transfer of reports when these are available, b) on-demand transfer of reports when the EM (periodically) request these. The measurement reports should be transferred from EMs to the NMC via bulk file transfer. The NMC may store the files for a specified period of time (e.g. one hour) where it is available for the OSSs to collect them. Alternatively, the NMC may keep track of each destination OSS, notify these when report files are available, and remove these once all OSSs have notified the NMC that the reports have been processed. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2.4 Measurement report XML file format | Measurement report files may be stored in a well-defined XML file format aligned with 3GPP. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2.4.1 3GPP XML file format | Table 12.1 shows XML tags specified by 3GPP. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 107 Table 12.1: XML tags used for performance measurement report example XML tag Description measCollecFile fileHeader measData fileFooter fileHeader fileFormatVersion fileHeader dnPrefix and fileSender localDn For the XML schema based XML format, the DN is split into the DN prefix and the Local DN (LDN) (see [i.43]). XML attribute specification "dnPrefix" may be absent in case the DN prefix is not configured in the sender. XML attribute specification "localDn" may be absent in case the LDN is not configured in the sender. fileSender elementType For the XML schema based XML format, XML attribute specification "elementType" may be absent in case the "senderType" is not configured in the sender. fileHeader vendorName For the XML schema based XML format, XML attribute specification "vendorName" may be absent in case the "vendorName" is not configured in the sender. measCollec beginTime managedElement managedElement userLabel For the XML schema based XML format, XML attribute specification "userLabel" may be absent in case the "nEUserName" is not configured in the CM applications. fileHeader dnPrefix and managedElement localDn For the XML schema based XML format, the DN is split into the DN prefix and the Local DN (LDN) (see [i.43]). XML attribute specification "localDn" may be absent in case the LDN is not configured in the CM applications. managedElement swVersion For the XML schema based XML format, XML attribute specification "swVersion" may be absent in case the "nESoftwareVersion" is not configured in the CM applications. measInfo measInfoId granPeriod endTime job jobId granPeriod duration For the XML schema based XML format, the value of XML attribute specification "duration" should use the truncated representation "PTnS". repPeriod duration For the XML schema based XML format, the value of XML attribute specification "duration" should use the truncated representation "PTnS". measTypes or measType For the XML schema based XML format, depending on sender's choice for optional positioning presence, either XML element "measTypes" or XML elements "measType" will be used. measValue measValue measObjLdn measResults or r For the XML schema based XML format, depending on sender's choice for optional positioning presence, either XML element "measResults" or XML elements "r" will be used. suspect measCollec endTime measType p An optional positioning XML attribute specification of XML element "measType" (XML schema based), used to identify a measurement type for the purpose of correlation to a result. The value of this XML attribute specification is expected to be a non-zero, non- negative integer value that is unique for each instance of XML element "measType" that is contained within the measurement data collection file. r p An optional positioning XML attribute specification of XML element "r", used to correlate a result to a measurement type. The value of this XML attribute specification should match the value of XML attribute specification "p" of the corresponding XML element "measType" (XML schema based). ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 108 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2.4.2 Schema for performance measurement XML file format | XML schema, measCollec.xsd, specified in [i.42] may be used for this purpose. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.2.4.3 Example measurement report file in XML format | The following shows an example measurement report file in the XML format: <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="MeasDataCollection.xsl"?> <measCollecFile xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec"> <fileHeader fileFormatVersion="32.435 V7.0" vendorName="Company NN" dnPrefix="DC=a1.companyNN.com,SubNetwork=1,IRPAgent=1"> <fileSender localDn="SubNetwork=CountryNN,MeContext=MEC-Gbg-1,ManagedElement=RNC-Gbg-1" elementType="RNC"/> <measCollec beginTime="2000-03-01T14:00:00+02:00"/> </fileHeader> <measData> <managedElement localDn="SubNetwork=CountryNN,MeContext=MEC-Gbg-1,ManagedElement=RNC-Gbg- 1" userLabel="RNC Telecomville"/> <measInfo> <job jobId="1231"/> <granPeriod duration="PT900S" endTime="2000-03-01T14:14:30+02:00"/> <repPeriod duration="PT1800S"/> <measTypes>attTCHSeizures succTCHSeizures attImmediateAssignProcssuccImmediateAssignProcs</measTypes> <measValue measObjLdn="RncFunction=RF-1,UtranCell=Gbg-997"> <measResults>234 345 567 789</measResults> </measValue> <measValue measObjLdn="RncFunction=RF-1,UtranCell=Gbg-998"> <measResults>890 901 123 234</measResults> </measValue> <measValue measObjLdn="RncFunction=RF-1,UtranCell=Gbg-999"> <measResults>456 567 678 789</measResults> <suspect>true</suspect> </measValue> </measInfo> </measData> <fileFooter> <measCollec endTime="2000-03-01T14:15:00+02:00"/> </fileFooter> </measCollecFile> 12.3 Recommendations for DVB-RCS2 performance measurements Performance measurements should meet the purpose of enabling the operator (SNO or SVNO) identify network elements with degraded performance as well as the root cause for degraded performances. In summary, performance measurements should meet these requirements: • Enable operator staff to discover degraded performance: - Service accessibility. - Service retainability. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 109 - Quality of service. • Enable operator staff to isolate the root cause of degraded performance. • Re-use existing DVB-RCS specifications (in particular, the DVB RCS2 MIB). • Align with principles and specifications published by other telecommunications fora. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.3.1 Performance measurements | Performance measurements presented here adhere to the principles in 3GPP performance measurement specifications (e.g. [i.44]). Each measurement monitors/measures/counts a certain aspect of performance and has an obvious relation to other measurements such that comparable Key Performance Indicators (KPIs) can be defined. Typically, it is desirable to scan the network on "success rates" on certain procedures in the network (e.g. the RCST logon procedure) in order to determine poorly performing network elements. Thus, it is necessary to count both the number of attempts and successes of the procedure. In order to isolate the root cause, it is also desirable to count the number of "failures" due to different causes when known. For performance measurements monitoring a signal, it is desirable to measure both the transmitted signal strength, the received signal strength, and the quality/accuracy of the received signal in order to determine high losses or interference. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.3.2 Impact on DVB-RCS2 | This clause presents a minimum set of performance measurements, which may be extended by additional vendor- specific measurements. All performance measurements should be made available to the NMC/OSS through the mechanisms defined in clause 12.1. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4 Recommended performance measurements for DVB-RCS | In the following, measurements are defined for RCSTs in a DVB-RCS2-based satellite communications network. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.1 Managed object classes | Although all measurements are done at RCST level, some will be done remotely at the RCST whereas others can be done at the central hub (NCC). The overall goal is to provide a sufficient set of measurements that enables efficient network monitoring where operations staff can easily compare measurements for all RCSTs across the network, no matter the equipment provider. To separate remote and central measurements, the following assumes two different managed object classes, both representing RCSTs: • RCSTRemote • RCSTHub Each corresponds to an Element Manager (EM) representing different aspects of the RCST Network Element (NE). |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.2 Measurement specification format | All measurements in the following are presented in the following structure: • Textual description • Collection Method (CC=Cumulative Counter, GAUGE, DER=Discrete Event Registration, SI=Status Inspection) • Condition: The specific details/events causing an update to the measurement result ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 110 • Measurement units (e.g. seconds) • Measurement identifier (as used in measurement result files) • Managed object class (e.g. RCST) • Technology generation (e.g. RCS2) |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3 RCST accessibility | |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.1 Number of Attempted Logons | • This measurement provides the number of attempted logons using DA and RA • CC • Receipt of a Logon burst (DA or RA) by the NCC from the RCST • Each measurement is an integer value. • RCST.AttLogon.DA RCST.AttLogon.RA • RCSTHub • RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.2 Number of Rejected Logons | • This measurement provides the number of rejected logons for an RCST for different causes (RESOURCE = no resource, ACCOUNT = account is valid or paid, OTHER) • CC • Transmission of a TIM-U message indicating rejected logon by the NCC to the RCST • Each measurement is an integer value. • RCST.RejLogon.RESOURCE RCST.RejLogon.ACCOUNT RCST.RejLogon.OTHER • RCSTHub • RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.3 Number of Acknowledged Logons | a) This measurement provides the number of acknowledged logon attempts a) CC b) Transmission of a TIM-U message indicating acknowledged logon by the NCC to the RCST c) Each measurement is an integer value d) RCST.AckLogon e) RCSTHub f) RCS2 ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 111 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.4 Number of Successful Logons | a) This measurement provides the number of successful logon attempts b) CC c) Receipt of a control burst message following logon acknowledgement by the NCC from the RCST d) Each measurement is an integer value e) RCST.SucLogon f) RCSTHub g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.5 Number of Failed Logons | a) This measurement provides the number of failed logon attempts b) CC c) Either: No receipt of a control burst message following logon acknowledgement by the NCC from the RCST, Or: Receipt of another logon burst (DA or RA) by the NCC from the RCST, indicating that the RCST has not received a TIM-U message with logon acknowledgement d) Each measurement is an integer value e) RCST.FailLogon f) RCSTHub g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.6 Number of Logoffs | a) This measurement provides the number of logoffs of different logoff causes specified in [i.3] b) CC c) Logoff message sent to RCST by NCC or autonomous silent logoff as per the logoff procedure described d) Each measurement is an integer value e) RCST.Logoff.NCC RCST.Logoff.USER RCST.Logoff.AUTO RCST.Logoff.STANDBY RCST.Logoff.SYNC RCST.Logoff.FREQ RCST.Logoff.INTERNAL RCST.Logoff.OTHER f) RCSTHub g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.7 Forward Link Bit Error Rate | a) This measurement provides the RCST Bit Error Rate (BER) of the Forward Link b) SI c) The average BER of the Forward link at the RCST within the granularity period ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 112 d) The result is an integer (0..63) where the meaning is: 0: BER = 0 1: -infinity < Log10(BER) < -6.1 2: -6.1 <= Log10(BER) < -6.0 ... 61: -0.3 <= Log10(BER) < -0.2 62: -0.2 <= Log10(BER) < -0.1 63: -0.1 <= Log10(BER) e) RCST.FwdBER f) RCSTRemote g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.8 Forward Link Carrier-to-Noise Ratio | a) This measurement provides the RCST Carrier-to-Noise Ratio (CNR) of the Forward Link b) SI c) The average CNR of the Forward link at the RCST in 0,1 dB units within the granularity period d) 0,1 dB e) RCST.FwdCNR f) RCSTRemote g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.9 Forward Link Received Power | a) This measurement provides the Forward Link Rx Power in the RCST b) SI c) The average RX Power of the Forward link at the RCST in 0,1 dBm units within the granularity period d) 0,1 dBm e) RCST.FwdRxPower f) RCSTRemote g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.10 Return Link Received EbN0 | a) This measurement provides the Return Link EbN0 of the RCST measured in the hub b) SI c) The average EbN0 of the Return link of the RCST in 0,1 dB units within the granularity period d) 0,1 dB e) RCST.RtnEbN0 f) RCSTHub g) RCS2 ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 113 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.11 Return Link Transmitted EIRP | a) This measurement provides the Return Link EIRP of the RCST b) SI c) The average EIRP of the Return link in the RCST in dBW within the granularity period d) dBW e) RCST.RtnEIRP f) RCSTRemote g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.12 Number of Capacity Requests | a) This measurement provides the number of solicited capacity requests sent by the RCST of the different capacity categories b) CC c) Receipt of capacity request by the NCC from the RCST d) Each measurement is an integer value e) RCST.CapacityRequests.VBDC RCST.CapacityRequests.RBDC RCST.CapacityRequests.AVBDC f) RCSTHub g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.13 Number of Rejected VBDC Capacity Requests | a) This measurement provides the number of rejected VBDC capacity requests of different causes b) CC c) Evaluation by the NCC of a VBDC capacity request from the RCST where the capacity request is not met due to the following causes: d) The capacity request backlog is full e) The capacity request has expired f) Resources are not available to satisfy the capacity request g) Other reason h) Each measurement is an integer value i) RCST.VBDCCapacityRequestsFail.BACKLOG RCST.VBDCCapacityRequestsFail.EXPIRED RCST.VBDCCapacityRequestsFail.RESOURCE RCST.VBDCCapacityRequestsFail.OTHER j) RCSTHub k) RCS2 ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 114 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.14 Number of Rejected RBDC Capacity Requests | a) This measurement provides the number of rejected RBDC capacity requests of different causes b) CC c) Evaluation by the NCC of a RBDC capacity request from the RCST where the capacity request is not met due to the following causes: d) The capacity request backlog is full e) The capacity request has expired f) Resources are not available to satisfy the capacity request g) Other reason h) Each measurement is an integer value i) RCST.RBDCCapacityRequestsFail.BACKLOG RCST.RBDCCapacityRequestsFail.EXPIRED RCST.RBDCCapacityRequestsFail.RESOURCE RCST.RBDCCapacityRequestsFail.OTHER j) RCSTHub k) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.15 Number of Rejected AVBDC Capacity Requests | a) This measurement provides the number of rejected AVBDC capacity requests of different causes b) CC c) Evaluation by the NCC of a AVBDC capacity request from the RCST where the capacity request is not met due to the following causes: d) The capacity request backlog is full e) The capacity request has expired f) Resources are not available to satisfy the capacity request g) Other reason h) Each measurement is an integer value i) RCST.AVBDCCapacityRequestsFail.BACKLOG RCST.AVBDCCapacityRequestsFail.EXPIRED RCST.AVBDCCapacityRequestsFail.RESOURCE RCST.AVBDCCapacityRequestsFail.OTHER j) RCSTHub k) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.16 Return Link Throughput | a) This measurement provides the total return link throughput of different capacity categories b) CC c) Sum of the throughput on all channels (all timeslots) in granularity period measured at the NCC d) Kilobit ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 115 e) RCST.RtnThroughout f) RCSTHub g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.17 Return Link Allocated Throughput | a) This measurement provides the return link throughput at different capacity categories b) CC c) Sum of allocated throughput on all channels in granularity period for the different capacity categories d) Kilobit e) RCST.RtnAllocThroughput.CRA RCST.RtnAllocThroughput.FCA RCST.RtnAllocThroughput.VBDC RCST.RtnAllocThroughput.RBDC RCST.RtnAllocThroughput.AVBDC f) RCSTHub g) RCS2 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 12.4.3.18 Return Link Unused CRA Capacity | a) This measurement provides the return link unused CRA capacity b) CC c) Unused, available CRA capacity in the granularity period d) Kilobit e) RCST.RtnCRACapacityUnused f) RCSTHub g) RCS2 13 Dynamic connectivity protocol guidelines for mesh regenerative systems Dynamic connectivity is supported in RCS2 thanks to the Dynamic Connectivity Protocol (DCP) as specified in Annex E of [i.1]. DCP is a control signalling protocol between the NCC and the RCST. This protocol is used when IP connectivity with the NCC is achieved after RCST logon and allows the mapping of IP parameters and policies to L2 parameters, and to dynamically set one or several mesh links within connectivity channels to an RCST according to set of values configured by L2S or management. Mesh RCSTs (transparent or regenerative) support DCP protocol for mesh link establishment for DVB-RCS2 in Mesh Regenerative systems and Mesh overlay systems. This clause introduces some recommendations on the usage of DCP over Mesh Regenerative Systems. The Mesh System Descriptor (with tag 0xE1) is provided by the NCC in the TIM-B message. This descriptor indicates: • whether or not the system is ready to process dynamic connectivity logon requests, and • a list of frames that may be used for mesh traffic, for each superframe used for mesh. Note that if the descriptor length is '0', then all frames can be used for mesh traffic. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 116 The NCC may assume that the listed set of frames constitutes the RPLS for all the mesh receivers that are using the superframe. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.1 DCP messages | The minimum set of messages to implement a valid DCP in a Mesh regenerative system is: • Link Service Establishment Request by RCST • Link Service Establishment Response by NCC • Link Service Establishment Request by NCC • Link Service Establishment Response by RCST • Link Service Release Request • Link Service Release Response • Acknowledgement The rest of the messages are optional, and are described in the [i.1] document. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.1.1 DCP logon | The DCP Logon procedure can be started when IP connectivity with the NCC is achieved. It permits the mapping of IP parameters and policies to L2 parameters. It also allows to dynamically set connectivity channels to an RCST according to the set of values configured by management and L2S. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.1.1.1 RCST DCP successful logon | A successful DCP Logon is achieved when the RCST receives confirmation by the NCC. The procedure is illustrated in Figure 13.1. Figure 13.1: Successful logon ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 117 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.1.1.2 RCST DCP failed logon | DCP logon may fail due to rejection from the NCC or due to DCP message loss(es). This is illustrated in Figure 13.2. Figure 13.2: Failed logon |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.1.2 RCST DCP connections procedures | The basic dynamic connectivity procedures supported by a regenerative mesh RCST include: • RCST-initiated bidirectional connections • RCST-initiated unidirectional multicast connections • NCC-initiated bidirectional connections • NCC-initiated unidirectional multicast connections RCST sends a LINK SERVICE ESTABLISHMENT REQUEST message upon receiving at its LAN interface an IP packet that cannot be mapped to an existing connection. More specifically, two triggers are listed below identifying the conditions under which the LINK SERVICE ESTABLISHMENT REQUEST messages is sent: • addressing/routing trigger, if the packet matches an existing flow type (with defined IP CoS/PHB), but its next hop IP destination address does not match any of the existing connections; • QoS trigger, if the packet's IP CoS/PHB does not match the service used in an existing connection using the same next hop IP address. A packet can be forwarded to an active connection only when it is addressed to the same destination RCST and if its associated LL service matches that of the active connection. The RCST sends a LINK SERVICE RELEASE REQUEST message for those active connections not carrying traffic in either direction after a configurable timeout. Upon receiving a LINK SERVICE RELEASE REQUEST, an RCST sends a LINK SERVICE RELEASE RESPONSE to the peer RCST as acknowledgement of the request. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 118 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.1.2.1 RCST DCP successful unicast connection | A successful unicast connection establishment procedure is described in Figure 13.3. Figure 13.3: Successful unicast connection ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 119 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.1.2.2 RCST DCP successful multicast connection | Figure 13.4: Successful multicast connection |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.2 DCP-enabled RCST state machines | A DCP-enabled RCST should implement at least the DCP Logon and unicast/multicast connection setup procedures. Following clauses describe these state machines. The RCST should also be assigned in its MIB the configurable timeouts and number of retries expressed in the figures. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.2.1 DCP logon | Figure 13.5 shows the state machine for DCP logon. If a DCP LOGON RESPONSE is not received in the wait_for_Response state, the RCST may retry the request for a configurable number of times. The RCST should go to the initial state after a configurable Timeout_T0. Figure 13.5: DCP logon state machine ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 120 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.2.2 DCP unicast connection | Figures 13.6 and 13.7 show state machinesrun fora connection establishment sequence for the initiating terminal and the peer terminal, respectively. The number of retries and configurable timers are expressed in the figure and should be assigned appropriate values in the RCSTs MIB. Figure 13.6: Unicast connection setup in the initiating terminal ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 121 Figure 13.7: Unicast connection setup in the peer terminal |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.2.3 DCP multicast connection | The multicast connection setup state machine is similar to the unicast connection setup state machine with some different procedures and parameters. This state machine is shown in Figure 13.8. Figure 13.8: Multicast connection setup in the initiating terminal ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 122 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.2.4 DCP routing procedures | The DCP protocol performs unicast/multicast address resolution and routing functions, specifically for meshed systems. If the next hop IP address of an outgoing packet is not found in the AR database, a DCP connection establishment request is triggered by the RCST to find the L2 address of the next hop. In case the system does not support the dynamic routing function (e.g. OSPF), the DCP protocol can assist the RCST with IP routing information. The NCC does not allow DCP connections across different SVNs or VRF domains. The RCST may indicate in the request message the next hop IP address (Next hop address field in the Triggering datagram identifier IE) according to its RIB. When this field has been filled by the RCST and the NCC cannot identify the destination RCST from the triggering packet destination address, then the NCC should use the address of the next hop field to obtain the MAC24 address and the FPDU identifiers corresponding to the peer RCST. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 13.2.5 Other possible DCP functionalities | DCP is also a complement to the functionality of the interfaces already defined in the DVB-RCS2 and DVB-S/S2 standards. Other functions that may be added by the DCP protocol for DVB-RCS2 control plane can be summarized as: • QoS-driven dynamic allocation of bandwidth resources connectivity channels, following the execution of a Connection Admission Control (CAC) function. • Dynamic control of the communicating parties in the DVB-RCS2 system, via configuration parameters and policies. • Dynamic allocation/assignment of logical resources to allocation channels. • Definition of isolated and independent satellite sub-networks within the global interactive network (i.e. each subnetwork is characterized by its own terminal population, bandwidth resources, addressing space/plan). |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14 Transparent mesh overlay networking | Table 14.1 presents some terminology specifically used in this clause. Table 14.1: Additional terminology for transparent mesh overlay networks Term Definition Link In the IP communication context this refers to a data link as a sub-IP Connection that can be used for submission of IP traffic destined to a specific range of IP addresses; in the satellite communication context a connection via satellite connecting parts of the ground segment. Behaviour Aggregate Traffic aggregate that gets unified treatment regarding the transport over a link. Link QoS Class Traffic classification recognized by the RCST. Link Service The set of policies used to implement a certain Link Behaviour or Link Behaviour Group for a specific link. Link Stream Stream of consecutive PPDUs over a link carrying a consecutive stream of ALPDUs. Link Behaviour The characteristics of a Link Behaviour Aggregate related to the transport over the link. Link Behaviour Group A set of Link Behaviours that have specific common policies related to the transport over the link. Receiver Physical Layer Segment A part of the physical layer monitored in its entirety by an associated receiver, as seen from the transmitter side. Request Class Resource request classification recognized by the MF-TDMA resource controller. Link Interface A sub-interface of the satellite interface. It can be used to reach a subset of the link receivers that can be reached via the satellite interface. Dynamic Connectivity Protocol (DCP), which is specified in [i.1], aims to support mesh overlay networking in combination with star topology in the same network. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 123 Five link types can be identified in the applicable networks: 1) Bi-directional link between mesh RCSTs using MF-TDMA 2) Unidirectional link from an RCST to the hub GW using MF-TDMA 3) Unidirectional link from the hub Feeder to an RCST using TDM 4) Unidirectional link from the hub Feeder for transport of multicast with the TDM 5) Unidirectional link from an RCST for transport of mesh multicast using MF-TDMA The link types 2 and 3 are the existing link types used in forward and return direction in a star DVB-RCS2 system. The link type 1 is a mesh link where a mesh RCST is not only able to send MF-TDMA bursts, but it is also capable of receiving them. Link types 4 and 5 are additions that support multicast. The main extensions to DVB-RCS2 to provide mesh overlay networking are identified here: • Each mesh-capable RCST is equipped with a DVB-RCS2 compatible burst receiver, possibly a wideband multi-carrier receiver, to receive MF-TDMA burst transmissions from other mesh RCSTs. This receiver operates concurrently with the DVB-S2 compliant receiver for the reception of the TDM Forward Link from the Feeder. • The router within each RCST is extended to support IP routes for use within its Mesh Satellite Subnet. • The RCST supports DCP client part, enabling on-demand mesh link establishment. • The Network Control Centre is enhanced with a Mesh Controller, which implements the server part of the DCP, and which is responsible for mesh link management and control, as well as mesh routing. Full mesh networking is created by enabling mesh links between RCSTs on demand. This demand is traffic initiated and it is expressed as a link request to a Mesh Controller containing sufficient information so that the Mesh Controller can identify the correct link destination, IP hosts reachable via this destination and the applicable link service specification. The mesh RCSTs need to be registered or logged on to the Mesh Controller in order to send the link request. How the request will be treated by the Mesh Controller depends on the destination, whether it can be reached over a mesh link, the receiver state, the state of the link service (permanently or temporarily blocked or not) et cetera. After receipt of a valid link request (no erroneous data, the receiver up and logged on), the Mesh Controller will attempt to establish the link service for the opposite traffic direction as applicable for the link service requested. The establishment of the opposite direction should at least have progressed to either the "link service established" or "link service blocked" state before the initiating traffic arrives at the destination RCST. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.1 Networking principles | A mesh capable RCST first logs on to the NCC as a DVB-RCS2 RCST and then logs on to the Mesh Controller as a DCP client. The RCST provides its IP addresses applicable for mesh routing in the DCP logon request. The DCP server in the Mesh Controller includes this information in a common mesh routing table for a Mesh Satellite Subnet within the Super-frame. If the set of attached IP addresses changes, the RCST will clear all dynamic links and routes, and will logon to the MC again. A new DCP logon will update the MC routing entries related to the RCST. The permanent hub links and a default route to the hub are automatically established based on the DVB-RCS2 level logon response. This is sufficient to achieve star operation. A mesh capable RCST will only send a DCP logon message if the hub indicates mesh capability. A mesh capable RCST that either connects to a hub that does not support mesh networking or does not get response to its DCP logon message, will map all the satellite traffic to the permanent hub links. In the latter case, the RCST will reattempt DCP logon. The mesh default GWs, the IP address space to be accessed via the hub and the IP address space for mesh networking are set according to the DCP logon response, which occurs as a response to a DCP logon request issued any time after the DVB-RCS2 logon. The mesh default GW may be another mesh RCST and thus a dynamic link may be required to reach the mesh default GW; or it may be at the hub in which case the link to the default GW is permanent. An IP packet neither identified as mesh traffic nor identified as hub traffic is mapped to the mesh default GW (which can be either the hub or another mesh RCST). An IP packet for the satellite network maps either to a permanent hub link or to a dynamic link. Forwarding of traffic to the hub does not require link establishment control signalling. Temporary rerouting to hub may occur, and this requires the routing part of the link establishment control signalling. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 124 If an incoming packet is identified as mesh traffic it will eventually be mapped to a specific dynamic link. If a mapping to a specific dynamic link is not yet known, DCP is employed to establish the specific route entry and the specific link that will be used for the packet. The latter can be by association to an already established link, and the link establishment is then skipped. Packet forwarding may be rejected by the Mesh Controller and this packet and similar packets will then be discarded or blocked for a given period (proper ICMP could then be given to the source IP address). After this blocking period a similar packet will again trigger a link establishment attempt. The minimum attempt hold-off period to be used in this case is indicated in the logon response message, as one of the DCP system parameters. The link response message contains one of the link rejected values (since there can be several reasons for link reject) in the reason field. Traffic may be temporarily rerouted by the Mesh Controller, and the triggering packet and similar packets will then follow the new route for the lifetime of the route. After the expiration of the lifetime, the route will be cleared and a similar packet will again trigger a link establishment attempt, allowing a renewed routing decision. The Mesh Controller will provide explicit routing information to avoid that e.g. NMS traffic goes to the mesh default GW, when the default GW is a mesh RCST. This is achieved by informing the mesh RCST of the destination address space that applies to the hub link, so that the mesh RCST sets up permanent mapping to the permanent hub link for this address space. The hub can be the mesh default GW, or any mesh RCST can be used as mesh default GW. The applicable mesh default GW is identified by using the DVB IP address of the mesh RCST or the hub, as applicable. The RCST will set up a dynamic link to the mesh default GW when required. It is also possible to identify a secondary mesh default GW, which will be used in case the primary default GW cannot be reached. Traffic to a mesh default GW with an IP address outside the mesh address space and outside the local LAN address space is mapped to the permanent hub link, independent of the hub link address space. This link is the default route when no specific link can be found. A mesh default GW specification within the mesh destination address space (possibly, the user traffic interface address of the RCST that acts as mesh default GW) implies that a dynamic link is required to reach the mesh default GW. Further, the mesh default GW can be set to an IP address of the local LAN address space, used specifically at the RCST that acts as mesh default GW. This default GW IP address should be the address of the LAN side default GW to get into the WAN. The RCST should not default to route packets received from the MF-TDMA onto the MF-TDMA again. The assumed next-hop address is indicated, if known, in the link establishment request, if this address is already known to the RCST. If not, it will be set to all-zeros. The DCP server should not accept link establishment to the next-hop address if the next-hop address and destination address do not match the current network topology as known by the Mesh Controller. The RCST should then be instructed to clear the erroneous route entry. The RCST will clear any existing route entries which conflicts with the route entries conveyed to the RCST through the most recent call establishment signalling. (Note that overlapping routes may exist). |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.2 Mesh multicast | The mesh multicast addresses a RCST is allowed to forward, if any, are given in mesh Logon Response, as a part of DCP address space. RCST adds all received mesh multicast address to its multicast routing table when parsing Logon Response message. If a change in mesh multicast configuration occurs, RCST will be notified by DCP server using Link Service Establishment Request message with status/reason field indicating change of mesh multicast configuration (see table 9 for coding of the status). Mesh multicast addresses configured for the RCST will be given in Route Entries for link IE of the Link Service Establishment request. Content of other IEs of the message will not be applicable. Upon reception of this message, RCST will update its DCP address space and its multicast routing table by adding new multicast address and removing addresses no longer applicable. DCP server will repeat sending this LSE request message with mesh multicast change status until it receives a response or a number of outstanding responses has reached its limit. Link ID for this message will always be 0, while the service id will be the message identifier that RCST will have to use when replying to the message. Traffic to a mesh multicast address received at LAN side will initiate mesh link establishment, if an applicable route cannot be found, and the link will be granted if the QoS class the link is requested for is configured for the RCST. If not, link will be denied. TXID is assigned and may be the same as the TXID assigned for unicast. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 125 Update of mesh multicast configuration is not sent to RCST if there only has been change in the QoS class configured for the RCST. In that case, DCP server will release any existing mesh multicast link that is up and cannot longer be supported, and it will not allow establishment of a new link on not supported QoS link. On the receiver side, there is no mesh link establishment related to reception of mesh multicast traffic. Mesh multicast addresses and TXID are broadcasted in the MMT table, encoding the TXID in the elementary_PID field. On reception of IGMP join from LAN side, the RCST may open the receiver for the relevant TXIDs as required, if any is found in the MMT table for the subscribed multicast. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.3 RCST MF-TDMA transmitter | |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.3.1 RCST protocol architecture | Figure 14.1 illustrates with an example the principal protocol structure of a mesh RCST. Figure 14.1: Structure of the mesh RCST interfaces, showing concurrent link streams at each Link Interface The satellite interface is in the example in Figure 1 divided into 5 link interfaces (LI). Each LI supports here one or two concurrent link streams. Within a LI, there is one BA for each QoS. A BA maps to one LS of the associated LI. Several BAs using the LI may share a link stream (LS) as a single SA, or a solitary BA may have a dedicated LS. This is a policy choice at the transmitter side. There may be several BAs in use towards a mesh RCST at the same transmitter. LI0 connects to the hub. The associated BAs and LSes are for this LI automatically set up at DVB-RCS2 logon, independent of the MC and without involving DCP. The mesh RCST uses DVB-S2 TDM for LI0 reception and DVB- RCS2 MF-TDMA for transmission. LI1-LI4 each represents a satellite link to one or several mesh RCSTs in the mesh satellite subnet. This segregation is non-overlapping. These links are based on DVB-RCS2 MF-TDMA in both directions. Associated BAs and LSs are set up and released controlled by DCP signalling between the RCST and the MC. The LL Service (LLS) serves a single Link Behaviour (LB) or an LB group. The LLS is subject to certain policies of which some are inherited from the HL association, some are permanent, some are configured in advance, some are signalled through DCP and some are enforced by the resource controller. A system may use a separate Receiver Physical Layer Segment (RPLS) per satellite link destination or it may be based on sharing RPLS between several link destinations. The transmitter may in the latter case use shared BAs and shared LSes, merging the traffic aggregates for two or more destinations having the same RPLS into one LI. It can be assumed that any timeslot applicable for the RPLS can be used to reach the destinations monitoring the RPLS given that sufficient power and waveform can be used in the timeslot. An Assignment ID value points to only one RPLS. The use of timeslots with Assignment IDs pointing to different RPLS cannot be swapped between LIs. Packet Classification and Address Resolution Link Interface 0 LI 3 LI 1 LI 2 BA a BA c LI 4 IP Router BA d BA e BA f BA g BA h BA i BA j BA k LAN Interface Address Mapping BA b LS 1 LS 2 LS 3 LS 4 LS 5 LS 6 LS 7 LS 8 Satellite Interface ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 126 Traffic is sent over the mesh LIs as DVB-RCS2 PPDUs, kept apart between transmitters by use of different FPDU Transmitter identifiers (TXID) and between LSes of the same transmitter by different PPDU Fragment ID values, and kept apart between destination RCSTs by use of individual receiver ALPDU MAC24 addresses. The LS is determined at the transmitter by associating a packet to a LI, and to a BA of that LI. The packets of a BA are all sent in the same LS. The PPDUs of the LS are placed into FPDUs that are transmitted in timeslots that are known to be monitored by the destination RCST, i.e. part of the RPLS monitored by that RCST. SDU reception is achieved by monitoring applicable timeslots, reassembling ALPDUs from each LS that may be applicable for the receiver, dropping the ALPDUs not aimed for the receiver and making a forwarding decision for each SDU that is aimed for the RCST. The Request Class (RC) is used towards the resource controller in the NCC to identify the LLS associated with each capacity request, and the required RPLS. The resource controller indicates through the Assignment ID each timeslot assigned to the mesh RCST transmitter. The Assignment ID values are used to segregate the timeslot resources for each LI. Segregation of LQC may be done using the Assignment ID. Alternatively, the RCST may be allowed to map each timeslot to a pool for each LI and utilize for each LI these timeslots according to the applicable QoS policies. Figure 14.2: Internal Link Interface packet classification and transmission scheduling Each LI supports a number of queues, each used for a specific BA, as illustrated in Figure 14.2. Each BA maps to one LLS. The LLS may serve an LB group by applying different policies for the BAs it is serving. Figure 14.2 illustrates that the distribution of the timeslots controls the shaping and scheduling of submission from each LS and between the LSes. PPDUs from different LSes are interleaved onto the LI. SDUs from different queues are interleaved in a shared LS. The BA queues are FIFO queues unless packets have to be dropped from the queue due to over-filling. The FPDUs of the different link LIs are interleaved into the TX Stream. Each LI maps to only one RPLS. The RCST assumes that each Assignment ID value consistently identifies a single RPLS. All the timeslots of an RPLS are assumed monitored by the recipients indicated to monitor this RPLS. An RPLS may be as narrow as one single RCST or as wide as all the carriers in use by the super-frame, or a subset of the carriers in the super-frame. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.3.2 Routing | The satellite sub-interface address resolution table in the terminal is populated with static elements by the mesh controller through the DCP logon response, separating between default address resolution and dynamic address resolution. The static entries are given by the DCP address space and hub links address space received in DCP Logon Response. The mesh controller populates the address resolution table further with dynamic entries on demand. The dynamic entries may map to static and dynamic links. Table 14.2 shows an example of a satellite interface side routing table at RCST. LLS b LLS c LLS a BA1 BA2 BA3 BA4 Packet Classification through inspection by Multi-Field Classifier Link Stream B Link Stream A Distribution of burst resources for this LI LI burst transmission ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 127 Table 14.2: Example of RCST routing table for a transparent mesh overlay network # Base address Mask Next hop Virtual link Metric Comment 1 10.12.0.0 255.255.0.0 - 0 0 Star address space; Inserted by DCP logon response 2 10.13.0.0 255.255.0.0 - 0 1 Star address space; Inserted by DCP logon response 3 10.10.0.0 255.255.0.0 - - 0 DCP address space; Inserted by DCP logon response 4 10.11.0.0 255.255.0.0 - - 0 DCP address space; Inserted by DCP logon response 5 10.10.11.0 255.255.255.248 10.10.11.01 4 1 Tied to an active mesh link; cleared when services are cleared 6 10.10.85.0 255.255.255.248 10.10.11.01 4 2 Tied to an active mesh link; cleared when services are cleared 7 10.10.12.0 255.255.255.248 destination temporarily unreachable - - Hold-off to block temporarily in order to limit signalling 8 10.10.13.0 255.255.255.248 temporary route to the hub 0 3 Hold-off to forward to the hub temporarily for connectivity 9 0.0.0.0 0.0.0.0 10.10.10.100 3 4 Primary default route used for destinations outside Mesh and Hub address space 10 0.0.0.0 0.0.0.0 10.10.10.110 Secondary default route; for redundancy 11 0.0.0.0 0.0.0.0 10.10.10.120 Alternate secondary default route; for redundancy Entries 3-4 define non-contiguous ranges in the address space where DCP will be used to resolve destination to next hop. They are inserted by the DCP logon response. Entries 5-8 are inserted by dynamic DCP link control as a result of DCP link establishment. Entries 9-11 define alternate default routes to default GWs. They are inserted by the DCP logon response. They are resolved to link through the associated next hop IP address (here 10.10.10.100 for the primary default GW). Entries 5 and 6 are routes for active mesh link services. The entries are removed when the respective link services are released. The routes use the same virtual link as they go via the same next hop router. The virtual link identifies the RPLS monitored by the receiver of the next hop router. Entry 5 describes the destinations directly attached to the link receiver with no router in-between. Entry 6 describes a subnet that is behind another router. It is feasible that the entry 4 subnet could also be reached over another link with lower metric. Entry 7 is established due to a link service rejection and the cause is failure to connect to the destination RCST. The status is then that the next-hop is neither reachable over the TDMA nor via the default route. Other routing possibilities to the destination are not known. The entry is cleared at blocking timeout. This type of entry can limit useless DCP signalling and useless transmission to the hub. Entry 8 is established due to a mesh link rejection and the cause in the link establishment response. The planned next- hop is reachable but not by direct mesh link. It is believed to be reachable via the hub. The entry is cleared at blocking timeout. The reason for this type of reroute may e.g. be current link conditions and service policies (would require service class based address resolution). The metric will have to be larger than 2 to allow several metric values to be used for differentiated routing over multiple mesh links. Entry 9 is the default route to the default GW. This route is never cleared. It may map to a virtual link that uses DCP link service establishment. It may map to the hub and then the necessary virtual link and corresponding links are automatically established at RCST logon. Entries 10 and 11 are routes to secondary default GW. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 128 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.3.3 Link and Link Service establishment and release | |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.3.3.1 Establishment | A LL service is established for a specific link. In cases where there is only one LL service for a link, the LL service establishment is integrated with the link establishment. DCP is employed to establish the specific route entry and the specific link that should be used for the packet mapping to this LL service. The need to differ link from LL service establishment comes from the fact that there might be several LL services using the same link (transmitting packets of different QoS classes between two RCSTs). The first time we establish a link service between two RCSTs, also the link is established. In the response from the Mesh Controller a global reference is provided for the link, and the Request Class identifier to use when asking for capacity for this specific link service. Also, the MC provides routing information applicable for the link, and the TXID to be used by the transmitter. If needing to establish another link service between the two RCSTs, neither the global reference for the link nor the link routing information is required, since we already have it, but request class for requesting capacity and TXID to use (this may be the same TXID that is already in use for another link service). So, the process of link service establishment will be the same in both cases. The difference is that the Mesh Controller in the second case will not assign a new global link reference; it will duplicate the link establishment response from the first case apart from giving a new LL service ID, a new request class and maybe a new TXID. An initial LL service ID is chosen by the RCST in the link establishment request. The Mesh Controller will in its response to the RCST assign a LL service ID for that specific service. This ID is unique within the link it is established for (within the link identified by the global link reference). It is therefore a unique reference of a LL service within a link as seen from the Mesh Controller and the participating RCSTs. The value of the LL Service ID used in the Link Establishment Request from the RCST indicates the LQC of the requested LL service. In other signals, the LL Service ID indicates the unique identifier for the link service. The remote RCST will receive link establishment request by the Mesh Controller with all necessary link and link service information (as already decided by the link initiator and the Mesh Controller). It needs either to accept or reject the link establishment. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.3.3.2 Release | Complementary to link and LL service establishment, there is link and LL service release. A link will exist as long as there is a LL services that belongs to it. When the last LL service is released, the link itself is released. The RCST initiating link establishment will be the main responsible for releasing LL service and links. The remote RCST will also release an inactive link after a long timeout in order to avoid a hang situation. The mesh Controller also has the opportunity to release LL services and links. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 14.4 RCST MF-TDMA receiver | A mesh-capable RCST needs to be equipped with a DVB-RCS2 compatible burst receiver, and possibly a wideband multi-carrier burst receiver. The receiver needs to be selective of the set of TXIDs that applies for it in its current state. These may be signalled by the means of DCP, signalled through the MMT, or possibly locally synthesized from TBTP2 parsing. Unicast traffic is specifically addressed to the MAC24 address assigned at DVB-RCS2 logon. Nominally, a burst is associated to a specific transmitter by the explicit TXID in the FPDU, and the contained ALPDU is associated to a specific receiver through the explicit MAC24, in combination associating the ALPDU to a specific link. The burst receiver may however be built to accept packets without MAC24 arriving in timeslots known in advance to be used for a specific link, even without explicit TXID tagging. Such selectivity is feasible by using receiver timeslot selectivity throughout the system. This can be exploited for header compression. The link specific timeslots should be sufficiently identified by the transmitter and Assignment ID. The burst receiver is tuned to the RPLS. The RPLS can be built in different ways, and may be synthesized locally in real time from the TBTP2 based on the dynamic information given by DCP. By this design the burst receiver cannot be expected to monitor other slots than those explicitly assigned, but the burst receiver can neither be expected to not monitor other timeslots on the indicated mesh carriers, if such suppression is not specifically known supported by the implementation. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 129 14.5 Adaptive Coding and Modulation, and adaptive timeslot sizing DVB-RCS2 offers the opportunity to do per-burst ACM and adaptive timeslot sizing. A possible strategy for exploiting this may be to: • Parse the TBTP2 also at the receiver side to determine the timeslot structure of each individual frame, and the modulation and coding that will be used in each individual timeslot. • Prevent the mesh transmitter from using transmission types on a specific link that cannot be expected to close the link to the specific mesh receiver. 15 Dynamic connectivity protocol guidelines for transparent mesh overlay networks |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 15.1 Mesh carrier frequencies | The NCC sends in TIM-B a Mesh System descriptor with a list of frames that may be used for mesh traffic, for each Super-frame used for mesh. The descriptor also indicates the transponder frequency offset for these frames. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 15.2 Mounting DCP | The DCP messages are transported as UDP packets using a specific DCP UDP port and specific IP addresses, and the NCC needs to indicate this to the mesh RCST. The Mesh Controller IP address, the DCP multicast address and the UDP port number used for exchanging DCP messages is given in Logon Response TIM-U. An Extension Protocol Descriptor is used to indicate these connection details for an extension protocol. Extension protocols may be used to supplement the lower layer signalling system via IPv4 M&C. The DCP protocol is mounted with the reception of this descriptor. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 15.3 RCST mesh capability signalling | The DVB-RCS2 logon request message of a mesh capable RCST may inform the NCC of the transparent-mesh capability of the RCST. |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 15.4 DCP message transport | The DCP signalling is UDP/IPv4 based, apart from the initial mesh information exchanged from using DVB-RCS2 L2S signals, as explained in the earlier clause. Table 15.1 gives an overview over the DCP messages. The DCP messages are organized into two main groups, management messages and link control messages. ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 130 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 15.5 Summary of DCP messages | Table 15.1: DCP messages Management Messages Direction Description DCP Logon Request RCST Mesh Controller Used to log on a mesh RCST to a mesh network; provides RCST terminal and router information to be exploited by Mesh Controller for later link establishments DCP Logon Response Mesh Controller RCST Response from the Mesh Controller; gives the RCST configuration, DCP system information and the hub space and mesh space route information DCP Agent Management Request Mesh Controller RCST Used by Mesh Controller to get the DCP client to perform specific tasks, such as: *clear all dynamic link and routes, *clear all session data and logon, *clear all session data and go to star-only state *leave star-only state and logon to Mesh Controller DCP Agent Management Response RCST Mesh Controller Response by RCST. Link Control Messages Direction Description DCP Link Service Establishment Request RCST Mesh Controller Mesh Controller RCST Either by RCST or Mesh Controller, used to establish link service Also used for mesh multicast configuration update when sent from Mesh controller DCP Link Service Establishment Response RCST Mesh Controller Mesh Controller RCST Either by RCST or Mesh Controller, response to a link service establishment DCP Link Service Release Request RCST Mesh Controller Mesh Controller RCST Either by RCST or Mesh Controller, Used to release link service DCP Link Service Release Response RCST Mesh Controller Mesh Controller RCST Either by RCST or Mesh Controller, response to a link service release DCP Link Status Enquiry Mesh Controller RCST Depending on the System options enabled, could be link quality polling. DCP Link Status Response RCST Mesh Controller RCST response to the mesh status enquiry DCP Link Service Control Acknowledgment RCST Mesh Controller Mesh Controller RCST Used where just a handshake is required ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 131 |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 15.6 DCP message sequence diagrams | |
fc9c999440d0c3f544c424c8c56027ec | 101 545-5 | 15.6.1 DCP logon | Figure 15.1: Message exchange during DVB-RCS2 logon and DCP log on - Successful DCP logon Mesh Controller NCC RCST From this point, all messages between Mesh Controller and RCST are UDP based Operational Logon Response gives DCP server IP address and port UDP number TIM-B indicates mesh support RCST capability field indicates DCP support and mesh capability MSC DCP_Init_VSAT DCPLogonResponse DCP Logon Request Broadcast TIM Logon Response (unicast TIM) Logon Request (CSC burst) ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 132 Figure 15.2: Message exchange during DVB-RCS2 and DCP logon - Unsuccessful DCP logon Mesh RCST will continue to send DCP logon requests until it succeeds to log on. The frequency of logon requests should be limited (RCST should keep trying because the Mesh Controller may be expected to come up; if the Mesh Controller has not been intended to come up, the NCC would not have distributed the basic mesh information in the TIM-B and TIM-U). If a mesh RCST does not receive DCP logon response from the Mesh Controller, it will map all the satellite traffic to the permanent hub links and thus operate in the star mode. Mesh Controller NCC RCST After timeout, RCST will again try to logon to the Mesh Controller From this point, all the messages between the Mesh Controller and RCST are UDP based Not operational Logon Response gives DCP server IP address and port UDP number GW capability field indicates mesh support RCST class of RCST capability field indicates mesh capability MSC DCP_Init_VSAT_Failure DCP Logon Request DCP Logon Request Broadcast TIM Logon Response (unicast TIM) Logon Request ETSI ETSI TR 101 545-5 V1.1.1 (2014-04) 133 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.