Showing posts with label ieee. Show all posts
Showing posts with label ieee. Show all posts

Friday, July 19, 2019

The IEEE 802.16m Reference Model


Figure below illustrates the IEEE 802.16 reference model. The data link layer of IEEE 802.16 standard comprises three sub-layers. The service-specific convergence sub-layer (CS) provides any transformation or mapping of network-layer data packets into MAC SDUs. On the transmitter side, the CS receives the data packets through the CS Service Access Point (SAP) and delivers MAC SDUs to the MAC Common Part Sub-layer (MAC CPS) through the MAC SAP. This includes classifying network-layer SDUs and associating them with the proper MAC Service Flow Identifiers (SFID) and Connection Identifiers (CID). The convergence sub-layer also includes payload header suppression function to compress the higher-layer protocol headers. Multiple CS specifications are provided for interfacing with various network-layer protocols such as Asynchronous Transfer Mode (ATM)i and packet-switched protocols such as IP or Ethernet. The internal format of the CS payload is unique to the CS, and the MAC CPS is not required to understand the format of or parse any information from the CS payload.  


The IEEE 802.16 reference model

The MAC CPS provides the core MAC functionality of system access, bandwidth allocation, connection establishment, and connection maintenance. It can receive data from the various convergence sub-layers, through the MAC SAP classified into particular MAC connections. An example of MAC CPS service definition is given in reference. The Quality of Service (QoS) is further applied to the transmission and scheduling of data over the physical layer. 

The MAC also contains a separate security sub-layer providing authentication, secure key exchange, and encryption. The user data, physical layer control, and statistics are transferred between the MAC CPS and the Physical Layer (PHY) via the PHY SAP which is implementation-specific. The IEEE 802.16 physical layer protocols include multiple specifications, defined through several amendments and revisions, each appropriate for a particular frequency range and application.

The IEEE 802.16 compliant devices include mobile stations or base stations. Given that the IEEE 802.16 devices may be part of a larger network, and therefore would require interfacing with entities for management and control purposes, a Network Control and Management System (NCMS) abstraction has been introduced in the IEEE 802.16 standard as a “black box” containing these entities. The NCMS abstraction allows the physical and MAC layers specified in the IEEE 802.16 standard to be independent of the network architecture, the transport network, and the protocols used in the backhaul, and therefore would allow greater flexibility. The NCMS entity logically exists at both BS and MS sides of the radio interface. Any necessary inter-BS coordination is coordinated through the NCMS entity at the BS. An IEEE 802.16 entity is defined as a logical entity in an MS or BS that comprises the physical and MAC layers on the data, control, and management planes.

The IEEE 802.16f amendment (currently part of IEEE 802.16-2009 standard) provided enhancements to IEEE 802.16-2004 standard, defining a management information base (MIB), for the physical and medium access control layers and the associated management procedures. The management information base originates from the Open Systems Interconnection Network Management Model and is a type of hierarchical database used to manage the devices in a communication network. It comprises a collection of objects in a virtual database used to manage entities such as routers and switches in a network.

The IEEE 802.16 standard describes the use of a Simple Network Management Protocol (SNMP),ii i.e., an IETF protocol suite, as the network management reference model. The standard consists of a Network Management System (NMS), managed nodes, and a service flow database. The BS and MS managed nodes collect and store the managed objects in the form of WirelessMAN Interface MIB and Device MIB that are made available to network management system via management protocols, such as SNMP. A Network Control System contains the service flow and the associated Quality of Service information that have to be provided to BS when an MS enters into the network. The Control SAP (C-SAP) and Management SAP (M-SAP) interface the control and management plane functions with the upper layers. The NCMS entity presents within each MS. The NCMS is a layer-independent entity that may be viewed as a management entity or control entity. Generic system management entities can perform functions through NCMS and standard management protocols can be implemented in the NCMS. If the secondary management connection does not exist, the SNMP messages, or other management protocol messages, may go through another interface in the customer premise or on a transport connection over the air interface. Figure 3-4 describes a simplified network reference model. Multiple mobile stations may be attached to a BS. The MS communicates to the BS over the air interface using a primary management connection, basic connection or a secondary management connection. The latter connection types have been replaced with new connection types in IEEE 802.16m standard




Sunday, June 6, 2010

IEEE 802.16e-2005 Specification

The IEEE 802.16e-2005 specification defines the mobile WiMAX network protocols and the related message sequences. The specification consists of the PHY and the MAC layers, as shown in Figure 1. The MAC layer is composed of a security sublayer, a MAC common part sublayer, and a convergence sublayer.


