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

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium, and a program product. The method is performed by a first node and comprises: obtaining first information, wherein the first information is used for monitoring a first event in a wireless charging service associated with a first device, and the first device is a massive Internet of Things device. Through the present disclosure, the quality of service of the wireless charging service for the massive Internet of Things device can be improved.

Description

Technical Field

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

[0002] As people's lives and work become increasingly intelligent, more and more large-scale Internet of Things (IoT) devices will be deployed. Thanks to the deployment of these large-scale IoT devices, large-scale communication services will be possible. Summary of the Invention

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

[0004] According to a first aspect of the present disclosure, a communication method is provided. The communication method is performed by a first node. The communication method includes: acquiring first information, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

[0005] According to a second aspect of the present disclosure, a communication method is provided. This communication method is performed by a third node. The communication method includes: sending first information to a first node, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

[0006] According to a third aspect of the present disclosure, a communication method is provided. The communication method is performed by a communication system. The communication system includes a first node and a third node. The communication method includes: the third node sending first information to the first node, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

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

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

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

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

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

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

[0013] According to embodiments of this disclosure, the service quality of wireless charging services for large-scale Internet of Things (IoT) devices can be improved.

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

[0015] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

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

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

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

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

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

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

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

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

[0024] Figure 5 This is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0025] Figure 6A This is an interactive schematic diagram of an exemplary implementation of the communication method provided in the embodiments of this disclosure.

[0026] Figure 6B This is an interactive schematic diagram of an exemplary implementation of the communication method provided in the embodiments of this disclosure.

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

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

[0029] Figure 8B This is a schematic diagram of the chip structure provided according to an embodiment of this disclosure. Detailed Implementation

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

[0031] In a first aspect, embodiments of this disclosure provide a communication method. This communication method is performed by a first node. The communication method includes: acquiring first information, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

[0032] In this embodiment, the first node can acquire first information, which is used to monitor first events related to the wireless charging service associated with a large number of IoT devices. This enables the subscription and notification of relevant events for the wireless charging service associated with a large number of IoT devices, improving the performance of the communication system for the wireless charging service of large-scale IoT devices.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the first information indicates a first event.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the first event includes at least one of the following: an event related to the wireless charging state of the first device; an event related to the operation of the wireless charging service; an event related to the activation of wireless charging; and an event related to the wireless charging service.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, events related to the wireless charging state of the first device include at least one of the following: the power level of the first device meets a first condition; a periodic timer times out.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, events related to the operation of the wireless charging service include at least one of the following: the time during which the service operation is unreachable exceeds a threshold; the number of times the service operation is unreachable exceeds a threshold; an indication message indicating the success of the service operation is obtained; an indication message indicating the failure of the service operation is obtained; a timer for the service operation times out; or no response to the service operation is received within the time window for the service operation.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, events related to the activation of wireless charging include at least one of the following: the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; wherein the second node is used to wirelessly charge the first device.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, events related to the wireless charging service include at least one of the following: obtaining indication information indicating the start of a service operation of the wireless charging service; obtaining indication information indicating the stop of a service operation of the wireless charging service; a timer timeout for triggering wireless charging; a timer timeout for the wireless charging service; and the battery level of the first device meeting a second condition.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the operation of obtaining the first information includes at least one of the following: receiving the first information sent by the third node; obtaining the first information from the local machine.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes: sending second information to a third node, wherein the second information indicates the result of monitoring for the first event.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the result of monitoring the first event includes at least one of the following: the battery level of the first device; the wireless charging service is unreachable; the wireless charging service fails; the wireless charging service succeeds; the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; the wireless charging service starts; the wireless charging service stops; wherein the second node is used to wirelessly charge the first device.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the third node includes at least one of the following: AF; charging safety controller; MCIoTF.

[0043] In some embodiments of the first aspect, the first node is different from the second node; wherein the above method further includes: sending first information to the second node; receiving second information sent by the second node, wherein the second information indicates the result of monitoring for the first event.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the second node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0046] In a second aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a third node. The communication method includes: sending first information to a first node, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

[0047] In this embodiment, the third node can provide first information to the first node, which is used to monitor first events related to the wireless charging service associated with a large number of IoT devices. This enables the subscription and notification of relevant events for the wireless charging service associated with a large number of IoT devices, improving the performance of the communication system for the wireless charging service of large-scale IoT devices.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the first information indicates a first event.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the first event includes at least one of the following: an event related to the wireless charging state of the first device; an event related to the operation of the wireless charging service; an event related to the activation of wireless charging; and an event related to the wireless charging service.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, events related to the wireless charging state of the first device include at least one of the following: the power level of the first device meets a first condition; a periodic timer times out.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, events related to the operation of the wireless charging service include at least one of the following: the time during which the service operation is unreachable exceeds a threshold; the number of times the service operation is unreachable exceeds a threshold; an indication message indicating the success of the service operation is obtained; an indication message indicating the failure of the service operation is obtained; a timer for the service operation times out; or no response to the service operation is received within the time window for the service operation.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, events related to the activation of wireless charging include at least one of the following: the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; wherein the second node is used to wirelessly charge the first device.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, events related to the wireless charging service include at least one of the following: obtaining indication information indicating the start of a service operation of the wireless charging service; obtaining indication information indicating the stop of a service operation of the wireless charging service; a timer timeout for triggering wireless charging; a timer timeout for the wireless charging service; and the battery level of the first device meeting a second condition.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes: receiving second information sent by the first node, wherein the second information indicates the result of monitoring for the first event.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the result of monitoring the first event includes at least one of the following: the battery level of the first device; the wireless charging service is unreachable; the wireless charging service fails; the wireless charging service succeeds; the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; the wireless charging service starts; the wireless charging service stops; wherein the second node is used to wirelessly charge the first device.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the second node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the first node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the third node includes at least one of the following: AF; wireless charging safety controller; MCIoTF.

[0059] In a third aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a communication system. The communication system includes a first node and a third node. The communication method includes: the third node sending first information to the first node, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

[0060] In a fourth aspect, embodiments of this disclosure provide a communication device. The communication device is a first node. The communication device includes a transceiver module. The transceiver module is configured to: acquire first information, wherein the first information is used to monitor a first event in a wireless charging service associated with the first device, and the first device is a large-scale Internet of Things (IoT) device.

[0061] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information indicates a first event.

[0062] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first event includes at least one of the following: an event related to the wireless charging state of the first device; an event related to the operation of the wireless charging service; an event related to the activation of wireless charging; and an event related to the wireless charging service.

[0063] In conjunction with some embodiments of the fourth aspect, in some embodiments, events related to the wireless charging state of the first device include at least one of the following: the battery level of the first device meets a first condition; a periodic timer times out.

[0064] In conjunction with some embodiments of the fourth aspect, in some embodiments, events related to the operation of the wireless charging service include at least one of the following: the time during which the service operation is unreachable exceeds a threshold; the number of times the service operation is unreachable exceeds a threshold; an indication message indicating the success of the service operation is obtained; an indication message indicating the failure of the service operation is obtained; a timer for the service operation times out; or no response to the service operation is received within the time window for the service operation.

[0065] In conjunction with some embodiments of the fourth aspect, in some embodiments, events related to the activation of wireless charging include at least one of the following: the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; wherein the second node is used to wirelessly charge the first device.

[0066] In conjunction with some embodiments of the fourth aspect, in some embodiments, events related to the wireless charging service include at least one of the following: obtaining indication information indicating the start of a service operation of the wireless charging service; obtaining indication information indicating the stop of a service operation of the wireless charging service; a timer timeout for triggering wireless charging; a timer timeout for the wireless charging service; and the battery level of the first device meeting a second condition.

[0067] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is configured to perform at least one of the following: receiving first information sent by a third node; or obtaining first information from a local source.

[0068] In some embodiments, in conjunction with the fourth aspect, the above method further includes: sending second information to a third node, wherein the second information indicates the result of monitoring for the first event.

[0069] In conjunction with some embodiments of the fourth aspect, in some embodiments, the result of monitoring the first event includes at least one of the following: the battery level of the first device; the wireless charging service is unreachable; the wireless charging service fails; the wireless charging service succeeds; the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; the wireless charging service starts; the wireless charging service stops; wherein the second node is used to wirelessly charge the first device.

[0070] In conjunction with some embodiments of the fourth aspect, in some embodiments, the third node includes at least one of the following: AF; charging safety controller; MCIoTF.

[0071] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first node is different from the second node; wherein the transceiver module is further configured to: send first information to the second node; and receive second information sent by the second node, wherein the second information indicates the result of monitoring for the first event.

[0072] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0073] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0074] In a fifth aspect, embodiments of this disclosure provide a communication device. The communication device is a third node. The communication device includes a transceiver module. The transceiver module is configured to send first information to a first node, wherein the first information is used to monitor a first event in a wireless charging service associated with the first device, and the first device is a large-scale Internet of Things (IoT) device.

[0075] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information indicates a first event.

[0076] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first event includes at least one of the following: an event related to the wireless charging state of the first device; an event related to the operation of the wireless charging service; an event related to the activation of wireless charging; and an event related to the wireless charging service.

[0077] In conjunction with some embodiments of the fifth aspect, in some embodiments, events related to the wireless charging state of the first device include at least one of the following: the power level of the first device meets a first condition; a periodic timer times out.

[0078] In conjunction with some embodiments of the fifth aspect, in some embodiments, events related to the operation of the wireless charging service include at least one of the following: the time during which the service operation is unreachable exceeds a threshold; the number of times the service operation is unreachable exceeds a threshold; an indication message indicating the success of the service operation is obtained; an indication message indicating the failure of the service operation is obtained; a timer for the service operation times out; or no response to the service operation is received within the time window for the service operation.

[0079] In conjunction with some embodiments of the fifth aspect, in some embodiments, events related to the activation of wireless charging include at least one of the following: the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; wherein the second node is used to wirelessly charge the first device.

[0080] In conjunction with some embodiments of the fifth aspect, in some embodiments, events related to the wireless charging service include at least one of the following: obtaining indication information indicating the start of a service operation of the wireless charging service; obtaining indication information indicating the stop of a service operation of the wireless charging service; a timer timeout for triggering wireless charging; a timer timeout for the wireless charging service; and the battery level of the first device meeting a second condition.

[0081] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further configured to: receive second information sent by the first node, wherein the second information indicates the result of monitoring for the first event.

[0082] In conjunction with some embodiments of the fifth aspect, in some embodiments, the result of monitoring the first event includes at least one of the following: the battery level of the first device; the wireless charging service is unreachable; the wireless charging service fails; the wireless charging service succeeds; the wireless charging capability of the first device is activated; the wireless charging capability of the first device is deactivated; the wireless charging capability of the second node is activated; the wireless charging capability of the second node is deactivated; the wireless charging service starts; the wireless charging service stops; wherein the second node is used to wirelessly charge the first device.

[0083] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0084] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first node includes at least one of the following: a terminal device; an access network device; or an MCIoTF.

[0085] In conjunction with some embodiments of the fifth aspect, in some embodiments, the third node includes at least one of the following: AF; wireless charging safety controller; MCIoTF.

[0086] In a sixth aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first to second aspects and their possible implementations.

[0087] In a seventh aspect, embodiments of this disclosure provide a communication system. The communication system includes at least one of the following: a first node configured to perform the communication method as described in any of the first aspect and its possible embodiments; and a third node configured to perform the communication method as described in any of the second aspect and its possible embodiments.

[0088] In an eighth aspect, embodiments of this disclosure provide a storage medium storing instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first to third aspects and their possible implementations.

[0089] In a ninth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the communication method as described in any of the first to third aspects and their possible implementations.

[0090] In a tenth aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first to third aspects and their possible implementations.

[0091] In an eleventh aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first to third aspects and their possible implementations.

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

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

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

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

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

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

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

[0099] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

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

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

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

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

[0104] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

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

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

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

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

[0109] 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 subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

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

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

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

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

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

[0115] Figure 1 This is a schematic diagram of the architecture of a communication system provided according to embodiments of this disclosure. Figure 1 As shown, the communication system 100 includes a first network element 101, a second network element 102, a third network element 103, a fourth network element 104, a fifth network element 105, a sixth network element 106, and a first device 107.

[0116] In some embodiments, the first network element 101 may be a consumer of the MC service. In some embodiments, the first network element 101 may be a node requesting the implementation of the MC service.

[0117] In some embodiments, the first network element 101 may be a network function deployed by the application provider.

[0118] In some embodiments, the first network element 101 may be, for example, an application function (AF).

[0119] In some embodiments, the first network element 101 may be, for example, an application service provider (ASP).

[0120] In some embodiments, the first network element 101 may be, for example, a massive communication application function (MCAF).

[0121] In some embodiments, the first network element 101 may be a data network (DN).

[0122] In some embodiments, the second network element 102 may be responsible for providing an access interface for external application functions to the communication network, thereby exposing and managing functions such as network events, parameter configuration, quality of service (QoS) policies, location information, and data analysis.

[0123] In some embodiments, the second network element 102 may be, for example, a network exposure function (NEF).

[0124] In some embodiments, the third network element 103 may be responsible for subscription data management, authentication services, event subscription and notification, context management of large-scale IoT devices, network slicing management, etc.

[0125] In some embodiments, the third network element 103 may be, for example, a large-scale communication IoT data management function (MC IoT data management, MCIoTDM).

[0126] In some embodiments, the fourth network element 104 can be responsible for the management, control, and billing triggering of MC services.

[0127] In some embodiments, the fourth network element 104 may be, for example, a massive communication function (MCF), a massive communication management function (MCMF), or a massive communication IoT function (MCIoTF).

[0128] In some embodiments, the fourth network element 104 may be, for example, an ambient IoT (AIoT) function (AIoTF) or an AIoT management function (AIoTMF).

[0129] In some embodiments, the fifth network element 105 may be responsible for managing the UE's access and mobility, etc.

[0130] In some embodiments, the fifth network element 105 may be, for example, an access and mobility management function (AMF).

[0131] In some embodiments, the sixth network element 106 can support wireless charging for a large number of IoT devices.

[0132] In some embodiments, the sixth network element 106 may be, for example, a terminal device.

[0133] In some embodiments, the sixth network element 106 may be, for example, an access network device.

[0134] In some embodiments, the sixth network element 106 may be, for example, an MCF, an MCMF, or an MCIoTF.

