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

Abstract

The present disclosure relates to a communication method and apparatus, a communication device, a storage medium, and a program product. The method is executed by a first node, and comprises: determining that a first event related to charging is triggered; and sending a first message to a second node, wherein the first message is used for enabling charging for a first service. The solution of the present disclosure enables triggering and reporting of chargeable events for MC services.

Description

Communication method and apparatus, communication device, storage medium and program product TECHNICAL FIELD

[0001] The present disclosure relates to the field of wireless communication, and in particular, to a communication method and apparatus, a communication device, a storage medium and a program product. BACKGROUND

[0002] With the intelligentization of people's life, work and other scenarios, more and more massive communication (MC) devices will be deployed. MC services are usually implemented based on a large number of MC devices.

[0003] SUMMARY

[0004] Embodiments of the present disclosure relate to a communication method and apparatus, a communication device, a communication system, a storage medium and a program product.

[0005] According to a first aspect of embodiments of the present disclosure, a communication method is provided. The method is performed by a first node. The method comprises: determining that a first event related to charging is triggered; and sending, to a second node, a first message, wherein the first message is used to implement charging for a first service.

[0006] According to a second aspect of embodiments of the present disclosure, a communication method is provided. The method is performed by a second node. The method comprises: receiving a first message sent by a first node, wherein the first message is used to implement charging for a first service; and performing, according to the first message, a first operation related to the charging for the first service.

[0007] According to a third aspect of embodiments of the present disclosure, a communication apparatus is provided. The apparatus is arranged in a first node. The apparatus comprises a processing module and a transceiver module. The processing module is configured to determine that a first event related to charging is triggered; and the transceiver module is configured to send, to a second node, a first message, wherein the first message is used to implement charging for a first service.

[0008] According to a fourth aspect of embodiments of the present disclosure, a communication apparatus is provided. The apparatus is arranged in a second node. The apparatus comprises a processing module and a transceiver module. The transceiver module is configured to receive a first message sent by a first node, wherein the first message is used to implement charging for a first service; and the processing module is configured to perform, according to the first message, a first operation related to the charging for the first service.

[0009] According to a fifth aspect of embodiments of the present disclosure, a communication device is provided. The communication device comprises: one or more processors; and a memory storing instructions. The instructions, when executed by the device, cause the communication device to implement the communication method according to any one of the first aspect and the second aspect.

[0010] According to a sixth aspect of embodiments of the present disclosure, a communication system is provided. The communication system comprises a first node, a second node. The first node is configured to perform the communication method according to the first aspect. The second node is configured to perform the communication method according to the second aspect.

[0011] According to a seventh aspect of embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. The instructions, when executed on a communication device, cause the communication device to perform the communication method according to any one of the first aspect and the second aspect.

[0012] According to an eighth aspect of embodiments of the present disclosure, a program product is provided. The program product, when executed by a communication device, causes the communication device to perform the communication method according to any one of the first aspect and the second aspect.

[0013] According to a ninth aspect of embodiments of the present disclosure, a computer program is provided. The computer program, when executed on a computer, causes the computer to perform the communication method according to any one of the first aspect and the second aspect.

[0014] According to a tenth aspect of embodiments of the present disclosure, a chip or chip system is provided. The chip or chip system comprises processing circuitry. The processing circuitry is configured to perform the communication method according to any one of the first aspect and the second aspect.

[0015] According to embodiments of the present disclosure, triggering and reporting of a billable event of an MC service can be implemented.

[0016] It should be understood that the general description above and the detailed description below are only exemplary and explanatory, and do not constitute a limitation on the embodiments of the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the present disclosure and serve to explain the principles of the present disclosure together with the specification.

[0018] FIG. 1 is an architecture schematic diagram of a communication system according to embodiments of the present disclosure.

[0019] FIGS. 2A to 2D are schematic diagrams of connection topologies for AIoT.

[0020] FIG. 3A is an interaction schematic diagram of a communication method according to embodiments of the present disclosure.

[0021] FIG. 3B is an interaction schematic diagram of a communication method according to embodiments of the present disclosure.

[0022] FIG. 3C is an interaction schematic diagram of a communication method according to embodiments of the present disclosure.

[0023] FIG. 4A is a flow diagram of a communication method according to an embodiment of the present disclosure.

[0024] FIG. 4B is a flow diagram of a communication method according to an embodiment of the present disclosure.

[0025] FIG. 4C is a flow diagram of a communication method according to an embodiment of the present disclosure.

[0026] FIG. 5 is a flow diagram of a communication method according to an embodiment of the present disclosure.

[0027] FIG. 6 is an interaction diagram of a communication method according to an embodiment of the present disclosure.

[0028] FIG. 7 is a structural diagram of a communication apparatus according to an embodiment of the present disclosure.

[0029] FIG. 8A is a structural diagram of a communication device according to an embodiment of the present disclosure.

[0030] FIG. 8B is a structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] The embodiments of the present disclosure provide a communication method and apparatus, a communication device, a communication system, a storage medium and a program product.

[0032] In a first aspect, the embodiments of the present disclosure provide a communication method. The method is performed by a first node. The method comprises: determining that a first event related to charging is triggered; and sending a first message to a second node, wherein the first message is used to implement charging for a first service.

[0033] Through the embodiments, after determining that the first event related to charging is triggered, the first node sends the first message to the second node to implement the charging for the first service. In this way, triggering and reporting of the chargeable event of the first service can be implemented, and the accuracy and efficiency of charging can be improved.

[0034] In combination with some embodiments of the first aspect, in some embodiments, the first message comprises at least one of the following: charging indication information, used to trigger the second node to perform a charging operation; event indication information, used to indicate the first event; and charging data, comprising charging data collected for the first service.

[0035] In combination with some embodiments of the first aspect, in some embodiments, the charging data comprises at least one of the following: charging data related to registration; charging data related to connection; charging data related to location; charging data related to the first service; and charging data related to a first task of the first service.

[0036] Through the embodiment, corresponding charging data can be acquired for different functions or objects. The charging data can be related to registration, connection, location, first service, first task of the first service, etc. The registration, connection, location, first service, and first task of the first service can all be used as a basis for collecting charging data, thereby achieving charging data collection for specific objects and enhancing the flexibility and applicability of charging.

[0037] With reference to some embodiments of the first aspect, in some embodiments, the charging data is acquired according to charging information, and the charging information comprises at least one of the following: identification information of the third node; identification information of the fourth node; identification information of a service area of the first service; identification information of a first task of the first service.

[0038] With reference to some embodiments of the first aspect, in some embodiments, the charging information is related to at least one of the following: application function, reader, large-scale communication device, rate group, charging key value, and payment party.

[0039] With reference to some embodiments of the first aspect, in some embodiments, the first message is sent according to address information of the second node; and the address information of the second node is obtained in at least one of the following manners: determined according to the received context information; provided by a policy control function (PCF); provided by a unified data management (UDM) function; provided by a network repository function (NRF); provided by an access and mobility management function (AMF); or determined according to local configuration.

[0040] With reference to some embodiments of the first aspect, in some embodiments, the priority order between the multiple manners of determining the address information can be determined according to at least one of the following: operator policy, and local configuration.

[0041] With reference to some embodiments of the first aspect, in some embodiments, the first message is related to a first area of the first service; and the first area is obtained in at least one of the following manners: determined by the second node, or preconfigured.

[0042] With reference to some embodiments of the first aspect, in some embodiments, the first event is related to at least one of the following: connection of the first node; registration of the third node; registration of the fourth node; the first service; a first task of the first service; and location reporting.

[0043] In some embodiments of the first aspect, in some embodiments, the first node is deployed with a charging configuration, the charging configuration being used to determine at least one of: the first event, the charging status.

[0044] In some embodiments of the first aspect, in some embodiments, the charging configuration is related to at least one of: an application function, a reader-writer, a massive communication device, a rate group, a charging key value, a payment party.

[0045] In a second aspect, the embodiments of the present disclosure provide a communication method. The method is performed by a second node. The above method comprises: receiving a first message sent by a first node, wherein the first message is used to implement charging for a first service; and performing a first operation related to charging of the first service according to the first message.

[0046] Through the present embodiment, the second node can receive the first message sent by the first node to implement charging for the first service. In this way, triggering and reporting of a chargeable event of the first service can be implemented, and the accuracy and efficiency of charging can be improved.

[0047] In some embodiments of the second aspect, in some embodiments, the first message comprises at least one of: charging indication information, used to trigger the second node to perform the charging operation; event indication information, used to indicate the first event; and charging data, comprising charging data collected for the first service.

[0048] In some embodiments of the second aspect, in some embodiments, the charging data comprises at least one of: charging data related to registration; charging data related to connection; charging data related to location; charging data related to the first service; and charging data related to a first task of the first service.

[0049] In some embodiments of the second aspect, in some embodiments, the charging data is obtained according to charging information, the charging information comprising at least one of: identification information of a third node; identification information of a fourth node; identification information of a service area of the first service; and identification information of a first task of the first service.

[0050] In some embodiments of the second aspect, in some embodiments, the charging information is related to at least one of: an application function, a reader-writer, a massive communication device, a rate group, a charging key value, a payment party.

[0051] In some embodiments of the second aspect, in some embodiments, the first operation comprises at least one of: creating a charging data record (CDR); opening the CDR; and closing the CDR.

[0052] In some embodiments of the second aspect, in some embodiments, the first message is related to a first area of the first service; wherein the first area is obtained by at least one of the following: determined by the second node, preconfigured.

[0053] In some embodiments of the second aspect, in some embodiments, the first event is related to at least one of the following: a connection of the first node; a registration of a third node; a registration of a fourth node; the first service; a first task of the first service; a location report.

[0054] In a third aspect, the embodiments of the present disclosure provide a communication apparatus. The apparatus is arranged in a first node. The apparatus comprises a processing module and a transceiver module. The processing module is configured to determine that a first event related to charging is triggered. The transceiver module is configured to send a first message to a second node, wherein the first message is used to implement charging for a first service.

[0055] In some embodiments of the third aspect, in some embodiments, the first message comprises at least one of the following: charging indication information, used to trigger the second node to perform a charging operation; event indication information, used to indicate the first event; charging data, comprising charging data collected for the first service.

[0056] In some embodiments of the third aspect, in some embodiments, the charging data comprises at least one of the following: charging data related to registration; charging data related to connection; charging data related to location; charging data related to the first service; charging data related to a first task of the first service.

[0057] In some embodiments of the third aspect, in some embodiments, the charging data is obtained according to charging information, and the charging information comprises at least one of the following: identification information of the third node; identification information of the fourth node; identification information of a service area of the first service; identification information of a first task of the first service.

