HSCN Interconnectivity Requirements Summary

Transcription

1 Intercnnectivity Requirements Summary 25/05/2016 Cpyright 2016 Health and Scial Care Infrmatin

2 Intercnnectivity Requirements Summary V0.1 25/05/ Purpse The purpse f this brief is t prvide the high level requirements brief in rder t facilitate the prpsals discussed in the Wrkshp held n 19 th May Sectins 1, 2 and 3 f this dcument are prvided by. Sectin 4 is prvided by Accenture t illustrate a Pint f View (PV) fr peering technical slutin based n a cmmercial availability f UK based infrastructure. 2 Requirements fr Netwrk Intercnnects Market / Cmmercial Technical Prvide a level playing field fr all participating netwrk prviders Remve the need fr a large cre backbne as the bulk f applicatins and services are mved lcally r t the internet i.e usage is flexible and will nt require cmmercial change t increase / decrease capacity Availability & Perfrmance: 99.99% availability fr the intercnnect infrastructure Netwrk latency jitter requirement ver the f 10millisecnds, measured ver a perid f 5 minutes as the abslute value f the difference in frwarding delay fr any tw packets Each pint f intercnnectivity must achieve availability f 99.95%. Supprt ruting ut f the bx acrss netwrk endpints and t natinal applicatins Simple and effective fault diagnsis between supplier netwrks Prvide centralised cnnectivity t external netwrks (e.g. SWAN r Janet) i.e. permit central intercnnects t these services fr all service prviders Delivery / Operatinal Timescales t deliver nte needs this prir t April 17 with an ambitin t be ready by Dec 16 Ease f delivery / transitin frm N3 Ability t cnnect N3/Transitin Netwrk within the timescales Phased cnnectins fr netwrk service prviders as they gain cmpliance N need fr majr infrastructure changes t cnnect new suppliers r services, with n impact n existing supplier services Service view acrss the functin fr issue reslutin including transparency fr each cnnected service prvider 3 Other Cnsideratins Optins fr wh perates and manages the intercnnect infrastructure Funding mdel funded r funded by the supply chain via cnsumer revenue Page 1 f 6

3 Intercnnectivity Requirements Summary V0.1 25/05/ Cre Netwrk Architecture peering slutin based n cmmercial availability f UK based infrastructure - PV Intrductin The purpse f this sectin is t prvide an analysis f the ptin t mve frm the current N3 Cre architecture fr the aggregatin f carrier netwrks twards with a mre pen, agile, flexible, industry and technlgy market relevant netwrk architecture leveraging a peering slutin based n cmmercial availability f UK based infrastructure. This PV is created by Accenture in the spirit t cllabrate with the Technlgy wrking grup t prvide an analysis f peering ptins fr the netwrk architecture and t help the wrking grup t select the best ptin and architecture amng the fllwing: Optin 1 - Re-use f PSN t deliver a peering netwrk slutin Optin 2 - Re-use N3 peering by enhancing f the current infrastructure Optin 3 - Peering slutin based n cmmercial availability f UK based infrastructure bjective f this dcument prgramme The Health and Scial Care Netwrk () prgramme ambitin is t prvide a reliable, efficient and flexible way fr health and care rganisatins t access and exchange electrnic infrmatin by reducing csts and cmplexity, standardising netwrks, enabling service sharing and extending the parameters f cllabrative wrking. This will be achieved by migrating ut frm current N3, whilst embracing the PSN by: Establishing netwrk arrangements that supprt the integratin f health and scial care, reginal cllabratin and flexible wrk patterns Creating a marketplace f assured netwrk services that drives cmpetitin amngst suppliers, imprves cnsumer chice, supprts innvatin and delivers value fr mney Reducing duplicatin by enabling health and scial care rganisatins t reuse and share existing netwrk infrastructure and services t access the infrmatin they need Reducing reliance n a centrally managed, natinal, private netwrk Specifically fr the netwrk architecture, the bjective f is t remve the need fr a large cre backbne as the bulk f applicatins and services are and will be mved lcally r t the clud r Internet. By ding that, has an ambitin t supprt ruting ut f the bx acrss netwrk endpints and t natinal applicatins limiting the needs fr a majr infrastructure changes t cnnect new suppliers r services. The netwrk shuld als prvide a centralised cnnectivity t ther netwrks (e.g. SWAN r Janet i.e.) t enable central intercnnects t these services fr all SPs. The preferred ptin frm, as presented t the wrking grup n May 19 th 2016 (see picture belw), is t prvide a simple and uncmplicated cnnectivity, flexible t adpt quickly t end-custmer needs (i.e. deply increased bandwidth), supprt best pssible perfrmance (aviding traffic t span a cre, but use rute servers/rute reflectrs t ensure shrtest path) and simplifies end-t-end Service Assurance & fault diagnsis. Page 2 f 6

