Network node and communication method

Abstract

A network node disclosed herein includes: a reception unit for receiving a first message requesting the establishment of a data channel from a terminal, receiving a second message accepting the establishment of the data channel from a second node directly or via a third node, and receiving a third message, including contents for accepting the establishment of the data channel, from a terminating terminal when necessary; a control unit for specifying at least one established data channel established on the basis of at least one of the first message, the second message, or the third message, and specifying an application to be used in the established data channel and a charging party for the established data channel on the basis of first setting information, related to the data channel, and second setting information, related to the charging party, acquired in advance; and a transmission unit for transmitting, to a fourth node, a fourth message requesting the initiation of the recording of charging information including information indicating the established data channel and the charging party for the established data channel.

Description

Network node and communication method

[0001] The present invention relates to a network node in a communication system and a communication method.

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. Various wireless technologies are being studied for 5G to meet the requirements of achieving a throughput of 10 Gbps or more while keeping latency in wireless sections to 1 ms or less.

[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the network architecture of LTE, is being considered (for example, Non-Patent Document 1).

[0004] Furthermore, as an IMS (IP Multimedia Subsystem) architecture that supports the data channel capabilities of terminals, specifications for an IMS data channel network are being studied (see, for example, Non-Patent Document 2). In the IMS data channel network, a Data Channel Signalling Function (DCSF) having a signaling function, a Media Function (MF) having a media-related function, and a Data Channel Application Server (DCAS) that is an application server are arranged on both the calling and called sides.

[0005] 3GPP TS 23.501 V18.3.0 (2023-09) 3GPP TS 23.228 V18.3.0 (2023-09) 3GPP TS 32.260 V18.1.0 (2023-09) IETF RFC8864

[0006] Existing specifications for IMS charging (e.g., Non-Patent Document 3) do not specify specifications for charging IMS data channels. Furthermore, the existing specifications do not allow for the recording and charging of data usage broken down by media component. Furthermore, functions related to the recording and charging of data usage by network nodes such as UPF and SMF in 5GS are not supported in IMS data channels. Furthermore, an external interface for alternate party charging in IMS is not specified.

[0007] The present invention has been made in view of the above points, and has as its object to measure the amount of data used and store billing information in an IMS data channel network.

[0008] According to the disclosed technology, there is provided a network node having: a receiving unit that receives, from a terminal via a first network node, a first message requesting the establishment of a data channel; a second message that accepts the establishment of the data channel from a second network node either via a third network node or directly; and, if necessary, receives, from a terminating terminal via the first network node, a third message including content accepting the establishment of the data channel; a control unit that identifies at least one established data channel based on at least one of the first message, the second message, and the third message, and identifies an application to be used on the established data channel and a charger for the established data channel based on first setting information related to the data channel and second setting information related to a charger that have been acquired in advance; and a transmitting unit that transmits, to a fourth network node, a fourth message requesting the start of recording of charging information, the fourth message including information indicating the established data channel and the charger for the established data channel.

[0009] According to the disclosed technology, data usage can be measured and billing information can be stored in an IMS data channel network.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 3 is a diagram for explaining an example of an IMS data channel network. FIG. 4 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. FIG. 7 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. FIG. 8 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. FIG. 9 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 10 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 11 is a diagram showing an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG.

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced, and systems subsequent to LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0013] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.

[0014] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0015] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0016] The AMF is connected to the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are mutually connected via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0017] The SMF is a network node 30 having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that stores the data.

[0018] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0019] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0020] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0021] The SMF is a network node 30 having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is a SEPP in the visited network, and the hSEPP is a SEPP in the home network.

[0022] As shown in Figure 2, a UE is in a roaming environment connected to a RAN and an AMF in a Visited PLMN (VPLMN). The VPLMN and a Home PLMN (HPLMN) are connected via a vSEPP and an hSEPP. The UE can communicate with a UDM in the HPLMN via the AMF in the VPLMN, for example.

[0023] Fig. 3 is a diagram illustrating an example of an IMS data channel network. As shown in Fig. 3, the IMS data channel network is configured with a terminal 20 (UE) and multiple network nodes 30 in each of an originating network and a terminating network. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection. The network node 30 has, for example, the following functions described in Non-Patent Document 2:

[0024] The IMS-AGW (Access Gateway) is a network node 30 having a gateway function between the UE and the IMS network.

[0025] A P-CSCF (Proxy-Call Session Control Function) is a network node 30 having a proxy function between the UE and the IMS network.

[0026] The S-CSCF (Serving-Call Session Control Function) is a network node 30 having functions related to session control for the UE.