[0135] In some embodiments, the sixth network element 106 may be, for example, AIoTF or AIoTMF.

[0136] In some embodiments, the first device 107 may be, for example, an Internet of Things (IoT) device. In some embodiments, the first device 107 may be, for example, a large-scale IoT device. For example, the first device 107 may be a 5G IoT device, a 6G IoT device, etc. In some embodiments, the first device 107 may be an MCIoT device. For example, the first device 107 may be a 5G MCIoT device, a 6G MCIoT device, etc. In some embodiments, the MC service may include an AIoT service, for example, a 5G AIoT service, a 6G AIoT service. For example, the first device 107 may be an AIoT device.

[0137] In some embodiments, the first device 107 can be charged and / or powered by received electromagnetic waves.

[0138] In some embodiments, one or more of the first network element 101, the second network element 102, the third network element 103, the fourth network element 104, the fifth network element, and the sixth network element 106 may be core network elements. In some embodiments, the first network element 101 may be a third-party server located outside the core network. In some embodiments, the sixth network element 106 may be a core network element, an access network device, or a terminal device.

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

[0140] In some embodiments, the technical solutions of this disclosure can be applied to Open Radio Access Network (Open RAN) architectures. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0141] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

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

[0143] The following embodiments of this disclosure can be applied to Figure 1The communication system 100 shown, or a part of the main body of the communication system 100, but not limited thereto. Figure 1 The entities shown are illustrative; the communication system 100 may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

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

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

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

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

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

[0149] In some embodiments, multiple connection topologies exist for AIoT devices. In some embodiments, a first connection topology (or Topology 1, first type of topology) may be: base station <—> AIoT device. In some embodiments, the AIoT device can directly communicate bidirectionally with the base station. Communication between the base station and the AIoT device may include AIoT service-related data and / or signaling. In some embodiments, a second connection topology (or Topology 2, second type of topology) may be: base station <—> intermediate node <—> AIoT device. In some embodiments, user equipment (UE) can be used as an intermediate node under network control. In some embodiments, the AIoT device can communicate bidirectionally with an intermediate node located between the AIoT device and the base station. The intermediate node can forward information between the base station and the AIoT device. In some embodiments, a third connection topology (or Topology 3, third type of topology) may 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 some embodiments, the fourth link topology (or Topology 4, fourth type of topology) can be: UE <—> AIoT device. In some embodiments, the AIoT device can communicate bidirectionally with the UE. In some embodiments, the communication between the AIoT device and the UE can include AIoT service data and / or signaling. In different connection topologies, the reader can be implemented by different types of devices. For example, the reader can be a base station, an intermediate node, a UE, etc.

[0150] In some embodiments, in accordance with the requirements of AIoT, the one-way end-to-end latency can be, for example, 1 second or even 10 seconds, and the reliability of the communication service can be, for example, 99% or even 99.9%.

[0151] In some embodiments, massive communication (MC) is a development direction of 6G technology. In massive communication services, the number and types of IoT devices participating in the communication will increase significantly. It is understood that MC services may also have other names, and this disclosure does not specifically limit them.

[0152] In some embodiments, MC services often involve a large number of IoT devices, which consume energy in the process of implementing specific business operations or tasks of MC services.

[0153] Therefore, how to enable communication systems to support wireless charging for large-scale IoT devices is a technical problem that urgently needs to be solved.

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

[0155] In step S2101, the first network element 101 sends a request message to the second network element 102.

[0156] In some embodiments, the first network element 101 can send a request message. In some embodiments, the request message can be sent by the first network element 101, but is not limited to this; it can also be sent by other entities.

[0157] In some embodiments, the second network element 102 can receive request messages. In some embodiments, the request message can be received by the second network element 102, but is not limited thereto, and can also be received by other entities.

[0158] In some embodiments, the request message sent by the first network element 101 may include first information. In some embodiments, step S2101 may include: the first network element 101 sending the first information to the second network element 102.

[0159] In some embodiments, the first information may instruct monitoring of the wireless charging service. In some embodiments, the first information may instruct monitoring of a first event of the wireless charging service. In some embodiments, the first information may be used to monitor a first event in the wireless charging service associated with the first device 107. In some embodiments, the first information may be used to subscribe to notifications regarding a first event of the wireless charging service. In some embodiments, the first information may be used to request reporting of a first event of the wireless charging service. In some embodiments, the first information may be used to request obtaining monitoring results of a first event of the wireless charging service for the first device 107.

[0160] In some embodiments, the first information may indicate a first event. In some embodiments, the first information may indicate the first event for which monitoring and reporting of the wireless charging service of the first device 107 is targeted.

[0161] In some embodiments, the first event may be associated with at least one of the following: the wireless charging state of the first device 107, the operation of the wireless charging service, the activation of wireless charging, and the wireless charging service. In some embodiments, the first event may include at least one of the following: an event related to the wireless charging state of the first device 107, an event related to the operation of the wireless charging service, an event related to the activation of wireless charging, and an event related to the wireless charging service.

[0162] In some embodiments, the first event may be related to the wireless charging state of the first device 107. In some embodiments, the first event related to the wireless charging state of the first device 107 may include at least one of the following: the battery level of the first device 107 meets a first condition, or a periodic timer times out.

[0163] In some embodiments, the first event may include the battery level of the first device 107 meeting a first condition. In other words, the first event can be triggered when the battery level of the first device 107 meets the first condition.

[0164] In some embodiments, the first condition may be a threshold value for the battery level of the first device 107. When the battery level of the first device 107 reaches the threshold value, a first event may be triggered.

[0165] In some embodiments, the power level of the first device 107 can be indicated by at least one of the following methods: power value, power percentage, power level.

[0166] In some embodiments, the first condition may include a threshold value for the battery level of the first device 107. For example, the first condition may be 50 mA, i.e., the threshold is 50 mA. Then, when the battery level of the first device 107 reaches or exceeds 50 mA, the first event can be triggered.

[0167] In some embodiments, the first condition may include a threshold for the percentage of battery power of the first device 107. For example, the first condition may be 80% of the total battery power of the first device 107, i.e., the threshold is 80%. Then, when the battery power of the first device 107 reaches or exceeds 80% of the total battery power, the first event may be triggered.

[0168] In some embodiments, the first condition may include a threshold value for the battery level of the first device 107. For example, the first condition may be that the battery level of the first device 107 has reached a specific battery level, i.e., the threshold value is that specific battery level. Then, when the battery level of the first device 107 reaches or exceeds the specific battery threshold value, a first event may be triggered. In some embodiments, the specific battery level may be high battery level, full battery level, etc.

[0169] In some embodiments, monitoring of the wireless charging status of the first device 107 can be performed periodically. For example, the battery level of the first device 107 can be monitored at fixed time intervals. In some embodiments, the first event can be a periodic timer timeout. The periodic timer can be used to implement periodic monitoring of the wireless charging status of the first device 107, and the timing duration of the periodic timer can be equal to the monitoring period of the wireless charging status. In some embodiments, the monitoring of the wireless charging status of the first device 107 can be implemented periodically by cyclically timing the periodic timer. In some embodiments, the first event can be triggered whenever the periodic timer times out. After the first event is triggered, the periodic timer can be reset to restart the timing.

[0170] In some embodiments, the first event may be related to the operation of the wireless charging service. In some embodiments, the event related to the operation of the wireless charging service may include at least one of the following: the time during which the operation is unreachable exceeds a threshold, the number of times the operation is unreachable exceeds a threshold, an indication message indicating the success of the operation is obtained, an indication message indicating the failure of the operation is obtained, a timer for the operation expires, or there is no response to the operation within the time window for the operation.

[0171] In some embodiments, the first event may include the duration of service unavailability exceeding a threshold. In some embodiments, the service operation for the wireless charging service of the first device 107 may be unavailable, and the duration of service unavailability may exceed a threshold. In this case, the first event may be triggered. In some embodiments, a timer may be set for the unavailability of the service operation. The duration of the timer may be set to the unavailability duration threshold. In some embodiments, the first event may be triggered when the timer expires.

[0172] In some embodiments, the first event may include the number of times a service operation is unavailable exceeding a threshold. In some embodiments, a service operation for the wireless charging service of the first device 107 may be unavailable, and the number of times the service operation is unavailable may exceed a threshold. In this case, the first event may be triggered. For example, the first event may be triggered if the number of consecutive times a service operation for the wireless charging service of the first device 107 is unavailable exceeds a threshold.

[0173] In some embodiments, the first event may include receiving indication information indicating successful operation of the service. In some embodiments, the indication information may indicate successful operation of the wireless charging service, and the first event may include receiving the indication information. In some embodiments, the first event may be triggered upon receiving indication information indicating successful operation of the wireless charging service.

[0174] In some embodiments, the first event may include receiving indication information indicating a service operation failure. In some embodiments, the indication information may indicate a service operation failure of the wireless charging service, and the first event may include receiving the indication information. In some embodiments, the first event may be triggered upon receiving indication information indicating a service operation failure of the wireless charging service.

[0175] In some embodiments, the first event may include a timer timeout for a service operation. In some embodiments, a timer may be set for a service operation of the wireless charging service. When the timer times out, the service operation may be considered to have failed (or not succeeded), and the first event may be triggered.

[0176] In some embodiments, the first event may include the absence of a response to a service operation within a time window of the wireless charging service's operation. In some embodiments, this time window may be used to monitor the service operations of the wireless charging service. Therefore, if no response is received for the service operation within the time window, the service operation may be considered to have failed (or unsuccessfully) and may be released. In some embodiments, the first event may be triggered if there is no response to the service operation within the time window of the wireless charging service's operation.

[0177] In some embodiments, the first event may be related to the activation of wireless charging. In some embodiments, the event related to the activation of wireless charging may include at least one of the following: the wireless charging capability of the first device 107 is activated, the wireless charging capability of the first device 107 is deactivated, the wireless charging capability of the sixth network element 106 is activated, and the wireless charging capability of the sixth network element 106 is deactivated.

[0178] In some embodiments, a first event may be triggered when the wireless charging capability of the first device 107 is activated. In some embodiments, a first event may be triggered when the wireless charging capability of the first device 107 is deactivated. In some embodiments, the wireless charging capability of the first device 107 may refer to the ability of the first device 107 to receive radio waves in the environment and perform charging.

[0179] In some embodiments, the wireless charging capability of the first device 107 can be activated or deactivated depending on the contract area of ​​the first device 107. For example, if the first device 107 is located in or enters the contract area, the wireless charging capability of the first device 107 can be activated. For example, if the first device 107 is located outside or leaves the contract area, the wireless charging capability of the first device 107 can be deactivated.

[0180] In some embodiments, the wireless charging capability of the first device 107 can be activated or deactivated according to the wireless charging time window of the first device 107. In some embodiments, the wireless charging capability of the first device 107 can be activated within the time window. For example, the wireless charging capability of the first device 107 can be activated when the start time of the time window arrives. In some embodiments, the wireless charging capability of the first device 107 can be deactivated outside the time window. For example, the wireless charging capability of the first device 107 can be deactivated when the end time of the time window arrives.

[0181] In some embodiments, the first event can be triggered when the wireless charging capability of the sixth network element 106 is activated. In some embodiments, the first event can be triggered when the wireless charging capability of the sixth network element 106 is deactivated. In some embodiments, the wireless charging capability of the sixth network element 106 may refer to the ability of the sixth network element 106 to wirelessly charge the first device 107.

[0182] In some embodiments, the wireless charging capability of the sixth network element 106 can be activated or deactivated depending on the contracted area of ​​the sixth network element 106. For example, if the sixth network element 106 is located within or enters the contracted area, its wireless charging capability can be activated. Conversely, if the sixth network element 106 is located outside or leaves the contracted area, its wireless charging capability can be deactivated.

[0183] In some embodiments, the wireless charging capability of the sixth network element 106 can be activated or deactivated according to the wireless charging time window of the sixth network element 106. In some embodiments, the wireless charging capability of the sixth network element 106 can be activated within the time window. For example, the wireless charging capability of the sixth network element 106 can be activated when the start time of the time window arrives. In some embodiments, the wireless charging capability of the sixth network element 106 can be deactivated outside the time window. For example, the wireless charging capability of the sixth network element 106 can be deactivated when the end time of the time window arrives.

[0184] In some embodiments, the first event may be related to a wireless charging service. In some embodiments, the event related to the wireless charging service may include at least one of the following: obtaining indication information indicating the start of a service operation of the wireless charging service; obtaining indication information indicating the stop of a service operation of the wireless charging service; a timer timeout for triggering wireless charging; a timer timeout for the wireless charging service; and the battery level of the first device meeting a second condition.

[0185] In some embodiments, the first event may include acquiring indication information indicating the commencement of service operations for the wireless charging service. In some embodiments, the indication information may indicate the commencement of service operations for the wireless charging service, and the first event may include receiving the indication information. In some embodiments, the first event may be triggered upon receiving indication information indicating the commencement of service operations for the wireless charging service.

[0186] In some embodiments, the first event may include obtaining indication information that instructs the wireless charging service to cease operation. In some embodiments, the indication information may instruct the wireless charging service to cease operation, and the first event may include receiving the indication information. In some embodiments, the first event may be triggered upon receiving the indication information instructing the wireless charging service to cease operation.

[0187] In some embodiments, the first event may include a timer timeout for triggering wireless charging. In some embodiments, a timer may be set for wireless charging. When the timer times out, the wireless charging service may begin. In some embodiments, the first event may be triggered upon the timer timeout.

[0188] In some embodiments, the first event may include a timer timeout for the wireless charging service. In some embodiments, a timer may be set for the wireless charging service. When the timer times out, the wireless charging service may stop. In some embodiments, the first event may be triggered upon the timer timeout.

[0189] It is understood that the duration of the timer used for the wireless charging service can be equal to the window length of the wireless charging time window. In some embodiments, the duration of the timer's timing is the wireless charging time window. When the timer expires, the end time of the time window arrives. At this point, the wireless charging service operation stops, and the first event can be triggered.

[0190] In some embodiments, the first event may include the battery level of the first device 107 meeting a second condition. In other words, the first event may be triggered when the battery level of the first device 107 meets the second condition.

[0191] In some embodiments, the second condition may be a threshold value for the battery level of the first device 107. When the battery level of the first device 107 reaches the threshold value, the wireless charging service for the first device 107 may be stopped, and a first event may be triggered. For example, the second condition may be 100% of the total battery level of the first device 107. Then, when the battery level of the first device 107 reaches 100% of its total battery level, the first event may be triggered.

