WO2013161243A1

WO2013161243A1 - Control node, method mounted to control node, program, and mobile station

Info

Publication number: WO2013161243A1
Application number: PCT/JP2013/002666
Authority: WO
Inventors: 孝法岩井
Original assignee: 日本電気株式会社
Priority date: 2012-04-26
Filing date: 2013-04-19
Publication date: 2013-10-31
Also published as: JP6194883B2; JPWO2013161243A1

Abstract

A control node (16) contains a control unit (10). The control unit (10) responds to a first request from an external network (17) and transmits a new connection request to a core network node disposed on a core network (15). The new connection request triggers the core network (15) to replace an existing connection with the new connection in order to transfer packet data between a mobile station (11) and the external network (17).

Description

Control node, method implemented in control node, program, and mobile station

The present invention relates to a mobile communication system, and in particular, a connection for a mobile station to communicate with an external network (eg, packet, data, network (PDN)) via a cellular radio access network (radio access network (RAN)) and a core network. Regarding settings.

Third Generation Partnership Project (3GPP) Release 8 and later stipulates the following four procedures as a procedure for setting up a PDN connection and adding an individual bearer to an existing PDN connection.

(1) Set up the first PDN connection (including default bearer) led by the mobile station (hereinafter referred to as User Equipment (UE)). In 3GPP Release 8 and later, a default PDN connection including a default bearer is set when the UE is attached to the core network. Therefore, in 3GPP Release 8 and later, the procedure for setting the first PDN connection corresponds to the initial attach procedure. Specifically, this procedure is described in 3GPP TS 23.40111V11.0.0-12 (2011-12) §5.3.2 "Attach procedure".

(2) Add bearers (individual bearers) to existing PDN connections led by the network. The core network may start setting up additional individual bearers in response to a request from an external server. This procedure is described in 3GPP TS 23.401 V11.0.0 (2011-12) §5.4.1 Dedicated bearer activation ". In addition, 3GPP TS 23.203 V11.4.0 (2011-12) §7.4.2 “IP CAN Session Modification; PCRF Initiated” also describes this procedure.

(3) Add individual bearer to existing PDN connection led by UE. This procedure is described in 3GPP TS 23.401 V11.0.0 (2011-12) §5.4.5 "UE requested bearer resource modification".

(4) UE sets the new PDN connection in addition to the existing PDN connection. That is, a multiple PDN connection is set between the core network and the UE based on the UE request. This procedure is described in 3GPP TS 23.401 V11.0.0 (2011-12) 5.10.2 "UE requested PDN connectivity".

Here, “UE initiated” means that the setting of the PDN connection or additional bearer is triggered by a request (message) transmitted from the UE to the core network. On the other hand, “network initiative” means a core network in response to a request from an external network or an application function (eg, application service provider, third-party application server, SIP server) or in response to a voluntary determination of the core network. Means to start setting up a PDN connection or additional bearer.

Also, the 3GPP PDN connection is an association between the UE and an external network (i.e. PDN). A PDN connection is represented by the IP address (IPv4 address or IPv6 prefix) of the UE. The PDN is an IP network, such as the Internet, an Internet service provider, a corporate intra network, and the like. The UE and the packet core network use Access Point Name (APN) to identify the PDN. In Evolved Packet System (EPS), one PDN connection is set for a set of UE IP address (IPv4 address or IPv6 Prefix) and APN. One PDN connection may include a plurality of Evolved Packet System (EPS) bearers having different QoS parameters. That is, an individual EPS bearer can be set in addition to the default EPS bearer in one PDN connection. Setting information describing an EPS bearer is called an EPS bearer context. In the Universal Mobile Telecommunications System (UMTS), an additional General Packet Radio Service (GPRS) bearer can be set for one PDN connection. The configuration information describing the GPRS bearer is called a Packet Data Protocol (PDP) context.

Bearer is a logical communication path for transferring user data packets. For example, an evolved packet system (EPS) sets an EPS bearer, and UMTS sets a GPRS bearer. EPS bearers include radio bearers (between UE and eNB), S1 bearers (between eNB and serving gateway (S-GW)), and S5 / S8 bearers (S-GW and Packet Data Network Gateway (P-GW)). Between). A radio bearer is a radio link. The S1 bearer and the S5 / S8 bearer are GPRS Tunneling Protocol (GTP) tunnels. User data packets transferred through the GTP tunnel are encrypted using a tunneling protocol (e.g. IPsec).