[0027] The I-CSCF (Interrogate-Call Session Control Function) is a connection point on the destination network side between networks (e.g., between the source network side and the destination network side) in the IMS network, and is a network node 30 that has, for example, the function of forwarding a received SIP request to the S-CSCF of its own network.

[0028] An IMS AS (IP Multimedia Subsystem Application Server) is a network node 30 in an IMS network that has functions such as communicating with a DCSF for event notification and receiving data channel control instructions from the DCSF to communicate with an MF. The IMS AS also receives a communication termination point registration request from a DCSF (Data Channel Signalling Function), converts the received registration request into a SIP Register, and sends it to a Serving-Call Session Control Function (S-CSCF). The IMS AS also converts a data channel establishment request received from the DCSF into a SIP INVITE and sends it to the S-CSCF.

[0029] The DCSF (Data Channel Signaling Function) is a network node 30 that has functions such as receiving an event report from the IMS-AS and determining whether to allow the provision of a data channel service, managing the bootstrap data channel, and performing HTTP web server functions.

[0030] An MF (Media Function) is a network node 30 in an IMS network that has functions such as media resource management and forwarding of data channel media traffic. The MF processes media between a DCAS (Data Channel Application Server), which is a communication termination point, and a destination termination point based on configuration information received from a DCSF. The MF may also be called a DCMF (Data Channel Media Function). The MF may also be called an MRF (Multimedia Resource Function).

[0031] A DCAS (Data Channel Application Server) is a network node 30 having functions such as a communication termination point for media and signaling in the IMS network.

[0032] In addition, the network nodes described in Figures 1, 2 and 3 may be able to access a CDF (Charging Data Function), a CHF (Charging Function) and a CGF (Charging Gateway Function), which are network nodes 30 that manage charging information (Charging Data Record, CDR) based on data volume.

[0033] (First Embodiment) A first embodiment will be described below. In the first embodiment, a procedure for measuring the amount of data used and storing billing information in an IMS data channel network will be described.

[0034] Existing specifications for IMS charging (e.g., Non-Patent Document 3) do not prescribe specifications for charging IMS data channels. In the existing specifications, media components described based on the Session Description Protocol (SDP) (i.e., the description in the "m=" line in the SDP) are the minimum granularity of description in a Charging Data Record (CDR). Therefore, it is not possible to record data usage in the CDR and perform charging at the granularity of data channels that subdivide and allocate media components (i.e., the description in each a=dcmap line under the m= line in the SDP).

[0035] Furthermore, in 5GS, the UPF monitors data usage and reports it to the SMF, which then writes the information to the CDR in the CHF. On the other hand, the IMS does not have the corresponding function, and it is not possible to store data usage in the CDR and charge based on the data usage.

[0036] Furthermore, an external application interface (API) has not been defined for alternate party charging in IMS, which is similar to sponsor charging in 5GS.

[0037] In the first embodiment, a DCSF CDR is newly introduced into the CDF, where the DCSF, which manages data channels, creates a DCSF CDR for each data channel. The CDF may also be called a CHF. The MF measures data usage for each data channel and reports it to the DCSF. In addition, a new API for setting up alternate party charging is introduced into the DCSF.

[0038] In the procedures described below, requests, responses, notifications, etc. transmitted and received between network nodes may be called messages (e.g., request messages), and information included in messages may be called parameters.

[0039] 4 is a diagram showing an example of a first sequence diagram according to an embodiment of the present invention. The processing of each step in FIG. 4 will now be described.

[0040] Steps S401 to S413 are steps for setting up billing associated with uploading a data channel (DC) application.

[0041] S401: The DCAS 30g sends a request message (Nnef_DCappUploading_Create request) to the NEF 30f requesting uploading of a DC application. The request message includes the DC application, a profile of the DC application, and information about an alternate party for billing (Alternate Party Information). The DC application is an application that the terminal 20 downloads from a network and installs on the terminal 20 for use. The profile of the DC application includes information such as the identifier of the DC application and the form in which the DC application is used (e.g., P2A (between the terminal 20 and an application server) or P2A2P (multiple terminals 20 communicate via an application server)). The information about the alternate party for billing may also include, for example, the name of the alternate party, the identifier of the alternate party, and the access destination (e.g., IP address).

[0042] S402: The NEF 30f transfers the information (parameters) included in the request message received in S401 without processing them.

[0043] S403: The NEF 30f transfers the request message received in S401 to the DCSF 30d as an Ndcsf_DCappUploading_Create request.

