WO2008001447A1

WO2008001447A1 - Mobile communication method and mobile communication device

Info

Publication number: WO2008001447A1
Application number: PCT/JP2006/313003
Authority: WO
Inventors: Yuji Tazaki
Original assignee: Fujitsu Limited
Priority date: 2006-06-29
Filing date: 2006-06-29
Publication date: 2008-01-03

Abstract

Provided is a mobile communication device which is arranged as a BS (104) for an MS (103) to perform handover-enabled communication by the WiMAX communication. The mobile communication device includes generation means for generating setting information which correlates a unique identifier of the MS (103) to a unique identifier of an ASN-GW (102) as an anchor of the MS (103) when the MS (103) makes an entry to a CSN (101). Moreover, the mobile communication device includes transmission means for transmitting the setting information generated by the generation means by putting the information on a primitive information element upon handover based on the movement of the MS (103).

Description

Specification

Mobile communication method and mobile communication device

Technical field

TECHNICAL FIELD [0001] The present invention relates to a mobile communication method and a mobile communication device, and more particularly, to a mobile communication method and a mobile communication device with improved control during handover by a WiMAX communication method.

Background art

[0002] Conventionally, handover (HO) control in a mobile communication system includes a configuration that controls transfer on an IP address (see, for example, Patent Document 1 below). There is a configuration that performs packet transfer by definition (for example, see Patent Document 2 below.) _{0 In} addition, at the time of data transmission, a data packet including a message is used to execute a transaction between the mobile terminal device and the gateway. (For example, refer to Patent Document 3 below.) ₀ These conventional technologies do not realize handover control via a specific node to be realized by the Wi MAX Forum.

[0003] WiMAX is based on the 802.16e technology and is a standard specification for supporting mobile communication networks. In the current WiMAX, there are multiple handono (HO) methods as options. FIG. 16 is a diagram showing an overall configuration of a mobile communication system in WiMAX.

[0004] The WiMAX system is roughly divided into three nodes: CSN (Core Service Network) 1001, ASN (Access Service Network) 1002, and MS (Mobile Station) 1003. ASN—GW stands for ASN (Gate Way). When communicating with a CN (Correspondent Node) 1010 outside of the MS1003 WiM AX system, the MS1003 uses a data path (DP: Data Path) 1026 configured on R6 between the BS (Base Station) 1004 and the ASN1002. , And the IP packet to CN1010 via MIP session 1023 (within the MIP tunnel) configured on R3 between ASN1002 and CSN1001. FIG. 17 is a diagram showing a data path setting state during MS movement. This shows the status when the MS 1003 moves and moves beyond the BS1004 area managed by one ASN1002. If MS1003 moves in the X direction across different ASN1002s (R4 movement between ASN1002a and 1002b), ASN1002a itself will move until ASN (Anchor ASN) 1002ai that has been communicating and functions as an anchor Without setting, DP1024 is set on R4 between ASN1002a and 1002b (association of R3 and R4), and the destination ASN1002 b force is also set to DP1026b on R6 (association of R4 and R6). The moved MS 1003 communicates with the destination BS 1004b using general-purpose ARQ (Automatic Repeat Request) control and device identification ID (CID / SFID).

[0006] HO-Request (HO- Req) is one of the important primitives used when the MS 1003 moves. FIG. 18 is a table showing primitive information elements. As shown in Table 1100, typical IE (information elements) defined by HO-Request include Target BSID, Serving BSID, and Anchor GWID.

[0007] Anchor GWID 1101 is used as an ID (identifier) and indicates Anchor ASN 1002a or Anchor DP 1026a. HO means that MS1003 is handed over to Target BSID (BS1 004b). For this reason, if it does not go through Anchor ASN1002a, the Primitive transfer will be the Target BSID of IE or Serving B SID described in HO—Request (HO—Req) ZHO—Response (HO—Rsp) It can be easily done just by transferring to, but this causes the problem [b] described later.

[0008] In WiMAX, it is an option (undeveloped state) for Primitive to pass through Anchor ASN, and the content of processing related to actual transfer is not stipulated in the standard specification. In WiMAX, the transfer process that considers the implementation status is different from the exchange formats using existing technology and SIP, so processing that specifically considers the implementation is required.

Patent Document 1: Japanese Unexamined Patent Application Publication No. 2006-80690

Patent Document 2: Japanese Patent Laid-Open No. 2006-74379

Patent Document 3: Japanese Translation of Special Publication 2003-515280

Disclosure of the invention Problems to be solved by the invention

[0010] However, in the standard specification of WiMAX that is currently standardized, the following problems occur when performing handover (HO).

[a] According to WiMAX standard specifications, BS generates Primitive including IE called Anchor ASN (Anchor GWID)! /, but it is not concrete! /.

[B] In the handover method, in which the control signal does not pass through Anchor ASN (Anchor GWID, ie Anchor DP) between the interfaces called R4ZR6, the R4 DP (data path) that carries the user data ) Will be linked together. FIG. 19 is a diagram for explaining problems with the conventional technology. As shown in the figure, when the movement of MS1003 is a movement across a plurality of AS N1002, R4 which is DP1024 between Anchor ASN1002a and the destination ASN1002c becomes a daisy chain. If this R4 path becomes longer, there will be a problem that packet delay and communication quality will be affected.

