Communication method, communication device, communication system, storage medium, and program product

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The method is executed by a first node and comprises: transmitting first information to a second node, wherein the first information is used for instructing the second node to charge for a first service on the basis of usage-related data for charging. By means of the solution of the present disclosure, charging for an MC service supported by, for example, a 6G IoT device can be implemented.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of wireless communication, and more particularly to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] As people's lives and work become increasingly intelligent, more and more massive communication (MC) devices will be deployed. MC services are typically implemented based on a large number of MC devices. Summary of the Invention

[0003] This disclosure relates to a communication method, communication device, communication system, storage medium, and program product.

[0004] According to a first aspect of the present disclosure, a communication method is provided. The method is performed by a first node. The method includes: sending first information to a second node, wherein the first information is used to instruct the second node to perform billing based on billing quantity data for a first service.

[0005] According to a second aspect of the present disclosure, a communication method is provided. The method is executed by a second node. The method includes: receiving first information; and, based on the first information, performing billing based on billing data for a first service.

[0006] According to a third aspect of the present disclosure, a communication method is provided. The method is performed by a third node. The method includes: receiving first information sent by a first node; sending the first information to a second node; wherein the first information is used to instruct the second node to perform billing based on billing quantity data for a first service.

[0007] According to a fourth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication method as described in any one of the first to third aspects.

[0008] According to a fifth aspect of the present disclosure, a communication system is provided. The communication system includes a first node, a second node, and a third node. The first node is configured to perform the communication method as described in the first aspect. The second node is configured to perform the communication method as described in the second aspect. The third node is configured to perform the communication method as described in the third aspect.

[0009] According to a sixth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any one of the first to third aspects.

[0010] According to a seventh aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When the program or instructions are executed by a communication device, they implement the steps of the communication method as described in the first to third aspects.

[0011] According to an eighth aspect of the present disclosure, a computer program is provided. When this computer program is run on a computer, it causes the computer to perform the communication method as described in any one of the first to third aspects.

[0012] According to a ninth aspect of the present disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method as described in any one of the first to third aspects.

[0013] According to embodiments of this disclosure, billing can be applied, for example, to MC services.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0016] Figure 1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0017] Figure 2A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0018] Figure 2B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0019] Figure 2C is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0020] Figure 3 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0021] Figure 4 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0022] Figure 5A is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0023] Figure 5B is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure.

[0024] Figure 6A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0025] Figure 6B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. Detailed Implementation

[0026] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0027] In a first aspect, embodiments of this disclosure provide a communication method. The method is performed by a first node. The method includes: sending first information to a second node, wherein the first information is used to instruct the second node to perform billing based on billing quantity data for a first service.

[0028] In the above embodiments, the first node can send first information to the second node, enabling the second node to perform billing based on the billing amount for the first service. This allows billing for the first service to be implemented.

[0029] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following: billing indication information for triggering the second node to perform billing operations; event indication information for indicating a first event; and billing quantity data.

[0030] In the above embodiments, the first node can send at least one of billing indication information, event indication information, and billing usage data to the second node using the first information. The billing indication information can be used to trigger billing, causing the second node to perform a billing operation. The event indication information can be used to indicate a first event related to the billing of the first service, enabling the second node to determine the event to which the billing of the first service applies. The billing usage data can be data obtained by the first node through statistics for billing purposes. Based on the billing usage data, the second node can obtain the bill related to the first service and realize the billing of the first service. Based on one or more of the billing indication information, event indication information, and billing usage data, the second node can accurately realize usage-based billing for the first service.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the billing data may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0032] In the above embodiments, the billing data can be related to the number of devices, tasks, data usage, time usage, number of events, etc. Thus, billing for the first service can be implemented based on one or more of the following: number of devices, tasks, data usage, time usage, and number of events, significantly enhancing the flexibility and applicability of billing.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the billing data may be obtained based on billing information; wherein the billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the billing information may be associated with at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the transmission of the first information may be triggered by a first event, the first event including at least one of the following: the start of a first session; the end of a first session; the start of a first service; the end of a first service; the billing amount data of the first service reaching a first threshold.

[0036] In the above embodiments, the transmission of billing data can be triggered when events such as session start, session end, service start, service end, or billing data reaching a threshold are occurred. Billing data transmitted for session start and session end events can be used for session-based billing. Billing data transmitted for service start and service end events can be used for service-based billing. Events where billing data reaches a threshold can be used for usage reallocation or service termination. Thus, accurate billing and billing control for the first service can be achieved.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving second information sent by a third node, wherein the second information includes at least one of the following: a first quota, which is the maximum amount of billing data allocated on the first node for the first service; and a first threshold, used to trigger the first node to report billing data.

[0038] In the above embodiments, a first quota and a first threshold can be allocated to the billing volume data of the first service. The first quota ensures that the billing volume of the first service does not exceed a specific upper limit. The first threshold can be used to determine whether to increase the quota for the billing volume of the first service, thereby realizing dynamic and precise management of the quota and improving the system's working efficiency.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the second information may include a first rule, which is used by the first node to monitor and / or report billing data, and the first rule includes a first quota and / or a first threshold.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the billing data related to the first quota may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the operation of sending the first information to the second node may include one of the following: sending the first information to the second node according to the address information of the second node; or sending the first information to the third node so that the third node sends the first information to the second node according to the address information of the second node.

[0042] In a second aspect, embodiments of this disclosure provide a communication method. This method is executed by a second node. The method includes: receiving first information; and, based on the first information, performing billing for a first service based on billing data.

[0043] In the above embodiments, the first node can send first information to the second node, enabling the second node to perform billing based on billing volume data for the first service. This allows billing for the first service to be implemented.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following: billing indication information for triggering the second node to perform billing operations; event indication information for indicating a first event; and billing quantity data.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the billing data may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0046] In conjunction with some embodiments of the second aspect, in some embodiments, the billing data may be obtained based on billing information; wherein the billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the billing information is associated with at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the transmission of the first information may be triggered by a first event, the first event including at least one of the following: the start of a first session; the end of a first session; the start of a first service; the end of a first service; the billing amount data of the first service reaching a first threshold.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: receiving third information sent by a third node, wherein the third information is used to request a quota of billing data for the first service; sending fourth information to the third node, wherein the fourth information includes at least one of the following: a first quota, which is the maximum amount of billing data allocated on the first node for the first service; a second quota, which is the maximum amount of billing data allocated for the first service; and a first threshold, used to trigger the first node to report billing data.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the billing data related to the first quota may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the operation of receiving the first information may include one of the following: receiving the first information sent by the first node; or receiving the first information sent by the first node via a third node.

[0052] In a third aspect, embodiments of this disclosure provide a communication method. This method is executed by a third node. The method includes: receiving first information sent by a first node; sending the first information to a second node; wherein the first information is used to instruct the second node to perform billing based on billing quantity data for a first service.

[0053] In the above embodiment, the third node can send the first information from the first node to the second node, enabling the second node to perform billing for the billing data of the first service. This allows billing for the first service to be achieved.

[0054] In conjunction with some embodiments of the third aspect, in some embodiments, the first information may include at least one of the following: billing indication information for triggering the second node to perform billing operations; event indication information for indicating a first event; and billing quantity data.

[0055] In conjunction with some embodiments of the third aspect, in some embodiments, the billing data may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0056] In conjunction with some embodiments of the third aspect, in some embodiments, the billing data may be obtained based on billing information; wherein the billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0057] In conjunction with some embodiments of the third aspect, in some embodiments, billing information may be associated with at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, sponsor.

[0058] In conjunction with some embodiments of the third aspect, in some embodiments, the first information may be sent by the first node when a first event is triggered, the first event including at least one of the following: the start of a first session; the end of a first session; the start of a first service; the end of a first service; the billing amount data of the first service reaches a first threshold.

[0059] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: sending third information to a second node, wherein the third information is used to request a quota for billing data for the first service; receiving fourth information sent by the second node, wherein the fourth information includes at least one of a first quota, a second quota, and a first threshold; sending second information to the first node; wherein the second information includes at least one of a first quota and a first threshold; the first quota is the maximum amount of billing data allocated to the first node for the first service; the second quota is the maximum amount of billing data allocated to the first service; and the first threshold is used to trigger the first node to report billing data.

[0060] In conjunction with some embodiments of the third aspect, in some embodiments, the second information sent by the third node to the first node may include a first rule, which is used by the first node to monitor and / or report billing data, and the first rule includes a first quota and / or a first threshold.

[0061] In conjunction with some embodiments of the third aspect, in some embodiments, the billing data related to the first quota may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0062] In a fourth aspect, embodiments of this disclosure provide a first node. The first node includes a transceiver module. The transceiver module is configured to send first information to a second node, wherein the first information is used to instruct the second node to perform billing based on billing volume data for a first service.

[0063] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information may include at least one of the following: billing indication information for triggering the second node to perform billing operations; event indication information for indicating a first event; and billing quantity data.

[0064] In conjunction with some embodiments of the fourth aspect, in some embodiments, the billing data may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0065] In conjunction with some embodiments of the fourth aspect, in some embodiments, the billing data may be obtained based on billing information; wherein the billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0066] In conjunction with some embodiments of the fourth aspect, in some embodiments, the billing information may be associated with at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, sponsor.

[0067] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transmission of the first information may be triggered by a first event, the first event including at least one of the following: the start of a first session; the end of a first session; the start of a first service; the end of a first service; the billing amount data of the first service reaching a first threshold.

[0068] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module may also be configured to: receive second information sent by the third node, wherein the second information includes at least one of the following: a first quota, which is the maximum amount of billing data allocated on the first node for the first service; and a first threshold, which is used to trigger the first node to report billing data.

[0069] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information may include a first rule, which is used by the first node to monitor and / or report billing data, and the first rule includes a first quota and / or a first threshold.

[0070] In conjunction with some embodiments of the fourth aspect, in some embodiments, the billing data related to the first quota may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0071] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module may be configured to perform one of the following: sending first information to the second node based on the address information of the second node; sending the first information to the third node so that the third node sends the first information to the second node based on the address information of the second node.

[0072] In a fifth aspect, embodiments of this disclosure provide a second node. The second node includes a transceiver module and a processing module. The transceiver module is configured to receive first information. The processing module is configured to perform billing based on billing volume data for a first service, according to the first information.

[0073] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information may include at least one of the following: billing indication information for triggering the second node to perform billing operations; event indication information for indicating a first event; and billing quantity data.

[0074] In conjunction with some embodiments of the fifth aspect, in some embodiments, the billing data may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0075] In conjunction with some embodiments of the fifth aspect, in some embodiments, the billing data may be obtained from billing information; wherein the billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0076] In conjunction with some embodiments of the fifth aspect, in some embodiments, the billing information is associated with at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor.

[0077] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transmission of the first information may be triggered by a first event, the first event including at least one of the following: the start of a first session; the end of a first session; the start of a first service; the end of a first service; the billing amount data of the first service reaching a first threshold.

[0078] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to: receive third information sent by a third node, wherein the third information is used to request a quota of billing data for the first service; send fourth information to the third node, wherein the fourth information includes at least one of the following: a first quota, which is the maximum amount of billing data allocated on the first node for the first service; a second quota, which is the maximum amount of billing data allocated for the first service; and a first threshold, used to trigger the first node to report billing data.

[0079] In conjunction with some embodiments of the fifth aspect, in some embodiments, the billing data related to the first quota may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0080] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may be configured to perform one of the following: receiving first information sent by the first node; receiving first information sent by the first node via a third node.

[0081] In a sixth aspect, embodiments of this disclosure provide a third node. The third node includes a transceiver module. The transceiver module is configured to: receive first information sent by a first node; and send the first information to a second node; wherein the first information is used to instruct the second node to perform billing based on billing quantity data for a first service.

[0082] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first information may include at least one of the following: billing indication information for triggering the second node to perform billing operations; event indication information for indicating a first event; and billing quantity data.

[0083] In conjunction with some embodiments of the sixth aspect, in some embodiments, the billing data may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0084] In conjunction with some embodiments of the sixth aspect, in some embodiments, the billing data may be obtained from billing information; wherein the billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0085] In conjunction with some embodiments of the sixth aspect, in some embodiments, the billing information may be associated with at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor.

