JP2015115767A - Mobile communication system, mobile station, network device, and mobile communication method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mobile communication system, mobile station, network device, and mobile communication method that can ensure a terminal operation expected by the core network such as avoiding repeated call requests or location registration requests of the mobile station according to a Cause value communicated by the core network.SOLUTION: The method comprises: a step in which a mobile station transmits, to a network device via a wireless base station, a valid Cause value that can be recognized by the mobile station and indicates the reason why the core network rejects a call request or a location registration request from the mobile station; a step S10 in which the network device acquires the valid Cause value transmitted by the mobile station via the wireless base station; and a step S70 in which if the network device cannot accept the call request or the location registration request transmitted by the mobile station, the network device sets an associated Cause value which is an acquired valid Cause value and which is associated with the rejection reason, and transmits the associated Cause value set to the mobile station.

Description

  The present invention relates to a mobile communication system, a mobile station, a network device, and a mobile communication method capable of transmitting and receiving a Cause value indicating a reason why a core network rejects a transmission request or a location registration request from a mobile station.

  In recent years, in mobile communication systems, so-called “Always-on” type mobile stations have been increasing in which a communication path (bearer) between a mobile station and a core network is always established and communication is always possible. In particular, a smartphone having an LCD screen and a touch panel and allowing a user to install an application relatively freely is generally an always-on type.

  Such an always-on type mobile station automatically tries to establish a communication channel by re-transmitting the communication channel when the communication channel is disconnected for some reason or when the transmission request is rejected. For this reason, even when the communication path cannot be established for a specific reason, such as when the requested access point name (APN) cannot be established, the mobile station repeats retransmission, resulting in congestion of the core network. obtain.

  Therefore, in order to prevent such congestion, the 3rd Generation Partnership Project (3GPP) stipulates that the core network sends a response (Reject) including a value (Cause value) indicating the reason for rejection to the mobile station. (For example, see Non-Patent Document 1 and Non-Patent Document 2).

  FIG. 1 shows an example of a cause value of a packet transmission (ESM) system. For example, when a mobile station sends a call request based on VoLTE (Voice over LTE) to the core network, but the core network cannot connect to the requested APN, the Mobility Management Entity (MME) sends the PDN Connectivity received from the mobile station. In response to the request, PDN Connectivity Reject including Cause # 66 (Requested APN not supported in current RAT and PLMN combination) is transmitted to the mobile station. A mobile station that has received a PDN Connectivity Reject including Cause # 66 retransmits until a radio access technology (RAT) change (for example, change from LTE to 3G), power OFF / ON, or SIM card insertion / removal Cancel.