[C] HO—Passing user data through Anchor ASN (that is, Anchor DP) with only IE defined in Request is impossible by standard description alone.

[d] HO—Passing user data through Anchor AS N (that is, Anchor DP) with only the IE defined in Response is impossible with the standard description alone.

[0013] The present invention has been made in view of the above, and can perform primitive transfer via the ASN of the anchor, resulting in a decrease in service quality during WiMAX handover! The object of the present invention is to provide a mobile communication method and a mobile communication device.

Means for solving the problem

[0014] In order to solve the above-described problems and achieve the object, the present invention provides a mobile communication method for allowing a mobile station to perform handover with a WiMAX communication method, wherein the mobile station is a network. When the base station that communicates with the mobile station enters the configuration information that associates the unique identifier of the mobile station with the unique identifier of the access management device that is an anchor for the mobile station. The production | generation process to produce | generate is included, It is characterized by the above-mentioned.

[0015] According to the above configuration, when a mobile station enters the network, it is possible to associate the correspondence between the mobile station and the anchor access control device. Thus, after this, the mobile station Primitives at the time of a nodeover that has moved can be transferred via the anchor access management device.

The invention's effect

[0016] According to the present invention, the mobile station and the anchor access control device can be associated with each other, so that the primitive at the time of handover based on the movement of the mobile station can be transferred via the anchor access control device. Become. Thus, there is an effect that each device constituting the system can smoothly and efficiently execute necessary handover processing when the mobile station moves.

Brief Description of Drawings

FIG. 1 is a diagram showing a system configuration of a mobile communication apparatus according to Embodiment 1 of the present invention.

[FIG. 2] FIG. 2 is a sequence diagram showing processing of each component unit for temporary entry.

FIG. 3 is a diagram showing a setting table for Anchor GWID.

FIG. 4 is a diagram showing a state at the time of handover of an MS.

FIG. 5 is a diagram showing a state of handover.

FIG. 6 is a diagram showing an example in which a handover request does not pass through the anchor ASN

FIG. 7 is a diagram showing an example in which a handover request passes through an anchor ASN.

[FIG. 8] FIG. 8 is a flowchart showing a procedure for transferring a hand-on request in the ASN-GW.

FIG. 9 is a diagram illustrating an example in which a handover response passes through an anchor ASN.

FIG. 10 is a flowchart showing a handover response transfer procedure in the ASN-GW.

[FIG. 11-1] FIG. 11 1 is a sequence diagram showing the transfer process of each unit on data paths R4 and R6 (part 1).

[FIG. 11-2] FIG. 11 2 is a sequence diagram showing transfer processing of each unit on data paths R4 and R6 (part 2).

FIG. 12 is a flowchart showing a data-nos setting preparation process. FIG. 13 is a flowchart showing a data path setting process.

FIG. 14 is a diagram showing a data path switching state before and after handover.

[Fig. 15-1] Fig. 15-1 is a diagram showing all states of DP setting (part 1).

[Fig. 15-2] Fig. 15-2 shows all states of DP setting (part 2).

[Fig. 15-3] Fig. 15-3 shows all states of DP setting (No. 3).

[Fig. 15-4] Fig. 15-4 shows all states of DP setting (No. 4).

[Fig. 15-5] Fig. 15-5 shows the entire DP setting status (No. 5).

FIG. 16 is a diagram showing an overall configuration of a mobile communication system in WiMAX.

FIG. 17 is a diagram showing a data path setting state during MS movement.

FIG. 18 is a table showing primitive information elements.

FIG. 19 is a diagram for explaining problems with the prior art.

Explanation of symbols

[0018] 101 CSN

102 ASN-GW

103 MS

104 BS

110 CN

300 Setting table

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, preferred embodiments of a mobile communication method and a mobile communication device according to the present invention will be described in detail with reference to the accompanying drawings. The present invention relates to processing at the time of handover in WiMAX, and has the following characteristic configuration corresponding to the problems [a] to [d] described above.

[0020] [a] When MS enters or reentry to the network (at the time of initial before HO), SFA (Service Flow Authorization) in ASN-GW in the sequence called Pre-Provisioned or BS RR—Request is sent to SFM (Service Flow Management) as a resource reservation primitive (synonymous with message). Mock When setting a new CID (Connection ID), the SFA in the ASN—GW sends a similar Primitive (message) to the SFM. Although there is no IE that sets Anchor G WID in RR—Request, since it can be uniquely determined as a system, Anchor GWID for MS is set by this Primitive.

[0021] [b] Anchor ASN (Anchor DP) force When data packets are transmitted to the MS via multiple DPs, there is a possibility that network delay and quality degradation may occur. Limit the number of data paths from MS to MS to a maximum of 2DP.

[c] Since only the IE defined in the HO—Request cannot pass the HO—Request through the Anchor ASN (Anchor DP), transfer logic including information of the lower layer (IP layer) is used.

[d] Since only the IE defined in HO—Response cannot pass HO—Response via Anchor AS N (Anchor DP), transfer logic including lower layer information is used.

[0022] (Embodiment 1)

FIG. 1 is a diagram showing a system configuration of a mobile communication apparatus according to Embodiment 1 of the present invention. This is the overall configuration of the mobile communication system in WiMAX shown in Fig. 1, and each component is arranged in the same way as the conventional technology (see Fig. 16). This shows the state of the initial entry (Network entry) to the network by the MS. FIG. 2 is a sequence diagram showing the processing of each component unit for temporary entry. This will be described with reference to FIG. 1 and FIG. In the following, the handover request (Request) is abbreviated as Req, and the response (Response) is abbreviated as Rsp.

