JP2016025406A - Network node and method for charging management - Google Patents

Abstract

The present invention contributes to facilitation of charging and billing according to the volume of signaling caused by the operation of a wireless terminal. A network node (110) includes a processor (112) coupled to a memory (113). The processor (112) executes charging processing for the wireless terminal (211). The billing process includes recording the occurrence of control plane signaling due to the operation of the wireless terminal (211) in a billing data record (CDR). The CDR is used for billing in the billing domain. The control plane signaling occurs during at least one of a radio resource control connection establishment procedure, an attach procedure, a detach procedure, a bearer establishment procedure, and a handover procedure for the radio terminal (211). [Selection] Figure 3

Description

  The present application relates to charging management in mobile communication networks.

  Non-Patent Document 1 defines a basic architecture for charging function and charging management in the Third Generation Partnership Project (3GPP). Non-Patent Document 2 defines the charging function and charging management in the 3GPP packet switched domain. Typically, packet forwarding nodes in the core network (eg, Serving General Packet Radio Service (GPRS) Support Node (SGSN), Gateway GPRS Support Node (GGSN), Serving Gateway (S-GW), Packet Data Network Gateway ( P-GW)) has Charging Trigger Function (CTF) and Charging Data Function (CDF). In the billing management framework, the packet forwarding node in the core network is called a packet switched core network node (PCN).

  The CTF detects that a chargeable event has occurred. A chargeable event means an activity that uses a resource or service of a communication network. For example, 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).

  The CTF transfers charging information related to the detected chargeable event to the CDF via the Rf reference point. A set of charging information sent from the CTF to the CDF is called a charging event. Each charging event corresponds exactly to one chargeable event.

  The CDF receives a charging event from the CTF. Then, the CDF generates a charging data record (Charging Data Record (CDR)) for each predetermined charging party using the charging information included in the charging event. CDR is a formatted collection of information about a chargeable event (e.g. time of call set-up, duration of the call, amount of data transferred, etc.). The CDR is used for billing and billing and accounting in the billing domain. Note that 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. In addition, one charging target event may cause charging for a plurality of charging parties. Thus, one or more CDRs may be generated for one billable event.

3GPP TS 32.240 V11.6.0 (2013-03) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Charging architecture and principles (Release 11)”, March 2013 3GPP TS 32.251 V11.6.0 (2013-03) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Packet Switched (PS) domain charging (Release 11)”, March 2013

  Currently, various wireless terminals such as smartphones and machine type communication (MTC) devices are used. An MTC device is also called a Machine-to-Machine (M2M) device. MTC devices are installed in various devices such as machines (e.g., vending machines, gas meters, electric meters, automobiles, railway vehicles) and sensors (e.g., sensors relating to environment, agriculture, traffic, etc.). Among these various wireless terminals, there are wireless terminals having a high communication frequency or a high movement frequency. Therefore, the volume (number of messages) of control plane (C-plane) signaling that the mobile communication network must process has increased. C-plane signaling refers to the exchange of control signals or messages between network nodes, which is performed to provide a mobile terminal network service or resource to a wireless terminal.

  C-plane signaling is a wireless terminal operation such as attach, detach, change between idle mode (eg, RRC_IDLE mode) and connected mode (eg, RRC_CONNECTED mode), position change caused by movement in idle mode, And handover due to movement in the connected mode. Therefore, a wireless terminal performing tricky operations such as frequent attachment and detachment, frequent change between the idle mode and the connected mode, frequent position change, and frequent handover may cause an increase in signaling volume. Increases the load.

  The present inventor has examined improvements for facilitating charging and billing according to the signaling volume resulting from the operation of the wireless terminal. Non-Patent Document 2 describes Mobility management generated CDR (M-CDR). The M-CDR is generated by the Serving GPRS Support Node (SGSN), and records the mobility change of the wireless terminal, specifically, the change of the routing area. However, Non-Patent Document 2 does not disclose generating a CDR for recording other C-Plane signaling excluding a change of the Routing Area (that is, the location registration area).

  A major problem to be solved by the embodiments disclosed herein is an improvement that contributes to facilitating charging and billing according to the volume of signaling caused by the operation of a wireless terminal Is to provide. This big problem may be subdivided into a plurality of specific problems. One fragmented issue (a) provides improvements to contribute to facilitating billing and billing according to the volume of other C-Plane signaling excluding changes in the Routing Area (ie location registration area) It is to be. Another subdivided issue (b) contributes to facilitation of charging and billing according to the volume of C-Plane signaling (eg, radio resource control (RRC) signaling, handover signaling) in radio access networks It is to provide an improvement to do. Yet another subdivided issue (c) is to alleviate the additional load imposed on the network node to enable charging and billing according to the volume of C-Plane signaling. Yet another subdivided issue (d) is that the C-Plane signaling volume generated in the Visited Public Land Mobile Network (VPLMN) during roaming of wireless terminals can be easily done in the Home Public Land Mobile Network (HPLMN). It is to provide an improvement to be able to grasp.

  In other words, one of the objectives that the embodiments disclosed herein attempt to achieve is an apparatus, method, and method that contributes to solving at least one of the large and subdivided problems described above. Is to provide a program. It should be noted that this object is only one of the objects that the embodiments disclosed herein intend to achieve. Other objects or problems and novel features will become apparent from the description of the present specification or the accompanying drawings.

  In one embodiment, the network node includes a memory and a processor configured to perform charging processing for the wireless terminal. The charging process includes recording the occurrence of control plane signaling due to the operation of the wireless terminal in a charging data record. The billing data record is used for billing in a billing domain. The control plane signaling includes at least a radio resource control connection establishment procedure for the radio terminal, an attach procedure for the radio terminal, a detach procedure for the radio terminal, a bearer establishment procedure for the radio terminal, and a handover procedure for the radio terminal. Occurs during one.

  In one embodiment, a method performed by a network node for charging management includes recording the occurrence of control plane signaling due to wireless terminal operation in a charging data record. The billing data record is used for billing in a billing domain. The control plane signaling includes at least a radio resource control connection establishment procedure for the radio terminal, an attach procedure for the radio terminal, a detach procedure for the radio terminal, a bearer establishment procedure for the radio terminal, and a handover procedure for the radio terminal. Occurs during one.

  In one embodiment, the program includes a group of instructions (software code) for causing the computer to perform the above-described method when read by the computer.

  The above-described embodiments can provide an apparatus, a method, and a program that contribute to solving at least one of the above-described large problems and subdivided problems. It should be noted that this effect is only one of a plurality of effects expected to be brought about by a plurality of embodiments disclosed herein.

