T T A S t a n d a r d

Transcription

1 d 정보통신단체표준 ( 국문표준 ) 제정일 : 2015 년 12 월 16 일 개정일 : 2017 년 06 월 xx 일 T T A S t a n d a r RCS 서비스단말연동규격 Advanced Communication Service (Rich Communication Suite) Technical Specification for Mobile Network Operator

2 표준초안검토위원회모바일응용서비스프로젝트그룹 (PG910) 표준안심의위원회전파 / 이동통신기술위원회 (TC9) 성명 소속 직위 위원회및직위 표준번호 표준 ( 과제 ) 제안 박지수 KT 수석 WG9103 의장 표준초안작성자 이신형 네이블 책임 WG9103 간사 사무국담당 김대중 TTA 부장 - 이혜영 TTA 책임 - 본문서에대한저작권은 TTA 에있으며, TTA 와사전협의없이이문서의전체또는일부를상업적목적으로복제또는 배포해서는안됩니다. 본표준발간이전에접수된지식재산권확약서정보는본표준의 부록 ( 지식재산권확약서정보 ) 에명시하고있으며, 이후접수 된지식재산권확약서는 TTA 웹사이트에서확인할수있습니다. 본표준과관련하여접수된확약서외의지식재산권이존재할수있습니다. 발행인 : 한국정보통신기술협회회장발행처 : 한국정보통신기술협회 13591, 경기도성남시분당구분당로 47 Tel : , Fax : 발행일 :

3 서 문 1 표준의목적 이표준은국내이동통신 RCS(Rich Communication Suite) 서비스단말기에서통합 메시지 (RCS, SMS, MMS) 서비스를제공하는경우, 구현해야할 RCS 기능에대한 요구사항을기술하는것을목적으로한다. 2 주요내용요약 이표준은이동통신 RCS 서비스를위한단말연동구간에정의되는규격으로서버및단말기의관련기능, 정보의흐름을규정하는규격이다. RCS 서비스를제공하기위한핵심적인프로토콜및전송프로토콜을정의하고단말연동기능을정의한다. 또한국제표준및단체규격등과호환가능하도록정의하여상호연동성을보장한다. 3 인용표준과의비교 3.1 참조표준과의관련성 이표준은 GSMA RCS5.3 표준을기반으로하여국내및국외제품이국내및 국외에동시에서비스제공할수있도록관련국내외표준과의호환성을 고려하였다. 3.2 인용표준과본표준의비교표 GSMA RCS 5.3 비고 1. 적용범위 - 추가 2. 인용표준 - 추가 3. 용어정의 1.3 Definition of Terms 수정 4. 약어 - 추가 5. RCS 서비스네트워크구성도 - 추가 6. 일반요구사항 2. RCS 5 General Procedures 수정 i

4 7. 서비스시나리오 3. RCS 5 Services 수정 8. 국내 RCS 추가요구사항 - 추가 부속서A IMS Registration 동작 - 추가 부속서B MO and Configuration parameters - 추가 ii

5 Preface 1 Purpose of Standard The standard specifies requirements for a mobile terminal (UE) regarding RCS function in order to provide the integrated messaging service (RCS, SMS, MMS). 2 Summary The standard is to describe the mobile RCS UE-to-Network Interface (UNI), which is composed of the related functionality of server and mobile terminal, and message flows between a server and a mobile terminal (UE). Also, the standard defines RCS core, transport protocols and interoperability between mobile terminal and mobile operators networks. The standard follows the international standards and specifications. 3 Relationship to Reference Standards 3.1 Relationship of Reference Standards (Recommendations) The standard is based on GSMA RCS 5.3 standard and consider interoperability with domestic and international standards to provide RCS services both at home and aboard. 3.2 Differences between Reference Standard (recommendation) and this Standard GSMA RCS 5.3 Remarks 2. Constitution and Scope - added 3. Reference Standards (Recommendations) - added 4. Terms and Definitions 1.3 Definition of Terms modified 5. RCS Service Requirements for interworking - added 6. General Requirements 2. RCS 5 General Procedures modified 7. Service Scenarios 3. RCS 5 Services modified 8. Additional Standard - added iii

6 목 차 1 적용범위 (Scope) 1 2 인용표준 (References) 1 3 용어정의 (Definitions) 1 4 약어 (Abbreviations) 1 5 RCS 서비스네트워크구성도 (RCS Service Network Block Diagram) 2 6 일반요구사항 (General Requirements) 기본요구사항 (Basic Requirements) RCS Protocol / Access Technologies 서비스가입절차 (Procedures the joining Service) Multidevice 지원 (Multi-device Support) 보안 (Security) PNB (Personal Network Blacklist) 20 7 서비스시나리오 (Service Scenarios) to-1 Chat Group Chat File Transfer Content Sharing Capability Discovery SPI (Social Presence Information) IP Voice Call IP Video Call (IR.94) Geo location Services Sticker 159 iv

7 8 국내 RCS 추가요구사항 (Additional Standard) User-Agent 정의 (Define User-Agent) 안심문자 (Reliable Message Service) 166 부속서 A IMS Registration 동작 170 부속서 B MO and Configuration parameters 181 부록 Ⅰ-1 지식재산권확약서정보 212 Ⅰ-2 시험인증관련사항 213 Ⅰ-3 본표준의연계 (family) 표준 214 Ⅰ-4 참고문헌 215 Ⅰ-5 영문표준해설서 216 Ⅰ-6 표준의이력 217 v

8 RCS 서비스단말연동규격 (Advanced Communication Service (Rich Communication Suite) Technical Specification for Mobile Network Operator) 1 적용범위 (Scope) 이표준은국내이동통신 RCS(Rich Communication Suite) 서비스단말기에서통합메시지 (RCS, SMS, MMS) 서비스를제공하는경우, 단말기에구현해야할 RCS 기능에대한요구사항을기술하는것을목적으로한다. SMS/MMS 의기능요구사항은각사업자의단말기연동규격을따르도록한다. 2 인용표준 (References) GSMA RCS Advanced Communications Services and Client Specification Version 용어정의 (Definitions) 해당사항없음 4 약어 (Abbreviations) IM MSRP RCS SDP SIP XCAP Instant messaging Message Session Relay Protocol Rich Communication Suite Session Description Protocol Session Initiation Protocol XML Configuration Access Protocol 1

9 5 RCS 서비스네트워크구성도 (RCS Service Network Block Diagram) RCS 서비스를위한네트워크구성도는아래와같으며, TrGW 기능유무에따라 RCS IM 서버에서 TrGW 기능을대신할수있다. Operator A Network Operator B Network RCS-PS RCS-VS RCS-IM(PF) RCS-IM(CF) RCS-IM(CF) RCS-IM(PF) RCS-VS RCS-PS HSS S-CSCF S-CSCF HSS P-CSCF I-CSCF IBCF/TrGW IBCF/TrGW I-CSCF P-CSCF UE SIP DIAMETER XCAP MSRP RTP UE ( 그림 5-1) RCS 서비스를위한네트워크구성도 6 일반요구사항 (General Requirements) 6.1 기본요구사항 (Basic Requirements) 본 RCS 서비스단말연동규격을준수하는 RCS 단말은 RCC.60 을기본으로동작하여 하기규격에서명시하는추가적인기능을수용하여동작하여야한다 단말모드 RCC 의 RCS Device Modes 중 RCS-VoLTE mode 를지원한다. 2

10 6.1.2 Client Type 단말클라이언트는 RCS Embedded/Downloadable Client 2 가지형식으로지원될수 있다 RCS Embedded Client 기본주소록, 갤러리, calling application 에 RCS 메시지앱에진입할수있어야한다 RCS Downloadable Client Embedded Client 가설치되어있을경우 Downloadable Client 는동작하지않아야한다 Addressing and ID 단말은 SIP Request 의 P-Asserted-Identity 혹은 From 헤더값을사용해서발신자의정보를획득하고, P-Asserted-Identity 헤더값이 From 헤더값보다우선한다. 그룹대화의경우 Referred-By 헤더값으로발신자의정보를획득한다. SIP/TEL URI 는아래의형식을따르며동일한형식으로상호변환된다. TEL URI: tel: SIP URI: sip: @domain;user=phone User part 의경우 및 010 형태를모두지원해야하되 TEL URI 와 SIP URI 가모두동일해야한다. + 가없는 Local number 의경우다음과같은형식을따른다. tel:local_number;phone-context=<home_domain_name> Anonymous Address 의경우아래의형식으로기본으로사용하되 USER PART 가 anonymous 라면 Anonymous Address 로판단한다. SIP URI: sip:anonymous@domain APN 지원및 QOS 지원 단말은데이터차단및 WiFi ON 시에도 IMS APN 을통해 IMS 서비스가가능해야한다. 단말은 CONFIGURATION SERVER, CSCF 의 IP 주소를단말내부의 IMS APN 을 지원하기위한 routing table 에등록하여야한다. ( 단대용량 FT 제외 ) 3

11 ACS IP 주소는아래 URL 에각사업자의 MNC, MCC 사용하여 DNS query 를통해획득한다.( CSCF IP 주소는 ACS 에서전달받은 LBO_P-CSCF_Address 를통해획득한다. HTTP FT 는 Internet APN 을활용하여서비스를제공한다. Content 서버 IP 주소는 ACS 에서전달받은 Content-serveruri 값을통해획득한다 RCS 서비스의 IMS SIP 시그널링에사용되는 default Bearer 에대해 QCI 값은 5 가사용된다. < 표 6-1> Packet type 별 APN type, Bearer type 그리고 QCI Index Packet type APN type Bearer type QCI Index 일반 Data packet Internet APN Default bearer 6 (non-gbr) IMS Signaling IMS APN Default bearer 5 (non-gbr) RCS VS (TBD) [RTP/RTCP packet] IMS APN Dedicated bearer (GBR) 엔지니어링모드요구사항 단말은엔지니어링모드에 RCS 설정메뉴를제공해야한다. 6.2 RCS Protocol / Access Technologies RCS Protocol RCS 프로토콜은 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다 Access Technologies Access Technologies 는 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다. 6.3 서비스가입절차 (Procedures the joining Service) 단말 Auto-Configuration Server 연동규격 4

12 Auto-Configurationuration Procedures HTTP(S) based client configuration UE 에서 CONFIGURATION SERVER 의 Session 을할당받기위한 HTTP GET 메시지루틴과, 할당받은 Session 을통해 User Configuration 을전송받는 HTTPS GET 메시지루틴으로구성된다. UE 에서 Session 을할당받기위해 HTTP GET 메시지를전송하면, CONFIGURATION SERVER 는할당한 Session 의정보를 200 OK 메시지의 Set-Cookie header 에넣어전송한다. UE 는해당 Cookie 값을파싱하여 HTTPS GET 메시지의 Cookie header 에넣어해당메시지의 Session 을찾을수있게한다. The Auto-Configuration server URL 은 RCS 서비스를위해 reserved 된 domain 의 config subdomain 을사용하여다음과같이설정한다. a) MCC (Mobile Country Code) : 450 b) MNC (Mobile Network Code) 1) SKT: 2) KT: 3) LGU+: 5

