欢迎来到麦多课文档分享! | 帮助中心 海量文档,免费浏览,给你所需,享你所想!
麦多课文档分享
全部分类
  • 标准规范>
  • 教学课件>
  • 考试资料>
  • 办公文档>
  • 学术论文>
  • 行业资料>
  • 易语言源码>
  • ImageVerifierCode 换一换
    首页 麦多课文档分享 > 资源分类 > PDF文档下载
    分享到微信 分享到微博 分享到QQ空间

    ANSI TIA-41.371-E-2012 Mobile Application Part (MAP) - Broadcast Teleservice Transport Capability《移动应用部分(MAP).广播用户终端业务传输能力》.pdf

    • 资源ID:438477       资源大小:3.61MB        全文页数:24页
    • 资源格式: PDF        下载积分:10000积分
    快捷下载 游客一键下载
    账号登录下载
    微信登录下载
    二维码
    微信扫一扫登录
    下载资源需要10000积分(如需开发票,请勿充值!)
    邮箱/手机:
    温馨提示:
    如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
    如需开发票,请勿充值!如填写123,账号就是123,密码也是123。
    支付方式: 支付宝扫码支付    微信扫码支付   
    验证码:   换一换

    加入VIP,交流精品资源
     
    账号:
    密码:
    验证码:   换一换
      忘记密码?
        
    友情提示
    2、PDF文件下载后,可能会被浏览器默认打开,此种情况可以点击浏览器菜单,保存网页到桌面,就可以正常下载了。
    3、本站不支持迅雷下载,请使用电脑自带的IE浏览器,或者360浏览器、谷歌浏览器下载即可。
    4、本站资源下载后的文档和图纸-无水印,预览文档经过压缩,下载后原文更清晰。
    5、试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。

    ANSI TIA-41.371-E-2012 Mobile Application Part (MAP) - Broadcast Teleservice Transport Capability《移动应用部分(MAP).广播用户终端业务传输能力》.pdf

    1、 TIA-41.371-E August 2012Mobile Application Part (MAP) - Broadcast Teleservice Transport Capability ANSI/TIA-41.371-E-2012 APPROVED: AUGUST 8, 2012 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers

    2、and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-me

    3、mber of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA

    4、in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety p

    5、roblems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. SP-3-3590.371-RV5-A, fo

    6、rmulated under the cognizance of the TIA TR-45 Mobile and Personal Communications Systems Standards, TR-45.8 Subcommittee on Core Networks- Mobile and Personal Communications Standards). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Ar

    7、lington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/standards/catalog/ All rights re

    8、served Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please co

    9、ntact the TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright or Telecommunications Industry Association Technology (b) there is no assurance that the Docu

    10、ment will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property ri

    11、ghts (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requ

    12、ested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the p

    13、arties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If th

    14、e Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of ma

    15、ndatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encourageme

    16、nt of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential

    17、 Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES,

    18、 EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESS

    19、LY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUME

    20、NT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDIN

    21、G DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL EL

    22、EMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. REVISION HISTORYRevision Date RemarksX.S0004-371-E v1.0 April 2008 Initial publication.X.S0004-371-E v1.01234567891011121314151617181920212223242526272829303132333435363738394041424344

    23、45464748495051525354555657585960371-1PART 3711 Broadcast Teleservice Transport Capability1.1 Successful Broadcast of Teleservice Messages: MSC-based Periodicity ControlThis scenario describes the transfer of a message to several MSCs, and its successful delivery to MS-based SMEs via their respective

    24、 Serving MSCs. Since periodicity is controlled and supported by theServing MSCs, they shall need to store the broadcast teleservice payload and other associatedattributes for the duration of the broadcast.X.S0004-371-E v1.012345678910111213141516171819202122232425262728293031323334353637383940414243

    25、4445464748495051525354555657585960371-2a. The MC receives and accepts an SMDPP requesting broadcast of a teleservice message to MS-based SMEs. The SMDPP includes the following parameters:Figure 1 Successful Broadcast of Teleservice Messages: MSC-based Periodicity ControlParameters Usage TypeSMS_Bear

    26、erData Any desired message. RSMS_OriginalOriginating-AddressNetwork address of the originating SME; e.g., A.RaSMS_TeleserviceIdentifier If a value is present, it identifies the teleservice used for interpreting the bearer data.MBCbSMS_BTTI:BroadcastCategory Indicates that this is a BTTC message and

    27、provides a specific subject matter of the Teleservice payload (e.g., emergency, system operator announcement, advertise-ment, sports) to be broadcast.RSMTOriginatorMSC-n MSC-2 MSC-1 SMEabcdefghiSMTsmdpp ACKMCDestination Serving SystemsEach with its own Broadcast ZoneOriginatingSystemsAMS-SMEsin MSCs

    28、1, 2, nBsmdpp SMTsmdpp SMDPP SMS_BearerData, SMS_OriginalOriginatingAddress, SMS_TeleserviceIdentifier, SMS_BTTISMTsmdpp SMDPP SMS_BearerData, SMS_OriginalOriginatingAddress, SMS_TeleserviceIdentifier, SMS_BTTISMDPP SMS_BearerData, SMS_OriginalOriginatingAddress, SMS_TeleserviceIdentifier, SMS_BTTIS

    29、MDPP SMS_BearerData, SMS_OriginalOriginatingAddress, SMS_TeleserviceIdentifier, SMS_BTTISMD-REQsRepeat as per specified broadcast periodicityjSMD-REQskX.S0004-371-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960371-3b. . and respon

    30、ds with an smdpp positive acknowledgment (which may include anSMS_BearerData parameter if there is bearer data to return).c, e, g. The MC sends an SMDPP to the various MSCs (MSC-1, MSC-2, . MSC-n), that are part of the prescribed broadcast domain. The MC includes the parameters in Step-a with the ex

    31、ception that the MC remaps the following parameters:BroadcastCategory-SpecificInformationIndicates relevant data pertaining to this broadcast mes-sage, for a specific broadcast category (e.g., Indication of preferred language).OBroadcastMessage-IdentifierUniquely identifies the broadcast message ove

    32、r the net-work originating from a particular SME (i.e., unique on a per-SME basis).RaBroadcastMessageStatus Indicates whether the broadcast message is new, or a replacement of an existing message with the same iden-tification.OBroadcastMessage-PriorityIndicates the priority of broadcast for the Tele

    33、service payload.OBroadcastPeriodicity Indicates the recommended start time, duration, and rep-etition rate of the broadcast (e.g., start time: 0900 hours, duration: 2 hours and repetition rate: every 5 minutes).RBroadcastServiceGroup Identifies the broadcast target mobile station audience (e.g., Tar

    34、get Service Group).OBroadcastZoneIdentifiercIndicates the requested geographical area over which the message should be broadcast (e.g., cells, sectors or both within an MSC, or whole MSC; absence of both this parameter and BroadcastZoneIdentifierList indicates all MSCs within the broadcast domain of

    35、 MC).OBroadcastZone-IdentifierListcIndicates a requested list of geographical areas over which the message should be broadcast (e.g., cells, sec-tors or both within an MSC, or whole MSC; absence of both this parameter and BroadcastZoneIdentifier indi-cates all MSCs within the broadcast domain of MC)

    36、.OPreferredLanguage-IndicatorIndicates the language in which the broadcast message payload is written (e.g., Franais, English).OdNotes:a. Inclusion of both parameters ensures the uniqueness of the broadcast message.b. This parameter is a TCAP mandatory parameter of SMDPP and is required for TDMA.c.

    37、The parameters, BroadcastZoneIdentifier and BroadcastZoneIdentifierList, are mutu-ally exclusive.d. Applicable for CDMA. For CDMA, the MC re-encodes the PreferredLanguage-Indicator from the value specified in Part 550, Section 2.180 for the language in useto the value used by the MS for the language

    38、 in use (i.e., to the value specified inTSB58).Parameters Usage TypeSMS_BTTI:PreferredLanguage-IndicatorIndication of the language in which the broadcast mes-sage payload is written (e.g., Franais, English).OaParameters Usage TypeX.S0004-371-E v1.01234567891011121314151617181920212223242526272829303

    39、13233343536373839404142434445464748495051525354555657585960371-4d, f, h. Upon reception of an SMDPP, each MSC responds with an empty smdpp positive acknowl-edgment.i. The MSCs process the received BTTI parameters to determine the broadcasting characteristics (e.g., priority and zone). The MSCs (via

    40、the selected cell or sectors) broadcast the SMD-REQUEST for reception by all active destination MS-based SMEs. The MSCs include the following information (as appropriate based on the air interface specification):BroadcastZoneIdentifierbIndicates the MC remapped geographical areas over which the mess

    41、age should be broadcast (e.g., cells, sec-tors or both within an MSC, or whole MSC; absence of both this parameter and BroadcastZoneIdentifierList, indicates whole MSC).OBroadcastZone-IdentifierListbIndicates a list of MC remapped geographical areas over which the message should be broadcast (e.g.,

    42、cells, sec-tors or both within an MSC, or whole MSC; absence of both this parameter and BroadcastZoneIdentifier, indi-cates whole MSC).ONotes:a. Applicable for CDMA. For CDMA, the MC re-encodes the PreferredLanguage-Indicator from the value specified in Part 550, Section 2.180 for the language in us

    43、eto the value used by the MS for the language in use (i.e., to the value specified inTSB58).b. The parameters, BroadcastZoneIdentifier and BroadcastZoneIdentifierList, are mutu-ally exclusive.Parameters Usage TypeSMS_BearerData Any desired message. RSMS_OriginalOriginating-AddressNetwork address of

    44、the originating SME; i.e., A.OaNotes:a. At time of publication, this was only applicable for TDMA.SMS_TeleserviceIdentifier Identification of the teleservice; used for interpreting the bearer data.OSMS_BTTIBroadcastCategory Indicates the specific subject matter of the Teleservice payload (e.g., emer

    45、gency system operator announce-ment, advertisement, sports) to be broadcast.RBroadcastCategory-SpecificInformationIndicates relevant data pertaining to this broadcast mes-sage, for a specific broadcast category (e.g., Indication of preferred language).OBroadcastLanguage-Indicatorbb. Encoding as per

    46、the received PreferredLanguageIndicator parameter.Indicates the language in which the broadcast message payload is written (e.g., Franais, English).Occ. Applicable for CDMA.BroadcastMessage-IdentifierIdentifies the broadcast message. Parameter may be remapped by Serving MSC.RBroadcastServiceGroup Id

    47、entifies the broadcast target mobile station audience (e.g., Target Service Group).OParameters Usage TypeX.S0004-371-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960371-5j-k. The MSC repeats Step-i, in accordance with the prescribe

    48、d broadcast periodicity.X.S0004-371-E v1.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960371-61.2 Successful Cancellation of Broadcast of Teleservice Messages: MSC-based Periodicity ControlThis scenario describes the deletion of a previ

    49、ously received teleservice message by their respectiveServing MSCs within the indicated geographical area. a. The MC receives and accepts an SMDPP requesting cancellation of a periodic SMS message toan MS-based SME.Figure 2 Successful Cancellation of Broadcast of Teleservice Messages: MSC-based Periodicity ControlParameters Usage TypeSMS_BearerData Any desired message.MBCaSMS_OriginalOriginating-AddressNetwork address of the originating SME; e.g., A.RbSMS_TeleserviceIdentifiercIf a value is present, it identifies the telese


    注意事项

    本文(ANSI TIA-41.371-E-2012 Mobile Application Part (MAP) - Broadcast Teleservice Transport Capability《移动应用部分(MAP).广播用户终端业务传输能力》.pdf)为本站会员(proposalcash356)主动上传,麦多课文档分享仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文档分享(点击联系客服),我们立即给予删除!




    关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

    copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
    备案/许可证编号:苏ICP备17064731号-1 

    收起
    展开