WO2008128461A1 - Method of responding deltepersonalityrequest message in ultra mobile broadband - Google Patents

Method of responding deltepersonalityrequest message in ultra mobile broadband Download PDF

Info

Publication number
WO2008128461A1
WO2008128461A1 PCT/CN2008/070708 CN2008070708W WO2008128461A1 WO 2008128461 A1 WO2008128461 A1 WO 2008128461A1 CN 2008070708 W CN2008070708 W CN 2008070708W WO 2008128461 A1 WO2008128461 A1 WO 2008128461A1
Authority
WO
WIPO (PCT)
Prior art keywords
delete
access terminal
message
feature
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2008/070708
Other languages
English (en)
French (fr)
Inventor
Xiaowu Zhao
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to US12/596,123 priority Critical patent/US20100128674A1/en
Publication of WO2008128461A1 publication Critical patent/WO2008128461A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier

Definitions

  • the present invention relates to ultra mobile broadband technology, and more particularly to a method for responding to "delivery attribute request message" in ultra mobile broadband technology.
  • UMB Ultra Mobile Broadband
  • CDMA2000 Code Division Multiple Access
  • UMB's air interface technology can greatly enhance the performance of communication networks based on CDMA2000 access technology, laying the foundation for users to provide more and higher requirements for wireless multimedia services.
  • each eBS evolved BS, evolved technology base station
  • AT in the active set of AT (Access Terminal) have their own design ideas of the protocol stack.
  • Each eBS in the active set has a set of negotiated features ( Personality ).
  • Each eBS and AT independently decides what kind of personality (Personality) is used between the protocol stacks between them.
  • a property (Personality) is defined as a complete set of negotiated protocol subtypes, application subtypes, attribute values, non-attribute data values, and public data (all of which can be used as a practical example of a protocol or application). Many characteristics (Personality) are represented by different indices.
  • the activation set includes three evolutionary technology base stations supporting UMB, which are represented by eBS1, eBS2, and eBS3, respectively.
  • Each session information (Session Info) of the eBS includes personality A, personality B, and personality. C, personality D and other personality index (Index).
  • the SessionSignature X indicates the session signature X, and after the AT negotiates with the eBS1, it indicates that the personality A of the eBS1 is the protocol or the application instance in use, and after the AT negotiates with the eBS2 and the eBS3, respectively, the respective personality C is in the protocol being used or Applications.
  • the management of the characteristics (Personality) is very important, it determines the effective protocol stack that the AT can negotiate with each eBS.
  • the following related messages are defined to involve the deletion of Personality:
  • the message is that the access network (ie eBS or AN) requires the AT to delete one or more characteristics (Personality). Its format is shown in Table 1:
  • the access network is set to 0x0d.
  • Transaction ID This value is incremented each time the access network sends a Delete Property Request message.
  • the access network sets this field to the number of occurrences of the Personality index in this message.
  • the access network sets the domain to the corresponding personality (Personality) that you want to delete.
  • the access network will be set in the order of priority deletion.
  • This field is currently set to 0 to ensure that the length of the entire message is an integer multiple of the octet. You can also set the number of digits according to your specific needs.
  • Deletement (Personality) Accept (DeletePersonalityAccept) message This message is an access terminal that displays the feature (Personality) to be deleted to the access network. Its format is shown in Table 2:
  • the access terminal is set to OxOe.
  • Transaction ID The access terminal sets this field value to the corresponding value of the corresponding message for the corresponding Personality request.
  • the access terminal sets the domain to the corresponding deleted personality ( Personality ).
  • Reserved bits This field is currently set to 0 to ensure that the length of the entire message is an integer multiple of the 8-bit group, and the number of bits can be set according to specific needs.
  • Deletement (Personality) Reject (DeletePersonalityReject) message This message is used by the access terminal to reject the request to delete the Personality requested by the access network.
  • the format is as shown in Table 3:
  • the access network is set to OxOf.
  • Transaction ID The access terminal sets this field value to the corresponding value corresponding to the rejected Personality request message.
  • the access terminal sets this field, where the information indicates the reason why the DeletePersonalityRequest message is rejected.
  • Reserved bits This field is currently set to 0 to ensure that the length of the entire message is an integer multiple of the 8-bit group, and the number of bits can be set according to specific needs.
  • the Personality acceptance message includes only one feature that can accept the deletion (Personality).
  • the deletion property (Personality) request message shown in Table 1 it is possible to carry a plurality of characteristics (Personality) that are desired to be deleted. Therefore, the access terminal accepts the message of the deletion identity (Personality) in the prior art to feed back the deletion personality request message of the access network, and there is a certain degree of non-correspondence.
  • the access terminal needs to send a delete identity (Personality) accept message to the access network multiple times, which is very Waste of air resources.
  • the technical problem to be solved by the present invention is to provide a method for responding to a "Personality Request message" in the ultra-mobile broadband technology to solve the "Personality” request of the access terminal in response to the access network in the prior art.
  • the message can only be used to feedback the "Personality Acceptance Message" of a Personality, the problem of wasted air resources.
  • the present invention firstly provides a method for responding to a "delete feature request message" in an ultra mobile broadband technology, and the "delete feature request message" is sent by an access network through an air interface of the ultra mobile broadband.
  • the "delete feature accept message” Providing an access terminal, where the access terminal sends a "delete feature accept message” to the access network when the access network requests to delete one or more characteristics, the "delete feature accept message”
  • the information carried in the information includes: a message identifier, a transaction identifier, a feature count, and a characteristic index, where the characteristic count information is determined by the access terminal according to the number of characteristics that are agreed to be deleted, and the characteristic index information is The access terminal agrees to delete one or more characteristics.
  • the characteristic count information may be the number of the characteristics that the access terminal agrees to delete.
  • the present invention further provides a method for responding to a "delete feature request message" by an access terminal in an ultra mobile broadband technology, comprising the following steps:
  • the present invention also provides a method for responding to a "delete feature request message" in an ultra mobile broadband technology, and the "delete feature request message" is sent by an access network to an access terminal through an air interface of the ultra mobile broadband.
  • the access terminal When the access network is required to delete one or more characteristics, the access terminal sends a "delete feature response message" to the access network, and the information carried in the "delete feature response message" includes: a message An identifier, a transaction identifier, an acceptance inclusion identifier, a feature count, a feature index, and a rejection reason, wherein the acceptance inclusion identifier is determined according to whether the access terminal agrees to delete the characteristic, and the characteristic count information is determined by the The incoming terminal is determined according to the number of characteristics that are agreed to be deleted, and the characteristic index information is one or more characteristics that the access terminal agrees to delete.
  • the characteristic count information may be the number of the characteristics that the access terminal agrees to delete.
  • the receiving inclusion identifier is determined to be that the access terminal agrees to delete the feature, and does not specify the reason for the rejection; the acceptance inclusion identifier is determined to be that the access terminal refuses to delete the feature, The feature count information is not specified.
  • the present invention also provides a method for responding to a "delete feature request message" by an access terminal in an ultra mobile broadband technology, comprising the following steps:
  • the access terminal determines whether it agrees to delete one or more of the characteristics, and if it agrees, determines the number of characteristics that agree to delete, and then proceeds to step (3), if not, then proceeds to step (4);
  • the access terminal will agree to delete the content of the at least one characteristic as the "receive inclusion identifier” information, the number of characteristics to be deleted as the “characteristic count” information, and also agree to delete one or more characteristics.
  • the "characteristic index” information it is filled in the "delete feature response message” and sent to the access network;
  • the access terminal disagrees with the deletion of any feature as the "receive inclusion of identification” information, and rejects the deletion of the feature as the “rejection reason” information, populates the "delete feature response message", and sends it to The access network.
  • the deletion characteristic response message further includes the following information: a message identifier, a transaction identifier, and a reserved bit.
  • the present invention also provides a method for responding to a "delete feature request message" in an ultra mobile broadband technology, where the "delete feature request message" is sent by an access network to an access terminal through an air interface of the ultra mobile broadband, Methods include:
  • the access terminal When the access network is required to delete one or more characteristics, the access terminal sends a "delete feature response message" to the access network, and the information carried in the "delete feature response message" includes: Message ID, Transaction ID, Accept Include ID, Rejection Attribute Count, Feature Index, Retention Bit, and Reason for Rejection, where:
  • Determining, the inclusion, the identifier is determined according to whether the access terminal agrees to delete the characteristic; and the characteristic index information, when the refusal to delete any feature, rejects one or more characteristics of the deletion for the access terminal;
  • the reject characteristic count information is determined by the access terminal according to the number of characteristics that are rejected for deletion.
  • the receiving inclusion identifier determines that the access terminal agrees to delete all the characteristics, and does not specify the reason for the rejection, and ignores the rejection characteristic count;
  • the acceptance inclusion identifier determines that the access terminal refuses to delete any of the characteristics, specifies the information of the rejection reason, and the number of all characteristics that are rejected for deletion as the rejection characteristic count information.
  • the present invention also provides a method for responding to a "delete feature request message" by an access terminal in an ultra mobile broadband technology, comprising the following steps:
  • the access terminal determines whether it agrees to delete all the requested features, and if yes, proceeds to step (3), and if not, proceeds to step (4); (3) The access terminal will agree to delete the content of all the features as the "receive inclusion identifier" information, fill it into the "delete feature response message", and send it to the access network;
  • the access terminal disagrees with deleting any feature as the "receive inclusion of identification” information, and rejects the number of features to be deleted as “rejection characteristic count” information, and also rejects one or more characteristics of the deletion.
  • the "characteristic index” information the corresponding attribute reason is rejected as the "rejection reason” information, and the information is filled in the "delete characteristic response message" and transmitted to the access network.
  • the deletion characteristic response message further includes the following information: a message identifier, a transaction identifier, and a reserved bit.
  • the present invention enhances the characteristics of the UMB technology by enhancing or extending the message by accepting the personality (Personality), or by directly defining a new delete attribute (Personality) response message on the access terminal side (
  • the management mechanism of Personality saves the signaling interaction overhead of the air interface and saves the air interface resources.
  • FIG. 1 is a schematic diagram of a negotiated Personality embodiment owned by an eBS in the prior art
  • FIG. 2 is a schematic diagram of an embodiment of a method for deleting a personality request message by an access terminal through an enhanced delete Personality accept message response access network
  • FIG. 3 is a schematic diagram of an embodiment of a method for deleting a personality request message of an access terminal by the access terminal by deleting a personality response message;
  • FIG. 4 is an embodiment of a method for an access terminal to respond to a "Personality Request message" of an access network through a UMB air interface.
  • the present invention will be further described in detail below in conjunction with the drawings and specific embodiments.
  • the property (Personality) that is desired to be deleted is carried.
  • a delete attribute (Personality) accept message in the prior art can only indicate the deletion of a feature (Personality) that is desired to be deleted. Therefore, the access terminal needs to send a delete identity (Personality) accept message to the access network multiple times for carrying a message of a delete identity (Personality) requesting to delete multiple characteristics (Personality).
  • the present invention provides the following two ideas:
  • Enhancing or extending the Delete Personality Acceptment message in the prior art so that an enhanced or extended Delete Property (Personality) accept message may include multiple characteristics (Personality) of the accepted deletion.
  • the enhanced identity feature accepts the message, and also carries the function of rejecting the feature (Personality) to reject the message, so the deletion feature (Personality) acceptance message and the deletion property (Personality) rejection message in the prior art can be adopted. Replace it.
  • the enhanced delete property accepts the (DeletePersonalityAccept) message format, as shown in Table 5:
  • the access terminal is set to 0x0e.
  • Transaction ID The access terminal sets this field value to the corresponding value in the corresponding deletion request (personality) request message.
  • the access terminal sets this field to the number of times the personality index appears in this message.
  • Characteristic index The access terminal sets this field to the corresponding feature that each agrees to be deleted.
  • Reserved bit 2 This field is currently set to 0 to ensure that the length of the entire message is an integer multiple of the 8-bit group, and the number of bits can be set according to specific needs.
  • the information includes: message identification, transaction identification, Personality count, Personality index, and reserved bits. Characteristics (Personality) The count information is determined by the number of characteristics (Personality) included in the message; Personality The index information is a specific one or more characteristics (Personality) that the access terminal agrees to delete.
  • the method for the access terminal to respond to the "Personality Request message" of the access network through the UMB air interface includes the following steps:
  • Step 201 When the access network requests to delete one or more characteristics (Personality), send a "Personality Request message" to the access terminal through the UMB air interface, where the message indicates the feature to be deleted (Personality) ;
  • Step 202 After receiving the "Personality Request message", the access terminal determines one or more characteristics (Personality) that are agreed to be deleted, and determines the number of characteristics (Personality) that are agreed to be deleted;
  • Step 203 The access terminal determines the "Personality Count” information as the number of characteristics (Personality) carried in the message, and uses one or more characteristics (Personality) agreed to be deleted as the "Personality Index” information. Filled in the "Personality Accept Message", that is, the enhanced delete feature (Personality) accepts the message and sends it to the access network.
  • This new message replaces the two messages by taking into account the functionality of the Deletement feature (DeletePality) and its enhanced functionality, as well as the ability to delete the Personality Deny (Received PersonityReject) message. For example, it is defined as "Delete Personality Response (DeletePolicalityResponse) message", and the access terminal sends the "Personality Response Message" as feedback after receiving the "Personality Request Message" of the access network. Either accept the deletion of at least one feature ( Personality ) or refuse to delete any personality.
  • the access terminal is set to OxOe.
  • Transaction ID The access terminal sets this field value to the corresponding value of the corresponding message (Personality) request message.
  • the access terminal sets the field to the corresponding feature (Personality) for which it is agreed to be deleted. Otherwise, the access terminal ignores or does not include this domain.
  • This field is set to 0 to ensure that the length of the entire message is an integer multiple of the octet.
  • Reason for rejection If the value of 'accept the identifier is T, the access terminal ignores or does not include this field. Otherwise, the access terminal sets this field to display the delete attribute (Personality) request message. The reason for being rejected.
  • the value of the code is as shown in Table 4 above.
  • the above acceptance of the word containing the identifier is 1 bit, and the value can be reversed.
  • the access terminal accepts the characteristics (Personality) in at least one deletion request
  • the value of this field is set to '0, otherwise it is set to T.
  • Receiving the inclusion identifier actually identifies two states: one is to accept the deletion of some or all of the "Personality" request message (Personality), and the other is to refuse to delete the "Personality request message". Any of the characteristics mentioned (Personality).
  • Step 301 Access network When it is required to delete one or more characteristics (Personality), a "delete personality request message" is sent to the access terminal through the UMB air interface, and the message indicates the feature to be deleted (Personality);
  • Step 302 After receiving the "delete personality request message", the access terminal determines whether it agrees to delete one or more characteristics (Personality), and if it agrees to delete at least one of its characteristics (Personality), determines the feature that agrees to delete ( After the number of Personality), go to step 303, if you do not agree to delete any of the characteristics (Personality), then go to step 304;
  • Step 303 The access terminal will agree to delete the content of at least one feature (Personality) as the "receive inclusion identifier" information, agree to delete the number of characteristics (Personality) as the “Personality Count” information, and also agree to delete one or more
  • the property (Personality) is filled in the "Personality Response Message" and sent to the access network.
  • Step 304 The access terminal uses the content that does not agree to delete any feature (Personality) as the "receive inclusion identifier” information, and rejects the feature of the deletion (Personality) as the "rejection reason” information, and populates the "delete personality response message”. Medium, sent to the access network.
  • Method 3 define a new air interface message
  • This new message takes into account the functionality of the Deletement (PersonalityAccept) message and its enhanced functionality, as well as the delete feature rejection (DeletePersonalityReject).
  • the function of the message can thus replace these two messages. For example, define it as "delete feature response
  • the access terminal is set to OxOe.
  • Transaction ID The access terminal sets this field value to the corresponding value of the corresponding message (Personality) request message.
  • RejectPersonalityCount If the value of 'accept the include flag' is '0', the access terminal sets this field to the number of times the feature (Personality) index appears in this message. The characteristics corresponding to these characteristics (Personality) index are rejected. Otherwise, the access terminal ignores or does not include this domain.
  • Reserved bits 1 , 2 This field is set to 0 to ensure that the length of the entire message is an integer multiple of the octet.
  • Reason for rejection If 'accept the value of T, the access terminal ignores or does not include this field. Otherwise, the access terminal sets this field to show the reason why the corresponding feature (Personality) is rejected. Its value code is as shown in Table 4 above.
  • the above acceptance of the word containing the identifier is 1 bit, and the value can be reversed.
  • Receiving the inclusion of the identifier actually identifies two states: one is to accept all of the "Personality request message" characteristics (Personality), and the other is to accept the part "Personality request message” Personality or refusal to delete any of the properties (Personality) mentioned in the "Personality Request Message".
  • the above description of the value 0 or 1 is not intended to limit the invention.
  • the access terminal responds to the "Personality Request message" of the access network through the UMB air interface.
  • the method includes the following steps: Step 401: Access network When it is required to delete one or more characteristics (Personality), a "delete feature request message" is sent to the access terminal through the UMB air interface, and the message indicates one or more characteristics (Personality) to be deleted;
  • Step 402 After receiving the "Deletion Feature Request message", the access terminal determines whether to agree to delete all the included personalities. If it agrees to delete all the personalities, go to step 403, if you do not agree to delete the Any feature ( Personality ), then go to step 404;
  • Step 403 The access terminal agrees to delete the content of all the characteristics (Personality) as the "receive inclusion identifier" information is set to T, is filled in the "delete feature response message", and is sent to the access network;
  • Step 404 The access terminal treats the content that does not agree to delete any feature (Personality) as The inclusion of the identifier "information is set to '0', and the number of characteristics (Personality) that are refused to be deleted is used as the "rejection characteristic count” information, and one or more characteristics (Personality) that are rejected are also referred to as "Personality Index” information.
  • the reason for refusing to delete the corresponding feature (Personality) is used as the "rejection reason" message, and is filled in the "delete feature response message” and sent to the access network.
  • the present invention enhances the management mechanism of the characteristics (Personality), and has the following beneficial effects:
  • the management mechanism of the feature is enhanced by encrypting or expanding the acceptance message of the prior art in the prior art.
  • the access terminal can accept the deletion of multiple characteristics (Personality) through a Deleted Personality Accept (DeletePersonalityAccept) message.
  • DeletePersonalityAccept Deleted Personality Accept
  • a new Deletement feature (PersonalityResponse) message is defined on the access terminal side to feedback the access property request message of the access network. Not only can one or more characteristics (Personality) to be deleted be displayed at one time, but also information about the characteristics of the access terminal that refuses to be deleted (Personality) can be displayed at the same time, thereby further saving air interface signaling interaction overhead and valuable air interface resources. .
  • the foregoing method 3 defines a new air interface message, which takes into account the function of the Deletement Personality Acceptance message and the above-mentioned enhanced function, and the function of deleting the FeaturePenalityReject message, thereby replacing These two messages.
  • the method for responding to the "Delete Feature Request message" in the Ultra Mobile Broadband (UMB) technology disclosed in the present invention is suitable for solving the "Personality Request message" of the access terminal in response to the access network in the prior art.
  • the problem of deleting a "Personality Acceptance Message" of a feature (Personality) can be feedback at a time, and the method of the present invention applies the access terminal to access when the access network requires deletion of one or more characteristics.
  • the network transmits a "delete feature accept message" carrying feature count information, feature index information, and the like.
  • the invention enhances the management mechanism of characteristics in the UMB system, and saves signaling interaction overhead and air interface resources of the air interface.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Description

超移动宽带技术中对 "删除特性请求消息" 的响应方法
技术领域
本发明涉及超移动宽带技术， 尤其涉及超移动宽带技术中对 "删除特性 ( ersonality )请求消息" 的响应方法。
背景技术
目前， 无线通讯不同接入技术领域中， 都在研究和发展今后一个时期内 相应接入技术的演进，以提供相应系统和网络的性能及业务能力。 UMB ( Ultra Mobile Broadband, 超移动宽带）则是 CDMA2000接入技术演进的新技术。 UMB这一空中接口的诸多技术可以大大提升以 CDMA2000接入技术为基础 的通讯网络的性能， 为用户提供更多、 更高要求的无线多媒体业务奠定了本 质基础。
UMB在无缝切换的设计过程中， 提出了 AT ( Access Terminal, 接入终 端）的激活集中的每个 eBS ( evolved BS , 演进技术基站）和 AT都有其各自 的协议栈的设计思想。 激活集中的每个 eBS 都拥有一套协商后的特性 ( Personality )。 每个 eBS和 AT独自决定他们之间的协议栈釆用什么样的特 性 ( Personality ) 。 一个特性（Personality ) 定义为一套完整的经协商的协议 子类型、 应用子类型、 属性值、 非属性数据值、 和公共数据（这些都可以用 作一个协议或者应用的实用实例）。 诸多的特性（ Personality )编成不同的指 数（index )来代表。
以上内容可以参见图 1 ,激活集中包括有三个支持 UMB的演进技术基站， 分别用 eBSl、 eBS2和 eBS3表示， 其中每个 eBS的会话信息 （ Session Info ) 中, 都包含 personality A、 personality B、 personality C、 personality D等不同 的 personality指数（Index ) 。 SessionSignature X表示会话签名 X, 并且 AT 与 eBSl协商后， 指示 eBSl的 personality A为处于正在使用的协议或者应用 实例， AT与 eBS2、 eBS3协商后， 分别指示各自的 personality C为处于正在 使用的协议或者应用实例。 在这项技术中， 特性（Personality ) 的管理非常重要， 它确定 AT能和每 个 eBS协商成功的有效的协议栈。 现有技术中， 定义了如下相关的消息涉及 到 Personality的删除：
( 1 )删除 ersonality请求 ( DeletePersonalityRequest ) 消息
该消息是接入网 （即 eBS 或者 AN )要求 AT删除一个或者多个特性 ( Personality ) 。 其格式如表 1所示：
表 1、 删除特性（Personality )请求消息格式
Figure imgf000004_0001
表 1 中 "特性（Personality )指数" 域和 "保留位" 域之间留有空行， 表示只有 personality指数出现计数次。
其中，
消息标识： 接入网设为 0x0d。
事务标识： 接入网每发送一次删除特性（Personality )请求消息， 就增加 此值。
特性（ Personality )计数： 接入网将此域设为本消息中特性（ Personality ) 指数的出现的次数。
特性 （ Personality ) 指数： 接入网将该域设为相应的希望删除的特性 ( Personality ) 。 接入网将按照优先删除的顺序进行设置。
保留位： 这个域当前设为 0以保证整个消息的长度是 8位组的整数倍， 也可根据具体需要具体设置其位数。
( 2 )删除特性 ( Personality )接受（ DeletePersonalityAccept ) 消息 该消息是接入终端向接入网显示要删除的特性（Personality )。 其格式如 表 2所示：
表 2、 删除特性（Personality )接受消息格式
Figure imgf000005_0001
其中，
消息标识： 接入终端设为 OxOe。
事务标识： 接入终端将此域值设为在对应删除特性（ Personality )请求消 息的相应值。
特性 （Personality ) 指数： 接入终端将该域设为相应的被删除的特性 ( Personality ) 。
保留位： 这个域当前设为 0以保证整个消息的长度是 8位组的整数倍， 也可根据具体需要具体设置其位数。
( 3 )删除特性（Personality )拒绝（ DeletePersonalityReject ) 消息 该消息是接入终端用来拒绝接入网要求的删除 Personality请求， 其格式 如表 3所示：
表 3、 删除特性（Personality )拒绝消息格式 域（ Field ) 长度（比特 ) ( Length ( bits ) ) 消息标识 ( MessagelD ) 8
事务标识 ( TransactionID ) 8
拒绝原因 （RejectReason ) 8
保留位（Reserved ) 0-7根据需要（as needed) 其中，
消息标识： 接入网设为 OxOf。
事务标识：接入终端将此域值设为对应于被拒绝的删除特性（ Personality ) 请求消息的相应值。
拒绝原因： 接入终端设此域， 其中的信息表示删除特性（Personality )请 求（ DeletePersonalityRequest ) 消息被拒绝的原因。
保留位： 这个域当前设为 0以保证整个消息的长度是 8位组的整数倍， 也可根据具体需要具体设置其位数。
删除特性（Personality )请求消息被拒绝的原因， 可能有多种情况， 其值 编码如表 4所示：
表 4、 拒绝原因值 ( RejectReason Values )
Figure imgf000006_0001
从表 2所示的删除特性（Personality )接受消息格式中可以看到， 该删除 特性（ Personality )接受消息只包括一个可以接受删除的特性（ Personality ) 。 但是， 如表 1所示的删除特性（Personality )请求消息中， 可以携带多个希望 被删除的特性 （Personality ) 。 因此， 接入终端以现有技术中的删除特性 ( Personality )接受消息来反馈接入网的删除 personality请求消息， 存在一定 程度的不对应。 而且， 对于接入网请求删除多个特性（Personality ) 的情形， 接入终端就需要向接入网多次发送删除特性（Personality )接受消息， 这是很 浪费空中资源的。
发明内容
本发明所要解决的技术问题在于提供超移动宽带技术中对 "删除特性 ( Personality )请求消息" 的响应方法， 以解决现有技术中接入终端在响应接 入网的 "删除特性（Personality )请求消息" 时， 一次只能反馈删除一个特性 ( Personality ) 的 "删除特性（ Personality )接受消息" ， 由此而带来的空中 资源浪费的问题。
为解决上述技术问题， 本发明首先提供一种超移动宽带技术中对 "删除 特性请求消息" 的响应方法， 所述 "删除特性请求消息" 由接入网通过所述 超移动宽带的空中接口发送给接入终端， 其中， 在所述接入网要求删除一个 或多个特性时，由所述接入终端向所述接入网发送一个"删除特性接受消息"， 所述 "删除特性接受消息" 中携带的信息包括： 消息标识、 事务标识、 特性 计数、 以及特性指数， 其中， 所述特性计数信息由所述接入终端根据同意删 除的特性的个数而确定， 所述特性指数信息为所述接入终端同意删除的一个 或多个特性。
进一步地， 所述特性计数信息可以为所述接入终端同意删除的所述特性 的个数。
本发明进而提供一种在超移动宽带技术中由接入终端对 "删除特性请求 消息" 的响应方法， 包括如下步骤：
接入网要求删除一个或多个特性时， 向所述接入终端发送所述 "删除特 性请求消息" ；
所述接入终端确定同意删除的一个或多个特性， 并确定其个数； 所述接入终端将所述同意删除的特性个数作为 "特性计数" 信息， 并将 所述同意删除的一个或多个特性作为 "特性指数" 信息， 填充入 "删除特性 接受消息" 中， 发送至所述接入网。 本发明还提供一种超移动宽带技术中对 "删除特性请求消息" 的响应方 法， 所述 "删除特性请求消息" 由接入网通过所述超移动宽带的空中接口发 送给接入终端， 在所述接入网要求删除一个或多个特性时， 由所述接入终端 向所述接入网发送一个 "删除特性回应消息" ， 所述 "删除特性回应消息" 中携带的信息包括： 消息标识、 事务标识、 接受包含标识、 特性计数、 特性 指数、 以及拒绝原因， 其中， 所述接受包含标识根据所述接入终端是否同意 删除特性的结果而确定， 所述特性计数信息由所述接入终端才艮据同意删除的 特性的个数而确定， 所述特性指数信息为所述接入终端同意删除的一个或多 个特性。
进一步地， 所述特性计数信息可以为所述接入终端同意删除的所述特性 的个数。
进一步地， 所述接受包含标识确定为所述接入终端同意删除所述特性， 则不指定所述拒绝原因的信息； 所述接受包含标识确定为所述接入终端拒绝 删除所述特性， 则不指定所述特性计数信息。
本发明还提供一种在超移动宽带技术中由接入终端对 "删除特性请求消 息" 的响应方法， 包括如下步骤：
( 1 )接入网要求删除一个或多个特性时， 向所述接入终端发送所述 "删 除特性请求消息" ；
( 2 )所述接入终端判断是否同意删除其中的一个或多个特性， 如果同意 则确定同意删除的特性的个数后， 转步骤（3 ) ， 如果不同意则转步骤（4 )；
( 3 )所述接入终端将同意删除至少一个特性的内容作为 "接收包含标识" 信息， 将所述同意删除的特性个数作为 "特性计数" 信息， 还将同意删除的 一个或多个特性作为 "特性指数" 信息， 填充入 "删除特性回应消息" 中， 发送至所述接入网；
( 4 )所述接入终端将不同意删除任何特性的内容作为 "接收包含标识" 信息， 并将拒绝删除特性的原因作为 "拒绝原因" 信息， 填充入 "删除特性 回应消息" 中， 发送至所述接入网。 所述删除特性回应消息， 进一步还包括如下信息： 消息标识、 事务标识、 保留位。
本发明还提供一种超移动宽带技术中对 "删除特性请求消息" 的响应方 法， 所述 "删除特性请求消息" 由接入网通过所述超移动宽带的空中接口发 送给接入终端， 该方法包括：
在所述接入网要求删除一个或多个特性时， 由所述接入终端向所述接入 网发送一个 "删除特性回应消息" ， 所述 "删除特性回应消息" 中携带的信 息包括： 消息标识、 事务标识、 接受包含标识、 拒绝特性计数、 特性指数、 保留位、 以及拒绝原因， 其中：
所述接受包含标识根据所述接入终端是否同意删除特性的结果而确定； 所述特性指数信息， 在拒绝删除任何特性时， 为所述接入终端拒绝删除 的一个或多个特性；
所述拒绝特性计数信息， 由所述接入终端根据拒绝删除的特性的个数而 确定。
所述接受包含标识确定为所述接入终端同意删除全部所述特性， 则不指 定所述拒绝原因的信息， 忽略拒绝特性计数；
所述接受包含标识确定为所述接入终端拒绝删除任何所述特性， 则指定 所述拒绝原因的信息， 以及拒绝删除的全部特性的个数作为所述拒绝特性计 数信息。
本发明还提供一种在超移动宽带技术中由接入终端对 "删除特性请求消 息" 的响应方法， 包括如下步骤：
( 1 )接入网要求删除一个或多个特性时， 向所述接入终端发送所述 "删 除特性请求消息" ；
( 2 )所述接入终端判断是否同意删除所请求的全部特性， 如果同意则转 至步骤（3 ) , 如果不同意则转至步骤（4 ) ； ( 3 )所述接入终端将同意删除全部特性的内容作为 "接收包含标识"信 息， 填充入 "删除特性回应消息" 中， 发送至接入网；
( 4 )所述接入终端将不同意删除任何特性的内容作为 "接收包含标识" 信息， 并将拒绝删除的特性个数作为 "拒绝特性计数" 信息， 还将拒绝删除 的一个或多个特性作为 "特性指数"信息，将拒绝删除对应特性原因作为 "拒 绝原因" 信息， 并将所述各信息填充入 "删除特性回应消息" 中， 发送至接 入网。
所述删除特性回应消息， 进一步还包括如下信息： 消息标识、 事务标识、 保留位。
与现有技术相比， 本发明通过对删除特性（Personality )接受消息进行增 强或扩展， 或者直接通过在接入终端侧定义一个新的删除特性（Personality ) 回应消息， 增强了 UMB技术中特性（Personality ) 的管理机制， 节约了空中 接口的信令交互开销， 并进而节约了空中接口资源。
附图概述
图 1为现有技术中 eBS拥有的协商后的 Personality实施例示意图； 图 2为接入终端通过增强后的删除 Personality接受消息响应接入网的删 除 personality请求消息方法实施例；
图 3 为接入终端通过删除 personality 回应消息响应接入网的删除 personality请求消息方法实施例；
图 4 为接入终端通过 UMB 空中接口响应接入网的 "删除特性 ( Personality )请求消息" 的方法实施例。
本发明的较佳实施方式
下面结合附图和具体实施方式对本发明做进一步详细的说明。 如表 1所示的删除特性（Personality )请求消息中， 携带希望被删除的特 性 ( Personality ) 。 但是， 现有技术中的一条删除特性（Personality )接受消 息只能指示删除一个希望被删除的特性（Personality )。 因此对携带有希望删 除多个特性（Personality ) 的删除特性（Personality )请求消息， 接入终端就 需要多次向接入网发送删除特性（ Personality )接受消息。 为了改进此技术缺 陷， 本发明提供如下两种思路：
( 1 )对现有技术中的删除 Personality接受（ DeletePersonalityAccept )消 息进行增强或扩展， 使得一条增强或扩展后的删除特性（Personality )接受消 息就可以包括所接受删除的多个特性（Personality ) 。
( 2 )定义一种新的空中接口消息， 该新消息在功能上不仅兼顾上述思路
( 1 ) 中增强删除特性 ( Personality ) 接受消息， 而且还携带了删除特性 ( Personality )拒绝消息的功能，因此可将现有技术中的删除特性（ Personality ) 接受消息和删除特性（Personality )拒绝消息替换掉。
下面分别详细阐述这两种思路的具体实现方式。
方式一、 增强的删除特性（ Personality )接受 （ DeletePersonalityAccept ) 消息
在现有的删除特性（ Personality )接受消息中，增加一个新的域， 比如 "特 性（ Personality )计数（ PersonalityCount )"字段，以显示接收方在删除 Personality 请求（ DeletePersonalityRequest ) 消息中所接受可以删除的特性（ Personality ) 的个数。每个要删除的特性（ Personality )则由随后的 Personality指数（ Index ) 来表示。 这样， 将现有技术中的删除特性（Personality )接受消息进行增强之 后， 特性（Personality )指数就可以根据需要决定出现的次数， 而不是现在技 术中的一次。
增强后的删除特性（Personality )接受（DeletePersonalityAccept )消息格 式， 如表 5所示：
表 5、 增强后的删除 Personality接受消息格式 域 (Field) 长度 (比特) (Length (bits) ) 消息标识 （MessagelD) 8
事务标识 (TransactionID) 8
特性计数 ( Personal ityCount) 4
保留位 1 (Reserved) 4 如下内容记录出现特件计数次 (PersonalityCount instances of the following record)
特性指数 (Personality Index) 4
保留位 2 (Reserved) 0-7 根据需耍 (as needed) 表 5 中 "特性（Personality)指数" 域和 "保留位" 域之间留有空行， 表示只有 personality指数出现计数次。
其中，
消息标识： 接入终端设为 0x0e。
事务标识： 接入终端将此域值设为在对应删除特性（personality)请求消 息的相应值。
特性计数： 接入终端将此域设为本消息中特性（personality)指数出现的 次数。
保留位 1: 这个域当前设为 '0000', 接收方将忽视该域.
特性指数： 接入终端将此域设为相应的每个同意被删除的特性
( ersonality ) 。
保留位 2: 这个域当前设为 0以保证整个消息的长度是 8位组的整数倍， 也可根据具体需要具体设置其位数。
因此， 对现有技术中的删除特性（Personality)接受消息进行增强之后， 接入终端向接入网发送 "删除特性（Personality)接受消息" 时， 该 "删除特 性（Personality)接受消息" 中携带的信息包括： 消息标识、 事务标识、 特 性 ( Personality )计数、 特性（Personality)指数、 以及保留位。 其中的特性 ( Personality )计数信息由本消息包含的特性（Personality )个数而确定； 特 性 ( Personality ) 指数信息为接入终端同意删除的具体的一个或多个特性 ( Personality ) 。
在此基础上， 接入终端通过 UMB 空中接口响应接入网的 "删除特性 ( Personality )请求消息" 的方法， 如图 2所示， 包括如下步骤：
步骤 201 : 接入网要求删除一个或多个特性（Personality )时， 通过 UMB 空中接口向接入终端发送 "删除特性（Personality )请求消息" ， 该消息中指 示出欲要删除的特性（Personality ) ；
步骤 202: 接入终端接收到该 "删除特性（Personality )请求消息" 后， 确定同意删除的一个或多个特性 （Personality ) , 并确定同意删除的特性 ( Personality ) 的个数；
步骤 203: 接入终端将 "特性（Personality )计数" 信息确定为本消息所 携带的特性（Personality )个数， 并将同意删除的一个或多特性（Personality ) 作为 "特性（Personality )指数" 信息， 填充入 "删除特性（Personality )接 受消息" 中， 也即增强后的删除特性（Personality )接受消息， 发送至接入网。
方式二、 定义新的空中接口消息
该新消息兼顾删除特性（Personality )接受（ DeletePersonalityAccept ) 消 息的功能及其上述增强后的功能， 以 及删除 Personality 拒绝 ( DeletePersonalityReject )消息的功能， 因而可以替代这两条消息。 比如将其 定义为 "删除 Personality回应 （ DeletePersonalityResponse ) 消息" ， 接入终 端在接收到接入网的 "删除特性（Personality )请求消息" 后， 发送该 "删除 特性 （ Personality ) 回应消息 " 作为反馈， 或者接受删除至少一个特性 ( Personality ) , 或者拒绝删除任何 personality。
该删除特性（ Personality )回应（ DeletePersonalityResponse )消息的格式， 如表 6所示：
表 6、 删除 Personality回应消息格式 域（ Field ) 长度（比特 ) ( Length ( bits ) ) 消息标识 ( MessagelD ) 8
事务标识 ( TransactionID ) 8
接受包含标识 ( Acceptlncld ) 1
特' |·生计数 ( PersonalityCount ) 4
如下内容" i己录出现特' f生计数次 ( PersonalityCount instances of the following record ) 特性指数 ( Personality Index ) 4 保留位（Reserved ) 0-7根据需要 ( as needed) 拒绝原因 （RejectReason ) 8
消息标识： 接入终端设为 OxOe。
事务标识： 接入终端将此域值设为在对应删除特性（Personality )请求消 息的相应值。
接受包含标识： 如果接入终端接受至少一个删除请求中的特性 ( Personality ) , 则此域的值设为 'Γ , 否则设为 '0， 。
特性（ Personality )计数： 如果 '接受包含标识， 的值为 T , 则接入 终端将此域设为本消息中特性 （ Personality ) 指数出现的次数。 这些特性 ( Personality )指数对应的特性（ Personality )是被同意删除的。 否则， 接入 终端忽略或者不包含此域。
特性（ Personality )指数： 如果 '接受包含标识， 的值为 T , 接入终 端将该域设为相应的每个同意被删除的特性（Personality )。 否则， 接入终端 忽略或者不包含此域。
保留位： 这个域设为 0 , 以保证整个消息的长度是 8位组的整数倍。 拒绝原因： 如果 '接受包含标识， 的值为 T , 则接入终端忽略或者不 包含此域， 否则， 接入终端设置此域以显示删除特性（Personality )请求消息 被拒绝的原因。 其值编码如上述表 4所示。
当然， 上述的接受包含标识的字长为 1位， 其值也可以反过来设置。 比 如接入终端接受至少一个删除请求中的特性（Personality )， 则此域的值设为 '0， ， 否则设为 T 。 接收包含标识实际上标识了两种状态： 一种是接受 删除部分或全部 "删除特性（ Personality )请求消息"中的特性（ Personality ) , 另一种是拒绝删除 "删除特性（Personality )请求消息" 所提到的任何一个特 性 ( Personality ) 。
在表 6所示格式的基础上， 接入终端通过 UMB空中接口响应接入网的 "删除特性（Personality )请求消息" 的方法， 如图 3所示， 包括如下步骤： 步骤 301 : 接入网要求删除一个或多个特性（Personality )时， 通过 UMB 空中接口向接入终端发送 "删除 personality请求消息" ， 该消息中指示出欲 要删除的特性（Personality ) ；
步骤 302: 接入终端接收到该 "删除 personality请求消息"后， 判断是否 同意删除其中的一个或多个特性（Personality ) , 如果同意删除其至少一个特 性 ( Personality ) , 则确定同意删除的特性（Personality ) 的个数后， 转步骤 303 , 如果不同意删除其中的任何特性（Personality ) , 则转步骤 304;
步骤 303: 接入终端将同意删除至少一个特性（Personality ) 的内容作为 "接收包含标识"信息， 同意删除的特性（Personality )个数作为 "Personality 计数"信息， 还将同意删除的一个或多个特性（Personality )作为 "Personality 指数" 信息， 填充入 "删除 Personality回应消息" 中， 发送至接入网；
步骤 304:接入终端将不同意删除任何特性（Personality )的内容作为 "接 收包含标识"信息， 并将拒绝删除特性（Personality )的原因作为 "拒绝原因" 信息， 填充入 "删除 Personality回应消息" 中， 发送至接入网。
方式三、 定义新的空中接口消息
该新消息兼顾删除特性（Personality )接受（ DeletePersonalityAccept ) 消 息的功能及其上述增强后的功能，以及删除特性拒绝（ DeletePersonalityReject ) 消息的功能， 因而可以替代这两条消息。 比如将其定义为 "删除特性回应
( DeletePersonalityResponse ) 消息" ， 接入终端在接收到接入网的 "删除特 性（Personality )请求消息" 后， 发送该 "删除特性（Personality ) 回应消息" 作为反馈， 或者接受删除至少一个特性（Personality ) , 或者拒绝删除任何特 该删除特性回应（DeletePersonalityResponse )消息的格式， 如表 7所示: 表 7、 删除特性回应消息格式
Figure imgf000016_0001
其中，
消息标识： 接入终端设为 OxOe。
事务标识： 接入终端将此域值设为在对应删除特性（Personality )请求消 息的相应值。
接受包含标识：如果接入终端接受所有删除请求中的特性（Personality ) , 则此域的值设为 'Γ , 否则设为 '0， 。
拒绝特性计数（ RejectPersonalityCount )： 如果 '接受包含标识， 的值为 '0， ， 则接入终端将此域设为本消息中特性（Personality )指数出现的次数。 这些特性（Personality )指数对应的特性（Personality )是被拒绝删除的。 否 则， 接入终端忽略或者不包含此域。
特性（ Personality )指数： 如果 '接受包含标识， 的值为 '0' , 接入终 端将该域设为相应的每个拒绝被删除的特性（Personality )。 否则， 接入终端 忽略或者不包含此域。
保留位 1 , 2: 这个域设为 0, 以保证整个消息的长度是 8位组的整数倍。 拒绝原因： 如果 '接受包含标识， 的值为 T , 则接入终端忽略或者不 包含此域， 否则， 接入终端设置此域以显示对应的特性（Personality )删除被 拒绝的原因。 其值编码如上述表 4所示。
当然， 上述的接受包含标识的字长为 1位， 其值也可以反过来设置。 接 收包含标识实际上标识了两种状态：一种是接受全部 "删除特性（Personality ) 请求消息"中的特性（ Personality ) ,另一种是接受部分 "删除特性（ Personality ) 请求消息"所提到的特性（ Personality )或者拒绝删除 "删除特性（ Personality ) 请求消息" 所提到的任何一个特性（Personality )。 上述取值为 0或 1的描述 不作为对本发明的限定。
在表 7所示格式的基础上， 接入终端通过 UMB空中接口响应接入网的 "删除特性（Personality )请求消息" 的方法， 如图 4所示， 包括如下步骤： 步骤 401 : 接入网要求删除一个或多个特性（Personality )时， 通过 UMB 空中接口向接入终端发送 "删除特性请求消息" ， 该消息中指示出欲要删除 的一个或多个特性（Personality ) ；
步骤 402: 接入终端接收到该 "删除特性请求消息" 后， 判断是否同意 删除所包含的全部特性（ Personality ) ,如果同意删除全部特性（ Personality ) , 则转步骤 403 ,如果不同意删除其中的任何特性 ( Personality ) ,则转步骤 404;
步骤 403: 接入终端将同意删除全部特性（Personality ) 的内容作为 "接 收包含标识"信息设为 T , 填充入 "删除特性回应消息" 中， 发送至接入 网；
步骤 404:接入终端将不同意删除任何特性（ Personality )的内容作为 "接 收包含标识" 信息设为 '0' , 并将拒绝删除的特性（Personality )个数作为 "拒绝特性计数"信息， 还将拒绝删除的一个或多个特性（Personality )作为 "Personality指数" 信息， 拒绝删除对应特性（Personality ) 的原因作为 "拒 绝原因" 信息， 填充入 "删除特性回应消息" 中， 发送至接入网。
本实施例中上述取值为 0或 1的描述不作为对本发明的限定， 亦可颠倒 使用。
与现有技术相比， 本发明增强了特性（Personality )的管理机制， 具有如 下的有益效果：
上述方式一通过对现有技术中的删除特性（Personality )接受消息进行增 强或扩展， 增强了特性 （Personality ) 的管理机制。 对于删除多个特性 ( Personality ) 的请求， 接入终端可以通过一个增强删除特性（Personality ) 接受（DeletePersonalityAccept )消息显示接受多个特性（Personality )的删除。 这样既澄清了现有技术的含糊， 使得接入终端与接入网之间的管理技术更加 明确和有效， 又避免按照现有技术中通过空中接口对同一个删除特性 ( Personality )请求消息进行多次反馈。 这也就有效地节约了空中接口的信令 交互开销， 进而节约了宝贵的空中接口资源。
上述方式二通过在接入终端侧定义一个新的删除特性（Personality )回应 ( DeletePersonalityResponse )消息 , 来对接入网的删除特性（ Personality )请 求消息进行反馈。 不仅可以一次显示所要删除的一个或多个特性 ( Personality ) , 而且可以同时显示接入终端拒绝删除的特性（ Personality ) 的相关信息， 进一步节约了空中接口信令交互开销， 和宝贵的空中接口资源。
上述方式三定义了一个新的空中接口消息， 该新消息兼顾删除特性 ( Personality )接受（DeletePersonalityAccept )消息的功能及其上述增强后的 功能， 以及删除特性拒绝（DeletePersonalityReject )消息的功能， 因而可以替 代这两条消息。 工业实用性 本发明公开的超移动宽带（UMB )技术中对 "删除特性请求消息" 的响 应方法， 适于解决现有技术中接入终端在响应接入网的 "删除特性 ( Personality )请求消息" 时， 一次只能反馈删除一个特性（Personality ) 的 "删除特性（Personality )接受消息" 的问题， 应用本发明的所述方法在接入 网要求删除一个或多个特性时， 由接入终端向接入网发送携带特性计数信息、 特性指数信息等的一个 "删除特性接受消息" 。 本发明增强了 UMB 系统中 特性的管理机制， 节约了空中接口的信令交互开销和空中接口资源。