[0192] In some embodiments, the first information may also indicate parameters related to the first event. In some embodiments, the first event indicated by the first information may include the battery level of the first device 107 meeting a first condition, and the parameters indicated by the first information may include a threshold value in the first condition. In some embodiments, the first event indicated by the first information may include a periodic timer timeout, and the parameters indicated by the first information may include the duration of the periodic timer. In some embodiments, the first event indicated by the first information may include a service operation being unreachable for a period exceeding a threshold, and the parameters indicated by the first information may include a threshold value for the unreachable time. In some embodiments, the first event indicated by the first information may include a service operation being unreachable for a number of times exceeding a threshold, and the parameters indicated by the first information may include a threshold value for the number of unreachable times. In some embodiments, the first event indicated by the first information may include a timer timeout for a service operation, and the parameters indicated by the first information may include the duration of the timer. In some embodiments, the first event indicated by the first information may include no response to a service operation within a time window for the service operation, and the parameters indicated by the first information may include at least one of the start time, end time, and duration of the time window. In some embodiments, the first event indicated by the first information may include a timer timeout for triggering wireless charging, and the parameters indicated by the first information may include the duration of the timer. In some embodiments, the first event indicated by the first information may include a timer timeout for the wireless charging service, and the parameters indicated by the first information may include the duration of the timer. In some embodiments, the first event indicated by the first information may include the battery level of the first device 107 meeting a second condition, and the parameters indicated by the first information may include a threshold value in the second condition.

[0193] In some embodiments, the request message sent by the first network element 101 may further include fifth information. In some embodiments, step S2101 may include: the first network element 101 sending the fifth information to the second network element 102. The fifth information may be used to request wireless power charging (WPC) for the first device 107. In some embodiments, the fifth information may be used to request the execution of a wireless charging service for the first device 107.

[0194] In some embodiments, the fifth information may include at least one of the following: wireless charging indication information, information of the first device 107, identification information of the first network element 101, and wireless charging parameter information.

[0195] In some embodiments, the wireless charging indication information may indicate a wireless charging request. In some embodiments, the wireless charging indication information may indicate that the first network element 101 requests to perform a wireless charging service. In some embodiments, the wireless charging indication information may indicate that the request message carrying fifth information is a request message for wireless charging.

[0196] In some embodiments, wireless charging indication information may be carried in a field, which may include one or more bits. In some embodiments, a first value of the field may indicate wireless charging, and a second value of the field may not indicate wireless charging. For example, the field may have one bit. In this case, the first value may be 1 and the second value may be 0; or, the first value may be 0 and the second value may be 1. In some embodiments, the presence of the field may indicate wireless charging, and the absence of the field may not indicate wireless charging. For example, if the fifth information includes a field carrying wireless charging indication information, then the fifth information is used to request wireless charging for the first device; otherwise, the fifth information is not used to request wireless charging for the first device.

[0197] In some embodiments, the information of the first device 107 may be information related to the first device 107 required to perform a wireless charging service for the first device 107.

[0198] In some embodiments, the information of the first device 107 may include at least one of the following: identification information of the first device 107 and location information of the first device 107. It is understood that the information of the first device 107 may also include other information related to the first device 107, and this disclosure does not specifically limit this.

[0199] In some embodiments, the identification information of the first network element 101 can be used to identify the first network element 101. For example, if the first network element 101 is an AF, then the identification information of the first network element 101 can be the AF ID.

[0200] In some embodiments, the parameter information for wireless charging may indicate the relevant parameters of the wireless charging service performed on the first device 107.

[0201] In some embodiments, the parameters indicated by the wireless charging parameter information may include at least one of the following: charging time, charging power, and charging target. It is understood that the parameter information may also indicate other parameters related to the wireless charging service, and this disclosure does not specifically limit these parameters.

[0202] In some embodiments, the wireless charging parameter information may indicate at least one of the following regarding the charging time: the start time of wireless charging, the end time of wireless charging, and the duration of wireless charging.

[0203] In some embodiments, the wireless charging parameter information may indicate at least one of the following regarding charging power: the maximum power of wireless charging and the minimum power of wireless charging.

[0204] In some embodiments, the wireless charging parameter information may indicate the target amount of power to be wirelessly charged to the first device 107, with respect to the charging target.

[0205] In some embodiments, when the first network element 101 determines that it needs to wirelessly charge the first device 107, the first network element 101 may send a request message. In some embodiments, the first network element 101 may periodically send request messages to request wireless charging for the first device 107. For example, the charging cycle for the first device 107 may be one week, one month, one year, etc., and the first network element 101 may send request messages according to this cycle. In some embodiments, the first network element 101 may non-periodically send request messages to request wireless charging for the first device 107. For example, the first network element 101 may obtain the battery status of the first device 107 and send a request message when the battery status is insufficient. For example, the first network element 101 may predict the battery status of the first device 107 and send a request message when it is predicted that the battery status is below a preset threshold.

[0206] In some embodiments, the second network element 102 may be a NEF. In some embodiments, the request message sent by the first network element 101 to the second network element 102 may be an Nnef_6GMCIoT_WPC request message.

[0207] In step S2102, the second network element 102 determines the fourth network element 104.

[0208] In some embodiments, upon receiving the fifth information, the second network element 102 may determine the fourth network element 104. In some embodiments, the operation of the second network element 102 determining the fourth network element 104 may include: the second network element 102 selecting the fourth network element 104 based on the fifth information and / or local configuration.

[0209] In some embodiments, the local configuration of the second network element 102 may include at least one of the following: protocol agreement, operator configuration, and operation administration and maintenance (OAM) configuration.

[0210] In some embodiments, if a fourth network element 104 for the fifth information does not exist, the second network element 102 may reject the request message from the fourth network element 104. For example, if no fourth network element 104 is deployed in the core network, the second network element 102 may determine that no fourth network element 104 for the fifth information exists. For example, if all fourth network elements 104 deployed in the core network are unsuitable for implementing the wireless charging service requested by the fifth information, the second network element 102 may determine that no fourth network element 104 for the fifth information exists.

[0211] In step S2103, the second network element 102 sends a request message to the fourth network element 104.

[0212] In some embodiments, the second network element 102 can send a request message. In some embodiments, the request message can be sent by the second network element 102, but is not limited to this; it can also be sent by other entities.

[0213] In some embodiments, the fourth network element 104 can receive request messages. In some embodiments, the request message can be received by the fourth network element 104, but is not limited to this, and can also be received by other entities.

[0214] In some embodiments, the request message sent by the second network element 102 may include first information. In some embodiments, step S2103 may include: the second network element 102 sending the first information to the fourth network element 104.

[0215] In some embodiments, the request message sent by the second network element 102 may further include fifth information. In some embodiments, step S2103 may include: the second network element 102 sending the fifth information to the fourth network element 104.

[0216] In some embodiments, the second network element 102 may send a request message to the determined fourth network element 104. In some embodiments, the request message sent by the second network element 102 may be the same as the request message received by the second network element 102 from the first network element 101. In some embodiments, the request message sent by the second network element 102 may be different from the request message received by the second network element 102 from the first network element 101.

[0217] In some embodiments, the fourth network element 104 may be an MCIoTF. In some embodiments, the request message sent by the second network element 102 may be an Nmciotf_6GMCIoT_WPC request message.

[0218] In some embodiments, the first network element 101 may be an untrusted network function. In this case, by executing steps S2101 to S2103, the fifth message sent by the first network element 101 can reach the fourth network element 104 via the second network element 102.

[0219] In some embodiments, the first network element 101 may be a trusted network function. In this case, step S2102 may not be performed. Through steps S2101 and S2103, the fifth information sent by the first network element 101 can directly reach the fourth network element 104.

[0220] In step S2104, the fourth network element 104 performs authorization.

[0221] In some embodiments, upon receiving a request message from the second network element 102, the fourth network element 104 may perform authorization in response to the request message.

[0222] In some embodiments, step S2104 may include: verifying the first information and / or the fifth information in the received request message.

[0223] In some embodiments, the verification of the first information and / or the fifth information by the fourth network element 104 can be implemented as follows: the fourth network element 104 interacts with the third network element 103 to verify the first information and / or the fifth information. In some embodiments, the fourth network element 104 can send the first information and / or the fifth information to the third network element 103; then, the third network element 103 can verify the first information and / or the fifth information and send the verification result to the fourth network element 104. In some embodiments, the fourth network element 104 can send the first information and / or the fifth information to the third network element 103; then, the third network element 103 can send the information required to verify the first information and / or the fifth information to the fourth network element 104; the fourth network element 104 can verify the first information and / or the fifth information based on the obtained information to obtain the verification result.

[0224] In some embodiments, the verification of the first information and / or the fifth information by the fourth network element 104 can be implemented as follows: the fourth network element 104 verifies the first information and / or the fifth information according to the locally configured and / or locally stored information required to verify the first information and / or the fifth information, so as to obtain the verification result.

[0225] In some embodiments, the verification of the first information and / or the fifth information by the fourth network element 104 can be implemented as follows: the fourth network element 104 interacts with the third network element 103 and verifies the first information and / or the fifth information based on its local configuration. In some embodiments, the fourth network element 104 can send the first information and / or the fifth information to the third network element 103; then, the third network element 103 can send the information required to verify the first information and / or the fifth information to the fourth network element 104; the fourth network element 104 can verify the first information and / or the fifth information based on the acquired information and its local configuration to obtain the verification result.

[0226] In some embodiments, the result of the test may include whether the test was successful or failed.

[0227] In some embodiments, if the verification is successful, the fourth network element 104 may authorize the monitoring of the wireless charging service of the first device 107 requested by the first information request. If the verification fails, the fourth network element 104 may not authorize the monitoring of the wireless charging service of the first device 107 requested by the first information request.

[0228] In some embodiments, if the verification is successful, the fourth network element 104 may authorize the wireless charging service requested by the fifth information request to the first device 107. If the verification fails, the fourth network element 104 may not authorize the wireless charging service requested by the fifth information request to the first device 107.

[0229] In step S2105, the fourth network element 104 sends a response message to the second network element 102.

[0230] In some embodiments, the fourth network element 104 can send a response message. In some embodiments, the response message can be sent by the fourth network element 104, but is not limited to this; it can also be sent by other entities.

[0231] In some embodiments, the second network element 102 can receive a response message. In some embodiments, the response message can be received by the second network element 102, but is not limited thereto, and can also be received by other entities.

[0232] In some embodiments, the response message sent by the fourth network element 104 may be a response message to the request message in step S2103. For example, the response message sent by the fourth network element 104 may be an Nmciotf_6GMCIoT_WPC response message.

[0233] In some embodiments, the response message sent by the fourth network element 104 may indicate whether to accept the request in the request message regarding wireless charging of the first device 107. In one example, the response message may indicate acceptance of the request to wirelessly charge the first device 107. For example, if the fourth network element 104 successfully verifies the first information and / or the fifth information, and the wireless charging service for the first device 107 is authorized, the response message may indicate acceptance of the request to wirelessly charge the first device 107. In one example, the response message may indicate rejection of the request to wirelessly charge the first device 107. For example, if the fourth network element 104 fails to verify the first information and / or the fifth information, and / or the wireless charging service for the first device 107 is not authorized, the response message may indicate rejection of the request to wirelessly charge the first device 107.

[0234] In some embodiments, if a request to wirelessly charge the first device 107 is refused, the response message may also indicate the reason for the refusal. In some embodiments, the response message may include a reason code. The reason code may be used to identify the reason for the refusal.

[0235] In step S2106, the second network element 102 sends a response message to the first network element 101.

[0236] In some embodiments, the second network element 102 can send a response message. In some embodiments, the response message can be sent by the second network element 102, but is not limited to this, and can also be sent by other entities.

[0237] In some embodiments, the first network element 101 can receive a response message. In some embodiments, the response message can be received by the first network element 101, but is not limited thereto, and can also be received by other entities.

[0238] In some embodiments, upon receiving a response message from a fourth network element 104, the second network element 102 may send a response message to the first network element 101. In some embodiments, the response message sent by the second network element 102 may be a response message to the request message in step S2101. For example, the response message sent by the second network element 102 may be an Nnef_6GMCIoT_WPC response message.

[0239] In some embodiments, the response message sent by the second network element 102 may indicate at least one of the following: whether to accept the request in the request message regarding wireless charging of the first device 107, and the reason for rejection.

[0240] In step S2107, the fourth network element 104 triggers the sixth network element 106 to perform wireless charging.

[0241] In some embodiments, if the wireless charging service requested by the fifth information request for the first device 107 is authorized, the fourth network element 104 can trigger the sixth network element 106 to perform wireless charging. In other words, the fourth network element 104 can trigger the sixth network element 106 to implement the wireless charging service for the first device 107.

[0242] In some embodiments, step S2107 may include: determining a sixth network element 106 for wirelessly charging the first device 107.

[0243] In some embodiments, the operation of the fourth network element 104 determining the sixth network element 106 can be implemented as follows: the fourth network element 104 sends a request message to the sixth network element 106 and receives a response message or an acknowledgment message sent by the sixth network element 106. For example, if the response message indicates that the sixth network element 106 is reachable, the sixth network element 106 that sends the response message can be selected. For example, if a response message or an acknowledgment message is received, the sixth network element 106 that sends the acknowledgment message can be selected.

[0244] In some embodiments, the operation of the fourth network element 104 determining the sixth network element 106 can be implemented as follows: the fourth network element 104 sends a request message to the first device 107 through the sixth network element 106, and receives a response message or an acknowledgment message through the sixth network element 106. For example, if the response message indicates that the first device 107 is reachable, the sixth network element 106 used to receive the response message can be selected. For example, if a response message or an acknowledgment message is received, the sixth network element 106 used to receive the response message can be selected.

[0245] In some embodiments, the operation of the fourth network element 104 determining the sixth network element 106 can be implemented as follows: the fourth network element 104 determines the sixth network element 106 based on the subscribed status information of the sixth network element 106. In some embodiments, the fourth network element 104 may subscribe to status information from one or more sixth network elements 106. The fourth network element 104 can select the sixth network element 106 based on the obtained status information of these sixth network elements 106. In some embodiments, the subscribed status information may include at least one of the following: whether the sixth network element 106's wireless charging function is active, whether the sixth network element 106 has subscribed to wireless charging, the time window in which the sixth network element 106 supports wireless charging, and the area in which the sixth network element 106 supports wireless charging. It is understood that the status information subscribed to for each sixth network element 106 may also include other information, which is not specifically limited in this embodiment.

