CN101060710B - A method for rapid selecting the link in the media independent switching technology - Google Patents

Abstract

The related fast selecting-link method comprises: the top entity sends at least one LinkType parameter to MIHF entity through MIU command; the latter selects proper link accordingly. This invention introduces better service to terminal.

Description

In media-independent switching technology, select the method for link fast

Technical field

The present invention relates to the communications field, relate in particular to media-independent switching technology.

Background technology

The selection of the moving of the variation of channel circumstance, user, different business etc. all may cause internetwork switching.In order to make client device roaming or between heterogeneous network, to carry out seamless switching automatically when switching, MIH (Media Independent Handover, media-independent switches) technology has been proposed.Described MIH technology can reduce switching delay and loss of data, guarantees the continuity of conversation procedure, strengthens user's experience.

Media-independent switching technology is mainly by MIHF (Media Independent HandoverFunction, independent medium switching functional entity) the media-independent service that provides realizes, the position of described MIHF and crucial media-independent service as shown in Figure 1, the media-independent service of wherein said key mainly comprises:

1, media-independent service, it provides information model and information bank so that formulate handover decisions effectively.

2, media-independent command service, it is used for user's control of giving an order and switches relevant link behavior.

3, media-independent Event Service, it comprises incident and trigger that local and remote interface produces.

The media-independent service that provides by MIHF, upper layer entity can be known the time that is about to begin of switching in advance, and the information such as network condition of portable terminal region, and can carry out the preparation of switching in advance according to the described information of knowing, comprise selection of carrying out network and access point etc., thereby can improve the performance of switching greatly, particularly the vertical switching between different Access Networks.

The media-independent order that MIHF provides comprises MIH order and LINK order.Because Link State constantly changes along with moving of time and terminal, the information that MICS (media-independent command service) provides, as link parameters such as signal strength signal intensity, link-speeds also is dynamic, therefore in order to make switching easier, upper layer entity need be configured, control the behavior of bottom to different bottom links and obtain the information of bottom by corresponding command configuration.

In the media-independent Event Service that MIHF provides, the end that rises of incident comprises the L2 data link layer, PHY or MIHF, the different event of holding according to rising can be divided into Link incident (end that rises is the incident of MIH lower floor) and MIH incident (end that rises is the incident of MIHF layer) again.The destination of Link incident comprises the MIH of native protocol stack and/or the MIH of remote protocol stack, etc.; The destination of MIH incident comprises the layer 3 of this locality or far-end, and/or other upper layer entity.

The prior art one relevant with the present invention is can the bottom access link being configured by the media-independent order that the MIHF entity provides of providing in the present standard.Its main contents are as follows:

Upper layer entity sends to the MIHF entity by following MIH order with the configuration link parameter:

MIH_Configure_Thresholds.request(

LinkParameterList

)

The MIHF entity orders the configuration status with link parameter to report upper layer entity by following MIH.

MIH_Configure_Thresholds.confirm(

LinkParameterStatusList

)

Wherein, the definition of described LinkParameterList parameter is as shown in table 1:

Title	Type	Effective range	Describe
				LinkParameterList?	Tabulation	N/A?	The tabulation of following parameters set: LinkParameterTypeInitiateActionThreshold, RollbackActionThreshold, ExecuteActionThreshold
Link?ParameterType?	Link?Speed，Link?Bit?Error?Rate，	N/A?	The parameter type that needs configuration

	Link Frame Loss Ratebefore retransmission, Link Signal Strength
				InitiateActionThreshold	Pei Zhi parameter is provided with corresponding threshold value as required	N/A	The upper strata will begin to prepare to initiate corresponding behavior after the parameter value of reality surpasses this threshold value.
RollbackActionThreshold	Pei Zhi parameter is provided with corresponding threshold value as required	N/A	After the parameter of reality turned back to normal value again, the operational order that sent last time may be cancelled or regain in the upper strata.
				ExecuteActionThreshold	Pei Zhi parameter is provided with corresponding threshold value as required	N/A	After the parameter of reality surpasses this threshold value, the order of certain behavior will be initiated to carry out in the upper strata.

Table 1

Wherein, the definition of described LinkParameterStatusList parameter is as shown in table 2:

Name	Type	Valid?range	Description
				LinkParameterStatusList?	Tabulation	N/A?	The tabulation LinkParameterTypeStatus of following parameters collection
LinkParameterType?	Link?Speed，Link?Bit?Error?Rate，Li?nk?Frame?Loss?Ratebefore?retransmission，Link?Signal?Strength	N/A?	The parameter type that needs configuration
				Status?	Enumerated?	Success is failed	Configuration result