[0086] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first information may be sent by the first node when a first event is triggered, the first event including at least one of the following: the start of a first session; the end of a first session; the start of a first service; the end of a first service; the billing amount data of the first service reaches a first threshold.

[0087] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module may further be configured to: send third information to the second node, wherein the third information is used to request a quota for billing data for the first service; receive fourth information sent by the second node, wherein the fourth information includes at least one of a first quota, a second quota, and a first threshold; send second information to the first node; wherein the second information includes at least one of a first quota and a first threshold; the first quota is the maximum amount of billing data allocated to the first node for the first service; the second quota is the maximum amount of billing data allocated to the first service; and the first threshold is used to trigger the first node to report billing data.

[0088] In conjunction with some embodiments of the sixth aspect, in some embodiments, the second information sent by the third node to the first node may include a first rule, which is used by the first node to monitor and / or report billing data, and the first rule includes a first quota and / or a first threshold.

[0089] In conjunction with some embodiments of the sixth aspect, in some embodiments, the billing data related to the first quota may include at least one of the following: billing data related to the number of devices; billing data related to the tasks of the first service; billing data related to the data usage of the first service; billing data related to the time usage of the first service; and billing data related to the number of events of the first service.

[0090] In a seventh aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0091] In an eighth aspect, embodiments of this disclosure provide a communication system. The communication system includes a first node, a second node, and a third node. The first node is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The second node is configured to perform the communication method as described in any of the second aspect and its possible embodiments. The third node is configured to perform the communication method as described in any of the third aspect and its possible embodiments.

[0092] In a ninth aspect, embodiments of this disclosure provide a storage medium. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first, second, third, and possible embodiments thereof.

[0093] In a tenth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any of the first, second, third, and possible embodiments thereof.

[0094] In an eleventh aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0095] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first, second, third, and possible embodiments thereof.

[0096] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0097] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, network equipment, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.

[0098] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0099] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0100] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0101] In the embodiments of this disclosure, unless otherwise stated, elements expressed in the singular form, such as “a,” “one,” “a kind,” “the,” “the,” “the,” “the,” “the,” “the,” “the,” “the,” “this,” etc., can mean “one and only one,” or “one or more,” “at least one,” etc. For example, when articles such as “a,” “an,” and “the” are used in translation, the noun following the article can be understood as either a singular or a plural expression.

[0102] In the embodiments of this disclosure, "a plurality of" means two or more.

[0103] In some embodiments, terms such as “at least one (at least one, at least one item, at least one)” and “one or more” may be used interchangeably.

[0104] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0105] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0106] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. As another example, if the object being described is "information", then "second information" and "first information" can be the same information or different information, and their content can be the same or different.

[0107] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0108] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0109] In some embodiments, terms such as “greater than,” “more than,” “higher than,” and “exceeding” can be used interchangeably; terms such as “greater than or equal to,” “not less than,” “more than or equal to,” “not less than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably; terms such as “less than,” “less than,” and “lower than” can be used interchangeably; and terms such as “less than or equal to,” “not greater than,” “less than or equal to,” “not more than,” “lower than or equal to,” “not higher than,” and “below” can be used interchangeably.

[0110] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0111] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0112] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0113] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "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", and "client" can be used interchangeably.

[0114] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0115] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0116] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0117] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0118] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0119] Figure 1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a first node 101, a second node 102, a third node 103, a fourth node 104, and a fifth node 105.

[0120] In some embodiments, the first node 101 can be used for data transmission of large-scale communication services, as well as for monitoring, collecting, and reporting data, events, etc.

[0121] In some embodiments, the first node 101 may be, for example, a user plane function (UPF).

[0122] In some embodiments, the second node 102 can implement functions such as billing related to business.

[0123] In some embodiments, the second node 102 may be, for example, a charging function (CHF).

[0124] In some embodiments, the third node 103 can be used to implement functions such as management, control, and billing triggering of large-scale communication services.

[0125] In some embodiments, the third node 103 may be, for example, a massive communication function (MCF). In some embodiments, the MCF may also be referred to as a massive communication management function (MCMF).

[0126] In some embodiments, the third node 103 may be, for example, an access and mobility management function (AMF). For example, the third node 103 may be an enhanced AMF.

[0127] In some embodiments, the third node 103 may be a session management function (SMF). For example, the third node 103 may be an enhanced SMF.

[0128] In some embodiments, the third node 103 can be a standalone network function. For example, the MCF can be deployed independently. In some embodiments, the third node 103 can be deployed integrated with other network functions. For example, all or part of the MCF's functionality can be deployed in the AMF; in other words, the MCF can be integrated into the AMF. For example, all or part of the MCF's functionality can be deployed in the SMF; in other words, the MCF can be integrated into the SMF.

[0129] In some embodiments, the fourth node 104 may be used to implement functions such as supporting the A-Uu air interface, registering with the controller, supporting functions corresponding to requests from the controller, implementing inventory and transmitting inventory results, and transmitting commands and command responses.

[0130] In some embodiments, the fifth node 105 can be used to implement MC services.

[0131] In some embodiments, the fifth node 105 may be, for example, an MC device.

[0132] In some embodiments, the first node 101 may be a core network device. It is understood that the first node 101 may also be other types of devices, and this disclosure does not impose specific limitations on them.

[0133] In some embodiments, the second node 102 may be a core network device. It is understood that the second node 102 may also be other types of devices, and this disclosure does not impose specific limitations on them.

[0134] In some embodiments, the third node 103 may be a core network device. It is understood that the third node 103 may also be other types of devices, and this disclosure does not impose specific limitations on them.

[0135] In some embodiments, the fourth node 104 may be a terminal, an access network device, or the like. It is understood that the fourth node 104 may also be other types of devices, and this disclosure does not impose specific limitations on these types of devices.

[0136] In some embodiments, the fifth node 105 may be a sensor, an electronic tag, a terminal, etc. It is understood that the fifth node 105 may also be other types of devices, and this disclosure does not impose specific limitations on them.

[0137] In some embodiments, the MC service may include an AIoT service. In some embodiments, the third node 103 may be an AIoT controller. In one example, the third node 103 may be an AIoT function (AIoTF) or an AIoT management function (AIoTMF). In some embodiments, the fourth node 104 may be an AIoT reader. In some embodiments, the fifth node 105 may be an AIoT device.

[0138] In some embodiments, the terminal includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0139] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0140] In some embodiments, the communication system 100 described above may be a 5G communication system or a 6G communication system. It should be noted that the communication system 100 may also be other communication systems, such as a 4G communication system, and this disclosure does not specifically limit it in this regard.

[0141] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0142] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or some of the main components in the communication system 100, but are not limited thereto. The main components shown in FIG1 are illustrative. The communication system 100 may include all or some of the main components in FIG1, or may include other main components other than those in FIG1. ​​The number and form of each main component are arbitrary. Each main component may be physical or virtual. The connection relationship between the main components is illustrative. The main components may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0143] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0144] In recent years, the Internet of Things (IoT) has received significant attention in the wireless communications world. With the widespread application of IoT technology in wireless communications, higher demands are being placed on the size, complexity, and power performance of IoT devices. More things are expected to be interconnected to improve productivity and enhance quality of life. Further reductions in the size, complexity, and power of IoT devices enable the deployment of billions, or even hundreds of billions, of IoT devices for various applications, providing added value throughout the value chain. However, IoT devices often require built-in energy storage devices such as batteries. This necessitates manual battery replacement or charging, increasing maintenance costs and reducing convenience. In some scenarios, this can even lead to security risks, such as in wireless sensors in the power industry and the oil industry.

[0145] To address the above issues, a novel IoT technology, namely Ambient IoT (AIoT), is proposed. Devices employing AIoT technology can be referred to as AIoT devices. AIoT devices can be powered through energy capture. For example, an AIoT device can capture energy in the form of electromagnetic waves, light, sound waves, etc., from its surrounding environment to provide electrical power. In some embodiments, AIoT devices may have limited energy storage capabilities.

[0146] In some embodiments, AIoT devices can be categorized into three types. The first type of AIoT device has neither energy storage capability nor independent signal generation capability. The second type of AIoT device has energy storage capability but lacks independent signal generation capability. The third type of AIoT device has both energy storage capability and independent signal generation capability. For the first and second types of AIoT devices, signals can be generated through backscattering.

[0147] In some embodiments, the overall architecture of AIoT includes AIoT devices, readers, AIoT controllers, and application functions (AF).

[0148] In some embodiments, multiple connection topologies exist for AIoT devices. Figures 2A to 2D are schematic diagrams of connection topologies for AIoT. As shown in Figures 2A to 2D, there are typically four different connection topologies for AIoT devices.

[0149] In some embodiments, as shown in FIG2A, the first connection topology (or Topology 1, first type of topology) can be: base station <—> AIoT device. In some embodiments, the AIoT device can directly communicate bidirectionally with the base station. The communication between the base station and the AIoT device can include data and / or signaling related to AIoT services. In the first connection topology, the transmission from the base station to the AIoT device and the transmission from the AIoT device to the base station can be the same or different.

[0150] In some embodiments, as shown in Figure 2B, the second connection topology (or Topology 2, second type of topology) can be: base station <—> intermediate node <—> AIoT device. In some embodiments, user equipment (UE) can be used as an intermediate node under network control. In some embodiments, the AIoT device can communicate bidirectionally with the intermediate node located between the AIoT device and the base station. The intermediate node can be a relay with AIoT capabilities, an integrated access and backhaul (IAB) node, a UE, a repeater, etc. The intermediate node can forward information between the base station and the AIoT device.

[0151] In some embodiments, as shown in Figure 2C, the third connection topology (or Topology 3, Third Type Topology) can be: Base Station <—> Auxiliary Node <—> AIoT Device <—> Base Station. In some embodiments, the AIoT device can send data and / or signaling to the base station and can receive data and / or signaling from the auxiliary node. In some embodiments, the AIoT device can receive data and / or signaling from the base station and can send data and / or signaling to the auxiliary node. In this topology, the auxiliary node can be a relay, integrated access and backhaul node, UE, repeater, etc., with AIoT capabilities.

[0152] In some embodiments, as shown in Figure 2D, the fourth link topology (or topology 4, fourth type of topology) can be: UE <—> AIoT device. In some embodiments, the AIoT device can communicate bidirectionally with the UE. In some embodiments, the communication between the AIoT device and the UE can include AIoT service data and / or signaling.

[0153] In different connection topologies, readers can be implemented by different types of devices. For example, a reader can be a base station, an intermediate node, a UE, etc. Massive communication (MC) is a development direction of 6G technology. In massive communication services, the number and types of devices participating in the communication will increase. It is understood that MC services can also have other names, and this disclosure does not specifically limit them.

[0154] In some embodiments, devices employing MC technology can be categorized into low-capability devices and high-capability devices based on their capabilities. In some embodiments, a low-capability device may be a device with relatively weak computing and / or communication capabilities. In one example, a low-capability device may be characterized by small size, low complexity, and low power consumption. Low-capability devices may include, for example, narrowband IoT (NB-IoT) and AIoT devices. In some embodiments, a high-capability device may be a device with relatively strong computing and / or communication capabilities. A high-capability device employing MC technology may, for example, have a lower network interaction frequency.

[0155] In some embodiments, MC services may include 5G AIoT services. In some embodiments, MC services may include 6G IoT services. In some embodiments, 6G IoT services may include services related to high-capability devices, services related to low-capability devices, 6G AIoT services, IoT services supported by 6G UEs, etc.

[0156] In some embodiments, the MC device may include an AIoT device. In some embodiments, the type of MC device may include 3GPP devices and non-3GPP devices. 3GPP devices are, for example, devices contracted with an operator. Non-3GPP devices are, for example, devices owned by an application provider or vendor. Billing models in the related art may not support the feature requirements of future communication systems. For example, future billing models may not be based on data or time usage, may use different events for billing, or may not be billed on a device-by-device basis.

[0157] Therefore, how to achieve effective billing for MC services is an urgent problem to be solved.

[0158] Figure 2A is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 2A, the communication method of the embodiment of the present disclosure includes steps S2101 to S2112.

[0159] In step S2101, the first node 101 determines the second node 102.

