Progress on FMC Network Architectures Sample Clauses

Progress on FMC Network Architectures. Functional Convergence Sharing the infrastructure of an access/aggregation network implies that the control functions responsible for this infrastructure take into account both mobile and fixed traffics. In other words, the control planes of the fixed and mobile networks have to converge, at least partially, in order to efficiently allocate resources. This convergence can be achieved at different levels, depending on how the infrastructure sharing is performed. For example, if the sharing is limited to the allocation of different wavelengths channels on WDM links, the control plane has only to ensure that a given wavelength channel is just allocated once, either to fixed or to mobile traffic. A more complex set of networking functions has to be designed for a more complete convergence with finer granularity, e.g. the sharing of a common new MAC (called here a Meta-MAC) in the aggregation network. Ethernet-based architectures, and in particular those considered for delivering Carrier-Ethernet, are likely candidates for the Meta-MAC, as they are currently used both for backhauling mobile traffic and for operating fixed metro networks. COMBO shall also specifically consider Meta-MACs designed for transparent optical transport (such as OBS and OPS) in order to take advantage of their energy-friendly potential. Specification of a Meta-MAC: The set of networking function to be designed to facilitate functional convergence would potentially include the specification of filtering and marking rules, used to classify fixed and mobile traffic into Meta-MAC SDUs, prior to encapsulation into Meta-MAC PDUs. Meta-MAC scheduling and forwarding principles should be defined (i.e. functions belonging to the data plane of the converged network), together with control plane functions such as routing. The following major points shall be addressed:
Sample 1
AutoNDA by SimpleDocs
Progress on FMC Network Architectures. Structural Convergence Once specified, functions have to be distributed over network equipment. At the level of fixed-mobile convergence in the sense of equipment and infrastructure mutualization (which we call structural convergence), some work has been done in the context of the European FP7 ALPHA project on Analogue Radio over Fibre technologies [31], [32] (see Section 1.2.4 for more details). In COMBO, Digital Radio over Fibre (D-RoF) is of higher interest because it has no linearity constraints, an advanced standardization and it is widely implemented by mobile station vendors. Moreover, D-RoF opens the way to BBU hotelling and C- RAN [33]. COMBO will contribute to the progress of the state-of-the-art of current separated fixed and mobile access/aggregation networks with a set of innovative architectural concepts: - Sharing of equipment supporting both fixed (OLT) and mobile (BBU) interfaces: The advantages and feasibility of shared equipment supporting both fixed (OLT) and mobile (BBU) interfaces will be investigated. As an example, consider the problem of mobile backhauling. Nowadays mobile traffic is gathered from distributed sets of base stations typically with a dedicated backhaul. COMBO proposes to enable new backhaul architectures that allow moving the mobile- traffic processing (which takes place in the so called Base Band Unit, or BBU) in a separated and possibly distant location, which can be far from the antenna location (reduced to a Remote Radio Header or RRH). This kind of approach is usually referred to as BBU hotelling. - Node consolidation in a fixed mobile converged network: Up to now, the availability of locations for mobile base station sites and for fixed network central offices are not re-considered by each other for new deployments. This leads to contradicting evolution paths. While the fixed networks access considers a node consolidation by reducing the number of central offices with pure passive long reach access up to 100 km, in mobile networks, a strongly increasing number of new active sites are expected. COMBO will provide new use cases and assessment tools for node consolidation in a fixed-mobile converged network.
Sample 1

Related to Progress on FMC Network Architectures

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Synchronization The Licensor hereby grants limited synchronization rights for One (1) music video streamed online (Youtube, Vimeo, etc..) for up to 500,000 non-monetized video streams on all total sites. A separate synchronisation license will need to be purchased for distribution of video to Television, Film or Video game.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!