The inventor of the present invention examined improvement of a mobile communication system suitable for machine type communication (MTC) service. MTC is also called a machine-to-machine (M2M) network or a sensor network. When MTC is housed in a mobile communication system, typically 3GPP communication functions (eg, environmental sensors for agriculture, traffic, etc.) and sensors (eg, vending machines, gas meters, electric meters, automobiles, railway vehicles) ie mobile station functions). 3GPP defines "MTC device" as a mobile station mounted on machines and sensors for MTC. The MTC device connects to the mobile operator's core network via the cellular RAN and “communicates with the MTC user. The MTC user is located in the external network and has an MTC application. The MTC application implemented in the MTC user. Communicates with the MTC application implemented on the MTC device, and the MTC user is also referred to as the Application Server (AS).

As shown in Non-Patent Document 1, 3GPP has three scenarios, an end model and an indirect model, as a realization scenario for end-to-end communication in the application layer between an MTC device and an MTC user. Is stipulated. In the direct model, the MTC user performs direct user plane (data plane) communication with the MTC device by connecting directly to the mobile operator network.

On the other hand, in the indirect model, MTC users connect to the mobile operator network indirectly through the service provided by the Service Capability Server (Services Capability Server (SCS)), thereby indirectly connecting with the MTC device. In addition to basic user plane communication, additional services on the control plane (eg トリガ triggering of MTC devices) are used. In the indirect model, the SCS communicates with the core network and communicates with the MTC device via the core network. In addition, the SCS provides MTC users with a user plane and data plane interface (e.g. application program interface (API)). The SCS may also be called an MTC server, an M2M service platform, an M2M service server, or an MTC service server. SCS is assumed to be both a model that is centrally managed by the mobile operator with the core network and a model that is managed by one or more MTC users regardless of the mobile operator. In the latter model, SCS and MTC users may be combined. In other words, the function of the SCS may be integrated with the function of the MTC user.

The hybrid model is a model that combines the direct model and the indirect model described above. That is, in the hybrid model, the MTC user directly connects to the operator network for user plane communication with the MTC device, and uses the SCS to use additional services on the control plane.

In MTC services, unlike human-to-human (H2H) services, MTC users are expected to have many usage forms with strong administrative authority. This is because the MTC device is a monitoring target by the MTC user in many usage modes. Therefore, in the MTC service, it is desirable that the core network can set a new PDN connection in response to a request from the MTC user side, not from the MTC device side. However, 3GPP Release 8 and later do not stipulate a procedure for setting a new PDN connection in addition to the existing PDN connection led by the network. For this reason, the external network (e.g. MTC user) cannot request the core network to set a new PDN connection with the UE (e.g. MTC device).

Note that, as described above, 3GPP Release 8 and later stipulates procedures for adding individual bearers to existing PDN connections led by the network. However, for example, when an IPv6 communication is newly started with a UE in which an external network is performing IPv4 communication using an IPv4 PDN connection, an additional bearer cannot be set for the existing IPv4 PDN connection. In this case, it is necessary to newly set up an IPv6 PDN connection in addition to the existing IPv4 PDN connection. However, external networks cannot request a new IPv6 PDN connection from the core network.

The present invention has been made based on the above-mentioned findings of the inventors. That is, the present invention provides a control node that contributes to network-driven setting of a new connection in addition to an existing connection between the UE and an external network (eg, PDN connection), a method implemented in the control node, a program, And to provide mobile stations.

In the first aspect, the control node includes a control unit. In response to the first request from the external network, the control unit operates to send a new connection request to the core network node arranged in the core network. The new connection request triggers the core network to set a new connection for packet data transfer between the mobile station and the external network in addition to the existing connection.

In the second aspect, the method implemented in the control node includes transmitting a new connection request to the core network node arranged in the core network in response to the first request from the external network. The new connection request triggers the core network to set a new connection for packet data transfer between the mobile station and the external network in addition to the existing connection.

In the third aspect, a program for causing a computer to perform a method implemented in a control node is provided. The method includes controlling to send a new connection request to a core network node located in the core network in response to a first request from an external network. The new connection request triggers the core network to set a new connection for packet data transfer between the mobile station and the external network in addition to the existing connection.

In the fourth aspect, the mobile station that communicates with the external network via the cellular radio access network and the core network includes a control unit. The controller sets a new connection for packet data transfer between the mobile station and the external network in addition to the existing connection based on a request from the core network via the cellular radio access network. Operate. The request is generated in response to a new connection request from the external network to the core network.

