WO2009076822A1 - 用于WiMAX系统的多业务流操作的优化方法 - Google Patents

用于WiMAX系统的多业务流操作的优化方法 Download PDF

Info

Publication number
WO2009076822A1
WO2009076822A1 PCT/CN2008/073156 CN2008073156W WO2009076822A1 WO 2009076822 A1 WO2009076822 A1 WO 2009076822A1 CN 2008073156 W CN2008073156 W CN 2008073156W WO 2009076822 A1 WO2009076822 A1 WO 2009076822A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
path
target network
service flows
handover
Prior art date
Application number
PCT/CN2008/073156
Other languages
English (en)
French (fr)
Inventor
Li Chu
Jianquan Song
Ling Xu
Original Assignee
Zte Corporation
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 Corporation filed Critical Zte Corporation
Priority to US12/744,307 priority Critical patent/US8254334B2/en
Priority to JP2010534352A priority patent/JP5106637B2/ja
Priority to EP08861399.7A priority patent/EP2209266B1/en
Publication of WO2009076822A1 publication Critical patent/WO2009076822A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface
    • H04W36/142Reselecting a network or an air interface over the same radio air interface technology
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/76Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/765Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points
    • H04L47/767Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points after changing the attachment point, e.g. after hand-off
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/82Miscellaneous aspects
    • H04L47/824Applicable to portable or mobile terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016Hand-off preparation specially adapted for end-to-end data sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup

Definitions

  • the present invention relates to the field of communications, and in particular to a global interoperability for microwave access.
  • WiMAX Worldwide Interoperability for Microwave Access, referred to as WiMAX
  • NWG Network Working Group
  • the message may carry a merged resource indication (merged resource indication) field. Used to indicate whether the operation result of multiple service flows in the same request message is bound. If multiple service flows are bound, any service flow failure will cause all service flow reservation operations in the entire request message to fail.
  • FIG. 1 is a signaling flowchart of a process in a handover preparation phase when performing handover in the prior art. As shown in FIG.
  • the handover scenario is (target network) initiating an authorization key context acquisition and data channel pre-registration, in order to facilitate understanding and Description, only the flow of switching to the target network 1 is shown in FIG. 1, and it is easy to think that there may be multiple target networks in actual processing. As shown in FIG. 1, the handover scenario is (target network) initiating an authorization key context acquisition and data channel pre-registration, in order to facilitate understanding and Description, only the flow of switching to the target network 1 is shown in FIG. 1, and it is easy to think that there may be multiple target networks in actual processing. As shown in FIG.
  • the process of the handover preparation phase may include the following steps (step 11 - step 17):
  • Step 11 MS (the terminal sends an air interface handover request (MOB_MSHO-REQ) message to the Serving ASN (current service network), Initiate a switch;
  • Step 12 The current serving network sends a handover request (HO_Req) message to the one or more target networks, where the handover request (HO_Req) message includes an authenticator identifier (Authenticator ID) and an anchor network gateway identifier (Anchor ASN GW ID).
  • Step 13 Target ASN 1 (Target Network 1) initiates a context request procedure to the Authenticator ASN (Authentication Network).
  • the step 13 may be postponed until the handover action phase is re-initiated;
  • Step 14 Target ASN 1 ( The target network 1) or the Anchor ASN (the network where the data management unit is located) initiates a data channel pre-establishment process.
  • the step 14 may be deferred until the handover action phase is performed;
  • Step 15 In response to the handover request, the Target ASN 1 Send HO Rsp to Serving ASN
  • Step 16 The Serving ASN sends a MOB_BSHO-RSP (Air Interface Switching Response) message to the MS, the MOB_BSHO-RSP message including one or more networks selected for the MS to switch to the target Base station Target BS;
  • Step 17 The Serving ASN sends HO_Ack (Handover Correct Response) to Target ASN 1 (Target Network 1) to which the potential Target BS belongs.
  • HO_Ack Haandover Correct Response
  • Step 201 the Serving ASN sends a HO_Cnf (Handover Confirmation) message to the Target ASN, and the process of the handover action phase may include the following.
  • Step 201 - Step 211) Step 201: According to the protocol, the MS sends a MOB_HO-IND (Air Interface Switching Indication) message to the Serving ASN, and notifies the handover to one of the Target ASNs selected by the Serving ASN; 202. After receiving the MOB_HO-IND message, the Serving ASN sends a HO_Cnf (Handover Confirmation) message to the Target ASN selected in the previous step.
  • Step 203 The selected Target ASN sends a HO_Ack acknowledgement message to the Serving ASN.
  • Step 208 if the HO-Req or HO-Cnf message includes an Anchor ASN GW ID field, and no data channel has occurred yet The pre-registration process, the process can choose to occur at this step; if the data channel pre-registration process has occurred and the Data Delivery Trigger is included in the SF Info (service 3 ⁇ 4 ⁇ 4 information) in the Path_Prereg-Req and response messages Then, the MS immediately triggers the distribution of any service flow of the MS; Step 206, the MS initiates a network re-entry process to the selected Target ASN; Step 207, the selected Target ASN initiates a data channel registration process to the Anchor ASN; Step 208,
  • the Serving ASN sends a HO_Complete message to notify the completion of the handover; Steps 210-211, after the establishment of the selected Target ASN data channel is completed, the Anchor ASN may initiate a data channel registration process to the old Serving ASN.
  • a technical solution for introducing an optimization process of a multi-service flow binding relationship into a handover process has not been proposed.
  • SUMMARY OF THE INVENTION The present invention has been made in view of the problem that a technical solution for introducing an optimization process of a multi-service flow binding relationship to a handover process has not been proposed.
  • the main object of the present invention is to provide a microwave access system for global use.
  • An optimization method for multi-service flow operation of the interworking system which can provide a target network to select a service flow binding operation during the handover process, thereby improving multi-service flow processing.
  • an optimization method for multi-service flow operation of a microwave access global interworking system is provided.
  • the method includes: adding, in a handover request message, a path pre-registration request message, and a path registration request message, a merge resource indication, where the merge resource indication is used to indicate whether multiple service flows of the terminal are mutually bound;
  • the target network may determine whether to allow the terminal to perform handover according to the indication of the merged resource in the handover request message and whether the handover of the multiple service flows is accepted by the target network;
  • Pre-establishment processing in the case of allowing multiple service flows of the terminal to be switched from the current serving network to the target network, the merged resource indication in the path pre-registration request message and whether the data channel can be established for multiple service flows Registration, the network where the target network or the data management unit is located can determine whether the data channel between the target network and the network where the data unit is located can be pre-established; and the path establishment process allows the multiple service flows of the terminal to be switched from the current service network to the target.
  • the network where the data management unit is located can determine whether it is possible to establish a network between the target network and the data management unit. Data channel.
  • the switching request processing further includes: initiating a handover by the terminal to the current serving network or initiating a handover by the current serving network; the current serving network sends a handover request message to the target network; and the merged resource indication in the handover request message indicates the terminal If multiple service flows are bound, if some of the multiple service flows are rejected by the target network, the target network may determine that the terminal is not allowed to perform handover; if each of the multiple service flows is not Rejected by the target network, Then the target network can judge that the terminal is allowed to switch.
  • the method further includes: the target network sending a response message to the current serving network, and omitting part of the information required for the subsequent handover in the response message; the current serving network notifying the alternate target network of the handover a terminal, where the target network that rejects the terminal is not included in the candidate target network.
  • the method further includes: sending, by the target network, a path pre-registration request message to the network where the data management unit is located, or sending a path pre-registration request message to the target network by the network where the data management unit is located; If the resource merge indication in the message indicates that multiple service flows are bound to each other, if the network where the message receiver is located fails to process the path pre-registration corresponding to some of the plurality of service flows, the target network or data management The network where the unit is located determines that the data channel between the target network and the network where the data management unit is located is not allowed to be pre-established, and the path pre-establishment process is terminated; if the path corresponding to each of the multiple service flows is pre-established, This allows the data channel to be pre-established.
  • the method further includes: the target network sending the path registration request message to the network where the data management unit is located; the resource merge indication in the path registration request message indicating that the multiple service flows are bound to each other and the path pre-registration is not performed.
  • the network where the data management unit is located fails to process the path registration corresponding to some of the plurality of service flows, the network where the data management unit is located determines that the data channel with the target network is not allowed to be established, and the path establishment is terminated. Processing; if the path corresponding to each of the plurality of service flows is successfully established, the data channel is allowed to be established with the target network.
  • the method further includes: transmitting, in the handover process, a merged resource indication indicating a binding relationship of the multiple service flows of the terminal from the current service network to the target network. And indicating, by the at least one of the following: the identifier of the merged resource indicator is used in conjunction with the identifier of the service flow; the multiple service flows having the binding relationship are indicated by the merged resource with the same identifier; The information of each group of service flows in the plurality of service flows respectively sets a merge resource indication.
  • the merge resource indication in the handover request message, the path pre-registration request message, and the path registration request message indicates that the plurality of service flows are not mutually bound
  • the handover request processing, the path pre-establishment processing, and the handover request processing are performed.
  • the merge resource indication includes a merge resource requirement and a convergence sublayer type.
  • the convergence sublayer type is used to identify that the merged resource requires identification of the binding range of multiple service flows.
  • the binding scope includes: a terminal layer and a service convergence sub-layer.
  • an optimization method for multi-service flow operation of a microwave access global interworking system including: adding more in a handover request message, a path pre-registration request message, or a path registration request message
  • the traffic flow binding indication information where the multi-service flow binding indication information is used to indicate whether multiple service flows of the terminal are mutually bound
  • the handover request processing switching multiple service flows of the terminal from the current serving network to the target network And determining whether to allow the terminal to perform handover according to the multi-service flow binding indication information in the handover request message and whether the handover of the multiple service flows is accepted by the target network; the path pre-establishment processing, allowing multiple service flows of the terminal to be In the case that the current monthly network is switched to the target network, the multi-service flow binding indication information in the path pre-registration request message and whether the data channel pre-registration can be established for multiple service flows can be determined whether the target network can be pre-established.
  • the service flow establishes a data channel registration, and determines whether a data channel between the target network and the network where the data management unit is located can be established.
  • FIG. 1 is a signaling flow chart processed in a handover preparation phase according to the related art
  • FIG. 2 is a signaling flow chart processed in a handover action phase according to the related art
  • FIG. 3 is a flowchart according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of an optimization method for multi-service flow operation of a microwave access global interworking system according to Embodiment 2 of the present invention; FIG. .
  • the information about whether the multi-service flow is bound to the target network is sent in the handover process, and the target network is selected to determine the service flow binding operation.
  • Embodiment 1 In an embodiment of the present invention, an optimization method for multi-service flow operation of a microwave access global interworking system is provided.
  • 3 is a method for optimizing multi-service flow operation for a microwave access global interworking system according to an embodiment of the present invention. As shown in FIG. 3, the method includes steps S302-S308, and detailed steps are described below. .
  • Step S302 in the handover request (HO_Req) message, the path pre-registration iZ, the request (Path Prereg Req) message, and the path en route request (Path_Reg_Req) message, the enhancement port merges the resource indication, and the merge resource indication is used to indicate Whether the multiple service flows of the terminal are mutually bound, and the merged resource indication may include a merged resource requirement and a convergence sublayer type, where the merged resource requirement is used to identify whether multiple service flows are bound, when indicating multiple services When a flow is bound, the failure of any one of the service flows results in the following: The request for the predetermined operation of all the flows of the layer in the request is rejected; otherwise, when the multiple service flows are not bound, one is represented.
  • the failure of the service flow only affects itself, and does not affect the operation result of other service flows in the request.
  • the convergence sub-layer type is used to identify the binding scope of the multiple service flows.
  • the binding scope here includes: Terminal level and business convergence sub-level.
  • the above-mentioned combined resource indications can be expressed in the following three ways: (1) The identifier of the merged resource indicator is used in conjunction with the identifier of the service flow, that is, the information of all the service flows is carried in one message, The binding identifier of the merged resource is used in conjunction with the identifier of the service flow; (2) The multiple service flows having the binding relationship use the merged resource indications with the same identifier, that is, the information of all the service flows is carried in one message.
  • Step S304 the handover request processing, when the multiple service flows of the terminal are switched from the current serving network to the target network, the target network according to the combined resource indication in the HO-Req message and whether the switching of the multiple service flows is accepted by the target network, Determine whether the terminal is allowed to switch.
  • the current serving network may send the HO_Req message to the target network after receiving the handover message from the terminal, or may send the HO_Req message to the target network after the current serving network initiates the handover, and the merge carried in the HO-Req message. If the resource indication indicates that multiple service flows of the terminal are bound, if some of the multiple service flows are rejected by the target network, the target network may determine that the terminal is not allowed to perform the handover. At this time, the target network provides the current service.
  • the network sends a response message, and omits part of the information required for the subsequent handover in the response message; the current serving network informs the terminal of the alternate target network that is handed over, wherein the candidate target network does not include the target network that previously rejected the terminal; Each of the multiple service flows is not rejected by the target network, and the target network can determine that the terminal is allowed to perform the handover.
  • Step S306 the path pre-establishment process, in the case that the multiple service flows of the terminal are allowed to be switched from the current serving network to the target network, the network where the target network or the data management unit is located according to the merged resource indication in the Path_Prereg_Req message and Whether data channel pre-registration can be established for multiple service flows can determine whether the data channel between the target network and the network where the data management unit is located can be pre-established.
  • This step S306 may be performed during the handover preparation phase, or may be performed during the handover action phase, or may not be performed.
  • the target network may send a Path_Prereg_Req message to the network where the data management unit is located, or the network where the data management unit is located may send a Path_Prereg_Req message to the target network.
  • the resource merge indication in the Path_Prereg_Req message indicates that multiple service flows are mutually bound, if the network where the message receiver is located fails to process the path pre-registration corresponding to some of the plurality of service flows, The network where the target network or data management unit is located is judged not to be pre-built.
  • Step S308 the path establishment process, in the case that the plurality of service flows of the terminal are allowed to be switched from the current service network to the target network, and the path pre-registration process is not performed, the network where the target network or the data management unit is located is based on Path-Reg.
  • the indication of the merged resource in the Req message and whether it is possible to establish a data channel registration for multiple service flows can determine whether a data channel between the target network and the network where the data management unit is located can be established.
  • a data channel between the target network and the network where the data management unit is located can be established.
  • Target ASN 1 target network 1
  • Target ASN 1 is shown in FIG. 1
  • Target ASN 1 is taken as an example for processing other Target ASNs.
  • the processing of Target ASN 1 is similar.
  • at least one service flow is rejected by Target ASN 1.
  • the processing of the above scenario includes the following steps (step 11 - step 17): Step 11, the MS (terminal) sends to the Serving ASN (current service network)
  • Step 12 Serving ASN sends HO-Req message to one or more Target ASNs, the HO-Req message includes Authenticator ID and Anchor ASN GW ID (4 Miaoding access service network gateway identifier), and whether multiple service flows are bound to the indication; Step 13, if multiple service flows are marked as binding, then only one service flow is Target ASN
  • Target ASN 1 can decide to reject all the service flows of the MS according to the binding indication; then the subsequent context request process and the data channel pre-establishment process of step 14 below do not need to be initiated for Target ASN 1; Binding, the same as the original 3 ⁇ 43 ⁇ 4, Target ASN 1 initiates a context request procedure to the Authenticator ASN; Step 14: The target ASN 1 or the Anchor ASN initiates a data channel pre-establishment process; if there is no binding, the original process is the same; Step 15: The Target ASN 1 sends a HO-Rsp message to the Serving ASN to confirm the handover request; Labeled as Binding, Bay) The HO-Rsp message may not contain the following information: Data Path Info, HO ID (Handover Indicator), Service Level Prediction (Service Level Prediction), HO Process Optimization (Handover Optimization) , HO Authorization Policy Support, Action Time; Data Integrity Info; and BS HO RSP Code can be determined to reject the following information: Data
  • the MOB BSHO-RSP message includes a potential switchable target BS (target base station) selected by the one or more networks for the MS, and if the multiple service flows are marked as bound, the Target ASN 1 is not included; Step 17, Serving The ASN sends the HO_Ack to the Target ASN (alternative target network) to which all potential target BSs belong. If multiple service flows are marked as binding, the above target ASN 1 is not included in the candidate target network.
  • target base station target base station
  • the handover scenario is the AK context acquisition and the data channel pre-registration initiated by the Target ASN
  • the multiple service flows of the MS are originally bound
  • the MS switches from ASN a to ASN b due to the previous The handover message does not bring the information bound to the MS multi-service flow to ASN b, so the ASN b default MS multi-service flow is not bound.
  • the MS switches again at ASN b there is a flow in which ASN b will become the Serving ASN accordingly.
  • at least one service flow is rejected by the Target ASN 1, the network environment shown in FIG.
  • Step 11 In the same process as the original process, the MS sends a MOB_MSHO-REQ message to the Serving ASN. Initiating a handover, the step is the same as step 11 in the prior art; Step 12, the Serving ASN sends an HO Req message to one or more Target ASNs, the message includes an Authenticator ID and an Anchor ASN GW ID; if the Serving ASN fails to access the other network If the binding information of the multi-service flow is obtained, the HO_Req message will not include whether the multiple service flows are bound or not. The default is not bound.
  • Step 13 As long as one service flow is rejected by the Target ASN 1, according to the multiple services of the MS, the target relationship is the binding relationship, and the target ASN 1 smashes all the services of the MS, and the subsequent context request process and the data channel of the step 14 are pre-processed.
  • the establishment process does not need to be initiated for the target ASN 1, that is, directly to the step 15; and because the binding relationship information is lost in the previous handover, the Serving ASN in the current handover considers that the multi-service flow of the MS has no binding relationship.
  • the error processing is performed.
  • the target ASN 1 initiates a context request process to the Authenticator ASN, and proceeds to step 14.
  • step 14 the target ASN 1 or the Anchor ASN initiates a data channel pre-establishment process; if not, the same
  • the original process is as follows: Step 15: The Target ASN 1 sends a HO Rs message to the Serving ASN to confirm the handover request.
  • the HO_Rsp message may not include the following information required for subsequent handover processing: Data Path Info, HO ID (Switch ID), Service Level Prediction, HO Process Op Timization (switching process optimization), HO Authorization Policy Support, Action Time, Data Integrity Info; and BS HO RSP Code can be determined as rejected
  • the Serving ASN considers that the multi-service flow of the MS has no binding relationship in the current handover, and the information is the same as the original process. .
  • Step 16 The Serving ASN sends a MOB BSHO-RSP message to the MS, where the MOB BSHO-RSP message includes a potential switchable target BS selected by the one or more networks for the MS; if multiple service flow binding relationships are performed according to the MS
  • the message does not include the above-mentioned Target ASN 1; however, since the binding relationship information is lost in the previous handover, the Serving ASN in the current handover considers that the multi-service of the MS has no binding relationship, the message may include The foregoing Target ASN 1 ; Step 17, the Serving ASN sends the HO_Ack to the ASN where the potential target BS is located, and the potential Target ASN may include the Target ASN 1 described above.
  • the multi-service flow in the request ( Path_Prereg_Req/Path_Reg_Req ) is a binding relationship, and includes the following steps (step 201 - step 211 ): Step 201: The MS sends a MOB_HO-IND (air interface switching indication) to the Serving ASN. The notification is switched to one of the Target ASNs selected by the Serving ASN.
  • MOB_HO-IND air interface switching indication
  • Step 202 After receiving the MOB_HO-IND message, the Serving ASN sends a HO_Cnf message to the selected Target ASN.
  • Step 203 Selecting the Target ASN to Serving The ASN sends a HO_Ack acknowledgment message; Step 204, if the HO_Req or HO_Cnf (Handover Acknowledgement) message includes an Authenticator ID field, and in the previous handover preparation phase, the AK context corresponding to the MS is not obtained, the selection The Target ASN will initiate a context request procedure to the Authenticator ASN to request an AK context for the MS.
  • Step 205 if the data channel pre-registration process occurs during the handover action phase, according to an embodiment of the present invention, the Path-Prereg-Req multi-service If the flow binding indicates that the data path establishment failure of the at least one service flow fails, the Target ASN or the Anchor ASN notifies the other party that the data channel pre-delivery establishment fails in the Path_Prereg_Rsp message, and Even if the Data Delivery Trigger field is included in the SF Info in Path-Prereg-Req and the response message, it is not touched.
  • Step 206 the MS initiates a network re-entry process to the Target ASN;
  • Step 207 the Target ASN initiates a data channel registration process to the Anchor ASN.
  • FIG. 4 is a flowchart of the optimization method. As shown in FIG. 4, the following steps are included. (Step S402 - Step S408): Step S402, adding the multi-service flow binding indication information to the handover request message, the path pre-registration request message, or the path registration request message, where the multi-service flow binding indication information is used to indicate the terminal Whether multiple business flows are bound to each other.
  • Step S404 the handover request processing, when the plurality of service flows of the terminal are switched from the current serving network to the target network, whether the multi-service flow binding indication information in the handover request message and the handover of the multiple service flows are targeted
  • the network accepts and judges whether the terminal is allowed to switch.
  • Step S406 the path pre-establishment process, in the case of allowing the multiple service flows of the terminal to be switched from the current serving network to the target network, according to the multi-service flow binding indication information in the path pre-registration request message and whether it is possible to
  • the service flow establishes a pre-registration of the data channel, and determines whether the data channel between the target network and the network where the data management unit is located can be pre-established.
  • Step S408 the path establishment process, in the case that the plurality of service flows of the terminal are allowed to be switched from the current serving network to the target network, and the path pre-registration process is not performed, according to the multi-service flow binding indication information in the path registration request message And whether it is possible to establish a data channel registration for multiple service flows, and determine whether a data channel between the target network and the network where the data management unit is located can be established.
  • the foregoing multi-service flow binding indication information may be the combined resource indication in the foregoing Embodiment 1. It can be seen from the above description that the above steps S404 to S408 are similar to the above-mentioned S304-S308, and are not mentioned here.
  • the multi-service flow binding indication information is carried in the handover.
  • Request message or path pre-registration request message, or path registration request message.
  • AK Authorization Key
  • Anchor ASN and Serving ASN are co-configured and R4 (Reference Point 4) data channel pre-registers the scenario initiated by Anchor ASN/Serving ASN; and Anchor ASN and Serving ASN is configured together, And the data channel pre-registration message is merged into the scenario sent in the handover control message; the scenario initiated by the network-initiated handover, and the like. And, for network-initiated handover, initiated by Serving ASN or Serving ASN/Authenticator ASN (when configured together). It should be noted that in the above scenario, except for the network-initiated handover, other scenarios are handovers initiated by the MS.
  • the target network can directly make a decision on the handover request of multiple service flows without acquiring the information from the network element that retains the merged resource information or transmitting the handover request information to the network.
  • the yuan is then judged by the network element. Therefore, the resource overhead of the related information interaction is saved, and the complete delivery of the original service flow binding information is also ensured.
  • the present invention is applicable to other handover action phase scenarios in addition to the scenarios described above for the handover action phase.
  • the Target ASN does not receive the HO_Cnf of the R4 (reference point 4); the Serving ASN does not receive the MOB MSHO-REQ message; the Anchor ASN, the Authenticator ASN and the Serving ASN are configured together, and the Serving ASN initiates the channel registration.
  • the selection of the decision of the target network for the service flow binding operation can be provided during the handover process, which overcomes the deficiencies in the prior art in the case of multiple service flows; and ensures that the terminal after one handover The integrity of the original service flow binding information avoids the errors that may result in multi-service flow processing.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

