CN101442397B - Transmission method for reason value - Google Patents
Transmission method for reason value Download PDFInfo
- Publication number
- CN101442397B CN101442397B CN2007101945643A CN200710194564A CN101442397B CN 101442397 B CN101442397 B CN 101442397B CN 2007101945643 A CN2007101945643 A CN 2007101945643A CN 200710194564 A CN200710194564 A CN 200710194564A CN 101442397 B CN101442397 B CN 101442397B
- Authority
- CN
- China
- Prior art keywords
- failure
- reason value
- message
- relevant
- response message
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a method for transmitting a cause value. The method comprises the following steps: in step S102, a second communication entity responds from a request message of a first communication entity and carries out operation; in step S104, under the condition of operation failure, the second communication entity feeds back a response message to the first communication entity, wherein a general failure cause value relevant to the request message and a specific failure cause value relevant to specific operation are put in different type length value fields of the response message for limiting or are put in the same type length value field of the response message for limiting; and in step S106, the first communication entity receives, analyzes and processes the response message. The method can make definition for indicating a failure cause field clearer, reduce repeated and redundant definition, and effectively avoid chaos occurring in subsequent operation and save mass system resource.
Description
Technical field
The present invention relates to the communications field, relate in particular to a kind of failure reason value transmission method.
Background technology
The NWG (network technology working group) of Wimax (Worldwide Interoperability for Microwave Access, micro-wave access global inter communication) has proceeded to the R1.1.x version at present, during the R1.5 version is being discussed and worked out.In existing R1.1.x version, there is the application of a large amount of TLV (Type Length Value, type lengths values) field.
In the NWG existing standard, Failure indication (mistake indication) is used to indicate the failure cause of previous request message.Following several types of cause values are arranged respectively: the message header failure code, general message body failure code, the common failure code of message, the specific failure code of message, wherein the back is the failure reason value relevant with concrete operations for two types.The Failureindication reference table 1 of this standard definition:
| Type (type) | 69 |
| Length in octets (byte is the length of unit) | 1?byte |
| Value (value) | Most significant bit is reserved as an error extension flag; (highest significant position keeps as a wrong extending marking) ● 0=Unspecified Error; (unspecified mistake) Error Codes:1-16 Message Header Failure Codes; (error code: 1-16 message header failure code) ● 1=Incompatible Version Number; (version number does not match) ● 2=Invalid Function Type; (invalid function type) ● 3=Invalid Message Type; (invalid message type) ● 4=Unknown MSID; (unknown terminal iidentification) ● 5=Transaction Failure; (handling failure) ● 6=Unknown Source Identifier; (unknown source sign) ● 7=Unknown Destination Identifier; (unknown purpose sign) ● 8=Invalid Message Header; (invalid message header) ● 9-15=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:16-31 General Message Body Failure Codes; (the general message body failure code of error code: 16-31) ● 16=Invalid message format; (invalid message format) ● 17=Mandatory TLV missing; (having omitted essential type lengths values) ● 18=TLV Value Invalid; (type lengths values is invalid) ● 19=Unsupported Options; (unsupported option) ● 20-31=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:32-47 Message Generic Failure Codes; (error code: the general failure code of 32-47 message) ● 32=Timer expired without response; (not having the response timer expiry) ● 33-47=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:48-127 Message Specific Failure Codes; (error code: the specific failure code of 48-127 message) ● 48=Requested Context Unavailable; (context of request does not obtain) ● 49=Authorization Failure; (authorization failure) ● 50=Registration Failure; (registration failure) ● 51=No Resources; (not having resource) ● 52-127=Reserved for Future Use; (being that purposes in the future keeps); (To be updated with sub section team specific error handling); (upgrading) with sub-chapters and sections particular error processing |
| Description (description) | Indicates the reason for failure of a previous request messageFailure indication should be the First TLV in a response message whenit is failure for the request message. (indicates the failure cause of previous request message.When being used to indicate the request message failure, Failure indication (failure indication) should be first type lengths values of response message.) |
| Parent TLV (father TLV) | None (nothing) |
Table 1
Reservation Result (reservation result) is the sub-TLV (sub-TLV) of SF Info (Business Stream information), and the result of expression resource reservation is defined as as shown in table 2:
| Type (type) | 152 |
| Length in octets (byte is the length of unit) | 2 |
| Value (value) | Result can be one of the following; (result can be following a kind of): ● 0x0000=Successfully Created; (successfully creating) ● 0x0001=Request Denied-No resources; (not having resource) ● 0x0002=Request Denied due to Policy; (because of the request of strategy refusal) ● 0x0003=Request Denied due to Requests for Other FlowsFailed.; (because of the request failure of other streams is refused) ● 0x0004=Request Failed; (Unspecified reason) asks failure; (nothing indicates reason) ● 0x0005=Request Denied due to MS reason; (because of the request of terminal reason refusal) ● Other=Reserved; (reservation) |
| Description (description) | Indicates the result of a Resource Reservation Request (result of a resource reservation request of indication) |
| Parent TLV (father TLV) | SF Info (Business Stream information) |
Table 2
Authentication Result (authenticating result) is defined as as shown in table 3:
| Type (type) | 18 |
| Length in octets (byte is the length of unit) | 1 |
| Value (value) | The value of this parameter indicates to BS the results of EAPauthentication process (this parameter is to the result of base station indication extended authentication agreement authentication process): ● 0=Success (success) ● 1=Failure (failure) Other values are reserved (other is worth reservation) |
| Description (description) | Indication of EAP success (success of indication extended authentication agreement authentication) |
| Parent TLV (s) (father TLV) | Authentication Complete (authentication completion) |
Table 3
There is the application of a large amount of TLV fields in the existing version of NWG, in much relevant TLV, all defined failure reason value separately with operation.Such as, in SF Info, Reservation Result is used for indicating the result of resource reservation as sub-TLV.0 representes successfully, the various failure causes of other value representations.Obviously, these two types of failure reason values of common failure code of message among this and the Failure indication and the specific failure code of message repeat.Because failure reason value is a field very commonly used, cause a large amount of resource overhead wastes like this; Simultaneously,, cause a plurality of local indications that same failure cause occurs, both be not easy to unified management, the subsequent operation of carrying out according to this cause value is caused obscure again because the failure reason value indication is chaotic.
Summary of the invention
To above one or more problems; The present invention provides a kind of transmission method for reason value; Definition to failure reason value is adjusted; General failure cause unification that will be relevant with message header and message body is placed on definition in the failure indication (Failure indication), and the specific failure cause relevant with concrete operations is placed on respectively and operates among the relevant TLV and define.
Transmission method for reason value provided by the invention comprises step S102, and the second communication entity is in response to operating from the request message of first communication entity; Step S104; Under the situation of operation failure; The second communication entity is to the first communication entity feedback response message; Wherein, general failure reason value that will be relevant with request message and the specific failure reason value of being correlated with concrete operations are placed on respectively to limit or be placed in the same type lengths values field in the response message in the different type lengths values field in the response message and limit; Step S106, first communication entity analyze and handle after receiving response message.
Wherein, general failure reason value comprise following one of at least: message header failure code and message body failure code.In response message, can be shown as the merit indication through a type lengths values field list, also can be shown as the merit indication through the specific list of values in the cause value type lengths values field.Be placed under the situation about limiting in same type lengths values field or the dissimilar length field at the general failure reason value relevant with request message with the relevant specific failure reason value of concrete operations, the type lengths values field is for can expand the type lengths values field that maybe can not expand.
In the WiMAX wireless communication system; Be placed on respectively when limiting in the different type lengths values field in the response message when general failure reason value that will be relevant with the relevant specific failure reason value of concrete operations, will the general failure reason value relevant be placed in the indication field of failing and limit with request message with request message.
Be placed on respectively when limiting in the different type lengths values field in the response message when general failure reason value that will be relevant with the relevant specific failure reason value of concrete operations with request message; If response message has comprised the type lengths values field of indicating general failure reason value; The type lengths values field that then no longer comprises the specific failure reason value that indication is relevant with concrete operations; If response message has comprised the type lengths values field of the specific failure reason value that indication is relevant with concrete operations, then no longer comprise the type lengths values field of indicating general failure reason value.
Adopt the present invention, can make the definition of indication failure cause field more clear, reduce the definition of repeated and redundant, effectively avoid the confusion that possibly occur in the subsequent operation, and saved a large amount of system resources.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the flow chart according to transmission method for reason value of the present invention; And
Fig. 2 is Business Stream visioning procedure figure according to an embodiment of the invention.
Embodiment
With reference to accompanying drawing, specify embodiment of the present invention below.
Transmission method for reason value provided by the invention may further comprise the steps, and is as shown in Figure 1:
Step S102, the second communication entity is in response to operating from the request message of first communication entity; Step S104; Under the situation of operation failure; The second communication entity is to the first communication entity feedback response message; Wherein, general failure reason value that will be relevant with request message and the specific failure reason value of being correlated with concrete operations are placed on respectively to limit or be placed in the same type lengths values field in the response message in the different type lengths values field in the response message and limit; Step S106, first communication entity analyze and handle after receiving response message.
General failure reason value comprise following one of at least: message header failure code and message body failure code.In response message, can be shown as the merit indication through a type lengths values field list, also can be shown as the merit indication through the specific list of values in the cause value type lengths values field.Be placed under the situation about limiting in same type lengths values field or the dissimilar length field at the general failure reason value relevant with request message with the relevant specific failure reason value of concrete operations, the type lengths values field is for can expand the type lengths values field that maybe can not expand.
In the WiMAX wireless communication system; Be placed on respectively when limiting in the different type lengths values field in the response message when general failure reason value that will be relevant with the relevant specific failure reason value of concrete operations, will the general failure reason value relevant be placed in the indication field of failing and limit with request message with request message.
Be placed on respectively when limiting in the different type lengths values field in the response message when general failure reason value that will be relevant with the relevant specific failure reason value of concrete operations with request message; If response message has comprised the type lengths values field of indicating general failure reason value; The type lengths values field that then no longer comprises the specific failure reason value that indication is relevant with concrete operations; If response message has comprised the type lengths values field of the specific failure reason value that indication is relevant with concrete operations, then no longer comprise the type lengths values field of indicating general failure reason value.
In one embodiment of the invention, general, general failure reason value unification is placed among the TLV_C defines.For example can define being placed among the Failure Indication among the NWG with message header, failure cause unification that message body is relevant; Other failure causes relevant with concrete operations are placed among the TLV_S that is correlated with this operation and define.The TLV_S of for example relevant with resource reservation operation indication failure can be Reservation Result, and ReservationResult is the sub-TLV of SF Info.
When failure cause is general cause value, then in message, comprise TLV_C indication failure cause; When failure cause is other cause values relevant with concrete operations, then in message, comprise TLV_S indication failure cause.Both have one to get final product.
A value representation that can be used as TLV_C or TLV_S is indicated in success.For example, the TLV_C value is 0 o'clock, and expression is operated successfully; Or the TLV_S value is 0 o'clock, and expression is operated successfully.
Cause value definition to existing Failure indication; Keep original failure reason value relevant with message header and message body; The common failure code of message and two types of cause values of the specific failure code of message are removed, are put into respectively in the failure reason value relevant and define reference table 4 with concrete operations:
| Type (type) | 69 |
| Length in octets (byte is the length of unit) | 1 |
| Value (value) | Most significant bit is reserved as an error extension flag; (; (highest significant position keeps as a wrong extending marking)) ● 0=Unspecified Error; (unspecified mistake) Error Codes:1-16 Message Header Failure Codes; (error code: 1-16 message header failure code) ● 1=Incompatible VersionNumber; (version number does not match) ● 2=Invalid Function Type; (invalid function type) ● 3=Invalid Message Type; (invalid message type) ● 4=Unknown MSID; (unknown terminal iidentification) ● 5=Transaction Failure; (handling failure) ● 6=Unknown Source Identifier; (unknown source sign) ● 7=Unknown Destination Identifier; (unknown purpose sign) ● 8=Invalid Message Header; (invalid message header) ● 9-15=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:16-31 General Message Body Failure Codes; (the general message body failure code of error code: 16-31) ● 16=Invalid message format; (invalid message format) ● 17=Mandatory TLV missing; (having omitted essential type lengths values) ● 18=TLV Value Invalid; (type lengths values is invalid) ● 19=Unsupported Options; (unsupported option) ● 20-31=Reserved for Future Use; (being that purposes in the future keeps) |
| Description (description) | Indicates the reason for general failure of a previous request messageFailure indication should be the First TLV in a response messagewhen it is failure forthe request message. (indicates the failure cause of previous request message.When being used to indicate the request message failure, Failure indication (mistake indication) should be first type lengths values of response message.) |
| Parent TLV (father TLV) | None (nothing) |
Table 4
Reservation Result will be used for indicating resource reservation requested operation result, comprise removing all failure reason values relevant with message header and message body among the resource reservation requested operation result, reference table 5:
| Type (type) | 152 |
| Length in octets (byte is the length of unit) | 2 |
| Value (value) | Result can be one ofthe following; (result can be following a kind of): ● 0x0000=Successfully Created; (successfully creating) ● 0x0001=Request Denied-No resources; (not having resource) ● 0x0002=Request Denied due to Policy; (because of the request of strategy refusal) ● 0x0003=Request Denied due to Requests for Other FlowsFailed.; (because of the request failure of other streams is refused) ● 0x0004=Request Failed; (Unspecified reason) asks failure; (nothing indicates reason) ● 0x0005=Request Denied due to MS reason; (because of the request of terminal reason refusal) ● 0x0006=Timer expired without response; (not having the response timer expiry) ● Other=Reserved |
| Description (description) | Indicates the result of a Resource Reservation Request. (result of a resource reservation request of indication) |
| Parent TLV (father TLV) | SF Info (Business Stream information) |
Table 5
Authentication Result will be used to indicate the result of EAP access, comprise removing all failure reason values relevant with message header and message body, reference table 6:
| Type (type) | 18 |
| Length in octets (byte is the length of unit) | 1 |
| Value (value) | The value of this parameter indicates to BS the results of EAPauthentication process; (this parameter is to the result of base station indication extended authentication agreement authentication process): ● 0x00=Success; (success) ● 0x01=Failure; (failure) ● 0x02=Timer expired without response; (not having the response timer expiry) ● 0x03=Requested Context Unavailable; (context of request does not obtain) ● 0x04-0xFF=Reserved for future use; (being that purposes in the future keeps) Other values are reserved.; (other is worth reservation) |
| Description (description) | Indication of EAP success (success of indication extended authentication agreement authentication) |
| Parent TLV (s) (father TLV) | Authentication Complete (authentication completion) |
Table 6
In another embodiment of the present invention, all failure reason value unifications are placed among the TLV_O define.Both comprised general, general failure cause; Also comprise the reason relevant with concrete operations.Can all failure reason value unifications be placed among the TLV_O and define, comprise the cause value relevant with various concrete operations.
TLV_O here is Failure Indication, reference table 7, and this field is defined as follows:
First is general, general cause value, is 0-47;
Second portion is and the relevant cause value of SF (Business Stream) operation, is 48-71;
Third part is and the relevant cause value of Paging (paging) operation, is 72-95;
The 4th part is and the relevant cause value of Authentication (authentication), is 96-119;
Other can be the relevant cause value of other operations and reserve 119-255.
Can all failure reason value unifications be placed among the Failure Indication and define, comprise the cause value relevant with various concrete operations.
| Type (type) | 69 |
| Length in octets (byte is the length of unit) | 1 |
| Value (value) | Most significant bit is reserved as an error extension flag; (highest significant position keeps as mistake expansion sign) ● 0=Unspecified Error; (unspecified mistake) Error Codes:1-16 Message Header Failure Codes; (error code: 1-16 message header failure code) ● 1=Incompatible Version Number; (version number does not match) ● 2=Invalid Function Type; (invalid function type) ● 3=Invalid Message Type; (invalid message type) ● 4=Unknown MSID; (unknown terminal iidentification) ● 5=Transaction Failure; (handling failure) ● 6=Unknown Source Identifier; (unknown source sign) ● 7=Unknown Destination Identifier; (unknown purpose sign) ● 8=Invalid Message Header; (invalid message header) ● 9-15=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:16-31 General Message Body Failure Codes; (the general message body failure code of error code: 16-31) ● 16=Invalid message format; (invalid message format) ● 17=Mandatory TLV missing; (having omitted essential type lengths values) ● 18=TLV Value Invalid; (type lengths values is invalid) ● 19=Unsupported Options; (unsupported option) ● 20-31=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:32-47 Other Message Generic Failure Codes error code: the general failure code of other message of 32-47 |
| ● 32=Timer expired without response; (not having the response timer expiry) ● 33=Requested Context Unavailable; (context of request does not obtain) ● 34-47=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:48-71 SF Operation Failure Codes error code: 48-71 Business Stream operation failure sign indicating number ● 48=Request Denied-No resources; (because of there not being the request of resource refusal) ● 49=Request Denied due to Policy; (because of the request of strategy refusal) ● 50=Request Denied due to Requests for Other FlowsFailed; (because of request is refused in other stream request failure) ● 51=Request Denied due to MS reason; (former thereby refusal request) ● 52-71=Reserved for Future Use because of the terminal; (being that purposes in the future keeps); (Tobe updated with sub section team specific error handling); (upgrading) Error Codes:72-95 Paging Operation Failure Codes with sub-chapters and sections particular error processing; (error code: 72-95 paging operation failure code) ● 72-95=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:96-119 Authentication Operation Failure Codes; (error code: 96-119 authentication operations failure code) ● 96-119=Reserved for Future Use; (being that purposes in the future keeps) 120-255=Reserved; (To be updated with sub section team specific errorhandling); (keep＜handle with sub-chapters and sections particular error and upgrade) | |
| Description (description) | Indicates the reason for failure of a previous request messageFailure indication should be the First TLV in a response message whenit is failure for the request message. (indicates the failure cause of previous request message.When being used to indicate the request message failure, Failure indication (mistake indication) should be first type lengths values of response message.) |
| Parent TLV (father TLV) | None (nothing) |
Table 7
Other indication failure cause TLVs relevant with concrete operations can according to circumstances delete or revise.In the present embodiment, can be with Reservation Result, the AuthenticationResult deletion.
In another embodiment of the present invention, all failure reason value unifications are placed among the TLV_O define.Both comprised general, general failure cause, also comprised the reason relevant with concrete operations.TLV_O is for can expand TLV.For example, TLV_O length is i.e. 8 bits (bit) of 1 byte, then the highest bit of TLV_O is reserved to be used as expansion and to indicate the position.When this expansion sign position is 0,7 the bits indications in back failure reason values; When this expansion sign position was 1, these 7 bits were indicated failure reason value jointly with back to back 1 byte in back.
All failure reason value unifications are placed among the TLV_O define, comprise the cause value relevant with various concrete operations.
TLV_O here is Failure Indication, and the length of this field can be expanded, reference table 8, and this field is defined as follows:
First bit of highest order reserves and is used as expansion sign position.When expansion indicates the position when being 0,7 the bits indications in back failure reason values, promptly Failure Indication field length is 1 byte, but 128 of values, definition as follows:
First is general, general cause value, is 0-47;
Second portion is and the relevant cause value of SF operation, is 48-71;
Third part is and the relevant cause value of paging (Paging) operation, is 72-95;
The 4th part is and the relevant cause value of authentication (Authentication), is 96-119;
Other can be the relevant cause value of other operations and reserve 119-127.
When expansion indicates the position when being 1, a byte of Failure Indication extended length to back then, that is: the 7+8 of back bit indicated failure reason value, and Failure Indication field length is 2 bytes, but value is to define as follows:
First is general, general cause value, is 0-47;
Second portion is and the relevant cause value of SF (Business Stream) operation, is 48-71;
Third part is and the relevant cause value of Paging (paging) operation, is 72-95;
The 4th part is and the relevant cause value of Authentication (authentication), is 96-119;
Other can be the relevant cause value of other operations and reserve 119-255.
| Type (type) | 69 |
| Length in octets (byte is the length of unit) | Variable (variable) |
| Value (value) | Most significant bit is reserved as an error extension flag, if the mostsignificant bit is set 0, the length in octets is 1; (highest significant position keeps as a wrong extending marking else the length in octetsis 2; If highest significant position is changed to 0; Then this field length is 1 byte, otherwise is 2 bytes) ● 0=Unspecified Error (unspecified mistake) Error Codes:1-16 Message Header Failure Codes (error code: 1-16 message header failure code) ● 1=Incompatible Version Number (version number does not match) ● 2=Invalid Function Type (invalid function type) ● 3=Invalid Message Type (invalid message type) ● 4=Unknown MSID (unknown terminal iidentification) ● 5=Transaction Failure (handling failure) ● 6=Unknown Source Identifier (unknown resource identification) ● 7=Unknown Destination Identifier (unknown purpose sign) ● 8=Invalid Message Header (invalid message header) ● 9-15=Reserved for Future Use (being that purposes in the future keeps) Error Codes:16-31 General Message Body Failure Codes (the general message body failure code of error code: 16-31) ● 16=Invalid message format (invalid message format) ● 17=Mandatory TLV missing (having omitted essential type lengths values) ● 18=TLV Value Invalid (type lengths values is invalid) |
| ● 19=Unsupported Options; (unsupported option) ● 20-31=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:32-47 Other Message Generic Failure Codes; (error code: the general failure code of 32-47 message) ● 32=Timer expired without response; (not having the response timer expiry) ● 33=Requested Context Unavailable; (context of request does not obtain) ● 34-47=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:48-71 SF Operation Failure Codes; (error code: the specific failure code of 48-127 message) ● 48=Request Denied-No resources Requested ContextUnavailable; (context of request does not obtain) ● 49=Request Denied due to Policy; (because of the request of strategy refusal) ● 50=Request Denied due to Requests for Other FlowsFailed Registration Failure; (because of the request failure of other streams is refused) ● 51=Request Denied due to MS reason; (because of the request of terminal reason refusal) ● 52-71=Reserved for Future Use; (being that purposes in the future keeps); (To be updated with sub section team specific error handling); (upgrading) Error Codes:72-95 Paging Operation Failure Codes with sub-chapters and sections particular error processing; (error code: 72-95 paging operation failure code) ● 72-95=Reserved for Future Use; (being that purposes in the future keeps) Error Codes:96-119 Authentication Operation Failure Codes; (error code: 96-119 authentication operations failure code) ● 96-119=Reserved for Future Use; (being that purposes in the future keeps) other=Reserved for Future Use; (To be updated with sub section teamspecific errorhandling) other=be that in the future purposes keeps; (upgrading) with sub-chapters and sections particular error processing | |
| Description (description) | Indicates the reason for failure of a previous request messageFailure indication should be the First TLV in a response message whenit is failure for the request message. (indicates the failure cause of previous request message.When being used to indicate the request message failure, Failure indication (mistake indication) should be first type lengths values of response message.) |
| Parent TLV (father TLV) | None (nothing) |
Table 8
Other indication failure cause TLVs relevant with concrete operations can according to circumstances delete or revise.In the present embodiment, can be with Reservation Result, Authentication Result deletion.
The data channel enrollment response message is fed back the Request Processing result who creates a plurality of Business Streams in the data passage register request message.
In the prior art, in the data channel enrollment response message, two these results' of field indication failure cause is arranged, Reservation Result and Failure Indication.
Fig. 2 is Business Stream visioning procedure figure according to an embodiment of the invention.As shown in Figure 2, in the Business Stream visioning procedure, the data channel enrollment response message is fed back the result who creates the Request Processing of a plurality of Business Streams in the data passage register request message.
S202: grappling service flow authorization device (Anchor SFA) is received grade of service attribute, and resource reservation request (RR_Req) message is sent to current business flow authorized device (ServingSFA).
S204: whether current business flow authorized device inspection need create a data passages, according to sendaisle register request message or passage modify request messages to service flow management device (SFM) as a result.Suppose and be the passage register request here.
S206: whether the inspection of service flow management device has enough unlimited resources, and whether judgement accepts this request.Under situation about accepting, will send a dynamic service increases request (DSA_Req) message to the terminal.
S208: this DSA_Req (dynamic service increases request) message is accepted or is refused at the terminal.
S210: terminal acceptance among acceptance of service flow management device and the S208 among the supposition S206, the service flow management device will be confirmed reservation of resources to current business flow authorized device sendaisle grade response message or passage modification response message.It is the passage register response here.
S212: after the success response of receiving the service flow management device, the current business flow authorized device will send the resource reservation response message to grappling service flow authorization device and confirm reservation of resources.If response is failure, and predetermined result (Reservation Result) all indicated failure cause with failure indication (FailureIndication), and then the current business flow authorized device can't be indicated the processing of failing according to a unified reason.(causing the flow process confusion)
S214: passage registration ack message or passage are revised acknowledge message will be sent to the service flow management device.It is the passage registration ack message here.
S216: after receiving the success response of current business flow authorized device, grappling service flow authorization device will be replied the resource reservation acknowledge message to the current business flow authorized device.
The improvements of the embodiment of the invention are:
S210: terminal acceptance among acceptance of service flow management device and the S208 among the supposition S206, the service flow management device will be confirmed reservation of resources to current business flow authorized device sendaisle enrollment response message or passage modification response message.It is the passage register response here.Do not suppose and accept that the technology of pressing this programme has only this multi-business flow of field indication to create the failure cause of Request Processing, Reservation Result or FailureIndication in the passage enrollment response message.
S212: after the success response of receiving the service flow management device, the current business flow authorized device will send the resource reservation response message to grappling service flow authorization device and confirm reservation of resources.If response is failure, then the current business flow authorized device will be according to this failure cause indication (Reservation Result or Failure Indication, both only can the occur) processing of failing that occurs in the message.Clear process is simple.The reason if the failure cause response message does not match then directly abandons this message.If resource-constrained, can only provide than the less resource of ask, then the current business flow authorized device possibly accepted the low-grade business of being authorized.Other failure causes are correspondingly processed.
The present invention provides a kind of transmission method for reason value; Definition to failure reason value is adjusted; General failure cause unification that will be relevant with message header and message body is placed among the TLV; As defining among the Failure indication, and the specific failure cause relevant with concrete operations is placed on respectively and operates among the relevant TLV and define.Adopt the present invention, can make the definition of indication failure cause field more clear, reduce the definition of repeated and redundant, effectively avoid the confusion that possibly occur in the subsequent operation, and saved a large amount of system resources.
The above is merely the preferred embodiments of the present invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (7)
1. a transmission method for reason value is characterized in that, may further comprise the steps:
Step S102, the second communication entity is in response to operating from the request message of first communication entity;
Step S104; Under the situation of said operation failure; Said second communication entity is to the said first communication entity feedback response message; Wherein, general failure reason value that will be relevant with described request message and the specific failure reason value of being correlated with concrete operations are placed on respectively to limit or be placed in the same type lengths values field in the said response message in the different type lengths values field in the said response message and limit; And
Step S106, said first communication entity is analyzed and is handled after receiving said response message.
2. transmission method for reason value according to claim 1 is characterized in that, said general failure reason value comprise following one of at least: message header failure code and message body failure code.
3. transmission method for reason value according to claim 2 is characterized in that, in said response message, is shown as the merit indication through a type lengths values field list.
4. transmission method for reason value according to claim 2 is characterized in that, in said response message, is shown as the merit indication through the specific list of values in the cause value type lengths values field.
5. according to claim 3 or 4 described transmission method for reason value; It is characterized in that; Be placed under the situation about limiting in same type lengths values field or the different type lengths values field at the general failure reason value relevant with described request message with the relevant specific failure reason value of concrete operations, said type lengths values field is for can expand the type lengths values field that maybe can not expand.
6. transmission method for reason value according to claim 5; It is characterized in that; In the WiMAX wireless communication system; Be placed on respectively when limiting in the different type lengths values field in the said response message when general failure reason value that will be relevant with described request message with the relevant specific failure reason value of concrete operations, general failure reason value that will be relevant with described request message is placed in the indication field of failing and limits.
7. transmission method for reason value according to claim 5; It is characterized in that; Be placed on respectively when limiting in the different type lengths values field in the said response message when general failure reason value that will be relevant with the relevant specific failure reason value of concrete operations with described request message; If said response message has comprised the type lengths values field of indicating general failure reason value; The type lengths values field that then no longer comprises the specific failure reason value that indication is relevant with concrete operations; If said response message has comprised the type lengths values field of the specific failure reason value that indication is relevant with concrete operations, then no longer comprise the type lengths values field of indicating general failure reason value.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101945643A CN101442397B (en) | 2007-11-23 | 2007-11-23 | Transmission method for reason value |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101945643A CN101442397B (en) | 2007-11-23 | 2007-11-23 | Transmission method for reason value |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101442397A CN101442397A (en) | 2009-05-27 |
| CN101442397B true CN101442397B (en) | 2012-07-04 |
Family
ID=40726660
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101945643A Expired - Fee Related CN101442397B (en) | 2007-11-23 | 2007-11-23 | Transmission method for reason value |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101442397B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102684865B (en) * | 2011-03-07 | 2015-05-27 | 中国移动通信有限公司 | Method, system and device for data synchronization |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1968094A (en) * | 2006-11-23 | 2007-05-23 | 华为技术有限公司 | Method, system and server for prompting the cause for user terminal authentication failure |
| CN1984463A (en) * | 2006-01-10 | 2007-06-20 | 华为技术有限公司 | Method for obtaining service failure reason in heterogeneous network |
| CN101047623A (en) * | 2006-03-28 | 2007-10-03 | 华为技术有限公司 | Method and device for responding resource preleave require or strategy decision require |
-
2007
- 2007-11-23 CN CN2007101945643A patent/CN101442397B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1984463A (en) * | 2006-01-10 | 2007-06-20 | 华为技术有限公司 | Method for obtaining service failure reason in heterogeneous network |
| CN101047623A (en) * | 2006-03-28 | 2007-10-03 | 华为技术有限公司 | Method and device for responding resource preleave require or strategy decision require |
| CN1968094A (en) * | 2006-11-23 | 2007-05-23 | 华为技术有限公司 | Method, system and server for prompting the cause for user terminal authentication failure |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101442397A (en) | 2009-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105188045A (en) | Vehicle communication D2D discovery method, device and terminal | |
| US6370391B1 (en) | Mobile station and network having hierarchical index for cell broadcast service | |
| JP3103378B2 (en) | Wireless telecommunications system with supplementary services | |
| US20020196764A1 (en) | Method and system for authentication in wireless LAN system | |
| US20070149173A1 (en) | Wireless Data Service Apparatus and Method in Broadcast Mobile Communication System | |
| CN1264525A (en) | Remote clearing of access to telecommunication service | |
| CN1332576C (en) | Method and system for realizing concentration service to dynamic establish user group | |
| CN101622889A (en) | Move the route of the short message of initiating | |
| CN101442397B (en) | Transmission method for reason value | |
| CN111182542A (en) | Method, system, base station and readable storage medium for establishing proximity service | |
| EP3035770B1 (en) | Call service implementation method and device | |
| CN101669377A (en) | Mobility management (mm) and session management (sm) for sae/lte | |
| CN103997796A (en) | Method for processing service data | |
| CN101711043A (en) | Method and device for destroying compression context in robustness header compression | |
| CN101815240A (en) | Service opening method, communication system and relevant equipment | |
| CN105933140A (en) | Intelligent cross-network operation and maintenance monitoring technology | |
| US20110212727A1 (en) | Method for processing handoff confirm messages | |
| CN113949640B (en) | Service data processing method and device | |
| JP2011504700A (en) | Method for accessing a closed group in a radio access network | |
| CN110290123B (en) | Method for fast expanding and coding/decoding JT/T809 protocol | |
| CN100359900C (en) | System and method for implementing transaction identifier assignment of media gateway control protocol | |
| CN101325804B (en) | Method, device and system for acquiring cryptographic key | |
| KR20000062204A (en) | Message re-transmission method and repetition message processing method of mobile station using it on communication network | |
| CN113015132B (en) | Communication method and communication system | |
| CN100512528C (en) | Method for realizing imputation position registor user control |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120704 Termination date: 20201123 |