Billing Function Node, Billing Device, and Billing Method

Abstract

The present invention provides a charging function (CF) node (10) having a reception means (11) for receiving information including a tracking area code (TAC), and a transmission means (12) for transmitting a charging data record (CDR) including the TAC, the transmission means setting a TAC conforming to a first standard to a prescribed position in the CDR when said TAC is received by the reception means, and setting a TAC conforming to a second standard to an extended region when said TAC is received by the reception means.

Description

Technical Field

[0001] The present disclosure relates to a charging function node, a charging device, and a charging method.

Background Art

[0002] A technique for billing a user using a charging function (CHF, Charging Function) defined by the Third Generation Partnership Project (3GPP) is known (for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in related technologies, for example, charging may not be performed appropriately. An object of the present disclosure is to provide a charging function node, a charging device, a communication system, a method, and a program that can perform charging appropriately in view of the above-described problems.

Means for Solving the Problems

[0005] In a first aspect according to the present disclosure, there is provided a charging function (CHF) node having receiving means for receiving information including a tracking area code (TAC), and transmitting means for transmitting a charging data record (CDR) including the tracking area code. When the transmitting means receives the tracking area code compliant with a first standard by the receiving means, the transmitting means sets the tracking area code at a predetermined position of the charging data record. When the transmitting means receives the tracking area code compliant with a second standard by the receiving means, the transmitting means sets the tracking area code in an extended area of the charging data record.

[0006] Also, in a second aspect according to the present disclosure, there is provided a charging device having receiving means for receiving a charging data record (CDR) including a tracking area code (TAC) from a charging function (CHF) node, and charging means for performing charging based on the extracted tracking area code. When the receiving means receives the tracking area code compliant with a first standard, the receiving means extracts the tracking area code from a predetermined position of the charging data record. When the receiving means receives the tracking area code compliant with a second standard, the receiving means extracts the tracking area code from an extended area of the charging data record.

[0007] Also, in a third aspect according to the present disclosure, a charging function (CHF) node executes a process of receiving information including a tracking area code (TAC) and a process of transmitting a charging data record (CDR) including the tracking area code. In the transmitting process, when the tracking area code compliant with a first standard is received in the receiving process, the tracking area code is set at a predetermined position of the charging data record, and when the tracking area code compliant with a second standard is received in the receiving process, the tracking area code is set in an extended area of the charging data record. A charging method is provided.

[0008] Also, in a fourth aspect according to the present disclosure, a charging device receives a charging data record (CDR) including a tracking area code (TAC) from a charging function (CHF) node. When the tracking area code compliant with a first standard is received, the tracking area code is extracted from a predetermined position of the charging data record, and when the tracking area code compliant with a second standard is received, the tracking area code is extracted from an extended area of the charging data record, and charging is performed based on the extracted tracking area code. A charging method is provided.

Advantages of the Invention

[0009] According to one aspect, it is possible to appropriately perform charging.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Mode for Carrying Out the Invention

[0011] The principles of the present disclosure are described with reference to several exemplary embodiments. These embodiments are described for illustrative purposes only and are intended to help those skilled in the art understand and implement the present disclosure without suggesting any limitations on the scope of the present disclosure. The disclosure described herein may be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0012] <System Configuration> FIG. 1 is a diagram showing a configuration example of a charging system 1 according to an embodiment. In FIG. 1, the charging system 1 includes a charging function (CHF, (Charging Function) node 10, charging devices 20A, 20B, network function (NF, Network Function) nodes 30A, 30B. Note that the number of the charging function node 10, charging devices 20A, 20B, network function nodes 30A, 30B is not limited to the example in FIG. 1.

[0013] The charging function node 10, the charging devices 20A and 20B, the network function nodes 30A and 30B are connected so that they can communicate with each other through, for example, a LAN (Local Area Network), the Internet, a core network, or the like.

[0014] The network function node 30A is a network function node compliant with a first standard, which is a specific wireless communication standard. The first standard may be, for example, the wireless communication standard of the fourth-generation mobile communication system (4G) defined by 3GPP. Note that 4G may include, for example, LTE-Advanced, WiMAX2, Long Term Evolution (LTE), etc.

[0015] The network function node 30A transmits a tracking area code (TAC) in a format with a data size of 2 octets (bytes) to the charging function node 10 in accordance with the first standard. Note that the TAC may be, for example, a tracking area composed of one or more cells and indicating the position of a wireless communication terminal managed on the network, encoded by a wireless communication carrier. Note that the "wireless communication terminal" in the present disclosure may include, for example, wireless communication terminals such as smartphones, in-vehicle wireless communication devices, and wireless communication devices for IoT (Internet of Things).

[0016] The network function node 30B is a network function node compliant with a second standard, which is a wireless communication standard newer than the first standard. The second standard may be, for example, the wireless communication standard of the fifth-generation mobile communication system (5G) defined by 3GPP. Also, the second standard may be, for example, a wireless communication standard of the sixth-generation mobile communication system (6G, beyond 5G) or later that has already been defined by 3GPP or will be defined in the future.

[0017] The network function node 30B transmits a TAC in a format with a data size other than 2 octets (for example, 3 octets) to the charging function node 10 in accordance with the second standard.

[0018] The charging function node 10 generates (outputs) a CDR (Charging Data Record) embedded with the TAC received from the network function node 30A or the network function node 30B, and transmits it to the charging device 20A or the charging device 20B which is a higher-level charging device.

[0019] The charging device 20A is a charging device compliant with the first standard. The charging device 20B is a charging device corresponding to the function of the charging function node 10 of the present disclosure.

[0020] The charging devices 20A and 20B charge (bill) the user of the wireless communication terminal based on the CDR received from the charging function node 10.

[0021] <Hardware Configuration> FIG. 2 is a diagram showing a hardware configuration example of the charging function node 10 and the charging device 20B according to the embodiment. Hereinafter, the charging function node 10 will be described as an example. The hardware configuration example of the charging device 20B may be the same as the hardware configuration example of the charging function node 10. In the example of FIG. 2, the charging function node 10 (computer 100) includes a processor 101, a memory 102, and a communication interface 103. These components may be connected by a bus or the like. The memory 102 stores at least a part of the program 104. The communication interface 103 includes an interface necessary for communication with other network elements.

[0022] When program 104 is executed through the cooperation of a processor 101, a memory 102, etc., at least part of the processing of the embodiments of the present disclosure is performed by computer 100. Memory 102 may be of any type suitable for a local technical network. Memory 102 may be, as a non-limiting example, a non-transitory computer-readable storage medium. Also, memory 102 may be implemented using any suitable data storage technology such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 102 is shown for computer 100, there may be several physically different memory modules in computer 100. Processor 101 may be of any type. Processor 101 may include one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and, as a non-limiting example, a processor based on a multi-core processor architecture. Computer 100 may have multiple processors such as an application-specific integrated circuit chip that is temporally dependent on a clock that synchronizes the main processor.

[0023] Embodiments of the present disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, a microprocessor, or other computing device.

[0024] The present disclosure also provides at least one computer program product tangibly stored in a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which are executed on a device on a target physical processor or virtual processor to execute the processes or methods of the present disclosure. Program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of the program modules may be combined or divided among the program modules as desired in various embodiments. The machine-executable instructions of the program modules can be executed within local or distributed devices. In a distributed device, the program modules can be arranged on both local and remote storage media.

[0025] The program code for executing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes are provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing devices. When the program code is executed by the processor or controller, the functions / operations in the flowchart and / or the implementation block diagram are executed. The program code is executed entirely on the machine, partly on the machine as a stand-alone software package, partly on the machine, partly on a remote machine, or entirely on a remote machine or server.

[0026] The 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 recording media. Examples of non-transitory computer-readable media include magnetic recording media, magneto-optical recording media, optical disk media, semiconductor memories, etc. Magnetic recording media include, for example, flexible disks, magnetic tapes, hard disk drives, etc. Magneto-optical recording media include, for example, magneto-optical disks, etc. Optical disk media include, for example, Blu-ray disks, CD (Compact Disc)-ROM (Read Only Memory), CD-R (Recordable), CD-RW (ReWritable), etc. Semiconductor memories include, for example, solid state drives, mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, RAMs (random access memories), etc. Also, the program may 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 transitory computer-readable media can supply the program to the computer via wired communication channels such as electric wires and optical fibers, or wireless communication channels.

[0027] <Configuration> Next, with reference to FIGS. 3 and 4, the configurations of the charging function node 10 and the charging device 20B according to the embodiment will be described. FIG. 3 is a diagram showing an example of the configuration of the charging function node 10 according to the embodiment. FIG. 4 is a diagram showing an example of the configuration of the charging device 20B according to the embodiment. Note that the configurations shown in FIGS. 3 and 4 are merely examples. As long as the processing of the present disclosure can be executed, the names of the respective parts can be any names.

[0028] <<Charging Function Node 10>> The charging function node 10 includes a receiving unit 11 and a transmitting unit 12. Each of these units may be realized by the cooperation of one or more programs installed in the charging function node 10 and hardware such as the processor 101 and the memory 102 of the charging function node 10.

[0029] The receiving unit 11 receives information including a tracking area code from the network function node 30A or the network function node 30B. The transmitting unit 12 transmits a charging data record including a tracking area code to the charging device 20A or the charging device 20B which is a higher-level charging device. When the transmitting unit 12 receives a TAC compliant with the first standard by the receiving unit 11, the transmitting unit 12 sets the TAC at a predetermined position (byte position, area) of the CDR, and when the transmitting unit 12 receives a TAC compliant with the second standard by the receiving unit 11, the transmitting unit 12 sets the TAC in an extended area of the CDR.

[0030] <<Charging device 20B>> The charging device 20B includes a receiving unit 21 and a charging unit 22. Each of these units may be realized by the cooperation of one or more programs installed in the charging device 20B and hardware such as the processor 101 and the memory 102 of the charging device 20B.

[0031] The receiving unit 21 receives a CDR including a TAC from the charging function node 10. The charging unit 22 charges the user based on the CDR received by the receiving unit 21. When the charging unit 22 receives a TAC compliant with the first standard by the receiving unit 21, the charging unit 22 extracts the TAC from a predetermined position of the CDR, and when the charging unit 22 receives a TAC compliant with the second standard by the receiving unit 21, the charging unit 22 extracts the TAC from an extended area of the CDR, and performs charging based on the extracted TAC.

[0032] <Process> <<Process of the charging function node 10>> Next, referring to FIGS. 5 to 7, an example of the processing of the charging function node 10 according to the embodiment will be described. FIG. 5 is a flowchart showing an example of the processing of the charging function node 10 according to the embodiment. FIG. 6 is a diagram showing an example of a CDR for the first standard according to the embodiment. FIG. 7 is a diagram showing an example of a CDR for the second standard according to the embodiment.

[0033] In step S101, the receiving unit 11 of the charging function node 10 receives information including the user ID and TAC from the network function node 30A or the network function node 30B. Here, the receiving unit 11 may receive, for example, a 2-octet format TAC compliant with the 4G standard (an example of the "first standard") from the network function node 30A. Also, the receiving unit 11 may receive, for example, a 3-octet format TAC compliant with the 5G standard (an example of the "second standard") from the network function node 30B.

[0034] The user ID is identification information of the user of the wireless communication terminal. The user ID may be, for example, a contract identification number (IMSI, International Mobile Subscriber Identity), a number unique to the SIM (USIM, UIM) card (ICCID, Integrated Circuit Card ID), or an international mobile equipment identifier (IMEI, International Mobile Equipment Identifier), etc.

[0035] Subsequently, the transmitting unit 12 of the charging function node 10 determines whether the received TAC format complies with the first standard (step S102). Here, the transmitting unit 12 may determine whether it complies with the first standard based on, for example, the data size of the TAC. In this case, the transmitting unit 12 may determine that it complies with the first standard when the data size of the TAC is 2 octets, and determine that it complies with the second standard when the data size of the TAC is 3 octets, for example.

[0036] Further, the transmission unit 12 may determine whether it complies with the first standard based on, for example, the source of the TAC. In this case, for example, when the source of the TAC is the network function node 30A, the transmission unit 12 may determine that it complies with the first standard, and when the source of the TAC is the network function node 30B, the transmission unit 12 may determine that it complies with the second standard.

[0037] When the received TAC format complies with the first standard (YES in step S102), the transmission unit 12 of the charging function node 10 generates a charging data record (CDR) with a 2-octet TAC set at a predetermined position (step S103) and proceeds to the process of step S105.

[0038] Here, as shown in FIG. 6, the predetermined position may be, for example, an area 612 within an area 611 where tracking area identification information (TAI) in the CDR 601 is set. Here, the TAI may be composed of a mobile country code (MCC), a mobile network code (MNC), and a TAC based on the first standard.

[0039] In the example of FIG. 6, the first byte of CDR601 is a value indicating a tag, the second byte is a value indicating the byte size (data length) of the subsequent data, and the third byte is a value indicating the type of the data format of CDR601 (format definition). The fourth byte to the eighth byte is the area 611 where TAI is set, and among them, the seventh byte and the eighth byte are the area 612 where TAC is set. Note that NCGI (NR Cell Global Identifier) is set from the ninth byte to the sixteenth byte. Note that NCGI is composed of MCC (Mobile Country Code), MNC (Mobile Network Code), and NCI (NR Cell Identity), and is used to globally identify an NR (New Radio, 5G) cell. NCGI can be regarded as equivalent to the 4G CGI (Cell Global Identity).

[0040] Thus, for example, in the charging device 20A that supports only the first standard, when receiving a CDR601 including a 2-octet format TAC compliant with the first standard, the TAC can be read from the conventional area 612 and the user can be charged.

[0041] On the other hand, when the format of the received TAC does not conform to the first standard (NO in step S102), as shown in FIG. 7, the transmission unit 12 of the charging function node 10 generates a CDR in which 2-octet dummy data is included in TAI and 3-octet TAC is set in the extended area of the CDR (step S104).

[0042] In the example of FIG. 7, similar to the example of FIG. 6, the first byte of CDR701 is a value indicating a tag, the second byte is a value indicating the byte size (data length) of the subsequent data, and the third byte is a value indicating the format definition of CDR701. Also, the fourth byte to the eighth byte is the area 711 where TAI is set, and among them, the seventh byte and the eighth byte are the area 712 where TAC is set. Also, NCGI is set from the ninth byte to the sixteenth byte.

[0043] In the example of FIG. 7, compared with the example of FIG. 6, the value of the second byte is set to "18", which is a value that is 4 bytes larger in the extended area (bytes 17 to 20). The value of the third byte has a custom value for extension set. Note that since 3 to 128 of the format definition are not defined by standard for Spare, "3" is set in the example of FIG. 7.

[0044] Also, in the example of FIG. 7, dummy data of 2 - octet TAC is set in area 712 within area 711 where TAI in CDR701 is set. The transmission unit 12 may set, for example, as the dummy data, a specific value that is not used as TAC in a radio communication system according to the first standard (for example, EPS (Evolved Packet System), a 4G radio communication system). Note that in the example of FIG. 7, the first octet of the dummy data is "5C" in hexadecimal and the second octet is "10" in hexadecimal, which are fixed values.

[0045] Also, in the example of FIG. 7, a flag (discrimination flag) for determining whether it is a TAC conforming to the first standard is set in area 721 of the 17th octet. Note that, for example, when the charging device 20B determines whether it is a TAC conforming to the first standard based on the value of the third byte, the flag is not essential. Also, in the example of FIG. 7, a TAC conforming to the second standard is set in the 3 - octet area 722 from the 18th octet to the 20th octet.

[0046] For example, in the 4G standard, the data size of the TAC is defined as a fixed length of 2 octets. On the other hand, in the 5G standard, the data size of the TAC is defined as a fixed length of 3 octets. When a communication system compliant with the 4G standard and a communication system compliant with the 5G standard coexist in a commercial network, it is assumed that CDRs of both 4G and 5G are sent from the CHF to the upper charging device. In this case, in the charging device in the communication system compliant with the 4G standard, when the TAC of the CDR transmitted from the CHF is 3 octets, only 2 octets are recognized, and it is considered that a shift will occur in the binary data to be read.

[0047] On the other hand, according to the present disclosure, in the charging device 20A that supports only the first standard (for example, 4G), when receiving the CDR 701 of FIG. 7 including the 3-octet format TAC compliant with the second standard, dummy data of the TAC can be read from the conventional area 712. Therefore, since no shift occurs in the binary data to be read, an unexpected error can be reduced. Also, in the charging device 20A, data other than the TAC is read normally. Therefore, when the contract regarding the fees between the user and the wireless communication carrier does not depend on the geographical conditions when the user's wireless communication terminal communicates, the user can be appropriately charged.

[0048] Subsequently, the transmission unit 12 of the charging function node 10 transmits the generated CDR to the charging device 20A or the charging device 20B (step S105). Here, the transmission unit 12 may determine the transmission destination of the CDR based on, for example, the received user ID. In this case, the transmission unit 12 may transmit the CDR to a charging device according to whether the contract content regarding the fees between the user and the wireless communication carrier varies depending on the geographical conditions when the user's wireless communication terminal communicates. In this case, when the user has a contract where the communication fee under the second standard does not depend on the geographical conditions when the user's wireless communication terminal communicates, the transmission unit 12 may determine the transmission destination of the CDR as the charging device 20A. Thereby, for example, the operation (use) of the charging device 20A that performs charging depending on the geographical conditions only for communication under the first standard can be continued.

[0049] <<Processing of Charging Device 20B>> Next, with reference to FIG. 8, an example of the processing of the charging device 20B according to the embodiment will be described. FIG. 8 is a flowchart showing an example of the processing of the charging device 20B according to the embodiment.

[0050] In step S201, the receiving unit 21 of the charging device 20B receives the user ID and the CDR, etc. from the charging function node 10.

[0051] Subsequently, the charging unit 22 of the charging device 20B determines whether the format of the TAC included in the received CDR conforms to the first standard (step S202). Here, the charging unit 22 may determine whether the format of the TAC conforms to the first standard based on, for example, the above-described discrimination flag (the area 721 of the 17th octet of the CDR701 in FIG. 7). In this case, the charging unit 22 may perform the determination based on, for example, the value of the discrimination flag or the presence or absence of the discrimination flag.

[0052] Also, the charging unit 22 may determine whether the format of the TAC conforms to the first standard based on, for example, the value of the format definition of the second byte of the CDR.

[0053] When conforming to the first standard (YES in step S202), the charging unit 22 extracts (reads) a 2-octet TAC from a predetermined position among the received CDRs (step S203), and proceeds to the process of step S205. Here, for example, the charging unit 22 may extract the 2-octet data at the 7th and 8th bytes (region 612 in FIG. 6) among the received CDRs as the TAC.

[0054] On the other hand, when not conforming to the first standard (NO in step S202), the charging unit 22 extracts a 3-octet TAC from the extended area among the received CDRs (step S204). Here, for example, the charging unit 22 may extract the 3-octet data at the 18th to 20th bytes (region 722 in FIG. 7) among the received CDRs as the TAC.

[0055] Subsequently, the charging unit 22 of the charging device 20B charges the user based on the extracted TAC (step S205). Thereby, the charging device 20B of the present disclosure can support both the TAC of the first standard and the TAC of the second standard.

[0056] Note that the present invention is not limited to the above-described embodiment, and can be appropriately modified without departing from the gist.

[0057] Some or all of the above-described embodiments can be described as follows in the appended claims, but are not limited thereto. (Appended Claim 1) Receiving means for receiving information including a Tracking Area Code (TAC); Transmitting means for transmitting a Charging Data Record (CDR) including the tracking area code; having wherein the transmitting means when receiving the tracking area code conforming to the first standard by the receiving means, sets the tracking area code at a predetermined position of the charging data record; When the tracking area code compliant with the second standard is received by the receiving means, the tracking area code is set in an area where the charging data record is extended. Charging function (CHF) node. (Appendix 2) The first standard is a radio communication standard of the fourth-generation mobile communication system. The second standard is a radio communication standard of the fifth-generation mobile communication system. The charging function node described in Appendix 1. (Appendix 3) The transmitting means When the tracking area code compliant with the first standard is received by the receiving means, the 2-octet tracking area code is set at the predetermined position of the charging data record. When the tracking area code compliant with the second standard is received by the receiving means, 2-octet dummy data is set at the predetermined position, and the 3-octet tracking area code is set in an area where the charging data record is extended. The charging function node described in Appendix 1 or 2. (Appendix 4) The dummy data is a specific value that is not used as the tracking area code in the radio communication system according to the first standard. The charging function node described in Appendix 3. (Appendix 5) The transmitting means The charging data record is transmitted to a charging device according to whether the charge varies depending on geographical conditions when the user's contract content communicates with the user's wireless communication terminal. The charging function node described in any one of Appendices 1 to 4. (Appendix 6) Receiving means for receiving a charging data record (CDR) including a tracking area code (TAC) from a charging function (CHF) node. When the receiving means receives the tracking area code compliant with the first standard, the tracking area code is extracted from a predetermined position of the charging data record, and when the receiving means receives the tracking area code compliant with the second standard, the tracking area code is extracted from an extended area of the charging data record, and charging means for performing charging based on the extracted tracking area code; A charging device having (Appendix 7) The first standard is a radio communication standard of the fourth generation mobile communication system, The second standard is a radio communication standard of the fifth generation mobile communication system. The charging device according to Appendix 6. (Appendix 8) A charging function (CHF, CHarging Function) node performs a process of receiving information including a tracking area code (TAC, Tracking Area Code), and a process of transmitting a charging data record (CDR, Charging Data Record) including the tracking area code, and in the process of transmitting, when the tracking area code compliant with the first standard is received by the receiving process, the tracking area code is set at a predetermined position of the charging data record, and when the tracking area code compliant with the second standard is received by the receiving process, the tracking area code is set in an extended area of the charging data record. A charging method. A charging method. (Appendix 9) A charging device receives a charging data record (CDR, Charging Data Record) including a tracking area code (TAC, Tracking Area Code) from a charging function (CHF, CHarging Function) node, When the tracking area code compliant with the first standard is received, the tracking area code is extracted from a predetermined position of the charging data record. When the tracking area code compliant with the second standard is received, the tracking area code is extracted from an extended area of the charging data record, and charging is performed based on the extracted tracking area code. Charging method.

Explanation of symbols

[0058] 1 Charging system 10 Charging function node 11 Receiver 12 Transmitter 20A Charging device 20B Charging device 21 Receiver 22 Charging unit 30A Network function node 30B Network function node

Claims

1. Receiving means for receiving information including a tracking area code (TAC, Tracking Area Code); Transmitting means for transmitting a charging data record (CDR, Charging Data Record) including the tracking area code; having; The transmitting means: When the tracking area code compliant with the first standard is received by the receiving means, the tracking area code is set at a predetermined position of the charging data record; When the tracking area code compliant with the second standard is received by the receiving means, the tracking area code is set in an extended area of the charging data record; A charging function (CHF, Charging Function) node.

2. The first standard is a radio communication standard of a fourth-generation mobile communication system; The second standard is a radio communication standard of a fifth-generation mobile communication system; The charging function node according to Claim 1.

3. The transmitting means: When the tracking area code compliant with the first standard is received by the receiving means, a 2-octet tracking area code is set at the predetermined position of the charging data record; When the tracking area code compliant with the second standard is received by the receiving means, 2-octet dummy data is set at the predetermined position, and a 3-octet tracking area code is set in an extended area of the charging data record; The charging function node according to Claim 1 or 2.

4. The dummy data is a specific value not used as the tracking area code in the radio communication system according to the first standard; The charging function node according to Claim 3.

5. The transmitting means: Transmits the charging data record to a charging device according to whether the charge varies depending on geographical conditions when the user's contract content communicates with the user's wireless communication terminal; The charging function node according to any one of Claims 1 to 4.

6. Receiving means for receiving a charging data record (CDR, Charging Data Record) including a tracking area code (TAC, Tracking Area Code) from a charging function (CHF, Charging Function) node; When the tracking area code compliant with the first standard is received by the receiving means, the tracking area code is extracted from a predetermined position of the charging data record. When the tracking area code compliant with the second standard is received by the receiving means, the tracking area code is extracted from an extended area of the charging data record, and charging means for performing charging based on the extracted tracking area code; A charging device having the above. **Claim 7** The first standard is a wireless communication standard of a fourth-generation mobile communication system, The second standard is a wireless communication standard of a fifth-generation mobile communication system, The charging device according to claim 6. **Claim 8** A charging function (CHF, Charging Function) node performs processing for receiving information including a tracking area code (TAC, Tracking Area Code), and processing for transmitting a charging data record (CDR, Charging Data Record) including the tracking area code. In the processing for transmitting, when the tracking area code compliant with the first standard is received by the receiving processing, the tracking area code is set at a predetermined position of the charging data record, when the tracking area code compliant with the second standard is received by the receiving processing, the tracking area code is set in an extended area of the charging data record. A charging method. **Claim 9** A charging device receives a charging data record (CDR, Charging Data Record) including a tracking area code (TAC, Tracking Area Code) from a charging function (CHF, Charging Function) node, when the tracking area code compliant with the first standard is received, the tracking area code is extracted from a predetermined position of the charging data record, and when the tracking area code compliant with the second standard is received, the tracking area code is extracted from an extended area of the charging data record, and charging is performed based on the extracted tracking area code. A charging method. ​

Images