It is a block diagram which shows the charge management architecture which concerns on embodiment of this invention. It is a flowchart which shows an example of operation | movement of CTF which concerns on embodiment of this invention. It is a flowchart which shows an example of operation | movement of CDF which concerns on embodiment of this invention. It is a block diagram which shows the structural example of the network node which concerns on embodiment of this invention. It is a block diagram which shows the other structural example of the network node which concerns on embodiment of this invention. It is a flowchart which shows an example of operation | movement of CTF which concerns on embodiment of this invention. It is a flowchart which shows an example of operation | movement of CDF which concerns on embodiment of this invention. It is a figure which shows the structural example of the mobile communication network which concerns on embodiment of this invention. It is a figure which shows the structural example of the mobile communication network which concerns on embodiment of this invention. It is a figure which shows the structural example of the mobile communication network which concerns on embodiment of this invention. It is a figure which shows the structural example of the mobile communication network which concerns on embodiment of this invention. It is a flowchart which shows an example of operation | movement of the network node which concerns on embodiment of this invention.

  Hereinafter, specific embodiments 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.

  A plurality of embodiments described below can be implemented independently or can be implemented in combination as appropriate. The plurality of embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different purposes or problems and contribute to producing different effects.

<First Embodiment>
FIG. 1 is a block diagram showing a charging management architecture according to the present embodiment, and specifically shows a 3GPP offline charging architecture. The 3GPP network 10 includes a Charging Trigger Function (CTF) 11, a Charging Data Function (CDF) 12, and a Charging Gateway Function (CGF) 13 as elements for offline charging. The CTF 11 monitors the usage status of the resources in the 3GPP network 10 by the wireless terminal. In other words, the CTF 11 collects information related to a chargeable event in the network element (or network node). Then, the CTF 11 assembles the collected information into a charging event. A charging event corresponds to a set of charging information related to a chargeable event. The CTF 11 then transfers a charging event to the CDF 12 via the Rf reference point.

  The CDF 12 receives a charging event from the CTF 11 via the Rf reference point. Then, the CDF 12 generates one or a plurality of charging data records (Charging Data Record (CDR)) using information included in the charging event. The CDR is generated for each charged party. The CDR may be created from one charging event or a plurality of charging events. The relationship between the CDF 12 and the CTF 11 may be 1 to 1 (1: 1) or 1 to n (1: n) as shown in FIG. That is, the CDF 12 may receive a charging event from a plurality of CTFs 11.

  The CDR created by the CDF 12 is transferred to the CGF 13 via the Ga reference point. The CGF 13 operates as a gateway between the 3GPP network 10 and the billing domain 50. The relationship between the CGF 13 and the CDF 12 may be 1 to 1 (1: 1) or 1 to m (1: m). That is, the CGF 13 may receive CDRs from a plurality of CDFs 12. The CGF 13 has a CDR storage for persistently recording the CDR. The CGF 13 generates a CDR file including one or a plurality of CDRs and transmits it to the billing domain 50 via the Bx reference point.

  CTF 11 is located in a network element (or network node). Typically, CTF 11 is a core network element (core network node) such as Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), Serving GPRS Support Node (SGSN). , Or Gateway General Packet Radio Service Support Node (GGSN). The CTF 11 according to this embodiment is arranged in a radio access network element (radio access network node), for example, Evolved NodeB (eNB) or Radio Network Controller (RNC), as will be described in detail later. Also good.

  The CDF 12 may be located in an entity (e.g., computer system) physically separated from the network element. Alternatively, the CDF 12 may be arranged in any network element in the 3GPP network 10. In this case, the CDF 12 may be integrally disposed in the network element together with the CTF 11. Specifically, the CDF 12 may be arranged in a core network element (core network node) or a radio access network element (radio access network node).

  The CGF 13 may be arranged in an entity (e.g., computer system) physically separated from the network element. Alternatively, the CGF 13 may be integrally disposed in the network element together with the CDF 12.

  Subsequently, details of functions of the CTF 11 and the CDF 12 according to the present embodiment will be described below. In order to facilitate charging and billing according to the signaling volume resulting from the operation of the wireless terminal, the CTF 11 and the CDF 12 treat the control plane signaling as a chargeable event. In other words, the CTF 11 and the CDF 12 monitor the use of the control plane resource in the 3GPP network 10 by the wireless terminal, and record the number (volume) of control plane signaling caused by the operation of the wireless terminal in the CDR.

  FIG. 2 is a flowchart showing an example of the operation of the CTF 11. The CTF 11 detects the occurrence of control plane signaling due to the operation of the wireless terminal (step S11). Then, the CTF 11 assembles the detected charging information regarding the control plane signaling into a charging event, and transmits the charging event to the CDF 12 (step S12).

  FIG. 3 is a flowchart showing an example of the operation of the CDF 12. The CDF 12 receives a charging event related to control plane signaling from the CTF 11 (step S21). Then, the CDF 12 records the occurrence of control plane signaling due to the operation of the wireless terminal in the CDR based on the charging information included in the received charging event (step S22). Specifically, the CDF 12 may create a syntax that matches the CDR using the charging information included in the received charging event, and add this to the CDR.

  The generation of the CDR related to control plane signaling by the CTF 11 and the CDF 12 may be event based charging. That is, the CTF 11 treats one control plane signaling (that is, one procedure) as one chargeable event, and from this one chargeable event to one charge event (charging event) ) And the charging event (charging event) may be transmitted to the CDF 12. When CDF 12 receives one charging event corresponding to one control plane signaling (ie, one procedure), it creates a new CDR, records the charging event, closes the CDR, and The CDR may be transmitted to the CGF 13.

  Instead, the generation of CDR related to control plane signaling by the CTF 11 and the CDF 12 may be session based charging. In this case, a period from when the wireless terminal is attached to the core network until it is detached may be handled as one session. That is, the CDF 12 may generate a new CDR in response to the wireless terminal attaching to the core network (that is, MME or SGSN). The CTF 11 treats one control plane signaling (that is, one procedure) as one chargeable event, and handles one charging event from the one chargeable event. The charging event may be generated and transmitted to the CDF 12. The CDF 12 adds a syntax corresponding to the charging event received from the CTF 11 to the CDR. The CDF 12 may close the CDR according to the detachment of the wireless terminal. The CDR may be closed based on factors other than the detachment of the wireless terminal, such as a time limit, a signaling count limit, a CDR data size limit, and the like. These CDRs are called partial CDRs.