13 ( 그림 6-1) RCS 서비스최초개통시 Configuration 연동 a) HTTP GET (UE -> CONFIGURATION SERVER) GET / HTTP/1.1 Host: Connection: Keep-Alive b) 200 OK (CONFIGURATION SERVER -> UE) with Set-Cookie header HTTP/ OK Set-Cookie: sessionid= d85eab2bb7a121 Connection: close Content-Length: 0 1) Set-Cookie Header 를사용하여 cookie 값을전달한다. c) HTTPS GET (UE -> CONFIGURATION SERVER) with Cookie header GET/?vers=0&IMSI= &rcs_version=5.1B&rcs_profile=joyn_blackbird&client_vendor=LGE& client_version=bifrost- 1.0&terminal_vendor=LGE&terminal_model=D320n&terminal_sw_version=1.0&IMEI= HTTP/1.1 Accept-Language: en Cookie: sessionid= d85eab2bb7a121 Accept: */* User-Agent: Dalvik/1.6.0 (Linux; U; Android 4.4.2; LG-D320 Build/KOT49I.A ) 6

14 Host: Connection: Keep-Alive 1) Server로부터수시한 Resposne의 Set-Cookie Header의값을 Cookie Header 에설정하여전달한다. 2) UE가서버에전송하는 HTTPS GET 메시지의 RequestUri 매개변수는다음과같다. < 표 6-2> (Configuration Procedures) UE 가서버에전송하는 RequestUri 매개변수 URI Parameter vers 0 Configuration 을 update 해야할경우설정 UE 의 configuration 이손상되었다고판단하고, full configuration 을제공한다. 양수 version of the static parameters -1 booting 될때 RCS services 가 disable 된 device/client (including the autoconfiguration query performed) -2 RCS is disabled on the device -3 RCS 가 dormant state 일경우 (i.e. no registration) Ex) vers=1 IMSI IMSI 정보 ( 선택 ) EX) IMSI= rcs_version 5.1B rcs_profile client_vendor joyn_blackbird RCS 서비스 Client 제공 vendor 정보 [String (4 max)] Ex) client_vendor=lge client_version RCS 서비스 Client 버전 Platform 영문 + 숫자 ( 최대 9 자 ) VersionMajor 숫자 ( 최대 2 자 ) VersionMinor 숫자 ( 최대 2 자 ) Ex) client_version=rcsandrd-1.4 terminal_vendor 단말 vendor 정보 [String (4 max)] Ex) terminal_vendor=lge terminal_model 단말 model 정보. Smart Phone Model 정보 [String (10 max)] Ex) terminal_model=d320n 7

15 terminal_sw_version 단말 sw version 정보 Ex) terminal_sw_version=1.0 IMEI IMEI 정보 ( 선택 ) Ex) IMEI= friendly_device_name a user friendly identification for the device( 선택 ) <5.1 규격의 Version 4.0 에추가 > d) 200 OK (CONFIGURATION SERVER -> UE) HTTP/ OK Content-Type: text/xml Connection: close Content-Length: 5079 <?xml version="1.0"?> <wap-provisioningdoc version="1.1"> <characteristic type="vers"> <parm name="version" value="1"/> <parm name="validity" value=" "/> </characteristic> <characteristic type="application">.. </characteristic> </wap-provisioningdoc> 1) Content-Type: text/xml 2) Content: Annex의 Full XML Configuration 참조 Network initiated configuration request Configuration Server 에서 configuration 이변경시단말에변경사항을 SMS 를통해 notification 을전달하고단말은해당 SMS 수신시 CONFIGURATION SERVER 에 Configuration 조회를수행해야한다 SMS 를통한 First time Configuration 변경 Notification CONFIGURATION SERVER 에서각사별 SMS-GW 를통해서 SMS Notification 전송을 요청한다. Configuration 변경 Notification 을위한 SMS 포맷은아래와같다. 8

16 [(UDH header handling as per [3GPP TS ])] 참고 DataCodingScheme = 08 (UCS2) UserDataHeader = UDHL length fields= , Destination port: 0x9199 (37273 in decimal) Source Port: 0x0000 (0 in decimal)" The SMS content IMSI 값에 rcscfg 를붙여서사용한다. 예를들어 IMSI 값이 라면 rcscfg" 와같이사용된다. [ d ] a) 단말은 SIM 에있는 IMSI 값과 match 되는 request 를수신하면아래와같이동작해야한다. 1) 만일 IMS Network 에 REGISTER 가되어있다면 DE-REGISTER 절차를수행한다. 2) HTTP Configuration 절차를수행한다 SMS 를통한 Re-Configuration 변경 Notification CONFIGURATION SERVER 에서각사별 SMSGW 를통해서 SMS Notification 전송을요청한다. Configuration 변경 Notification 을위한 SMS 포맷은아래와같다. DataCodingScheme = 08 (UCS2) UserDataHeader = UDHL length fields= , Destination port: 0x9199 (37273 in decimal) Source Port: 0x0000 (0 in decimal)" The SMS content XML Configuration 에있는 Private_User_Identity parameter 와 rcscfg 를붙여서 사용한다. 예 ) private identity 가 @ims.mnc001.mcc214.3gppnetwork.org 이면해당값은아래와같이사용한다 @ims.mnc001.mcc214.3gppnetwork.org-rcscfg [ d732e6d6e e6d e e f726b2e6f7267] a) 단말은 IMPI 와 match 되는 request 를수신하면아래와같이동작해야한다. 9

17 1) 만일 IMS Network 에 REGISTER 가되어있다면 DE-REGISTER 절차를 수행한다. 2) Version 과 validity parameter 의값을 0 으로설정하고 HTTP Configuration 절차를수행한다. 3) Configuration 절차가완료되면 RCS Client 는 Server 로부터수신한 Configuration 을기반으로 IMS Network 에 REGISTER 절차를수행한다 예외처리 Error Response Auto-Configuration Server 의 Response 와 Response 별로 Client 동작은아래와같다. < 표 6-3> RCS Client 서비스예외처리 Response Use case Client behaviour 200 OK 503 Retry after 200 OK + XML with full configuration 200 OK + XML with version and validity period only 200 OK + XML with version and validity period only and both set to OK + XML with version and validity period only and both set to -1 Initial HTTP request response The server is processing the request/provision New configuration sent to the device No update needed Customer or device are not valid or the customer has been unprovisioned from RCS (temporary) Customer or device are not valid or the customer has been unprovisioned from RCS (permanently) 10 The client sends the HTTPS request including the cookie Retry after the time specified in the RetryAfter header Process configuration, try to register and if successful, not try reconfiguration until the validity period is expired, the device/client is restarted or SIM is changed Retry only after validity period, next restart or SIM change Retry only after next restart or SIM change If a configuration was available, it shall be removed from the client. The client shall no longer retry autoconfiguration until SIM is changed or a factory reset performed. If a configuration was available, it shall be removed from the client.

18 Response Use case Client behaviour 500 Internal Server error (or any other HTTP error except 403) 403 Forbidden 409 Conflict 511 Network Authentication Required The Auto- Configurationuration server is unreachable Internal error during configuration/provisioning Invalid request (e.g. missing parameters, wrong format) A duplicate value was provided for the friendly_device_name Network-based authentication is not possible (e.g. in case of non-ps access). Auto-Configurationuration server missing or down Retry on next reboot/the next time the client starts The configuration is removed in the device and version is set to 0. Retry on next reboot, the next time the client starts The user should be asked to provide another value for the friendly_device_name parameter and the configuration request should be retried including the new value Start non-ps configuration flow as defined in Retry on next reboot, the next time the client starts Empty Body 정상적인처리가되었을경우, 메시지의 Configuration XML 은 configuration version, validity of the configuration 과 configuration body 세가지로구성되며, configuration body 는제공되지않을수도있다. 특정가입자의 RCS 서비스를강제중지하기위해사용한다. Configuration Response 의 Version/Validity 정보를특정한값으로설정하여 RCS 서비스단말로전송하고, 단말에서 RCS 서비스를 disable 시킬수있다. Configuration body 가제공되지않는경우는다음과같다 Configuration 버전이동일한경우 <?xml version="1.0"?> <wap-provisioningdoc version="1.1"> <characteristic type="vers"> 11

19 <parm name= version value= X /> <parm name= validity value= Y /> </characteristic> </wap-provisioningdoc> a) client 에서올라온 version 과 server 에서관리하고있는 configuration 버전이같은경우 1) Version 은 UE 가요청한 vers 값이설정된다. 2) Validity 는 Server Configuration 의 validity 값이설정된다. 3) Configuration Body 는빈값으로설정된다 서비스일시정지인경우 <?xml version="1.0"?> <wap-provisioningdoc version="1.1"> <characteristic type="vers"> <parm name= version value= 0 /> <parm name= validity value= 0 /> </characteristic> </wap-provisioningdoc> a) Service Provider 가해당 Client 의 RCS Service 를 temporary 하게 disable 해야하는경우 1) Version 은 0 값이설정된다. 2) Validity 는 0 값이설정된다. 3) Configuration Body 는빈값으로설정된다. 4) 단말은다음번 booting 시에 configuration 절차를다시수행한다 서비스정지인경우 <?xml version="1.0"?> <wap-provisioningdoc version="1.1"> <characteristic type="vers"> <parm name= version value= -1 /> <parm name= validity value= -1 /> </characteristic> </wap-provisioningdoc> 12

20 a) Service Provider 가해당 Client 의 RCS Service 를 permanent 하게 disable 해야하는경우 1) Version은 -1 값이설정된다. 2) Validity는 -1 값이설정된다. 3) Configuration Body는빈값으로설정된다 Auto-Configuration 조회무응답처리 Auto-Configuration 조회시무응답이거나네트워크연결이되지않을경우에 5 회 재시도하고, RCS 단말에선기존에단말이가지고있는 Auto-Configuration 정보를 이용하여 RCS 서비스이용한다. Configuration 조회는 next reboot 시점에서재시도한다. a) 재시도간격 : 5 초 Auto-Configuration Full body 처리 단말이 Auto-Configuration MO 에 Application node 가포함한경우 configuration 을 항상업데이트한다 XDMS handing XML Document Handling RCS 클라이언트는 IMS Core 접속을위해사업자가제공하는인증방식을따르며아래방식중에서제공된다. XDMS 는 RLS-Services, Resource-lists, Pres-rules, PIDF-manipulation 문서를관리하며, XCAP PUT, GET, DEL 및 Directory GET 을제공한다. RCS 클라이언트는 Directory GET 을통해서 XCAP 문서의상태를확인하고, 문서가없거나버전이다를경우클라이언트에저장된문서기준으로저장한다. RCS 클라이언트는 RCS 5.3 에서정의하는 resource-lists, pres-rules 문서의모든항목을정의해야하며, rls-services 문서에 rcs, rcs_poll Service-URI 를정의하고관리해야한다 Authorizing XCAP Requests 13

21 XDMS 는가입자인증을위해 Aggregation Proxy 기능을수행하며, HTTP Digest Authentication 방식을사용한다. NETWORK A USER A SERVER 1. HTTP Request Unauthorized 3. HTTP Request + Auth Header 4. REQUEST PROCESS 5. Response ( 그림 6-2) HTTP Digest Authorization a) HTTP Request 전송. 인증헤더미포함 GET /services/rls-services/users/sip: @nablecomm.com/index HTTP/1.1 Host: xcap.example.com X-3GPP-Asserted-Identity: sip: @nablecomm.com Connection: close Content-Length: 0 b) USER A 인증을위해 nonce 값이포함된 401 Unauthorized 응답을전송 GET /services/rls-services/users/sip: @nablecomm.com/index HTTP/1.1 Host: xcap.example.com X-3GPP-Asserted-Identity: sip: @nablecomm.com Connection: close Content-Length: 0 c) User ID, Password, nonce, cnonce 값을이용하여인증헤더를생성하고이를포함한 HTTP Request 를전송한다. GET /services/rls-services/users/sip: @nablecomm.com/index HTTP/1.1 Authorization: Digest username=" ",realm="nablecomm.com",qop="auth",nonce="6-0",nc= , uri="/services/rlsservices/users/sip: @nablecomm.com/index",opaque=" ",cnonce="4d ", response="8f2eebd9b97ba040979b8f3fd018049b" Host: xcap.example.com X-3GPP-Asserted-Identity: sip: @nablecomm.com 14

22 Connection: close Content-Length: 0 d) HTTP Digest 인증절차가정상적으로완료되었으면해당요청에대한처리를한다. 인증실패시 400 Bad Request 전송후종료 e) 요청에대한처리결과를전송한다. 1) 향후운영중성능에대한이슈가나온다면인증헤더재사용을통한성능개선을사업자간협의를통해사용여부를결정한다 IMS Registration IMS 단말은 WiFi 연결상태에서도 LTE 및 3G IP 를이용하여 Registration 을수행해야 하며, 데이터차단상태에서도 IMS APN 을이용하여 Registration 해야한다. User A IMS-Core IM PS REGISTER 401 Unauthorized REGISTER 3'rd party REGISTER 200 OK 3'rd party REGISTER 200 OK 200 OK SUBSCRIBE (reg) 200 OK NOTIFY (reg) 200 OK Registration management ( 그림 6-3) IMS Registration 단말은상기 flow 내에서 401 Unauthorized 메시지내의 RAND, AUTH 값을서버로부터전달받아 ISIM/USIM 기반의인증을이용해서 RES 값을생성하여, 다음 Register 메시지에포함하여전달해야한다. IMS Registration 관련한자세한사항은각사의 IMS 단말기규격 을참고하도록한다. a) 3 rd party REGISTER example REGISTER sip:rcs-im.operator_a.net;lr SIP/2.0 15

23 To: Via: SIP/2.0/UDP :5060;branch=z9hG4bK7b3a1e94_ CSeq: 2 REGISTER From: <sip:scscf.operatora.net>;tag=7b3a1e92 Call-ID: b2bua user_a.operatora.net Contact: <sip: :5060> Expires: 8400 Max-Forwards: 69 Content-Length: 0 P-User-Database: P-Charging-Vector: P-Visited-Network-ID: "operatora.net" P-Charging-Function-Addresses: User-Agent: Feature tags that can be upload when IMS Registration 단말은 Registration 시 SIP Contact header 필드의 Feature Tag 에 RCS 서비스를지원 가능한서비스로등록하여야한다. < 표 6-4> Feature tags that can be upload when IMS Registration Service Chat/MSRP-FT HTTP-FT Feature Tag +g.oma.sip-im +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.fthttp a) Extension 을사용해야하기때문에 (Sticker 등 ) Configuration parameter 중 ALLOW RCS EXTENSIONS 은항상 1 이여야한다 Feature Tag Capability Discovery 를통해지원가능한 Feature tag 는다음과같다. < 표 6-5> RCS 제공서비스별 Feature Tag Service Feature Tag 16

24 Service Image Share Video Share Chat Full Store and Forward Group Chat File Transfer File Transfer Thumbnail File Transfer Store and Forward File Transfer via HTTP Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Feature Tag +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.gsma-is Service-id: org.gsma.imageshare Version: 1.0 +g.3gpp.cs-voice Service-id: org.gsma.videoshare Version: 1.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcse.im Service-id: org.openmobilealliance:im-session Version : 1.0 Or Service-id: org.openmobilealliance:chatsession Version : 2.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.fullsfgroupchat Service-Id: org.3gpp.urn:urn-7:3gppapplication. ims.iari.rcs.fullsfgroupchat Version: 1.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcse.ft Service-id: org.openmobilealliance:file-transfer Version : 1.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.ftthumb Service-id: org.openmobilealliance:file-transfer-thumb Version : 2.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.ftstandfw Service-id: org.openmobilealliance:file-transfer Version : 2.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.fthttp Service-id: org.openmobilealliance:file-transfer-http Version :

25 Service Feature Tag IP Based Standalone messaging Video Share outside of a voice call Social presence information IP Voice Call (as per MMTEL) IP Video Call (as per MMTEL) RCS IP Voice Call RCS IP Video Call Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple +g.3gpp.icsi-ref= urn%3aurn-7%3a3gppservice.ims.icsi.oma.cpm.msg,urn%3aurn-7%3a3gppservice.ims.icsi.oma.cpm.largemsg Service-id: org.openmobilealliance:standalonemsg Version: 2.0 +g.3gpp.iari-ref= urn:urn-7:3gpp-application.ims.iari.gsma-vs Service-id: org.gsma.videoshare Version: 2.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcse.sp Service-id: org.3gpp.urn:urn-7:3gppapplication.ims.iari.rcse.sp Version: 1.0 +g.3gpp.icsi-ref= urn%3aurn-7%3a3gppservice.ims.icsi.mmtel Service-id: org.3gpp.urn:urn-7:3gpp-service.ims.icsi.mmtel Version: 1.0 Media capabilities: audio, duplex +g.3gpp.icsi-ref= urn%3aurn-7%3a3gppservice.ims.icsi.mmtel ;video Service-id: org.3gpp.urn:urn-7:3gpp-service.ims.icsi.mmtel Version: 1.0 Media capabilities: audio, video, duplex +g.gsma.rcs.ipcall Service-id: org.3gpp.urn:urn-7:3gppservice.ims.icsi.mmtel.gsma.ipcall Version: 1.0 Media capabilities: audio, duplex +g.gsma.rcs.ipcall;video Service-id: org.3gpp.urn:urn-7:3gppservice.ims.icsi.mmtel.gsma.ipcall Version: 1.0 Media capabilities: audio, video, duplex RCS IP Video Call Tag +g.gsma.rcs.ipvideocallonly 18

26 Service where video media cannot be removed by the user Geolocation PUSH Geolocation PULL Geolocation PULL using File Transfer Sticker Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Tag Service Tuple Feature Tag Service-id: org.3gpp.urn:urn-7:3gppservice. ims.icsi.mmtel.gsma.ipcall.ipvideocallonly Version: 1.0 Media capabilities: audio, video, duplex +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.geopush Service-id: org.3gpp.urn:urn-7:3gppapplication.ims.iari.rcs.geopush Version: 1.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.geopull Service-id: org.3gpp.urn:urn-7:3gppapplication.ims.iari.rcs.geopullft Version: 1.0 +g.3gpp.iari-ref= urn%3aurn-7%3a3gppapplication.ims.iari.rcs.geopullft Service-id: org.3gpp.urn:urn-7:3gppapplication.ims.iari.rcs.geopullft Version: 1.0 +g.3gpp.iari-ref="urn%3aurn-7%3a3gppapplication.ims.iari.rcs.sticker Service-Id: org.3gpp.urn:urn-7:3gppapplication.ims.iari.rcs.sticker 6.4 Multidevice 지원 (Multi-device Support) Multidevice 지원은 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다. 6.5 보안 (Security) RCS 서비스를위해가입자인증및패킷암호화를통해보안기능을제공한다 Access Signaling Security RCS 클라이언트와서버는 Media 보안을위해아래의방식을지원한다. 19

27 a) MSRP over TLS b) Secure RTP (SRTP) c) HTTP Digest Authentication for XCAP d) Username/Password or SASL based authentication at one moment for Message Storage e) HTTP Digest Authentication for Contents Server(File Download) 6.6 PNB (Personal Network Blacklist) RCS 사용자는 resource-lists 문서를사용해서각서비스별차단리스트를관리하고, IM 은발신 / 착신구간에서차단리스트의포함여부를확인하여서비스를차단한다. 차단리스트관리를위한 Resource-lists 문서에추가되는 list 형식은 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다. 20

28 7 서비스시나리오 (Service Scenarios) P-Preferred-Service 헤더의경우 NNI 구간에서는전송하지않는다 to-1 Chat RCS User 간의 1-to-1 Chat 메시지교환을위한절차를기술한다 대화방개설 단말에서발신하는 INVITE 메시지의 expire time 은 1800 초로설정, refresher 는 uac 로설정해야한다. 세션만료시간의 2 분의 1 시간주기로 refresh(sip UPDATE) 를시도해야한다. Subject Header 를설정하지않아야한다. 발신단말은 200OK 수신후 MSRP 세션을수립해야하며이후메시지는 MSRP 를통해전송해야한다. a) Initial Invite 를수신한단말은 RCS MO 에정의된 AutAccept 값에따라아래와같이동작한다. 1) AutAccept = 1 : 자동응답으로수신단말은 Initial Invite 를받으면 200 OK 를전송하고 MSRP 세션을맺는다. 2) AtoAccept = 0 : 수동응답으로대화방진입시까지 200OK 를전송하지않는다. 이동통신사업자의기존 SMS/LMS 의요율을 RCS 에서도적용하기위해 LMS 를구별한다. 장문 / 단문구분기준은기존 SMS/LMS 의기준을따른다. ( 영문만있을시 160 자, 한글포함되면 70 자 ) 이를위해 CPIM 헤더에국내규격으로아래정의된네임스페이스와헤더를추가하여표시한다. NS: Korea-RCShttp:// < 표 7-1> 대화방을위한 CPIM 헤더 CPIM Header Status Content 비고 Korea- Optional short: SMS 과금텍스트 type TTA 전용 RCS.TextType ( 텍스트 long: LMS(MMS) 과금텍스트 type 21

29 발신시 Mandatory) [ 발신동작 ] 발신단말은 text 전송시해당헤더에텍 스트 type 을넣어발신 발신 IM 서버는수신된메시지 CPIM 의 DateTime 을네트워크시간으로보정하여착신 IM 서버로전송한다. Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B 1. INVITE (message-id=1, msg1) 2. INVITE (message-id=1, msg1) 3. INVITE (message-id=1, msg1) 4. INVITE (message-id=1, msg1) 5. INVITE (message-id=1, msg1) 6. INVITE (message-id=1, msg1) 7. INVITE (message-id=1, msg1) Ringing Ringing Ringing Ringing Ringing Ringing Ringing 22

30 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B 15. MESSAGE (message-id=1, delivered) 16. MESSAGE (message-id=1, delivered) 17. MESSAGE (message-id=1, delivered) 18. MESSAGE (message-id=1, delivered) 19. MESSAGE (message-id=1, delivered) 20. MESSAGE (message-id=1, delivered) 21. MESSAGE (message-id=1, delivered) 22. MESSAGE 200 OK 23. MESSAGE 200 OK 24. MESSAGE 200 OK 25. MESSAGE 200 OK 26. MESSAGE 200 OK 27. MESSAGE 200 OK 28. MESSAGE 200 OK 31. ACK OK OK User opens chat window OK 32. ACK OK OK 37. ACK 36. ACK 38. ACK OK 41. ACK OK 42. ACK MSRP Session establishment 43. MSRP SEND (message-id=1, displayed) 44. MSRP SEND (message-id=1, displayed) 45. MSRP SEND (message-id=1, displayed) 46. MSRP 200 OK 47. MSRP 200 OK 48. MSRP 200 OK ( 그림 7-1) (1-to-1 Chat) 대화방개설 23

31 a) INVITE (User A ->IMS Core A) INVITE tel:user_b SIP/2.0 Via: SIP/2.0/UDP user_a.operatora.net;branch=z9hg4bknashds8 To: <tel:user_b> From: <sip:user_a@operatora.net>;tag= Call-ID: a84b4c76e66710-user_a.operatora.net Route: <sip:pcscf.operatora.net:7531;lr>,<sip:scscf.operatora.net;lr> Contact: <sip:user_a@operatora.net>;+g.oma.sip-im P-Preferred-Identity: "user_a" <sip:user_a@operatora.net> Max-Forwards: 70 Cseq: 3141 INVITE Accept-Contact: *;+g.oma.sip-im Require: timer Session-Expires: 180;refresher=uac Supported: timer Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Subject: Initial Message Contribution-ID: dfb4e64f-2c98-46a1-8e14-98eb5736a268 User-Agent:.. Content-Type: multipart/mixed;boundary=++ Content-Length: Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message 7654 TCP/TLS/MSRP * a=setup: active a=accept-types: message/cpim application/im-iscomposing+xml a=accept-wrapped-types: * a=path:msrps:// :7654/iau39soe2843z;tcp

32 Content-Type: Message/CPIM;charset=UTF-8 Content-Length:.. From: To: DateTime: T15:09:12.000Z NS: imdn <urn:ietf:params:imdn> NS: Korea-RCS < Korea-RCS.TextType: short imdn.message-id: 1 imdn.disposition-notification: positive-delivery, display Content-Type: text/plain Content-Length:.. msg b) Ringing (IM PF A -> IMS Core A) SIP/ Ringing Via: SIP/2.0/UDP scscf.operatora.net;branch=z9hg4bk29b9dad,sip/2.0/udp pcscf.operatora.net;branch=z9hg4bk240f34.1,sip/2.0/udp user_a.operatora.net;branch=z9hg4bknashds8 To: <sip:user_a@operatorb.net>;tag= From: <sip:user_a@operatora.net>;tag= Call-ID: a84b4c76e66710-user_a.operatora.net Record-Route: <sip:scscf.operatora.net;lr>, <sip:pcscf.operatora.net;lr> Cseq: 3141 INVITE Content-Length: 0 c) MESSAGE (User B -> IMS Core B) MESSAGE sip:user_a@operatora.net SIP/2.0 Via: SIP/2.0/UDP user_b.operatorb.net;branch=z9hg4bk2akkakdi042a Max-Forwards: 69 P-Preferred-Identity: "user_b" <sip:user_b@operatorb.net> From: <sip:user_b@operatorb.net>;tag=1234 To: <sip:user_a@operatora.net> CSeq: 1 MESSAGE 25

33 Accept-Contact:*;+g.oma.sip-im;require;explicit Contribution-ID: dfb4e64f-2c98-46a1-8e14-98eb5736a268 P-Preferred-Service: +g.oma.sip-im User-Agent:.. Content-Type: Message/CPIM Content-Length:.. From: > To: user_a NS: imdn <urn:ietf:params:imdn> DateTime: T15:09:19Z imdn.message-id: 1 Content-Disposition: notification Content-Type: message/imdn+xml Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <imdn xmlns="urn:ietf:params:xml:ns:imdn"> <message-id>1</message-id> <datetime> t15:09:12z</datetime> <delivery-notification> <status> <delivered/> </status> </delivery-notification> </imdn> d) 200 OK (User B -> IMS Core B) SIP/ OK Via: SIP/2.0/UDP pcscf.operatorb.net;branch=z9hg4bkkzaz42kkdkaf, SIP/2.0/UDP scscf.operatorb.net;branch=z9hg4bkkz23923dd, SIP/2.0/UDP rcsimpf.operatorb.net;branch=z9hg4bkkzkkda23d Max-Forwards: 69 Record-Route: <sip:pcscf.operatorb.net;lr>, <sip:scscf.operatorb.net;lr>, <sip:rcsim-pf.operatorb.net;lr> P-Charging-Vector: From: To: Call-ID: 26

34 Cseq: Require: Supported: Session-Expires: 180;refresher=uas Contact: <sip:user_b.operatorb.net:1030;lr>+g.oma.sip-im Allow: User-Agent:.. Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message 8888 TCP/TLS/MSRP * a=accept-types: message/cpim application/im-iscomposing+xml a=accept-wrapped-types: * a=path:msrps:// :8888/9di4eae923wzd;tcp a=sendrecev a=setup:active 대화방종료 Inactivity Timeout 처리 IM 세션타이머시간은환경설정으로조정할수있다. BYE 메시지는 Reason 헤더 (Reason: SIP;cause=480;text="Bearer Temporary Unavailable") 를포함한다 27

35 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B MSRP Inactivity Timeout Chat Session establishment 1. BYE (Reason: SIP;cause=200;text="Call completed") 2. BYE (Reason: SIP;cause=200;text="Call completed") 3. BYE (Reason: SIP;cause=200;text="Call completed") OK OK OK 7. BYE (Reason: SIP;cause=200;text="Call completed") 8. BYE (Reason: SIP;cause=200;text="Call completed") OK OK 11. BYE (Reason: SIP;cause=200;text="Call completed") 12. BYE (Reason: SIP;cause=200;text="Call completed") OK OK ( 그림 7-2) (1-to-1 Chat) Inactivity Timer 에의한세션종료 대화입력상태전달 대화입력중상태표시는 CPIM 헤더를가지고전송하지않으며 delivery/displayed notification 이요구되지않아야한다. iscomposing 이전달될수없을때에도 Store 하지않는다. (Optional) 28

36 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B Chat Session establishment 메시지입력 1. MSRP SEND (iscomposing active) 2. MSRP SEND (iscomposing active) 3. MSRP SEND (iscomposing active) 4. MSRP 200 OK 5. MSRP 200 OK 6. MSRP 200 OK 메시지취소 7. MSRP SEND (iscomposing idle) 8. MSRP SEND (iscomposing idle) 9. MSRP SEND (iscomposing idle) 10. MSRP 200 OK 11. MSRP 200 OK 12. MSRP 200 OK ( 그림 7-3) (1-to-1 Chat) 대화중입력표시상태전달 a) MSRP SEND (User A ->IM PF A) MSRP 07f906d1 SEND To-Path: msrp:// :19200/36a5188a_0_2_nr;tcp From-Path: msrps:// :7654/iau39soe2843z;tcp Message-ID: 07fa06d1 Byte-Range: 1-138/138 Content-Type: application/im-iscomposing+xml <?xml version="1.0" encoding="utf-8"?> <iscomposing xmlns="urn:ietf:params:xml:ns:im-iscomposing" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd"> <state>active</state> <contenttype>text/plain</contenttype> <refresh>90</refresh> </iscomposing> f906d1$ b) MSRP 200 OK (IM PF A -> User A) MSRP 07f906d1 200 OK 29

37 To-Path: msrps:// :7654/iau39soe2843z;tcp From-Path: a=path:msrp:// :19200/36a5188a_0_2_nr;tcp Message-ID: 07fa06d f906d1$ c) MSRP SEND (User A ->IM PF A) MSRP 07f906d2 SEND To-Path: msrp:// :19200/36a5188a_0_2_nr;tcp From-Path: msrps:// :7654/iau39soe2843z;tcp Message-ID: 07fa06d2 Byte-Range: 1-138/138 Content-Type: application/im-iscomposing+xml <?xml version="1.0" encoding="utf-8"?> <iscomposing xmlns="urn:ietf:params:xml:ns:im-iscomposing" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd"> <state>idle</state> <contenttype>text/plain</contenttype> <refresh>90</refresh> </iscomposing> f906d2$ d) MSRP 200 OK (IM PF A -> User A) MSRP 07f906d2 200 OK To-Path: msrps:// :7654/iau39soe2843z;tcp From-Path: a=path:a=path:msrp:// :19200/36a5188a_0_2_nr;tcp Message-ID: 07fa06d f906d2$ 대화하기 발신자단말로부터전달되는 IMDN requesting displayed notification 을포함하는 메시지에대해서수신자단말은발신자단말에 IMDN displayed status 를나타내는 MSRP SEND request 를보내야한다. 발신자단말로부터의 multiple IM session 에대한 pending 처리는 [RCS2-OMA- SIMPLE-ENDORS] 규격을따른다. 30

38 발신 IM 서버는수신된메시지 CPIM 의 DateTime 을네트워크시간으로보정하여착신 IM 서버로전송한다. Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B Chat Session establishment 1. MSRP SEND (message-id=3,msg3) 2. MSRP SEND (message-id=3,msg3) 3. MSRP SEND (message-id=3,msg3) 4. MSRP 200 OK 5. MSRP 200 OK 6. MSRP 200 OK 9. MSRP SEND (message-id=3,'delivered') 8. MSRP SEND (message-id=3,'delivered') 7. MSRP SEND (message-id=3,'delivered') 10. MSRP 200 OK 11. MSRP 200 OK 12. MSRP 200 OK 13. MSRP SEND (message-id=3,'displayed') 14. MSRP SEND (message-id=3,'displayed') 15. MSRP SEND (message-id=3,'displayed') 16. MSRP 200 OK 17. MSRP 200 OK 18. MSRP 200 OK ( 그림 7-4) (1-to-1 Chat) 대화히기 a) MSRP SEND (User A ->IM PF A) MSRP 07f906d8 SEND To-Path: msrp:// :19200/36a5188a_0_2_nr;tcp From-Path: msrps:// :7654/iau39soe2843z;tcp Message-ID: 07fa06d8 Byte-Range: 1-138/138 Content-Type: Message/CPIM;charset=UTF-8 From: <sip:anonymous@anonymous.invalid> To: <sip:anonymous@anonymous.invalid> NS : imdn <urn:ietf:params :imdn> Imdn.Message-ID:1 DateTime: T22:19:55Z 31

39 imdn.disposition-notification: positive-delivery, display Content-Type: text/plain Content-Length:.. Hi f906d8$ b) MSRP 200 OK (IM PF A -> User A) MSRP 07f906d8 200 OK To-Path: msrps:// :7654/iau39soe2843z;tcp From-Path: a=path:a=path:msrp:// :19200/36a5188a_0_2_nr;tcp Message-ID: 07fa06d f906d8$ c) MSRP SEND (User B -> IM PF B) MSRP YuUoN7%Kn% SEND To-Path: msrp:// :19201/93n3423u_2_4_nr;tcp From-Path: msrps:// :8888/9di4eae923wzd;tcp Message-ID: 29K.aDydA8 Byte-Range: 1-138/138 Content-Type: Message/CPIM;charset=UTF-8 From: user_b<sip:user_b@operatora.net > To: user_a <sip:user_a@operatorb.net> NS: imdn <urn:ietf:params:imdn> imdn.message-id: 1 DateTime: T12:16:49Z Content-Type: message/imdn+xml Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <imdn xmlns="urn:ietf:params:xml:ns:imdn"> <message-id>1</message-id> <datetime> t12:16:49z</datetime> <recipient-uri>sip:user_b@operatorb.net</recipient-uri> <delivery-notification> 32

40 <status> <delivered/> </status> </delivery-notification> </imdn> d) MSRP 200 OK (IM PF B -> User B) MSRP YuUoN7%Kn% 200 OK To-Path: msrps:// :8888/9di4eae923wzd;tcp From-Path: msrp:// :19201/93n3423u_2_4_nr;tcp Message-ID: 29K.aDydA YuUoN7%Kn%$ e) MSRP SEND (User B -> IM PF B) MSRP YuUoN7%Kn% SEND To-Path: msrp:// :19201/93n3423u_2_4_nr;tcp From-Path: msrps:// :8888/9di4eae923wzd;tcp Message-ID: 07fa06d8 Byte-Range: 1-138/138 Content-Type: Message/CPIM From: user_b<sip:user_b@operatora.net > To: user_a <sip:user_a@operatorb.net> NS: imdn <urn:ietf:params:imdn> imdn.message-id: 1 DateTime: T12:16:49Z Content-Disposition: notification Content-Type: message/imdn+xml Content-Length: <?xml version="1.0" encoding="utf-8"?> <imdn xmlns="urn:ietf:params:xml:ns:imdn"> <message-id>1</message-id> <datetime> t22:19:55z</datetime> <display-notification> <status> <displayed/> </status> </display-notification> 33

41 </imdn> f) MSRP 200 OK (IM PF B -> User B) MSRP YuUoN7%Kn% 200 OK To-Path: msrps:// :8888/9di4eae923wzd;tcp From-Path: msrp:// :19201/93n3423u_2_4_nr;tcp Message-ID: 29K.aDydA YuUoN7%Kn%$ Delivery and Display Notifications 착신디바이스는채팅메시지를수신하게되면 delivery, display notification 메시지를 생성하여발신자에게전송해야한다. CPIM 의 imdn.disposition-notification 헤더에 positive-delivery, display 의사용이 가능하며 positive-delivery 는반드시포함해야한다. negative-delivery 는 1 대 1 채팅에서사용되지않는다. a) 대화방개설 Flow 참조 Store and forward 착신자오프라인 착신클라이언트가오프라인상태일때 Store and forward 동작이다. 34

42 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B 1. INVITE (message-id=1, msg1) User Offline 2. INVITE (message-id=1, msg1) 3. INVITE (message-id=1, msg1) 4. INVITE (message-id=1, msg1) 5. INVITE (message-id=1, msg1) Temporarily Unavailable 7. ACK MSG Stored msg OK OK OK 12. ACK 11. ACK 13. ACK OK 16. ACK OK 17. ACK MSRP Session establishment 18. MSRP SEND (message-id=2, msg2) 19. MSRP SEND (message-id=2, msg2) MSG Stored msg2 20. MSRP 200 OK 21. MSRP 200 OK 22. MSRP SEND (message-id=3, msg2) 23. MSRP SEND (message-id=3, msg2) MSG Stored msg3 24. MSRP 200 OK 25. MSRP 200 OK ( 그림 7-5) (1-to-1 Chat: Store and forward) 착신자오프라인 35

43 착신자온라인전환 ( 채팅세션존재 ) 착신클라이언트가오프라인상태이어서채팅메시지를 Store 하고채팅세션이존재할 때착신클라이언트가온라인상태로전환되어 forward 하는동작이다. Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B Chat Session were previously established MSG Stored: msg1, msg2, msg3 User B is back online Registration 1. INVITE (message-id=1, msg1) 2. INVITE (message-id=1, msg1) Ringing Ringing 5. MESSAGE (message-id=1, delivered) 6. MESSAGE (message-id=1, delivered) OK OK 9. MSRP SEND (message-id=1, delivered) 10. MSRP SEND (message-id=1, delivered) 11. MSRP 200 OK 12. MSRP 200 OK 13. INVITE (message-id=2, msg2) 14. INVITE (message-id=2, msg2) Ringing Ringing 17. MESSAGE (message-id=2, delivered) 18. MESSAGE (message-id=2, delivered) OK OK 21. MSRP SEND (message-id=2, delivered) 22. MSRP SEND (message-id=2, delivered) 23. MSRP 200 OK 24. MSRP 200 OK Busy Here (previous INVITE) Busy Here (previous INVITE) 27. ACK 28. ACK 36

44 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B User opens chat window OK 31. ACK OK 32. ACK MSRP Session establishment 33. MSRP SEND (message-id=1,displayed) 34. MSRP SEND (message-id=1,displayed) 35. MSRP SEND (message-id=1,displayed) 36. MSRP 200 OK 37. MSRP 200 OK 38. MSRP 200 OK 39. MSRP SEND (message-id=2,displayed) 40. MSRP SEND (message-id=2,displayed) 41. MSRP SEND (message-id=1,displayed) 42. MSRP 200 OK 43. MSRP 200 OK 44. MSRP 200 OK 45. MSRP SEND (message-id=3,msg3) 46. MSRP 200 OK 47. MSRP SEND (message-id=3,delivered) 48. MSRP SEND (message-id=3,delivered) 49. MSRP SEND (message-id=3,delivered) 50. MSRP 200 OK 51. MSRP 200 OK 52. MSRP 200 OK 53. MSRP SEND (message-id=3,displayed) 54. MSRP SEND (message-id=3,displayed) 55. MSRP SEND (message-id=3,displayed) 56. MSRP 200 OK 57. MSRP 200 OK 58. MSRP 200 OK ( 그림 7-6) (1-to-1 Chat: Store and forward) 착신자온라인전환 ( 채팅세션존재 ) 37

45 착신자온라인전환 ( 채팅세션해제 ) 착신클라이언트가오프라인상태이어서채팅메시지를 Store 하고채팅세션이종료된 후에착신클라이언트가온라인상태로전환되어 forward 하는동작이다. Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B Chat Session is released MSG Stored: msg1, msg2, msg3 User B is back online Registration 1. INVITE (message-id=1, msg1) 2. INVITE (message-id=1, msg1) Ringing Ringing 5. MESSAGE (message-id=1, delivered) 6. MESSAGE (message-id=1, delivered) OK OK 8. SIP INVITE (rcse-standfw@domain, a=sendonly) 9. SIP INVITE (rcse-standfw@domain, a=sendonly) 10. SIP INVITE (rcse-standfw@domain, a=sendonly) 11. INVITE (rcse-standfw@domain, a=sendonly) 12. INVITE (rcse-standfw@domain, a=sendonly) OK OK 15. ACK 16. ACK OK OK OK 20. ACK 21. ACK 22. ACK MSRP Session establishment (send only) 23. MSRP SEND (message-id=1, delivered) 24. MSRP SEND (message-id=1, delivered) 25. MSRP 200 OK 26. MSRP 200 OK 27. INVITE (message-id=2, msg1) 28. INVITE (message-id=2, msg1) 38

46 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B Ringing Ringing 31. MESSAGE (message-id=2, delivered) 32. MESSAGE (message-id=2, delivered) OK OK 35. MSRP SEND (message-id=2, delivered) 36. MSRP SEND (message-id=2, delivered) 37. MSRP 200 OK 38. MSRP 200 OK Busy Here (previous INVITE) Busy Here (previous INVITE) 41. ACK 42. ACK 49. MSRP SEND (message-id=1,displayed) 50. MSRP 200 OK 55. MSRP SEND (message-id=1,displayed) 56. MSRP 200 OK 63. MSRP SEND (message-id=3,delivered) 45. ACK OK 48. MSRP SEND (message-id=1,displayed) 51. MSRP 200 OK 46. ACK User opens chat window OK MSRP Session establishment 47. MSRP SEND (message-id=1,displayed) 52. MSRP 200 OK 54. MSRP SEND (message-id=2,displayed) 57. MSRP 200 OK 53. MSRP SEND (message-id=2,displayed) 58. MSRP 200 OK 59. MSRP SEND (message-id=3,msg3) 60. MSRP 200 OK 62. MSRP SEND (message-id=3,delivered) 61. MSRP SEND (message-id=3,delivered) 39

47 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B 64. MSRP 200 OK 65. MSRP 200 OK 66. MSRP 200 OK 67. MSRP SEND (message-id=3,displayed) 68. MSRP SEND (message-id=3,displayed) 69. MSRP SEND (message-id=3,displayed) 70. MSRP 200 OK 71. MSRP 200 OK 72. MSRP 200 OK Chat Session release ( 그림 7-1) (1-to-1 Chat: Store and forward) 착신자온라인전환 ( 채팅세션해제 ) 착신자온라인전환 ( 발신자오프라인 ) 착신클라이언트가오프라인상태이어서채팅메시지를 Store 하고채팅세션이종료된후에착신클라이언트가온라인상태로전환되어 forward 한다. 이후 Notification 메시지를발신으로전달하였으나발신클라이언트가오프라인상태이어서 Notification 메시지를 Store 하는동작이다. Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B User A offline MSG Stored: msg1, msg2, msg3 User B is back online Registration 1. INVITE (message-id=1, msg1) 2. INVITE (message-id=1, msg1) Ringing Ringing 5. MESSAGE (message-id=1, delivered) 6. MESSAGE (message-id=1, delivered) OK OK 40

48 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B 9. INVITE (rcse-standfw@domain, sendonly) 10. INVITE (rcse-standfw@domain, sendonly) 11. INVITE (rcse-standfw@domain, sendonly) 12. INVITE (rcse-standfw@domain, sendonly) Temporarily Unavailable 14. ACK OK OK OK 18. ACK 19. ACK 20. ACK MSRP Session establishment (send only) 21. MSRP SEND (message-id=1, delivered) Notification stored 22. MSRP 200 OK 23. INVITE (message-id=2, msg1) 24. INVITE (message-id=2, msg1) Ringing Ringing 27. MESSAGE (message-id=2, delivered) 28. MESSAGE (message-id=2, delivered) OK OK Busy Here (previous INVITE) Busy Here (previous INVITE) 33. ACK 34. ACK 35. MSRP SEND (message-id=2, delivered) Notification stored 36. MSRP 200 OK 39. ACK OK 40. ACK User opens chat window OK MSRP Session establishment 41

49 Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B 41. MSRP SEND (message-id=1, displayed) 41. MSRP SEND (message-id=1, displayed) Notification stored 42. MSRP 200 OK 43. MSRP 200 OK 44. MSRP SEND (message-id=2, displayed) 45. MSRP SEND (message-id=2, displayed) Notification stored 46. MSRP 200 OK 47. MSRP 200 OK 48. MSRP SEND (message-id=3, msg3) 49. MSRP 200 OK 50. MSRP SEND (message-id=3, delivered) 51. MSRP SEND (message-id=3, delivered) 52. MSRP SEND (message-id=3, delivered) Notification stored 53. MSRP 200 OK 54. MSRP 200 OK 55. MSRP 200 OK 56. MSRP SEND (message-id=3, displayed) 57. MSRP SEND (message-id=3, displayed) 58. MSRP SEND (message-id=3, displayed) 59. MSRP 200 OK 60. MSRP 200 OK 61. MSRP 200 OK ( 그림 7-82) (1-to-1 Chat: Store and forward) 착신자온라인전환 ( 발신자오프라인 ) 42

50 발신자온라인전환 발신자의디바이스가온라인상태가되면 delivered/displayed notification 전달을위한세션을생성한다. 이러한세션은 sendonly 로설정을하고 INVITE 요청메시지의 P- Asserted-Identity 헤더값을 으로설정을하여발신자의디바이스에서자동수락을할수있도록한다. Network A Network B User A IMS Core IM (PF) IM (PF) IMS Core User B User A is back online Notification stored Registration 1. INVITE (rcse-standfw@<domain, a=sendonly) 2. INVITE (rcse-standfw@<domain, a=sendonly) OK OK 5. ACK 6. ACK MSRP Session establishment 7. MSRP SEND (message-id=1, delivered) 8. MSRP 200 OK 9. MSRP SEND (message-id=2, delivered) 10. MSRP 200 OK 11. MSRP SEND (message-id=1, displayed) 12. MSRP 200 OK 13. MSRP SEND (message-id=2, displayed) 14. MSRP 200 OK 15. MSRP SEND (message-id=3, delivered) 16. MSRP 200 OK 17. MSRP SEND (message-id=3, displayed) 18. MSRP 200 OK Chat Session release ( 그림 7-93) (1-to-1 Chat: Store and forward) 발신자온라인전환 a) INVITE (IM PF A -> User A) INVITE sip:user_a@operatora.net SIP/2.0 Via: SIP/2.0/UDP rcsim-pf.operatora.net;branch=z9hg4bkkzkkda23d Max-Forwards: 54 Record-Route: <sip:rcsim-pf.operatora.net;lr> 43

51 P-Charging-Vector: P-Asserted-Identity: From: To: Call-ID: cb03a0s09a2sdfglkj Cseq: Require: Supported: Contact: <sip:rcsim-pf.operatora.net;lr>;expire=180;+g.oma.sip-im Accept-Contact:*;+g.oma.sip-im;require;explicit Allow: Contribution-ID: dfb4e64f-2c98-46a1-8e14-98eb5736a268 Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message TCP/MSRP * a=sendonly a=accept-types:message/cpim a=accept-wrapped-types: * a=path: a=path:msrp:// :19200/36a5188a_0_2_nr;tcp 착신자측에러처리 착신자또는 IMS Core 로부터 480/404 이외의에러응답을수신하면채팅메시지를 Store 하되발신자로 486 Busy Here 응답을전송함으로써세션수립은하지않는다. 404 의경우 Store 를하지않는다. 44

52 Network A Network B User A IMS-Core IM (PF) IM (PF) IMS-Core User B 1. INVITE (message-id=1, msg1) 2. INVITE (message-id=1, msg1) 3. SIP INVITE (message-id=1, msg1) 4. SIP INVITE (message-id=1, msg1) 5. SIP INVITE (message-id=1, msg1) 6. Temporary ERROR (except 480/404) 7. ACK MSG Store msg Busy Here Busy Here Cleint/network error or timeout Busy Here 12. ACK 11. ACK 13. ACK Busy Here Busy Here 16. ACK 17. ACK ( 그림 7-104) (1-to-1 Chat: Store and forward) 착신자측에러 < 표 7-2> Mapping of received Error Responses by the Messaging Server Response received on terminating leg Response sent on originating leg Store the message 480 Temporarily unavailable 200 OK Y 408 Request Timeout 486 Busy Here Y 487 Request Terminated 486 Busy Here Y 500 Server Internal Error 486 Busy Here Y 503 Service Unavailable 486 Busy Here Y 504 Server Timeout 486 Busy Here Y 600 Busy Everywhere 486 Busy Here Y 603 Decline 486 Busy Here Y Any other response (including 404 Not Found and 200 OK) Received response (that is no mapping is done) N 45

53 Mapping of received Error Responses by the Messaging Server 테이블의경우 GSMA RCS5.3 Table 45 부분을발췌하였다. 7.2 Group Chat Group Chat 유지시간과 PF 의메시지보관주기는동일하게하며이는사업자정책에따라변경이가능하다. 다음은 RCS User 간의 Group Chat 메시지교환을위한절차를기술한다 대화방개설 Initial INVITE 의경우 MSRP 세션정보와참여자 List 만포함하며 INVITE 에첫번째메시지와 Subject 헤더는포함하지않는다. IM (CF) 는착신 IM (PF) 응답전수신되는채팅메시지및참여자이벤트를착신리스트별로버퍼링한다. IM (CF) 는착신 IM (PF) 로부터 200 OK 수신시버퍼링된메시지및참여자이벤트를전송한다. 착신 IM (PF) 는 IM (CF) 로부터수신된메시지및이벤트를착신단말로전송하거나 Store & forward 한다. Group Chat subject 는설정하지않는다. INVITE 메시지의 Expire 헤더값은 1800 초로한다. 그러므로단말은 Session Refresh Timer 시간은 1800 초로설정한다. RCS user 로기확인된 contacts 들에대해서는 Group Chat capability query 하지않는다. Conference ID 생성규칙 < 통신사 Prefix [s,k,u]>cf[server 예 ) scf_im_1_123@sktims.net kcf_im_2_4567@ims.mnc008.mcc450.3gppnetwork.org ucf_im_3_8901@lte-lguplus.co.kr 46

54 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C 1. INVITE 2. INVITE 3. INVITE 4. INVITE (User B) 5. INVITE (User B) OK OK 16. ACK 17. ACK 6. INVITE (User B) 7. INVITE (User B) OK 11. ACK OK 18. ACK 8. INVITE (User B) OK 12. ACK MSRP Session establishment Conference Event Subscription OK 21. ACK OK 22. ACK MSRP Session establishment Conference Event Subscription 23. INVITE (User C) 24. INVITE (User C) OK OK 35. ACK 36. ACK 25. INVITE (User C) 26. INVITE (User C) 27. INVITE (User C) OK OK 30. ACK 31. ACK OK 37. ACK MSRP Session establishment Conference Event Subscription ( 그림 7-115) (Group Chat) 대화방개설 a) INVITE (User A -> IMS Core A) INVITE sip:conference-factory@operatora.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: <sip:pcscf.operatora.net;lr>,<sip:scscf.operatora.net;lr> P-Preferred-Identity: "user_a" <sip:user_a@operatora.net> 47

55 From: To: Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent: Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message 7654 TCP/TLS/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrps:// :7654/iau39soe2843z;tcp --++ Content-Type: application/resource-lists+xml Content-Disposition: recipient-list Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" 48

56 xmlns:xsi=" <list> <entry uri="tel:user_b"/> <entry uri="tel:user_c"/> </list> </resource-lists> b) INVITE (IMS Core A -> IM PF A) c) INVITE (IM PF A -> IM CF A) d) INVITE (IM CF A -> IMS Core A) INVITE tel:user_b SIP/2.0 Via: SIP/2.0/UDP im.operatora.net:5060;branch=z9hg4bk28bvnasj Max-Forwards: 70 Route:.. P-Asserted-Identity: <sip:user_a@operatora.net> From: <sip:conference-factory@operatora.net>;tag=93bajw To: <tel:user_b> Call-ID: bvkaoi3ibi2eijdjd Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uas Supported: timer Referred-By: <sip:user_a@operatora.net> Contact: <sip:conf-id@operatora.net>;+g.oma.sip-im;isfocus Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent: Content-Type: application/sdp Content-Length:.. 49

57 v=0 o= IN IP s=c=in IP t=0 0 m=message TCP/MSRP * a=setup:actpass a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrp:// :19240/73f0367h_1_3_nr;tcp --++ Content-Type: application/resource-lists+xml Content-Disposition: recipient-list Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" <list> <entry uri="sip:user_a@operatora.net"/> <entry uri="sip:user_c@operatorb.net"/> </list> </resource-lists> e) INVITE (IMS Core A -> IMS Core B) f) INVITE (IMS Core B -> IM PF B) g) INVITE (IM PF B -> IMS Core B) INVITE sip:user_b@operatorb.net SIP/2.0 Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bkbiq892hjg Max-Forwards: 70 Route:.. P-Asserted-Identity: <sip:user_a@operatora.net> From: <sip:conference-factory@operatora.net>;tag=82nbguyh2 To: <sip:user_b@operatorb.net> Call-ID: b82n128dja812 50

58 Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uas Supported: timer Referred-By: <sip:user_a@operatora.net> Contact: <sip:conf-id%40operatora.net_pf-id@operatorb.net>;+g.oma.sip-im;isfocus Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent: Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message TCP/MSRP * a=setup:actpass a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrp:// :19201/93n3423u_2_4_nr;tcp --++ Content-Type: application/resource-lists+xml Content-Disposition: recipient-list Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" <list> 51

59 <entry <entry </list> </resource-lists> h) INVITE (IMS Core B -> User B) i) 200 OK (User B -> IMS Core B) j) 200 OK (IMS Core B -> IM PF B) SIP/ OK Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bkbiq892hjg Max-Forwards: 67 Record-Route: <sip:pcscf.operatorb.net;lr>, <sip:scscf.operatorb.net;lr> P-Asserted-Identity: <sip:user_b@operatorb.net> From: <sip:conference-factory@operatora.net>;tag=82nbguyh2 To: <sip:user_b@operatorb.net>;tag=v82821 Call-ID: b82n128dja812 Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Session-Expires: 300;refresher=uas Supported: timer Contact: <sip:user_b@ :5060>;+g.oma.sip-im;isfocus Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY User-Agent:.. Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message 8888 TCP/TLS/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * 52

60 a=path:msrps:// :8888/9di4eae923wzd;tcp k) ACK (IM PF B -> IMS Core B) ACK sip:user_b@ :5060 SIP/2.0 To: <sip:user_b@operatorb.net>;tag=v82821 Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bk37gvbhwy CSeq: 1 ACK From: <sip:conference-factory@operatora.net>;tag=82nbguyh2 Route: <sip:scscf.operatorb.net;lr>, <sip:pcscf.operatorb.net;lr> Call-ID: b82n128dja812 Max-Forwards: 70 Content-Length: 0 l) ACK (IMS Core B -> User B) m) 200 OK (IM PF B -> IMS Core B) n) 200 OK (IMS Core B -> IMS Core A) o) 200 OK (IMS Core A -> IM CF A) SIP/ OK Via: SIP/2.0/UDP im.operatora.net:5060;branch=z9hg4bk28bvnasj Max-Forwards: 67 Record-Route:.. P-Asserted-Identity: <sip:user_b@operatorb.net> From: <sip:conference-factory@operatora.net>;tag=93bajw To: <sip:user_b@operatorb.net>;tag=182b1234 Call-ID: bvkaoi3ibi2eijdjd Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Session-Expires: 300;refresher=uas Supported: timer Contact: <sip:pf-id@operatorb.net>;+g.oma.sip-im;isfocus Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY User-Agent:.. Content-Type: application/sdp Content-Length:.. v=0 o= IN IP

61 s=c=in IP t=0 0 m=message TCP/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrp:// :19201/93n3423u_2_4_nr;tcp p) ACK (IM CF A -> IMS Core A) ACK sip:pf-id@operatorb.net SIP/2.0 To: <sip:user_b@operatorb.net>;tag=182b1234 Via: SIP/2.0/UDP im.operatora.net:5060;branch=z9hg4bkb82jw9sawwr4 CSeq: 1 ACK From: <sip:conference-factory@operatora.net>;tag=93bajw Route:.. Call-ID: bvkaoi3ibi2eijdjd Max-Forwards: 70 Content-Length: 0 q) ACK (IMS Core A -> IMS Core B) r) ACK (IMS Core B -> IM PF B) s) 200 OK (IM CF A -> IMS Core A) t) 200 OK (IMS Core A -> User A) SIP/ OK Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 67 Record-Route: <sip:orig@scscf.operatora.net;lr>, <sip:pcscf.operatora.net;lr> From: <sip:user_a@operatora.net>;tag= To: <sip:conference-factory@operatora.net>;tag=23b8ajsai Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Session-Expires: 300;refresher=uac P-Asserted-Identity: sip:conference-factory@operatora.net Supported: timer Contact: <sip:pf-id@operatora.net>;+g.oma.sip-im;isfocus Accept-Contact: *;+g.oma.sip-im;require;explicit 54

62 Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY User-Agent:.. Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message TCP/MSRP * a=setup:passive a=accept-types:message/cpim a=accept-wrapped-types: * a=path:a=path:msrp:// :19200/36a5188a_0_2_nr;tcp u) ACK (User A -> IMS Core A) ACK sip:pf-id@operatora.net SIP/2.0 To: <sip:conference-factory@operatora.net>;tag=23b8ajsai Via: SIP/2.0/UDP :1357;branch=z9hG4bKvhahe8232e CSeq: 1 ACK From: <sip:user_a@operatora.net>;tag= Route: <sip:pcscf.operatora.net;lr>, <sip:orig@scscf.operatora.net;lr> Call-ID: cb03a0s09a2sdfglkj Max-Forwards: 70 Content-Length: 0 v) ACK (IMS Core A -> IM CF A) w) INVITE (IM CF A -> IMS Core A) x) INVITE (IMS Core A -> IMS Core B) y) INVITE (IMS Core B -> IM PF B) z) INVITE (IM PF B -> IMS Core B) aa) INVITE (IMS Core B -> User B) bb) 200 OK (User B -> IMS Core B) cc) 200 OK (IMS Core B -> IM PF B) dd) ACK (IM PF B -> IMS Core B) 55

63 ee) ACK (IMS Core B -> User B) ff) 200 OK (IM PF B -> IMS Core B) gg) 200 OK (IMS Core B -> IMS Core A) hh) 200 OK (IMS Core A -> IM CF A) ii) ACK (IM CF A -> IMS Core A) jj) ACK (IMS Core A -> IMS Core B) kk) ACK (IMS Core B -> IM PF B) 대화방이벤트관리 Conference Event Package IM (CF) 는착신 IM (PF) 로부터 Subscription 을수신하기전발생하는참여자이벤트를 버퍼링한다. 착신 IM (PF) 로부터 Subscription 을수신하면버퍼링중이던참여자 이벤트를전달한다. IM (PF) 는 B2BUA 로동작하여 IM (CF) 로 Subscription 을요청하고수신되는참여자 이벤트를저장한다. 착신단말로부터 Subscription 을수신하면저장중이던참여자 이벤트를전달한다. IM (CF) 는발생되는참여자이벤트에따라 Notification 의 xml 메시지에 joining-info 또는 disconnection-info 를포함한다. when 엘리먼트의값은참여자이벤트가발생한시간이며 UTC (Universal Time Coordinated) 기준으로설정한다. 56

64 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment 1. SUBSCRIBE (conference) OK 3. NOTIFY (conference) OK 5. SUBSCRIBE (conference) 6. SUBSCRIBE (conference) OK OK 9. NOTIFY (conference) 10. NOTIFY (conference) OK OK 14. SUBSCRIBE (conference) 15. SUBSCRIBE (conference) OK OK 19. NOTIFY (conference) 20. NOTIFY (conference) 13. SUBSCRIBE (conference) OK 21. NOTIFY (conference) 참여자정보저장 OK OK OK MSRP Session Establishment 25. SUBSCRIBE (conference) 26. SUBSCRIBE (conference) OK OK 참여자정보전달 29. NOTIFY (conference) OK 30. NOTIFY (conference) OK MSRP Session Establishment Conference Event Subscription ( 그림 7-126) (Group Chat) Conference Event Package a) SUBSCRIBE (IM PF A -> IM CF A) PF는 B2BUA로동작하여 CF로 Conference Event Subscription을한다. SUBSCRIBE sip:conf-id@operatora.net SIP/2.0 Via: SIP/2.0/UDP operatora.net:5060;branch=z9hg4bkwc721k3fiv From: <sip:user_a@operatora.net>;tag=8v823 To: <sip:conf-id@operatora.net> Event: conference Route:.. 57

65 Accept: application/conference-info+xml Call-ID: Cseq: 1 SUBSCRIBE P-Asserted-Identity: <sip:user_a@operatora.net> Contact: <sip:pf-id@operatora.net:5060>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Expires: 3600 Max-Forwards: 70 Content-Length: 0 b) 200 OK (IM CF A -> IM PF A) SIP/ OK Via: SIP/2.0/UDP operatora.net:5060;branch=z9hg4bkwc721k3fiv To: <sip:conf-id@operatora.net>;tag=vjsu13vd Cseq: 1 SUBSCRIBE From: <sip:user_a@operatora.net>;tag=8v823 Event: conference Record-Route:.. Accept: application/conference-info+xml Call-ID: wc721k3fiv@operatora.net Contact: sip:conf-id@operatora.net Expires: 3600 c) NOTIFY (IM CF A -> IM PF A) NOTIFY sip:pf-id@operatora.net:5060 SIP/2.0 To: <sip:user_a@operatora.net>;tag=8v823 Cseq: 1 NOTIFY From: <sip:conf-id@operatora.net>;tag=vjsu13vd Event: conference Call-ID: wc721k3fiv@operatora.net Contact: sip:conf-id@operatora.net Content-Type: application/conference-info+xml Subscription-State: active;expires=3600 Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <conference-info xmlns="urn:ietf:params:xml:ns:conference-info" entity="conference-uri" state="full" version="1"> <users> 58

66 <user entity="tel:user_a" state="full"> <endpoint entity="tel:user_a"> <status>connected</status> <joining-method>dialed-in</joining-method> <joining-info> <when> t04:00:00z</when> </joining-info> </endpoint> </user> <user entity="tel:user_b" state="full"> <endpoint entity="tel:user_b"> <status>connected</status> <joining-method>dialed-out</joining-method> <joining-info> <when> t04:00:10z</when> </joining-info> </endpoint> </user> <user entity="tel:user_c" state="full"> <endpoint entity="tel:user_c"> <status>pending</status> </endpoint> </user> </users> </conference-info> d) 200 OK (IM PF A -> IM CF A) e) SUBSCRIBE (User A -> IMS Core A) SUBSCRIBE sip:conf-id@operatora.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bK57c1f18f_ From: <sip:user_a@operatora.net>;tag=13145aade To: <sip:conf-id@operatora.net> Event: conference Route:.. Accept: application/conference-info+xml Call-ID: 6a7b1c2f@ Cseq: 1 SUBSCRIBE P-Preferred-Identity: <sip:user_a@operatora.net> 59

67 Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Expires: 3600 Max-Forwards: 70 Content-Length: 0 f) SUBSCRIBE (IMS Core A -> IM PF A) g) 200 OK (IM PF A -> IMS Core A) h) 200 OK (IMS Core A -> User A) SIP/ OK Via: SIP/2.0/UDP :1357;branch=z9hG4bK57c1f18f_ To: <sip:conf-id@operatora.net>;tag=38b823 Cseq: 1 SUBSCRIBE From: <sip:user_a@operatora.net>;tag=13145aade Event: conference Record-Route:.. Accept: application/conference-info+xml Call-ID: 6a7b1c2f@ Contact: sip:pf-id@operatora.net Expires: 3600 i) NOTIFY (IM PF A -> IMS Core A) j) NOTIFY (IMS Core A -> User A) k) 200 OK (User A -> IMS Core A) l) 200 OK (IMS Core A -> IM PF A) m) SUBSCRIBE (IM PF B -> IMS Core B) n) SUBSCRIBE (IMS Core B -> IMS Core A) o) SUBSCRIBE (IMS Core A -> IM CF A) p) 200 OK (IM CF A -> IMS Core A) q) 200 OK (IMS Core A -> IMS Core B) r) 200 OK (IMS Core B -> IM PF B) s) NOTIFY (IM CF A -> IMS Core A) t) NOTIFY (IMS Core A -> IMS Core B) u) NOTIFY (IMS Core B -> IM PF B) 60

68 v) 200 OK (IM PF B -> IMS Core B) w) 200 OK (IMS Core B -> IMS Core A) x) 200 OK (IMS Core A -> IM CF A) y) SUBSCRIBE (User B -> IMS Core B) z) SUBSCRIBE (IMS Core B -> IM PF B) aa) 200 OK (IM PF B -> IMS Core B) bb) 200 OK (IMS Core B > User B) cc) NOTIFY (IM PF B -> IMS Core B) dd) NOTIFY (IMS Core B > User B) ee) 200 OK (User B -> IMS Core B) ff) 200 OK (IMS Core B -> IM PF B) 대화참여알림 단말은 Notification 메시지의 xml 에서 joining-info 의 when 을참조하여해당참여자의 입장이발생한시간을확인한다. 또한대화참여알림은시간 (GMT 시간 ) 까지단말에서 필수로구현하여지원해야한다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C User D MSRP Session Establishment Conference Event Subscription Adding Participants to a Group Chat 대화방참여 MSRP Session Establishment Conference Event Subscription Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C User D 1. NOTIFY (conference) 2. NOTIFY (conference) 3. NOTIFY (conference) OK OK OK Conference Event Notification Conference Event Notification Conference Event Notification 61

69 ( 그림 7-137) (Group Chat) 대화참여알림 a) NOTIFY (IM CF A -> IMS Core A) NOTIFY sip:pf-id@operatora.net:5060 SIP/2.0 To: <sip:user_a@operatora.net>;tag=8v823 Cseq: 2 NOTIFY From: <sip:conf-id@operatora.net>;tag=vjsu13vd Event: conference Call-ID: wc721k3fiv@operatora.net Contact: sip:conf-id@operatora.net Content-Type: application/conference-info+xml Subscription-State: active;expires=3560 Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <conference-info xmlns="urn:ietf:params:xml:ns:conference-info" entity="conference-uri" state="partial" version="2"> <users> <user entity="tel:user_d" state="partial"> <endpoint entity="tel:user_d"> <status>connected</status> <joining-method>dialed-out</joining-method> <joining-info> <when> t04:00:50z</when> </joining-info> </endpoint> </user> </users> </conference-info> b) NOTIFY (IM PF A -> IMS Core A) c) NOTIFY (IMS Core A -> User A) d) 200 OK (User A -> IMS Core) e) 200 OK (IMS Core -> IM PF A) f) 200 OK (IM PF A -> IM CF A) 대화종료알림 62

70 단말은 Notification 메시지의 xml 에서 disconnection-info 의 when 을참조하여해당 참여자의퇴장이발생한시간을확인한다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment Conference Event Subscription 1. NOTIFY (conference) 2. NOTIFY (conference) 3. NOTIFY (conference) OK OK OK Leaving a Group Chat Conference Event Notification 대화방나가기 Conference Event Notification ( 그림 7-148) (Group Chat) 대화종료알림 a) NOTIFY (IM CF A -> IMS Core A) NOTIFY sip:pf-id@operatora.net:5060 SIP/2.0 To: <sip:user_a@operatora.net>;tag=8v823 Cseq: 2 NOTIFY From: <sip:conf-id@operatora.net>;tag=vjsu13vd Event: conference Call-ID: wc721k3fiv@operatora.net Contact: sip:conf-id@operatora.net Content-Type: application/conference-info+xml Subscription-State: active;expires=3560 Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <conference-info xmlns="urn:ietf:params:xml:ns:conference-info" entity="conference-uri" state="partial" version="3"> <users> <user entity="tel:user_c" state="partial"> <endpoint entity="tel:user_c"> <status>disconnected</status> <disconnection-method>departed</disconnection-method> 63

71 <disconnection-info> <when> t04:03:25z</when> </disconnection-info> </endpoint> </user> </users> </conference-info> b) NOTIFY (IM PF A -> IMS Core A) c) NOTIFY (IMS Core A -> User A) d) 200 OK (User A -> IMS Core) e) 200 OK (IMS Core -> IM PF A) f) 200 OK (IM PF A -> IM CF A) 대화방참여자추가 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C User D MSRP Session Establishment User D 를대화방에초대 1. REFER Accepted 2. REFER 3. REFER Accepted Accepted 7. INVITE (User D) 8. INVITE (User D) OK OK 19. ACK 20. ACK 9. INVITE (User D) 10. INVITE (User D) 11. INVITE (User D) OK OK 14. ACK 15. ACK OK 21. ACK MSRP Session establishment Conference Event Subscription 22. Conference Event Notification ( 그림 7-15) (Group Chat) 대화방참여자추가 a) REFER (User A -> IMS Core A) REFER sip:conf-id@operatora.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bK8237g9vnsaj To: <sip:conf-id@operatora.net>;tag=v82821 From: <sip:user_a@operatora.net>;tag=82nbguyh2 64

72 Call-ID: cb03a0s09a2sdfglkj CSeq: 2 REFER Contact: <sip: :1357>;+g.oma.sip-im Refer-To: <cid:cn35t8jf02@operatora.net> Refer-Sub: false Require: multiple-refer, norefersub Max-Forwards: 70 Content-Type: application/resource-lists+xml Content-Disposition: recipient-list Content-Length:.. Content-ID: <cn35t8jf02@operatora.net> <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" <list> <entry uri="tel:user_d" /> </list> </resource-lists> b) REFER (IMS Core A -> IM PF A) c) REFER (IM PF A -> IM CF A) d) 202 Accepted (IM CF A -> IM PF A) e) 202 Accepted (IM PF A -> IMS Core A) f) 202 Accepted (IMS Core A -> User A) SIP/ Accepted Via: SIP/2.0/UDP :1357;branch=z9hG4bK8237g9vnsaj To: <sip:conf-id@operatora.net>;tag=v82821 From: <sip:user_a@operatora.net>;tag=82nbguyh2 Call-ID: cb03a0s09a2sdfglkj CSeq: 2 REFER Refer-Sub: false Contact: sip:conf-id@operatora.net Content-Length: 0 g) INVITE (IMS CF A -> IMS Core A) h) INVITE (IMS Core A -> IMS Core B) 65

73 i) INVITE (IMS Core B -> IM PF B) j) INVITE (IM PF B -> IMS Core B) k) INVITE (IMS Core B -> User B) l) 200 OK (User B -> IMS Core B) m) 200 OK (IMS Core B -> IM PF B) n) ACK (IM PF B -> IMS Core B) o) ACK (IMS Core B -> User B) p) 200 OK (IM PF B -> IMS Core B) q) 200 OK (IMS Core B -> IMS Core A) r) 200 OK (IMS Core A -> IM CF A) s) ACK (IM CF A -> IMS Core A) t) ACK (IMS Core A -> IMS Core B) u) ACK (IMS Core B -> IM PF B) 대화방종료 모든참여자퇴장 모든참여자가명시적으로퇴장하여, 1 명만남은경우에대화방은종료된다. IM 서버 (CF) 는보관중이던그룹대화세션정보를삭제한다. IM 서버 (CF) 는 IM (PF) 로 BYE 메시지를전송하여그룹대화세션을종료시킨다. BYE 메시지는 Reason 헤더 (SIP;cause=410;text= Gone ) 를포함한다. 해당 Reason 헤더를수신한단말은해당대화방으로 rejoin 을전송하지않아야한다. 66

74 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment 1. BYE (Reason: SIP;cause=200;text="Call completed") 2. BYE (Reason: SIP;cause=200;text="Call completed") OK OK 5. BYE (Reason: SIP;cause=200;text="Call completed") OK User C 퇴장한상태 Conference Event Notification 7. BYE (Reason: SIP;cause=410;text="Gone") 8. BYE (Reason: SIP;cause=410;text="Gone") OK OK 9. BYE (Reason: SIP;cause=410;text="Gone") OK 13. BYE (Reason: SIP;cause=410;text="Gone") 14. BYE (Reason: SIP;cause=410;text="Gone") OK OK 17. Conference Event Notification ( 그림 7-169) (Group Chat) 모든참여자퇴장 a) BYE (User A -> IMS Core A) BYE sip:pf-id@operatora.net SIP/2.0 To: <sip:conference-factory@operatora.net>;tag=23b8ajsai Via: SIP/2.0/UDP :1357;branch=z9hG4bKadfsi39239 CSeq: 3 BYE From: <sip:user_a@operatora.net>;tag= Route: <sip:pcscf.operatora.net;lr>, <sip:scscf.operatora.net;lr> Call-ID: cb03a0s09a2sdfglkj Reason: SIP;cause=410;text="Gone" Contact: <sip: :1357>;+g.oma.sip-im Max-Forwards: 70 Content-Length: 0 b) BYE (IMS Core A -> IM PF A) c) 200 OK (IM PF A -> IMS Core A) d) 200 OK (IMS Core A -> User A) e) BYE (IM PF A -> IM CF A) f) 200 OK (IM CF A -> IM PF A) g) BYE (IM CF A -> IMS Core A) h) BYE (IMS Core A -> IMS Core B) 67

75 i) BYE (IMS Core B -> IM PF B) BYE sip:pf-id@operatorb.net SIP/2.0 To: <sip:user_b@operatorb.net>;tag=182b1234 Via: SIP/2.0/UDP im.operatora.net:5060;branch=z9hg4bk CSeq: 3 BYE From: <sip:conference-factory@operatora.net>;tag=93bajw Route:.. Call-ID: bvkaoi3ibi2eijdjd Reason: SIP;cause=410;text="Gone" Contact: <sip:conf-id@operatora.net>;+g.oma.sip-im;isfocus Max-Forwards: 70 Content-Length: 0 j) 200 OK (IM PF B -> IMS Core B) k) 200 OK (IMS Core B -> IMS Core A) l) 200 OK (IMS Core A -> IM CF A) m) BYE (IM PF B -> IMS Core B) n) BYE (IMS Core B -> User B) o) 200 OK (User B -> IMS Core B) BYE sip:user_b@ :5060 SIP/2.0 To: <sip:user_b@operatorb.net>;tag=v82821 Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bkbvhew82 CSeq: 3 BYE From: <sip:conference-factory@operatora.net>;tag=82nbguyh2 Route: <sip:scscf.operatorb.net;lr>, <sip:pcscf.operatorb.net;lr> Call-ID: b82n128dja812 Reason: SIP;cause=410;text="Gone" Contact: <sip:conf-id%40operatora.net_pf-id@operatorb.net>;+g.oma.sip-im;isfocus Max-Forwards: 70 Content-Length: 0 p) 200 OK (IMS Core B -> IM PF B) q) NOTIFY (IM CF A -> IMS Core A) Inactivity Timeout 처리 68

76 IM 서버 (CF) 는 MSRP Inactivity 타이머만료시 RCS 5.3 의 Long Lived Group Chat 기능을위하여 Focus Session ID, Contribution-ID 및참여자리스트를보관한다. 보관주기는마지막대화시점을기준으로최소 1 개월을기본으로하여, 통신사업자의운영정책으로관리한다. 보관주기는설정으로관리할수있어야한다. IM 서버 (CF) 는 IM (PF) 로 BYE 메시지를전송하여그룹대화세션을종료시킨다. BYE 메시지는 Reason 헤더 (SIP;cause=480;text= Bearer Temporary Unavailable ) 를포함한다. Inactivity 타이머값은 IM 서버 (CF) 기준으로 5 분을기본으로설정하며, 변경이 가능하다. 발 / 착신 IM 서버 (PF) 는 IM 서버 (CF) 간 Connection Loss 등의오류상황을 대비하기위하여 Inactivity 타이머의구동이가능하나 IM 서버 (CF) 의 Inactivity 타이머 시간보다길어야한다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment Inactivity Timeout 1. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") OK 3. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") 4. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") OK OK Conference Event Notification 그룹대화세션정보저장 7. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") 8. BYE OK OK 9. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") OK 13. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") 14. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") OK OK Conference Event Notification 17. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") 18. BYE 19. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") OK OK OK 23. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") 24. BYE (SIP;cause=480;text="Bearer Temporary Unavailable") OK OK 27. Conference Event Notification ( 그림 7-17) (Group Chat) Inactivity Timeout 처리 a) BYE (IM CF A -> IM PF A) b) 200 OK (IM PF A -> IM CF A) 69

77 c) BYE (IM PF A -> IMS Core A) BYE sip: :1357 SIP/2.0 Via: SIP/2.0/UDP im.operatora.net:5060;branch=z9hg4bkb992b9ua9 CSeq: 3 ACK To: <sip:user_a@operatora.net>;tag= From: <sip:conference-factory@operatora.net>;tag=23b8ajsai Route: <sip:orig@scscf.operatora.net;lr>, <sip:pcscf.operatora.net;lr> Call-ID: cb03a0s09a2sdfglkj Reason: SIP;cause=480;text="Bearer Temporary unavailable" Contact: sip:pf-id@operatora.net;+g.oma.sip-im;isfocus Max-Forwards: 70 Content-Length: 0 d) BYE (IMS Core A -> User A) e) 200 OK (User A -> IMS Core A) f) 200 OK (IMS Core A -> IM PF A) g) BYE (IM CF A -> IMS Core A) BYE sip:pf-id@operatorb.net SIP/2.0 To: <sip:user_b@operatorb.net>;tag=182b1234 Via: SIP/2.0/UDP im.operatora.net:5060;branch=z9hg4bk823hg CSeq: 3 BYE From: <sip:conference-factory@operatora.net>;tag=93bajw Route:.. Call-ID: bvkaoi3ibi2eijdjd Reason: SIP;cause=480;text="Bearer Temporary unavailable" Contact: <sip:conf-id@operatora.net>;+g.oma.sip-im;isfocus Max-Forwards: 70 Content-Length: 0 h) BYE (IMS Core A -> IMS Core B) i) BYE (IMS Core B -> IM PF B) j) 200 OK (IM PF B -> IMS Core B) k) 200 OK (IMS Core B -> IMS Core A) l) 200 OK (IMS Core A -> IM CF A) m) BYE (IM PF B -> IMS Core B) BYE sip:user_b@ :5060 SIP/2.0 70

78 To: Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bkvmkas92 CSeq: 3 BYE From: <sip:conference-factory@operatora.net>;tag=82nbguyh2 Route: <sip:scscf.operatorb.net;lr>, <sip:pcscf.operatorb.net;lr> Call-ID: b82n128dja812 Reason: SIP;cause=480;text="Bearer Temporary unavailable" Contact: <sip:conf-id%40operatora.net_pf-id@operatorb.net>;+g.oma.sip-im;isfocus Max-Forwards: 70 Content-Length: 0 n) BYE (IMS Core B -> User B) o) 200 OK (User B -> IMS Core B) p) 200 OK (IMS Core B -> IM PF B) q) BYE (IM CF A -> IMS Core A) r) BYE (IMS Core A -> IMS Core B) s) BYE (IMS Core B -> IM PF B) t) 200 OK (IM PF B -> IMS Core B) u) 200 OK (IMS Core B -> IMS Core A) v) 200 OK (IMS Core A -> IM CF A) w) BYE (IM PF B -> IMS Core B) x) BYE (IMS Core B -> User B) y) 200 OK (User B -> IMS Core B) z) 200 OK (IMS Core B -> IM PF B) aa) NOTIFY (IM PF B -> IMS Core B) NOTIFY sip:pf-id@operatorb.net:5060 SIP/2.0 To: <sip:user_b@operatorb.net>;tag=8v823 Cseq: 4 NOTIFY From: <sip:conf-id@operatora.net>;tag=vjsu13vd Event: conference Call-ID: wc721k3fiv@operatora.net Contact: sip:conf-id@operatora.net Subscription-State: terminated;reason=noresource Content-Length: 0 71

79 7.2.5 대화방참여자나가기 세션이존재하는경우 단말은 BYE 메시지를전송하여그룹대화방을나가기한다. BYE 메시지는 Reason 헤더 (SIP;cause=200;text= Call completed ) 를포함한다. IM 서버 (CF) 는해당 Reason 헤더가포함된 BYE 메시지를수신하면해당참여자를참여자리스트에서제거하고각참여자에게참여자이벤트를전달한다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment 대화방나가기 1. BYE (Reason: SIP;cause=200;text="Call completed") 2. BYE (Reason: SIP;cause=200;text="Call completed") OK OK 5. BYE (Reason: SIP;cause=200;text="Call completed") OK 9. Conference Event Notification ( 그림 7-18) (Group Chat) 그룹대화방나가기 a) BYE (User A -> IMS Core A) BYE sip:pf-id@operatora.net SIP/2.0 To: <sip:conference-factory@operatora.net>;tag=23b8ajsai Via: SIP/2.0/UDP :1357;branch=z9hG4bKadfsi39239 CSeq: 3 BYE From: <sip:user_a@operatora.net>;tag= Route: <sip:pcscf.operatora.net;lr>, <sip:orig@scscf.operatora.net;lr> Call-ID: cb03a0s09a2sdfglkj Reason: SIP;cause=200;text="Call completed" Contact: <sip: :1357>;+g.oma.sip-im Max-Forwards: 70 Content-Length: 0 b) BYE (IMS Core A -> IM PF A) c) 200 OK (IM PF A -> IMS Core A) d) 200 OK (IMS Core A -> User A) 72

80 e) BYE (IM PF A -> IMS CF A) f) 200 OK (IM CF A -> IMS PF A) 세션이없는경우 GSMA Rich Communication Suite 5.3 Advance Communications Services and Client Specification Version 6.0 표준의 Explicit Departure 절을따른다. 세션이없을때참여자가대화방을나가면, 그룹대화방재시작을위한최초수신된 INVITE 요청에대하여자동으로 603 Decline 응답을전송할수있다. CF 는 603 Decline 응답을수신하면해당참여자를참여자리스트에서제거하고각참여자에게참여자이벤트를전달한다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C Group Chat Session Closed by Inactivity Timeout 1. INVITE (Focus Session ID, Contribution-ID) 2. INVITE (Focus Session ID, Contribution-ID) 3. INVITE (Focus Session ID, Contribution-ID) 4. INVITE (User B) 5. INVITE (User B) 6. INVITE (User B) 7. INVITE (User B) 8. INVITE (User B) OK OK 11. ACK 12. ACK OK OK OK 16. ACK 17. ACK 18. ACK 대화방나가기 MSRP Session establishment Conference Event Subscription OK 21. ACK OK 22. ACK MSRP Session establishment Conference Event Subscription 23. INVITE (User C) 24. INVITE (User C) Decline Decline 35. ACK 36. ACK 25. INVITE (User C) 26. INVITE (User C) 27. INVITE (User C) Decline Decline 30. ACK 31. ACK Decline 37. ACK Conference Event Notification 73

81 ( 그림 7-19) (Group Chat) 세션종료후나가기 서비스해지로인한대화방나가기 Long lived Group Chat 보관기간동안 PF 에서도그룹대화방정보를저장한다. 서비스해지이벤트를수신하면해당참여자의모든그룹대화에서명시적나가기처리한다. 해당사용자의그룹대화가세션이종료된상태이면그룹대화를재개하여명시적나가기처리하므로 CF 의위치가자사 / 타사에관계없이대화방나가기처리를할수있다 대화입력상태전달 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment User A 대화입력 1. MSRP SEND (iscomposing active) 2. MSRP SEND (iscomposing active) 3. MSRP 200 OK 4. MSRP 200 OK 5. MSRP SEND (iscomposing active) 6. MSRP SEND (iscomposing active) 7. MSRP 200 OK 8. MSRP 200 OK User A 대화입력중표시 User A 대화입력취소 13. MSRP SEND (iscomposing idle) 9. MSRP SEND (iscomposing active) 10. MSRP SEND (iscomposing active) 11. MSRP 200 OK 12. MSRP 200 OK 14. MSRP SEND (iscomposing idle) 15. MSRP 200 OK User A 대화입력중표시 16. MSRP 200 OK 17. MSRP SEND (iscomposing idle) 18. MSRP SEND (iscomposing idle) 19. MSRP 200 OK 20. MSRP 200 OK User A 대화입력중표시해제 21. MSRP SEND (iscomposing idle) 22. MSRP SEND (iscomposing idle) 23. MSRP 200 OK 24. MSRP 200 OK User A 대화입력중표시해제 ( 그림 ) (Group Chat) 대화입력상태메시지전달 a) MSRP SEND (User_a -> IM PF A) MSRP 07f906d8 SEND To-Path: msrp:// :19200/36a5188a_0_2_nr;tcp From-Path: msrps:// :7654/iau39soe2843z;tcp Message-ID: 07fa06d8 Byte-Range: 1-341/341 74

82 Content-Type: application/im-iscomposing+xml <?xml version="1.0" encoding="utf-8"?> <iscomposing xmlns="urn:ietf:params:xml:ns:im-iscomposing" xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd"> <state>active</state> <contenttype>text/plain</contenttype> <refresh>90</refresh> </iscomposing> f906d8$ b) MSRP SEND (IM PF A -> IM CF A) c) MSRP 200 OK (IM CF A -> IM PF A) d) MSRP 200 OK (IM PF A -> User A) e) MSRP SEND (IM CF A -> IM PF B) f) MSRP SEND (IM PF B -> User B) g) MSRP 200 OK (User B -> IM PF B) h) MSRP 200 OK (IM PF B -> IM CF A) i) MSRP SEND (IM CF A -> IM PF B) j) MSRP SEND (IM PF B -> User C) k) MSRP 200 OK (User C -> IM PF B) l) MSRP 200 OK (IM PF B -> IM CF A) m) MSRP SEND (User A -> IM PF A) MSRP 07f906d8 SEND To-Path: msrp:// :19200/36a5188a_0_2_nr;tcp From-Path: msrps:// :7654/iau39soe2843z;tcp Message-ID: 07fa06d8 Byte-Range: 1-341/341 Content-Type: application/im-iscomposing+xml <?xml version="1.0" encoding="utf-8"?> <iscomposing xmlns="urn:ietf:params:xml:ns:im-iscomposing" 75

83 xmlns:xsi=" xsi:schemalocation="urn:ietf:params:xml:ns:im-composing iscomposing.xsd"> <state>idle</state> <lastactive> t14:25:11z</lastactive> <contenttype>text/plain</contenttype> </iscomposing> f906d8$ n) MSRP SEND (IM PF A -> IM CF A) o) MSRP 200 OK (IM CF A -> IM PF A) p) MSRP 200 OK (IM PF A -> User A) q) MSRP SEND (IM CF A -> IM PF B) r) MSRP SEND (IM PF B -> User B) s) MSRP 200 OK (User B -> IM PF B) t) MSRP 200 OK (IM PF B -> IM CF A) u) MSRP SEND (IM CF A -> IM PF B) v) MSRP SEND (IM PF B -> User C) w) MSRP 200 OK (User C -> IM PF B) x) MSRP 200 OK (IM PF B -> IM CF A) 76

84 7.2.7 대화하기 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment 1. MSRP SEND (message-id=1, msg1) 2. MSRP SEND (message-id=1, msg1) 3. MSRP 200 OK 4. MSRP 200 OK 5. MSRP SEND (message-id=1, msg1) 6. MSRP SEND (message-id=1, msg1) 7. MSRP 200 OK 8. MSRP 200 OK 9. MSRP SEND (message-id=1, delivered) 10. MSRP SEND (message-id=1, delivered) 11 MSRP 200 OK 12. MSRP 200 OK 13. MSRP SEND (message-id=1, delivered) 14. MSRP SEND (message-id=1, delivered) 15 MSRP 200 OK 16. MSRP 200 OK 17. MSRP SEND (message-id=1, displayed) 18. MSRP SEND (message-id=1, displayed) 19 MSRP 200 OK 20. MSRP 200 OK 21. MSRP SEND (message-id=1, displayed) 22. MSRP SEND (message-id=1, displayed) 23 MSRP 200 OK 24. MSRP 200 OK 25. MSRP SEND (message-id=1, msg1) 26. MSRP SEND (message-id=1, msg1) 28. MSRP 200 OK 27. MSRP 200 OK 29. MSRP SEND (message-id=1, delivered) 30. MSRP SEND (message-id=1, delivered) 31 MSRP 200 OK 32. MSRP 200 OK 33. MSRP SEND (message-id=1, delivered) 34. MSRP SEND (message-id=1, delivered) 35 MSRP 200 OK 36. MSRP 200 OK 37. MSRP SEND (message-id=1, displayed) 38. MSRP SEND (message-id=1, displayed) 39 MSRP 200 OK 40. MSRP 200 OK 41. MSRP SEND (message-id=1, displayed) 42. MSRP SEND (message-id=1, displayed) 43 MSRP 200 OK 44. MSRP 200 OK ( 그림 ) (Group Chat) MSRP 메시지전송 77

85 a) MSRP SEND (User A -> IM PF A) MSRP 07f906d8 SEND To-Path: msrp:// :19200/36a5188a_0_2_nr;tcp From-Path: msrps:// :7654/iau39soe2843z;tcp Message-ID: 07fa06d8 Byte-Range: 1-138/138 Content-Type: Message/CPIM; charset=utf-8 From: <sip:user_a@operatora.net> To: <sip:conference-factory@operatora.net> NS : imdn <urn:ietf:params :imdn> Imdn.Message-ID: msgid1 DateTime: T14:25:11Z imdn.disposition-notification: positive-delivery, display Content-Type: text/plain - 대화내용 f906d8$ b) MSRP SEND (IM PF A -> IM CF A) c) MSRP 200 OK (IM CF A -> IM PF A) d) MSRP 200 OK (IM PF A -> User A) MSRP 07f906d8 200 OK To-Path: msrps:// :7654/iau39soe2843z;tcp From-Path: a=path:msrp:// :19200/36a5188a_0_2_nr;tcp f906d8$ e) MSRP SEND (IM CF A -> IM PF B) MSRP 9a18f0a9c SEND To-Path: msrp:// :19201/93n3423u_2_4_nr;tcp From-Path: msrp:// :19240/73f0367h_1_3_nr;tcp Message-ID: 07fa06d8 Byte-Range: 1-138/138 Content-Type: Message/CPIM; charset=utf-8 Content-Length:.. 78

86 From: To: NS : imdn <urn:ietf:params :imdn> Imdn.Message-ID: msgid1 DateTime: T14:25:11Z imdn.disposition-notification: positive-delivery, display Content-Type: text/plain -대화내용 a18f0a9c$ f) MSRP SEND (IM PF B -> User B) g) MSRP 200 OK (User B -> IM PF B) h) MSRP 200 OK (IM PF B -> IM CF A) i) MSRP SEND (User B -> IM PF B) MSRP d93kswow SEND To-Path: msrp:// :19201/93n3423u_2_4_nr;tcp From-Path: msrps:// :8888/9di4eae923wzd;tcp Message-ID: 12339sdqwer Byte-Range: 1-138/138 Content-Type: Message/CPIM From: <sip:user_b@operatorb.net> To: <sip:conference-factory@operatora.net> NS: imdn <urn:ietf:params:imdn> imdn.message-id: d834jied93rf Content-Type: message/imdn+xml Content-Disposition: notification <?xml version="1.0" encoding="utf-8"?> <imdn xmlns="urn:ietf:params:xml:ns:imdn"> <message-id>msgid1</message-id> <datetime> t14:25:12z</datetime> <recipient-uri>user_b@operatorb.net</recipient-uri> <delivery-notification> 79

87 <status> <delivered/> </status> </delivery-notification> </imdn> d93kswow$ j) MSRP SEND (IM PF B -> IM CF A) k) MSRP 200 OK (IM CF A -> IM PF B) l) MSRP 200 OK (IM PF B -> User B) MSRP d93kswow 200 OK To-Path: msrps:// :8888/9di4eae923wzd;tcp From-Path: msrp:// :19201/93n3423u_2_4_nr;tcp d93kswow$ m) MSRP SEND (IM CF A -> IM PF A) MSRP 9ajdia8110a SEND To-Path: msrp:// :19200/36a5188a_0_2_nr;tcp From-Path: msrp:// :19240/73f0367h_1_3_nr;tcp Message-ID: ajkj1u8a71ljd Byte-Range: 1-138/138 Content-Type: Message/CPIM From: <sip:user_c@operatorb.net> To: <sip:conference-factory@operatora.net> NS: imdn <urn:ietf:params:imdn> imdn.message-id: kjdsaklqj818ua987 Content-Type: message/imdn+xml Content-Disposition: notification <?xml version="1.0" encoding="utf-8"?> <imdn xmlns="urn:ietf:params:xml:ns:imdn"> <message-id>msgid1</message-id> <datetime> t14:25:12z</datetime> <recipient-uri>user_c@operatorb.net</recipient-uri> <delivery-notification> <status> 80

88 <delivered/> </status> </delivery-notification> </imdn> ajdia8110a$ n) MSRP SEND (IM PF A -> User A) o) MSRP 200 OK (User A -> IM PF A) p) MSRP 200 OK (IM PF A -> IM CF A) q) MSRP SEND (User B -> IM PF B) MSRP dkei38sd SEND To-Path: msrp:// :19201/93n3423u_2_4_nr;tcp From-Path: msrps:// :8888/9di4eae923wzd;tcp Message-ID: 12339sdqwer Byte-Range: 1-138/138 Content-Type: Message/CPIM From: <sip:user_b@operatorb.net> To: <sip:conference-factory@operatora.net> NS: imdn <urn:ietf:params:imdn> imdn.message-id: dfjkleriou Content-Type: message/imdn+xml Content-Disposition: notification <?xml version="1.0" encoding="utf-8"?> <imdn xmlns="urn:ietf:params:xml:ns:imdn"> <message-id>msgid1</message-id> <datetime> t14:25:15z</datetime> <recipient-uri>user_b@operatorb.net</recipient-uri> <delivery-notification> <status> <displayed/> </status> </delivery-notification> </imdn> dkei38sd$ 81

89 r) MSRP SEND (IM PF B -> IM CF A) s) MSRP 200 OK (IM CF A -> IM PF B) t) MSRP 200 OK (IM PF B -> User B) MSRP dkei38sd 200 OK To-Path: msrp:// :19201/93n3423u_2_4_nr;tcp From-Path: msrps:// :8888/9di4eae923wzd;tcp dkei38sd$ u) MSRP SEND (IM CF A -> IM PF A) v) MSRP SEND (IM PF A -> User A) w) MSRP 200 OK (User A -> IM PF A) x) MSRP 200 OK (IM PF A -> IM CF A) y) MSRP SEND (IM CF A -> IM PF B) z) MSRP SEND (IM PF B -> User C) aa) MSRP 200 OK (User C -> IM PF B) bb) MSRP 200 OK (IM PF B -> IM CF A) cc) MSRP SEND (User C -> IM PF B) dd) MSRP SEND (IM PF B -> IM CF A) ee) MSRP 200 OK (IM CF A -> IM PF B) ff) MSRP 200 OK (IM PF B -> User C) gg) MSRP SEND (IM CF A -> IM PF A) hh) MSRP SEND (IM PF A -> User A) ii) MSRP 200 OK (User A -> IM PF A) jj) MSRP 200 OK (IM PF A -> IM CF A) kk) MSRP SEND (User C -> IM PF B) ll) MSRP SEND (IM PF B -> IM CF A) mm) MSRP 200 OK (IM CF A -> IM PF B) nn) MSRP 200 OK (IM PF B -> User C) oo) MSRP SEND (IM CF A -> IM PF A) 82

90 pp) MSRP SEND (IM PF A -> User A) qq) MSRP 200 OK (User A -> IM PF A) rr) MSRP 200 OK (IM PF A -> IM CF A) 대화방 Rejoin 단말은 Network Loss 후재접속이가능한시점또는서버로부터 Inactivity Timeout 에의한 BYE 메시지를수신한이후대화재개를위하여 rejoin 시도를한다. 단말은최초대화방개설시에, Contact 헤더에포함된 Focus Session ID 를 Request URI 로설정하여 rejoin 을위한 INVITE 를전송한다. Contribution-ID 를포함해야하며, 참여자리스트는포함하지않아야한다 그룹대화진행중 Rejoin IM 서버 (PF) 가단말로부터 rejoin 요청수신시 Contribution-ID 기준으로세션이 존재하면 rejoin 처리하고, Store 된메시지나 Delivery/Display Notification 메시지가 있으면단말로전달한다. 저장된참여자이벤트가있으면단말로전달한다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C MSRP Session Establishment Network Loss & Acquired MSG Stored msg1, notifications 1. INVITE (Focus Session ID, Contribution-ID) 2. INVITE (Focus Session ID, Contribution-ID) OK OK 5. ACK 6. ACK MSRP Session Establishment Conference Event Subscription 7. MSRP SEND (message-id=1, msg1) 8. MSRP 200 OK Delivery and Display Notifications ( 그림 7-22) (Group Chat) 그룹대화진행중 Rejoin a) INVITE (User B -> IMS Core B) INVITE sip:conf-id@operatora.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 83

91 Route: <sip:pcscf.operatorb.net;lr>,<sip:scscf.operatorb.net;lr> P-Preferred-Identity: "user_b" From: To: Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent:.. v=0 o= IN IP s=c=in IP t=0 0 m=message 8888 TCP/TLS/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrps:// :8888/9di4eae923wzd;tcp b) INVITE (IMS Core B -> IM PF B) c) 200 OK (IM PF B -> IMS Core B) SIP/ OK Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bkbiq892hjg Max-Forwards: 67 Record-Route: <sip:pcscf.operatorb.net;lr>, <sip:scscf.operatorb.net;lr> P-Asserted-Identity: sip:user_b@operatorb.net From: <sip:user_b@operatorb.net>;tag=v82821 To: <sip:conf-id@operatora.net>;tag=

92 Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Session-Expires: 300;refresher=uas Supported: timer Contact: <sip:user_b@ :5060>;+g.oma.sip-im;isfocus Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY User-Agent:.. Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message TCP/MSRP * a=setup:passive a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrp:// :19201/93n3423u_2_4_nr;tcp d) 20 OK (IMS Core B -> User B) e) ACK (User B -> IMS Core B) f) ACK (IMS Core B -> IM PF B) g) MSRP SEND (IM PF B -> User B) h) MSRP 200 OK (User B -> IM PF B) 85

93 그룹대화종료후 Rejoin IM 서버 (PF) 가단말로부터 rejoin 요청을수신하였을때그룹대화세션이종료된상태이면 rejoin 요청을 IM 서버 (CF) 로전달한다. IM 서버 (CF) 가 rejoin 요청을수신하면보관중인그룹대화세션정보와참여자리스트를이용하여대화방을재개한다. IM 서버 (PF) 는그룹대화세션이확립되면사용자에게 Store 된메시지나 Delivery/Display Notification 메시지가있으면단말로전달한다. 저장된참여자이벤트가있으면단말로전달한다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C Group Chat Session Release 8. INVITE (User A) OK 14. ACK MSG Stored msg1, notifications 1. INVITE (Focus Session ID, Contribution-ID) 2. INVITE (Focus Session ID, Contribution-ID) 3. INVITE (Focus Session ID, Contribution-ID) 4. INVITE (Focus Session ID, Contribution-ID) 5. INVITE (Focus Session ID, Contribution-ID) 그룹대화세션정보조회 6. INVITE (User A) 7. INVITE (User A) OK OK 12. ACK 13. ACK MSRP Session Establishment Conference Event Subscription OK OK 19. ACK 20. ACK OK 18. ACK OK 24. ACK OK 23. ACK MSRP Session Establishment Conference Event Subscription 25. INVITE (User C) 26. INVITE (User C) 27. INVITE (User C) 28. INVITE (User C) 29. INVITE (User C) 86

94 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C OK OK 36. ACK 37. ACK OK OK 38. ACK OK OK MSRP Session Establishment Conference Event Subscription 39. MSRP SEND (message-id=1, msg1) 40. MSRP 200 OK Delivery and Display Notifications ( 그림 ) (Group Chat) 그룹대화종료후 Rejoin a) INVITE (User B -> IMS Core B) INVITE sip:conf-id@operatora.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: <sip:pcscf.operatorb.net;lr>,<sip:orig@scscf.operatorb.net;lr> P-Preferred-Identity: "user_b" <sip:user_b@operatorb.net> From: <sip:user_b@operatorb.net>;tag= To: <sip:conference-factory@operatora.net> Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent:.. v=0 o= IN IP

95 s=c=in IP t=0 0 m=message 8888 TCP/TLS/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrps:// :8888/9di4eae923wzd;tcp b) INVITE (IMS Core B -> IM PF B) c) INVITE (IM PF B -> IMS Core B) d) INVITE (IMS Core B -> IMS Core A) e) INVITE (IMS Core A -> IM CF A) f) INVITE (IM CF A -> IM PF A) g) INVITE (IM PF A -> IMS Core A) h) INVITE (IMS Core A -> User A) i) 200 OK (User A -> IMS Core A) j) 200 OK (IMS Core A -> IM PF A) k) 200 OK (IM PF A -> IM CF A) l) ACK (IM CF A -> IM PF A) m) ACK (IM PF A -> IMS Core A) n) ACK (IMS Core A -> User A) o) 200 OK (IM CF A -> IMS Core A) p) 200 OK (IMS Core A -> IMS Core B) q) 200 OK (IMS Core B -> IM PF B) r) ACK (IM PF B -> IMS Core B) s) ACK (IMS Core B -> IMS Core A) t) ACK (IMS Core A -> IM CF A) u) 200 OK (IM PF B -> IMS Core B) v) 200 OK (IMS Core B -> User B) w) ACK (User B -> IMS Core B) 88

96 x) ACK (IMS Core B -> IM PF B) y) INVITE (IM CF A -> IMS Core A) z) INVITE (IMS Core A -> IMS Core B) aa) INVITE (IMS Core B -> IM PF B) bb) INVITE (IM PF B -> IMS Core B) cc) INVITE (IMS Core B -> User C) dd) INVITE (User C -> IMS Core B) ee) 200 OK (IMS Core B -> IM PF B) ff) 200 OK (IM PF B -> IMS Core B) gg) 200 OK (IMS Core B -> User C) hh) 200 OK (IMS Core B -> IMS Core A) ii) 200 OK (IMS Core A -> IM CF A) jj) ACK (IM CF A -> IMS Core A) kk) ACK (IMS Core A -> IMS Core B) ll) ACK (IMS Core B -> IMS Core B) mm) MSRP SEND (IM PF B -> User B) nn) MSRP 200 OK (User B -> IM PF B) 대화방 Restart CF 가그룹대화세션정보의보관주기가만료되어삭제한이후 rejoin 요청을수신하면 404 응답을전송한다. 단말은 404 응답을수신하면기존대화방과동일한 Contribution-ID 와참여자리스트를포함한새로운 Initial INVITE 를전송함으로써대화방을 restart 한다. 89

97 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C Group Chat Session Release 4. INVITE (rejoin) 5. INVITE (rejoin) Not Found Not Found 10. ACK 11. ACK 그룹대화세션정보조회 2. INVITE (rejoin) 3. INVITE (rejoin) Not Found 9. ACK Not Found 15. ACK 17. INVITE 1. INVITE (rejoin) Not Found 14. ACK 16. INVITE 동일한 Contribution-ID 와 resource-lists 를가진 Initial INVITE User B 에의한 Group Chat Restart ( 그림 ) (Group Chat) 대화방 Restart a) INVITE (User B -> IMS Core B) INVITE sip:conference-factory@operatora.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: <sip:pcscf.operatorb.net;lr>,<sip:scscf.operatorb.net;lr> P-Preferred-Identity: "user_b" <sip:user_b@operatorb.net> From: <sip:user_b@operatorb.net>;tag= To: <sip:conference-factory@operatora.net> Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent:.. 90

98 --++ Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message 8888 TCP/TLS/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrps:// :8888/9di4eae923wzd;tcp --++ Content-Type: application/resource-lists+xml Content-Disposition: recipient-list Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" <list> <entry uri="tel:user_a"/> <entry uri="tel:user_c"/> </list> </resource-lists> b) INVITE (IMS Core B -> IM PF B) c) INVITE (IM PF B -> IMS Core B) d) INVITE (IMS Core B -> IMS Core A) e) INVITE (IMS Core A -> IM CF A) f) 404 Not Found (IM CF A -> IMS Core A) g) 404 Not Found (IMS Core A -> IMS Core B) 91

99 h) 404 Not Found (IMS Core B -> IM PF B) i) ACK (IMS Core A -> IMS Core B) j) ACK (IMS Core B -> IMS Core A) k) ACK (IMS Core A -> IM CF A) l) 404 Not Found (IM PF B -> IMS Core B) m) 404 Not Found (IMS Core B -> User B) SIP/ Not Found Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bkbiq892hjg Max-Forwards: 67 Record-Route: <sip:pcscf.operatorb.net;lr>, <sip:scscf.operatorb.net;lr> From: <sip:conference-factory@operatora.net>;tag= To: <sip:user_b@operatorb.net>;tag=v82821 Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 User-Agent:.. Content-Length:.. n) ACK (User B -> IMS Core B) o) ACK (IMS Core B -> IM PF B) p) INVITE (User B -> IMS Core B) 그룹대화 Restart 시 Focus Session은 User의 Network 망에서생성된다. INVITE sip:conference-factory@operatorb.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: <sip:pcscf.operatorb.net;lr>,<sip:orig@scscf.operatorb.net;lr> P-Preferred-Identity: "user_b" <sip:user_b@operatorb.net> From: <sip:user_b@operatorb.net>;tag= To: <sip:conference-factory@operatorb.net> Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uac Supported: timer 92

100 Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent: Content-Type: application/sdp Content-Length:.. v=0 o= IN IP s=c=in IP t=0 0 m=message 8888 TCP/TLS/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrps:// :8888/9di4eae923wzd;tcp --++ Content-Type: application/resource-lists+xml Content-Disposition: recipient-list Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" <list> <entry uri="sip:user_a@operatora.net"/> <entry uri="sip:user_c@operatorb.net"/> </list> </resource-lists>

101 q) INVITE (IMS Core B -> IM PF B) Store and Forward 그룹대화종료후 Deliver Group Chat Messages while Chat is idle (RCS 5.3 Appendix B.1.17.) 을참조하여 작성되었다. Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C Group Chat Session Release MSG Stored: msg1, notifications User B is back online 1. REGISTER OK 3. REGISTER OK 5. INVITE (Focus Session ID, Contribution-ID) 6. INVITE (Focus Session ID, Contribution-ID) 7. INVITE (Focus Session ID, Contribution-ID) 그룹대화세션정보조회 9. INVITE (User A) 10. INVITE (User A) OK OK 8. INVITE (User A) OK 94

102 Network A Network B User A IMS Core RCS IM (PF) RCS IM (CF) RCS IM (PF) IMS Core User B User C 16. ACK 15. ACK 14. ACK MSRP Session Establishment Conference Event Subscription OK OK 21. ACK 22. ACK OK 20. ACK 23. INVITE (User B) 24. INVITE (User B) OK OK 27. ACK 28. ACK OK 32. ACK OK 31. ACK MSRP Session Establishment Conference Event Subscription 33. INVITE (User C) 34. INVITE (User C) OK OK 44. ACK 45. ACK 35. INVITE (User C) 36. INVITE (User C) 37. INVITE (User C) OK OK OK OK 46. ACK MSRP Session Establishment Conference Event Subscription 47. MSRP SEND (message-id=1, msg1) 48. MSRP 200 OK Delivery and Display Notifications ( 그림 ) (Group Chat) 그룹대화종료후저장된메시지전달 a) REGISTER (User B -> IMS Core B) b) 200 OK (IMS Core B -> User B) c) REGISTER (IMS Core B -> IM PF B) d) 200 OK (IM PF B -> IMS Core B) e) INVITE (IM PF B -> IMS Core B) 95

103 INVITE SIP/2.0 Via: SIP/2.0/UDP im.operatorb.net:5060;branch=z9hg4bkbiq892hjg Max-Forwards: 70 Route: P-Asserted-Identity: "user_b" From: To: Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: user_a_ac04ce5254f321455_1 Require: recipient-list-invite, timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length:.. P-Preferred-Service: +g.oma.sip-im User-Agent:.. v=0 o= IN IP s=c=in IP t=0 0 m=message TCP/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrp:// :19201/93n3423u_2_4_nr;tcp f) INVITE (IMS Core B -> IMS Core A) g) INVITE (IMS Core A -> IM CF A) h) INVITE (IM CF A -> IM PF A) i) INVITE (IM PF A -> IMS Core A) j) INVITE (IMS Core A -> User A) 96

104 k) 200 OK (User A -> IMS Core A) l) 200 OK (IMS Core A -> IM PF A) m) 200 OK (IM PF A -> IM CF A) n) ACK (IM CF A -> IM PF A) o) ACK (IM PF A -> IMS Core A) p) ACK (IMS Core A -> User A) q) 200 OK (IM CF A -> IMS Core A) r) 200 OK (IMS Core A -> IMS Core B) s) 200 OK (IMS Core B -> IM PF B) t) ACK (IM PF B -> IMS Core B) u) ACK (IMS Core B -> IMS Core A) v) ACK (IMS Core A -> IM CF A) w) INVITE (IM PF B -> IMS Core B) x) INVITE (IMS Core B -> User B) y) 200 OK (User B -> IMS Core B) z) 200 OK (IMS Core B -> IM PF B) aa) ACK (IM PF B -> IMS Core B) bb) ACK (IMS Core B -> User B) cc) 200 OK (IM PF B -> IMS Core B) dd) 200 OK (IMS Core B -> User B) ee) ACK (User B -> IMS Core B) ff) ACK (IMS Core B -> IM PF B) gg) INVITE (IM CF A -> IMS Core A) hh) INVITE (IMS Core A -> IMS Core B) ii) INVITE (IMS Core B -> IM PF B) jj) INVITE (IM PF B -> IMS Core B) kk) INVITE (IMS Core B -> User C) ll) INVITE (User C -> IMS Core B) 97

105 mm) 200 OK (IMS Core B -> IM PF B) nn) 200 OK (IM PF B -> IMS Core B) oo) 200 OK (IMS Core B -> User C) pp) 200 OK (IMS Core B -> IMS Core A) qq) 200 OK (IMS Core A -> IM CF A) rr) ACK (IM CF A -> IMS Core A) ss) ACK (IMS Core A -> IMS Core B) tt) ACK (IMS Core B -> IMS Core B) uu) MSRP SEND (IM PF B -> User B) vv) MSRP 200 OK (User B -> IM PF B) 7.3 File Transfer HTTP 파일전송의 Content-type 은다음과같이정의한다. < 표 7-3> 파일전송종류별 Content Type File Type form-data, file-info Content-Type image/gif image/wbmp image/bmp Image Video Voice thumbnail, image thumbnail, video voice (image/xbmp) image/png image/jpeg image/jpg image/jpe video/3gp video/3gpp video/3g2 (mp4) audio/amr audio/3gpp (audio/3gp) audio/mpga audio/mpega audio/mp2 98

106 File Type form-data, file-info Content-Type audio/mp3 audio/m4a audio/mid audio/midi audio/kar audio/xmf audio/wav (audio/imy) audio/ogg Contact vcard vcard doc docx ppt pptx Document Document file xls xlsx hwp txt pdf gul, 소용량 / 대용량파일전송구분 목적 UNI 구간의경우단말에서파일전송시파일의크기에따라 IMS PDN 을사용할것인지 Internet PDN 을사용할것인지를정한다. NNI 구간의경우 IMS PDN 으로파일전송이되는경우건당과금하고 Internet PDN 으로들어오는경우패킷과금으로구분하여처리한다 to-1 파일전송 HTTP 파일전송 채팅세션이있는상태에서파일전송 99

107 발신측은채팅세션이존재할경우 Contents Storage 에파일을업로드처리하고 Contents Storage 로부터착신측으로전달할다운로드 URL 을수신하여 MSRP SEND message/cpim 형식으로다운로드 URL 을착신측으로전달한다. 착신측은수신받은다운로드 URL 을통해 Network Storage 로부터파일을다운로드처리한다. Contents 보안을위해 Network Storage 로의모든 HTTP 요청은 HTTP Digest 인증방식으로인증처리하고 TLS 방식으로연동한다. Network A User A IMS Core IM (PF) Network Storage IM (PF) User B Chat Session establishment File upload 1. HTTPS POST (Empty Body) 2. HTTPS 401 Unauthorized 3. HTTPS POST (TID, Thumbnail, Content File) 4. HTTPS 200 OK (application/vnd.rcs-ft-http+xml) 5. MSRP SEND (CPIM, Content-Type : application/vnd.gsma.rcs-ft-http+xml) 6. MSRP SEND (CPIM, Content-Type : application/vnd.gsma.rcs-ft-http+xml) 7. MSRP SEND (CPIM, Content-Type : application/vnd.gsma.rcs-ft-http+xml) 8. MSRP 200 OK 9. MSRP 200 OK 10. MSRP 200 OK 11. MSRP SEND (CPIM/IMDN[Message-ID], delivered) 12. MSRP SEND (CPIM/IMDN[Message-ID], delivered) 13. MSRP SEND (CPIM/IMDN[Message-ID], delivered) 14. MSRP 200 OK 15. MSRP 200 OK 16. MSRP 200 OK 17. HTTPS GET (Thumbnail) 18. HTTPS 401 Unauthorized 19. HTTPS GET (Thumbnail) 20. HTTPS 200 OK Preview 100

108 Network A User A IMS Core IM (PF) Network Storage IM (PF) User B 21. HTTPS GET (Content File) 22. HTTPS 401 Unauthorized 23. HTTPS GET (Content File) 24. HTTPS 200 OK File Donwload 25. MSRP SEND (CPIM/IMDN[Message-ID], displayed) 26. MSRP SEND (CPIM/IMDN[Message-ID], displayed) 27. MSRP SEND (CPIM/IMDN[Message-ID], displayed) 28. MSRP 200 OK 29. MSRP 200 OK 30. MSRP 200 OK ( 그림 ) File Transfer: 세션이있는상태에서 HTTP 파일전송 a) HTTP(S) POST (User A -> Network Storage) POST /rcsim/content/upload HTTP/1.1 Host: :8080 Connection: Close Content-Type: multipart/form-data; boundary=++ Content-Length: 0 b) HTTP(S) 401 Unauthorized (Network Storage -> User A) HTTP/ Unauthorized WWW-Authenticate: Digest realm="scscf1.rcs-domain-name",qop="auth,authint",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",opaque="5ccc069c403ebaf9f0171e9517f40e41" Content-Length: 0 c) HTTP(S) POST(User A -> Network Storage) POST /rcsim/content/upload HTTP/1.1 Host: :8080 Connection: Close Content-Type: multipart/form-data; boundary=++ Authorization: Digest username="user_a",realm=" scscf1.rcs-domain-name ",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",uri="/[upload_url]", qop=auth,nc= , cnonce="0a4f113b",response="6629fae49393a c4ef1",opaque="5ccc069c403ebaf9f017 1e9517f40e41" --++ Content-Disposition: form-data; name="tid 101

109 Content-Type: text/plain Transaction-ID generate by the client --++ Content-Disposition: form-data; name="thumbnail"; filename="abcde12345_thumb.jpg" Content-Type: image/jpg Content-Length: Thumbnail content --++ Content-Disposition: form-data; name="file"; filename="abcde12345.jpg" Content-Type: image/jpg Content-Length: file content d) HTTP(S) 200 OK (Network Storage -> User A) HTTP/ OK Content-Length: Content-Type: application/vnd.gsma.rcs-ft-http+xml <?xml version="1.0" encoding="utf-8"?> <file> <file-info type="thumbnail"> <file-size>293019</file-size> <content-type>image/jpg</content-type> <data url = " :8080/FILE/user_a/ABCDE12345_thumb.jpg" until = " T19:30:00Z"/> </file-info> <file-info type="file"> <file-size>293019</file-size> <file-name>abcde12345.jpg</file-name> <content-type>image/jpg</content-type> <data url = " :8080/FILE/user_a/ABCDE12345.jpg" until = " T19:30:00Z"/> </file-info> </file> 102

110 e) MSRP SEND (User A -> IM PF A) MSRP 07f906d8 SEND To-Path: msrp://im-pf@operatora.net:19245/ims ims;tcp From-Path: msrp://user_a@operatora.net:7000/2b890560;tcp Message-ID: 07fa06d8 Byte-Range: 1-138/138 Content-Type: message/cpim From: 대화명 <sip:user_a@operatora.net> To: <tel:user_b> NS: imdn <usn:ietf:params:imdn> imdn.message-id: 11 DateTime: T22:19:55Z Imdn.Disposition-Notification: positive-delivery, display Content-Type: application/vnd.gsma.rcs-ft-http+xml Content-Length: <?xml version="1.0" encoding="utf-8"?> <file xmlns="urn:gsma:params:xml:ns:rcs:rcs:fthttp"> <file> <file-info type="thumbnail"> <file-size>293019</file-size> <content-type>image/jpg</content-type> <data url = " :8080/FILE/user_a/ABCDE12345_thumb.jpg" until = " T19:30:00Z"/> </file-info> <file-info type="file"> <file-size>293019</file-size> <file-name>abcde12345.jpg</file-name> <content-type>image/jpg</content-type <data url = " :8080/FILE/user_a/ABCDE12345.jpg" until = " T19:30:00Z"/> </file-info> </file> f906d8$ 103

111 f) MSRP SEND (IM PF A -> IM PF B) g) MSRP SEND (IM PF B -> User B) h) MSRP 200 OK (User B -> IM PF B) i) MSRP 200 OK (IM PF B -> IM PF A) j) MSRP 200 OK (IM PF A -> User A) k) MSRP SEND (User B -> IM PF B) l) MSRP SEND (IM PF B -> IM PF A) m) MSRP SEND (IM PF A -> User A) n) MSRP 200 OK (User A -> IM PF A) o) MSRP 200 OK (IM PF A -> IM PF B) p) MSRP 200 OK (IM PF B -> User B) q) HTTP(S) GET (User B -> Network Storage) GET :8080/FILE/user_a/ABCDE12345_thumb.jpg HTTP/1.1 Host: :8080 Connection: close Content-Length: 0 r) HTTP(S) 401 Unauthorized (Network Storage -> User B) HTTP/ Unauthorized WWW-Authenticate: Digest realm="scscf1.rcs-domain-name",qop="auth,authint",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",opaque="5ccc069c403ebaf9f0171e9517f40e41" Content-Length: 0 s) HTTP(S) GET (User B -> Network Storage) GET :8080/FILE/user_a/ABCDE12345_thumb.jpg HTTP/1.1 Host: :8080 Authorization: Digest username="user_a",realm=" scscf1.rcs-domain-name ",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",uri="/[upload_url]", qop=auth,nc= , cnonce="0a4f113b",response="6629fae49393a c4ef1",opaque="5ccc069c403ebaf9f017 1e9517f40e41" Content-Length: 0 t) HTTP(S) 200 OK (Network Storage -> User B) HTTP/ OK Content-Type: image/jpg 104

112 Content-Length:... binary thumbnail image u) HTTP(S) GET (User B -> Network Storage) v) HTTP(S) 401 Unauthorized (Network Storage -> User B) w) HTTP(S) GET (User B -> Network Storage) x) HTTP(S) 200 OK (Network Storage -> User B) y) MSRP SEND (User B -> IM PF B) z) MSRP SEND (IM PF B -> IM PF A) aa) MSRP SEND (IM PF A -> User A) bb) MSRP 200 OK (User A -> IM PF A) cc) MSRP 200 OK (IM PF A -> IM PF B) dd) MSRP 200 OK (IM PF B -> User B) 채팅세션이없는상태에서파일전송 채팅세션이없을경우채팅세션설정후업로드파일 URL 을착신단말로전송한다. 착신단말은업로드파일 URL 수신후다운로드한다. Contents 보안을위해단말은 Network Storage 와 TLS 방식으로연동한다. 105

113 Network A User A IMS Core IM (PF) Network Storage IM (PF) User B File Upload 1. HTTPS POST (Empty Body) 2. HTTPS 401 Unauthorized 3. HTTPS POST (TID, Thumbnail, Content File) 4. HTTPS 200 OK (application/vnd.rcs-ft-http+xml) 5. INVITE / 200 / ACK (1:1 New Chat Session Establish) 6. MESSAGE or MSRP send [CPIM(imdn/Message-ID=1, 'delivered') / 200 OK 7. HTTPS GET (Thumbnail) 8. HTTPS 401 Unauthorized 9. HTTPS GET (Thumbnail) 10. HTTPS 200 OK Preview 11. HTTPS GET (Content File) 12. HTTPS 401 Unauthorized 13. HTTPS GET (Content File) 14. HTTPS 200 OK File Donwload 15. MSRP SEND (CPIM/IMDN[Message-ID], displayed) 16. MSRP SEND (CPIM/IMDN[Message-ID], displayed) 17. MSRP SEND (CPIM/IMDN[Message-ID], displayed) 18. MSRP 200 OK 19. MSRP 200 OK 20. MSRP 200 OK ( 그림 ) File Transfer: 세션이없는상태에서 HTTP 파일전송 a) HTTP(S) POST (User A -> Network Storage) b) HTTP(S) 401 Unauthorized (Network Storage -> User A) c) HTTP(S) POST(User A -> Network Storage) d) HTTP(S) 200 OK (Network Storage -> User A) e) INVITE / 200 OK / ACK INVITE tel:user_b SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: <sip:pcscf.operatora.net:7531;lr;comp=sigcomp>, <sip:orig@scscf.operatora.net;lr> P-Preferred-Identity: "user_a" <sip:user_a@operatora.net> Privacy: none From: <sip:user_a@operatora.net>; tag=

114 To: <tel:user_b> Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Require: timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im; Accept-Contact: :*;+g.oma.sip-im;+g.3gpp.iari-ref="urn%3aurn-7%3a3gppapplication.ims.iari.rcs.fthttp";require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length: ( ) --++ Content-Type: application/sdp v=0 o= IN IP s=c=in IP t=0 0 m=message 3402 TCP/TLS/MSRP * a=accept-types:message/cpim application/im-iscomposing+xml a=path:msrps:// :3402/111111;tcp a=accept-wrapped-types: * --++ Content-Type: message/cpim From: 대화명 <sip:user_a@operatora.net> To: <tel:user_b> NS: imdn <usn:ietf:params:imdn> imdn.message-id: 11 DateTime: T22:19:55Z Imdn.Disposition-Notification: positive-delivery, display Content-Type: application/vnd.gsma.rcs-ft-http+xml Content-Length: 107

115 <?xml version="1.0" encoding="utf-8"?> <file xmlns="urn:gsma:params:xml:ns:rcs:rcs:fthttp"> <file> <file-info type="thumbnail"> <file-size>293019</file-size> <content-type>image/jpg</content-type> <!-- RCS > <data url = " :8080/FILE/user_a/ABCDE12345_thumb.jpg" until = " T19:30:00Z"/> </file-info> <file-info type="file"> <file-size>293019</file-size> <file-name>abcde12345.jpg</file-name> <!-- RCS > <content-type>image/jpg</content-type> <!-- RCS > <data url = " :8080/FILE/user_a/ABCDE12345.jpg" until = " T19:30:00Z"/> </file-info> </file> f) MSRP SEND or MESSAGE (delivered) / 200 OK : 세션이존재하지않으면, MESSAGE Method로 delivered를전송한다. g) HTTP(S) GET (User B -> Network Storage) h) HTTP(S) 401 Unauthorized (Network Storage -> User B) i) HTTP(S) GET (User B -> Network Storage) j) HTTP(S) 200 OK (Network Storage -> User B) k) HTTP(S) GET (User B -> Network Storage) l) HTTP(S) 401 Unauthorized (Network Storage -> User B) m) HTTP(S) GET (User B -> Network Storage) HTTP 200 OK (Network Storage -> User B) n) MSRP SEND (User B -> IM PF B) o) MSRP SEND (IM PF B -> IM PF A) p) MSRP SEND (IM PF A -> User A) q) MSRP 200 OK (User A -> IM PF A) 108

116 r) MSRP 200 OK (IM PF A -> IM PF B) s) MSRP 200 OK (IM PF B -> User B) 그룹파일전성 HTTP 파일전송 채팅세션이있는상태에서파일전송 채팅세션존재할경우채팅세션을통해서업로드파일 URL 을착신단말로전송한다. 착신단말은업로드파일 URL 수신후다운로드한다. Contents 보안을위해단말은 Network Storage 와 TLS 방식으로연동한다. 109

117 Network A User A IMS Core IM (PF) Network Storage IM (PF) User B User C Chat Session establishment File Upload 1. HTTPS POST (Empty Body) 2. HTTPS 401 Unauthorized 3. HTTPS POST (TID, Thumbnail, Content File) 4. HTTPS 200 OK (application/vnd.rcs-ft-http+xml) 5. MSRP SEND [CPIM(imdn/Message-ID=1, URL) / 200 OK 6. MSRP SEND [CPIM(imdn/Message-ID=1, ' delivered ') / 200 OK 7. HTTPS GET (Thumbnail) 8. HTTPS 401 Unauthorized 9. HTTPS GET (Thumbnail) 10. HTTPS 200 OK Preview 11. HTTPS GET (Content File) 12. HTTPS 401 Unauthorized 13. HTTPS GET (Content File) 14. HTTPS 200 OK File Donwload 15. MSRP SEND [CPIM(imdn/Message-ID=1, ' displayed ') / 200 OK 16. HTTPS GET (Thumbnail) 17. HTTPS 401 Unauthorized 18. HTTPS GET (Thumbnail) 19. HTTPS 200 OK Pop Up Preview 20. HTTPS GET (Content File) 21. HTTPS 401 Unauthorized 22. HTTPS GET (Content File) 23. HTTPS 200 OK File Donwload 24. MSRP SEND [CPIM(imdn/Message-ID=1, ' displayed ') / 200 OK ( 그림 ) File Transfer: 세션이있는경우 HTTP 파일전송 a) HTTPS POST (User A -> Network Storage) b) HTTPS 401 Unauthorized (Network Storage -> User A) c) HTTPS POST(User A -> Network Storage) d) HTTPS 200 OK (Network Storage -> User A) e) MSRP SEND / MSRP 200 OK f) MSRP SEND / MSRP 200 OK g) HTTPS GET (User B -> Network Storage) h) HTTPS 401 Unauthorized (Network Storage -> User B) 110

118 i) HTTPS GET (User B -> Network Storage) j) HTTPS 200 OK (Network Storage -> User B) k) HTTPS GET (User B -> Network Storage) l) HTTPS 401 Unauthorized (Network Storage -> User B) m) HTTPS GET (User B -> Network Storage) n) HTTPS 200 OK (Network Storage -> User B) o) MSRP SEND / MSRP 200 OK p) HTTPS GET (User C -> Network Storage) q) HTTPS 401 Unauthorized (Network Storage -> User C) r) HTTPS GET (User C -> Network Storage) s) HTTPS 200 OK (Network Storage -> User C) t) HTTPS GET (User C -> Network Storage) u) HTTPS 401 Unauthorized (Network Storage -> User C) v) HTTPS GET (User C -> Network Storage) w) HTTPS 200 OK (Network Storage -> User C) x) MSRP SEND / MSRP 200 OK 채팅세션이없는상태에서파일전송 채팅세션이없을경우채팅세션설정후업로드파일 URL 을착신단말로전송한다. 착신단말은업로드파일 URL 수신후다운로드한다. Contents 보안을위해단말은 Network Storage 와 TLS 방식으로연동한다. 111

119 Network A User A IMS Core IM (PF) Network Storage IM (PF) User B User C File Upload 1. HTTPS POST (Empty Body) 2. HTTPS 401 Unauthorized 3. HTTPS POST (TID, Thumbnail, Content File) 4. HTTPS 200 OK (application/vnd.rcs-ft-http+xml) 5. INVITE / 200 / ACK (1:N new chat session establish) 6. MSRP SEND [CPIM(imdn/Message-ID=1, URL) / 200 OK 7. MSRP SEND [CPIM(imdn/Message-ID=1, ' delivered ') / 200 OK 8. HTTPS GET (Thumbnail) 9. HTTPS 401 Unauthorized 10. HTTPS GET (Thumbnail) 11. HTTPS 200 OK Preview 12. HTTPS GET (Content File) 13. HTTPS 401 Unauthorized 14. HTTPS GET (Content File) 15. HTTPS 200 OK File Donwload 16. MSRP SEND [CPIM(imdn/Message-ID=1, ' displayed ') / 200 OK 17. HTTPS GET (Thumbnail) 18. HTTPS 401 Unauthorized 19. HTTPS GET (Thumbnail) 20. HTTPS 200 OK Preview 21. HTTPS GET (Content File) 22. HTTPS 401 Unauthorized 23. HTTPS GET (Content File) 24. HTTPS 200 OK File Donwload 25. MSRP SEND [CPIM(imdn/Message-ID=1, ' displayed ') / 200 OK ( 그림 ) File Transfer: 세션이없는경우 HTTP 파일전송 a) HTTP(S) POST (User A -> Network Storage) b) HTTP(S) 401 Unauthorized (Network Storage -> User A) c) HTTP(S) POST(User A -> Network Storage) d) HTTP(S) 200 OK (Network Storage -> User A) e) INVITE / 200 OK / ACK INVITE sip:conference-factory@operatora.net SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: <sip:pcscf.operatora.net;lr>,<sip:orig@scscf.operatora.net;lr> P-Preferred-Identity: "user_a" <sip:user_a@operatora.net> 112

120 Privacy: none From: tag= To: Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Require:recipient-list-invite, timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im;+g.3gpp.iari-ref="urn%3aurn-7%3a3gppapplication.ims.iari.rcs.fthttp" Accept-Contact: *;+g.oma.sip-im;require;explicit; Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length: ( ) Subject: Initial message --++ Content-Type: application/sdp v=0 o= IN IP s=c=in IP t=0 0 m=message 3402 TCP/TLS/MSRP * a=setup:active a=accept-types:message/cpim a=accept-wrapped-types: * a=path:msrps:// :3402/111111;tcp --++ Content-Type: application/resource-lists+xml Content-Disposition: recipient-list <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" <list> 113

121 <entry uri="tel:user_b"/> <entry uri="tel:user_c"/> </list> </resource-lists> f) MSRP SEND / MSRP 200 OK g) MSRP SEND / MSRP 200 OK h) HTTPS GET (User B -> Network Storage) i) HTTPS 401 Unauthorized (Network Storage -> User B) j) HTTPS GET (User B -> Network Storage) k) HTTPS 200 OK (Network Storage -> User B) l) HTTPS GET (User B -> Network Storage) m) HTTPS 401 Unauthorized (Network Storage -> User B) n) HTTPS GET (User B -> Network Storage) o) HTTPS 200 OK (Network Storage -> User B) p) MSRP SEND / MSRP 200 OK q) HTTPS GET (User C -> Network Storage) r) HTTPS 401 Unauthorized (Network Storage -> User C) s) HTTPS GET (User C -> Network Storage) t) HTTPS 200 OK (Network Storage -> User C) u) HTTPS GET (User C -> Network Storage) v) HTTPS 401 Unauthorized (Network Storage -> User C) w) HTTPS GET (User C -> Network Storage) x) HTTPS 200 OK (Network Storage -> User C) y) MSRP SEND / MSRP 200 OK 대용량파일전송 114

122 Management Object(MO) 의 ALWAYS_USE_IMS_APN=1 인 IMS PDN 기반사업자는모든 RCS 서비스를 IMS PDN 기반으로사용하여야한다. 하지만대용량파일전송시 Internet APN 을사용하면더다양한서비스와효율적인망운용을가능하게한다. 이를위해 RCS 서비스 feature(im/ft 등 ) 중 ALWAYS_USE_IMS_APN 의예외가적용되는신규 FTviaHTTP 서비스를정의한다. 새로운 FTviaHTTP 서비스는 RCS 사업자별로 APN 정책을달리적용가능하도록하여 Internet APN 을사용하도록한다. FTExtra feature 를통해전송가능한 content type(mime type) 과 max size 는사업자별로정책을정의할수있으며, 사업자간상호전송가능한 contents 및상호접속료율은다를수있다. 국내사업자향단말은기본파일전송의 MAX SIZE 를초과하고 FTExtra MAX SIZE 를초과하지않은파일에대해 FTExtra 서비스를이용한파일전송을지원하여야한다. 수신시에는파일사이즈를확인하지않는다. Data off 시대용량파일수 / 발신은제공하지않는다. MMS 수 / 발신시나리오와동일하게처리한다 Service Definition 신규 feature tag 및 service-id 는다음과같다. < 표 7-4> 대용량파일전송을위한신규 feature tag 및 service-id Feature tag Service-id +g.3gpp.iari-ref="urn%3aurn-7%3a3gpp-application.ims.iari.rcs.fthttpextra org.openmobilealliance:file-transfer-http-extra Version: 1.0 FTExtra 를위한 configuration 은다음과같다. < 표 7-5> 대용량파일전송을위한 configuration parameter Configuration Parameter Description RCS usage FT_HTTP_EXTRA_MAX_SIZE FTExtra 로전송가능한최대크기 (kb) Mandatory FT_HTTP_EXTRA_CS_URI FTExtra 로사용할 HTTP CS URI Mandatory 115

123 착신측에서 FT 와 FTExtra 를구별하기위해서 namespace 를사용한다. 이를위해 CPIM 의헤더에국내규격으로네임스페이스와헤더를추가하여표시한다. NS : rcs< 장 / 단문의경우도다음과같이동일한네임스페이스를사용한다. NS : rcs< < 표 7-6> 대용량파일전송을위한 CPIM 헤더 CPIM Header Status Content 비고 rcs.fthttptype Optional extra: Extra FT HTTP ( 대용량 ) [ 발신동작 ] 발신단말은 FT HTTP 전송시 file type/size 를체크하여해당 CPIM 헤더추가삽입 [ 수신동작 ] 헤더없을경우 : 일반 FT HTTP 로처리 ( 소용량 / 표준동작 ) 헤더값이 extra 일경우 : Extra FT HTTP 로처리 ( 대용량 ) Localization Function 파일전송시타사에콘텐츠저장되어있는경우착신측은착신측자사 Content Server 로인증및다운로드를요청한다. 요청을받은자사의 Content Server 는타사 Content Server 로파일다운로드를요청처리한다. Content Server 는타사에서전송받은파일을착신측으로전달한다 vcard Exchange 파일전송절차를이용하여 vcard 3.0 Format 의연락처를전송한다. 116

124 Network A Network A User A IMS Core IM (PF) IM(PF) IMS Core User B 1. INVITE / 200 / ACK (1:1 File Transfer Session establish) 2. MSRP SEND (CPIM, Content-Type : text/vcard) 3. MSRP SEND (CPIM, Content-Type : text/vcard) 4. MSRP SEND (CPIM, Content-Type : text/vcard) 5. MSRP 200 OK 6. MSRP 200 OK 7. MSRP 200 OK 8. BYE / 200 OK ( Session Release) 9. MESSAGE [CPIM(imdn/Message-ID=1, ' delivered ') / 200 OK ( 그림 7-30) File Transfer: vcard Exchange a) INVITE / 200 / ACK INVITE tel:user_b SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: <sip:pcscf.operatora.net:7531;lr>,<sip:orig@scscf.operatora.net;lr> P-Preferred-Identity: "user_a" <sip:user_a@operatora.net> Privacy: none From: <sip:user_a@operatora.net>; tag= To: <tel:user_b> Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Contribution-ID: 1794ac04ce5254f321334_0 Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im Accept-Contact: *;+g.oma.sip-im;require;explicit P-Preferred-Service: +g.oma.sip-im Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/related; type="application/sdp"; boundary="++" Content-Length: ( ) --++ Content-Type: application/sdp 117

125 Content-Length: v=0 o= IN IP4 user_a.operatora.net s=c=in IP4 user_a.operatora.net t=0 0 m=message 3402 TCP/TLS/MSRP * a=setup:active a=sendonly a=accept-types:text/vcard a=path:msrps://user_a.operatora.net/50007;tcp a=file-selector:name:"user_a" type:text/vcard size:4096 a=file-transfer-id:u8a9102jaheoadjqoaze a=file-disposition:attachment a=file-date:creation:"thu, 14 Jun :06: " a=accept-wrapped-types:* --++ Content-Type: message/cpim;charset=utf-8 Content-Length: From: user_a <sip:user_a@operatora.net> To: <tel:user_b> DateTime: T15:09:12Z NS: imdn <urn:ietf:params:imdn> imdn.message-id: 1 imdn.disposition-notification: positive-delivery b) MSRP SEND (User A -> IM PF A) MSRP 07f906d8 SEND To-Path: msrp://im-pf@operatora.net:19245/ims ims;tcp From-Path: msrp://user_a@operatora.net:7000/2b890560;tcp Message-ID: 07fa06d8 Byte-Range: 1-384/384 Content-Type: text/vcard 118

126 BEGIN:VCARD VERSION:3.0 N:Gump;Forrest FN:Forrest Gump ORG:Bubba Gump Shrimp Co. TITLE:Shrimp Man PHOTO;VALUE=URL;TYPE=GIF: TEL;TYPE=WORK,VOICE:(111) TEL;TYPE=HOME,VOICE:(404) ADR;TYPE=WORK:;;100 Waters Edge;Baytown;LA;30314;United States of America LABEL;TYPE=WORK:100 Waters Edge\nBaytown, LA 30314\nUnited States of America ADR;TYPE=HOME:;;42 Plantation St.;Baytown;LA;30314;United States of America LABEL;TYPE=HOME:42 Plantation St.\nBaytown, LA 30314\nUnited States of America REV: T195243Z END:VCARD f906d8$ c) MSRP SEND (IM PF A -> IM PF B) d) MSRP SEND (IM PF B -> User B) e) MSRP 200 OK (User B -> IM PF B) f) MSRP 200 OK (IM PF B -> IM PF A) g) MSRP 200 OK (IM PF A -> User A) h) BYE / 200 OK i) MSRP SEND / 200 OK Pause & Resume HTTP 방식의파일전송시 Content Server 로파일업로드 / 다운로드처리중사용자또는특정오류로인하여파일송수신이 Pause 처리되었을경우파일중단된지점부터파일을송수신할수있다. 업로드시 Pause & Resume 을지원하기위해서는반드시 POST 를통해서업로드요청이되어야하며메시지 Body 의 Multipart Content 에 tid 를포함하는경우에만가능하다. 119

127 다운로드의경우 Content-Range 헤더를포함하여다운로드되는파일의정보를 포함하는경우에만가능하다 File Upload Pause & Resume 최초파일 POST 업로드시 HTTP POST Request 메시지 Body 를 multipart/form-data 로 구성하고 TID 를포함하는경우 Pause & Resume 기능을제공한다. ( 그림 ) File Transfer: File Upload Pause & Resume a) HTTP(S) POST (User A -> Network Storage) b) HTTP(S) 401 Unauthorized (Network Storage -> User A) c) HTTP(S) POST(User A -> Network Storage) d) HTTP(S) GET(User A -> Network Storage) 120

128 GET /?tid=<tid_value>&get_upload_info HTTP/1.1 Host: :8080 User-Agent: Content-Length: 0 HTTP(S) 401 Unauthorized (Network Storage -> User A) HTTP/ Unauthorized WWW-Authenticate: Digest realm="scscf1.rcs-domain-name",qop="auth,authint",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",opaque="5ccc069c403ebaf9f0171e9517f40e41" Content-Length: 0 e) HTTP(S) GET (User A -> Network Storage) GET /?tid=<tid_value>&get_upload_info HTTP/1.1 Host: :8070 User-Agent: Authorization: Digest username="user_a",realm=" scscf1.rcs-domain-name ",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",uri="/", qop=auth,nc= , cnonce="0a4f113b",response="6629fae49393a c4ef1",opaque="5ccc069c403ebaf9f017 1e9517f40e41" Content-Length: 0 f) HTTP(S) 200 OK (Network Storage -> User A) HTTP/ OK Content-Type: application/vnd.gsma.rcs-ft-http+xml Content-Length: <?xml version="1.0" encoding="utf-8"?> <file-resume-info xmlns="urn:gsma:params:xml:ns:rcs:rcs:fthttpresume"> <file-range start="0" end="193019" / > <data url=" :8080/FILE/user_a/ABCDE12345.jpg"/> </file-resume-info> g) HTTP(S) PUT (User A -> Network Storage) PUT /FILE/user_a/ABCDE12345.jpg HTTP/1.1 Content-Type: image/jpeg Content-Length: Content-Range: bytes / Authorization: Digest username="user_a",realm=" scscf1.rcs-domain-name ",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",uri="/", qop=auth,nc= , cnonce="0a4f113b",response="6629fae49393a c4ef1",opaque="5ccc069c403ebaf9f017 1e9517f40e41" 121

129 <file content> h) HTTP(S) 200 OK (Network Storage -> User A) i) HTTP(S) GET (User A -> Network Storage) GET /?tid=<tid_value>&get_download_info HTTP/1.1 Host: :8070 User-Agent: Authorization: Digest username="user_a",realm=" scscf1.rcs-domain-name ",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",uri="/", qop=auth,nc= , cnonce="0a4f113b",response="6629fae49393a c4ef1",opaque="5ccc069c403ebaf9f017 1e9517f40e41" Content-Length: 0 j) HTTP(S) 200 OK (Network Storage -> User A) HTTP/ OK Content-Length: Content-Type: application/vnd.gsma.rcs-ft-http+xml <?xml version="1.0" encoding="utf-8"?> <file> <file-info type="thumbnail"> <file-size>293019</file-size> <content-type>image/jpg</content-type> <data url = " :8080/FILE/user_a/ABCDE12345_thumb.jpg" until = " T19:30:00Z"/> </file-info> <file-info type="file"> <file-size>293019</file-size> <file-name>abcde12345.jpg</file-name> <content-type>image/jpg</content-type> <data url = " :8080/FILE/user_a/ABCDE12345.jpg" until = " T19:30:00Z"/> </file-info> </file> 122

130 File Download Pause & Resume 파일다운로드중 Pause 되고, Resume 을시도하는경우수신받은 Download URL 로 다운로드를재시도한다. Resume HTTP GET 의경우 Content-Range Header 를반드시 포함해야한다. Network A User A IMS Core IM (PF) Network Storage IM (PF) User B Chat Session establishment 1. MSRP SEND [CPIM(imdn/Message-ID=1, File Donwload URL) / 200 OK 2. MESSAGE or MSRP SEND [CPIM(imdn/Message-ID=1, ' delivered ') / 200 OK 3. HTTPS GET (Thumbnail) 4. HTTPS 401 Unauthorized 5. HTTPS GET (Thumbnail) 6. HTTPS 200 OK Preview 7. HTTPS GET (Content File) 8. HTTPS 401 Unauthorized 9. HTTPS GET (Content File) File Donwload Pause Resume 10. HTTPS GET <File Content URL> (response, Content-Range) Partial Content 12. MSRP SEND [CPIM(imdn/Message-ID=1, 'displayed') / 200 OK ( 그림 ) File Transfer: File Download Pause & Resume a) MSRP 를통한파일다운로드정보송수신 b) 파일다운로드정보수신에대한 Delivered Notification 송수신 c) HTTPS GET (User B -> Network Storage) d) HTTPS 401 Unauthorized (Network Storage -> User B) e) HTTPS GET (User B -> Network Storage) 123

131 f) HTTP 200 OK (Network Storage -> User B) g) HTTPS GET (User B -> Network Storage) h) HTTPS 401 Unauthorized (Network Storage -> User B) i) HTTPS GET (User B -> Network Storage) j) HTTPS GET (User B -> Network Storage) GET :8080/FILE/user_a/ABCDE12345_thumb.jpg HTTP/1.1 Host: :8080 Authorization: Digest username="user_a",realm=" scscf1.rcs-domain-name ",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",uri="/[upload_url]", qop=auth,nc= , cnonce="0a4f113b",response="6629fae49393a c4ef1",opaque="5ccc069c403ebaf9f017 1e9517f40e41" Content-Range: byte / Content-Length: 0 k) HTTP 206 Partial content (Network Storage -> User B) HTTP/ Partial content Date: Wed, 15 Nov :25:24 GMT Last-Modified: Wed, 15 Nov :58:08 GMT Content-Range: bytes / Content-Length: Content-Type: image/jpg... binary content 파일전송시 thumbnail max size 제한 파일전송시 thumbnail max size 를제한할수있다. 7.4 Content Sharing Content Sharing 서비스는 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다. 7.5 Capability Discovery Capability discovery process through OPTIONS 124

132 OPTIONS 를이용한 Capability discovery 는 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 을따른다 Capability discovery via Presence Discovery via presence 지원 착신 : sip:user1@operatora.net RCS client 의 configuration parameter 중 CAPABILITY DISCOVRY MECHANISM 설정이 PRESENCE 인경우지원된다. Network A Network B user1@operator A.net RCS AS PS_A IMS Core_A IBCF_A IBCF_B IMS Core_B RCS AS PS_B user2@operator B.net 0. Registration 1. PUBLISH (capabilities) 2. PUBLISH (capabilities) OK OK 5. SUBSCRIBE (Anonymous Fetch) 6. SUBSCRIBE (Anonymous Fetch) 7. SUBSCRIBE (Anonymous Fetch) 8. SUBSCRIBE (Anonymous Fetch) 9. SUBSCRIBE (Anonymous Fetch) OK OK 15. NOTIFY (user1 Capabilities) OK 16. NOTIFY (user1 Capabilities) OK 17. NOTIFY (user1 Capabilities) OK 18. NOTIFY (user1 Capabilities) 19. NOTIFY (user1 Capabilities) OK OK OK OK OK ( 그림 ) Capability discovery via presence 0. Registration (user1 IMS Core_A) 1) user1@operatora.net 는 Registration 절차를완료한다. l) PUBLISH capabilities (user1 IMS Core_A) 125

133 1) Expires 정보는 PUBLISH EXPIRY TIME ( 참조 Blackbrid 단말 Auto- Configuration Server 연동 ) 로설정한다. Provisioning 정보가없으면 Registration 시간과동일하게설정한다. 2) Body의 <tuple> 정보에단말에서지원가능한서비스 Tag 정보를설정한다. PUBLISH sip:user1@operatora.net SIP/2.0 Via: SIP/2.0/UDP user1-ip:port;branch=z9hg4bk-092kda9fd Max-Forwards: 70 To: <sip:user1@operatora.net> From: <sip:user1@operatora.net>;tag= Call-ID: a84b4c76e66710 CSeq: 1 PUBLISH Route: <sip:registration-serivce-route-header-value;lr> Event: presence Expires: 3600 P-Asserted-Identity: <sip:user1@operatora.net> Contact: <sip:user1-ip:port> Content-Length: 1897 Content-Type: application/pidf+xml;charset= UTF-8 <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns:opd="urn:oma:xml:pde:pidf:ext" xmlns:opd11="urn:oma:xml:pde:pidf:ext:1.1" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps" xmlns:gml=" xmlns:gs=" entity="sip:user1@operatora.net"> <tuple id="a2"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.3gpp.urn:urn-7:3gpp-servie.ims.icsi.mmtel</op:service-id> <op:version>1.0</op:version> </op:service-description> <caps:servcaps> <caps:audio>true</caps:audio> <caps:duplex><caps:supported><caps:full/></caps:supported></caps:duplex> 126

134 </caps:servcaps> </tuple> <tuple id="a1"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.3gpp.cs-videotelephony</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <tuple id="a12"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.gsma.videoshare</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <tuple id="a123"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.gsma.videoshare</op:service-id> <op:version>2.0</op:version> </op:service-description> </tuple> <tuple id="a132"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.openmobilealliance:im-session</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> </presence> m) PUBLISH capabilities (IMS Core_A RCS AS PS_A) 127

135 n) 200 OK(RCS AS PS_A IMS Core_A) o) 200 OK (IMS Core_A SIP/ OK Via: SIP/2.0/UDP user1-ip:port;branch=z9hg4bk-092kda9fd Max-Forwards: 70 To: From: Call-ID: a84b4c76e66710 CSeq: 1 PUBLISH SIP-ETag: A Contact: <sip:rcs AS PS_A_INFO> Expires: 3600 Content-Length: 0 1) SIP-ETag 정보를저장하고, Publish 정보를변경 (Publishing 시간연장, Capabilities 변경, de-registratio에의한 Publish 정보삭제 ) 요청하는경우 SIP-If-Match Header 정보에설정한다. p) SUBSCRIBE Anonymous Fetch (user2@operatorb.net IMS Core_B) SUBSCRIBE tel:user1 SIP/2.0 Via: SIP/2.0/UDP user2-ip:port;branch=z9hg4bk-092kda9fd Max-Forwards: 70 To: <tel:user1 > From: Anonymous <sip:anonymous@operatorb.net>;tag= Call-ID: a84b4c76e66710 CSeq: 1 SUBSCRIBE Route: <sip:registration-serivce-route-header-value;lr> Event: presence Expires: 0 P-Asserted-Identity: <sip:user2@operatorb.net> Privacy: id Accept: application/pidf+xml Contact: <sip:user2-ip:port> Content-Length: 0 SUBSCRIBE Anonymous Fetch (IMS Core_B IBCF_B) 1) IMS Core_B의착신서비스진행에의해 IBCF_B 로전달된다. SUBSCRIBE sip:user1@operatora.net SIP/

136 Via: Max-Forwards: To: <tel:user1 > From: Call-ID: CSeq: Route: <sip:ibcf_b_info;lr> Event: presence Expires: 0 Privacy: id Accept: application/pidf+xml Contact: Content-Length: 0 q) SUBSCRIBE Anonymous Fetch (IBCF_B IBCF_A) SUBSCRIBE sip:user1@operatora.net SIP/2.0 Via: Max-Forwards: To: <tel:user1 > From: Call-ID: CSeq: Route: <sip:ibcf_a_info;lr> Event: presence Expires: 0 Privacy: id Accept: application/pidf+xml Contact: <sip:ibcf_b%1fuser2%1foperatorb_net%1f@ibcf.operatorb.net> Content-Length: 0 r) SUBSCRIBE Anonymous Fetch (IBCF_A IMS Core_A) s) SUBSCRIBE Anonymous Fetch (IMS Core_A RCS AS PS_A) t) 200 OK (RCS AS PS_A IMS Core_A) SIP/ OK Via: To: <tel:user1>;tag=2 From: Call-ID: 129

137 CSeq: Event: presence Expires: 0 Contact: <sip:rcs AS PS_A_INFO> Content-Length: 0 u) 200 OK (IMS Core_A IBCF_A) v) 200 OK (IBCF_A IBCF_B) w) 200 OK (IBCF_B IMS Core_B) x) 200 OK (IMS Core_B user2@operatorb.net) y) NOTIFY user1 Capabilities (RCS AS PS_A IMS Core_A) NOTIFY sip:ibcf_a%1fuser1%1foperatora_net%1f@ibcf.operatora.net SIP/2.0 Via: SIP/2.0/UDP rcs_as_ps_ip:port;branch=z9hg4bk-2 To: Anonymous <sip:anonymous@operatorb.net>;tag= From: <tel:user1>;tag=2 Call-ID: CSeq: 1 NOTIFY Max-Forwards: 70 Event: presence Route: Subscription-State: terminated;reason=timeout Contact: <sip:rcs AS PS_A_INFO> Content-Type: application/pidf+xml;charset= UTF-8 Content-Length: 1897 <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns:opd="urn:oma:xml:pde:pidf:ext" xmlns:opd11="urn:oma:xml:pde:pidf:ext:1.1" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps" xmlns:gml=" xmlns:gs=" entity="sip:user1@operatora.net"> <tuple id="a2"> <status><basic>open</basic></status> <op:service-description> 130

138 <op:service-id>org.3gpp.urn:urn-7:3gpp-servie.ims.icsi.mmtel</op:service-id> <op:version>1.0</op:version> </op:service-description> <caps:servcaps> <caps:audio>true</caps:audio> <caps:duplex><caps:supported><caps:full/></caps:supported></caps:duplex> </caps:servcaps> </tuple> <tuple id="a1"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.3gpp.cs-videotelephony</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <tuple id="a12"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.gsma.videoshare</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <tuple id="a123"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.gsma.videoshare</op:service-id> <op:version>2.0</op:version> </op:service-description> </tuple> <tuple id="a132"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.openmobilealliance:im-session</op:service-id> <op:version>1.0</op:version> 131

139 </op:service-description> </tuple> </presence> z) NOTIFY user1 Capabilities (IMS Core_A IBCF_A) aa) NOTIFY user1 Capabilities (IBCF_A IBCF_B) bb) NOTIFY user1 Capabilities (IBCF_B IMS Core_B) cc) NOTIFY user1 Capabilities (IMS Core_B dd) 200 OK IMS Core_B) SIP/ OK Via: To: From: Call-ID: CSeq: 1 NOTIFY Contact: <sip:user2_info> Content-Length: 0 ee) 200 OK (IMS Core_B IBCF_B) ff) 200 OK (IBCF_B IBCF_A) gg) 200 OK (IBCF_A IMS Core_A) hh) 200 OK (IMS Core_A RCS AS PS_A) Capability polling mechanism Capability polling via OPTIONS message OPTIONS 를이용한 Capability pollig 은 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 을따른다 Capability polling via anonymous fetch a) 발신 : sip:user1@operatora.net b) 착신 : sip:user2@operatorb.net 132

140 Network A Network B user1@operator A.net RCS AS PS_A IMS Core_A IBCF_A IBCF_B IMS Core_B RCS AS PS_B user2@operator B.net Polling timer expires 1. SUBSCRIBE (Anonymous Fetch) 2. SUBSCRIBE (Anonymous Fetch) 3. SUBSCRIBE (Anonymous Fetch) 4. SUBSCRIBE (Anonymous Fetch) 5. SUBSCRIBE (Anonymous Fetch) OK OK 11. NOTIFY (user1 Capabilities) OK 12. NOTIFY (user1 Capabilities) OK 13. NOTIFY (user1 Capabilities) OK 14. NOTIFY (user1 Capabilities) 15. NOTIFY (user1 Capabilities) OK OK OK OK OK Restart polling timer (Only if POLLING PERIOD > 0) ( 그림 7-34) Capabilities polling via anonymous fetch c) CAPABILITY INFO EXPIRY period expired RCS User 1) Polling timer expires CAPABILITY INFO EXPIRY에설정된주기마다 phone address book 에등록된사용자중에 RCS 사용자이나 CAPABILITY INFO EXPIRY 주기가 expired 된연락처에대하여주기적 capability polling 을수행한다. 2) Restart polling timer Provisioning된 polling timer를다음 polling time으로설정한다 Capability values and status Capability values and status 는 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 표준을따른다. 7.6 SPI (Social Presence Information) RCS 클라이언트는 RCS 가입자에대해 VIP Contact 여부와 Location sharing 여부에 따라별도의그룹으로관리한다. VIP Contact 개수는 Provisioning 된정보에서 MAX- 133

141 NUMBER-OF-SUBSCRIPTIONS-IN-PRESENCE-LIST 정보이하로유지할수있고 Location sharing 업데이트주기 Provisioning 정보중 MAX LOCATION UPDATE 로 설정되거나사업자정책에따른다 Support of SPI items SPI 는아래리스트를기본으로하고, 사업자정책에의해추가될수있다. a) Portrait icon b) Favorite link c) Free text d) Timestamp e) Geolocation f) Availability SPI publication RCS client 는 Provisioning 정보에 PRESENCE PROFILE 정보가 1 로설정된경우 SPI publication 을할수있다. SPI publication 을등록하는경우 Capability discovery 의 OPTIONS tag 또는 Capability discovery via presence 의 Service Description 정보에 Social Presence Service 정보를설정한다. < 표 7-7> RCS 서비스 SPI OPTIONS Tag 정보 RCS Service Tag Social presence information +g.3gpp.iari-ref= urn%3aurn-7%3a3gpp-application.ims.iari.rcse.sp < 표 7-8> RCS 서비스 SPI Service-description 정보 RCS Service Service-description Social presence information Service-id: org.3gpp.urn:urn-7:3gpp-applicatin.ims.iari.rcse.sp Version: 1.0 Contact: tel/sip URI 134

142 SPI 는 XCAP 문서 (Permenant PIDF) 로등록하는것을기본으로하고, 사업자정책에 따라 SIP PUBLISH 를통해서 PS 에등록하여관리할수있다. SIP PUBLISH 를이용하는 경우, 사용자의 Registration 여부에따라 SPI 정보제공이달라질수있다. Network A Network B user1@operator A.net RCS AS XDMS_A RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B RCS AS XDMS_B user2@operator B.net 1. XCAP PUT (PIDF person) Unauthorized 3. XCAP PUT (PIDF person) Ceated ( 그림 7-35) SPI Publication a) XCAP PUT PIDF person (user1 RCS AS XDMS_A) xcap-root 정보는 Provisioning 정보중 XCAP Root URI 를설정한다. XCAP 인증정보는 Provisioning 정보중 "XCAP Authentication type 이 Early IMS 이면 X- extened Header 정보를설정하여야한다. XCAP Authentication type 가 Digest 이면 XCAP Authentication user name 와 XCAP Authentication Secret 의 Provisioing 정보에의해 HTTP Digest 인증을수행한다. 1) SPI 정보를구성하기위한 PIDF 정보는 AVAILABLITY AUTHORISATION, FAVORITE LINK CONTOL, FAVORITE LINK URLS, FAVORITE LINK LABEL MAX LENGTH, ICON MAX SIZE, NOTE MAX SIZE, LOCATION TEXT MAX LENGTH, LOCATION VALIDITY 의 Provisioning 정보를기준으로설정한다. PUT HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Intented-Identity: sip:user1@operatora.net Content-Type: application/pidf+xml;charset="utf-8" Content-Length:.. b) 401 Unauthorized (RCS AS XDMS_A user1@operatora.net) 135

143 HTTP/ Unauthorized Server: XDM-proxy/OMA2.0 aggregation-proxy Date: Thu, 10 Aug :50:33 GMT WWW-Authenticate: Digest realm= xcap.operatora.net,nonce= 47364c23432d2e131a5fb210812c,qop-int Content-Length: 0 c) OPTIONS (IBCF_A IBCF_B) PUT HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Intented-Identity: sip:user1@operatora.net Authorization: Digest realm="xcap.rcs.com",nonce="47364c23432d2e131a5fb210812c", username="sip:user1@operatora.net",qop=auth-int,uri="/org.openmobilealliance.xcapdirectory/users/sip:user1@operatora.net/directory.xml", response="2c8ee200cec7f6e966c932a e4", cnonce="dcd99agsfgfsa8b7102dd2f0e8b1", nc= Content-Type: application/pidf+xml;charset="utf-8" Content-Length: 1436 <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns:opd="urn:oma:xml:pde:pidf:ext" xmlns:opd11="urn:oma:xml:pde:pidf:ext:1.1" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps" xmlns:gml=" xmlns:gs=" entity="sip:user1@operatora.net"> <pdm:person id="a1233"> <op:overriding-willingness><op:basic>open</op:basic></op:overriding-willingness> <rpid:status-icon opd:etag="26362"> <opd11:link opd11:label="my blog" opd11:priority="0.8"> <rpid:place-type opd:util=" t21:00:00z"> <rpid:other>herentals, Belgium</rpid:other> 136

144 </rpid:place-type> <rpid:time-offset opd:until=" t21:00:00z">+120</rpid:time-offset> <gp:geopriv> <gp:location-info> <gs:circle srsname="urn:ogc:def:crs:epsg::4326"> <gml:pos> </gml:pos> <gs:radius uom="urn:ogc:def:uom:epsg::9001">10</gs:radius> </gs:circle> </gp:location-info> <gp:usage-rules> <gp:retention-expiry> t21:00:00z</gp:retention-expiry> </gp:usage-rules> </gp:geopriv> <pdm:note>i ll be PAG</pdm:note> </pd:person> </presence> d) 201 Created (RCS AS XDMS_A HTTP/ Created Server: XDM-proxy/OMA2.0 XDMS Date: Thu, 10 Aug :50:33 GMT Etag: B Content-Length: SPI sharing SPI sharing 을위한선행과정 Capability discovery 과정에서 SPI 서비스가가능한사용자간에는 SPI sharing 서비스를요청할수있다. SPI sharing 서비스를이용하기위해서는 XDMS 문서조회와 RLS Subscription 및 presence.winfo Subscription 이선행되어야한다. 137

145 Network A = Presentity A = terminating side Network B = Watcher B = originating side user1@operator A.net RCS AS XDMS_A RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B RCS AS XDMS_B user2@operator B.net 1. XCAP GET directory Unauthorized 3. XCAP GET directory OK 5. XCAP GET resource-lists OK 7. XCAP GET rls-services OK 9. XCAP GET pres-rules OK 11. SUBSCRIBE (rcs eventlist) 12. SUBSCRIBE (rcs eventlist) OK OK 15. NOTIFY (active eventlist) 16. NOTIFY (active eventlist) OK OK 19. SUBSCRIBE (presence.winfo) 20. SUBSCRIBE (presence.winfo) OK OK 24. NOTIFY (active presence.winfo) 23. NOTIFY (active presence.winfo) OK OK ( 그림 7-36) SPI sharing 을위한선행과정 a) XCAP GET directory (user1@operatora.net RCS AS XDMS_A) GET HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Intented-Identity: sip:user1@operatora.net Content-Length: 0401 Unahtorized (RCS AS XDMS_A user1@operatora.net) b) XCAP GET directory (user1@operatora.net RCS AS XDMS_A) HTTP/ OK 138

146 Server: XDM-proxy/OMA2.0 aggregation-proxy Date: Thu, 10 Aug :50:33 GMT Content-Type: application/vnd.oma.xcap-directory+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <xcap-directory xmlns="urn:oma:xml:xdm:xcap-directory"> <folder auid="resource-lists"> <entry etag="e1"/> </folder> <folder auid="rls-services"> <entry etag="e2"/> </folder> <folder auid="org.openmobileaaliance.pres-rules"> <entry etag="e3"/> </folder> <folder auid="pidf-manipulation"/> <!-- SPI publication 에의해 Permernant PIDF 를생성한경우해당정보가표시된다 --> </xcap-directory> c) 200 OK (RCS AS XDMS_A d) XCAP GET resource-lists RCS AS XDMS_A) GET HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: X-3GPP-Asserted-Identity: X-3GPP-Intented-Identity: Authorization: Digest realm="xcap.rcs.com",nonce="47364c23432d2e131a5fb210812c", response="2c8ee200cec7f6e966c932a e4", cnonce="dcd99agsfgfsa8b7102dd2f0e8b1", nc= Content-Length: 0 e) 200 OK (RCS AS XDMS_A user1@operatora.net) HTTP/ OK 139

147 Server: XDM-serv/OMA2.0 XDMS Date: Thu, 10 Aug :50:33 GMT Etag: E1 Content-Type: application/resource-lists+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists" xmlns:xd="urn:oma:xml:xdm:xcap-directory" xmlns:xsi=" <!-- The list oma_buddylist contains references to any individual list used according to OMA IG for presence subscriptions. --> <list name="oma_buddylist"> <external <external </list> <!-- The list rcs_poll_buddylist contains references to individual lists used for RCS non-vip contacts - -> <list name="rcs_poll_buddylist"> <external anchor=" <external anchor=" </list> <!-- The list oma_grantedcontacts contains the list of all granted contacts --> <list name="oma_grantedcontacts"> <external anchor=" <external anchor=" </list> <!-- The list rcs_basic_spi_only_grantedcontacts contains the list of all basic SPI Only granted contacts --> <list name="rcs_basic_spi_only_grantedcontacts"> 140

148 <external <external </list> <!-- The list oma_blockedcontacts contains the list of all blocked contact --> <list name="oma_blockedcontacts"> <external <external </list> <!-- The list of VIP contacts the owner wants to provide all social presence information to. This list also includes the owner s own URI --> <list name="rcs"> <display-name>my presence buddies with location sharing</display-name> <entry uri="sip:user1@operatora.net"/> <!-- tel URI --> </list> <!-- The list of VIP Contacts the owner wants to provide only basic social presence information to --> <list name="rcs_basic_spi_only"> <display-name>my presence buddies without location sharing </display-name> </list> <!-- The list of NON-VIP Contacts the owner wants to provide all social presence information to --> <list name="rcs_poll"> <display-name>my NON-VIP presence contacts with location sharing</display-name> </list> <!-- The list of NON-VIP Contacts the owner wants to provide only basic social presence information to --> <list name="rcs_poll_basic_spi_only"> <display-name>my NON-VIP presence contacts without location sharing</display-name> </list> <!-- The list of blocked contacts --> <list name="rcs_blockedcontacts"> <display-name>my blocke contacts</display-name> 141

149 </list> <!-- The list of revoked contacts --> <list name="rcs_revokedcontacts"> <display-name>my revoked contacts</display-name> </list> <!-- Blackbird NOT USAGE. PNB MANAGEMENT configuration parameter is set to enabled only --> <list name="rcs_pnb_chat_blockedusers"> <display-name>my chat blacklist</display-name> </list> <list name="rcs_pnb_ft_blockedusers"> <display-name>my file transfer blacklist</display-name> </list> <list name="rcs_pnb_standalone_blockedusers"> <display-name>my standalone blacklist</display-name> </list> <list name="rcs_pnb_outchat_blockedusers"> <display-name>my outgoing chat blacklist</display-name> </list> <list name="rcs_pnb_outft_blockedusers"> <display-name>my outgoing file transfer blacklist</display-name> </list> <list name="rcs_pnb_outstandalone_blockedusers"> <display-name>my standalone IM blacklist</display-name> </list> </resource-lists> f) XCAP GET rls-services RCS AS XDMS_A) GET HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: X-3GPP-Asserted-Identity: X-3GPP-Intented-Identity: Authorization: Digest realm="xcap.rcs.com",nonce="47364c23432d2e131a5fb210812c", response="2c8ee200cec7f6e966c932a e4", cnonce="dcd99agsfgfsa8b7102dd2f0e8b1", nc=

150 Content-Length: 0 g) 200 OK (RCS AS XDMS_A user1@operatora.net) HTTP/ OK Server: XDM-serv/OMA2.0 XDMS Date: Thu, 10 Aug :50:33 GMT Etag: E1 Content-Type: application/rls-services+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <rls-services xmlns="urn:ietf:params:xml:ns:rls-services"> <service uri="sip:user1@operatora.net;pres-list=rcs"> <resource-list> <packages><package>presence</package></packages> </service> <service uri="sip:user1@operatora.net;pres-list=rcs_poll"> <resource-list> <packages><package>presence</package></packages> </service> </rls-services> h) XCAP GET pres-rules (user1@operatora.net RCS AS XDMS_A) GET HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Intented-Identity: sip:user1@operatora.net Authorization: Digest realm="xcap.rcs.com",nonce="47364c23432d2e131a5fb210812c", username="sip:user1@operatora.net",qop=auth-int,uri="/org.openmobilealliance.xcapdirectory/users/sip:user1@operatora.net/directory.xml", 143

151 response="2c8ee200cec7f6e966c932a e4", cnonce="dcd99agsfgfsa8b7102dd2f0e8b1", nc= Content-Length: 0 i) 200 OK (RCS AS XDMS_A user1@operatora.net) HTTP/ OK Server: XDM-serv/OMA2.0 XDMS Date: Thu, 10 Aug :50:33 GMT Etag: E1 Content-Type: application/auth-policy+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <cr:ruleset xmlns:ocp="urn:oma:xml:xdm:common-policy" xmlns:op="urn:oma:xml:prs:pres-rules" xmlns:pr="urn:ietf:params:xml:ns:pres-rules" xmlns:cr="urn:ietf:params:xml:ns:common-policy"> <!-- This rule allows allows all service capabilities to be sent for anonymous requests --> <!-- To realize the service capabilities to all requirement --> <!-- This rule replaces the default "wp_prs_block_anonymous" rule --> <!-- NOTE: May be modified to only allow RCS specified services --> <cr:rule id="rcs_allow_services_anonymous"> <cr:conditions><ocp:anonymous-request/></cr:conditions> <cr:actions><pr:sub-handling>allow</pr:sub-handling></cr:actions> <cr:transformations> <pr:provide-services><pr:all-services/></pr:provide-services> <pr:provide-all-attributes/> </cr:transformations> </cr:rule> <cr:rule id="wp_prs_allow_own"> <cr:conditions> <cr:identity/> </cr:conditions> <cr:actions><pr:sub-handling>allow</pr:sub-handling></cr:actions> <cr:transformations> <pr:provide-services><pr:all-servies/></pr:provide-services> <pr:provide-persons><pr:all-persons/></pr:provide-persons> <pr:provide-devices><pr:all-devices/></pr:provide-devices> <pr:provide-all-attributes/> 144

152 </cr:transformations> </cr:rule> <cr:rule id="wp_prs_unlisted"> <cr:conditions><ocp:other-identity/></cr:conditons> <cr:actions><pr:sub-handling>confirm</pr:sub-handling></cr:actions> </cr:rule> <cr:rule id="wp_prs_grantedcontacts"> <cr:conditions> <ocp:external-list> <ocp:entry </ocp:external-list> </cr:conditions> <cr:actions><pr:sub-handling>allow</pr:sub-handling></cr:actions> <cr:transformations> <pr:provide-services><pr:all-servies/></pr:provide-services> <pr:provide-persons><pr:all-persons/></pr:provide-persons> <pr:provide-devices><pr:all-devices/></pr:provide-devices> <pr:provide-all-attributes/> </cr:transformations> </cr:rule> <cr:rule id="rcs_basic_spi_only_grantedcontacts"> <cr:conditions> <ocp:external-list> <ocp:entry </ocp:external-list> </cr:conditions> <cr:actions><pr:sub-handling>allow</pr:sub-handling></cr:actions> <cr:trnasformations> <pr:provide-services><pr:all-servces/></pr:provide-services> <pr:provide-persons><pr:all-persons/></pr:provide-persons> <pr:provide-devices><pr:all-devices/></pr:provide-devices> <pr:provide-note>true</pr:provide-note> <pr:provide-status-icon>true</pr:provie-status-icon> <pr:provide-unknown-attribute ns="urn:oma:xml:pde:pidf:ext:1.1" 145

153 name="link">true</pr:provide-unknown-attribute> <op:provide-willingness>true</op:provide-willingness> <pr:provide-unknown-attribute ns="urn:oma:xml:prs:pidf:oma-pres" name="servicedescription">true</pr:provide-unknown-attribute> </cr:transformations> </cr:rule> <cr:rule id="wp_prs_blockedcontacts"> <cr:conditions> <ocp:external-list> <ocp:entry </ocp:external-list> </cr:conditions> <cr:actions><pr:sub-handling>block</pr:sub-handling></cr:actions> </cr:rule> </cr:ruleset> j) SUBSCRIBE rcs eventlist IMS Core_A) Expires 정보는 Registration 시간과동일하게설정한다. P-Asserted-Identity와 From Header의 display-name에 NICKNAME을포함한다. SPI sharing 요청시착신자로전달되는정보이다. SUBSCRIBE SIP/2.0 Via: SIP/2.0/UDP user1-ip:port;branch=z9hg4bk-1 To: From: Expires: 3600 Call-ID: A Contact: sip:user1-ip:port Max-Forwards: 70 CSeq: 1 SUBSCRIBE Event: presence Supported: eventlist Privacy: none P-Asserted-Identity: "sip:user1@operatora.net-nickname" <sip:user1@operatora.net> Accept: application/rlmi+xml,application/pidf+xml,multipart/related Content-Length: 0 146

154 k) SUBSCRIBE rcs eventlist (IMS Core_A RCS AS PS_A) l) 200 OK (RCS AS PS_A IMS Core_A) m) 200 OK (IMS Core_A n) NOTIFY active eventlist (RCS AS PS_A IMS Core_A) NOTIFY sip:user1-ip:port SIP/2.0 Via: SIP/2.0/UDP ps_ip:port;branch=z9hg4bk-r.s-random From: To: Call-ID: A Contact: <sip:rcs AS PS_A INFO> Max-Forwards: 70 CSeq: 1 NOTIFY SIP-ETag: R Event: presence Require: eventlist Subscription-State: active;expires=3600 Content-Type: multipart/related;type="application/rlmi+xml"; start="<nxyxae@operatora.net>";boundary="50ubfw7lscvltggupe5z" Content-Length: UBfW7LSCVLtggUPe5z Content-Transfer-Encoding: binary Content-ID: <nxyxae@operatora.net> Content-Type: application/rlmi+xml;charset="utf-8" <?xml version="1.0" encoding="utf-8"?> <list xmlns="urn:ietf:params:xml:ns:rmli" uri="sip:user1@operatora.net" version="0" fullstate="true"> <resource uri="sip:user1@operatora.net"> <instance id="hqzsuxtfyq" state="actvie" cid="c1"/> </resource> </list> --50UBfW7LSCVLtggUPe5z Content-Transfer-Encoding: binary Content-ID: <C1> Content-Type: application/pidf+xml;charset="utf-8" 147

155 SPI PIDF --50UBfW7LSCVLtggUPe5z-- o) NOTIFY active eventlist (IMS Core_A p) 200 OK IMS Core_A) q) 200 OK (IMS Core_A RCS AS PS_A) r) SUBSCE presence.winfo IMS Core_A) Expires 정보는 Registration 시간과동일하게설정한다. SUBSCRIBE SIP/2.0 Via: SIP/2.0/UDP user1-ip:port;branch=z9hg4bk-1 To: From: Expires: 3600 Call-ID: B Contact: sip:user1-ip:port Max-Forwards: 70 CSeq: 1 SUBSCRIBE Event: presence.winfo Accept: application/watcherinfo+xml Privacy: none Content-Length: 0 s) SUBSCE presence.winfo (IMS Core_A RCS AS PS_A) t) 200 OK (RCS AS PS_A IMS Core_A) SIP/ OK Via: To: <user1@operatora.net>;tag=2 From: <user1@operatora.net>;tag=1 Expires: 3600 Call-ID: Contact: <sip:rcs AS PS_A INFO> CSeq: 1 SUBSCRIBE Event: presence.winfo Content-Length: 0 u) 200 OK (IMS Core_A user1@operatora.net) 148

156 v) NOTIFY active presence.winfo (RCS AS PS_A IMS Core_A) NOTIFY sip:user1-ip:port SIP/2.0 Via: SIP/2.0/UDP ps-ip:port;branch=z9hg4bk-p.w-random From: To: Call-ID: B Contact: sip:ps-ip:port SIP-ETag: W Max-Forwards: 70 CSeq: 1 NOTIFY Event: presence.winfo Subscription-State: active;expires=3600 Content-Type: application/watcherinfo+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="0" state="full"> <watcher-list resource="sip:user1@operatora.net" package="presence"> <watcher id="1" event="subscribe" status="active">user1@operatora.net</watcher> </watcher-list> </watcherinfo> w) NOTIFY active presence.winfo (IMS Core_A user1@operatora.net) x) 200 OK (user1@operatora.net IMS Core_A) y) 200 OK (IMS Core_A RCS AS PS_A) SPI sharing 요청및수락 SPI sharing 요청은 NOTIFY (presence.winfo) 에의해수락 / 거절을할수있다. 수락 / 거절을하기전에아래의정보를선택할수있어야한다. a) VIP Contact 으로설정할지여부 b) Location sharing 할지여부 149

157 Network A = Presentity A = terminating side Network B = Watcher B = originating side user1@operator A.net RCS AS XDMS_A RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B RCS AS XDMS_B user2@operator B.net 3. NOTIFY (xcap-diff) 1. XCAP PUT resouce-lists Created 5. SUBSCRIBE (presence) OK pending 8. NOTIFY (active presence.winfo) 7. NOTIFY (active presence.winfo) OK 11. XCAP PUT resource-lists Created OK 13. NOTIFY (xcap-diff) OK 15. NOTIFY (presence) OK 18. NOTIFY (active presence.winfo) 17. NOTIFY (active presence.winfo) OK OK Network A = Presentity A = terminating side Network B = Watcher B = originating side user1@operator A.net RCS AS XDMS_A RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B RCS AS XDMS_B user2@operator B.net 21. NOTIFY (active eventlist) 22. NOTIFY (active eventlist) OK OK 25. SUBSCRIBE (presence) OK 27. NOTIFY (presence) OK 29. NOTIFY (active presence.winfo) 30. NOTIFY (active presence.winfo) OK 34. NOTIFY (active eventlist) 33. NOTIFY (active eventlist) OK OK OK ( 그림 ) SPI Sharing 150

158 a) XCAP PUT resource-lists RCS AS XDMS_B) 1) VIP Contact 으로 Location sharing을설정은 resource-lists 의 list name 이 rcs 에 entry를추가한다. 2) VIP Contact 이나, Location을제외한 sharing (Basic SPI) 설정은 resourcelists 의 list name 이 rcs_basic_spi_only 에 entry를추가한다. PUT HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: X-3GPP-Asserted-Identity: X-3GPP-Intented-Identity: Authorization: Digest realm="xcap.operatorb.net",nonce="47364c23432d2e131a5fb210812c", response="2c8ee200cec7f6e966c932a e4", cnonce="dcd99agsfgfsa8b7102dd2f0e8b1", nc= Content-Type: application/xcap-el+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <entry b) 201 Created (RCS AS XDMS_B HTTP/ Created Server: XDM-serv/OMA2.0 XDMS Date: Thu, 10 Aug :50:33 GMT Etag: E1.1 Content-Length: 0 c) NOTIFY xcap-diff (RCS AS XDMS_B RCS AS PS_B) NOTIFY sip:ps-ip:port SIP/2.0 Via: SIP/2.0/UDP ps-ip:port;branch=z9hg4bk-x.s-random SIP-ETag: D From: <sip:subscriptionproxy@operatorb.net>;tag=2 To: <sip:user2@operatorb.net>;tag=1 151

159 Contact: sip:xdms-ip:port Call-ID: D Event: xcap-diff ;diff-processing=aggregate Subscription-State: active;expires= Max-Forwards: 70 CSeq: 3 NOTIFY Content-Type: application/xcap-diff+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <xcap-diff xmlns="urn:ietf:params:xml:ns:xcap-diff" xcap-root=" <document previous-etag="e1" sel="resource-lists/users/sip:user2@operatorb.net/index" newetag="e1.1"> <add sel="resource-lists/list%5b@name=%22rcs%22%5d"> <entry uri="sip:user1@operatora.net"/> </add> </document> </xcap-diff> d) 200 OK (RCS AS PS_B RCS AS XDMS_B) e) SUBSCRIBE presence (RCS AS PS_B IMS Core_B IMS Core_A RCS AS PS_A) 1) Expires 정보는 RLS SUBSCRIBE rcs eventlist 시간과동일하게설정한다. SUBSCRIBE sip:user1@operatora.net SIP/2.0 Via: SIP/2.0/UDP user1-ip:port;branch=z9hg4bk-1 To: <sip:user1@operatora.net> From: "sip:user2@operatorb.net-nickname" <sip:user2@operatorb.net>;tag=1 Expires: 3600 Call-ID: A Contact: sip:user1-ip:port Max-Forwards: 70 CSeq: 1 SUBSCRIBE Event: presence Privacy: none P-Asserted-Identity: "sip:user2@operatorb.net-nickname" <sip:user2@operatorb.net> Accept: application/pidf+xml Content-Length: 0 152

160 f) 202 Pending (RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B) g) NOTIFY active presence.winfo (RCS AS PS_A IMS Core_A) NOTIFY sip:user1-ip:port SIP/2.0 Via: SIP/2.0/UDP ps-ip:port;branch=z9hg4bk-p.w-random From: To: Call-ID: B Contact: sip:ps-ip:port SIP-ETag: W Max-Forwards: 70 CSeq: 2 NOTIFY Event: presence.winfo Subscription-State: active;expires=3000 Content-Type: application/watcherinfo+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="1" state="full"> <watcher-list resource="sip:user1@operatora.net" package="presence"> <watcher id="1" event="subscribe" status="active">sip:user1@operatora.net</watcher> <watcher id="user2" event="subscribe" status="pending">sip:user2@operatorb.net</watcher> </watcher-list> </watcherinfo> h) NOTIFY active presence.winfo (IMS Core_A user1@operatora.net) i) 200 OK (user1@operatora.net IMS Core_A) j) 200 OK (IMS Core_A RCS AS PS_A) k) XCAP PUT resource-lists (user1@operatorb.net RCS AS XDMS_A) 1) VIP Contact 등록과정은 1과동일하다. PUT HTTP/1.1 Host: xdms-ip:port Date: Thu, 10 Aug :50:33 GMT User-Agent:.. X-XCAP-Asserted-Identity: sip:user1@operatora.net X-3GPP-Asserted-Identity: sip:user1@operatora.net 153

161 X-3GPP-Intented-Identity: Authorization: Digest realm="xcap.operatora.net",nonce="47364c23432d2e131a5fb210812c", response="2c8ee200cec7f6e966c932a e4", cnonce="dcd99agsfgfsa8b7102dd2f0e8b1", nc= Content-Type: application/xcap-el+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <entry 201 Created (RCS AS XDMS_A l) NOTIFY xcap-diff (RCS AS XDMS_A RCS AS PS_A) m) 200 OK (RCS AS PS_A RCS AS XDMS_A) n) NOTIFY presence (RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B) 1) Expires 정보는 RLS SUBSCRIBE rcs eventlist 시간과동일하게설정한다. NOTIFY sip:rcs AS PS_B_INFO SIP/2.0 Via: From: To: Call-ID: A Contact: Max-Forwards: 70 CSeq: 1 NOTIFY Event: presence Subscription-State: active;expires=3600 Content-Type: application/pidf+xml;charset= UTF-8 Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns:opd="urn:oma:xml:pde:pidf:ext" xmlns:opd11="urn:oma:xml:pde:pidf:ext:1.1" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps" 154

162 xmlns:gml=" xmlns:gs=" <tuple id="a2"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.3gpp.urn:urn-7:3gpp-servie.ims.icsi.mmtel</op:service-id> <op:version>1.0</op:version> </op:service-description> <caps:servcaps> <caps:audio>true</caps:audio> <caps:duplex><caps:supported><caps:full/></caps:supported></caps:duplex> </caps:servcaps> </tuple> <tuple id="a1"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.3gpp.cs-videotelephony</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <tuple id="a12"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.gsma.videoshare</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <tuple id="a123"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.gsma.videoshare</op:service-id> <op:version>2.0</op:version> </op:service-description> </tuple> 155

163 <tuple id="a132"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.openmobilealliance:im-session</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <tuple id="a133"> <status><basic>open</basic></status> <op:service-description> <op:service-id>org.3gpp.urn:urn-7:3gpp-applicatin.ims.iari.rcse.sp</op:service-id> <op:version>1.0</op:version> </op:service-description> </tuple> <pdm:person id="a1233"> <op:overriding-willingness><op:basic>open</op:basic></op:overriding-willingness> <rpid:status-icon <opd11:link opd11:label="my blog" opd11:priority="0.8"> <rpid:place-type opd:util=" t21:00:00z"> <rpid:other>herentals, Belgium</rpid:other> </rpid:place-type> <rpid:time-offset opd:until=" t21:00:00z">+120</rpid:time-offset> <gp:geopriv> <gp:location-info> <gs:circle srsname="urn:ogc:def:crs:epsg::4326"> <gml:pos> </gml:pos> <gs:radius uom="urn:ogc:def:uom:epsg::9001">10</gs:radius> </gs:circle> </gp:location-info> <gp:usage-rules> <gp:retention-expiry> t21:00:00z</gp:retention-expiry> </gp:usage-rules> </gp:geopriv> <pdm:note>i ll be PAG</pdm:note> </pd:person> 156

164 </presence> rcs_basic_spi_only 로추가하여 Location sharing을설정하지않은경우 <gp:geopriv> 정보를포함하지않는다. o) 200 OK (RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B) p) NOTIFY active presence.winfo (RCS AS PS_A IMS Core_A) NOTIFY sip:user1-ip:port SIP/2.0 Via: SIP/2.0/UDP ps-ip:port;branch=z9hg4bk-p.w-random From: To: Call-ID: B Contact: sip:ps-ip:port SIP-ETag: W Max-Forwards: 70 CSeq: 3 NOTIFY Event: presence.winfo Subscription-State: active;expires=3000 Content-Type: application/watcherinfo+xml;charset="utf-8" Content-Length:.. <?xml version="1.0" encoding="utf-8"?> <watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo" version="2" state="full"> <watcher-list resource="sip:user1@operatora.net" package="presence"> <watcher id="1" event="subscribe" status="active">sip:user1@operatora.net</watcher> <watcher id="user2" event="subscribe" status="active">sip:user2@operatorb.net</watcher> </watcher-list> </watcherinfo> q) NOTIFY active presence.winfo (IMS Core_A user1@operatora.net) r) 200 OK (user1@operatora.net IMS Core_A) s) 200 OK (IMS Core_A RCS AS PS_A) t) NOTIFY active eventlist (RCS AS PS_B IMS Core_B) NOTIFY sip:user1-ip:port SIP/2.0 Via: SIP/2.0/UDP ps_ip:port;branch=z9hg4bk-r.s-random From: <sip:user1@operatora.net;pres-list=rcs>;tag=2 To: "sip:user1@operatora.net-nickname" <sip:user1@operatora.net>;tag=1 Call-ID: A 157

165 Contact: <sip:rcs AS PS_A INFO> Max-Forwards: 70 CSeq: 2 NOTIFY SIP-ETag: R Event: presence Require: eventlist Subscription-State: active;expires=3000 Content-Type: multipart/related;type="application/rlmi+xml"; start="<nxyxae@operatora.net>";boundary="50ubfw7lscvltggupe5z" Content-Length: UBfW7LSCVLtggUPe5z Content-Transfer-Encoding: binary Content-ID: <nxyxae@operatorb.net> Content-Type: application/rlmi+xml;charset="utf-8" <?xml version="1.0" encoding="utf-8"?> <list xmlns="urn:ietf:params:xml:ns:rmli" uri="sip:user2@operatorb.net" version="1" fullstate="false"> <resource uri="sip:user1@operatora.net"> <instance id="hqzsuxtfyq" state="actvie" cid="c1"/> </resource> </list> --50UBfW7LSCVLtggUPe5z Content-Transfer-Encoding: binary Content-ID: <C1> Content-Type: application/pidf+xml;charset="utf-8" SPI PIDF --50UBfW7LSCVLtggUPe5z-- u) NOTIFY active eventlist (IMS Core_B user2@operatorb.net) v) 200 OK (user2@operatorb.net IMS Core_B) w) 200 OK (IMS Core_B RCS AS PS_B) x) SUBSCRIE presence (RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B) 158

166 y) 200 OK (RCS AS PS_B IMS Core_B IMS Core_A RCS AS PS_A) z) NOTIFY presence (RCS AS PS_B IMS Core_B IMS Core_A RCS AS PS_A) aa) 200 OK (RCS AS PS_A IMS Core_A IMS Core_B RCS AS PS_B) bb) NOTIFY presence.winfo (RCS AS PS_B IMS Core_B) cc) NOTIFY presence.winfo (IMS Core_B dd) 200 OK IMS Core_B) ee) 200 OK (IMS Core_B RCS AS PS_B) ff) NOTIFY active eventlist (RCS AS PS_A IMS Core_A) gg) NOTIFY active eventlist (IMS Core_A hh) 200 OK IMS Core_A) ii) 200 OK (IMS Core_A RCS AS PS_A) 7.7 IP Voice Call IP Voice Call 서비스는 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다. 7.8 IP Video Call (IR.94) IP Video Call 서비스는 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다. 7.9 Geo location Services Geolocation 서비스는 GSMA RCS Advanced Communications Services and Client Specification Version 6.0 규격에준한다 Sticker 스티커기능은 Capability Exchange 통해서확인된스티커가능단말끼리 Chat session 을이용하여스티커를전송하는기능이다. 본가이드에서는 UNI 규격을정의하고 NNI 규격은정의하지않는다. 159

167 전송단말은발신하고자하는스티커에대한스티커정보를보내게되고, 수신단말은전달받은스티커정보를이용하여스티커를보여주어야한다. 이때, 스티커가로컬캐쉬에존재하지않는경우스티커서버로부터스티커를다운로드해야한다 Service definition 스티커발신시수신단말이스티커사용가능한지 Capability Exchange 를통해 확인하여야한다. Capability discovery 는 OPTIONS 와 Presence 를모두지원하고 OPTIONS 를위한 feature tag 와 Presence 를위한 XML schema 는다음과같다. < 표 7-9> 스티커서비스를위한 feature tag 및 XML schema Feature tag XML +g.3gpp.iari-ref="urn%3aurn-7%3a3gpp-application.ims.iari.rcs.sticker application/vnd.gsma.rcs-sticker+xml schema Service ID org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcs.sticker Version: 1.0 스티커정보는 Set-id 와 item-id 로구분한다. 움직이는스티커파일의형식은 webp ( 또는 animated gif 를사용한다. 또한다운로드된스티커파일은별도관리되어공개되지않아야한다. 스티커구분자및파일형식은다음과같다. < 표 7-10> 스티커구분자및파일형식 구분형식필수 Stickerset Id: Unique string ( st + 년월일시분초 + 스티커셋이름 사업자 realm ) Y ex) st candycon@skt.co.kr, name nums st wooeng@uplus.co.kr until: String ex) T15:25: Z 만기일자가지난스티커는발신이불가능해야한다. ( 해당파라미터가없는경우만기제약이없이영구적으로사용가능하다 ) String ex) wooeng 스티커 Set 의이름이며발신 UI 구성에이용할수있다 string ex) 10 Y Y 160

168 items ttsset 스티커 set 에포함된 item 개수 id: 해당 set 내 unique 한 item id name: 단말 UI notification bar 또는 snippet 등에서 text 로표현가능한 item 이름이다. url: 다운로드가능한스티커링크주소 ) Thumbnail: 다운로드가능한 thumbnail 링크주소이다. 발신단말은 Thumbnail 을이용하여스티커선택 UI 를구성할수있다. Locale: 지원언어 Ex) ko, en, de Y N ttsname String : 단말에서 TTS 로표현가능한스티커 Set 의이름 N ttsitems Id : 해당 ttsset 내 unique 한 ttsitem id, sticker-set-item-id 와동일 Name: 단말에서 TTS 로표현가능한 Item 이름 N 실제 wooeng 이라는스티커셋의폴더구성과설명에대해서아래와같이나타난다. ( 그림 ) 스티컷셋폴더구성스티커세트는아래제공된메타정보로구성된다. <?xml version="1.0" encoding="utf-8"?> <sticker xmlns="urn:gsma:params:xml:ns:rcs:rcs:sticker"> <set id="st wooeng@uplus.co.kr" until=" t15:25: z"> <name>wooeng</name> <thumbnail> st wooeng@uplus.co.kr&file=st wooeng@ uplus.co.kr&type=png</thumbnail> <nums>3</nums> 161

169 <items> <item id="1" name="hi" url=" &type=gif" thumbnail=" <item id="2" name="dance" url=" 2.dance&type=gif" thumbnail=" <item id="3" name="act_charming" url=" thumbnail=" &type=png"/> </items> <tts> <ttsset locale="ko"> <ttsname> 웽 </ttsname> <ttsitems> <ttsitem id="1" name=" 안녕 "/> <ttsitem id="2" name=" 춤 "/> <ttsitem id="3" name=" 매력 "/> </ttsitems> </ttsset> <ttsset locale="en"> <ttsname>wooeng</ttsname> <ttsitems> <ttsitem id="1" name="hi"/> <ttsitem id="2" name="dance"/> <ttsitem id="3" name="act_charming"/> </ttsitems> </ttsset> <ttsset locale="de"> <ttsname>wooeng</ttsname> <ttsitems > 162

170 <ttsitem id="1" name="hallo"/> <ttsitem id="2" name="tanz"/> <ttsitem id="3" name="charme"/> </ttsitems> </ttsset> </tts> </set> </sticker> 스티커구매 단말은스티커서버에있는스티커를구매과정을통하여신규스티커세트를스티커서버에서다운로드할수있다. 신규스티커구매는스티커스토어에접속하여직접구매하는경우와스티커 Set-id 를이용한간편구매과정을통하여가능하다. 신규스티커구매관련프로토콜은 RCS 외규격사항이므로별도규격을통해논의하기로한다 TTS TTS 를지원하는단말은 tts 메타정보의 ttsname 과 ttsitem 을이용하여지원하도록 한다. tts 메타정보는 locale 을포함하여야하고, 단말의 locale 로 TTS 를지원하여야 한다 스티커전송및수신 발신단말은메타정보중일부정보를발췌하여보내며, 수신단말은수신된메타정보를이용하여스티커를표현해야한다. 수신한단말은해당정보를통해스티커서버에서스티커를다운로드하거나, 로컬캐쉬에저장된스티커이미지를이용하여보여줄수있어야한다. 만기일자를이용하여스티커발신권한을제한하여야한다. 스티커전송시아래의방법을사용한다. a) Session 이존재하지않을경우 1) INVITE SDP 의 a=accept-wrapped-types attribute 에 application/vnd.gsma.rcssticker+xml 을삽입 2) CPIM Content-Type 을 application/vnd.gsma.rcs-sticker+xml 로설정 163

171 3) CPIM Body 는별도로 schema 정의한 XML 을넣어서보냄 b) Session 존재할경우 1) 전제조건 : 단말발신 / 수신이모두 capability exchange에서 sticker 단말일경우, a=accept-wrapped-types 에 application/vnd.gsma.rcs-sticker+xml 으로 Session이맺어진상태 2) MSRP CPIM Content-Type을 application/vnd.gsma.rcs-sticker+xml 로설정 3) CPIM Body는별도로 schema 정의한 XML 을넣어서보냄 content-type: application/vnd.gsma.rcs-sticker+xml <?xml version="1.0" encoding="utf-8"?> <sticker xmlns="urn:gsma:params:xml:ns:rcs:rcs:sticker"> < set id="st wooeng@uplus.co.kr" until=" t15:25: z"> <name>wooeng</name> <thumbnail> st wooeng@uplus.co.kr&file=st wooeng@ uplus.co.kr&type=png </thumbnail> <nums>3</nums> <items> < item id="1" name="hi" url=" down.jsp?folder=st wooeng@uplus.co.kr&file=1.hi&type=gif" thumbnail= " folder=st wooeng@uplus.co.kr&file=1.hi&type=png" /> </items> <tts> <ttsset locale="ko"> <ttsname> 웽 </ttsname> <ttsitems> <ttsitem id="1" name=" 안녕 "/> </ttsitems> </ttsset> <ttsset locale="en"> <ttsname>wooeng</ttsname> <ttsitems> <ttsitem id="1" name="hi"/> </ttsitems> </ttsset> <ttsset locale="de"> 164

172 <ttsname>wooeng</ttsname> <ttsitems > <ttsitem id="1" name="hallo"/> </ttsitems> </ttsset> </tts> </set> </sticker> Sticker 발신단말 Sticker Server ( 스티커저장 ) IM AS Sticker 수신단말 Capability Exchange Via INVITE, MSRP 1. URL 2. Set ID & Item ID Via INVITE, MSRP 1. URL 2. Set ID & Item ID Check Set ID & Item ID If not exit in local Download Sticker with URL info ( 그림 ) 단말의스티커발신및수신 165

173 8 국내 RCS 추가요구사항 (Additional Standard) 8.1 User-Agent 정의 (Define User-Agent) User-Agent = User-Agent HCOLON VoLTE-client-val VoLTE-client-val = "TTA-RCS/1.0" SP device-info SP device-type SP operator device-info = device-model SLASH software-version device-model = 1*16(alphanum / - / _ /. ) software-version = 1*16(alphanum / - / _ /. ) device-type = "Device_Type" SLASH value value = RCS_Android_Phone / RCS_iPhone / RCS_Android_PAD / RCS_iPad / RCS_Tablet_PC operator = "SKT" / "KT" / "LGU" / OMD / token ReliabeMessageMarkUrl : Reliable Message Image download URL 예 ) User-Agent: TTA-RCS/1.0 SHV-E330L/KMR1R Device_Type/ RCS_Android_Phone OMD 8.2 안심문자 (Reliable Message Service) RCS 로전달되는메시지중이동통신사에서인증한메시지에대해표시를해준다. 해당표시는메시지송신자가변조되지않았음을의미하며메시지수신자가안심하고메시지를확인할수있게한다. 해당메시지를송신받은단말은안심문자헤더에포함된 URL 의이미지를다운받아해당메시지와동시에보여주어야한다. 안심마크이미지는최소 60 일저장하고있어야하며, Local 에저장된안심마크이미지를사용할수없는경우안심문자헤더에포함된 URL 의안심마크이미지를재다운로드한다 메시지의구성 RCS 에서안심문자는 CPIM 의헤더에국내규격으로네임스페이스와헤더를추가하여 표시한다. 166

174 안심문자의사용 CPIM 헤더 안심문자를위한 CPIM 헤더는다음과같이정의된다. Content-Type: Message/CPIM NS: Korea-RCS Korea-RCS.ReliableMessageOption: ReliabeMessageMarkUrl MSRP 메시지샘플 MSRP t-7d6ea7df19ef SEND To-Path: msrp:// :19212/ims ims;tcp From-Path: msrp:// :19207/u02_7_0_21299_tp_300;tcp Message-ID: 9b566a985e8c4d68a8a1db2926e498bb Byte-Range: 1-317/317 Content-Type: Message/CPIM From: To: NS: imdn <urn:ietf:params:imdn> imdn.message-id: 9b566a985e8c4d6898a1db2926e498bb DateTime: T01:35:42.762Z imdn.disposition-notification: positive-delivery NS: Korea-RCS Korea-RCS.ReliableMessageOption: Content-type: text/plain;charset=utf-8 Content-length: 9 안심문자샘플입니다 t-7d6ea7df19ef$ INVITE 메시지샘플 INVITE tel:user_b SIP/2.0 Via: SIP/2.0/UDP :1357;branch=z9hG4bKnashds7 Max-Forwards:

175 Route: <sip:pcscf.operatora.net:7531;lr;comp=sigcomp>, P-Preferred-Identity: "user_a" Privacy: none From: tag= To: <tel:user_b> Call-ID: cb03a0s09a2sdfglkj Cseq: 1 INVITE Require: timer Session-Expires: 300;refresher=uac Supported: timer Contact: <sip: :1357>;+g.oma.sip-im; Accept-Contact: :*;+g.oma.sip-im;+g.3gpp.iari-ref="urn%3aurn-7%3a3gppapplication.ims.iari.rcs.fthttp";require;explicit Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE, SUBSCRIBE, NOTIFY Content-Type: multipart/mixed;boundary=++ Content-Length: ( ) --++ Content-Type: application/sdp v=0 o= IN IP s=c=in IP t=0 0 m=message 3402 TCP/TLS/MSRP * a=accept-types:message/cpim application/im-iscomposing+xml a=path:msrps:// :3402/111111;tcp a=accept-wrapped-types: * --++ Content-Type: message/cpim NS: Korea-RCS <mid:korea-rcs@tta.or.kr> Korea-RCS.ReliableMessageOption: From: 대화명 <sip:user_a@operatora.net> To: <tel:user_b> NS: imdn <usn:ietf:params:imdn> 168

176 imdn.message-id: 11 DateTime: T22:19:55Z Imdn.Disposition-Notification: positive-delivery, display Content-Type: application/vnd.gsma.rcs-ft-http+xml Content-Length: 안심문자샘플입니다

177 부속서 A ( 본부속서는표준내용의일부임 ) IMS Registration 동작 (IMS Registration Procedure) A-1.1 APCS 접속요건 a) Power off/on 및비행기모드설정해제시 b) LTE/3G attach 또는 Re-Attach 이후 c) IMS PDN disconnect 후 connection 시 d) WAP PUSH 메시지수신 -> SMS push 수신시 e) DM 서버연동 DM_polling_period(pollingPeriod) 만료시 -> APCS validity period 만료시 f) Registration 시 403(Forbidden) 응답최초수신시 g) 단말의 IP 변경시 h) IM 변경이나 Factory Reset 이발생할경우 A APCS retry 시나리오 Default MO 는사용하지않고단말에서 First APCS 접속실패서규격에따라 xms 로동작한다. 국내는 IM CAP ALWAYS ON 동작으로단말부팅후, APCS 실패시다음부팅전까지 메시지를전혀받을수없는상황이발생할가능성이있으므로필수로구현하여야한다. 170

178 ( 그림 A-1) APCS retry 흐름도 APCS provision retry 수정사항은다음과같다. < 표 A-1> APCS provision retry 수정사항 Pre-condition 기존구현사항수정된국내시나리오 - AC Failed(5xx) - 기존 Provisioning 값이없는경우 - AC Failed(Timeout, Unreachable) - 기존 Provisioning 값이없는경우 - Next boot 때 AC 를다시시도 - Next boot 때 AC 를다시시도 - Next boot 때또는 12 시간이후 AC 다시시도 (Client 는 fallback 동작한다 ) - Next boot 때또는 24 시간이후 AC 다시시도 (Client 는 fallback 동작한다 ) -AC Failed -기존 Provisioning 값이있지만 Validity 가 expired 된경우 - Next boot 때 AC 를다시 시도 - AC Validity 를 24h 를더한 값으로업데이트후 Regi. 를 시도 A-2.2 IMS Registration 동작 기본적인동작은각이동통신사의 IMS 단말기규격에따른다. 본절에서는 RCS 와 관련한 IMS 관련동작에대한사항만기술한다. A Single Registration RCS 기능을지원하는 IMS 단말의 Single Registration 부팅동작절차는다음과같다. ( 그림 A-1) RCS 기능지원단말의 Single Registration 부팅동작절차 171

179 A Dual Registration RCS 기능을지원하는 IMS 단말의 Dual Registration 부팅동작절차는다음과같다 ( 그림 A-3) RCS 기능지원단말의 Dual Registration 부팅동작절차 a) RCS 는 VoLTE Registration 과별도로수행되며, VoLTE Registration 에영향을주어서는안된다. b) P-CSCF 의경우 RCS 는 APCS 값을사용하며, PCO 는이용하지않음 c) APCS 의 SIP Timer value 는 RCS Registration 에대하여독립적으로적용된다. d) RCS Registration 에사용되는 IMPI, IMPU, domain 등의경우 ISIM or USIM 으로부터획득한값 (VoLTE UICC 이동성과동일 ) 을이용한다. 획득불가시 APCS 값을이용한다. A 단말 De-registration 다음의경우단말에서는 De-registration 을해야한다. a) 단말 Power off 및단말재부팅 b) 단말비행기모드설정 c) APCS 접속후 RCS Service 가 disable 된경우 A 단말 RCS Registration 실패처리 단말에서 RCS Registration 이실패하는경우다음과같이처리한다. a) VoLTE(UICC) 와동일하게가져가나, 예외사항추가 172