Network node, information processing system, information processing method, and non-transitory storage medium
By using data identifiers in billing data records in wireless communication networks for reward payment and fee claim, the problem of insufficient enthusiasm for user data provision is solved, and the quality and reliability of data provision are improved.
Patent Information
- Application Number
- CN202410019602.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2024-01-05
- Publication Date
- 2024-11-15
AI Technical Summary
The prior art is difficult to effectively motivate users to provide valuable data, resulting in insufficient enthusiasm for providing data.
By introducing billing data records in the wireless communication network, including the data identifier of the data providing device, generating billing data records, and making reward payments and fee requests respectively during the data provision and utilization process, ensuring that the data provision user gets the appropriate award.
Increase enthusiasm for providing high-quality data, promote more useful data provision, and enhance the reliability and rarity of data provision.
Smart Images

Figure CN118972794A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a network node, an information processing system, an information processing method, and a non-transitory storage medium. Background Art
[0002] Japanese Patent Laid-Open No. 2008-242553 discloses a technology in which a server registers user information of a user's portable terminal participating in information provision, retrieves a user participating in providing information corresponding to the information category of information provision requested from a client's portable terminal, and sends a request for information provision to the user terminal of the corresponding user. In this way, information meaningful to the client seeking information provision can be collected. Summary of the invention
[0003] The present disclosure provides a technology capable of providing a reward to a user who has contributed to providing data.
[0004] A first aspect of the present disclosure relates to a network node that constitutes a wireless communication network. The network node has a processor. The processor is configured to: receive a charging data request; and generate a charging data record in response to receiving the charging data request. The charging data record contains a data identifier of data provided by a data providing device.
[0005] The information processing system involved in the second mode of the present disclosure includes a network node and a billing domain. The network node has a first processor, which is configured to perform: receiving a billing data request; generating a billing data record in response to receiving the billing data request; and sending the billing data record to the billing domain. The billing domain has a second processor, which is configured to perform: receiving the billing data record; and request processing or payment processing based on the billing data record. The billing data record contains an identifier of data provided by a data providing device.
[0006] The third mode of the present disclosure involves an information processing method performed by a network node constituting a wireless communication network. The information processing method includes: receiving a charging data request; and generating a charging data record in response to the receipt of the charging data request. The charging data record includes a data identifier of data provided by a data providing device.
[0007] A non-transitory storage medium according to a fourth aspect of the present disclosure stores instructions that can be executed by a computer and cause the computer to execute the method according to the third aspect.
[0008] According to the aspect of the present disclosure, since it is possible to provide incentives to users who have contributed to the provision of data, it is possible to promote the provision of more useful data. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, in which like reference numerals represent like elements, and in which: Figure 1 The diagram illustrates components of a wireless communication system. Figure 2 This is a diagram for explaining CHF (Charging Function). Figure 3A This is a diagram showing a configuration example of an information processing device that can operate as a NF, an OAM terminal, and an external server. Figure 3B This is a diagram showing a configuration example of an information processing device that can operate as a user terminal. Figure 4A It is a sequence diagram related to the collection and provision of sensor measurement data. Figure 4B It is a sequence diagram related to the collection and provision of sensor measurement data. Figure 5 This is a flowchart related to billing processing based on BD (Billing Domain). DETAILED DESCRIPTION
[0010] (summary) Consider collecting data from a user terminal or other device and providing the data or processed data to other user terminals or other devices. As an example, the user terminal may be a mobile communication terminal, and the collected data may be sensory measurement data measured by the user terminal. In such a system, whether the user provides data, and the frequency, accuracy, and importance of the data provided by the user depend on the user. Therefore, in order to increase the enthusiasm for providing data, it is also desirable to appropriately reward the user who provides the data.
[0011] One method of the present disclosure is a network node, which constitutes a wireless communication network, and is characterized in that it has a processor, which executes: receiving a charging data request (Charging Data Request); and generating a charging data record (Charging Data Record) in response to receiving the charging data request (Charging Data Record), wherein the charging data record includes a data identifier of data provided by a data providing device.
[0012] An example of a wireless communication network is a system using 5G, 4G, LTE, LTE-A, SUPER3G, IMT-Advanced, NR and others, and next-generation systems enhanced therefrom. In addition, other examples of wireless communication networks are IEEE802.11 (Wi-Fi (registered trademark)), IEEE802.16 (WiMAX (registered trademark)), IEEE802.20, UWB, Bluetooth (registered trademark), other systems, and next-generation systems enhanced therefrom. A wireless communication network may also be a system composed of a plurality of systems.
[0013] The charging data record is also called CDR (Charging Data Record). In this method, the charging data record includes a data identifier of the data provided by the data providing device. In addition, a first charging data record is generated when the data is provided by the data providing device, and a second charging data record is generated when the data is used by the data using device. By generating charging data records in accordance with data provision and data use, and including data identifiers in these charging data records, it is possible to perform reward payment processing for users of the data providing device in accordance with the actual performance of data use.
[0014] In this embodiment, the generation of the charging data record may include the generation of a first charging data record including a data identifier of the data provided by the data providing device and an identifier of the data providing device, and the generation of a second charging data record including a data identifier of the data used by the data using device. By generating the first charging data record and the second charging data record in this way, it is possible to provide a reward to the data providing user according to the actual use performance.
[0015] The second charging data record may further include an identifier of the data utilization device. Since the second charging data record includes the identifier of the data utilization device, it is possible to charge the user of the data utilization device for the data utilization.
[0016] A billing data record containing a data identifier of data provided by a data providing device and an identifier of the data providing device can be regarded as a billing data record related to data provision (first billing data record). A billing data record containing a data identifier of data utilized by a data utilizing device (second billing data record) can be regarded as a billing data record related to data utilization. As for the "data identifier of the data provided by the data providing device" (first data identifier) and the "data identifier of the data utilized by the data utilizing device" (second data identifier), as long as the correspondence between the two can be grasped, they can be the same or different. For example, in the case where the data utilizing device directly utilizes the data provided by the data providing device, it is simple if the first data identifier and the second data identifier are the same. In addition, in the case where the data utilizing device utilizes data produced based on the data provided by the data providing device, one or more first data identifiers can be established to correspond to the second data identifier, and the correspondence is recorded in the network node.
[0017] By including the data identifier of the data provided by the data providing device and the identifier of the data providing device in the billing data record, it is possible to perform a reward payment process for the user of the data providing device that provided the data. In addition, by including the data identifier of the data used by the data using device and the identifier of the data using device in the billing data record, it is possible to perform a fee collection process for the user of the data using device that used the data. In addition, due to the existence of both the billing data record related to the provision of data and the billing data record related to the use of data, it is possible to perform a reward payment process corresponding to the actual use performance of the data for the user of the data providing device. In addition, when it is not necessary to perform a fee collection process for the user of the data using device, the identifier of the data using device may not be included in the CDR related to the use of data that is generated when the data is used by the data using device.
[0018] In this method, the data may be sensory data obtained by sensing of the data providing device. The sensory data may be raw data obtained by the data providing device, or data processed by the data providing device or other devices based on the raw data. An example of processed data may include the type, position, size, and moving speed of an object detected by sensing.
[0019] In this method, the data identifier may be an identifier of an object included in the sensor measurement data. The object identifier may be the same identifier assigned to the same object, or the same object may be assigned a different identifier for each measurement instance. The data identifier in the present disclosure may also be regarded as an identifier of the sensor measurement.
[0020] In this method, the billing data request and the billing data record may each include at least one of the importance, reliability, and rarity of the data. By including this information in the billing data record, a larger reward can be paid to a user who provides data with high importance, reliability, or rarity, thereby promoting the provision of data with high importance, reliability, or rarity.
[0021] In this embodiment, the billing data record generated by the network node may be sent from the network node to the billing domain periodically or in response to a request. The billing domain performs at least one of a reward payment process for a user of the data providing device and a data usage fee collection process for a user of the data using device based on the billing data record obtained from the network node.
[0022] Another embodiment of the present disclosure is an information processing system, which includes a network node and a billing domain, characterized in that the network node has a processor, which executes: receiving a charging data request (Charging Data Request); generating a charging data record (Charging Data Record) in response to the receipt of the charging data request; and sending the charging data record to the billing domain, and the billing domain has a processor, which executes: receiving the charging data record; and request processing or payment processing based on the charging data record, the charging data request and the charging data record respectively contain an identifier of data provided by a data providing device (UE) and an identifier of the data providing device, or contain an identifier of data utilized by a data utilizing device and an identifier of the data utilizing device.
[0023] In this aspect, the processor of the billing domain may execute at least one of a request processing for a user of the data providing device and a payment processing for a user of the data utilizing device.
[0024] In this method, the processor of the billing domain may execute: receiving a first billing data record involving data provided by the data providing device, and a second billing data record involving data utilized by the data utilizing device; and performing payment processing on a user of the data providing device who provided the data with the data identifier based on the data identifier contained in the second billing data record.
[0025] In this method, the billing data request and the billing data record may respectively further include at least one of the importance, reliability, and rarity of the data, and in the payment processing, payment is made of an amount corresponding to at least one of the importance, reliability, and rarity of the data.
[0026] Another embodiment of the present disclosure is a method executed by a network node constituting a wireless communication network, characterized in that it includes: receiving a charging data request (Charging Data Request); and generating a charging data record (Charging Data Record) in response to the reception of the charging data request, wherein the charging data request and the charging data record respectively include a data identifier of data provided by a data providing device (UE) and an identifier of the data providing device, or include a data identifier of data utilized by a data utilizing device and an identifier of the data utilizing device.
[0027] The present disclosure also includes a computer program for causing a computer to execute each step of the above method, and a computer program for implementing the above network node or information processing system by a computer. The present disclosure also includes a computer readable medium having the above computer program recorded thereon.
[0028] (Implementation Method 1) Hereinafter, the embodiments of the present disclosure will be described based on the accompanying drawings. The following embodiments are merely examples for explanation, and the present disclosure is not limited to the configuration of the embodiments. For example, the following describes an example in which the present disclosure is applied to a 5th generation mobile communication system, but the present disclosure can be applied to a mobile communication system of the 4th generation or the 5th generation or later. In addition, the present disclosure can also be applied to a mobile communication system specified by other than 3GPP, and can also be applied to any wireless communication system or wired communication system other than a mobile communication system. In addition, it is assumed that the data provided and used by the user terminal is the sensor data measured by the user terminal. However, the data provided and used can also be sensor data measured by a device other than the user terminal, and can also be any data other than the sensor data.
[0029] <Composition of information processing system> Figure 1 The components (constituent elements) constituting the fifth generation mobile communication system (5G network) are shown. Figure 1In the figure, UE (User Equipment) 2 is the terminal of the user (subscriber). RAN (Radio Access Network) 3 is the access network to the 5G core network (5GC). RAN 3 is composed of base stations (gNB). The 5G network has a 5G core network (5GC) and an access network ((R)AN), and the 5G network is connected to UE 2, DN 5, and AF 12. NF 11a~11n are functions implemented by executing programs by one or more computers (information processing devices). However, any two or more of NF11a~11n can also be implemented by a single computer. NF 11a~11n can also be called network nodes or network components.
[0030] 5GC is composed of a collection of components with specified functions called NF (Network Function). Figure 1 In FIG. 1 , the following contents are shown as NF 11 constituting 5GC. Figure 1 It is represented by a thick rectangle.
[0031] UPF (User Plane Function) 11a AMF (Access and Mobility Management Function) 11b SMF (Session Management Function) 11c PCF (Policy Control Function) 11d NEF (Network Exposure Function) 11e NRF (Network Repository Function) 11g NSSF (Network Slice Selection Function) 11h AUSF (Authentication Server Function) 11i UDM (Unified Data Management)11j NWDAF (Network Data Analytics Function) 11k CHF (Charging Function) 11m SENSING (Sensing Function) 11n
[0032] The UPF 11a performs routing and forwarding of user packets (user plane packets sent and received by the UE 2), packet inspection, and QoS processing.
[0033] AMF 11b is an on-network accommodation device for UE in 5GC. AMF 11b accommodates RAN 3 and performs subscriber authentication control, location (mobility) management of UE 2, and the like.
[0034] SMF 11c manages PDU (Protocol Data Unit) sessions and controls UPF 11a to implement QoS (Quality of Service) control and policy control. PDU sessions are virtual communication paths for data exchange between UE 2 and DN (Data Network) 5. DN 5 is a data network (Internet, etc.) outside 5GC.
[0035] PCF 11d performs QoS control, policy control, and billing control under the control of SMF 11c. In QoS control, communication quality control such as packet forwarding priority is performed. In policy control, communication control such as QoS, packet forwarding permission, and billing based on network or subscriber information is performed.
[0036] NEF 11e plays a role of intervening in the communication between external nodes and nodes in the control plane.
[0037] NRF 11g stores and manages information of NFs (such as AMF, SMF, UPF, etc.) within 5GC. NRF 11g can answer multiple NF candidates to the query source in response to the query related to the NF to be used.
[0038] The NSSF 11h has a function of selecting a network slice to be used by a subscriber from among network slices generated by network slicing. A network slice is a virtual network having characteristics according to a usage.
[0039] AUSF 11i is a subscriber authentication server that performs subscriber authentication under the control of AMF 11b.
[0040] UDM 11j stores subscriber-related information, provides subscriber information, or acquires, registers, deletes, and changes the status of UE 2.
[0041] NWDAF 11k has the function of performing the following operations from each NF 11, OAM terminal 8 ( Figure 2 ), external servers, etc. It is a NF that provides analysis information on the network.
[0042] The CHF 11m is a network node having online charging and offline charging functions. The CHF 11m is connected to a NF (network node) having a charging trigger function (CTF). The details of the CHF 11m will be described later.
[0043] SENSING 11n implements sensing services including collecting sensing information from UE 2, RAN 3 (base station (gNB)) or other nodes, and providing the collected sensing information to UE 2 or other external systems (AF 12, DN 5, etc.). Details of SENSING 11n are described later.
[0044] AF 12 is an NF that is part of 5GC and provides application services via NRF 11g, or is an NF that is outside 5GC and provides application services via NEF 11e. AF 12 performs processing using sensor data, for example. As an example, AF 12 generates dynamic map information based on sensor measurement data obtained from SENSING 11. In addition, UE 2 or an application executed by UE 2 may act as AF 12.
[0045] In 5GC, multiple NFs of the same type are sometimes prepared. For example, NF 11 is sometimes prepared for each data center (organization). In addition, one NF 11 is sometimes shared between data centers. In addition, multiple NF 11s of the same type are sometimes configured in one data center. The number of data centers and the number of NF 11 can be appropriately set according to the correspondence between NF 11 and data centers.
[0046] Figure 2 11 is a diagram for explaining CHF 11m in more detail. CHF 11m provides services using the Nchf interface. CTF included in SMF 11c and SENSING 11n can access CHF 11m using the Nchf interface.
[0047] like Figure 2As shown, CHF 11m can communicate with billing domain 13 (BD, requesting device) by using CGF (Charging Gateway Function). In addition, CHF 11m can also be combined with ABMF (Account Balance Management Function) and RF (Rating Function) to form a billing device. Figure 2 In the example, the CGF is included in the billing device, but the CGF may also be included in the billing domain, or may be a network element independent of the billing device and the billing domain.
[0048] SENSING (sensing unit) 11n is a network node having functions of collecting sensory measurement data from UE 2, analyzing and processing the sensory measurement data, and providing the sensory data to AF 12. "Sensor data" in the present disclosure is a term that includes at least one of the sensory measurement data itself received and provided from UE 2, and data based on the sensory measurement data received and provided (for example, data obtained by analyzing the sensory measurement data or the analysis result). SENSING 11n includes CTF (Charging Trigger Function), and CTF requests CHF 11m to generate CDR. SENSING 11n accepts the designation of sensing from, for example, AF 12 of the data request source, a specific NF 11, etc., via NEF 11e, and collects sensor information from the designated monitoring object. Then, SENSING 11n notifies the AF 12, etc., which has accepted the designation, of the collected sensory data. SENSING 11n can collect sensing data from at least one of AF 12 connected to 5GC, RAN 3 (gNB), external server, UE 2, and NF 11 other than the above-mentioned specific NF 11 via NEF 11e. The sensing service based on SENSING 11n can be performed through one of the Subscribe / Notify method and the Request / Response method (the same as the provisions of TS23.288 Chapter 6.1).
[0049] The BD (Billing Domain) 13 is a network node that has a function of performing billing processing. The term "billing" in the present disclosure includes at least one of the granting of incentives (payment of fees) and the collection of fees (charge collection). The BD 13 obtains the CDR from the CHF 11m, and performs billing mediation, billing, and other processing (such as statistical processing).
[0050] <Configuration of Information Processing Device and Terminal> Figure 3A 1 is a diagram showing a configuration example of an information processing device that can operate as NFs 11a to 11k, an OAM terminal, and an external server. Figure 3A In the embodiment, the information processing device 20 can be formed by using a personal computer (PC), a workstation (WS), or a server machine, etc., a dedicated or general-purpose information processing device (computer). Of course, the information processing device 20 can also be a collection of one or more computers (cloud).
[0051] The information processing device 20 includes a processor 21 as a processing unit or a control unit (controller), a storage device 22 , a communication interface 23 (communication IF 23 ), an input device 24 , and a display 25 , which are connected to each other via a bus 26 .
[0052] The storage device 22 includes a main storage device and an auxiliary storage device. The main storage device is used as at least one of a storage area for programs and data, a program expansion area, a program operation area, and a buffer area for communication data. The main storage device is composed of a RAM (Random Access Memory) or a combination of RAM and ROM (Read Only Memory). The auxiliary storage device is used as a storage area for data and programs. In the auxiliary storage device, a non-volatile storage medium is applied. Non-volatile storage media are, for example, hard disks, Solid State Drives (SSDs), flash memories, or EEPROMs (Electrically Erasable Programmable Read-Only Memory). In addition, the storage device 22 may include a drive device for a disk recording medium.
[0053] The communication IF 23 is a circuit that performs communication processing. For example, the communication IF 23 is a network interface card (NIC). In addition, the communication IF 23 may also be a wireless communication circuit that performs wireless communication (5G, wireless LAN (Wi-Fi (registered trademark)), BLE, etc.). In addition, the communication IF 23 may also be a combination of a circuit that performs wired communication processing and a wireless communication circuit.
[0054] The input device 24 includes keys, buttons, a pointing device, and a touch panel, etc., and is used to input information. The display 25 is, for example, a liquid crystal display, etc., and displays information and data.
[0055] The processor 21 performs various processes by executing various programs stored in the storage device 22. When the processor 21 executes the programs stored in the storage device 22, the information processing device 20 can operate as the NFs 11a to 11k, the OAM terminal 8, and the external servers 12a and 12b.
[0056] Figure 3B 4 is a diagram showing a configuration example of a terminal 40 that can operate as a UE 2. The terminal 40 includes a processor 41, a storage device 42, a communication interface 43 (communication IF 43), an input device 44, and a display 45 that are connected to each other via a bus 46. The processor 41, the storage device 42, the communication IF 43, the input device 44, and the display 45 can use the same devices as the processor 21, the storage device 22, the communication IF 23, the input device 24, and the display 25. Therefore, their description is omitted.
[0057] Processors 21 and 41 are, for example, Central Processing Units (CPU). CPU is also called Microprocessor Unit (MPU). Processors 21 and 41 may be composed of a single processor or multiple processors. In addition, a single physical CPU connected through a single socket may also have a multi-core structure. Processors 21 and 41 may also include computing devices composed of various circuits such as Digital Signal Processor (DSP) or Graphics Processing Unit (GPU). In addition, processors 21 and 41 may also have a structure that cooperates with at least one of an integrated circuit (IC), other digital circuits, and analog circuits. Integrated circuits include LSI, Application Specific Integrated Circuit (ASIC), and programmable logic devices (PLD). PLD includes, for example, Field-Programmable Gate Array (FPGA). Processors 21 and 41 also include, for example, so-called microcontrollers (MCU), SoC (System-on-a-chip), system LSI, or chip sets.
[0058] <Action example: Data collection and provision processing> Figure 4A to Figure 4B 1 is a sequence diagram showing an example of actions related to the collection and provision of sensor data in the method disclosed in the present invention. In addition, the sequence diagram shown here is only an example, and may include processes other than those shown in the diagram, may omit part of the processes shown in the diagram, and may change the execution order of the processes shown in the diagram. Figure 4A to Figure 4B In the example of data provision based on Subscribe / Notify method, data provision can also be performed using Request / Response method. Figure 4A to Figure 4B In this paper, offline charging is taken as a prerequisite, but online charging can also be used.
[0059] In this operation example, the UE 2 that transmits the sensing data to the SENSING 11n is an example of a “data providing device”, and the AF 12 that receives the sensing data from the SENSING 11n is an example of a “data utilizing device”.
[0060] In steps S12 to S14, AF 12 using sensor data subscribes to the sensor data for SENSING 11n via NEF 11e. The subscription message contains an identifier for identifying AF 12 and parameters for the sensor data of the subscription object. The identifier (AFID) of AF 12 (external server) is used as an identifier (UEID) for identifying the data user (subscriber) in the data collection and provision process. The parameters for the sensor measurement data used to identify the subscription object can be expressed as conditions related to the type of object, location, moving speed, size, etc. The subscription message from AF 12 is sent to SENSING 11n via NEF 11e. Figure 4A In the example, the parameters included in the subscription message in S12 to S14 are set to be the same, but for example, the NEF 11e may change the parameters included in the subscription message.
[0061] In step S16, the user terminal 2 providing the sensing data transmits the sensing data to the SENSING 11n. The data transmission message includes the identifier of the UE 2 and the sensing data. Here, the sensing data may be raw data of the sensing performed by the UE 2 or data processed from the raw data.
[0062] In step S18, SENSING 11n performs data processing on the sensory measurement data obtained from UE 2. An example of data processing is a process of identifying the object of sensory measurement contained in the sensory measurement data. The identification of the object includes object recognition (identification of the type of object), position determination, size determination, movement speed determination, etc. SENSING 11n also obtains an object identifier (Object ID) of the identified object contained in the sensory measurement data. For example, whenever SENSING 11n obtains sensory measurement data, it assigns a unique identifier to the object obtained based on the sensory measurement data.
[0063] In addition, SENSING 11n can also find the reliability of object recognition. Object recognition can typically be performed using a learning model (object recognition means) obtained through machine learning, and the learning model outputs the result of object recognition and the reliability of the result. The reliability output from the learning model or the value based on the reliability is equivalent to the reliability of the above-mentioned object recognition. In addition, SENSING 11n can also find the rarity (rarity, scarcity) of the sensor measurement data. Rarity can be determined from various aspects. As an example, the rarity of an object with a lower frequency of occurrence or detection is determined to be higher, and the rarity of sensor measurement data at a location and / or time period with a lower number or frequency of sensor measurement data is determined to be higher. For example, SENSING 11n collects the types of objects contained in the sensor measurement data obtained so far, the location and / or time period of the measurement object, etc., and calculates the rarity of each sensor data according to the number of data or the frequency of occurrence. In addition, SENSING 11n can also find the importance of sensor data. The importance may be determined by combining the reliability and the rarity, for example, as an average or a total, or may be determined based on other criteria.
[0064] The SENSING 11n stores the result of the data processing in the storage device.
[0065] In step S20, SENSING 11n sends a charging data request (Charging Data Request) to CHF 11m. The charging data request includes information that can determine that the charging data request is associated with data provision. The charging data request includes the identifier of UE 2 that provides data, the reliability of the sensing data, and the identifier of the object included in the sensing data.
[0066] In step S22, the CHF 11m generates a charging data record (CDR) in response to receiving the charging data request. The CDR contains information that can determine that the CDR is associated with the data provided by the UE 2. The CDR contains the identifier of the UE 2 that provided the data, the reliability of the sensor data, and the identifier of the object included in the sensor data. The generated CDR is stored in the storage device in the CHF 11m.
[0067] In step S24, the CHF 11m transmits a notification (Charging Answer) indicating that the generation of the CDR is completed to the SENSING 11n.
[0068] In step S26, SENSING 11n sends the sensing data to NEF 11e (Notification). The processing of step S26 is performed in response to SENSING 11n obtaining the sensing data of the object to which the subscription is applied from NEF 11e. The Notification message includes the object identifier, the reliability of the sensing data, and the sensing data. As a substitute or supplement to the sensing measurement data provided by UE 2, the sensing data sent to NEF 11e can also be the result of data processing by SENSING 11n.
[0069] In step S28, the NEF 11e sends a charging data request (Charging Data Request) to the CHF 11m. The charging data request includes the identifier of the AF 12 as the data provision target (subscriber), the reliability of the sensing data, and the identifier of the object included in the sensing data.
[0070] In step S30, the CHF 11m generates a charging data record (CDR) in response to receiving the charging data request. The CDR includes information that can be used to identify the association between the CDR and the use of data by the AF 12. The CDR includes an identifier of the AF 12 as a data provision target, the reliability of the sensing data, and an identifier of an object included in the sensing data. The generated CDR is stored in a storage device in the CHF 11m.
[0071] The CDR includes the identifier of the AF 12 to which the data is provided in order to charge the user of the AF 12. If the user of the AF 12 is not charged, it is not necessary to identify the user who used the data, so the data use CDR may not include the user identifier.
[0072] In step S32, the CHF 11m transmits a notification (Charging Answer) to the SENSING 11n indicating that the generation of the CDR has been completed.
[0073] In step S34, the NEF sends the sensing data to the AF 12 (API Notification). The message contains at least the sensing data.
[0074] In step S36, the AF 12 transmits a notification (Notification Acknowledge) to the NEF indicating that the sensing data has been received.
[0075] <Action Example: Billing Processing> Figure 5This is a flowchart showing the flow of a billing process related to provision and utilization of sensing measurement data, which is executed by the BD (Billing Domain; billing device) 13 . Figure 5 The example is a flowchart of a billing process in which an incentive payment amount to a user of a data providing UE is determined according to actual data usage performance.
[0076] In step S51 , the BD 13 acquires the CDR from the CHF 11m. The provision of the CDR from the CHF 11m to the BD 13 , in other words, the reception of the CDR from the CHF 11m by the BD 13 may be performed periodically or based on a transmission request from the BD 13 .
[0077] The following processing from step S52 onwards is performed for each acquired CDR.
[0078] In step S52, the BD 13 determines whether the CDR is related to data utilization. If the CDR is related to data utilization, the process proceeds to step S54. Hereinafter, for the sake of explanation, the CDR related to data utilization is also referred to as data utilization CDR.
[0079] In step S53, the BD 13 identifies a CDR having the same object identifier (Object ID) as the object identifier (Object ID) included in the CDR currently being processed from the already acquired CDRs. Hereinafter, for the sake of explanation, the CDR related to data provision is also referred to as a data provision CDR. By identifying the data provision CDR, it is possible to grasp the UE 2 that provides the data used by the AF 12 (or the data used in its processing). In addition, instead of searching for the corresponding data provision CDR from the already acquired CDRs, the BD 13 may also inquire the CHF 11m at this point in time to acquire the corresponding CDR.
[0080] In step S54, BD 13 calculates the payment amount for UE 2 that provides data. The payment amount can be determined, for example, in accordance with the reliability of the provided sensor data, specifically, the reliability contained in the data provision CDR. The payment amount can also be determined based on other parameters such as the importance and rarity of the sensor data. In addition, the payment amount can also be determined based on the contribution of UE 2 in the provision of data to AF 12. The contribution of UE 2 can be determined, for example, based on the contribution ratio of the data provided by UE 2 in the data used in the production of the data provided to AF 12. The contribution ratio can be determined as the ratio of the sensor data based on UE 2 to the sensor data used in the data production. The ratio can be either a ratio based on a simple quantity or a weighted ratio (weighted ratio) using a weight based on at least any one of reliability, rarity, and importance.
[0081] In step S55, the BD 13 calculates the amount charged to the user of the AF 12 who has used the data. The amount charged may be determined according to the reliability of the sensing data, or may be a fixed amount, for example.
[0082] In step S56 , the BD 13 performs payment processing for the UE 2 and claim processing for the AF 12 .
[0083] In addition, the amount of reward payment may also be determined by steps other than those described above. For example, a reward may be paid regardless of data utilization performance as long as the provided data meets a prescribed benchmark. In this case, the amount of payment may be a fixed amount or a variable amount depending on the degree of compliance with the benchmark.
[0084] <Advantageous Effects of the Present Embodiment> According to this embodiment, by storing the object identifier in the CDR related to the provision and use of the sensory measurement data, the data utilization performance is associated with the UE that provided the sensory data. Therefore, it is possible to make a reward payment to the data providing UE (UE 2) according to the utilization performance of the sensory data. In addition, by determining the reward amount (payment amount) according to the reliability of the sensory measurement data, the user of UE 2 is more motivated to provide sensory measurement data with higher reliability.
[0085] According to the above, more and more reliable sensing measurement data are provided from the user terminal. By obtaining more and more reliable sensing measurement data, more useful services can be provided to the AF 12, which also helps to improve the convenience of users who use the services.
[0086] <Other Modifications> The above-described embodiment is ultimately just an example, and the present disclosure can be implemented with appropriate changes without departing from the gist of the disclosure.
[0087] In the above embodiment, the data provided and used by the user terminal is sensor data measured by the user terminal, but the data provided and used may be sensor data measured by a device other than the user terminal, or may be any data other than sensor data.
[0088] In the above-mentioned embodiment, data provision to the user terminal is performed by the Subscribe / Notify method, but it may be performed by the Request / Response method.
[0089] In the above embodiment, rewards are given for data provision and fees are charged for data use, but fees for data use may not be charged. In the case where fees for data use are not charged, the generation of CDR related to data use (step S30) may not be performed, but CDR related to data use may be generated in order to give rewards corresponding to data use performance. If only rewards corresponding to data use performance are given, it is not necessary to identify the user terminal that uses the data, so the data use CDR may not include the identifier of the second user terminal.
[0090] The present disclosure can also be implemented by providing a computer program that implements the functions described in the above embodiments to a computer and causing one or more processors of the computer to read out and execute the program. Such a computer program can be provided to the computer via a non-temporary computer-readable storage medium that can be connected to the system bus of the computer, or it can be provided to the computer via a network. Non-temporary computer-readable storage media include, for example, any type of disk (floppy disk (registered trademark), hard disk drive (HDD)), optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic card, flash memory, optical card, and any type of medium suitable for storing electronic instructions.
Claims
1. A network node, which constitutes a wireless communication network, characterized in that: A processor is provided, the processor being configured to execute: receiving a request for billing data; and generating a billing data record in response to receipt of the billing data request, The charging data record contains a data identifier of the data provided by the data providing device.
2. The network node according to claim 1, characterized in that Generating the billing data record includes: generating a first charging data record comprising a data identifier of the data provided by the data providing device and an identifier of the data providing device; and A second charging data record is generated that includes a data identifier of the data utilized by the data utilization device.
3. The network node according to claim 2, characterized in that: The second charging data record also contains an identifier of the data utilizing device.
4. The network node according to claim 1, characterized in that: The data is sensing data obtained by sensing measurement performed by the data providing device.
5. The network node according to claim 4, characterized in that: The data identifier is an identifier of an object determined based on the sensor data.
6. The network node according to claim 1, characterized in that: The billing data request and the billing data record each further include the importance of the data.
7. The network node according to claim 1, characterized in that: The billing data request and the billing data record each further include the reliability of the data.
8. The network node according to claim 1, characterized in that: The charging data request and the charging data record each further include the rarity of the data.
9. The network node according to claim 1, characterized in that: The processor is configured to send the billing data record to a billing domain periodically or in response to a request.
10. An information processing system, characterized in that: have: Network nodes; and Billing domain, in, The network node has a first processor, wherein the first processor is configured to: receiving a request for billing data; generating a billing data record in response to receipt of the billing data request; and sending the billing data record to the billing domain, The billing domain has a second processor configured to execute: receiving and processing said charging data record; and Request processing or payment processing based on the billing data record, The charging data record contains a data identifier of the data provided by the data providing device.
11. The information processing system according to claim 10, characterized in that: Generating the billing data record includes: generating a first charging data record comprising a data identifier of the data provided by the data providing device and an identifier of the data providing device; and A second charging data record is generated that includes a data identifier of the data utilized by the data utilization device.
12. The information processing system according to claim 11, characterized in that: The second charging data record also contains an identifier of the data utilizing device.
13. The information processing system according to claim 10, characterized in that: The second processor of the billing domain is configured to perform payment processing for a user of the data providing device.
14. The information processing system according to claim 13, characterized in that: The second processor of the billing domain is configured to execute: receiving a first charging data record related to data provided by the data providing device and receiving a second charging data record related to data utilized by the data utilizing device; as well as Based on the data identifier included in the second charging data record, payment processing is performed for a user of the data providing device who provided data of the data identifier.
15. The information processing system according to claim 14, characterized in that: The billing data request and the billing data record each further include at least one of the importance, reliability, and rarity of the data, In the payment process, payment is made of an amount corresponding to at least one of the importance, reliability, and rarity of the data.
16. An information processing method, which is executed by a network node constituting a wireless communication network, characterized in that: include: receiving a request for billing data; as well as generating a billing data record in response to receipt of the billing data request, The charging data record contains a data identifier of the data provided by the data providing device. 17 . A non-transitory storage medium storing a command executable by a computer and causing the computer to execute the method according to claim 16 .