Claims

权 利 要 求 书
1、一种超移动宽带技术中对 "删除特性请求消息"的响应方法，所述 "删 除特性请求消息 "由接入网通过所述超移动宽带的空中接口发送给接入终端， 其特征在于：
在所述接入网要求删除一个或多个特性时， 由所述接入终端向所述接入 网发送一个 "删除特性接受消息" , 所述 "删除特性接受消息" 中携带的信 息包括： 消息标识、 事务标识、 特性计数、 特性指数、 以及保留位， 其中： 所述特性指数信息， 是所述接入终端同意删除的一个或多个特性； 所述特性计数信息， 由所述 "删除特性接受消息" 所包含的接入终端同 意删除的特性个数而确定。
2、 如权利要求 1所述的方法， 其特征在于： 所述特性计数信息， 为所述 "删除特性接受消息" 所包含的接入终端同 意删除的特性个数。
3、 一种在超移动宽带技术中由接入终端对 "删除特性请求消息" 的响应 方法， 其特征在于， 包括如下步骤：
接入网要求删除一个或多个特性时， 向所述接入终端发送所述 "删除特 性请求消息" ；
所述接入终端确定同意删除的一个或多个特性， 并确定其个数； 所述接入终端将所述同意删除的特性个数作为 "特性计数" 信息， 并将 所述同意删除的一个或多个特性作为 "特性指数" 信息， 填充入 "删除特性 接受消息" 中， 将所述删除特性接受消息发送至所述接入网。
4、 如权利要求 3所述的方法， 其特征在于：
所述 "删除特性接受消息" 中携带的信息还包括： 消息标识、 事务标识、 以及保留位。
5、一种超移动宽带技术中对 "删除特性请求消息"的响应方法，所述 "删 除特性请求消息 "由接入网通过所述超移动宽带的空中接口发送给接入终端， 其特征在于：
在所述接入网要求删除一个或多个特性时， 由所述接入终端向所述接入 网发送一个 "删除特性回应消息" ， 所述 "删除特性回应消息" 中携带的信 息包括： 消息标识、 事务标识、 接受包含标识、 特性计数、 特性指数、 保留 位、 以及拒绝原因， 其中：
所述接受包含标识根据所述接入终端是否同意删除特性的结果而确定； 所述特性指数信息， 为所述接入终端同意删除的一个或多个特性； 所述特性计数信息，由所述接入终端根据同意删除的特性的个数而确定。
6、 如权利要求 5所述的方法， 其特征在于， 所述特性计数信息为所述接 入终端同意删除的所述特性的个数。
7、 如权利要求 5所述的方法， 其特征在于：
所述接受包含标识确定为所述接入终端同意删除所述特性， 则不指定所 述拒绝原因的信息；
所述接受包含标识确定为所述接入终端拒绝删除所述特性， 则不指定所 述特性计数信息。
8、 一种在超移动宽带技术中由接入终端对 "删除特性请求消息" 的响应 方法， 其特征在于， 包括如下步骤：
( 1 )接入网要求删除一个或多个特性时， 向所述接入终端发送所述 "删 除特性请求消息" ；
( 2 )所述接入终端判断是否同意删除其中的一个或多个特性， 如果同意 则确定同意删除的特性的个数后，转至步骤（ 3 ) ,如果不同意则转至步骤（ 4 )；
( 3 )所述接入终端向所述接入网发送 "删除特性回应消息" ， 在该 "删 除特性回应消息" 中， 配置 "接收包含标识" 信息的内容为同意删除至少一 个特性， 将同意删除的一个或多个特性作为 "特性指数" 信息， 将所述同意 删除的特性个数作为 "特性计数" 信息； ( 4 )所述接入终端向所述接入网发送 "删除特性回应消息" , 在该 "删 除特性回应消息" 中， 配置 "接收包含标识" 信息的内容为不同意删除任何 特性， 并将拒绝删除特性的原因作为 "拒绝原因" 信息。
9、 如权利要求 8所述的方法， 其特征在于：
所述删除特性回应消息， 进一步还包括如下信息：
消息标识、 事务标识、 保留位。
10、 一种超移动宽带技术中对 "删除特性请求消息" 的响应方法， 所述 "删除特性请求消息 " 由接入网通过所述超移动宽带的空中接口发送给接入 终端， 其特征在于：
在所述接入网要求删除一个或多个特性时， 由所述接入终端向所述接入 网发送一个 "删除特性回应消息" ， 所述 "删除特性回应消息" 中携带的信 息包括： 消息标识、 事务标识、 接受包含标识、 拒绝特性计数、 特性指数、 保留位、 以及拒绝原因， 其中：
所述接受包含标识根据所述接入终端是否同意删除特性的结果而确定； 所述特性指数信息， 在拒绝删除任何特性时， 为所述接入终端拒绝删除 的一个或多个特性；
所述拒绝特性计数信息， 由所述接入终端根据拒绝删除的特性的个数而 确定。
11、 如权利要求 10所述的方法， 其特征在于：
所述接受包含标识确定为所述接入终端同意删除全部所述特性， 则不指 定所述拒绝原因的信息， 忽略拒绝特性计数；
所述接受包含标识确定为所述接入终端拒绝删除任何所述特性， 则指定 所述拒绝原因的信息， 以及拒绝删除的全部特性的个数作为所述拒绝特性计 数信息。
12、 一种在超移动宽带技术中由接入终端对 "删除特性请求消息" 的响 应方法， 其特征在于， 包括如下步骤：
(1 )接入网要求删除一个或多个特性时， 向所述接入终端发送所述 "删 除特性请求消息" ；
(2)所述接入终端判断是否同意删除所请求的全部特性， 如果同意则转 至步骤（3) , 如果不同意则转至步骤（4) ；
(3)所述接入终端将同意删除全部特性的内容作为 "接收包含标识"信 息， 填充入 "删除特性回应消息" 中， 发送至接入网；
(4)所述接入终端将不同意删除任何特性的内容作为 "接收包含标识" 信息， 并将拒绝删除的特性个数作为 "拒绝特性计数" 信息， 还将拒绝删除 的一个或多个特性作为 "特性指数"信息，将拒绝删除对应特性原因作为 "拒 绝原因" 信息， 并将所述各信息填充入 "删除特性回应消息" 中， 发送至接 入网。
13、 如权利要求 12所述的方法， 其特征在于：
所述删除特性回应消息， 进一步还包括如下信息：
消息标识、 事务标识、 保留位。
PCT/CN2008/070708 2007-04-18 2008-04-14 Method of responding deltepersonalityrequest message in ultra mobile broadband Ceased WO2008128461A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/596,123 US20100128674A1 (en) 2007-04-18 2008-04-14 Method of Responding DeletePersonalityRequest Message in Ultra Mobile Broadband

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007100937847A CN101291266B (zh) 2007-04-18 2007-04-18 超移动宽带技术中对“删除特性请求消息”的响应方法
CN200710093784.7 2007-04-18

