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

Abstract

The present disclosure relates to communication methods, a communication device, a communication device, a storage medium, and a program product. A method is executed by a first node, and comprises: sending first information to a second node, wherein the first information is used for instructing the second node to charge for a first service or a first event of the first service, the first service supports asynchronous type communication, and the first node supports collection of charging information. By means of the solution of the present disclosure, charging for services supporting asynchronous type communication 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] Communication systems are offering increasingly diverse services. Some services may have low latency requirements or do not require immediate processing. Communication systems need to be able to support the implementation of such services. Summary of the Invention

[0003] How communication networks bill services that support asynchronous type communication (ATC) is a technical problem that needs to be solved.

[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 instructs the second node to perform billing for a first service or a first event of the first service, the first service supporting asynchronous communication, and the first node supporting the collection of billing information.

[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 sent by a first node; and performing billing for a first service or an event related to the first service based on the first information; wherein the first service supports asynchronous communication, and the first node supports the collection of billing information.

[0006] According to a third aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication method as described in either the first or second aspect.

[0007] According to a fourth aspect of the present disclosure, a communication system is provided. The communication system includes a first node and a second 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.

[0008] According to a fifth 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 or second aspects.

[0009] According to a sixth 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 and second aspects.

[0010] According to a seventh aspect of the present disclosure, a computer program is provided. When the 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 second aspects.

[0011] According to an eighth 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 second aspects.

[0012] According to embodiments of this disclosure, billing for services that support asynchronous communication can be implemented.

[0013] 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

[0014] 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.

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

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

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

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

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

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

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

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

[0023] 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 instructs the second node to perform billing for a first service or a first event of the first service, the first service supporting asynchronous communication, and the first node supporting the collection of billing information.

[0024] In the above embodiments, the first node can send first information to the second node, enabling the second node to perform billing for the first service or a first event of the first service. This allows for billing of services that support asynchronous communication.

[0025] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: billing indication information for triggering the second node to perform a billing operation; event indication information for indicating a first event; and billing information.

[0026] In the above embodiments, the first node can send at least one of billing indication information, event indication information, and billing information 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 information can be billing data obtained by the first node through statistics. Based on the billing information, the second node can obtain the bill related to the first service to realize the billing of the first service. Thus, based on one or more of the billing indication information, event indication information, and billing quantity data, the second node can accurately realize the billing for the first service.

[0027] In conjunction with some embodiments of the first aspect, in some embodiments, the billing information includes at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to sponsors; billing events related to sponsors; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0028] In the above embodiments, billing information can be related to storage time usage, storage data usage, storage event usage, data groups, sponsors, service areas, etc. This significantly enhances the flexibility and applicability of billing.

[0029] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is triggered by a first event, the first event including at least one of the following: a time window for storing information; a load level for storing information; the number of terminals associated with the transmission of stored data; the number of sessions associated with the transmission of stored data; the amount of stored data transmitted associated with a terminal; the amount of stored data transmitted associated with a session; an expiration notification; the number of terminals whose stored data has expired; the number of sessions whose stored data has expired; and an alarm notification.

[0030] In conjunction with some embodiments of the first aspect, in some embodiments, the billing information is related to at least one of the following: storage time usage of the first service; storage data usage of the first service; storage event usage of the first service; the number of service signaling messages of the stored first service; the number of service signaling messages transmitted from the storage function node of the first service; the first service; the rate group associated with the first service; the billing keyword associated with the first service; the sponsor of the first service; and the service area of ​​the first service.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the transmission of the first information is triggered by a first condition, the first condition being related to the function of the first service, and the first condition being used to indicate the state of the function.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the first condition is included in the billing configuration information of the first node, the billing configuration information being configured according to one of the following: event; service; node requesting the first service; node requesting the first event; sponsor.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the first condition includes at least one of the following: the first service begins; the first service ends; the first event begins; the first event ends; the function of the first service changes.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, sending first information to a second node includes: sending first information to a second node based on the address information of the second node; wherein the address information of the second node is determined based on at least one of the following: the address of the second node used to transmit the context of the first service; the address of the second node as part of access and mobility policy control information; the address of the second node as a charging feature; the address of the second node provided during node discovery; or the address of the second node associated with the charging features of the first node, the charging features being provided by the local configuration of the first node.

[0035] 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 sent by a first node; and, based on the first information, performing billing for a first service or an event related to the first service; wherein the first service supports asynchronous communication, and the first node supports the collection of billing information.

[0036] In the above embodiments, the first node can send first information to the second node, enabling the second node to perform billing for the first service or a first event of the first service. This allows for billing of services that support asynchronous communication.

[0037] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following: billing indication information, used to trigger the second node to perform billing operations; event indication information, used to indicate a first event; and billing information.

[0038] In conjunction with some embodiments of the second aspect, in some embodiments, the billing information includes at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to sponsors; billing events related to sponsors; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0039] In conjunction with some embodiments of the second aspect, in some embodiments, the billing information includes at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to sponsors; billing events related to sponsors; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0040] In the above embodiments, billing information can be related to storage time usage, storage data usage, storage event usage, data groups, sponsors, service areas, etc. This significantly enhances the flexibility and applicability of billing.

[0041] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is triggered by a first event, the first event including at least one of the following: a time window for storing information; a load level for storing information; the number of terminals associated with the transmission of stored data; the number of sessions associated with the transmission of stored data; the amount of stored data transmitted associated with a terminal; the amount of stored data transmitted associated with a session; an expiration notification; the number of terminals whose stored data has expired; the number of sessions whose stored data has expired; and an alarm notification.

[0042] In conjunction with some embodiments of the second aspect, in some embodiments, the billing information is related to at least one of the following: storage time usage of the first service; storage data usage of the first service; storage event usage of the first service; the number of service signaling messages stored for the first service; the number of service signaling messages transmitted from the storage function node of the first service; the first service; the rate group associated with the first service; the billing keyword associated with the first service; the sponsor of the first service; and the service area of ​​the first service.

[0043] In conjunction with some embodiments of the second aspect, in some embodiments, the transmission of the first information is triggered by a first condition, the first condition being related to the function of the first service, and the first condition being used to indicate the state of the function.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the first condition is included in the billing configuration information of the first node, and the billing configuration information is configured according to one of the following: event; service; node requesting the first service; node requesting the first event; sponsor.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the first condition includes at least one of the following: the first service begins; the first service ends; the first event begins; the first event ends; the function of the first service changes.

[0046] In conjunction with some embodiments of the second aspect, in some embodiments, sending first information to a second node includes: sending first information to a second node based on the address information of the second node; wherein the address information of the second node is determined based on at least one of the following: the address of the second node used to transmit the context of the first service; the address of the second node as part of access and mobility policy control information; the address of the second node as a charging feature; the address of the second node provided during node discovery; or the address of the second node associated with the charging features of the first node, the charging features being provided by the local configuration of the first node.

[0047] In a third aspect, embodiments of this disclosure provide a communication device, such as a first node. The communication device includes a transceiver module configured to send first information to a second node, wherein the first information is used to instruct the second node to perform billing for a first service or a first event of the first service, the first service supporting asynchronous communication, and the first node supporting the collection of billing information.

[0048] In conjunction with some embodiments of the third aspect, in some embodiments, the first information includes 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 information.