[0023] The WiMAX system includes CSN101, ASN-GW102, and MS103 nodes. 110 is CN and 104 is BS. ASN-GW 102 is called an access management device, BS is a base station, and MS is a mobile station.

[0024] MS103 (MSID = MS1) performs network entry. The MS 103 receives the authentication of the CSN 101 via the BS 104 (BSID = B1) and the ASN—GW 102 (ASN—GWID = A1) (S 101). Pre- Provisioned Service Flow Creation When PD-Rsp can be set, Anchor AS for the unique identifier (MSID) of MS103 N—The unique identifier of GW102 Anchor GWID is set as ASN—GW102 that has transmitted PD-Rsp. That is, the BS 104 performs PD-Req (Sl 02) on the ASN-GW 102, and the ASN-GW 102 performs PD-Req (S103) on the CSN 101. Thereafter, the ASN-GW 102 that has received the PD-Rsp (S104) from the CSN 101 sends the PD-Rsp to the BS 104 (S105). At this time, the BS 104 sets Anchor GWID (S106).

FIG. 3 is a diagram showing an anchor GWID setting table. BS104 (BSID = BS1) is the Anchor GWID = A1 indicating that the ASN—GW102 that received the PD—Rsp (S105) response to PD-Req (S102) is the anchor of MSI 03 (MSID = MS1). Generate the corresponding setting information and set as setting table 300. This setting information is generated by generating means (not shown) provided in BSK 104). This setting information is used as Anchor GWID 1101 shown in FIG. Then, the MS 103 generates and deletes a service flow ID (SFID) by DSA (Dynamic Service Addition) Req, Rsp, or the like. In addition, information regarding path registration is exchanged between the BS 104 and the ASN-GW 102.

[0026] After that, the MS 103 acquires an IP address and performs MIP Registration (MS 103 itself for CMIP, ASN—PMIP client function in the GW 102 for PMIP). Even when a new Service Flow is set, since the primitive is transferred to Anchor ASN (A1) 102, it is uniquely determined as Anchor ASN = A1 for MSID (MS 1).

FIG. 4 is a diagram showing a state at the time of handover of the MS. An example in which MS103 (MSID = MS1) includes movement across R4 is shown. As described above, the BS 104 (BSID = BS1) creates the setting table 300 shown in FIG. Therefore, when MS103 (MSID = MS1) is handed over, the transmission means (not shown) of BS104 (BSID = BS1) loads the setting information of this setting table 300 on the HO—Req IE (information element) and transfers it. To do. In the example shown in the figure, this HO—Req is transferred from Anchor ASN102 (ASN—GWID = Anchor GWID = A1) to BS 104 (BSID = BS2) of the HO destination. At this time, HO—Req is transferred to BS 104 (BSID = BS2) via ASN—GW 102 (ASN—GWI D = A2) accommodating BSID = BS2. [0028] (Case 1 at handover)

Next, various cases at the time of handover of the MS 103 will be described. FIG. 5 is a diagram showing the state of the handover. In the example of Fig. 5, after MS103 force network entry (see Fig. 1), at least once, R4 is crossed over to another ASN-GW102 (ASN-GWID = A2) (position P1) This is a case where handover was subsequently performed within ASN-GW102 (AS N-GWID = A2) of the same relay (Relay) (position P2).

[0029] FIG. 6 is a diagram illustrating an example in which the handono request does not pass through the anchor ASN. If the H O-Req force Anchor ASN—GW 102 (ASN—GWID = A 1) is not passed! /, This HO—Req need only be sent to the target BSID BS104 (BSID = BS3). For this reason, the BS 104 (BSID = BS 2) that received the HO request from the MS 103 at the position P1 first transmits the HO—Req to the ASN—GW 102 (ASN—GWID = A 2) that manages the BS 104 (S201) . Relay (not Anchor) ASN—GW102 (ASN—GWI D = A2) extracts Target BSID from IE in HO—Req (see Figure 18), and HO—Req is BS104 of Target BSID (position P2). Transmit to (BSID = BS3) (S202). In this case, Anchor ASN—GW102 (ASN—GWID = A1) does not receive HO—ReqZRsp.

[0030] FIG. 7 is a diagram illustrating an example in which a handono request passes through an anchor ASN. Unlike FIG. 6, FIG. 7 shows the case where HO—Req passes through Anchor ASN—GW 102 (ASN—GWID = A1). HO—As defined in Req! Primitives cannot be transferred to Target BSID B S104 (BSID = BS3) via Anchor ASN-GW102 (ASN-GWID = A1) only by IE. Thus, the ASN-GW 102 (ASN-GWID = A1, A2) can obtain the HO-Req transmission source (MS103) as unique identification information from the IP address of the lower layer. As a result, as shown in FIG. That is, HO—Req from MS103 at position P1 is BS104 (BSID = BS2) → ASN-GW102 (ASN-GWID = A2) → Anchor ASN-GW102 (ASN-GWID = A1) → ASN—GW102 (ASN—GWID = A2) → can be transferred to BS104 at position P2 (Target BSID = BS3).