[0044] S404: In the function of handling policies, the DCSF 30d stores the information (parameters) included in the request message received in S403 as policy information.

[0045] S405: In its policy handling function, the DCSF 30d generates binding information based on the information received in S403 (information about the DC application, the profile of the DC application, and the proxy for billing). The binding information may be, for example, a stream ID or a label associated with the DC application. The terminal 20 uses the binding information as information for specifying the DC and DC application. The DCSF 30d can identify the DC and DC application based on the binding information received from the terminal 20. The binding information may also be referred to as additional information.

[0046] S406: The DCSF 30d sends an Ndcsf_DCappUploading_Create response to the NEF 30f as a response to the request message received in S403.

[0047] S407: The NEF 30f sends an Nnef_DCappUploading_Create response to the DCSF 30d as a response to the request message received in S401.

[0048] S408: The DCAS 30g sends a request message (Nnef_DCappUploading_Update request) to the NEF 30f requesting updating of the DC application, the profile of the DC application, and information on the alternate party for charging. Here, the request message includes the profile of the DC application to be updated and information on the alternate party for charging (Alternate party information).

[0049] S409: The NEF 30f transfers the information (parameters) included in the request message received in S408 without processing them.

[0050] S410: The NEF 30f transfers the request message received in S408 to the DCSF 30d as an Ndcsf_DCappUploading_Update request.

[0051] S411: The DCSF 30d, in its function of handling policies, updates policy information based on the information (parameters) included in the request message received in S410.

[0052] S412: The DCSF 30d sends an Ndcsf_DCappUploading_Update response to the NEF 30f as a response to the request message received in S410.

[0053] S413: The NEF 30f sends an Nnef_DCappUploading_Update response to the DCSF 30d as a response to the request message received in S408.

[0054] Steps S414 to S420 are steps for setting up billing without uploading a Data Channel (DC) application.

[0055] S414: The DCAS 30g sends a request message (Nnef_ChargeableParty_Create request) to the NEF 30f to request the setting of an alternate party that can perform charging for the DC. The request message includes the profile of the DC application to be updated and information about the alternate party for charging.

[0056] S415: The NEF 30f recognizes that the request message received in S414 is a request regarding an alternative party for charging the DC, and selects the DCSF as the destination instead of the PCF, which is the destination in cases other than charging the DC.

[0057] S416: The NEF 30f transfers the information (parameters) included in the request message received in S414 without processing them.

[0058] S417: The NEF 30f transfers the request message received in S414 to the DCSF 30d as an Ndcsf_DcPolicyAuthorization_Create request.

[0059] S418: In the function of handling policies, the DCSF 30d updates information on the proxy for billing the DC application based on the information (parameters) included in the request message received in S417.

[0060] S419: The DCSF 30d sends an Ndcsf_DcPolicyAuthorization_Create response to the NEF 30f as a response to the request message received in S417.

[0061] S420: The NEF 30f transmits an Nnef_ChargeableParty_Create response to the DCAS 30g as a response to the request message received in S414.

[0062] In steps S401 to S420, the DCAS 30g may send a request message directly to the DCSF 30d without going through the NEF 30f.

[0063] Next, the procedure for establishing a data channel will be described. Fig. 5 is a diagram showing an example of a second sequence diagram according to an embodiment of the present invention. The processing of each step in Fig. 5 will be described below.

[0064] S501: The terminal 20 sends a SIP INVITE to the P-CSCF 30a to request the establishment of a data channel.

[0065] S502: A bootstrap data channel setup signaling procedure (see Section AC.7.1 of Non-Patent Document 2) is executed among the terminal 20, the P-CSCF 30a, the S-CSCF 30b, the IMS AS 30c, the DCSF 30d, and the MF 30e. In this procedure, the terminal 20 downloads a DC application from the DCSF 20d. In addition, the terminal 20 obtains binding information (already described in S405 of FIG. 4) associated with the downloaded DC application.

[0066] S503: The terminal 20 sends a SIP re-INVITE including the binding information acquired in S502 to the P-CSCF 30a.

[0067] S504: The P-CSCF 30a transmits the received SIP re-INVITE to the S-CSCF 30b.

[0068] S505: The S-CSCF 30b sends the received SIP re-INVITE to the IMS AS 30c.

[0069] S506: The IMS AS 30c sends a Nimsas_SessionEventControl_Notify request including information about the received SIP re-INVITE to the DCSF 30d.