[0160] In some embodiments, the first node 101 may determine a second node 102 for implementing billing for the first service.

[0161] In some embodiments, the first service can be a 6G MC service. For example, the first service may include a 6G AIoT service. It is understood that the first service can also be other services for large-scale deployment of communications, such as services supported by 6G IoT devices, including 6G MC services for terminals with different capabilities, and this disclosure does not specifically limit this.

[0162] In some embodiments, the first service may include a 5G MC service. For example, the first service may include a 5G AIoT service.

[0163] In some embodiments, the first node 101 may be, for example, a UPF.

[0164] In some embodiments, the second node 102 may be, for example, a CHF.

[0165] In some embodiments, the first node 101 may determine the second node 102 through a discovery and selection process. For example, the first node 101 may determine the second node 102 through network repository function (NRF) discovery and selection.

[0166] In some embodiments, step S2101 can be performed during the session establishment process of the first service. In some embodiments, during the session establishment process of the first service, the first node 101 can determine the second node 102.

[0167] In some embodiments, step S2101 can be executed after the MC session establishment process of the first service. In some embodiments, after the session establishment process of the first service is completed, the first node 101 can determine the second node 102.

[0168] In some embodiments, an MC session, or first session, can be established for a first service through the MC session establishment process. The first session can be used to implement the transmission of messages and / or data for the first service.

[0169] In some embodiments, step S2101 may be executed during the registration process of the fifth node 105. In some embodiments, step S2101 may be executed during the registration process of the fourth node 104. In some embodiments, step S2101 may be executed upon receiving a service request from the AF.

[0170] In some embodiments, through step S2101, the first node 101 can obtain the address information of the second node 102. For example, the first node 101 can obtain the IP address of the second node 102.

[0171] In step S2102, the third node 103 receives the service request.

[0172] In some embodiments, the third node 103 can receive service requests. These service requests can be used to transmit data and / or messages related to MC services.

[0173] In some embodiments, the third node 103 can support MC session and service billing. In one example, the third node 103 can support billing for MC sessions and services. In some embodiments, the MC service may include an AIoT service, in which case the third node 103 can support AIoT session and service billing.

[0174] In some embodiments, a service request may be associated with at least one of the following: a first service, and a first task of the first service. In some embodiments, a service request may request the implementation of the first service. In some embodiments, a service request may request the implementation of the first task within the first service.

[0175] In some embodiments, the first task may include at least one of the following: inventory and command. In some embodiments, the command may include at least one of the following: read, write, disable, environmental data reporting, perception data reporting, and event subscription for MC services. It is understood that the first task may also have other types, and this disclosure does not specifically limit them.

[0176] In some embodiments, the first service may be associated with one or more devices. For example, the first service may be associated with one or more MC devices. For example, the first service may be associated with one or more AIoT devices. In some embodiments, the first service may be associated with one or more readers. For example, the first service may be associated with one or more readers to enable operation on MC devices. For example, the first service may be associated with one or more readers to enable operation on AIoT devices.

[0177] In some embodiments, the first task may be associated with one or more devices. For example, the first task may be associated with one or more MC devices. For example, the first task may be associated with one or more AIoT devices. In some embodiments, the first task may be associated with one or more readers / writers. For example, the first task may be associated with one or more readers / writers to enable operation on MC devices. For example, the first task may be associated with one or more readers / writers to enable operation on AIoT devices.

[0178] In some embodiments, the third node 103 can receive service requests sent by another node (not shown). In some embodiments, the other node sending the service request can be an AF (Active Controller). This AF can be dedicated to providing MC (Multi-Channel Network) services, or it can provide MC services and other services simultaneously. It is understood that an AF providing MC services can also be referred to as an MCAF. In some embodiments, service requests sent by the AF can reach the third node 103 via NEF (Network Exposure Function) and PCF (Programmable Component Function). In some embodiments, service requests sent by the AF can reach the third node 103 via NEF, PCF, and AMF (Application-Mediated Function).

[0179] In some embodiments, the third node 103 may trigger the start of a billing event upon receiving a service request from another node.

[0180] In some embodiments, the third node 103 can trigger the initiation of a billing event when a subscription event occurs. For example, a subscription event may be the execution or triggering of a periodic service. In this case, the third node 103 can trigger a billing event each time the service is executed or triggered.

[0181] In step S2103, the first node 101 monitors the usage.

[0182] In some embodiments, the first node 101 may support MC sessions and service billing. In some embodiments, the feature list of the first node 101 may include indication information to indicate that the first node 101 supports MC sessions and service billing. In some embodiments, the MC service may include an AIoT service, in which case the first node 101 may support AIoT sessions and service billing.

[0183] In some embodiments, the first node 101 can monitor the usage of the first service under the instruction of the third node 103. In one example, when the third node 103 receives a service request, the third node 103 can send an instruction message to the first node 101 to trigger the first node 101 to monitor the usage of the first service. Then, the first node 101 can start monitoring the usage of the first service according to the received instruction message.

[0184] In some embodiments, the first node 101 can automatically begin monitoring the usage of the first service. In one example, the first node 101 can begin monitoring the usage of the first service after the session for the first service has been established.

[0185] In some embodiments, the usage of the first service is related to the billing of the first service. In other words, the first node 101 monitors the usage of the first service related to the billing of the first service. In some embodiments, this usage may be referred to as the billing amount.

[0186] In some embodiments, during the usage monitoring process in step S2103, the first node 101 may collect billing information. In some embodiments, the billing information may be information associated with the billing of the first service. In some embodiments, the billing information may include at least a portion of the information related to the first service. In some embodiments, the billing information may be used to indicate the usage of the first service.

[0187] In some embodiments, billing information may include at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0188] In some embodiments, the reader type can be the type of reader associated with the first service. In some embodiments, the reader type can include base stations and terminals, depending on the device implementing the reader. In some embodiments, the first node 101 can collect the reader type of the reader associated with the first service. For example, the reader associated with the first service can include at least one of the following: a base station type reader, or a terminal type reader.

[0189] In some embodiments, a reader identifier can be used to identify a reader. In some embodiments, a reader identifier can be used to uniquely identify a reader deployed in a network. For example, the reader identifier can be assigned to the reader when it is deployed in the network. For example, the reader identifier can be assigned to the reader by the device manufacturer. In some embodiments, the reader can be implemented by a terminal. In this case, the reader identifier can be represented by a terminal identifier. For example, the reader identifier of a terminal-type reader can include an International Mobile Equipment Identity (IMEI), a Media Access Control (MAC) address, an International Mobile Subscriber Identity (IMSI), a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), etc. In some embodiments, the reader can be implemented by a base station. In this case, the reader identifier can be represented by a base station identifier. For example, the reader identifier of a base station-type reader can include a global gNB identifier, a global eNB identifier, etc. In some embodiments, the reader identifier can be specifically assigned to an MC device that supports read / write operations for MC services.

[0190] In some embodiments, the topology type can be the topology type of a first service. In some embodiments, the topology type can include: Topology 1, Topology 2, Topology 3, and Topology 4. In some embodiments, the topology type related to the first service can include one or more of Topology 1, Topology 2, Topology 3, and Topology 4.

[0191] In some embodiments, the business area may be the region targeted by the first service. In some embodiments, the first service may be implemented for MC devices within the business area. In some embodiments, the business area may have a specific range, and the MC devices associated with the first service may be deployed within that range. For example, the business area may include a campus, industrial park, port, warehouse, or shopping mall.

[0192] In some embodiments, time usage can be the duration of the first service. In some embodiments, time usage can include the duration of the first service. In other words, time usage can be the duration of the first service from the start to the end of the service. In one example, time usage can be the duration from when the first node 101 receives the first data packet of the first service to the last data packet. In one example, time usage can be the duration of the first session of the first service.

[0193] In some embodiments, billing for the first service may also be related to a time period. In this case, time usage may also include the start and / or end times of the first service. In one example, time usage may include the start and / or end times of a day. For example, time usage may include a start time of 10:30 AM and / or an end time of 2:00 PM. In one example, time usage may include the start and / or end dates within a week. For example, time usage may include a start date of Monday and / or an end date of Friday. In one example, time usage may include the start and / or end dates within a year. For example, time usage may include a start date of December 3rd and / or an end date of December 5th.

[0194] In some embodiments, data usage can be the traffic data used to implement a first service. In one example, data usage may include the amount of data for the first service. It is understood that data usage is usage related to the traffic of data, and therefore may also be referred to as traffic (volume) usage.

[0195] In some embodiments, the event may be an event related to the billing of the first service. It is understood that the event is associated with a specific action. In other words, the associated event is satisfied when the specific action occurs. In some embodiments, the event related to the billing of the first service may be referred to as a billable event, a billing trigger condition, etc.

[0196] In some embodiments, see Table 1 below for an explanation of the categories of events.

[0197] In Table 1, PEC stands for pose event charging.

[0198] Referring to Table 1, events can be categorized into multiple types, such as business-related events and session-related events. Each category of events can include one or more behaviors. For example, session-related events can include the following two behaviors: MC session start and MC session end. Similarly, business-related events can include the following two behaviors: MC business start and MC business end.

[0199] In Table 1, the first column from the left lists the events-related behaviors. Different behaviors and scenarios can correspond to different types of messages. Message types can include event messages. Event messages, such as billing data requests (events), can be used to trigger event-based billing operations.

[0200] In some embodiments, the events given in Table 1 may have corresponding trigger levels. Trigger levels can be used to indicate the triggering priority or preference of the corresponding event. In some embodiments, different categories of events may correspond to different trigger levels.

[0201] In some embodiments, the event-related behaviors listed in Table 1 may have corresponding trigger levels. Trigger levels can be used to indicate the triggering priority or preference of the corresponding behavior. In some embodiments, different behaviors may correspond to different trigger levels.

[0202] In some embodiments, a service group may be the service group to which a first service belongs. In some embodiments, the service group may include one or more MC services. The first service may be a service within the service group. In some embodiments, the first service may be a service group, and the service group may include one or more MC services. In other words, the first service may include one or more MC services. In some embodiments, billing information for a service group may include the identification information of the service group. For example, the billing information may include the group identifier of the service group.

[0203] In some embodiments, the task may be a task associated with a first service. In some embodiments, the task in the billing information may include the first task. In some embodiments, the billing information for a task may include the task's identification information. For example, the billing information may include the task's identifier.

[0204] In some embodiments, the first node 101 may monitor usage based on at least one of the following: MC session, device owner, application function, device type, network, service type, rate group, and sponsor. In other words, the first node 101 may collect billing information based on at least one of the following: MC session, device owner, application function, device type, network, service type, rate group, charging key, and sponsor.

[0205] In some embodiments, an MC session may be identified by a service identifier and / or a task identifier. In some embodiments, usage monitoring may be performed on a per-service identifier basis. In some embodiments, billing information may be collected on a per-service identifier basis. In some embodiments, usage monitoring may be performed on a per-task identifier basis. In some embodiments, billing information may be collected on a per-task identifier basis.

[0206] In some embodiments, a device holder is the party that owns the MC device. In some embodiments, the holder may be identified by a holder identifier. In some embodiments, the holder may be identified by both the holder identifier and the device type of the MC device. In some embodiments, usage monitoring may be performed on a per-holder identifier basis. In some embodiments, usage monitoring may be performed on a per-holder identifier and per-device-type basis. In some embodiments, billing information may be collected on a per-holder identifier basis. In some embodiments, billing information may be collected on a per-holder identifier and per-device-type basis.

[0207] In some embodiments, application functionality may be identified by application functionality identifiers. In some embodiments, usage monitoring may be performed on a per-application-functional-identity basis. In some embodiments, billing information may be collected on a per-application-functional-identity basis.

[0208] In some embodiments, the device type can be diverse. In one example, the device type may include: MC device type, AIoT device type, device type 1, device type 2a, and device type 2b. It is understood that the device type may also include other types, and this disclosure does not specifically limit them.

[0209] In some embodiments, device type 1 may have low peak power consumption (e.g., about 1 μW), energy storage capability, and device-to-reader (D2R) transmission using backscattering.

[0210] In some embodiments, device type 2a may have a high peak power consumption (e.g., less than or equal to several hundred μW), energy storage capability, and D2R transmission employs backscattering.

