Network node and communication method

Abstract

This network node comprises: a reception unit that receives, from a first network node different from the network node, a first message including identification information about an application function for requesting the use of an IoT service involving wireless communication with one or more terminals; and a transmission unit that transmits, to a second network node different from the network node on the basis of the first message, a second message pertaining to charging for the use of the IoT service. The transmission unit transmits the second message including the identification information about the application function as information indicating a to-be-charged object.

Description

Network Node and Communication Method

[0001] The present disclosure relates to a network node and a communication method for use in a wireless communication system.

[0002] In 3GPP (registered trademark, the same applies hereinafter) (3rd Generation Partnership Project), which is a standardization project for wireless communication systems, the implementation of services using ambient power-enabled terminals is being studied (see, for example, Non-Patent Document 1). Such technology is referred to as AIoT (Ambient Internet of Things), and such terminals are referred to as AIoT devices or AIoT terminals.

[0003] An AIoT terminal may be a terminal supplied with power by energy harvesting. An AIoT terminal is batteryless or has limited energy storage capacity (e.g., a capacitor), and can be supplied with energy by harvesting radio waves, light, motion, heat, or any other suitable power source.

[0004] Compared with IoT technologies already introduced in 3GPP standards, such as NB-IoT (Narrow Band Internet of Things) and eMTC (enhanced Machine-Type Communication), AIoT technology can realize terminals with low complexity, small size, low capability, and low power consumption. AIoT terminals may be maintenance-free and have a long service life.

[0005] 3GPP Technical Specification "3GPP TS 22.369 V19.3.0 (2024-09)", 3GPP Technical Specification "3GPP TS 32.240 V19.2.0 (2024-12)", 3GPP Technical Specification "3GPP TS 32.291 V19.1.0 (2024-12)", 3GPP Technical Specification "3GPP TS 32.295 V18.0.0 (2024-04)"

[0006] AIoT services using AIoT devices in wireless communication systems are a new type of service, and it is desirable to realize a method for appropriately billing for the use of AIoT services.

[0007] Therefore, this disclosure provides a network node and a communication method that enable appropriate billing for the use of IoT services in a wireless communication system.

[0008] According to the technology of this disclosure, a network node is provided which includes a receiving unit that receives a first message from a first network node different from the network node, the first message containing identification information of an application function that requests the use of an IoT service involving wireless communication with one or more terminals, and a transmitting unit that transmits a second message concerning billing for the use of the IoT service to a second network node different from the network node, based on the first message, wherein the transmitting unit transmits the second message containing identification information of the application function as information indicating the subject of the billing.

[0009] Furthermore, the technology of this disclosure provides a communication method performed by a network node, comprising: receiving a first message from a first network node different from the network node, which includes identification information of an application function requesting the use of an IoT service involving wireless communication with one or more terminals; and transmitting a second message to a second network node different from the network node, based on the first message, regarding billing for the use of the IoT service, wherein the network node transmits the second message, which includes identification information of the application function, as information indicating the subject of the billing.

[0010] This figure shows an example configuration of a wireless communication system according to the embodiment. This figure illustrates inventory operation in the wireless communication system according to the embodiment. This figure illustrates an example of existing billing operation for UE as a comparative example. This figure illustrates billing operation for the use of AIoT service according to the embodiment. This figure shows an example configuration of AIoTF according to the embodiment. This figure shows an example configuration of CHF according to the embodiment. This figure shows the first embodiment. This figure shows the second embodiment. This figure shows the third embodiment. This figure shows the fourth embodiment. This figure shows an example hardware configuration of each communication entity according to the embodiment. This figure shows an example configuration of a vehicle according to the embodiment.

[0011] The wireless communication system according to an embodiment will be described below with reference to the drawings.

[0012] Existing technologies will be used as appropriate in the operation of the wireless communication system. Existing technologies include, for example, existing communication methods based on the 3GPP standard, such as 5G / NR (New Radio). Existing technologies are not limited to 5G / NR, but may also include methods such as 4G / LTE (Long Term Evolution) and LTE-Advanced, as well as wireless LAN (Local Area Network).

[0013] The embodiments described below are examples and are not limited to those embodiments. For example, the following embodiments mainly describe a wireless communication system having an AIoT device (also referred to as the "AIoT system"), but the wireless communication system may have other IoT devices (e.g., NB-IoT devices and / or eMTC devices, etc.) in place of, or in addition to, the AIoT device.

[0014] In other words, the wireless communication system of this disclosure is applicable not only to AIoT devices but also to other IoT devices. In the following description of embodiments, the term "AIoT device" may be used interchangeably with the term "IoT device" or the term "terminal."

[0015] (1) Example of System Configuration First, the configuration of the wireless communication system according to this embodiment will be described. Figure 1 is a diagram showing an example of the configuration of the wireless communication system according to this embodiment.

[0016] As shown in Figure 1, the wireless communication system according to this embodiment includes a network (NW) 1, a UE (User Equipment) 2, and an AIoT device 3. The wireless communication system according to this embodiment may be a 5GS (5G System) or may be called an AIoT system. NW1 may be a 5G network or a 6G network, but in the following description of the embodiments, we will mainly assume that NW1 is a 5G network.

[0017] The elements that constitute NW1 are called network nodes. The term "network node" can be used interchangeably with the term "NF (Network Function)". Network nodes may be logically configured entities or physically configured entities. Hereinafter, one network node will be assigned to each function, but one network node may implement multiple functions, or multiple network nodes may implement one function. Network nodes may be composed of one or more computers. Note that the "connection" described below may be a logical connection or a physical connection.

[0018] NW1 includes an AF (Application Function) 11, a CN (Core Network) 12, a RAN (Radio Access Network) 13, a Billing System 14, and an OAM (Operations, Administration and Maintenance) 15.

[0019] AF11 is a network node that has the function of controlling applications. AF11 is connected to CN12. AF11 may also be an external node located outside CN12, for example, an external application server. In this embodiment, AF11 uses an AIoT service provided by CN12, which involves wireless communication with one or more AIoT devices 3. In the illustrated example, there is one AF11, but there may be multiple AF11s. Multiple AF11s may correspond one-to-one with multiple operators (multiple users, multiple customers).

