Powered by Lexis+®
CASE STUDY

“I'm able to do more in the day, which means I'm providing more value to my clients - and it's helped my margins in terms of how much I can bill. LexisNexis is helping me make money.”

ParrisWhittaker

Access all documents on Layered architecture

Layered architecture meaning

What does Layered architecture mean?
In legal practice, layered architecture describes how a communications or IT system is organised into discrete technical layers (for example, physical, network, transport and application), each adding functionality to the underlying medium of communication and serving the layer above. The term is not defined in legislation or case law; it is a descriptive technical expression, often linked to the OSI model or protocol stack, used across telecoms regulation and technology, outsourcing, cloud and software contracts. Key legal uses include: allocating responsibilities, warranties, service levels and liability by layer (for example, connectivity, routing, middleware and application); specifying interfaces and interoperability; structuring cybersecurity controls and “defence in depth”; and mapping data protection roles and processing activities across suppliers in the stack. It is frequently referenced in procurement specifications, transitional services arrangements and multi-vendor integration clauses. Practical significance: it clarifies scope, interfaces and integration risk, and supports compliance assessments under telecoms and cyber regimes. Usage is broadly consistent across England & Wales, Scotland, Northern Ireland and Ireland, though regulatory touchpoints differ (for example, Ofcom and UK open internet/NIS Regulations; ComReg and EU open internet/EECC and NIS/NIS2 frameworks).
Speed up all aspects of your legal work with tools that help you to work faster and smarter. Win cases, close deals and grow your business–all whilst saving time and reducing risk.

View the related Practice Notes about Layered architecture

PRACTICE NOTES
2002 ISDA Master Agreement Schedule: A Practical Negotiation and Drafting Checklist on Termination, Cross-Default, Specified Transactions, Tax, Credit Support, Notices and Other Key Elections

What is the ISDA Schedule? The International Swaps and Derivatives Association (ISDA) operates a layered documentation framework, often termed the ISDA documentation architecture. For any trade within this framework, the key components are: master agreement schedule to the master agreement credit support documents confirmation The ISDA Master Agreement is a standard-form umbrella contract setting out boilerplate provisions. The Schedule complements and varies the Master Agreement where the parties require. It enables the parties to adapt the Master Agreement to their specific needs by inserting amendments, or by adding alternative or additional terms. The Schedule is the element of the ISDA Master Agreement that the parties negotiate. The bulk of protection is provided by the Master Agreement itself. If transactions are undertaken before the Schedule has been negotiated and agreed, the Confirmation should specify that a deemed Master Agreement exists. Nonetheless, best practice is to have the Schedule settled and agreed prior to entering into any derivative transaction...

Read More Right Arrow