WO2010119728A1 - 移動通信システム、基地局、ゲートウェイ装置、コアネットワーク装置、通信方法 - Google Patents
移動通信システム、基地局、ゲートウェイ装置、コアネットワーク装置、通信方法 Download PDFInfo
- Publication number
- WO2010119728A1 WO2010119728A1 PCT/JP2010/053204 JP2010053204W WO2010119728A1 WO 2010119728 A1 WO2010119728 A1 WO 2010119728A1 JP 2010053204 W JP2010053204 W JP 2010053204W WO 2010119728 A1 WO2010119728 A1 WO 2010119728A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- core network
- message
- call
- mobile station
- network device
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- 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/16—Gateway arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/04—Special services or facilities for emergency applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
Definitions
- the present invention relates to a mobile communication system, a base station, a gateway device, a core network device, and a communication method.
- HNB Home NodeB
- a form of use as a small wireless base station for home use or a form of use as a small wireless base station in a company is considered. It has been.
- CSG Cellular Subscriber Group
- the third generation mobile communication system shown in FIG. 1 includes an HNB 20, a femto base station gateway (Home NodeB GW, hereinafter abbreviated as HNB-GW) 30, a circuit switching center (Mobile Switching Center, hereinafter abbreviated as MSC). 40, a packet switching station (Serving GPRS Support Node, hereinafter abbreviated as SGSN) 50, and third-generation mobile stations 10-1 and 10-2.
- HNB Home NodeB GW
- MSC Mobile Switching Center
- the mobile station 10-1 is a valid mobile station.
- the mobile station 10-2 is a mobile station that attempts to receive service by the HNB 20 illegally, and is hereinafter referred to as an unauthorized mobile station 10-2.
- the mobile station 10 is referred to.
- the HNB 20 is connected to the operator's core network via the HNB-GW 30.
- the core network includes, as core network devices, an MSC 40 that controls circuit switching and an SGSN 50 that controls packet switching.
- the HNB 20 When the HNB 20 supports the CSG function, the HNB 20 notifies the mobile station 10 residing in its own area of the CSG identifier (CSG identity) of its own CSG cell (CSG Cell).
- CSG identity CSG identifier
- CSG Cell CSG Cell
- the mobile station 10-1 decodes the CSG identifier broadcast from the HNB 20, and determines whether or not the CSG identifier is included in its own CSG list.
- the mobile station 10-1 can camp on the CSG cell in which it is located and receive various services such as outgoing and incoming calls.
- the mobile station 10-1 selects an appropriate CSG cell different from the CSG cell without camping on the CSG cell in which it is located. Perform the action.
- the MSC 40 or SGSN 50 checks the IMSI (International Mobile Subscriber Identity) of the mobile station 10 and the CSG identifier of the CSG cell in which the mobile station 10 is located, so that the mobile station 10 Restrict access to HNB20 by 3GPP (TS25.467 Ver8.0.0 5.1.3).
- IMSI International Mobile Subscriber Identity
- the CSG function is a function introduced from Release 8 of 3GPP, there are cases where the mobile station 10-1 prior to Release 8 does not support the CSG function. There are also cases where the HNB 20 does not support the CSG function.
- the HNB 20 performs an identification procedure (3GPP TS24.008 Ver8.4.0) on the mobile station 10-1 to inquire the IMSI of the mobile station 10-1, and the mobile station 10-1 -1 is registered in the HNB-GW30, the HNBAP (HNB Application Part): UE REGISTER REQUEST procedure (3GPP TS25.469 Ver8.0.0) is performed on the HNB-GW30.
- the HNB-GW 30 regulates access by checking whether the IMSI of the mobile station 10-1 can access the HNB 20.
- the HNB-GW 30 determines that the mobile station 10-1 can access the HNB 20, the HNB-GW 30 notifies the HNB 20 that access is permitted by an HNBAP: UE REGISTER ACCEPT message. Thereby, the service by the HNB 20 is provided to the mobile station 10-1.
- the HNB-GW 30 determines that the unauthorized mobile station 10-2 cannot access the HNB 20, and notifies the HNB 20 that access is not permitted by the HNBAP: UE REGISTER REJECT message.
- the RRC Radio Resource Control
- the MSC 40, the SGSN 50, or the HNB-GW 30 regulates access based on the IMSI of the mobile station 10, so that unauthorized access to the HNB 20 is not permitted. Even if the station 10-2 makes a call, access to the HNB 20 is rejected by the mobile communication network during the signal establishment procedure.
- the mobile station 10-1 determines the cause of the establishment request in the RRC: RRC CONNECTION REQUEST message or RRC: INITIAL DIRECT TRANSFER that is sent to the HNB 20 at the time of RRC connection establishment request or signaling connection establishment request.
- RRC RRC CONNECTION REQUEST message
- RRC INITIAL DIRECT TRANSFER
- the HNB 20 sets the Registration Cause parameter of the HNBAP: UE REGISTER REQUEST message to be transmitted to the HNB-GW 30 to the “Emergency call” value.
- the HNB-GW30 does not implement access restrictions based on IMSI (3GPP TS25.467 Ver8.0.0 5.1.2).
- FIG. 2 shows the configuration of the RRC: RRC CONNECTION REQUEST message
- FIG. 3 shows the configuration of the RRC: INITIAL DIRECT TRANSFER message
- FIG. 4 shows the configuration of the Establishment Cause parameter in the RRC protocol
- 5 shows the configuration of the HNBAP: UE REGISTER REQUEST message
- FIG. 6 shows the configuration of the Registration Cause parameter in the HBNAP protocol.
- the above-described technology skips the access restriction of the HNB-GW 30 and permits the mobile station 10 to access the HNB 20.
- the Establishment Cause parameter in the RRC protocol is false as “Emergency call” and is not subject to the access restrictions of the HNB-GW30. As a result, access to the HNB 20 becomes possible.
- Such an illegal mobile station 10-2 can be easily created by modifying the software so that only the Establishment Cause parameter is altered.
- the RRC: RRC CONNECTION REQUEST message that is transmitted from the legitimate mobile station 10-1 to the common channel (RACH: Random Access Channel) and is not protected or tampered with is decoded, and the Establishment Cause parameter is set to “Emergency call”.
- a device that encodes an RRC: RRC CONNECTION REQUEST message and transmits it to the HNB 20 may be interposed. In this case, even the legitimate mobile station 10-1 is regarded as the unauthorized mobile station 10-2 as described above.
- Such an illegal mobile station 10-2 causes the following problems.
- the HNB 20 installed at home or in the company is illegally used by the unauthorized mobile station 10-2.
- the unauthorized mobile station 10-2 performs normal transmission by making a call through the HNB 20.
- a billing service that is cheaper than the billing service can be illegally received.
- a content service for a specific user is illegally received by the illegal mobile station 10-2.
- the core network device cannot know that the mobile station 10 has made a call as an emergency call.
- the HNB-GW 30 performs a call release process of the mobile station 10 that has made a false call as an emergency call. For this purpose, the HNB-GW 30 needs to know whether the call type that the mobile station 10 has actually called is an emergency call.
- the HNB-GW 30 cannot know the call type that the mobile station 10 has actually called.
- An object of the present invention is to provide a mobile communication system, a base station, a gateway device, a core network device, and a communication method that allow a core network device to know that a mobile station has made an emergency call. .
- Another object of the present invention is to provide a mobile communication system, a gateway device, a core network device, and a communication method in which the gateway device can know the call type that the mobile station has actually called.
- the first mobile communication system of the present invention is: A mobile communication system comprising: a mobile station; a base station that performs radio communication with the mobile station; a gateway device that connects the base station to a core network; and a core network device that is disposed in the core network.
- the base station A control unit including information indicating that the mobile station has made an outgoing call as an emergency call in a message;
- the core network device is: A receiving unit configured to receive the message transmitted from the base station;
- the second mobile communication system of the present invention is A mobile communication system comprising: a mobile station; a base station that performs radio communication with the mobile station; a gateway device that connects the base station to a core network; and a core network device that is disposed in the core network.
- the gateway device is A control unit including information indicating that the mobile station has made an outgoing call as an emergency call in a message;
- the core network device is: A receiving unit configured to receive the message transmitted from the gateway device;
- the third mobile communication system of the present invention is A mobile communication system comprising: a mobile station; a base station that performs radio communication with the mobile station; a gateway device that connects the base station to a core network; and a core network device that is disposed in the core network.
- the core network device is: A control unit that includes in a message information indicating that the call type originated by the mobile station is an emergency call; A transmission unit for transmitting the message to the gateway device;
- the gateway device is A receiving unit configured to receive the message transmitted from the core network device;
- the base station of the present invention A base station connected to a core network device arranged in the core network via a gateway device, A control unit that includes in the message information indicating that the mobile station has made a call as an emergency call; A transmission unit that transmits the message to the core network device.
- the first gateway device of the present invention is: A gateway device for connecting a base station to a core network device arranged in a core network, A control unit that includes in the message information indicating that the mobile station has made a call as an emergency call; A transmission unit that transmits the message to the core network device.
- the second gateway device of the present invention is A gateway device for connecting a base station to a core network device arranged in a core network, A receiving unit configured to receive a message transmitted from the core network device and including information indicating that a call type originated by the mobile station is an emergency call;
- the first core network device of the present invention is: A core network device arranged in the core network, A receiving unit configured to receive a message transmitted from the base station and including information indicating that the mobile station has made a call as an emergency call;
- the second core network device of the present invention is: A core network device arranged in the core network, A receiving unit configured to receive a message transmitted from the gateway device and including information indicating that the mobile station has made a call as an emergency call;
- the third core network device of the present invention A core network device arranged in the core network, A control unit that includes in a message information indicating that the call type originated by the mobile station is an emergency call; A transmission unit that transmits the message to the gateway device.
- the first communication method of the present invention includes: A mobile communication system comprising: a mobile station; a base station that performs radio communication with the mobile station; a gateway device that connects the base station to a core network; and a core network device that is disposed in the core network.
- a communication method The base station includes in a message information indicating that the mobile station originated as an emergency call; The base station transmitting the message to the core network device; The core network device receiving the message transmitted from the base station.
- the second communication method of the present invention includes: A mobile communication system comprising: a mobile station; a base station that performs radio communication with the mobile station; a gateway device that connects the base station to a core network; and a core network device that is disposed in the core network.
- a communication method The gateway device includes in a message information indicating that the mobile station has made a call as an emergency call; The gateway device transmitting the message to the core network device; The core network device receiving the message transmitted from the gateway device.
- the third communication method of the present invention is: A mobile communication system comprising: a mobile station; a base station that performs radio communication with the mobile station; a gateway device that connects the base station to a core network; and a core network device that is disposed in the core network.
- the core network device includes in a message information indicating that the call type originated by the mobile station is an emergency call; The core network device transmitting the message to the gateway device; The gateway device receiving the message transmitted from the core network device.
- the fourth communication method of the present invention is: A communication method by a base station connected to a core network device arranged in a core network via a gateway device, Including in the message information indicating that the mobile station originated as an emergency call; Transmitting the message to the core network device.
- the fifth communication method of the present invention is: A communication method by a gateway device that connects a base station to a core network device arranged in a core network, Including in the message information indicating that the mobile station originated as an emergency call; Transmitting the message to the core network device.
- the sixth communication method of the present invention is: A communication method by a gateway device that connects a base station to a core network device arranged in a core network, Receiving a message transmitted from the core network device and containing information indicating that the call type originated by the mobile station is an emergency call.
- the seventh communication method of the present invention A communication method by a core network device arranged in a core network, Receiving a message transmitted from the base station and including information indicating that the mobile station has made a call as an emergency call.
- the eighth communication method of the present invention is: A communication method by a core network device arranged in a core network, Receiving a message transmitted from the gateway device and including information indicating that the mobile station has made a call as an emergency call.
- the ninth communication method of the present invention A communication method by a core network device arranged in a core network, Including in the message information indicating that the call type originated by the mobile station is an emergency call; Transmitting the message to the gateway device.
- the base station or the gateway device includes information indicating that the mobile station has made a call as an emergency call in a message and transmits the message to the core network device. .
- the core network device can know that the mobile station has made a call as an emergency call.
- the core network device includes information indicating that the call type originated by the mobile station is an emergency call, and transmits the message to the gateway device.
- the gateway device can know that the call type that the mobile station has actually called is an emergency call.
- FIG. 1 is a block diagram illustrating a configuration of an HNB-GW according to a first embodiment of this invention.
- (First embodiment) 7 to 10 show configurations of the HNB 20, the HNB-GW 30, the MSC 40, and the SGSN 50 according to the present embodiment, respectively.
- the HNB 20 of the present embodiment includes a control unit 21A that includes information indicating that the mobile station 10 has made an emergency call in a RANAP (Radio Access Network Application Part) protocol message, and the RANAP protocol. And a transmission unit 22A for transmitting the message to the HNB-GW 30.
- the RANAP protocol message is a message in the application layer of the radio access network, and has, for example, yesterday when the CC / MM signal transmitted / received between the UE and the core network device is transparently transferred within the RAN. .
- the HNB-GW 30 of the present embodiment includes a receiving unit 31A that receives a RANAP protocol message from the HNB 20, a control unit 32A that extracts the RANAP protocol message, and the RANAP protocol message to the MSC 40 or the SGSN 50.
- the MSC 40 of the present embodiment indicates that the receiving unit 41A that receives the RANAP protocol message from the HNB-GW 30 and that the mobile station 10 has made a call as an emergency call in the RANAP protocol message.
- the mobile station 10 has a control unit 42A that determines whether or not the call type that the mobile station 10 has actually called is an emergency call, and performs call release processing if the call is not an emergency call.
- the SGSN 50 of the present embodiment indicates that the receiving unit 51A that receives the RANAP protocol message from the HNB-GW 30 and that the mobile station 10 has made an emergency call in the RANAP protocol message. If the information is included, the mobile station 10 determines whether or not the call type that the mobile station 10 has actually called is an emergency call. .
- the MSC 40 or the SGSN 50 can know that the mobile station 10 has made a call as an emergency call.
- the MSC 40 or the SGSN 50 can perform the call release processing of the mobile station 10 when the mobile station 10 has falsified the Establishment Cause and impersonated an emergency call. It can be prevented from receiving.
- (Second Embodiment) 11 to 14 show configurations of the HNB 20, the HNB-GW 30, the MSC 40, and the SGSN 50 of the present embodiment, respectively.
- the present embodiment is an example in which the configurations and operations of the HNB 20, HNB-GW 30, MSC 40, and SGSN 50 of the first embodiment of FIGS.
- the HNB 20 of the present embodiment includes a mobile station signal transmission / reception unit 201A, a RUA (RANAP User Adaptation) message processing unit 202A, an HNB-GW signal transmission / reception unit 203A, an HNBAP message processing unit 204A, A call control unit 205A, an RRC message processing unit 206A, and a RANAP message processing unit 207A.
- a RUA RANAP User Adaptation
- the RUA message processing unit 202A, the HNBAP message processing unit 204A, the call control unit 205A, the RRC message processing unit 206A, and the RANAP message processing unit 207A constitute the control unit 21A shown in FIG. Yes.
- the HNB-GW signal transmission / reception unit 203A is an example of the transmission unit 22A shown in FIG.
- the mobile station signal transmission / reception unit 201 ⁇ / b> A has a secret function for concealing (encrypting and decrypting) the message, and a signal delivery confirmation for confirming message delivery. Functions, and a signal distribution function for distributing messages.
- the HNB-GW signal transmission / reception unit 203A has a secret function, a signal delivery confirmation function, a signal distribution function, etc. as functions for transmitting / receiving an HNBAP protocol message and an RUA protocol message to / from the HNB-GW 30. .
- the RRC message processing unit 206A has a function of encoding an RRC protocol message to be transmitted to the mobile station 10 and a function of decoding an RRC protocol message received from the mobile station 10.
- the HNBAP message processing unit 204A has a function of encoding a HNBAP protocol message to be transmitted to the HNB-GW 30 and a function of decoding an HNBAP protocol message received from the HNB-GW 30.
- the RANAP message processing unit 207A has a function of encoding a RANAP message transmitted to the HNB-GW 30 and a function of decoding a RANAP protocol message received from the HNB-GW 30.
- the RUA protocol is a protocol that functions to transfer a RANAP protocol message.
- the RUA message processing unit 202A has a function of encoding a RUA protocol message to be transmitted to the HNB-GW 30, and a RUA protocol message received from the HNB-GW 30. It has a decoding function.
- the call control unit 205A activates various call processes such as RRC connection establishment, bearer establishment, and mobility control based on the RRC protocol message and the RANAP protocol message. Further, the call control unit 205A activates the HNBAP protocol and performs a registration process of the mobile station 10 to the HNB-GW 30.
- the above functions are functions that a call processing unit mounted on the HNB 20 generally has.
- the call control unit 205A has, as a characteristic function of the present embodiment, the Emergency Cause value of the RANAP protocol message to be transmitted to the HNB-GW 30 based on the Registration Cause parameter of the HNBAP protocol message received from the HNB-GW 30. Has a function to set.
- the HNB-GW 30 of the present embodiment includes an HNB signal transmission / reception unit 301A, an RUA message processing unit 302A, an SGSN signal transmission / reception unit 303A, an MSC signal transmission / reception unit 304A, and an HNBAP message. It has a processing unit 305A, a call control unit 306A, a RANAP message processing unit 307A, and a station data storage unit 308A.
- the RUA message processing unit 302A, the HNBAP message processing unit 305A, the call control unit 306A, the RANAP message processing unit 307A, and the station data storage unit 308A constitute the control unit 32A shown in FIG. Yes.
- the HNB signal transmission / reception unit 301A is an example of the reception unit 31A illustrated in FIG. 8, and the SGSN signal transmission / reception unit 303A and the MSC signal transmission / reception unit 304A are examples of the transmission unit 33A illustrated in FIG. It is.
- the HNB signal transmission / reception unit 301A has a secret function, a signal delivery confirmation function, and the like as functions for transmitting / receiving RUA protocol messages and HNBAP protocol messages to / from the HNB 20.
- the MSC signal transmission / reception unit 304A has an order control function for controlling the order of messages, a delivery confirmation function, and the like as functions for transmitting and receiving RANAP protocol messages to and from the MSC 40.
- the SGSN signal transmission / reception unit 303 ⁇ / b> A has a delivery confirmation function, a sequence control function, and the like as functions for transmitting / receiving a RANAP protocol message to / from the SGSN 50.
- the HNBAP message processing unit 305A has a function of encoding an HNBAP protocol message to be transmitted to the HNB 20 and a function of decoding an HNBAP protocol message received from the HNB.
- the RUA message processing unit 302A has a function of encoding a RUA protocol message to be transmitted to the HNB 20 and a function of decoding a RUA protocol message received from the HNB 20.
- the RANAP message processing unit 307A has a function of encoding a RANAP protocol message to be transmitted to the MSC 40 and a function of decoding a RANAP protocol message received from the MSC 40.
- the call control unit 306A performs registration processing for the HNB 103 and registration processing for the mobile station 10. Further, the call control unit 306A can access the station data stored in the station data storage unit 308A. In the station data, a list of accessible IMSIs is set for each CSG. Based on this IMSI list, the HNB-GW 30 implements access control to the HNB 20.
- the above functions are functions that a call processing unit mounted on the HNB-GW 30 generally has.
- the MSC 40 of the present embodiment includes an anti-HNB-GW signal transmitting / receiving unit 401A, a RANAP message processing unit 402A, a NAS (Non Access Stratum) message processing unit 403A, a call control unit 404A, A station data storage unit 405A.
- a RANAP message processing unit 402A includes a RANAP message processing unit 402A, a NAS (Non Access Stratum) message processing unit 403A, a call control unit 404A, A station data storage unit 405A.
- NAS Non Access Stratum
- the RANAP message processing unit 402A, NAS message processing unit 403A, call control unit 404A, and station data storage unit 405A constitute the control unit 42A shown in FIG.
- the HNB-GW signal transmitting / receiving unit 401A is an example of the receiving unit 41A illustrated in FIG.
- the HNB-GW signal transmission / reception unit 401A has a delivery confirmation function, a sequence control function, and the like as functions for transmitting / receiving a RANAP protocol message to / from the HNB-GW 30.
- the RANAP message processing unit 402A has a function of encoding a RANAP message transmitted to the HNB-GW 30 and a function of decoding a RANAP protocol message received from the HNB-GW 30.
- the call control unit 404A has a call processing function that performs call processing such as call establishment and call release, a mobility control function that performs mobility control such as location registration and handover, and an access restriction function that regulates access to the HNB 20. is doing.
- the call control unit 404A can access the station data stored in the station data storage unit 405A. In the station data, a list of accessible IMSIs is set for each CSG. Based on this IMSI list, the MSC 40 regulates access to the HNB 20.
- the above functions are functions that a call processing unit mounted on the MSC 40 generally has.
- the call control unit 404A analyzes the NAS message when the Emergency Cause parameter is set in the RANAP protocol message received from the HNB-GW 30, and the mobile station 10 has a function of discriminating whether the call type originated by 10 is an emergency call. If it is not an emergency call, the call controller 404A performs a call release process.
- the SGSN 50 includes an HNB-GW signal transmission / reception unit 501A, a RANAP message processing unit 502A, a NAS message processing unit 503A, a call control unit 504A, and a station data storage unit 505A. And have.
- the RANAP message processing unit 502A, NAS message processing unit 503A, call control unit 504A, and station data storage unit 505A constitute the control unit 52A shown in FIG.
- the HNB-GW signal transmitting / receiving unit 501A is an example of the receiving unit 51A illustrated in FIG.
- the HNB-GW signal transmission / reception unit 501A has a delivery confirmation function, a sequence control function, and the like as functions for transmitting / receiving a RANAP protocol message to / from the HNB-GW 30.
- the RANAP message processing unit 502A has a function of encoding a RANAP message transmitted to the HNB-GW 30 and a function of decoding a RANAP protocol message received from the HNB-GW 30.
- the NAS message processing unit 503A has a function for transmitting and receiving messages of the NAS protocol (CC protocol, MM protocol) to and from the mobile station 10.
- the call control unit 504A has a call processing function, a movement control function, and an access restriction function.
- the call control unit 504A can access the station data stored in the station data storage unit 505A.
- a list of accessible IMSIs is set for each CSG. Based on this IMSI list, the SGSN 50 regulates access to the HNB 20.
- the above functions are functions that a call processing unit mounted on the SGSN 50 generally has.
- the call control unit 504A analyzes the NAS message when the Emergency Cause parameter is set in the RANAP protocol message received from the HNB-GW 30, and the mobile station 10 has a function of discriminating whether the call type originated by 10 is an emergency call. If it is not an emergency call, the call control unit 504A performs a call release process.
- step S101 the mobile station 10 sets the establishment cause (FIG. 4) to the RRC: RRC CONNECTION REQUEST message (FIG. 2), and in step S102, the RRC: RRC CONNECTION REQUEST message is sent to the HNB 20. Send.
- the HNB 20 After securing the radio resource, the HNB 20 notifies the mobile station 10 to that effect by an RRC: RRC CONNECTION SETUP message in step S103.
- the mobile station 10 After establishing the RRC connection, the mobile station 10 notifies the HNB 20 of this in an RRC: RRC CONNECTION SETUP COMPLETE message in step S104.
- step S105 the mobile station 10 sets the CM Service Type parameter (FIG. 17) of the CM SERVICE REQUEST message (FIG. 16), which is an MM protocol message, to “Emergency call establishment” and the CM SERVICE REQUEST message.
- RRC Included in INITIAL DIRECT TRANSFER message ( Figure 3).
- step S106 the mobile station 10 sets the Establishment Cause (FIG. 4) of the RRC: INITIAL DIRECT TRANSFER message to “Emergency Call”, and transmits the RRC: INITIAL DIRECT TRANSFER message (FIG. 3) to the HNB 20. .
- the RRC protocol message processing unit 707A decodes the RRC: RRC CONNECTION REQUEST message transmitted in step S102 and the RRC: INITIAL DIRECT TRANSFER message transmitted in step S106.
- the call control unit 205A stores the Establishment Cause value (FIG. 4) notified from the mobile station 10 by the RRC: RRC CONNECTION REQUEST message and the RRC: INITIAL DIRECT TRANSFER message (step S107). Based on the Establishment Cause value, the Registration Cause parameter is determined and set in the HNBAP: UE REGISTER REQUEST message (FIG. 5).
- FIG. 18 shows a flowchart of the Registration Cause parameter determination process.
- step S201 the call control unit 205A determines whether the Establishment Cause value is “Emergency Call”. If it is “Emergency Call”, the call control unit 205A sets the Registration Cause parameter to “Emergency Call” in step S202. If it is not “Emergency Call”, the Registration Cause parameter is determined as “Normal Call” in step S203.
- the HNB 20 transmits an HNBAP: UE REGISTER REQUEST message (FIG. 5) in which the Registration Cause parameter is set to the HNB-GW 30.
- the HNB signal transmission / reception unit 301A receives the HNBAP: UE REGISTER REQUEST message, the HNBAP message processing unit 305A decodes the HNBAP: UE REGISTER REQUEST message, and the call control unit 306A in step S109 Based on the Registration Cause parameter set in the HNBAP: UE REGISTER REQUEST message, it is determined whether to perform access restriction (step S110).
- the call control unit 306A assigns a context ID to the corresponding mobile station 10
- the HNBAP message processing unit 305A encodes the HNBAP: UE REGISTER ACCEPT message
- the HNB signal transmission / reception unit 301A determines in step S111. Then, the HNBAP: UE REGISTER ACCEPT message is transmitted to the HNB 20.
- the call control unit 205A determines whether the Registration Cause parameter is “Emergency Call” in step S112. If the “Emergency Call” is set, the call control unit 205A Generate the Emergency Cause parameter (FIG. 19) introduced by the invention.
- the RANAP message processing unit 207A encodes the RANAP: INITIAL UE MESSAGE message including the Emergency Cause parameter. Further, the RANAP message processing unit 207A sets a NAS-PDU (Protocol Data Unit) parameter in the RANAP: INITIAL UE MESSAGE message, and the CM-SERVICE REQUEST message of the MM protocol received from the mobile station 10 in the NAS-PDU parameter.
- NAS-PDU Protocol Data Unit
- the RUA message processing unit 703A generates a RUA: CONNECT message including the RANAP: INITIAL UE MESSAGE message. That is, the RANAP: INITIAL UE MESSAGE message is transferred from the HNB 20 to the HNB-GW 30 by the RUA: CONNECT message in step S114.
- the RUA message processing unit 302A decodes the CONNECT message of the RUA protocol
- the call control unit 306A extracts the RANAP: INITIAL UE MESSAGE message already encoded in the HNB 20, and the RANAP message processing unit 307A
- the RANAP: INITIAL UE MESSAGE message is transmitted to the MSC 40 based on the routing information such as the CN Domain ID.
- the RANAP message processing unit 402A decodes the RANAP: INITIAL UE MESSAGE message, and the NAS message processing unit 403A decodes the CM SERVICE REQUEST message set in the NAS-PDU. These decoding results are notified to the call control unit 404A.
- the call control unit 404A determines whether or not the Emergency Cause parameter introduced in the present invention is set. If the Emergency Cause parameter is set, in Step S117, CS (Circuit Switching) Start anti-fraud processing for services.
- CS Circuit Switching
- FIG. 20 shows a flowchart of fraud countermeasure processing for the CS service.
- step S301 the call control unit 404A sets the CM Service set in the CM SERVICE REQUEST message (TS24.008 Ver8.5.0 section 9.2.9) of the MM protocol transmitted from the mobile station 10. Check whether the Type parameter (TS24.008 Ver8.5.0 section 10.5.3.3) is “Emergency Call Establishment”.
- the call control unit 404A calls the telephone number (TS24.008 Ver8.5.0) of the SETUP (TS24.008 Ver8.5.0 section 9.3.23 Setup) message of the CC protocol, which is a call signal transmitted by the MSC 40.
- Check if section 10.5.4.7) is an emergency number.
- Called Party BCD Number refers to the called number
- BCD Binary-coded decimal
- the one digit in is represented by a four-digit binary number representing 0 to 9.
- step S303 the call control unit 404A checks whether or not the EMERGENCY SETUP procedure (TS24.008 Ver8.5.0 section 9.3.8) is performed in the mobile station 10. For example, when a message for starting “emergency call establishment” is received from the mobile station 10, it is checked whether the EMERGENCY SETUP procedure is performed from the information element “Emergency setup message type”.
- the call control unit 404A determines that the call type is an emergency call, and continues the call processing for the emergency call. On the other hand, if none of the checks match, the call control unit 404A determines in step S304 that the call type is a normal call, regards it as an unauthorized mobile station 10-2, and activates a call release process. .
- the operation sequence in the case of a packet-switched call is the same except that the processing performed in the MSC 40 in the case of a circuit-switched call is performed in the SGSN 50.
- SM Session Management
- GMM GPRS Mobility Management
- the fraud countermeasure process activated in step S117 is a fraud countermeasure process for PS (Packet Switching) service. This process is different from the CS service in the emergency call identification method.
- PS Packet Switching
- VoIP Voice over IP
- GMM is a protocol for mobility management in packet service (PS).
- FIG. 21 shows a flowchart of fraud countermeasure processing for the PS service.
- step S401 the call control unit 504A of the SGSN 50 transmits an active PDP (Packet Data Protocol) context request message (3GPP TS24.008 Ver8.5.0 section 9.5.) Transmitted from the mobile station 10 in step S401.
- PDP Packet Data Protocol
- APN Access Point Name
- step S402 the call control unit 504A checks whether or not the GMM procedure performed in the mobile station 10 is the Emergency Attach procedure (TR23.869 Ver9.0.0).
- step S403 the call control unit 504A checks whether the PDP Context activated in the SGSN 50 is an emergency call PDP Context. For example, it is checked whether the PDP Context activated on the SGSN 50 is an Emergency PDP Context with TR23.869 Ver9.0.0.
- the call control unit 504A determines that the call type is an emergency call, and continues the call processing for the emergency call. On the other hand, if none of the checks match, the call control unit 504A determines in step S504 that the call type is a normal call, regards it as an unauthorized mobile station 10-2, and activates a call release process. .
- (Third embodiment) 22 to 24 show the configurations of the MSC 40, SGSN 50, and HNB-GW 30 of this embodiment, respectively.
- the MSC 40 of this embodiment determines whether the call type that the mobile station 10 has actually called is an emergency call, and includes information indicating that the call type is an emergency call in the RANAP protocol message. It has a control unit 41B and a transmission unit 42B that transmits the RANAP protocol message to the HNB-GW 30.
- the SGSN 50 of the present embodiment determines whether the call type that the mobile station 10 has actually called is an emergency call, and sends information indicating that the call type is an emergency call to the RANAP protocol message. And a transmission unit 52B that transmits the RANAP protocol message to the HNB-GW 30.
- the HNB-GW 30 of this embodiment includes a receiving unit 31B that receives a RANAP protocol message from the MSC 40 or the SGSN 50, and information indicating that the call type is an emergency call in the RANAP protocol message.
- a control unit 32B that performs call release processing.
- the HNB-GW 30 can know that the call type that the mobile station 10 has actually called is an emergency call.
- the HNB-GW 30 can execute the call release processing of the mobile station 10 when the mobile station 10 has falsified the Establishment Cause and falsely calls it, so that the service provided by the HNB 20 is illegal. It can be prevented from receiving.
- (Fourth embodiment) 25 to 27 show the configurations of the MSC 40, SGSN 50, and HNB-GW 30, respectively, according to this embodiment.
- This embodiment is an example in which the configuration and operation of the SC 40, SGSN 50, and HNB-GW 30 of the third embodiment shown in FIGS.
- the MSC 40 of the present embodiment includes an anti-HNB-GW signal transmission / reception unit 401B, a RANAP message processing unit 402B, a NAS message processing unit 403B, a call control unit 404B, a station data storage unit 405B, have.
- the RANAP message processing unit 402B, NAS message processing unit 403B, call control unit 404B, and station data storage unit 405B constitute the control unit 41B shown in FIG. Further, the HNB-GW signal transmission / reception unit 401B is an example of the transmission unit 42B illustrated in FIG.
- the HNB-GW signal transmission / reception unit 401B, the RANAP message processing unit 402B, the NAS message processing unit 403B, and the station data storage unit 405B are respectively connected to the HNB-GW signal transmission / reception unit 401A and the RANAP message processing unit 402A shown in FIG.
- the NAS message processing unit 403A and the station data storage unit 405A have the same functions.
- the call control unit 404B has a function generally possessed by a call processing unit mounted on the MSC 40, similarly to the call control unit 404A shown in FIG.
- the call control unit 404B analyzes the NAS message to determine whether the call type originated by the mobile station 10 is an emergency call, and based on the determination result. In addition, it has a function of setting the Call Type parameter of the RANAP protocol message to be transmitted to the HNB-GW 30.
- the SGSN 50 of the present embodiment includes an HNB-GW signal transmission / reception unit 501B, a RANAP message processing unit 502B, a NAS message processing unit 503B, a call control unit 504B, and a station data storage unit 505B. And have.
- the RANAP message processing unit 502B, the NAS message processing unit 503B, the call control unit 504B, and the station data storage unit 505B constitute the control unit 51B shown in FIG. Further, the HNB-GW signal transmission / reception unit 501B is an example of the transmission unit 52B illustrated in FIG.
- the HNB-GW signal transmission / reception unit 501B, the RANAP message processing unit 502B, the NAS message processing unit 503B, and the station data storage unit 505B are respectively connected to the HNB-GW signal transmission / reception unit 501A and the RANAP message processing unit 502A shown in FIG. ,
- the NAS message processing unit 503A and the station data storage unit 505A have the same functions.
- the call control unit 504B has a function generally possessed by a call processing unit mounted on the SGSN 50, like the call control unit 504A shown in FIG.
- the call control unit 504B analyzes the NAS message to determine whether the call type originated by the mobile station 10 is an emergency call, and based on the determination result. In addition, it has a function of setting the Call Type parameter of the RANAP protocol message to be transmitted to the HNB-GW 30.
- the HNB-GW 30 of the present embodiment includes an HNB signal transmission / reception unit 301B, an RUA message processing unit 302B, an SGSN signal transmission / reception unit 303B, an MSC signal transmission / reception unit 304B, and an HNBAP message. It has a processing unit 305B, a call control unit 306B, a RANAP message processing unit 307B, and a station data storage unit 308B.
- the RUA message processing unit 302B, the HNBAP message processing unit 305B, the call control unit 306B, the RANAP message processing unit 307B, and the station data storage unit 308B constitute the control unit 32B shown in FIG. Yes.
- the SGSN signal transmission / reception unit 303B and the MSC signal transmission / reception unit 304B are examples of the reception unit 31B illustrated in FIG.
- the HNB signal transmission / reception unit 301B, the RUA message processing unit 302B, the SGSN signal transmission / reception unit 303B, the MSC signal transmission / reception unit 304B, the HNBAP message processing unit 305B, the RANAP message processing unit 307B, and the station data storage unit 308B are respectively shown in FIG.
- the call control unit 306B has a function generally possessed by a call processing unit installed in the HNB-GW 30, as with the call control unit 306A shown in FIG.
- the call control unit 306B allows the mobile station 10 to make a call when the Normal Call is set in the Call Type parameter of the RANAP protocol message received from the MSC 40 or the SGSN 50. If it is determined that the call type is a normal call and the mobile station 10 makes a call as an emergency call at this time, it has a function of performing a call release process.
- the configuration of the HNB 20 of the present embodiment may be the same as in FIG.
- the call control unit 205A of the HNB 20 only needs to have a function that a call processing unit mounted on the HNB 20 generally has.
- Operation example 1 This operation example is an example in which the call type determination result determined by the MSC 40 or the SGSN 50 is notified by a COMMON ID message of RANAP (3GPP TS25.413).
- the core network device transmits a RANAP: COMMON ID message to the HNB-GW 30 after the signaling connection is established.
- call control unit 404B activates Call Type parameter determination processing in step S502 after establishing a signaling connection in step S501.
- FIG. 29 shows a flowchart of Call Type parameter determination processing in the MSC 40.
- step S601 the call control unit 404B sets the CM Service set in the CM SERVICE REQUEST message (TS24.008 Ver8.5.0 section 9.2.9) of the MM protocol transmitted from the mobile station 10. Check whether the Type parameter (TS24.008 Ver8.5.0 section 10.5.3.3) is “Emergency Call Establishment”.
- the call control unit 404B sets the telephone number (TS24.008 Ver 8.5) of the SETUP (TS24.008 9.3.23 Ver 8.5.0 section Setup) message of the CC protocol, which is a call signal transmitted by the MSC 40. .0 Check if section 10.5.4.7) is an emergency number.
- TS24.008 Ver 8.5.0 Figure 10.5.91 / 3GPP TS 24.008 Called party BCD number information element, Number digit 1, Number digit 2, Number digit 3, etc. correspond to telephone numbers, and this phone Check if the number is an emergency number.
- Called Party BCD Number in section 24.008 of TS24.008 refers to the called number
- BCD is one of the numerical representation methods in the computer. Indicates a 4-digit binary number representing up to 9.
- step S603 the call control unit 404B checks whether the EMERGENCY SETUP procedure (TS24.008 Ver 8.5.0 section 9.3.8) is performed in the mobile station 10. For example, when a message for starting “emergency call establishment” is received from the mobile station 10, it is checked whether the EMERGENCY SETUP procedure is performed from the information element “Emergency setup message type”.
- the call control unit 404B determines in step S604 that the call type is an emergency call, and determines the Call Type parameter to “Normal Call”. On the other hand, if none of the checks match, the call control unit 404B determines in step S605 that the call type is a normal call, and determines the Call Type parameter to “Emergency Call”.
- the Call Type parameter is determined when the call control unit 404B transmits the RANAP: COMMON ID message to the HNB-GW 30 in step S503, the Call Type parameter is set.
- the structure of the RANAP: COMMON ID message according to the present invention is shown in FIG.
- the call control unit 306B determines that the mobile station 10 has accessed the HNB-GW 30 in step S505.
- HNBAP Compared with the Registration Cause parameter (FIG. 6) of the UE REGISTER REQUEST message (FIG. 5).
- FIG. 31 is a diagram showing a table for determining processing in the HNB-GW 30 according to the present embodiment according to the call type.
- the Call Type parameter notified from the MSC 40 is “Normal Call” regardless of whether the Registration Cause parameter of the HNBAP: UE REGISTER REQUEST message is “Emergency Call”. From this, the HNB-GW 30 determines that the mobile station 10 has falsely accessed the HNB 20 as an emergency call, and performs call release processing.
- the operation sequence in the case of a packet-switched call is the same except that the processing performed in the MSC 40 in the case of a circuit-switched call is performed in the SGSN 50.
- the Call Type parameter determination process activated in step S502 is different.
- FIG. 32 shows a flowchart of Call Type parameter determination processing in the SGSN 50.
- step S701 the call control unit 504B is set in the SM protocol Activate PDP context request message (3GPP TS24.008 Ver8.5.0 section 9.5.1) transmitted from the mobile station 10.
- PDP context request message (3GPP TS24.008 Ver8.5.0 section 9.5.1) transmitted from the mobile station 10.
- APN 3GPP TS24.008 9.5.1 10.5.6.1
- step S702 the call control unit 504B checks whether or not the GMM procedure performed in the mobile station 10 is the Emergency Attach procedure (TR23.869 Ver9.0.0).
- step S703 the call control unit 504B checks whether the PDP Context activated in the SGSN 50 is an emergency call PDP Context. For example, it is checked whether the PDP Context activated on the SGSN 50 is an Emergency PDP Context with TR23.869 Ver9.0.0.
- the call control unit 504B determines that the call type is an emergency call in step S704, and determines the Call Type parameter to “Normal Call”. On the other hand, if none of the checks match, the call control unit 504B determines in step S705 that the call type is a normal call, and determines the Call Type parameter to “Emergency Call”.
- the call control unit 504B sets the Call Type parameter if the Call Type parameter is determined when the RANAP: COMMON ID message is transmitted to the HNB-GW 30.
- the configuration of the RANAP: COMMON ID message according to the present invention is the same as that of the MSC 40 as shown in FIG.
- the call control unit 306B when receiving the RANAP: COMMON ID message, if the Call Type parameter is included, the HNBAP: UE REGISTER REQUEST message when the mobile station 10 accesses the HNB-GW 30 (see FIG. Compare with Registration Cause parameter of 5) (Fig. 6).
- the Call Type parameter notified from the SGSN 50 is “Normal Call” regardless of whether the Registration Cause parameter of the HNBAP: UE REGISTER REQUEST message is “Emergency Call”. From this, the HNB-GW 30 determines that the mobile station 10 has falsely accessed the HNB 20 as an emergency call, and performs call release processing.
- Operation example 2 This operation example is an example in which the call type discrimination result discriminated in the MSC 40 or the SGSN 50 is notified by a DIRECT TRANSFER message of RANAP (3GPP TS25.413).
- the core network device transmits a RANAP: DIRECT TRANSFER message to the HNB-GW 30 when transmitting a NAS message such as the CC protocol or the MM protocol.
- call control unit 404B activates Call Type parameter determination processing in step S802 after the NAS message is transmitted in step S801.
- the Call Type parameter determination process in the MSC 40 is the same as in the operation example 1, and is as shown in FIG.
- the call control unit 404B sets the Call Type parameter if the Call Type parameter is determined when the RANAP: DIRECT TRANSFER message is transmitted to the HNB-GW 30 in step S803.
- the configuration of the RANAP: DIRECT TRANSFER message according to the present invention is shown in FIG.
- the call control unit 306B when receiving the RANAP: DIRECT TRANSFER message, includes the Call Type parameter in step S804, the mobile station 10 accesses the HNB-GW 30 in step S805.
- HNBAP Compared with the Registration Cause parameter (FIG. 6) of the UE REGISTER REQUEST message (FIG. 5).
- the Call Type parameter notified from the MSC 40 is “Normal Call”, regardless of whether the Registration Cause parameter of the HNBAP: UE REGISTER REQUEST message is “Emergency Call”. From this, the HNB-GW 30 determines that the mobile station 10 has falsely accessed the HNB 20 as an emergency call, and performs call release processing.
- the operation sequence in the case of a packet-switched call is the same except that the processing performed in the MSC 40 in the case of a circuit-switched call is performed in the SGSN 50.
- the Call Type parameter determination process activated in step S802 is different.
- the Call Type parameter determination process in the SGSN 50 is the same as that in the operation example 1, and is as shown in FIG.
- the call control unit 504B sets the Call Type parameter if the Call Type parameter is determined when the RANAP: DIRECT TRANSFER message is transmitted to the HNB-GW 30.
- the configuration of the RANAP: DIRECT TRANSFER message according to the present invention is the same as that of the MSC 40 as shown in FIG.
- the call control unit 306B when receiving the RANAP: DIRECT TRANSFER message, includes the Call Type parameter, the HNBAP: UE REGISTER REQUEST message when the mobile station 10 accesses the HNB-GW 30 (see FIG. Compare with Registration Cause parameter of 5) (Fig. 6).
- the Call Type parameter notified from the SGSN 50 is “Normal Call”, regardless of whether the Registration Cause parameter of the HNBAP: UE REGISTER REQUEST message is “Emergency Call”.
- the HNB-GW 30 determines that the mobile station 10 has falsely accessed the HNB 20 as an emergency call, and performs call release processing.
- the HNB-GW 30 originally accesses the HNB 20. It is possible to prevent the unauthorized mobile station 10-2, which cannot be used, from falsifying the Establishment Cause as an emergency call and receiving a service from the HNB 20.
- Operation example 3 This operation example is an example in which the call type discrimination result discriminated in the MSC 40 or the SGSN 50 is notified by an RAAB (Radio Access Bearer) ASSIGNMENT REQUEST message of RANAP (3GPP TS25.413).
- RAAB Radio Access Bearer
- FIG. 35 shows the operation after the process shown in FIG. 15 is completed, but the processes in steps S112, S113, S116, and S117 shown in FIG. 15 are not performed, and steps S114 and S115 are performed.
- the RANAP: INITIAL UE MESSAGE message transmitted in the step does not include the Emergency Cause parameter.
- the RANAP RAB ASSIGNMENT REQUEST message is sent to the HNB-GW30. Send to.
- call control unit 404B after receiving the call establishment request from mobile station 10 in step S901, call control unit 404B performs QoS (Quality of Service) for the radio access bearer in step S902. Then, in step S903, a Call Type parameter determination process is started.
- the Call Type parameter determination process in the MSC 40 is the same as in the operation example 1, and is as shown in FIG.
- the call control unit 404B sets the Call Type parameter if the Call Type parameter is determined when the RANAP: RAB ASSIGNMENT REQUEST message is transmitted to the HNB-GW 30 in step S904.
- the structure of the RANAP: RAB ASSIGNMENT REQUEST message according to the present invention is shown in FIG.
- HNBAP Compared with the Registration Cause parameter (FIG. 6) of the UE REGISTER REQUEST message (FIG. 5).
- the Call Type parameter notified from the MSC 40 is “Normal Call” regardless of whether the Registration Cause parameter of the HNBAP: UE REGISTER REQUEST message is “Emergency Call”. From this, the HNB-GW 30 determines that the mobile station 10 has falsely accessed the HNB 20 as an emergency call, and performs call release processing.
- the operation sequence in the case of a packet-switched call is the same except that the processing performed in the MSC 40 in the case of a circuit-switched call is performed in the SGSN 50.
- the Call Type parameter determination process activated in step S802 is different.
- the Call Type parameter determination process in the SGSN 50 is the same as that in the operation example 1, and is as shown in FIG.
- the call control unit 504B sets the Call Type parameter if the Call Type parameter is determined when the RANAP: RAB ASSIGNMENT REQUEST message is transmitted to the HNB-GW 30.
- the configuration of the RANAP: RAB ASSIGNMENT REQUEST message according to the present invention is the same as that of the MSC 40 as shown in FIG.
- the call control unit 306B when receiving the RANAP: RAB ASSIGNMENT REQUEST message, includes the Call Type parameter, the HNBAP: UE REGISTER REQUEST message (when the mobile station 10 accesses the HNB-GW30) Compared with the Registration Cause parameter of FIG. 5) (FIG. 6).
- the Call Type parameter notified from the SGSN 50 is “Normal Call”, regardless of whether the Registration Cause parameter of the HNBAP: UE REGISTER REQUEST message is “Emergency Call”. From this, the HNB-GW 30 determines that the mobile station 10 has falsely accessed the HNB 20 as an emergency call, and performs call release processing.
- the method performed by the HNB 20, HNB-GW 30, MSC 40, and SGSN 50 of the present invention may be applied to a program for causing a computer to execute.
- the program can be stored in a storage medium and can be provided to the outside via a network.
- the setting of the Emergency Cause value to the RANAP protocol message is performed by the HNB 20, but may be performed by the HNB-GW 30.
- the fraud countermeasure processing is performed by the MSC 40 or the SGSN 50, but may be performed by the HNB-GW 30.
- the HNB-GW 30 receives information indicating that the actual call type originated by the mobile station 10 is an emergency call from the MSC 40 or the SGSN 50, and the table of FIG. Fraud countermeasure processing will be carried out using.
- information indicating that the mobile station 10 has made a call as an emergency call using the RANAP protocol message or the actual call type that the mobile station 10 has called Information indicating an emergency call was communicated between the HNB 20, the HNB-GW 30, and the core network device (MSC 40 or SGSN 50).
- the message is not limited to the RANAP protocol message, but may be any other message as long as the message can be communicated between the HNB 20, the HNB-GW 30, or the core network device.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Emergency Management (AREA)
- Environmental & Geological Engineering (AREA)
- Public Health (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
(2)マクロ基地局が提供する通常の課金サービスよりも安い課金サービスを提供することができる
(3)基地局と移動局との距離が近く、移動局が高い無線品質(Ec/Io)を得ることができるため、64QAM(64 Quadrature Amplitude Modulation)やMIMO(Multiple Input Multiple Output)の高速化技術を活かすことができ、HNB配下において高速パケットサービスを提供することができる
(4)HNBの局所性を活かした特有のコンテンツサービスを提供することができる
このように、HNBによるサービスは、多くの利点を有するため、通信事業者と契約を結んだ加入者や、そのHNBの所持者が許容した加入者のみに提供されるべきである。
(2)不正移動局10-2は、HNB20を介した発信を行うことによって、通常の課金サービスよりも安い課金サービスを不正に受けることができてしまう
(3)特定のユーザ向けへのコンテンツサービスを不正移動局10-2が不正に受けてしまう
このような問題を解決する方法としては、移動局10が緊急呼として発呼を行った場合に、コアネットワーク装置側で、その移動局10の呼解放処理を行うことが考えられる。そのためには、コアネットワーク装置は、移動局10が緊急呼として発呼を行ったことを知る必要がある。
移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムであって、
前記基地局は、
前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有し、
前記コアネットワーク装置は、
前記基地局から送信されてきた前記メッセージを受信する受信部を有する。
移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムであって、
前記ゲートウェイ装置は、
前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有し、
前記コアネットワーク装置は、
前記ゲートウェイ装置から送信されてきた前記メッセージを受信する受信部を有する。
移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムであって、
前記コアネットワーク装置は、
前記移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含める制御部と、
前記メッセージを前記ゲートウェイ装置に送信する送信部と、
前記ゲートウェイ装置は、
前記コアネットワーク装置から送信されてきた前記メッセージを受信する受信部を有する。
ゲートウェイ装置を介して、コアネットワークに配置されたコアネットワーク装置に接続される基地局であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有する。
基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有する。
基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置であって、
前記コアネットワーク装置から送信されてきた、移動局が発呼した呼種別が緊急呼であることを示す情報を含むメッセージを受信する受信部を有する。
コアネットワークに配置されたコアネットワーク装置であって、
基地局から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信する受信部を有する。
コアネットワークに配置されたコアネットワーク装置であって、
ゲートウェイ装置から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信する受信部を有する。
コアネットワークに配置されたコアネットワーク装置であって、
前記移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含める制御部と、
前記メッセージをゲートウェイ装置に送信する送信部と、を有する。
移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムによる通信方法であって、
前記基地局が、前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記基地局が、前記メッセージを前記コアネットワーク装置に送信するステップと、
前記コアネットワーク装置が、前記基地局から送信されてきた前記メッセージを受信するステップと、を有する。
移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムによる通信方法であって、
前記ゲートウェイ装置が、前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記ゲートウェイ装置が、前記メッセージを前記コアネットワーク装置に送信するステップと、
前記コアネットワーク装置が、前記ゲートウェイ装置から送信されてきた前記メッセージを受信するステップと、を有する。
移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムによる通信方法であって、
前記コアネットワーク装置が、前記移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含めるステップと、
前記コアネットワーク装置が、前記メッセージを前記ゲートウェイ装置に送信するステップと、
前記ゲートウェイ装置が、前記コアネットワーク装置から送信されてきた前記メッセージを受信するステップと、を有する。
ゲートウェイ装置を介して、コアネットワークに配置されたコアネットワーク装置に接続される基地局による通信方法であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記メッセージを前記コアネットワーク装置に送信するステップと、を有する。
基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置による通信方法であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記メッセージを前記コアネットワーク装置に送信するステップと、を有する。
基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置による通信方法であって、
前記コアネットワーク装置から送信されてきた、移動局が発呼した呼種別が緊急呼であることを示す情報を含むメッセージを受信するステップを有する。
コアネットワークに配置されたコアネットワーク装置による通信方法であって、
基地局から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信するステップを有する。
コアネットワークに配置されたコアネットワーク装置による通信方法であって、
ゲートウェイ装置から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信するステップを有する。
コアネットワークに配置されたコアネットワーク装置による通信方法であって、
移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含めるステップと、
前記メッセージをゲートウェイ装置に送信するステップと、を有する。
図7~図10に、本実施形態のHNB20、HNB-GW30、MSC40、およびSGSN50の構成をそれぞれ示す。
図11~図14に、本実施形態のHNB20、HNB-GW30、MSC40、およびSGSN50の構成をそれぞれ示す。本実施形態は、図7~図10の第1の実施形態のHNB20、HNB-GW30、MSC40、およびSGSN50の構成および動作をより具体化した例である。
まず、移動局10が回線交換の緊急呼として発呼を行った場合の動作例を、図15のシーケンス図に沿って説明する。
次に、移動局10がパケット交換の緊急呼として発呼を行った場合の動作例を説明する。
図22~図24に、本実施形態のMSC40、SGSN50、およびHNB-GW30の構成をそれぞれ示す。
図25~図27に、本実施形態のMSC40、SGSN50、およびHNB-GW30の構成をそれぞれ示す。本実施形態は、図22~図24の第3の実施形態のSC40、SGSN50、およびHNB-GW30の構成および動作をより具体化した一例である。
本動作例は、MSC40あるいはSGSN50において判別した呼種別の判別結果を、RANAP(3GPP TS25.413)のCOMMON IDメッセージにて通知する例である。
まず、MSC40が回線交換呼の呼種別の判別結果をRANAPのCOMMON IDメッセージにて通知する場合の動作例を、図28のシーケンス図に沿って説明する。なお、図28は、図15に示した処理が終了した後の動作を示すものであるが、図15に示したステップS112,S113,S116,S117の処理は行われず、また、ステップS114,S115において送信されるRANAP:INITIAL UE MESSAGEメッセージにはEmergency Causeパラメータが含まれないものとする。
次に、SGSN50がパケット交換呼の呼種別の判別結果をRANAPのCOMMON IDメッセージにて通知する場合の動作例を説明する。
本動作例は、MSC40あるいはSGSN50において判別した呼種別の判別結果を、RANAP(3GPP TS25.413)のDIRECT TRANSFERメッセージにて通知する例である。
まず、MSC40が回線交換呼の呼種別の判別結果をRANAPのDIRECT TRANSFERメッセージにて通知する場合の動作例を、図33のシーケンス図に沿って説明する。なお、図33は、図15に示した処理が終了した後の動作を示すものであるが、図15に示したステップS112,S113,S116,S117の処理は行われず、また、ステップS114,S115において送信されるRANAP:INITIAL UE MESSAGEメッセージにはEmergency Causeパラメータが含まれないものとする。
次に、SGSN50がパケット交換呼の呼種別の判別結果をRANAPのDIRECT TRANSFERメッセージにて通知する場合の動作例を説明する。
これによって、パケット交換のVoIPのケースにおいても、本来、HNB20にアクセスできない不正移動局10-2が、Establishment Causeを改ざんして緊急呼と偽り、HNB20によるサービスを受けることを防止することができる。
本動作例は、MSC40あるいはSGSN50において判別した呼種別の判別結果を、RANAP(3GPP TS25.413)のRAB(Radio Access Bearer) ASSIGNMENT REQUESTメッセージにて通知する例である。
まず、MSC40が回線交換呼の呼種別の判別結果をRANAPのRAB ASSIGNMENT REQUESTメッセージにて通知する場合の動作例を、図35のシーケンス図に沿って説明する。なお、図35は、図15に示した処理が終了した後の動作を示すものであるが、図15に示したステップS112,S113,S116,S117の処理は行われず、また、ステップS114,S115において送信されるRANAP:INITIAL UE MESSAGEメッセージにはEmergency Causeパラメータが含まれないものとする。
次に、SGSN50がパケット交換呼の呼種別の判別結果をRANAPのRAB ASSIGNMENT REQUESTメッセージにて通知する場合の動作例を説明する。
Claims (44)
- 移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムであって、
前記基地局は、
前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有し、
前記コアネットワーク装置は、
前記基地局から送信されてきた前記メッセージを受信する受信部を有する移動通信システム。 - 前記メッセージは、
RANAPプロトコルのINITIAL UE MESSAGEメッセージであり、
前記基地局の前記制御部は、
前記INITIAL UE MESSAGEメッセージにEmergency Causeパラメータを追加し、前記移動局が緊急呼として発呼を行ったことを示す情報を前記Emergency Causeパラメータに含める、請求項1に記載の移動通信システム。 - 移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムであって、
前記ゲートウェイ装置は、
前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有し、
前記コアネットワーク装置は、
前記ゲートウェイ装置から送信されてきた前記メッセージを受信する受信部を有する移動通信システム。 - 前記メッセージは、
RANAPプロトコルのINITIAL UE MESSAGEメッセージであり、
前記ゲートウェイ装置の前記制御部は、
前記INITIAL UE MESSAGEメッセージにEmergency Causeパラメータを追加し、前記移動局が緊急呼として発呼を行ったことを示す情報を前記Emergency Causeパラメータに含める、請求項3に記載の移動通信システム。 - 前記コアネットワーク装置は、
前記メッセージに、前記移動局が緊急呼として発呼を行ったことを示す情報が含まれている場合、前記移動局が発呼した呼種別が緊急呼であるか判別し、緊急呼でなければ呼解放処理を行う制御部をさらに有する、請求項1から4のいずれか1項に記載の移動通信システム。 - 移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムであって、
前記コアネットワーク装置は、
前記移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含める制御部と、
前記メッセージを前記ゲートウェイ装置に送信する送信部と、を有し、
前記ゲートウェイ装置は、
前記コアネットワーク装置から送信されてきた前記メッセージを受信する受信部を有する移動通信システム。 - 前記メッセージは、
RANAPプロトコルのCOMMON IDメッセージであり、
前記コアネットワーク装置の前記制御部は、
前記COMMON IDメッセージにCall Typeパラメータを追加し、前記移動局が発呼した呼種別が緊急呼であることを示す情報を、前記Call Typeパラメータに含める、請求項6に記載の移動通信システム。 - 前記メッセージは、
RANAPプロトコルのDIRECT TRANSFERメッセージであり、
前記コアネットワーク装置の前記制御部は、
前記DIRECT TRANSFERメッセージにCall Typeパラメータを追加し、前記移動局が発呼した呼種別が緊急呼であることを示す情報を、前記Call Typeパラメータに含める、請求項6に記載の移動通信システム。 - 前記メッセージは、
RANAPプロトコルのRAB ASSIGNMENT REQUESTメッセージであり、
前記コアネットワーク装置の前記制御部は、
前記RAB ASSIGNMENT REQUESTメッセージにCall Typeパラメータを追加し、前記移動局が発呼した呼種別が緊急呼であることを示す情報を、前Call Typeパラメータに含める、請求項6に記載の移動通信システム。 - 前記ゲートウェイ装置は、
前記メッセージに、前記移動局が発呼した呼種別が通常呼であることを示す情報が含まれている場合、当該移動局から通知されている呼種別が緊急呼であれば呼解放処理を行う制御部をさらに有する、請求項6から9のいずれか1項に記載の移動通信システム。 - ゲートウェイ装置を介して、コアネットワークに配置されたコアネットワーク装置に接続される基地局であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有する基地局。 - 前記メッセージは、
RANAPプロトコルのINITIAL UE MESSAGEメッセージであり、
前記制御部は、
前記INITIAL UE MESSAGEメッセージにEmergency Causeパラメータを追加し、前記移動局が緊急呼として発呼を行ったことを示す情報を前記Emergency Causeパラメータに含める、請求項11に記載の基地局。 - 基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含める制御部と、
前記メッセージを前記コアネットワーク装置に送信する送信部と、を有するゲートウェイ装置。 - 前記メッセージは、
RANAPプロトコルのINITIAL UE MESSAGEメッセージであり、
前記制御部は、
前記INITIAL UE MESSAGEメッセージにEmergency Causeパラメータを追加し、前記移動局が緊急呼として発呼を行ったことを示す情報を前記Emergency Causeパラメータに含める、請求項13に記載のゲートウェイ装置。 - 基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置であって、
前記コアネットワーク装置から送信されてきた、移動局が発呼した呼種別が緊急呼であることを示す情報を含むメッセージを受信する受信部を有するゲートウェイ装置。 - 前記メッセージに、前記移動局が発呼した呼種別が通常呼であることを示す情報が含まれている場合、当該移動局から通知されている呼種別が緊急呼であれば呼解放処理を行う制御部をさらに有する、請求項15に記載のゲートウェイ装置。
- コアネットワークに配置されたコアネットワーク装置であって、
基地局から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信する受信部を有するコアネットワーク装置。 - コアネットワークに配置されたコアネットワーク装置であって、
ゲートウェイ装置から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信する受信部を有するコアネットワーク装置。 - 前記メッセージに、前記移動局が緊急呼として発呼を行ったことを示す情報が含まれている場合、前記移動局が発呼した呼種別が緊急呼であるか判別し、緊急呼でなければ呼解放処理を行う制御部をさらに有する、請求項17または18に記載のコアネットワーク装置。
- 前記コアネットワーク装置は、
回線交換を制御する回線交換局であり、
前記制御部は、
前記移動局から送信されてきたMMプロトコルのCM SERVICE REQUESTメッセージに設定されているCM Service TypeパラメータがEmergency Call Establishmentである場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項19に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
回線交換を制御する回線交換局であり、
前記制御部は、
自装置が送信する発呼信号であるCCプロトコルのSETUPメッセージの電話番号が緊急番号である場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項19に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
回線交換を制御する回線交換局であり、
前記制御部は、
前記移動局にてEMERGENCY SETUP手順が行われている場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項19に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
パケット交換を制御するパケット交換局であり、
前記制御部は、
前記移動局から送信されてきたSMプロトコルのActivate PDP context requestメッセージに設定されているAPNが緊急呼に特有のものである場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項19に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
パケット交換を制御するパケット交換局であり、
前記制御部は、
前記移動局にて行われているGMM手順がEmergency Attach手順である場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項19に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
パケット交換を制御するパケット交換局であり、
前記制御部は、
自装置にて起動しているPDP Contextが緊急呼用のPDP Contextである場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項19に記載のコアネットワーク装置。 - コアネットワークに配置されたコアネットワーク装置であって、
前記移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含める制御部と、
前記メッセージをゲートウェイ装置に送信する送信部と、を有するコアネットワーク装置。 - 前記コアネットワーク装置は、
回線交換を制御する回線交換局であり、
前記制御部は、
前記移動局から送信されてきたMMプロトコルのCM SERVICE REQUESTメッセージに設定されているCM Service TypeパラメータがEmergency Call Establishmentである場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項26に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
回線交換を制御する回線交換局であり、
前記制御部は、
自装置が送信する発呼信号であるCCプロトコルのSETUPメッセージの電話番号が緊急番号である場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項26に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
回線交換を制御する回線交換局であり、
前記制御部は、
前記移動局にてEMERGENCY SETUP手順が行われている場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項26に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
パケット交換を制御するパケット交換局であり、
前記制御部は、
前記移動局から送信されてきたSMプロトコルのActivate PDP context requestメッセージに設定されているAPNが緊急呼に特有のものである場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項26に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
パケット交換を制御するパケット交換局であり、
前記制御部は、
前記移動局にて行われているGMM手順がEmergency Attach手順である場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項26に記載のコアネットワーク装置。 - 前記コアネットワーク装置は、
パケット交換を制御するパケット交換局であり、
前記制御部は、
自装置にて起動しているPDP Contextが緊急呼用のPDP Contextである場合、前記移動局が発呼した呼種別を緊急呼と判別する、請求項26に記載のコアネットワーク装置。 - 前記メッセージは、
RANAPプロトコルのCOMMON IDメッセージであり、
前記制御部は、
前記COMMON IDメッセージにCall Typeパラメータを追加し、前記移動局が発呼した呼種別が緊急呼であることを示す情報を、前記Call Typeパラメータに含める、請求項26から32のいずれか1項に記載のコアネットワーク装置。 - 前記メッセージは、
RANAPプロトコルのDIRECT TRANSFERメッセージであり、
前記制御部は、
前記DIRECT TRANSFERメッセージにCall Typeパラメータを追加し、前記移動局が発呼した呼種別が緊急呼であることを示す情報を、前記Call Typeパラメータに含める、請求項26から32のいずれか1項に記載のコアネットワーク装置。 - 前記メッセージは、
RANAPプロトコルのRAB ASSIGNMENT REQUESTメッセージであり、
前記制御部は、
前記RAB ASSIGNMENT REQUESTメッセージにCall Typeパラメータを追加し、前記移動局が発呼した呼種別が緊急呼であることを示す情報を、前Call Typeパラメータに含める、請求項26から32のいずれか1項に記載のコアネットワーク装置。 - 移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムによる通信方法であって、
前記基地局が、前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記基地局が、前記メッセージを前記コアネットワーク装置に送信するステップと、
前記コアネットワーク装置が、前記基地局から送信されてきた前記メッセージを受信するステップと、を有する通信方法。 - 移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムによる通信方法であって、
前記ゲートウェイ装置が、前記移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記ゲートウェイ装置が、前記メッセージを前記コアネットワーク装置に送信するステップと、
前記コアネットワーク装置が、前記ゲートウェイ装置から送信されてきた前記メッセージを受信するステップと、を有する通信方法。 - 移動局と、前記移動局と無線通信を行う基地局と、前記基地局をコアネットワークに接続するゲートウェイ装置と、前記コアネットワークに配置されたコアネットワーク装置と、を有してなる移動通信システムによる通信方法であって、
前記コアネットワーク装置が、前記移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含めるステップと、
前記コアネットワーク装置が、前記メッセージを前記ゲートウェイ装置に送信するステップと、
前記ゲートウェイ装置が、前記コアネットワーク装置から送信されてきた前記メッセージを受信するステップと、を有する通信方法。 - ゲートウェイ装置を介して、コアネットワークに配置されたコアネットワーク装置に接続される基地局による通信方法であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記メッセージを前記コアネットワーク装置に送信するステップと、を有する通信方法。 - 基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置による通信方法であって、
移動局が緊急呼として発呼を行ったことを示す情報をメッセージに含めるステップと、
前記メッセージを前記コアネットワーク装置に送信するステップと、を有する通信方法。 - 基地局を、コアネットワークに配置されたコアネットワーク装置に接続するゲートウェイ装置による通信方法であって、
前記コアネットワーク装置から送信されてきた、移動局が発呼した呼種別が緊急呼であることを示す情報を含むメッセージを受信するステップを有する通信方法。 - コアネットワークに配置されたコアネットワーク装置による通信方法であって、
基地局から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信するステップを有する通信方法。 - コアネットワークに配置されたコアネットワーク装置による通信方法であって、
ゲートウェイ装置から送信されてきた、移動局が緊急呼として発呼を行ったことを示す情報を含むメッセージを受信するステップを有する通信方法。 - コアネットワークに配置されたコアネットワーク装置による通信方法であって、
移動局が発呼した呼種別が緊急呼であることを示す情報をメッセージに含めるステップと、
前記メッセージをゲートウェイ装置に送信するステップと、を有する通信方法。
Priority Applications (12)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BRPI1006629-2A BRPI1006629B1 (pt) | 2009-04-17 | 2010-03-01 | Sistema de comunicação móvel, aparelho de gateway, aparelho de rede de base e método de comunicação |
KR1020137025671A KR20130119508A (ko) | 2009-04-17 | 2010-03-01 | 이동 통신 시스템, 이동국, 기지국, 게이트웨이 장치, 코어 네트워크 장치, 통신 방법 |
CN201080017080.1A CN102396249B (zh) | 2009-04-17 | 2010-03-01 | 移动通信系统、基站、网关装置、核心网络装置以及通信方法 |
JP2011509238A JP5375954B2 (ja) | 2009-04-17 | 2010-03-01 | 移動通信システム、基地局、ゲートウェイ装置、コアネットワーク装置、通信方法 |
EP17163823.2A EP3306966B1 (en) | 2009-04-17 | 2010-03-01 | Mobile communication system, base station, gateway apparatus, core network apparatus, and communication method |
RU2011146642/07A RU2503141C2 (ru) | 2009-04-17 | 2010-03-01 | Система мобильной связи, базовая станция, устройство шлюза, устройство базовой сети и способ связи |
KR1020157000256A KR101779458B1 (ko) | 2009-04-17 | 2010-03-01 | 이동 통신 시스템, 이동국, 기지국, 게이트웨이 장치, 코어 네트워크 장치, 통신 방법 |
US13/258,888 US9241247B2 (en) | 2009-04-17 | 2010-03-01 | Mobile communication system, base station, gateway apparatus, core network apparatus, and communication method |
EP10764314.0A EP2421286A4 (en) | 2009-04-17 | 2010-03-01 | MOBILE COMMUNICATION SYSTEM, BASE STATION, GATEWAY APPARATUS, CENTRAL NETWORK APPARATUS, COMMUNICATION METHOD |
CA2758430A CA2758430C (en) | 2009-04-17 | 2010-03-01 | Mobile communication system, base station, gateway apparatus, core network apparatus, and communication method |
AU2010237984A AU2010237984C1 (en) | 2009-04-17 | 2010-03-01 | Mobile communication system, base station, gateway apparatus, core network apparatus, communication method |
US14/578,947 US9560508B2 (en) | 2009-04-17 | 2014-12-22 | Mobile communication system, base station, gateway apparatus, core network apparatus, and communication method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2009101130 | 2009-04-17 | ||
JP2009-101130 | 2009-04-17 |
Related Child Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/258,888 A-371-Of-International US9241247B2 (en) | 2009-04-17 | 2010-03-01 | Mobile communication system, base station, gateway apparatus, core network apparatus, and communication method |
US201113258888A A-371-Of-International | 2009-04-17 | 2011-09-22 | |
US14/578,947 Continuation US9560508B2 (en) | 2009-04-17 | 2014-12-22 | Mobile communication system, base station, gateway apparatus, core network apparatus, and communication method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010119728A1 true WO2010119728A1 (ja) | 2010-10-21 |
Family
ID=42982397
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/053204 WO2010119728A1 (ja) | 2009-04-17 | 2010-03-01 | 移動通信システム、基地局、ゲートウェイ装置、コアネットワーク装置、通信方法 |
Country Status (10)
Country | Link |
---|---|
US (2) | US9241247B2 (ja) |
EP (2) | EP3306966B1 (ja) |
JP (5) | JP5375954B2 (ja) |
KR (3) | KR20110138239A (ja) |
CN (2) | CN102396249B (ja) |
AU (1) | AU2010237984C1 (ja) |
BR (1) | BRPI1006629B1 (ja) |
CA (2) | CA2758430C (ja) |
RU (2) | RU2503141C2 (ja) |
WO (1) | WO2010119728A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013168700A1 (ja) * | 2012-05-07 | 2013-11-14 | 株式会社エヌ・ティ・ティ・ドコモ | 移動局 |
JP2014500661A (ja) * | 2010-11-04 | 2014-01-09 | クアルコム,インコーポレイテッド | ワイヤレス通信システム内でのフェムトアクセスポイントを介した通信 |
JP2016021766A (ja) * | 2009-04-17 | 2016-02-04 | 日本電気株式会社 | 移動通信システム、基地局、ゲートウェイ装置、コアネットワーク装置、通信方法 |
JP2016511614A (ja) * | 2013-03-13 | 2016-04-14 | クアルコム,インコーポレイテッド | 悪意のあるインフラストラクチャに対するワイヤレスデバイス対策のための方法および装置 |
WO2016157890A1 (ja) * | 2015-03-30 | 2016-10-06 | 日本電気株式会社 | 同報配信システム、ゲートウェイ装置、同報配信方法及び記憶媒体 |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101365588B1 (ko) * | 2012-07-25 | 2014-02-21 | 에스케이텔레콤 주식회사 | 기지국게이트웨이장치 및 기지국게이트웨이장치의 동작 방법 |
US9265084B2 (en) * | 2012-09-11 | 2016-02-16 | Apple Inc. | Data buffering based on access stratum conditions in a call having both circuit-switched and packet-switched components |
US20160366631A1 (en) | 2014-12-04 | 2016-12-15 | Telefonaktiebolaget Lm Ericsson Publ) | Position determination of a wireless device |
CN105101246B (zh) * | 2015-07-27 | 2018-10-12 | 中国联合网络通信集团有限公司 | 一种确定存在覆盖空洞的小区的方法及装置 |
US9711521B2 (en) * | 2015-08-31 | 2017-07-18 | Taiwan Semiconductor Manufacturing Co., Ltd. | Substrate fabrication method to improve RF (radio frequency) device performance |
US9761546B2 (en) | 2015-10-19 | 2017-09-12 | Taiwan Semiconductor Manufacturing Co., Ltd. | Trap layer substrate stacking technique to improve performance for RF devices |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003244284A (ja) | 2002-02-20 | 2003-08-29 | Nec Corp | 移動端末、緊急呼管理装置、緊急呼管理システム及び緊急呼の管理方法 |
WO2009013792A1 (ja) * | 2007-07-20 | 2009-01-29 | Fujitsu Limited | 緊急呼番号情報取得システム |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5010A (en) * | 1847-03-13 | Improvement in hemp-brakes | ||
JP2535939B2 (ja) | 1987-08-27 | 1996-09-18 | 日本電気株式会社 | 多方向多重通信システム |
JPS6455927A (en) | 1987-08-27 | 1989-03-02 | Nec Corp | Multi-direction multiplex communication system |
US7623447B1 (en) * | 2000-04-10 | 2009-11-24 | Nokia Corporation | Telephony services in mobile IP networks |
GB0015365D0 (en) | 2000-06-22 | 2000-08-16 | Nokia Networks Oy | Location services interworking with intelligent network |
EP1387589A1 (de) * | 2002-07-29 | 2004-02-04 | Siemens Aktiengesellschaft | Media Gateway zur Bereitstellung der PSTN/ISDN Dienste in Netzwerken der nächsten Generation |
US7333795B2 (en) * | 2003-10-24 | 2008-02-19 | Motorola Inc. | Emergency call placement method |
GB0326264D0 (en) | 2003-11-11 | 2003-12-17 | Nokia Corp | Emergency call support for mobile communications |
JP2005236703A (ja) * | 2004-02-20 | 2005-09-02 | Hitachi Hybrid Network Co Ltd | Ip電話網への再呼び出しシステム及び再呼び出し方法 |
JP4269983B2 (ja) * | 2004-03-12 | 2009-05-27 | 沖電気工業株式会社 | 中継装置、中継方法、および中継プログラム |
JP5155165B2 (ja) | 2005-08-02 | 2013-02-27 | クゥアルコム・インコーポレイテッド | Voip緊急呼出支援 |
EP1768337A1 (en) * | 2005-09-26 | 2007-03-28 | Alcatel | Intelligent border element |
DE602006007625D1 (de) * | 2006-02-24 | 2009-08-13 | Ericsson Telefon Ab L M | Gebührenberechnung- und ortsindikationen in einem generischen zugangsnetz |
JP4672571B2 (ja) * | 2006-02-24 | 2011-04-20 | 日本電信電話株式会社 | VoIPネットワークにおける緊急呼呼び返し方法、緊急呼呼び返しシステム、VoIPノード装置およびプログラム |
US20090061877A1 (en) * | 2006-07-14 | 2009-03-05 | Gallagher Michael D | Generic Access to the Iu Interface |
US20080076392A1 (en) | 2006-09-22 | 2008-03-27 | Amit Khetawat | Method and apparatus for securing a wireless air interface |
JP2008141490A (ja) * | 2006-12-01 | 2008-06-19 | Mitsubishi Electric Corp | 緊急通報制御装置、無線通信端末および基地局 |
CN101222750B (zh) * | 2007-01-09 | 2014-07-09 | 华为技术有限公司 | 处理紧急呼叫、紧急呼叫回叫中被叫用户的方法及其应用 |
US8019331B2 (en) * | 2007-02-26 | 2011-09-13 | Kineto Wireless, Inc. | Femtocell integration into the macro network |
WO2008111001A2 (en) | 2007-03-13 | 2008-09-18 | Nokia Corporation | System for establishing and controlling emergency priority in a communication system |
US8072953B2 (en) * | 2007-04-24 | 2011-12-06 | Interdigital Technology Corporation | Wireless communication method and apparatus for performing home Node-B identification and access restriction |
CN101068279B (zh) * | 2007-06-13 | 2011-01-19 | 中兴通讯股份有限公司 | 一种紧急呼叫的回呼实现方法 |
CN101466083B (zh) * | 2007-12-18 | 2010-12-08 | 华为技术有限公司 | 一种紧急呼叫方法和装置 |
CN101500213B (zh) | 2008-02-03 | 2011-04-20 | 华为技术有限公司 | 一种用户设备紧急接入的方法、设备和系统 |
CN101448232B (zh) * | 2008-04-30 | 2013-05-08 | 中兴通讯股份有限公司 | 紧急呼叫实现方法及系统、用户设备 |
JP4755223B2 (ja) | 2008-05-26 | 2011-08-24 | 富士通株式会社 | 無線通信システム |
US20120069737A1 (en) * | 2009-03-27 | 2012-03-22 | Telefonaktiebolaget L M Ericsson (Publ) | Overload avoidance with home node b gateway (henb gw) in lte |
BRPI1006629B1 (pt) | 2009-04-17 | 2021-07-20 | Nec Corporation | Sistema de comunicação móvel, aparelho de gateway, aparelho de rede de base e método de comunicação |
-
2010
- 2010-03-01 BR BRPI1006629-2A patent/BRPI1006629B1/pt active IP Right Grant
- 2010-03-01 CA CA2758430A patent/CA2758430C/en active Active
- 2010-03-01 JP JP2011509238A patent/JP5375954B2/ja active Active
- 2010-03-01 AU AU2010237984A patent/AU2010237984C1/en not_active Ceased
- 2010-03-01 KR KR20117024175A patent/KR20110138239A/ko not_active Application Discontinuation
- 2010-03-01 CN CN201080017080.1A patent/CN102396249B/zh active Active
- 2010-03-01 EP EP17163823.2A patent/EP3306966B1/en active Active
- 2010-03-01 US US13/258,888 patent/US9241247B2/en active Active
- 2010-03-01 CN CN201410747936.0A patent/CN104507090B/zh active Active
- 2010-03-01 KR KR1020137025671A patent/KR20130119508A/ko active Application Filing
- 2010-03-01 KR KR1020157000256A patent/KR101779458B1/ko active IP Right Grant
- 2010-03-01 RU RU2011146642/07A patent/RU2503141C2/ru active
- 2010-03-01 EP EP10764314.0A patent/EP2421286A4/en not_active Ceased
- 2010-03-01 WO PCT/JP2010/053204 patent/WO2010119728A1/ja active Application Filing
- 2010-03-01 CA CA2872131A patent/CA2872131C/en active Active
-
2013
- 2013-09-11 JP JP2013188233A patent/JP5605482B2/ja active Active
-
2014
- 2014-07-03 JP JP2014137453A patent/JP5648762B2/ja active Active
- 2014-10-28 JP JP2014219003A patent/JP2015043615A/ja active Pending
- 2014-12-22 US US14/578,947 patent/US9560508B2/en active Active
-
2015
- 2015-08-27 JP JP2015167924A patent/JP2016021766A/ja active Pending
- 2015-12-24 RU RU2015155588A patent/RU2632906C2/ru active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003244284A (ja) | 2002-02-20 | 2003-08-29 | Nec Corp | 移動端末、緊急呼管理装置、緊急呼管理システム及び緊急呼の管理方法 |
WO2009013792A1 (ja) * | 2007-07-20 | 2009-01-29 | Fujitsu Limited | 緊急呼番号情報取得システム |
Non-Patent Citations (3)
Title |
---|
"3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3(Release 8)", 3GPP TS 24.008 V8.5.0 (2009-03), March 2009 (2009-03-01), pages 277, 286, 287, XP050364471 * |
"3rd Generation Partnership Project;Technical Specification Group Radio Access Network;UTRAN architecture for 3G Home NodeB;Stage 2 (Release 8)", 3GPP TS 25.467 V8.1.0., March 2009 (2009-03-01), XP050369092 * |
See also references of EP2421286A4 |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016021766A (ja) * | 2009-04-17 | 2016-02-04 | 日本電気株式会社 | 移動通信システム、基地局、ゲートウェイ装置、コアネットワーク装置、通信方法 |
US9560508B2 (en) | 2009-04-17 | 2017-01-31 | Nec Corporation | Mobile communication system, base station, gateway apparatus, core network apparatus, and communication method |
JP2014500661A (ja) * | 2010-11-04 | 2014-01-09 | クアルコム,インコーポレイテッド | ワイヤレス通信システム内でのフェムトアクセスポイントを介した通信 |
US9544943B2 (en) | 2010-11-04 | 2017-01-10 | Qualcomm Incorporated | Communicating via a FEMTO access point within a wireless communications system |
WO2013168700A1 (ja) * | 2012-05-07 | 2013-11-14 | 株式会社エヌ・ティ・ティ・ドコモ | 移動局 |
JP2013236169A (ja) * | 2012-05-07 | 2013-11-21 | Ntt Docomo Inc | 移動局 |
US9769649B2 (en) | 2012-05-07 | 2017-09-19 | Ntt Docomo, Inc. | Mobile station |
JP2016511614A (ja) * | 2013-03-13 | 2016-04-14 | クアルコム,インコーポレイテッド | 悪意のあるインフラストラクチャに対するワイヤレスデバイス対策のための方法および装置 |
WO2016157890A1 (ja) * | 2015-03-30 | 2016-10-06 | 日本電気株式会社 | 同報配信システム、ゲートウェイ装置、同報配信方法及び記憶媒体 |
JPWO2016157890A1 (ja) * | 2015-03-30 | 2017-12-14 | 日本電気株式会社 | 同報配信システム、ゲートウェイ装置、同報配信方法及び記憶媒体 |
US10341822B2 (en) | 2015-03-30 | 2019-07-02 | Nec Corporation | Broadcast delivery system, gateway device, broadcast delivery method and storage medium |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5648762B2 (ja) | 移動通信システム、基地局、ゲートウェイ装置、コアネットワーク装置、通信方法 | |
JP4957864B2 (ja) | 移動通信システム | |
RU2574388C2 (ru) | Система мобильной связи, базовая станция, устройство шлюза, устройство базовой сети и способ связи | |
AU2014208327B2 (en) | Mobile communication system, base station, gateway apparatus, core network apparatus, communication method | |
AU2012203527B2 (en) | Mobile communication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080017080.1 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10764314 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010237984 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011509238 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13258888 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2758430 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2010237984 Country of ref document: AU Date of ref document: 20100301 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20117024175 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010764314 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 8346/CHENP/2011 Country of ref document: IN |
|
ENP | Entry into the national phase |
Ref document number: 2011146642 Country of ref document: RU Kind code of ref document: A |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: PI1006629 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: PI1006629 Country of ref document: BR Kind code of ref document: A2 Effective date: 20111017 |