[0020] CN12 is the network portion that provides functions such as connectivity between subscribers (users) and external networks, management of network resources, mobility management, security, and charging. CN12 may also be a 5GC (5G Core Network). Network nodes included in CN12 may be referred to as CN nodes.

[0021] In this embodiment, CN12 includes a Network Exposure Function (NEF) 12a, an AIoT Function (AIoTTF) 12b, an AIoT Data Management (AIoTTDM) 12c, a Charging Function (CHF) 12d, and an Access and Mobility Management Function (AMF) 12e.

[0022] NEF12a is a network node that has the function of providing authorized AF11s with a means to access CN12. NEF12a mediates communication between AF11 and CN nodes (e.g., AIOTF12b). However, CN12 does not necessarily have to have NEF12a. For example, if AIOTF12b also performs authentication of AF11, communication between AF11 and AIOTF12b may occur without going through NEF12a.

[0023] The AIoTF 12b is a network node that provides functions for managing and controlling AIoT services using the AIoT device 3. The AIoTF 12b may be integrated with the AMF 12e. Such an AMF 12e may be an AMF dedicated to AIoT services. Alternatively, the AIoTF 12b may be a separate network node from the AMF 12e and communicate with the RAN 13 via the AMF 12e. The AIoTF 12b communicates regarding AIoT services with a reader device, which is a device that performs wireless communication with the AIoT device 3. The reader device is a base station 13a or UE2. As will be described in detail later, in this embodiment, the AIoTF 12b has a function to trigger (start) the billing procedure (billing operation) for the use of AIoT services.

[0024] AIoTDM12c is a network node that provides the function of managing data related to AIoT services. For example, AIoTDM12c may function as a front-end for a UDR (User Data Repository) and provide an interface with other network nodes. A UDR is a network node that provides the function of storing data about subscribers (users). AIoTDM12c may mediate communication between AIoTF12b and the UDR. However, CN12 does not necessarily have to have AIoTDM12c. For example, if a dedicated UDR is provided for an AIoT service, communication between AIoTF12b and the UDR may occur without going through AIoTDM12c.

[0025] CHF12d is a network node that has the function of performing billing processing. CHF12d may also have the function of collecting, processing, and transmitting billing information. CHF12d may support various types of billing, such as offline billing and / or online billing as described later. CHF12d may collect information on service usage from other network nodes, convert the collected information into billing data that is easy for the billing system 14 to process, such as in the format of a CDR (Charging Data Record), and transmit the billing data to the billing system 14. A CDR is a formatted representation of information on billed events and sessions, such as call duration and / or data transfer volume, and is used for billing and accounting processing.

[0026] The AMF12e is a network node that has functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and terminal mobility management.

[0027] RAN13 is the network portion that provides wireless communication to UE2 and AIoT device 3. RAN13 manages and allocates wireless resources and communicates wirelessly with UE2 and AIoT device 3 via a wireless interface. RAN13 may also be an NG (Next Generation)-RAN in 5G. Network nodes included in RAN13 may be referred to as RAN nodes.

[0028] RAN13 has a plurality of base stations 13a and 13b. In the illustrated example, RAN13 has a base station 13a that operates as a reader device and a base station 13b that performs wireless communication with UE2 which also operates as a reader device. The reader device is a device capable of performing wireless communication with the AIoT device 3.

[0029] Base station 13a performs wireless communication with AIoT device 3a. UE2 performs wireless communication with AIoT device 3b. Base station 13a, which operates as a reader device, is referred to as a RAN reader, and UE2, which operates as a reader device, is referred to as a UE reader. The air interface between the reader device and AIoT device 3 is referred to as an AIoT air interface. In this embodiment, RAN 13 may be an AIoT-dedicated RAN specialized for AIoT services.

[0030] The billing system 14 is a network node that has the function of processing billing. The billing system 14 may also have the function of processing billing data, creating invoices (billing statements), and collecting payments. For example, the billing system 14 may receive billing data transmitted from CHF 12d, process the billing data based on the user's contract information and / or rate plan to calculate the billing amount, create an invoice for the user based on the billing amount, and process the collection of payments from the user. In the illustrated example, the billing system 14 is located outside of CN 12, but the billing system 14 may constitute part of CN 12.

[0031] OAM15 is a network node that has the functions of operating, managing, and maintaining NW1. For example, CN12 and RAN13 are networks belonging to a certain telecommunications carrier (also referred to as "operator"), and OAM15 may also be a network node belonging to that telecommunications carrier.

[0032] UE2 is a terminal such as a smartphone, mobile phone, tablet, wearable device, or communication module. The UE2, which is a reader device, may be a terminal dedicated to being a reader device. In this embodiment, UE2 performs wireless communication with the base station 13b and wireless communication with the AIoT device 3b.

[0033] The AIoT device 3 is an energy harvesting-enabled device. The AIoT device 3 may be a device that is powered by energy harvesting. The AIoT device 3 is battery-less or has limited energy storage capacity (e.g., a capacitor) and may be powered by harvesting radio waves, light, motion, heat, or any other suitable power source.

[0034] The AIoT device 3 may be less complex, smaller, less powerful, and consume less power compared to IoT devices already introduced under the 3GPP standard, such as NB-IoT devices and eMTC devices. The AIoT device 3 may be maintenance-free and may have a long lifespan (e.g., 10 years or more). The AIoT device 3 may be installed to blend into its surrounding environment.

[0035] One use case for AIoT device 3 is inventory management. In this use case, for example, it is expected that the status of goods and materials will be understood in real time based on identification information (device ID), status information (which may include location information), and / or measured values ​​(sensor information) transmitted by AIoT device 3 in a warehouse or store. For such inventory management, the "Inventory" function in the AIoT service is used. Inventory is a function that manages AIoT device 3.