[0211] In some embodiments, device type 2b may have higher peak power consumption (e.g., less than or equal to hundreds of μW), energy storage capacity, and D2R transmission is generated internally by this type of device.

[0212] In some embodiments, the network may be the network used to implement the first service. In some embodiments, the network may be identified by network information. In some embodiments, the network information may indicate the network operator. The first service may be implemented through the networks of one or more operators. In one example, usage monitoring may be performed on a per-operator network. In one example, billing information may be collected on a per-operator network. In some embodiments, the network information may indicate whether the network is a public or private network. The first service may be implemented through a public network. In one example, usage monitoring may be performed on a per-public network. In one example, billing information may be collected on a per-public network. The first service may be implemented through a private network. In one example, usage monitoring may be performed on a per-private network. In one example, billing information may be collected on a per-private network.

[0213] In some embodiments, the network implementing the first service may be associated with the deployment of the MC device. For example, the MC device associated with the first service may be deployed in the networks of one or more operators. For example, the MC device associated with the first service may be deployed in at least one public network and / or at least one private network. In some embodiments, network information used to indicate the network may be included in the identification information of the MC device. For example, the network information may be part of the device identifier of the MC device.

[0214] In some embodiments, service types may include inventory management services, command services, etc. Inventory management services can be used to implement inventory operations on MC devices. Command services can be used to implement operations such as reading, writing, invalidating, reporting environmental data, reporting sensed data, and subscribing to events related to MC devices. In some embodiments, service types may include MC services, AIoT services, massive machine-type communication (mMTC) services, etc. In some embodiments, usage monitoring can be performed for each service type. In some embodiments, billing information can be collected for each service type.

[0215] In some embodiments, a rate group may be a grouped entity subject to uniform billing. In some embodiments, a rate group may include at least one of the following: one or more services, one or more tasks, or one or more locations. In one example, one or more services may constitute a rate group. In one example, one or more tasks may constitute a rate group. In one example, one or more locations may constitute a rate group. In one example, one or more services for one or more locations may constitute a rate group. In one example, one or more tasks for one or more locations may constitute a rate group. In some embodiments, usage monitoring may be performed for each rate group. In some embodiments, billing information may be collected for each rate group.

[0216] In some embodiments, billing keywords can be used to identify specific groups or types and perform billing statistics at different rates. In some embodiments, billing keywords can be used to identify the required groups or types. In some embodiments, billing keywords can be used to identify the authorized groups or types. In some embodiments, usage monitoring can be performed on a per-billing-keyword basis. In some embodiments, billing information can be collected per-billing-keyword basis.

[0217] In some embodiments, the sponsor may be responsible for settling the costs of the first service. In other words, the sponsor may be responsible for making payments for the first service. In some embodiments, usage monitoring may be performed on a per-sponsor basis. In some embodiments, billing information may be collected per-sponsor. It is understood that the sponsor may be the same as or different from the provider of the first service and the holder of the MC device, and this disclosure does not specifically limit this.

[0218] In some embodiments, billing information may be collected for any one or more of the following: MC session, device owner, application function, device type, network, service type, rate group, and sponsor. In some embodiments, billing information may be collected for each MC session, and / or each device owner, and / or each application function, and / or each device type, and / or each network, and / or each service type, and / or each rate group, and / or each sponsor. In some embodiments, the collected billing information for each MC session, and / or each device owner, and / or each application function, and / or each device type, and / or each network, and / or each service type, and / or each rate group, and / or each sponsor may include one or more of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0219] In step S2104, the first node 101 sends the first information to the second node 102.

[0220] In some embodiments, the first node 101 may send first information. In some embodiments, the first information may be sent by the first node 101, but is not limited thereto, and may also be sent by other entities.

[0221] In some embodiments, the second node 102 may receive the first information. In some embodiments, the first information may be received by the second node 102, but is not limited thereto, and may also be received by other entities.

[0222] In some embodiments, the second node 102 may be determined in step S2101.

[0223] In some embodiments, the first information may be sent upon the triggering of a first event. In some embodiments, the first node 101 may determine that a first event related to a first service has been triggered and send the first information.

[0224] In some embodiments, the first event may include at least one of the following: the start of the first session, the end of the first session, the start of the first service, and the end of the first service.

[0225] In some embodiments, in step S2104, the first node 101 may send the first information when the first session begins or the first service begins.

[0226] In some embodiments, the first information can be used to implement billing for the first service. In some embodiments, the first information can be used to trigger the second node 102 to perform billing operations for the first service.

[0227] In some embodiments, the first information can be used to instruct the second node 102 to perform billing based on billing quantity data for the first service. In some embodiments, the first information instructing the second node 102 to perform billing based on billing quantity data for the first service can be understood as the first information being used by the second node 102 to perform billing according to the first information. In other words, after receiving the first information, the second node 102 can perform billing based on billing quantity data for the first service according to the content contained in the first information. It is understood that the first information can be used to trigger or command the second node 102 to perform billing based on billing quantity data for the first service. For example, the first information triggering the second node 102 to perform billing based on billing quantity data for the first service can be understood as the second node 102, after receiving the first information, determining to trigger billing based on billing quantity data according to the first information, or the first information triggering billing based on billing quantity data.

[0228] In some embodiments, the first information may include at least one of the following: billing indication information, event indication information, and billing quantity data.

[0229] In some embodiments, billing indication information can be used to trigger the second node 102 to perform a billing operation.

[0230] In some embodiments, the billing indication information may include a field. This field may include one or more bits. The field may have a first value. The first value is used to instruct the second node 102 to perform a billing operation.

[0231] In some embodiments, event indication information may be used to indicate a first event. In some embodiments, event indication information may indicate a first event that has been triggered in relation to a first service. In some embodiments, event indication information may indicate the start of a first session and / or the start of a first service.

[0232] In some embodiments, the event indication information may include a field. This field can indicate different first events with different values. For example, the field can indicate the start of a first service with a first value. For example, the field can indicate the start of a first session with a second value. For example, the field can indicate both the start of a first service and the start of a first session with a third value.

[0233] In some embodiments, the event indication information may include two fields. These two fields may each indicate a different first event. In one example, the first field may be used to indicate whether a first service has started. For example, the first field may indicate the start of a first service using a first value. In one example, the second field may be used to indicate whether a first session has started. For example, the second field may indicate the start of a first session using a first value. It is understood that both the first field indicating the start of a first service and the second field indicating the start of a first session can be implemented simultaneously, or only one of them can be implemented.

[0234] In some embodiments, the implementation of the first service may include data transmission on the user plane. In this case, the data transmission of the first service on the user plane can be implemented through one or more MC sessions. In some embodiments, the first session may include at least one MC session from one or more MC sessions of the first service. For example, the first session may include some MC sessions from one or more MC sessions of the first service. For example, the first session may include all MC sessions from one or more MC sessions of the first service. It should be noted that the MC session is not limited to the user plane; in some cases, the MC session may also be on the control plane or the data plane, and this disclosure does not specifically limit this.

[0235] In some embodiments, the billing volume data may be associated with the first service.

[0236] In some embodiments, the billing data may include at least one of the following: billing data related to the number of devices, billing data related to the tasks of the first service, billing data related to the data usage of the first service, billing data related to the time usage of the first service, and billing data related to the number of events of the first service.

[0237] In some embodiments, billing for the first service may be related to the number of MC devices associated with the first service. In some embodiments, the billing amount data related to the number of devices may include the number of MC devices. In some embodiments, billing is performed based on the number of MC devices supported by the network, and billing is performed based on a tariff or rate corresponding to a specific number. In some embodiments, the number of MC devices is related to the billing of the first service. In one example, different tariffs or rates may be used to implement billing for different number ranges. For example, billing for the first service corresponding to MC devices counted in thousands may use a first tariff or rate, and billing for the first service corresponding to MC devices counted in tens of thousands may use a second tariff or rate.

[0238] In some embodiments, billing for the first service may be associated with tasks within the first service. In some embodiments, the billing amount data associated with tasks in the first service may include at least one of the following: a task session request and a task session response. In some embodiments, a task session request may be used to request a session for a task. In some embodiments, a task session response may be a response to a task session request. In some embodiments, billing for the first service may be associated with the number of tasks in the first service. In one example, the number of tasks in the first service may be associated with the billing of the first service. In one example, different quantity ranges may be billed using different rates or tariffs. For example, billing for the first service corresponding to tasks counted in thousands may use a first rate or tariff, and billing for the first service corresponding to tasks counted in tens of thousands may use a second rate or tariff. In some embodiments, billing for the first service may be associated with the number of message interactions within tasks in the first service. In one example, the number of message interactions included in a task within the first service may be associated with the billing of the first service.

[0239] In some embodiments, billing for the first service may be associated with the data usage in the first service. In some embodiments, the billing amount data associated with the data usage of the first service may include the data usage of the first service. In one example, the billing amount data associated with the data usage of the first service may include the amount of data transmitted by the first node 101 for the first service.

[0240] In some embodiments, the billing data related to the data usage of the first service may include the billing data related to the data usage of a first session of the first service. In one example, the billing data related to the data usage of the first service may include the amount of data transmitted by the first node 101 for the first session of the first service.

[0241] In some embodiments, billing for the first service may be associated with time usage within the first service. In some embodiments, billing data associated with time usage of the first service may include the time usage of the first service. In one example, billing data associated with time usage of the first service may include at least one of the following: start time of the first service, completion time of the first service, duration of the first service, start time of the first task, end time of the first task, duration of the first task, start time of the first session, end time of the first session, and duration of the first session.

[0242] In some embodiments, billing for the first service may be associated with the number of events for the first service. In some embodiments, the billing amount data associated with the number of events for the first service may include the number of events for the first service.

[0243] In some embodiments, the first service may include one or more MC services. In this case, the billing volume data may include billing volume data related to the number of MC services. In some embodiments, billing for the first service may be associated with the number of MC services within the first service.

[0244] In some embodiments, billing volume data may be obtained for at least one of the following: MC session, device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor. In one example, billing volume data may be obtained for each MC session. In one example, billing volume data may be obtained for each device owner. In one example, billing volume data may be obtained for each application function. In one example, billing volume data may be obtained for each device type. In one example, billing volume data may be obtained for each network. In one example, billing volume data may be obtained for each service type. In one example, billing volume data may be obtained for each rate group. In one example, billing volume data may be obtained for each billing keyword. In one example, billing volume data may be obtained for each sponsor.

[0245] In some embodiments, the billing quantity data may be obtained based on billing information. In some embodiments, the first node 101 may collect the billing quantity data based on billing information.

[0246] In some embodiments, billing information may be associated with at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0247] In some embodiments, the monitoring and reporting of the usage of the first service by the first node 101 can be implemented according to a first rule. In some embodiments, the first rule may be configured for the first session of the first service and used by the first node 101 to monitor and report the usage.

[0248] In some embodiments, the first rule may be a usage reporting rule (URR). In some embodiments, the first rule may be a first session, which may be a packet forwarding control protocol (PFCP) session related to large-scale communication.

[0249] In some embodiments, the first rule may be determined by the third node 103 and provided to the first node 101.

[0250] In some embodiments, the first information may be carried in a first message. In some embodiments, the first node 101 may send a first message to the second node 102, the first message including the first information.

[0251] In step S2105, the second node 102 performs a billing operation.

[0252] In some embodiments, the second node 102 may perform billing operations based on the first information. In some embodiments, the second node 102 may perform billing operations related to a first service based on the first information. In some embodiments, the second node 102 may perform billing operations related to a first session based on the first information.

[0253] In some embodiments, the billing operations performed by the second node 102 may be account and rate control for the first service. In some embodiments, the billing operations performed by the second node 102 may include account and rate control for the first session. In some embodiments, the billing operations performed by the second node 102 may include account and rate control for the first task.

[0254] In some embodiments, a billing operation may include operations related to a charging data record (CDR). In some embodiments, a billing operation may include at least one of the following: creating a CDR, opening a CDR, or closing a CDR.

[0255] In some embodiments, if the first message is of type event message or initial message, the billing operation may include creating a CDR. In some embodiments, if the first message is of type event message or initial message, the billing operation may include opening a CDR. In some embodiments, if the first message is of type event message or termination message, the billing operation may include closing a CDR.