4 Intercnnectivity Requirements Summary V0.1 25/05/2016 Netwrk Architecture leveraging a peering slutin based n cmmercial availability f UK based infrastructure. Health and Public Sectr, and mre generally all industries, are evlving very rapidly t Digital Services impacting business prcesses, custmer experiences and demands, integratin with business partners and suppliers and adptin f new technlgies including Clud services, Mbility, Tele medicine and Internet f Things. In rder t pen a marketplace f assured netwrk services by April 2017 which will deliver t endcustmers a cmpetitive supplier prtfli requires a strategic and pragmatic apprach t create the aggregatin netwrk. There are certainly multiple appraches fr the creatin f the aggregatin netwrk. Cnsidering the ambitin, end-custmer requirements, SPs pen marketplace, technlgy and industry evlutin, and the aggressive timeline, the ptin f an aggregatin based n Carrier Neutral Facility can be the best ptin t meet visin and requirements. Carrier Neutral Facilities (CNF) are telecmmunicatin hsting facilities which ffer secure, private crss-cnnectin pints between prviders and clud services hsted in their facilities. Large number f tier-1 and tier-2 Service Prviders, Carriers, Internet Service Prviders and Clud prviders are hsted already tday within mayr Carrier Neutral Facilities in UK. With a Carrier Neutral Facility strategy, can accelerate the launch f an pen market having a trusted and easy way fr Service Prviders and Carriers t jin prgramme: Fr tier-1 and tier-2 Service Prviders and Carriers already at the CNF it will be sufficient t cmply with the certificatin and bligatin f t be able t ffer their services t the marketplace. Unless changes t the physical infrastructure are required, the n-barding f thse Service Prviders will be simple and fast Fr ther Service Prviders which are nt at CNF tday, they will have a simplified way t jin by cnnecting t CNF and aviding the negtiatin and creatin f multiple NNIs with the ther Service Prviders. They will als benefit f being at CNF t expand their service prtfli and market beynd (leveraging fr instance a direct cnnectin t Clud and ther SPs), maximizing the investment f the cnnectin int a CNF will als benefit frm CNF t hst any additinal equipment r devices, such as and, that and eventually end-custmers wuld require t cmply with security standards, service management standards and ther requirements r business needs. Page 3 f 6

5 Intercnnectivity Requirements Summary V0.1 25/05/2016 The picture belw shws a ptential architecture fr the aggregatin netwrk base n CNF: Ruters A Ruters ILLUSTRATIVE B N Internet Prviders Clud Prviders N3 / Transitin Netwrks Management (NSI) ILLUSTRATIVE Peering f multiple Service Prviders is realized within CNF with a simplified architecture cntrlled by LAN switches and empwered as necessary by and fr a greater level f security. Reliability f the netwrk will be ensured by establishing at least 2 CNF gegraphically distant fr Disaster Recvery plus a physically redundant LAN, and wherever needed security, infrastructure fr the peering at each CNF lcatin. A higher number f CNF lcatins culd be als cnsidered wherever an pen market with reginal, lcal and smaller Service Prviders will make them easier t jin. Netwrk Architecture will remain similar t the ne described in the picture abve. The benefits f CNF apprach are summarized in the table belw: Benefit area Evaluatin Descriptin Technical cmplexity Lw This architecture simplify netwrk eliminating technical cmplexity and cnstraints assciated with a multiple Service Prviders aggregated netwrks via a prliferatin f NNIs between them. Perfrmance High Simplified architecture withut a prliferatin f NNIs will increase perfrmance f the verall netwrk. CNF apprach will als imprve perfrmance as cmpared t N3 netwrk because traffic will send acrss the shrtest path, withut even crssing the CNFs wherever pssible (i.e. traffic n the same Service Prviders netwrk and VPN), as ppsite f tday where traffic needs t travers GCN and N3 netwrks. Reliability High Reliability f the netwrk will be ensured by establishing at least 2 CNF gegraphically distant fr Disaster Recvery plus a physically redundant LAN, and wherever needed security, infrastructure fr the peering at each CNF lcatin. Flexibility scalability and High CNF will allw t adpt best t market changes, regulatry changes, merges and acquisitins, new service prviders, increase data traffic, changes t bligatins and/r security plicies. The n-barding Page 4 f 6