[0058] In some embodiments of the third aspect, in some embodiments, the charging information is related to at least one of the following: application function, reader, large-scale communication device, rate group, charging key value, payment party.

[0059] In some embodiments of the third aspect, in some embodiments, the first message is sent according to address information of the second node; wherein the address information of the second node is obtained by at least one of the following: determined according to received context information; provided by a PCF; provided by a UDM function; provided by a NRF; provided by an AMF; determined according to local configuration.

[0060] In some embodiments of the third aspect, in some embodiments, the priority order among the plurality of ways of determining the address information can be determined according to at least one of the following: an operator policy, a local configuration.

[0061] In some embodiments of the third aspect, in some embodiments, the first message is related to a first area of the first service; wherein the first area is obtained by at least one of the following: determined by the second node, preconfigured.

[0062] In some embodiments of the third aspect, in some embodiments, the first event is related to at least one of the following: a connection of the first node; a registration of a third node; a registration of a fourth node; the first service; a first task of the first service; a location report.

[0063] In some embodiments of the third aspect, in some embodiments, the first node is deployed with a charging configuration, the charging configuration being used to determine at least one of the following: the first event, a charging state.

[0064] In some embodiments of the third aspect, in some embodiments, the charging configuration is related to at least one of the following: an application function, a reader-writer, a large-scale communication device, a rate group, a charging key value, a payment party.

[0065] In a fourth aspect, the embodiments of the present disclosure provide a communication apparatus. The apparatus is arranged at a second node. The apparatus includes a processing module and a transceiver module. The transceiver module is configured to receive a first message sent by a first node, wherein the first message is used to implement charging for a first service. The processing module is configured to perform a first operation related to the charging for the first service according to the first message.

[0066] In some embodiments of the fourth aspect, in some embodiments, the first message includes at least one of the following: charging indication information, used to trigger the second node to perform a charging operation; event indication information, used to indicate a first event; charging data, including charging data collected for the first service.

[0067] In some embodiments of the fourth aspect, in some embodiments, the charging data includes at least one of the following: charging data related to a registration; charging data related to a connection; charging data related to a location; charging data related to the first service; charging data related to a first task of the first service.

[0068] In some embodiments of the fourth aspect, in some embodiments, the charging data is obtained according to charging information, the charging information including at least one of the following: identification information of a third node; identification information of a fourth node; identification information of a service area of the first service; identification information of a first task of the first service.

[0069] In some embodiments combining with the fourth aspect, in some embodiments, the charging information is related to at least one of: an application function, a reader-writer, a large-scale communication device, a rate group, a charging key value, a payment party.

[0070] In some embodiments combining with the fourth aspect, in some embodiments, the first operation comprises at least one of: creating a charging data record (CDR); opening a CDR; closing a CDR.

[0071] In some embodiments combining with the fourth aspect, in some embodiments, the first message is related to a first area of the first service; wherein the first area is obtained by at least one of: determined by the second node, preconfigured.

[0072] In some embodiments combining with the fourth aspect, in some embodiments, the first event is related to at least one of: a connection of the first node; a registration of a third node; a registration of a fourth node; the first service; a first task of the first service; a location report.

[0073] In a fifth aspect, the embodiments of the present disclosure provide a communication device. The communication device comprises: one or more processors; and a memory storing instructions. The instructions, when executed by the communication device, cause the communication device to implement the communication method according to any one of the first aspect and possible implementation manners thereof.

[0074] In a sixth aspect, the embodiments of the present disclosure provide a communication device. The communication device comprises: one or more processors; and a memory storing instructions. The instructions, when executed by the communication device, cause the communication device to implement the communication method according to any one of the second aspect and possible implementation manners thereof.

[0075] In a seventh aspect, the embodiments of the present disclosure provide a communication system. The communication system comprises at least one of: a first node, a second node. The first node is configured to perform the communication method according to any one of the first aspect and possible implementation manners thereof. The second node is configured to perform the communication method according to any one of the second aspect and possible implementation manners thereof.

[0076] In an eighth aspect, the embodiments of the present disclosure provide a storage medium. The storage medium stores instructions. The instructions, when executed on a communication device, cause the communication device to perform the communication method according to any one of the first aspect, the second aspect and possible implementation manners thereof.

[0077] In a ninth aspect, the embodiments of the present disclosure provide a program product. The program product, when executed by a communication device, causes the communication device to perform the communication method according to any one of the first aspect, the second aspect and possible implementation manners thereof.

[0078] In a tenth aspect, the embodiments of the present disclosure provide a computer program. The computer program, when running on a computer, causes the computer to perform the communication method according to any one of the first aspect, the second aspect, and possible implementation manners thereof.

[0079] In an eleventh aspect, the embodiments of the present disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method according to any one of the first aspect, the second aspect, and possible implementation manners thereof.

[0080] It can be understood that the above communication apparatus, communication device, communication system, storage medium, program product, computer program, chip, and chip system are all used to perform the method provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved thereby can refer to the beneficial effects in the corresponding method, which will not be described here again.

[0081] The embodiments of the present disclosure provide a communication method and apparatus, a communication device, a communication system, a storage medium, and a program product. In some embodiments, the terms of the communication method, the information processing method, and the information transmission method can be replaced with each other, the terms of the communication apparatus, the communication device, the network device, the network function, and the network entity can be replaced with each other, and the terms of the communication system and the information processing system can be replaced with each other.

[0082] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation manners in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, the steps of different embodiments or part or all of the steps of different embodiments can be combined arbitrarily, and an embodiment can be combined with the optional implementation manners of other embodiments.

[0083] In the embodiments of the present disclosure, the terms and / or descriptions between the embodiments are consistent and can be referred to each other if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0084] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and not as a limitation on the present disclosure.

[0085] In the embodiments of the present disclosure, an element represented in singular form, such as "a", "an", "one", "the", "said", "the aforementioned", "the foregoing", "this", and the like, unless otherwise specified, can represent "one and only one", or can represent "one or more", "at least one", and the like. For example, in the case of using articles such as "a", "an", "the" in English, the noun after the article can be understood as a singular expression, or can be understood as a plural expression.

[0086] In the embodiments of the present disclosure, "a plurality of" means two or more than two.

[0087] In some embodiments, the terms "at least one", "one or more", and the like can be replaced with each other.

[0088] In some embodiments, the writing manners such as "at least one of A, B", "A and / or B", "A in one case, B in another case", "in response to a case A, in response to a case B", and the like can include the following technical solutions according to the case: A is executed in some embodiments (A is executed regardless of B); B is executed in some embodiments (B is executed regardless of A); A and B are selectively executed in some embodiments (A and B are selected from A and B); A and B are executed in some embodiments (A and B are executed). When there are more branches such as A, B, C, and the like, it is similar to the above.

[0089] In some embodiments, the writing manners such as "A or B" and the like can include the following technical solutions according to the case: A is executed in some embodiments (A is executed regardless of B); B is executed in some embodiments (B is executed regardless of A); A and B are selectively executed in some embodiments (A and B are selected from A and B). When there are more branches such as A, B, C, and the like, it is similar to the above.

[0090] The prefix words of "first", "second" and the like in the embodiments of the present disclosure are merely used to distinguish different description objects, and do not constitute limitation on the position, order, priority, quantity or content of the description objects. The description of the description objects should refer to the description in the context of the claims or embodiments, and should not constitute redundant limitation because of the use of the prefix words. For example, the description objects are "fields", and the ordinal words before "fields" in "first field" and "second field" do not limit the position or order between "fields". "First" and "second" do not limit whether the "fields" modified thereby are in the same message, nor do they limit the order of "first field" and "second field". For another example, the description objects are "levels", and the ordinal words before "levels" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description objects is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "devices" can be one or more. In addition, the objects modified by different prefix words can be the same or different. For example, the description objects are "devices", and "first device" and "second device" can be the same device or different devices, and their types can be the same or different. For another example, the description objects are "information", and "second information" and "first information" can be the same information or different information, and their contents can be the same or different.

[0091] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0092] In some embodiments, the terms of "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0093] In some embodiments, the terms of "greater than", "more than", "higher than", "exceeding" and the like can be replaced with each other, the terms of "greater than or equal to", "not less than", "more than or equal to", "not less than", "higher than or equal to", "not lower than", "above" and the like can be replaced with each other, the terms of "less than", "less than", "lower than" and the like can be replaced with each other, the terms of "less than or equal to", "not greater than", "less than or equal to", "not more than", "lower than or equal to", "not higher than", "below" and the like can be replaced with each other.

[0094] In some embodiments, an apparatus or the like can be interpreted as an entity, and can also be interpreted as virtual, and the name thereof is not limited to the name described in the embodiments, and the terms "apparatus", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject" and the like can be replaced with each other.

[0095] In some embodiments, a "network" can be interpreted as an apparatus (for example, an access network device, a core network device, and the like) included in the network.

[0096] 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", "bandwidth part (BWP)" and the like can be replaced with each other.

[0097] 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," "client," and so on can be replaced with each other.

[0098] In some embodiments, the access network device, the core network device, or the network device can be replaced with a terminal. For example, the embodiments of the present disclosure can also be applied to a structure in which communication between the access network device, the core network device, or the network device and the terminal is replaced with communication between a plurality of terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. In addition, the terms "uplink," "downlink," and the like can also be replaced with terms corresponding to the inter-terminal communication (e.g., "side"). For example, the uplink channel, the downlink channel, and the like can be replaced with the side channel, and the uplink, the downlink, and the like can be replaced with the sidelink.

[0099] In some embodiments, the terminal can be replaced with the access network device, the core network device, or the network device. In this case, the access network device, the core network device, or the network device can also be configured to have all or part of the functions of the terminal.

[0100] In some embodiments, the data, information, etc. can be obtained in compliance with the laws and regulations of the country where the location is situated.

[0101] In some embodiments, the data, information, etc. can be obtained after obtaining the consent of the user.

[0102] In addition, each element, each row, or each column in the table of the embodiments of the present 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.

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

[0104] In some embodiments, the first node 101 can be configured to implement the management, control, charging triggering, etc. of the massive communication service.

[0105] In some embodiments, the first node 101 may, for example, be at least part of a controller.

[0106] In some embodiments, the first node 101 may, for example, be a massive communication function (MCF). In some embodiments, the MCF can also be referred to as a massive communication management function (MCMF).

[0107] In some embodiments, the massive communication service may, for example, be an AIoT service, and the first node 101 may, for example, be an AIoT function (AIoTF). In some embodiments, the first node 101 may, for example, be an AIoT management function (AIoTMF).

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

[0109] In some embodiments, the first node 101 may, for example, be a charging trigger function (CTF). In some embodiments, the CTF can be deployed in the MCF or the AMF. In some embodiments, the CTF can be independent of the MCF and the AMF.

