2015年8月13日 星期四

C-RAN

About C-RAN, please refer to the wiki link as below

C-RAN

Basically, the ISP considers to adopt the technology of the LTE-A as below

1. CA - Carrie Aggregation  - Three types: (a) Intra-band Contiguous (b) Intra-band Non-contiguous (c) Inter-band Non-contiguous

2. MIMO

MIMO為LTE-A帶來更高階的4×4或8×8,但也因此造成裝置支援的問題,目前尚無支援4×4 MIMO的智慧型手機。
當然MIMO不須在發送器以及接收端取得平衡。美國T-Mobile支援4×2 MIMO,即在基地台建置4條天線,在裝置端建置2條。4×2 MIMO仍然可以改善網路效能,效果在下行鏈路尤為可觀,裝置得以傳送訊號至四條不同天線,而不只有兩條。
美國電信商Sprint已部署支援8×8 MIMO的LTE TDD基地台一段時間。提供此類無線電系統的廠商有阿爾卡特朗訊(Alcatel-Lucent)、諾基亞通信,以及三星(Samsung)。中國移動也正著手建置類似的無線電系統,除Alcatel-Lucent和諾基亞外,也和愛立信(Ericsson)、華為和中興通訊合作。然而Sprint因為裝置支援問題,尚未開通8×8 MIMO,目前僅為其LTE TDD傳輸擴展4×2 MIMO。
雖然MIMO確實能增加網路容量,卻無法帶來和載波聚合一樣的益處。首先,因為智慧型手機的天線空間已經相當有限,無法再容納MIMO。其次,營運商須要增加天線,甚至可能要添置無線電系統才能支援MIMO,這些流程帶來的額外成本都高於只須進行軟體升級的載波聚合。

3. CoMP

CoMP is a technology that prevents base station interference and abrupt call disconnections in coverage boundary areas by enhancing signal strength, the lack of which leads to a significant drop in data transmission speed, and CA is a technology that provides twice or faster data rates by utilizing multiple frequency bands at the same time.

coordinated Multipoint (CoMP) Transmission – Formalized in 3GPP Release 11, CoMP would be another key characteristic of a true LTE Advanced network. In a Coordinated multipoint transmission and reception scenario, multiple eNodeBs work with each other dynamically to avoid interference with other transmission signals. This leads to a better utilization of system resources and an enhancement of both network coverage and quality for cell edge users.

CoMP技術能讓終端用戶裝置同時與多處無線電端點通訊。這使得數站基地台能藉此合作,在上、下行鏈路共同分配網路資源並傳送資料;此外該技術還能在終端用戶裝置與數站基地台通訊時,改善邊緣地區的效能。
圖4 CoMP圖示
與其讓不同基地台的訊號帶來干擾且削弱網路效能,CoMP反倒能讓那些基地台共同合作改善邊緣地區效能。圖4為CoMP基本功能圖示。
CoMP的標準化從3GPP第11版本開始,並在第12版本持續進行。CoMP最大的問題在於不同基地台無線電系統之間的協調,需要低延遲的網路回傳技術。理想狀態下,這能透過C-RAN解決,但因為缺少能連接各個無線電接頭(Radio Head)的光纖,使得大部分的營運商難以進行部署。
CoMP最初的建置在上行鏈路完成,不須經標準化,或是裝置端的協調和調整。由於下行鏈路須要經過完整協調,因此建置過程將較難執行。
下行鏈路協調的首批建置將於頻段內進行,使用與單一頻帶單位連接之多重無線電單位的專用基地台,此舉將可能會限制涵蓋範圍。在3GPP第12版本批准之前,頻段內CoMP距離商業化仍有幾年的路要走,屆時才能解決多處基地台間網路回傳延遲的問題。
4. eICIC

  • Enhanced Inter-Cell Interference Coordination – eICIC will be the primary interference management and mitigation procedure adopted in the LTE-A network. It is typically used in a heterogeneous network where both macro and pico cells transmit and receive data at the same time. The weaker signal from the smaller cell can be easily overpowered by the stronger signal from the larger cell. In eICIC, certain subframes are transmitted by the macro cell without any data. These almost blank subframes (ABS) are low power control channels. The users in the pico cell area then communicate with their base station during such blank subframes. This minimizes the interference between the macro and pico cell on both traffic and control channels. Advanced interference mitigation schemes have been used in LTE networks, but with the increasingly high density of wireless network cells, more sophisticated schemes like eICIC are required

eICIC在網路方面的角色和CoMP類似,兩者都能降低基地台間的干擾,並改善邊緣區域效能。兩種技術之間最大不同在於,eICIC是利用相似頻道解決小型基地台與大型基地台間的干擾;而CoMP則著重在大型基地台間的干擾。

2015年8月10日 星期一


  • 網路RC4加密演算法已可快速破解,資安研究人員呼籲別再使用了
  • 繼今年初英特爾(Intel)收購領特(Lantiq)之後,高通(Qualcomm)旗下子公司高通創銳訊(Qualcomm Atheros)日前也宣布買下寬頻網路半導體開發商伊卡諾(Ikanos),強化局端(Central Office)和家庭閘道器解決方案陣容
  • IOS整合了路由器、交換器、網路,及電信等功能,屬於多工作業系統,現為多數思科路由器及網路交換器的主要平台。而駭客則是把IOS中用來儲存啟動程式的唯讀記憶體監控模式(ROM Monitor mode,ROMMON)換成惡意的ROMMON影像

News 8/11/2015


  • Enterprise Linux OpenStack Platform 7的主要特色包括簡化了OpenStack的部署與管理、提供OpenStack上任務或應用的高可得性、更強大的安全控管、改善網路彈性,以及強化備份能力。