用于 WiMAX系统的多业务流操作的优化方法 技术领域 本发明涉及通信领域, 并且特别地, 涉及一种用于微波接入全球互通
( Worldwide Interoperability for Microwave Access , 简称为 WiMAX ) 系统的 多业务流操作的优化方法。 背景技术 在 WiMAX无线通信系统中,可以同时为一个用户提供多个业务流的月 务。 WiMAX 允许将多个业务流的操作请求携带在一个消息中。 在网络工作 组 (Network Working Group, 简称为 NWG, 其是 WiMAX标准组织的其中 一个工作组, 负责 WiMAX系统网络技术相关工作) 标准中, 消息中可以携 带有合并资源指示 (合并资源指示) 字段, 用于表示同一个请求消息中多个 业务流的操作结果是否绑定。 如果多个业务流绑定, 则任一个业务流失败都 会导致整个请求消息中所有的业务流预定操作失败;如果多个业务流不绑定, 则任一个业务流失败只会影响自身的预定结果;如果没有合并资源指示字段, 则默认多个业务流没有绑定。 在切换过程中同样会涉及到多个业务流的处理。 在现有的 NWG 标准 中, 对于切换请求消息的定义中并没有包含合并资源指示字段, 这样可能会 导致终端在一次切换后, 原有的业务流绑定信息丢失。 在业务流绑定信息丢 失的情况下, 如果需要重新获得丢失的信息, 则需要进行相应的处理, 这增 加了信令流量。 图 1是现有技术中进行切换时切换准备阶段的处理的信令流程图,如图 1 所示, 切换场景为 (目标网络) 发起授权密钥上下文获取和数据通道预登 记, 为了便于理解和描述, 图 1中仅示出了向目标网络 1切换的流程, 而容 易想到, 在实际处理过程中, 可能会存在多个目标网络。 如图 1所示,切换准备阶段的处理可包括以下步骤(步骤 11一步骤 17 ): 步骤 11 : MS (终端向 Serving ASN (当前服务网络)发送空口切换请 求 ( MOB— MSHO-REQ ) 消息, 发起切换; 步骤 12: 当前服务网络向一个或多个目标网络发送切换请求( HO— Req ) 消息, 该切换请求( HO_Req ) 消息包括鉴别器标识( Authenticator ID )和锅 定网络网关标识 ( Anchor ASN GW ID ); 步骤 13 : Target ASN 1 (目标网络 1 )向 Authenticator ASN (鉴权网络) 发起上下文请求流程, 在具体实施过程中, 该步骤 13 可以推迟至切换行动 阶段再发起; 步骤 14: Target ASN 1 (目标网络 1 )或 Anchor ASN (数据管理单元所 在网络)发起数据通道预建立流程, 在具体实施过程中, 该步骤 14 可以推 迟至切换行动阶段再执行; 步骤 15 : 响应于切换请求, Target ASN 1向 Serving ASN发送 HO Rsp
(切换响应) 消息; 步骤 16: Serving ASN向 MS发送 MOB— BSHO-RSP (空口切换响应) 消息, 该 MOB— BSHO-RSP消息包括一个或多个网络为 MS选择的 在的可 切换到的目标基站 Target BS; 步骤 17: Serving ASN向潜在的 Target BS所属的 Target ASN 1 (目标 网络 1 ) 发送 HO_Ack (切换正确应答)。 此外,若 MS的多个业务流原为绑定关系,当 MS从 ASN a切换到 ASN b后, 由于先前的切换消息并没有将该 MS多业务流绑定的信息带给 ASN b, 所以 ASN b默认 MS的多业务流没有绑定。 这样可能会导致终端的多个业务 流绑定信息在发生一次切换后就丢失。 因此, 才艮据现有技术, 当 MS在 ASN b再次发生切换时, 所执行的处 理与图 1所示的处理相同, 只是 ASN b修改为相应的 Serving ASN。 此外,现有 NWG对 Path— Prereg— Req(路径预登己请求)和 Path— Reg— Req (路径登记请求) 的定义中不包括合并资源指示字段, 这样, 对于多业务流 操作请求, 不能保证切换后原有业务流绑定信息完整传递, 这并不利于目标 网络对于多业务流的判决优化。 图 2是现有技术中进行切换时切换行动阶段的处理的信令流程图,如图 2所示, Serving ASN向 Target ASN发送 HO— Cnf (切换确认 ) 消息, 切换行 动阶段的处理可包括以下步骤 (步骤 201―步骤 211 ): 步骤 201 , 才艮据协议规定, MS向 Serving ASN发送 MOB— HO-IND (空 口切换指示)消息,通知切换到 Serving ASN所选择的 Target ASN中的一个; 步骤 202, Serving ASN接收到 MOB— HO-IND消息后, 向上一步选择 的 Target ASN发送 HO_Cnf (切换确认 ) 消息; 步骤 203 , 上述选择的 Target ASN 向 Serving ASN发送 HO— Ack确认 消息; 步骤 204, 若 HO— Req或 HO— Cnf消息包含鉴别器标识 ( Authenticator
ID ), 且在之前的切换准备阶段, 对应 MS的 4吏权密钥 (Authentication Key, 简称为 AK ) 上下文并没有被获取, 则上述选择的 Target ASN 就会向 Authenticator ASN (鉴权器所在网络)发起上下文请求流程, 为 MS请求 4受 权密钥 (AK ) 上下文; 步骤 205 , 若 HO— Req或 HO— Cnf消息包含 Anchor ASN GW ID (锚定 网络网关标识) 字段, 且还没有发生数据通道预登记流程, 则该流程可选择 在这一步发生; 若数据通道预登记流程已发生且在 Path— Prereg— Req 和响应 消息中的 SF Info(业务¾¾信息)中包括 Data Delivery Trigger(数据分发触发 ), 则立即触发 MS任何业务流的分发; 步骤 206 , MS发起向上述选择的 Target ASN的网络重进入流程; 步骤 207, 上述选择的 Target ASN向 Anchor ASN发起数据通道登记流 程; 步骤 208 , 在网络重进入成功完成后, 上述选择的 Target ASN 发起 CMAC Key Count (基于密码的消息鉴定码密钥计数 ) 更新流程; 步骤 209 , 在网络重进入成功完成后, 上述选择的 Target ASN 可向
Serving ASN发送 HO— Complete (切换完成) 消息通知切换完成; 步骤 210-211 ,在与上述选择的 Target ASN数据通道建立完成后, Anchor ASN可向旧的 Serving ASN发起数据通道去登记流程。 目前,尚未提出将多业务流绑定关系的优化处理引入到切换过程的技术 方案。 发明内容 考虑到目前尚未提出将多业务流绑定关系的优化处理引入到切换过程 的技术方案的问题而做出本发明, 为此, 本发明的主要目的在于提供一种用 于微波接入全球互通系统的多业务流操作的优化方法, 该方法可在切换过程 中提供目标网络对业务流绑定操作的选择, 从而完善了多业务流处理。 根据本发明的一方面,提供了一种用于微波接入全球互通系统的多业务 流操作的优化方法。 该方法包括: 在切换请求消息、 路径预登记请求消息、 和路径登记请求 消息中增加合并资源指示, 其中, 合并资源指示用于表示终端的多个业务流 是否相互绑定; 切换请求处理,在将终端的多个业务流从当前服务网络切换至目标网络 时, 目标网络可根据切换请求消息中的合并资源指示以及多个业务流的切换 是否被目标网络接受, 判断是否允许终端进行切换; 路径预建立处理,在允许将终端的多个业务流从当前服务网络切换到目 标网络的情况下, 才艮据路径预登记请求消息中的合并资源指示以及是否能够 对多个业务流建立数据通道预登记, 目标网络或数据管理单元所在网络可判 断是否能够预建立目标网络与数据单元所在网络之间的数据通道; 以及 路径建立处理,在允许将终端的多个业务流从当前服务网络切换到目标 网络, 并且未进行路径预登记处理的情况下, 根据路径登记请求消息中的合 并资源指示以及是否能够对多个业务流建立数据通道登记, 数据管理单元所 在网络可判断是否能够建立目标网络与数据管理单元所在网络之间的数据通 道。 其中, 在切换请求处理中, 进一步包括: 由终端向当前服务网络发起切 换或者由当前服务网络发起切换; 当前服务网络向目标网络发送切换请求消 息; 在切换请求消息中的合并资源指示表示终端的多个业务流为绑定的情况 下, 如果多个业务流中的部分业务流被目标网络拒绝, 则目标网络可以判断 不允许终端进行切换;如果多个业务流中的每个业务流均未被目标网络拒绝, 则目标网络可以判断允许终端进行切换。 并且, 在不允许终端进行切换的情 况下, 进一步包括: 目标网络向当前服务网络发送响应消息, 并在响应消息 中省略后续切换所需的部分信息; 当前服务网络将切换的备选目标网络告知 终端, 其中, 备选目标网络中不包括拒绝终端的目标网络。 另外, 在路径预建立处理中, 进一步包括: 目标网络向数据管理单元所 在网络发送路径预登己请求消息、 或者由数据管理单元所在网络向目标网络 发送路径预登记请求消息; 在路径预登记请求消息中的资源合并指示表示多 个业务流相互绑定的情况下, 如果消息接收方所在网络在处理对应于多个业 务流中的部分业务流的路径预登记时失败, 则目标网络或数据管理单元所在 网络判断不允许预建立目标网络与数据管理单元所在网络之间的数据通道, 并终止路径预建立处理; 如果对应于多个业务流中每个业务流的路径预登己 建立均成功, 则允许预建立该数据通道。 此外, 在路径建立处理中, 进一步包括: 目标网络将路径登记请求消息 发送至数据管理单元所在网络; 在路径登记请求消息中的资源合并指示表示 多个业务流相互绑定并且未进行路径预登记的情况下, 如果数据管理单元所 在网络在处理对应于多个业务流中的部分业务流的路径登记时失败, 则数据 管理单元所在网络判断不允许建立与目标网络的数据通道, 并终止路径建立 处理; 如果对应于多个业务流中每个业务流的路径登己建立均成功, 则允许 与目标网络建立数据通道。 并且, 在该方法中, 进一步包括: 在切换过程中将指示终端的多个业务 流的绑定关系的合并资源指示从当前服务网络传递给目标网络。 以及, 合并资源指示的表示方式包括以下至少之一: 合并资源指示的标 识与业务流的标识配合使用; 具有绑定关系的多个业务流使用具有相同的标 识的合并资源指示; 具有绑定关系的多个业务流中的每一组业务流的信息分 别设置合并资源指示。 除此之外, 在切换请求消息、 路径预登记请求消息、 和路径登记请求消 息中的合并资源指示表示多个业务流未相互绑定的情况下, 则进行切换请求 处理、 路径预建立处理、 和路径建立处理, 之后触发多个业务流处理。 其中, 合并资源指示中包含合并资源要求和汇聚子层类型。 并且, 汇聚子层类型用 于标识合并资源要求对多个业务流的绑定范围进行标识。 其中, 绑定范围包 括: 终端层面和业务汇聚子层面。 根据本发明的又一方面,提供了一种用于微波接入全球互通系统的多业 务流操作的优化方法, 包括: 在切换请求消息、 路径预登记请求消息、 或路 径登记请求消息中添加多业务流绑定指示信息, 其中, 多业务流绑定指示信 息用于表示终端的多个业务流是否相互绑定; 切换请求处理, 在将终端的多 个业务流从当前服务网络切换至目标网络时, 根据切换请求消息中的多业务 流绑定指示信息以及多个业务流的切换是否被目标网络接受, 判断是否允许 终端进行切换; 路径预建立处理, 在允许将终端的多个业务流从当前月 务网 络切换到目标网络的情况下, 才艮据路径预登记请求消息中的多业务流绑定指 示信息以及是否能够对多个业务流建立数据通道预登记, 判断是否能够预建 立目标网络与数据管理单元所在网络之间的数据通道; 路径建立处理, 在允 许将终端的多个业务流从当前服务网络切换到目标网络, 并且未进行路径预 登记处理的情况下, 才艮据路径登记请求消息中的多业务流绑定指示信息以及 是否能够对多个业务流建立数据通道登记, 判断是否能够建立目标网络与数 据管理单元所在网络间的数据通道。 通过本发明的上述技术方案,通过在切换过程中提供目标网络对业务流 绑定操作进行判决的选择, 克服了现有技术中在多业务流情况下的不足; 同 时保证了终端在一次切换后原有业务流绑定信息的完整性, 避免了由此可能 导致的多业务流处理的错误。 附图说明 图 1是根据相关技术的在切换准备阶段中处理的信令流程图; 图 2是根据相关技术的在切换行动阶段中处理的信令流程图; 图 3 是根据本发明实施例一的用于微波接入全球互通系统的多业务流 操作的优化方法的流程图; 图 4 是根据本发明实施例二的用于微波接入全球互通系统的多业务流 操作的优化方法的流程图。 具体实施方式 功能相克述 在本发明实施例提供的技术方案中,通过在切换过程中将多业务流是否 绑定的信息发送到目标网络, 提供目标网络对业务流绑定操作进行判决的选 择, 保证了终端在一次切换后原有业务流绑定信息的完整性, 避免了由此可 能导致的对于多业务流处理的错误。 下面将参考附图并结合实施例, 来详细说明本发明。 需要说明的是, 如 果不沖突, 本申请中的实施例以及实施例中的特征可以相互组合。 实施例一 在本发明实施例中,提供了一种用于微波接入全球互通系统的多业务流 操作的优化方法。 图 3是根据本发明实施例的用于微波接入全球互通系统的 多业务流操作的优化方法, 如图 3所示, 该方法包括步骤 S302—步骤 S308 , 以下对各步骤进行详细的 4 述。 步骤 S302 , 在切换请求 ( HO— Req ) 消息、 路径预登 iZ,请求 ( Path Prereg Req ) 消息、 和路径登己请求 ( Path_Reg_Req ) 消息中增力口合 并资源指示, 该合并资源指示用于表示终端的多个业务流是否相互绑定, 合 并资源指示中可以包含有合并资源要求和汇聚子层类型, 其中, 合并资源要 求用于对多个业务流是否绑定进行标识, 当表示多个业务流绑定时, 表示任 何一个业务流的失败都导致如下结果: 对该请求中该层面的所有流的预定操 作的请求被全部拒绝; 否则, 当表示多个业务流不绑定时, 表示一个业务流 的失败只影响其本身, 不影响该请求中其它业务流的操作结果; 汇聚子层类 型用于标识合并资源要求对多个业务流的绑定范围进行标识, 这里的绑定范 围包括: 终端层面和业务汇聚子层面。 在 HO Req消息、 Path— Prereg— Req消息、 和 Path— Reg— Req消息中的合 并资源指示表示多个业务流未相互绑定的情况下, 进行切换请求处理、 路径 预建立处理、 和路径建立处理, 之后触发多个业务流处理。 在切换过程中, 合并资源指示从当前服务网络传递到目标网络。 上述合并资源指示可以有以下三种表示方式: (一) 合并资源指示的标 识与业务流的标识配合使用, 即, 所有业务流的信息在一个消息中携带, 同 时合并资源的绑定标识与业务流的标识配合使用; (二)具有绑定关系的多个 业务流使用具有相同的标识的合并资源指示, 即, 所有业务流的信息在一个 消息中携带, 且具有绑定关系的多个业务流使用相同的绑定标记, 用于识别 这一组具有相互绑定关系的业务流; (三)具有绑定关系的多个业务流中的每 一组业务流的信息分别设置合并资源指示, 即, 具有绑定关系的多个业务流 中的每一组业务流的信息分别设置在一个消息中, 并配合合并资源的绑定标 识共同表示这组业务流的绑定关系。 步骤 S304, 切换请求处理, 在将终端的多个业务流从当前服务网络切 换至目标网络时, 目标网络根据 HO— Req消息中的合并资源指示以及多个业 务流的切换是否被目标网络接受, 判断是否允许终端进行切换。 具体地,当前服务网络可以接收来自终端的发起切换消息后向目标网络 发送 HO— Req 消息, 也可以当前服务网络自行发起切换后向目标网络发送 HO_Req消息, 在携带在 HO— Req消息中的合并资源指示表示终端的多个业 务流被绑定的情况下, 如果多个业务流中的部分业务流被目标网络拒绝, 则 目标网络可以判断不允许终端进行切换, 此时, 目标网络向当前服务网络发 送响应消息, 并在响应消息中省略后续切换所需的部分信息; 当前服务网络 将切换的备选目标网络告知终端, 其中, 备选目标网络中不包括之前拒绝了 终端的目标网络; 如果多个业务流中的每个业务流均未被目标网络拒绝, 则 目标网络可以判断允许终端进行切换。 步骤 S306, 路径预建立处理, 在允许将终端的多个业务流从当前服务 网络切换到目标网络的情况下, 目标网络或数据管理单元所在网络根据 Path— Prereg— Req 消息中的合并资源指示以及是否能够对多个业务流建立数 据通道预登记, 可以判断是否能够预建立目标网络与数据管理单元所在网络 之间的数据通道。 该步骤 S306 可能在切换准备阶段执行, 也可能在切换行 动阶段执行, 也可能不执行。 在路径预建立处理中, 可以是目标网络向数据管理单元所在网络发送 Path— Prereg— Req 消息, 也可以是数据管理单元所在网络向目标网络发送 Path— Prereg— Req消息。 在 Path— Prereg— Req消息中的资源合并指示表示多个业务流相互绑定的 情况下, 如果消息接收方所在网络在处理对应于多个业务流中的部分业务流 的路径预登记时失败, 则目标网络或数据管理单元所在网络判断不允许预建 立目标网络和数据管理单元所在网络之间的数据通道, 并终止路径预建立处 理; 如果消息接收方所在网络在处理对应于多个业务流中每个业务流的路径 预登记建立均成功, 则允许预建立该数据通道。 步骤 S308 , 路径建立处理, 在允许将终端的多个业务流从当前服务网 络切换到目标网络, 并且未进行路径预登记处理的情况下, 目标网络或数据 管理单元所在网络才艮据 Path— Reg— Req 消息中的合并资源指示以及是否能够 对多个业务流建立数据通道登记, 可以判断是否能够建立目标网络与数据管 理单元所在网络之间的数据通道。 由以上描述可以看出, 在切换请求处理、 路径预建立处理、 和路径建立 处理过程中, 如果业务流相互绑定, 则只要有一个业务流被拒绝或失败, 则 与之绑定的其它业务流的切换、 路径预建立、 和路径建立结果同样是失败。 下面将结合具体场景对本发明进行描述。 首先基于图 1所示的网络环境对切换准备阶段进行描述。 切换场景为 Target ASN (目标网络)发起 AK上下文获取和数据通道预 登记。如图 1所示, 由于不考虑其他 Target ASN的情况, 图 1中仅示出 Target ASN 1 (目标网络 1 ), 这里也仅以 Target ASN 1为例进行描述, 对于其它的 Target ASN的处理与 Target ASN 1的处理类似。 殳定, 至少有一个业务流被 Target ASN 1拒绝。 此时, 上述场景的处理 包括以下步骤 (步骤 11一步骤 17 ): 步骤 11 , MS (终端 ) 向 Serving ASN ( 当前服务网络) 发送
MOB MSHO-REQ消息, 发起切换, 该步骤与现有技术中的步骤 11相同; 步骤 12 , Serving ASN向一个或多个 Target ASN发送 HO— Req消息, 该 HO— Req消息包括 Authenticator ID和 Anchor ASN GW ID ( 4苗定接入业务 网络网关标识), 以及多个业务流是否绑定标示; 步骤 13 ,若多个业务流标示为绑定,则只要有一个业务流被 Target ASN
1拒绝, 则 Target ASN 1就可才艮据该绑定标示判定, 拒绝该 MS所有业务流; 则后续上下文请求流程和以下步骤 14的数据通道预建立流程对 Target ASN 1 啫不必发起; 若没有绑定, 则同原有¾¾程, Target ASN 1向 Authenticator ASN 发起上下文请求流程; 步骤 14 , Target ASN 1或 Anchor ASN发起数据通道预建立流程; 若没 有绑定, 则同原有流程; 步骤 15 , Target ASN 1向 Serving ASN发送 HO—Rsp消息确认切换请求; 若多个业务流标示为绑定, 贝) HO—Rsp消息可以不包含如下信息: Data Path Info (数据通道信息), HO ID (切换标识), Service Level Prediction (业务等 级预报 ), HO Process Optimization (切换处理优化 ), HO Authorization Policy Support (切换 4受权策略支持 ), Action Time (操作时间;), Data Integrity Info (数据完整性信息); 且 BS HO RSP Code (基站切换响应码 ) 可以确定为拒 绝切换; 步骤 16 , Serving ASN 向 MS 发送 MOB BSHO-RSP 消息, 该
MOB BSHO-RSP消息包括一个或多个网络为 MS选择的潜在的可切换到的 target BS(目标基站),如果多个业务流标示为绑定,则不包括上述 Target ASN 1 ; 步骤 17 , Serving ASN向所有潜在的 target BS所属的 Target ASN (备选 的目标网络) 发送 HO— Ack, 如果多个业务流标示为绑定, 则备选的目标网 络中不包括上述 Target ASN 1。 此外, 在切换场景为 Target ASN发起的 AK上下文获取和数据通道预 登记的情况下, 如果 MS的多个业务流本来为绑定关系, 则当 MS从 ASN a 切换到 ASN b后, 由于先前的切换消息并没有将该 MS多业务流绑定的信息 带给 ASN b , 因此 ASN b默认 MS的多业务流没有绑定。 当 MS在 ASN b 再次发生切换时, 会有如下流程, 其中, ASN b将相应地成为 Serving ASN。 同样, 支设至少有一个业务流被 Target ASN 1拒绝的情况, 基于图 1 所示的网络环境, 包括以下步骤: 步骤 11 , 同原有流程, MS向 Serving ASN发送 MOB— MSHO-REQ消 息, 发起切换, 该步骤与现有技术中的步骤 11相同; 步骤 12 , Serving ASN向一个或多个 Target ASN发送 HO Req消息, 消息包括 Authenticator ID和 Anchor ASN GW ID; 若 Serving ASN未能从其 他网元处获取到多业务流的绑定信息, 则 HO_Req消息将不包括多个业务流 是否绑定标示, 默认为不绑定; 步骤 13 , 只要有一个业务流被 Target ASN 1拒绝, 按照该 MS的多个 业务 ¾ϊ本来为绑定关系, Target ASN 1 巨绝该 MS的所有业务 则后续上 下文请求流程和步骤 14的数据通道预建立流程对 Target ASN 1都不必发起, 即直接转入步骤 15; 而由于该绑定关系信息在先前的切换中丢失, 导致当前 切换中 Serving ASN认为, 该 MS的多业务流没有绑定关系, 进入错误的处 理, 同协议原有流程, Target ASN 1向 Authenticator ASN发起上下文请求流 程, 转入步骤 14; 步骤 14 , Target ASN 1或 Anchor ASN发起数据通道预建立流程; 若没 有绑定, 则同原有流程; 步骤 15 , Target ASN 1向 Serving ASN发送 HO Rs 消息确认切换请求; 如果按照该 MS多个业务流绑定关系, 则 HO— Rsp消息可以不包含以下后续 切换处理所需的信息: Data Path Info (数据通道信息), HO ID (切换标识), Service Level Prediction (业务水平预报 ), HO Process Optimization (切换处 理优化 ), HO Authorization Policy Support (切换授权策略支持 ), Action Time (操作时间), Data Integrity Info (数据完整性信息); 且 BS HO RSP Code (基 站切换响应码) 可以确定为拒绝切换; 但是, 由于该绑定关系信息在先前的 切换中丢失, 导致当前切换中 Serving ASN认为该 MS的多业务流没有绑定 关系, 则同原有流程, 消息所带信息与原有流程一样。 步骤 16 , Serving ASN 向 MS 发送 MOB BSHO-RSP 消息, 该 MOB BSHO-RSP消息包括一个或多个网络为 MS选择的潜在的可切换到的 target BS; 如果按照该 MS多个业务流绑定关系, 则该消息不包括上述 Target ASN 1; 但是, 由于该绑定关系信息在先前的切换中丢失, 导致当前切换中 Serving ASN认为, 该 MS的多业务 ¾ϊ没有绑定关系, 则该消息可能包括上 述 Target ASN 1 ; 步骤 17 , Serving ASN向潜在的 target BS所在的 ASN发送 HO— Ack , 潜在的 Target ASN中可能包括上述 Target ASN 1。 接下来将基于图 2 所示的网路环境对切换行动阶段的处理过程进行描 述, !设切换场景为 Serving ASN向 Target ASN发送 HO— Cnf消息, 并且数 据通道粒度为每业务流, 且数据通道请求 ( Path_Prereg_Req/Path_Reg_Req ) 中多业务流为绑定关系, 包括以下步骤(步骤 201—步骤 211 ): 步骤 201 , MS向 Serving ASN发送 MOB_HO-IND (空口切换指示)消 息通知切换到 Serving ASN所选择的 Target ASN中的一个; 步骤 202, Serving ASN接收到 MOB— HO-IND消息后, 向选择的 Target ASN 发送 HO— Cnf消息; 步骤 203 , 选择的 Target ASN 向 Serving ASN发送 HO— Ack确认消息; 步骤 204 ,若 HO— Req或 HO— Cnf (切换确认 )消息包含 Authenticator ID 字段, 且在之前的切换准备阶段, 对应该 MS的 AK上下文并没有被获取, 该选择的 Target ASN就会向 Authenticator ASN发起上下文请求流程, 为该 MS请求 AK上下文; 步骤 205 , 如果数据通道预登记流程若在切换行动阶段发生, 根据本发 明实施例, Path— Prereg— Req中多业务流绑定标示如果是绑定关系并且^ 1设有 至少一个业务流的数据通道建立失败, 则 Target ASN 或 Anchor ASN 在 Path— Prereg— Rsp 消息中通知对方数据通道预登己建立失败, 并且, 即使在 Path— Prereg— Req和响应消息中的 SF Info中包括 Data Delivery Trigger字段, 也不触发该 MS任何业务流的分发; 如果成功预建立数据通道, 则执行以下 处理; 步骤 206 , MS发起向该 Target ASN的网络重进入流程; 步骤 207,该 Target ASN向 Anchor ASN发起数据通道登记流程;其中, 在数据通道粒度为每业务流、 且数据通道请求 ( Path— Reg— Req ) 中多业务流 为绑定的情况下, 如果在数据通道建立前未进行数据通道预登记, 则发生三 方握手的数据通道建立流程:当任一个业务流对应的数据通道建立被拒绝时, 如果 Path— Reg— Req 中多业务流绑定标示为绑定关系, 贝l Anchor ASN 在 Path— Reg— Rsp消息中通知 Target ASN数据通道登己建立失败; 步骤 208 , 在网络重进入成功后, Target ASN发起 CMAC Key Count ( CMAC密钥计数 ) 更新流程; 步骤 209 , 在网络重进入成功后, Target ASN 向 Serving ASN 发送
HO— Complete (切换完成) 消息通知切换完成; 步骤 210-211 , 在与 Target ASN数据通道建立完成后, Anchor ASN可 向先前的 Serving ASN发起数据通道去登记流程。 实施例二 在本发明实施例中,提供了一种用于微波接入全球互通系统的多业务流 操作的优化方法, 图 4是该优化方法的流程图, 如图 4所示, 包括以下步骤 (步骤 S402—步骤 S408 ): 步骤 S402, 在切换请求消息、 路径预登记请求消息、 或路径登记请求 消息中添加多业务流绑定指示信息, 其中, 多业务流绑定指示信息用于表示 终端的多个业务流是否相互绑定。 步骤 S404, 切换请求处理, 在将终端的多个业务流从当前服务网络切 换至目标网络时, 才艮据切换请求消息中的多业务流绑定指示信息以及多个业 务流的切换是否被目标网络接受, 判断是否允许终端进行切换。 步骤 S406, 路径预建立处理, 在允许将终端的多个业务流从当前服务 网络切换到目标网络的情况下, 根据路径预登记请求消息中的多业务流绑定 指示信息以及是否能够对多个业务流建立数据通道预登记, 判断是否能够预 建立目标网络与数据管理单元所在网络之间的数据通道。 步骤 S408 , 路径建立处理, 在允许将终端的多个业务流从当前服务网 络切换到目标网络, 并且未进行路径预登记处理的情况下, 根据路径登记请 求消息中的多业务流绑定指示信息以及是否能够对多个业务流建立数据通道 登记, 判断是否能够建立目标网络与数据管理单元所在网络间的数据通道。 优选地,上述多业务流绑定指示信息可以是上述实施例一中的合并资源 指示。 由以上描述可以看出, 上述步骤 S404到步骤 S408与上述 S304—步骤 S308类似, 这里不再赞述; 另外, 与实施例一不同的是, 这里的多业务流绑 定指示信息是携带在切换请求消息、 或路径预登记请求消息、 或路径登记请 求消息中。 本领域技术人员应当理解, 除了以上描述的场景之外, 本发明同样适用 于切换准备阶段的其它应用场景, 例如, 授权密钥(AK )上下文由当前服务 的接入网发送、 目标接入网发起数据通道预登记的场景;锚定接入网(Anchor ASN )与( Serving ASN )共同配置且 R4(参考点 4 )数据通道预登记由 Anchor ASN/Serving ASN发起的场景; 以及 Anchor ASN与 Serving ASN共同配置、 且数据通道预登记消息合到切换控制消息中发送的场景; 网络发起的切换的 场景等。 并且, 对于 网 络发起的切换, 由 Serving ASN 或 Serving ASN/Authenticator ASN (共同配置时) 发起。 应当注意, 在上述场景中, 除特别注明网络发起的切换外, 其它场景都 是由 MS发起的切换。 不难看出, 通过增加合并资源指示, 目标网络能够对多个业务流的切换 请求直接作出判决, 而不需要从保留该合并资源信息的网元处获取该信息或 者将切换请求信息传递给该网元再由该网元作出判决。 因此节省了相关信息 交互的资源开销, 同时也保证了原有业务流绑定信息的完整传递。 另夕卜, 除以上描述的切换行动阶段的描述的场景之外, 本发明还适用于 其它切换行动阶段场景。例如, Target ASN未收到 R4(参考点 4 )的 HO— Cnf; Serving ASN未收到 MOB MSHO-REQ消息; Anchor ASN , Authenticator ASN 与 Serving ASN共同配置, Serving ASN发起通道登记等。 借助于本发明的技术方案,可在切换过程中提供目标网络对业务流绑定 操作进行判决的选择, 克服了现有技术中在多业务流情况下的不足; 同时保 证了终端在一次切换后原有业务流绑定信息的完整性, 避免了由此可能导致 的对于多业务流处理的错误。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种用于微波接入全球互通系统的多业务流操作的优化方法, 其特征在 于, 包括:
在切换请求消息、 路径预登记请求消息、 和路径登记请求消息中添 加合并资源指示, 其中, 所述合并资源指示用于表示终端的多个业务流 是否相互绑定;
切换请求处理,在将所述终端的多个业务流从当前月 务网络切换至 目标网络时, 才艮据所述切换请求消息中的合并资源指示以及所述多个业 务流的切换是否被所述目标网络接受,判断是否允许所述终端进行切换; 路径预建立处理,在允许将所述终端的多个业务流从所述当前服务 网络切换到所述目标网络的情况下, 根据所述路径预登记请求消息中的 合并资源指示以及是否能够对所述多个业务流建立数据通道预登记, 判 断是否能够预建立所述目标网络与数据管理单元所在网络之间的数据通 道;
路径建立处理,在允许将所述终端的多个业务流从所述当前月 务网 络切换到所述目标网络, 并且未进行所述路径预登记处理的情况下, 根 据所述路径登记请求消息中的合并资源指示以及是否能够对所述多个业 务流建立数据通道登记, 判断是否能够建立所述目标网络与数据管理单 元所在网络间的数据通道。
2. 才艮据权利要求 1所述的优化方法, 其特征在于, 在所述切换请求处理中, 进一步包括:
由所述终端向所述当前服务网络发起切换或者由所述当前服务网 络发起切换;
所述当前服务网络向所述目标网络发送所述切换请求消息; 在所述切换请求消息中的合并资源指示表示所述终端的所述多个 业务流为绑定的情况下, 如果所述多个业务流中的部分业务流被所述目 标网络拒绝, 则所述目标网络判断不允许所述终端进行切换; 如果所述 多个业务流中的每个业务流均未被所述目标网络拒绝, 则所述目标网络 判断允许所述终端进行切换。
3. 根据权利要求 2所述的优化方法, 其特征在于, 在不允许所述终端进行 切换的情况下, 进一步包括:
所述目标网络向所述当前服务网络发送响应消息,并在所述响应消 息中省略后续切换所需的部分信息;
所述当前月 务网络将切换的备选目标网络告知所述终端, 其中, 所 述备选目标网络中不包括拒绝所述终端的所述目标网络。
4. 才艮据权利要求 1所述的优化方法, 其特征在于, 在所述路径预建立处理 中, 进一步包括:
所述目标网络向数据管理单元所在网络发送所述路径预登记请求 消息、 或者由数据管理单元所在网络向所述目标网络发送所述路径预登 己请求消息;
在所述路径预登记请求消息中的资源合并指示表示所述多个业务 流相互绑定的情况下, 如果所述目标网络或所述数据管理单元所在网络 在处理对应于所述多个业务流中的部分业务流的路径预登己时失败, 则 所述目标网络或数据管理单元所在网络判断不允许预建立所述目标网络 与所述数据管理单元所在网络之间的数据通道, 并终止所述路径预建立 处理; 如果对应于所述多个业务流中每个业务流的路径预登己建立均成 功, 则允许预建立所述数据通道。
5. 才艮据权利要求 1所述的优化方法, 其特征在于, 在所述路径建立处理中, 进一步包括:
所述目标网络将所述路径登记请求消息发送至数据管理单元所在 网络;
在所述路径登记请求消息中的资源合并指示表示所述多个业务流 相互绑定并且未进行路径预登记的情况下, 如果所述数据管理单元所在 网络在处理对应于所述多个业务流中的部分业务流的路径登记时失败, 则所述数据管理单元所在网络判断不允许建立与所述目标网络的数据通 道, 并终止所述路径建立处理; 如果对应于所述多个业务流中每个业务 流的路径登记建立均成功, 则允许与所述目标网络建立数据通道。
6. 才艮据权利要求 1所述的优化方法, 其特征在于, 进一步包括: 在切换过程中将指示所述终端的多个业务流的绑定关系的合并资 源指示从所述当前服务网络传递给所述目标网络。
7. 根据权利要求 1所述的优化方法, 其特征在于, 所述合并资源指示的表 示方式包括以下至少之一:
所述合并资源指示的标识与业务流的标识配合使用; 具有绑定关系的多个业务流使用具有相同的标识的合并资源指示; 具有绑定关系的多个业务流中的每一组业务流的信息分别设置合 并资源指示。
8. 根据权利要求 1至 7中任一项所述的优化方法, 其特征在于, 在所述切 换请求消息、 所述路径预登记请求消息、 和所述路径登记请求消息中的 合并资源指示表示所述多个业务流未相互绑定的情况下, 则进行所述切 换请求处理、 所述路径预建立处理、 和所述路径建立处理, 之后触发所 述多个业务流处理。
9. 根据权利要求 1至 7中任一项所述的优化方法, 其特征在于, 所述合并 资源指示中包含所述合并资源要求和汇聚子层类型。
10. 根据权利要求 9所述的优化方法, 其特征在于, 所述汇聚子层类型用于 标识所述合并资源要求对所述多个业务流的绑定范围进行标识。
11. 根据权利要求 10所述的优化方法, 其特征在于, 所述绑定范围包括: 终 端层面和业务汇聚子层面。
12. 一种用于微波接入全球互通系统的多业务流操作的优化方法, 其特征在 于, 包括:
在切换请求消息、 路径预登记请求消息、 或路径登记请求消息中添 加多业务流绑定指示信息, 其中, 所述多业务流绑定指示信息用于表示 终端的多个业务流是否相互绑定;
切换请求处理,在将所述终端的多个业务流从当前月 务网络切换至 目标网络时, 才艮据所述切换请求消息中的多业务流绑定指示信息以及所 述多个业务流的切换是否被所述目标网络接受, 判断是否允许所述终端 进行切换; 路径预建立处理,在允许将所述终端的多个业务流从所述当前服务 网络切换到所述目标网络的情况下, 根据所述路径预登记请求消息中的 多业务流绑定指示信息以及是否能够对所述多个业务流建立数据通道预 登记, 判断是否能够预建立所述目标网络与数据管理单元所在网络之间 的数据通道;
路径建立处理,在允许将所述终端的多个业务流从所述当前月 务网 络切换到所述目标网络, 并且未进行所述路径预登记处理的情况下, 根 据所述路径登记请求消息中的多业务流绑定指示信息以及是否能够对所 述多个业务流建立数据通道登记, 判断是否能够建立所述目标网络与数 据管理单元所在网络间的数据通道。
PCT/CN2008/073156 2007-11-23 2008-11-21 用于WiMAX系统的多业务流操作的优化方法 WO2009076822A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US12/744,307 US8254334B2 (en) 2007-11-23 2008-11-21 Optimization method of multiple service flows operation for WiMAX system
JP2010534352A JP5106637B2 (ja) 2007-11-23 2008-11-21 WiMAXシステムに用いるマルチプルサービスストリーム操作の最適化方法
EP08861399.7A EP2209266B1 (en) 2007-11-23 2008-11-21 Optimization method of multiple service flows operation for wimax system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710187727.5 2007-11-23
CN2007101877275A CN101442734B (zh) 2007-11-23 2007-11-23 用于WiMAX系统的多业务流操作的优化方法