[0110] In some embodiments, the second node 102 can implement functions such as charging related functions.

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

[0112] In some embodiments, the third node 103 may, for example, be used to implement functions such as support for A-Uu air interface, registration to a controller, support for requesting corresponding functions from the controller, implementation of inventory and delivery of inventory results, delivery of commands and command responses, and the like.

[0113] In some embodiments, the third node 103 may, for example, be a reader.

[0114] In some embodiments, the fourth node 104 can be used to implement MC services.

[0115] In some embodiments, the fourth node 104 may, for example, be an MC device. In some embodiments, the fourth node 104 can be an AIoT device.

[0116] In some embodiments, the fifth node 105 can be used to implement functions such as registration of MC devices and readers, authentication and authorization of AFs, verification of AFs, storage of reader information, storage of MC device information, and the like.

[0117] In some embodiments, the fifth node 105 can be part of a controller.

[0118] In some embodiments, the fifth node 105 can include at least one of an AMF, a session management function (SMF), a policy control function (PCF), an authentication server function (AUSF), and a unified data management (UDM).

[0119] In some embodiments, the first node 101 can be a core network device or the like. It can be understood that the first node 101 can also be other types of devices, and the embodiments of the present disclosure do not make specific limitations thereto.

[0120] In some embodiments, the second node 102 can be a server, a core network device, or the like. It can be understood that the second node 102 can also be other types of devices, and the embodiments of the present disclosure do not make specific limitations thereto.

[0121] In some embodiments, the third node 103 can be a terminal, an access network device, or the like. It can be understood that the third node 103 can also be other types of devices, and the embodiments of the present disclosure do not make specific limitations thereto.

[0122] In some embodiments, the fourth node 104 can be a sensor, an electronic tag, a terminal, or the like. It can be understood that the fourth node 104 can also be other types of devices, and the embodiments of the present disclosure do not make specific limitations thereto.

[0123] In some embodiments, the fifth node 105 can be a server, a core network device, or the like. It can be understood that the fifth node 105 can also be other types of devices, and the embodiments of the present disclosure do not make specific limitations thereto.

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

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

[0126] In some embodiments, the above-described communication system 100 can be a 5G communication system, a 6G communication system. It should be noted that the communication system 100 can also be other communication systems, for example, a 4G communication system, and the embodiments of the present disclosure do not make specific limitations thereto.

[0127] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed by the embodiments of the present disclosure. It can be known by those skilled in the art that, with the evolution of system architecture and the appearance of new business scenarios, the technical solutions proposed by the embodiments of the present disclosure are also applicable to similar technical problems.

[0128] The following embodiments of the present disclosure can be applied to the communication system 100 shown in FIG. 1 or part of the subjects in the communication system 100, but are not limited thereto. The subjects shown in FIG. 1 are exemplary, the communication system 100 can include all or part of the subjects in FIG. 1, or include other subjects other than FIG. 1, the number and form of each subject is arbitrary, each subject can be physical or virtual, the connection relationship between each subject is exemplary, each subject can not be connected or can be connected, the connection can be any way, can be direct connection or indirect connection, can be wired connection or wireless connection.

[0129] Embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication methods, next-generation system expanded based on them, and the like. In addition, a plurality of systems can be combined (for example, combination of LTE or LTE-A and 5G, and the like).

[0130] In recent years, with the wide application of Internet of Things (IoT) technology in the field of wireless communication, higher requirements are put forward for the size, complexity, power and other performances of IoT devices. In particular, IoT devices often need to be built-in with energy storage devices such as batteries. This results in the need for people to manually replace or charge the batteries of IoT devices. Obviously, this not only increases the maintenance cost of IoT devices, but also reduces the convenience of IoT devices.

[0131] To address the above concerns, a new IoT technology, i.e., ambient IoT (AIoT) technology, is proposed. A device employing the AIoT technology can be referred to as an AIoT device. An AIoT device can be a device that is powered by energy harvesting. For example, an AIoT device can harvest energy in the form of electromagnetic waves, light, sound waves, etc. in its surrounding environment to achieve power supply. In some embodiments, an AIoT device can have limited energy storage capability.

[0132] In some embodiments, AIoT devices can be classified into three types. The first type of AIoT device has neither energy storage capability nor independent signal generation capability. The second type of AIoT device has energy storage capability but does not have independent signal generation capability. The third type of AIoT device has both energy storage capability and independent signal generation capability. For the first type of AIoT device and the second type of AIoT device, a signal can be generated in a backscattering manner.

[0133] In some embodiments, there are multiple connection topologies for AIoT devices. FIGs. 2A-2D are schematic diagrams of connection topologies for AIoT. As shown in FIGs. 2A-2D, there can be four different connection topologies for AIoT devices in general.

[0134] In some embodiments, as shown in FIG. 2A, the first connection topology (or referred to as topology 1, first type of topology) can be: base station <—> AIoT device. In some embodiments, an AIoT device can directly communicate bi-directionally with a base station. The communication between the base station and the AIoT device can include AIoT traffic related data and / or signaling. In the first connection topology, the transmission from the base station to the AIoT device and the transmission from the AIoT device to the base station can be the same or different.

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

[0136] In some embodiments, as shown in FIG. 2C, the third connection topology (or referred to as topology 3, the third type of topology) can be: base station <—> auxiliary node <—> AIoT device <—> base station. In some embodiments, the AIoT device can send data and / or signaling to the base station, and can receive data and / or signaling from the auxiliary node. In some embodiments, the AIoT device can receive data and / or signaling from the base station, and can send data and / or signaling to the auxiliary node. In this topology, the auxiliary node can be an AIoT-capable relay, an integrated access and backhaul node, a UE, a repeater, etc.

[0137] In some embodiments, as shown in FIG. 2D, the fourth connection topology (or referred to as topology 4, the fourth type of topology) can be: UE <—> AIoT device. In some embodiments, the AIoT device can communicate with the UE in both directions. In some embodiments, the communication between the AIoT device and the UE can include data and / or signaling of AIoT traffic.

[0138] In different connection topologies, the reader-writer can be implemented by different types of devices. For example, the reader-writer can be a base station, an intermediate node, a UE, etc.

[0139] Massive communication (MC) is one of the development directions of 6G technology. In massive communication services, the number and types of devices participating in communication will be more and more.

[0140] Then, how to implement effective charging for MC services is a problem to be solved.

[0141] FIG. 3A is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. The communication method related by the embodiment of the present disclosure can be applied to the communication system 100. As shown in FIG. 3A, the communication method of the embodiment of the present disclosure includes steps S3101 to S3107.

[0142] In step S3101, the third node 103 and / or the fourth node 104 sends a registration request message to the first node 101.

[0143] In some embodiments, the third node 103 and / or the fourth node 104 can initiate a registration process to the first node 101.

[0144] In some embodiments, the first node 101 can receive the registration request message. The registration request message can be used to register the third node 103 and / or the fourth node 104 to the first node 101.

[0145] In some embodiments, the registration request message can include third information.

[0146] In some embodiments, the third information can be used to implement registration of the third node 103 and / or the fourth node 104.

[0147] In some embodiments, the third information can comprise at least one of the following: identification information, capability information, location information.

[0148] In some embodiments, the identification information can be used to identify the third node 103 and / or the fourth node 104. For example, the identification information can comprise an identifier of the third node 103. For example, the identification information can comprise an identifier of the fourth node 104.

[0149] In some embodiments, the capability information can be used to indicate capability of the third node 103 and / or the fourth node 104. For example, the capability information can indicate capability of the third node 103. For example, the capability information can indicate capability of the fourth node 104.

[0150] In some embodiments, the location information can be used to indicate location of the third node 103 and / or the fourth node 104. For example, the location information can comprise a deployment location of the third node 103. For example, the location information can comprise a deployment location of the fourth node 104.

[0151] In step S3102, the first node 101 performs a registration procedure.

[0152] In some embodiments, the first node 101 can interact with the third node 103 and / or the fourth node 104, and the fifth node 105, to continue the registration procedure, to implement registration for the third node 103 and / or the fourth node 104.

[0153] In some embodiments, in step S3102, the first node 101 can determine the second node 102.

[0154] In some embodiments, the first node 101 can determine address information of the second node 102.

[0155] In some embodiments, the address information of the second node 102 can be used to address the second node 102. In some embodiments, the address information of the second node 102 can be used to implement communication with the second node 102. In some embodiments, the address information of the second node 102 can comprise an internet protocol (IP) address of the second node 102. It can be understood that the address information of the second node 102 can also comprise other information that can be used to address the second node 102, which is not limited specifically in the embodiments of the present disclosure.

[0156] In some embodiments, the address information of the second node 102 can be obtained by at least one of the following manners: determined according to the received context information; provided by a PCF; provided by a UDM function; provided by a NRF; provided by an AMF; determined according to local configuration.

[0157] In some embodiments, the address information of the second node 102 can be obtained by the first node 101 from context information received from another first node (not shown). In some embodiments, the another first node can be a source node, and the first node 101 can be a target node. In some embodiments, the first service or the first task of the first service can be switched from the another first node to the first node 101. In order to realize the switching, the context information of the first service and / or the context information of the first task can be sent from the another first node to the first node 101. The address information of the second node 102 can be included in the context information.

[0158] In some embodiments, the first service can include an MC service. In some embodiments, the MC service can include an AIoT service.

[0159] In some embodiments, the first task of the first service can include at least one of the following: inventory, command. In some embodiments, the command can include at least one of the following: read, write, disable, environment data reporting, perception data reporting, event subscription of the MC service. It can be understood that the first task can also have other types, which are not limited in the embodiments of the present disclosure.

[0160] In some embodiments, the address information of the second node 102 can be provided by a PCF. In some embodiments, the PCF can provide access and mobility policy control information to the first node 101, and the address information of the second node 102 can be included in the access and mobility policy control information.

[0161] In some embodiments, the address information of the second node 102 can be provided by a UDM. In some embodiments, the UDM can provide charging characteristics to the first node 101, and the address information of the second node 102 can be included in the charging characteristics. In some embodiments, the charging characteristics can be included in subscription information related to the third node 103 and / or the fourth node 104 in the UDM.

[0162] In some embodiments, the address information of the second node 102 can be provided by a NRF. In some embodiments, the NRF can provide the address information of the second node 102 to the first node 101 in a discovery process.

[0163] In some embodiments, the address information of the second node 102 can be provided by an AMF. In some embodiments, the AMF providing the address information of the second node 102 can comprise at least one of the following: an AMF serving a reader-writer of the UE type, an AMF having the same or similar service area as the first node 101.

[0164] In some embodiments, the address information of the second node 102 can be determined according to a local configuration of the first node 101. In some embodiments, the address information of the second node 102 can be saved in the configuration information of the first node 101.