[0031] (Handono Request HO—Req Transfer Procedure) Figure 8 is a flow chart showing the procedure for transferring a handover request in the ASN-GW. Each ASN-GW 102 described above executes the processing shown in FIG. At this time, it is assumed that whether or not the own ASN-GW 102 is Anchor is known in advance by setting. In the figure, TBS is Target BSID, A—GW is Anchor GWID, Self GW is self ASN—GWID ゝ R—GW is an abbreviation for Relay ASN-GWID (ASN—GW managing Target BS).

[0032] When the ASN-GW 102 receives the HO-Req (step S801), the ASN-GW 102 determines whether this HO has received the power of BS 104 (step S802). If HO is received from BS 104 (step S802: Yes), it is determined whether GW = A—GW (step S803). If the own GW—ASN102 is Anchor (step S803: Yes), it is determined whether the TBS is a BS under its own ASN (step S804). If the TBS of HO—Req is BS 104 under its own ASN-GW102 (step S804: Yes), this HO—Req is sent to BS 104 under its own ASN-GW102 (step S805). End the transfer process. At this time, the data path (DP) of R6 is limited to one (details will be described later).

[0033] In step S802, if HO—Req is not received from BS 104 (step S8 02: No), HO—Req is received from another ASN—GW 102, and then TBS is subordinate to its own AS N. It is determined whether it is a BS (step S806). If TBS is BS104 under its own ASN-GW102 (step S806: Yes), ASN-GW102 sends this HO-Req to BS104 under its own ASN-GW102 (step S807), and HO-Req The transfer process ends. In this case, the DP of R6 is limited to one.

[0034] On the other hand, in step S806, if the TBS is not BS 104 under its own ASN—GW 102 (step S806: No), HO—Req is transmitted to R—GW (step S808), and HO—Re q transfer processing is performed. Exit. In other words, HO-Req is transferred to ASN-GW 102 that manages Target BS 104 via R4. In this case, the R4 DP is limited to one.

[0035] In step S803, if the own GW-ASN102 is not Anchor (step S803: No), HO-Req is transmitted to A-GW (step S809), and HO-Req transfer processing is terminated. . In step S804, if the TBS of HO—Req is not BS104 under its own ASN—GW 102 (step S804: No), HO—Req is sent to R—GW. (Step S810), HO—Req transfer processing is terminated. That is, HO-Req is transferred to ASN-GW 102 that manages Target BS 104 via R4. In this case, the DP of R4 is limited to one.

The processing content shown in FIG. 8 will be specifically described using an example in which the handono request in FIG. 7 passes through the anchor ASN. As shown in FIG. 7, it is assumed that MS103 has performed a handover from position P1 to P2. BS104 sets Target BSID (BSID = BS3) so that MS 103 moves to position P2 in HO—Req, and Anchor A SN-GW102 (ASN-GWID = Anchor GWID = A1) in Anchor GWID Configure and send to Relay ASN GW102 (ASN—GWID = A2) (route al in Figure 7).

[0037] Relay ASN—GW102 (ASN—GWID = A2) first receives HO—Req from Serving BS (ie BS1 04), and its own ASN—GW is not Anchor GWID (≠ A1) And HO—Req is transferred to Anchor ASN—GW 102 (Anchor GWID = A1) (route bl in FIG. 7, step S803: No → step S809 in FIG. 8).

[0038] Next, Anchor ASN—GW102 (ASN—GWID = A1) does not receive HO—Req from BS104, and its own ASN is Anchor ASN (Anchor GWID = A1) Recognize. As a result, Anchor ASN—GW102 (ASN—GWID = A 1) forwards 110—1 ^ to Relay ASN—GW102 (ASN—GW = A2) managing Target BSID (BSID = BS3) (FIG. 7). Path ₍ 1: Step S806: No → Step S808 in Fig. 8).

[0039] The Relay ASN-GW 102 (ASN-GWID = A2), which has once transmitted the HO-Req, receives the HO-Req having the same content again. However, since HO—Req has not been received from BS 104 and Target BSID (BSID = BS3) exists under its own ASN, HO against Target BSID (BSID = BS3) — Req is transferred (path dl in FIG. 7, step S806: Yes → step S807 in FIG. 8).

[0040] (Handover Response HO—Rsp Transfer Procedure)

FIG. 9 is a diagram illustrating an example in which the handover response passes through the anchor ASN. FIG. 10 is a flowchart showing a handover response transfer procedure in the ASN-GW. For HO—Response (HO—Rsp), Target BSID (BSID = The Primitive transmitted from BS3) to Serving BSID (SBS, BSID = BS2) is almost the same as HO-Req (see Fig. 8). Note that the transmission source of this HO-Req is SBS and the transmission destination is TBS, based on the transfer of HO-Req. Conversely, for HO-Rsp transfer, the HO-Req destination TBS is sent from the HO-Rsp and forwarded to the HO-Req source SBS.

Each process shown in FIG. 10 is individually executed by each ASN-GW 102 described above. At this time, it is assumed that whether or not the own ASN-GW 102 is Anchor is known in advance by setting.

[0042] When the ASN-GW 102 receives the HO-Rsp (step S1001), the ASN-GW 102 determines whether this HO has received as much as the BS 104 (step S 1002). If HO is received from BS 104 (step S1002: Yes), it is determined whether GW = A—GW (step S1003). If the own GW—ASN102 is Anchor (step S1003: Yes), it is determined whether the SBS is a BS under its own ASN (step S1004). If the SBS of the HO—Rsp is the BS104 under its own ASN—GW102 (step S 1004: Yes), this HO—Rsp is sent to the SBS 104 (step S 10 05), and the HO—Rsp transfer process is terminated . In this case, the data path (DP) of R6 is limited to one.