[0036] For example, the AIoT device 3 may be attached to an article, in particular to a product. Here, "the AIoT device is attached to a product" means that the AIoT device 3 is attached to the product directly or indirectly. Direct attachment of the AIoT device 3 to a product means that the AIoT device 3 may be incorporated into the product, or the AIoT device 3 may be attached to the product. Indirect attachment of the AIoT device 3 to a product means that the AIoT device 3 may be attached to the product via a string or the like, or the AIoT device 3 may be attached to the product's packaging.

[0037] Furthermore, while the following three categories ("A" to "C") have been considered for the AIoT device 3, the AIoT device 3 according to this embodiment may belong to any of these categories.

[0038] Device "A": It lacks energy storage capabilities and independent signal generation / amplification functions. In other words, it performs RF (Radio Frequency) transmission using backscatter. In backscatter transmission, AIoT device 3 transmits information to the reader device by reflecting radio waves received from the reader device and changing the reflection pattern of the radio waves.

[0039] Device "B": It has an energy storage function but no independent signal generation function. In other words, it performs RF transmission using backscatter. It is possible to amplify the reflected signal using the stored energy.

[0040] Device "C": It has energy storage capabilities and independent signal generation capabilities. In other words, it has an active RF component for transmission, enabling active transmission rather than RF reflection.

[0041] Furthermore, the operation of communicating with the AIoT device 3 is also referred to as an "AIoT operation." In addition, examples of AIoT service types include "inventory" and "command."

[0042] • Inventory: The inventory allows for the extraction and / or discovery of one or more AIoT devices 3. The inventory also allows for the detection of AIoT devices 3 present around the reader device and the collection of their information. Unlike UE2, AIoT devices 3 are not always connected to NW1. The inventory function allows NW1 to acquire information about AIoT devices 3 (device ID, status, measured values, etc.) at the necessary time.

[0043] Figure 2 is a diagram illustrating the inventory operation in the wireless communication system according to this embodiment. As shown in Figure 2, the inventory is performed, for example, in the following steps 1) to 4).

[0044] 1) Trigger: CN12 instructs the reader device to start an inventory. For example, CN12 transmits an inventory request to the reader device (in the illustrated example, base stations 13#1 to 13#3 selected as reader devices). CN12 may start the inventory in response to an AIoT service request from AF11. Each of the AIoT service request and the inventory request may include the device ID of each AIoT device 3 targeted for inventory.

[0045] 2) Broadcasting of a paging message by the reader device: The reader device broadcasts a paging message including information (device ID) for identifying the AIoT devices 3 targeted for inventory. Such a paging message may also be referred to as a broadcast message, an inventory request, or an inventory message.

[0046] 3) Response from AIoT devices 3: Each AIoT device 3 matching the broadcast identification information (device ID) responds to the reader device, for example, via random access.

[0047] 4) Information collection: The reader device collects necessary information from the AIoT devices 3 that have responded, and provides the collected information to CN12. CN12 may provide the collected information to AF11.

[0048] Through such an inventory, it may be possible to detect and identify AIoT devices 3. For example, it is possible to grasp what devices are present in an area and identify each AIoT device 3. Furthermore, the inventory may make it possible to monitor device states (such as operating status, remaining battery level, etc.) and collect data (such as sensing data, etc.).

[0049] Commands: Commands can be used to read, write, control, disable, and / or enable one or more AIoT devices 3. Examples of commands include the Read command for reading and the Write command for writing.

[0050] Furthermore, in addition to "Inventory" and "Command," the AIoT service type may also include "Device Selection." "Device Selection" allows for the selection of the appropriate AIoT device 3 to perform a specific task when a large number of AIoT devices 3 exist.

[0051] The device ID, which is the identifier of the AIoT device 3, can be any information that uniquely identifies the AIoT device 3, such as an EPC (Electronic Product Code), MAC address, or serial number. Such a device ID is an identifier unique to the AIoT device 3 (i.e., a fixed identifier) ​​and is called a permanent identifier. If the AIoT device 3 can implement a SIM (Subscriber Identity Module) card or eSIM, the device ID of the AIoT device 3 may be a SUCI (Subscriber Concealed Identifier) ​​or SUPI (Subscription Permanent Identifier).

[0052] Furthermore, there are two topologies (Topology 1 and Topology 2) for the connection between the AIoT device 3 and the NW1.

[0053] As shown in Figure 1, in the architecture of topology 1, the AIoT device 3a is connected to CN 12 via a base station 13a, which is a RAN node. The base station 13a is an AIoT-enabled base station that supports the AIoT air interface, and may be, for example, an AIoT-specific base station (AIoT-specific gNB). In other words, in topology 1, the base station 13a functions as a leader device.

[0054] In the Topology 2 architecture, the AIoT device 3b is connected to the CN 12 via the UE2 and base station 13b. The UE2 is an AIoT-enabled UE that supports the AIoT air interface. In other words, in Topology 2, the UE2 functions as a leader device.

[0055] In the architectures of Topologies 1 and 2, the interface of the AIoT device 3 is the same. The AIoT device 3 is a small device, such as an IC tag in RFID (Radio Frequency Identification), and does not necessarily have to be able to accommodate a UICC (Universal Integrated Circuit Card), such as a USIM (Universal Subscriber Identity Module) and / or a SIM (Subscriber Identity Module). Furthermore, the AIoT device 3 may be a simple device that does not implement an eSIM.

[0056] (2) Example of billing operation Next, the billing operation in the wireless communication system according to this embodiment will be described.

[0057] Existing billing methods in wireless communication systems are basically designed with UE (User Engineer) in mind and do not take AIoT devices 3 (AIoT services) into consideration.

[0058] Existing billing methods include, for example, offline billing, which collects billing information after service use and processes billing retrospectively; online billing, which collects billing information in real time while the service is being used and processes billing immediately; and converged billing, which combines these two methods (see Non-Patent Documents 2-4).

[0059] Furthermore, existing billing methods include event-based billing, which generates billing information based on the occurrence of specific billable events, and session-based billing, which generates billing information related to sessions during service use (see Non-Patent Documents 2-4).