[0165] In some embodiments, the first node 101 can obtain the address information of the second node 102 in multiple ways as above. In some embodiments, the address information obtained by the first node 101 in different ways can be the same or different.

[0166] In some embodiments, there can be a priority relationship between the multiple ways in which the first node 101 obtains the address information of the second node 102. In some embodiments, the priority order between the multiple ways of obtaining the address information can be determined according to at least one of the following: operator policy, local configuration.

[0167] In step S3103, the first node 101 sends a registration accept message to the third node 103 and / or the fourth node 104.

[0168] In some embodiments, the third node 103 and / or the fourth node 104 can receive the registration accept message.

[0169] In some embodiments, the registration accept message can be used to inform that the registration of the third node 103 and / or the fourth node 104 is accepted.

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

[0171] In some embodiments, the second node 102 can receive the first message.

[0172] In some embodiments, the first message can be used to request the second node 102 to implement charging.

[0173] In some embodiments, the first message can be sent by the first node 101 for a registration, which can comprise at least one of the following:

[0174] The registration of the third node 103, the registration of the fourth node 104.

[0175] In some embodiments, the first message is not limited in name, which can be, for example, a charging data request message, a charging request message, a charging execution indication message, etc.

[0176] In some embodiments, the first message can comprise at least one of the following: charging indication information, event indication information, charging data.

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

[0178] In some embodiments, the charging operation can comprise a first operation. In an example, the charging indication information can be used to trigger the second node 102 to perform the first operation.

[0179] In some embodiments, the charging indication information can be included in a specific field. In an example, the field can comprise one bit. When the bit value of the bit is 1, the charging indication information indicates to perform the charging operation. At this time, the charging is in an active state. When the bit value of the bit is 0, the charging indication information indicates not to perform the charging operation or to stop the charging operation. At this time, the charging is in an inactive state.

[0180] In some embodiments, the presence of the charging indication information can represent to perform the charging operation, and the absence of the charging indication information can represent not to perform the charging operation or to stop the charging operation.

[0181] In some embodiments, the event indication information can be used to indicate a first event.

[0182] In some embodiments, the first event can be an event related to charging. In some embodiments, the first event can be referred to as a chargeable event.

[0183] In some embodiments, the charging data can comprise data used to implement charging.

[0184] In some embodiments, the charging data can be charging data collected for the first service. In some embodiments, the charging data can be collected by the first node 101.

[0185] In some embodiments, the charging data can comprise at least one of the following: registration related charging data, connection related charging data, location related charging data, first service related charging data, first task of the first service related charging data.

[0186] In some embodiments, the charging data can comprise registration related charging data. In some embodiments, the charging data can comprise data related to registration of the third node 103 and / or the fourth node 104.

[0187] In some embodiments, the charging data can comprise charging data related to the connection. In some embodiments, the charging data can comprise charging data related to the connection between the first node 101 and the third node 103. In some embodiments, the connection between the first node 101 and the third node 103 can be associated with the first service and / or a first task of the first service.

[0188] In some embodiments, the charging data can comprise charging data related to a location. In some embodiments, the charging data can comprise charging data related to a location of the third node 103 and / or the fourth node 104. In an example, the charging data can comprise charging data related to a deployment location of the third node 103 and / or the fourth node 104. In an example, the charging data can comprise charging data related to a service area of the third node 103 and / or the fourth node 104.

[0189] In some embodiments, the charging data can comprise charging data related to the first service. In some embodiments, the charging data can comprise at least one of: charging data related to a service request of the first service, charging data related to an inventory request and / or an inventory response, charging data related to a command request and / or a command response, environmental data of the third node 103 and / or the fourth node 104.

[0190] In some embodiments, the charging data can comprise charging data related to a first task of the first service. In some embodiments, the charging data can comprise charging data related to a session request and / or a session response of the first task of the first service.

[0191] In some embodiments, the charging data can be acquired for at least one of: an application function, a reader, an MC device, a rating group, a charging key, a payee. In an example, the charging data can be acquired for each application function. In an example, the charging data can be acquired for each reader. For example, the charging data can be acquired for each third node 103. In an example, the charging data can be acquired for each MC device. For example, the charging data can be acquired for each fourth node 104. In an example, the charging data can be acquired for each rating group. In an example, the charging data can be acquired for each charging key. In an example, the charging data can be acquired for each payee.

[0192] In some embodiments, the payment party can be a party that pays for the cost generated by the first service, i.e., a sponsor. It can be understood that the payment party can be different from the provider or the request party of the first service, and can also be different from the deployment party of the third node 103 and the fourth node 104. In some embodiments, the charging of one or more first services can correspond to the same payment party.

[0193] In some embodiments, the charging data can be obtained according to the charging information. In some embodiments, the first node 101 can collect the charging data according to the charging information.

[0194] In some embodiments, the charging information can be related to at least one of the following: an application function, a reader, an MC device, a rate group, a charging key value, a payment party.

[0195] In some embodiments, the charging information can be related to an application function. At this time, the charging data can be obtained for the application function, for example. The charging data can include at least one of the following: connection-related charging data, location-related charging data, first-service-related charging data, and first-task-of-the-first-service-related charging data.

[0196] In some embodiments, the charging information can be related to a reader. At this time, the charging data can be obtained for the third node 103, for example. The charging data can include at least one of the following: registration-related charging data, connection-related charging data, location-related charging data, first-service-related charging data, and first-task-of-the-first-service-related charging data.

[0197] In some embodiments, the charging information can be related to an MC device. At this time, the charging data can be obtained for the fourth node 104, for example. The charging data can include at least one of the following: registration-related charging data, connection-related charging data, location-related charging data, first-service-related charging data, and first-task-of-the-first-service-related charging data.

[0198] In some embodiments, the charging information can be related to a rate group and / or a charging key value. At this time, the charging data can be obtained for the third node 103, for example. The charging data can include at least one of the following: location-related charging data, first-service-related charging data, and first-task-of-the-first-service-related charging data.

[0199] In some embodiments, the charging information can be related to a payment party. At this time, the charging data can be acquired, for example, for the payment party. The charging data can include at least one of the following: charging data related to registration, charging data related to connection; charging data related to location, charging data related to the first service, charging data related to the first task of the first service.

[0200] In some embodiments, the charging information can include at least one of the following: identification information of the third node 103, identification information of the fourth node 104, identification information of a service area of the first service, identification information of the first task of the first service.

[0201] In some embodiments, the first message is sent in a case where a first event is triggered. In some embodiments, the first node 101 can send the first message to the second node 102 in a case where it is determined that the first event is triggered.

[0202] In some embodiments, the first event can be understood as a first condition. The first event being triggered can be understood as the first condition being met.

[0203] In some embodiments, in a case where the first event is triggered, the first message can contain identification information, which can be used to indicate the object of charging. In some embodiments, the identification information contained in the first message can include at least one of the following: identification information of the fourth node 104, identification information of the third node 103, identification information of the first task, identification information of the first service, identification information of the AF, identification information of the payment party.

[0204] In some embodiments, referring to Table 1 below, the categories of the first event are described.

[0205] Table 1: Categories of the first event

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

[0207] Referring to Table 1, the first event can be divided into multiple categories, for example, the multiple categories can include: registration-related events, connection-related events, service-related events, task-related events, and location reporting-related events. The first event of each category can include one or more behaviors.

[0208] In Table 1, the first column from the left gives the behavior associated with the first event. Different behaviors and different scenarios can correspond to different types of messages. The types of messages can include: event message, initial message, termination message. An event message, such as a charging data request (event), can be used to trigger an event-based charging operation. An initial message, such as a charging data request (initial), can be used to trigger a charging start. A termination message, such as a charging data request (termination), can be used to trigger a charging termination.

[0209] In some embodiments, the type of message can be indicated by charging indication information in the first message. For example, the charging indication information can be used to indicate event charging, start charging, or termination charging.

[0210] In some embodiments, the scenario in the embodiment shown in Figure 3A can be a PEC. For example, the sending of the first message can be after the registration of the third node 103 and / or the fourth node 104 has been checked.

[0211] In some embodiments, the first event given in Table 1 can have a corresponding trigger level. The trigger level can be used to represent the trigger priority or preference of the corresponding first event. In some embodiments, different categories of first events can correspond to different trigger levels.

[0212] In some embodiments, the first event-related behavior given in Table 1 can have a corresponding trigger level. The trigger level can be used to represent the trigger priority or preference of the corresponding behavior. In some embodiments, different behaviors can correspond to different trigger levels.

[0213] In some embodiments, the first message in step S3104 can be a charging data request message (event) or a charging data request message (initial).

[0214] In some embodiments, the first message can be related to a first area of the first service. The first message sent by the first node 101 can be for one first area. In some embodiments, in the case that the presence of the third node 103 and / or the fourth node 104 in the first area changes, the change can be reported to the second node 102. For example, the third node 103 and / or the fourth node 104 can be removed from the first area, or newly appear in the first area. In some embodiments, the first area can be referred to as a presence reporting area (PRA).

[0215] In some embodiments, the first area can be obtained by at least one of the following: determined by the second node 102, preconfigured.

[0216] In some embodiments, the first area can be determined by the second node 102 and provided to the first node 101. In an example, the first area can be identified by PRA identification information. In an example, the first area can be related to at least one of the following: a list of readers, a list of service identities, a list of task identities, a list of AF identities, a list of payers, a list of tracking areas (TAs), a list of access network devices, a list of cell identities.

[0217] In some embodiments, the first area can be pre-configured by an operator or a network. In an example, the first area can be identified by PRA identification information.

[0218] In some embodiments, a charging profile can be deployed in the first node 101.

[0219] In some embodiments, the charging profile can be used to determine at least one of the following: a first event, a charging status.

[0220] In some embodiments, the first event can be related to at least one of the following functions: connection of the first node 101, registration of the third node 103, registration of the fourth node 104, a first service, a first task of the first service, location reporting. In some embodiments, the connection of the first node 101 can include a connection between the first node 101 and the third node 103.

[0221] In some embodiments, the first event can be used by the first node 101 to determine whether to trigger charging. In some embodiments, the first event can be used by the first node 101 to determine whether to send the first message. In an example, step S3104 is performed in the case that the first event is triggered.

[0222] In some embodiments, the charging status can be used to indicate a status for at least one of the above functions. In some embodiments, the charging status can include at least one of the following: charging activity, charging scenario.

[0223] In some embodiments, the charging activity can include: active, inactive. The active state means that charging is in progress, i.e., charging is in an activated state. Inactive means that no charging is performed, i.e., charging is in a non-activated state.

[0224] In some embodiments, the charging scenario can include at least one of the following: IEC, ECUR, PEC.