[0070] S507: The DCSF 30d identifies the DC application, the DC related to the DC application, and information about the DC (Data Channel related description) based on the binding information included in the request message received in S506. The information about the DC is expressed as SDP DCMAP Attributes and SDP DCSA Attributes (see Non-Patent Document 4). Thereafter, the DCSF 30d sets a DC corresponding to the DC application requested by the terminal 20. Here, multiple DCs may be associated with the DC application.

[0071] S508: The DCSF 30d checks the profile of the DC application identified in S507, and identifies information on an alternate party for billing in the DC application.

[0072] S509: The DCSF 30d determines that, because a billing substitute has been set for the DC application identified in S507, it is necessary to monitor the data usage for the DC using the DC application. Monitoring means monitoring the data usage for each data channel corresponding to the DC application and measuring the data usage.

[0073] S510: The DCSF 30d sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS 30c. The request message includes MF setting information to be set in the MF 30e.

[0074] S511: The IMS AS 30c sends an Nmf_MRM_Create request to the MF 30e. The request message includes MF setting information. The MF 30e sets the received MF setting information in its own device.

[0075] S512: The MF 30e sends an Nmf_MRM_Create response to the IMS AS 30c as a response to the request message received in S511.

[0076] S513: The IMS AS 30c sends a Nimsas_MediaControl_MediaInstruction response to the DCSF 30d as a response to the request message received in S510.

[0077] S514: The DCSF 30d sends an Ndcsf_SessionEventControl_Notify request including the information received in S506 (SIP re-INVITE information) to the NEF 30f.

[0078] S515: The NEF 30f sends an Nnef_SessionEventControl_Notify request including the information (SIP re-INVITE information) received in S514 to the DCAS 30g. Also, in S514 to S517, the DCAS 30g may send and receive messages directly to and from the DCSF 30d without going through the NEF 30f.

[0079] S516: The DCAS 30g transmits an Nnef_SessionEventControl_Notify response to the NEF 30f as a response to the request message received in S515. The request message includes information about the DC accepted by the DCAS 30e in S515.

[0080] S517: The NEF 30f transmits an Ndcsf_SessionEventControl_Notify response to the DCSF 30d as a response to the request message received in S514. The request message includes information about the DC accepted by the DCAS 30e in S515.

[0081] In the processes from S518 to S522, the setting information in the MF 30e is updated to establish only the DC accepted by the DCAS 30e in S515 and to set the DC for the called terminal. S518: The DCSF 30d sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS 30c. The request message includes MF setting information to be set in the MF 30e, which was generated based on the information about the DC received in S517.

[0082] S519: The IMS AS 30c sends an Nmf_MRM_Create request to the MF 30e. The request message includes MF setting information. The MF 30e sets the received MF setting information in its own device.

[0083] S520: The MF 30e sends an Nmf_MRM_Create response to the IMS AS 30c as a response to the request message received in S519. The response message includes information about the DC set in the MF 30e. This information may also be included in messages sent and received in the following steps, as necessary.

[0084] S521: The IMS AS 30c sends a Nimsas_MediaControl_MediaInstruction response to the DCSF 30d as a response to the request message received in S518.

[0085] S522: The DCSF 30d sends a Nimsas_SessionEventControl_Notify response to the IMS AS 30c as a response to the request message received in S506.

[0086] The process following S522 will be described. Fig. 6 is a diagram showing an example of a third sequence diagram according to an embodiment of the present invention. The process of each step in Fig. 6 will be described below.

[0087] S523: The IMS AS 30c sends a SIP re-INVITE (including binding information) to the S-CSCF 30b.

[0088] S524: The S-CSCF 30b transmits the received SIP re-INVITE to the terminating network and the terminating terminal. The terminating network and the terminating terminal execute the same processing as in the existing specifications. Note that in the case of the P2A mode, no processing is executed for the terminating network and the terminating terminal. The same applies to the subsequent processing.

[0089] S525: The S-CSCF 30b receives a 200 OK from the terminating network and the terminating terminal. The 200 OK includes the source IP address of the terminating terminal and information about the DC selected by the terminating terminal from among the DCs set in the MF 30e (the DC that the terminating terminal accepts establishment of).

[0090] S526: The S-CSCF 30b sends a 200 OK to the IMS AS 30c.

[0091] S527: The IMS AS 30c sends a Nimsas_SessionEventControl_Notify request including the received 200 OK information to the DCSF 30d. The 200 OK information may also be included in messages sent and received in the subsequent procedures, as necessary.