For example, the CTF 11 and the CDF 12 may handle at least one of the following procedures as a chargeable event. The CTF 11 and the CDF 12 may handle signaling that occurs in the procedures listed below as a chargeable event. Specific examples of procedures that are considered chargeable events include:
-Radio Resource Control (RRC) connection establishment procedure for wireless terminals;
・ Attachment procedure for wireless terminal;
-Detach procedures for wireless terminals;
・ Bearer establishment procedure for wireless terminals;
A location update procedure for the wireless terminal; and a handover procedure for the wireless terminal.

  The RRC connection establishment procedure for the radio terminal is performed between the radio terminal and the radio access network node (that is, eNB or RNC). Thus, the RRC connection establishment procedure causes signaling between the radio terminal and the radio access network node (ie, eNB or RNC).

  Attach and detach procedures for wireless terminals involve Non-Access Stratum (NAS) signaling between the wireless terminal and the core network (ie, MME or SGSN). Messages regarding NAS signaling are transmitted and received transparently between the wireless terminal and the core network (MME / SGSN) without being terminated in the wireless access network. Furthermore, the attach and detach procedures cause signaling between the radio access network (ie eNB or RNC) and the core network (ie MME or SGSN). Furthermore, the attach and detach procedures cause signaling in the core network, such as signaling between MME and Home Subscriber Server (HSS) and signaling between MME and S-GW. In this case, the CTF 11 and the CDF 12 may be arranged in a core network node (that is, MME or SGSN) that performs mobility management and session management. For example, the MME or SGSN may record the occurrence of an attach request message from the wireless terminal in the CDR.

  The bearer establishment procedure is executed to set up or activate a bearer (that is, Evolved Packet System (EPS) bearer or Internet Protocol Connectivity Access Network (IP-CAN) bearer) for wireless terminal to perform user plane communication. The Similar to the attach and detach procedures, the bearer establishment procedure involves Non-Access Stratum (NAS) signaling between the wireless terminal and the core network (ie, MME or SGSN). Furthermore, the bearer establishment procedure causes signaling between the radio access network and the core network and within the core network. In this case, the CTF 11 and the CDF 12 may be arranged in a core network node (that is, MME or SGSN) that performs mobility management and session management. For example, the MME or SGSN may record the occurrence of a bearer establishment request message (that is, Service Request or Activate PDP Context Request) from the wireless terminal in the CDR.

  The location update procedure is executed for updating a location registration area (that is, a tracking area or a routing area) in mobility management of a wireless terminal. The location update procedure also involves Non-Access Stratum (NAS) signaling between the wireless terminal and the core network (ie, MME or SGSN). Furthermore, the location update procedure causes signaling between the radio access network and the core network and within the core network. In this case, the CTF 11 and the CDF 12 may be arranged in a core network node (that is, MME or SGSN) that performs mobility management and session management. For example, the MME or SGSN may record the occurrence of a location update request message (that is, Tracking Area Update (TAU) Request or Routing Area Update (RAU) Request) from the wireless terminal in the CDR.

  The handover procedure for a radio terminal involves signaling between the radio terminal and the radio access network node, signaling within the radio access network, signaling between the radio access network and the core network, and signaling within the core network. In this case, the CTF 11 and the CDF 12 may be arranged in a radio access network node (that is, eNB or RNC) that controls handover. The eNB or RNC may record the occurrence of signaling at the inter-eNB interface (X2 interface) or the inter-RNC interface (Iur interface) accompanying the handover in the CDR. Alternatively, the CTF 11 and the CDF 12 may be arranged in the core network node (that is, MME or SGSN). The MME or SGSN may record the occurrence of signaling with the eNB or RNC accompanying the handover in the CDR.

  As described above, the CTF 11 and the CDF 12 according to the present embodiment operate so as to record the generation of control plane signaling due to the operation of the wireless terminal in the CDR. Therefore, the CTF 11 and the CDF 12 can contribute to facilitating charging and billing according to the volume of signaling caused by the operation of the wireless terminal. This is because the billing domain 50 can use the CDR created by the CDF 12 for billing and billing and accounting.

  In one preferred aspect, the CTF 11 and the CDF 12 operate to record in the CDR signaling generated during at least one of an RRC connection establishment procedure, an attach procedure, a detach procedure, a bearer establishment procedure, and a handover procedure for the wireless terminal. May be. This can address one of the subdivided issues that contribute to facilitation of billing and billing according to the volume of other C-Plane signaling excluding changes in the Routing Area (that is, location registration area). it can.

  In another preferred aspect, the CTF 11 and the CDF 12 are arranged in a radio access network node (eg, eNB or RNC), and record signaling generated during at least one of an RRC connection establishment procedure and a handover procedure for the radio terminal in the CDR. It may operate to do. Thereby, it is possible to cope with one of the subdivided problems that contribute to facilitation of charging and billing according to the volume of C-Plane signaling in the radio access network.

  Subsequently, a configuration example of the network node according to the present embodiment will be described below. The network node 100 shown in FIG. 4 includes a network interface 101, a control unit 102, and a CTF / CDF functional unit 103. The network node 100 may be a radio access network node or a core network node.

  The network interface 101 is used to communicate with other network nodes. The network interface 101 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.

  The control unit 102 performs communication control for providing resources or services to the wireless terminal. For example, when the network node 100 is a radio access network node (e.g., eNB or RNC), the control unit 102 may execute communication control including RRC and Radio Resource Management (RRM). If the network node 100 is a core network node (e.g., MME or SGSN), the control unit 102 may perform NAS signaling, mobility management, and session management.

  The CTF / CDF functional unit 103 executes the functions of the CTF 11 and the CDF 12 described in this embodiment.

  FIG. 5 shows another configuration example of the network node according to the present embodiment. Referring to FIG. 5, the network node 110 includes a network interface 111, a processor 112, and a memory 113. The network node 110 may be a radio access network node or a core network node.

  The network interface 111 is used to communicate with other network nodes. The network interface 111 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.

  The processor 112 reads out and executes software (computer program) from the memory 113, thereby performing communication control (eg, RRC and RRM, or mobility management and session management), and the functions of the CTF 11 and the CDF 12 described in the present embodiment. Execute. The processor 112 may be, for example, a microprocessor, a micro processing unit (MPU), or a central processing unit (CPU). The processor 112 may include a plurality of processors.

  The memory 113 is configured by a combination of a volatile memory and a nonvolatile memory. The volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof. The nonvolatile memory is, for example, a mask read only memory (MROM), a programmable ROM (PROM), a flash memory, a hard disk drive, or a combination thereof. Further, the memory 113 may include a storage that is physically separated from the processor 112. In this case, the processor 112 may access the memory 113 via the network interface 111 or another I / O interface not shown.

  In the example of FIG. 5, the memory 113 includes an S1-MME module 114, an S6a module 115, an S11 module 116, a NAS module 117, an EPS Mobility Management (EMM) module 118, an EPS Session Management (ESM) module 119, and a CTF / CDF module. Used to store software modules including 120. The CTF / CDF module 120 includes a group of instructions and data for executing the functions of the CTF 11 and the CDF 12. The processor 112 can perform the operations of the CTF 11 and the CDF 12 described in the present embodiment by reading the CTF / CDF module 120 from the memory 113 and executing it.