[0225] In some embodiments, the charging profile can be related to at least one of the following: application function, reader, MC device, rate group, charging key value, payer.

[0226] In step S3105, the second node 102 can perform a first operation.

[0227] In some embodiments, the first operation can be an operation related to charging. In some embodiments, the first operation can be related to charging of the first service.

[0228] In some embodiments, the first operation can be performed by the second node 102 according to the first message.

[0229] In some embodiments, the first message can comprise charging indication information, and the second node 102 can determine to perform the first operation related to charging according to the charging indication information.

[0230] In some embodiments, the first operation can comprise an operation related to a charging data record (CDR). In some embodiments, the first operation can comprise at least one of: creating a CDR, opening a CDR, closing a CDR. In some embodiments, the type of the first message can be an event message or an initial message, and the first operation can be creating a CDR. In some embodiments, the type of the first message can be an initial message, and the first operation can be opening a CDR. In some embodiments, the type of the first message can be a termination message, and the first operation can be closing a CDR.

[0231] In some embodiments, the first operation can comprise at least one of: accepting the first message, storing information carried in the first message, and updating authorization of the first event and / or charging manner of the first time according to the first message.

[0232] In some embodiments, the second node 102 can determine whether to accept the first message.

[0233] In some embodiments, the second node 102 can store information contained in the first message locally. For example, the second node 102 can store event indication information, charging data, etc. in the first message.

[0234] In some embodiments, the first message can be used to request subscription update of the first event. In this case, the second node 102 can perform the first operation in the case that the first event changes and / or the charging manner changes.

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

[0236] In some embodiments, the second node 102 can send the second message in response to the first message.

[0237] In some embodiments, the first node 101 can receive a second message.

[0238] In some embodiments, the second message can be a response message or an acknowledgement message of the first message.

[0239] In some embodiments, the second message can indicate that the charging of the first message request is accepted. In some embodiments, the second message can indicate that the charging of the first message request is triggered. In some embodiments, the second message can indicate that the charging of the first message request is not accepted or rejected.

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

[0241] In some embodiments, through steps S3104 to S3106, the triggering and reporting of the charging can be implemented.

[0242] In some embodiments, in the interaction between the first node 101 and the second node 102, the first node 101 can implement converged charging. For example, the first node 101 can converge data related to registration. For example, the first node 101 can converge data related to connection. For example, the first node 101 can converge data related to the first service. For example, the first node 101 can converge data related to the first task. For example, the first node 101 can converge data related to location reporting. In some embodiments, the first node 101 can converge multiple data among data related to registration, data related to connection, data related to the first service, and data related to the first task. The converged charging data can be provided by the first node 101 to the second node 102 through the first message.

[0243] In step S3107, the first node 101 continues to perform the registration process.

[0244] In some embodiments, the first node 101 can continue to interact with the third node 103 and / or the fourth node 104, and the fifth node 105, to complete the registration of the third node 103 and / or the fourth node 104.

[0245] Through steps S3101 to S3107, the communication method of the embodiments of the present disclosure can be implemented.

[0246] The communication method related to the embodiments of the present disclosure can include at least one of steps S3101 to S3107. For example, step S3104 can be implemented as an independent embodiment. For example, the combination of steps S3103 and S3104 can be implemented as an independent embodiment. For example, the combination of steps S3104 and S3105 can be implemented as an independent embodiment. For example, the combination of steps S3103, S3104 and S3105 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S3101 to S3107 are not limited to this.

[0247] In some embodiments, other optional implementations described before or after the description corresponding to FIG. 3A can be referred to.

[0248] FIG. 3B is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. The communication method related to the embodiments of the present disclosure can be applied to the communication system 100. As shown in FIG. 3B, the communication method of the embodiments of the present disclosure includes steps S3201 to S3212.

[0249] In step S3201, the third node 103 and / or the fourth node 104 sends a registration request message to the first node 101.

[0250] The optional implementation of step S3201 can refer to the optional implementation of step S3101 of FIG. 3A and other associated parts in the embodiments related to FIG. 3A, which will not be described here.

[0251] In step S3202, the first node 101 performs a registration procedure.

[0252] The optional implementation of step S3202 can refer to the optional implementation of step S3102 of FIG. 3A and other associated parts in the embodiments related to FIG. 3A, which will not be described here.

[0253] In step S3203, the first node 101 interacts with the fifth node 105.

[0254] In some embodiments, the first node 101 can interact with the fifth node 105 to obtain the policy information of the third node 103 and / or the fourth node 104.

[0255] In some embodiments, the fifth node 105 can comprise a PCF. In an example, the policy information can comprise AM policy control information. The first node 101 can obtain the AM policy control information of the third node 103 and / or the fourth node 104 through an AM policy association establishment procedure or an AM policy association modification procedure. For example, the first node 101 can select a PCF, and send an AM policy control establishment request message or an AM policy control update request message to the selected PCF. The PCF can send an AM policy control establishment response message or an AM policy control update response message to the first node 101, which comprises the AM policy control information determined by the PCF.

[0256] In some embodiments, the policy information can comprise address information of the second node 102. For example, the address information of the second node 102 can be contained in the AM policy control information.

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

[0258] The optional implementation of step S3204 can refer to the optional implementation of step S3104 in FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0259] In some embodiments, the categories of the first event are described with reference to Table 2 below.

[0260] Table 2: Categories of the first event

[0261] In some embodiments, the scenario in the embodiments shown in FIG. 3B can be ECUR. For example, the sending of the first message can be after the registration of the third node 103 and / or the fourth node 104 has been verified. For example, the first message can be sent for the registration of the third node 103 and / or the fourth node 104 to be authorized authentication.

[0262] In some embodiments, the first message in step S3204 can be a charging data request message (initial).

[0263] In step S3205, the second node 102 can perform a first operation.

[0264] The optional implementation of step S3205 can refer to the optional implementation of step S3105 in FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0265] In some embodiments, the first operation performed by the second node 102 can comprise opening a CDR.

[0266] In some embodiments, the second node 102 can perform account and rating control for the registration of the third node 103 and / or the fourth node 104 according to the first message to implement a charging function.

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

[0268] The optional implementation of step S3206 can refer to the optional implementation of step S3106 of FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0269] In some embodiments, in the case that the second message indicates acceptance of the charging request of the first message, the first node 101 can implement authorization authentication of the registration of the third node 103 and / or the fourth node 104.

[0270] In step S3207, the first node 101 continues to perform the registration procedure.

[0271] In some embodiments, the first node 101 can continue to interact with the third node 103 and / or the fourth node 104 and the fifth node 105 to confirm the acceptance of the registration of the third node 103 and / or the fourth node 104.

[0272] In step S3208, the first node 101 sends a registration acceptance message to the third node 103 and / or the fourth node 104.

[0273] In some embodiments, the third node 103 and / or the fourth node 104 can receive the registration acceptance message.

[0274] In some embodiments, the registration acceptance message can be used to inform the third node 103 and / or the fourth node 104 that the registration is accepted.

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

[0276] The optional implementation of step S3209 can refer to the optional implementation of step S3104 of FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0277] In some embodiments, the first message in step S3209 can be a charging data request message (termination).

[0278] In some embodiments, the first message can include charging data.

[0279] In some embodiments, the sending of the first message can be performed after the registration of the third node 103 and / or the fourth node 104 is successful. For example, the first message can be sent for the third node 103 and / or the fourth node 104 which is registered successfully.

[0280] In step S3210, the second node 102 can perform the first operation.

[0281] The optional implementation of step S3210 can refer to the optional implementation of step S3105 of FIG. 3A, and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0282] In some embodiments, the first operation performed by the second node 102 can include closing the CDR.

[0283] In some embodiments, the second node 102 can modify the CDR based on the charging data carried in the first message. After completing the modification of the CDR, the second node 102 can close the CDR.

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

[0285] The optional implementation of step S3211 can refer to the optional implementation of step S3106 of FIG. 3A, and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0286] In step S3212, the registration is completed.

[0287] In some embodiments, the first node 101 can interact with the third node 103 and / or the fourth node 104, and the fifth node 105, to complete the registration process of the third node 103 and / or the fourth node 104.

[0288] The communication method involved in the embodiments of the present disclosure can include at least one of steps S3201 to S3212. For example, step S3204 can be implemented as an independent embodiment. For example, step S3209 can be implemented as an independent embodiment. For example, the combination of steps S3204, S3205 can be implemented as an independent embodiment. For example, the combination of steps S3209, S3210 can be implemented as an independent embodiment. For example, the combination of steps S3204, S3209 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S3201 to S3212 are not limited to this.

[0289] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 3B.

[0290] FIG. 3C is an interaction diagram of a communication method according to an embodiment of the present disclosure. The communication method related by the embodiment of the present disclosure can be applied to the communication system 100. As shown in FIG. 3C, the communication method of the embodiment of the present disclosure includes steps S3301 to S3310.

[0291] In step S3301, the first node 101 obtains a service request message.

[0292] In some embodiments, the first node 101 can receive the service request message from the fifth node 105.

[0293] In some embodiments, the first node 101 can receive the service request message from the AF. In an example, the AF can be a massive communication AF used for requesting to implement a massive communication service.

[0294] In some embodiments, the service request information can be related to a first service. In an example, the first service can be an MC service.

[0295] In some embodiments, the service request information can be related to a first task of the first service.

[0296] In some embodiments, the first task can include at least one of the following: inventory, command. In some embodiments, the command can include at least one of the following: read, write, invalidate. It can be understood that the first task can also have other types, which are not limited in the embodiment of the present disclosure.

[0297] It should be noted that, before step S3301, the registration of the third node 103 and / or the fourth node 104 has been completed. In some embodiments, during the registration process of the third node 103 and / or the fourth node 104, the first node 101 can complete the determination of the second node 102.

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

[0299] The optional implementation of step S3302 can refer to the optional implementation of step S3104 of FIG. 3A and other associated parts in the embodiments related by FIG. 3A, which will not be described here.

[0300] In some embodiments, the first event can be related to the first service. In other words, the category of the first event can be a first service related event.

[0301] In some embodiments, the first event can be related to the first service. In other words, the category of the first event can be a first task related event.

[0302] In some embodiments, the categories of the first event are illustrated with reference to Table 3 below.

[0303] Table 3: Categories of the first event

[0304] In some embodiments, the scenario in the embodiment shown in FIG. 3B can be PEC or ECUR. For example, the sending of the first message can be performed after receiving a request for the first service or the first task.

[0305] In some embodiments, the first message in step S3302 can be a charging data request message (initial) or a charging data request message (event).

[0306] In step S3303, the second node 102 can perform a first operation.