Publications (1)

Publication Number Publication Date
WO2008128461A1 true WO2008128461A1 (en) 2008-10-30

Family

ID=39875093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070708 Ceased WO2008128461A1 (en) 2007-04-18 2008-04-14 Method of responding deltepersonalityrequest message in ultra mobile broadband

Country Status (3)

Country Link
US (1) US20100128674A1 (zh)
CN (1) CN101291266B (zh)
WO (1) WO2008128461A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5698822B1 (ja) * 2013-10-25 2015-04-08 株式会社Ｎｔｔドコモ 移動通信方法、移動通信システム及び無線基地局

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1237052A (zh) * 1998-05-25 1999-12-01 三菱电机株式会社 多通信连接设定方法
US6950413B1 (en) * 2000-07-20 2005-09-27 Jenn-Chorng Liou Mutually-assisted proximity informer system and method with wireless devices
CN1917478A (zh) * 2006-09-14 2007-02-21 杭州华为三康技术有限公司 转发报文的处理方法及处理模块

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4224370B2 (ja) * 2003-09-25 2009-02-12 パナソニック株式会社 入力制御装置及び入力制御方法
US7502820B2 (en) * 2004-05-03 2009-03-10 Microsoft Corporation System and method for optimized property retrieval of stored objects
US8072922B2 (en) * 2006-07-31 2011-12-06 Qualcomm Incorporated Method and apparatus for negotiating personalities in a wireless communications system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1237052A (zh) * 1998-05-25 1999-12-01 三菱电机株式会社 多通信连接设定方法
US6950413B1 (en) * 2000-07-20 2005-09-27 Jenn-Chorng Liou Mutually-assisted proximity informer system and method with wireless devices
CN1917478A (zh) * 2006-09-14 2007-02-21 杭州华为三康技术有限公司 转发报文的处理方法及处理模块

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Session Control Plane for Ultra Mobile Broadband (UMB) Air interface Specification", 3GPP2 C.S0084-007.0 VERSION 2.0, August 2007 (2007-08-01), Retrieved from the Internet <URL:http://www.3gpp2.org/public_html/specs/alltsgscfm.cfm> *
"Session Control Plane for Ultra Mobile Broadband (UMB) Air interface Specification", 3GPP2 C.S0084-007-0 VERSION 1.0, 5 April 2007 (2007-04-05), Retrieved from the Internet <URL:http://www.ftp.3pp2.org/TSGC/Working/2007/2007-0405-PlenaryConfCall/C00-20070405-002_C.S0084-0v1.0_UMB_UpperLayer.pdf.zip> *