[0049] In conjunction with some embodiments of the third aspect, in some embodiments, the billing information includes at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to sponsors; billing events related to sponsors; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0050] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is triggered by a first event, the first event including at least one of the following: a time window for storing information; a load level for storing information; the number of terminals associated with the transmission of stored data; the number of sessions associated with the transmission of stored data; the amount of stored data transmitted associated with a terminal; the amount of stored data transmitted associated with a session; an expiration notification; the number of terminals whose stored data has expired; the number of sessions whose stored data has expired; and an alarm notification.

[0051] In conjunction with some embodiments of the third aspect, in some embodiments, the billing information is related to at least one of the following: storage time usage of the first service; storage data usage of the first service; storage event usage of the first service; the number of service signaling messages stored for the first service; the number of service signaling messages transmitted from the storage function node of the first service; the first service; the rate group associated with the first service; the billing keyword associated with the first service; the sponsor of the first service; and the service area of ​​the first service.

[0052] In conjunction with some embodiments of the third aspect, in some embodiments, the transmission of the first information is triggered by a first condition, the first condition being related to the function of the first service, and the first condition being used to indicate the state of the function.

[0053] In conjunction with some embodiments of the third aspect, in some embodiments, the first condition is included in the billing configuration information of the first node, which is configured according to one of the following: event; service; node requesting the first service; node requesting the first event; sponsor.

[0054] In conjunction with some embodiments of the third aspect, in some embodiments, the first condition includes at least one of the following: the first service begins; the first service ends; the first event begins; the first event ends; the function of the first service changes.

[0055] In conjunction with some embodiments of the third aspect, in some embodiments, sending first information to a second node includes: sending first information to a second node based on the address information of the second node; wherein the address information of the second node is determined based on at least one of the following: the address of the second node used to transmit the context of the first service; the address of the second node as part of access and mobility policy control information; the address of the second node as a charging feature; the address of the second node provided during node discovery; or the address of the second node associated with the charging features of the first node, the charging features being provided by the local configuration of the first node.

[0056] In a fourth aspect, embodiments of this disclosure provide a communication device, such as a second node. The communication device includes: a transceiver module configured to receive first information sent by a first node; and to perform billing for a first service or an event related to the first service based on the first information; wherein the first service supports asynchronous communication, and the first node supports the collection of billing information.

[0057] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information includes at least one of the following: billing indication information for triggering the second node to perform a billing operation; event indication information for indicating a first event; and billing information.

[0058] In conjunction with some embodiments of the fourth aspect, in some embodiments, the billing information includes at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to the sponsor; billing events related to the sponsor; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0059] In conjunction with some embodiments of the fourth aspect, in some embodiments, the billing information includes at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to the sponsor; billing events related to the sponsor; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0060] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information is triggered by a first event, the first event including at least one of the following: a time window for storing information; a load level for storing information; the number of terminals associated with the transmission of stored data; the number of sessions associated with the transmission of stored data; the amount of stored data transmitted associated with a terminal; the amount of stored data transmitted associated with a session; an expiration notification; the number of terminals whose stored data has expired; the number of sessions whose stored data has expired; and an alarm notification.

[0061] In conjunction with some embodiments of the fourth aspect, in some embodiments, the billing information is associated with at least one of the following: storage time usage of the first service; storage data usage of the first service; storage event usage of the first service; the number of service signaling messages stored for the first service; the number of service signaling messages transmitted from the storage function node of the first service; the first service; the rate group associated with the first service; the billing keyword associated with the first service; the sponsor of the first service; and the service area of ​​the first service.

[0062] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transmission of the first information is triggered by a first condition, the first condition being related to the function of the first service, and the first condition being used to indicate the state of the function.

[0063] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first condition is included in the billing configuration information of the first node, the billing configuration information being configured according to one of the following: event; service; node requesting the first service; node requesting the first event; sponsor.

[0064] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first condition includes at least one of the following: the first service begins; the first service ends; the first event begins; the first event ends; the function of the first service changes.

[0065] In conjunction with some embodiments of the fourth aspect, in some embodiments, sending first information to a second node includes: sending first information to a second node based on the address information of the second node; wherein the address information of the second node is determined based on at least one of the following: the address of the second node used to transmit the context of the first service; the address of the second node as part of access and mobility policy control information; the address of the second node as a charging feature; the address of the second node provided during node discovery; or the address of the second node associated with the charging features of the first node, the charging features being provided by the local configuration of the first node.

[0066] In a fifth 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, and possible embodiments thereof.

[0067] In a sixth aspect, embodiments of this disclosure provide a communication system. The communication system includes a first node and a second 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.

[0068] In a seventh aspect, embodiments of this disclosure provide a storage medium storing 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, and possible embodiments thereof.

[0069] In an eighth 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, and possible embodiments thereof.

[0070] In a ninth 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, and possible implementations thereof.

[0071] In a tenth 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, and possible embodiments thereof.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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.

[0076] 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.

[0077] 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.

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

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

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

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

[0085] 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.

[0086] 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.

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

[0088] 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.

[0089] 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.

[0090] In some embodiments, access network devices, core network devices, or network devices can be replaced with 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 with 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, uplink link, downlink link, etc., can be replaced with sidelink link.

[0091] 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.

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

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

[0094] 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.

[0095] 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 and a second node 102.

[0096] In some embodiments, the first node 101 may be used for storing and / or transmitting service data for a first service that supports asynchronous type communication, and / or storing and / or transmitting service signaling for the first service.

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

[0098] In some embodiments, the first node 101 may be, for example, an asynchronous type communication data repository (ATCDR).

[0099] In some embodiments, the first node 101 may be, for example, an asynchronous type communication repository function (ATCRF).

[0100] In some embodiments, the first node 101 may be, for example, an asynchronous type communication buffering function (ATCBF).

[0101] In some embodiments, the first node 101 may be, for example, an access and mobility management function (AMF).

[0102] In some embodiments, the first node 101 may be, for example, a session management function (SMF).

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] 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).

[0111] Here, we will explain the important concepts involved in the disclosed embodiments.

[0112] 1. 6G Use Cases

[0113] Communication technology is evolving from 5G to 6G. In addition to enhancements in system architecture and functionality, 6G communication systems also require support for a wider range of usage scenarios.

[0114] In some embodiments, the proposed use cases for 6G communication technology include: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing.

[0115] In some embodiments, immersive communication is an extension of enhanced mobile broadband (eMBB) in 5G. Immersive communication covers use cases that provide users with rich, interactive video (immersive) experiences, including interactions with machine interfaces.

[0116] In some embodiments, immersive communication is used in a range of environments, including hotspots, towns, and rural areas, creating additional and new demands compared to eMBB in 5G.

[0117] In some embodiments, typical use cases for immersive communication include immersive extended reality (XR), remote multi-sensory presentation, and holographic communication. Supporting mixed data streams of video, audio, and other environmental data in a time-synchronized manner is an integral part of immersive communication, and also includes independent support for sound.

[0118] In some embodiments, across various environments, the ability to achieve enhanced spectral efficiency and a consistent service experience is critical, along with the need to balance higher data rates and greater mobility. Specific immersive communication use cases requiring responsive and precise interaction with real and virtual objects also need to support high reliability and low latency, as well as large system capacity for simultaneous connections of a large number of devices.

[0119] In some embodiments, the use cases for Hyper-Reliable and Low-Latency Communication (URLLC) extend the use cases of Ultra-Reliable and Low-Latency Communication (URLLC) in 5G. The use cases covered by URLLC are expected to have more stringent requirements in terms of reliability and latency. This is typically used for time synchronization operations, where failure to meet these requirements can lead to serious consequences for the application.