[0307] Optional implementation of step S3303 can be referred to optional implementation of step S3105 of FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0308] In some embodiments, the first operation performed by the second node 102 can include opening a CDR.

[0309] In some embodiments, the second node 102 can perform accounting and rate control for the first service and / or the first task according to the first message to realize a charging function.

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

[0311] Optional implementation of step S3304 can be referred to optional implementation of step S3106 of FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0312] In some embodiments, in the case where the second message indicates acceptance of the charging request of the first message, the first node 101 can realize authorization of the first service and / or the first task.

[0313] In step S3305, the first node 101 continues to perform a service process.

[0314] In some embodiments, the first node 101 can interact with at least one of the third node 103, the fourth node 104, and the fifth node 105 to complete the process of the first service and / or the first task.

[0315] In some embodiments, the messages exchanged between the first node 101, the third node 103, the fourth node 104, the fifth node 105 can comprise at least one of: a service request message, an inventory request message and / or a response message, a command request message and / or a response message, environmental data of the third node 103 and / or the fourth node 104.

[0316] In step S3306, the first node 101 completes the service flow.

[0317] In some embodiments, the first node 101 can determine that the service flow of the first service and / or the first task is completed.

[0318] In some embodiments, the first node 101 can determine that the first service and / or the first task is successfully executed.

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

[0320] Optional implementation of step S3307 can refer to the optional implementation of step S3104 of FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0321] In some embodiments, the first message in step S3307 can be a billing data request message (terminate).

[0322] In some embodiments, the first message can comprise billing data.

[0323] In some embodiments, the first message can be sent for the first service and / or the first task. For example, the first message can be sent for the completed first service and / or the first task.

[0324] In step S3308, the second node 102 can perform a first operation.

[0325] Optional implementation of step S3308 can refer to the optional implementation of step S3210 of FIG. 3B and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

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

[0327] Optional implementation of step S3309 can refer to the optional implementation of step S3106 of FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0328] In step S3310, the first service and / or the first task is completed.

[0329] In some embodiments, the first node 101 can interact with the third node 103 and / or the fourth node 104, and the fifth node 105 to confirm the completion of the procedure of the first service and / or the first task.

[0330] The communication method related to the embodiments of the present disclosure can include at least one of steps S3301 to S3310. For example, step S3302 can be implemented as an independent embodiment. For example, step S3307 can be implemented as an independent embodiment. For example, a combination of steps S3302 and S3303 can be implemented as an independent embodiment. For example, a combination of steps S3307 and S3308 can be implemented as an independent embodiment. For example, a combination of steps S3302 and S3307 can be implemented as an independent embodiment. It should be noted that possible independent embodiments composed of one or more of steps S3301 to S3310 are not limited to this.

[0331] In some embodiments, other optional implementations described before or after the corresponding description of FIG. 3C can be referred to.

[0332] In some embodiments, the names of information and the like are not limited to the names described in the embodiments, and terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, “chip”, and the like can be replaced with each other.

[0333] In some embodiments, terms such as “uplink”, “physical uplink”, and the like can be replaced with each other, terms such as “downlink”, “physical downlink”, and the like can be replaced with each other, and terms such as “side”, “sidelink”, “sidelink communication”, “direct connection”, “direct link”, “direct communication”, and the like can be replaced with each other.

[0334] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based", and the like can be replaced with each other.

[0335] In some embodiments, the terms "moment", "time point", "time", "time position", and the like can be replaced with each other, and the terms "time length", "time period", "time window", "window", "time", and the like can be replaced with each other.

[0336] In some embodiments, the terms "acquire", "obtain", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive", and the like can be replaced with each other, and can be interpreted as receiving from other subjects, acquiring from protocols, obtaining from higher layers, obtaining by self-processing, autonomously implementing, and the like.

[0337] In some embodiments, the terms "send", "transmit", "report", "issue", "transmit", "bidirectional transmission", "send and / or receive", and the like can be replaced with each other.

[0338] In some embodiments, the terms "certain", "preset", "pre-set", "set", "indicated", "certain", "arbitrary", "first", and the like can be replaced with each other, and "certain A", "preset A", "pre-set A", "set A", "indicated A", "certain A", "arbitrary A", "first A" can be interpreted as A specified in advance in a protocol and the like, can be interpreted as A obtained by setting, configuring, or indicating, and the like, can be interpreted as certain A, certain A, arbitrary A, or first A, and the like, but are not limited thereto.

[0339] In some embodiments, determination or judgment can be performed by a value represented by 1 bit (0 or 1), can be performed by a true or false value (Boolean value) represented by true or false, can be performed by comparison of numerical values (for example, comparison with a predetermined value), but is not limited thereto.

[0340] In some embodiments, the terms "service" and "traffic" can be replaced with each other.

[0341] FIG. 4A is a flow diagram of a communication method according to embodiments of the present disclosure. Embodiments of the present disclosure relate to a communication method. The communication method is performed by a first node 101. As shown in FIG. 4A, the above method includes steps S4101 to S4106.

[0342] In step S4101, a registration request message is acquired.

[0343] Optional implementation of step S4101 can be referred to optional implementation of step S3101 in FIG. 3A and other associated parts in embodiments related to FIG. 3A, which will not be repeated here.

[0344] In some embodiments, the first node 101 can receive the registration request message sent by the third node 103 and / or the fourth node 104, but is not limited thereto, and can also receive the registration request message sent by other subjects.

[0345] In step S4102, a registration procedure is performed.

[0346] Optional implementation of step S4102 can be referred to optional implementation of step S3102 in FIG. 3A and other associated parts in embodiments related to FIG. 3A, which will not be repeated here.

[0347] In step S4103, a registration acceptance message is sent.

[0348] Optional implementation of step S4103 can be referred to optional implementation of step S3103 in FIG. 3A and other associated parts in embodiments related to FIG. 3A, which will not be repeated here.

[0349] In some embodiments, the first node 101 can send the registration acceptance message to the third node 103 and / or the fourth node 104, but is not limited thereto, and can also send the registration acceptance message to other subjects.

[0350] In step S4104, a first message is sent.

[0351] Optional implementation of step S4104 can be referred to optional implementation of step S3104 in FIG. 3A and other associated parts in embodiments related to FIG. 3A, which will not be repeated here.

[0352] In some embodiments, the first node 101 can send the first message to the second node 102, but is not limited thereto, and can also send the first message to other subjects.

[0353] In step S4105, a second message is acquired.

[0354] Optional implementation of step S4105 can be referred to optional implementation of step S3106 in FIG. 3A and other associated parts in embodiments related to FIG. 3A, which will not be repeated here.

[0355] In some embodiments, the first node 101 can receive the second message sent by the second node 102, but is not limited thereto, and can also receive the second message sent by other subjects.

[0356] In step S4106, the registration procedure is continued to be performed.

[0357] The optional implementation of step S4106 can refer to the optional implementation of step S3107 in FIG. 3A, and other associated parts in the embodiments involved in FIG. 3A, which are not described herein again.

[0358] The communication method involved in the embodiments of the present disclosure can include at least one of steps S4101 to S4106.

[0359] FIG. 4B is a flow diagram of a communication method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a communication method. The communication method is performed by the first node 101. As shown in FIG. 4B, the above method includes steps S4201 to S4210.

[0360] In step S4201, a registration request message is obtained.

[0361] The optional implementation of step S4201 can refer to the optional implementation of step S3201 in FIG. 3B, and other associated parts in the embodiments involved in FIG. 3B, which are not described herein again.

[0362] In some embodiments, the first node 101 can receive the registration request message sent by the third node 103 and / or the fourth node 104, but is not limited thereto, and can also receive the registration request message sent by other subjects.

[0363] In step S4202, a registration procedure is performed.

[0364] The optional implementation of step S4202 can refer to the optional implementation of step S3202 in FIG. 3B, and other associated parts in the embodiments involved in FIG. 3B, which are not described herein again.

[0365] In step S4203, the fifth node 105 is interacted with.

[0366] The optional implementation of step S4203 can refer to the optional implementation of step S3203 in FIG. 3B, and other associated parts in the embodiments involved in FIG. 3B, which are not described herein again.

[0367] In step S4204, a first message is sent.

[0368] The optional implementation of step S4204 can refer to the optional implementation of step S3204 in FIG. 3B, and other associated parts in the embodiments involved in FIG. 3B, which are not described herein again.

[0369] In some embodiments, the first node 101 can send the first message to the second node 102, but is not limited thereto, and can send the first message to other subjects.

[0370] In step S4205, the second message is acquired.

[0371] Optional implementation of step S4205 can be referred to optional implementation of step S3206 in FIG. 3B and other associated parts in embodiments involved in FIG. 3B, which will not be repeated here.

[0372] In some embodiments, the first node 101 can receive the second message sent by the second node 102, but is not limited thereto, and can receive the second message sent by other subjects.

[0373] In step S4206, the registration procedure is continued.

[0374] Optional implementation of step S4206 can be referred to optional implementation of step S3207 in FIG. 3B and other associated parts in embodiments involved in FIG. 3B, which will not be repeated here.

[0375] In step S4207, the registration accept message is sent.

[0376] Optional implementation of step S4207 can be referred to optional implementation of step S3208 in FIG. 3B and other associated parts in embodiments involved in FIG. 3B, which will not be repeated here.

[0377] In some embodiments, the first node 101 can send the registration accept message to the third node 103 and / or the fourth node 104, but is not limited thereto, and can send the registration accept message to other subjects.

[0378] In step S4208, the first message is sent.

[0379] Optional implementation of step S4208 can be referred to optional implementation of step S3209 in FIG. 3B and other associated parts in embodiments involved in FIG. 3B, which will not be repeated here.

[0380] In some embodiments, the first node 101 can send the first message to the second node 102, but is not limited thereto, and can send the first message to other subjects.

[0381] In step S4209, the second message is acquired.

[0382] Optional implementation of step S4209 can be referred to optional implementation of step S3211 in FIG. 3B and other associated parts in embodiments involved in FIG. 3B, which will not be repeated here.

[0383] In some embodiments, the first node 101 can receive the second message sent by the second node 102, but is not limited thereto, and can also receive the second message sent by other subjects.

[0384] In step S4210, the registration is completed.

[0385] The optional implementation of step S4210 can refer to the optional implementation of step S3212 in FIG. 3B and other associated parts in the embodiments involved in FIG. 3B, which will not be repeated here.

[0386] The communication method involved in the embodiments of the present disclosure can include at least one of steps S4201 to S4210.

[0387] FIG. 4C is a flow diagram of a communication method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a communication method. The communication method is performed by the first node 101. As shown in FIG. 4C, the above method includes steps S4301 to S4308.

[0388] In step S4301, a service request message is obtained.

