【未解决】搞懂rcsjta的项目的编译和测试的逻辑如何上手

• Albatros RCS 5.1 standard
• Blackbird RCS 5.2 standard

• Blackbird意味着RCS 5.2的标准
• GSMA针对RCS的商业推广名称是：Joyn

-----------------------------------
 Supported standards at 07/09/2012
-----------------------------------

IETF:
-----
RFC 1321 - The MD5 Message-Digest Algorithm
RFC 2327 - SDP: Session Description Protocol
RFC 2373 - IP Version 6 Addressing Architecture
RFC 2392 - Content-ID and Message-ID Uniform Resource Locators
RFC 2617 - HTTP Authentication: Basic and Digest Access Authentication
RFC 3261 - SIP: Session Initiation Protocol
RFC 3263 - Session Initiation Protocol (SIP): Locating SIP Servers
RFC 3264 - An Offer/Answer Model with the Session Description Protocol (SDP)
RFC 3265 - Session Initiation Protocol (SIP) Specific Event Notification
RFC 3325 - Private Extensions to the Session Initiation Protocol (SIP) forAsserted Identity within Trusted Networks
RFC 3339 - Date and Time on the Internet
RFC 3455 - Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)
RFC 3515 - The Session Initiation Protocol (SIP) Refer Method
RFC 3550 - RTP: A Transport Protocol for Real-Time Applications
RFC 3608 - Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration
RFC 3840 - Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
RFC 3856 - A Presence Event Package for the Session Initiation Protocol (SIP)
RFC 3857 - A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)
RFC 3858 - An Extensible Markup Language (XML) Based Format for Watcher Information
RFC 3862 - Common Presence and Instant Messaging (CPIM): Message Format
RFC 3863 - Presence Information Data Format (PIDF)
RFC 3891 - The Session Initiation Protocol (SIP) "Replaces" Header
RFC 3903 - Session Initiation Protocol (SIP) Extension for Event State Publication
RFC 3966 - The tel URI for Telephone Numbers
RFC 3994 - Indication of Message Composition for Instant Messaging
RFC 4007 - IPv6 Scoped Address Architecture
RFC 4028 - The Session Timers in the Session Initiation Protocol (SIP)
RFC 4145 - TCP-Based Media Transport in the Session Description Protocol (SDP)
RFC 4566 - SDP: Session Description Protocol
RFC 4662 - A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists
RFC 4480 - RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
RFC 4481 - Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals
RFC 4961 - Symmetric RTP / RTP Control Protocol (RTCP)
RFC 4975 - The Message Session Relay Protocol (MSRP)
RFC 5262 - Presence Information Data Format (PIDF) Extension for Partial Presence
RFC 5438 - Instant Message Disposition Notification (IMDN)
RFC 5547 - A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
RFC 5626 - Managing Client-Initiated Connection in the Session Initiation Protocol
RFC 5627 - Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)
RFC 5839 - An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification"
RFC 6135 - An Alternative Connection Model for the Message Session Relay Protocol (MSRP)
RFC 6223 - Indication of Support for Keep-Alive

draft-ietf-sip-uri-list-conferencing-01     - Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)
draft-ietf-sip-multiple-refer-01     - Referring to Multiple Resources in the Session Initiation Protocol (SIP)
draft-ietf-simple-imdn-04         - Instant Message Disposition Notification
draft-ietf-mmusic-file-transfer-mech-03     - A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
draft-ietf-simple-msrp-sessmatch-10     - Session Matching Update for the Message Session Relay Protocol (MSRP)
draft-kaplan-dispatch-session-id-03     - A Session Identifier for the Session Initiation Protocol (SIP)

3GPP:
-----
TS 24.229 - IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP), Stage 3
TS 24.279 - Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services, Stage 3

OMA:
----
Instant Messaging using SIMPLE Architecture, v1.0
Instant Messaging Requirements, v1.0
Instant Messaging using SIMPLE, v1.0
Presence SIMPLE Architecture, v2.0
Resource List Server (RLS) XDM Specification, v2.0

GSMA:
-----
RCS Release 1 - Functional Description
RCS Release 1 - Technical Realization
RCS Release 2 - Functional Description
RCS Release 2 - Technical Realization
RCS Release 2 - Endorsement of OMA SIP/SIMPLE IM 1.0
RCS Release 2 - Management Objects
RCS-e Version 1.1 - Services and Client Specification
RCS-e Version 1.2.1 - Services and Client Specification
RCS-e GSMA RCS IOT RCS-e Implementation Guidelines 2.1
RCS-e GSMA RCS IOT RCS-e Implementation Guidelines 3.1

IR74 - Video Share Interoper ability Specification
IR79 - Image Share Interoperability Specification

Main branches
master is the official release of the project containing the last stable release.
* RCS Crane Priority Release scope: RCS 5.3
* TAPI 1.6.1
* Go to branch. 

tapi_1.6.1 contains the Crane Priority Release TAPI 1.6.1 release.
* RCS Blackbird scope: RCS 5.30 specifications
* TAPI 1.6.1
* Go to branch.

tapi_1.5.1 contains the Blackbird TAPI 1.5.1 release.
* RCS Blackbird scope: RCS 5.0 and 5.1 specifications including RCS-e 1.2.2 & Hot Fixes
* TAPI 1.5.1
* Go to branch.

albatros contains the Albatros release.
* RCS Albatros 2.0 scope
* Albatros TAPI
* Go to branch.
Temp branches
securitymodel3 contains an implementation of the security model defined by GSMA to control TAPI access.
* RCS Blackbird scope: RCS 5.0 and 5.1 specifications including RCS-e 1.2.2 & Hot Fixes
* TAPI 1.5
* Security Model http://www.gsma.com/network2020/wp-content/uploads/2015/06/RCC-55-v2-0.pdf
* Go to branch.

