WO2015022764A1 - 無線通信システム及び課金制御のための方法 - Google Patents
無線通信システム及び課金制御のための方法 Download PDFInfo
- Publication number
- WO2015022764A1 WO2015022764A1 PCT/JP2014/003062 JP2014003062W WO2015022764A1 WO 2015022764 A1 WO2015022764 A1 WO 2015022764A1 JP 2014003062 W JP2014003062 W JP 2014003062W WO 2015022764 A1 WO2015022764 A1 WO 2015022764A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mtc
- address
- entity
- charging
- charging rule
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/66—Policy and charging system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/82—Criteria or parameters used for performing billing operations
- H04M15/8271—Based on the number of used services, e.g. call forwarding or call barring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/106—Mapping addresses of different types across networks, e.g. mapping telephone numbers to data network addresses
Definitions
- This application is related to billing control for Machine type communication (MTC).
- MTC Machine type communication
- Non-Patent Document 1 stipulates a charging function and a charging management in a packet-switched network of Third Generation Partnership Project (3GPP).
- packet forwarding nodes eg, egServing General Packet Radio Service (GPRS) Support Node (SGSN), Gateway GPRS Support Node (GGSN), Serving Gateway (S-GW), Packet Data Network Gateway ( P-GW)
- CTF Charging, Trigger, Function, (CTF), and Charging, Data, Function, (CDF).
- the packet forwarding node in the core network is called Packet Switched Core Network Node (PCN). That is, the PCN as a CTF collects charging information (charging information) about a chargeable event (chargeable event). Then, the PCN as the CDF generates Charging Data Record (CDR) for each predetermined charging party (charged party) using the collected billing information.
- PCN Packet Switched Core Network Node
- Chargeable event means an activity that uses a communication network resource or service.
- Billable events include user to user communication (eg, a single call, a data communication session or a short message), user to network communication (eg, service profile administration), inter-network communication (eg, transferring calls, signaling, or short messages), or mobility (eg, roaming or inter-system handover).
- CDR means formatted billing information (eg, e.g., call time, data transfer amount, etc.).
- One chargeable event may be divided into a plurality of charge units by a predetermined time limit (communication time) or a predetermined data volume limit.
- one charging target event may cause charging for a plurality of charging parties.
- one or more CDRs may be generated for one billable event.
- MTC Machine Type Communication
- M2M Machine-to-Machine
- 3GPP defines a mobile station (MS, UE) that is implemented in a machine and sensor for MTC as an “MTC device”.
- MTC devices are installed in various devices such as machinery (e.g., firewood vending machines, gas meters, electric meters, automobiles, railway vehicles) and sensors (e.g., sensors related to the environment, agriculture, traffic, etc.).
- the MTC device connects to the Public Land Mobile Network (PLMN) and communicates with the MTC application server (Application Server (AS)).
- PLMN Public Land Mobile Network
- AS Application Server
- the MTC application server is arranged outside the PLMN (external network), executes the MTC application, and communicates with the MTC UE application mounted on the MTC device.
- An MTC application server is generally controlled by an MTC service provider (M2M service provider).
- 3GPP is a network architecture that includes Service, Capability, Server (SCS) and Machine, Type, Communication, Interworking, Function (MTC-IWF), and reference points (interfaces) related to these to enable MTC application servers to communicate with MTC devices. ) Is defined.
- the SCS is an entity that connects an MTC application server to a 3GPP PLMN and enables the MTC application server to communicate with a UE (that is, an MTC device) via a PLMN service defined by 3GPP.
- the SCS also enables the MTC application server to communicate with the MTC-IWF. It is assumed that the SCS is controlled by a PLMN operator or an MTC service provider.
- MTC-IWF is a control plane entity belonging to PLMN.
- MTC-IWF has a connection with SCS, and nodes in PLMN (for example, Home Subscriber Server (HSS), Short Message Service-Service Center (SMS-SC), Serving GPRS Support Node (SGSN), Mobility Management Entity (MME), Mobile Switching Center (MSC)).
- HSS Home Subscriber Server
- SMS-SC Short Message Service-Service Center
- SGSN Serving GPRS Support Node
- MME Mobility Management Entity
- MSC Mobile Switching Center
- Non-Patent Document 2 describes the optimization of billing related to MTC (see Section 8.2 of Non-Patent Document 2). Specifically, Non-Patent Document 2 describes generating bulk CDR in units of MTC groups including a plurality of MTC devices instead of generating CDRs in units of individual MTC devices.
- the inventors of the present invention considered a use case in which one MTC device is used by a plurality of SCS, a plurality of MTC application servers, or a plurality of MTC service providers.
- using the MTC device means performing uplink data communication and / or downlink data communication with the MTC device.
- a case where one MTC device installed in an automobile is shared by an MTC application server of an automobile manufacturer, an MTC application server of an expressway administrator, and a plurality of MTC application servers of a plurality of traffic information providers is considered. .
- the communication fee of the MTC device is not charged to the contractor of the MTC device, but the customer who uses the MTC device (that is, the administrator of the SCS, the administrator of the MTC application server, or It may be appropriate for each MTC service provider) to be charged.
- the customer who uses the MTC device that is, the administrator of the SCS, the administrator of the MTC application server, or It may be appropriate for each MTC service provider
- PCN Packet Switched Core Core Network Node
- CTF Packet Switched Core Core Network Node
- CDF Packet Switched Core Core Network Node
- the present invention has been made on the basis of the knowledge of the inventor described above, and one of its purposes is to provide MTC to customers who use MTC devices in use cases where one MTC device is used by a plurality of customers. It is to provide a method and an apparatus for enabling charging of a communication charge of a device.
- a policy type and charging type rule function (PCRF) entity includes a control entity that transmits a charging rule creation instruction.
- the charging rule creation instruction includes a first address indicating a communication destination node or network when the MTC device receives the trigger information.
- the method for charging control includes a policy type and a charging type rule function when a device action request including trigger information transmitted to a machine type communication (MTC) device is received from a service type Capability server (SCS).
- PCRF includes sending a billing rule creation instruction to the entity.
- the billing rule creation instruction includes a first address indicating a communication destination node or network when the MTC device receives the trigger information.
- the program includes a group of instructions for causing a computer to perform the method according to the second aspect described above.
- the wireless communication system includes a Machine type Communication Interworking Function (MTC-IWF) entity, a Policy and Charging Rule Function (PCRF) entity, and a packet forwarding node.
- MTC-IWF Machine type Communication Interworking Function
- PCRF Policy and Charging Rule Function
- the MTC-IWF entity is configured to receive a device action request including trigger information from a Service Capability Server (SCS). Further, the MTC-IWF entity is configured to send a device trigger request including the trigger information to a serving node in response to receiving the device action request. Furthermore, the MTC-IWF entity is configured to send a charging rule creation instruction to a Policy and Charging Rule Function (PCRF) entity in response to receiving the device action request.
- PCRF Policy and Charging Rule Function
- the charging rule creation instruction includes a first address indicating a node or network with which a target machine type communication (MTC) device should communicate in the user plane in response to delivery of the trigger information based on the device trigger request.
- the PCRF entity is configured to create a charging rule in response to the charging rule creation instruction.
- the charging rule includes an uplink packet flow transmitted from the target MTC device in which the first address is designated as a destination address, and the target MTC device in which the first address is designated as a source address. Define at least one of the downlink packet flows to be transmitted.
- the PCRF entity is configured to transmit the charging rule to a packet forwarding node located in the core network.
- the packet forwarding node counts at least one of the uplink packet flow and the downlink packet flow based on the charging rule, and includes Charging Data Record () including charging information aggregated with respect to the first address. CDR).
- a method and an apparatus are provided for enabling the customer who uses the MTC device to charge the communication fee of the MTC device. it can.
- FIG. 1 is a diagram illustrating a configuration example of a wireless communication network according to the present embodiment.
- the wireless communication network according to the present embodiment is a 3GPP Universal Mobile Telecommunications System (UMTS) network or a Long Term Evolution (LTE) network.
- UMTS Universal Mobile Telecommunications System
- LTE Long Term Evolution
- MTC-IWF entity 1 is a control plane entity belonging to PLMN5.
- the MTC-IWF entity 1 has a connection with the SCS 2 via the Tsp reference point.
- the Tsp reference point is, for example, Application Programming Interfaces (API), and uses a Diameter-based protocol.
- the MTC-IWF entity 1 has a connection with a node in the PLMN 5.
- MTC-IWF entity 1 has a connection with HLR / HSS 51 via an S6m reference point, a connection with SMS-SC 52 via a T4 reference point, and a T5a / T5b reference point. Connection to the SGSN / MME 53.
- the MTC-IWF entity 1 may be a single independent physical entity or may be a functional entity added to another network element (for example, HLR / HSS 51 or SGSN / MME 53). .
- the HLR / HSS 51 is a control plane node arranged in the core network of the PLMN 5 and manages the subscriber information of the UE 3.
- SMS-SC 52 transmits a short message in the Mobile Terminated (MT) direction and a short message in the Mobile Originated (MO) direction.
- SGSN / MME 53 is a control plane node arranged in the core network of PLMN 5 and performs terminal mobility management (e.g. location registration), bearer management (e.g. bearer establishment, bearer configuration change, bearer release), and the like.
- SGSN / MME 53 sends and receives control messages to and from nodes in Radio Access Network (RAN) 56 (that is, Radio Network Controller (RNC), eNodeB, etc.) and Non-Access Stratum (NAS) with UE3. Send and receive messages.
- RAN Radio Access Network
- RNC Radio Network Controller
- NAS Non-Access Stratum
- the NAS message is a control message that is not terminated at the RAN 56 and is transmitted and received transparently between the UE 3 and the SGSN / MME 53 without depending on the RAN radio access scheme.
- the GGSN / P-GW 54 is a user plane packet transfer node arranged in the PLMN 5 core network, and transfers user data (that is, Internet Protocol (IP) packets).
- IP Internet Protocol
- the GGSN / P-GW 54 plays a role of a gateway to an external IP network (Packet Data Network in 3GPP).
- the GGSN / P-GW 54 has Charging Trigger Function (CTF), Charging Data Function (CDF), and Policy and Charging Enforcement Function (PCEF). That is, the GGSN / P-GW 54 serving as a CTF collects charging information (charging information) about a chargeable event (chargeable event). Then, the GGSN / P-GW 54 as the CDF generates Charging Data Record (CDR) for each predetermined charging party (charged party) using the collected charging information.
- CTF Charging Trigger Function
- CDF Charging Data Function
- PCEF Policy and Charging Enforcement Function
- the GGSN / P-GW 54 as the PCEF is based on the policy data and charging control (PCC) rules supplied from the policy data and charging function (PCRF) entity 55 in units of service data flows (ie, IP packet flows) of the UE 3. Quality of service (QoS) control and flow based bearer charging (FBC).
- PCC policy data and charging control
- PCRF policy data and charging function
- QoS Quality of service
- FBC flow based bearer charging
- the FBC is realized by CTF, CDF, and PCEF included in the GGSN / P-GW 54.
- the GGSN / P-GW 54 filters the service data flow of UE3, monitors the service data flow as a chargeable event that triggers the generation and closing of the CDR, counts the number of packets in the service data flow, Generate a CDR containing billing information about the flow.
- the PCRF entity 55 has an interface with the PCRF of the GGSN / P-GW 54 via the Gx reference point, and an interface with the Application Function (AF) via the Rx reference point.
- the MTC-IWF entity 1 and the PCRF entity 55 are connected by an Rx reference point. That is, the PCRF entity 55 receives application level service information from the MTC-IWF entity 1, determines the PCC rule, and supplies the PCC rule to the GGSN / P-GW 54.
- the PCC rule supply method from the PCRF entity 55 to the GGSN / P-GW 54 may be a method in which the PCRF entity 55 voluntarily provides a PCC rule to the GGSN / P-GW 54 (so-called push method), or the UE 3 bearer establishment Alternatively, a method (so-called pull method) in which the GGSN / P-GW 54 requests a PCC rule from the PCRF entity 55 according to bearer modification may be used.
- the PCC rule includes information elements necessary for PCEF in order to perform policy control (QoS control) and charging for each UE 3 service data flow.
- PCC rules include service data flow packet filter settings (called Traffic Flow Template (TFT) or Service Data Flow (SDF) template), billing methods (for example, offline billing, online billing, non-billing, etc.), measurement It includes methods (eg, time to be measured for service data flow, volume, events, etc.), service identifiers for identifying service data flows, and so on.
- TFT Traffic Flow Template
- SDF Service Data Flow
- the SCS 2 connects the MTC application server 4 to the PLMN 5 so that the MTC application server 4 can communicate with the UE 3 (that is, the MTC device) via the PLMN service defined by 3GPP. Further, the SCS 2 enables the MTC application server 4 to communicate with the MTC-IWF entity 1.
- the SCS 2 is controlled by the operator of the PLMN 5 or the MTC service provider. SCS2 is also called an MTC server or an M2M server.
- the SCS 2 may be a single independent physical entity or may be a functional entity added to another network element (for example, the MTC application server 4).
- UE3 executes MTC UE application 31 and behaves as an MTC device.
- the UE 3 as an MTC device connects to the SGSN / MME 53 via the Radio Access Network (RAN) 56 and communicates with the MTC application server 4.
- RAN Radio Access Network
- UE3 may be an MTC gateway device.
- MTC gateway devices have 3GPP mobile communication capabilities (ie UE capabilities) and connect to neighboring devices (eg sensors, radio frequency identification (RFID) tags, car navigation devices) via personal / local area connection technology To do.
- Specific examples of personal / local area connection technologies include IEEE 802.15, ZigBee, Bluetooth, IEEE 802.11a.
- the neighboring device connected to the MTC gateway device is typically a device that does not have a 3GPP mobile communication function, but may be a device that has a 3GPP mobile communication function (that is, an MTC device). .
- MTC device and MTC gateway device are used without any particular distinction. That is, the term MTC device as used herein encompasses an MTC gateway device. Therefore, UE3 as an MTC device also means UE3 as an MTC gateway device.
- the MTC-IWF entity 1 and SCS 2 perform device trigger request (Request) and confirmation, and notification of device trigger request result (confirmation) and confirmation (confirmation) at the Tsp reference point. That is, the MTC-IWF entity 1 receives a device action request for triggering the UE 3 as an MTC device from the SCS 2. Next, the MTC-IWF entity 1 transmits / receives a signaling message to / from the control node in the PLMN 5 in order to distribute trigger information to the UE 3 based on the device action request. In 3GPP, it is assumed that, for example, a T4 reference point or a T5 (T5a, T5b, or T5c) reference point is used for distribution of trigger information.
- the MTC-IWF entity 1 When using the T4 reference point, the MTC-IWF entity 1 transmits a device trigger request for delivery of trigger information to the SMS-SC 52. On the other hand, when the T5 reference point is used, the MTC-IWF entity 1 transmits a device trigger request to the SGSN / MME 53. The MTC-IWF entity 1 receives the trigger information distribution result from the SMS-SC 52 or the SGSN / MME 53 and transmits the trigger information distribution result to the SCS 2.
- the customer who uses the MTC device is notified.
- the MTC-IWF entity 1, the PCRF entity 55, and the GGSN / P-GW 54 operate as follows.
- UE 3 MTC device
- SCS 2 or application server 4 that is a device trigger request source in response to reception of trigger information by a device trigger.
- the charge for data communication on the user plane of UE3 after device triggering can be charged to the device trigger requesting customer (that is, SCS administrator, MTC application server administrator, or MTC service provider).
- MTC-IWF entity 1 receives a device action request (Device Action Request (DAR)) including trigger information for UE 3 (that is, target MTC device) from SCS2.
- DAR Device Action Request
- the MTC-IWF entity 1 transmits a device trigger request (Device Trigger Request (DTR)) including trigger information to the SGSN / MME 53.
- DTR Device Trigger Request
- the MTC-IWF entity 1 may transmit DTR to SMS-SC52.
- the MTC-IWF entity 1 includes an internal identifier (for example, International Mobile Subscriber Identity (IMSI)) of the UE3 used in the PLMN 5 and an SGSN / MME53 (serving node) associated with the UE3.
- IMSI International Mobile Subscriber Identity
- SGSN / MME53 serving node
- the MTC-IWF entity 1 transmits a charging rule creation instruction to the PCRF entity 55 in response to receiving the DAR from the SCS 2.
- the charging rule creation instruction includes a first address indicating a node or network with which UE 3 (target MTC device) should communicate in the user plane in response to the delivery of trigger information based on DTR.
- the first address may be, for example, the IP address or network address of the SCS 2 that is the transmission source of the DAR, or the IP address or network address of the application server 4 that requested the DCS to the SCS 2.
- the DAR may include a first address.
- the MTC-IWF entity 1 may receive the first address from the SCS 2 when receiving the DAR from the SCS 2.
- the charging rule creation instruction may include an internal identifier (for example, IMSI) in the PLMN 5 of the UE 3 in order to specify the UE 3. Further, the charging rule creation instruction may include information indicating that the charging method is charging for each service data flow related to the first address. Specifically, the charging rule creation instruction is a downlink service data flow (IP packet flow) having a first address as a source address, or an uplink service data flow having a first address as a destination address ( IP packet flow) or both may be charged.
- IP packet flow IP packet flow
- IP packet flow IP packet flow
- the PCRF entity 55 creates a PCC rule in response to the charging rule creation instruction.
- This PCC rule is based on the uplink service data flow (IP packet flow) transmitted from the UE 3 in which the first address is designated as the destination address, or in the UE 3 in which the first address is designated as the source address. Define the downlink service data flow (IP packet flow) to be transmitted, or both.
- the PCC rule may indicate the creation of a CDR including charging information aggregated for the service data flow of UE3 for the first address. Specifically, the PCC rule may indicate a packet count of a service data flow and acquisition of a time stamp as a measurement method.
- the PCRF entity 55 transmits the PCC rule to the GGSN / P-GW 54 having PCEF and CDF.
- the PCRF entity 55 may push the PCC rule to the GGSN / P-GW 54.
- the GGSN / P-GW 54 may transmit a PCC request to the PCRF entity 55 and pull-receive the PCC rule from the PCRF entity 55.
- the GGSN / P-GW 54 is an uplink service flow in which the first address is designated as the destination address, or a downlink service flow in which the first address is designated as the source address, or Both of these are counted, and a CDR including billing information aggregated for the first address is created.
- the GGSN / P-GW 54 uses each MTC device instead of each MTC device (ie, UE). It is possible to create a CDR including billing information aggregated for each customer. Therefore, this embodiment makes it possible to charge the communication fee of the MTC device to the customer who uses the MTC device.
- FIG. 2 is a sequence diagram showing an example of a charging control method according to the present embodiment.
- the SCS 2 transmits a device action request (DAR) to the MTC-IWF entity 1.
- This DAR includes trigger information to be transmitted to the UE 3 and a first address (in this case, the IP address of the application server 4) for identifying the customer who requested the device trigger.
- the DAR may include an external identifier (eg, uniform resource identifier (URI)) of UE 3 (target MTC device).
- URI uniform resource identifier
- the MTC-IWF entity 1 inquires of the HLR / HSS 51 about the UE 3 internal identifier (here, IMSI) corresponding to the UE 3 external identifier and the SGSN / MME 53 (serving node) associated with the UE 3. Based on the response from the HLR / HSS 51, the MTC-IWF entity 1 selects a transmission destination of a device trigger request (DTR) from among a plurality of SGSN / MMEs 53.
- DTR device trigger request
- step S103 the MTC-IWF entity 1 transmits DTR to the selected SGSN / MME 53.
- This DTR includes an internal identifier (here, IMSI) of UE3 (target MTC device) and trigger information to be transmitted to UE3.
- the MTC-IWF entity 1 transmits a PCC rule creation instruction to the PCRF entity 55.
- This PCC rule creation instruction includes an internal identifier (here, IMSI) of UE 3 (target MTC device), and a first address (here, the IP address of application server 4) for identifying the customer who requested the device trigger. )including.
- the PCRF entity 55 creates a PCC rule for Flow Based ⁇ ⁇ ⁇ ⁇ bearer Charging (FBC) of UE3's uplink service data flow and / or downlink service data flow for the first address.
- FBC bearer Charging
- SGSN / MME 53 delivers trigger information to UE3.
- the SGSN / MME 53 may distribute trigger information from the SGSN / MME 53 to the UE 3 using NAS-Protocol Data Unit (NAS-PDU).
- NAS-PDU NAS-Protocol Data Unit
- Various methods have been proposed for the delivery of trigger information or small data using NAS-PDU.
- the trigger information may be delivered to the UE 3 as an SMS message, for example.
- ECM-IDLE EPSRANConnection Management IDLE
- RRC_IDLE Radio Resource Control IDLE
- step S106 in response to receiving the trigger information, the UE 3 starts a bearer establishment procedure (for example, Service Request procedure) in order to perform data communication on the user plane.
- the PCRF entity 55 transmits the PCC rule created in accordance with the PCC rule creation instruction in step S104 to the GGSN / P-GW 54 (step S107).
- the PCC rule may be sent from the PCRF entity 55 to the GGSN / P-GW 54 in IP Connectivity Access Network (IP-CAN) session Establishment / Modification procedure initiated by the GGSN / P-GW 54 as the PCEF.
- IP-CAN IP Connectivity Access Network
- the PCC rule may be pushed from the PCRF entity 55 to the GGSN / P-GW 54.
- step S108 the UE 3 performs data communication (IP packet communication) on the user plane with the SCS 2 or the MTC application server 4.
- the GGSN / P-GW 54 performs policy control (QoS control) and charging for each service data flow of the UE 3 in accordance with the PCC rules.
- QoS control policy control
- the GGSN / P-GW 54 monitors the service data flow of the UE 3, and generates a CDR for each customer (here, the MTC application server 4) with which the UE 3 communicates. To do.
- FIG. 3 is a block diagram illustrating a configuration example of the MTC-IWF entity 1 according to the present embodiment.
- the MTC-IWF entity 1 shown in FIG. 3 includes a device trigger control unit 10 that controls a device trigger for the UE 3 (MTC device).
- the device trigger control unit 10 is configured to receive a DAR including trigger information from the SCS 2.
- the device trigger control unit 10 is configured to transmit DTR including trigger information to the SGSN / MME 53 in response to reception of the DAR.
- the device trigger control unit 10 is configured to transmit a PCC rule creation instruction to the PCRF entity 55 in response to reception of the DAR.
- the PCC rule creation instruction includes the first address indicating the node or network of the external network (PDN) with which the UE 3 should communicate in the user plane in response to the delivery of the trigger information based on the DTR.
- the first address is, for example, the address of the SCS 2 or the MTC application server 4 managed by the customer who requested the device trigger, or the network address of the network to which these belong.
- FIG. 4 is a flowchart showing an example of an operation for charging in the MTC-IWF entity 1 according to the present embodiment.
- the MTC-IWF entity 1 receives a DAR requesting a device trigger from the SCS2.
- the MTC-IWF entity 1 inquires of the HLR / HSS 51 about the IMSI and serving node information of the device trigger UE3 (target MTC device).
- step S203 the MTC-IWF entity 1 selects the SGSN / MME 53 based on the inquiry result to the HLR / HSS 51 (that is, the received serving node information).
- step S204 the MTC-IWF entity 1 transmits DTR to the selected SGSN / MME 53.
- step S ⁇ b> 205 the MTC-IWF entity 1 transmits a PCC rule creation instruction including the IP address (that is, the first address) related to the SCS 2 or the MTC application server 4 that is the device trigger request source to the PCRF entity 55.
- FIG. 5 is a flowchart showing an example of an operation for charging in the PCRF entity 55 according to the present embodiment.
- the PCRF entity 55 receives from the MTC-IWF entity 1 a PCC rule creation instruction including the IP address (that is, the first address) related to the device trigger request source SCS2 or MTC application server 4.
- a PCC rule that defines a service data flow between the SCS2 or MTC application server 4 that is a device trigger request source and the UE3 (target MTC device) is created.
- This PCC rule specifies a billing method and a measurement method necessary for collecting billing information and creating a CDR for each service data flow.
- step S303 the PCRF entity 55 receives a PCC request indicating the IMSI of the UE 3 (target MTC device) from the GGSN / P-GW 54.
- step S304 the PCRF entity 55 transmits the PCC rule to the GGSN / P-GW 54 in response to the PCC request.
- Steps S303 and S304 show the case where the GGSN / P-GW 54 pull-receives the PCC rule. As already described, the PCRF entity 55 pushes the PCC rule to the GGSN / P-GW 54 and sends it. Also good.
- FIG. 6 is a flowchart showing an example of an operation for charging in the GGSN / P-GW 54 according to the present embodiment.
- the GGSN / P-GW 54 receives a bearer establishment request (for example, Modify Bearer Request or Create Session Request from the SGSN or S-GW).
- the GGSN / P-GW 54 transmits a PCC request indicating the IMSI of UE3 (target MTC device) to the PCRF entity 55.
- the GGSN / P-GW 54 receives the PCC rule from the PCRF entity 55.
- This PCC rule defines a service data flow between the device trigger request source SCS2 or MTC application server 4 and UE3 (target MTC device), and charging information is collected and CDRs are created for each service data flow. Specify the billing method and measurement method necessary for this.
- the GGSN / P-GW 54 counts the service data flow based on the PCC rules, and creates a CDR including the charging information aggregated for the SCS2 or MTC application server 4 that is the device trigger request source.
- FIG. 7 is a sequence diagram illustrating an example of a charging control method according to the present embodiment.
- the MTC-IWF entity 21 has Charging Trigger Function (CTF) and Charging Data Function (CDF). That is, the MTC-IWF entity 21 as a CTF monitors the occurrence of a device trigger as a chargeable event. Then, the MTC-IWF entity 21 as a CDF creates a CDR including charging information that is aggregated regarding the SCS 22 or the MTC application server that requested the device trigger.
- CTF Charging Trigger Function
- CDF Charging Data Function
- the SCS 22 transmits a device action request (DAR) to the MTC-IWF entity 21.
- the DAR includes trigger information to be transmitted to UE3. Further, the DAR may include an external identifier (for example, URI) of the UE 23 (target MTC device).
- the MTC-IWF entity 21 inquires of the HLR / HSS 251 about the internal identifier (here, IMSI) of the UE 23 corresponding to the external identifier of the UE 23 and the SGSN / MME 253 (serving node) associated with the UE 23.
- the MTC-IWF entity 21 selects a destination of a device trigger request (DTR) from among a plurality of SGSN / MME 253 based on the response from the HLR / HSS 251.
- DTR device trigger request
- the MTC-IWF entity 21 transmits DTR to the selected SGSN / MME 253.
- the DTR includes an internal identifier (here, IMSI) of the UE 23 (target MTC device) and trigger information to be transmitted to the UE 23.
- step S505 the SGSN / MME 253 distributes trigger information to the UE 23 via the RAN 256.
- the delivery method of the trigger information may be the same as that in step S104 in FIG.
- step S505 the SGSN / MME 253 transmits a response (Device Trigger ⁇ ⁇ ⁇ ⁇ Request ACK) indicating success or failure of the device trigger to the MTC-IWF entity 21.
- step S506 the MTC-IWF entity 21 creates a CDR including the accounting information aggregated for the SCS 22 or MTC application server that is the device trigger request source.
- the MTC-IWF entity 21 may consider the success or failure of the device trigger in creating the CDR.
- a device trigger fee is charged. Can be charged to the customer who requested the device trigger.
- the processing performed by the MTC-IWF entity, SCS, MTC application server, PCRF entity, GGSN / P-GW, HLR / HSS, SGSN / MME, and UE described in the first and second embodiments is performed in the computer system.
- Non-transitory computer readable media include various types of tangible storage media (tangible storage medium). Examples of non-transitory computer-readable media are magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), Compact Disc Read Only Memory (CD-ROM), CD-ROM R, CD-R / W, 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.
- MTC-IWF Machine Type Communication Inter Working Function
- SCS Service Capability Server
- UE User Equipment
- PLMN Public Land Mobile Network
- Device Trigger Control Unit 31 MTC UE Application 51 Home Location Register / Home Subscriber Server (HLR / HSS) 52 Short Message Service-Service Center (SMS-SC) 53 Serving General Packet Radio Service (GPRS) Support Node / Mobility Management Entity (SGSN / MME) 54 Gateway GPRS Support Node / Packet Data Network Gateway (GGSN / P-GW) 55 Policy and Charging Rule Function (PCRF) 56 Radio Access Network (RAN)
Abstract
Description
図1は、本実施形態に係る無線通信ネットワークの構成例を示す図である。一例において、本実施形態に係る無線通信ネットワークは、3GPPのUniversal Mobile Telecommunications System(UMTS)ネットワーク又はLong Term Evolution(LTE)ネットワークである。
本実施形態では、1つのMTCデバイスに対して複数の顧客(つまり、SCSの管理者、MTC アプリケーションサーバの管理者、又はMTCサービスプロバイダ)からデバイストリガーが行われる際に、デバイストリガーの料金をデバイストリガーの要求元の顧客に課金するための方法及び装置について説明する。図7は、本実施形態に係る課金制御方法の一例を示すシーケンス図である。本実施形態では、MTC-IWFエンティティ21は、Charging Trigger Function (CTF) 及び Charging Data Function (CDF) を有する。すなわち、CTFとしてのMTC-IWFエンティティ21は、課金対象イベントとしてデバイストリガーの発生を監視する。そして、CDFとしてのMTC-IWFエンティティ21は、デバイストリガーの要求元のSCS22又はMTCアプリケーションサーバに関して集計された課金情報を含むCDRを作成する。
上述した第1及び第2の実施形態は、3GPPのUMTSネットワーク及びLTEネットワークに関する具体例を示した。しかしながら、第1及び第2の実施形態は、MTCをサポートする他の無線通信ネットワークに適用されてもよい。
2 Service Capability Server (SCS)
3 User Equipment(UE)
4 MTC アプリケーションサーバ
5 Public Land Mobile Network(PLMN)
10 デバイストリガー制御部
31 MTC UEアプリケーション
51 Home Location Register/Home Subscriber Server(HLR/HSS)
52 Short Message Service - Service Center(SMS-SC)
53 Serving General Packet Radio Service (GPRS) Support Node/Mobility Management Entity (SGSN/MME)
54 Gateway GPRS Support Node/Packet Data Network Gateway (GGSN/P-GW)
55 Policy and Charging Rule Function(PCRF)
56 Radio Access Network(RAN)
Claims (9)
- Machine type Communication(MTC)デバイスに送信されるトリガー情報を含むデバイスアクションリクエストをService Capability Server(SCS)から受信した場合にPolicy and Charging Rule Function (PCRF)エンティティに課金ルール作成指示を送信する制御手段を備え、
前記課金ルール作成指示は、前記MTCデバイスが前記トリガー情報を受信した場合の通信先のノード又はネットワークを示す第1のアドレスを含む、
無線通信システム。 - 前記課金ルール作成指示は、前記PCRFエンティティによる課金ルールの生成を引き起こし、
前記課金ルールは、コアネットワーク内に配置されたパケット転送ノードに前記PCRF エンティティから供給され、前記パケット転送ノードによる前記第1のアドレスに関して集計された課金情報を含むCharging Data Record(CDR)の作成のために使用される、
請求項1に記載の無線通信システム。 - 前記課金ルールは、前記第1のアドレスがディスティネーションアドレスとして指定されたアップリンク・パケットフロー、及び前記第1のアドレスがソースアドレスとして指定されたダウンリンク・パケットフローの少なくとも一方を定義する、請求項2に記載の無線通信システム。
- 前記第1のアドレスは、前記SCSのInternet Protocol(IP)アドレス若しくはネットワークアドレス、又は前記デバイスアクションリクエストを前記SCSに要求したアプリケーションサーバのIPアドレス若しくはネットワークアドレスである、請求項1~3のいずれか1項に記載の無線通信システム。
- 前記デバイスアクションリクエストは、前記第1のアドレスを含み、
前記第1のアドレスは、前記トリガー情報の配信によって前記MTCデバイスに通知される、
請求項1~4のいずれか1項に記載の無線通信システム。 - Machine type Communication(MTC)デバイスに送信されるトリガー情報を含むデバイスアクションリクエストをService Capability Server(SCS)から受信した場合にPolicy and Charging Rule Function (PCRF)エンティティに課金ルール作成指示を送信することを備え、
前記課金ルール作成指示は、前記MTC デバイスが前記トリガー情報を受信した場合の通信先のノード又はネットワークを示す第1のアドレスを含む、
課金制御のための方法。 - 課金制御のための方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体であって、
前記方法は、
Machine type Communication(MTC)デバイスに送信されるトリガー情報を含むデバイスアクションリクエストをService Capability Server(SCS)から受信した場合にPolicy and Charging Rule Function (PCRF)エンティティに課金ルール作成指示を送信することを備え、
前記課金ルール作成指示は、前記MTCデバイスが前記トリガー情報を受信した場合の通信先のノード又はネットワークを示す第1のアドレスを含む、
非一時的なコンピュータ可読媒体。 - Machine type Communication(MTC)デバイスに送信されるトリガー情報を含むデバイスアクションリクエストをService Capability Server(SCS)から受信した場合にPolicy and Charging Rule Function (PCRF)エンティティに課金ルール作成指示を送信する制御手段を備え、
前記課金ルール作成指示は、前記MTCデバイスが前記トリガー情報を受信した場合の通信先のノード又はネットワークを示す第1のアドレスを含む、
Machine type Communication Inter Working Function(MTC-IWF)エンティティ。 - Machine type Communication Inter Working Function(MTC-IWF)エンティティと、
Policy and Charging Rule Function(PCRF)エンティティと、
パケット転送ノードと、
を備え、
前記MTC-IWFエンティティは、トリガー情報を含むデバイスアクションリクエストをService Capability Server(SCS)から受信するよう構成され、
前記MTC-IWFエンティティは、前記デバイスアクションリクエストの受信に応答して、前記トリガー情報を含むデバイストリガーリクエストをサービングノードに送信するよう構成され、
前記MTC-IWFエンティティは、前記デバイスアクションリクエストの受信に応答して、Policy and Charging Rule Function(PCRF)エンティティに課金ルール作成指示を送信するよう構成され、
前記課金ルール作成指示は、前記デバイストリガーリクエストに基づく前記トリガー情報の配信に応答してターゲットMachine type Communication(MTC)デバイスがユーザープレーンにおいて通信するべきノード又はネットワークを示す第1のアドレスを含み、
前記PCRFエンティティは、前記課金ルール作成指示に応答して課金ルールを作成するよう構成され、
前記課金ルールは、前記第1のアドレスがディスティネーションアドレスとして指定された前記ターゲットMTCデバイスから送信されるアップリンク・パケットフロー、及び前記第1のアドレスがソースアドレスとして指定された前記ターゲットMTCデバイスに送信されるダウンリンク・パケットフローの少なくとも一方を定義し、
前記PCRFエンティティは、コアネットワーク内に配置されたパケット転送ノードに前記課金ルールを送信するよう構成され、
前記パケット転送ノードは、前記課金ルールに基づいて、前記アップリンク・パケットフロー及び前記ダウンリンク・パケットフローの少なくとも一方をカウントし、前記第1のアドレスに関して集計された課金情報を含むCharging Data Record(CDR)を作成するよう構成されている、
無線通信システム。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/911,622 US20160198049A1 (en) | 2013-08-12 | 2014-06-09 | Wireless communication system and method for charging control |
JP2015531719A JPWO2015022764A1 (ja) | 2013-08-12 | 2014-06-09 | 無線通信システム及び課金制御のための方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013167630 | 2013-08-12 | ||
JP2013-167630 | 2013-08-12 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015022764A1 true WO2015022764A1 (ja) | 2015-02-19 |
Family
ID=52468160
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/003062 WO2015022764A1 (ja) | 2013-08-12 | 2014-06-09 | 無線通信システム及び課金制御のための方法 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20160198049A1 (ja) |
JP (1) | JPWO2015022764A1 (ja) |
WO (1) | WO2015022764A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106851526A (zh) * | 2015-12-07 | 2017-06-13 | 阿尔卡特朗讯 | 一种用于处理mtc消息的方法与设备 |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015131926A1 (en) * | 2014-03-04 | 2015-09-11 | Nokia Solutions And Networks Management International Gmbh | Ran based gateway functions |
CN106233757B (zh) | 2014-03-31 | 2021-11-02 | 康维达无线有限责任公司 | M2m服务层与3gpp网络之间的过载控制和协调 |
EP3367640A4 (en) * | 2015-10-20 | 2019-05-22 | Sony Corporation | DEVICE AND METHOD |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
CN111211913B (zh) * | 2017-06-30 | 2021-04-09 | 华为技术有限公司 | 一种计费方法、设备及系统 |
CN110417560B (zh) | 2018-04-28 | 2023-09-12 | 华为技术有限公司 | 计费的方法、装置及系统 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004104462A (ja) * | 2002-09-10 | 2004-04-02 | Kaisen Baitai Kenkyusho:Kk | 遠隔監視カメラ制御方法 |
JP2009141518A (ja) * | 2007-12-04 | 2009-06-25 | Softbank Mobile Corp | 課金処理方法及びそのシステム |
WO2012022966A1 (en) * | 2010-08-20 | 2012-02-23 | Wireless Technology Solutions Llc | Apparatus, method and system for managing data transmission |
JP2012533242A (ja) * | 2009-07-16 | 2012-12-20 | ▲ホア▼▲ウェイ▼技術有限公司 | 課金計数のための方法および装置 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1260910C (zh) * | 2004-08-11 | 2006-06-21 | 华为技术有限公司 | 基于分组数据流计费触发事件和重授权事件的处理方法 |
EP2709291B1 (en) * | 2011-05-11 | 2018-10-10 | LG Electronics Inc. | Method and apparatus for mtc in a wireless communication system |
KR101830200B1 (ko) * | 2011-07-07 | 2018-04-11 | 삼성전자 주식회사 | 이동통신 망의 디바이스 트리거링 제어 장치 및 방법 |
JP5891790B2 (ja) * | 2011-12-28 | 2016-03-23 | 富士通株式会社 | 課金システム、課金情報処理装置、課金情報生成装置、課金情報修正方法、プログラム |
JP6194883B2 (ja) * | 2012-04-26 | 2017-09-13 | 日本電気株式会社 | 制御ノード、制御ノードに実装される方法、及びプログラム |
CN108347713B (zh) * | 2012-04-27 | 2021-12-28 | 交互数字专利控股公司 | Wtru及由wtru执行的方法 |
JP5961769B2 (ja) * | 2013-01-04 | 2016-08-02 | インターデイジタル パテント ホールディングス インコーポレイテッド | サービスレイヤデタッチコマンドおよびアタッチ通知を処理するための方法および装置 |
CN110418300B (zh) * | 2013-07-08 | 2021-08-03 | 康维达无线有限责任公司 | 将无imsi设备连接到epc |
KR102112132B1 (ko) * | 2013-07-24 | 2020-05-18 | 콘비다 와이어리스, 엘엘씨 | 서비스 도메인 과금 시스템 및 방법 |
EP3025524A2 (en) * | 2013-07-25 | 2016-06-01 | Convida Wireless, LLC | Service layer southbound interface and quality of service |
-
2014
- 2014-06-09 US US14/911,622 patent/US20160198049A1/en not_active Abandoned
- 2014-06-09 WO PCT/JP2014/003062 patent/WO2015022764A1/ja active Application Filing
- 2014-06-09 JP JP2015531719A patent/JPWO2015022764A1/ja active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004104462A (ja) * | 2002-09-10 | 2004-04-02 | Kaisen Baitai Kenkyusho:Kk | 遠隔監視カメラ制御方法 |
JP2009141518A (ja) * | 2007-12-04 | 2009-06-25 | Softbank Mobile Corp | 課金処理方法及びそのシステム |
JP2012533242A (ja) * | 2009-07-16 | 2012-12-20 | ▲ホア▼▲ウェイ▼技術有限公司 | 課金計数のための方法および装置 |
WO2012022966A1 (en) * | 2010-08-20 | 2012-02-23 | Wireless Technology Solutions Llc | Apparatus, method and system for managing data transmission |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106851526A (zh) * | 2015-12-07 | 2017-06-13 | 阿尔卡特朗讯 | 一种用于处理mtc消息的方法与设备 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2015022764A1 (ja) | 2017-03-02 |
US20160198049A1 (en) | 2016-07-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7444153B2 (ja) | 第1の装置による方法及びpcrf装置による方法 | |
WO2015022764A1 (ja) | 無線通信システム及び課金制御のための方法 | |
US9100816B2 (en) | Charging method, device, and system | |
EP3140954B1 (en) | Online charging for proximity services | |
JP6652177B2 (ja) | システム、サービスプラットフォーム、及び方法 | |
CN103517245B (zh) | 一种d2d通信的计费方法和系统 | |
WO2015033580A1 (ja) | 通信装置、制御装置、通信方法、制御方法およびプログラム | |
JP6481741B2 (ja) | 装置およびscsエンティティ | |
JP6090310B2 (ja) | 移動通信システム、ゲートウェイ装置、課金ポリシー制御方法及びプログラム | |
CN102111741B (zh) | 计费实现方法及装置 | |
CN104247331A (zh) | 用于管理网络资源的方法和节点以及相应的系统和计算机程序 | |
JP6394602B2 (ja) | Mtc−iwfエンティティ、scsエンティティ、pcrfエンティティ、及び通信方法 | |
US10237418B2 (en) | Methods, systems, and computer readable media for charging based on radio congestion in mobile networks | |
CN105025453A (zh) | 一种邻近通信的计费方法和设备 | |
WO2015033581A1 (ja) | 通信装置、制御装置、管理装置、通信方法、制御方法、管理方法およびプログラム | |
JP6484941B2 (ja) | ネットワークノード及び課金管理のための方法 | |
WO2011082524A1 (zh) | 机器到机器的数据传输方法、系统及移动性管理网元装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14836385 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2015531719 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14911622 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14836385 Country of ref document: EP Kind code of ref document: A1 |