[0256] In some embodiments, the CDR may be for at least one of the following: a first service, a first session of a first service, or a first task of a first service.

[0257] In step S2106, the second node 102 sends a second message to the first node 101.

[0258] In some embodiments, the second node 102 may send a second message. In some embodiments, the second message may be sent by the second node 102, but is not limited thereto, and may also be sent by other entities.

[0259] In some embodiments, the first node 101 may receive the second message. In some embodiments, the second message may be received by the first node 101, but is not limited thereto, and may also be received by other entities.

[0260] In some embodiments, the second message may be sent by the second node 102 in response to the first message. In some embodiments, the second message may be a response message or an acknowledgment message to the first message.

[0261] In some embodiments, the second message may indicate acceptance of the billing request from the first message. In some embodiments, the second message may indicate that the billing request from the first message has been triggered. In some embodiments, the second message may indicate non-acceptance or rejection of the billing request from the first message.

[0262] In some embodiments, the message type of the second message can be the same as that of the first message. For example, if the first message is an initial message, then the second message can be an initial message. For example, if the first message is an event message, then the second message can be an event message. For example, if the first message is a termination message, then the second message can be a termination message.

[0263] In step S2107, the first node 101 continues to execute the first service.

[0264] In some embodiments, the first node 101 may continue to perform the business process of the first service through the first session.

[0265] In step S2108, the first service is completed.

[0266] In some embodiments, the first node 101 completes the transmission of all data and / or messages for the first service through a first session. In this case, the first service is completed.

[0267] In step S2109, the first node 101 sends the first information to the second node 102.

[0268] The optional implementation of step S2109 can be found in the optional implementation of step S2104 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0269] In step S2110, the second node 102 performs a billing operation.

[0270] The optional implementation of step S2110 can be found in the optional implementation of step S2105 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0271] In some embodiments, the type of the first message may be an event message or a termination message, and the billing operation may include closing the CDR.

[0272] In step S2111, the second node 102 sends a second message to the first node 101.

[0273] The optional implementation of step S2111 can be found in the optional implementation of step S2106 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0274] In step S2112, the first node 101 determines that the first service has been completed.

[0275] In some embodiments, upon receiving a second message, the first node 101 can determine that the first service has been completed. In some embodiments, the second message can be a confirmation message for the first message indicating that the first service has been completed. In this case, upon receiving the second message, the first node 101 can determine that the second node 102 has completed the billing operation and closed the CDR. Therefore, the first node 101 can determine that the first service has been completed.

[0276] The communication method of this embodiment can be implemented through steps S2101 to S2112.

[0277] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2112. For example, step S2103 may be implemented as a standalone embodiment, step S2104 may be implemented as a standalone embodiment, step S2109 may be implemented as a standalone embodiment, and a combination of steps S2103 and S2104 may be implemented as a standalone embodiment, but is not limited thereto.

[0278] In some embodiments, steps S2101, S2102, S2104, S2105, S2106, S2107, S2108, S2109, S2110, S2111, and S2112 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2101, S2102, S2103, S2104, S2105, S2106, S2107, S2108, S2110, S2111, and S2112 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0279] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc., from one subject to another passes through other subjects, it can be interpreted as the message being forwarded from one subject to another via other subjects, or it can be interpreted as the message being sent from one subject to another without passing through other subjects. For example, step S2114.

[0280] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0281] Figure 2B is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 2B, the communication method of the embodiment of the present disclosure includes steps S2201 to S2216.

[0282] In step S2201, the third node 103 determines the second node 102.

[0283] The optional implementation of step S2201 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0284] In some embodiments, the third node 103 may determine the second node 102 through a discovery and selection process. For example, the third node 103 may determine the second node 102 through NRF discovery and selection.

[0285] In some embodiments, step S2201 can be performed during the session establishment process of the first service. In some embodiments, during the session establishment process of the first service, the third node 103 can determine the second node 102.

[0286] In some embodiments, step S2201 can be performed after the MC session establishment process of the first service. In some embodiments, after the session establishment process of the first service is completed, the third node 103 can determine the second node 102.

[0287] In some embodiments, an MC session, or first session, can be established for a first service through the MC session establishment process. The first session can be used to implement the transmission of messages and / or data for the first service.

[0288] In some embodiments, step S2201 may be executed during the registration process of the fifth node 105. In some embodiments, step S2201 may be executed during the registration process of the fourth node 104. In some embodiments, step S3201 may be executed upon receiving a service request from the AF.

[0289] In some embodiments, through step S2201, the third node 103 can obtain the address information of the second node 102. For example, the third node 103 can obtain the IP address of the second node 102.

[0290] In step S2202, the third node 103 receives a service request.

[0291] The optional implementation of step S2202 can be found in the optional implementation of step S2102 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0292] In step S2203, the first node 101 monitors the usage.

[0293] The optional implementation of step S2203 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0294] In step S2204, the first node 101 sends the first information to the third node 103.

[0295] In some embodiments, the first node 101 may send first information. In some embodiments, the first information may be sent by the first node 101, but is not limited thereto, and may also be sent by other entities.

[0296] In some embodiments, the third node 103 may receive the first information. In some embodiments, the first information may be received by the third node 103, but is not limited thereto, and may also be received by other entities.

[0297] In some embodiments, the first information may be sent upon the triggering of a first event. In some embodiments, the first node 101 may determine that a first event related to a first service has been triggered and send the first information.

[0298] In some embodiments, the first event may include at least one of the following: the start of the first session, the end of the first session, the start of the first service, and the end of the first service.

[0299] In some embodiments, in step S2204, the first node 101 may send the first information when the first session begins or the first service begins.

[0300] In some embodiments, the first information can be used to implement billing for the first service. In some embodiments, the first information can be used to trigger the second node 102 to perform billing operations for the first service.

[0301] In some embodiments, the first information may include at least one of the following: billing indication information, event indication information, and billing quantity data.

[0302] In some embodiments, billing indication information can be used to trigger the second node 102 to perform a billing operation.

[0303] In some embodiments, the billing indication information may include a field. This field may include one or more bits. The field may have a first value. The first value is used to instruct the second node 102 to perform a billing operation.

[0304] In some embodiments, event indication information may be used to indicate a first event. In some embodiments, event indication information may indicate a first event that has been triggered in relation to a first service. In some embodiments, event indication information may indicate the start of a first session and / or the start of a first service.

[0305] In some embodiments, the event indication information may include a field. This field can indicate different first events with different values. For example, the field can indicate the start of a first service with a first value. For example, the field can indicate the start of a first session with a second value. For example, the field can indicate both the start of a first service and the start of a first session with a third value.

[0306] In some embodiments, the event indication information may include two fields. These two fields may each indicate a different first event. In one example, the first field may be used to indicate whether a first service has started. For example, the first field may indicate the start of a first service using a first value. In one example, the second field may be used to indicate whether a first session has started. For example, the second field may indicate the start of a first session using a first value. It is understood that both the first field indicating the start of a first service and the second field indicating the start of a first session can be implemented simultaneously, or only one of them can be implemented.

[0307] In some embodiments, the billing volume data may be associated with the first service.

[0308] In some embodiments, the billing data may include at least one of the following: billing data related to the number of devices, billing data related to the tasks of the first service, billing data related to the data usage of the first service, billing data related to the time usage of the first service, and billing data related to the number of events of the first service.

[0309] In some embodiments, billing for the first service may be related to the number of MC devices associated with the first service. In some embodiments, the billing amount data related to the number of devices may include the number of MC devices.

[0310] In some embodiments, billing for the first service may be associated with a task within the first service. In some embodiments, the billing amount data associated with a task in the first service may include at least one of the following: a task session request and a task session response. In some embodiments, a task session request may be used to request a session for a task. In some embodiments, a task session response may be a response to a task session request.

[0311] In some embodiments, billing for the first service may be associated with the data usage in the first service. In some embodiments, the billing amount data associated with the data usage of the first service may include the data usage of the first service. In one example, the billing amount data associated with the data usage of the first service may include the amount of data transmitted by the first node 101 for the first service.

[0312] In some embodiments, billing for the first service may be associated with time usage within the first service. In some embodiments, billing data associated with time usage of the first service may include the time usage of the first service. In one example, billing data associated with time usage of the first service may include at least one of the following: start time of the first service, completion time of the first service, duration of the first service, start time of the first task, end time of the first task, duration of the first task, start time of the first session, end time of the first session, and duration of the first session.

[0313] In some embodiments, billing for the first service may be associated with the number of hours of the first service. In some embodiments, the billing amount data associated with the number of events of the first service may include the number of events of the first service.

[0314] In some embodiments, the first service may include one or more MC services. In this case, the billing volume data may include billing volume data related to the number of MC services. In some embodiments, billing for the first service may be associated with the number of MC services within the first service.

[0315] In some embodiments, billing volume data may be obtained for at least one of the following: MC session, device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor. In one example, billing volume data may be obtained for each MC session. In one example, billing volume data may be obtained for each device owner. In one example, billing volume data may be obtained for each application function. In one example, billing volume data may be obtained for each device type. In one example, billing volume data may be obtained for each network. In one example, billing volume data may be obtained for each service type. In one example, billing volume data may be obtained for each rate group. In one example, billing volume data may be obtained for each billing keyword. In one example, billing volume data may be obtained for each sponsor.

[0316] In some embodiments, the billing quantity data may be obtained based on billing information. In some embodiments, the first node 101 may collect the billing quantity data based on billing information.

[0317] In some embodiments, billing information may be associated with at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

[0318] In some embodiments, the monitoring and reporting of the usage of the first service by the first node 101 can be implemented according to a first rule. In some embodiments, the first rule may be configured for the first session of the first service and used by the first node 101 to monitor and report the usage.

[0319] In some embodiments, the first rule may be a URR. In some embodiments, the first rule may be a first session, which may be a PFCP session related to large-scale communication.

[0320] In some embodiments, the first rule may be determined by the third node 103 and provided to the first node 101.

[0321] In step S2205, the third node 103 sends the first information to the second node 102.

[0322] In some embodiments, the third node 103 may send a first message. In some embodiments, the first message may be sent by the third node 103, but is not limited to this, and may also be sent by other entities.

[0323] In some embodiments, the second node 102 may receive the first message. In some embodiments, the first message may be received by the second node 102, but is not limited thereto, and may also be received by other entities.

[0324] In some embodiments, the third node 103 may be determined in step S3201.

[0325] In some embodiments, the third node 103 may send the received first message to the second node 102. In some embodiments, the third node 103 may send the received first information to the second node 102.

[0326] In step S2206, the second node 102 performs a billing operation.

[0327] The optional implementation of step S2206 can be found in the optional implementation of step S2105 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0328] In step S2207, the second node 102 sends a second message to the third node 103.

[0329] In some embodiments, the second node 102 may send a second message. In some embodiments, the second message may be sent by the second node 102, but is not limited thereto, and may also be sent by other entities.

[0330] In some embodiments, the third node 103 may receive the second message. In some embodiments, the second message may be received by the third node 103, but is not limited thereto, and may also be received by other entities.

[0331] In some embodiments, the second message may be sent by the second node 102 in response to the first message. In some embodiments, the second message may be a response message or an acknowledgment message to the first message.

[0332] In some embodiments, the second message may indicate acceptance of the billing request from the first message. In some embodiments, the second message may indicate that the billing request from the first message has been triggered. In some embodiments, the second message may indicate non-acceptance or rejection of the billing request from the first message.

[0333] In some embodiments, the message type of the second message can be the same as that of the first message. For example, if the first message is an initial message, then the second message can be an initial message. For example, if the first message is an event message, then the second message can be an event message. For example, if the first message is a termination message, then the second message can be a termination message.

[0334] In step S2208, the third node 103 sends a second message to the first node 101.

[0335] In some embodiments, the third node 103 may send a second message. In some embodiments, the second message may be sent by the third node 103, but is not limited thereto, and may also be sent by other entities.

[0336] In some embodiments, the first node 101 may receive the second message. In some embodiments, the second message may be received by the first node 101, but is not limited thereto, and may also be received by other entities.

[0337] In step S2209, the first node 101 continues to execute the first service.

[0338] In some embodiments, the first node 101 may continue to perform the business process of the first service through the first session.