<Second Embodiment>
In the present embodiment, a modified example of the operations of the CTF 11 and the CDF 12 described in the first embodiment will be described. The configuration example of the wireless communication system according to the present embodiment may be the same as that of FIG. 1 described with respect to the first embodiment. The configuration example of the network node according to the present embodiment may be the same as the configuration example shown in FIG.

  In the present embodiment, the CTF 11 operates so as to transfer a charging event including charging information to the CDF 12 when the control plane signaling occurs a predetermined number of times. Then, the CDF 12 operates to record data indicating multiple occurrences of control plane signaling in the CDR. In other words, the CTF 11 and the CDF 12 according to the present embodiment handle multiple occurrences of control plane signaling as chargeable events.

  FIG. 6 is a flowchart showing an example of the operation of the CTF 11 according to the present embodiment. The CTF 11 detects the occurrence of control plane signaling due to the operation of the wireless terminal a plurality of predetermined times (step S31). Then, the CTF 11 assembles the detected charging information related to multiple times of control plane signaling into a charging event, and transmits the charging event to the CDF 12 (step S32).

  This embodiment addresses one of the subdivided issues of mitigating the additional load placed on network nodes to enable billing and billing according to C-Plane signaling volume. Can do. This is because the CDF 12 does not need to create or update a CDR for each signaling, and therefore the number of CDR processes (creation or update) in the CDF 12 can be reduced.

<Third Embodiment>
In the present embodiment, a modified example of the operation of the CDF 12 described in the first embodiment will be described. The configuration example of the wireless communication system according to the present embodiment may be the same as that of FIG. 1 described with respect to the first embodiment. The configuration example of the network node according to the present embodiment may be the same as the configuration example shown in FIG.

  In the present embodiment, the CDF 12 operates to record data indicating multiple occurrences of control plane signaling in the CDR. Operation | movement of CTF11 should just be the same as that of 1st Embodiment.

  FIG. 7 is a flowchart showing an example of the operation of the CDF 12 according to the present embodiment. The CDF 12 receives a charging event related to control plane signaling from the CTF 11 (step S41). However, the CDF 12 does not immediately create or update the CDR based on the received charging event. That is, the CDF 12 counts the occurrence of control plane signaling without recording it in the CDR. When the CDF 12 receives a charging event related to control plane signaling from the CTF 11 a plurality of times (step S41), the CDF 12 creates or updates the CDR (step S42). Specifically, the CDF 12 creates a syntax that matches the CDR using the charging information included in the multiple charging events received, and adds this to the CDR.

  Similar to the second embodiment, this embodiment is subdivided to alleviate the additional load imposed on the network node to enable charging and billing according to the C-Plane signaling volume. Can address one of the challenges. This is because the CDF 12 does not need to create or update a CDR for each signaling, and therefore the number of CDR processes (creation or update) in the CDF 12 can be reduced.

<Fourth Embodiment>
FIG. 8 shows a configuration example of the mobile communication network according to the present embodiment. FIG. 8 shows an example of EPS. That is, the network shown in FIG. 8 includes an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 210 and an Evolved Packet Core (EPC) 220. The E-UTRAN 210 includes a wireless terminal (User Equipment (UE)) 211 and an eNB 212. EPC 220 includes S-GW 221, P-GW 222, MME 223, HSS 224, Policy and Charging Rule Function (PCRF) 225, and CGF 226.

  The S-GW 221 and the P-GW 222 are user plane packet transfer nodes, and transfer user data (that is, Internet Protocol (IP) packets). The S-GW 221 is a gateway to the E-UTRAN 210, and is connected to the eNB 212 via the S1-U interface. The P-GW 222 is a gateway to the packet data network (PDN) 230 and is connected to the PDN 230 via the SGi interface. The PDN 230 may be an external network such as the Internet, or may be a network for an IP service (e.g., IP Multimedia Subsystem (IMS) service) provided by an operator who manages the EPC 220.

  The MME 223, the HSS 224, the PCRF 225, and the CGF 226 are control plane nodes or entities. The MME 223 performs mobility management and session management for the radio terminal (UE) 211. The HSS 224 manages subscriber information of the wireless terminal (UE) 211. The PCRF 225 is connected to the P-GW 222 via the Gx interface, and is connected to the Application Function (AF) in the PDN 230 via the Rx interface. The PCRF 225 receives application level service information from the AF in the PDN 230, determines a Policy and Charging Control (PCC) rule, and supplies the PCC rule to the P-GW 222. The P-GW 222 has a Policy and Charging Enforcement Function (PCEF), and performs quality of service (QoS) control and flow in units of service data flow (ie, IP packet flow) of the wireless terminal (UE) 211 in accordance with PCC rules. Performs Base Based Bearer Charging (FBC). The CGF 226 receives the CDR from the network node, generates a CDR file, and transfers the CDR file to the billing domain 50.

  In the example of FIG. 8, the MME 223 has a CTF and a CDF. The CTF and CDF arranged in the MME 223 provide the functions of the CTF 11 and CDF 12 described in any of the first to third embodiments. That is, the CTF and CDF arranged in the MME 223 record the generation of control plane signaling due to the operation of the radio terminal (UE) 211 in the CDR, and send the CDR to the CGF 226. As a result, the MME 223 contributes to facilitating billing based on the number of occurrences of control plane signaling caused by the operation of the radio terminal (UE) 211.

  Specifically, the MME 223 may operate to record in the CDR signaling generated during at least one of an attach procedure, a detach procedure, and a bearer establishment procedure. This can address one of the subdivided issues that contribute to facilitation of billing and billing according to the volume of other C-Plane signaling excluding changes in the Routing Area (that is, location registration area). it can.

  Moreover, as FIG. 8 shows, eNB212 may have CTF and CDF. The CTF and CDF arranged in the eNB 212 provide the functions of the CTF 11 and CDF 12 described in any of the first to third embodiments. That is, the CTF and CDF arranged in the eNB 212 record the generation of control plane signaling caused by the operation of the radio terminal (UE) 211 in the CDR, and send the CDR to the CGF 226. As a result, the MME 223 contributes to facilitating billing based on the number of occurrences of control plane signaling caused by the operation of the radio terminal (UE) 211.

  Specifically, the eNB 212 may operate so as to record the signaling generated during at least one of the RRC connection establishment procedure and the handover procedure for the radio terminal (UE) 211 in the CDR. Thereby, it is possible to cope with one of the subdivided problems that contribute to facilitation of charging and billing according to the volume of C-Plane signaling in the E-UTRAN 210.

  Of course, other network nodes shown in FIG. 8 may also have CTF and / or CDF. For example, the S-GW 221 and the P-GW 222 may have a CTF and a CDF for IP-CAN bearer charging.