cpm contains a CPM/CMS implementation for chat and messaging.
* IMAP stack
* Go to branch.

tapi_0.9.0 contains the Blackbird TAPI pre release.
* RCS Blackbird scope: RCS 5.0 and 5.1 specifications including RCS-e 1.2.2 & Hot Fixes
* First TAPI
* Go to branch.

## Main branches ##

**`master`** is the official release of the project containing the last stable release.
  * RCS Crane Priority Release scope: RCS 5.3
  * TAPI 1.6.1
  * [Go to branch.](https://github.com/android-rcs/rcsjta/tree/master)
<br></li></ul>

**`tapi_1.6.1`** contains the Crane Priority Release TAPI 1.6.1 release.
  * RCS Blackbird scope: RCS 5.30 specifications
  * TAPI 1.6.1
  * [Go to branch.](https://github.com/android-rcs/rcsjta/tree/tapi_1.6.1)
<br>


**`tapi_1.5.1`** contains the Blackbird TAPI 1.5.1 release.
  * RCS Blackbird scope: RCS 5.0 and 5.1 specifications including RCS-e 1.2.2 & Hot Fixes
  * TAPI 1.5.1
  * [Go to branch.](https://github.com/android-rcs/rcsjta/tree/tapi_1.5.1)
<br>

**`albatros`** contains the Albatros release.
  * RCS Albatros 2.0 scope
  * Albatros TAPI
  * [Go to branch.](https://github.com/android-rcs/rcsjta/tree/albatros)
<br>


## Temp branches ##

**`securitymodel3`** contains an implementation of the security model defined by GSMA to control TAPI access.
  * RCS Blackbird scope: RCS 5.0 and 5.1 specifications including RCS-e 1.2.2 & Hot Fixes
  * TAPI 1.5
  * Security Model http://www.gsma.com/network2020/wp-content/uploads/2015/06/RCC-55-v2-0.pdf
  * [Go to branch.](https://github.com/android-rcs/rcsjta/tree/securitymodel3)
<br>


**`cpm`** contains a CPM/CMS implementation for chat and messaging.
  * IMAP stack
  * [Go to branch.](https://github.com/android-rcs/rcsjta/tree/cpm)
<br>


**`tapi_0.9.0`** contains the Blackbird TAPI pre release.
  * RCS Blackbird scope: RCS 5.0 and 5.1 specifications including RCS-e 1.2.2 & Hot Fixes
  * First TAPI
  * [Go to branch.](https://github.com/android-rcs/rcsjta/tree/tapi_0.9.0)

• TAPI 1.5
• TAPI 1.5.1 specification
• /Users/xxx/dev/xxx/RCS/rcsjta/docs/tapi/RCC.53_v3.0_1.5.1-r1.docx
• Javadoc
• https://rawgit.com/android-rcs/rcsjta.javadoc/javadoc1.5/reference/packages.html
• TAPI 1.6
• TAPI 1.6.1 specification
• /Users/xxx/dev/xxx/RCS/rcsjta/docs/tapi/RCC.53_CR1005_1.6.1.docx
• Javadoc
• https://rawgit.com/android-rcs/rcsjta.javadoc/javadoc1.6/reference/packages.html

package
com.gsma.services.rcs
The RCS service is implemented into an Android background service which offers a high level API: the RCS Terminal API.
The RCS API is a client/server interface based on database providers, AIDL API & Intents. Several UI may be connected at a time to manage RCS events and to interact with the single stack instance running in background.
The RCS API permits to implement RCS application (e.g. enhanced address book, content sharing app, chat view, widgets) by hiding RCS protocols complexity.
The RCS API offers the following service API:
- Capability API: contact capabilities discovery.
- Chat API: 1-1 chat and group chat.
- File Transfer API: transfer a file.
- Video Share API: live video sharing during a CS call.
- Image Share API: image sharing during a CS call.
- UX API: links third party applications with RCS applications.
The RCS API uses the following Android concepts:
- Intents mechanism to broadcast incoming events (e.g. notification) and incoming invitations to any Android activity or broadcast receiver which are declared in the device.
- AIDL interfaces to initiate and to manage session in real time (start, session monitoring, stop). Session events are managed thanks to callback mechanism.
Note: Methods of the RCS API throw an exception if the RCS service is not available, not initialized or not registered to the IMS platform.
Note: Remote application exceptions are not yet supported by the AIDL SDK, a generic AIDL exception is thrown instead.
Note: The supported formats for a contact used as a method parameter are:
- Phone number in national or international format (e.g. +33xxx).
- SIP address (e.g. "John" ).
- SIP-URI (e.g. sip:+33xxx@domain.com).
- Tel-URI (e.g. tel:+33xxx).

• 对应的SDK=RCSJTA SDK：
• 1.5
• https://github.com/android-rcs/rcsjta.build/tree/tapi_1.5
• https://github.com/android-rcs/rcsjta.build/blob/tapi_1.5/rcsjta_sdk_20170309-091924.zip
• 1.6
• https://github.com/android-rcs/rcsjta.build/tree/tapi_1.6
• https://github.com/android-rcs/rcsjta.build/blob/tapi_1.6/rcsjta_sdk_20170309-070206.zip

• /Users/xxx/dev/xxx/RCS/rcsjta/
• docs
• RCSJTA_open_source.ppt
• tapi
• wiki
• TAPI_architecture.ppt
• TAPI_capabilities_contact.ppt
• TAPI_chat.ppt

转载请注明：在路上 » 【未解决】搞懂rcsjta的项目的编译和测试的逻辑如何上手