UniPro(R) Specifications

MIPI Alliance Launches M-PHY v2.0 + UniPro v1.41 Specifications

Click here for more information - www.mipi.org/mphyunipro

The goal of the UniPro working group is to develop an open specification layered protocol. Main features and capabilities include high bandwidth, application agnostic, support for a network and forward compatibility to address market needs. Beginning with its first released specification in 2007, the group has continued to deliver a specification which meets its goals.

Specifications are available to MIPI members only. For more information on joining MIPI, please go to Join MIPI.

  • UniPro Specification v1.41 – Active (both the base document and corresponding full stack SDL document) 

Specification for Unified Protocol v1.41

Base Document

Introduction

The Unified Protocol (UniPro) v1.41 specification, including the primary document (MIPI01) and its corresponding formal reference model (SDL) document (MIPI02), defines a layered protocol for interconnecting devices and components within mobile device systems. It is applicable to a wide range of component types including application processors, co-processors and modems, as well as different types of data traffic including control messages, bulk data transfer and packetized streaming. Implementing the UniPro specification reduces time-to-market and design costs by simplifying the interconnection of peripherals. In addition, the extensible nature of the specification simplifies new feature implementation.

Target applications for UniPro include wireless handsets, tablets/netbooks, digital cameras and multimedia devices. UniPro is optimized for mobile applications and scalable from single link to full network. 

The document references the MIPI Alliance specification for UniPro: SDL State Machines for formal definition of PHY Adapter for M-PHY (L1.5), Data Link (L2), Network (L3), Transport (L4), layer protocols and Device Management Entity (DME).

To aid in understanding the concepts presented in this specification, the UniPro description is loosely based on the ISO OSI Reference Model (OSI/RM). See section 4.3 for more information on the similarities and differences to the OSI/RM.  

Scope

This document defines the protocol used to transfer data between Devices that implement the UniPro specification. This includes definitions of data structures, such as Packets and Frames, used to convey information across the Network. In addition, flow control, error handling, power and state management, and connection services are also within the scope of this document.

The PHY Adapter, Data Link, Network and Transport layer protocols are described in Section 5, Section 6, Section 7 and Section 8, respectively, as well as in [MIPI02]. The DME (Section 9) is also described in [MIPI02].
The electrical interface, physical layer timing and encoding, application-specific protocols and command sets are out of scope for this document.

Figure 1 shows the scope of this document as it relates to the OSI/RM.

    SSS

Target applications for UniPro include wireless handsets, tablets/netbooks, digital cameras and multimedia devices. UniPro is optimized for mobile applications and scalable from single link to full network.Scope

Scope 

The document references the MIPI Alliance specification for UniPro: SDL State Machines for formal definition of PHY Adapter for M-PHY (L1.5), Data Link (L2), Network (L3), Transport (L4), layer protocols and Device Management Entity (DME).
 

To aid in understanding the concepts presented in this specification, the UniPro description is loosely based on the ISO OSI Reference Model (OSI/RM). See section 4.3 for more information on the similarities and differences to the OSI/RM. Target applications for UniPro include wireless handsets, tablets/netbooks, digital cameras and multimedia devices. UniPro is optimized for mobile applications and scalable from single link to full network. 

The document references the MIPI Alliance specification for UniPro: SDL State Machines for formal definition of PHY Adapter for M-PHY (L1.5), Data Link (L2), Network (L3), Transport (L4), layer protocols and Device Management Entity (DME).
 

To aid in understanding the concepts presented in this specification, the UniPro description is loosely based on the ISO OSI Reference Model (OSI/RM). See section 4.3 for more information on the similarities and differences to the OSI/RM. 

Target applications for UniPro include wireless handsets, tablets/netbooks, digital cameras and multimedia devices. UniPro is optimized for mobile applications and scalable from single link to full network.

 

The document references the MIPI Alliance specification for UniPro: SDL State Machines for formal definition of PHY Adapter for M-PHY (L1.5), Data Link (L2), Network (L3), Transport (L4), layer protocols and Device Management Entity (DME).
 

To aid in understanding the concepts presented in this specification, the UniPro description is loosely based on the ISO OSI Reference Model (OSI/RM). See section 4.3 for more information on the similarities and differences to the OSI/RM. 

Target applications for UniPro include wireless handsets, tablets/netbooks, digital cameras and multimedia devices. UniPro is optimized for mobile applications and scalable from single link to full network.

 

The document references the MIPI Alliance specification for UniPro: SDL State Machines for formal definition of PHY Adapter for M-PHY (L1.5), Data Link (L2), Network (L3), Transport (L4), layer protocols and Device Management Entity (DME).
 

To aid in understanding the concepts presented in this specification, the UniPro description is loosely based on the ISO OSI Reference Model (OSI/RM). See section 4.3 for more information on the similarities and differences to the OSI/RM. 

Target applications for UniPro include wireless handsets, tablets/netbooks, digital cameras and multimedia devices. UniPro is optimized for mobile applications and scalable from single link to full network. 

The document references the MIPI Alliance specification for UniPro: SDL State Machines for formal definition of PHY Adapter for M-PHY (L1.5), Data Link (L2), Network (L3), Transport (L4), layer protocols and Device Management Entity (DME).

Purpose

This specification can be used by manufacturers to design products that adhere to MIPI Alliance specifications for host processor and peripheral interfaces.

Implementing the UniPro specification reduces the time-to-market and design cost of mobile Devices by simplifying the interconnection of products from different manufacturers. In addition, implementing new features is simplified due to the extensible nature of the UniPro specification.

Specification for Unified Protocol v1.41

SDL Document

Overview

The SDL model of the UniPro stack is a normative companion document to MIPI Alliance Specification for Unified Protocol (UniPro ), v1.41. The behavior of UniPro's PHY Adapter (M-PHY only), Data Link, Network, Transport and DME layers are formalized using the SDL language (ITU-T Recommendation Z.100 (2002): Specification and Description Language [ITUT01])

The formality of the UniPro SDL model is useful for resolving any text ambiguities or for getting an impression of how the described functionality might be partitioned into more manageable functional entities. In case of any mismatches between [MIPI01] and the SDL model, the SDL model has precedence.

The reader can nevertheless find many details of the UniPro specification in [MIPI01] without consulting the SDL description.
Note that, again, the structure of the SDL model does not constrain possible implementations: any implementation which provides identical behavior on its external interfaces to the SDL model is allowed. These external interfaces are the physical medium (wires) attached to the physical layer and the more abstract “ports” which connect the Transport Layer to applications. In this release of UniPro, the DME layer and its interfaces are largely informative, and mainly serve to illustrate how the protocol stack can be configured.

When modeling MIPI Alliance Specification for Unified Protocol v1.41 [MIPI01] in SDL, some SDL-specific choices were made to ease the implementation and testing of the layers as well as overcome limitations of SDL. These choices are documented in the SDL code with comments and, where possible, in the text of this document.

Specifications