Table 2

By the technical scheme of prior art one as can be seen, there is following defective in it:

Upper layer entity sends the MIH configuration order behind the MIHF entity, and the MIHF entity can't be judged the link that specifically will dispose any type according to the link parameter in the described MIH configuration order, thereby has influence on the switching of terminal in heterogeneous network.

The flow process that the incident that the prior art two relevant with the present invention provides upper layer entity by the MIHF entity bottom entity to be provided is registered, its main thought is: the registration primitive that provides by MIHF, as MIH_Event_Register, the event registration process that realizes, concrete information word have RequestedEventList, is used for showing the upper layer entity needs or interested event type.When the incident of bottom entity generation upper layer entity registration, by MIHF entity notice upper layer entity.

Can provide necessary event information to upper layer entity by prior art two, help upper layer entity to switch preparation.Yet support that the terminal of MIH function generally is a multimode terminal, the incident that is provided, information and command service generally are at different access network technologies, therefore have different requirements and function.But the prior art upper layer entity does not provide the type of Access Network, and like this, the MIHF entity can't know which Access Network these service requests are at, thereby can't carry out effective service to terminal.

Summary of the invention

The purpose of this invention is to provide a kind of method of in media-independent switching technology, selecting link fast, by the present invention, LinkType parameter during the MIHF entity can be ordered according to the MIH that upper layer entity sends is judged the link that specifically will dispose any type very soon; And in event handler procedure, upper layer entity of the present invention can provide the type of Access Network, thereby makes the MIHF entity can know that service request is the information at which Access Network, thereby can carry out effective service to terminal.

The objective of the invention is to be achieved through the following technical solutions:

The invention provides a kind of method of selecting link in media-independent switching technology fast, it comprises:

A, upper layer entity switch the MIH order by media-independent and issue at least one Linktype LinkType parameter to media-independent handoff functionality MIHF entity;

B, described MIHF entity are selected corresponding link according to described LinkType parameter.

Wherein, when upper layer entity needed the configuration link parameter, described steps A specifically comprised:

Upper layer entity is handed down to the MIHF entity by MIH link configuration request message with at least one LinkType parameter.

Wherein, when upper layer entity needed the configuration link parameter, described steps A also comprised:

Upper layer entity is handed down to the MIHF entity by MIH link configuration request message with the link parameter tabulation LinkParameterList of corresponding each LinkType parameter.

Wherein, when upper layer entity carried out the MIH event registration, described steps A specifically comprised:

Upper layer entity is handed down to the MIHF entity by the event registration request message with at least one LinkType parameter.

Wherein, when upper layer entity carried out the MIH event registration, described steps A also comprised:

Upper layer entity is handed down to the MIHF entity by the event registration request message with the list of thing of corresponding each LinkType parameter.

Wherein, when upper layer entity carried out the cancellation of MIH incident, described steps A specifically comprised:

Upper layer entity is handed down to the MIHF entity by incident de-registration request message with at least one LinkType parameter.

Wherein, when upper layer entity carried out the cancellation of MIH incident, described steps A also comprised:

Upper layer entity is handed down to the MIHF entity by incident de-registration request message with the list of thing of corresponding each LinkType parameter.

Wherein, described step B specifically comprises:

After B1, MIHF entity receive the order of upper layer entity transmission, select link corresponding, and described link is carried out the link parameter configuration according to the Linktype of described LinkType parameter identification.

Wherein, described step B also comprises:

B2, MIHF entity return described LinkType parameter to upper layer entity, and the link parameter configuration result of the Linktype link corresponding of sign;

The information that B3, described upper layer entity return according to the MIHF entity is known the parameter configuration state of the Linktype link corresponding of each LinkType parameter identification.

Wherein, described step B specifically comprises:

After B4, MIHF entity receive the registered events request message that upper layer entity sends to, select link corresponding according to the Linktype of wherein LinkType parameter identification;

Or,

After B5, MIHF entity receive the Logout Events request message that upper layer entity sends to, select link corresponding according to the Linktype of wherein LinkType parameter identification.

Wherein, described step B also comprises:

B6, MIHF entity register incident in the described list of thing to the bottom entity requests of the Access Network of described link correspondence; And when transmitting the response of bottom, carry described LinkType parameter to the event registration situation;

B7, described upper layer entity know that according to described LinkType parameter the bottom of Access Network of respective links is to the response of event registration situation;

Or,

B8, MIHF entity nullify incident in the described list of thing to the bottom entity requests of the Access Network of described link correspondence; And when transmitting the response of bottom, carry described LinkType parameter to the event registration situation;

