MSCBSC 移动通信论坛
搜索
登录注册
网络优化工程师招聘专栏 4G/LTE通信工程师最新职位列表 通信实习生/应届生招聘职位

  • 阅读:1605
  • 回复:0
IMS和SIP中SMS
Mr Kang

鎵嬫満鍙风爜宸查獙璇


 发短消息    关注Ta 

C友·铁杆勋章   公益·慈善勋章   C友·贡献勋章   纪念勋章·七周年   财富勋章·万元户   专家·高级勋章   财富勋章·财运连连   财富勋章·小财主   C友·登录达人   财富勋章·富甲一方   纪念勋章·八周年   纪念勋章·九周年   纪念勋章·十周年   纪念勋章·十二周年   C友·技术大神  
积分 104726
帖子 8512
威望 1620287 个
礼品券 11319 个
专家指数 23981
注册 2007-3-13
回答问题数 0
回答被采纳数 0
回答采纳率 0%
 
发表于 2020-10-07 08:58:36  只看楼主 

        "按比特计流量的日子,你还记得吗?---Byte与Bit”已在微信公众号"跟着老康学5G"中推出,敬请关注!


        IMS和SIP中短信(SMS)的传递过程非常简单,终端发送消息即可;是否接收发送报告可由网络或终端选择(发送报告可选)。有关短信(SMS)规范可见3GPP  TS 24.341。在IMS和SIP中SMS的注册及流程如下:


1.终端(短信能力)注册

       3GPP TS 24.341 5.3.2.2规定,终端是否支持通过IP传输(SM-over-IP ),其在注册时标记; 

       RFC 3840中定义了终端通过IMS网络处理的参数,其中,包括:"+g.3gpp.smsip" 


1.1 终端注册示例

REGISTER sip:test.3gpp.com SIP/2.0

Expires: 600000

Authorization: Digest ....

CSeq: 1 REGISTER

Max-Forwards: 70

Route: <sip:[2001:0:0:2::2]:5060;lr>

f: <sip:310410123456789@test.3gpp.com>;tag=1148585218

i: 229717043

k: pathsec-agree

l: 0

m: <sip:310410123456789@[2001:0:0:2::1]:5060>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";+g.3gpp.smsip;+sip.instance="<urn:gsma:imei:35858205-001765-1>"

                                              image.png

t: <sip:310410123456789@test.3gpp.com>

v: SIP/2.0/TCP [2001:0:0:2::1]:5060;branch=z9hG4bK1447958797smg;transport=TCP


2.终端短信发送


2.1 短信发送主要流程

Direction

Message

UA   <-- NW

Request : MESSAGE <URI> | (RP) RP-DATA (Network to   MS)

UA   --> NW

200   OK

UA   --> NW

Request : MESSAGE <URI> | (RP) RP-ACK (MS to   Network)

UA   <-- NW

202   Accepted

2.2 消息内容(MO)

       Request: MESSAGE tel:19037029920;phone-context=TestIMS.com | (RP) RP-DATA (MS to Network)

MESSAGE tel:19037029920;phone-context=TestIMS.com SIP/2.0

f: "Test" <sip:+11234567890@test.3gpp.com>;tag=834037901

t: <tel:19037029920;phone-context=TestIMS.com>

CSeq: 834037887 MESSAGE

i: 834037887_2367153256@2001:0:0:1::1

v: SIP/2.0/UDP [2001:0:0:1::1]:5060;branch=z9hG4bK253093091

Max-Forwards: 70

Route: <sip:[2001:0:0:1::2]:5060;lr>

c: application/vnd.3gpp.sms

Allow: MESSAGE

Request-Disposition: no-fork

User-Agent: Test User Agent

l: 28

 

v: SIP/2.0/UDP [2001:0:0:1::1]:5060;branch=z9hG4bK253093091

Route: <sip:[2001:0:0:1::2]:5060;lr>

c: application/vnd.3gpp.sms

Allow: MESSAGE

Request-Disposition: no-fork

User-Agent: Test User Agent

 

Message Body

GSM A-I/F RP - RP-DATA (MS to Network)

RP-Message Reference

RP-Message Reference: 0x05 (5)

RP-Origination Address

Length: 0

RP-Destination Address - (19037029920)

0... .... = TP-RP: TP Reply Path parameter is not set in this SMS SUBMIT/DELIVER

.0.. .... = TP-UDHI: The TP UD field contains only the short message

..0. .... = TP-SRR: A status report is not requested

...1 0... = TP-VPF: TP-VP field present - relative format (2)

.... .0.. = TP-RD: Instruct SC to accept duplicates

.... ..01 = TP-MTI: SMS-SUBMIT (1) // This is indication of MO-SMS

TP-MR: 88

TP-Destination-Address - (555)

Length: 3 address digits