According to each aspect described above, in addition to the existing connection between the UE and the external network (eg と PDN connection), a control node that contributes to setting a new connection led by the network, a method implemented in the control node, A program and a mobile station can be provided.

1 is a block diagram illustrating a configuration example of a mobile communication network according to Embodiment 1. FIG. 3 is a flowchart illustrating an example of a method implemented in a control node according to the first embodiment. 6 is a block diagram illustrating another configuration example of the mobile communication network according to Embodiment 1. FIG. 6 is a block diagram illustrating another configuration example of the mobile communication network according to Embodiment 1. FIG. 6 is a block diagram illustrating another configuration example of the mobile communication network according to Embodiment 1. FIG. 6 is a sequence diagram illustrating an example of a procedure for setting a new connection in the mobile communication network according to Embodiment 1. FIG. 6 is a sequence diagram illustrating an example of a procedure for setting a new connection in the mobile communication network according to Embodiment 1. FIG. 6 is a sequence diagram illustrating an example of a procedure for setting a new connection in the mobile communication network according to Embodiment 1. FIG. FIG. 10 is a sequence diagram showing an example of a new connection setting procedure in the mobile communication network according to the second embodiment. FIG. 10 is a sequence diagram showing an example of a new connection setting procedure in the mobile communication network according to the third embodiment.

Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and redundant description is omitted as necessary for clarification of the description.

<Embodiment 1 of the Invention>
FIG. 1 shows a configuration example of a mobile communication network according to the present embodiment. In the configuration example of FIG. 1, UE 11 communicates with PDN 17 as an external network via cellular RAN 14 and core network 15. A connection (eg PDN connection) is set between UE 11 and core network 15 for packet data transfer between UE 11 and PDN 17. The mobile operator domain 18 generally indicates a network range managed and operated by a mobile operator.

Furthermore, the mobile communication network according to the present embodiment includes a control node 16. The control node 16 includes the control unit 10. The control unit 10 is configured to perform signaling between the core network 15 and the PDN 17. In response to a request from the PDN 17 (specifically, a node arranged in the PDN 17), the control unit 10 responds to a request from a core network node (eg P-GW, Mobility Management Entity (MME), Gateway) arranged in the core network 15. It operates to send a new connection request to GPRS Support Node (GGSN) or Serving GPRS Support Node (SGSN).

The new connection request triggers the core network 15 to set a new connection for packet data transfer between the UE 11 and the PDN 17 in addition to the existing connection. That is, the core network 15, the cellular RAN 14, and the UE 11 set an additional new connection used for communication between the UE 11 and the PDN 17 by performing signaling in response to a new connection request from the control node 16. Specifically, the UE 11 includes a control unit 110. Based on the request from the core network 15 via the cellular RAN 14, the control unit 110 operates to set a new connection for packet data transfer between the UE 11 and the PDN 17 in addition to the existing connection.

Each new connection and existing connection includes at least one bearer. As already mentioned, a bearer is a logical communication path for transferring user data packets. Moreover, a new connection is represented by the address of UE11 different from the address of UE11 in the existing connection. In other words, in the new connection, the UE 11 is identified by an address different from the address in the existing connection.

As an example, consider a case where the mobile communication network according to the present embodiment is an EPS including EPC and E-UTRAN. In this case, each of the new connection and the existing connection corresponds to a PDN connection and includes at least one EPS bearer. The new PDN connection is represented by an IP address of UE 11 that is different from the IP address of UE 11 in the existing PDN connection. However, since the new PDN connection and the existing PDN connection are PDN connections related to the same PDN 17, they are set for the same APN corresponding to the PDN 17. The new PDN connection may be identified by an IP version that is different from the IP version of the existing PDN connection. For example, when the existing PDN connection is an IPv4 connection, the new PDN connection may be an IPv6 connection.

The control node 16 having the control unit 10 shown in FIG. 1 may be a control plane node. That is, the user data packet transfer may be performed between the gateway node (e.g. P-GW, Gateway GPRS Support Node (GGSN)) included in the core network 15 and the PDN 17 without passing through the control node 16.

FIG. 2 is a flowchart showing a specific example of the operation of the control unit 10. In step S101, the control unit 10 receives a request from the PDN 17 having an existing connection with the UE 11. In step S102, the control unit 10 transmits a new connection request to the core network node (e.g. P-GW, MME, GGSN, or SGSN) in response to a request from the PDN 17.