B9, described upper layer entity know that according to described LinkType parameter the bottom of the Access Network of respective links nullifies the response of situation to incident.

Wherein, described step B also comprises:

B10, when the bottom entity of correspondence has the incident of upper layer entity registration to take place, indicate to upper layer entity by the MIHF entity, and when upper layer entity sends MIH incident indication MIH_EVENT.indication, carry described LinkType parameter at the MIHF entity;

B11, described upper layer entity are known the situation of the incident that takes place in the bottom of Access Network of respective links according to described LinkType parameter.

As seen from the above technical solution provided by the invention, because issuing at least one Linktype LinkType parameter by the MIH order, upper layer entity gives the MIHF entity among the present invention, therefore in the link parameter layoutprocedure, described MIHF entity can be selected the link of needs configuration according to described LinkType parameter; And in event handler procedure,, can make the MIHF entity learn that service request is the information at which Access Network, thereby can carry out effective service terminal by the LinkType parameter that upper layer entity provides.

Description of drawings

Fig. 1 for the position of MIHF entity in the background technology with and the schematic diagram of media-independent service is provided;

Fig. 2 is the flow chart of first embodiment provided by the invention;

Fig. 3 is the flow chart of second embodiment provided by the invention;

Fig. 4 is the flow chart of the 3rd embodiment provided by the invention.

Embodiment

First embodiment provided by the invention is when upper layer entity needs the configuration link parameter, and upper layer entity issues LinkType (Linktype) parameter by the MIH order and gives the MIHF entity; Described MIHF entity selects corresponding link to carry out the link parameter configuration according to described LinkType parameter.Specific implementation process comprises the steps: as shown in Figure 2

Step 1, upper layer entity are passed through MIH link parameter configuration request message with the LinkType parameter, and the LinkParameterList of corresponding described LinkType parameter (link parameter tabulation) is handed down to the MIHF entity.

In the step 1, upper layer entity sends the link parameter configuring request by following link parameter configuration request message to the MIH layer:

MIH_Configure_Thresholds.request(

LinkType

LinkParameterList

)

The LinkType that carries in the described link parameter configuration request message and the definition of LinkParameterList parameter are as shown in table 3:

Name	Type	Valid?range	Description
				LinkType	The chain line	Effective Linktype	The Linktype sign is with various access skills

?	?	?	Art link corresponding type (802.11,802.16,3GPP, 3GPP2 etc.)
				LinkParameterList?	Tabulation	?	The tabulation of following parameters set: LinkParameterTypeInitiateActionThreshold, RollbackActionThreshold, ExecuteActionThreshold

Table 3

After step 2, MIHF entity receive the MIH link parameter configuration request message of upper layer entity transmission, select link corresponding, and described link is carried out the link parameter configuration according to the Linktype of described LinkType parameter identification.

After the MIHF entity is received the MIH link parameter configuration request message of upper layer entity transmission, can initiate the link parameter configuration order to the respective link of this locality or far-end according to the Linktype of LinkType sign.After configuration is finished, carry out following steps:

Step 3, the MIHF entity returns described LinkType parameter to upper layer entity, and the link parameter configuration result of the Linktype link corresponding of sign.

The MIH layer entity reports upper layer entity by following message with chain line LinkType and configuration result LinkParameterStatusList.

MIH_Configure_Thresholds.confirm(

LinkType

LinkParameterStatusList

)

Wherein the definition of LinkType is with the definition unanimity among the MIH_Configure_Thresholds.request, and the definition of LinkParameterStatusList is with the prior art unanimity.

Step 4, the information that described upper layer entity returns according to the MIHF entity are known the parameter configuration result of the Linktype link corresponding of described LinkType parameter identification.

When carrying out the media-independent switching, the upper strata need be registered the incident that bottom provided by MIHF, so that provide necessary event notice when needs switch, the preparation that helps the upper strata to switch.Second embodiment provided by the invention is exactly when upper layer entity carries out the MIH event registration, and upper layer entity issues Linktype LinkType parameter by the MIH order and gives the MIHF entity; Described MIHF entity is selected corresponding link according to described LinkType parameter, and the technology of carrying out the events corresponding registration to the bottom entity of the Access Network of described link correspondence.Its specific implementation process comprises the steps: as shown in Figure 3

Step 1, upper layer entity are passed through the event registration request message with the LinkType parameter, and the list of thing of corresponding described LinkType parameter is handed down to the MIHF entity.

Upper layer entity sends MIH_Event_Register.request (request of MIH event registration) message to the MIHF entity, wherein carrying LinkType and RequestEventList parameter, described LinkType parameter is used for identifying the interested Linktype of upper layer entity; Described RequestEventList parameter is used for identifying the interested incident of upper layer entity on the corresponding described Linktype.Specific implementation primitive is:

MIH_Event_Register.request(

LinkType，

RequestEventList

)

The definition of wherein said LinkType and RequestEventList parameter is as shown in table 4:

Name	Type	Length	Value
				LinkType?	31?	Variable?	Identifier?of?link?for?which?EventRegister?was?conducted
RequestedEventLi?st?	4?	Variable?	A?rray?of?event?codes?formatted?asmessaged-id：?Event?Code1，Event?Code2，EventCode3，....

Table 4

After the MIHF entity receives the registered events request message that upper layer entity sends to, select link corresponding according to the Linktype of wherein LinkType parameter identification; Register incident in the described list of thing to the bottom entity requests of the Access Network of described link correspondence then, and when transmitting the response of bottom, carry described LinkType parameter the event registration situation.The specific implementation process is as follows:

Step 2, after the MIHF entity receives the registered events request message that upper layer entity sends to, Linktype according to wherein LinkType parameter identification is selected link corresponding, and registers incident in the described list of thing to the bottom entity requests of the Access Network of described link correspondence.

In the step 2, send the event registration request by Link_Event_Register.request message to the bottom entity of the Access Network of described link correspondence, incident in the described list of thing of request registration, carry the RequestEventList parameter in the wherein said message, be used for identifying the interested registered events of upper layer entity.

Step 3 after corresponding Access Network bottom entity is received the event registration request, according to the situation of self supporting, is returned the event registration response message to MIHF, comprises the result of each event registration.

In the step 3,, identify the result of each event registration by the ResponseEventList parameter that Link_Event_Register.confirm (link event registration response) message is carried.

Step 4, the event registration response message that the forwarding of MIHF entity is received from Access Network bottom entity is given upper layer entity, and carries described LinkType parameter when transmitting the event registration response message.

Specific implementation primitive is:

MIH_Event_Register.confirm(

LinkType，

ResponseEventList

)

LinkType wherein and ReponseEventList definition are as shown in table 5:

Name	Type	Length	Value
				LinkType?	31?	Variable?	Identifier?of?linkfor?which?Event?Register?wasconducted
ReponseEventList?	5?	Variable?	Array?of?event?codes?formatted?as?messaged-id：Event?Code1，Event?Code2，Event?Code3，....

Table 5

After event registration response message that the MIHF entity is transmitted arrived upper layer entity, described upper layer entity knew that according to described LinkType parameter the bottom of Access Network of respective links is to the response of event registration situation.

Step 5, when the bottom entity of correspondence had the incident of upper layer entity registration to take place, as Link Up, Link Down and Link Going Down sent Lin k_Event_indication (link event indication) message to the MIHF entity.

Step 6, the MIHF entity is given upper layer entity by the information of the indication of MIH_EVENT.indication (indication of MIH incident) forwards bottom entity, and carries described LinkType parameter at the MIHF entity when upper layer entity sends MIH_EVENT.indication.

Afterwards, described upper layer entity is known the situation of the incident that takes place in the bottom of Access Network of respective links according to described LinkType parameter.

In media-independent switching technology, the incident that some no longer needs also can be nullified according to the actual conditions of oneself in the upper strata, in order to avoid waste resource in event handling.The 3rd embodiment provided by the invention is to carry out the flow process that the MIH incident is nullified at upper layer entity, and its core is: upper layer entity issues Linktype LinkType parameter by the MIH order and gives the MIHF entity; Described MIHF entity is selected corresponding link according to described LinkType parameter, and carries out the events corresponding registration to the bottom entity of the Access Network of described link correspondence.Specific implementation process comprises the steps: as shown in Figure 4

Step 1, message is with the LinkType parameter, and the list of thing of corresponding described LinkType parameter is handed down to the MIHF entity by MIH_Event_Deregister.request message (MIH incident de-registration request) for upper layer entity.

Step 2, after the MIHF entity receives the Logout Events request message that upper layer entity sends to, Linktype according to wherein LinkType parameter identification is selected link corresponding, and nullifies incident in the described list of thing by Link_Event_Deregister.request message to the bottom entity requests of the Access Network of described link correspondence;

Step 3, after corresponding Access Network bottom entity is received the incident de-registration request, according to the situation of self supporting, nullify the ResponseEventList parameter that response message carries by the Link_Event_Deregister.confirm incident, return the result that each incident is nullified to MIHF.

Step 4, the event registration response message that the forwarding of MIHF entity is received from Access Network bottom entity is given upper layer entity, and carries described LinkType parameter when transmitting the event registration response message.