[0120] In some embodiments, typical use cases for ultra-reliable low-latency communication include communications for full automation, control, and operation in industrial environments. These communication types facilitate a variety of applications, such as machine interaction, emergency services, telemedicine, and monitoring of power transmission and distribution.

[0121] In some embodiments, use cases for ultra-reliable low-latency communication may require support for enhanced reliability and low latency, and depending on the use case, may also require precise location and connection density.

[0122] In some embodiments, massive communication is used in 5G for massive machine-type communication (mMTC). Massive communication involves connecting large-scale devices or sensors for a wide range of use cases and applications.

[0123] In some embodiments, typical use cases for large-scale communications include expansion and new applications in smart cities, transportation, logistics, health, energy, environmental monitoring, agriculture, and other areas where various IoT devices, either without batteries or with long-life batteries, are required.

[0124] In some embodiments, large-scale communication use cases may require support for high connection density, and depending on the use case, may also require different data rates, low power consumption, mobility, extended coverage, and high security and reliability.

[0125] In some embodiments, ubiquitous connectivity is used to improve connectivity and, more importantly, to bridge the digital divide. Connectivity can be improved, particularly through interoperability with other systems. A key focus of ubiquitous connectivity use cases is addressing currently uncovered or difficult-to-reach areas, especially rural, remote, and sparsely populated regions.

[0126] In some embodiments, typical use cases for ubiquitous connectivity include, but are not limited to, IoT and mobile broadband communications.

[0127] In some embodiments, the use cases of integrated artificial intelligence and communication can support distributed computing and artificial intelligence (AI) applications. Typical use cases for integrated artificial intelligence and communication include autonomous driving, automated collaboration between devices for assistive medical applications, the transfer of heavy computational operations across devices and networks, and the creation and prediction of digital twins.

[0128] In some embodiments, the use cases of integrated communications intelligence may require support for high regional traffic capacity and high data rates for user experience, as well as low latency and high reliability, depending on the specific use case. Beyond communications, the use cases of integrated communications intelligence are expected to include a range of new capabilities related to the integration of AI and computing functions, including the acquisition, preparation, and processing of data from different sources; distributed AI model training, model sharing, and distributed inference across international mobile telecommunications (IMT) systems; and the orchestration and linking of computing resources.

[0129] In some embodiments, integrated sensing and communication use cases facilitate new applications and services that require sensing capabilities. This helps provide wide-area, multi-dimensional sensing, providing spatial information about unconnected objects and connected devices, as well as their movement and surrounding environment.

[0130] In some embodiments, use cases for integrated communication and sensing include navigation, activity detection and motion tracking (e.g., gesture recognition, fall detection, vehicle / pedestrian detection), environmental monitoring (e.g., rain / pollutant detection), and providing sensing data / information related to the surrounding environment for use in AI, XR, and digital twin applications.

[0131] In some embodiments, along with the provided communication capabilities, the use cases of integrated communication and sensing need to support high-precision positioning and sensing-related capabilities, including range / rate / angle estimation, object and presence detection, positioning, imaging, and mapping.

[0132] It should be noted that each of the 6G use cases described above can also be considered a corresponding type of service. For example, the service in the immersive communication use case can be an immersive communication service. For example, the service in the ultra-reliable low-latency communication use case can be an ultra-reliable low-latency communication service. For example, the service in the massive MIMO use case can be a massive MIMO service. For example, the service in the ubiquitous connectivity use case can be a ubiquitous connectivity service. For example, the service in the integrated intelligent communication use case can be an integrated intelligent communication service. For example, the service in the integrated communication sensing use case can be an integrated communication sensing service.

[0133] 2. Asynchronous communication

[0134] Some communication information transmitted in a communication system may not have strict latency requirements or real-time processing requirements. In order to implement the transmission of this type of communication information in a targeted manner, the concept of asynchronous communication was proposed.

[0135] Asynchronous communication is designed to meet the service and communication requirements of communication systems. Asynchronous communication can be understood as a mechanism, feature, or function. It involves delaying the transmission of communication information. In some embodiments, when using asynchronous communication, the communication system, particularly the core network, can delay the transmission of communication information.

[0136] In some embodiments, when asynchronous communication is employed, the core network can store or buffer the communication information after acquiring it, and then transfer or synchronize the stored or buffered information at an appropriate time. For example, communication information from a specific network function to a terminal can use an asynchronous communication mechanism. The communication information from the network function can be stored in the core network after arriving at the core network, and the core network will then transmit the communication information to the terminal at an appropriate time. Similarly, communication information from one network function to another can use an asynchronous communication mechanism. The communication information from the former can be stored in the core network after arriving at the core network, and the core network will then transmit the communication information to the latter at an appropriate time. Thus, the asynchronous communication mechanism enables delayed transmission of communication information.

[0137] In some embodiments, asynchronous communication may target communication information that includes service signaling and / or service data. In one example, asynchronous communication may be applied to the transmission of service signaling. In another example, asynchronous communication may be applied to the transmission of service data.

[0138] Based on the above, how communication networks should bill services that support asynchronous communication is a problem that needs to be solved.

[0139] In some embodiments, the terms “services supporting asynchronous communication (services supporting ATC)”, “asynchronous communication services (ATC services)”, “asynchronous communication services (ATC services)”, etc., can be used interchangeably.

[0140] Figure 2 is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 2, the communication method of this embodiment includes steps S201 to S212.

[0141] In some embodiments, the communication system 100 includes a first node 101, a second node 102, and a terminal 201.

[0142] In step S201, the first node 101 determines the second node 102.

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

[0144] In some embodiments, the first service may support asynchronous communication. In some embodiments, the first service may be a service that employs an asynchronous communication mechanism or function. In some embodiments, the first service that supports asynchronous communication may be referred to as an asynchronous communication service, i.e., an ATC service.

[0145] In some embodiments, the first service may include an application service provided by an application provider. This application service may be associated with one or more service consumers (e.g., terminal 210). For example, the application service may include uplink and / or downlink service data directed to terminal 210, and / or service signaling related to the application service.

[0146] In some embodiments, the first service may be a service related to terminal 210. For example, the first service may include signaling interactions related to terminal 210. In this process, the signaling related to terminal 210 may be referred to as service signaling.

[0147] In some embodiments, the first service may include services supported by a 6G communication system. In one example, the type of the first service may include at least one of the following: immersive communication, ultra-reliable low-latency communication, massive MIMO, ubiquitous connectivity, integrated intelligent communication, and integrated communication sensing. It is understood that the first service may also be other services, such as services supported by a 5G communication system, etc., and this disclosure does not specifically limit them.

[0148] In some embodiments, asynchronous communication functions include at least one of the following: storage of service signaling, transmission of service signaling, storage of service data, and transmission of service data. In some embodiments, when asynchronous communication is supported, the service signaling and / or service data of the first service can be stored and / or transmitted by the communication network. In some embodiments, service signaling can be transmitted on the control plane. In some embodiments, service data can be transmitted on at least one of the control plane, user plane, and data plane.