3GPP TS 23.228 V11.5.0 Subclause 5.10.3.0 Removal of IP CAN bearers used to transport IMS SIP signaling, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 11), 3GPP June 2012 3GPP TS 24.229 V11.5.0 B.2.2.1B Re-establishment of the PDP context for SIP signaling, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 11), 3GPP, September 2012

  However, the above-described conventional method for preventing retransmission of a mobile station using the Cause value has the following problems. Specifically, as shown in FIG. 1, the specified Cause value differs depending on the release of 3GPP Technical Standard. For example, the above-mentioned Cause # 66 is relatively new and is specified in Release 12, but is not specified in Release 8.

  Since the core network cannot know which Release is compatible with the mobile station that has transmitted the transmission request, there is a possibility that the cause value that the mobile station cannot recognize is notified. For example, the above-described Cause # 66 may be notified to a Release 8 compatible mobile station. In such a case, the mobile station cannot recognize the cause value, and thus repeats retransmission, which may cause unnecessary processing and congestion in the core network. Further, such a problem is not limited to a call origination request, but also applies to a mobile station location registration request to the core network.

  In addition, it is possible to manage the release of mobile stations, or to manage the recognizable cause values for each type of mobile station (model type), but when mobile stations sold overseas roam Considering the existence of mobile stations sold by Mobile Virtual Network Operator (MVMO) or mobile stations (so-called SIM-free terminals) obtained by users, such management takes time and is not thorough. .

  Therefore, the present invention has been made in view of such a situation, and the core network is surely prevented from repeating a transmission request or a location registration request of a mobile station based on a Cause value notified from the core network. It is an object of the present invention to provide a mobile communication system, a mobile station, a network apparatus, and a mobile communication method that can reliably execute an expected terminal operation.

  A first feature of the present invention is a mobile communication system 10 (mobile communication system) including a UE 100 (mobile station) and a network device (for example, MME 210) constituting a core network 200 (core network), The mobile station is a Cause value indicating a reason why the core network rejects a call origination request (for example, PDN Connectivity Request) or a location registration request (for example, Tracking Area Update Request) from the mobile station, and the mobile station A cause value transmission unit 107 (Cause value transmission unit) that transmits a recognizable effective cause value to the network device via a radio base station (NB20, eNB30), and the network device receives the radio from the mobile station. A Cause value acquisition unit 215 (Cause value acquisition unit) for acquiring the effective Cause value transmitted via the base station, and the transmission request or the location registration request transmitted from the mobile station are received. If it cannot be attached, the corresponding Cause value acquired by the Cause value acquisition unit, the corresponding Cause value associated with the reason that it cannot be accepted is set, and the set corresponding Cause value is moved. The gist is to include a Cause value setting unit 217 (Cause value setting unit) to be transmitted to the station.

  A second feature of the present invention is a mobile station that performs communication with a network device that constitutes a core network via a radio base station, and the core network rejects a transmission request or a location registration request from the mobile station. The gist of the present invention is to provide a cause value transmitting unit that transmits a cause value indicating the reason for the mobile station to the network device via the wireless base station.

  A third feature of the present invention is a network device that constitutes a core network and performs communication with a mobile station via a radio base station, and is transmitted from the mobile station via the radio base station, A Cause value indicating the reason why the core network rejects a call origination request or a location registration request from a station, and a Cause value acquisition unit for obtaining an effective Cause value that can be recognized by the mobile station; and transmitted from the mobile station If the call request or the location registration request cannot be accepted, the corresponding cause value acquired by the cause value acquisition unit and associated with the reason why the call cannot be accepted is set. And a cause value setting unit that transmits the set corresponding cause value to the mobile station.

  A fourth feature of the present invention is a mobile communication method using a mobile station and a network device constituting a core network, wherein the mobile station sends a call origination request or a location registration request from the mobile station. A cause value indicating a reason for rejection by the network, the effective cause value recognizable by the mobile station being transmitted to the network device via a radio base station, and the network device from the mobile station to the Acquiring the effective cause value transmitted via a radio base station; and when the network device cannot accept the transmission request or the location registration request transmitted from the mobile station, the acquired An effective cause value is set, and a corresponding cause value associated with the reason that it cannot be accepted is set, and the set corresponding cause value is moved. And summarized in that and transmitting to.

  According to the feature of the present invention, a mobile that can reliably execute a terminal operation expected by the core network, such as reliably preventing a mobile station's transmission request or location registration request from being repeated based on a Cause value notified from the core network. A communication system, a mobile station, a network device, and a mobile communication method can be provided.

It is a figure which shows the example of the Cause value of the conventional packet transmission (ESM) type | system | group. 1 is an overall schematic configuration diagram of a mobile communication system 10 according to an embodiment of the present invention. It is a functional block block diagram of UE100 which concerns on embodiment of this invention. It is a functional block block diagram of MME210 which concerns on embodiment of this invention. It is a figure which shows the operation | movement sequence which UE100 which concerns on embodiment of this invention includes all the effective Cause values in the message of a location registration type | system | group (MM) type | system | group. It is a figure which shows the operation | movement sequence which UE100 which concerns on embodiment of this invention includes the effective cause value of MM type | system | group in the message of a location registration (MM) type | system | group. It is a figure which shows the operation | movement sequence which UE100 which concerns on embodiment of this invention includes the effective Cause value of SM type | system | group in the packet transmission (SM) type | system | group message. It is a figure which shows the setting operation | movement flow of the corresponding Cause value by MME210 which concerns on embodiment of this invention. It is a figure which shows the example of the Cause value (effective Cause value) hold | maintained by UE100 which concerns on embodiment of this invention.

  Next, an embodiment of the present invention will be described. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. However, it should be noted that the drawings are schematic and ratios of dimensions and the like are different from actual ones.

  Accordingly, specific dimensions and the like should be determined in consideration of the following description. Moreover, it is a matter of course that portions having different dimensional relationships and ratios are included between the drawings.