As described above, in the example of FIG. 1, the control node 16 having the control unit 10 responds to the request from the PDN 17 and the core network nodes (eg P-GW, MME, GGSN, Or a new connection request is sent to SGSN). In response to the new connection request, the core network 15, the cellular RAN 14, and the UE 11 set a new connection for packet data transfer between the UE 11 and the PDN 17 in addition to the existing connection. That is, in the example of FIG. 1, a new connection between the UE 11 and the PDN 17 can be set by network initiative.

The function of the control node 16 described above (that is, the control unit 10) may be arranged in the core network 15. For example, the control unit 10 may be arranged in a gateway node included in the core network 15. The gateway node operates as a gateway with the PDN 17 and terminates a bearer set with the UE 11 for user data transfer. For example, in the case of EPS, the gateway node is a P-GW that terminates an EPS bearer. In the case of UMTS, the gateway node is a GGSN that terminates the GPRS bearer. FIG. 3 shows an example in which the control unit 10 is arranged in the P-GW 153 when the mobile communication network according to the present embodiment is EPS. In the example of FIG. 3, the P-GW 153 transmits a new connection request to the core network node (e.g. S-GW or MME) arranged in the core network 15 in response to the request from the PDN 17. Based on this new connection request, a new PDN connection is set between the P-GW 153 and the UE 11.

Further, when the mobile communication network according to the present embodiment provides the MTC service, the control node 16 shown in FIG. 1 may be a service capability server (Services Capability Server (SCS)). FIG. 4 shows an example in which the control unit 10 is arranged in the SCS 16A. The SCS 16A provides an interface to an MTC user (or MTC application) 17A, which is a specific example of the PDN 17. In response to a request from the MTC user 17A, the SCS 16A requests a new connection to a core network node (eg P-GW, MME, GGSN, SGSN, or MTC Interworking Function (MTC-IWF)) arranged in the core network 15. Send. Based on this new connection request, a new connection is set between the gateway node (e.g. P-GW or GGSN) included in the core network 15 and the UE 11. The MTC device 11A and the MTC user 17A, which are specific examples of the UE 11, can transmit and receive user data packets via an existing connection or a new connection.

The SCS 16A may transmit a new connection request to the MTC-IWF 154. The MTC-IWF 154 provides a function for interworking between the control node in the core network and the SCS 16A. That is, the MTC-IWF 154 transfers or translates the signaling protocol used at the interface with the SCS 16A in order to activate the function of the operator network (e.g. core network 15).

Note that FIG. 4 described above corresponds to the indirect model of MTC. The present embodiment can also be applied to an MTC hybrid model or a direct model. FIG. 5 shows a specific example of a hybrid model of MTC. In the example of FIG. 5, the MTC user 17A is directly connected to the core network 15 via a user plane (UP) interface and is connected to the SCS 16A via a control plane (CP) interface. In the same manner as described in the example of FIG. 4, the SCS 16A responds to the request from the MTC user 17A, and the core network node (eg P-GW, MME, GGSN, SGSN, or MTC) arranged in the core network 15 Send a new connection request to Interworking Function (MTC-IWF).

Further, in the MTC indirect model or the hybrid model shown in FIGS. 4 and 5, the control unit 10 may be arranged in a node having the MTC-IWF. As described above, the MTC-IWF provides a function for the SCS 16A to interact with the control node in the core network. The MTC-IWF communicates with, for example, an MME, a Home Subscriber Server (HSS) that manages subscriber data, and a Charge Data Function (CDF) that manages billing information. As an example, consider a model in which the SCS 16A is managed by one or more MTC users. In this model, the SCS 16A is located outside the mobile operator domain 18. In this model, when the MTC-IWF having the control unit 10 transmits a new connection request to a core network node (eg MME or SGSN) arranged in the core network 15 in response to a request from the SCS 16A as an external network. Good.

When the present embodiment is applied to the direct model of MTC, the control unit 10 may be arranged in the P-GW 153 as shown in FIG. The P-GW 153 may transmit a new connection request to the core network node (e.g. S-GW or MME) arranged in the core network 15 in response to the request from the MTC user 17A. Based on this new connection request, a new PDN connection is set between the P-GW 153 and the UE 11.

As already described, in the MTC service, it is expected that there are many usage modes in which the MTC user 17A has strong management authority. Therefore, in the MTC service, it is desirable that the core network 15 can set a new PDN connection in response to a request from the MTC user 17A side, not from the MTC device 11A side. However, 3GPP Release 8 and later do not stipulate a procedure for setting a new PDN connection in addition to the existing PDN connection led by the network. On the other hand, this embodiment can set a new PDN connection for communication between the MTC user 17A and the MTC device 11A in response to a request from the MTC user 17A. Therefore, this embodiment is suitable for a mobile communication network that provides an MTC service.