[0246] In some embodiments, the operation of the fourth network element 104 determining the sixth network element 106 can be implemented as follows: the fourth network element 104 sends a check-alive message to the sixth network element 106 and selects the sixth network element 106 that has received the reply message.

[0247] In some embodiments, the operation of the fourth network element 104 determining the sixth network element 106 can be implemented as follows: the fourth network element 104 sends a check-alive message to the first device 107 through the sixth network element 106, and selects the sixth network element 106 that has received the reply message.

[0248] It should be noted that the above methods of determining the sixth network element 106 based on request messages, determining the sixth network element 106 based on subscription status information, and determining the sixth network element 106 based on check-alive messages can be combined arbitrarily, and this disclosure does not impose specific limitations on this.

[0249] In some embodiments, the determination of the sixth network element 106 by the fourth network element 104 can also be achieved using a network repository function (NRF). In some embodiments, the wireless charging capability of the sixth network element 106 can be registered to the NRF, so the NRF can store the wireless charging capability of the sixth network element 106. For example, the sixth network element 106 can register a configuration file containing its own wireless charging capability to the NRF by sending an Nnrf_NFManagement_NFRegister request or an Nnrf_NFManagement_NFUpdate request. In this way, the fourth network element 104 can select the sixth network element 106 with wireless charging capability by interacting with the NRF. In some embodiments, the fourth network element 104 can discover the sixth network element 106 with wireless charging capability by sending an Nnrf_NFDiscovery_Request request to the NRF. In some embodiments, the NRF can return one or more sixth network elements 106 with wireless charging capability to the fourth network element 104. For example, the NRF can return a configuration file of one or more sixth network elements 106 with wireless charging capability to the fourth network element 104. In some embodiments, the fourth network element 104 can select the sixth network element 106 based on the configuration file from the NRF.

[0250] In some embodiments, step S2107 may further include: activating the wireless charging function of the sixth network element 106. In some embodiments, in order for the determined sixth network element 106 to wirelessly charge the first device 107, the fourth network element 104 may activate the wireless charging function of the sixth network element 106. In some embodiments, the wireless charging function of the sixth network element 106 determined by the fourth network element 104 may be inactive, or the fourth network element 104 may not be certain whether the wireless charging function of the sixth network element 106 is active. In this case, the fourth network element 104 may activate the wireless charging function of the sixth network element 106. In some embodiments, the fourth network element 104 may interact with the sixth network element 106 to activate the wireless charging function of the sixth network element 106. For example, the fourth network element 104 may send an activation message to the sixth network element 106 to activate the wireless charging function of the sixth network element 106.

[0251] It is understandable that the fourth network element 104 may not perform the operation of activating the sixth network element 106 to perform wireless charging. In some embodiments, the fourth network element 104 has already determined that the wireless charging function of the selected sixth network element 106 is active during the process of determining the sixth network element 106. In this case, the operation of activating the wireless charging function of the sixth network element 106 may not be performed. In some embodiments, the fourth network element 104 may implicitly activate the wireless charging function of the sixth network element 106 through the request message sent in step S2108. In the latter case, activating the wireless charging function of the sixth network element 106 can be achieved through step S2108.

[0252] In step S2108, the fourth network element 104 sends a request message to the sixth network element 106.

[0253] In some embodiments, the fourth network element 104 can send a request message. In some embodiments, the request message can be sent by the fourth network element 104, but is not limited to this; it can also be sent by other entities.

[0254] In some embodiments, the sixth network element 106 can receive request messages. In some embodiments, the request message can be received by the sixth network element 106, but is not limited thereto, and can also be received by other entities.

[0255] In some embodiments, the request message may be sent by the fourth network element 104 to the selected sixth network element 106.

[0256] In some embodiments, the request message may include at least one of the following: first information and sixth information.

[0257] In some embodiments, the request message may include first information. In some embodiments, step S2108 may include: the fourth network element 104 sending the first information to the sixth network element 106. It is understood that in some embodiments, the request message may not include the first information.

[0258] In some embodiments, the request message may include sixth information. In some embodiments, step S2108 may include: the fourth network element 104 sending the sixth information to the sixth network element 106.

[0259] In some embodiments, the sixth information can be used to initiate wireless charging of the first device 107 by the sixth network element 106. In some embodiments, the sixth information can be used by the sixth network element 106 to perform wireless charging of the first device 107. In some embodiments, the sixth information can instruct the sixth network element 106 to perform wireless charging of the first device 107.

[0260] In some embodiments, the sixth information may include at least one of the following: wireless charging indication information, identification information of the sixth network element 106, information of the first device 107, and wireless charging parameter information.

[0261] In some embodiments, the fourth network element 104 can directly send a request message to the sixth network element 106. In one example, the fourth network element 104 can be an MCIoTF, and the sixth network element 106 can be a local MCIoTF. In this case, the fourth network element 104 and the sixth network element 106 can constitute a multi-level MCIoTF architecture. The MCIoTF can directly send a request message to the local MCIoTF. In one example, the fourth network element 104 can be an MCIoTF, and the sixth network element 106 can be another MCIoTF. In this case, the MCIoTF can directly send a request message to another MCIoTF. In one example, the fourth network element 104 can be an MCIoTF, and the sixth network element 106 can be a terminal device or an access network device. In this case, the MCIoTF can directly send a request message to the terminal device or the access network device.

[0262] In some embodiments, the fourth network element 104 can send a request message to the sixth network element 106 through the fifth network element 105. In one example, the fourth network element 104 can be an MCIoTF, and the sixth network element 106 can be a terminal device or an access network device. In this case, the MCIoTF can send a request message to the terminal device or access network device through the fifth network element 105. For example, the fifth network element 105 can be an AMF.

[0263] In step S2109, the sixth network element 106 sends a first message to the first device 107.

[0264] In some embodiments, the sixth network element 106 can send a first message. In some embodiments, the first message can be sent by the sixth network element 106, but is not limited to this, and can also be sent by other entities.

[0265] In some embodiments, the first device 107 may receive the first message. In some embodiments, the first message may be received by the first device 107, but is not limited thereto, and may also be received by other entities.

[0266] In some embodiments, upon receiving a request message from the fourth network element 104, the sixth network element 106 can determine to wirelessly charge the first device 107 based on the sixth information carried in the request message. Thus, the sixth network element 106 can send a first message.

[0267] In some embodiments, the first message may include fourth information. In some embodiments, step S2109 may include: the sixth network element 106 sending the fourth information to the first device 107. In some embodiments, the fourth information may be used to initiate wireless charging of the first device 107. In some embodiments, the fourth information may be used to perform wireless charging of the first device 107. In some embodiments, the fourth information may indicate that wireless charging of the first device 107 has started.

[0268] In some embodiments, the fourth information may include at least one of the following: wireless charging indication information, identification information of the sixth network element 106, information of the first device 107, and wireless charging parameter information.

[0269] In some embodiments, in response to a first message, the first device 107 can perform wireless charging. For example, the first device 107 can charge itself using electromagnetic waves emitted by a sixth network element 106, based on fifth information carried in the first message. Accordingly, after sending the first message, the sixth network element 106 can send electromagnetic waves to the first device 107 to achieve wireless charging of the first device 107.

[0270] In step S2110, the first device 107 sends a second message to the sixth network element 106.

[0271] In some embodiments, the first device 107 may send a second message. In some embodiments, the second message may be sent by the first device 107, but is not limited thereto, and may also be sent by other entities.

[0272] In some embodiments, the sixth network element 106 can receive the second message. In some embodiments, the second message can be received by the sixth network element 106, but is not limited thereto, and can also be received by other entities.

[0273] In some embodiments, the second message may include third information. In some embodiments, step S2110 may include: the first device 107 sending the third information to the sixth network element 106.

[0274] In some embodiments, the third information is used to report the result of wireless charging of the first device 107. In some embodiments, the third information is used to notify the first device 107 of the result of wireless charging. In some embodiments, the third information is used to report the wireless charging of the first device 107. In some embodiments, the third information is used to provide information on the wireless charging of the first device 107.

[0275] In some embodiments, the third information may indicate at least one of the following: the result of wireless charging, constraints related to wireless charging, and the power status of the first device 107.

[0276] In some embodiments, the result of wireless charging indicated by the third information may include one of the following: charging successful, charging failed, or charging stopped. In some embodiments, when the first device 107 completes wireless charging according to the fourth information, the result of wireless charging may be charging successful. In some embodiments, when the first device 107 fails to perform wireless charging according to the fourth information, the result of wireless charging may be charging failed. In some embodiments, when the first device 107 stops wireless charging during the process of performing wireless charging according to the fourth information, the result of wireless charging may be charging stopped.

[0277] In some embodiments, constraints related to wireless charging may be pre-configured in the first device 107. In some embodiments, the constraints related to wireless charging may be used to limit the execution of wireless charging by the first device 107.

[0278] In some embodiments, constraints related to wireless charging may include at least one of the following: constraints on the execution conditions of wireless charging, and constraints on the charging parameters of wireless charging.

[0279] In some embodiments, constraints on the execution conditions of wireless charging are used to determine the start and / or stop of wireless charging of the first device 107. For example, constraints on the execution conditions of wireless charging may include at least one of the following: temperature constraints and operating state constraints. In some embodiments, temperature constraints may include a temperature range. For example, within the temperature range of the temperature constraint, wireless charging of the first device 107 may be performed. In some embodiments, operating state constraints may include the first device 107 being in a non-operating state. For example, when the first device 107 is in an operating state, wireless charging of the first device 107 may not be performed.

[0280] In some embodiments, constraints on charging parameters for wireless charging are used to limit the wireless charging process of the first device 107. For example, constraints on charging parameters for wireless charging may include at least one of the following: charging power constraints and charging time constraints. In some embodiments, charging power constraints may include a charging power value or a charging power range. In some embodiments, charging time constraints may include charging duration and / or a time window for wireless charging.

[0281] In some embodiments, the third information may simultaneously indicate the result of wireless charging and the constraints associated with wireless charging.

[0282] In some embodiments, the result of wireless charging indicated by the third information may be charging failure. Meanwhile, the constraints related to wireless charging indicated by the third information may include at least one of the following: temperature constraints, operating state constraints, charging power constraints, and charging time constraints. For example, the third information may indicate that the temperature of the first device 107 is higher or lower than the temperature range of the temperature constraint. For example, the third information may indicate that the first device 107 is in an operating state. For example, the third information may indicate that the power of the electromagnetic waves received by the first device 107 for wireless charging is lower than the charging power value or charging power range of the charging power constraint. For example, the third information may indicate that the power of the electromagnetic waves received by the first device 107 for wireless charging is higher than the charging power value or charging power range of the charging power constraint. For example, the third information may indicate that the first device 107 is not within the wireless charging time window.

[0283] In some embodiments, the result of wireless charging indicated by the third information may be charging cessation. Meanwhile, the constraints related to wireless charging indicated by the third information may include at least one of the following: temperature constraints, operating state constraints, charging power constraints, and charging time constraints. For example, the third information may indicate that the temperature of the first device 107 is above or below a temperature range constrained by a temperature constraint. For example, the third information may indicate that the first device 107 is in an operating state. For example, the third information may indicate that the power of the electromagnetic waves received by the first device 107 for wireless charging is below a charging power value or charging power range constrained by a charging power constraint. For example, the third information may indicate that the power of the electromagnetic waves received by the first device 107 for wireless charging is above a charging power value or charging power range constrained by a charging power constraint. For example, the third information may indicate that the time window for wireless charging of the first device 107 has ended.

[0284] In some embodiments, the third information may indicate the battery status of the first device 107. For example, the third information may indicate the current battery level of the first device 107, i.e., the battery level of the first device 107 when sending the third information. It is understood that the battery status of the first device 107 indicated by the third information may include the battery level of the first device 107 before wireless charging, the battery level of the first device 107 after wireless charging, and the change in the battery level of the first device 107 during the wireless charging process.

[0285] In some embodiments, the second message may include at least one of the following: a response message, a reporting message, or a stop message.

[0286] In some embodiments, the second message may be a response message to the first message. For example, the second message may be sent before, during, or after the first device 107 performs wireless charging. In some embodiments, the third information carried in the second message may include constraints related to wireless charging and / or the power status of the first device 107.

[0287] In some embodiments, the second message may be a reporting message for reporting the result of wireless charging of the first device 107. In some embodiments, the third information carried in the second message may include the result of wireless charging, and / or constraints related to wireless charging, and / or the power status of the first device 107.

[0288] In some embodiments, the second message may be a stop message to indicate that wireless charging of the first device 107 may be stopped. In some embodiments, the third information carried in the second message may include the result of wireless charging, and / or constraints related to wireless charging, and / or the power status of the first device 107.

[0289] It should be noted that the number of second messages sent by the first device 107 to the sixth network element 106 can be greater than or equal to one. For example, the first device 107 can send a response message before wireless charging to indicate the power status of the first device 107 and the constraints related to wireless charging. Afterwards, the first device 107 can send a reporting message after wireless charging is complete to indicate the power status of the first device 107. (The last sentence is a repetition of the previous one and can be omitted.)

[0290] It is understandable that, in cases where wireless charging fails or stops, the constraints related to wireless charging indicated in the third information can also be interpreted as the cause of the charging failure or cessation.

[0291] In some embodiments, the third information can be used to provide the sixth network element 106 with constraints related to wireless charging of the first device 107, such as charging power constraints and charging time constraints. In this case, the sixth network element 106 can perform wireless charging of the first device 107 taking into account the obtained constraints related to wireless charging.

[0292] In step S2111, the sixth network element 106 performs monitoring.

[0293] In some embodiments, upon receiving the first information, the sixth network element 106 can monitor, measure, and report the wireless charging service of the first device 107 based on the first information.

[0294] In some embodiments, the sixth network element 106 can monitor a first event of the wireless charging service for the first device 107. In some embodiments, the sixth network element 106 can monitor whether the first event of the wireless charging service for the first device 107 is triggered.

[0295] In some embodiments, the monitored first event may be associated with the wireless charging status of the first device 107. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if the battery level of the first device 107 meets a first condition. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if the periodic timer times out.