[0060] Figure 3 is a diagram illustrating an example of existing billing behavior for UE4 as a comparative example. Here, we will explain the behavior using session-based billing.

[0061] As shown in Figure 3, in step S1, UE4 sends a registration request message to AMF12e. NAS (Non-Access Stratum) signaling is used as the signaling between UE4 and AMF12e.

[0062] In step S2, the AMF12e processes the registration request message and allocates resources (e.g., authentication, mobility parameters, etc.) for the UE4.

[0063] In step S3, the AMF12e sends a registration response message to the UE4.

[0064] In step S4, UE4 sends a session establishment request to AMF12e. Based on the session establishment request, AMF12e checks whether the session needs to be charged. Note that a network node other than AMF12e that receives the session establishment request may also perform the above check and cooperate with CHF12d as described below.

[0065] If the session requires billing, in step S5, AMF12e sends a billing request message to CHF12d.

[0066] In step S6, CHF12d initiates session-based billing processing based on predefined billing rules in response to a billing request message. CHF12d may also consider the type of service, the UE4 subscription plan, and usage thresholds.

[0067] In step S7, CHF12d sends a billing response message to AMF12e.

[0068] In step S8, AMF12e periodically sends a billing update to CHF12d if resource usage changes or if real-time billing adjustments are required. For example, if UE4 starts using more bandwidth or switches to a different network slice, AMF12e sends an updated billing request to CHF12d, and CHF12d calculates the new bill.

[0069] In step S9, AMF12e sends a final billing request message to CHF12d at the end of the session, which includes information on the total resource usage.

[0070] In step S10, CHF12d generates the final billing data (e.g., the total amount charged for services based on usage).

[0071] In step S11, CHF12d transmits the billing data (CDR) to the billing system 14.

[0072] In step S12, AMF12e sends a session termination message to CHF12d.

[0073] Thus, in existing billing operations for UE4, it is common to bill for individual UE4, for example, individual sessions. However, in AIoT services, a large number of AIoT devices 3 can be accommodated on NW1. Also, as shown in the inventory operation in Figure 2, a large number of AIoT devices 3 can be the target of AIoT services.

[0074] Therefore, when billing is performed on a per-AIIoT device 3 basis or per-session basis for AIIoT device 3, there is a problem in that the load on NW1 increases, for example, by generating a large amount of billing data (CDR). AIIoT services using AIIoT device 3 are new services, and it is desirable to realize a method for appropriately billing for the use of AIIoT services.

[0075] Figure 4 is a diagram illustrating the billing operation for the use of the AIoT service according to this embodiment. Here, we assume a scenario in which the operator's NW1 (particularly CN12) provides the AIoT service to the user (customer, business operator).

[0076] The user (customer, business operator) requests the CN12 to use AIoT services such as inventory and / or commands for the AIoT device 3 from the corresponding AF11. As described above, the inventory provides identification information for the AIoT device 3, and the commands may include read and / or write operations. The CN12 and RAN13 communicate with the AIoT device 3 using the operator's licensed frequency band (Licensed Spectrum) and execute the AIoT services.

[0077] AIoT device 3 is a low-complexity device that can provide small amounts of data and does not necessarily establish a session with NW1. Therefore, it is inappropriate to apply session-based billing to AIoT services.

[0078] Therefore, in this embodiment, event-based billing, rather than session-based billing, is applied to the AIoT service. Such event-based billing is triggered (started) by the AIoTTF 12b. In other words, the AIoTTF 12b in this embodiment has a billing trigger function.

[0079] Furthermore, in this embodiment, CN12 does not charge on an AIoT device 3 basis, but rather on an AF11 basis, that is, on a user (customer, business) basis. For example, when AF11 requests CN12 to use AIoT services for a large number of AIoT devices 3, CN12 charges AF11 rather than individual AIoT devices 3.

[0080] As a result, CN12 no longer needs to generate individual billing data (CDR) for each AIoT device 3, and only needs to generate consolidated billing data (CDR) for AF11. This makes it possible to suppress an increase in the load on NW1, especially the load on CN12.

[0081] Furthermore, the CN12 according to this embodiment enables billing based on the type of AIoT service. The types of AIoT services include, for example, "inventory" and "command". This makes it possible to perform more accurate billing for AIoT services. The CN12 according to this embodiment can, for example, charge different rates for "inventory" and "command". Under the premise that "inventory" uses more resources than "command", the charge for "inventory" may be higher than the charge for "command".

[0082] Specifically, as shown in Figure 4, firstly, AF11 sends an AIoT service request message to CN12 requesting the use of the AIoT service. NEF12a of CN12 receives the AIoT service request message. NEF12a then sends (forwards) the AIoT service request message to AIoTTF12b.

[0083] Here, the AIoT service request message received by AIoTTF12b includes the "AIoT service type" and the "AF ID".

[0084] "AIIoT service type" is information indicating the type of AIIoT service requested by AF11, such as "inventory" or "command". "AIIoT service type" may also include "device selection". "Command" may be further subdivided into types such as "write command" and "read command".

[0085] "AF ID" is the identification information of AF11 requesting the use of AIoT services. "AF ID" may also be an identifier that uniquely identifies AF11. "AF ID" may also be an identifier that uniquely identifies the user (customer, business) corresponding to AF11.

[0086] The AIoT service request message received by AIoTTF12b may include the device ID of each AIoT device 3 designated by AF11 as a target for AIoT services. The device ID may be a persistent identifier.

[0087] Secondly, the AIoTF12b, which has a billing trigger function, sends a billing request message to the CHF12d requesting billing processing. The CHF12d receives the billing request message. The billing request message may also be called a billing data request message.

[0088] The billing request message sent from AIoTTF12b to CHF12d includes "AF ID" as information indicating the target of billing for the use of the AIoT service. This makes it possible to bill AF11 rather than individual AIoT devices 3.

[0089] Furthermore, the billing request message sent from AIoTF12b to CHF12d includes the "AIoT service type." This allows for precise billing, such as differentiating between "inventory" and "commands."