Subsequently, a specific example of signaling for generating a new connection led by a network based on a request from the PDN 17 will be described below. The sequence diagram of FIG. 6 shows a first example of a new connection setting procedure in the mobile communication network according to the present embodiment. The example in FIG. 6 is described with respect to EPS, and the core network 15 in FIG. 6 includes an MME 151, an S-GW 152, and a P-GW 153.

In step S201, the PDN 17 transmits a new connection request to the control node 16. This new connection request includes, for example, a UE ID indicating UE 11 and a QoS policy required for the new connection. For example, the PDN 17 may transmit a new connection request in response to determining the change of the QoS policy applied to the communication in the application layer with the UE 11. Further, the PDN 17 may transmit a new connection request in response to determining to start IPv6 (IPv4) communication while performing IPv4 (IPv6) communication with the UE 11.

In step S202, the control node 16 (that is, the control unit 10) authenticates whether the PDN 17 has the authority to request a new connection. The control node 16 may perform the authentication in cooperation with another node (e.g. policy server or Policy and charging rules and PCR (PCRF)).

If the PDN 17 can authenticate that it has the authority to request a new connection, the control node 16 transmits a new connection request to the core network 15 (step S203). The new connection request requests the core network 15 to generate a new PDN connection. For example, the control node 16 may transmit a new connection request to the P-GW 153 that manages the end point of the bearer. The new connection request includes the identifier (UEID) of UE 11 and the designation of the QoS policy notified from PDN 17. The new connection request may include the QoS parameter of the EPS bearer corresponding to the QoS policy, not the QoS policy of the application layer. The QoS parameter of the EPS bearer includes, for example, at least one of QoS Class Identifier (QCI), Allocation and Retention Priority (ARP), Guaranteed Bit Rate (GBR), and Maximum Bit Rate (MBR).

The P-GW 153 of the core network 15 transmits a new connection request from the SCS 16 to the MME 151 or to the MME 151 via the S-GW 152. The MME 151 performs signaling with the S-GW 152 and the P-GW 153 to generate a bearer for a new PDN connection. Specifically, the MME 151 sends a session creation request (Create Session Request) to the S-GW 152 in the same manner as defined in §5.10.2 “UE Requested PDN Connection” of 3GPP TS 23.401 V11.0.0. Just send it.

In step S204, the core network 15 (e.g. MME 151) transmits a bearer setup request to the cellular RAN. The bearer setup request may include session management information including information on a new PDN connection, packet filter settings (e.g. TFT), and EPS bearer QoS parameters as information transmitted to the UE. The information on the new PDN connection includes, for example, the APN of the new PDN connection, the PDN type (i.e. IPv4 or IPv6), the PDN address (i.e. IP address) assigned to the UE 11 and the like. Specifically, the bearer setup request may include a message similar to the PDN Connectivity Accept message defined in §5.10.2 “UE requested PDN connectivity” of 3GPP TS 23.401 V11.0.0.

In step S205, the radio resource management entity (e.g. eNB) of the cellular RAN 14 transmits a reconfiguration request (e.g. RRC Connection Reconfiguration message) to the UE11. The reconfiguration request includes information on the new PDN connection notified from the core network 15 (e.g. MME 151). The UE 11 performs IP address setting and radio bearer setting for the new PDN connection according to the reconfiguration request, and maps the data packet flow to the bearer of the new PDN connection by adjusting the packet filter (e.g.gTFT).

In steps S206 to S208, responses to the requests in steps S203 to S205 are transmitted. More specifically, in step S208, the control node 16 (control unit 10) receives a new connection approval message transmitted from the core network 15 (eg P-GW 153) in response to the new connection request in step S203. . The approval message includes flow specifying information for specifying a data packet to be transferred using the EPS bearer of the added new PDN connection. The flow specifying information includes, for example, the IP address of the UE 11 in the new PDN connection. In addition, the flow identification information includes (i) bearer identifier (ii) port number, (iii) protocol number, and (iv) Type of At least one of Service (TOS) fields may be included.

In step S209, the control node 16 transmits a new connection approval message to the PDN 17 in response to the new connection request in step S201. This message includes flow specifying information for specifying the data packet transferred using the EPS bearer of the added new PDN connection.

In step S210, the PDN 17 performs data communication with the UE 11 using a new PDN connection.