[0092] S528: The DCSF 30d sends a Charging Data request to the CDF 30h. The request message includes information about the alternate charging party identified in S507 (Alternate party information) as the address of the alternate charging party (Alternate Charged Party Address). Furthermore, the request message includes an identifier of the DC application (DC application identifier) ​​that is the subject of charging identified in S507, and information about the DC (Data Channel related description). In the processing of subsequent steps, the DC application identifier and information about the DC included in the request message may be included in a message that requests the CDF 30h to update or stop recording charging information, in order to identify the subject of charging.

[0093] S529: The CDF 30h starts recording the DCSF charging information for the DC application (Open DCSF CDR for DC application) based on the information included in the request message received in S528.

[0094] S530: The CDF 30h transmits a Charging Data response to the DCSF 30d as a response to the request message received in S528.

[0095] In the processes from S531 to S535, the source IP address of the end terminal and the DC selected by the end terminal from among the DCs set in the MF 30e are notified to the MF 30e. S531: The DCSF 30d sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS 30c. The request message includes information indicating a request to monitor data usage.

[0096] S532: The IMS AS 30c sends an Nmf_MRM_Create request to the MF 30e. The request message includes information indicating a request to monitor the amount of data usage.

[0097] S533: MF30e identifies the DC to monitor based on the source IP address of the terminal included in the received request message and the DC selected by the terminal from among the DCs set in MF30e, configures its own device to monitor the usage of the data, and monitors the usage of the data.

[0098] S534: The MF 30e sends an Nmf_MRM_Create response to the IMS AS 30c as a response to the request message received in S532.

[0099] S535: The IMS AS 30c sends a Nimsas_MediaControl_MediaInstruction response to the DCSF 30d as a response to the request message received in S531.

[0100] In the processes from S536 to S539, the information confirmed by the end terminal (such as the selected DC) is included in the message to be sent, thereby notifying the DCAS 30g.

[0101] S536: The DCSF 30d sends an Ndcsf_SessionEventControl_Notify request including the 200 OK information received in S527 to the NEF 30f.

[0102] S537: The NEF 30f sends an Nnef_SessionEventControl_Notify request including the 200 OK information received in S536 to the DCAS 30g.

[0103] S538: The DCAS 30g sends an Nnef_SessionEventControl_Notify response to the NEF 30f as a response to the request message received in S537.

[0104] S539: The NEF 30f sends an Ndcsf_SessionEventControl_Notify response to the DCSF 30d as a response to the request message received in S536.

[0105] S540: The DCSF 30d sends a Nimsas_SessionEventControl_Notify response including 200 OK information to the IMS AS 30c as a response to the request message received in S527. Also, in S536 to S539, the DCAS 30g may send and receive messages directly to and from the DCSF 30d without going through the NEF 30f.

[0106] S541: The IMS AS 30c sends a 200 OK to the S-CSCF 30b.

[0107] S542: The S-CSCF 30b transmits a 200 OK to the P-CSCF 30a.

[0108] S543: The P-CSCF 30a transmits a 200 OK to the terminal 20.

[0109] S544: The terminal 20 transmits an ACK to the P-CSCF 30a as a response to the received 200 OK.

[0110] S545: The P-CSCF 30a transmits an ACK to the S-CSCF 30b.

[0111] S546: The S-CSCF 30b sends an ACK to the IMS AS 30c.

[0112] S547: The IMS AS 30c sends an ACK to the S-CSCF 30b.

[0113] S548: The S-CSCF 30b transmits an ACK to the terminating network and the terminating terminal.

[0114] Next, the procedure for using the data channel will be described. Fig. 7 is a diagram showing an example of a fourth sequence diagram according to an embodiment of the present invention. The processing of each step in Fig. 7 will be described below.

[0115] S701: The MF 30e detects a report trigger (for example, a trigger set to periodically perform a report).

[0116] S702: The MF 30e sends an Nmf_Report_Notify request to the IMS AS 30c. The request message includes a data usage report.

[0117] S703: The IMS AS 30c sends a Nimsas_MediaControl_MediaReport_Notify request to the DCSF 30d. The request message includes a data usage report.

[0118] S704: The DCSF 30d sends a Charging Data request to the CDF 30h. The request message includes a usage report on the amount of data used.

[0119] S705: The CDF 30h updates the record of the DCSF's billing information for the DC application (Update DCSF CDR for DC application) based on the report on the amount of data usage (Usage report) included in the request message received in S704.

[0120] S706: The CDF 30h transmits a Charging Data response to the DCSF 30d as a response to the request message received in S704.

[0121] Next, the procedure for releasing a data channel will be described. Fig. 8 is a diagram showing an example of a fifth sequence diagram according to an embodiment of the present invention. The processing of each step in Fig. 8 will be described below.