[0339] In step S2210, the first service is completed.

[0340] In some embodiments, the first node 101 completes the transmission of all data and / or messages for the first service through a first session. In this case, the first service is completed.

[0341] In step S2211, the first node 101 sends a first message to the third node 103.

[0342] The optional implementation of step S2211 can be found in the optional implementation of step S2204 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0343] In step S2212, the third node 103 sends a first message to the second node 102.

[0344] The optional implementation of step S2212 can be found in the optional implementation of step S2205 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0345] In step S2213, the second node 102 performs a billing operation.

[0346] The optional implementation of step S2213 can be found in the optional implementation of step S2205 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0347] In some embodiments, the type of the first message may be an event message or a termination message, and the billing operation may include closing the CDR.

[0348] In step S2214, the second node 102 sends a second message to the third node 103.

[0349] The optional implementation of step S2214 can be found in the optional implementation of step S2207 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0350] In step S2215, the third node 103 sends a second message to the first node 101.

[0351] The optional implementation of step S2215 can be found in the optional implementation of step S2208 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0352] In step S2216, the first node 101 determines that the first service has been completed.

[0353] The optional implementation of step S2216 can be found in the optional implementation of step S2112 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0354] In some embodiments, upon receiving a second message, the first node 101 can determine that the first service has been completed. In some embodiments, the second message can be a confirmation message for the first message indicating that the first service has been completed. In this case, upon receiving the second message, the first node 101 can determine that the second node 102 has completed the billing operation and closed the CDR. Therefore, the first node 101 can determine that the first service has been completed.

[0355] In some embodiments, upon receiving the second message, the third node 103 can determine that the first service has been completed. In some embodiments, the second message can be a confirmation message for the first message indicating that the first service has been completed. In this case, upon receiving the second message, the third node 103 can determine that the second node 102 has completed the billing operation and closed the CDR. Therefore, the third node 103 can determine that the first service has been completed.

[0356] The communication method of this embodiment can be implemented through steps S2201 to S2216.

[0357] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2216. For example, step S2203 may be implemented as a standalone embodiment, step S2204 may be implemented as a standalone embodiment, step S2205 may be implemented as a standalone embodiment, step S2210 may be implemented as a standalone embodiment, step S2211 may be implemented as a standalone embodiment, a combination of steps S2204 and S2205 may be implemented as a standalone embodiment, a combination of steps S2210 and S2211 may be implemented as a standalone embodiment, and a combination of steps S2203, S2204, and S2205 may be implemented as a standalone embodiment, but is not limited thereto.

[0358] In some embodiments, steps S2201, S2202, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2212, S2213, S2214, S2215, and S2216 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201, S2202, S2203, S2204, S2206, S2207, S2208, S2209, S2210, S2211, S2212, S2213, S2214, S2215, and S2216 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2201, S2202, S2203, S2204, S2205, S2206, S2207, S2208, S2209, S2210, S2211, S2213, S2214, S2215, and S2216 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0359] In some embodiments, if the arrow in the interaction diagram representing the sending of information, signaling, etc., from one subject to another passes through other subjects, it can be interpreted as the message being forwarded from one subject to another via other subjects, or it can be interpreted as the message being sent from one subject to another without passing through other subjects. For example, steps S2207, S2212, and S2216.

[0360] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0361] Figure 2C is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. The communication method involved in the embodiment of the present disclosure can be applied to the communication system 100. As shown in Figure 3C, the communication method of the embodiment of the present disclosure includes steps S2301 to S2309.

[0362] In step S2301, the third node 103 sends third information to the second node 102.

[0363] In some embodiments, the third node 103 may send third information. In some embodiments, the third information may be sent by the third node 103, but is not limited thereto, and may also be sent by other entities.

[0364] In some embodiments, the second node 102 may receive third information. In some embodiments, the third information may be received by the second node 102, but is not limited thereto, and may also be received by other entities.

[0365] In some embodiments, the third information may be used to request a credit limit for the billing data of the first service. In some embodiments, the third information may be used to request a credit limit for the usage of the first service.

[0366] In step S2302, the second node 102 sends the fourth information to the third node 103.

[0367] In some embodiments, the second node 102 may send fourth information. In some embodiments, the fourth information may be sent by the second node 102, but is not limited thereto, and may also be sent by other entities.

[0368] In some embodiments, the third node 103 may receive fourth information. In some embodiments, the fourth information may be received by the third node 103, but is not limited thereto, and may also be received by other entities.

[0369] In some embodiments, the fourth information can be used to allocate a credit limit for the first service. In some embodiments, the fourth information can be used to authorize a credit limit for the first service.

[0370] In some embodiments, the fourth information may include at least one of the following: a first quota, a second quota, and a first threshold.

[0371] In some embodiments, the first quota is the maximum usage of billing data allocated for the first service on the first node 101. It is understood that the first quota is the current maximum usage allocated for the billing data of the first service on a single first node 101. That is, when the billing data of the first service reaches or is close to the current maximum usage corresponding to the first quota, the maximum usage of the billing data allocated for the first service on the first node 101 can be adjusted using a new first quota (e.g., step S3307). For example, a larger quota can be allocated for the billing data of the first service on the first node 101, i.e., the maximum usage increases.

[0372] In some embodiments, the billing data associated with the first quota may include at least one of the following: billing data related to the number of devices, billing data related to the tasks of the first service, billing data related to the data usage of the first service, billing data related to the time usage of the first service, and billing data related to the number of events of the first service. In some embodiments, the first quota may include a quota associated with one of the following: billing data related to the number of devices, billing data related to the tasks of the first service, billing data related to the data usage of the first service, billing data related to the time usage of the first service, and billing data related to the number of events of the first service. In one example, the first quota may include a maximum number of devices. In one example, the first quota may include a maximum number of tasks of the first service. In one example, the first quota may include a maximum data usage of the first service. For example, the first quota may include a maximum amount of data transmitted in a first session of the first service. In one example, the first quota may include a maximum amount of time usage of the first service. For example, the first quota may include a maximum duration of the first service. In one example, the first quota may include a maximum number of events of the first service.

[0373] In some embodiments, the second quota is the maximum usage of billing data allocated for the first service. It is understood that the first quota is the current maximum usage of billing data allocated for the first service. In some embodiments, the first service may be associated with one or more first nodes 101, then the second quota may be the total maximum usage of billing data allocated for the first service on these one or more nodes 101. In some embodiments, the billing data associated with the second quota may include at least one of the following: billing data related to the number of devices, billing data related to the tasks of the first service, billing data related to the data usage of the first service, billing data related to the time usage of the first service, and billing data related to the number of events of the first service.

[0374] In some embodiments, a first threshold can be used to trigger the first node 101 to report billing data. In some embodiments, the first threshold can be less than or equal to a first quota. When the usage of a first service meets the first threshold, the first node 101 can report billing data.

[0375] In some embodiments, the first threshold may be related to at least one of the following: billing data related to the number of devices, billing data related to the tasks of the first service, billing data related to the data usage of the first service, billing data related to the time usage of the first service, and billing data related to the number of events of the first service.

[0376] In some embodiments, the first threshold may be set for the amount of usage already used. In some embodiments, the reporting of billing data may be triggered when the amount of usage of the first service reaches or exceeds the first threshold.

[0377] In some embodiments, the first threshold may be set for the remaining usage. In some embodiments, the reporting of billing data may be triggered when the unused usage of the first service is equal to or less than the first threshold.

[0378] In some embodiments, the fourth information may be sent in response to the third information. In some embodiments, after receiving the third information, the second node 102 may set a first quota, and / or a second quota, and / or a first threshold, and include them in the fourth information.

[0379] In some embodiments, the number of first nodes 101 associated with the first service can be one or more. In some embodiments, when there are multiple first nodes 101, the second quota can be a total quota set for multiple first nodes 101, and the first quota can be a quota set for each individual first node 101. In some embodiments, different first nodes 101 can have the same first quota or different first quotas. In some embodiments, the first threshold can be set for a single first node 101. In some embodiments, different first nodes 101 can have the same first threshold or different first thresholds.

[0380] In step S2303, the third node 103 sends the second information to the first node 101.

[0381] In some embodiments, the third node 103 may send second information. In some embodiments, the second information may be sent by the third node 103, but is not limited thereto, and may also be sent by other entities.

[0382] In some embodiments, the first node 101 may receive the second information. In some embodiments, the second information may be received by the first node 101, but is not limited thereto, and may also be received by other entities.

[0383] In some embodiments, the second information can be used to allocate a quota for the first service on the first node 101. In some embodiments, the fourth information can be used to authorize a quota for the first service on the first node 101.

[0384] In some embodiments, the second information may include a first quota and / or a first threshold.

[0385] In some embodiments, the second information may include a first rule. In some embodiments, the second information may be used to send the first rule to the first node 101. In some embodiments, the first rule may be used by the first node 101 to monitor and / or report billing data.

[0386] In some embodiments, the first rule may include a first quota and / or a first threshold.

[0387] In some embodiments, the second information may be carried in the session modification request message.

[0388] In some embodiments, after receiving the fourth information from the second node 102, the third node 103 may send the second information to the first node 101 based on the fourth information.

[0389] In some embodiments, the first quota carried in the fourth message may be a quota for the first node 101. In some embodiments, the third node 103 may use the first quota received from the second node 102 as a quota for the first node 101. In some embodiments, the third node 103 may determine the quota of the first node 101 based on the second quota received from the second node 102. For example, the first quota carried in the second message may be determined by the third node 103 based on the second quota carried in the fourth message.

[0390] In some embodiments, the first threshold carried in the fourth message may be a threshold for the first node 101. In some embodiments, the third node 103 may use the first threshold received from the second node 102 as a threshold for the first node 101.

[0391] In step S2304, the first node 101 monitors the usage.

[0392] The optional implementation of step S2304 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0393] In step S2305, the first node 101 sends the first information to the third node 103.

[0394] The optional implementation of step S2305 can be found in the optional implementation of step S2204 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0395] In some embodiments, the first node 101 may send first information. In some embodiments, the first information may be sent by the first node 101, but is not limited thereto, and may also be sent by other entities.

[0396] In some embodiments, the third node 103 may receive the first information. In some embodiments, the first information may be received by the third node 103, but is not limited thereto, and may also be received by other entities.

[0397] In some embodiments, the first information may be used to implement billing for the first service.

[0398] In some embodiments, the first node 101 may send first information upon triggering a first event. In some embodiments, the first event may include the billing data of the first service reaching a first threshold. In some embodiments, the first event may include the usage of the billing data of the first service meeting a first threshold. In one example, the first threshold may be set for the used usage of the first service. For example, the first event may be triggered when the used usage of the first service reaches or exceeds the first threshold. In one example, the first threshold may be set for the unused (i.e., remaining) usage of the first service. For example, the first event may be triggered when the unused usage of the first service is equal to or lower than the first threshold.

[0399] In some embodiments, the first threshold may be related to at least one of the following: billing data related to the number of devices, billing data related to the tasks of the first service, billing data related to the data usage of the first service, billing data related to the time usage of the first service, and billing data related to the number of events of the first service. In one example, if the first threshold corresponding to the billing data related to the number of devices is satisfied, the first node 101 can determine that the first event has been triggered. In one example, if the first threshold corresponding to the billing data related to the tasks of the first service is satisfied, the first node 101 can determine that the first event has been triggered. In one example, if the first threshold corresponding to the billing data related to the data usage of the first service is satisfied, the first node 101 can determine that the first event has been triggered. In one example, if the first threshold corresponding to the billing data related to the number of events of the first service is satisfied, the first node 101 can determine that the first event has been triggered. It should be noted that the first thresholds for the various billing data mentioned above can be used in any combination. For example, if the first threshold corresponding to the billing amount data related to the data usage of the first service is met, and the first threshold corresponding to the billing amount data related to the number of devices is met, the first node 101 can determine that the first event is triggered.

[0400] In some embodiments, the first information may include at least one of the following: billing indication information, event indication information, and billing quantity data.

[0401] In some embodiments, event indication information may be used to indicate that the billing amount data of the first service has reached a first threshold.

[0402] In some embodiments, the first information may be carried in the first message. In some embodiments, the first message may be a session reporting request message.