(1) Overall Schematic Configuration of Mobile Communication System FIG. 1 is an overall schematic configuration diagram of a mobile communication system 10 according to the present embodiment. As shown in FIG. 1, the mobile communication system 10 includes a mobile station 100 (hereinafter referred to as UE 100), a radio base station 20 (hereinafter referred to as NB 20), a radio base station 30 (hereinafter referred to as eNB 30), and a core network 200.

  The UE 100 can be connected to the core network 200 via the 3G-type NB20 or the Long Term Evolution (LTE) -type eNB30. Note that the UE 100 may be connectable to the core network 200 via a radio access network according to the 2G scheme.

  The core network 200 includes a plurality of network devices, specifically, Mobility Management Entity 210 (hereinafter referred to as MME210), Serving GPRS Support Node (hereinafter referred to as SGSN220), Serving Gateway (SGW), Packet Data Network Gateway (PGW), Policy and Charging Rules Function (PCRF) and Mobile Switching Center / Visitor Location Register 230 (hereinafter referred to as MSC / VLR230).

  The MME 210 accommodates the eNB 30 and provides mobility control such as location registration of the UE 100, a bearer control function established by the UE 100, and the like. The SGSN 220 accommodates a radio access network (UTRAN) according to the 3G system including the NB 20, and provides a packet switching function and the like. SGSN 220 may accommodate a radio access network (GERAN) according to the 2G scheme.

  The SGW is a visited packet switch that accommodates a 3GPP (LTE) access system. The PGW is a connection point with the IMS platform, and is a packet switch that performs IP address assignment and packet transfer to the SGW. The PGW performs QoS control, bearer setting control, and the like in cooperation with the PCRF. The PCRF executes quality of service (QoS) control of user data transfer and control for charging.

  The MSC / VLR 230 is a 3G system circuit-switching domain switch, which controls and processes voice communication calls and performs location registration of the UE 100 and the like.

(2) Functional Block Configuration of Mobile Communication System Next, a functional block configuration of the mobile communication system 10 according to the present embodiment will be described. Specifically, the functional block configuration of UE 100 and MME 210 will be described.

(2.1) UE100
FIG. 3 is a functional block configuration diagram of UE 100. As illustrated in FIG. 3, the UE 100 includes a location registration processing unit 101, a connection processing unit 103, a cause value holding unit 105, and a cause value transmission unit 107.

  The location registration processing unit 101 performs processing related to location registration of the UE 100 with respect to the core network 200, specifically, mobility management (MM) -related processing. The location registration processing unit 101 transmits a location registration request corresponding to the cell in the area to the core network 200.

  More specifically, the location registration processing unit 101 can transmit a Tracking Area Update Request to the MME 210 when the UE 100 is in a cell formed by the eNB 30. Further, the location registration processing unit 101 can transmit a Routing Area Update Request to the SGSN 220 or an Attach Request to the MSC / VLR 230 when the UE 100 is in the cell formed by the NB 20.

  The connection processing unit 103 executes processing related to the connection of the UE 100 to the core network 200, specifically, Session Management (SM) processing. The connection processing unit 103 transmits to the core network 200 a call origination request corresponding to the cell in the service area and the communication type to be executed.

  More specifically, the connection processing unit 103 can transmit a PDN Connectivity Request to the MME 210 when the UE 100 is in a cell formed by the eNB 30. Further, the connection processing unit 103 can transmit an Activate PDP Context Request to the SGSN 220 when the UE 100 is in the cell formed by the NB 20.

  The Cause value holding unit 105 holds a Cause value indicating the reason why the core network 200 rejects the transmission request or the location registration request from the UE 100. Specifically, the Cause value holding unit 105 holds a Cause value that the UE 100 can recognize. The Cause value that can be recognized by the UE 100 differs depending on the release of 3GPP Technical Standard (TS) supported by the UE 100. For example, as shown in FIG. 1, the number of Cause values specified for Release 8 and Release 12 is different, and Cause # 66 is specified for Release 12, but is specified for Release 8. Not.

  FIGS. 9A and 9B show examples of Cause values (effective Cause values) held by the UE 100 (Cause value holding unit 105). As shown in FIG. 9A, the Cause value holding unit 105 may hold a list indicating whether or not all Cause values can be recognized (Supported / Not supported in the drawing). As shown in b), it may be held as a list indicating whether or not only a Cause value defined by a subsequent 3GPP Release (for example, Release 12) can be recognized.

  Further, the Cause value that can be recognized by the UE 100 is not limited to the TS supported by the UE 100, and may vary depending on the mounting state of the UE 100. For example, a specific Cause value may not be implemented and the UE 100 may not be able to recognize it. The Cause value holding unit 105 can also hold a Cause value (hereinafter referred to as an effective Cause value) that can be recognized by the UE 100 based on the corresponding Release and mounting status of the UE 100.

  The Cause value transmission unit 107 transmits a Cause value to the network devices configuring the core network 200. Specifically, the cause value transmission unit 107 sends the effective cause value held by the cause value holding unit 105 to the network device (MME210, SGSN220 or MSC / VLR230) via the radio base station (NB20 or eNB30). Send. That is, the Cause value transmission unit 107 is a Cause value indicating the reason why the core network 200 rejects a transmission request or a location registration request from the UE 100, and an effective Cause value that can be recognized by the UE 100 is transmitted via the radio base station. Can be sent to a network device.

  More specifically, the Cause value transmission unit 107 sends a message (Tracking Area Update Request, Routing Area Update Request) to the Non Access Stratum (NAS) layer transmitted to the network device by the location registration processing unit 101 or the connection processing unit 103. And an Attach Request) can include a list of valid Cause values. For example, the Cause value transmission unit 107 can include a list indicating all effective Cause values in the MM message. Alternatively, the Cause value transmission unit 107 may include a list indicating all effective Cause values in the SM message.

  Further, the Cause value transmission unit 107 can include an effective Cause value related to the call request in the call request message (PDN Connectivity Request and Activate PDP Context Request). For example, in the case of a PDN Connectivity Request, the Cause value transmission unit 107 can include only an ESM (EPS Session Management) effective Cause value as shown in FIG. 1 in the PDN Connectivity Request.

  Similarly, the Cause value transmission unit 107 can include an effective Cause value related to the location registration request in the location registration request message (Tracking Area Update Request, Routing Area Update Request, and Attach Request). For example, in the case of a Tracking Area Update Request, the Cause value transmission unit 107 can include only an EMM (EPS Mobility Management) type effective Cause value in the Tracking Area Update Request. A method of assigning the effective cause value type to each message will be described later.