[0122] S801: The terminal 20 transmits a message (BYE) to the P-CSCF 30a to release the data channel.

[0123] S802: The P-CSCF 30a transmits a BYE to the S-CSCF 30b.

[0124] S803: The S-CSCF 30b sends a BYE to the IMS AS 30c.

[0125] S804: The IMS AS 30c sends a Nimsas_SessionEventControl_Notify request, including the received BYE information, to the DCSF 30d, requesting the release of the data channel.

[0126] S805: The DCSF 30d sends a Nimsas_MediaControl_MediaReport request to the IMS AS 30c. The request message includes a request for immediate reporting of the data usage amount, which is the difference from the previous report (Immediate reporting).

[0127] S806: The IMS AS 30c sends an Nmf_Report request to the MF 30e. The request message includes a request for immediate reporting of the data usage amount, which is the difference from the previous report (Immediate reporting).

[0128] S807: The MF 30e sends an Nmf_Report response to the IMS AS 30c in response to the received request message. The response message includes a report on the amount of data usage (Usage report) that is the difference from the previous report.

[0129] S808: The IMS AS 30c sends a Nimsas_MediaControl_MediaReport response to the DCSF 30d in response to the request message received in S805. The response message includes a usage report on the amount of data usage that is the difference from the previous report.

[0130] S809: The DCSF 30d sends a Charging Data request to the CDF 30h. The response message to the request message includes a usage report on the amount of data usage that is the difference from the previous report.

[0131] S810: The CDF 30h updates the record of the DCSF's billing information for the DC application (Update DCSF CDR for DC application) based on the report on the amount of data usage (Usage report) included in the request message received in S809.

[0132] S811: The CDF 30h transmits a Charging Data response to the DCSF 30d as a response to the request message received in S809.

[0133] S812: The DCSF 30d sends a Charging Data request to the CDF 30h. The response message of the request message includes information instructing the CDF 30h to stop recording charging information.

[0134] S813: In response to the request message received in S812, the CDF 30h ends recording of the DCSF charging information for the DC application (Close DCSF CDR for DC application).

[0135] S814: The CDF 30h transmits a Charging Data response to the DCSF 30d as a response to the request message received in S812.

[0136] In the processes of S815 to S818, the deletion of the setting related to the monitoring of the data usage is notified to the MF 30e. S815: The DCSF 30d sends a Nimsas_MediaControl_MediaInstruction request to the IMS AS 30c. The request message includes information requesting the deletion of the setting related to the monitoring of the data usage.

[0137] S816: The IMS AS 30c sends an Nmf_MRM_Delete request to the MF 30e. The request message includes information requesting deletion of the settings related to monitoring of data usage. In response to the received request message, the MF 30e deletes the settings for monitoring data usage.

[0138] S817: The MF 30e sends an Nmf_MRM_Delete response to the IMS AS 30c as a response to the request message received in S816.

[0139] S818: The IMS AS 30c sends a Nimsas_MediaControl_MediaInstruction response to the DCSF 30d as a response to the request message received in S815.

[0140] In the processing from S819 to S822, the release of the data channel is notified to the DCAS 30g.

[0141] S819: The DCSF 30d sends an Ndcsf_SessionEventControl_Notify request to the NEF 30f. The request message includes information instructing the release of the data channel. This information may also be included in messages sent and received in subsequent steps as necessary.

[0142] S820: The NEF 30f sends an Nnef_SessionEventControl_Notify request to the DCAS 30g. In response to the received request message, the DCAS 30g releases the data channel.

[0143] S821: The DCAS 30g sends an Nnef_SessionEventControl_Notify response to the NEF 30f as a response to the request message received in S820.

[0144] S822: The NEF 30f sends an Ndcsf_SessionEventControl_Notify response to the DCSF 30d as a response to the request message received in S819.

[0145] S823: The DCSF 30d sends a Nimsas_SessionEventControl_Notify response to the IMS AS 30c as a response to the request message received in S804.

[0146] S824: The IMS AS 30c sends a BYE to the S-CSCF 30b.

[0147] S825: The S-CSCF 30b transmits a BYE to the terminating network and the terminating terminal.

