1. New SOIS Reference Architecture
SOIS architecture has two reference models, one is the service reference model(in the Yellow book), the other is the layered communications reference model. According to the discussion on 9th November , the communications reference model is updated as follows.

2. New SOIS Reference Architecture
Application Layer: include architecture specific application support services and device services that supporting MO services/PUS services/Application specific Services, which are also in this layer. SOIS use EDS to define the SAPs to these services and the devices. Application support services may include Message Transfer Service(MTS, silver book), Device Data Pooling Service(DDPS, silver book), or any other agency defined services. Device Services may include Device access Service(DAS, silver book), Device Virtualization Service(DVS, silver book),Time Access Service (TAS, silver book), File and Packet Store Service (FPSS, silver book), or any other agency defined services Existing CCSDS application protocols such as BP、AMS、CFDP、etc. and other protocols can be used to support those services.
Transfer Layer：include architecture specific internetwork transfer services to be used for data exchanging among different subnetworks. SAPs of these services will be defined by EDS which is SOIS architecture specific . These services may be implemented using existing transport and network protocols such as LTP、TCP、UDP、IP、etc.
Subnetwork Layer：defines SAPs for a single subnet, which may be implemented by several subnetwork convergence protocols. Normally this layer include OSI layer1~2 protocols, but for some subnet such as TTE, it may optionally include OSI layer 3~4 protocols on top of include OSI layer1~2 protocols. The services defined by SOIS include Packet Service(PS)、Memory Access Service(MAS)、 Synchronisation Service (SS) 、Device Discovery Service(DDS)、 Test Service(TS).

3. New SOIS Reference Architecture
User Case 1

4. New SOIS Reference Architecture
User Case 2

5. New SOIS Reference Architecture
User Case 3