Femto相关协议UTRANIuh接口RANAPUserAdaptionRUA信令

1、3gpp ts 25.468 v10.0.0 (2011-03)technical specification3rd generation partnership project;technical specification group radio access network;utran iuh interface ranap user adaption (rua) signalling (release 10)the present document has been developed within the 3rd generation partnership project (3gp

2、p tm) and may be further elaborated for the purposes of 3gpp.the present document has not been subject to any approval process by the 3gpp organizational partners and shall not be implemented.this specification is provided for future development work within 3gpp only. the organizational partners acc

3、ept no liability for any use of this specification.specifications and reports for implementation of the 3gpp tm system should be obtained via the 3gpp organizational partners' publications offices.keywordsumts, radio.3gpppostal address3gpp support office address650 route des lucioles - sophia an

4、tipolisvalbonne - francetel.: +33 4 92 94 42 00 fax: +33 4 93 65 47 16internetcopyright notificationno part may be reproduced except as authorized by written permission.the copyright and the foregoing restriction extend to reproduction in all media.© 2011, 3gpp organizational

5、partners (arib, atis, ccsa, etsi, tta, ttc).all rights reserved.umts is a trade mark of etsi registered for the benefit of its members3gpp is a trade mark of etsi registered for the benefit of its members and of the 3gpp organizational partnerslte is a trade mark of etsi currently being registered f

6、or the benefit of its members and of the 3gpp organizational partnersgsm® and the gsm logo are registered and owned by the gsm associationcontentsforeword51scope62references63definitions and abbreviations63.1definitions63.2abbreviations64general74.1procedure specification principles74.2forwards

7、 and backwards compatibility74.3specification notations75rua services86services expected from the transport layer87functions of rua88rua procedures88.1elementary procedures88.2connect88.2.1general88.2.2successful operationhnb originatedhnb-gw originated98.3direct transfer108.3.1gener

8、al108.3.2successful operation (hnb-gw originated)108.3.3successful operation (hnb originated)108.3.4abnormal conditions108.4disconnect108.4.1general108.4.2successful operation (hnb originated)118.4.3successful operation (hnb-gw originated)118.4.4abnormal conditions118.5connectionless transfer118.5.1

9、general118.5.2successful operation (hnb-gw originated)118.5.3successful operation (hnb originated)128.5.4abnormal conditions128.6error indication128.6.1general128.6.2successful operation129elements for rua communication139.1message functional definition and content139.1.1general139.1.2message conten

10、tspresencecriticalityrangeassigned criticality139.1.3connect149.1.4direct transfer149.1.5disconnect149.1.6connectionless transfer149.1.7error indication159.2information element definitions159.2.0general159.2.1message type159.2.2context id169.2.3establishment cause

11、169.2.4intra domain nas node selector169.2.5ranap message189.2.6cn domain indicator189.2.7cause189.2.8criticality diagnostics209.2.9csg membership status219.3message and information element abstract syntax (with asn.1)229.3.0general229.3.1usage of private message mechanism for non-standard use229.3.

12、2elementary procedure definitions229.3.3pdu definitions259.3.4information element definitions299.3.5common definitions339.3.6constant definitions349.3.7container definitions359.4message transfer syntax3810handling of unknown, unforeseen, and erroneous protocol data3910.1general3910.2transfer syntax

13、error3910.3abstract syntax error3910.3.1general3910.3.2criticality information4010.3.3presence information4010.3.4not comprehended ie/ie group4procedure code4atype of message4ies other than the procedure code and type of message4110.3.5missing ie or ie group4210.3.6ies or

14、ie groups received in wrong order or with too many occurrences or erroneously present4310.4logical error4410.5exceptions44annex a (informative):change history45forewordthis technical specification (ts) has been produced by the 3rd generation partnership project (3gpp).the contents of the present doc

15、ument are subject to continuing work within the tsg and may change following formal tsg approval. should the tsg modify the contents of the present document, it will be re-released by the tsg with an identifying change of release date and an increase in version number as follows:version x.y.zwhere:x

16、the first digit:1presented to tsg for information;2presented to tsg for approval;3or greater indicates tsg approved document under change control.ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.zthe third digit is incremented when

17、 editorial only changes have been incorporated in the document.1scopethe present document specifies the ranap user adaption (rua) between the home node b (hnb) and the home node b gateway (hnb-gw). it fulfils the hnb- hnb-gw communication requirements specified in ts 25.467 3 and is defined over the

18、 iuh reference point. it provides transparent transport for ranap messages.2referencesthe following documents contain provisions which, through reference in this text, constitute provisions of the present document.·references are either specific (identified by date of publication, edition numbe

19、r, version number, etc.) or nonspecific.·for a specific reference, subsequent revisions do not apply.·for a non-specific reference, the latest version applies. in the case of a reference to a 3gpp document (including a gsm document), a non-specific reference implicitly refers to the latest