[0148] According to the above-described embodiment, the DCSF 30d receives a first message requesting the establishment of a data channel from the terminal 20 via the IMS AS 30c (S501-S506), receives a second message accepting the establishment of the data channel from the DCAS 30g (S516-S517, S538-S539), and, if necessary, receives a third message including the content accepting the establishment of the data channel from the terminating terminal via the IMS AS 30c (S525-S527). The DCSF 30d also identifies at least one established data channel based on at least one of the first message, the second message, and the third message, and identifies an application to be used for the established data channel and a charger for the established data channel based on previously acquired first setting information related to the data channel and second setting information related to a charger (S507-S509, S531-S535). The DCSF 30d also transmits to the CDF 30h a fourth message requesting the start of recording of billing information, the fourth message including information indicating the established data channel and the billing person for the established data channel (S528).

[0149] In addition, DCSF 30d transmits a fifth message to MF 30e via IMS AS 30c requesting measurement of data usage for each established data channel (S532), receives a report of the measured data usage for each established data channel from MF 30e via IMS AS 30c (S702), and transmits a sixth message to CDF 30h requesting that the measured data usage be recorded in the charging information (S704).

[0150] In addition, DCSF30d receives from DCAS30g, either via NEF30f or directly, the first setting information including the application to be used on the data channel and a profile including an identifier of the data channel, and the second setting information including the access destination of the charger (S401-S403), and generates additional information for identifying the data channel corresponding to the first message based on the first setting information and the second setting information (S405).

[0151] DCSF30d also receives a seventh message from IMS AS30c requesting the release of the established data channel (S804), sends an eighth message via IMS AS30c to MF30e requesting that it immediately report the data usage amount, which is the difference from the previous report (S805, S806), receives from MF30e a report of the data usage amount in response to the request made in the eighth message (S807, S808), and sends a ninth message via IMS AS30c to MF30e requesting that it release the established data channel (S815, S816).

[0152] In addition, the MF30e receives a message from the IMS AS30c requesting measurement of data usage for each data channel (S532), measures the data usage (S533), and transmits a report of the measured data usage to the IMS AS30c (S702).

[0153] According to the above-described embodiment, data usage can be measured and billing information can be stored in an IMS data channel network.

[0154] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0155] <Base Station 10 and Network Node 30> Fig. 9 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 9, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 9 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0156] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

[0157] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out from the storage device as needed. The content of the setting information is, for example, information related to a communication path in the IMS data channel network.

[0158] As described in the embodiment, the control unit 140 performs processing related to the IMS data channel. The control unit 140 also performs processing related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0159] <Terminal 20> Fig. 10 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 10, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 10 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.

[0160] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving control signals, reference signals, etc. transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0161] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 in a storage device and reads them out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to communication paths in the IMS data channel network.

[0162] As described in the embodiment, the control unit 240 performs processing related to the IMS data channel. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0163] (Hardware Configuration) The block diagrams (FIGS. 9 and 10) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0164] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0165] For example, the base station 10, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0166] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0167] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0168] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0169] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0170] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0171] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0172] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0173] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0174] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0175] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0176] Fig. 12 shows an example configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0177] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0178] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0179] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0180] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0181] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0182] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0183] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0184] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0185] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0186] <Additional Notes> (Additional Note 1) A network node having: a receiving unit that receives, from a terminal via a first network node, a first message requesting the establishment of a data channel; receives, from a second network node, via a third network node or directly, a second message accepting the establishment of the data channel; and, if necessary, receives, from a terminating terminal via the first network node, a third message including content accepting the establishment of the data channel; a control unit that identifies at least one established data channel based on at least one of the first message, the second message, and the third message; and identifies an application to be used on the established data channel and a charger for the established data channel based on first setting information regarding the data channel and second setting information regarding a charger, which have been acquired in advance; and a transmitting unit that transmits, to a fourth network node, a fourth message requesting the start of recording of charging information, the fourth message including information indicating the established data channel and the charger for the established data channel. (Supplementary Item 2) The network node according to Supplementary Item 1, wherein the transmitter transmits a fifth message to a fifth network node via the first network node, requesting measurement of data usage for each established data channel, the receiver receives a report of the measured data usage for each established data channel from the fifth network node via the first network node, and the transmitter transmits a sixth message to the fourth network node, requesting recording of the measured data usage in the charging information. (Supplementary Item 3) The network node according to Supplementary Item 1, wherein the receiver receives from the second network node directly or via the third network node the first setting information including an application to be used on a data channel and a profile including an identifier of the data channel, and the second setting information including an access destination of the charger, and the controller generates accompanying information for identifying a data channel corresponding to the first message based on the first setting information and the second setting information.(Supplementary Item 4) The network node according to Supplementary Item 2, wherein the receiving unit receives a seventh message from the first network node requesting release of the established data channel, the transmitting unit transmits an eighth message, via the first network node, to the fifth network node requesting immediate reporting of the data usage amount, which is a difference from a immediately preceding report, the receiving unit receives a report of the data usage amount in response to the request in the eighth message from the fifth network node via the first network node, and the transmitting unit transmits a ninth message, via the first network node, to the fifth network node requesting release of the established data channel. (Supplementary Item 5) A network node comprising: a receiving unit that receives a message from a first network node requesting measurement of data usage amount for each data channel, a control unit that measures the data usage amount, and a transmitting unit that transmits a report of the measured data usage amount to the first network node. (Supplementary clause 6) A communication method executed by a network node, comprising the steps of: receiving, from a terminal via a first network node, a first message requesting the establishment of a data channel; receiving, from a second network node, via a third network node or directly, a second message accepting the establishment of the data channel; if necessary, receiving, from a terminating terminal via the first network node, a third message including content accepting the establishment of the data channel; identifying at least one established data channel to be established based on at least one of the first message, the second message, and the third message; identifying an application to be used for the established data channel and a charger for the established data channel based on first setting information regarding the data channel and second setting information regarding a charger, which have been obtained in advance; and transmitting, to a fourth network node, a fourth message requesting the start of recording of charging information, the fourth message including information indicating the established data channel and the charger for the established data channel.