[0296] In some embodiments, the first event monitored may be associated with a service operation of the wireless charging service. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if the time during which the service operation is unreachable exceeds a threshold. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if the number of times the service operation is unreachable exceeds a threshold. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if indication information indicating the success of the service operation is obtained. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if indication information indicating the failure of the service operation is obtained. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if a timer used for the service operation times out. In some embodiments, the sixth network element 106 may determine that the first event has been triggered if there is no response to the service operation within the time window used for the service operation.

[0297] In some embodiments, the monitored first event may be associated with the activation of wireless charging. In some embodiments, the sixth network element 106 may determine that the first event has been triggered when the wireless charging capability of the first device 107 is activated. In some embodiments, the sixth network element 106 may determine that the first event has been triggered when the wireless charging capability of the first device 107 is deactivated. In some embodiments, the sixth network element 106 may determine that the first event has been triggered when the wireless charging capability of the sixth network element 106 is activated. In some embodiments, the sixth network element 106 may determine that the first event has been triggered when the wireless charging capability of the sixth network element 106 is deactivated.

[0298] In some embodiments, the monitored first event may be associated with a wireless charging service. In some embodiments, the sixth network element 106 may determine that the first event has been triggered upon receiving indication information indicating the start of a service operation of the wireless charging service. In some embodiments, the sixth network element 106 may determine that the first event has been triggered upon receiving indication information indicating the stop of a service operation of the wireless charging service. In some embodiments, the sixth network element 106 may determine that the first event has been triggered upon the timer used to trigger wireless charging expires. In some embodiments, the sixth network element 106 may determine that the first event has been triggered upon the timer used for the wireless charging service expires. In some embodiments, the sixth network element 106 may determine that the first event has been triggered upon the battery level of the first device 107 meeting a second condition.

[0299] It should be noted that step S2111 may be omitted. In this case, monitoring of the wireless charging service for the first device 107 may not be performed by the sixth network element 106.

[0300] In step S2112, the sixth network element 106 sends a response message to the fourth network element 104.

[0301] In some embodiments, the sixth network element 106 can send a response message. In some embodiments, the response message can be sent by the sixth network element 106, but is not limited to this; it can also be sent by other entities.

[0302] In some embodiments, the fourth network element 104 can receive a response message. In some embodiments, the response message can be received by the fourth network element 104, but is not limited thereto, and can also be received by other entities.

[0303] In some embodiments, the response message sent by the sixth network element 106 may be a response message to the request message in step S2108.

[0304] In some embodiments, the response message may include second information. In some embodiments, step S2112 may include: the sixth network element 106 sending the second information to the fourth network element 104.

[0305] In some embodiments, the second information may indicate the result of monitoring the first event. In some embodiments, the second information may be used to indicate the result of monitoring the first event. In some embodiments, the second information may be used to report the monitoring result of the first event. In some embodiments, the second information may include the result of monitoring the first event.

[0306] In some embodiments, the results of monitoring a first event can indicate the first event that was triggered.

[0307] In some embodiments, the result of monitoring the first event may include at least one of the following: the battery level of the first device 107 (battery value or percentage, or high / low battery level); the wireless charging service is unreachable; the wireless charging service fails; the wireless charging service succeeds; the wireless charging capability of the first device 107 is activated; the wireless charging capability of the first device 107 is deactivated; the wireless charging capability of the sixth network element 106 is activated; the wireless charging capability of the sixth network element 106 is deactivated; the wireless charging service starts; the wireless charging service stops.

[0308] In some embodiments, the result of monitoring the first event may include the battery level of the first device 107, and indicate that the triggered first event is that the battery level of the first device 107 meets a first condition, and / or the periodic timer times out.

[0309] In some embodiments, the battery level of the first device 107 can be indicated by at least one of the following: battery value, battery percentage, and battery level. In some embodiments, the result of monitoring the first event can indicate the battery value of the first device 107. For example, the result of monitoring the first event can indicate that the battery value of the first device 107 is 50 mAh, 60 mAh, etc. In some embodiments, the result of monitoring the first event can indicate the battery percentage of the first device 107. For example, the result of monitoring the first event can indicate that the battery percentage of the first device 107 is 30%, 50%, etc. In some embodiments, the result of monitoring the first event can indicate the battery level of the first device 107. For example, the result of monitoring the first event can indicate that the battery level of the first device 107 is low battery, medium battery, or high battery.

[0310] In some embodiments, the result of monitoring the first event may include the wireless charging service being unavailable, and indicating that the first event triggered is the service being unavailable for a period of time exceeding a threshold, and / or the number of times the service is unavailable exceeds a threshold.

[0311] In some embodiments, the result of monitoring the first event may include the successful operation of the wireless charging service, and the triggered first event may be an indication message indicating the successful operation of the service.

[0312] In some embodiments, the result of monitoring the first event may include a failure of the wireless charging service operation, and the triggered first event may be an indication of obtaining indication information indicating the failure of the service operation, and / or a timer timeout for the service operation, and / or no response to the service operation within the time window for the service operation.

[0313] In some embodiments, the result of monitoring the first event may include the activation of the wireless charging capability of the first device 107, and indicate that the triggered first event is the activation of the wireless charging capability of the first device 107.

[0314] In some embodiments, the result of monitoring the first event may include the deactivation of the wireless charging capability of the first device 107, and indicate that the triggered first event is the deactivation of the wireless charging capability of the first device 107.

[0315] In some embodiments, the result of monitoring the first event may include the activation of the wireless charging capability of the sixth network element 106, and indicate that the triggered first event is the activation of the wireless charging capability of the sixth network element 106.

[0316] In some embodiments, the result of monitoring the first event may include the deactivation of the wireless charging capability of the sixth network element 106, and indicate that the triggered first event is the deactivation of the wireless charging capability of the sixth network element 106.

[0317] In some embodiments, the result of monitoring the first event may include the start of the wireless charging service, and indicate that the triggered first event is an indication of obtaining service operation information indicating the start of the wireless charging service, and / or a timer timeout for triggering wireless charging.

[0318] In some embodiments, the result of monitoring the first event may include the wireless charging service stopping, and indicating that the triggered first event is an indication that the wireless charging service operation has stopped, and / or a timer for the wireless charging service has timed out, and / or the battery level of the first device meets a second condition.

[0319] In some embodiments, the response message may include third information. In some embodiments, step S2112 may include: the sixth network element 106 sending the third information to the fourth network element 104.

[0320] In some embodiments, the sixth network element 106 can directly send a response message to the fourth network element 104. In some embodiments, the sixth network element 106 can send a response message to the fourth network element 104 via the fifth network element 105.

[0321] In step S2113, the fourth network element 104 performs monitoring.

[0322] For optional implementations of step S2113, please refer to [link / reference]. Figure 2A Optional implementations of step S2111, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0323] In some embodiments, the fourth network element 104 performs monitoring of the wireless charging service for the first device 107. It should be noted that the monitoring method performed by the fourth network element 104 can be referred to the monitoring method performed by the sixth network element 106, and will not be described in detail here.

[0324] It should be noted that step S2113 may be omitted. In this case, the monitoring of the wireless charging service for the first device 107 may not be performed by the fourth network element 104.

[0325] In some embodiments, monitoring of the wireless charging service for the first device 107 can be performed by the sixth network element 106 and / or the fourth network element 104. For example, step S2111 can be performed, but step S2113 may not be performed. For example, step S2113 can be performed, but step S2111 may not be performed. For example, both steps S2111 and S2113 can be performed.

[0326] In step S2114, the fourth network element 104 sends a notification message to the second network element 102.

[0327] In some embodiments, the fourth network element 104 can send a notification message. In some embodiments, the notification message can be sent by the fourth network element 104, but is not limited to this; it can also be sent by other entities.

[0328] In some embodiments, the second network element 102 can receive notification messages. In some embodiments, the notification message can be received by the second network element 102, but is not limited thereto, and can also be received by other entities.

[0329] In some embodiments, the notification message may include second information. In some embodiments, step S2114 may include: the fourth network element 104 sending the second information to the second network element 102.

[0330] In some embodiments, the notification message may include third information. In some embodiments, step S2114 may include: the fourth network element 104 sending the third information to the second network element 102.

[0331] In some embodiments, the notification message may be sent based on at least one of the following: a subscription from the first network element 101, or a local configuration from the fourth network element 104.

[0332] In some embodiments, the first network element 101 can subscribe to the monitoring results of the wireless charging service of the first device 107 from the fourth network element 104 through a request message carrying first information or other messages. In some embodiments, if the first network element 101 does not subscribe, the local configuration of the fourth network element 104 can configure the fourth network element 104 to report the monitoring results of the wireless charging service of the first device 107 to the first network element 101.

[0333] In some embodiments, the first network element 101 can subscribe to the result of wireless charging of the first device 107 from the fourth network element 104 through a request message carrying fifth information or other messages. In some embodiments, if the first network element 101 does not subscribe, the local configuration of the fourth network element 104 can configure the fourth network element 104 to report the result of wireless charging of the first device 107 to the first network element 101.

[0334] In some embodiments, the notification message sent by the fourth network element 104 may be an Nmciotf_6G MCIoT_WPC notification message.

[0335] In step S2115, the second network element 102 sends a notification message to the first network element 101.

[0336] In some embodiments, the second network element 102 can send a notification message. In some embodiments, the notification message can be sent by the second network element 102, but is not limited to this; it can also be sent by other entities.

[0337] In some embodiments, the first network element 101 can receive notification messages. In some embodiments, the notification message can be received by the first network element 101, but is not limited thereto, and can also be received by other entities.

[0338] In some embodiments, the notification message may include second information. In some embodiments, step S2115 may include: the second network element 102 sending the second information to the first network element 101.

[0339] In some embodiments, the notification message may include third information. In some embodiments, step S2115 may include: the second network element 102 sending the third information to the first network element 101.

[0340] In some embodiments, the notification message sent by the second network element 102 may be an Nnef_6G MCIoT_WPC notification message.

[0341] In some embodiments, the first network element 101 may be an untrusted network function. In this case, the second and / or third information sent by the fourth network element 104 may reach the first network element 101 via the second network element 102.

[0342] In some embodiments, the first network element 101 may be a trusted network function. In this case, the second and / or third information sent by the fourth network element 104 can directly reach the first network element 101.

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

[0344] In some embodiments, the first network element 101 may be AF, ASP, MCAF, DN, etc.

[0345] In some embodiments, the first network element 101 may be a charging safety controller. For example, the charging safety controller may be located within the core network or outside the core network. In some embodiments, the first network element 101 may be a stand-alone network function or may be integrated with other network functions.

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

[0347] In some embodiments, steps S2104 and S2105 may be performed in an alternate order or simultaneously, and steps S2105 and S2107 may be performed in an alternate order or simultaneously.

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

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

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

[0351] In step S2201, the first device 107 sends a request message to the fourth network element 104.

[0352] In some embodiments, the first device 107 may send a request message. In some embodiments, the request message may be sent by the first device 107, but is not limited thereto, and may also be sent by other entities.

[0353] In some embodiments, the fourth network element 104 can receive request messages. In some embodiments, the request message can be received by the fourth network element 104, but is not limited to this, and can also be received by other entities.

[0354] In some embodiments, the request message may be used to request wireless charging of the first device 107. In some embodiments, the request message may be used to request the execution of a wireless charging service for the first device 107.

[0355] In some embodiments, when the first device 107 determines that wireless charging is required, the first device 107 may send a request message. In some embodiments, the first device 107 may periodically send request messages to request wireless charging. For example, the charging cycle for the first device 107 may be one week, one month, one year, etc., and the first device 107 may send request messages according to this cycle. In some embodiments, the first device 107 may non-periodically send request messages to request wireless charging. For example, the first device 107 may check its own battery status and send a request message when the battery status is below a preset threshold.

[0356] In some embodiments, the request message sent by the first device 107 may include fifth information. In some embodiments, step S2201 may include: the first device 107 sending the fifth information to the second network element 102. The fifth information may be used to request wireless charging for the first device 107.

[0357] In some embodiments, the fifth information may include at least one of the following: wireless charging indication information, information of the first device 107, and wireless charging parameter information.

[0358] In some embodiments, the wireless charging indication information may indicate a wireless charging request. In some embodiments, the wireless charging indication information may indicate that the first device 107 requests to perform a wireless charging service. In some embodiments, the wireless charging indication information may indicate that the request message carrying fifth information is a request message for wireless charging.

[0359] In some embodiments, wireless charging indication information may be carried in a field, which may include one or more bits. In some embodiments, a first value of the field may indicate wireless charging, and a second value of the field may not indicate wireless charging. For example, the field may have one bit. In this case, the first value may be 1 and the second value may be 0; or, the first value may be 0 and the second value may be 1. In some embodiments, the presence of the field may indicate wireless charging, and the absence of the field may not indicate wireless charging. For example, if the fifth information includes a field carrying wireless charging indication information, then the fifth information is used to request wireless charging for the first device; otherwise, the fifth information is not used to request wireless charging for the first device.

[0360] In some embodiments, the information of the first device 107 may be information related to the first device 107 required to perform a wireless charging service for the first device 107.

[0361] In some embodiments, the information of the first device 107 may include identification information of the first device 107. It is understood that the information of the first device 107 may also include other information related to the first device 107, and this disclosure does not specifically limit this.

[0362] In some embodiments, the parameter information for wireless charging may indicate the relevant parameters of the wireless charging service performed on the first device 107.

[0363] In some embodiments, the parameters indicated by the wireless charging parameter information may include at least one of the following: charging time, charging power, and charging target. It is understood that the parameter information may also indicate other parameters related to the wireless charging service, and this disclosure does not specifically limit these parameters.

[0364] In some embodiments, the wireless charging parameter information may indicate at least one of the following regarding the charging time: the start time of wireless charging, the end time of wireless charging, and the duration of wireless charging.

[0365] In some embodiments, the wireless charging parameter information may indicate at least one of the following regarding charging power: the maximum power of wireless charging and the minimum power of wireless charging.

[0366] In some embodiments, the wireless charging parameter information may indicate the target amount of power to be wirelessly charged to the first device 107, with respect to the charging target.