20、 version of that document in the same release as the present document.13gpp ts 25.401: "utran overall description".23gpp ts 25.413: "utran iu interface radio access network application part (ranap) signalling".33gpp ts 25.467: "utran architecture for 3g home nodeb; stage 2&q

21、uot;.43gpp tr 25.921: "guidelines and principles for protocol description and error handling".53gpp tr 21.905: "vocabulary for 3gpp specifications".6itu-t recommendation x.691 (07/2002): "information technology - asn.1 encoding rules: specification of packed encoding rules (

22、per)".7itu-t recommendation x.680 (07/2002): "information technology - abstract syntax notation one (asn.1): specification of basic notation".8itu-t recommendation x.681 (07/2002): "information technology - abstract syntax notation one (asn.1): information object specification&qu

23、ot;.9ietf rfc 4960 (09/2007): "stream control transmission protocol".3definitions and abbreviations3.1definitionsfor the purposes of the present document, the terms and definitions given in tr 21.905 5. a term defined in the present document takes precedence over the definition o

24、f the same term, if any, in tr 21.905 5.ue-associated signalling connection: ue-associated signalling connection is a logical connection between hnb and hnb-gw associated to an iu signalling connection for a particular ue over the single signalling connection between the hnb and hnb-gw, id

25、entified by the identities context id and cn domain id. 3.2abbreviationsfor the purposes of the present document, the following abbreviations apply:cncore networkepelementary procedurehnbhome node bhnb-gwhome node b gatewaypduprotocol data unitruaranap user adaptionsctpstream control transmission pr

26、otocol4generalthe protocol described in the present document is the protocol between hnb-gw and hnb.4.1procedure specification principlesthe principle for specifying the procedure logic is to specify the functional behaviour of the hnb & hnb-gw exactly and completely.the following specification

27、principles have been applied for the procedure text in clause 8:-the procedure text discriminates between:1)functionality which "shall" be executed:-the procedure text indicates that the receiving node "shall" perform a certain function y under a certain condition. if the receivi

28、ng node supports procedure x but cannot perform functionality y requested in the request message of a class 1 ep, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.2)functionality which "shall, if supp

29、orted" be executed:-the procedure text indicates that the receiving node "shall, if supported," perform a certain function y under a certain condition. if the receiving node supports procedure x, but does not support functionality y, the receiving node shall proceed with the execution

30、 of the ep, possibly informing the requesting node about the not supported functionality.-any required inclusion of an optional ie in a response message is explicitly indicated in the procedure text. if the procedure text does not explicitly indicate that an optional ie shall be included in a respon

31、se message, the optional ie shall not be included.4.2forwards and backwards compatibilitythe forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and ies or groups of related ies, include id and criticality fields that are coded in a sta

32、ndard format that will not be changed in the future. these parts can always be decoded regardless of the standard version.4.3specification notationsfor the purposes of the present document, the following notations apply:procedurewhen referring to an elementary procedure in the specification the proc

33、edure name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. hnb registration procedure.messagewhen referring to a message in the specification the message name is written with all letters in upper case characters followed by the

34、 word "message", e.g. connect message.iewhen referring to an information element (ie) in the specification the information element name is written with the first letters in each word in upper case characters and all letters in italic font followed by the abbreviation "ie", e.g. h

35、nb identity ie.value of an iewhen referring to the value of an information element (ie) in the specification the "value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "abstract syntax error (reject)" or "background ".5rua servicesrua p

36、rovides the signalling service between the hnb and the hnb-gw that is required to fulfil the rua functions described in clause 7.6services expected from the transport layerfollowing service is expected from the transport layer:-reliable and in sequence delivery of signalling data using sctp (ietf rf

37、c 4960 9)7functions of ruathe rua has the following functions:-transparent transfer of ranap messages-error handling. this function allows the reporting of general error situations, for which function specific error messages have not been defined.these functions are implemented by one or several rua

38、 elementary procedures described in the following clauses.8rua procedures8.1elementary procedurestable 1 summarizes the eps.table 1; elementary procedureselementary proceduremessageconnectconnectdirect transferdirect transferdisconnectdisconnectconnectionless transferconnectionless transfererror ind

39、icationerror indication8.2connect8.2.1generalthe hnb or hnb-gw can initiate this procedure to establish an ue-associated signalling connection and carry a ranap message.8.2.2successful operationhnb originatedfigure 1: connect to hnb-gw procedurethis procedure is used to carry the first ranap