Next, a sequence diagram relating to the second example shown in FIG. 7 will be described. FIG. 7 is a modification of FIG. 6 and shows a case where the mobile communication network provides an MTC service. The example of FIG. 6 corresponds to the MTC indirect model (FIG. 4), and the control unit 10 is arranged in the SCS 16A. The UE 11 is an MTC device 11A, and the PDN 17 is an MTC user 17A. In step S300 of FIG. 7, the MTC user 17A determines a change in the QoS policy applied to the MTC device 11A in the application layer. In step S301, the MTC user 17A transmits a QoS change request to the SCS 16A. This QoS change request includes specification of the UEID indicating the MTC device 11A and a new QoS policy after the change.

In step S302, the SCS 16A determines whether or not a new PDN connection is necessary according to the QoS change request from the MTC user 17A. Further, the SCS 16A authenticates whether or not the MTC user 17A has the authority to request a new connection. If it is determined that a new PDN connection is necessary and it is authenticated that the MTC user 17A has the authority to request a new connection, the SCS 16A transmits a new connection request to the core network 15 (step S303). In the direct model and the hybrid model, the SCS 16A can communicate with the P-GW 153 that manages the bearer termination point. Accordingly, the SCS 16A may transmit a new connection request directly to the P-GW 153 without going through the MTC-IWF 154. The operations and processes in steps S204 to S208 in FIG. 7 are the same as the corresponding step group shown in FIG.

In step S309, the SCS 16A transmits a QoS change notification to the MTC user 17 in response to the QoS change request in step S301. This notification includes flow specifying information for specifying the data packet transferred using the EPS bearer of the added new PDN connection. The operations and processes in step S210 in FIG. 7 are the same as the corresponding steps shown in FIG.

FIG. 8 shows a third example of a new connection setting procedure in the mobile communication network according to the present embodiment. In the second example (FIG. 7), an example is shown in which the SCS 16A performs authentication (S302) regarding new connection setting authority. However, this authentication function may be arranged in the MTC-IWF 154. FIG. 8 shows a procedure for creating a new connection by signaling via the MTC-IWF 154.

Steps S300, S301, S204 to S207, S309, and S210 in FIG. 8 are the same as the corresponding step group shown in FIG. In step S402, the SCS 16A determines whether or not a new PDN connection is necessary according to the QoS change request from the MTC user 17A. When it is determined that a new PDN connection is necessary, the SCS 16A transmits a new connection request to the MTC-IWF 154.

The MTC-IWF 154 authenticates whether or not the SCS 16A has the authority to request a new connection setting (step S403). The MTC-IWF 154 may perform the authentication in cooperation with another node (e.g. policy server, or policy and charging rules and function (PCRF)). When the SCS 16A authenticates that it has authority, the MTC-IWF 154 transfers a bearer generation request to the node of the core network 15 (step S404). The MTC-IWF 154 may transfer a bearer generation request to the P-GW 153 that manages the bearer termination point, for example. Further, the MTC-IWF 154 may transfer a bearer generation request to the MME 151.

In step S408, the MTC-IWF 154 receives a new connection approval message transmitted from the core network 15 (e.g. P-GW 153 or MME 151) in response to the new connection request in step S404. In step S409, the MTC-IWF 154 transfers a new connection approval message to the SCS 16A.

<Embodiment 2>
In the present embodiment, a modification of the above-described first embodiment will be described. The mobile communication network according to the present embodiment is configured such that a charging policy different from that of an existing connection can be applied to a new connection. For example, the mobile communication network may make the communication fee for the new PDN connection free. Further, the mobile communication network may make the communication fee for the new PDN connection lower or higher than the communication fee for the existing connection. Further, the mobile communication network may make the charging destination of the new connection different from the charging destination of the existing connection.

The sequence diagram of FIG. 9 shows a specific example of a new connection setting procedure in the mobile communication network according to the present embodiment. FIG. 9 is a modification of FIG. 6, and the operations and processes in steps S201 to S210 other than step S501 are the same as the corresponding steps shown in FIG.

In step S501, the control node 16 (control unit 10) communicates with the PCRF 155 of the core network 15 in order to apply a charging rule different from that of the existing PDN connection to the new PDN connection. Thereby, the PCRF 155 applies the charging rule for the new PDN connection to the P-GW 153 based on the communication with the control node 16. Then, the P-GW 153 communicates with a Charge Data Function (CDF) that manages charging information based on the set charging rule.

