Explore chapters and articles related to this topic
Photonic Network
Published in Naoaki Yamanaka, High-Performance Backbone Network Technology, 2020
Compared to a point to point data link, a multiaccess data link layer is complex and need extra overhead for complex header information such as MAC addresses. Such information were useful, if there had been various protocols used at the Internetworking layer. However, in the Internet backbone, all the information is carried as IP packets, headers of which contain all the information to relay the packets to the destination. So, data link layer headers are redundant. Worse, to support IP multicast or QoS (Quality of Service) assurance, multi-access data link layer must have its own mechanism of multicast or QoS assurance and, in addition, mapping between the data link and the Internetworking layer multicast or QoS assurance must be defined. On the other hand, if IP routers are connected by point to point data link, data link layer multicast is no different from data link layer unicast and QoS is assured by proper queuing at the output of the IP routers.
The Future of Network Operations
Published in Marcus K. Weldon, The Future X Network, 2018
In the current DevOps methodology (shown in the left side of figure 9), the application software is delivered from the development team to the operations team, which then deploys and operates it. The development team uses feedback from the operations team to generate the next software release using agile methodology, implementing the prioritized changes that are requested by operations. The right side of figure 9 shows the Dev-for-Ops framework, including the dependencies between the vendor and the operator, and how availability, visibility, adaptability and scalability are provided. Note that this is the same functionality described in the previous subsection as service fulfillment and service assurance but the focus here is on the development of the overall solution. These characteristics must be embedded in the solutions delivered by the vendor based on a synergistic, trusted relationship between vendor and operator.
Toward Information-Centric Networking: Research, Standardization, Business, and Migration Challenges
Published in Hassnaa Moustafa, Sherali Zeadally, Media Networks: Architectures, Applications, and Standards, 2016
Wei Koong Chai, Michael Georgiades, Spiros Spirou
ICN will support content owners to distribute their content on a large scale in a fashion similar to how it is done today, that is, ICN should not force drastic changes to how content is published for the access of the public. Content owners may still opt to pay for CDN-like services but the underlying mechanism of content publication (e.g., content naming, resolution) should be transparent to them. This will mean that a Content Owner will save the costs that it will otherwise inherit if it used a service provided by a CDN provider. To achieve this, however, the ICN services must offer the necessary confidentiality, reliability, and quality-of-service assurance to avoid the need of enforcing the content owners to establish SLAs with every network operator covering the regional area or targeted customer group of interest.
Studying the Impact of SIP Message Differentiation on the Quality of VoIP Session Control Procedures
Published in IETE Technical Review, 2021
Jasmina Baraković Husić, Sabina Baraković, Seudin Kasumović
The algorithm allows a differentiation between service classes, thus enabling the signalling messages of one service class to have preferential treatment over the signalling messages of other service class. This may be useful in emergent situations when huge traffic amount from multiple services causes the SIP call control server overload and leads to a severe congestion problem. The proposed algorithm may provide satisfactory service quality, service assurance (reliability and availability), and user experience when using these services.