(2.2) MME210
FIG. 4 is a functional block configuration diagram of the MME 210. As illustrated in FIG. 4, the MME 210 includes a location registration processing unit 211, a connection processing unit 213, a cause value acquisition unit 215, a cause value setting unit 217, and a cause value holding unit 219.

  The location registration processing unit 211 performs processing related to location registration of the UE 100 with respect to the core network 200. Specifically, the location registration processing unit 211 receives a location registration request from the UE 100, and performs location registration of the UE 100 with respect to the core network 200 based on the received location registration request. In addition, the location registration processing unit 211 transmits a response (Accept or Reject) to the received location registration request to the UE 100. Examples of responses here include Attach Accept, Attach Reject, Tracking Area Update Accept, Tracking Area Reject, and the like.

  The connection processing unit 213 executes processing related to the connection of the UE 100 to the core network 200. Specifically, the connection processing unit 213 receives a call request from the UE 100, and sets a communication path (bearer) with the UE 100 based on the received call request. Also, the connection processing unit 213 transmits a response (Accept or Reject) to the received call request to the UE 100. Examples of responses here include Activate Default Bearer Context Request, UE Connectivity Request Reject, and the like.

  The Cause value acquisition unit 215 acquires the effective cause value transmitted from the UE 100 via the radio base station (NB20 or eNB30). Specifically, the Cause value acquisition unit 215 acquires the effective Cause value included in the location registration request (Tracking Area Update Request, Routing Area Update Request, and Attach Request) received by the location registration processing unit 211. Also, the Cause value acquisition unit 215 acquires the effective Cause value included in the outgoing request (PDN Connectivity Request and Activate PDP Context Request) received by the connection processing unit 213.

  Cause value setting section 217 sets a Cause value to be transmitted to UE 100. Specifically, the Cause value setting unit 217 sets a Cause value indicating the reason why it cannot be accepted when it cannot accept a call request or a location registration request transmitted from the UE 100.

  In particular, the cause value setting unit 217 refers to the effective cause value acquired by the cause value acquisition unit 215 when setting the cause value. Specifically, the Cause value setting unit 217 includes, in the effective Cause value acquired by the Cause value acquisition unit 215, a Cause value to be transmitted to the UE 100 depending on the reason that it cannot be accepted. Set the Cause value.

  On the other hand, the Cause value setting unit 217, when the Cause value acquired by the Cause value acquisition unit 215 does not include a Cause value to be transmitted to the UE 100 depending on the reason that it cannot be accepted, that is, the UE 100 When the UE 100 cannot recognize the cause value to be transmitted to the UE, it is an effective cause value acquired by the cause value acquisition unit 215 and is associated with the reason that it cannot be accepted (hereinafter, the corresponding cause value) ) Is set. More specifically, the Cause value acquisition unit 215 sets another Cause value that is included in the effective Cause value and associated with the reason that it cannot be accepted.

  Also, the Cause value setting unit 217 transmits the set Cause value to the UE 100. Specifically, the Cause value setting unit 217 transmits a response message to the UE 100 including a Cause value via the connection processing unit 213 or a location registration request including the Cause value via the location registration processing unit 211. A response message to the UE 100 is transmitted. When the cause value setting unit 217 sets the corresponding cause value, the cause value setting unit 217 transmits a response message including the corresponding cause value to the UE 100.

  The Cause value holding unit 219 holds an association of Cause values used to substitute a Cause value to be transmitted to the UE 100 with a Cause value that can be recognized by the UE 100. The association is used when the cause value to be transmitted to the UE 100 cannot be recognized by the UE 100 (when it is not an effective cause value). For example, if the Cause value to be transmitted to UE100 is Cause # 66 (Requested APN not supported in current RAT and PLMN combination), but the Cause # 66 is not included in the effective Cause value that UE100 can recognize, it is valid. UE 100 is notified of Cause # 27 (Missing or unknown APN), which is a corresponding Cause value included in the Cause value and associated with Cause # 66. As described above, the cause value holding unit 219 holds the association between the cause value that should be transmitted to the UE 100 and the corresponding cause value that substitutes the cause value when the cause value cannot be transmitted.

  Also, the Cause value holding unit 219 can generate or update a list of effective Cause values that can be recognized by the UE 100 based on the effective Cause value acquired by the Cause value acquiring unit 215, and can also hold the list.