[0090] The billing request message sent from AIoTTF12b to CHF12d may include "number of operations." "Number of operations" is information indicating the number of times the operation providing the AIoT service is performed. This allows for billing based on the number of operations. For example, billing control can be implemented such that the more operations performed, the higher the billing cost.

[0091] For example, if the AIoTF 12b continuously receives AIoT service requests from the same AF 11 and performs multiple AIoT service operations, the information indicating the number of such AIoT service operations may be referred to as the "number of operations." If the AIoTF 12b periodically sends billing request messages to the CHF 12d for the same AF 11, the information indicating the number of AIoT service operations within one or more cycles may be referred to as the "number of operations."

[0092] The billing request message sent from AIoTTF12b to CHF12d may include the "number of AIoT devices." The "number of AIoT devices" is information indicating the number of AIoT devices 3 on which the AIoT service is run. This allows for billing based on the number of AIoT devices on which the AIoT service is run. For example, billing control can be implemented such that the more AIoT devices on which the AIoT service is run, the higher the billing price.

[0093] For example, when performing an inventory on N AIoT devices 3 (N: an integer greater than or equal to 1), the value of N may be defined as the "number of AIoT devices." When performing a write operation (write command) on M AIoT devices 3 (M: an integer greater than or equal to 1), the value of M may be defined as the "number of AIoT devices."

[0094] Thirdly, CHF12d generates billing data (CDR) based on the billing request message from AIoTF12b and sends a billing data message containing the CDR to the billing system 14. The billing system 14 receives the billing data message.

[0095] The billing data message (CDR) sent from CHF12d to the billing system 14 includes an "AF ID" as information indicating the subject of billing for the use of the AIoT service. This makes it possible to bill AF11 rather than individual AIoT devices 3.

[0096] Furthermore, the billing data message (CDR) sent from CHF12d to the billing system 14 includes the "AIoT service type." This allows for precise billing, such as differentiating between "inventory" and "commands."

[0097] The billing data message (CDR) sent from CHF12d to the billing system 14 may include the "number of operations". This allows for billing based on the number of operations.

[0098] The billing data message (CDR) sent from CHF12d to the billing system 14 may include the "number of AIoT devices." This allows for billing based on the number of AIoT devices on which the AIoT service is running.

[0099] Fourth, the billing system 14 processes billing for the user (customer, business) corresponding to AF 11 based on the billing data message (CDR) from CHF 12d.

[0100] In addition, the billing operation for the use of the AIoT service according to this embodiment may be performed using any of the following methods: offline billing, online billing, or converged billing.

[0101] (3) Examples of device configurations Next, the configurations of AIoTF12b and CHF12d according to this embodiment will be described.

[0102] (3.1) Example of AIoTF Configuration Figure 5 is a diagram showing an example of the functional configuration of the AIoTF 12b according to this embodiment. However, the configuration shown in Figure 5 may be an example of the hardware configuration of the AIoTF 12b.

[0103] As shown in Figure 5, the AIoTF 12b includes a receiving unit 121b, a transmitting unit 122b, a storage unit 124b, and a control unit 125b. Note that this functional configuration (functional block) is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to this embodiment.

[0104] The receiving unit 121b and the transmitting unit 122b constitute a transceiver unit 123b that communicates with other communication devices. The receiving unit 121b includes the function of receiving various signals transmitted from other communication devices and obtaining information from the received signals, for example, higher layer information. The transmitting unit 122b includes the function of generating signals to be transmitted to other communication devices and transmitting said signals.

[0105] The memory unit 124b includes a storage device, which stores pre-configured setting information and the like in the storage device, and reads it from the storage device as needed. The control unit 125b performs processing to control the above-mentioned operations and the operations described later in the AIoTF 12b. The signal transmission function unit of the control unit 125b may be included in the transmission unit 122b, and the signal reception function unit of the control unit 125b may be included in the reception unit 121b.

[0106] In the AIoTF12b configured in this way, the receiving unit 121b receives an AIoT service request message (an example of a first message) from the NEF12a (an example of a first network node) requesting the use of the AIoT service. The AIoT service request message includes identification information (AF ID) of the AF11 requesting the use of the AIoT service.

[0107] Based on the AIoT service request message received by the receiving unit 121b, the transmitting unit 122b sends a billing request message (an example of a second message) to the CHF 12d (an example of a second network node) requesting billing processing. Here, the transmitting unit 122b sends a billing request message that includes the identification information (AF ID) of AF 11 as information indicating the subject of billing.

[0108] The billing request message may be generated by the control unit 125b. The transmission unit 122b may transmit the billing request message generated by the control unit 125b to the CHF 12d.

[0109] The AIoT service request message received by the receiving unit 121b further includes an AIoT service type, which is information indicating the type of AIoT service requested by AF 11. The transmitting unit 122b may send a billing request message further including the AIoT service type to CHF 12d.

[0110] The transmitting unit 122b may send a billing request message to the CHF 12d that further includes the number of operations and / or the number of AIoT devices.

[0111] The control unit 125b controls the system to perform the type of AIoT service operation (e.g., inventory or command operation) requested in the AIoT service request message, based on the AIoT service request message. For example, in the case of offline billing, the transmission unit 122b may send a billing request message to the CHF 12d after the control unit 125b has performed the AIoT service operation. Alternatively, in the case of online billing or converged billing, the transmission unit 122b may send a billing request message to the CHF 12d before the control unit 125b has performed the AIoT service operation.

[0112] (3.2) Example of CHF configuration Figure 6 is a diagram showing an example of the functional configuration of CHF12d according to this embodiment. However, the configuration shown in Figure 6 may be an example of the hardware configuration of CHF12d.

[0113] As shown in Figure 6, the CHF 12d includes a receiving unit 121d, a transmitting unit 122d, a storage unit 124d, and a control unit 125d. Note that this functional configuration (functional block) is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to this embodiment.