[0389] The optional implementation of step S4301 can refer to the optional implementation of step S3301 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0390] In step S4302, a first message is sent.

[0391] The optional implementation of step S4302 can refer to the optional implementation of step S3302 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0392] In some embodiments, the first node 101 can send the first message to the second node 102, but is not limited thereto, and can also send the first message to other subjects.

[0393] In step S4303, a second message is obtained.

[0394] The optional implementation of step S4303 can refer to the optional implementation of step S3304 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0395] In some embodiments, the first node 101 can receive the second message sent by the second node 102, but is not limited thereto, and can also receive the second message sent by other subjects.

[0396] In step S4304, the service flow is continued.

[0397] The optional implementation of step S4304 can refer to the optional implementation of step S3305 in FIG. 3C and other associated parts in the embodiments related to FIG. 3C, which will not be repeated here.

[0398] In step S4305, the service flow is completed.

[0399] The optional implementation of step S4305 can refer to the optional implementation of step S3306 in FIG. 3C and other associated parts in the embodiments related to FIG. 3C, which will not be repeated here.

[0400] In step S4306, the first message is sent.

[0401] The optional implementation of step S4306 can refer to the optional implementation of step S3307 in FIG. 3C and other associated parts in the embodiments related to FIG. 3C, which will not be repeated here.

[0402] In some embodiments, the first node 101 can send the first message to the second node 102, but is not limited thereto, and can send the first message to other subjects.

[0403] In step S4307, the second message is obtained.

[0404] The optional implementation of step S4307 can refer to the optional implementation of step S3309 in FIG. 3C and other associated parts in the embodiments related to FIG. 3C, which will not be repeated here.

[0405] In some embodiments, the first node 101 can receive the second message sent by the second node 102, but is not limited thereto, and can receive the second message sent by other subjects.

[0406] In step S4308, the first service and / or the first task are completed.

[0407] The optional implementation of step S4308 can refer to the optional implementation of step S3310 in FIG. 3C and other associated parts in the embodiments related to FIG. 3C, which will not be repeated here.

[0408] The communication method related to the embodiments of the present disclosure can include at least one of steps S4301 to S4308.

[0409] FIG. 5 is a flow diagram of a communication method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method. The communication method is performed by the second node 102. As shown in FIG. 5, the above method includes steps S501 to S503.

[0410] In step S501, a first message is obtained.

[0411] The optional implementation of step S501 can refer to the optional implementation of steps S3104 in FIG. 3A, S3204, S3209 in FIG. 3B, S3302, S3307 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3A, FIG. 3B, and FIG. 3C, which are not described here again.

[0412] In some embodiments, the second node 102 can receive the first message sent by the first node 101, but is not limited thereto, and can also receive the first message sent by other subjects.

[0413] In step S502, a first operation is performed.

[0414] The optional implementation of step S502 can refer to the optional implementation of steps S3105 in FIG. 3A, S3205, S3210 in FIG. 3B, S3303, S3308 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3A, FIG. 3B, and FIG. 3C, which are not described here again.

[0415] In some embodiments, the first operation can be performed based on the first message.

[0416] In step S503, a second message is sent.

[0417] The optional implementation of step S503 can refer to the optional implementation of steps S3105 in FIG. 3A, S3205, S3210 in FIG. 3B, S3303, S3308 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3A, FIG. 3B, and FIG. 3C, which are not described here again.

[0418] In some embodiments, the second node 102 can send the second message to the first node 101, but is not limited thereto, and can also send the second message to other subjects.

[0419] The communication method related to the embodiments of the present disclosure can include at least one of steps S501 to S503.

[0420] FIG. 6 is a flow diagram of a communication method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a communication method. As shown in FIG. 6, the above method includes step S601.

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

[0422] The optional implementation of step S601 can refer to the optional implementation of steps S3104 in FIG. 3A, steps S3204 and S3209 in FIG. 3B, steps S3302 and S3307 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3A, FIG. 3B and FIG. 3C, which are not described herein again.

[0423] The method steps on the side of the first node 101 and the second node 102 in the foregoing embodiments are involved.

[0424] In the following, the technical solutions of the embodiments of the present disclosure are exemplarily described through specific implementation manners.

[0425] In some embodiments, large-scale communication services need support of large-scale communication charging event collection and reporting, so as to effectively meet the charging needs of the services.

[0426] In some embodiments, the MCF or AIoTF (i.e., the first node) supports charging information collection. The charging information can be counted or monitored according to at least one of the following: for each AF (identified by an AF ID); for each service (identified by a service ID); for each rate group and / or charging key value (using an independent charging key value); for each payer (identified by a payer ID and an ASP ID); for each MC device (identified by a device ID).

[0427] In some embodiments, the charging information collected by the MCF or AIoTF can include at least one of the following: a reader (e.g., a reader of an AIoT service); a device (e.g., a device of an AIoT service); a service area (e.g., a service for one campus); a task (e.g., a one-time inventory task, which can be identified by a task ID).

[0428] In some embodiments, the MCF or AIoTF selects a CHF address for charging reporting. The CHF address selection can be implemented in the process of registering the device (i.e., the fourth node) / the reader (i.e., the third node) to the network, or in the process of receiving a service request from the AF. The address selection can consider the following selections:

[0429] - the CHF address used for the service context / task context transferred from the source MCF or AIoTF;

[0430] - the CHF address provided by the PCF as part of the access and mobility policy control information;

[0431] - the CHF address provided by the UDM as a charging feature;

[0432] - the CHF address provided by the NRF in the discovery process;

[0433] - CHF address provided by AMF, e.g. AMF serving the UE reader, AMF with the same or similar business area as MCF or AIoT F;

[0434] - Charging characteristics provided locally by MCF or AIoT F.

[0435] In some embodiments, in case multiple choices are provided, the priority order between these choices can be determined according to operator policy and / or local configuration.

[0436] In some embodiments, the selected CHF address can be used for the collection and reporting of charging events / data. Charging events / data are related to AF, service, payer, rate group / charging key value, and take into account registered readers, devices, business area, task, etc.

[0437] In some embodiments, MCF or AIoT F can interact with CHF (i.e. second node).

[0438] In some embodiments, CHF can subscribe to a list of presence reporting areas for reporting by MCF or AIoT F whether the presence of devices / readers in the presence reporting area has changed.

[0439] In some embodiments, the presence reporting areas of MCF or AIoT F include:

[0440] - Dedicated presence reporting area defined by CHF, identified by PRA identifier and elements of the presence reporting area (e.g. list of readers (including UE readers and MC-RAN readers), list of service identities, task ID, AF ID, payer ID, list of TAs, list of MC-RAN nodes, list of cell identities);

[0441] - Presence reporting area pre-configured by operator / network, identified by PRA identifier.

[0442] In some embodiments, MC service charging can be implemented by MCF or AIoT F interacting with CHF. Charging data can include:

[0443] - Charging data related to registration (e.g. device registration, reader registration);

[0444] - Charging data related to reader connection between UE / MC-RAN and MCF or AIoT F for MC service;

[0445] - Charging data related to device location or reader location;

[0446] - Charging data related to MC service (e.g., service request, inventory and command request / response, environment data of device / reader);

[0447] - Charging data related to task of MC service (e.g., task session request and response of service).

[0448] In some embodiments, the MCF or AIoTF charging configuration can be used to determine the applicable trigger conditions for each function (e.g., registration of reader or device, connection of MCF or AIoTF, MC service, task of MC service, location reporting), and can include the status of each function (e.g., charging active or inactive, charging scenarios (including IEC, ECUR, PEC, etc. scenarios)).

[0449] In some embodiments, the MCF or AIoTF can support multiple trigger conditions and categories (chargeable events).

[0450] In some embodiments, the charging data request can be sent to the CHF under certain conditions (chargeable events). In the case of charging data being sent to the CHF, the charging data can include identifiers such as device ID, reader ID, task ID, service ID, AF ID, and payer ID.

[0451] In some embodiments, the charging trigger conditions (chargeable events) can be determined by the relevant behavior in the case of obtaining the charging trigger conditions and related behaviors. The trigger conditions and categories supported by the MCF or AIoTF are shown in Table 4 below:

[0452] Table 4: Trigger conditions and categories supported by MCF or AIoTF

[0453] In some embodiments, the MCF or AIoTF implements converged charging by interacting with the CHF. The charging data targeted by the converged charging can be related to at least one of the following: registration of reader or device, connection of MCF or AIoTF, MC service, task of MC service, and location reporting management.

[0454] In the embodiments of the present disclosure, part or all of the steps, and optional implementation manners thereof, can be combined with part or all of the steps in other embodiments, or can be combined with optional implementation manners of other embodiments.

[0455] The embodiments of the present disclosure further provide a communication apparatus for implementing any of the above methods. For example, the embodiments of the present disclosure provide a communication apparatus comprising units or modules for implementing the steps performed by the first node in any of the above methods. For example, the embodiments of the present disclosure provide a communication apparatus comprising units or modules for implementing the steps performed by the second node in any of the above methods. For example, the embodiments of the present disclosure provide a communication apparatus comprising units or modules for implementing the steps performed by the third node in any of the above methods.

[0456] It should be understood that the division of units or modules in the above apparatus is only a logical functional division, and all or part of them can be integrated into one physical entity or physically separated. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor connected with a memory, the memory stores instructions, and 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 of the apparatus, wherein the processor is, for example, a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be implemented by the design of the hardware circuit, and the hardware circuit can be understood as one or more processors; for example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are implemented by the design of the logical relationship between the elements in the circuit; for another example, in another implementation, the hardware circuit is a programmable logic device (PLD), and taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to implement the functions of part or all of the units or modules. All units or modules of the above apparatus can be implemented in the form of processor calling software, or all units or modules can be implemented in the form of hardware circuit, or part of the units or modules are implemented in the form of processor calling software, and the remaining part is implemented in the form of hardware circuit.

[0457] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), and the like. In another implementation, the processor can implement certain functions through a logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by a dedicated integrated circuit or a programmable logic device, such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the hardware circuit configuration. It can be understood that the processor loads instructions to implement the functions of the above part or all units or modules. In addition, 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), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0458] FIG. 7 is a structural schematic diagram of a communication apparatus provided by the embodiments of the present disclosure. As shown in FIG. 7, the communication apparatus 700 can include at least one of the following: a transceiver module 701, a processing module 702.