[0149] In some embodiments, the first node 101 may be a UPF. In this case, the first node 101 can support the storage and / or transmission of service data for the first service. In some embodiments, the first node 101 may be an ATCDR. In this case, the first node 101 can support the storage and / or transmission of service data for the first service, and / or support the storage and / or transmission of service signaling for the first service. In some embodiments, the first node 101 may be an AMF, SMF, or other control plane network element. In this case, the first node 101 can support the storage and / or transmission of service signaling for the first service.

[0150] In some embodiments, the second node 102 may be a CHF.

[0151] 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.

[0152] In some embodiments, step S201 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.

[0153] In some embodiments, step S201 may be performed after the first 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 may determine the second node 102.

[0154] In some embodiments, step S201 can be performed after the registration process of terminal 210 is completed. In some embodiments, after terminal 210 registers with the network, the first node 101 can determine the second node 102.

[0155] In some embodiments, through step S201, 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. For example, the first node 101 can obtain the fully qualified domain name (FQDN) of the second node 102. Based on the address information, the first node 101 can determine the corresponding second node 102.

[0156] In some embodiments, the address information of the second node 102 may be determined based on at least one of the following methods: address information provided by another first node (not shown), address information provided by PCF, address information provided by UDM, address information provided by NRF, address information provided by AMF or SMF, or local configuration.

[0157] In some embodiments, first node 101 may receive address information from another first node, which can be used to address second node 102. In some embodiments, a first service may be switched from another first node to first node 101, in which case the other first node may send the address information of second node 102 to first node 101. In some embodiments, this address information can be used for the service context of the first service. In some embodiments, first node 101 may be an AMF, SMF, or ATCDF as the destination, and the other first node may be an AMF, SMF, or ATCDF as the source, in which case the address information can be used for the service context of the first service transmitted from the other first node to first node 101.

[0158] In some embodiments, the first node 101 may receive address information from the PCF, which can be used to address the second node 102. In some embodiments, the PCF may provide access and mobility policy control information to the first node 101. The address information of the second node 102 may be included in the access and mobility policy control information.

[0159] In some embodiments, the first node 101 may receive address information from the UDM, which can be used to address the second node 102. In some embodiments, the UDM may provide billing features to the first node 101. The address information of the second node 102 may be included in the billing features.

[0160] In some embodiments, the first node 101 may receive address information from the NRF, which can be used to address the second node 102. In some embodiments, the address information of the second node 102 may be provided to the first node 101 by the NRF during the discovery process.

[0161] In some embodiments, the first node 101 may receive address information from an AMF or SMF, which can be used to address the second node 102. In some embodiments, the first node 101 may not be an AMF or SMF. For example, the first node 101 may be an ATCDR or UPF. Meanwhile, the first node 101 and the AMF and / or SMF may have the same or similar service areas. In this case, the first node 101 with the same or similar service areas, and the AMF and / or SMF, may be served by the same second node 102. Then, the AMF or SMF can provide the address information of the second node 102 to the first node 101. For example, the AMF or SMF can provide the address information of its associated second node 102 to the first node 101.

[0162] In some embodiments, the first node 101 may obtain the address information of the second node 102 based on its local configuration. In some embodiments, the local configuration of the first node 101 may include the billing characteristics of the first node 101. The billing characteristics may include the address information of the second node 102 associated with the billing of the first node 101.

[0163] In some embodiments, the first node 101 may determine the second node 102 by at least one of the above methods.

[0164] In some embodiments, if the first node 101 obtains the address information of the second node 102 through two or more of the above methods, the second node 102 can be further determined from the address information of the second node 102 obtained through these multiple methods.

[0165] In some embodiments, there may be a priority relationship among the various methods used to obtain the address information of the second node 102. In some embodiments, the first node 101 may tend to use the method with higher priority to obtain the address of the second node 102. In some embodiments, the priority relationship between different methods may be determined based on the first node 101's operator policy and / or OAM configuration and / or local configuration.

[0166] In some embodiments, the address information of the second node 102 determined in step S201 can be used to implement at least one of the following for a first service supporting asynchronous communication: collection of billing information and reporting of billing information. In some embodiments, billing information may include billing events and billing data. In one example, the address information of the second node 102 can be used to implement at least one of the following for a first service supporting asynchronous communication: collection of billing events, reporting of billing events, collection of billing data, and reporting of billing data.

[0167] In some embodiments, the collection and reporting of billing information for the first service of asynchronous type communication can be independent of the collection and reporting of other types of billing information.

[0168] In some embodiments, the first node 101 may be configured with a charging profile. The charging profile may also be referred to as a charging profile. The charging profile of the first node 101 can be used to determine the triggering conditions for asynchronous communication. In some embodiments, the charging profile can be used to determine the triggering conditions for charging asynchronous communication. In some embodiments, the charging profile may include the state of functionality related to asynchronous communication. For example, the charging profile may include a charging state and / or a charging scenario. In some embodiments, the charging state may be charging active or charging deactivated. The first node 101 in the charging active state can perform charging-related functions. The first node 101 in the charging deactivated state does not perform charging-related functions.

[0169] In some embodiments, the billing configuration information may be configured according to at least one of the following: event, service, node requesting the first service, node requesting the first event, and sponsor. The billing profile may be determined for each event, each service, each node requesting the first service, each node requesting the first event, each sponsor, etc. In one example, different billing profiles may be applied for different events. In one example, different billing profiles may be applied for different services. In one example, different billing profiles may be applied for different nodes requesting the first service. In one example, different billing profiles may be applied for different sponsors.

[0170] In step S202, the first node 101 receives the first request.

[0171] In some embodiments, the first node 101 may receive the first request.

[0172] In some embodiments, the first request may be a request related to asynchronous type communication.

[0173] In some embodiments, the first request may be a request for a first service. For example, the first request may be used to instruct operations such as storage and transmission of service signaling and / or service data for the first service. For example, the first request may be used to request the storage and transmission of service signaling and / or service data for the first service.

[0174] In some embodiments, the first request may be used to indicate the usage of a first service. In some embodiments, the usage associated with the first service may include at least one of the following: time usage, traffic usage, and event usage. In some embodiments, the usage associated with the first service may be for at least one of the following operations: storage and transmission.

[0175] In some embodiments, the first request may be a request for an event related to a first service. For example, the first request may be used to indicate an event related to the usage of the first service.

[0176] In step S203, the first node 101 obtains billing information.

[0177] In some embodiments, the first node 101 may support billing related to a first service and / or billing related to a first event of the first service. In some embodiments, the first node 101 may perform processing of service signaling and / or service data for the first service that supports asynchronous communication. In some embodiments, the first node 101 may collect and report billing information for the first service that supports asynchronous communication.

[0178] In some embodiments, the billing information may include at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to sponsors; billing events related to sponsors; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0179] In some embodiments, the billing data related to the storage time usage of the first service can be obtained based on the storage time statistics of the service signaling and / or service data of the first service. In some embodiments, the storage time usage can be related to the storage duration and / or storage period. In some embodiments, the storage time usage can include the storage duration of the service signaling and / or service data of the first service. The storage duration can refer to the duration between the start and end times of storing the service signaling and / or service data. For example, the storage duration can be 5 minutes, 10 minutes, 1 hour, 24 hours, etc. In some embodiments, the storage time usage can include the storage period of the service signaling and / or service data of the first service. In one example, a day can be divided into two periods, for example, a daytime period from 8:00 to 20:00, and a nighttime period from 20:00 to 8:00 the next day. The storage time usage can indicate whether the storage period is a daytime period or a nighttime period. In one example, a week can be divided into two periods, for example, a weekday period from Monday to Friday, and a weekend period on Saturday and Sunday. The storage time usage can indicate whether the storage period is a weekday period or a weekend period. It is understandable that storage time usage can span multiple time periods.