[0367] In some embodiments, the first device 107 can send the fifth information via the control plane. For example, the first device 107 can send the fifth information to the fourth network element 104 via the access network device and / or AMF on the control plane. For example, the request message containing the fifth information sent by the first device 107 can be control plane signaling. For example, the first device 107 can send the fifth information to the fourth network element 104 via the local MCIoTF on the control plane. For example, the request message containing the fifth information sent by the first device 107 can be user plane data. For example, the first device 107 can send the fifth information to the fourth network element 104 via the control plane. For example, the request message containing the fifth information sent by the first device 107 can be user plane data.

[0368] In some embodiments, the first device 107 can send the fifth information via the user plane. For example, the first device 107 can send the fifth information to the fourth network element 104 via a local MCIoTF on the user plane. For example, the request message containing the fifth information sent by the first device 107 can be user plane data. For example, the first device 107 can send the fifth information to the fourth network element 104 via the user plane. For example, the request message containing the fifth information sent by the first device 107 can be user plane data.

[0369] In some embodiments, the request message sent by the first device 107 to the fourth network element 104 may be an Nmciotf_6GMCIoT_WPC request message.

[0370] In some embodiments, the fourth network element 104 can obtain the first information. In some embodiments, the fourth network element 104 can obtain the first information locally. In some embodiments, the first information can be obtained based on the local configuration of the fourth network element 104.

[0371] In some embodiments, the local configuration of the fourth network element 104 may include at least one of the following: protocol agreement, OAM configuration, and operator policy.

[0372] In step S2202, the fourth network element 104 performs authorization.

[0373] For optional implementations of step S2202, please refer to [link / reference]. Figure 2A Optional implementations of step S2104, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0374] In step S2203, the fourth network element 104 triggers the sixth network element 106 to perform wireless charging.

[0375] For optional implementations of step S2203, please refer to [link / reference]. Figure 2A Optional implementations of step S2107, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0376] In step S2204, the fourth network element 104 sends a request message to the sixth network element 106.

[0377] For optional implementations of step S2204, please refer to [link / reference]. Figure 2A Optional implementations of step S2108, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0378] In step S2205, the sixth network element 106 sends a first message to the first device 107.

[0379] For optional implementations of step S2205, please refer to [link / reference]. Figure 2A Optional implementations of step S2109, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0380] In step S2206, the first device 107 sends a second message to the sixth network element 106.

[0381] For optional implementations of step S2206, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2110, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0382] In step S2207, the sixth network element 106 performs monitoring.

[0383] For optional implementations of step S2207, please refer to [link / reference]. Figure 2A Optional implementations of step S2111, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0384] In some embodiments, the sixth network element 106 may perform monitoring based on the first information.

[0385] In some embodiments, the first information may be received by the sixth network element 106 from the fourth network element 104.

[0386] In some embodiments, the first information may be obtained based on the local configuration of the sixth network element 106. In some embodiments, the local configuration of the sixth network element 106 may include at least one of the following: protocol agreement, OAM configuration, and operator policy.

[0387] In step S2208, the sixth network element 106 sends a response message to the fourth network element 104.

[0388] For optional implementations of step S2208, please refer to [link / reference]. Figure 2A Optional implementations of step S2112, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0389] In step S2209, the fourth network element 104 performs monitoring.

[0390] For optional implementations of step S2209, please refer to [link / reference]. Figure 2A Optional implementations of step S2113, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0391] In some embodiments, the fourth network element 104 may perform monitoring based on the first information.

[0392] In some embodiments, the first information may be obtained based on the local configuration of the fourth network element 104. In some embodiments, the local configuration of the fourth network element 104 may include at least one of the following: protocol agreement, OAM configuration, and operator policy.

[0393] In step S2210, the fourth network element 104 sends a notification message to the second network element 102.

[0394] Optional implementations of step S2210 can be found in [reference needed]. Figure 2A Optional implementations of step S2114, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0395] In step S2211, the second network element 102 sends a notification message to the first network element 101.

[0396] Optional implementations of step S2211 can be found in [reference]. Figure 2A Optional implementations of step S2115, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0397] In some embodiments, the fourth network element 104 may determine to report second information and / or third information based on the subscription of the first network element 101.

[0398] In some embodiments, the fourth network element 104 may determine whether to report the second information and / or the third information based solely on its local configuration. In some embodiments, the fourth network element 104 may determine, based on configuration information, to report the second information and / or the third information to the first network element 101. For example, the fourth network element 104 may send a notification message to the second network element 102 according to operator policies, and provide the second information and / or the third information to the first network element 101 through the second network element 102. In this case, steps S2210 and S2211 may be executed. In some embodiments, the fourth network element 104 may determine, based on the second information and / or configuration information, not to report the third information to the first network element 101. In this case, steps S2210 and S2211 may not be executed.

[0399] In step S2212, the fourth network element 104 sends a response message to the first device 107.

[0400] In some embodiments, the fourth network element 104 can send a response message. In some embodiments, the response message can be sent by the fourth network element 104, but is not limited to this; it can also be sent by other entities.

[0401] In some embodiments, the first device 107 may receive a response message. In some embodiments, the response message may be received by the first device 107, but is not limited thereto, and may also be received by other entities.

[0402] In some embodiments, the response message sent by the fourth network element 104 may be a response message to the request message in step S2201. In some embodiments, the response message sent by the fourth network element 104 may be an Nmciotf_6GMCIoT_WPC response message.

[0403] In some embodiments, the response message sent by the fourth network element 104 may include third information. In some embodiments, step S2210 may include: the fourth network element 104 sending third information to the first device 107.

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

[0405] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2212. For example, step S2204 may be implemented as a standalone embodiment, the combination of steps S2204 and S2207 may be implemented as a standalone embodiment, and the combination of steps S2201 and S2209 may be implemented as a standalone embodiment, but is not limited thereto.

[0406] In some embodiments, steps S2210 and S2212 may be performed in an alternate order or simultaneously.

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

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

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

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

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

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

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

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

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

[0416] In some embodiments, the terms "service," "business," and "traffic" can be used interchangeably. In some embodiments, the terms "wireless charging service" and "wireless charging business" can be used interchangeably, as can the terms "service operation" and "business operation."

[0417] In some embodiments, the terms "Internet of Things device", "MC device", "massive Internet of Things device" and other similar terms can be used interchangeably.

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

[0419] Figure 3A This is an interactive schematic diagram of a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. Figure 3A As shown, the above method includes steps S3101 to S3103.

[0420] In step S3101, the first network element 101 sends the first information to the fourth network element 104.

[0421] For optional implementations of step S3101, please refer to [link / reference]. Figure 2A Steps S2101, S2102, S2103 Figure 2B Optional implementations of step S2201, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0422] In some embodiments, step S3101 may be omitted. The fourth network element 104 may obtain the first information locally.

[0423] In step S3102, the fourth network element 104 performs monitoring.

[0424] Optional implementations of step S3102 can be found in [reference]. Figure 2A Step S2113 Figure 2B Optional implementations of step S2209, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0425] In step S3103, the fourth network element 104 sends the second information to the first network element 101.

[0426] For optional implementations of step S3103, please refer to [link / reference]. Figure 2A Steps S2114, S2115 Figure 2B The optional implementation methods of steps S2210 and S2211, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

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

[0428] Figure 3B This is an interactive schematic diagram of a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. Figure 3B As shown, the above method includes steps S3201 to S3205.

[0429] In step S3201, the first network element 101 sends the first information to the fourth network element 104.

[0430] For optional implementations of step S3201, please refer to [link / reference]. Figure 2A Steps S2101, S2102, S2103 Figure 2B Optional implementations of step S2201, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0431] In some embodiments, step S3201 may be omitted. The fourth network element 104 can obtain the first information locally.

[0432] In step S3202, the fourth network element 104 sends the first information to the sixth network element 106.

[0433] For optional implementations of step S3202, please refer to [link / reference]. Figure 2A Step S2108 Figure 2B Optional implementations of step S2204, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0434] In step S3203, the sixth network element 106 performs monitoring.

[0435] For optional implementations of step S3203, please refer to [link / reference]. Figure 2A Step S2111 Figure 2B Optional implementations of step S2207, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0436] In step S3204, the sixth network element 106 sends the second information to the fourth network element 104.

[0437] For optional implementations of step S3204, please refer to [link / reference]. Figure 2A Step S2112 Figure 2B Optional implementations of step S2208, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0438] In step S3205, the fourth network element 104 sends the second information to the first network element 101.

[0439] For optional implementations of step S3205, please refer to [link / reference]. Figure 2A Steps S2114, S2115 Figure 2B The optional implementation methods of steps S2210 and S2211, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

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

[0441] Figure 3C This is an interactive schematic diagram of a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. Figure 3C As shown, the above method includes steps S3301 to S3306.

[0442] In step S3301, the first network element 101 sends the first information to the fourth network element 104.

[0443] For optional implementations of step S3301, please refer to [link / reference]. Figure 2A Steps S2101, S2102, S2103 Figure 2B Optional implementations of step S2201, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0444] In some embodiments, step S3201 may be omitted. The fourth network element 104 can obtain the first information locally.

[0445] In step S3302, the fourth network element 104 sends the first information to the sixth network element 106.

[0446] For optional implementations of step S3302, please refer to [link / reference]. Figure 2A Step S2108 Figure 2B Optional implementations of step S2204, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0447] In step S3303, the sixth network element 106 performs monitoring.

[0448] For optional implementations of step S3303, please refer to [link / reference]. Figure 2A Step S2111 Figure 2B Optional implementations of step S2207, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0449] In step S3304, the sixth network element 106 sends the second information to the fourth network element 104.

[0450] For optional implementations of step S3304, please refer to [link / reference]. Figure 2A Step S2112 Figure 2B Optional implementations of step S2208, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0451] In step S3305, the fourth network element 104 performs monitoring.

[0452] For optional implementations of step S3305, please refer to [link / reference]. Figure 2A Step S2113 Figure 2BOptional implementations of step S2209, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0453] In step S3306, the fourth network element 104 sends the second information to the first network element 101.

[0454] For optional implementations of step S3306, please refer to [link / reference]. Figure 2A Steps S2114, S2115 Figure 2B The optional implementation methods of steps S2210 and S2211, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0455] In some embodiments, the second information sent by the fourth network element 104 to the first network element 101 includes at least one of the following: the result of monitoring the wireless charging service of the first device 107 reported by the sixth network element 106, and the result of monitoring the wireless charging service of the first device 107 by the fourth network element 104.

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

[0457] Figure 4A This is an interactive schematic diagram of a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. Figure 4A As shown, the above method includes steps S4101 to S4103.

[0458] In step S4101, the first node acquires the first information.

[0459] For optional implementations of step S4101, please refer to [link / reference]. Figure 2A Optional implementation methods for steps S2101, S2102, S2103, and S2108 Figure 2B Steps S2201, S2204, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0460] In some embodiments, the first node may receive first information sent by the third node.

[0461] In some embodiments, the first node can obtain the first information from the local machine.

[0462] In some embodiments, the first information may be used to monitor a first event in a wireless charging service associated with the first device.

[0463] In step S4102, the first node performs monitoring of the first event.

[0464] For optional implementations of step S4102, please refer to [link / reference]. Figure 2A Steps S2111, S2113 Figure 2B Optional implementation methods for steps S2207 and S2209, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0465] In step S4103, the first node sends the second information.

[0466] For optional implementations of step S4103, please refer to Figure 2A Steps S2112, S2114, S2115 Figure 2B Optional implementation methods for steps S2208, S2210, and S2211, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0467] In some embodiments, the second information may indicate the results of monitoring the first event.

[0468] In some embodiments, the third node may be the first network element 101. In some embodiments, the third node may be the fourth network element 104. For example, the third node may include at least one of the following: AF, charging safety controller, and MCIoTF.

[0469] In some embodiments, the first node may be a fourth network element 104. For example, the first node may include an MCIoTF. In some embodiments, the first node may receive first information from the first network element 101. In some embodiments, the first node may send second information to the first network element 101.

[0470] In some embodiments, the first node may be a sixth network element 106. For example, the first node may include at least one of the following: a terminal device, an access network device, or a (local) MCIoTF. In some embodiments, the first node may receive first information from a fourth network element 104. In some embodiments, the first node may send second information to the fourth network element 104.

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

[0472] Figure 4B This is an interactive schematic diagram of a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. Figure 4B As shown, the above method includes steps S4201 to S4205.

[0473] In step S4201, the first node acquires the first information.

[0474] For optional implementations of step S4201, please refer to [link / reference]. Figure 2A Optional implementation methods for steps S2101, S2102, S2103, and S2108 Figure 2B Steps S2201, S2204, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0475] In some embodiments, the first node may receive first information sent by the third node.

[0476] In some embodiments, the first node can obtain the first information from the local machine.

[0477] In some embodiments, the first information may be used to monitor a first event in a wireless charging service associated with the first device.

[0478] In step S4202, the first node sends the first information to the second node.

[0479] For optional implementations of step S4202, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2108 Figure 2B Step S2204, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0480] In step S4203, the second node performs monitoring of the first event.

[0481] For optional implementations of step S4203, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2111 Figure 2B Step S2207, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0482] In step S4204, the second node sends the second information to the first node.

[0483] For optional implementations of step S4204, please refer to [link / reference]. Figure 2A Optional implementation methods of step S2112 Figure 2B Step S2208, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0484] In step S4205, the first node sends the second information to the third node.

[0485] For optional implementations of step S4103, please refer to Figure 2A Steps S2112, S2114, S2115 Figure 2B Optional implementation methods for steps S2208, S2210, and S2211, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0486] In some embodiments, the second information may indicate the results of monitoring the first event.

[0487] In some embodiments, the third node may be the first network element 101. For example, the third node may include at least one of the following: AF, charging safety controller.

[0488] In some embodiments, the first node may be a fourth network element 104. For example, the first node may include an MCIoTF.

[0489] In some embodiments, the second node may be a sixth network element 106. For example, the second node may include at least one of the following: a terminal device, an access network device, or a (local) MCIoTF.

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

[0491] Figure 5 This is an interactive schematic diagram of a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. Figure 5 As shown, the above method includes step S501.

[0492] In step S501, the first node acquires the first information.

[0493] In some embodiments, the first node may receive first information sent by the third node.

[0494] In some embodiments, the first node can obtain the first information from the local machine.

[0495] For optional implementations of step S501, please refer to [link / reference]. Figure 2A Optional implementation methods for steps S2101, S2102, S2103, and S2108 Figure 2B Steps S2201, S2204, and Figure 2A , Figure 2B Other related parts in the embodiments involved will not be described in detail here.