[0114] The receiving unit 121d and the transmitting unit 122d constitute a transceiver unit 123d that communicates with other communication devices. The receiving unit 121d includes the function of receiving various signals transmitted from other communication devices and obtaining information from the received signals, for example, higher layer information. The transmitting unit 122d includes the function of generating signals to be transmitted to other communication devices and transmitting those signals.

[0115] The memory unit 124d includes a storage device, which stores pre-configured setting information and the like in the storage device, and reads it from the storage device as needed. The control unit 125d performs processing to control the above-mentioned operations and the operations described later in the CHF 12d. The signal transmission function unit of the control unit 125d may be included in the transmission unit 122d, and the signal reception function unit of the control unit 125d may be included in the reception unit 121d.

[0116] In the CHF12d configured in this way, the receiving unit 121d receives a billing request message (an example of a first message) requesting billing processing from the AIoTF12b (an example of a first network node). The billing request message includes identification information (AF ID) of the AF11 requesting the use of the AIoT service.

[0117] Based on the billing request message received by the receiving unit 121d, the transmitting unit 122d sends a billing data message (an example of a second message) requesting billing processing to the billing system 14 (an example of a second network node). Here, the transmitting unit 122d sends a billing data message that includes the identification information (AF ID) of AF 11 as information indicating the subject of billing (i.e., the subject of the invoice).

[0118] The billing data message (CDR) may be generated by the control unit 125d. The transmission unit 122d may transmit the billing data message (CDR) generated by the control unit 125d to the billing system 14.

[0119] The billing request message received by the receiving unit 121d further includes an AIoT service type, which is information indicating the type of AIoT service requested by AF 11. The transmitting unit 122d may send a billing data message (CDR) further including the AIoT service type to the billing system 14.

[0120] The transmission unit 122d may send a billing data message (CDR) to the billing system 14 that further includes the number of operations and / or the number of AIoT devices.

[0121] (4) Examples Next, the first to fourth examples will be described based on the system configuration example and billing operation example described above.

[0122] (4.1) Figure 7 of the first embodiment shows the first embodiment of this embodiment.

[0123] The first embodiment is an example in which billing for the use of an AIoT service is carried out according to an event-based and offline billing method.

[0124] As shown in Figure 7, in step S101, AF11 sends an AIoT service request message to NEF12a. NEF12a receives the AIoT service request message. The AIoT service request message includes the AIoT service type (e.g., inventory or command) and the device ID of each AIoT device 3 that is the target of the AIoT service.

[0125] In step S102, NEF12a sends an AIoT service request message to AIoTTF12b. AIoTTF12b receives the AIoT service request message. The AIoT service request message includes the AIoT service type (e.g., inventory or command), the device ID of each AIoT device 3 targeted by the AIoT service, and the AF ID of AF11. The AF ID may be included in the AIoT service request message in step S101. Alternatively, if the AF ID is not included in the AIoT service request message in step S101, NEF12a may include the AF ID in the AIoT service request message in step S102.

[0126] In step S103, the AIoTF12b and AIoTDM12c perform service approval processing for the AIoT service request message.

[0127] In step S104, the AIoTF 12b, the reader device (base station 13a or UE2), and the AIoT device 3 perform an AIoT service operation of the type requested by AF 11 (e.g., inventory or command). The AMF 12e may also be involved in the AIoT service operation.

[0128] In step S105, the AIoTF 12b sends an AIoT service response message to the NEF 12a. The NEF 12a receives the AIoT service response message. The AIoT service response message includes AIoT service data. The AIoT service data is data that includes the results of the AIoT service operation. For example, the AIoT service data may include information collected by the inventory. The AIoT service data may also include information indicating the success or failure of the command.

[0129] In step S106, NEF12a sends an AIoT service response message to AF11. AF11 receives the AIoT service response message. The AIoT service response message includes AIoT service data.

[0130] In step S107, the AIoTF 12b sends a billing request message to the CHF 12d. The CHF 12d receives the billing request message. The billing request message includes the AIoT service type (e.g., inventory or command) and the AF ID of AF 11. The billing request message may further include the number of operations and / or the number of AIoT devices.

[0131] In step S108, CHF12d generates billing data (CDR) based on the billing request message. The billing data (CDR) includes the AIoT service type (e.g., inventory or command) and the AF ID of AF11. The billing data (CDR) may further include the number of operations and / or the number of AIoT devices.

[0132] In step S109, CHF12d sends a billing response message to AIoTF12b. AIoTF12b receives the billing response message.

[0133] In step S110, CHF12d sends a billing data message containing the generated CDR to the billing system 14. The billing system 14 receives the billing data message and performs billing processing based on the billing data message.

[0134] (4.2) Second Embodiment Figure 8 is a diagram showing the second embodiment of this embodiment.

[0135] The second embodiment is similar to the first embodiment in that it charges for the use of the AIoT service according to an event-based and offline billing method. However, the second embodiment modifies some of the sequences in the first embodiment. The differences between the second embodiment and the first embodiment will be explained in detail.

[0136] As shown in Figure 8, the operation of steps S121 to S123 is the same as in the first embodiment.

[0137] In step S124, the AIoTF 12b sends an AIoT service response message to the NEF 12a. The NEF 12a receives the AIoT service response message. In this embodiment, the AIoT service response message does not contain AIoT service data and functions simply as an acknowledgment (Ack).

[0138] In step S125, NEF12a sends an AIoT service response message to AF11. AF11 receives the AIoT service response message.

[0139] In step S126, the AIoTF 12b, the reader device (base station 13a or UE2), and the AIoT device 3 perform an AIoT service operation of the type requested by AF 11 (e.g., inventory or command). The AMF 12e may also be involved in the AIoT service operation.

[0140] In step S127, the AIoTF 12b sends an AIoT service notification message to the NEF 12a. The NEF 12a receives the AIoT service notification message. The AIoT service notification message includes AIoT service data. The AIoT service data is data that includes the results of the AIoT service operation. For example, the AIoT service data may include information collected by the inventory. The AIoT service data may also include information indicating the success or failure of a command.

[0141] In step S128, NEF12a sends an AIoT service notification message to AF11. AF11 receives the AIoT service notification message. The AIoT service response message includes AIoT service data.