Add a Note Here
Figure 1: IEEE 802.16e-2005 protocol layers.
Add a Note HereData transmission between a BS and a SS at the PHY layer relies on the resource allocation of data burst through the OFDMA scheme. A BS can transmit to multiple SSs concurrently in the downlink (DL) direction in separate subchannels or separate symbols; similarly, multiple SSs can transmit to the same BS concurrently in the uplink (UL) direction in separate subchannels or separate symbols. Each channel width is from 1.25 to 20 MHz, which spreads to different frequency bands. Therefore, the PHY layer supports orthogonal subchannels for multiple accesses. This design can reduce interference and improve capacity. Moreover, it has the advantages of flexible subchannelization and bandwidth allocation.
Add a Note HereThe security sublayer is to ensure the privacy of subscribers across the WiMAX network by encrypting connections between a SS and a BS. In addition, a BS can protect against unauthorized access to data transport services by enforcing encryption of the associated service flows across the network. Privacy employs an authenticated client/server key management protocol in which a BS, the server, controls distribution of keying material to a SS, the client. Additionally, the basic privacy mechanisms are strengthened by adding digital-certificate-based SS authentication to its key management protocol.
Add a Note HereOver the security sublayer, there are the MAC common part sublayer and the convergence sublayer. The MAC common part sublayer utilizes a shared medium mechanism to efficiently handle the resource of communication links. On top of the MAC common part sublayer is the convergence sublayer, which includes MAC service access points (APs). The MAC layer functionalities in IEEE 802.16e-2005 specification are illustrated in Figure 2.


Add a Note Here
Figure 2: Medium Access Control (MAC) layer functionalities in the IEEE 802.16e-2005 specification.
Add a Note HereIn summary, the IEEE 802.16e-2005 specification offers improvements over the technology specified by the original fixed WiMAX standard. These significant improvements can cost-effectively deliver broadband services to end-users, offering increased performance in NLOS environments for mobility and fixed indoor applications. These improvements can be categorized as follows.

§  Add a Note HereMobility: The support for mobility is the major feature of mobile WiMAX, which introduces new MAC for handover and allows a SS to maintain a connection when moving from one BS to another. Mobile WiMAX is designed to support mobility applications up to 160 km/h.
§  Add a Note HereHigh availability: High connection availability in NLOS environments can be supported in mobile WiMAX by using advanced antenna, channel coding, subchannelization, and dynamic modulation technologies to increase link budget.
§  Add a Note HereNLOS performance: New technologies have been introduced in mobile WiMAX. These include support for intelligent antenna technology, such as Multiple-Input Multiple-Output (MIMO) and adaptive antenna system (AAS), high-performance coding, such as turbo coding (TC), and a Hybrid Automatic Repeat reQuest (HARQ) mechanism for increasing NLOS performance.
§  Add a Note HereSecurity: Based on the security features of the fixed WiMAX standard, the mobile WiMAX specification introduces a number of enhancements. For example, the AES as well as 3DES are now a mandatory feature. New high-performance coding schemes, such as TC and low-density parity check (LDPC), are included. These features enhance the security of the mobile WiMAX air interface.
§  Add a Note HereQoS: Both the connection and service-type-based QoS are designed to meet the requirements of mobile broadband services. These two QoS mechanisms manage both UL and DL directions and support two-way traffic, such as VoIP. The mobile WiMAX QoS has the features of service multiplexing, low data latency, and varying granularity to support real-time broadband multimedia applications.

Friday, April 2, 2010

Support of Beamforming in the IEEE 801.16 Standards


Add a Note HereBeamforming is defined in IEEE 802.16-2004 and in 802.16e. This feature is not in the set of the fixed WiMAX profiles. For the mobile WiMAX profiles, this feature is mandatory to be supported by the MS and optional for the BS. For the mobile WiMAX, several mechanisms that enhance the performance and operation of beamforming are provisioned.
Add a Note HereIn the downlink, in order to be able to beamform several users at the same and on different subchannels, a zone is dedicated (indicated in the DL-MAP). This region, labelled (2) in Figure 1, contains permutations with dedicated pilot channels. This means that an MS receiving a burst in this region only takes as valid pilots the pilots associated with the subchannel it has been allocated.

Add a Note HereFigure 1: Example of a frame with regions supporting AAS operation
Add a Note HereIn the uplink, as mentioned previously, the beamforming mechanisms can be applied on any MS. However, to improve the performance and to help the BS in detecting/measuring the interference experienced by the users it wants to serve, a specific signalling zone may be allocated: the uplink sounding zone (indicated by UIUC=13). Actually, the BS may ask some MS to transmit a signal in this zone so that the BS can evaluate the interference on some subcarriers for those MSs.

Add a Note HereFinally, in order to limit the signalling overhead, the WiMAX solution employing beamforming may use the compressed maps and submaps to transmit the common signalling messages (DL-MAP/UL-MAP). Indeed, this permits different modulation, coding and repetition schemes to be applied to several zones in the DL-MAP/UL-MAP message. This solution can also be employed in the case of MIMO or the support of the HARQ.
Related Posts with Thumbnails