<Embodiment 3>
In the present embodiment, a modification of the above-described first embodiment will be described. In this Embodiment, the control part 10 operate | moves so that the starting request | requirement of the application program which uses a new connection may be transmitted to UE11. Thereby, the control part 110 of UE11 can specify the application program which uses a new connection. In other words, the UE 11 can specify the packet flow that should flow to the bearer of the new connection. Therefore, UE11 can set the packet filter with respect to the bearer of a new connection appropriately.

The sequence diagram of FIG. 10 shows a specific example of a new connection setting procedure in the mobile communication network according to the present embodiment. FIG. 10 is a modification of FIG. 7 and shows a case where the mobile communication network provides an MTC service. Operations and processes in other steps except steps S601, S609, and S610 in FIG. 10 are the same as the corresponding steps shown in FIG.

In step S601, the MTC user 17A transmits a QoS change request to the SCS 16A having the control unit 10. This QoS change request includes designation of the UE ID indicating the MTC device 11A and the new QoS policy after the change. Further, the QoS change request includes identification information (hereinafter referred to as application ID) of the application program to which the new QoS policy is applied.

In step S609, the SCS 16A transmits a notification indicating an application program using a new connection to the MTC device 11A. The notification in step S609 includes, for example, application program identification information (application ID).

In step S610, the MTC device 11A activates an application program corresponding to the application ID notified from the SCS 16A, and sets a packet filter to map a data packet transmitted / received by the application program to a bearer of a new PDN connection.

Note that FIG. 10 is only an example. For example, the operation of transmitting the application program activation request described in the present embodiment to the UE 11 may be added to the procedure illustrated in FIG. Further, the operation according to the present embodiment may be applied to an MTC direct model. Furthermore, the operation of transmitting the application program activation request described in the present embodiment to the UE 11 may be performed not only when the MTC service is provided but also for the normal UE 11.

<Other embodiments>
Embodiments 1 to 3 described above may be used in appropriate combination.

The processing performed by the control unit 10, the control unit 110, the control node 16, the SCS 16A, the UE 11, the MTC device 11A, and the nodes of the core network 15 (eg MME 151, P-GW 153) described in the first to third embodiments is the ASIC. You may implement | achieve using the semiconductor processing apparatus containing (Application | Specific * Integrated | Circuit). Moreover, these processes may be realized by causing a system including at least one computer called a microprocessor, a microcontroller, a Micro Processing Unit (MPU), or the like to execute a program. Specifically, one or a plurality of programs including an instruction group for causing the computer system to perform the algorithm described using the flowcharts and sequence diagrams in this specification may be created, and the programs may be supplied to the computer system. .

This program can be stored using various types of non-transitory computer readable media and supplied to a computer. Non-transitory computer readable media include various types of tangible storage media (tangible storage medium). Examples of non-transitory computer-readable media include magnetic recording media (eg, flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg, magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD- R, CD-R / W, and semiconductor memory (for example, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)). The program may also be supplied to the computer by various types of temporary computer-readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

Furthermore, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the gist of the present invention already described.

This application claims priority based on Japanese Patent Application No. 2012-101634 filed on April 26, 2012, the entire disclosure of which is incorporated herein.

10 Control Unit 11 Mobile Station (User Equipment (UE))
11A MTC device 11B MTC gateway device 12 Local device 13 Personal / local area network 14 Cellular radio access network 15 Core network 16 Control node 16A Services Capability Server (SCS)
17 Packet Data Network (PDN)
17A MTC user 18 Mobile operator domain 110 Control unit 151 Mobility management entity (MME)
152 Serving gateway (S-GW)
153 Packet data Network gateway (P-GW)
154 MTC interworking function (MTC-IWF)
155 Policy and Charging Rules Function (PCRF)

Claims