[0180] In some embodiments, the billing data related to the storage traffic usage of the first service can be obtained from the storage data statistics based on the service data of the first service. In some embodiments, the storage traffic usage can be related to the amount of stored data. In some embodiments, the storage traffic usage can include the amount of stored service data of the first service.

[0181] In some embodiments, the billing data related to the storage event usage of the first service can be obtained based on the statistics of storage events of the first service. In some embodiments, the storage event usage can be related to storage events. In some embodiments, the storage event usage can include the number of storage events of the first service. In one example, in the first service, each storage operation can be regarded as a storage event. For example, the first service can be a video file playback service, then storing a video file can be a storage event.

[0182] In some embodiments, billing data related to the first service may be obtained based on statistics of asynchronous communication operations performed for the first service. In some embodiments, asynchronous communication operations performed for the first service may include storage and transmission. In some embodiments, billing data related to the first service may be obtained by statistically analyzing storage operations and / or transmission operations related to the first service. In some embodiments, billing data related to the first service may include at least one of the following: the amount of stored service data, the number of stored service signaling messages, the amount of transmitted service data, and the number of transmitted service signaling messages. In some embodiments, statistics on the storage and / or transmission of service data and statistics on the storage and / or transmission of service signaling may be performed jointly or separately. Thus, common billing data or separate billing data may be obtained for service data and service signaling. In some embodiments, statistics on storage and statistics on transmission may be performed jointly or separately. Thus, common billing data or separate billing data may be obtained for storage and transmission.

[0183] In some embodiments, the billing event associated with the first event may be obtained based on operational statistics of asynchronous type communication performed for the first service. In some embodiments, the first event may be associated with storage and / or transmission in the first service.

[0184] In some embodiments, the service signaling and / or service data of the first service may reside in packets, and billing data may be associated with the data packets of the first service. In some embodiments, data packets may be determined according to storage and transmission. In this case, the storage of the service signaling and / or service data of the first service may correspond to one packet, and the transmission of the service signaling and / or service data of the first service may correspond to another packet. Then, the billing data may include the number of service signaling (e.g., storage signaling) and / or the amount of service data in the packet corresponding to storage; and / or, the billing data may include the number of service signaling (e.g., storage signaling) and / or the amount of service data in the packet corresponding to transmission. For example, service signaling may be divided into signaling for implementing storage and signaling for implementing transmission. For service signaling, the billing data associated with the packet corresponding to storage may include the number of storage signaling, and the billing data associated with the packet corresponding to transmission may include the number of transmission signaling.

[0185] In some embodiments, the billing events related to data packets of the first service may be derived based on the data packets. In some embodiments, the billing events may include billing events related to service signaling and / or service data in the corresponding storage packets; and / or, the billing data may include billing events related to service signaling and / or service data in the corresponding transmission packets.

[0186] In some embodiments, the billing data related to the sponsor may be statistically obtained for the sponsor of the first service. In some embodiments, the first node 101 may statistically analyze the billing data of the first service for the sponsor of the first service. In some embodiments, the sponsor-related billing data of the first service may be at least a portion of the billing data of the first service.

[0187] In some embodiments, the billing events related to the sponsor can be statistically obtained for the sponsor of the first service. In some embodiments, the first node 101 can statistically obtain the billing events of the first service for the sponsor of the first service. In some embodiments, the billing events related to the sponsor of the first service can be at least a portion of the billing events of the first service.

[0188] In some embodiments, the first service may be a service specific to a particular service area. For example, the first service may be a service provided to terminal 210 within the service area. In some embodiments, billing data related to the service area of ​​the first service may be statistically analyzed for the service area. In some embodiments, billing events related to the service area of ​​the first service may be statistically analyzed for the service area. In some embodiments, the number of service areas may be one or more.

[0189] In some embodiments, the first event may include at least one of the following: a time window for storing information; a load level for storing information; the number of terminals 210 associated with the transmission of stored data; the number of sessions associated with the transmission of stored data; the amount of stored data transmitted associated with terminal 210; the amount of stored data transmitted associated with a session; an expiration notification; the number of terminals 210 whose stored data has expired; the number of sessions whose stored data has expired; and an alarm notification.

[0190] It should be noted that the stored information here may include business signaling and / or business data.

[0191] In some embodiments, the first event may include a time window for storing information. In some embodiments, the first event may include events related to the time window for storing information. The time window may be used to store service signaling and / or service data for the first service. In some embodiments, events related to the time window may include at least one of the following: the time window is about to expire, the time window has expired, the time window has ended, or the time window is in progress.

[0192] In some embodiments, the first event may include the load level of the stored information. In some embodiments, the first event may include events related to the load level of the stored information. In some embodiments, storage capacity may be authorized on the first node 101 for a first service. At this time, the amount of service signaling and / or service data that the first node 101 can store for the first service does not exceed the authorized storage capacity. In one example, the load level of the stored information may be determined according to the proportion of the stored service signaling and / or service data of the first service occupied by the authorized storage capacity for the first service. In some embodiments, the storage capacity of the first node 101 for storing information for asynchronous communication may be preset. This storage capacity may be used for storing service data and / or service signaling of one or more asynchronous communication services. In one example, the load level of the stored information may be determined according to the proportion of the stored service signaling and / or service data of all asynchronous services occupied by the storage capacity in the first node 101. In both methods, the load level may be divided into low load, high load, and full load according to the different occupancy ratios. A low load occurs when the proportion of stored service signaling and / or service data occupied by the storage capacity does not exceed 50%. A high load is defined as the proportion of storage capacity occupied by stored business signaling and / or business data being between 50% and 90%. A high load is defined as the proportion of storage capacity occupied by stored business signaling and / or business data being more than 90%. In some embodiments, events related to the load level may include at least one of the following: the load level of the stored information is low, the load level of the stored information is high, or the load level of the stored information is full.

[0193] In some embodiments, the first event may include the number of terminals 210 associated with the transmission of stored data. In some embodiments, the first event may include events related to the number of terminals 210 associated with the transmission of stored data. In some embodiments, service data for the first service may be directed to one or more terminals 210. In this case, stored data related to the first service may be transmitted to one or more terminals 210. In some embodiments, events related to the number of terminals 210 associated with the transmission of stored data may include at least one of the following: a change in the number of terminals 210, or the number of terminals 210 reaching a specific range.

[0194] In some embodiments, the first event may include the number of sessions associated with the transmission of stored data. In some embodiments, the first event may include events related to the number of sessions associated with the transmission of stored data. In some embodiments, the service data of the first service may be for one or more sessions. In this case, the stored data associated with the first service may be transmitted in the first or more sessions. In some embodiments, events related to the number of sessions associated with the transmission of stored data may include at least one of the following: the number of sessions changes, or the number of sessions reaches a certain range.

[0195] In some embodiments, the first event may include the amount of stored data transmitted associated with terminal 210. In some embodiments, the first event may include events related to the amount of stored data transmitted associated with terminal 210. In some embodiments, events related to the amount of stored data transmitted associated with terminal 210 may include at least one of the following: the amount of stored data transmitted is not zero, the amount of stored data transmitted is greater than a preset threshold, or the amount of stored data transmitted reaches the amount of stored data.