Also Published As

Publication number Publication date
CN101291266A (zh) 2008-10-22
US20100128674A1 (en) 2010-05-27
CN101291266B (zh) 2011-05-11

Similar Documents

Publication Publication Date Title
CN113411857B (zh) 通信方法及装置
CN101242568B (zh) 一种无线通讯网络中服务质量协商的方法及系统
CN100531010C (zh) 通信系统中提供广播/多播服务的状态信息的方法和系统
EP4132213A1 (en) Method for controlling media streaming service transmission, user terminal, network node, system, storage medium, and electronic device
WO2019033796A1 (zh) 会话处理方法及相关设备
WO2008000128A1 (en) A method and register and system for group calling
EP2026626A1 (en) Apparatuses, methods and system for Service Flow Management in a Broadband Wireless Communication System
CN108156645A (zh) 接入处理方法、基站及移动通信终端
CN116686383A (zh) 一种通信方法及用户设备
CN101316237A (zh) 动态业务流的处理方法
CN101299830B (zh) Iu接口并行的多媒体广播组播业务会话的更新方法和装置
CN116261141A (zh) 基于5g物联网卡的sa网络接入方法、系统、装置及介质
WO2008125057A1 (fr) Procédé et système de communication avec un abonné supportant divers services de messagerie
WO2022156716A1 (zh) 接入网系统
WO2007022729A1 (en) A method and system for increasing the resource using efficiency in communication network
WO2008128461A1 (en) Method of responding deltepersonalityrequest message in ultra mobile broadband
CN102045844A (zh) 能力信息上报方法和装置
CN101309223A (zh) 数据通道建立方法及系统
CN101309506B (zh) 呼叫控制方法、移动交换中心及通信系统
CN101309507B (zh) 超移动宽带特性的处理方法
CN110166503B (zh) 信息交互方法、设备及计算机可读存储介质
CN101567827A (zh) 终端会话切换中传送会话记录的方法、系统及设备、终端
CN101277296A (zh) 一种配置协商方法、系统和设备
CN101296438A (zh) 用于超移动宽带网络的特性管理方法和系统
CN115334594B (zh) 铁路5g专网调度通信业务服务质量协商控制实现方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08734066

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 12596123

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08734066

Country of ref document: EP

Kind code of ref document: A1