[0403] It should be noted that when the first node 101 sends the first information, the first node 101 can continue to transmit the message and / or data of the first service until the billing amount data of the first service reaches the first quota of the first node 101.

[0404] In step S2306, the third node 103 sends third information to the second node 102.

[0405] The optional implementation of step S2306 can be found in the optional implementation of step S2301 in Figure 2C, as well as other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0406] In some embodiments, upon receiving information from the first node 101, the third node 103 may send a third message to the second node 102 to request a new quota.

[0407] In some embodiments, the third information may include the first information. In some embodiments, the third information may be sent together with the first information to the second node 102.

[0408] In some embodiments, through steps S2305 and S3306, the first node 101 can send first information to the second node 102 through the third node 103.

[0409] In some embodiments, the first node 101 can directly send the first information to the third node 103. In this case, the first information may bypass the third node 103 or may be transmitted transparently at the third node 103.

[0410] In step S2307, the second node 102 sends the fourth information to the third node 103.

[0411] The optional implementation of step S2307 can be found in the optional implementation of step S2302 in Figure 2C, as well as other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0412] In some embodiments, the second node 102 may allocate a new first quota, and / or a second quota, and / or a first threshold. In some embodiments, the second node 102 may authorize a new first quota, and / or a second quota, and / or a first threshold.

[0413] In some embodiments, the first quota in step S2307 may be the same as or different from the first quota in step S2302. In some embodiments, the first threshold in step S2307 may be the same as or different from the first threshold in step S2302.

[0414] In some embodiments, the first quota in step S2307 may include the first quota in step S2302. For example, the first quota in step S2302 may be a first quantity, and the first quota in step S2307 may be a second quantity, and the second quantity may be greater than the first quantity. Then, the newly allocated quota in step S2307 is the difference between the second quantity and the first quantity. In other words, the increment of the quota is the difference between the second quantity and the first quantity.

[0415] In some embodiments, the first quota in step S2307 may not include the first quota in step S2302. For example, the first quota in step S2302 may be a first quantity, and the first quota in step S2307 may be a second quantity. Then, the newly allocated quota in step S2307 is the second quantity. In other words, the increment of the quota is the second quantity. In this case, the second quantity may be greater than, equal to, or less than the first quantity.

[0416] In some embodiments, the second quota in step S2307 may be the same as or different from the second quota in step S2302.

[0417] In some embodiments, the second quota in step S2307 may include the second quota in step S2302. For example, the second quota in step S2302 may be a third quantity, and the second quota in step S2307 may be a fourth quantity, and the second quantity may be greater than the third quantity. Then, the newly allocated quota through step S2307 is the difference between the fourth and third quantities. In other words, the quota increment is the difference between the fourth and third quantities.

[0418] In some embodiments, the second quota in step S2307 may not include the second quota in step S2302. For example, the second quota in step S2302 may be a third quantity, and the second quota in step S2307 may be a fourth quantity. Then, the newly allocated quota in step S2307 is the fourth quantity. In other words, the quota increment is the fourth quantity. In this case, the fourth quantity may be greater than, equal to, or less than the third quantity.

[0419] In step S2308, the third node 103 sends the second information to the first node 101.

[0420] The optional implementation of step S2308 can be found in the optional implementation of step S2303 in Figure 2C, as well as other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0421] In step S2309, the first node 101 monitors the usage.

[0422] The optional implementation of step S2309 can be found in the optional implementation of step S2304 in Figure 2C, as well as other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0423] In some embodiments, if the usage of the first service reaches the first quota, the first node 101 may stop transmitting messages and / or data for the first service.

[0424] In some embodiments, if the usage reaches the first quota recently acquired by the first node 101, the first node 101 and the third node 103 may terminate the first service.

[0425] The communication method of this disclosure embodiment can be implemented through steps S2301 to S2309.

[0426] The communication method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2309. For example, step S2301 may be implemented as an independent embodiment, step S2302 may be implemented as an independent embodiment, step S2303 may be implemented as an independent embodiment, step S2305 may be implemented as an independent embodiment, step S2306 may be implemented as an independent embodiment, step S2307 may be implemented as an independent embodiment, a combination of steps S2301 and S2302 may be implemented as an independent embodiment, a combination of steps S2302 and S2303 may be implemented as an independent embodiment, a combination of steps S2306 and S2307 may be implemented as an independent embodiment, and a combination of steps S2301, S2302 and S2303 may be implemented as an independent embodiment, but is not limited thereto.

[0427] In some embodiments, steps S2306 and S2309 may be performed in an alternate order or simultaneously.

[0428] In some embodiments, steps S2302, S2303, S2304, S2305, S2306, S2307, S2308, and S2309 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S2301, S2303, S2304, S2305, S2306, S2307, S2308, and S2309 are optional, and one or more of these steps may be omitted or substituted in different embodiments. Steps S2301, S2302, S2303, S2304, S2306, S2307, S2308, and S2309 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0429] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0430] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0431] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0432] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0433] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0434] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0435] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0436] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0437] In some embodiments, the terms "service", "business", and "traffic" can be used interchangeably.

[0438] In some embodiments, the terms "billing data", "usage data", and "billing usage data" can be used interchangeably.

[0439] Figure 3 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 3, the method includes steps S301 and S302.

[0440] In step S301, the first node 101 determines that the first event has been triggered.

[0441] In step S302, the first node 101 sends the first information to the second node 102.

[0442] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0443] Figure 4 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This disclosure relates to a communication method. As shown in Figure 4B, the method includes steps S401 and S403.

[0444] In step S401, the first node 101 determines that the first event has been triggered.

[0445] In step S402, the first node 101 sends the first information to the third node 103.

[0446] In step S403, the third node 103 sends the first information to the second node 102.

[0447] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0448] In the following, the technical solutions of the embodiments of this disclosure will be described by way of specific implementation.

[0449] In some embodiments, a large-scale communication billing method (monitored and reported by UPF) is proposed to support large-scale (e.g., environmental IoT) services, thereby meeting the billing requirements of the services.

[0450] In some embodiments, the UPF (i.e., the first node) supports the collection and reporting of usage data or time for billing purposes. In some embodiments, the UPF supports the monitoring and reporting of billing information (e.g., to the CHF, directly, or via the MCF or AIoTF). In some embodiments, billing amounts or events can be monitored or reported:

[0451] - For each MC session (e.g., an AIoT session), it can be identified by a session ID (identifier) ​​or a task ID;

[0452] - For each holder (which can be identified by the holder ID, or the holder ID and MC device type);

[0453] - For each AF (which can be identified by the AF ID);

[0454] - For each device type (which can be identified by device type, e.g., MC device type, AIoT device type, device 1, device 2a, device 2b);

[0455] - For each network (which can be identified by network information, such as network information in the device ID, e.g., public / private network, carrier);

[0456] - For each service type (which can be identified by the service type, such as inventory service operation or command service operation, or AIoT service, or 6G mMTC service);

[0457] - For each rate group / billing keyword (e.g., each group or type of billing keyword required or authorized);

[0458] - For each sponsor (identified by sponsor ID, or sponsor ID and application server provider (ASP) ID).

[0459] In some embodiments, the UPF supports the monitoring and reporting of billing information (e.g., to the CHF, directly, or via the MCF or AIoTF), and can collect billing information. In some embodiments, the billing information may include:

[0460] - Reader type (e.g., reader type for environmental IoT services, base station (BS) reader, UE reader);

[0461] - Reader ID (e.g., reader ID for environmental IoT business);

[0462] - Topology type (e.g., topology type for environmental IoT business);

[0463] - Business area (e.g., the business campus);

[0464] - Time usage (e.g., time period for environmental IoT business);

[0465] - Data usage (e.g., data usage in environmental IoT business);

[0466] - Events / tasks / groups (e.g., events, groups, or tasks in environmental IoT, identified by event type, group ID, or task ID).

[0467] In some embodiments, interaction with CHF (i.e., the second node) is possible.

[0468] In some embodiments, MC service billing is performed through interaction between the UPF and CHF (directly or via the MCF or AIoTF). In some embodiments, billing quantity data includes:

[0469] - Billing data related to the number of devices (e.g., the number of devices in an MC device);

[0470] - Billing data related to tasks in the MC business (e.g., task session requests and responses for the business);

[0471] - Billing data related to data usage of MC services (e.g., data usage of services);

[0472] - Billing data related to the time usage of MC services (e.g., time usage of services);

[0473] - Billing data related to the number of events in the MC service (e.g., event usage of the service).

[0474] In some embodiments, the billing data related to the number of devices, the tasks of the MC service, the data usage of the MC service, the time usage of the MC service, and the number of events of the MC service can be per device type / per AF / per task / per reader / per topology type / per service area / per session.

[0475] In some embodiments, indirect reporting from UPF to CHF (e.g., via MCF / AIoTF) is described.

[0476] In some embodiments, for indirect reporting from UPF to CHF to enable MC service billing, MC (e.g., AIoT) billing is supported by MCF / AIoTF and UPF.

[0477] In some embodiments, MCF supports MC / AIoTF session and service billing. In some embodiments, UPF sets MC billing indication in the UPF feature list to support MC / AIoT billing.

[0478] In some embodiments, if the MCF and UPF support MC billing, the SMF requests the UPF to measure and report the amount of MC data transmitted for the entire MC session (or, for location-dependent MC sessions, as part of the MC session based on location).

[0479] In some embodiments, the MCF provides a URR in the UPF for MC sessions (e.g., PFCP sessions associated with MC), such as data volume-based measurements for reporting MC data usage via the interface between the MCF / AioTF and the UPF.

[0480] In some embodiments, if there are multiple UPFs for a single MC (e.g., AIoT) PDU session, quota management can be applied to all UPFs or to each UPF, and use case and billing information reporting can be applied to each UPF.

[0481] In some embodiments, the UPF (optionally, or the MCF or AIoTF) supports CHF discovery and selection functionality. In some embodiments, this functionality is used by the UPF (or MCF or AIoTF) to select the CHF that manages billing (e.g., PDU sessions for MC service sessions / AIoT service sessions, etc.).

[0482] In some embodiments, the UPF directly selects the CHF address for billing reporting. CHF address selection can be completed during the session establishment process with the network (or device / reader registration), or it can be completed during the process of receiving a service request from the AF.

[0483] In some embodiments, the selected CHF address is used for the collection and reporting of billing events / data for AF, business, sponsor, rate group, or billing keyword, taking into account registered readers, devices, business areas, tasks, etc.

[0484] In some embodiments, a billable event (i.e., the first event) can be a trigger condition and category supported by UPF.

[0485] In some embodiments, a billing data request is sent to the CHF when specific conditions (billing events) are met. In some embodiments, when a billing event is sent to the CHF, it may include identifiers such as device ID, reader ID, task ID, service ID, AF ID, and sponsor ID.

[0486] In some embodiments, billing trigger conditions (billing events) are specified along with the associated behavior at implementation time. See Table 1 for the trigger conditions and categories supported by UPF.

[0487] Figure 5A is an interactive schematic diagram of an exemplary embodiment of the communication method provided according to an embodiment of the present disclosure. This communication method relates to event charging with unit reservation (ECUR) for an MC session or a task within an MC session. Here, the charging message for the MC session or task within the ECR is described. As shown in Figure 5A, the communication method includes the following steps:

[0488] Step 0: The MC session establishment process is complete, and the CHF is selected. The CHF is selected by the UPF, or by the MCF or AIoTF.

[0489] Step 1: The MCF / AIoTF receives the MC session or task requested by the MC service, such as inventory or command of the AIoT service.

[0490] Step 2: For the MC session or task requesting the UPFMC service, send a billing data request (initial) to the CHF. In some embodiments, if the reporting is indirect through the MCF, step 2a is performed, reporting from the UPF to the CHF via the MCF / AIoTF.

[0491] Step 3: CHF performs account and rate control for the MC session or task for the MC business and opens CDR.

[0492] Step 4: CHF confirms by sending a billing data response (initial), and UPF authorizes the MC session or task of the MC service. If reporting is indirectly through MCF, then step 4a is executed, from CHF to UPF via MCF / AIoTF.

[0493] Step 5: For the business, continue the MC session or task process of the MC business (including business requests, inventory requests / responses, command requests / responses, and environmental data of devices / readers).