[0496] In the following, specific embodiments of the present disclosure will be described by way of example.

[0497] In some embodiments, this disclosure provides a method for supporting 6G MCIoT wireless charging status monitoring and notification to support wireless charging of large-scale IoT devices.

[0498] In some embodiments, 6G MCIoT wireless charging status monitoring and notification information (i.e., first information) is provided to MCIoTF to support wireless charging of a large number of IoT devices.

[0499] In some embodiments, the 6G MCIoT wireless charging status monitoring and notification information includes:

[0500] - 6G MCIoT wireless charging status events and reporting event triggers. 6G MCIoT wireless charging status events include:

[0501] - Wireless charging percentage;

[0502] - Wireless charging threshold;

[0503] - Wireless charging service operation is unavailable, failed, or successful;

[0504] - Wireless charging activated;

[0505] - Wireless charging deactivates;

[0506] - Wireless charging service is now available;

[0507] Wireless charging service has been discontinued.

[0508] In some embodiments, monitoring and notification (or event reporting) of subscription events regarding the 6G MCIoT wireless charging status will be communicated from the 6G MCIoTF to the consumer (e.g., the 6G MCIoT ASP AF, or the WPC security controller).

[0509] In some embodiments, the wireless power charging equipment (WPCE) (a 3GPP UE or NG-RAN or local MCIoTF with wireless charging capability) or the 6G MCIoTF is required to perform monitoring / measurement of subscription events for the 6G MCIoT wireless charging status:

[0510] - Wireless charging percentage, for example, periodically reported in each time window (5 minutes) to trigger percentage reporting;

[0511] - Wireless charging threshold, for example, up to 80%, to trigger percentage reporting;

[0512] - Wireless charging service operation becomes unreachable, fails, or succeeds, for example, if the unreachability (time and / or number of times) exceeds a threshold, triggering a WPC status report;

[0513] - Wireless charging is activated, for example, based on the contracted area or time window, the WPC capability of WPCE is activated;

[0514] - Wireless charging is deactivated, for example, based on the contracted region or time window, the WPC capability of WPCE is deactivated;

[0515] - Wireless charging service begins, for example, WPC service operation for 6G MCIoT by WPCE begins due to a request or event trigger (e.g., charging start time);

[0516] - Wireless charging service stops, for example, WPC service operation of WPCE for 6G MCIoT stops because of a request or event trigger (e.g., charging window timeout, or device battery threshold being reached).

[0517] In some embodiments, monitoring / measurement of events related to the 6G MCIoT wireless charging status can be applied based on 6G MCIoT ASP AF requests, and / or WPC security controller requests, and / or operator WPC policy controls.

[0518] In some embodiments, the monitoring / measurement results of 6G MCIoT wireless charging status events will be notified to the subscription consumer (e.g., 6G MCIoT ASP AF, or WPC security controller) directly or via NEF by the wireless charging device (3GPP UE or NG-RAN or local MCIoTF with wireless charging capability) or the 6G MCIoTF.

[0519] In some embodiments, 6G MCIoTF (Massive Communication IoT Function) supports wireless power supply service operation for 6G massive IoT devices.

[0520] In some embodiments, if a wireless charging request is received from the AF:

[0521] - Supports interaction with AF (or via NEF) for wireless power service, and authorizes the trusted AF to perform wireless power service operation requests after receiving a wireless charging request from AF.

[0522] -6G MCIoTF performs selection and reselection of wireless charging devices (3GPP UE or NG-RAN or local MCIoTF with wireless charging capability) (as described above);

[0523] - Trigger a 3GPP UE or NG-RAN or MCIoTF to perform wireless charging operations for 6G massive IoT devices (e.g., activate or deactivate wireless charging as a wireless power supply device);

[0524] - Based on local configuration or AF request, report service operation results to AF (via NEF).

[0525] In some embodiments, if a wireless charging request is received from a 6G massive IoT device:

[0526] - Supports direct (e.g., local MCIoTF control) or indirect (e.g., via 3GPP UE or NG-RAN) interaction with 6G massive IoT devices for Power over Wireless service, and authorizes Power over Wireless service operation requests after receiving wireless charging requests from 6G massive IoT devices;

[0527] -6G MCIoTF performs selection and reselection of wireless charging devices (3GPP UE or NG-RAN or local MCIoTF with wireless charging capability) (as described above);

[0528] - Trigger a 3GPP UE or NG-RAN or MCIoTF to perform wireless charging operations for 6G massive IoT devices (e.g., activate or deactivate wireless charging as a wireless power supply device);

[0529] - Based on local configuration or 6G massive IoT service provider function requests, report service operation results to 6G massive IoT devices and / or 6G massive IoT service provider functions (via NEF).

[0530] In some embodiments, the 6G Massive Service Provider Functionality supports Wireless Power Service operation for 6G MCIoTF (Massive Communications IoT Functionality):

[0531] - Interacts with NEF to enable wireless charging-related services to be made available to third parties;

[0532] - Interacts with 6G MCIoTF for wireless charging-related services to be made available to trusted AFs.

[0533] Figure 6A This is an interactive schematic diagram illustrating an exemplary implementation of the communication method provided according to embodiments of this disclosure. For example... Figure 6A As shown, this method involves support for WPC services of 6G massive IoT (request from 6G MCIoT ASP).

[0534] In step 1, the 6G Massive IoT Service Provider Function sends an Nnef_6G MCIoT_WPC request message to the NEF (in the case of an untrusted AF) (AF ID, WPC request indication, information related to the target 6G MCIoT device).

[0535] In some embodiments, 6G MCIoT wireless charging status monitoring and notification information is provided to MCIoTF to support wireless charging of a large number of IoT devices.

[0536] In some embodiments, the 6G MCIoT wireless charging status monitoring and notification information includes:

[0537] - 6G MCIoT wireless charging status events and reporting event triggers. 6G MCIoT wireless charging status events include:

[0538] - Wireless charging percentage;

[0539] - Wireless charging threshold;

[0540] - Wireless charging service operation is unavailable, failed, or successful;

[0541] - Wireless charging activated;

[0542] - Wireless charging deactivates;

[0543] - Wireless charging service is now available;

[0544] Wireless charging service has been discontinued.

[0545] In some embodiments, the 6G MCIoT service provider functionality supports wireless power delivery service operation for 6G MCIoTF:

[0546] - Interacts with NEF to enable wireless charging-related services to be made available to third parties;

[0547] - Interacts with 6G MCIoTF for wireless charging-related services to be made available to trusted AFs.

[0548] In step 2, NEF confirms the 6G MCIoTF (e.g., based on requests and / or operator policies, Xunze 6GMCIoTF).

[0549] In some embodiments, if no 6G MCIoTF exists for the WPC service request, the NEF rejects the 6G MCIoT WPC request to terminate the process.

[0550] In step 3, the NEF first sends the Nmciotf_6G MCIoT_WPC request message (AF ID, WPC request indication, information related to the target 6G MCIoT device).

[0551] In step 4, the 6G MCIoTF receives the Nmciotf_6G MCIoT_WPC request message and verifies the parameters included in the request.

[0552] In some embodiments, the 6G MCIoTF is required to perform monitoring / measurement of subscription events for the 6G MCIoT wireless charging state:

[0553] - Wireless charging percentage, for example, periodically reported in each time window (5 minutes) to trigger percentage reporting;

[0554] - Wireless charging threshold, for example, up to 80%, to trigger percentage reporting;

[0555] - Wireless charging service operation becomes unreachable, fails, or succeeds, for example, if the unreachability (time and / or number of times) exceeds a threshold, triggering a WPC status report;

[0556] - Wireless charging is activated, for example, based on the contracted area or time window, the WPC capability of WPCE is activated;

[0557] - Wireless charging is deactivated, for example, based on the contracted region or time window, the WPC capability of WPCE is deactivated;

[0558] - Wireless charging service begins, for example, WPC service operation for 6G MCIoT by WPCE begins due to a request or event trigger (e.g., charging start time);

[0559] - Wireless charging service stops, for example, WPC service operation of WPCE for 6G MCIoT stops because of a request or event trigger (e.g., charging window timeout, or device battery threshold being reached).

[0560] In some embodiments, the monitoring / measurement results of 6G MCIoT wireless charging status events will be notified to the subscriber consumer (e.g., 6G MCIoT ASP AF, or WPC security controller) directly by the 6G MCIoTF or via the NEF.

[0561] In some embodiments, the 6G MCIoTF supports interaction with the AF (or via the NEF) for wireless power supply services, and after receiving a wireless charging request from the AF, authorizes the trusted AF to perform wireless power supply service operation requests.

[0562] In some embodiments, the 6G MCIoTF triggers a 3GPP UE or NG-RAN or MCIoTF to perform wireless charging operations for 6G massive IoT devices (e.g., activating or deactivating wireless charging as a wireless power supply device).

[0563] In some embodiments, the 6G MCIoTF reports service operation results to the AF (via NEF) based on local configuration or AF request.

[0564] In step 5, the 6G MCIoTF sends an Nmciotf_6G MCIoT_WPC response message (accept or reject, [reason code]) to the NEF.

[0565] In step 6, NEF sends an Nnef_6G MCIoT_WPC response message (accept or reject, [reason code]) to AF. If the response is a rejection, the process ends here.

[0566] In step 7, the 6G MCIoTF confirms the WPC device (e.g., selects the 6G MCIoT wireless power supply device based on a request and / or operator policy; the WPC device can be a 3GPP UE, NG-RAN, or a local MCIoTF) to activate or deactivate the wireless charging operation.

[0567] In some embodiments, the wireless charging device (a 3GPP UE or NG-RAN or a local MCIoTF with wireless charging capability) is required to perform monitoring / measurement of subscription events for the 6G MCIoT wireless charging state:

[0568] - Wireless charging percentage, for example, periodically reported in each time window (5 minutes) to trigger percentage reporting;

[0569] - Wireless charging threshold, for example, up to 80%, to trigger percentage reporting;

[0570] - Wireless charging service operation becomes unreachable, fails, or succeeds, for example, if the unreachability (time and / or number of times) exceeds a threshold, triggering a WPC status report;

[0571] - Wireless charging is activated, for example, based on the contracted area or time window, the WPC capability of WPCE is activated;

[0572] - Wireless charging is deactivated, for example, based on the contracted region or time window, the WPC capability of WPCE is deactivated;

[0573] - Wireless charging service begins, for example, WPC service operation for 6G MCIoT by WPCE begins due to a request or event trigger (e.g., charging start time);

[0574] - Wireless charging service stops, for example, WPC service operation of WPCE for 6G MCIoT stops because of a request or event trigger (e.g., charging window timeout, or device battery threshold being reached).

[0575] In some embodiments, the monitoring / measurement results of 6G MCIoT wireless charging status events will be notified to the subscription consumer (e.g., 6G MCIoT ASP AF, or WPC security controller) directly or via NEF by the wireless charging device (3GPP UE or NG-RAN or local MCIoTF with wireless charging capability).

[0576] In step 8, the 6G MCIoTF sends a 6G MCIoT WPC request message (WPC request indication, WPC device ID, and information related to the target 6G MCIoT device) directly or via the AMF to the WPC device.

[0577] In step 9, the WPC device (e.g., UE, NG-RAN, or local 6G MCIoTF) sends a WPC start message to the 6G MCIoT device to begin WPC operation for the target 6G MCIoT device.

[0578] In step 10, the MCIoT device sends a WPC response / reporting / stop message to the WPC device. The response / reporting / stop message may include charging results (e.g., failure, success, constraint), power status data, etc.

[0579] In step 11, in response, the WPC device (e.g., UE, NG-RAN, or local 6G MCIoTF) sends a WPC response message to the 6G MCIoTF directly or through a proxy function (e.g., AMF).

[0580] In step 12, according to the subscription or operator policy of the AF, the 6G MCIoTF reports the result of the 6G MCIoT WPC request to the NEF by sending the Nmciotf_6GMCIoT_WPC notification message.

[0581] In step 13, NEF informs the 6G MCIoT WPC request result to the 6G MCIoT WPC service provider function by sending the Nnef_6G MCIoT_WPC notification message.

[0582] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0583] Figure 6B This is an interactive schematic diagram illustrating an exemplary implementation of the communication method provided according to embodiments of this disclosure. For example... Figure 6B As shown, this method involves supporting WPC services for 6G massive IoT (requests from 6G MCIoT devices).

[0584] In step 1, the 6G MCIoT device sends an Nmciotf_6G MCIoT_WPC request message (6G MCIoT device ID, WPC request indication) directly or through a 6G CP / UP function (e.g., NG-RAN, AMF, switching agent function, etc.) to the 6G MCIoT function.

[0585] In some embodiments, 6G MCIoT wireless charging status monitoring and notification information is provided to MCIoTF to support wireless charging of a large number of IoT devices.

[0586] In some embodiments, the 6G MCIoT wireless charging status monitoring and notification information includes:

[0587] - 6G MCIoT wireless charging status events and reporting event triggers. 6G MCIoT wireless charging status events include:

[0588] - Wireless charging percentage;

[0589] - Wireless charging threshold;

[0590] - Wireless charging service operation is unavailable, failed, or successful;

[0591] - Wireless charging activated;

[0592] - Wireless charging deactivates;

[0593] - Wireless charging service is now available;

[0594] Wireless charging service has been discontinued.

[0595] In step 2, the 6G MCIoTF receives the Nmciotf_6G MCIoT_WPC request message and verifies the parameters included in the request.

[0596] In some embodiments, the 6G MCIoTF is required to perform monitoring / measurement of subscription events for the 6G MCIoT wireless charging state:

[0597] - Wireless charging percentage, for example, periodically reported in each time window (5 minutes) to trigger percentage reporting;

[0598] - Wireless charging threshold, for example, up to 80%, to trigger percentage reporting;

[0599] - Wireless charging service operation becomes unreachable, fails, or succeeds, for example, if the unreachability (time and / or number of times) exceeds a threshold, triggering a WPC status report;

[0600] - Wireless charging is activated, for example, based on the contracted area or time window, the WPC capability of WPCE is activated;

[0601] - Wireless charging is deactivated, for example, based on the contracted region or time window, the WPC capability of WPCE is deactivated;

[0602] - Wireless charging service begins, for example, WPC service operation for 6G MCIoT by WPCE begins due to a request or event trigger (e.g., charging start time);