(3) Operation of Mobile Communication System Next, the operation of the mobile communication system 10 described above will be described. Specifically, an operation related to notification of a Cause value that can be recognized by the UE 100 from the core network 200 to the UE 100 will be described.

(3.1) Transmission of Effective Cause Value by UE 100 First, an example of the operation of transmitting an effective cause value by the UE 100 will be described. UE 100 is an operation that includes all effective cause values in a location registration (MM) message (operation example 1), and an operation that includes an MM effective cause value in a location registration (MM) message (operation example 2). , And an operation (operation example 3) of including an SM-based effective cause value in a packet transmission (SM) message.

(3.1.1) Operation example 1
FIGS. 5A to 5C show an operation sequence in which the UE 100 includes all effective cause values in a location registration (MM) message. As shown in FIG. 5A, the UE 100 can transmit an Attach Request including a list of valid cause values that can be recognized by the UE 100 (a list of corresponding cause values in the figure) to the MSC / VLR 230.

  Note that, as shown in FIG. 9A, the UE 100 may transmit a list indicating whether or not all Cause values can be recognized (Supported / Not supported in the figure), or FIG. ), A list indicating whether or not only a Cause value defined by a subsequent 3GPP Release (for example, Release 12) can be recognized may be transmitted.

  Further, as illustrated in FIG. 5B, when transmitting a Routing Area Update Request (RAU), the UE 100 can transmit a Routing Area Update Request including an effective Cause value to the SGSN 220. Further, as illustrated in FIG. 5C, when transmitting the Tracking Area Update Request (TAU), the UE 100 can transmit the Tracking Area Update Request including the effective Cause value to the MME 210.

(3.1.2) Operation example 2
6A to 6C show an operation sequence in which the UE 100 includes an MM-based effective cause value in a location registration (MM) -based message. As shown in FIG. 6A, the UE 100 can transmit a Location Area Update Request including a list of valid Cause values that can be recognized by the UE 100 (a list of corresponding MM Cause values in the figure) to the MSC / VLR 230.

  Further, as illustrated in FIG. 6B, when transmitting a Routing Area Update Request (RAU), the UE 100 includes a GPRS Mobility Management (GMM) system effective cause value (a list of corresponding GMM Cause values in the figure). A Routing Area Update Request can be sent to SGSN 220. Furthermore, as illustrated in FIG. 6C, when transmitting a Tracking Area Update Request (TAU), the UE 100 includes an EPS Cause Management (EMM) effective cause value (a list of corresponding EMM Cause values in the figure). Tracking Area Update Request can be sent to MME210.