[0196] In some embodiments, the first event may include the amount of session-associated stored data transferred. In some embodiments, the first event may include events related to the amount of session-associated stored data transferred. In some embodiments, events related to the amount of session-associated stored data transferred may include at least one of the following: the amount of stored data transferred is not zero, the amount of stored data transferred is greater than a preset threshold, or the amount of stored data transferred reaches the amount of stored data.

[0197] In some embodiments, the first event may include an expiration notification. In some embodiments, the storage time and / or data volume of business data and / or business signaling in the first node 101 may have an upper limit. In one example, the first event may include the storage time of business data and / or business signaling in the first node 101 reaching or exceeding the upper limit. In this case, the expiration notification may be a time expiration notification, indicating that the storage time has expired. In another example, the first event may include the data volume of business data and / or business signaling stored in the first node 101 reaching or exceeding the upper limit. In this case, the expiration notification may be a data volume expiration notification, indicating that the stored data volume exceeds the maximum storage capacity.

[0198] In some embodiments, the first event may include the number of terminals 210 whose stored data has expired. In some embodiments, the first event may include events related to the number of terminals 210 whose stored data has expired. In some embodiments, events related to the number of terminals 210 whose stored data has expired may include at least one of the following: the number of terminals 210 whose stored data has expired is reduced to 0, or the number of terminals 210 whose stored data has expired exceeds a preset threshold.

[0199] In some embodiments, the first event may include an alarm notification. In some embodiments, a threshold may be set for the storage time of the stored data. The first node 101 may issue an alarm notification when the storage time of the stored data reaches or exceeds the threshold. In some embodiments, the threshold set for the storage time may be less than the upper limit of the storage time. For example, if the storage time is in the form of duration, the threshold may be shorter than the upper limit. If the storage time is in the form of moments, the threshold may be earlier than the upper limit. In some embodiments, a threshold may be set for the amount of stored data. The first node 101 may issue an alarm notification when the amount of stored data reaches or exceeds the threshold.

[0200] In some embodiments, the billing information mentioned above may be related to at least one of the following: storage time usage of the first service; storage data usage of the first service; storage event usage of the first service; the number of service signaling messages of the first service stored; the number of service signaling messages transmitted, the service signaling messages originating from the storage function node of the first service; the first service; the rate group associated with the first service; the billing keyword associated with the first service; the sponsor of the first service; and the service area of ​​the first service.

[0201] In some embodiments, a rate group may be a group for uniform billing. In some embodiments, a rate group may include at least one of the following: one or more services, one or more tasks, one or more sessions, one or more terminals 210, 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 sessions may constitute a rate group. In one example, one or more locations may constitute a rate group. In one example, one or more terminals 210 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.

[0202] 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.

[0203] 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 at least one of the provider of the first service and the holder of terminal 210, and this disclosure does not specifically limit this.

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

[0205] In some embodiments, see Table 1 below for an explanation of the categories of the second event.

[0206] In Table 1, PEC stands for post event charging, and ECR stands for event charging with unit reservation.

[0207] Referring to Table 1, the second event can be categorized into multiple types. For example, these categories may include: ATC service, ATC service events, and ATC status reporting. Each category's second event may include one or more behaviors. For instance, events in the ATC service category may include the following two behaviors: ATC session start and ATC session end. Similarly, the second event in the ATC service event category may include the following two behaviors: ATC service event start and ATC service event completion. For example, second events related to ATC status reporting may include ATC status change.

[0208] In Table 1, the first column from the left lists the behaviors associated with the second event. Different behaviors and different 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.

[0209] In step S204, the first node 101 sends the first information to the second node 102.

[0210] 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.

[0211] 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.

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

[0213] In some embodiments, the transmission of the first information may be triggered by a first condition. In some embodiments, the first condition is related to the function of the first service. In some embodiments, the first condition is used to indicate the status of the function. In some embodiments, the first condition may be included in the billing configuration information of the first node.

[0214] In some embodiments, the first condition may include a second event. In some embodiments, the first information may be sent upon triggering the second event. In some embodiments, the first node 101 may determine that a second event related to the first service has been triggered and send the first information. In some embodiments, the second event may be used to trigger the sending of the first information.

[0215] In some embodiments, the second event may include at least one of the following: first service start, first service completion, first service event start, first service event completion, ATC state change.

[0216] In some embodiments, in step S204, the first node 101 may send the first information when the first service starts or when an event of the first service begins.

[0217] 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.

[0218] In some embodiments, the first information can be used to instruct the second node 102 to perform billing for the first service or the first event of the first service. In some embodiments, the first information instructing the second node 102 to perform billing for the first service or the first event of the first service can be understood as the first information being used by the second node 102 to perform billing based on the first information. In other words, after receiving the first information, the second node 102 can perform billing for the first service or the first event of the first service based on 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 for the first service or the first event of the first service. For example, the first information triggering the second node 102 to perform billing for the first service or the first event of the first service can be understood as the second node 102 determining to trigger billing based on the first information after receiving the first information, or the billing being triggered by the first information.

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

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

[0221] 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.

[0222] In some embodiments, event indication information may be used to indicate a second event. In some embodiments, event indication information may indicate a triggered second event related to the first service. In some embodiments, event indication information may indicate the start of the first service, the start of an event of the first service, a change in ATC status, etc.

[0223] 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.

[0224] In step S205, the second node 102 performs a billing operation.

[0225] 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 the first service based on the first information. In some embodiments, the second node 102 may perform billing operations related to asynchronous communication of the first service based on the first information.

[0226] 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 asynchronous communication.

[0227] 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.

[0228] 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.

[0229] In some embodiments, CDR can be for asynchronous type communication of the first service.

[0230] In step S206, the second node 102 sends the second information to the first node 101.

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

[0232] 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.

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

[0234] In some embodiments, the second information may indicate billing for accepting the first message request. In some embodiments, the second information may indicate that billing for the first message request has been triggered. In some embodiments, the second information may indicate billing for not accepting or rejecting the first message request.

[0235] In some embodiments, the message type of the second message can be the same as the message type 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.

[0236] In step S207, the first node 101 continues to execute the first service.

[0237] In some embodiments, the first node 101 may continue to execute the business process of the first service.

[0238] In some embodiments, the first node 101 may continue to execute the business process of the first event of the first business.

[0239] In step S208, the first node 101 completes the first service.

[0240] In some embodiments, the first node 101 can complete the first service.

[0241] In some embodiments, the first node 101 may complete the first event.

[0242] In step S209, the first node 101 sends the first information to the second node 102.

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

[0244] In step S210, the second node 102 performs a billing operation.

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

[0246] 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.

[0247] In step S211, the second node 102 sends the second information to the first node 101.

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

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

[0250] In some embodiments, upon receiving the second information, the first node 101 can determine that the first service or the first event of the first service has been completed. In some embodiments, the second information may be a confirmation message for the first message in the case of the completion of the first service or the first event. At this time, upon receiving the second information, the first node 101 can determine that the second node 102 has completed the billing operation and closed the CDR. Then, the first node 101 can determine that the first service or the first event has been completed.

[0251] The communication method of this embodiment can be implemented through steps S201 to S212.

[0252] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S212. For example, step S203 may be implemented as a standalone embodiment, step S204 may be implemented as a standalone embodiment, step S209 may be implemented as a standalone embodiment, and a combination of steps S203 and S204 may be implemented as a standalone embodiment, but is not limited thereto.