Publications (1)

Publication Number Publication Date
WO2009076822A1 true WO2009076822A1 (zh) 2009-06-25

Family

ID=40726944

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073156 WO2009076822A1 (zh) 2007-11-23 2008-11-21 用于WiMAX系统的多业务流操作的优化方法

Country Status (5)

Country Link
US (1) US8254334B2 (zh)
EP (1) EP2209266B1 (zh)
JP (1) JP5106637B2 (zh)
CN (1) CN101442734B (zh)
WO (1) WO2009076822A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013522990A (ja) * 2010-03-17 2013-06-13 ゼットティーイー コーポレーション オーセンティケータリロケーション要求の処理方法及びシステム
EP2475199A4 (en) * 2009-08-31 2016-06-15 Zte Corp TRANSFER METHOD AND SERVICE FOR SERVICE ACCESS NETWORK

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998529B (zh) * 2009-08-21 2014-06-11 中兴通讯股份有限公司 一种避免切换后终端能力窄化的方法及系统
CN102065515B (zh) * 2010-12-02 2014-07-02 中兴通讯股份有限公司 WiMAX系统中通知终端移动性限制拒绝的方法、装置及系统
CN102184231A (zh) * 2011-05-12 2011-09-14 广州市动景计算机科技有限公司 获取页面资源的方法及装置
US9338694B2 (en) 2014-06-16 2016-05-10 Freescale Semiconductor, Inc. Wireless communication system with SIPTO continuity

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1845527A (zh) * 2005-11-02 2006-10-11 华为技术有限公司 在微波接入全球互通系统中提供组播业务的方法及系统
US20070165709A1 (en) * 2005-12-02 2007-07-19 Qualcomm Incorporated Time slicing techniques for variable data rate encoding
CN101043440A (zh) * 2006-03-25 2007-09-26 华为技术有限公司 一种WiMAX网络中支持多业务流操作的方法

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7061896B2 (en) * 2000-09-20 2006-06-13 George Mason Intellectual Properties, Inc. Wireless label switched packet transfer network
US20040085957A1 (en) * 2002-11-01 2004-05-06 Sanjeev Verma Apparatus and method for providing IP connectivity to mobile nodes during handover
JP4199603B2 (ja) 2003-06-11 2008-12-17 株式会社エヌ・ティ・ティ・ドコモ 移動通信システムおよび制御局
KR101084113B1 (ko) * 2004-03-05 2011-11-17 엘지전자 주식회사 이동통신의 핸드오버에 적용되는 서비스 정보 전달 방법
US7957348B1 (en) * 2004-04-21 2011-06-07 Kineto Wireless, Inc. Method and system for signaling traffic and media types within a communications network switching system
JP2008507217A (ja) * 2004-07-16 2008-03-06 ブリッジポート ネットワークス, インコーポレイテッド セルラー電話通信及びインターネットプロトコル電話通信のための存在検出及びハンドオフ
KR100680749B1 (ko) * 2004-11-05 2007-02-08 삼성전자주식회사 이종 무선 네트워크를 사용하는 셀룰러 통신 시스템에서의핸드오버 장치 및 방법
US7369856B2 (en) * 2004-11-24 2008-05-06 Intel Corporation Method and system to support fast hand-over of mobile subscriber stations in broadband wireless networks
JP5096324B2 (ja) * 2005-06-01 2012-12-12 ▲ホア▼▲ウェイ▼技術有限公司 ワイヤレス通信システムにおいてサービス品質保証を提供するための方法及びシステム
FR2891979B1 (fr) * 2005-10-10 2008-10-24 Evolium Sas Soc Par Actions Si Procede pour ameliorer les transferts inter-cellulaires dans les systemes cellulaires de radiocommunications mobiles
US8064948B2 (en) * 2006-01-09 2011-11-22 Cisco Technology, Inc. Seamless roaming for dual-mode WiMax/WiFi stations
SG171641A1 (en) 2006-05-03 2011-06-29 Interdigital Tech Corp Wireless communication method and system for activating multiple service bearers via efficient packet data protocol context activation procedures
US7852817B2 (en) * 2006-07-14 2010-12-14 Kineto Wireless, Inc. Generic access to the Iu interface
US20080039086A1 (en) * 2006-07-14 2008-02-14 Gallagher Michael D Generic Access to the Iu Interface
US7912004B2 (en) * 2006-07-14 2011-03-22 Kineto Wireless, Inc. Generic access to the Iu interface
WO2008087521A1 (en) * 2007-01-15 2008-07-24 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for providing circuit switched domain services over a packet switched network
FI20075297A0 (fi) * 2007-04-27 2007-04-27 Nokia Siemens Networks Oy Menetelmä, radiojärjestelmä ja tukiasema
ATE546971T1 (de) * 2007-09-13 2012-03-15 Interdigital Tech Corp Verfahren und vorrichtung für bidirektionales handover
US8045525B1 (en) * 2007-10-02 2011-10-25 Nortel Networks, Limited Handover data integrity in a wireless data network
US20090265542A1 (en) * 2008-04-18 2009-10-22 Amit Khetawat Home Node B System Architecture
US8165091B2 (en) * 2008-06-27 2012-04-24 Nix John A Efficient handover of media communications in heterogeneous IP networks using LAN profiles and network handover rules
WO2012050845A1 (en) * 2010-09-28 2012-04-19 Research In Motion Limited Residential/enterprise network connection management and handover scenarios

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1845527A (zh) * 2005-11-02 2006-10-11 华为技术有限公司 在微波接入全球互通系统中提供组播业务的方法及系统
US20070165709A1 (en) * 2005-12-02 2007-07-19 Qualcomm Incorporated Time slicing techniques for variable data rate encoding
CN101043440A (zh) * 2006-03-25 2007-09-26 华为技术有限公司 一种WiMAX网络中支持多业务流操作的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2209266A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2475199A4 (en) * 2009-08-31 2016-06-15 Zte Corp TRANSFER METHOD AND SERVICE FOR SERVICE ACCESS NETWORK
JP2013522990A (ja) * 2010-03-17 2013-06-13 ゼットティーイー コーポレーション オーセンティケータリロケーション要求の処理方法及びシステム
US8732799B2 (en) 2010-03-17 2014-05-20 Zte Corporation Method and system for processing authenticator relocation request