<Fifth Embodiment>
FIG. 9 shows a configuration example of the mobile communication network according to the present embodiment. FIG. 9 illustrates a roaming architecture using a GPRS Tunneling Protocol (GTP) based S8 interface. The network shown in FIG. 9 includes VPLMN 310 and HPLMN 320. As is well known, PLMN is specified by Mobile Country Code (MCC) and Mobile Network Code (MNC). The HPLMN 320 is a PLMN that matches the MCC and MNC included in the International Mobile Subscriber Identity (IMSI) recorded in the Subscriber Identity Module (SIM) of the wireless terminal (UE) 311. The VPLMN 310 is a PLMN that is different from the HPLMN 320 of the wireless terminal (UE) 311.

  The VPLMN 310 includes an eNB 312, an S-GW 313, and an MME 314. The HPLMN 320 includes a P-GW 321, an HSS 322, a PCRF 323, and a CDF / CGF 324. The wireless terminal (UE) 311 receives a service at the roaming destination VPLMN 310. The wireless terminal (UE) 311 communicates with the PDN 330 via an S8 interface connected between the S-GW 313 in the VPLMN 310 and the P-GW 321 in the HPLMN 320. Note that the roaming architecture of FIG. 9 is merely an example. For example. The wireless terminal (UE) 311 may connect to the PDN 330 via a P-GW (not shown) in the VPLMN 310 and use the IP service of the PDN 330 (so-called local breakout method).

  In the example of FIG. 9, the MME 314 in the VPLMN 310 has a CTF. The CTF arranged in the MME 314 provides the function of the CTF 11 described in any of the first to third embodiments. That is, the CTF arranged in the MME 314 transmits a charging event indicating the occurrence of control plane signaling due to the operation of the radio terminal (UE) 311 to the CDF / CGF 324 in the HPLMN 320. The CDF / CGF 324 has the functions of CDF and CGF, and provides the function of the CDF 12 described in any of the first to third embodiments. That is, the CDF / CGF 324 records the occurrence of control plane signaling caused by the operation of the radio terminal (UE) 311 in the CDR, generates a CDR file, and sends this CDR file to the billing domain 50.

  Specifically, the MME 314 transmits a charging event related to signaling that occurs during at least one of the attach procedure, detach procedure, bearer establishment procedure, and location update procedure of the wireless terminal (UE) 311. Also good. Based on these charging events, the CDF / CGF 324 may record the occurrence of control plane signaling due to the operation of the radio terminal (UE) 311 in the roaming network (VPLMN 310) in the CDR. .

  Further, as shown in FIG. 9, the eNB 312 in the VPLMN 310 may have a CTF. The CTF arranged in the eNB 312 provides the function of the CTF 11 described in any of the first to third embodiments. That is, the CTF arranged in the MME 314 sends a charging event indicating the occurrence of control plane signaling due to the operation of the radio terminal (UE) 311 in the roaming network (VPLMN 310) to the CDF / CGF 324 in the HPLMN 320. Send to.

  Specifically, the eNB 312 may transmit a charging event related to signaling that occurs during at least one of the RRC connection establishment procedure and the handover procedure of the radio terminal (UE) 311. Based on these charging events, the CDF / CGF 324 may record the occurrence of control plane signaling caused by the operation of the radio terminal (UE) 311 in the CDR.

  As understood from the above description, in the example of FIG. 9, the CTF in the network node (eg, MME 314 and eNB 312) having the CTF in the VPLMN 310 is charged to the CDF (eg, CDF / CGF 324) in the HPLMN 320. (Charging event) is transmitted. Then, the CDF in the HPLMN 320 records the occurrence of control plane signaling caused by the operation of the radio terminal (UE) 311 in the roaming network (VPLMN 310) in the CDR. Thus, one of the subdivided issues of enabling the HPLMN 320 to easily grasp the C-Plane signaling volume generated in the VPLMN 310 when the wireless terminal (UE) 311 roams can be dealt with.