Afterwards, described upper layer entity knows that according to described LinkType parameter the bottom of the Access Network of respective links nullifies the response of situation to incident.

The process of the processing when only having described in the foregoing description at some links, when upper layer entity need be configured multilink, or to the bottom entity of multilink correspondence carry out event handling the time, need carry out when corresponding mutual with the MIHF entity, carry a plurality of LinkType parameters, be used for identifying respectively the link corresponding type, also need to carry LinkParameterList, LinkParameterStatusList, RequestEventList or the ResponseEventList parameter of each LinkType parameter correspondence simultaneously.

The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.

Claims (14)

1. a method of selecting link in media-independent switching technology fast is characterized in that, comprising:

A, upper layer entity switch the MIH order by media-independent and issue at least one Linktype LinkType parameter to media-independent handoff functionality MIHF entity;

B, described MIHF entity are selected corresponding link according to described LinkType parameter.

2. method according to claim 1 is characterized in that, when upper layer entity needed the configuration link parameter, described steps A specifically comprised:

Upper layer entity is handed down to the MIHF entity by MIH link configuration request message with at least one LinkType parameter.

3. method according to claim 2 is characterized in that, when upper layer entity needed the configuration link parameter, described steps A also comprised:

Upper layer entity is handed down to the MIHF entity by MIH link configuration request message with the link parameter tabulation LinkParameterList of corresponding each LinkType parameter.

4. method according to claim 1 is characterized in that, when upper layer entity carried out the MIH event registration, described steps A specifically comprised:

Upper layer entity is handed down to the MIHF entity by the event registration request message with at least one LinkType parameter.

5. method according to claim 4 is characterized in that, when upper layer entity carried out the MIH event registration, described steps A also comprised:

Upper layer entity is handed down to the MIHF entity by the event registration request message with the list of thing of corresponding each LinkType parameter.

6. method according to claim 1 is characterized in that, when upper layer entity carried out the cancellation of MIH incident, described steps A specifically comprised:

Upper layer entity is handed down to the MIHF entity by incident de-registration request message with at least one LinkType parameter.

7. method according to claim 6 is characterized in that, when upper layer entity carried out the cancellation of MIH incident, described steps A also comprised:

Upper layer entity is handed down to the MIHF entity by incident de-registration request message with the list of thing of corresponding each LinkType parameter.

8. according to claim 2 or 3 described methods, it is characterized in that described step B specifically comprises:

After B1, MIHF entity receive the order of upper layer entity transmission, select link corresponding, and described link is carried out the link parameter configuration according to the Linktype of described LinkType parameter identification.

9. method according to claim 8 is characterized in that, described step B also comprises:

B2, MIHF entity return described LinkType parameter to upper layer entity, and the link parameter configuration result of the Linktype link corresponding of sign;

The information that B3, described upper layer entity return according to the MIHF entity is known the parameter configuration state of the Linktype link corresponding of each LinkType parameter identification.

10. according to claim 4 or 5 described methods, it is characterized in that described step B specifically comprises:

After B4, MIHF entity receive the registered events request message that upper layer entity sends to, select link corresponding according to the Linktype of wherein LinkType parameter identification.

11., it is characterized in that described step B specifically comprises according to claim 6 or 7 described methods:

After B5, MIHF entity receive the Logout Events request message that upper layer entity sends to, select link corresponding according to the Linktype of wherein LinkType parameter identification.

12. method according to claim 10 is characterized in that, described step B also comprises:

B6, MIHF entity register incident in the described list of thing to the bottom entity requests of the Access Network of described link correspondence; And when transmitting the response of bottom, carry described LinkType parameter to the event registration situation;

B7, described upper layer entity know that according to described LinkType parameter the bottom of Access Network of respective links is to the response of event registration situation.

13. method according to claim 11 is characterized in that, described step B also comprises:

B8, MIHF entity nullify incident in the described list of thing to the bottom entity requests of the Access Network of described link correspondence; And when transmitting the response of bottom, carry described LinkType parameter to the event registration situation;

B9, described upper layer entity know that according to described LinkType parameter the bottom of the Access Network of respective links nullifies the response of situation to incident.

14., it is characterized in that described step B also comprises according to claim 10 or 12 described methods:

B10, when the bottom entity of correspondence has the incident of upper layer entity registration to take place, indicate to upper layer entity by the MIHF entity, and when upper layer entity sends MIH incident indication MIH_EVENT.indication, carry described LinkType parameter at the MIHF entity;

B11, described upper layer entity are known the situation of the incident that takes place in the bottom of Access Network of respective links according to described LinkType parameter.

Images