[0043] In step S1002, if HO—Rsp is not received from BS 104 (step S 1002: No), HO—Rsp is received from another ASN—GW 102, and then SBS is under its own ASN. It is determined whether it is BS (step S 1006). If the SBS is the BS 104 under its own ASN-GW 102 (step S1006: Yes), the ASN-GW 102 transmits this HO Rsp to the SBS 104 (step S1007), and ends the HO-Rsp transfer process. In this case, the DP of R6 is limited to one.

[0044] On the other hand, in step S1006, if SBS is not BS104 under its own ASN—GW102 (step S1006: No), HO—Rsp is transmitted to R-GW (step S1008), and HO Rsp is transferred. End the process. In this case, the R4 DP is limited to one.

[0045] In step S1003, if GW-ASN102 is not Anchor (step S1003: No), HO-Rsp is transmitted to A-GW (step S1009), and HO-Rsp transfer processing is performed. Exit. Further, in step S1004, if the SBS of HO—Rsp is not BS 104 under its own ASN—GW102 (step S1004: No), HO—Rsp is changed to R—GW. (Step S1010), and the HO—Rsp transfer process ends. In this case, the DP of R4 is limited to one.

The processing contents shown in FIG. 10 will be specifically described using an example in which the handover response in FIG. 9 passes through the anchor ASN. As shown in FIG. 9, it is assumed that the MS 103 performs a handover from the position P1 to P2.

[0047] First, the Target BSID (BS104, BSID = BS3) that received the HO—Req checks its own resource and generates each HO—Rsp IE (see FIG. 18). The nchor GWID and Serving BSID (see Fig. 18) in the HO—Rsp are sent to the ASN-GW102 (ASN GWID = A2) with the IE received from the HO—Req (route a2 in Fig. 9).

[0048] The ASN—GW102 (AS N—GWID = A2) that received the HO—Rsp from the Target BSID (BSID = BS3) is not the Anchor ASN—GW, so the ASN-GW 102 (ASN -HO-Rsp is transmitted to GWID = Anchor GWID = A 1) (route b2 in FIG. 9, step S1003: No → step S1009 in FIG. 10).

[0049] Anchor ASN—GW102 (ASN—GWID = A1) has not received HO—Rsp from Target BSID (BSID = BS3), and Serving BSID (BSID = BS2) is self-managed. Since it is not below, this HO—Rsp is transmitted to ASN-GW102 (ASN-GWI D = A2) of Relay (path c2 in FIG. 9, step S 1006 in FIG. 10: No → step S 1008 processing).

[0050] When Relay ASN—GW102 (ASN—GWID = A2) receives HO—Rsp from Anchor ASN—GW102 (ASN—GWID = A1), it does not receive from Target BSID (BSID = BS2). Since Serving BSID (BSID = BS3) exists under its own ASN—GW102 (ASN—GWID = A2), 110—1 ^ is transmitted to BS104 of Serving BSID (BSID = BS2) ( The route in FIG. 9 (12, step S 1006 in FIG. 10: Yes → step S 1007).

[0051] (Processing of each part between data paths R4 and R6 at the time of handover)

Next, processing of each unit between the data paths (DP) R4 and R6 at the time of handover will be described. FIG. 111 and FIG. 112 are sequence diagrams showing the transfer processing of each part on the data paths R4 and R6, respectively. These figures show the HO-Req shown in Figure 7, And each configuration at the time of HO-Rsp shown in Fig. 9 is shown. That is, the Relay ASN—GW shown in FIGS. 11-1 and 11-2 is the same ASN—GW 102 (ASN—GWID = A2) shown in FIGS. Serving BS (SBS) is BS10 4 (BSID = BS2), and Target BS (TBS) is BS104 (BSID = BS3).

[0052] 1. At the time of MS103 handover, as described above, SBS104 (BSID = BS2) generates setting information (see FIG. 3) in which MSID and Anchor GWID are associated (step S1101). This setting information is sent to the ASN-GW 102 on the HO-Req. Between the ASN-GWs 102, a transfer means (not shown) provided for each executes the HO-Req transfer process described above (see FIG. 8) (step S1102). In TBS104 (BSID = BS3), the MSID and Anchor GWID are stored in a memory (not shown) from the setting information included in the HO—Req (step S1103).

[0053] 2. TBS104 (BSID = BS3) sends Context Reg to SBS104 (BSID = BS2) based on the HO—Rsp transfer process described above (see FIG. 10) (step S1104).

3. SBS104 (BSID = BS2) sends Context Rprt to TBS104 (BSID = BS3) based on the HO—Req transfer process described above (see Fig. 8) (step SI 105). These primitives in 2. 3. are other primitives that need to be transferred to the same destination as 1. HO—Req.

[0054] 4. TBS104 (BSID = BS3) uses the setting information (MSID and Anchor GWID) stored in the memory to set the Path Pre for Anchor ASN—GW102 (ASN—GWID = A1). -Reg Req is sent (step SI 106). This Path Pre-Reg Req is performed based on a predetermined transfer process (step SI 107) described later.

5. Anchor ASN—GW102 (ASN—GWID = A1) responds to TBS104 (BSID = BS3) with Path Pre—Reg Rsp via Relay ASN—GW102 (ASN—GWID = A2) ( Step SI 108).

6. TBS104 (BSID = BS3) sends Path Pre-Reg A ck as a Primitive for confirmation of Pre-Reg request to Anchor ASN—GW102 (ASN—GWID = A1) (step S 1109) .

[0055] These 4. Path Pre -Reg Req, 5. Path Pre -Reg Rsp, 6. Path Pre -Reg Ack is performed to Anchor AS N-GW102 (ASN GWID = A1) and a plurality of BSs 104 constituting the system in order to confirm a reservation for securing DP path resources.

[0056] 7. TBS104 (BSID = BS3) sends HO-Rsp to SBS104 (BSID = BS2) based on the HO-Rsp transfer process described above (see FIG. 10) (step S1110). ).