<Sixth Embodiment>
FIG. 10 shows a configuration example of the mobile communication network according to the present embodiment. FIG. 10 shows a roaming architecture using a GTP-based S8 interface for Machine-Type Communication (MTC). The network shown in FIG. 9 includes VPLMN 410 and HPLMN 420. VPLMN 410 includes eNB 412, S-GW 413, and MME 414. The HPLMN 420 includes a P-GW 421, an HSS 422, an MTC Inter Working Function (MTC-IWF) entity 423, and a CGF 424. The MTC device 411 receives a service at the roaming destination VPLMN 410. The MTC device 411 communicates with the Service Capability Server (SCS) 431 or the MTC application server 432 via the S8 interface connected between the S-GW 413 in the VPLMN 410 and the P-GW 421 in the HPLMN 420.

  The MTC device 411 is a wireless terminal (UE) that behaves as an MTC device by executing the MTC UE application 31. The MTC device 411 may be an MTC gateway device. MTC gateway devices have 3GPP mobile communication functions (ie UE functions) and connect to neighboring devices (eg sensors, radio frequency identification (RFID) tags, car navigation systems) via personal / local area connection technology To do. Specific examples of the personal / local area connection technology include IEEE 802.15, ZigBee (registered trademark), Bluetooth (registered trademark), and 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). .

  The MTC-IWF entity 423 is a control plane entity belonging to the HPLMN 420. MTC-IWF entity 423 communicates with network elements such as HSS 422 and MME 414 via a signaling interface (reference point). The MTC-IWF entity 423 behaves as a control plane interface or gateway for the MTC service layer including the SCS 431 and the 3GPP PLMN to interwork while hiding the details of the 3GPP PLMN topology.

  The SCS 431 enables the MTC application server 432 to communicate with the MTC-IWF entity 423. The SCS 431 is assumed to be controlled by the operator of the HPLMN 420 or the MTC service provider.

  In the example of FIG. 10, the MME 414 in the VPLMN 410 has a CTF, and the MTC-IWF entity 423 in the HPLMN 420 has a CDF. The CTF arranged in the MME 414 provides the function of the CTF 11 described in any of the first to third embodiments. The CDF arranged in the MTC-IWF entity 423 provides the function of the CDF 12 described in any of the first to third embodiments. That is, the CTF arranged in the MME 314 indicates a charging event indicating the occurrence of control plane signaling due to the operation of the MTC device 411 in the roaming network (VPLMN 410) as a CDF in the HPLMN 420 (that is, MTC-IWF). To entity 423). The MTC-IWF entity 423 records the generation of control plane signaling due to the operation of the MTC device 411 in the roaming network (VPLMN 410) in the CDR, and sends this CDR to the CGF 424.

  Specifically, the MME 414 may transmit a charging event related to signaling that occurs during at least one of the MTC device 411 attach procedure, detach procedure, bearer establishment procedure, and location update procedure. Based on these charging events, the MTC-IWF entity 423 may record the occurrence of control plane signaling due to the operation of the MTC device 411 in the roaming network (VPLMN 410) in the CDR.

  As understood from the above description, in the example of FIG. 10, the CTF in the network node (eg, MME 414) having the CTF in the VPLMN 410 is charged to the CDF (eg, MTC-IWF entity 423) in the HPLMN 420. (Charging event) is notified. Then, the CDF in the HPLMN 420 records the occurrence of control plane signaling due to the operation of the MTC device 411 in the roaming network (VPLMN 410) in the CDR. Thereby, one of the subdivided problems of enabling the HPLMN 420 to easily grasp the C-Plane signaling volume generated in the VPLMN 410 when the MTC device 411 roams can be dealt with.

<Seventh Embodiment>
In the fifth and sixth embodiments, in order to easily grasp the volume of signaling generated in the roaming network (VPLMN) in the home network (HPLMN), the CTF in the roaming network (VPLMN) A specific configuration was adopted in which a charging event was sent to the CDF in (HPLMN). On the other hand, in the present embodiment, another specific configuration for enabling the home network (HPLMN) to easily grasp the volume of signaling generated in the roaming network (VPLMN) will be described.

  FIG. 11 shows a roaming architecture using a GTP-based S8 interface, similar to FIG. The network shown in FIG. 11 includes VPLMN 510 and HPLMN 520. The VPLMN 510 includes an eNB 512, an S-GW 513, and an MME 514. HPLMN 520 includes P-GW 521, HSS 522, PCRF 523, and CGF 524. The wireless terminal (UE) 511 receives a service at the roaming destination VPLMN 510. The wireless terminal (UE) 511 communicates with the PDN 530 via the S8 interface connected between the S-GW 513 in the VPLMN 510 and the P-GW 521 in the HPLMN 520.

  In the example of FIG. 11, the P-GW 521 in the HPLMN 520 has a CTF and a CDF. The CTF and CDF arranged in the P-GW 521 provide the functions of the CTF 11 and CDF 12 described in any of the first to third embodiments. That is, the CTF and CDF arranged in the P-GW 521 record the occurrence of control plane signaling caused by the operation of the radio terminal (UE) 511 in the roaming network (VPLMN 510) in the CDR, and store the CDR in the CGF 524. send. Thereby, the P-GW 521 contributes to the solution of the problem that the HPLMN 520 can easily grasp the C-Plane signaling volume generated in the VPLMN 510 when the wireless terminal (UE) 511 roams.

  The P-GW 521 is configured on the S8 interface due to at least one of the attach procedure, detach procedure, bearer establishment procedure, location update procedure, and handover procedure of the radio terminal (UE) 511 in the roaming network (VPLMN 510). A signaling message received from the P-GW 521 may be detected as a chargeable event. The signaling message received from the P-GW 521 on the S8 interface includes, for example, Create session Request, Delete session Request, and Modify Bearer Request.

  In the case of the attach procedure, the P-GW 521 may detect a Create session Request received from the S-GW 513 on the S8 interface as a chargeable event. Create session Request is sent to create a new setting or context for a new session or bearer.

  In the case of the detachment procedure, the P-GW 521 may detect a Delete session Request received from the S-GW 513 on the S8 interface as a chargeable event. Delete session Request is sent to delete a setting or context related to a session or bearer.

  In the case of the bearer establishment procedure, the location update procedure, and the handover procedure, the P-GW 521 may detect the Modify Bearer Request received from the S-GW 513 on the S8 interface as a chargeable event. The Modify Bearer Request is transmitted in order to update the setting or context related to the session or bearer, or to notify the P-GW 521 of some information related to the session or bearer.

  Note that the S-GW 513 creates, updates, and updates bearers caused by any of the attach procedure, detach procedure, bearer establishment procedure, location update procedure, and handover procedure of the wireless terminal (UE) 511 in the roaming network (VPLMN 510). Alternatively, when deleting, a signaling message may be transmitted to the P-GW 521 via the S8 interface. As a result, the P-GW 521 can reliably detect the occurrence of control plane signaling due to the operation of the radio terminal (UE) 311 in the roaming network (VPLMN 310).

  FIG. 12 is a flowchart showing an example of the operation of the P-GW 521. The P-GW 521 detects the occurrence of control plane signaling on the S8 interface due to the operation of the radio terminal (UE) 511 in the roaming network (VPLMN 510) as a chargeable event (step S51). . The P-GW 521 assembles the charging information regarding the detected control plane signaling into a charging event (step S52). Then, the P-GW 521 uses the charging information included in the charging event to create a syntax that matches the CDR, and adds this to the CDR (step S53).