[0142] The operation in steps S129 to S132 is the same as in the first embodiment.

[0143] (4.3) Third Embodiment Figure 9 is a diagram showing the third embodiment of this embodiment.

[0144] The third embodiment is an example in which billing for the use of an AIoT service is carried out on an event basis and according to an online or converged billing method. The differences between the third embodiment and the first embodiment will be explained in detail.

[0145] As shown in Figure 9, the operation of steps S141 to S143 is the same as in the first embodiment.

[0146] In step S144, the AIoTF 12b sends a billing request message to the CHF 12d. The CHF 12d receives the billing request message. The billing request message includes the type of AIoT service (e.g., inventory or command) and the AF ID of AF 11. The billing request message may further include the number of operations and / or the number of AIoT devices.

[0147] In step S145, CHF12d generates billing data (CDR) based on the billing request message. The billing data (CDR) includes the AIoT service type (e.g., inventory or command) and the AF ID of AF11. The billing data (CDR) may further include the number of operations and / or the number of AIoT devices.

[0148] In step S146, CHF12d sends a billing response message to AIoTF12b. AIoTF12b receives the billing response message.

[0149] In step S147, CHF12d sends a billing data message containing the generated CDR to the billing system 14. The billing system 14 receives the billing data message. The billing system 14 performs billing processing based on the billing data message.

[0150] In step S148, the AIoTF 12b, the reader device (base station 13a or UE2), and the AIoT device 3 perform an AIoT service operation of the type requested by AF 11 (e.g., inventory or command). The AMF 12e may also be involved in the AIoT service operation.

[0151] In step S149, the AIoTF 12b sends an AIoT service response message to the NEF 12a. The NEF 12a receives the AIoT service response message. The AIoT service response message includes AIoT service data.

[0152] In step S150, NEF12a sends an AIoT service response message to AF11. AF11 receives the AIoT service response message. The AIoT service response message includes AIoT service data.

[0153] (4.4) Fourth Embodiment Figure 10 is a diagram showing the fourth embodiment of this embodiment.

[0154] The fourth embodiment, like the third embodiment, is an embodiment in which billing for the use of the AIoT service is performed on an event basis and according to the method of online billing or converged billing. However, in this embodiment, a scenario is assumed in which an error occurs because AF11 does not have or does not have enough balance (also referred to as "credit") available for the AIoT service. The fourth embodiment will be explained mainly in terms of the differences from the first embodiment.

[0155] As shown in Figure 10, the operation of steps S161 to S163 is the same as in the first embodiment.

[0156] In step S164, the AIoTF 12b sends a billing request message to the CHF 12d. The CHF 12d receives the billing request message. The billing request message includes the AIoT service type (e.g., inventory or command) and the AF ID of AF 11. The billing request message may further include the number of operations and / or the number of AIoT devices.

[0157] In step S165, CHF12d determines that AF11 does not have or does not have enough credits available for the AIoT service.

[0158] In step S166, CHF12d sends a billing response message containing error information to AIoTF12b. AIoTF12b receives the billing response message. The error information may indicate that AF11 does not have any credits available for the AIoT service. Alternatively, the error information may indicate that AF11 does not have enough credits available for the AIoT service.

[0159] In step S167, the AIoTF 12b sends an AIoT service response message containing error information to the NEF 12a. The NEF 12a receives the AIoT service response message.

[0160] In step S168, NEF12a sends an AIoT service response message containing error information to AF11. AF11 receives the AIoT service response message. This allows AF11 to understand that the AIoT service was not performed due to insufficient credits.

[0161] (5) Hardware Configuration The block diagrams of each communication entity (network node, UE2, AIoT device3) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may be realized by combining the one device or the multiple devices with software.

[0162] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0163] For example, each communication entity (each communication device) in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 11 is a diagram showing an example of the hardware configuration of each communication entity according to the embodiment. Each of the above-described communication entities 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, and the like.

[0164] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station and AIoT device 3 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0165] Each of the functions in the aforementioned communication entities is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002, which then causes the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0166] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit and the like described above may be implemented by the processor 1001.

[0167] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit of each communication entity described above may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0168] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0169] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc 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 multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0170] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0171] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0172] 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 different buses may be configured for each device.

[0173] Furthermore, each communication entity may be composed of hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0174] Figure 12 shows an example of the configuration of a vehicle according to this embodiment.

[0175] 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 herein may be applied to a communication device mounted on the vehicle 2001, for example, to the communication module 2013.

[0176] The drive unit 2002 consists of, for example, 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, which is operated by the user.

[0177] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (I / O (Input / Output) ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0178] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

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

[0180] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS (Global Navigation Satellite System)), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0182] 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 external devices. For example, it can send and receive various types of information with external devices 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 or a mobile station.

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

[0184] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers 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 the external device 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-2029, etc., provided in the vehicle 2001.

[0185] (6) Supplementary Information on Embodiments The embodiments have been described above, but the present invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used in the explanation, but 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 this disclosure, and the items described above may be used in combination as necessary, and items described in one item may be applied to items described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, each communication entity has been described using a functional block diagram, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station according to the embodiment and the software operated by the processor of the terminal according to the embodiment may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0186] Furthermore, notification of information is not limited to the embodiments / models described herein and may be performed by other methods. For example, 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., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Information notified by higher layer signaling may be called configuration information. Information notified by physical layer signaling may be called control information. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0187] Each aspect / embodiment described herein may be applied to at least one of systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), Beyond-5G, 6G, FRA (Future Radio Access), NR, W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be combined and applied (for example, a combination of at least one of LTE and LTE-A and 5G).

[0188] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be rearranged in order, provided they are consistent. For example, the methods described herein present various step elements in an exemplary order and are not limited to the specific order presented.

[0189] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME (Mobility Management Entity) or an S-GW (Serving Gateway), but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0190] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0191] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0192] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0193] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0194] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0196] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0197] The terms “system” and “network” as used in this disclosure are interchangeable.

[0198] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or corresponding other information. For example, wireless resources may be indicated by an index.