Also Published As

Publication number Publication date
JP5106637B2 (ja) 2012-12-26
EP2209266A4 (en) 2012-11-21
JP2011504695A (ja) 2011-02-10
CN101442734A (zh) 2009-05-27
CN101442734B (zh) 2010-12-29
US20100284369A1 (en) 2010-11-11
EP2209266A1 (en) 2010-07-21
US8254334B2 (en) 2012-08-28
EP2209266B1 (en) 2017-01-04

Similar Documents

Publication Publication Date Title
JP7031944B2 (ja) 通信方法、ソース基地局、ターゲット基地局、コアネットワークデバイス、および端末デバイス
CN110945892B (zh) 安全实现方法、相关装置以及系统
EP2123088B1 (en) Apparatus and method providing auxillary handover command
US7710924B2 (en) Method of supporting media independent handover with resource management function in a mobile communication system
KR101737425B1 (ko) 응급 콜을 지원하는 이동 통신 시스템에서 보안 관리 방법 및 장치와 그 시스템
JP5421274B2 (ja) 異種無線アクセスネットワーク間におけるハンドオーバー方法
WO2009030164A1 (fr) Procédé, système et dispositif pour empêcher l'attaque par dégradation pendant qu'un terminal se déplace
US20110078442A1 (en) Method, device, system and server for network authentication
JP2012095305A (ja) リンク障害復旧のためのハンドオーバー方法とこの方法を具現するための無線機器及び基地局
WO2009076822A1 (zh) 用于WiMAX系统的多业务流操作的优化方法
CN101616408A (zh) 密钥衍生方法、设备及系统
WO2013159638A1 (zh) 跟踪区域更新后保持用户设备业务连续性的方法及装置
WO2009021442A1 (fr) Procédé et système pour maintenir la communication de schéma de compression d'en-tête robuste en continu
WO2009152656A1 (zh) 用户设备转移时密钥身份标识符的生成方法和生成系统
WO2017193387A1 (zh) 异制式小区间切换的方法及装置
WO2008009230A1 (fr) Procédé et système de traitement du déplacement de l'interface r3 dans un réseau d'interopérabilité mondiale pour l'accès micro-ondes
WO2012071833A1 (zh) 一种切换中选择目标基站的方法及系统
WO2011020388A1 (zh) 一种家用基站的切换类型控制方法和系统
WO2010108397A1 (zh) 用户管理和状态保持方法、装置及系统
WO2009052731A1 (en) A switching validate message processing method
CN102083037B (zh) 进入空闲模式的方法、网络切换方法、通信系统及设备
CN110830996B (zh) 一种密钥更新方法、网络设备及终端
CN108124514A (zh) 一种csfb的回落结果检测方法及装置、计算机存储介质
CN102300275B (zh) 通信过程中的切换方法和本地路由控制功能实体
WO2011150629A1 (zh) 一种基站间快速切换的方法和基站

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: 08861399

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 12744307

Country of ref document: US

Ref document number: 2010534352

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2008861399

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2008861399

Country of ref document: EP