2015年8月4日 星期二

XG.Fast

XG-Fast - 网速 

目前G.Fast宽带技术,使用了106Mhz的频率范围,为了提高网速,贝尔实验室的工程师,使用了500MHz的频率范围来传输数据。不过需要指出的是,虽然在数据传输速度上获得重大突破。
现有的G.Fast技术,可以在100多米的电话线上实现700Mbps的网速,而最新研发的XG-Fast,则可以在30米的距离上,实现10Gbps的单向传输网速,或是在70米的电话线上,实现1Gbps的双向传输(即同时按照这个速度上传或下载)

XG-Fast - 缺陷 

XG-Fast也存在一个弊端,那就是和过去的技术相比,传输的距离更短

2015年7月29日 星期三

How to rebuild the WMI in Win7

Try repairing and rebuilding the WMI service...

Click on start>Run>cmd

On the command prompt run the below steps in order

1. net stop winmgmt 
then go to the C:\Windows\system32\wbem directory and delete the Repository directory

2. net start winmgmt

3. cd /d %windir%\system32\wbem
4. for %i in (*.dll) do RegSvr32 -s %i
5. for %i in (*.exe) do %i /RegServer

and 

6. cd /d %windir%\sysWOW64\wbem
7. for %i in (*.dll) do RegSvr32 -s %i
8. for %i in (*.exe) do %i /RegServer


reboot and let me know ...

NOTE: A word of advice... Rebuilding the WMI repository will most probably result in some 3rd party products not working until their setup is re-run & their MOF re-added back to the repository.

2015年7月28日 星期二

OpFlex Control Protocol_Draft


ODL's Third Release – “Lithium” - Introduces New SDN Features & Capabilities

● Increased scalability and performance 
● Network services for cloud data center platforms 
● New features for security and automation 
● New and enhanced APIs for interoperability 
● Six new protocols to support an ever-widening set of use cases ( OpFlex is one of the six protocols)


Abstract

The OpFlex architecture provides a distributed control system based on a declarative policy information model. The policies are defined at a logically centralized policy repository (PR) and enforced within a set of distributed policy elements (PE). The PR communicates with the subordinate PEs using the OpFlex Control protocol. This protocol allows for bidirectional communication of policy, events, statistics, and faults. This document defines the OpFlex Control Protocol.

OpFlex is a policy driven system used to control a large set of physical and virtual devices. The OpFlex system architecture consists of a number of logical components. These are the

 OpFlex protocol uses JSON, XML, or OpFlex-Binary-RPC as the wire encoding.

Policy Repository (PR)
It handles policy resolution requests from the Policy Elements within the same administrative domain. These policies are configured directly by the user via a policy administration interface (API/UI/CLI/etc.)

PR - MIM (Management Information Model)
The hierarchical structure starts at a root node and all policies within the system can be reached via parent and child containment relationships. Each node has a unique Uniform Resource Identifier (URI) [RFC3986] that indicates its place in the tree.

PR -Managed Objects
MOs that contain statistic, fault, or health MOs are said to be observable
Properties, Child Relation, Parent Relation, MO Relations, Statistics, Faults, Health


Endpoint Registry (EPR)

The Endpoint Registry (EPR) is the component that stores the current operational state of the endpoints (EP) within the system
The EP registration information contains the scope of the EP such as the Tenant or logical network as well as location information such as the hypervisor where the EP resides. The EPR can be used by PEs to query the current EPR registrations as well as receive updates when the information changes.

Observer

The Observer serves as the monitoring subsystem that provides a detailed view of the system operational state and performance. It serves as a data repository for information related to trending, forensics, and long-term visibility data such as statistics, events, and faults.

Policy Elements (PE).

Policy elements reside on physical or virtual devices that are subjected to policy control under a given administrative domain. 

Two types of the PE triggers
(a) Local triggers involve local MO state transitions such as new control node additions, removals, or other operational events.
(b) Policy triggers invoked by other PEs are transmitted using the OpFlex Control Protocol

Security

OpFlex Control Protocol SHOULD be secured using Transport Layer Security (TLS) [RFC5246].
A TCP port will be requested from IANA for the OpFlex Control Protocol.

 Terminology:

  •  AD: Administrative Domain. A logical instantiation of the OpFlex system components controlled by a single administrative policy. 
  • EP: Endpoint. A device connected to the system. 
  •  EPR: Endpoint Registry. A logically centralized entity containing the endpoint registrations within associated administrative domain. 
  •  OB: Observer. A logically centralized entity that serves as a repository for statistics, faults, and events. 
  •  PE: Policy Element. A function associated with entities comprising the policy administrative domain that is responsible for local rendering of policy. 
  •  PR: Policy Repository. A logically centralized entity containing the definition of all policies governing the behavior of the associated administrative domain. 
  •  OpFlex Device: Entity under the management of a Policy Element. 

2015年7月27日 星期一

SDN - 7/29/2015

OpenFlow in the WAN are:
  • Power cost of managing devices
  • Predictable and deterministic routing decisions in the case of failover
  • Optimal routing decisions based on bandwidth and load
The way this is done will depend on where in the network the NFV functionality is hosted. There are three basic methods:

  • Standard servers running NFV functionality in the same topological network location as the appliance. This saves on hardware costs but does not reduce network complexity.
  • Much of the network functionality, including switches and appliances, can be virtualized in a hypervisor. This is the approach taken by Nicira and others. This may be appropriate in data center environments.
  • OpenFlow-capable switches can selectively shunt traffic to standard servers running NFV functionality off the main data path.