[0253] In some embodiments, steps S201, S202, S204, S205, S206, S207, S208, S209, S210, S211, and S212 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0254] 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.

[0255] 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.

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

[0257] 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.”

[0258] 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.

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

[0260] 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.

[0261] 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.

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

[0263] In some embodiments, the terms “billing information,” “billing data,” “usage data,” and “billing usage data” can be used interchangeably.

[0264] In some embodiments, the terms "buffering", "storing", and "saving" can be used interchangeably.

[0265] In some embodiments, the terms "transferring," "synchronizing," and "transmission" can be used interchangeably.

[0266] Figure 3 is another 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 step S301.

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

[0268] The optional implementations of step S301 can be found in the optional implementations of steps S204 and S209 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0269] In some embodiments, the first information includes at least one of the following: billing indication information for triggering the second node to perform a billing operation; event indication information for indicating a first event; and billing information.

[0270] In some embodiments, the billing information includes at least one of the following: billing data related to storage time usage of the first service; billing data related to storage data usage of the first service; billing data related to storage event usage of the first service; billing data related to the first service; billing events related to the first event; billing data related to data packets of the first service; billing events related to data packets of the first service; billing data related to sponsors; billing events related to sponsors; billing data related to the service area of ​​the first service; and billing events related to the service area of ​​the first service.

[0271] In some embodiments, the first information is triggered by a first event, which includes at least one of the following: a time window for storing information; a load level for storing information; the number of terminals associated with the transmission of stored data; the number of sessions associated with the transmission of stored data; the amount of stored data transmitted associated with a terminal; the amount of stored data transmitted associated with a session; an expiration notification; the number of terminals whose stored data has expired; the number of sessions whose stored data has expired; and an alarm notification.

[0272] In some embodiments, the billing information is associated with at least one of the following: storage time usage of the first service; storage data usage of the first service; storage event usage of the first service; the number of service signaling messages of the first service stored; the number of service signaling messages transmitted from the storage function node of the first service; the first service; the rate group associated with the first service; the billing keyword associated with the first service; the sponsor of the first service; and the service area of ​​the first service.

[0273] In some embodiments, the transmission of the first information is triggered by a first condition, which is related to the function of the first service and is used to indicate the state of the function.

[0274] In some embodiments, the first condition is included in the billing configuration information of the first node, which is configured according to one of the following: event; service; node requesting the first service; node requesting the first event; sponsor.

[0275] In some embodiments, the first condition includes at least one of the following: the first service begins; the first service ends; the first event begins; the first event ends; the function of the first service changes.

[0276] In some embodiments, sending first information to a second node includes: sending first information to a second node based on the address information of the second node; wherein the address information of the second node is determined based on at least one of the following: the address of the second node used to transmit the context of the first service; the address of the second node as part of access and mobility policy control information; the address of the second node as a charging feature; the address of the second node provided during node discovery; or the address of the second node associated with the charging features of the first node, the charging features being provided by the local configuration of the first node.

[0277] 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.

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

[0279] This disclosure provides embodiments supporting the collection of billing information via AMF / SMF / ATCDR. The statistics and measurement of billing information can take into account the following factors:

[0280] ATC's cache time usage (which can be represented by storage time);

[0281] ATC's cached traffic usage (which can be represented by the amount of stored data);

[0282] ATC's cached event usage (which can be represented by stored events, for example, each video or AI model is counted as one event);

[0283] The number of buffered signaling (which can be represented by signaling statistics, for a single UE or a group of UEs);

[0284] The number of NF synchronization signals from the ATC cache (which can be represented by signaling statistics for a single UE or a group of UEs);

[0285] Business identifier (can be represented by a business identifier);

[0286] Rate group / billing keyword (use separate billing keywords for ATC services);

[0287] Sponsors (can be represented by Sponsor and ASPID, for example, the operator or AF can be a sponsor for ATC features);

[0288] Service areas (e.g., different service areas for ATC services can be selected).

[0289] In some embodiments, the AMF / SMF / ATCDR selects the CHF address for billing reporting. The following options may be considered for performing CHF address selection:

[0290] CHF address, used for ATC service context transmitted by the source AMF / SMF / ATCDR;

[0291] CHF address, provided by PCR as part of access and mobility policy control information;

[0292] CHF address, provided by UDM as a billing feature;

[0293] CHF address, provided by NRF during the discovery process;

[0294] CHF address, provided by AMF / SMF. For example, if ATCDR / UPF performs billing statistics CTF, AMF has the same or similar service area as ATCDR.

[0295] AMF / SMF / ATCDR provides local billing features.

[0296] In some embodiments, the priority order of these options depends on the operator's policy or configuration.

[0297] In some embodiments, the selected CHF address is used for the collection and reporting of billing events / data for ATC services.

[0298] In some embodiments, the collection and reporting of ATC billing events / data can be independent of existing billing. For example, ATC events or traffic can be billed when data or time is already being billed as usual.

[0299] In some embodiments, the AMF / SMF / ATCDR / UPF interacts with the CHF to perform ATC service billing. In some embodiments, billing data / events include:

[0300] Billing data related to ATC buffer time usage;

[0301] Billing data related to ATC buffer traffic usage;

[0302] Billing data related to ATC buffer event usage;

[0303] Billing data / events related to ATC services (e.g., buffering, synchronization);

[0304] Billing data / events related to packet ATC data (e.g., the amount of buffer / synchronization signaling);

[0305] Billing data / events related to the sponsor (e.g., ATC usage statistics for the sponsor);

[0306] Billing data / events related to the service area (e.g., ATC usage statistics for the service area).

[0307] In some embodiments, the ATCDR billing profile is used by ATCDR to determine the applicable triggering conditions for each function and includes the state of the function (e.g., billing activation or deactivation, billing scenario).

[0308] In some embodiments, ATCDR billing configuration information is provided for each event, each service, each AF, and each sponsor.

[0309] In some embodiments, ATCDR / AMF / SMF / UPF can support triggering conditions and categories (billingable events).

[0310] In some embodiments, a billing data request is sent to CHF when a specific condition (billingable event) is met.

[0311] In some embodiments, when a billing event is sent to the CHF, the billing event includes an identifier, such as an event identifier, a service identifier, an AF identifier, or a sponsor identifier.

[0312] In some embodiments, billing trigger conditions (billingable events) have associated behaviors when they are met. The trigger conditions and categories supported by ATCDR / AMF / SMF / ATCDR / UPF can be found in Table 1.

[0313] Figure 4 is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of the present disclosure. This communication method relates to event charging with unit reservation (ECUR) for ATC services or events of ATC services. Here, the charging message for ATC services or events of ATC services in the ECR is described. As shown in Figure 4, the communication method includes the following steps:

[0314] Step 0: UE registration is complete. The CHF is selected by AMF / SMF / ATCDR.

[0315] Step 1: The ATCDR receives a request for ATC services or ATC service events, such as buffering or synchronization of ATC services, or time usage, traffic usage, or event usage of ATC services for buffering or synchronization.

[0316] Step 2: For ATC services or ATC service events, ATCDR sends a billing data request to CHF (initial).

[0317] Step 3: CHF performs account and rating control for ATC services or events related to ATC services and opens CDR.