8. SBS104 (BSID = BS2) sends HO—Ack to TBS104 (BSID = BS3) as a confirmation primitive for the HO—Rsp request (step S1111).

9. With the above processing, one Target BS (BSID = BS3) is determined, and the handover destination of MS103 is determined (step S1112). Then, SBS104 (BSID = BS2) sends HO—Confirm to TBS 104 (BSID = BS3) based on the HO—Req transfer process described above (see FIG. 8) (step S1113). TBS104 (BSID = BS3) stores information on Target BS described in HO—Confirm! (Step S1114).

[0057] 10. TBS104 (BSID = BS3) sends HO—Ack to SBS104 (BSID = BS2) as a confirmation for the HO—Confirm request (step S1115).

11. TBS104 (BSID = BS3) sends Path Reg Req to Anchor ASN—GW102 (ASN—GWID = A1) using the setting information (MSID and Anchor GWID) stored in memory. (Step SI 116). This Path Reg Req is performed based on a predetermined transfer process (step S 1117) described later.

12. Anchor's ASN -GW102 (ASN-GWID = A1) is connected to TBS 104 (BSID = BS 3) via Relay ASN—GW102 (ASN—GWID = A2)

Rsp is returned (step S 1118).

13. TBS104 (BSID = BS3) sends Path Reg Ack as Primitive for confirmation of Pre-Reg request to Anchor ASN—GW102 (ASN—GWID = A1) (step SI 119).

[0058] These 11. Path Reg Req, 12. Path Reg Rsp, and 13. Path Reg Ack, BS104 and Anchor AS N—GW102 (ASN — Exchanged with GWID = A1).

[0059] 14. After this, Anchor's ASN—GW102 (ASN—GWID = A1) The DP that has been set is canceled (step S 1120). For this purpose, Path DeReg Req is sent to BS 104 (BSID = BS2) which is the handover source BS. At this time, Relay ASN—GW 102 on the way forwards Path DeReg Req to SBS 104 (BSID = BS2) * 5.

15. SBS 104 (BSID = BS2) sends Path DeReg Rsp to ASN—GW102 (ASN-GWID = A1) of Anchor as a response to Path DeReg Req (step S 1121)

16. Finally, Anchor ASN—GW 102 (ASN—GWID = A1) sends Path DeReg Ack to SBS 104 (BSID = BS2) as a confirmation for the request of Path DeReg Rsp (step S 1122).

FIG. 12 is a flowchart showing data path setting preparation processing. This is processing related to the transfer of the Path Pre-Reg Req (Rsp) described above, and is executed by the ASN-GW102. First, when Path Pre-Reg Req is received (step S 1201), the force (self GW = A—GW force) at which the self ASN—GW 102 is Anchor is cut halfway (step S 1202).

[0061] If the local ASN—GW102 is not Anchor (step S 1202: No), a Path Pre-Reg Req is transmitted in the direction of Anchor GWI D (to the Anchor ASN—GW102) (step S1203). . Next, when the Path Pre-Reg Rsp transmitted from the ASN-GW 102 of the Anchor is received (step S I 204), the received Path Pre-Reg Rsp is transmitted in the reverse direction of the Anchor GWID (step S I 205). Thereafter, Path Pre-Reg Ack is received (step S I 206), and the above processing ends.

[0062] On the other hand, if the own GW102 is Anchor (step S1202: Yes) ゝ After responding with Path Pre-Reg Rsp (step SI 207), receiving Path Pre-Reg Ack (step SI 2 06), The above process ends.

FIG. 13 is a flowchart showing data path setting processing. Path Reg mentioned above

This is processing related to Req (Rsp) transfer, and is executed by ASN—GW102. The following processing is the same as in FIG. 12, and only the difference is whether the force Reg is Pre-Reg. First, when Path Reg Req is received (step S 1301), it is determined whether the own ASN—GW 102 is Anchor (ie, own GW = A—GW) (step S 1302). [0064] If the own GW is not Anchor (step SI 302: No), Path Reg Req is transmitted in the direction of Anchor GWID (to the ASN-GW 102 of Anchor) (step SI 303). Next, when the Path Reg Rsp transmitted from the Anchor ASN—GW 102 is received (step S 1304), the received Path Reg Rsp is transmitted in the reverse direction of the Anchor GWID (step S 1305). Thereafter, Path Reg Ack is received (step SI 306), and the above processing is terminated.

