[go: up one dir, main page]

WO2009118980A1 - Système de radiocommunication, contrôleur de passerelle et station de base - Google Patents

Système de radiocommunication, contrôleur de passerelle et station de base Download PDF

Info

Publication number
WO2009118980A1
WO2009118980A1 PCT/JP2009/000411 JP2009000411W WO2009118980A1 WO 2009118980 A1 WO2009118980 A1 WO 2009118980A1 JP 2009000411 W JP2009000411 W JP 2009000411W WO 2009118980 A1 WO2009118980 A1 WO 2009118980A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
access gateway
agw
control
charging
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2009/000411
Other languages
English (en)
Japanese (ja)
Inventor
渡辺晃司
高橋陽介
中原成人
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Communication Technologies Ltd
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 Hitachi Communication Technologies Ltd filed Critical Hitachi Communication Technologies Ltd
Priority to JP2010505289A priority Critical patent/JP5055428B2/ja
Publication of WO2009118980A1 publication Critical patent/WO2009118980A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/062—Pre-authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present invention relates to a wireless communication system, and more particularly, to a wireless communication system, a gateway control apparatus, and a base station that perform authentication processing and charging processing for each mobile terminal.
  • a communication range of each base station such as a nano cell, a pico cell, and a femto cell Cell size tends to be reduced. Further, it is considered to install AGW finely in an area where voice (VoIP) traffic is concentrated locally, such as a station or a downtown area.
  • VoIP voice
  • the conventional wireless communication network a relatively large number of base stations are accommodated in one AGW.
  • this network configuration even if the mobile terminal moves between base stations, there is a high possibility that the transmission / reception packet of the mobile terminal can be relayed by the same AGW. Therefore, the frequency of occurrence of handover between AGWs is relatively low.
  • communication of control messages performed between the AGW and the management server on the core network side for example, charging processing and user authentication processing, etc. Therefore, a network configuration that can reduce message exchange as much as possible is required.
  • FIG. 2 shows a configuration example of a conventional wireless communication network including a plurality of AGWs.
  • symbol 1 shows a core network (Core NW).
  • the core network 1 includes a mobile IP home agent (HA) 2 and an AAA (Authentication Authorization and Accounting) server 3 for user authentication / access authorization / accounting.
  • Reference numeral 4 (4A, 4B, 4C...) Denotes an access gateway (AGW: Access Gate Way) connected to a plurality of base stations (AN: Access Node) 20 (20A, 20B, 20C,).
  • Reference numeral 30 denotes a mobile station (AT: Access Terminal).
  • Each AGW 4 is accompanied by a radio resource control device (RNC: Radio Network Controller) 10 (10A, 10B, 10C,...), And each AGW 4 is connected to the home agent 2 as indicated by a solid line. ing. As indicated by a broken line, the AGW 4 and the RNC 10 communicate a control message with the AAA server 3, and the RNC 10 communicates a control message with the base station 10 accommodated in the AGW 4 to which the AGW 4 is attached.
  • RNC Radio Network Controller
  • the base stations 20A, 20B, and 20C are accommodated in the AGW 4A
  • the base station 20D is accommodated in the AGW 4B
  • the base station 20E is accommodated in the AGW 4C.
  • the AGW 4C is integrated with the base station 20E and the RNC.
  • Each base station (AN) may communicate with each other via an AGW, or may communicate with another base station via a connection line between the base stations as illustrated.
  • AGW 4 (4A, 4B,...) Is an IP router (1st hop hop router) to which AT 30 is first connected, and QoS control and authentication / authorization of each AT in the IP (Internet Protocol) layer / Functions as a packet data serving node (PDSN) that controls charging and the like.
  • IP Internet Protocol
  • PDSN packet data serving node
  • each AGW 4 serving as a connection point (Point of attachment) between the mobile station 30 and the core network 1 may generate an AAA request as a core network load only when an inter-AGW handover occurs.
  • each base station determines whether the handover is an inter-AGW handover, An AAA request message is transmitted to the core network.
  • the AAA server executes processing such as authentication / authorization / billing in response to the request message received from the base station.
  • FIG. 3 shows an example of a communication sequence for charging control of the mobile station (AT) 30 executed in the conventional wireless communication network shown in FIG.
  • the AT 30 connected to the AGW 4A via the base station (AN) 20C has moved into the communication area of the base station (AN) 20D, so that a handover from the AGW 4A to the AGW 4B occurs.
  • the handover source AN 20C is “S-AN”
  • the handover source AGW 4A is “S-AGW”
  • the handover destination AN 20D is “T-AN”
  • the handover destination AGW 4B is “T-AGW”.
  • a radio access network including an RNC and at least one AN connected to the RNC is referred to as a RAN (Radio Access Network).
  • the handover source RAN (S-RAN) is composed of the ANs 20A to 20C and the RNC 10A
  • the handover destination RAN is composed of the AN 20D and the RNC 10B.
  • a session is established between the AT 30 and the S-AN 20C, and the AAA server 3 authenticates the user of the AT 30 by a user authentication protocol, for example, EAP (Extensible Authentication Protocol).
  • EAP Extensible Authentication Protocol
  • PMIP Proxy Mobile Mobile Internet Protocol shows a state where a tunnel is set between the S-AN 20C and the S-AGW 4A.
  • an accounting start request message (Accounting Request (Start)) is transmitted from the S-AN to the S-AGW (101).
  • the message Accounting Request (Start) includes a user identifier and air link information such as radio QoS and radio resources requested by the AT 30.
  • the S-AGW generates a user data record: UDR including information extracted from the received message Accounting Request (Start) and charging information such as service time and the number of octets of transmission data, and generates a charging request message (Accounting) including the UDR.
  • Request (Start)) is transmitted to the AAA server 3 (102).
  • the Accounting Request (Start) message first transmitted from the S-AGW to the AAA server 3, the billing information such as the service time and the number of octets is in a null state.
  • Steps 104A and 104B indicate that the AT 30 enters a data communication state with the communication partner via the tunnel between the S-AN and the S-AGW. While the AT 30 is in the data communication state, the S-AGW and the S-AN collect the charging information of the AT 30 and store it in the management table in association with the user identifier.
  • a handover procedure is executed between the AT 30 and the HA 2 under the initiative of AT or RAN (105), and charging is performed in parallel with the handover procedure.
  • Switching processing is executed.
  • a charging end request message (Accounting Request (Stop)) is transmitted from the S-AN to the S-AGW (106), and the S-AGW that has received the Accounting Request (Stop) message is extracted from the received message.
  • a user data record (UDR: User Data Record) is generated from the recorded information and the charging information of the AT 30 stored in the management table, and this is sent to the AAA server 3 by a charging end request message (Accounting Request (Stop)). Transmit (107).
  • the AAA server 3 updates the charging information corresponding to the user identifier of the AT 30 based on the received Accounting Request (Stop) message, and transmits a charging response message (Accounting Response) to the S-AGW (108).
  • the user billing process is terminated.
  • the T-AN transmits a charging start request message (Accounting Request (Start)) including the user identifier of the AT 30 and the air link information to the T-AGW (109).
  • the T-AGW generates a user data record (UDR) including information extracted from the received AccountingAccountRequest (Start) message and charging information, and generates a charging request message (Accounting Request (Start)) including UDR as the AAA server 3. (110).
  • the billing information such as the service time and the number of octets is null.
  • Steps 114A and 114B indicate that the AT 30 is in a data communication state with the communication partner via the T-AN and T-AGW.
  • the T-AGW and the T-AN collect the charging information of the AT 30 and store it in the management table in association with the user identifier.
  • a session termination procedure is executed between the AT 30 and the T-AN and between the T-AN and the T-AGW (115A, 115B).
  • An accounting end request message (Accounting Request (Stop)) is transmitted to the T-AGW (116).
  • the T-AGW generates a UDR from the information extracted from the received Accounting Request (Stop) message and the charging information of the AT 30 stored in the management table, and the charging end request message (Accounting Request (Stop) containing this UDR is generated. )) Is transmitted to the AAA server 3 (117).
  • the AAA server 3 Upon receiving the Accounting3Request (Stop) message, the AAA server 3 updates the charging information corresponding to the user identifier indicated by the received message, and sends a charging response message (Accounting Response) to the T-AGW (118). The accounting process for the user identifier is terminated.
  • FIG. 4 shows an example of a communication sequence for user authentication executed in the conventional wireless communication network shown in FIG.
  • the AT 30 wirelessly connects to the S-AN and executes a session start procedure with the S-AN (step 130).
  • the S-AN sends a message (EAP Request) that triggers an authentication procedure to the AT 30 using a predetermined authentication protocol, for example, EAP (Extensible Authentication Protocol) (131)
  • EAP Response is returned to the S-AN (132).
  • the S-AN transmits an authentication request message (EAP Request) including the user identifier indicated by the EAP Response message to the S-AGW (133).
  • This message is transferred to the AAA server 3 by the S-AGW (134).
  • a control message for user authentication according to EAP is exchanged between the AT and the AAA server via the S-AN and S-AGW (135A, 135B, 135C).
  • the AAA server 3 When the user authentication is successful, the AAA server 3 includes, for the S-AGW, an authentication result (successful authentication) and control information used in wireless communication, such as QoS / User profile, MSK (Master Session Key), etc.
  • a control message (EAP success) is transmitted (136).
  • QoS Quality of Service
  • User profile indicates user information of the AT 30.
  • the MSK is information necessary for generating an encryption key that the AT 30 applies to transmission data encryption.
  • the S-AGW When the S-AGW receives the EAP success message, the S-AGW stores a part of the QoS / User profile extracted from the received message in the storage unit in association with the user identifier, and also receives the received EAP success message from the S-AN. Is transferred (137).
  • the S-AN After receiving the EAP success message, the S-AN stores information such as QoS / User profile, MSK, etc. extracted from the received message in the storage unit and transmits a control message indicating successful authentication to the AT 30 (138).
  • the address information (IP address) of the S-AGW to which the AT 30 is connected is notified to the AT 30 (139).
  • step 140 the S-AN sets up a PMIP tunnel between the S-AN and the S-AGW.
  • the S-AN transmits an RRQ (Registration Request) message of PMIP (Proxy Mobile IP) to the S-AGW and registers the location of the AT 30 in the S-AGW.
  • the AT 30 enters an IP service state in which IP packets are transmitted and received with the communication partner via the S-AN and S-AGW (141A, 141B).
  • the AT 30 moves from the S-AN communication range to the T-AN communication range, and the handover process (142) of the AT 30 from the S-AGW to the T-AGW is executed.
  • the AT 30 wirelessly connects to the T-AN and executes a session start procedure with the T-AN (step 143).
  • the T-AN sends an EAP trigger message (EAP Request) to the AT 30 in the same manner as the S-AN did (144).
  • the AT 30 returns a response message (EAP Response) including the user identifier to the T-AN (145).
  • the T-AN transmits an authentication request message (EAP ⁇ Request) including the user identifier indicated by the EAP Response message to the T-AGW (146).
  • This message is forwarded by the T-AGW to the AAA server 3 (147), and then for user authentication according to EAP between the AT and the AAA server via the T-AN and T-AGW.
  • Are transmitted (148A to 148C).
  • the AAA server 3 transmits a control message (EAP ⁇ ⁇ success) including an authentication result (authentication successful), QoS / User profile, MSK (Master Session Key), etc. to the T-AGW ( 149).
  • EAP ⁇ ⁇ success a control message including an authentication result (authentication successful), QoS / User profile, MSK (Master Session Key), etc.
  • the T-AGW Upon receipt of the EAP success message, the T-AGW stores the QoS / User profile extracted from the received message in the storage unit and forwards the received EAP success message to the T-AN (150).
  • the T-AN that has received the EAP success message stores information such as QoS / User profile and MSK extracted from the received message in the storage unit, and transmits a control message indicating successful authentication to the AT 30 (151).
  • the address information (IP address) of the T-AGW connected to the AT 30 is notified to the AT 30 (152).
  • the T-AN sends a PMIP RRQ (Registration Request) message to the T-AGW, registers the location of the AT 30 in the T-AGW, and establishes a PMIP tunnel between the T-AN and the T-AGW. Set.
  • the AT 30 enters an IP service state in which IP packets are transmitted / received to / from the communication partner via the T-AN and T-AGW (155A, 155B).
  • An object of the present invention is to provide a wireless communication network, an AGW, and a base station that can suppress an increase in load on a management server on the core network side due to AGW switching even when handover between AGWs increases.
  • an access gateway control device is disposed between an access gateway device (AGW) and a management server connected to the core network, for example, an AAA server.
  • AGWC access gateway control device
  • a management server connected to the core network, for example, an AAA server.
  • the control message issued due to the inter-AGW handover is processed by the access gateway control device instead of the management server.
  • the present invention relates to a plurality of access gateway devices (AGW) connected to a core network, a management server connected to the core network, and each of the plurality of access gateway devices (AGW).
  • AGW access gateway devices
  • a wireless communication system comprising a plurality of base stations connected to one, Having an access gateway controller connected to the core network, When each base station executes a communication procedure for connecting a mobile station to the core network, a user identifier of the mobile station and an inter-AGW handover are performed for a specific access gateway device connected to the base station.
  • Each of the access gateway devices forwards the control message received from any of the base stations to the access gateway control device,
  • the access gateway control device receives the control message from any of the access gateway devices, if the event type does not indicate the occurrence of an inter-AGW handover, the control message is transferred to the management server, and the event When the type indicates the occurrence of an inter-AGW handover, the management server responds to the control message instead of the management server.
  • the control message received from each access gateway device by the access gateway control device is, for example, a charging start request message.
  • the management server when receiving the charging start request message from the access gateway control device, the management server starts charging processing corresponding to the user identifier indicated by the charging start request message.
  • the access gateway control device has, for example, a management table for storing billing information in association with a user identifier.
  • a billing start request message is received from any access gateway device, the billing start request message If the event type does not indicate the occurrence of the inter-AGW handover, a table entry corresponding to the user identifier indicated by the charging start request message is generated in the management table, and the event type of the charging start request message is the occurrence of the inter-AGW handover Is sent to the access gateway device instead of the management server.
  • each base station When a mobile station that has been in a connected state is handed over to another base station, each base station transmits a user identifier of the mobile station and an AGW to a specific access gateway device connected to the base station.
  • a charging end request message including an event type indicating whether or not inter-handover has occurred and charging information corresponding to the user identifier is transmitted.
  • Each gateway device when receiving the charging end request message from any of the base stations, updates the charging information stored in association with the user identifier according to the charging information indicated by the charging end request message, A charging end request message including the user identifier and event type indicated by the charging end request message and the updated charging information is transmitted to the access gateway control device.
  • the charging end request message indicates the charging information stored in the management table in association with the user identifier. If it is updated according to the billing information and the event type of the billing end request message indicates the occurrence of an inter-AGW handover, a response message is transmitted to the access gateway device, and the event type is an inter-AGW handover occurrence Is not transmitted, a charging end request message including the user identifier and the updated charging information is transferred to the management server.
  • the control message received from each access gateway device by the access gateway control device may be, for example, a user authentication request message.
  • the management server when the management server receives the user authentication request message from the access gateway control device, it executes a predetermined user authentication procedure with the mobile station, and then sends a response message indicating the authentication result to the access gateway control device. Return it.
  • the access gateway control apparatus has a management table for storing authentication control information in association with a user identifier, and when receiving a response message indicating successful authentication from the management server, the user identifier and authentication indicated by the response message After the information and control information are stored in the management table, the response message is transferred to the access gateway apparatus that has transmitted the user authentication request message.
  • the event type is generated for the access gateway device based on the information stored in the management table. Send a control message.
  • a wireless communication system includes a plurality of access gateway control devices distributed and attached to each gateway device as the access gateway control device.
  • each access gateway control device has a flat form integrated with the gateway device.
  • each access gateway device transfers a control message received from any base station to an access gateway control device associated with the access gateway device.
  • each access gateway control device receives a control message including an event type from the access gateway device, if the event type does not indicate the occurrence of an inter-AGW handover, the control message is transferred to the management server.
  • the event type indicates the occurrence of an inter-AGW handover, an operation is performed in response to the control message instead of the management server.
  • the access gateway control device that has received a specific control message whose event type does not indicate the occurrence of the inter-AGW handover from the accompanying access gateway device among the plurality of access gateway control devices.
  • the other access gateway control device that operates as the main AGWC with respect to the specific user identifier indicated by the control message and receives the control message including the specific user identifier and the event type indicating the occurrence of the inter-AGW handover is the specific user identifier. Operates as a slave AGWC with respect to identifiers.
  • the access gateway control device functioning as the slave AGWC receives the control message including the specific user identifier
  • the access gateway control device transfers the control message to another access gateway control device operating as the primary AGWC, and sends it to the primary AGWC.
  • Control messages can be processed.
  • the access gateway control apparatus provides a mobile station user identifier and an AGW from any access gateway apparatus in a process of executing a communication procedure for connecting the mobile station to the core network via any base station.
  • Control message receiving means for receiving a control message including an event type indicating whether or not an inter-handover has occurred, and if the event type of the control message does not indicate the occurrence of an inter-AGW handover, the control message is transmitted to the management server
  • a control message transfer means for transferring to the control message, and a response means for responding to the control message in place of the management server when the event type of the control message indicates the occurrence of an inter-AGW handover.
  • the access gateway control apparatus arranged in association with a specific access gateway apparatus (AGW) according to the present invention provides an event indicating whether a user identifier of a mobile station and an inter-AGW handover have occurred from the access gateway apparatus.
  • AGW access gateway apparatus
  • a control message receiving means for receiving a control message including a type, and a user identifier indicated by the control message, it is determined whether the control message should be processed as a primary AGWC or a secondary AGWC, and processed as a secondary AGWC
  • the control message is transferred to another access gateway control device operating as the main AGWC.
  • the event type of the control message is set.
  • the event type is If the occurrence of inter-GW handover is not indicated, the control message is transferred to the management server. If the event type indicates the occurrence of inter-AGW handover, the control message is returned on behalf of the management server. And a control unit that operates.
  • the radio base station includes means for determining whether or not an inter-AGW handover has occurred when handing over a mobile station to another adjacent base station, and another adjacent base station In the course of executing a communication procedure for connecting a mobile station that has been handed over to the core network, a handover between the user identifier of the mobile station and the AGW occurs for a specific access gateway device connected to the base station And a means for transmitting a control message including an event type indicating whether or not the event has been performed.
  • the radio base station releases the session with the mobile station connected to the core network, whether or not a handover between the user identifier of the mobile station and the AGW has occurred for the specific access gateway device A control message including an event type indicating that is transmitted.
  • the control message issued due to the inter-AGW handover is processed by the access gateway control device on behalf of the management server, so even when the inter-AGW handover increases, Increase in management server load can be prevented.
  • This effect becomes prominent when, for example, a user of a mobile station makes frequent round trips between AGW boundaries and frequent inter-AGW handovers occur.
  • FIG. 1 shows a configuration example of a wireless communication network to which the present invention is applied.
  • the wireless communication network of FIG. 1 is characterized by the presence of an AGW control device (hereinafter referred to as AGWC) 40.
  • the AGWC 40 communicates control messages with the AAA server 3 and the plurality of AGWs 5 (5A, 5B, 5C,%) As indicated by broken lines.
  • the AGWC 40 is connected to the core network 1 in a pair with the HA 2, and the communication between the AGWC 40 and the AAA server 3, the communication between the AGWC 40 and the AGW 5, and the communication between the AGW 5 and the HA 2 and the AAA server 3 This is performed via the core network 1.
  • FIG. 5 shows another configuration example of a wireless communication network to which the present invention is applied.
  • the wireless communication network of FIG. 5 is characterized in that each AGW 6 (6A, 6B, 6C,...) Is equipped with the functions of the AGWC 40 (40A, 40B, 40C,...) Shown in FIG. .
  • the AGW may have a configuration in which the functions of the AN 30E and the RNC 10C are integrated in addition to the function 40C of the AGWC 40.
  • communication between the AGW and the AGWC 40 is performed via the internal bus of the AGW 6.
  • FIG. 6 shows one embodiment of a mobile station (AT) 30.
  • the AT 30 includes a control unit (processor) 31 connected to the internal bus 39, a storage unit 32, a user interface (U-INF) 33, a baseband (BB) signal processing unit 38, and an antenna 35.
  • an RF (Radio Frequency) unit 36 connected to the baseband signal processing unit 38 and an intermediate frequency (IF) signal processing unit 37 connected between the baseband signal processing unit 38 and the RF unit 36.
  • input / output devices such as a keyboard, a display, a telephone microphone, and a speaker included in the AT are represented by one user interface (U-INF) 33.
  • the storage unit 32 stores communication control routines, protocol processing routines, other control programs executed by the control unit 31, and programs for various applications.
  • the storage unit 32 also includes a data storage area corresponding to the application program, a work area, a transmission / reception buffer area for temporarily storing transmission / reception data, and a memory for holding address information, IP flow management information, and the like. Area is reserved.
  • the RF unit 36 down-converts the radio signal received by the antenna 35 to an intermediate frequency and outputs it to the IF signal processing unit 37, and up-converts the transmission signal input from the IF signal processing unit 37 to the radio frequency,
  • the amplified transmission signal is output to the antenna 35.
  • the IF signal processing unit 37 performs signal processing of an intermediate frequency.
  • the IF signal processing unit 37 performs A / D (Analog to Digital) conversion on the reception signal input from the RF unit 36 and outputs the converted signal to the BB signal processing unit 38, and the baseband input from the BB signal processing unit 38.
  • the transmission signal is D / A (Digital to Analog) converted and output to the RF signal processing unit 36.
  • the BB signal processing unit 38 modulates the transmission data output from the control unit 31 and the baseband signal of the transmission control message, outputs the modulated data to the IF signal processing unit 37, and demodulates the received signal from the IF signal processing unit 37. And the synchronization control based on the received signal, and outputs the demodulated baseband received signal to the control unit 31.
  • the control unit 31 assembles a packet from the baseband received signal of the wireless transmission unit input from the BB signal processing unit 38, extracts the received message from the received packet addressed to its own terminal, and executes a program corresponding to the type of the received message To do.
  • the received message includes user data, it is processed by an application program corresponding to the received message. As a result, data is output to the user interface 33 or stored in a predetermined area of the storage unit 32.
  • the control unit 31 executes a communication control routine corresponding to the message type, and performs transmission / reception processing of the control message according to the communication procedure.
  • the transmission data generated by the application program or the control message generated by the communication control routine is assembled into a transmission packet by the control unit 32, and as a baseband signal in a sub-packet format of a wireless transmission unit at a predetermined transmission timing BB The signal is output to the signal processing unit 38.
  • FIG. 7 shows an embodiment of the base station (AN) 20.
  • the AN 20 includes a control unit (processor) 21, a storage unit 22, a RAN line interface (RAN-INF) unit 24, an RF unit 26 connected to an antenna 25, an intermediate frequency (IF) signal processing unit 27 and a baseband (BB) signal processing unit 28.
  • a control unit processing unit
  • storage unit storage unit
  • RAN-INF RAN line interface
  • RF unit 26 connected to an antenna 25
  • IF intermediate frequency
  • BB baseband
  • the storage unit 22 includes a communication control routine, a protocol processing routine, and other control programs executed by the control unit 21, a transmission / reception buffer area for temporarily storing transmission / reception data, address information, IP flow management information, and the like. And a management table area for storing accounting information, user authentication information, control information, and the like corresponding to the user identifier are secured.
  • the RF unit 26 down-converts the radio signal received by the antenna 25 to an intermediate frequency and outputs it to the IF signal processing unit 27, and up-converts the transmission signal input from the IF signal processing unit 27 to the radio frequency, The amplified transmission signal is output to the antenna 25.
  • the IF signal processing unit 27 performs intermediate frequency signal processing.
  • the BB signal processing unit 28 modulates the transmission data output from the control unit 21 and the baseband signal of the transmission control message, outputs the modulated data to the IF signal processing unit 27, and demodulates the received signal from the IF signal processing unit 27. And the demodulated baseband reception signal is output to the control unit 21.
  • the control unit 21 assembles an uplink packet from the baseband received signal of the radio transmission unit input from the BB signal processing unit 28, converts it into a packet format that conforms to the communication protocol between the AN and AGW, and performs RAN-INF The packet is transferred to the unit 24, and the downlink packet received from the RAN-INF unit 24 is converted into a packet format that conforms to the communication protocol of the wireless section, and transferred to the BB signal processing unit 28.
  • the control unit 21 executes a response operation corresponding to the received control message according to the communication control routine and the protocol processing routine. To do.
  • the base station (AN) 20 may be incorporated in the AGW 5 together with the RNC 10 as in the AN 20E of FIG. Further, as shown in FIG. 1, a base station 20E integrated with the AGW and base stations 20A to 20D independent of the AGW may be mixed in one wireless communication system.
  • FIG. 8 shows an embodiment of the access gateway device (AGW) 5.
  • the AGW 5 includes a control unit (processor) 51, a storage unit 52, a user interface (U-INF) 53 operated by a network administrator, and a RAN for connecting to the AN 20 and the RNC 10 that are interconnected by the internal bus 25.
  • a line interface (RAN-INF) 54 and a network line interface (NW-INF) unit 55 for connecting to the core network 1 are included.
  • the AGW 5 communicates with the HA 2, the AAA server 3, and the AGWC 40 via the core network 1 connected by the NW-INF unit 55.
  • the storage unit 52 stores a communication control routine, a protocol processing routine, a charging processing routine, an authentication processing routine, and other control programs executed by the control unit 51.
  • the storage unit 52 stores management information such as charging information, QoS information, and encryption key information in association with a transmission / reception buffer area for temporarily storing transmission / reception packets and a user identifier (ID). Management table area or file area is secured.
  • control unit 51 When the control unit 51 receives a packet from the RAN-INF 54 or the NW-INF 55, it converts the protocol as necessary, transfers the received packet to any other interface unit, and charges each user according to the charging processing routine. Collect information. When receiving a packet including a control message from these interface units, the control unit 51 performs a response operation corresponding to the received message in accordance with a communication control routine, a protocol processing routine, or an authentication processing routine.
  • FIG. 9 shows an embodiment of the stand-alone AGW controller (AGWC) 40 shown in FIG.
  • the AGWC 40 includes a control unit (processor) 41, a storage unit 42, a user interface (U-INF) 43 operated by a network administrator, and a network for connecting to the core network 1. And a line interface (NW-INF) unit 45.
  • the AGWC 40 communicates control messages in the form of IP packets with the AAA server 3 and the AGWC 40 via the core network 1 connected by the NW-INF unit 45.
  • the storage unit 42 stores a communication control routine executed by the control unit 41, a charging processing routine, an authentication processing routine, and other control programs.
  • the storage unit 42 also includes a transmission / reception buffer area for temporarily storing transmission / reception packets, a charging information table area for storing charging information in association with a user ID, user authentication information, QoS information, and encryption key information.
  • FIG. 10 shows an embodiment of the AGWC integrated access gateway (AGW) 6 shown in FIG.
  • the AGW 6 includes an AGW unit 5 having the AGW function shown in FIG. 8 and an AGWC 40 having the AGWC function shown in FIG. 9 between the processors in which the internal bus 50 and the internal bus 49 are arranged.
  • the interface 60 is combined.
  • the user interface (U-INT) 53 of the AGW unit 5 also serves as the user interface (U-INT) 44 of the AGWC 40 shown in FIG.
  • communication between the AGCW 40 and the AAA server 3 is performed via the NW-INF 45 via the core network 1, and communication between the AGW unit 5, the HA 2 and the AAA server 3 is performed via the NW-INF 55.
  • communication is performed via the core network 1, and communication between the AGW unit 5 and the AGWC 40 is performed via the internal bus via the interprocessor interface 60.
  • a communication sequence for charging control of the mobile station (AT) 30 in the wireless communication network shown in FIG. 1 will be described with reference to FIGS.
  • the AT 30 connected to the AGW 5A via the base station (AN) 20C has moved into the communication range of the base station (AN) 20D, so that the AT 30 is handed over from the AGW 5A to the AGW 5B.
  • the handover source (Source) AGW 5A is “S-AGW”
  • the handover source AN 20C is “S-AN”
  • the handover destination (Target) AGW 5B is “T-AGW”
  • the handover destination AN 20D is “T-AN”.
  • a radio access network composed of AN and RNC is called RAN.
  • the S-AN that completes the connection sequence 100A to 100C of the AT 30 sends a charging start request message (Accounting Request (Start, open)) including the user identifier, air link information, and event type to the S- It transmits to AGW (101A).
  • the event type “Open” indicates that this charging start request message is issued at the start of communication between terminals.
  • the control unit 51 of the S-AGW upon receiving an AccountingAccountRequest (Start, Open) message (101A), the control unit 51 of the S-AGW generates a user data record (UDR) from the received message and AT30 user billing information, A charging start request message (Accounting Request (Start, Open)) including the event type is transmitted to the AGWC 40 (101B).
  • the billing information indicates, for example, the AT 30 service time, the number of octets, and the like. In the UDR transmitted first with the start of inter-terminal communication, the billing information is in a null state.
  • FIG. 12 shows an example of a format of a charging control message 280 transmitted and received between the AGW (S-AGW or T-AGW) and the AGWC 40 in the present embodiment.
  • the charging control message 280 includes a message type 281, a message ID 282, a message length 283, charging information 284, a charging status 285, a charging user ID 186, and an event type 286.
  • the message type 281 indicates the type of whether this message is a charging request (Request) message or a response (Response) message to the charging request
  • the message ID 282 is an identifier for associating the charging request message with the response message, message length 283.
  • the charging status 285 is a distinction between the start and end (Stop) of the charging process
  • the charging user ID 186 is the user identifier of the AT 30 to be charged
  • the event type 286 is the trigger for issuing this charging control message.
  • the event type 286 includes “Open” indicating the start of communication between terminals, “HO” indicating handoff between AGWs, and “Close” indicating the end of communication between terminals.
  • the control unit 41 of the AGWC 40 executes an operation corresponding to the received message according to the charging control message reception processing routine 400 shown in FIG.
  • the control unit 41 determines the message type 281 of the received message (step 401). If the message type 281 is a response (Response), that is, the charging request message transmitted immediately before by the AGWC. If the response message is received, the control unit 41 transfers the received message to the source AGW of the accounting request message (415), and ends this routine.
  • Response response
  • the control unit 41 transfers the received message to the source AGW of the accounting request message (415), and ends this routine.
  • the control unit 41 determines the charging state 285 of the received message (402).
  • the charging state 285 is “Start”
  • the control unit 41 determines the event type 287 of the received message (403), and when the event type indicates the start of inter-terminal communication (“Open”), the storage unit
  • the accounting record corresponding to the accounting user ID 286 is generated in the accounting information table area 52 (404), the event type is removed from the received message (405), and the AAA server 3 receives the accounting start request message (Accounting ⁇ ⁇ ⁇ ⁇ ⁇ Request (Start)). Transfer (406) to end this routine.
  • step 403 when the event type 287 of the received message indicates handoff (“HO”), the control unit 41 stores the charging information stored in the record corresponding to the charging user ID 286 indicated by the received message from the charging information table. Is updated (407) according to the billing information 284 indicated by the received message, and this routine is terminated.
  • step 402 If the charging status 285 of the received message indicates charging end (“Stop”) in step 402, the control unit 41 determines the event type 287 of the received message (410), and the event type is handoff (“HO”). ), The charging information is updated in step 407, and this routine is terminated.
  • the control unit 41 updates the charging information of the record corresponding to the charging user ID 286 in the charging information table, as in step 407.
  • a billing end request message (Accounting ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ Request ⁇ ⁇ (Stop)) is generated based on the updated billing information and received message (412), and this is transmitted to the AAA server (413). Thereafter, the control unit 41 deletes unnecessary records from the billing information table (414), and ends this routine.
  • the control unit 41 of the AGWC 40 performs an event from the received message according to the accounting control message reception processing routine 400 described above.
  • the type is removed and transferred to the AAA server 3 as an accounting start request message (Accounting Request (Start)) (102A).
  • step 405 in FIG. 13 may be omitted, and Accounting Request (Start, Open) that includes the event type may be transferred from the AGWC 40 to the AAA server 3.
  • the AAA server 3 Upon receiving the charging start request message (Accounting ⁇ ⁇ ⁇ ⁇ ⁇ RequestAccount (Start)), the AAA server 3 starts charging processing for the user identifier of the AT 30 and sends a charging response message (to the AGWC 40 that is the transmission source of the charging start request message). (Accounting Response) is returned (103A). When receiving the charging response message (Accounting Response), the AGWC 40 transfers this to the S-AGW that is the transmission source of the charging start request message (Accounting Request (Start, Open)) (103B).
  • Steps 104A and 104B indicate that the AT 30 is in a data communication state with the communication partner via the S-AN and S-AGW. While the AT 30 is in the data communication state, the S-AGW and the S-AN collect the charging information of the AT 30 and store it in the storage unit.
  • a handover procedure is executed between the AT 30 and the HA 2 under the initiative of the AT or the RAN (105), and charging switching processing is performed along with the handover. Executed.
  • the S-AN determines that the handover being executed in step 105 is an inter-AGW handover
  • the S-AN sends a user ID and charging information and an inter-AGW handoff (“HO”) to the S-AGW.
  • a charging end request message (Accounting Request (Stop, HO)) including the event type indicated is transmitted (106A).
  • the S-AGW control unit 51 When receiving the AccountingAGRequest (Stop, HO) message, the S-AGW control unit 51 updates the charging information corresponding to the user ID of the AT 30 stored in the storage unit 52 according to the charging information indicated by the received message. A UDR including the updated billing information is generated. After that, an accounting end request message (Accounting ⁇ ⁇ ⁇ ⁇ ⁇ Request (Stop, HO)) including this UDR and an event type indicating an AGW handoff (“HO”) is transmitted to the AGWC 40 (107A).
  • the control unit 41 of the AGWC 40 updates the charge information corresponding to the user ID of the AT 30 stored in the storage unit 42 based on the UDR indicated by the received charge end request message.
  • the charging information is updated, for example, in a format in which the number of octets indicated by the UDR indicated by the charging end request message or the service time is added to the number of octets indicated by the charging information record corresponding to the user ID of the AT 30 or the service time. .
  • control unit 41 of the AGWC 40 that has received the charging end request message checks the event type indicated by the received message, and if the event type indicates a handoff between AGWs as in this case, The response message (AccountingAccountResponse) to the accounting end request message is returned to the S-AGW without sending the accounting end request message to AAA3 (108A).
  • a charging start request message (Accounting) indicating that the event type is an inter-AGW handover (“HO”) request (Start, HO)) is generated and transmitted to the T-AGW (109A).
  • AccountingWrequest (Start, HO)
  • the T-AGW Upon receipt of AccountingWrequest (Start, HO), the T-AGW generates a UDR from the received message and the billing information stored in the storage unit, and a billing start request including the UDR and event type (“HO”)
  • a message (Accounting Request (Start, HO)) is transmitted to the AGWC 40 (110A).
  • the control unit 41 of the AGWC 40 When receiving the charging start request message (Accounting Request ⁇ ⁇ (Start, HO)), the control unit 41 of the AGWC 40 performs charging corresponding to the user ID of the AT 30 indicated by the storage unit 42 according to the charging control message reception processing routine described with reference to FIG. Update to information.
  • the control unit 41 of the AGWC 40 transmits a charging start request message to the AAA 3 when a charging start request message indicating that the event type is an AGW handoff “HO” is received as in this case. And a response message (Accounting ⁇ ⁇ ⁇ ⁇ Response) to the charging start request message is returned to the T-AGW (111A).
  • the AT 30 enters data communication with the communication partner via the T-AN and T-AGW, and the T-AGW and T-AN collect the charging information of the AT 30. This is stored in the storage unit.
  • a session termination procedure is executed between the AT 30 and the T-AN and between the T-AN and the T-AGW (115A, 115B).
  • a charging end request message (Accounting Request (Stop, close)) including a user ID and charging information and an event type indicating the end of inter-terminal communication (“Close”) is transmitted to the T-AGW (116A).
  • the T-AGW When the T-AGW receives the charging end request message (Accounting Request (Stop, close)), the T-AGW updates the charging information corresponding to the user ID of the AT 30 stored in the storage unit and the charging information indicated by the received message. Then, a UDR including the user ID and the updated charging information is generated, and a charging end request message (AccountingAccountRequest (Stop, close)) including the UDR and the event type indicating “close” is transmitted to the AGWC 40 (116B). .
  • AccountingAccountRequest (Stop, close)
  • the control unit 41 of the AGWC 40 When receiving the charging end request message (Accounting ⁇ Request (Stop, close)), the control unit 41 of the AGWC 40, based on the charging information indicated by the received message, in the same manner as when Accounting Request (Stop, HO) is received.
  • the charging information corresponding to the user ID of the AT 30 stored in is updated.
  • the control unit 41 of the AGWC 40 checks the event type indicated by the received message. If the event type indicates the end of inter-terminal communication (“Close”) as in this case, the AT stored in the billing file A UDR is generated from the charging information corresponding to the user ID and the received message, and a charging end request message (Accounting Request (Stop)) including this UDR is transmitted to the AAA server 3 to end the charging process of the AT 30 (117A). ).
  • the AAA 3 Upon receiving (AccountingAccountRequest (Stop)) from the AGWC 40, the AAA 3 updates the charging information of the user of the AT 30, transmits a charging response message (Accounting Response) to the AGWC 40 (118A), and terminates the charging processing of the user. To do.
  • the AGWC 40 transfers this to the T-AGW that is the source of the charging end request message (118B).
  • a communication sequence for charging control of the mobile station (AT) 30 in the wireless communication network shown in FIG. 5 will be described with reference to FIG.
  • the same steps as those in the first embodiment are denoted by the same reference numerals as those in FIG. 11 to simplify the description.
  • AGWC access gateway control devices
  • the control unit 41 of the AGWC (hereinafter referred to as S-AGWC) associated with the handover source AGW charges the AT 30 stored in the storage unit 42.
  • the information is notified to the AAA server 3, and the charging process of the AT 30 is terminated.
  • the AGWC attached to the handover destination AGW (hereinafter referred to as T-AGWC) starts the charging process for the AT 30, and receives the charging end request generated when the communication of the AT 30 ends from the T-AGW Then, a charging end request message including the charging information of the AT 30 is transmitted to the AAA server 3, and the charging process of the AT 30 is ended.
  • the control unit 41 of the T-AGWC executes the same operation as the above-described S-AGWC to charge the AT 30. End the process.
  • a code indicating that communication is in progress for example, “Intermediate” may be set in the charging state 285 of the charging control message shown in FIG.
  • FIG. 15 shows a flowchart of a charging control message reception processing routine 400A executed by the control unit 41 of the AGWC in the second embodiment.
  • the control unit 41 determines the message type 281 (401).
  • the received message is a response message to the charging request message
  • the received message is the charging request message. (415), this routine is terminated.
  • the control unit 41 determines the charging state 285 indicated by the received message (402).
  • the charging state 285 indicates start (Start)
  • the charging user ID 286 is stored in the charging file area. Is generated (404), and the event type 287 of the received message is determined (403).
  • the control unit 41 transmits a response message to the transmission source AGW of the accounting request message (416), and then ends this routine. If the start of terminal-to-terminal communication (“Open”) is indicated, the event type is removed from the received message (405) and transferred to the AAA server as an accounting start request message (Accounting Request (Start)) (406). This routine is terminated.
  • the control unit 41 updates the charging information of the charging record corresponding to the charging user ID 286 stored in the charging file area. After (407), the event type 287 of the received message is determined (410).
  • the control unit 41 determines that the user data record (UDR) includes the charging information of the AT 30 (Accounting Request (Stop)). Is generated (412), this is transmitted to the AAA server (413), the unnecessary accounting record is deleted from the accounting file area (414), and this routine is terminated.
  • the control unit 41 When the event type indicates handoff (“HO”), the control unit 41 generates a billing information notification message including the billing information of the AT 30 as UDR (416), and transmits this to the AAA server (413). Then, the unnecessary accounting record is deleted from the accounting file area (414), and this routine is terminated.
  • the control unit 51 of the S-AGW upon receiving Accounting ⁇ Request (Start, AccountOpen) from the S-AT (101A), the control unit 51 of the S-AGW generates a UDR and generates a charging start request message (Accounting Request including the UDR and the event type). (Start, Open)) is transmitted to the AGWC 40 (S-AGWC) via the inter-processor interface (101B). Similar to the AGWC 40 shown in FIG. 11, the S-AGWC sends an Accounting Request (Start) message to the AAA server 3 (102A) and receives a response message from the AAA server 3 (103A). Then, the data is transferred to the S-AGW (103B).
  • the S-AGW control unit 51 When an inter-AGW handoff occurs and a charging termination request (Accounting Request (Stop, HO)) is transmitted from the S-AN to the S-AGW (106A), the S-AGW control unit 51 performs UDR including charging information. And an accounting end request message (Accounting Request (Stop, HO)) including the event type indicating handoff (HO) between AGWs, and transmits AGWC 40A (S-AGWC) via the inter-processor interface (107A).
  • Accounting Request Stop, HO
  • AGWC 40A AGWC 40A
  • the control unit 41 of the S-AGWC When the charging end request message is received, the control unit 41 of the S-AGWC generates a charging information notification message (Accounting Request (Intermediate)) according to the charging control message reception processing routine 400A described in FIG. It transmits to the AAA server 3 (120). Upon receiving the charging information notification message, the AAA server 3 updates the charging information of the AT user indicated by the charging user ID 286 according to the charging information 284 of the received message, and then returns a charging response message to the S-AGWC (121). . When receiving the charging response message from the AAA server 3, the control unit 41 of the S-AGWC transmits the charging response message to the S-AGW via the inter-processor interface (108A).
  • the T-AN When the inter-AGW handover occurs, the T-AN that has moved to the AT 30 sends a charging start request message (Accounting request (Start, HO)) indicating that the event type is inter-AGW handover (“HO”) to the T-AGW. Transmit (109A).
  • the T-AGW Upon receipt of Accounting request (Start, HO), the T-AGW transmits a received message (Accounting Request (Start, HO)) to the AGWC 40B (T-AGWC) via the inter-processor interface (110A).
  • the T-AGWC control unit 41 Upon receipt of Accounting Request (Start, HO), the T-AGWC control unit 41 generates a billing record corresponding to the user ID of the AT 30 according to the billing control message reception processing routine 400A described in FIG. A response message is returned to the AGW (111A).
  • a session termination procedure is executed between the AT 30 and the T-AN and between the T-AN and the T-AGW (115A, 115B).
  • a charging end request message (Accounting Request (Stop, close)) is transmitted to the T-AGW (116A).
  • the T-AGW receives the Accounting Request (Stop, close) message
  • the T-AGW generates a UDR including charging information, and sends a charging end request message including the UDR (Accounting Request (Stop, ⁇ close)) via the inter-processor interface. It transmits to AGWC (116B).
  • the control unit 41 of the T-AGWC 40 updates and updates the charging information corresponding to the user ID of the AT 30 according to the charging control message reception processing routine 400A shown in FIG.
  • a UDR including charging information is generated, and a charging end request message (Accounting Request (Stop)) including this UDR is transmitted to the AAA server 3 to end the charging process of the AT 30 (117A).
  • the AAA 3 Upon receiving (AccountingAccountRequest (Stop)) from the T-AGWC, the AAA 3 updates the charging information of the user ID of the AT 30 and transmits a charging response message (Accounting Response) to the T-AGWC (118A). The billing process is terminated.
  • the T-AGWC 40 receives the charging response message for the charging end request message (Accounting Request (Stop)), it transfers this to the S-AGW (118B).
  • FIG. 16 shows a modification of the communication sequence for charging control of the mobile station (AT) 30 in the wireless communication network shown in FIG. 5 as the third embodiment of the present invention.
  • the AGWC AGWC 40A in FIG. 16
  • the T-AGWC that is the handover destination is operated as a slave AGWC.
  • the sub AGWC notifies the main AGWC of the charging information of the AT 30 received from the AGW when the AT 30 ends the communication with the partner terminal or when it becomes the S-AGWC due to the occurrence of a new inter-AGW handover. To do.
  • the main AGWC collects the charging information of the AT 30 during connection with the AT 30, and then updates the charging information of the AT 30 according to the charging information notified from the AGWC.
  • the main AGWC receives the charging information of the AT 30 from the plurality of slave AGWCs.
  • the main AGWC generates a UDR including the charging information of the AT 30 in response to the charging end request message received from the AGW or the slave AGWC when the AT 30 ends the communication with the counterpart terminal, and ends the charging including the UDR.
  • a request message is transmitted to the AAA server 3.
  • steps 100A to 107A have the same sequence as that in FIG.
  • the S-AGWC 40A operates as the main AGWC.
  • the main AGWC 40A receives an accounting end request message (Accounting Request (Stop, HO)) indicating that the event type is an AGW handoff (“HO”) from the S-AGW (107A)
  • the main AGWC 40A receives the S-AGW.
  • a response message (Accounting Response) is returned (108A), and the charging process for the AT 30 is continued.
  • a charging start request message (Accounting request (Start, HO)) indicating that the event type is an inter-AGW handover (“HO”) is sent from the T-AN to which the AT 30 has moved to the T-AGW.
  • the billing start request message (Accounting Request (Start, HO)) is transferred (110A) from the T-AGW to the T-AGWC 40B via the inter-processor interface.
  • the T-AGWC 40B Upon receiving an Accounting Request (Start, HO) message from the T-AGW, the T-AGWC 40B detects that an inter-AGW handover has occurred from the event type of the received message, and operates as a sub-AGWC for the billing process of the AT 30 . In this case, the T-AGWC 40B transfers an Accounting Request (Start, HO) message to the main AGWC 40A (110B). When receiving the Accounting Request (Start, HO) message from the T-AGWC 40B, the main AGWC 40A transmits a response message (Accounting Response) to the T-AGW and waits for notification of charging information from the T-AGWC 40B.
  • Accounting Request Start, HO
  • a charging termination request message (Accounting Request (Stop, close) is transmitted from the T-AN to the T-AGW (116A), and the T-AGW to the T-AGWC
  • a billing end request message (Accounting Request (Stop, close)) including the billing information of the AT 30 is transmitted to the UDR via the interface (116B)
  • the T-AGWC that is operating as the slave AGWC for the billing processing of the AT 30
  • the Accounting Request (Stop, close) message is received from the T-AGW, the received message is transferred to the main AGWC 40A (116C).
  • the main AGWC 40A When the main AGWC 40A receives the Accounting Request (Stop, Close) message from the T-AGWC 40B, the main AGWC 40A updates the charging information of the AT 30 stored in the charging file according to the charging information 285 indicated by the received message, and is updated to UDR.
  • a billing end request message (Accounting Request (Stop)) including the billing information is generated and transmitted to the AAA server 3 (117B).
  • the main AGWC 40A receives a response message to the charging end request message from the AAA server 3 (118A), it transfers this to the T-AGW (118C).
  • step 16 transmits a charging start request message to the AAA server 3 (step 102A), to the other AGWC Applying a predetermined group address, multicasting a first control message indicating that it has become the main AGWC in the charging process of the AT 30 (charging user ID), and sending a charging end request message to the AAA server 3 Is transmitted (step 117B), the second control message indicating that the charging process of the AT 30 (charging user ID) is completed may be multicast to the other AGWC.
  • each AGWC when each AGWC receives the first control message, each AGWC stores the correspondence relationship between the charging user ID indicated by the received message and the transmission source address (address of the main AGWC) in the address management table, and the event from the AGW When a charging start request message whose type indicates an AGW handoff is received, the main AGWC address corresponding to the charging user ID indicated by the received message can be retrieved from the address management table. Further, when each AGWC receives the second control message, each AGWC may delete the correspondence between the charging user ID indicated by the received message and the transmission source address (address of the main AGWC) from the address management table. Note that the address of the main AGWC may be set as the main AGWC address in the data part of each message separately from the source address indicated by the header parts of the first and second control messages.
  • FIG. 17 shows an example of the format of the authentication control message 290 used in this embodiment.
  • the authentication control message 290 includes a message type 291, a message ID 292, a message length 293, a user ID 294, data 295, and an event type 296.
  • the message type 291 includes, for example, four types of authentication request (“Request”), response (“Response”), authentication success notification (“Success”), and re-authentication completion notification (“Finish”).
  • the message ID 292 indicates an identifier for associating the authentication request message with another message
  • the message length 293 indicates the length of the subsequent fields 294 to 296.
  • the user ID 294 indicates an identifier of a user to be authenticated.
  • the data 295 includes user authentication information in the case of an authentication request message, and includes information such as User / QoS profile and an encryption key in addition to the user authentication information in the case of an authentication success notification message.
  • the event type 296 indicates the type of event that triggered the issuance of the authentication request. In this embodiment, as the event type 296, “Open” indicating the start of inter-terminal communication and “HO” indicating the inter-AGW handoff are displayed. And “Close” indicating the end of communication between terminals.
  • FIG. 18 shows an example of a flowchart of an authentication control message reception processing routine 500 executed by the control unit 41 when the AGWC 40 receives an authentication control message.
  • EAP Extensible Authentication Protocol
  • the control unit 41 determines the message type 291 of the received message (501), and if the message type is an authentication request “Request”, the received message The event type 296 of (EAP Request) is determined (502). If the event type 296 does not indicate the inter-AGW handoff “HO”, the control unit 41 removes the event type as necessary, and then forwards the received message (EAP Request) to the AAA server 3 ( 503), this routine is terminated.
  • EAP Extensible Authentication Protocol
  • the control unit 41 executes the EAP re-authentication procedure with the AT in place of the AAA server 3 (504), and performs user authentication.
  • a re-authentication completion notification message (EAP Finish) including the authentication result and information such as QoS / User profile and MSK read from the authentication data storage area is sent to the TAGW that is the source of the authentication request message (505), and this routine is finished.
  • step 501 when the message type 291 of the received message is an authentication success notification “Success”, the control unit 41 stores the content of the data 295 indicated by the received message (EAP success) in the authentication data storage area of the storage unit 42 (506). ), The received message (EAP success) is transferred to the S-AGW that is the source of the authentication request message (EAP request) (507), and this routine is terminated.
  • step 501 if the message type 291 of the received message is other than the authentication request “Request” or the authentication success notification “Success”, for example, if the received message is a response message indicating that the authentication has failed, the control unit 41 The received message is transferred to the S-AGW (508), and this routine is finished.
  • FIG. 19 shows a communication sequence for authentication control of the mobile station (AT) 30 according to this embodiment.
  • the same reference numerals as those in FIG. 4 are applied to the same steps as those in FIG.
  • the S-AGW that has received the authentication request message (EAP Request) from the S-AN (step 133) transmits the received authentication request message to the AGWC 40 (134A), and the AGWC 40 receives it from the S-AGW.
  • the authentication request message is transferred to the AAA server 3 (134B).
  • the AAA server 3 Upon receiving the authentication request message, the AAA server 3 performs user authentication procedures (135A to 135D) with the AT via the AGWC 40, S-AGW, and S-AN, for example, according to EAP (Extended Authentication Protocol). Execute.
  • the AAA server 3 succeeds in user authentication of the AT 30, the AAA server 3 sends an authentication result (“success”) to the AGWC 40, a user identifier of the AT 30, authentication information for the identifier, and control information used in wireless communication, for example Then, an authentication success notification message including QoS / User profile, MSK (Master Session Key), etc. is transmitted (136A).
  • the control unit 41 of the AGWC 40 When receiving the authentication success notification message from the AAA server 3, the control unit 41 of the AGWC 40 stores the received message data 296 in the storage unit 42 and then transfers the received message to the S-AGW (136B). At this time, the control unit 41 of the AGWC 40 uses the correspondence between the user identifier of the AT 30 included in the received message and the authentication information for the identifier (user authentication data) for use in the subsequent authentication procedure (147A, 162B, 149A). ) Is stored in the storage unit 42. Thereafter, steps 137 to 140 similar to those in the prior art described with reference to FIG. 4 are executed, and the AT 30 enters an IP service state in which IP packets are transmitted to and received from the communication partner via the S-AN and S-AGW (141A 141B).
  • the AT 30 handover process (142) from the S-AGW to the T-AGW is executed, and between the AT 30 and the T-AN, A session setting procedure is executed (step 143).
  • T-AN information including the IP address of the T-AGW is notified from the T-AN to the AT 30 in the course of executing the session setting procedure, and the S including the IP address of the S-AGW is transmitted from the AT 30 to the T-AN.
  • -AGW information is notified.
  • the control unit 21 of the T-AN stores the S-AGW information received from the AT 30 in the storage unit 22 and, as will be described later, the S-AGW information and the T-AGW information are collated to generate this time. It is determined whether the handover is a handover between AGWs.
  • an EAP trigger message (EAP Request) is transmitted from the T-AN to the AT 30 (144), and a response message (EAP Response) including a user identifier is transmitted from the AT 30 to the T-AN. It is returned (145).
  • EAP Response a response message
  • the T-AN receives a response message (EAP Response) from the AT 30
  • the authentication request message including the user identifier indicated by the EAP Response as the user ID 194 and the event type 296 indicating the inter-AGW handover “HO”.
  • EAP Request is generated and transmitted to the T-AGW 40 (146).
  • the T-AGW transfers it to the AGWC 40 (147A).
  • the control unit 41 of the AGWC 40 determines the event type of the received message according to the routine 500 shown in FIG.
  • the control unit 41 detects that the event type is “HO”, that is, an inter-AGW handover has occurred, the control unit 41 uses the user authentication data of the AT 30 stored in the storage unit 42 to replace the AAA server 3, The user authentication (re-authentication) procedure of the AT 30 is executed (162A, 162B).
  • the control unit 41 of the AGWC 40 transmits a re-authentication completion notification message (EAP Finish) including QoS / User profile, MSK (Master Session Key), etc. to the T-AGW (149A) ).
  • the T-AGW Upon receipt of the re-authentication completion notification message (EAP Finish), the T-AGW stores a part of the QoS / User profile extracted from the received message and then transfers the received message (EAP Finish) to the T-AN (150A). ). Upon receiving the re-authentication completion notification message (EAP Finish), the T-AN stores information such as QoS / User profile, MSK extracted from the received message, and then forwards the received message (EAP Finish) to the AT 30 (151A) ).
  • T-AGW information including the IP address of the T-AGW is notified from the T-AN to the AT 30 (152), and the T-AGW information is notified from the AT 30 to the S-AN (153).
  • the control unit 21 of the S-AN collates the S-AGW information stored in the storage unit 22 in advance with the T-AGW information received from the AT 30 to determine whether or not the currently generated handover is an inter-AGW handover. Can be judged.
  • Steps 154 to 155B executed thereafter are the same as those in the prior art described with reference to FIG.
  • the AGWC 40 executes the user re-authentication procedure on behalf of the AAA server 3. Even when inter-handover frequently occurs, it is possible to prevent an increase in the load on the AAA server 30.
  • FIG. 20 shows a communication sequence for authentication control of the mobile station (AT) 30 executed in the wireless communication network shown in FIG. 5 as a fifth embodiment of the present invention.
  • AT mobile station
  • FIG. 20 shows a communication sequence for authentication control of the mobile station (AT) 30 executed in the wireless communication network shown in FIG. 5 as a fifth embodiment of the present invention.
  • the same reference numerals as those in FIGS. 4 and 19 are applied to the same steps as those in FIGS. 4 and 19 to simplify the description of the overlapping portions.
  • the AGWC access gateway control devices integrated with the AGW.
  • the AGWC AGWC 40A in FIG. 20
  • EAP Request the first authentication request message for the AT 30
  • the AGWC is operated as a slave AGWC.
  • the slave AGWC when an authentication request message is issued due to the inter-AGW handover, the slave AGWC that has received this message forwards it to the received authentication request message main AGWC, and the main AGWC replaces the AAA server, A user authentication procedure is executed with the AT 30.
  • FIG. 21 shows an example of a flowchart of an authentication control message reception processing routine 500A executed by the control unit 41 of the AGWC 40 in the present embodiment.
  • EAP Extensible Authentication Protocol
  • the control unit 41 determines the message type 291 of the received message (511), and if the message type is the authentication request “Request”, the received message The event type 296 of (EAP Request) is determined (512). If the event type 296 is not the AGW handoff “HO”, the control unit 41 transfers the received message (EAP Request) to the AAA server 3 (513).
  • EAP Extensible Authentication Protocol
  • control unit 41 multicasts a declaration message notifying that it has become the main AGWC in the charging process of the user ID indicated by the received message (EAP Request) to another AGWC (514), and the storage unit 42
  • a table entry indicating the correspondence between the user ID and the IP address of the main AGWC (own AGWC) is registered in the main AGWC management table formed in (515), and this routine is terminated.
  • the table entry indicating the correspondence between the user ID indicated by the declaration message and the IP address of the main AGWC is registered in the main AGWC management table formed in each storage unit 42. .
  • step 512 if the event type 296 of the received message indicates inter-AGW handoff “HO”, the control unit 41 determines whether the operation mode of the own AGWC is the primary AGWC or the secondary AGWC (516).
  • the operation mode of the AGWC can be determined by searching the main AGWC management table for the IP address of the main AGWC corresponding to the user ID indicated by the received message, and whether this matches the IP address of the own AGWC.
  • the control unit 41 executes the EAP re-authentication procedure with the AT instead of the AAA server 3. (517) Upon completion of user authentication, re-authentication is completed for the slave TAGW that is the transfer source of the authentication request message, including the authentication result and information such as QoS / User profile and MSK read from the authentication data storage area A notification message (EAP Finish) is transmitted (518), and this routine is terminated.
  • the control unit 41 transfers the received message to the main AGWC specified in the main AGWC management table (519), and ends this routine.
  • the control unit 41 stores the content of the data 295 indicated by the received message (EAP Success) in the authentication data storage area of the storage unit 42 (520 After that, the received message (EAP success) is transferred to the AGW connected via the inter-processor interface (521), and this routine is finished.
  • step 511 if the message type 291 of the received message is other than the authentication request “Request” or the authentication success notification “success”, for example, the response message indicating that the received message has failed authentication, or the re-authentication result EAP In the case of the Finish message, the control unit 41 transfers the received message to the AGW connected via the inter-processor interface (522), and ends this routine.
  • the S-AGW that has received the authentication request message (EAP Request) from the S-AN (step 133) transmits the authentication request message to the AGWC 40A via the inter-processor interface 60. Then, the AGWC 40A transfers the authentication request message received from the S-AGW to the AAA server 3 (134B).
  • the session setting procedure (step 143) is executed between the AT 30 and the T-AN when a handover occurs.
  • the communication sequence up to this point is basically the same as that of the fourth embodiment described with reference to FIG. 19 except that the AGWC 40 is replaced with the AGWC 40A.
  • an EAP trigger message (EAP Request) is transmitted from the T-AN to the AT 30 (144), and a response message (EAP Response) including a user identifier is transmitted from the AT 30 to the T-AN. It is returned (145).
  • EAP Response the response message
  • the T-AN receives the response message (EAP Response) from the AT 30, the T-AN includes the user identifier indicated by the EAP Response message as the user ID 194, and the event type 296 indicates an inter-AGW handover “HO” authentication request message (EAP Request). Is transmitted to the T-AGW 40 (146).
  • the T-AGW transfers the authentication request message (EAP Request) to the AGWC 40B via the inter-processor interface (147A ′).
  • the control unit 41 of the AGWC 40B operates as a slave AGWC and transfers the received message to the AGWC 40A serving as the main AGWC according to the routine 500A shown in FIG. (161).
  • the control unit 41 of the main AGWC 40A determines the event type of the received message according to the routine 500A shown in FIG. 21, and executes the user authentication (re-authentication) procedure of the AT 30 on behalf of the AAA server 3 (162A, 162B). .
  • the control unit 41 of the main AGWC 40A notifies the sub-AGWC 40B of a re-authentication completion notification message (EAP / Finish) including QoS / User profile, MSK (Master Session Key), etc. Is transmitted (163).
  • the sub AGWC 40B When the sub AGWC 40B receives the re-authentication completion notification message (EAPAGFinish), it transfers it to the T-AGW (149A). After storing a part of the QoS / User profile extracted from the received message, the T-AGW transfers the received message (EAP Finish) to the T-AN (150A). Upon receiving the re-authentication completion notification message (EAP Finish), the T-AN stores information such as QoS / User profile, MSK extracted from the received message, and then forwards the received message (EAP Finish) to the AT 30 (151A) ). Thereafter, steps 152 to 155B similar to those in FIGS. 4 and 19 are executed.
  • the AGWC that has received the first authentication request message multicasts the main AGWC declaration message indicating the correspondence between the user ID to be authenticated and the IP address of the main AGWC to the other AGWC.
  • the slave AGWC that has received the authentication request due to the inter-AGWC handover may inquire the IP address of the main AGWC from other AGWCs.
  • FIG. 22 shows that with the AT 30 handover, the T-AN 20D transmits an authentication request message (EAP Request) indicating that the event type is “HO” to the AGW 5B (180), and the AGW 5B receives the received authentication request message. Is transferred to the AGWC 40B (181). At this point, the AGWC 40B does not have information necessary for the authentication process for the user ID indicated by the authentication request message (EAP Request).
  • EAP Request authentication request message
  • the AGWC 40B generates an address request message (Address Request) including the user ID to be authenticated extracted from the authentication request message and the IP address of the AGWC 40B indicating the inquiry source, and sets a predetermined group address as the destination IP address. Apply to address, multicast address request message to other AGWC (180-1 to 180-n).
  • the other AGWC that has received the address request message checks whether or not the information necessary for the authentication process is held in the storage unit 42 for the user ID specified by the received message.
  • the AGWC holding the information necessary for the authentication process is the AGWC 40A that is the main AGWC in the user ID authentication process, and the AGWC 40A returns a response message (Address Response) to the AGWC 40B (183).
  • the AGWC 40B can acquire the IP address of the main AGWC by receiving the response message, and can transfer (184) the authentication request message to the AGWC 40A using this as the destination address.
  • the address inquiry method described above can also be applied to the accounting process described with reference to FIG.
  • FIG. 23 shows an inter-AGW handover determination routine 600T executed by the control unit 21 of the AN 20 when it becomes the destination (T-AN) of the AT 30 due to handover between base stations.
  • Each AN 20 stores the IP address of the specific AGW 5 to which the AN 20 belongs in the storage unit 22 in advance, and receives an EAP Response message including a user identifier from a new session-connected AT 30 (for example, FIG. 19, Step 145 in FIG. 20, the control unit 21 applies the IP address of the specific AGW 5 to the destination address, and transmits an authentication request message (EAP Request) for user authentication of the AT 30 to the AGW.
  • the inter-AGW handover determination routine 600T is executed, for example, when the IP address of the S-AGW is received from the AT 30 in the session start procedure shown in step 143 of FIGS.
  • the control unit 21 of the AN 30 receives the IP address of the S-AGW (601), the IP address of the specific AGW (T-AGW) stored in the storage unit 22 and the IP address of the S-AGW received from the AT 30 Are matched (602). If the IP addresses match, the control unit 21 determines that a handover has occurred within the same subnet, and stores an event type code indicating “Open” in the event type storage area of the storage unit 22 (603). . If the IP address of the T-AGW and the IP address of the S-AGW do not match, the control unit 21 determines that an inter-AGW handover has occurred, and an event indicating the handover “HO” in the event type storage area The type code is stored (604).
  • the control unit 21 of the AN 30 When generating the authentication request message, the control unit 21 of the AN 30 sets the event type code indicated by the event type storage area in the event type field 296. This enables the AGWC 40 to determine whether the authentication request message received from the AGW is issued prior to the IP service or is issued due to the inter-AGW handover during the IP service. It becomes.
  • FIG. 24 shows an inter-AGW handover determination routine 600S that is executed by the control unit 21 of the AN 20 when it becomes the movement source (S-AN) of the AT 30 by the handover between base stations.
  • the inter-AGW handover determination routine 600S is executed when the IP address of the T-AGW is received from the destination AN (T-AN) of the AT 30 as shown in step 152 of FIGS. 19 and 20, for example.
  • the control unit 21 of the AN 30 Upon receiving the IP address of the T-AGW (611), the control unit 21 of the AN 30 receives the IP address of the specific AGW (in this case, S-AGW) stored in the storage unit 22 and the T-received from the AT 30.
  • the IP address of AGW is collated (612). If the IP addresses match, the control unit 21 determines that a handover has occurred within the same subnet, and stores an event type code indicating “Close” in the event type storage area of the storage unit 22 (613). .
  • control unit 21 determines that an inter-AGW handover has occurred, and an event indicating the handover “HO” in the event type storage area
  • the type code is stored (614).
  • the communication sequence is simplified.
  • the charging request message in the first and second embodiments is transmitted after the user authentication processing described in FIGS. 16, 19, and 20 is executed. Is done. Therefore, the event type determined in the above-described inter-AGW handover determination routine 600 can also be applied to the charging request message transmitted in the first and second embodiments.
  • steps 143 to 154 shown in FIG. 19 are executed immediately after the handover procedure 105. Therefore, the S-AN can apply the event type code determined in the inter-AGW handover determination routine 600S to the accounting termination request (Accounting Request (Stop, HO)) transmitted at 106A in the step of FIG.
  • FIG. 25 shows an example of a user information management table 700 that the AGWC 40 forms in the file area of the storage unit 42.
  • the user information management table 700 includes a plurality of table entries having a user ID 701.
  • the user information management table 700 shown here serves as both a user authentication management table and a billing management table.
  • Each table entry includes an authentication information field 702, a user profile field 703, and a QoS information field. 704, an MSK field 705, and a billing information field 706.
  • the billing information field 706 stores a plurality of information items such as service start time, service time, and transmission data amount.
  • the AGWC 40 when the AGWC 40 receives an authentication request response (EAP success) message from the AAA server 3, the AGWC 40 adds a table entry corresponding to the user ID indicated by the received message to the user information management table 700.
  • the entry stores authentication information, user profile, QoS, and MSK extracted from the received message.
  • the AGWC 40 receives a charging request message from the AGW after executing the user authentication procedure, the AGWC 40 searches the user information management table 700 for a table entry corresponding to the user ID indicated by the received message, and stores the service start time. The billing process corresponding to the user ID is started.
  • the AGWC 40 applies the authentication information and the user profile information stored in the user information management table 700 and receives the user re-authentication when receiving the authentication request message indicating the event type “HO” from any AGW. Perform the procedure. Further, when the accounting end request message having the event type “HO” is received from any AGW, the AGWC 40 searches the user information management table 700 for a table entry corresponding to the user ID indicated by the received message. Then, the contents of the charging information field 706 are updated based on the charging information indicated by the received message.
  • the AGWC 40 When the AGWC 40 receives a charge end request message whose event type indicates “Close” from any AGW, the AGWC 40 searches the user information management table 700 for a table entry corresponding to the user ID indicated by the received message, After updating the contents of the information field 706 according to the charging information indicated by the received message, a charging end request message including the charging information updated in UDR is transmitted to the AAA server 3. A table entry that becomes unnecessary after the accounting process is completed may be deleted from the user information management table 700 at this point. Further, in the embodiment in which the address of the main AGWC is notified to other AGWC as in the third and fifth embodiments, the main AGWC causes the other AGWC to terminate the charging for the specific user ID at this time. By notifying, the task as the main AGWC can be completed.
  • the present invention is effective for a wireless communication network including a management server such as a user authentication / access authorization / billing server.
  • wireless communication network to which this invention is applied The figure which shows the structural example of the conventional radio
  • the figure which shows one Example of AGGW integrated AGW6 shown in FIG. The communication sequence diagram for the accounting control which shows 1st Example of this invention.
  • the communication sequence diagram for charge control which shows 3rd Example of this invention.
  • the flowchart of the inter-AGW handover determination routine 600T executed by the control unit 21 of the AN 20.
  • 1 Core network
  • 2 Home agent (HA)
  • 3 AAA server
  • 4 Access gateway (AGW)
  • 10 Radio resource controller (RNC)
  • 20 Base station (AN)
  • 30 Mobile station (AT)
  • 40 Access gateway controller (AGWC)

Landscapes

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

Abstract

L'invention porte sur un système de radiocommunication dans lequel un contrôleur de passerelle d'accès (AGWC) est placé entre une pluralité de dispositifs de passerelle d'accès (AGW) qui hébergent chacun au moins une station de base radio et un serveur AAA (serveur de gestion) connecté à un coer de réseau, et un message de commande délivré en résultat du transfert entre les AGW est traité par les AGW à la place du serveur AAA pour ainsi réduire une charge non nécessaire sur l'échange de message entre les AGW et le serveur AAA.
PCT/JP2009/000411 2008-03-25 2009-02-03 Système de radiocommunication, contrôleur de passerelle et station de base Ceased WO2009118980A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2010505289A JP5055428B2 (ja) 2008-03-25 2009-02-03 無線通信システム、ゲートウェイ制御装置および基地局

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2008-078175 2008-03-25
JP2008078175 2008-03-25

Publications (1)

Publication Number Publication Date
WO2009118980A1 true WO2009118980A1 (fr) 2009-10-01

Family

ID=41113202

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2009/000411 Ceased WO2009118980A1 (fr) 2008-03-25 2009-02-03 Système de radiocommunication, contrôleur de passerelle et station de base

Country Status (2)

Country Link
JP (1) JP5055428B2 (fr)
WO (1) WO2009118980A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011068214A1 (fr) * 2009-12-04 2011-06-09 株式会社エヌ・ティ・ティ・ドコモ Procédé de communication mobile et appareil de passerelle
JP2013522983A (ja) * 2010-03-18 2013-06-13 ゼットティーイー コーポレイション アンカーオーセンティケータのリロケーション方法及びシステム
WO2013128513A1 (fr) * 2012-03-01 2013-09-06 Nec Corporation Système de communication, appareil de commande de passerelle, appareil de commande de chemin, procédé de communication et programme
JP2017506028A (ja) * 2014-01-08 2017-02-23 アルカテル−ルーセント 第三者ユーザのためにコアネットワークサービスを提供するための方法およびネットワーク要素

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005260435A (ja) * 2004-03-10 2005-09-22 Matsushita Electric Ind Co Ltd 移動通信システム及び無線ネットワーク制御方法
WO2007002659A2 (fr) * 2005-06-27 2007-01-04 Airvana, Inc. Transferts dormants inities par reseau
JP2007538476A (ja) * 2004-05-18 2007-12-27 エアヴァナ，インコーポレーテッド 無線ネットワーク・コントロール

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005260435A (ja) * 2004-03-10 2005-09-22 Matsushita Electric Ind Co Ltd 移動通信システム及び無線ネットワーク制御方法
JP2007538476A (ja) * 2004-05-18 2007-12-27 エアヴァナ，インコーポレーテッド 無線ネットワーク・コントロール
WO2007002659A2 (fr) * 2005-06-27 2007-01-04 Airvana, Inc. Transferts dormants inities par reseau

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011068214A1 (fr) * 2009-12-04 2011-06-09 株式会社エヌ・ティ・ティ・ドコモ Procédé de communication mobile et appareil de passerelle
JP2011120110A (ja) * 2009-12-04 2011-06-16 Ntt Docomo Inc 移動通信方法及びゲートウェイ装置
CN102648649A (zh) * 2009-12-04 2012-08-22 株式会社Ntt都科摩 移动通信方法和网关装置
JP2013522983A (ja) * 2010-03-18 2013-06-13 ゼットティーイー コーポレイション アンカーオーセンティケータのリロケーション方法及びシステム
US9032485B2 (en) 2010-03-18 2015-05-12 Zte Corporation Anchor authenticator relocation method and system
WO2013128513A1 (fr) * 2012-03-01 2013-09-06 Nec Corporation Système de communication, appareil de commande de passerelle, appareil de commande de chemin, procédé de communication et programme
JP2015508945A (ja) * 2012-03-01 2015-03-23 日本電気株式会社 通信システム、ゲートウェイ制御装置、経路制御装置、通信方法及びプログラム
JP2017506028A (ja) * 2014-01-08 2017-02-23 アルカテル−ルーセント 第三者ユーザのためにコアネットワークサービスを提供するための方法およびネットワーク要素

Also Published As

Publication number Publication date
JPWO2009118980A1 (ja) 2011-07-21
JP5055428B2 (ja) 2012-10-24

Similar Documents

Publication Publication Date Title
JP4746044B2 (ja) 状態転送にコアベースのノードを使用するよう拡張された技術
US7962142B2 (en) Methods and apparatus for the utilization of core based nodes for state transfer
JP4194840B2 (ja) 無線パケットデータサービス接続のハンドオフのための方法および装置
CN100592696C (zh) 在移动通信系统和无线局域网之间进行耦合的系统和方法
US20050220048A1 (en) Internet connection service method, system, and medium for mobile nodes
KR20060059064A (ko) 이동통신 시스템과 이를 위한 핸드오프 방법
US7561692B2 (en) Method of authenticating mobile terminal
JP2007526685A (ja) アクセスポイント間のステーション移動性
WO2006080749A1 (fr) Systeme et procede de transfert intercellulaire de mobile a double mode pour la connexion de systeme de communication mobile et de reseau sans fil
JP2005027314A (ja) モバイルＩＰｖ６ホームエージェントのシームレスハンドオーバー方法
KR100298371B1 (ko) 패킷 이동 통신망의 핸드 오버 수행 방법
CN100593929C (zh) 一种无线分组网络中的移动切换方法
JP5055428B2 (ja) 無線通信システム、ゲートウェイ制御装置および基地局
KR100485355B1 (ko) 무선랜에서의 분산 시스템간 핸드오프 방법
US9160547B2 (en) Method and devices for managing a data flow transfer
CN100563163C (zh) 一种ngn网络系统及实现移动性管理的方法
KR101037464B1 (ko) Ａｓｎ간 핸드오버 처리 방법 및 그 방법을 지원하는 ａｓｎ-ｇｗ
CN101772105A (zh) 切换方法以及接入网关
KR20090054145A (ko) 네트워크 기반의 고속 핸드오버 수행 방법
CN101325804B (zh) 获取密钥的方法、设备及系统
US20070274259A1 (en) Reducing Handoff Latency for a Mobile Station
KR102230823B1 (ko) 상황인지 기반 트래픽 경로최적화 관리 방법
KR20080010990A (ko) 프록시 이동 아이피를 사용하는 이동통신 시스템에서 이동아이피를 지원하는 이동 노드의 서비스 방법 및 시스템
HK1141647A (en) Enhanced techniques for using core based nodes for state transfer
CN106332045A (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: 09725476

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010505289

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09725476

Country of ref document: EP

Kind code of ref document: A1