40、message from the hnb to the hnb-gw. additional information is provided to enable the hnb-gw to handle the ranap message without it being necessary to inspect the contents and trigger the establishment of a new ue-associated signalling connection between hnb and hnb-gw, which is directly mapped to th

41、e iu signalling connection the ranap message refers to. note:the context id is used as the iu signalling connection identifier in the corresponding ranap messages. hnb-gw originatedfigure 1a: connect to hnb procedurethis procedure is used to carry the first ranap message from the hnb-gw to an

42、 hnb for a particular ue, e.g. ranap relocation request. this shall trigger the establishment of a new ue-associated signalling connection between hnb-gw and hnb, which is directly mapped to the iu signalling connection the ranap message refers to.the hnb-gw will allocate the context id. if the firs

43、t ranap message received by the hnb gw is a relocation request message and the relocation request does not contain the csg id of the target cell the rua connect message may contain the csg membership status ie.additional information is provided by the hnb-gw to the hnb to assist the hnb in handling

44、the ranap message.8.3direct transfer8.3.1generalthis procedure is initiated by either the hnb or hnb-gw to transport a ranap message between the two nodes. the hnb-gw can initiate this procedure to establish an ue-associated signalling connection when carrying the second ranap relocation request mes

45、sage.8.3.2successful operation (hnb-gw originated)figure 2: direct transfer to hnbthis procedure is used to carry any dl connection-oriented ranap message defined in ts 25.413 2 from the hnb-gw to the hnb. this procedure can be used to carry the second ranap relocation request message from the hnb-g

46、w to an hnb for a particular ue. this shall trigger the establishment of a second ue-associated signalling connection between hnb-gw and hnb, which is directly mapped to the iu signalling connection the ranap message refers to.8.3.3successful operation (hnb originated)figure 3: direct transfer to hn

47、b-gwthis procedure is used to carry any ul connection-oriented ranap message defined in ts 25.413 2, except those carried in connect or disconnect messages, from the hnb to the hnb-gw. 8.3.4abnormal conditions-8.4disconnect8.4.1generalthis procedure is initiated by either the hnb or the hnb-gw to te

48、rminate an ue-associated signalling connection between these nodes.8.4.2successful operation (hnb originated)figure 4: disconnect to hnb-gwthis procedure is used to carry the last ranap (ts 25.413 2) ul connection-oriented message of a given iu signalling connection to the hnb-gw over the iuh interf

49、ace. this procedure may also be used to indicate error conditions at the hnb. 8.4.3successful operation (hnb-gw originated)figure 5: disconnect to hnbthis procedure is used to close the connection of a given iu signalling connection over the iuh interface. this is initiated by the hnb-gw to handle r

50、elease in connections caused by error conditions. 8.4.4abnormal conditions-8.5connectionless transfer8.5.1generalthis procedure is initiated by either the hnb or the hnb-gw to transfer connectionless ranap messages between the hnb and hnb-gw.8.5.2successful operation (hnb-gw originated)figure 6: con

51、nectionless transfer to hnbthis procedure is used to carry any dl connectionless ranap message defined in ts 25.413 2 from the hnb-gw to the hnb.8.5.3successful operation (hnb originated)figure 7: connectionless transfer to hnb-gwthis procedure is used to carry any ul connectionless ranap message de

52、fined in ts 25.413 2 from the hnb to the hnb-gw.8.5.4abnormal conditions-8.6error indication8.6.1generalthe error indication procedure is initiated by either hnb or hnb-gw to report detected errors in one incoming message.8.6.2successful operationfigure 8 error indication hnb originated, successful

53、operationfigure 9 error indication hnb-gw originated, successful operation9elements for rua communication9.1message functional definition and content9.1.1generalsection 9.1 presents the contents of rua messages in tabular format. the corresponding asn.1 definition is presented in section 9.3. in cas

54、e there is contradiction between the tabular format in section 9.1 and the asn.1 definition, the asn.1 shall take precedence, except for the definition of conditions for the presence of conditional ies, where the tabular format shall take precedence.note:the messages have been defined in accordance

55、to the guidelines specified in tr 25.921 4.for each message there is, a table listing the signalling elements in their order of appearance in the transmitted message.9.1.2message contentspresenceall information elements in the message descriptions below are marked mandatory, optional or condi

56、tional according to table 3table 2: meaning of abbreviations used in rua messagesabbreviationmeaningmie's marked as mandatory (m) will always be included in the message.oie's marked as optional (o) may or may not be included in the message.cie's marked as conditional (c) will be included

57、 in a message only if the condition is satisfied. otherwise the ie is not included.criticalityeach information element or group of information elements may have a criticality information applied to it.following cases are possible.table 3: meaning of content within "criticality" columnabbreviationmeaningno criticality information is applied explicitly.yescri