In response to the first request from the external network, the control unit operates to send a new connection request to the core network node arranged in the core network,
The new connection request triggers the core network to set a new connection for packet data transfer between a mobile station and the external network in addition to the existing connection.
Control node.
The control node according to claim 1, wherein the new connection is represented by a second address of the mobile station different from a first address of the mobile station representing the existing connection.
The control node according to claim 1 or 2, wherein the new connection is identified by an IP version different from the IP version of the existing connection.
The control node according to any one of claims 1 to 3, wherein the new connection request includes specification of a QoS parameter assigned to a bearer of the new connection.
The control node according to any one of claims 1 to 4, wherein the new connection request includes designation of a type of the new connection.
The first request indicates addition or change of a QoS policy applied at an application layer to the mobile station;
The control node includes specification of a bearer QoS parameter corresponding to the QoS policy,
The control node according to any one of claims 1 to 5.
The controller is further responsive to the first request to operate to authenticate whether the external network is authorized to create a new PDN connection;
The control unit operates to transmit the new connection request to the core network node on the condition that the external network has been authenticated as having the authority.
The control node according to any one of claims 1 to 6.
The control unit is further configured to receive a first notification including identification information transmitted from the core network in response to the new connection request and identifying a data packet to be transferred using the new connection. The control node according to any one of claims 1 to 7, which operates.
The control node according to claim 8, wherein the control unit further operates to notify the specific information to the external network in response to reception of the first notification.
10. The control unit according to claim 1, wherein the control unit is further operable to communicate with a charging rule function of the core network in order to apply a charging rule different from the existing connection to the new connection. The described control node.
The control node according to any one of claims 1 to 10, wherein the control unit further operates to transmit a request for starting an application program using the new connection to the mobile station.
The control node is a Packet-Data-Network Gateway,
The core network node is a Serving Gateway or a Mobility Management Entity.
The control node according to any one of claims 1 to 11.
The control node according to any one of claims 1 to 11, wherein the core network node is a Packet-Data-Network Gateway or a Mobility Management Entity.
The mobile station is a Machine Type Communication (MTC) device,
The external network includes an MTC node that communicates with the MTC device via the core network and a cellular radio access network.
The control node according to any one of claims 1 to 13.
A method implemented in a control node,
In response to a first request from an external network, comprising sending a new connection request to a core network node located in the core network;
The new connection request triggers the core network to set a new connection for packet data transfer between a mobile station and the external network in addition to the existing connection.
Method.
The method of claim 15, wherein the new connection is represented by a second address of the mobile station that is different from a first address of the mobile station representing the existing connection.
The method according to claim 15 or 16, wherein the new connection is identified by an IP version different from the IP version of the existing connection.
The method according to any one of claims 15 to 17, wherein the new connection request includes specification of a QoS parameter assigned to a bearer of the new connection.
The method according to any one of claims 15 to 18, wherein the new connection request includes designation of a type of the new connection.
The first request indicates addition or change of a QoS policy applied at an application layer to the mobile station;
The control node includes specification of a bearer QoS parameter corresponding to the QoS policy,
The method according to any one of claims 15 to 19.
Responsive to the first request further comprising authenticating whether the external network is authorized to create a new PDN connection;
The transmitting includes transmitting the new connection request to the core network node on condition that the external network has been authenticated to have the authority.
The method according to any one of claims 15 to 20.
16. The method of claim 15, further comprising receiving a first notification including identification information for identifying a data packet transmitted from the core network in response to the new connection request and transferred using the new connection. The method according to any one of items 1 to 21.
23. The method of claim 22, further comprising notifying the specific information to the external network in response to receiving the first notification.
The method according to any one of claims 15 to 23, further comprising communicating with a charging rule function of the core network to apply a charging rule different from the existing connection to the new connection.
The method according to any one of claims 15 to 24, further comprising transmitting a request for starting an application program that uses the new connection to the mobile station.
The control node is a Packet-Data-Network Gateway,
The core network node is a Serving Gateway or a Mobility Management Entity.
The method according to any one of claims 15 to 25.
The method according to any one of claims 15 to 25, wherein the core network node is Packet-Data-Network Gateway or Mobility Management Entity.
The mobile station is a Machine Type Communication (MTC) device,
The external network includes an MTC node that communicates with the MTC device via the core network and a cellular radio access network.
The method according to any one of claims 15 to 27.
A non-transitory computer-readable medium storing a program for causing a computer to perform a method implemented in a control node,
The method comprises controlling to send a new connection request to a core network node located in the core network in response to a first request from an external network;
The new connection request triggers the core network to set a new connection for packet data transfer between a mobile station and the external network in addition to the existing connection.
Computer readable medium.
A mobile station that communicates with an external network via a cellular radio access network and a core network,
A control unit operable to set in addition to an existing connection a new connection for packet data transfer between the mobile station and the external network based on a request from the core network via the cellular radio access network; Prepared,
The request is generated in response to a new connection request from the external network to the core network.
Mobile station.
The mobile station according to claim 30, wherein the new connection is represented by a second address of the mobile station different from a first address of the mobile station representing the existing connection.
The mobile station according to claim 30 or 31, wherein the new connection is identified by an IP version different from an IP version of the existing connection.
The mobile station according to any one of claims 30 to 32, wherein the control unit further operates to receive a request for starting an application program that uses the new connection.