IMS系統(tǒng)中的SIP消息

IMS系統(tǒng)中的SIP消息\o"5G"#5G\o"4G"#4G\o"VOLTE"#VOLTE\o"IMS"#IMSIMS(IPMultimediaSubsystem)系統(tǒng)中除與會(huì)話相關(guān)的SIP(SessionInitiationProtocol）協(xié)議外,還有SigComp、RTP、RTCP、IPSec和Diameter協(xié)議。這些協(xié)議都非常重要，它們會(huì)影響UE或直接影響UE的工作。在VoLTE呼叫中SIP協(xié)議用于會(huì)話的創(chuàng)建,修改和終止；負(fù)責(zé)兩個(gè)用戶之間會(huì)話的協(xié)商。SIP不執(zhí)行由RTP&RTCP完成的傳輸層(數(shù)據(jù)傳遞）。SIP是按(順)序交互的協(xié)議,其功能和格式上類(lèi)似于HTTP的請(qǐng)求和響應(yīng)。每個(gè)SIP請(qǐng)求中都以包含請(qǐng)求類(lèi)型的起始行開(kāi)頭。SIP中所有消息列表如下：SIPMethodDescriptionReferenceINVITEINVITEindicatesthataclientisbeing

invitedtoparticipateinacallsessionRFC3261ACKACKConfirmsthattheclienthasreceiveda

finalresponsetoanINVITErequestRFC3261BYETerminatesacall;Itcanbesentbyeither

thecallerorthecalledpartyRFC3261CANCELCancelsanypendingrequestRFC3261OPTIONSItQueriesthecapabilitiesofserversRFC3261PRACKProvisionalacknowledgementRFC3262SUBSCRIBESubscribestoeventnotificationRFC3265NOTIFYNotifiesthesubscriberofanewEventRFC3265PUBLISHPublishesaneventtotheServerRFC3903INFOSendsmid-sessioninformationthatdoesnot

modifythesessionstateRFC6086REFERAsksrecipienttoissueaSIPrequest(call

transfer)RFC3515MESSAGETransportsinstantmessagesusingSIPRFC3428UPDATEModifiesthestateofasessionwithout

changingthestateofthedialogRFC3311SIP消息代碼SIP消息響應(yīng)主要負(fù)責(zé)對(duì)Internet號(hào)碼分配機(jī)構(gòu)(IANA)的SIP(會(huì)話初始協(xié)議）參數(shù)的維護(hù),它們?nèi)恳皂憫?yīng)代碼開(kāi)頭,共分為以下六類(lèi)：1XX(信息/臨時(shí))代碼:表示接收和處理的請(qǐng)求;如.100用于嘗試,180用于響鈴；2xx(成功操作)代碼:表示成功接收,理解并接受了該操作;如200OK,202接受;3XX(重定向代碼):需要采取進(jìn)一步操作（通常由發(fā)送者執(zhí)行）以完成請(qǐng)求,如一直移動(dòng)301,臨時(shí)移動(dòng)302;4XX(客戶端故障代碼):請(qǐng)求中包含語(yǔ)法錯(cuò)誤或無(wú)法在服務(wù)器上實(shí)現(xiàn),如401未經(jīng)授權(quán)，403禁止;5XX(編碼器錯(cuò)誤):服務(wù)器無(wú)法完成有效的請(qǐng)求,如500服務(wù)器內(nèi)部錯(cuò)誤,504服務(wù)器超時(shí)；6XX(全網(wǎng)故障)：該請(qǐng)求無(wú)法在任何服務(wù)器上完成,如600全忙，604無(wú)法疏通；100系列消息代碼SIPMessageCodeDescriptionReference100Trying180Ringing181CallIsBeing

Forwarded182Queued183SessionProgress199EarlyDialog

TerminatedRFC6228200系列消息代碼

SIP

MessageCodeDescriptionReference200

OK202

AcceptedRFC3265204

No

NotificationRFC5839300系列消息代碼SIPMessageCodeDescriptionReference300MultipleChoices301Moved

Permanently302Moved

Temporarily305UseProxy380Alternative

Service400系列消息代碼SIPMessageCodeDescriptionReference400BadRequest401Unauthorized402PaymentRequired403Forbidden404NotFound405MethodNot

Allowed406NotAcceptable407Proxy

AuthenticationRequired408RequestTimeout410Gone412Conditional

RequestFailedRFC3903413RequestEntity

TooLarge414Request-URIToo

Long415Unsupported

MediaType416UnsupportedURI

Scheme417Unknown

Resource-PriorityRFC4412420BadExtension421Extension

Required422SessionInterval

TooSmallRFC4028423IntervalToo

Brief424BadLocation

InformationRFC6442428UseIdentity

HeaderRFC4474429ProvideReferrer

IdentityRFC3892430FlowFailedRFC5626433Anonymity

DisallowedRFC5079436Bad

Identity-InfoRFC4474437UnsupportedCertificateRFC4474438InvalidIdentity

HeaderRFC4474439FirstHopLacks

OutboundSupportRFC5626440Max-Breadth

ExceededRFC5393469BadInfoPackageRFC6086470ConsentNeededRFC5360480Temporarily

Unavailable481Call/Transaction

DoesNotExist482LoopDetected483TooManyHops484Address

Incomplete485Ambiguous486BusyHere487Request

Terminated488NotAcceptable

Here489BadEventRFC3265491RequestPending493Undecipherable494Security

AgreementRequiredRFC3329500系列消息代碼SIPMessageCodeDescriptionReference500ServerInternal

Error501NotImplemented502BadGateway503Service

Unavailab