<Other embodiments>
In the above-described embodiment, the CTF 11 or a network node having a function equivalent to the CTF 11 selectively selects a process for detecting control plane signaling as a chargeable event for a specific wireless terminal. It may be executed. In order to distinguish a specific wireless terminal from other wireless terminals, for example, the identifier of the wireless terminal (eg, IMSI) or the attribute of the wireless terminal (eg low priority identifier, MTC identifier, or time tolerant identifier) is used. Also good. The network node may receive these identifiers from the wireless terminal or from a subscriber information server (eg, HSS).

  In the above-described embodiment, the description has been made mainly using specific examples related to EPS. However, these embodiments are not limited to other mobile communication systems such as Universal Mobile Telecommunications System (UMTS), 3GPP2 CDMA2000 system (1xRTT, High Rate Packet Data (HRPD)), Global System for Mobile communications (GSM®). ) / General packet radio service (GPRS) system, mobile WiMAX system, and the like.

  The method performed by the CTF 11 and the CDF 12 described in the above embodiments causes a computer system including at least one processor (eg, a microprocessor, a micro processing unit (MPU), and a central processing unit (CPU)) to execute a program. It may be realized by. Specifically, one or a plurality of programs including a group of instructions for causing a computer to execute an algorithm described using a flowchart or the like may be supplied to the computer.

  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. 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 discs), compact disc read only memory (CD-ROM), CD-ROMs. R, CD-R / W, and semiconductor memory (for example, mask ROM, programmable ROM (PROM), erasable PROM (EPROM), flash ROM, random access memory (RAM)) are included. The program may also be supplied to the computer by various types of transitory 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 above-described embodiment is merely an example relating to application of the technical idea obtained by the present inventors. That is, the technical idea is not limited to the above-described embodiment, and various changes can be made.

  For example, a part or all of the above-described embodiment can be described as in the following supplementary notes, but is not limited thereto.

(Appendix A1)
A network node,
Memory,
A processor coupled to the memory and configured to perform charging processing for the wireless terminal;
With
The network node is arranged in a home PLMN (home public land mobile network (HPLMN)) of the wireless terminal,
The charging process comprises recording in a charging data record the occurrence of control plane signaling resulting from the operation of the wireless terminal in a visited PLMN (visited public land mobile network (VPLMN)) different from the home PLMN.
Network node.

(Appendix A2)
The recording counts the occurrence of the control plane signaling without recording it in the billing data record, and the occurrence of the plurality of times triggered by the occurrence of the control plane signaling a plurality of times. The network node according to appendix A1, which includes recording data indicating the data in the billing data record.

(Appendix A3)
The recording includes receiving charging information transmitted from the visited PLMN with the occurrence of the control plane signaling in the visited PLMN, and being recorded in the charging data record based on the charging information. The network node of appendix A1, which involves generating data to be performed.

(Appendix A4)
The network node according to appendix A3, wherein the billing information is transmitted from the visited PLMN when the control plane signaling occurs a predetermined number of times.

(Appendix A5)
The network node is a gateway general packet radio service support node (GGSN), a packet data network gateway (P-GW), or a machine type communication interworking function (MTC-IWF) entity, and any one of appendices A1 to A4 The network node described in the section.

(Appendix A6)
The network node according to any one of appendices A1-A5, wherein the billing data record is used for billing in a billing domain.

(Appendix A7)
A network node,
Memory,
A processor coupled to the memory and configured to perform charging processing for the wireless terminal;
With
The network node is arranged in a visited PLMN (visited public land mobile network (VPLMN)) different from a home PLMN (home public land mobile network (HPLMN)) of the wireless terminal,
The charging process comprises transmitting charging information indicating occurrence of control plane signaling due to operation of the wireless terminal in the visited PLMN to a node of the home PLMN.
Network node.

(Appendix A8)
The billing information is used in the home PLMN to generate data to be recorded in a billing data record,
The billing data record is used for billing in a billing domain.
The network node according to appendix A7.

(Appendix A9)
The network node according to appendix A7 or A8, wherein the transmitting comprises transmitting the accounting information triggered by the occurrence of the control plane signaling a plurality of predetermined times.

(Appendix A10)
10. The network node according to any one of appendices A7 to A9, wherein the charging information indicates the number of occurrences of the control plane signaling in the visited PLMN.

(Appendix A11)
The network node is a Serving GPRS Support Node (SGSN) or Mobility Management Entity (MME)
The node of the home PLMN is a Machine Type Communication Inter Working Function (MTC-IWF) entity.
The network node according to any one of appendices A7 to A10.

(Appendix A12)
A method performed by a network node for billing management,
The network node is arranged in a home PLMN (home public land mobile network (HPLMN)) of a wireless terminal,
The method comprises recording the occurrence of control plane signaling due to the operation of the wireless terminal in a visited PLMN (visited public land mobile network (VPLMN)) different from the home PLMN in a charging data record,
Method.

(Appendix A13)
A method performed by a network node for billing management,
The network node is arranged in a visited PLMN (visited public land mobile network (VPLMN)) different from a home PLMN (home public land mobile network (HPLMN)) of the wireless terminal,
The method comprises transmitting charging information indicating occurrence of control plane signaling due to an operation of the wireless terminal in the visited PLMN to a node of the home PLMN.
Method.

(Appendix B1)
A network node,
Memory,
A processor coupled to the memory and configured to perform charging processing for the wireless terminal;
With
The charging process comprises recording in a charging data record the occurrence of control plane signaling within the radio access network due to the operation of the wireless terminal;
The billing data record is used for billing in a billing domain.
Network node.

(Appendix B2)
The network node according to appendix B1, wherein the network node is arranged in a radio access network.

(Appendix B3)
The control plane signaling occurs during at least one of a radio resource control connection establishment procedure for the radio terminal and a handover procedure for the radio terminal;
The network node according to appendix B1 or B2.