1... .... :  No extension

.000 .... :  Type of number: (0) Unknown

.... 0001 :  Numbering plan: (1) ISDN/telephone (E.164/E.163)

TP-DA Digits: 555

TP-PID: 0

00.. .... :  defines formatting for subsequent bits

..0. .... :  no telematic interworking, but SME-to-SME protocol

...0 0000 :  the SM-AL protocol being used between the SME and the MS (0)

TP-DCS: 0

00.. .... = Coding Group Bits: General Data Coding indication (0)

Special case, GSM 7 bit default alphabet

TP-Validity-Period: 24 hours 0 minutes

TP-User-Data-Length: (12) depends on Data-Coding-Scheme

TP-User-Data

SMS text: MO SMS Test

 

 短信发送报告:

    Request: MESSAGE sip:+11234567890@test.3gpp.com | (RP) RP-ACK (Network to MS)

MESSAGE sip:+11234567890@test.3gpp.com SIP/2.0

Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bK-b6999e582ee8a42f22e8aafe5f68f47b;rport

Via: SIP/2.0/UDP [2001:0:0:1::2]:60393;branch=z9hG4bK00476613

Max-Forwards: 69

From: <sip:1111@test.3gpp.com>;tag=00476613

To: <sip:+11234567890@test.3gpp.com>

Call-ID: 20131016-151124@[2001:0:0:1::2]:60393

CSeq: 1 MESSAGE

Request-Disposition: fork, parallel

Accept-Contact: *;+g.3gpp.smsip;require;explicit // This indicate that this SIP message is a SMS message

Content-Type: application/vnd.3gpp.sms  // This indicates that the SMS is in 3GPP format (not 3GPP2 format)

In-Reply-To: 834037887_2367153256@2001:0:0:1::1

P-Called-Party-ID: <sip:+11234567890@test.3gpp.com>

Content-Length: 13

Record-Route: <sip:[2001:0:0:1::2];lr>

 

Message Body

GSM A-I/F RP - RP-ACK (Network to MS)

RP-Message Reference

RP-Message Reference: 0x05 (5)

RP-User Data

Element ID: 0x41

Length: 9

TPDU (not displayed)

GSM SMS TPDU (GSM 03.40) SMS-SUBMIT REPORT

.0.. .... = TP-UDHI: The TP UD field contains only the short message

.... ..01 = TP-MTI: SMS-SUBMIT REPORT (1)

TP-Parameter-Indicator

0... .... :  No extension

.000 0... :  Reserved

.... .0.. :  TP-UDL not present

.... ..0. :  TP-DCS not present

.... ...0 :  TP-PID not present

TP-Service-Centre-Time-Stamp

Year 33, Month 13, Day 03

Hour 13, Minutes 63, Seconds 13

Timezone: GMT + 13 hours 15 minutes

2.3终端短信成功发送流程图


 

image.png


3.终端短信接收流程


3.1终端短信接收主要流程


           根据TS 34.229 18.2终端通过IMS网络接收短信的主要流程如下:

Direction

Message

UA   <-- NW

Request : MESSAGE <URI> | (RP) RP-DATA (Network to   MS)

UA   --> NW

200   OK

UA   --> NW

Request : MESSAGE <URI> | (RP) RP-ACK (MS to   Network)

UA   <-- NW

202   Accepted

3.2 消息内容(MT)

    Request: MESSAGE sip:+11234567890@test.3gpp.com | (RP) RP-DATA (Network to MS)

MESSAGE sip:+11234567890@test.3gpp.com SIP/2.0

Via: SIP/2.0/UDP [2001:0:0:1::2]:5060;branch=z9hG4bK-ad54683f54403f46ff8d8b553521e588;rport

Via: SIP/2.0/UDP [2001:0:0:1::2]:60393;branch=z9hG4bK0047D4EC

Max-Forwards: 69

From: <sip:1111@test.3gpp.com>;tag=0047D4EC

To: <sip:+11234567890@test.3gpp.com>

Call-ID: 20131016-151152@[2001:0:0:1::2]:60393

CSeq: 1 MESSAGE

Request-Disposition: no-fork

Accept-Contact: *;+g.3gpp.smsip;require;explicit // This indicate that this SIP message is a SMS message

Content-Type: application/vnd.3gpp.sms // This indicates that the SMS is in 3GPP format (not 3GPP2 format)

Content-Transfer-Encoding: binary

P-Called-Party-ID: <sip:+11234567890@test.3gpp.com>

Content-Length: 41

Record-Route: <sip:[2001:0:0:1::2];lr>

 

Message Body

GSM A-I/F RP - RP-DATA (Network to MS)

RP-Message Reference

RP-Origination Address - (999999)

Length: 4

1... .... = Extension: No Extension

.000 .... = Type of number: unknown (0x00)