[0318] Step 4: CHF confirms by sending a billing data response (initial), and ATCDR authorizes the ATC service or the ATC service event.

[0319] Step 5: For the service, continue the ATC service process, such as interacting with the consumer NF or UE (e.g., including buffering or synchronization of ATC services).

[0320] Step 6: The ATC service or the event procedure of the ATC service is completed.

[0321] Step 7: For ATC services or ATC service events, ATCDR sends a billing data request (termination) to CHF.

[0322] Step 8: For ATC services or ATC service events, CHF disables CDR.

[0323] Step 9: CHF confirms by sending a billing data response (termination) to ATCDR.

[0324] Step 10: ATCDR receives CHF's acknowledgment (ACK) and confirms the completion of the ATC service or the ATC service event.

[0325] 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.

[0326] 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.

[0327] 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 a configuration file, 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.

[0328] 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.

[0329] Figure 5 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 5, the communication device 500 may include at least one of the following: a transceiver module 501 and a processing module 502.

[0330] In some embodiments, the communication device 500 may be located at the first node 101. In some embodiments, the transceiver module 501 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 for a first service or a first event of the first service, the first service supports asynchronous communication, and the first node supports the collection of billing information. Optionally, the transceiver module 501 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, which will not be elaborated here. Optionally, the processing module 502 may be used to perform at least one of the other steps performed by the first node 101 in any of the above methods, which will not be elaborated here.

[0331] In some embodiments, the communication device 500 may be configured as a second node 102. In some embodiments, the transceiver module 501 may be configured to: receive first information sent by the first node; and perform billing for a first service or an event of the first service based on the first information; wherein the first service supports asynchronous communication and the first node supports the collection of billing information. Optionally, the transceiver module 501 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the second node 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module 502 may be used to perform at least one of the other steps performed by the second node 102 in any of the above methods, which will not be elaborated here.

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

[0333] 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.

[0334] 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.

[0335] 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 a first node, a second node, or a chip, chip system, or processor that supports the first node in implementing any of the above methods; it can also be a chip, chip system, or processor that supports the second node in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments, and specific details can be found in the descriptions in the above method embodiments.

[0336] 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.

[0337] 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 transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 6101 performs at least one of the other steps. 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.

[0338] 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.

[0339] 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.

[0340] 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.

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

[0342] 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.

[0343] 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. For example, the interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 6202 performs 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 the other steps.

[0344] 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.

[0345] 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.

[0346] 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.

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

[0348] 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.

[0349] 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 first information to the second node, wherein the first information is used to instruct the second node to perform billing for the first service or a first event of the first service, the first service supports asynchronous communication, and the first node supports the collection of billing information.

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 information.

3. The method according to claim 1 or 2, wherein, The billing information includes at least one of the following: Billing data related to the storage time usage of the first service; Billing data related to the storage data usage of the first service; Billing data related to the storage event usage of the first service; Billing data related to the first service; Billing events related to the first event; Billing data related to the data grouping of the first service; Billing events related to data packets from the first service; Billing data related to sponsors; Billing events related to sponsors; Billing data related to the service area of ​​the first service; Billing events related to the service area of ​​the first service.

4. The method according to claim 3, wherein, The first event includes at least one of the following: The time window for storing information; Load level of stored information; The number of terminals associated with the transmission of stored data; The number of sessions associated with the transmission of stored data; The amount of stored data transmitted associated with the terminal; The amount of stored data transferred in the session; Expiration notice; The number of terminals whose stored data has expired; The number of sessions whose stored data has expired; Alarm notification.

5. The method according to claim 4, wherein, The billing information is related to at least one of the following: Storage time usage of the first service; The amount of storage data used by the first service; Storage event usage of the first service; The number of service signaling entries for the first service stored; The number of service signaling messages transmitted, wherein the service signaling messages originate from the storage function node of the first service; The first service; The rate group associated with the first service; The billing keywords associated with the first service; The sponsor of the first business; The service area of ​​the first service.

6. The method according to any one of claims 1 to 5, wherein, The sending of the first information is triggered by a first condition, which is related to the function of the first service and is used to indicate the status of the function.

7. The method according to any one of claims 1 to 6, wherein, The first condition is included in the billing configuration information of the first node, and the billing configuration information is configured according to one of the following: event; business; Request the node for the first service; Request the node of the first event; Sponsor.

8. The method according to claim 6 or 7, wherein, The first condition includes at least one of the following: The first service begins; The first service has ended; The first event begins; The first event has ended; The function of the first service has been changed.

9. The method according to any one of claims 1 to 8, wherein, Sending the first information to the second node includes: Based on the address information of the second node, the first information is sent to the second node; wherein, The address information of the second node is determined based on at least one of the following: The address of the second node used to transmit the context of the first service; The address of the second node as part of the access and mobility policy control information; The address of the second node as a billing feature; The address of the second node provided during the node discovery process; The address of the second node associated with the billing characteristics of the first node, which are provided by the local configuration of the first node.

10. A communication method, executed by a second node, wherein, The method includes: Receive the first message sent by the first node; Based on the first information, billing is performed for the first service or the event of the first service; The first service supports asynchronous communication, and the first node supports the collection of billing 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 information.

12. The method according to claim 10 or 11, wherein, The billing information includes at least one of the following: Billing data related to the storage time usage of the first service; Billing data related to the storage data usage of the first service; Billing data related to the storage event usage of the first service; Billing data related to the first service; Billing events related to the first event; Billing data related to the data grouping of the first service; Billing events related to data packets from the first service; Billing data related to sponsors; Billing events related to sponsors; Billing data related to the service area of ​​the first service; Billing events related to the service area of ​​the first service.

13. The method according to claim 12, wherein, The first event includes at least one of the following: The time window for storing information; Load level of stored information; The number of terminals associated with the transmission of stored data; The number of sessions associated with the transmission of stored data; The amount of stored data transmitted associated with the terminal; Transfer volume of session-associated stored data Expiration notice; The number of terminals whose stored data has expired; The number of sessions whose stored data has expired; Alarm notification.

14. The method according to claim 13, wherein, The billing information is related to at least one of the following: Storage time usage of the first service; The amount of storage data used by the first service; Storage event usage of the first service; The number of service signaling entries for the first service stored; The number of service signaling messages transmitted, wherein the service signaling messages originate from the storage node of the first service; The first service; The rate group associated with the first service; The billing keywords associated with the first service; The sponsor of the first business; The service area of ​​the first service.

15. The method according to any one of claims 10 to 14, wherein, The sending of the first information is triggered by a first condition, which is related to the function of the first service and is used to indicate the status of the function.

16. The method according to any one of claims 10 to 15, wherein, The first condition is included in the billing configuration information of the first node, and the billing configuration information is configured according to one of the following: event; business; Request the node of the first service or the first event; Sponsor.

17. The method according to claim 15 or 16, wherein, The first condition includes at least one of the following: The first service begins; The first service has ended; The first event begins; The first event has ended; The function of the first service has been changed.

18. The method according to any one of claims 10 to 17, wherein, The address information of the second node is determined based on at least one of the following: The address of the second node used to transmit the context of the first service; The address of the second node as part of the access and mobility policy control information; The address of the second node as a billing feature; The address of the second node provided during the node discovery process; The address of the second node associated with the billing characteristics of the first node, which are provided by the local configuration of the first node.

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

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

21. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 9, 10 to 18.

22. 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 to 9, 10 to 18.

Images