[0199] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0200] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "Transmission / Reception Point (TRP)", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0201] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0202] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

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

[0204] 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 several other appropriate terms.

[0205] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do 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.

[0206] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminal may have the functions that the base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0207] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal.

[0208] The terms “determining” and “decision” as used in this disclosure may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in tables, databases or other data structures), and ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, “determining” may include resolving, selecting, choosing, establishing, and comparing. In other words, "judgment" and "decision" can include considering that some action has been "judged" or "decided." Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0209] The terms “connected,” “coupled,” and any variations thereof mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0210] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0211] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0212] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

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

[0214] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0215] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0216] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0217] A slot may consist of one or more symbols in the time domain (such as OFDM symbols or DC-FDMA (Single Carrier Frequency Division Multiple Access) symbols). A slot may also be a time unit based on neurology.

[0218] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

[0219] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0220] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0221] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal) in TTI units. However, the definition of TTI is not limited to this.

[0222] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0223] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0224] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0225] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0226] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0227] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0228] One or more RBs may also be called a Physical RB (PRB), Subcarrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0229] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0230] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common RBs (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of RBs relative to a common reference point of the carrier. PRBs may be defined and numbered within a given BWP.

[0231] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a terminal within a single carrier.

[0232] At least one of the configured BWPs may be active, and the terminal does not need to be expected to send or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0233] The above-described structures of wireless frames, subframes, slots, minislots, and symbols are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0234] When wireless parameters are "configured," this may mean that predetermined values ​​are pre-configured, or that wireless parameters notified by a network node or terminal are configured.

[0235] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0236] In this 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 "combine" may be interpreted similarly to "different."

[0237] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0238] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0239] This application claims priority to Japanese Patent Application No. 2025-030271 (February 27, 2025), and all of its contents are incorporated into the specification of this application.

[0240] (7) Additional notes: Features of the above-described embodiments are noted below.

[0241] - Appendix 1 A network node comprising: a receiving unit that receives a first message from a first network node different from the network node, which includes identification information of an application function that requests the use of an IoT service involving wireless communication with one or more terminals; and a transmitting unit that transmits a second message relating to billing for the use of the IoT service to a second network node different from the network node, based on the first message, wherein the transmitting unit transmits the second message which includes identification information of the application function as information indicating the subject of the billing.

[0242] - Appendix 2 The network node as described in Appendix 1, wherein the first message further includes information indicating the type of IoT service requested by the application function, and the transmitting unit transmits the second message, which further includes the information indicating the type, to the second network node.

[0243] - Appendix 3 The network node according to Appendix 1 or 2, wherein the transmitting unit transmits the second message, which further includes information indicating the number of times the IoT service is performed, to the second network node.

[0244] - Appendix 4 The first message is a message requesting the use of the IoT service, the second network node is a network node that performs billing, and the second message is a message requesting the billing process, as described in any of Appendix 1 to 3.

[0245] - Appendix 5 The first message is a message requesting billing processing, the second network node is a network node that performs billing processing, and the second message is a message requesting the billing processing, as described in any of Appendix 1 to 3.

[0246] - Appendix 6 A communication method performed by a network node, comprising: receiving a first message from a first network node different from the network node, which includes identification information of an application function requesting the use of an IoT service involving wireless communication with one or more terminals; and transmitting a second message to a second network node different from the network node, based on the first message, regarding charges for the use of the IoT service, wherein the network node transmits the second message, which includes identification information of the application function, as information indicating the subject of the charges.

[0247] 1: NW 2: UE (Reader device) 3: AIoT device 4: UE (Reader device) 12: CN 12a: NEF 12b: AIoTF 12c: AIoTDM 12d: CHF 12e: AMF 13: RAN 13a: Base station (Reader device) 13b: Base station 14: Billing system 15: OAM 121b: Receiving unit 121d: Receiving unit 122b: Transmitting unit 122d: Transmitting unit 123b: Transmitting / receiving unit 123d: Transmitting / receiving unit 124b: Storage unit 124d: Storage unit 125b: Control unit 125d: Control unit 1001: Processor 1002: Storage device 1003 : Auxiliary storage device 1004: Communication device 1005: Input device 1006: Output device 1007: Bus 2001: Vehicle 2002: Drive unit 2003: Steering unit 2004: Accelerator pedal 2005: Brake pedal 2006: Shift lever 2007: Front wheel 2008: Rear wheel 2009: Axle 2010: Electronic control unit 2012: Information service unit 2013: Communication module 2021-2029: Sensor 2030: Driving support system unit 2031: Microprocessor 2032: Memory 2033: Communication port

Claims

Network node, A receiving unit that receives a first message containing identification information of an application function requesting the use of an IoT service involving wireless communication with one or more terminals from a first network node different from the network node, The system includes a transmitting unit that, based on the first message, transmits a second message regarding billing for the use of the IoT service to a second network node different from the network node, The transmitting unit is a network node that transmits the second message, which includes the identification information of the application function as information indicating the subject of the charge. 　 The first message further includes information indicating the type of IoT service requested by the application function, The network node according to claim 1, wherein the transmitting unit transmits the second message, which further includes information indicating the type, to the second network node. 　 The network node according to claim 1, wherein the transmitting unit transmits the second message to the second network node, further including information indicating the number of times the IoT service is performed. 　 The first message is a message requesting the use of the IoT service, The second network node is a network node that performs billing processing, The network node according to any one of claims 1 to 3, wherein the second message is a message requesting the billing process. 　 The first message is a message requesting billing processing, The second network node is a network node that performs billing processing, The network node according to any one of claims 1 to 3, wherein the second message is a message requesting the billing process. 　 A communication method performed by a network node, Receiving a first message containing identification information of an application function requesting the use of an IoT service involving wireless communication with one or more terminals from a first network node different from the aforementioned network node, Based on the first message, a second message regarding billing for the use of the IoT service is sent to a second network node different from the network node. A communication method comprising the network node transmitting the second message, which includes identification information of the application function as information indicating the subject of the charge.

Images