.... 0001 = Numbering plan identification: ISDN/Telephony Numbering (Rec ITU-T E.164) (0x01)

BCD Digits: 999999

RP-Destination Address

RP-User Data

 

GSM SMS TPDU (GSM 03.40) SMS-DELIVER

0... .... = TP-RP: TP Reply Path parameter is not set in this SMS SUBMIT/DELIVER

.0.. .... = TP-UDHI: The TP UD field contains only the short message

..0. .... = TP-SRI: A status report shall not be returned to the SME

.... .1.. = TP-MMS: No more messages are waiting for the MS in this SC

.... ..00 = TP-MTI: SMS-DELIVER (0) // This is indication of MT-SMS

TP-Originating-Address - (1234567890)

Length: 10 address digits

1... .... :  No extension

.000 .... :  Type of number: (0) Unknown

.... 0001 :  Numbering plan: (1) ISDN/telephone (E.164/E.163)

TP-OA Digits: 1234567890

TP-PID: 0

00.. .... :  defines formatting for subsequent bits

..0. .... :  no telematic interworking, but SME-to-SME protocol

...0 0000 :  the SM-AL protocol being used between the SME and the MS (0)

TP-DCS: 0

00.. .... = Coding Group Bits: General Data Coding indication (0)

Special case, GSM 7 bit default alphabet

TP-Service-Centre-Time-Stamp

Year 13, Month 10, Day 16

Hour 15, Minutes 11, Seconds 29

Timezone: GMT + 5 hours 0 minutes

TP-User-Data

SMS text: this is a mt sms test message

 终端发送接收回持:

    Request: MESSAGE sip:1111@test.3gpp.com;phone-context=TestIMS.com | (RP) RP-ACK (MS to Network)

MESSAGE sip:1111@test.3gpp.com;phone-context=TestIMS.com SIP/2.0

f: "Test" <sip:+11234567890@test.3gpp.com>;tag=834066458

t: <sip:1111@test.3gpp.com;phone-context=TestIMS.com>

CSeq: 834066445 MESSAGE

i: 834066446_2367161720@2001:0:0:1::1

v: SIP/2.0/UDP [2001:0:0:1::1]:5060;branch=z9hG4bK502862226

Max-Forwards: 70

Route: <sip:[2001:0:0:1::2]:5060;lr>

c: application/vnd.3gpp.sms

Allow: MESSAGE

Request-Disposition: no-fork

User-Agent: Test User Agent

l: 6

 

Message Body

GSM A-I/F RP - RP-ACK (MS to Network)

RP-Message Reference

RP-Message Reference: 0x00 (0)

RP-User Data

Element ID: 0x41

Length: 2

TPDU (not displayed)

GSM SMS TPDU (GSM 03.40) SMS-DELIVER REPORT

.0.. .... = TP-UDHI: The TP UD field contains only the short message

.... .0.. = TP-MMS: More messages are waiting for the MS in this SC

.... ..00 = TP-MTI: SMS-DELIVER REPORT (0)

TP-Parameter-Indicator

0... .... :  No extension

.000 0... :  Reserved

.... .0.. :  TP-UDL not present

.... ..0. :  TP-DCS not present

.... ...0 :  TP-PID not present


3.3 终端通过IMS成功接收短信流程图

          TS. 24.341 B.6终端成功接收短信流程如下图:

image.png


原文来自:http://www.sharetechnote.com

整理:kangguoying20201007

扫码关注5G通信官方公众号,免费领取以下5G精品资料
  • 1、回复“ZGDX”免费领取《中国电信5G NTN技术白皮书
  • 2、回复“TXSB”免费领取《通信设备安装工程施工工艺图解
  • 3、回复“YDSL”免费领取《中国移动算力并网白皮书
  • 4、回复“5GX3”免费领取《 R16 23501-g60 5G的系统架构1
  • 5、回复“iot6”免费领取《【8月30号登载】物联网创新技术与产业应用蓝皮书——物联网感知技术及系统应用
  • 6、回复“6G31”免费领取《基于云网融合的6G关键技术白皮书
  • 7、回复“IM6G”免费领取《6G典型场景和关键能力白皮书
  • 8、回复“SPN2”免费领取《中国移动SPN2.0技术白皮书
  • 对本帖内容的看法? 我要点评

     

    快速回复主题    
    标题
    内容
     上传资料请点左侧【添加附件】

    当前时区 GMT+8, 现在时间是 2024-04-19 08:27:20
    渝ICP备11001752号  Copyright @ 2006-2016 mscbsc.com  本站统一服务邮箱:mscbsc@163.com

    Processed in 0.334295 second(s), 14 queries , Gzip enabled
    TOP
    清除 Cookies - 联系我们 - 移动通信网 - 移动通信论坛 - 通信招聘网 - Archiver