[0065] On the other hand, if the own GW102 is Anchor (step S1302: Yes), after responding with Path Reg Rsp (step SI 307), receiving Path Reg Ack (step SI 306), and the above processing ends. To do.

FIG. 14 is a diagram showing a data path switching state before and after the handover. This corresponds to the state at the time of the node over described with reference to FIG. The explanation is divided into the control signal plane (C— Plane) and the user information transfer plane (U— Plane). The IE described above is exchanged in each part by C-Plane, and among the codes 1 to 16 used in Fig. 11-1 and Fig. 11-2, the Primitive (4) of Path (Pre-) Reg related to DP switching 5. 6. 11. 12. 13.) are extracted and described. In addition, Primitive between each component is attached with subscripts a, b,... (Example: 4a, 4b), respectively.

[0067] U— Data transfer on the Plane side will be explained. Before handover, ASN-G W102 (ASN GWID) of Anchor via MS 103 (not shown) and SBS104 (BSID = BS2) by Old Air Data path (DP) is set up to = A1) (Old DP path indicated by dotted line in the figure). Before the handover, the MS 103 transfers data with the CSN 101 (see Fig. 4) via the R3 DP via the anchor ASN-GW 102 via the R6 DP.

[0068] Then, when the MS 103 is handed over and moves to the TBS 104 (BSID = BS3), as described above (see FIGS. 11-1 and 11-2), the C-Plane side performs the primitive transfer process. At the time of handover, Anchor ASN-GW102 (ASN GWID = A1) switches based on the contents of each Primitive to become a new DP (New DP path indicated by a solid line in the figure). At this time, Anchor ASN—GW102 (ASN—GWID = A1) is between Relay ASN—GW102 (ASN—GWID = A2) based on the contents of Primitive. The number of R4 DPs in is one. The number of DPs in R6 between ASN-GW102 (ASN-GWID = A2) and TBS104 (BSID = BS3) is one.

[0069] Then, FA (Foriegn Agent) in Anchor's ASN-GW102 switches old DP data before handover to New DP after handover (based on 12a. Path R eg Rsp and 13b. Path Reg Ack) switching). After the handover, MS103 sends data to and from CSN101 (see Fig. 5) from RSN DP via Relay ASN—GW102, via R4 DP via Anchor ASN—GW102, and via R3 DP. Data transfer.

[0070] As described above, according to the Primitive transfer method in which HO—Req is routed through Anchor ASN—GW102, the DP (R4 and R6) from MS103 to Anchor ASN—GW102 after HO is the maximum. Can be limited to two. At this time, the ASN-GW102 does not require any special operation.

[0071] That is, HO—Req Primitive is set to Anchor ASN—GW102 (ASN—GWID

= A 1), the number of data paths DP (R4) from this Anchor ASN—GW102 (ASN—GWI D = A1) to Relay ASN—GW102 (ASN—GWID = A2) Is limited to one. At the same time, the Relay ASN-GW102 (ASN-GWID = A2) force is also limited to one DP (R6) reaching the Target BS104. Accordingly, the number of DP (R6) from the ASN-GW102 (ASN-GWID = A1) of the anchor to the Target BS104 is limited to two. In this way, by limiting the number of DPs for primitive transfer during HO-Req to the minimum number, packet delay can be prevented and communication quality will not be degraded.

FIG. 15-1 to FIG. 15-5 are diagrams showing all states of DP setting. The state of Figure 15-1 is

The movement of MS103 is the case of movement between BS104 managed by Anchor ASN-GW102. When IP packets are transmitted between R3 (MIP) and MS 104, the R6 DP path (R6-1) before handover is switched at the switching point (SW) at the time of handover, and the R6 path (R6) after handover is switched. — Changed to 2). The HO-R eq at this time is transferred by the route HI (dotted line in the figure) from the SBS 104 before the handover to the ASN of the anchor to the TBS 104 after the handover. [0073] The state shown in Fig. 15-2 is when the MS 103 moves across different ASN-GWs 102 (when R4 changes from Anchor to Relay). In this case, the DP route (R6 1) of R6 before handover is switched at the switching point (SW) at the time of handover. The route is changed to (R6-2). The HO-Req at this time is transferred via the route H2 from the SBS 104 before the handover to the ASN of the anchor—GW 102 → the ASN of the relay—GW 102 → the TBS 104 after the handover.

[0074] The state shown in Fig. 15-3 is when the MS 103 moves across different ASN-GWs 102 (when changing R4 from Relay to Anchor). In this case, the R6 DP route (R6-1) and R4 route (R4-1) before the handover are switched at the switching point (SW) at the time of the handover, and after the handover with the ASN-GW102 of the Anchor R4 route between (R6-2). The HO-Req at this time is transferred via the route H3 from the SBS 104 before the handover to the ASN of the relay—GW 102 → the ASN of the anchor—GW 102 → the TBS 104 after the handover.

The state of FIG. 15-4 is the case where the movement of the MS 103 is the movement between the BSs 104 managed by the ASN-GW 102 of the Relay. In this case, the R6 DP path before handover (R6-1) and the R4 DP path (R4-1) are switched at the switching point (SW) during handover, and the R6 path after handover (R6 — Changed to 2) and R4 route (R4-2). The HO-Req at this time is transferred via the route H4 from the SBS 104 before the handover to the ASN of the relay-GW 102-> Anchor ASN-GW 102-> Relay ASN-GW 102--to the TBS 104 after the handover.