[0187] Any of Supplementary Items 1 to 6 makes it possible to measure the amount of data used and store billing information in an IMS data channel network.

[0188] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0189] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0190] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0191] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0192] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0193] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0194] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0195] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0196] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0197] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0198] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0199] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0200] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0201] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0202] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0203] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0204] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

[0205] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0206] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.

[0207] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0208] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0209] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0210] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0211] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0212] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0213] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0214] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0215] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0216] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0217] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0218] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0219] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0220] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0221] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0222] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A receiving unit that receives, from a terminal via a first network node, a first message requesting establishment of a data channel, receives, from a second network node via a third network node or directly, a second message accepting establishment of the data channel, and, if necessary, receives, from the incoming terminal via the first network node, a third message including content accepting establishment of the data channel; a control unit that identifies at least one established data channel based on at least one of the first message, the second message, and the third message, and identifies an application to be used in the established data channel and a charger for the established data channel based on first setting information regarding the data channel and second setting information regarding the charger, which are acquired in advance; and a transmitting unit that transmits, to a fourth network node, a fourth message requesting start of recording of charging information including information indicating the established data channel and the charger for the established data channel. A network node having the above components.

2. The transmitting unit transmits, via the first network node, a fifth message requesting measurement of data usage for each of the established data channels to a fifth network node, the receiving unit receives, via the first network node, a report of the measured data usage for each of the established data channels from the fifth network node, and the transmitting unit transmits, to the fourth network node, a sixth message requesting recording of the measured data usage in the charging information. The network node according to claim 1.

3. The receiving unit receives, from the second network node via the third network node or directly, the first setting information including an application to be used in the data channel and a profile including an identifier of the data channel, and the second setting information including an access destination of the charger. The control unit generates additional information for identifying the data channel corresponding to the first message based on the first setting information and the second setting information. The network node according to claim 1.

4. The receiving unit receives a seventh message for requesting release of the established data channel from the first network node; the transmitting unit transmits, via the first network node, an eighth message for requesting to immediately report the data usage amount, which is the difference from the previous report, to the fifth network node; the receiving unit receives, via the first network node, a report of the data usage amount in response to the request by the eighth message from the fifth network node; the transmitting unit transmits, via the first network node, a ninth message for requesting release of the established data channel to the fifth network node. The network node according to claim 2.

5. A network node comprising: a receiving unit that receives a message for requesting measurement of data usage amount for each data channel from a first network node; a control unit that measures the data usage amount; and a transmitting unit that transmits a report of the measured data usage amount to the first network node.

6. A communication method executed by a network node, the method comprising: receiving, from a terminal via a first network node, a first message for requesting establishment of a data channel; receiving, from a second network node via a third network node or directly, a second message for accepting establishment of the data channel; receiving, if necessary, from an incoming terminal via the first network node, a third message including content for accepting establishment of the data channel; identifying at least one established data channel based on at least one of the first message, the second message, and the third message; identifying an application to be used in the established data channel and a charger for the established data channel based on first setting information regarding the data channel and second setting information regarding the charger, which are obtained in advance; and transmitting, to a fourth network node, a fourth message for requesting start of recording of charging information, the fourth message including information indicating the established data channel and the charger for the established data channel.

Images