(3.1.3) Operation example 3
FIGS. 7A and 7B show an operation sequence in which the UE 100 includes an SM-use effective cause value in a packet transmission (SM) message. As shown to Fig.7 (a), UE100 can transmit Activate PDP Context Request including the list | wrist of the effective Cause value which UE100 can recognize (list of corresponding SM Cause values in a figure) to SGSN220.

  Further, as illustrated in FIG. 7B, when transmitting a PDN Connectivity Request, the UE 100 transmits a PDN Connectivity Request including an EPS Session Management (ESM) -based effective Cause value (a list of corresponding ESM Cause values in the diagram). Can be sent to SGSN 220.

(3.2) Setting of corresponding Cause value by network device Next, setting of a corresponding Cause value by the network device will be described. FIG. 8 shows an operation flow for setting a corresponding Cause value by the network device, specifically, the MME 210.

  As shown in FIG. 8, MME210 acquires the Cause value (effective Cause value) transmitted from UE100 in the case of the location registration or Attach from UE100 (S10). Specifically, the MME 210 acquires a list of valid Cause values included in a message (Tracking Area Update Request or Attach Request) requesting location registration or attachment from the UE 100.

  Next, the MME 210 receives a request for transmission of packet communication to a specific Access Point Name (APN) from the UE 100 (S20). Specifically, the MME 210 receives a PDN Connectivity Request designating a specific APN (for example, APN #A) from the UE 100.

  Based on the received PDN Connectivity Request, the MME 210 determines whether or not connection to the APN is possible (S30). When connection to the APN is not possible, connection to the APN may be possible due to contractual reasons between the user of the UE 100 or the operator of the mobile communication system 10 when the service via the APN is not supported. The case where it is not recognized is mentioned.

  When the connection to the APN is possible, the MME 210 executes a process for connecting the UE 100 to the APN (S40). Specifically, the MME 210 instructs the SGW / PGW or the like associated with the APN to set a communication path (bearer) based on the PDN Connectivity Request.

When the connection to the APN is impossible, the MME 210, among the effective Cause values acquired from the UE 100, a Cause value indicating that the connection to the APN is impossible, specifically,
It is determined whether or not Cause # 66 (Requested APN not supported in current RAT and PLMN combination) is included (S50).

  When Cause # 66 is included in the effective Cause value, MME 210 notifies Cause 100 to UE 100 (S60). Specifically, the MME 210 transmits a PDN Connectivity Reject including the Cause # 66 to the UE 100.

  On the other hand, when Cause # 66 is not included in the effective Cause value, MME 210 notifies UE 100 of a Cause value that substitutes for Cause # 66 (S70). Specifically, the MME 210 notifies the UE 100 of Cause # 27 (Missing or unknown APN) as the corresponding Cause value associated with Cause # 66.

  In other words, the MME 210 determines that the UE 100 cannot recognize Cause # 66 based on the effective Cause value acquired from the UE 100, and selects the Cause # 27 associated with the Cause value similar to Cause # 66. . In addition, the MME 210 confirms that Cause # 27 is included in the effective Cause value. And MME210 transmits PDN Connectivity Reject containing Cause # 27 to UE100.

  It should be noted that the corresponding cause value associated with the cause value similar to the cause # 66 may be plural instead of single, and the MME 210 may select one of the plurality of corresponding cause values. Also good.

(4) Action / Effect According to the mobile communication system 10, the UE 100 transmits an effective cause value that can be recognized by the UE 100 to a network device such as the MME 210. In addition, when the network device that has acquired the effective cause value from the UE 100 cannot accept a transmission request or a location registration request transmitted from the UE 100, it is an effective cause value that has been acquired from the UE 100 and cannot be accepted. The corresponding Cause value associated with is set, and the set corresponding Cause value is transmitted to the UE 100. As a result, the UE 100 can reliably recognize the Cause value transmitted from the core network 200, and can prevent the UE 100 from repeating the transmission request and the location registration request even though the core network 200 cannot accept it.

  That is, according to the mobile communication system 10, even if the UE 100 does not support a specific Cause value, the UE 100 can reliably make a call request or a location registration request based on the Cause value notified from the core network 200. Repeating can be prevented. More specifically, in the mobile communication system 10, there are a mixture of UE100 corresponding to the Cause value added in the subsequent 3GPPP Release and UE100 not corresponding to the Cause value. Even in this case, it is possible to reliably prevent the UE 100 from recognizing the cause value and the location registration request without recognizing the cause value notified from the core network 200.

  In addition, even when a mobile station sold overseas roams, a mobile station sold by Mobile Virtual Network Operator (MVMO), or a mobile station (so-called SIM-free terminal) obtained by the user, the mobile station Based on the acquired effective cause value, a corresponding cause value that the mobile station can recognize can be set, so that the mobile station cannot recognize the cause value notified from the core network 200 regardless of the type of the mobile station. It is possible to reliably prevent repeated transmission requests and location registration requests.

  In the present embodiment, since the effective cause value is transmitted from the UE 100 to the core network 200 using the message of the transmission request or the location registration request, the effective cause value is set in the core network 200 without specifying a new message. You can be notified. Similarly, since the corresponding Cause value is transmitted from the core network 200 to the UE 100 using a response message to the transmission request or the location registration request, the corresponding Cause value is notified to the UE 100 without specifying a new message. Can do.

  In the present embodiment, the effective cause value related to the transmission request can be included in the transmission request message, and the effective cause value related to the position registration request can be included in the location registration request message. Therefore, only the effective cause value related to each request can be notified from the UE 100 to the core network 200 efficiently and quickly.

  Furthermore, in this embodiment, the effective cause value regarding the location registration request and the transmission request can be included in the location registration request message. For this reason, it is possible to promptly notify all effective cause values from the UE 100 to the core network 200 at the stage of the location registration request.

(5) Other Embodiments As described above, the content of the present invention has been disclosed through one embodiment of the present invention. However, it is understood that the description and drawings constituting a part of this disclosure limit the present invention. should not do. From this disclosure, various alternative embodiments will be apparent to those skilled in the art.

  For example, in the above-described embodiment of the present invention, the operation of setting the corresponding Cause value by the network device has been described by taking the MME 210 as an example, but the SGSN 220 and the MSC / VLR 230 can also perform substantially the same operation, Although the type of message to be handled is different (see FIGS. 5 to 7), it has substantially the same function as the MME 210. That is, the SGSN 220 and the MSC / VLR 230 can also configure a network device in the same manner as the MME 210.

  Further, in the above-described embodiment, the form in which the effective cause value and the corresponding cause value are notified using the message related to the transmission request or the location registration request has been described. However, the effective cause value and the corresponding cause value are new messages. And may be notified by the message.

  Further, the present invention may be expressed as follows. A first feature of the present invention is a mobile communication system 10 (mobile communication system) including a UE 100 (mobile station) and a network device (for example, MME 210) constituting a core network 200 (core network), The mobile station is a Cause value indicating a reason why the core network rejects a call origination request (for example, PDN Connectivity Request) or a location registration request (for example, Tracking Area Update Request) from the mobile station, and the mobile station A cause value transmission unit 107 (Cause value transmission unit) that transmits a recognizable effective cause value to the network device via a radio base station (NB20, eNB30), and the network device receives the radio from the mobile station. A Cause value acquisition unit 215 (Cause value acquisition unit) for acquiring the effective Cause value transmitted via the base station, and the transmission request or the location registration request transmitted from the mobile station are received. If it cannot be attached, the corresponding Cause value acquired by the Cause value acquisition unit, the corresponding Cause value associated with the reason that it cannot be accepted is set, and the set corresponding Cause value is moved. The gist is to include a Cause value setting unit 217 (Cause value setting unit) to be transmitted to the station.

  In the first feature of the present invention, the Cause value transmission unit transmits a message of the transmission request or the location registration request including the effective Cause value to the network device, and the Cause value setting unit includes the corresponding Cause value A response message to the call request or the location registration request including a value may be transmitted to the mobile station.

  In the first feature of the present invention, the cause value transmission unit may include an effective cause value related to the call request in the call request message.

  In the first feature of the present invention, the cause value transmission unit may include an effective cause value related to the location registration request in the location registration request message.

  In the first feature of the present invention, the cause value transmission unit may include an effective cause value relating to the location registration request and the transmission request in the location registration request message.

  A second feature of the present invention is a mobile station that performs communication with a network device that constitutes a core network via a radio base station, and the core network rejects a transmission request or a location registration request from the mobile station. The gist of the present invention is to provide a cause value transmitting unit that transmits a cause value indicating the reason for the mobile station to the network device via the wireless base station.

  A third feature of the present invention is a network device that constitutes a core network and performs communication with a mobile station via a radio base station, and is transmitted from the mobile station via the radio base station, A Cause value indicating the reason why the core network rejects a call origination request or a location registration request from a station, and a Cause value acquisition unit for obtaining an effective Cause value that can be recognized by the mobile station; and transmitted from the mobile station If the call request or the location registration request cannot be accepted, the corresponding cause value acquired by the cause value acquisition unit and associated with the reason why the call cannot be accepted is set. And a cause value setting unit that transmits the set corresponding cause value to the mobile station.

  A fourth feature of the present invention is a mobile communication method using a mobile station and a network device constituting a core network, wherein the mobile station sends a call origination request or a location registration request from the mobile station. A cause value indicating a reason for rejection by the network, the effective cause value recognizable by the mobile station being transmitted to the network device via a radio base station, and the network device from the mobile station to the Acquiring the effective cause value transmitted via a radio base station; and when the network device cannot accept the transmission request or the location registration request transmitted from the mobile station, the acquired An effective cause value is set, and a corresponding cause value associated with the reason that it cannot be accepted is set, and the set corresponding cause value is moved. And summarized in that and transmitting to.

  As described above, the present invention naturally includes various embodiments that are not described herein. Therefore, the technical scope of the present invention is defined only by the invention specifying matters according to the scope of claims reasonable from the above description.

10 Mobile communication systems
20 NB
30 eNB
100 UE
101 Location registration processing section
103 Connection processing section
105 Cause value storage
107 Cause value transmitter
200 core network
210 MME
211 Location registration processing section
213 Connection processing section
215 Cause value acquisition unit
217 Cause value setting section
219 Cause value holding part
220 SGSN
230 MSC / VLR

Claims (8)

A mobile communication system including a mobile station and a network device constituting a core network,
The mobile station is a cause value indicating a reason why the core network rejects a transmission request or a location registration request from the mobile station, and an effective cause value that can be recognized by the mobile station is transmitted via a radio base station. A Cause value transmitter for transmitting to the network device;
The network device is:
A Cause value acquisition unit for acquiring the effective Cause value transmitted from the mobile station via the radio base station;
When the call request or the location registration request transmitted from the mobile station cannot be accepted, it is the effective cause value acquired by the cause value acquisition unit, and is associated with the reason why the request cannot be accepted. A mobile communication system comprising: a cause value setting unit configured to set a corresponding cause value and transmit the set corresponding cause value to the mobile station. The Cause value transmitting unit transmits the call request or the location registration request message including the valid Cause value to the network device,
The mobile communication system according to claim 1, wherein the cause value setting unit transmits a response message to the call request or the location registration request including the corresponding cause value to the mobile station.   The mobile communication system according to claim 2, wherein the Cause value transmission unit includes an effective Cause value related to the call request in the call request message.   The mobile communication system according to claim 2, wherein the Cause value transmission unit includes an effective Cause value related to the location registration request in the location registration request message.   The mobile communication system according to claim 2, wherein the cause value transmission unit includes an effective cause value related to the location registration request and the transmission request in the location registration request message. A mobile station that communicates with a network device that forms a core network via a radio base station,
A cause value indicating a reason why the core network rejects a transmission request or a location registration request from the mobile station, and an effective cause value that can be recognized by the mobile station is transmitted to the network device via the radio base station. A mobile station including a cause value transmission unit for transmission. A network device that constitutes a core network and performs communication with a mobile station via a radio base station,
An effective cause that is transmitted from the mobile station via the radio base station and indicates a reason why the core network rejects a call origination request or a location registration request from the mobile station, and is recognized by the mobile station. A Cause value acquisition unit for acquiring a value;
When the call request or the location registration request transmitted from the mobile station cannot be accepted, it is the effective cause value acquired by the cause value acquisition unit, and is associated with the reason why the request cannot be accepted. A network device comprising: a cause value setting unit that sets a corresponding cause value and transmits the set corresponding cause value to the mobile station. A mobile communication method using a mobile station and a network device constituting a core network,
The mobile station indicates a cause value indicating a reason why the core network rejects a transmission request or a location registration request from the mobile station, and an effective cause value that can be recognized by the mobile station is transmitted via a radio base station. Transmitting to the network device;
The network device obtaining the effective cause value transmitted from the mobile station via the radio base station;
If the network device cannot accept the call origination request or the location registration request transmitted from the mobile station, it is the acquired effective cause value, and is associated with the reason for the failure to accept A mobile communication method comprising: setting a cause value and transmitting the set corresponding cause value to the mobile station.

Images