[0494] Step 6: The MC session or task process of the MC business is completed.

[0495] Step 7: For the MC session or task of the MC service, the UPS sends a billing data request (terminated) to the CHF. If the reporting is indirect through the MCF, then step 7a is executed, and the data reaches the CHF from the UPF via the MCF / AIoTF.

[0496] Step 8: For the MC session or task of the MC service, CHF disables CDR.

[0497] Step 9: CHF confirms by sending a billing data response (termination) to UPF. If reporting is done indirectly through MCF, then step 9a is executed, from CHF to UPF via MCF / AIoTF.

[0498] Step 10: MCF / AIoTF receives CHF's acknowledgment (ACK) and confirms that the MC session or task of the MC service is completed.

[0499] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0500] Figure 5B is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. This communication method involves usage monitoring and reporting of MC services between the UPF and MCF / AIoTF.

[0501] In some embodiments, for indirect reporting from UPF to CHF to enable MC service billing, MC (AIoT) billing is supported by MCF / AIoTF and UPF.

[0502] In some embodiments, MCF supports MC / AIoTF session and service billing. In some embodiments, UPF sets MC billing indication in the UPF feature list to support MC / AIoT billing.

[0503] In some embodiments, if the MCF and UPF support MC billing, the SMF requests the UPF to measure and report the amount of MC data transmitted for the entire MC session (or, for location-dependent MC sessions, as part of the MC session based on location).

[0504] In some embodiments, the MCF provides a URR in the UPF for MC sessions (e.g., PFCP sessions associated with MC), such as data volume-based measurements for reporting MC data usage via the interface between the MCF / AioTF and the UPF.

[0505] In some embodiments, CHF authorizes quotas and requests MCF / AIoTF to request new quotas when the remaining quota drops below a threshold (the threshold is less than the quota).

[0506] In some embodiments, the quota can be:

[0507] - Billing data related to the number of devices (e.g., the number of devices in an MC device);

[0508] - Billing data related to tasks in the MC business (e.g., task session requests and responses for the business);

[0509] - Billing data related to data usage of MC services (e.g., data usage of services);

[0510] - Billing data related to the time usage of MC services (e.g., time usage of services);

[0511] - Billing data related to the number of events in the MC service (e.g., event usage of the service).

[0512] As shown in Figure 5B, the communication method includes the following steps:

[0513] Step 1: Based on the request from MCF, CHF authorizes an appropriate quota and requests the MCF function to request a new quota when the remaining quota drops below the threshold.

[0514] Step 2: The MCF sends a session modification request to the UPF, containing an updated URR information element. The URR information element includes usage thresholds and quotas, such as data volume thresholds and data volume quotas.

[0515] Step 3: UPF monitors usage and sends a report to CHF (directly or via MCF) when the threshold is reached.

[0516] Step 4: Upon reaching the usage threshold, the UPF sends a session reporting request along with a usage report to the MCF. The usage report includes a usage report trigger set to "Usage X" (e.g., quantity threshold or data volume threshold), and measured usage. The UPF continues forwarding business messages or data until the quota is reached.

[0517] Step 5: Based on the request from MCF, CHF authorizes a new quota and requests the MCF function to request a new limit.

[0518] Step 6: The UPF monitors usage and sends a report to the CHF (directly or via the MCF) when the threshold is reached; alternatively, it stops the transmission of service messages or data when the quota is reached. When the notified final quota is reached, both the UPF and MCF terminate the service.

[0519] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0520] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0521] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0522] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit, microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0523] In some embodiments, the communication device may be located at the first node 101. In some embodiments, the communication device may include at least one of a transceiver module and a processing module. The transceiver module may be configured to send first information to a second node, wherein the first information is used to instruct the second node to perform billing based on billing amount data for the first service. Optionally, the transceiver module may be used to perform at least one of the communication steps such as sending and / or receiving performed by the first node 101 in any of the above methods (e.g., steps S2101, S2104, S2106, S2109, S2111, S2112, S2204, S2208, S2211, S2215, S2216, S2303, S2305, S2308, but not limited thereto), which will not be elaborated here. Optionally, the processing module is used to execute at least one of the other steps executed by the first node 101 in any of the above methods (e.g., steps S2101, S2103, S2107, S2108, S2203, S2209, S2210, but not limited thereto), which will not be elaborated here.

[0524] In some embodiments, the communication device may be configured as a second node 102. In some embodiments, the communication device may include at least one of a transceiver module and a processing module. The transceiver module may be configured to receive first information. The processing module may be configured to perform billing based on billing quantity data for a first service according to the first information. Optionally, the transceiver module may be used to perform at least one of the communication steps (e.g., steps S2104, S2106, S2109, S2111, S2205, S2207, S2212, S2214, S2301, S2302, S2306, S2307, but not limited thereto) performed by the second node 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module may be used to perform at least one of the other steps (e.g., steps S2104, S2110, S2206, S2213, but not limited thereto) performed by the second node 102 in any of the above methods, which will not be elaborated here.

[0525] In some embodiments, the communication device may be located at the third node 103. In some embodiments, the communication device may include at least one of a transceiver module and a processing module. The transceiver module may be configured to: receive first information sent by the first node; send the first information to the second node; wherein the first information is used to instruct the second node to perform billing based on billing amount data for the first service. Optionally, the transceiver module may be used to perform at least one of the communication steps such as sending and / or receiving performed by the third node 103 in any of the above methods (e.g., steps S2102, S2112, S2201, S2202, S2204, S2205, S2207, S2208, S2211, S2212, S2214, S2215, S2216, S2301, S2302, S2303, S2305, S2306, S2307, S2308, but not limited thereto), which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps (e.g., step S2216, but not limited thereto) executed by the third node 103 in any of the above methods, which will not be elaborated here.

[0526] In some embodiments, the communication device can be implemented as a communication equipment.

[0527] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0528] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0529] Figure 6A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 6100 can be an MC device, a terminal (e.g., a user equipment), a network device (e.g., a core network device, an access network device), a chip, chip system, or processor that supports the MC device in implementing any of the above methods, a chip, chip system, or processor that supports the terminal in implementing any of the above methods, or a chip, chip system, or processor that supports the network device in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0530] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0531] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2104, S2106, S2109, S2111, S2201, S2202, S2204, S2205, S2207, S2208, S2211, S2212, S2214, S2215, S2301, S2...). At least one of S2302, S2303, S2305, S2306, S2307, S2308 (but not limited thereto) is performed by the processor 6101, and at least one of other steps (e.g., steps S2103, S2105, S2107, S2108, S2110, S2112, S2203, S2206, S2209, S2210, S2213, S2216, S2304, S2309, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0532] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.

[0533] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0534] Figure 6B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of the chip 6200 shown in Figure 6B, but it is not limited thereto.

[0535] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0536] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of the memories 6203 may be located outside chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0537] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2102, S2104, S2106, S2109, S2111, S2201, S2202, S2204, S2205, S2207, S2208, S2211, S2212, S2214, S2215, S2301, S2302, S2303, S2305, S2306, S2307, S2308, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2103, S2105, S2107, S2108, S2110, S2112, S2203, S2206, S2209, S2210, S2213, S2216, S2304, S2309, but not limited thereto).

[0538] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0539] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 6100, cause the communication device 6100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0540] This disclosure also provides a program product that, when executed by a communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0541] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

[0542] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only.

[0543] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A communication method, executed by a first node, wherein, The method includes: Send a first message to the second node, wherein the first message is used to instruct the second node to perform billing based on billing quantity data for the first service.

2. The method according to claim 1, wherein, The first information includes at least one of the following: Billing instruction information is used to trigger the second node to perform billing operations; Event indication information, used to indicate the first event; The billing data.

3. The method according to claim 1 or 2, wherein, The billing data includes at least one of the following: Billing data related to the number of equipment; Billing data related to the tasks of the first service; Billing data related to the data usage of the first service; Billing data related to the time usage of the first service; Billing data related to the number of events for the first service.

4. The method according to any one of claims 1 to 3, wherein, The billing volume data is obtained based on billing information; The billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

5. The method according to claim 4, wherein, The billing information is related to at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor.

6. The method according to any one of claims 1 to 5, wherein, The transmission of the first information is triggered by a first event, which includes at least one of the following: The first session begins; The first session has ended; The first service begins; The first service has ended; The billing data for the first service has reached the first threshold.

7. The method according to any one of claims 1 to 6, wherein, The method further includes: Receive second information sent by a third node, wherein the second information includes at least one of the following: The first quota is the maximum amount of billing data allocated to the first node for the first service. The first threshold is used to trigger the first node to report the billing amount data.

8. The method according to claim 7, wherein, The second information includes a first rule, which is used by the first node to monitor and / or report billing data. The first rule includes the first quota and / or the first threshold.

9. The method according to any one of claims 1 to 8, wherein, Sending the first information to the second node includes one of the following: Based on the address information of the second node, send the first information to the second node; The first information is sent to the third node, so that the third node sends the first information to the second node according to the address information of the second node.

10. A communication method, executed by a second node, wherein, The method includes: Receive the first message; Billing based on billing volume data is performed for the first service according to the first information.

11. The method according to claim 10, wherein, The first information includes at least one of the following: Billing instruction information is used to trigger the second node to perform billing operations; Event indication information, used to indicate the first event; The billing data.

12. The method according to claim 10 or 11, wherein, The billing data includes at least one of the following: Billing data related to the number of equipment; Billing data related to the tasks of the first service; Billing data related to the data usage of the first service; Billing data related to the time usage of the first service; Billing data related to the number of events for the first service.

13. The method according to any one of claims 10 to 12, wherein, The billing volume data is obtained based on billing information; The billing information includes at least one of the following: reader type, reader identifier, topology type, service area, time usage, data usage, event, service group, and task.

14. The method according to claim 13, wherein, The billing information is related to at least one of the following: device owner, application function, device type, network, service type, rate group, billing keyword, and sponsor.

15. The method according to any one of claims 10 to 14, wherein, The transmission of the first information is triggered by a first event, which includes at least one of the following: The first session begins; The first session has ended; The first service begins; The first service has ended; The billing data for the first service has reached the first threshold.

16. The method according to any one of claims 10 to 15, wherein, The method further includes: Receive third information sent by a third node, wherein the third information is used to request the amount of billing data for the first service; Send a fourth message to the third node, wherein the fourth message includes at least one of the following: The first quota is the maximum amount of billing data allocated to the first node for the first service. The second quota is the maximum amount of billing data allocated for the first service; The first threshold is used to trigger the first node to report the billing amount data.

17. The method according to any one of claims 10 to 16, wherein, The receipt of the first information includes one of the following: Receive the first information sent by the first node; The first information sent by the first node is received via the third node.

18. A communication method, executed by a third node, wherein, The method includes: Receive the first message sent by the first node; Send the first information to the second node; The first information is used to instruct the second node to perform billing based on the billing amount data for the first service.

19. The method according to claim 18, wherein, The first information includes at least one of the following: Billing instruction information is used to trigger the second node to perform billing operations; Event indication information, used to indicate the first event; The billing data.

20. The method according to claim 18 or 19, wherein, The method further includes: Send a third message to the second node, wherein the third message is used to request the amount of billing data for the first service; Receive fourth information sent by the second node, wherein the fourth information includes at least one of a first quota, a second quota, and a first threshold; Send the second information to the first node, wherein the second information includes at least one of the first quota and the first threshold; Wherein, the first quota is the maximum amount of billing data allocated to the first node for the first service; the second quota is the maximum amount of billing data allocated to the first service; and the first threshold is used to trigger the first node to report billing data.

21. The method according to claim 20, wherein, The second information sent by the third node to the first node includes a first rule, which is used by the first node to monitor and / or report billing data. The first rule includes the first quota and / or the first threshold.

22. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1-9, 10-17, and 18-21.

23. A communication system comprising a first node, a second node, and a third node, wherein, The first node is configured to implement the communication method as described in any one of claims 1 to 9, the second node is configured to implement the communication method as described in any one of claims 10 to 17, and the third node is configured to implement the communication method as described in any one of claims 18 to 21.

24. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-9, 10-17, and 18-21.

25. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method as described in any one of claims 1-9, 10-17, and 18-21.

Images