[0603] - Wireless charging service stops, for example, WPC service operation of WPCE for 6G MCIoT stops because of a request or event trigger (e.g., charging window timeout, or device battery threshold being reached).

[0604] In some embodiments, the monitoring / measurement results of 6G MCIoT wireless charging status events will be notified to the subscriber consumer (e.g., 6G MCIoT ASP AF, or WPC security controller) directly by the 6G MCIoTF or via the NEF.

[0605] In some embodiments, the 6G MCIoTF supports direct (e.g., local MCIoTF control) or indirect (e.g., via 3GPP US or NG-RAN) interaction with 6G massive IoT devices for wireless power supply services, and authorizes wireless power supply service operation requests after receiving wireless charging requests from 6G massive IoT devices.

[0606] In some embodiments, the 6G MCIoTF triggers a 3GPP UE or NG-RAN or MCIoTF to perform wireless charging operations for 6G massive IoT devices (e.g., activating or deactivating wireless charging as a wireless power supply device).

[0607] In some embodiments, the 6G MCIoTF reports service operation results to 6G MCIoT devices and / or 6G MCIoT service provider functions (via NEF) based on local configuration or 6G MCIoT service provider function requests.

[0608] In some embodiments, the 6G MCIoTF can send an Nmciotf_6G MCIoT_WPC response message (accept or reject, [reason code]) to a WPC device (e.g., UE, NG-RAN, or local 6G MCIoTF).

[0609] In step 3, the 6G MCIoTF confirms the WPC device (e.g., selects the 6G MCIoT wireless power supply device based on a request and / or operator policy, which can be selected directly or indirectly through the NRF; the WPC device can be a 3GPP UE, NG-RAN, or a local MCIoTF) to activate or deactivate the wireless charging operation.

[0610] In some embodiments, the wireless charging device (a 3GPP UE or NG-RAN or a local MCIoTF with wireless charging capability) is required to perform monitoring / measurement of subscription events for the 6G MCIoT wireless charging state:

[0611] - Wireless charging percentage, for example, periodically reported in each time window (5 minutes) to trigger percentage reporting;

[0612] - Wireless charging threshold, for example, up to 80%, to trigger percentage reporting;

[0613] - Wireless charging service operation becomes unreachable, fails, or succeeds, for example, if the unreachability (time and / or number of times) exceeds a threshold, triggering a WPC status report;

[0614] - Wireless charging is activated, for example, based on the contracted area or time window, the WPC capability of WPCE is activated;

[0615] - Wireless charging is deactivated, for example, based on the contracted region or time window, the WPC capability of WPCE is deactivated;

[0616] - Wireless charging service begins, for example, WPC service operation for 6G MCIoT by WPCE begins due to a request or event trigger (e.g., charging start time);

[0617] - Wireless charging service stops, for example, WPC service operation of WPCE for 6G MCIoT stops because of a request or event trigger (e.g., charging window timeout, or device battery threshold being reached).

[0618] In some embodiments, the monitoring / measurement results of 6G MCIoT wireless charging status events will be notified to the subscription consumer (e.g., 6G MCIoT ASP AF, or WPC security controller) directly or via NEF by the wireless charging device (3GPP UE or NG-RAN or local MCIoTF with wireless charging capability).

[0619] In step 4, the 6G MCIoTF sends a 6G MCIoT WPC request message (WPC request indication, WPC device ID, and information related to the target 6G MCIoT device) directly or via the AMF to the WPC device.

[0620] In step 5, the WPC device (e.g., UE, NG-RAN, or local 6G MCIoTF) sends a WPC start message to the 6G MCIoT device to initiate WPC operation for the target 6G MCIoT device.

[0621] In step 6, the MCIoT device sends a WPC response / reporting / stop message to the WPC device. The response / reporting / stop message may include charging results (e.g., failure, success, constraint), power status data, etc.

[0622] In step 7, in response, the WPC device (e.g., UE, NG-RAN, or local 6G MCIoTF) sends a WPC response message to the 6G MCIoTF directly or through a proxy function (e.g., AMF).

[0623] In step 8, according to the AF's subscription or operator policy (if applied), the 6G MCIoTF reports the result of the 6G MCIoT WPC request to the NEF by sending an Nmciotf_6G MCIoT_WPC notification message.

[0624] In step 9, NEF informs the 6G MCIoT WPC service provider function of the result of the 6G MCIoT WPC request by sending the Nnef_6G MCIoT_WPC notification message.

[0625] In step 10, the 6G MCIoTF sends a WPC response message to the 6G MCIoT device directly or through a proxy function (e.g., AMF) to notify the 6G MCIoT of the result of the WPC service and release resources.

[0626] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0627] In some embodiments, this disclosure provides a method for supporting 6G MCIoT wireless charging status monitoring and notification to support wireless charging of large-scale IoT devices, to support power consumption and management of 6G MCIoT devices, and to enable 6G MCIoT devices to capture sufficient energy from existing or deployed devices (UE, NG-RAN, or local 6G MCIoTF) in the environment to improve wireless energy capture efficiency and ensure stable and resilient wireless power supply for 6G MCIoT devices.

[0628] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus including units or modules for implementing the steps performed by the first node in any of the above methods. For example, this disclosure proposes an apparatus including units or modules for implementing the steps performed by the second node in any of the above methods. For example, this disclosure proposes an apparatus including units or modules for implementing the steps performed by the third node in any of the above methods.

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

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

[0631] Figure 7 This is a schematic diagram of the structure of a communication device provided according to an embodiment of this disclosure. For example... Figure 7 As shown, the communication device 700 may include at least one of the following: a transceiver module 701 and a processing module 702.

[0632] In some embodiments, the communication device 700 may be a first node. In some embodiments, the transceiver module 701 may be configured to: acquire first information, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, and the first device is a large-scale Internet of Things (IoT) device. Optionally, the transceiver module 701 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the first node in any of the above methods (e.g., steps S2103, S2105, S2108, S2109, S2110, S2112, S2114, S2201, S2204, S2205, S2206, S2208, S2210, S2212, but not limited thereto), which will not be elaborated here. Optionally, the processing module 702 is used to execute at least one of the other steps executed by the first node in any of the above methods (e.g., steps S2104, S2107, S2113, S2202, S2203, S2209, but not limited thereto), which will not be elaborated here.

[0633] In some embodiments, the communication device 700 can be a third node. In some embodiments, the transceiver module 701 can be configured to send first information to a first node, wherein the first information is used to request wireless charging for a first device, and the first device is a large-scale Internet of Things (IoT) device. Optionally, the transceiver module 701 can be used to perform at least one of the communication steps (e.g., steps S2101, S2103, S2105, S2108, S2112, S2114, S2115, S2201, S2204, S2208, S2210, S2211, S2212, but not limited thereto) performed by the third node in any of the above methods, which will not be elaborated here. Optionally, the processing module 702 is used to perform at least one of the other steps (e.g., steps S2103, S2104, S2107, S2202, S2203, but not limited thereto) performed by the third node in any of the above methods, which will not be elaborated here.

[0634] In some embodiments, Figure 7 The communication device shown can also be implemented as a communication equipment.

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

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

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

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

[0639] 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 such as sending and / or receiving in the above method (e.g., steps S2101, S2103, S2105, S2106, S2108, S2109, S2110, S2112, S2114, S2115, S2201, S2204, S2205, S2206, S2208, S2210, S2211, S2212, but not limited thereto), and the processor 8101 performs at least one of the other steps (e.g., steps S2102, S2104, S2107, S2111, S2113, S2202, S2203, S2207, S2209, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

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

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

[0642] Figure 8B This is a schematic diagram of the chip structure provided according to an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to... Figure 8B The diagram shown is a schematic representation of the structure of chip 8200, but it is not limited to this.

[0643] Chip 8200 includes one or more processors 8201. Chip 8200 is used to perform any of the methods described above.

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

[0645] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2103, S2105, S2106, S2108, S2109, S2110, S2112, S2114, S2115, S2201, S2204, S2205, S2206, S2208, S2210, S2211, S2212, but not limited thereto). The interface circuit 8202 performing the communication steps such as sending and / or receiving in the above method refers, for example, to the interface circuit 8202 performing 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 other steps (e.g., steps S2102, S2104, S2107, S2111, S2113, S2202, S2203, S2207, S2209, but not limited thereto).

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

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

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

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

Claims

1. A communication method, executed by a first node, wherein, The method includes: Obtain first information, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

2. The method according to claim 1, wherein, The first information indicates the first event.

3. The method according to claim 1 or 2, wherein, The first event includes at least one of the following: Events related to the wireless charging status of the first device; Events related to the business operations of the wireless charging service; Events related to the activation of wireless charging; Events related to the wireless charging service.

4. The method according to claim 3, wherein, Events related to the wireless charging status of the first device include at least one of the following: The power level of the first device meets the first condition; The periodic timer timed out.

5. The method according to claim 3 or 4, wherein, Events related to the operation of the wireless charging service include at least one of the following: The time during which the business operation is unavailable exceeds a threshold; The number of times the business operation was unreachable exceeded the threshold; Obtain indication information indicating that the business operation was successful; Obtain indication information indicating that the business operation has failed; The timer used for the aforementioned business operation timed out; There was no response to the business operation within the time window specified for the business operation.

6. The method according to any one of claims 3 to 5, wherein, Events associated with the activation of wireless charging include at least one of the following: The wireless charging capability of the first device is activated; The wireless charging capability of the first device is deactivated; The wireless charging capability of the second node is activated; The wireless charging capability of the second node is deactivated; The second node is used to wirelessly charge the first device.

7. The method according to any one of claims 3 to 6, wherein, Events related to the wireless charging service include at least one of the following: Obtain indication information indicating the start of the wireless charging service operation; Obtain indication information indicating that the wireless charging service operation should be stopped; The timer used to trigger wireless charging timed out; The timer used for the wireless charging service timed out; The power level of the first device meets the second condition.

8. The method according to any one of claims 2 to 7, wherein, The acquisition of the first information includes at least one of the following: Receive the first information sent by the third node; Obtain the first information from the local machine.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: Send a second message to a third node, wherein the second message indicates the result of monitoring for the first event.

10. The method according to claim 9, wherein, The results of monitoring the first event include at least one of the following: The power level of the first device; The wireless charging service is not operational. The wireless charging service operation failed. The wireless charging service operation was successful. The wireless charging capability of the first device is activated; The wireless charging capability of the first device is deactivated; The wireless charging capability of the second node is activated; The wireless charging capability of the second node is deactivated; The wireless charging service has commenced. The wireless charging service has been suspended. The second node is used to wirelessly charge the first device.

11. The method according to any one of claims 8 to 10, wherein, The third node includes at least one of the following: Application Function AF; Charging safety controller; MCIoTF (Massively Connected Internet of Things) is a large-scale communication IoT function.

12. The method according to claim 6 or 10, wherein, The first node is different from the second node; The method further includes: Send the first information to the second node; Receive second information sent by the second node, wherein the second information indicates the result of monitoring for the first event.

13. The method according to any one of claims 6, 10, and 12, wherein, The second node includes at least one of the following: Terminal equipment; Access network equipment; MCIoTF.

14. The method according to any one of claims 1 to 13, wherein, The first node includes at least one of the following: Terminal equipment; Access network equipment; MCIoTF.

15. A communication method, executed by a third node, wherein, The method includes: Send first information to a first node, wherein the first information is used to monitor a first event in a wireless charging service associated with a first device, the first device being a large-scale Internet of Things (IoT) device.

16. The method according to claim 15, wherein, The first information indicates the first event.

17. The method according to claim 15 or 16, wherein, The first event includes at least one of the following: Events related to the wireless charging status of the first device; Events related to the business operations of the wireless charging service; Events related to the activation of wireless charging; Events related to the wireless charging service.

18. The method according to claim 17, wherein, Events related to the wireless charging status of the first device include at least one of the following: The power level of the first device meets the first condition; The periodic timer timed out.

19. The method according to claim 17 or 18, wherein, Events related to the operation of the wireless charging service include at least one of the following: The time during which the business operation is unavailable exceeds a threshold; The number of times the business operation was unreachable exceeded the threshold; Obtain indication information indicating that the business operation was successful; Obtain indication information indicating that the business operation has failed; The timer used for the aforementioned business operation timed out; There was no response to the business operation within the time window specified for the business operation.

20. The method according to any one of claims 17 to 19, wherein, Events associated with the activation of wireless charging include at least one of the following: The wireless charging capability of the first device is activated; The wireless charging capability of the first device is deactivated; The wireless charging capability of the second node is activated; The wireless charging capability of the second node is deactivated; The second node is used to wirelessly charge the first device.

21. The method according to any one of claims 17 to 20, wherein, Events related to the wireless charging service include at least one of the following: Obtain indication information indicating the start of the wireless charging service operation; Obtain indication information indicating that the wireless charging service operation should be stopped; The timer used to trigger wireless charging timed out; The timer used for the wireless charging service timed out; The power level of the first device meets the second condition.

22. The method according to any one of claims 15 to 21, wherein, The method further includes: Receive second information sent by the first node, wherein the second information indicates the result of monitoring for the first event.

23. The method according to claim 22, wherein, The results of monitoring the first event include at least one of the following: The power level of the first device; The wireless charging service is not operational. The wireless charging service operation failed. The wireless charging service operation was successful. The wireless charging capability of the first device is activated; The wireless charging capability of the first device is deactivated; The wireless charging capability of the second node is activated; The wireless charging capability of the second node is deactivated; The wireless charging service has commenced. The wireless charging service has been suspended. The second node is used to wirelessly charge the first device.

24. The method according to claim 20 or 23, wherein, The second node includes at least one of the following: Terminal equipment; Access network equipment; MCIoTF (Massively Connected Internet of Things) is a large-scale communication IoT function.

25. The method according to any one of claims 15 to 24, wherein, The first node includes at least one of the following: Terminal equipment; Access network equipment; MCIoTF.

26. The method according to any one of claims 15 to 25, wherein, The third node includes at least one of the following: Application Function AF; Wireless charging safety controller; MCIoTF.

27. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1-14 and 15-26.

28. A communication system, wherein, The communication system includes at least one of the following: The first node is configured to perform the communication method as described in any one of claims 1-14; The third node is configured to perform the communication method as described in any one of claims 15-26.

29. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device implements the communication method as described in any one of claims 1-14 and 15-26.

30. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by the communication device, it implements the communication method as described in any one of claims 1-14 and 15-26.

Images