CushionTheBlow (구 BluemoonSoft)

The small form-factor pluggable (SFP) is a compact optical transceiver used in optical communications for both telecommunication and data communications applications. It interfaces a network device mother board (for a switch, router or similar device) to a fiber optic or unshielded twisted pair networking cable. It is a popular industry format supported by several fiber optic component vendors.

SFP transceivers are designed to support SONET, Gigabit Ethernet, Fibre Channel, and other communications standards. The standard is expanding to SFP+ which will be able to support data rates up to 10.0 Gbit/s (that will include the data rates for 8 gigabit Fibre Channel, and 10GbE. SFP+ module versions for optics as well as copper are being introduced. In comparison to Xenpak, X2 or XFP type of modules, SFP+ modules leave some of the circuitry to be implemented on the host board instead of inside the module.)

Reference:
http://en.wikipedia.org/wiki/SFP_transceiver

A transceiver is a device that has both a transmitter and a receiver which are combined and share common circuitry or a single housing. If no circuitry is common between transmit and receive functions, the device is a transmitter-receiver. The term originated in the early 1920s. Technically, transceivers must combine a significant amount of the transmitter and receiver handling circuitry. Similar devices include transponders, transverters, and repeaters.

Transceivers are called Medium Attachment Units (MAUs) in IEEE 802.3 documents.

Reference:
http://en.wikipedia.org/wiki/Transceiver

Representational State Transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The terms “Representational State Transfer” and “REST” were introduced in 2000 in the doctoral dissertation of Roy Fielding, one of the principal authors of the Hypertext Transfer Protocol (HTTP) specification. The terms have since come into widespread use in the networking community.

REST strictly refers to a collection of network architecture principles which outline how resources are defined and addressed. The term is often used in a looser sense to describe any simple interface which transmits domain-specific data over HTTP without an additional messaging layer such as SOAP or session tracking via HTTP cookies. These two meanings can conflict as well as overlap. It is possible to design any large software system in accordance with Fielding’s REST architectural style without using HTTP and without interacting with the World Wide Web. It is also possible to design simple XML+HTTP interfaces which do not conform to REST principles, and instead follow a model of remote procedure call. The difference between the uses of the term “REST” causes some confusion in technical discussions.

Systems which follow Fielding’s REST principles are often referred to as “RESTful”.

Refernce:
http://en.wikipedia.org/wiki/Representational_State_Transfer

Event-driven architecture (EDA) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events.

An event can be defined as "a significant change in state". For example, when a consumer purchases a car, the car's state changes from "for sale" to "sold". A car dealer's system architecture may treat this state change as an event to be detected, produced, published and consumed by various applications within the architecture.

This architectural pattern may be applied by the design and implementation of applications and systems which transmit events among loosely coupled software components and services. An event-driven system typically consists of event consumers and event producers. Event consumers subscribe to an intermediary event manager, and event producers publish to this manager. When the event manager receives an event from a producer, the manager forwards the event to the consumer. If the consumer is unavailable, the manager can store the event and try to forward it later. This method of event transmission is referred to in message-based systems as "store and forward" .

Building applications and systems around an event-driven architecture allows these applications and systems to be constructed in a manner that facilitates more responsiveness, because event-driven systems are, by design, more normalized to unpredictable and asynchronous environments.

Event-driven architecture complements service-oriented architecture (SOA) because services can be started by triggers such as events.

Computing machinery and sensing devices can detect state changes of objects or conditions and create events which can then be processed by a service or system. Event triggers are conditions that result in the creation of an event.

Reference:
http://en.wikipedia.org/wiki/Event_Driven_Architecture

Operations Support Systems (also called Operational Support Systems or OSS) are computer systems used by telecommunications service providers. The term OSS most frequently describes "network systems" dealing with the telecom network itself, supporting processes such as maintaining network inventory, provisioning services, configuring network components, and managing faults. The complementary term Business Support Systems or BSS is a newer term and typically refers to "business systems" dealing with customers, supporting processes such as taking orders, processing bills, and collecting payments. The two systems together are often abbreviated BSS/OSS or simply B/OSS.

The term OSS was historically used to include both network and business systems. It is still sometimes used in this sense, which can cause some confusion. When used in this way, the term OSS may be seen as inclusive of BSS.

Reference:
http://en.wikipedia.org/wiki/Operational_Support_Systems

TR-069 (short for Technical Report 069) is a DSL Forum technical specification entitled CPE WAN Management Protocol (CWMP). It defines an application layer protocol for remote management of end-user devices.

As a bidirectional SOAP/HTTP based protocol it provides the communication between CPE and Auto Configuration Servers (ACS). It includes both a safe auto configuration and the control of other CPE management functions within an integrated framework. In the course of the boom of the broadband market, the number of different Internet access possibilities grew as well (e.g. modems, routers, gateways, Set-top box, VoIP-phones). At the same time the configuration of this equipment became more complicated -- too complicated for the end-users. For this reason the TR-069 standard was developed. It provides the possibility of auto configuration of these access types. The technical specifications are managed and published by the DSL Forum. Using TR-069 the terminals can get in contact with the Auto Configuration Servers (ACS) and establish the configuration automatically. Accordingly other service functions can be provided. TR-069 is the current standard for activation of terminals in the range of DSL broadband market. Other fora, such as Home Gateway Initiative (HGI) and DVB, are endorsing CWMP as the protocol for remote management of home network devices (e.g. the HGI gateway) and terminals (e.g. the DVB IPTV STB).

Functions supported by TR-069:
Autoconfiguration and dynamic service activation
initial CPE configuration
remote CPE configuration
firmware management
version management
update management
status and performance control
logfile analysis and dynamic messages
diagnostics
connectivity and service control.
In the future TR-069 will control many additional options of the CPEs additionally to the pure standards for activation:

enquiry of the equipment functions
enquiry of information, diagnostics, status and capacity
firmware management
automatic process-controlled alarm
irrespective gateway data model, in access with TR-064 it is upgradeable with secondary equipment and functions

Reference:
http://en.wikipedia.org/wiki/TR-069

A broadband remote access server (BRAS) routes traffic to and from the digital subscriber line access multiplexers (DSLAM) on an Internet service provider's (ISP) network.

The BRAS sits at the core of an ISP's network, and aggregates user sessions from the access network. It is at the BRAS that an ISP can inject policy management and IP Quality of Service (QoS).

The specific tasks include:

Aggregates the output from DSLAMs
Provides user PPP sessions or IP over ATM sessions
Enforces quality of service (QoS) policies
Routes traffic into an Internet service provider’s backbone network
A DSLAM collects data traffic from multiple subscribers into a centralized point so that it can be uploaded to the router over a Frame Relay, ATM, or Ethernet connection.

The router provides the logical termination for PPP sessions. These may be PPP over Ethernet (PPPoE) or PPP over ATM (PPPoA) encapsulated sessions. By acting as the PPP termination point, the BRAS is responsible for assigning session parameters such as IP addresses to the clients. The BRAS is also the first IP hop from the client to the Internet.

The BRAS is also the interface to authentication, authorization and accounting systems (see RADIUS)

Reference:
http://en.wikipedia.org/wiki/Bras