The state of FIG. 15-5 is a case where the movement of the MS 103 straddles between the ASN of the Relay—GW 102 and further moves to the ASN—GW 102 of a different Relay. In this case, the R6 DP route (R6-1) before the handover and the R4 DP route (R4-1) are switched at the switching point (SW) during the handover, and the R6 route (R6) after the handover. — Changes to 2) and R4 route (R4-2). The HO-Req at this time is transferred via the route H5 from the SBS 104 before the handover to the ASN of the Relay 1 → GW 102 → the ASN of the Anchor → GW 102 → the ASN of the Relay 2 → GW 102 → the TBS 104 after the handover. [0077] In any of the cases shown in Fig. 15-1 to Fig. 15-5, the HO-Req at the time of handover is transferred from the SBS 104 to the TBS 104 via the ASN-GW 102 of the Anchor, and a new DP Is set. In either case, the number of DPs is one for R4 and one for R6. In particular, as shown in Fig. 15-5, even when the movement between ASN and GW102 of MS 103's mobility relay is crossed multiple times, it is possible to connect between ASN-GW102 of Anchor and ASN-GW102 of Relay. R4 DP can be switched to one. In other words, since DP (R4) between Relay AS N and GW102 is prevented from connecting between multiple Relays, packet delay and communication quality degradation can be prevented.

[0078] As described above, there are five patterns for the HO-Req primitive transfer. Otherwise, R3 DP handono, R8 data path handover.

[0079] In the above-described embodiment, the Primitive transfer at the time of handover in WiMAX has been described as an example. However, any communication method for performing message transfer via a specific node at the time of handover other than WiMAX alone may be used. Can be applied.

[0080] It should be noted that the method for transferring Primitive at the time of handover described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. . This program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read by the computer. This program may also be a transmission medium that can be distributed via a network such as the Internet!

Industrial applicability

[0081] As described above, the mobile communication method and the mobile communication apparatus according to the present invention are useful for processing at the time of handover when the mobile station moves, and particularly at the time of handover of the mobile station including WiMAX. Suitable for message transfer processing via a specific node.

Claims

The scope of the claims

[1] A mobile communication method for a mobile station to perform a handover enabling communication,

When the mobile station enters the network, the base station that communicates with the mobile station associates the unique identifier of the mobile station with the unique identifier of the access management apparatus that is an anchor for the mobile station. A mobile communication method comprising a generation step of generating setting information.

[2] In the handover based on the movement of the mobile station, the base station includes a transmission step of transmitting the setting information generated by the generation step on an information element of a primitive. Item 2. The mobile communication method according to Item 1.

[3] including a transfer step of transferring the setting information transmitted in the transmission step and loaded on the information element of the primitive to the base station of the movement destination via the access management device serving as an anchor. The mobile communication method according to claim 2, wherein the mobile communication method is characterized.

4. The mobile communication method according to claim 1, wherein the generating step can make the unique identifier of the mobile station based on an address unique to the mobile station.

[5] The transfer step includes an HO-Request as the primitive sent when the mobile station moves and another primitive that needs to be transferred to the same transfer destination as the HO-Request. The mobile communication method according to claim 3, wherein the HO-Request transmission source base station (SBS) is forwarded to the transmission destination base station (TBS) via the access management device serving as an anchor. .

[6] The transfer step includes an HO—Response that is a response to the HO—Request and the HO—Request.

Other primitives that need to be transferred to the same destination as Response are sent to the base station of the transmission source via the access management device (TBS) that is also the anchor of the transmission destination base station (TBS) of the HO-Request. 4. The mobile communication method according to claim 3, wherein the mobile communication method is transferred to SBS.

[7] The access management device serving as an anchor is configured to transmit data from the access management device to the mobile station based on the setting information placed in the primitive information element transferred in the transfer step. The mobile communication method according to claim 3, further comprising a data path number limiting step of limiting the number of paths to a maximum of two.

[8] In the data path number limiting step, based on the setting information placed on the information element of the primitive transferred by the access management device serving as an anchor in the transfer step, the access management device power When the access management device as a relay is interposed in the data path to the station, the number of data paths between the anchor access management device and the relay access management device is set to a maximum of one. The mobile communication method according to claim 7, wherein the mobile communication method is limited to one.

[9] In the data path number limiting step, when the access management device manages the mobile station under its control, the data path number limiting step includes the setting information placed in the information element of the primitive transferred in the transfer step. 8. The mobile communication method according to claim 7, wherein the number of data paths between the access management apparatus and the mobile station is limited to a maximum of one based on the base.

[10] A mobile communication device arranged as a base station in order for a mobile station to perform communication to enable handover,

When the mobile station enters the network, the mobile station includes generation means for generating setting information in which the unique identifier of the mobile station is associated with the unique identifier of the access management apparatus that is an anchor for the mobile station. A mobile communication device characterized by that.

11. The transmission device according to claim 10, further comprising a transmission unit that transmits the setting information generated by the generation unit on a primitive information element at the time of handover based on movement of the mobile station. Mobile communication device.

[12] A device at a position to which the setting information sent by the sending means and loaded on the information element of the primitive is transferred to the destination base station via the access management device serving as an anchor, 11. The mobile communication device according to claim 10, further comprising transfer means for transferring the primitive.