[0459] In some embodiments, the communication apparatus 700 can be the first node 101. In some embodiments, the processing module 702 is configured to determine that a first event related to charging is triggered. Optionally, the processing module 702 can be configured to perform at least one of other steps (for example, steps S3102, S3107, S3202, S3207, S3212, S3301, S3305, S3306, S3310, but not limited to this) in any one of the above methods other than the communication steps (for example, sending and / or receiving) performed by the first node 101, which will not be repeated here. In some embodiments, the transceiver module 701 is configured to send a first message to the second node, wherein the first message is used to implement charging for the first service. Optionally, the transceiver module 701 can be configured to perform at least one of the communication steps (for example, steps S3101, S3102, S3103, S3104, S3106, S3107, S3201, S3202, S3203, S3204, S3206, S3207, S3208, S3209, S3211, S3212, S3302, S3304, S3305, S3307, S3309, S3310, but not limited to this) in any one of the above methods performed by the first node 101, which will not be repeated here.

[0460] In some embodiments, the communication apparatus 700 can be the second node 102. In some embodiments, the transceiver module 701 is configured to receive the first message sent by the first node, wherein the first message is used to implement charging for the first service. Optionally, the transceiver module 701 can be configured to perform at least one of the communication steps (for example, steps S3104, S3106, S3204, S3206, S3209, S3211, S3302, S3304, S3307, S3309, but not limited to this) in any one of the above methods performed by the second node 102, which will not be repeated here. In some embodiments, the processing module 702 is configured to perform a first operation related to charging for the first service according to the first message. Optionally, the processing module 702 can be configured to perform at least one of other steps (for example, steps S3105, S3205, S3210, S3303, S3308, but not limited to this) in any one of the above methods other than the communication steps (for example, sending and / or receiving) performed by the second node 102, which will not be repeated here.

[0461] In some embodiments, the communication apparatuses shown in FIG. 7 can also be implemented in a physical manner, for example, a communication device.

[0462] In some embodiments, the transceiving module can include a transmitting module and / or a receiving module. The transmitting module and the receiving module can be separate or integrated together. Alternatively, the transceiving module can be mutually replaced with a transceiver.

[0463] In some embodiments, the processing module can be one module or include multiple sub-modules. Alternatively, the multiple sub-modules perform all or part of the steps required to be performed by the processing module respectively. Alternatively, the processing module can be mutually replaced with a processor.

[0464] FIG. 8A is a structural schematic diagram of a communication device according to embodiments of the present disclosure. The communication device 8100 can be an MC device, a terminal (e.g., a user equipment, etc.), a network device (e.g., a core network device, an access network device, etc.), a chip, a chip system, or a processor supporting the MC device to implement any of the above methods, a chip, a chip system, or a processor supporting the terminal to implement any of the above methods, or a chip, a chip system, or a processor supporting the network device to implement any of the above methods. The communication device 8100 can be used to implement the methods described in the above method embodiments, and details can be referred to the descriptions in the above method embodiments.

[0465] As shown in FIG. 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a special-purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process data of the programs. Alternatively, the communication device 8100 is configured to perform any of the above methods. Alternatively, the one or more processors 8101 are configured to invoke instructions to cause the communication device 8100 to perform any of the above methods.

[0466] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps (e.g., steps S3101, S3102, S3103, S3104, S3106, S3107, S3201, S3202, S3203, S3204, S3206, S3207, S3208, S3209, S3211, S3212, S3302, S3304, S3305, S3307, S3309, S3310, but not limited to) of transmitting and / or receiving in the above-described methods, and the processor 8101 performs at least one of the other steps (e.g., steps S3102, S3105, S3107, S3202, S3205, S3207, S3210, S3212, S3301, S3303, S3305, S3306, S3308, S3310, but not limited to). In optional embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Optionally, the terms transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced with each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced with each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced with each other.

[0467] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Optionally, all or part of the memory 8103 can also be outside the communication device 8100. In optional embodiments, the communication device 8100 can include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected with the memory 8103, and the interface circuit 8104 can be used to receive data from the memory 8103 or other devices, and can be used to send data to the memory 8103 or other devices. For example, the interface circuit 8104 can read the data stored in the memory 8103 and send the data to the processor 8101.

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

[0469] FIG. 8B is a structural schematic diagram of a chip according to an embodiment of the present disclosure. For the case where the communication device 8100 can be a chip or a chip system, the structural schematic diagram of a chip 8200 shown in FIG. 8B can be referred to, but is not limited thereto.

[0470] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to perform any of the above methods.

[0471] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the terms interface circuit, interface, transceiver pin, and the like can be replaced with each other. In some embodiments, the chip 8200 further includes one or more memories 8203 for storing data. Optionally, all or part of the memory 8203 can be outside the chip 8200. Optionally, the interface circuit 8202 is connected to the memory 8203, and the interface circuit 8202 can be configured to receive data from the memory 8203 or other devices, and the interface circuit 8202 can be configured to send data to the memory 8203 or other devices. For example, the interface circuit 8202 can read data stored in the memory 8203 and send the data to the processor 8201.

[0472] In some embodiments, the interface circuit 8202 performs at least one of the communication steps (for example, steps S3101, S3102, S3103, S3104, S3106, S3107, S3201, S3202, S3203, S3204, S3206, S3207, S3208, S3209, S3211, S3212, S3302, S3304, S3305, S3307, S3309, S3310, but not limited to) of transmitting and / or receiving and the like in the above method. The interface circuit 8202 performing the communication steps such as transmitting and / or receiving in the above method means that the interface circuit 8202 performs data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps (for example, steps S3102, S3105, S3107, S3202, S3205, S3207, S3210, S3212, S3301, S3303, S3305, S3306, S3308, S3310, but not limited to).

[0473] The modules and / or devices described in each of the embodiments of the virtual device, the physical device, the chip, and the like can be combined or separated as the case may be. Alternatively, part or all of the steps can also be executed by a plurality of modules and / or devices in cooperation, which is not limited here.

[0474] The embodiments of the present disclosure further propose a storage medium, and the storage medium stores instructions, which, when executed on the communication device 8100, cause the communication device 8100 to perform any of the above methods. Alternatively, the storage medium is an electronic storage medium. Alternatively, the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices. Alternatively, the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a transitory storage medium.

[0475] The embodiments of the present disclosure further propose a program product, and the program product, when executed by the communication device 8100, causes the communication device 8100 to perform any of the above methods. Alternatively, the program product is a computer program product.

[0476] The embodiments of the present disclosure further propose a computer program, which, when executed on a computer, causes the computer to perform any of the above methods.

[0477] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the application being indicated by the following claims.

[0478] It is to be understood that the application is not limited to the precise construction hereinafter described and as shown in the attached drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is limited only by the claims that follow.

Claims

1. A communication method performed by a first node, wherein, The method comprises: determining that a first event related to charging is triggered; sending a first message to a second node, wherein the first message is used to implement charging for a first service.

2. The method of claim 1, wherein, The first message comprises at least one of: charging indication information, used to trigger the second node to perform a charging operation; event indication information, used to indicate the first event; charging data, comprising charging data collected for the first service.

3. The method of claim 2, wherein, The charging data comprises at least one of: charging data related to registration; charging data related to connection; charging data related to location; charging data related to the first service; charging data related to a first task of the first service.

4. The method of claim 2 or 3, wherein, The charging data is obtained according to charging information, wherein the charging information comprises at least one of: identification information of a third node; identification information of a fourth node; identification information of a service area of the first service; identification information of a first task of the first service.

5. The method of claim 4, wherein, The charging information is related to at least one of: an application function, a reader-writer, a large-scale communication device, a rate group, a charging key value, a payment party.

6. The method of any one of claims 1 to 5, wherein, The first message is sent according to address information of the second node; wherein the address information of the second node is obtained by at least one of the following ways: determined according to received context information; provided by a policy control function (PCF); provided by a unified data management (UDM) function; provided by a network storage function (NRF); provided by an access and mobility management function (AMF); determined according to local configuration.

7. The method of claim 6, wherein, The priority order between the multiple ways of determining the address information can be determined according to at least one of: operator policy, local configuration.

8. The method of any one of claims 1 to 7, wherein, The first message is related to a first area of the first service; wherein the first area is obtained by at least one of the following ways: determined by the second node, preconfigured.

9. The method of any one of claims 1 to 8, wherein, The first event is related to at least one of: connection of the first node; registration of a third node; registration of a fourth node; the first service; a first task of the first service; location reporting.

10. The method of any one of claims 1 to 9, wherein, The first node is deployed with a charging configuration, which is used to determine at least one of: the first event, a charging state.

11. The method of claim 10, wherein, The charging configuration is related to at least one of: an application function, a reader-writer, a large-scale communication device, a rate group, a charging key value, a payment party.

12. A communication method performed by a second node, wherein, The method comprises: receiving a first message sent by a first node, wherein the first message is used to implement charging for a first service; performing a first operation related to charging of the first service according to the first message.

13. The method of claim 12, wherein, The first message comprises at least one of: charging indication information, used to trigger the second node to perform a charging operation; event indication information, used to indicate the first event; charging data, comprising charging data collected for the first service.

14. The method of claim 13, wherein, The charging data comprises at least one of: charging data related to registration; charging data related to connection; charging data related to location; charging data related to the first service; charging data related to a first task of the first service.

15. The method of claim 13 or 14, wherein, The charging data is obtained according to charging information, and the charging information includes at least one of the following: identification information of the third node; identification information of the fourth node; identification information of a service area of the first service; identification information of a first task of the first service.

16. The method of claim 15, wherein, The charging information is related to at least one of the following: application function, reader, large-scale communication device, rate group, charging key value, and payment party.

17. The method of any one of claims 12 to 16, wherein, The first operation includes at least one of the following: creating a charging data record (CDR); opening the CDR; closing the CDR.

18. The method of any one of claims 12 to 17, wherein, The first message is related to a first area of the first service; wherein the first area is obtained by at least one of the following: determined by the second node, preconfigured.

19. The method of any one of claims 12 to 18, wherein, The first event is related to at least one of the following: connection of the first node; registration of a third node; registration of a fourth node; the first service; a first task of the first service; location reporting.

20. A communication device arranged at a first node, wherein The apparatus includes: a processing module configured to determine that a first event related to charging is triggered; a transceiver module configured to send a first message to a second node, wherein the first message is used to implement charging for a first service.

21. A communications device arranged at a second node, wherein The apparatus includes: a transceiver module configured to receive a first message sent by a first node, wherein the first message is used to implement charging for a first service; a processing module configured to perform a first operation related to charging of the first service according to the first message.

22. A communication device comprising: one or more processors; a memory storing instructions; wherein the instructions, when executed on the communication device, cause the communication device to implement the communication method of any one of claims 1-11, 12-19.

23. A storage medium storing instructions, wherein, The instructions, when executed on the communication device, cause the communication device to implement the communication method of any one of claims 1-11, 12-19.

24. A computer program product comprising instructions, wherein, The instructions, when executed on the communication device, cause the communication device to implement the communication method of any one of claims 1-11, 12-19.

Images