(Appendix B4)
A method performed by a network node for billing management,
The method comprises recording occurrence of control plane signaling in a radio access network due to operation of a wireless terminal in a charging data record;
The billing data record is used for billing in a billing domain.
Method.

(Appendix C1)
A network node,
Memory,
A processor coupled to the memory and configured to perform charging processing for the wireless terminal;
With
The charging process comprises recording the occurrence of the control plane signaling in a charging data record triggered by the occurrence of a plurality of predetermined control plane signaling due to the operation of the wireless terminal;
The billing data record is used for billing in a billing domain.
Network node.

(Appendix C2)
The recording counts the occurrence of the control plane signaling without recording it in the billing data record, and the occurrence of the plurality of times triggered by the occurrence of the control plane signaling a plurality of times. The network node according to appendix C1, comprising recording data indicating the accounting data in the accounting data record.

(Appendix C3)
The recording includes receiving charging information transmitted with the occurrence of the control plane signaling in another network node, and generating data to be recorded in the charging data record based on the charging information Including
The charging information is transmitted from the other network node when the control plane signaling is generated a plurality of times.
The network node according to appendix C1.

(Appendix C4)
The control plane signaling includes a radio resource control connection establishment procedure for the radio terminal, an attach procedure for the radio terminal, a detach procedure for the radio terminal, a bearer establishment procedure for the radio terminal, a handover procedure for the radio terminal, and the radio The network node according to any one of appendices C1 to C3, which occurs during at least one of location update procedures related to a terminal.

(Appendix C5)
A method performed by a network node for billing management,
The method comprises recording occurrence of the control plane signaling in a charging data record triggered by occurrence of control plane signaling due to operation of a wireless terminal a plurality of predetermined times,
The billing data record is used for billing in a billing domain.
Method.

10 3GPP network 11 Charging Trigger Function (CTF)
12 Charging Data Function (CDF)
13 Charging Gateway Function (CGF)
50 billing domain 100 network node 101 network interface 102 control unit 103 CTF / CDF functional unit 110 network node 111 network interface 112 processor 113 memory 114 S1-MME interface module 115 S6a interface module 116 S11 interface module 117 Non-Access Stratum (NAS) module 118 EPS Mobility Management (EMM) module 119 EPS Session Management (ESM) module 120 CTF / CDF module 210 Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
220 Evolved Packet Core (EPC)
310 Visited Public Land Mobile Network (VPLMN)
320 Home Public Land Mobile Network (HPLMN)
410 Visited Public Land Mobile Network (VPLMN)
420 Home Public Land Mobile Network (HPLMN)

Claims (15)

A network node,
Memory,
A processor coupled to the memory and configured to perform charging processing for the wireless terminal;
With
The charging process comprises recording in a charging data record the occurrence of control plane signaling due to the operation of the wireless terminal;
The billing data record is used for billing in a billing domain,
The control plane signaling includes at least a radio resource control connection establishment procedure for the radio terminal, an attach procedure for the radio terminal, a detach procedure for the radio terminal, a bearer establishment procedure for the radio terminal, and a handover procedure for the radio terminal. Occurs during one,
Network node.   The recording counts the occurrence of the control plane signaling without recording it in the billing data record, and the occurrence of the plurality of times triggered by the occurrence of the control plane signaling a plurality of times. The network node according to claim 1, further comprising: recording data indicating the data in the billing data record. The recording includes receiving charging information transmitted with the occurrence of the control plane signaling in another network node, and generating data to be recorded in the charging data record based on the charging information Including
The charging information is transmitted from the other network node when the control plane signaling occurs a predetermined number of times.
The network node according to claim 1.   The charging process includes providing radio resources to the radio terminal, attaching the radio terminal to a core network, providing bearer resources to the radio terminal when the number of times of the control plane signaling exceeds a predetermined level, The network node according to any one of claims 1 to 3, further comprising restricting at least one of handover of the wireless terminal.   The network node according to any one of claims 1 to 4, wherein the network node is a node that is arranged in a core network and performs mobility management of the wireless terminal. The network node is located in a radio access network;
The control plane signaling occurs during at least one of a radio resource control connection establishment procedure for the radio terminal and a handover procedure for the radio terminal;
The network node according to claim 1. The network node is arranged in a home PLMN (home public land mobile network (HPLMN)) of the wireless terminal,
The recording comprises recording the occurrence of the control plane signaling in a visited PLMN (visited public land mobile network (VPLMN)) different from the home PLMN in the billing data record,
The network node according to claim 1. Recording the occurrence of the control plane signaling in the visited PLMN receives from the visited PLMN billing information transmitted with the occurrence of the control plane signaling in the visited PLMN, and Generating data to be recorded in the billing data record based on billing information,
The network node according to claim 7.   9. The network node according to claim 7 or 8, wherein the network node is a Gateway General Packet Radio Service Support Node (GGSN), a Packet Data Network Gateway (P-GW), or a Machine Type Communication Interworking Function (MTC-IWF) entity. Network node. A method performed by a network node for billing management,
The method comprises recording the occurrence of control plane signaling due to wireless terminal operation in a billing data record;
The billing data record is used for billing in a billing domain,
The control plane signaling includes at least a radio resource control connection establishment procedure for the radio terminal, an attach procedure for the radio terminal, a detach procedure for the radio terminal, a bearer establishment procedure for the radio terminal, and a handover procedure for the radio terminal. Occurs during one,
Method.   The recording counts the occurrence of the control plane signaling without recording it in the billing data record, and the occurrence of the plurality of times triggered by the occurrence of the control plane signaling a plurality of times. The method according to claim 10, further comprising recording data indicating the data in the billing data record. The recording includes receiving charging information transmitted with the occurrence of the control plane signaling in another network node, and generating data to be recorded in the charging data record based on the charging information Including
The charging information is transmitted from the other network node when the control plane signaling occurs a predetermined number of times.
The method of claim 10. The network node is located in a radio access network;
The control plane signaling occurs during at least one of a radio resource control connection establishment procedure for the radio terminal and a handover procedure for the radio terminal;
The method according to any one of claims 10 to 12. The network node is arranged in a home PLMN (home public land mobile network (HPLMN)) of the wireless terminal,
The recording comprises recording the occurrence of the control plane signaling in a visited PLMN (visited public land mobile network (VPLMN)) different from the home PLMN in the billing data record,
The method of claim 10.   The program for making a computer perform the method of any one of Claims 10-14.

Images