6 Intercnnectivity Requirements Summary V0.1 25/05/2016 f new Service Prviders is simplified because f a simplified apprach and architecture f the cre and peering. CNF ffers als hsting capacity fr any additinal equipment r devices t supprt new requirements, business mdel and traffic fr, Service Prviders and end-custmers. Manageability Optimized Simplified architecture at CNF will result als f a less cmplex netwrk and service management enabling a NSI t manage the netwrk peering, verall netwrk perfrmance and Service Prviders. An independent NSI apprach wuld be als gd strategy t ensure a level playing field and trust amng all Service Prviders fr an pen marketplace. Time f executin Fast CNF apprach will reduce significantly the time t bring live : Majr tier-1 and tier-2 Service Prviders are already at key CNF in UK, n majr activities are required besides t cmply with bligatin framewrk Other Service Prviders which are nt at CNF tday can jin by cnnecting t CNFs lcatin withut any need t establish multiple NNIs with ther SPs (which usually requires additinal effrt beynd cnnectivity in reaching NNI legal and cmmercial agreements) In additin t the benefits abve, CNF strategy will als allw Service Prviders t prvide endcustmers with new WAN architecture including hybrid WAN t prvide a secure Internet access verlay via SD-WAN (Sftware Defined Wide Area Netwrking) t ff-lad traffic frm private MPLS t Internet, prviding verall imprved perfrmance at a reduced csts. Transitin frm N3 / Transitin Netwrks t leveraging a CNF strategy As mentined in the previus paragraph, majrity f tier-1 and tier-2 Service Prviders, Carriers, Internet Service Prviders and Clud prviders are already hsted tday at the established Carrier Neutral Facilities (CNF) in UK. The multiple CNF lcatins and prviders in UK will als allw a high degree f flexibility required by an pen market at an increased and cnsistent stability and a high reliability f the verall netwrk. Once Service Prviders and Carriers becme certified with, transitin frm N3 / Transitin Netwrks t will requires, wherever needed, a recnfiguratin f the ruting, VRF and VPN tunnels, withut any additinal physical infrastructure re-prvisining. The CNF apprach will als simplify and de-risk transitin between N3 / Transitin Netwrks and by reducing cmplexity f the Dual Mde f Operatin (). The will be realized as a LAN, plus required security and firewalling, integratin at CNF t bridge N3 / Transitin Netwrks and prviding a seamless cmmunicatin between the ld (meaning end-custmer s lcatins still n N3 / Transitin Netwrks) and the new (end-custmer s lcatins migrated t ). The picture belw shws a ptential architecture fr the integratin with N3 / Transitin Netwrks base n CNF: Page 5 f 6

7 Intercnnectivity Requirements Summary V0.1 25/05/2016 Ruters A Ruters ILLUSTRATIVE B N Internet Prviders Clud Prviders N3/PSN N3 / Transitin Netwrks Management (NSI) Additinal questins frm Questin - Current sum ttal f NHS circuits is >500Gb/s. Which shuld be the Capacity / Sizing number f cnnectins? Answer Accrding t, N3 netwrk has a thrughput f ~30Gb/s with a number f cnnectin that exceed 500Gb/s. A like fr like supprt f tday s traffic int will requires the same thrughput n the Cre and aggregatin netwrk. Hwever the shift f traffic ver a secure Internet cnnectin, implementatin f new WAN slutin such has hybrid WAN, shift f applicatin cmpute lcally and in the Clud will prvide the pprtunity t reduce the Cre and aggregatin netwrk thrughput, r at least t limit its expansin t supprt the increase f data resulted by digitizatin f prcesses. CNF strategy will prvide better flexibility t adjust Cre and aggregatin netwrk thrughput t supprt best end-custmer demands. Questin - Can hsted services that require natinal access (e.g. Spine) cnnect t peering r wuld be better supprted n a backbne prviding wider dispersed PPs. Nte we think these culd be cnnected t DLNs Answer CNF will prvide the flexibility and scalability t hst and intercnnect services which requires natinal access. CNF can als help t cntrl and restrict thse services gegraphically f by dmain / cmpetence at CNF directly t supprt best requirements. Page 6 f 6