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

Abstract

The invention relates to a communication method and device, communication equipment, a storage medium and a program product. The method is performed by a first node and includes sending first information to a second node, where the first information is used to subscribe to a first event, the first event relating to reader-writer selection or reselection in large scale communications. Through the scheme of the invention, the reader-writer selection or reselection for the MC service can be realized.

Description

Technical Field

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

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

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

[0004] According to a first aspect of the present disclosure, a communication method is provided. The method is performed by a first node. The method includes sending first information to a second node, wherein the first information is used to subscribe to a reader change event, the reader change event being related to reader selection or reselection in large-scale communication.

[0005] According to a second aspect of the present disclosure, a communication method is provided. The method is performed by a second node. The method includes: receiving first information sent by a first node, wherein the first information is used to subscribe to a reader change event, the reader change event being related to reader selection or reselection in large-scale communication.

[0006] According to a third aspect of the present disclosure, a communication apparatus is provided. The apparatus is disposed at a first node. The apparatus includes a transceiver module. The transceiver module is configured to send first information to a second node, wherein the first information is used to subscribe to a reader / writer change event, the reader / writer change event being related to reader selection or reselection in large-scale communication.

[0007] According to a fourth aspect of the present disclosure, a communication apparatus is provided. The apparatus is disposed at a second node. The apparatus includes a transceiver module. The transceiver module is configured to receive first information sent by a first node, wherein the first information is used to subscribe to a reader / writer change event, the reader / writer change event being related to reader selection or reselection in large-scale communication.

[0008] According to a fifth aspect of this disclosure, a communication device is provided. The communication device includes: one or more processors; and a memory storing instructions. When executed by the device, the instructions cause the communication device to implement the communication method as described in the first or second aspect.

[0009] According to a sixth aspect of this disclosure, a communication system is provided. The communication system includes a first node and a second node. The first node is configured to perform the communication method as described in the first aspect. The second node is configured to perform the communication method as described in the second aspect.

[0010] According to a seventh 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 the first or second aspect.

[0011] According to an eighth aspect of the present disclosure, a program product is provided. When executed by a communication device, the program product causes the communication device to perform the communication method as described in the first or second aspect.

[0012] According to a ninth aspect of the present disclosure, a computer program is provided. When the computer program is run on a computer, it causes the computer to perform the communication method as described in the first or second aspect.

[0013] According to a tenth aspect of this 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 the first or second aspect.

[0014] According to embodiments of this disclosure, reader selection or reselection for MC services can be achieved.

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

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

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

[0018] Figures 2A to 2D This is a schematic diagram of the connection topology for AIoT.

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

[0020] Figure 4 This is a flowchart illustrating the communication method provided according to an embodiment of the present disclosure.

[0021] Figure 5 This is a flowchart illustrating the communication method provided according to an embodiment of the present disclosure.

[0022] Figure 6 This is a flowchart illustrating the communication method provided according to an embodiment of the present disclosure.

[0023] Figure 7A This is a flowchart illustrating the communication method provided according to an embodiment of the present disclosure.

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

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

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

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

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

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

[0030] In a first aspect, embodiments of this disclosure provide a communication method. The method is performed by a first node. The method includes: sending first information to a second node, wherein the first information is used to subscribe to a reader / writer change event, the reader / writer change event being related to reader selection or reselection in large-scale communication.

[0031] According to this embodiment, the first node can send first information to the second node to subscribe to reader change events related to reader selection in large-scale communication. In this way, the communication system can effectively detect reader change events and, in this case, perform reader selection and / or report the reader change events. This enables timely execution and notification of reader selection, reduces latency in the implementation of large-scale communication services, and improves network communication efficiency.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the event type may include at least one of the following: reader change; change of association between device and reader.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the reporting parameters may include at least one of the following: reporting content; reporting method; number of reporting times; maximum reporting duration; and reporting conditions.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the reported content may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; and second indication information for indicating a change in the association between the device and the reader.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the reporting conditions may include at least one of the following: a change in the reader; a change in the association between the device and the reader; a reporting trigger flag.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the triggering condition may include at least one of the following: a condition related to service completion; a condition related to service latency; a condition related to reader reachability; and a condition related to the number of service repetitions.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the service information may include at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving second information sent by the second node, wherein the second information is used to report the reader change event related to the previous selection or reselection of the reader.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the second information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for a reader change event.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving eighth information sent by the second node, wherein the eighth information is used to report reader change events related to the selected or reselected reader.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the first node may include at least one of the following: MCAF; PCF.

[0043] In a second aspect, embodiments of this disclosure provide a communication method. This method is executed by a second node. The method includes: receiving first information sent by a first node, wherein the first information is used to subscribe to a reader / writer change event, the reader / writer change event being related to reader selection or reselection in large-scale communication.

[0044] According to this embodiment, the first node can send first information to the second node to subscribe to reader change events related to reader selection in large-scale communication. In this way, the communication system can effectively detect reader change events and, in this case, perform reader selection and / or report the reader change events. This enables timely execution and notification of reader selection, reduces latency in the implementation of large-scale communication services, and improves network communication efficiency.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0046] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: sending second information to the first node, wherein the second information is used to report reader change events.

[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the second information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for the reader change event.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: determining the selected or reselected reader / writer.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: sending fourth information to a third node, wherein the fourth information is used to subscribe to a reader / writer change event; and receiving the third information sent by the third node.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the third node can be the previous reader or writer selected or reselected, and the fourth information is used to subscribe to reader change events related to the selected or reselected reader or writer.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the fourth information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the event type may include at least one of the following: reader change; change of association between device and reader.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the reporting parameters may include at least one of the following: reporting content; reporting method; number of reporting times; maximum reporting duration; and reporting conditions.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the reported content may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; and second indication information for indicating a change in the association between the device and the reader.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the reporting conditions may include at least one of the following: a change in the reader; a change in the association between the device and the reader; a reporting trigger flag.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the triggering condition may include at least one of the following: a condition related to service completion; a condition related to service latency; a condition related to reader reachability; and a condition related to the number of service repetitions.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the service information may include at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the third information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for the reader change event.

[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: sending fourth information to a fifth node, wherein the fourth information is used to subscribe to a reader change event; receiving third information sent by the fifth node; wherein the fifth node is a selected or reselected reader.

[0060] In conjunction with some embodiments of the second aspect, in some embodiments, the above method may further include: sending an eighth message to a first node, wherein the eighth message is used to report a reader change event related to the selected or reselected reader.

[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the second node may include at least one of the following: MCMF; AMF; UDM; NRF; NEF.

[0062] In a third aspect, embodiments of this disclosure provide a communication method. The method is executed by a third node. The method includes: executing a first service associated with at least one large-scale communication device; determining a reader change event trigger based on the execution result of the first service; and sending third information to a second node, wherein the third information is used to report the reader change event, the reader change event being related to reader selection or reselection in large-scale communication.

[0063] According to this embodiment, the third node can execute the first service and determine that a reader change event has been triggered. Then, the third node can send third information to the second node, reporting the reader change event related to reader selection in large-scale communication. (The last sentence appears to be incomplete and possibly refers to a separate, unrelated statement: "reader selection related in large-scale communication...")

[0064] In conjunction with some embodiments of the third aspect, in some embodiments, the third information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for the reader change event.

[0065] In conjunction with some embodiments of the third aspect, in some embodiments, the above method may further include: receiving fourth information sent by the second node, wherein the fourth information is used to subscribe to reader / writer change events.

[0066] In conjunction with some embodiments of the third aspect, in some embodiments, the fourth information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0067] In conjunction with some embodiments of the third aspect, in some embodiments, the event type may include at least one of the following: reader change; change of association between device and reader.

[0068] In conjunction with some embodiments of the third aspect, in some embodiments, the reporting parameters may include at least one of the following: reporting content; reporting method; number of reporting times; maximum reporting duration; and reporting conditions.

[0069] In conjunction with some embodiments of the third aspect, in some embodiments, the reported content may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; and second indication information for indicating a change in the association between the device and the reader.

[0070] In conjunction with some embodiments of the third aspect, in some embodiments, the reporting conditions may include at least one of the following: a change in the reader; a change in the association between the device and the reader; a reporting trigger flag.

[0071] In conjunction with some embodiments of the third aspect, in some embodiments, the triggering condition may include at least one of the following: a condition related to service completion; a condition related to service latency; a condition related to reader reachability; and a condition related to the number of service repetitions.

[0072] In conjunction with some embodiments of the third aspect, in some embodiments, service-related information may include at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

[0073] In conjunction with some embodiments of the third aspect, in some embodiments, the third node may include at least one of the following: UE; AN.

[0074] In a fourth aspect, embodiments of this disclosure provide a communication device. The device is disposed at a first node. The device includes a transceiver module. The transceiver module is configured to send first information to a second node, wherein the first information is used to subscribe to a reader / writer change event, the reader / writer change event being related to reader selection or reselection in large-scale communication.

[0075] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0076] In conjunction with some embodiments of the fourth aspect, in some embodiments, the event type may include at least one of the following: reader change; change of association between device and reader.

[0077] In conjunction with some embodiments of the fourth aspect, in some embodiments, the reporting parameters may include at least one of the following: reporting content; reporting method; number of reporting times; maximum reporting duration; and reporting conditions.

[0078] In conjunction with some embodiments of the fourth aspect, in some embodiments, the reported content may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; and second indication information for indicating a change in the association between the device and the reader.

[0079] In conjunction with some embodiments of the fourth aspect, in some embodiments, the reporting conditions may include at least one of the following: a change in the reader; a change in the association between the device and the reader; a reporting trigger flag.

[0080] In conjunction with some embodiments of the fourth aspect, in some embodiments, the triggering condition may include at least one of the following: a condition related to service completion; a condition related to service latency; a condition related to reader reachability; and a condition related to the number of service repetitions.

[0081] In conjunction with some embodiments of the fourth aspect, in some embodiments, service-related information may include at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

[0082] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module may also be configured to: receive second information sent by the second node, wherein the second information is used to report reader change events related to the previous selection or reselection of the reader.

[0083] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for a reader change event.

[0084] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module may also be configured to: receive an eighth message sent by the second node, wherein the eighth message is used to report a reader change event related to the selected or reselected reader.

[0085] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first node may include at least one of the following: MCAF; PCF.

[0086] In a fifth aspect, embodiments of this disclosure provide a communication device. The device is disposed at a second node. The device includes a transceiver module. The transceiver module is configured to receive first information sent by a first node, wherein the first information is used to subscribe to a reader / writer change event, the reader / writer change event being related to reader selection or reselection in large-scale communication.

[0087] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0088] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to send second information to the first node, wherein the second information is used to report reader change events.

[0089] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for a reader change event.

[0090] In conjunction with some embodiments of the fifth aspect, in some embodiments the above-described apparatus may further include a processing module, which may be configured to: determine the selected or reselected reader / writer.

[0091] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to: send fourth information to a third node, wherein the fourth information is used to subscribe to reader / writer change events; and receive third information sent by the third node.

[0092] In conjunction with some embodiments of the fifth aspect, in some embodiments, the third node can be the previous reader or writer selected or reselected, and the fourth information is used to subscribe to reader change events related to the selected or reselected reader or writer.

[0093] In conjunction with some embodiments of the fifth aspect, in some embodiments, the fourth information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0094] In conjunction with some embodiments of the fifth aspect, in some embodiments, the event type may include at least one of the following: reader change; change of association between device and reader.

[0095] In conjunction with some embodiments of the fifth aspect, in some embodiments, the reporting parameters may include at least one of the following: reporting content; reporting method; number of reporting times; maximum reporting duration; and reporting conditions.

[0096] In conjunction with some embodiments of the fifth aspect, in some embodiments, the reported content may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; and second indication information for indicating a change in the association between the device and the reader.

[0097] In conjunction with some embodiments of the fifth aspect, in some embodiments, the reporting conditions may include at least one of the following: a change in the reader; a change in the association between the device and the reader; a reporting trigger flag.

[0098] In conjunction with some embodiments of the fifth aspect, in some embodiments, the triggering condition may include at least one of the following: a condition related to service completion; a condition related to service latency; a condition related to reader reachability; and a condition related to the number of service repetitions.

[0099] In conjunction with some embodiments of the fifth aspect, in some embodiments, service-related information may include at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

[0100] In conjunction with some embodiments of the fifth aspect, in some embodiments, the third information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for the reader change event.

[0101] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module may also be configured to: send fourth information to the fifth node, wherein the fourth information is used to subscribe to reader change events; receive third information sent by the fifth node; wherein the fifth node is a selected or reselected reader.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the transceiver module may also be configured to: send an eighth message to the first node, wherein the eighth message is used to report a reader change event related to the selected or reselected reader.

[0103] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second node may include at least one of the following: MCMF; AMF; UDM; NRF; NEF.

[0104] In a sixth aspect, embodiments of this disclosure provide a communication apparatus. The apparatus is located at a third node. The apparatus includes a transceiver module and a processing module. The processing module is configured to: execute a first service associated with at least one large-scale communication device; and determine a reader change event trigger based on the execution result of the first service. The transceiver module is configured to send third information to a second node, wherein the third information is used to report the reader change event, which is related to reader selection or reselection in large-scale communication.

[0105] In conjunction with some embodiments of the sixth aspect, in some embodiments, the third information may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; second indication information for indicating a change in the association between the device and the reader; reporting method; number of reports; maximum reporting duration; reporting conditions; and triggering conditions for the reader change event.

[0106] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module may also be configured to: receive fourth information sent by the second node, wherein the fourth information is used to subscribe to reader / writer change events.

[0107] In conjunction with some embodiments of the sixth aspect, in some embodiments, the fourth information may include at least one of the following: event type; reporting parameters; triggering conditions; business information.

[0108] In conjunction with some embodiments of the sixth aspect, in some embodiments, the event type may include at least one of the following: reader change; change of association between device and reader.

[0109] In conjunction with some embodiments of the sixth aspect, in some embodiments, the reporting parameters may include at least one of the following: reporting content; reporting method; number of reporting times; maximum reporting duration; and reporting conditions.

[0110] In conjunction with some embodiments of the sixth aspect, in some embodiments, the reported content may include at least one of the following: first identification information for indicating the selected or reselected reader; second identification information for indicating the changed association between the device and the reader; first indication information for indicating a change in the reader; and second indication information for indicating a change in the association between the device and the reader.

[0111] In conjunction with some embodiments of the sixth aspect, in some embodiments, the reporting conditions may include at least one of the following: a change in the reader; a change in the association between the device and the reader; a reporting trigger flag.

[0112] In conjunction with some embodiments of the sixth aspect, in some embodiments, the triggering condition may include at least one of the following: a condition related to service completion; a condition related to service latency; a condition related to reader reachability; and a condition related to the number of service repetitions.

[0113] In conjunction with some embodiments of the sixth aspect, in some embodiments, service-related information may include at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

[0114] In conjunction with some embodiments of the sixth aspect, in some embodiments, the third node may include at least one of the following: UE; AN.

[0115] In a seventh aspect, embodiments of this disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the first aspect and its possible embodiments.

[0116] In an eighth aspect, embodiments of this disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the second aspect and its possible embodiments.

[0117] In a ninth aspect, embodiments of this disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When executed by the communication device, the instructions cause the communication device to implement the communication method as described in any of the third aspect and its possible embodiments.

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

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

[0120] In a twelfth aspect, embodiments of this disclosure provide a program product. When executed by a communication device, the program product causes the communication device to perform the communication method as described in any of the first, second, third, and possible embodiments thereof.

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

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

[0123] It is understood that the aforementioned communication devices, communication equipment, 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.

[0124] This disclosure provides a communication method and apparatus, 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 device, network device, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0146] 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 node 101, a second node 102, a third node 103, and a fourth node 104.

[0147] In some embodiments, the first node 101 can be used to initiate massive communication (MC) services.

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

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

[0150] In some embodiments, the first node 101 can be used to make strategic decisions for MC services.

[0151] In some embodiments, the first node 101 may be, for example, a policy control function (PCF).

[0152] In some embodiments, the second node 102 can be used to control MC services.

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

[0154] In some embodiments, the second node 102 may be, for example, the controller of the MC device.

[0155] In some embodiments, the second node 102 may be used to implement functions such as MC device registration, reader registration, AF authentication and authorization, AF verification, reader selection, disk request forwarding and disk result transmission, command request and command response forwarding, data collection, and reader information storage.

[0156] In some embodiments, the third node 103 can be used to trigger the MC device to perform MC services.

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

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

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

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

[0161] In some embodiments, the first node 101 may be a server, core network equipment, etc. It is understood that the first node 101 may also be other types of equipment, which will not be specifically described in this disclosure.

[0162] In some embodiments, the second node 102 may be a terminal, an access network device, a core network device, etc. It is understood that the second node 102 may also be other types of devices, which are not specifically described in this disclosure.

[0163] In some embodiments, the third node 103 may be a terminal, an access network device, etc. It is understood that the third node 103 may also be other types of devices, which are not specifically described in this disclosure.

[0164] In some embodiments, the fourth node 104 may be a sensor, an electronic tag, a terminal, etc. It is understood that the fourth node 104 may also be other types of devices, which are not specifically described in this disclosure.

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

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

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

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

[0169] The following embodiments of this disclosure can be applied to Figure 1 The 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.

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

[0171] In recent years, with the widespread application of IoT technology in the field of wireless communication, higher demands have been placed on the size, complexity, power, and other performance aspects of IoT devices. In particular, IoT devices often require built-in energy storage devices such as batteries. This necessitates manual battery replacement or charging of IoT devices. Clearly, this not only increases the maintenance costs of IoT devices but also reduces their convenience.

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

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

[0174] In some embodiments, there are multiple connection topologies for AIoT devices. Figures 2A to 2D This is a schematic diagram of the connection topology for AIoT. (Example) Figures 2A to 2D As shown, there are typically four different connection topologies for AIoT devices.

[0175] In some embodiments, such as Figure 2A As shown, the first connection topology (or Topology 1, First Type Topology) can 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 can include AIoT service-related data and / or signaling. In the first connection topology, the transmission from the base station to the AIoT device can be the same as or different from the transmission from the AIoT device to the base station.

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

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

[0178] In some embodiments, such as Figure 2D As shown, the fourth link topology (or Topology 4, Fourth Type 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 may include AIoT service data and / or signaling.

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

[0180] Massive communication is a development direction for IoT technology. Due to limitations in complexity and power consumption, it is necessary to select or reselect suitable readers to trigger AIoT devices to execute AIoT services, thereby meeting the latency and availability requirements associated with AIoT services.

[0181] Therefore, how to select the reader / writer for MC services is an urgent problem to be solved.

[0182] Figure 3 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 3 As shown, the communication method of this embodiment includes steps S301 to S309.

[0183] In some embodiments, the first node 101 may be an AF. In one example, the first node 101 may be an MCAF. In some embodiments, the first node 101 may be a PCF.

[0184] In some embodiments, the second node 102 may be a controller. In some embodiments, the second node 102 may include at least one of the following: access and mobility management function (AMF), massive communication management function (MCMF), unified data management function (UDM), network repository function (NRF), and network exposure function (NEF). In some embodiments, the AMF included in the second node 102 may be an enhanced AMF. In some embodiments, the MCMF included in the second node 102 may be an AIoT management function (AIoTMF) or an AIoT function (AIoTF). The AIoTMF (or AIoTF) can be used to manage AIoT services and AIoT devices.

[0185] In some embodiments, MCMF may also be referred to as massive communication function (MCF).

[0186] In some embodiments, the third node 103 may be a reader / writer. In some embodiments, the third node 103 may include at least one of the following: a terminal, an access network device.

[0187] In some embodiments, the fourth node 104 may be an MC device. For example, the fourth node 104 may be an AIoT device.

[0188] In some embodiments, the first node 101 may be an AF (Active AMF), and the second node 102 may include at least an enhanced AMF (Active AMF). In one example, the first node 101 may be an AF, and the second node 102 may include enhanced AMF, PCF (Active PCF), and NEF (Active NEF). In one example, the first node 101 may be an AF, and the second node 102 may include enhanced AMF, PCF, NEF, and UDM (Active UDM). In one example, the first node 101 may be an AF, and the second node 102 may include enhanced AMF, PCF, NEF, and NRF (Active NRF). In some embodiments, the first node 101 may be an AF, and the second node 102 may include at least an MCMF (Active MCMF). In one example, the first node 101 may be an AF, and the second node 102 may include MCMF, PCF, and NEF. In one example, the first node 101 may be an AF, and the second node 102 may include MCMF, PCF, NEF, and NRF.

[0189] In some embodiments, the first node 101 may be a PCF, and the second node 102 may include at least an enhanced AMF. In one example, the first node 101 may be a PCF, and the second node 102 may include an enhanced AMF and a UDM. In some embodiments, the first node 101 may be a PCF, and the second node 102 may include at least an MCMF. In one example, the first node 101 may be a PCF, and the second node 102 may include an MCMF and a UDM.

[0190] In step S301, the third node 103 sends the fifth message to the second node 102.

[0191] In some embodiments, the second node 102 may receive the fifth information.

[0192] In some embodiments, the fifth information may be used to indicate that the third node 103 supports large-scale communication. In some embodiments, the fifth information may be used to determine that the third node 103 has the capability to trigger MC services.

[0193] In some embodiments, the name of the fifth piece of information is not limited, and it may be, for example, capability information, capability indication information, etc.

[0194] In some embodiments, the fifth information can be sent via a reporting process. In one example, the third node 103 can send the fifth information to the second node 102 via a reporting message.

[0195] In some embodiments, the fifth information can be sent through a registration process. In one example, the third node 103 can send the fifth information to the second node 102 via a registration message.

[0196] In some embodiments, the fifth message may be sent to at least one of AMF, MCMF, UDM, NRF, and NEF.

[0197] In some embodiments, the number of third nodes 103 can be one or more. Each third node 103 can send fifth information to the second node 102.

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

[0199] In some embodiments, the second node 102 may receive the first information.

[0200] In some embodiments, the first information can be used to implement subscription for a first event. In some embodiments, the first information can be used to request reporting of the first event. In some embodiments, the first information can be used to support reader / writer selection. In some embodiments, the first information can be used to implement a subscription strategy for the first event.

[0201] In some embodiments, the first event may be related to reader selection in large-scale communication. In some embodiments, reader selection may include the selection and / or reselection of a reader. In some embodiments, reader selection may be referred to as reader selection or reselection, or reader selection and reselection, and this disclosure does not specifically limit it in this way.

[0202] In some embodiments, the first event is associated with reader selection, and reader selection causes a reader change. Therefore, the first event can also be referred to as the reader change event.

[0203] In some embodiments, the name of the first information is not limited, and it may be, for example, subscription instruction information, subscription information, subscription request information, etc.

[0204] In some embodiments, the first information may include at least one of the following: event type, reporting parameters, triggering conditions, and business information.

[0205] In some embodiments, the first information may include at least one of the following: event type information, reporting parameter information, event triggering information, and business-related information.

[0206] In some embodiments, event type information may be used to indicate the event type of the first event.

[0207] In some embodiments, the event type may include at least one of the following: reader change, association change between device and reader.

[0208] In some embodiments, a reader change can refer to a change in the reader used to trigger the MC device to perform MC services. For example, for a specific MC device, switching from one reader to another may be used to trigger the MC device to perform MC services.

[0209] In some embodiments, an association relationship may exist between the MC device and the reader / writer. This association relationship may also be referred to as a device-reader / writer association. In some embodiments, a reader / writer may be associated with one or more MC devices. In some embodiments, the MC device associated with a reader / writer may change. For example, an MC device that is associated with a reader / writer may no longer be associated with that reader / writer. For example, the reader / writer may be associated with a new MC device. In this case, the association between the device and the reader / writer changes.

[0210] In some embodiments, event type information may indicate subscription for a first event of type reader change. In some embodiments, event type information may indicate subscription for a first event of type change in the association between the device and the reader.

[0211] Understandably, the event type can also be considered to express what kind of event the first event is. For example, the first event could be a reader / writer change. Alternatively, the first event could be a change in the association between the device and the reader / writer. Furthermore, reader / writer changes and changes in the association between the device and the reader / writer are both related to reader / writer selection.

[0212] In some embodiments, the reported parameter information may be used to indicate the reported parameters associated with the first event.

[0213] In some embodiments, the reporting parameter information can be used to configure the reporting of the first event.

[0214] In some embodiments, the reporting parameter information may include at least one of the following: reporting content, reporting method, number of reporting times, maximum reporting duration, and reporting conditions.

[0215] In some embodiments, the reported content is information reported in response to the first event.

[0216] In some embodiments, the reported content may include at least one of the following: first identification information, second identification information, first instruction information, and second instruction information.

[0217] In some embodiments, the first identification information can be used to indicate the changed reader / writer. For example, if the first event may include a reader / writer change, the reported content may include the first identification information to indicate the changed reader / writer.

[0218] In some embodiments, the first indication information can be used to indicate a change in the reader / writer. For example, if the first event includes a change in the reader / writer, the reported content may include the first indication information to indicate that the change in the reader / writer has occurred.

[0219] In some embodiments, when the first event includes a change in the reader / writer, the reported content may include both the first identification information and the first indication information, or it may include only the first identification information or the first indication information.

[0220] In some embodiments, the second identification information can be used to indicate the changed association between the device and the reader. For example, if the first event may include a change in the association between the device and the reader, the reported content may include the second identification information to indicate the changed association between the device and the reader.

[0221] In some embodiments, the second indication information can be used to indicate a change in the association between the device and the reader. For example, if the first event may include a change in the association between the device and the reader, the reported content may include the second indication information to indicate the change in the association between the device and the reader.

[0222] In some embodiments, when the first event includes a change in the association between the device and the reader, the reported content may include both the second identification information and the second indication information, or it may include only the second identification information or the second indication information.

[0223] In some embodiments, the reporting method may be a method of reporting the first event.

[0224] In some embodiments, the reporting method may include at least one of the following: periodic reporting or immediate reporting.

[0225] In some embodiments, periodic reporting may refer to periodic reporting in response to the triggering of a first event.

[0226] In some embodiments, immediate reporting may mean reporting immediately when the first event is triggered.

[0227] In some embodiments, the number of reports can be the number of times a first event is reported.

[0228] In some embodiments, for periodic reporting, the number of reports may include the total number of periodic reports. In this case, once the total number of periodic reports has been reached, no further reporting is required.

[0229] In some embodiments, for an immediate reporting method, the number of reports may include the number of repetitions of the report. In this case, the number of times a report is made for a single triggering of the first event may be the number of repetitions.

[0230] In some embodiments, the maximum reporting time may be the maximum duration for reporting the first event.

[0231] In some embodiments, the maximum reporting time may include the maximum duration of a single report.

[0232] In some embodiments, for periodic reporting methods, the maximum reporting time may include the maximum total duration of periodic reporting.

[0233] In some embodiments, for immediate reporting, the maximum reporting time may include the maximum total duration of repeated reporting.

[0234] In some embodiments, the reporting condition may be the condition that triggers the reporting of the first event.

[0235] In some embodiments, the reporting conditions may include at least one of the following: reader change, change of association between device and reader, and reporting trigger flag.

[0236] In some embodiments, the reporting condition can be a change in the reader / writer, in which case a report can be triggered when the reader / writer changes.

[0237] In some embodiments, the reporting condition may be a change in the association between the device and the reader, in which case a reporting can be triggered when the association between the device and the reader changes.

[0238] In some embodiments, the reporting condition can be a reporting trigger flag, which can immediately trigger a report. In this case, the report triggered by the reporting trigger flag can be used to indicate whether there is a change in the reader / writer and / or whether there is a change in the association between the device and the reader / writer.

[0239] In some embodiments, the triggering condition may include conditions for determining whether to trigger and / or report a first event. In one example, the triggering condition may be referred to as an event filter or detection criterion.

[0240] In some embodiments, the triggering condition may include at least one of the following: a first condition, a second condition, a third condition, and a fourth condition.

[0241] In some embodiments, the first condition may be related to the degree of business completion.

[0242] In some embodiments, the first condition may be related to the completion level of the first service. In one example, the first service may include the MC service.

[0243] In some embodiments, the first condition may include a service completion threshold. Based on the service completion threshold, it can be determined whether the first condition is met. In one example, service completion may be measured by the number of MC devices implementing the first service. In another example, service completion may be the ratio of the number of MC devices implementing the first service to the total number of all MC devices related to the first service. For example, if all MC devices related to the first service implement the first service, the service completion rate is 100%. For example, if half of the MC devices related to the first service implement the first service, the service completion rate is 50%. In one example, the service completion threshold may be set to 70%, 80%, 90%, or other values; this disclosure does not impose specific limitations on the embodiments. In some embodiments, the first condition is met when the service completion rate is less than the service completion threshold; the first condition is not met when the service completion rate is greater than or equal to the service completion threshold.

[0244] In some embodiments, the first condition may include service success. Service success may, for example, mean that all MC devices perform the first service. In some embodiments, if the service is successful, the first condition is not met; if the service is unsuccessful (or fails), the first condition is met.

[0245] In some embodiments, the second condition may be related to service latency.

[0246] In some embodiments, the second condition may include a service delay threshold. Based on the service delay threshold, it can be determined whether the second condition is met. In some embodiments, the service delay may be the length of time between the start and completion of the first service. In some embodiments, the service delay threshold may be the maximum length of time between the start and completion of the first service. In one example, the maximum length of time may be a time window. For example, the length of the time window may be 5 seconds. In some embodiments, the second condition is met if the completion time of the first service exceeds the service window, i.e., the service delay of the first service is greater than the service delay threshold; the second condition is not met if the completion time of the first service does not exceed the service window, i.e., the service delay of the first service is less than or equal to the service delay threshold.

[0247] In some embodiments, the third condition may be related to reader reachability. In some embodiments, the third condition may be related to reader coverage and / or reachability.

[0248] In some embodiments, the third condition may be related to reader coverage. In some embodiments, the third condition may include whether the reader is covered by the second node 102, i.e., whether the second node 102 covers the reader. In one example, the second node 102 does not cover the reader, so the third condition is satisfied. In another example, the second node 102 covers the reader, so the third condition is not satisfied.

[0249] In some embodiments, the third condition may be related to the reachability of the reader. In some embodiments, the third condition may include whether the reader is reachable from the second node 102 (i.e., whether there is a connection between the reader and the second node 102). In one example, the reader is reachable from the second node 102, and the third condition is satisfied. In another example, the reader is not reachable from the second node 102, and the third condition is not satisfied.

[0250] In some embodiments, the fourth condition may be related to the number of times the business is repeated.

[0251] In some embodiments, the fourth condition may include the maximum number of times the first service is repeatedly executed. Based on the maximum number of times, it can be determined whether the fourth condition is met. In some embodiments, the fourth condition is met if the number of times the first service is repeatedly executed exceeds the maximum number of times; the fourth condition is not met if the number of times the first service is repeatedly executed does not exceed the maximum number of times.

[0252] In some embodiments, business-related information may include information related to the implementation of the first business.

[0253] In some embodiments, the service-related information may include information required to implement the first service. Based on the service-related information, the first node 101 may also request the second node 102 to implement the first service.

[0254] In some embodiments, service-related information may include at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

[0255] In some embodiments, the device category can be a category of MC devices. In some embodiments, the device category can include at least one of the following: conventional MC devices, high-latency devices, AIoT devices, NB-IoT devices, and high-capability devices. In some embodiments, the MC device category can be divided into machine-type communication devices, high-capability machine-type MC devices, etc. In some embodiments, the AIoT device category can be divided into Class 1 AIoT devices, Class 2A AIoT devices, Class 2B AIoT devices, etc. In some embodiments, high-latency devices can be divided into one or more latency levels. In some embodiments, the device category can also include the mobility characteristics of the MC device. For example, the MC device category can be divided into high-mobility devices, low-mobility devices, fixed devices, etc.

[0256] In some embodiments, the service type can be the type of a first service. In some embodiments, the service type of the first service can include at least one of the following: inventory, command. In some embodiments, the command can include at least one of the following: read, write, disable. It is understood that the first service can also have other types, and this disclosure does not specifically limit them.

[0257] In some embodiments, the device identifier may be used to identify the MC device performing the first service. In some embodiments, the device identifier may include at least one of the following: device identifier, device identifier group, and group identifier.

[0258] In some embodiments, a device identifier can be used to identify an MC device. In one example, there can be a one-to-one correspondence between the device identifier and the MC device. Each MC device can be uniquely identified by a device identifier.

[0259] In some embodiments, a device identifier group can be used to identify one or more MC devices. In one example, the device identifier group may include one or more device identifiers, and each device identifier may be used to uniquely identify an MC device.

[0260] In some embodiments, a group identifier can be used to identify one or more groups of MC devices. In some embodiments, multiple MC devices can be grouped according to device manufacturer, device vendor, region, etc.

[0261] In some embodiments, group identification can be implemented using a mask. In one example, a mask can be used to identify the manufacturer and / or distributor. In another example, a mask can be used to identify a specific region.

[0262] In some embodiments, device selection criteria can be used to select an MC device.

[0263] In some embodiments, the device selection criteria may be the filtering criteria of the MC device used to perform the first service.

[0264] In some embodiments, device selection criteria may include group identifiers and identifier lists.

[0265] In some embodiments, the group identifier can be used to identify a specific device type or a specific application provider. In one example, the group identifier can be used to identify an MC device with a specific device type. In another example, the group identifier can be used to identify an MC device managed by a specific application provider.

[0266] In some embodiments, the group identifier may be implemented using a mask.

[0267] In some embodiments, the identifier list may include device identifiers for one or more MC devices. In some embodiments, the identifier list may be a whitelist. In one example, the identifier list may be used to filter out MC devices included in the identifier list. In some embodiments, the identifier list may be a blacklist. In one example, the identifier list may be used to filter out MC devices included in the identifier list.

[0268] In some embodiments, the service location may be a location related to the implementation of the first service. In some embodiments, the service location may be indicated by location information. In some embodiments, the service location may include at least one of the following: the region of the first service, the region of the third node 103, the region of the second node 102, and the region of the first node 101.

[0269] In some embodiments, the region of the first service may be the region to which the implementation of the first service is targeted. In other words, the first service may be implemented for MC devices in that region. In some embodiments, the application service provider may be a provider of application services based on MC services. In some embodiments, the application service provider may be associated with the first node 101. In one example, the first node 101 may be deployed by the application service provider. The region of the first node 101 may be the region where the application service provider is located. In some embodiments, the region of the second node 102 may be the region where the controller is located. In one example, the region of the second node 102 may include the region where at least one of AMF, MCMF, UDM, NRF, and NEF is located. In some embodiments, the region of the second node 102 may be the region served by the controller. In one example, the region of the second node 102 may include the region served by at least one of AMF, MCMF, UDM, NRF, and NEF. In some embodiments, the region of the third node 103 may be the region of the reader / writer. In some embodiments,

[0270] In some embodiments, the service time may include the time for performing a first service. In some embodiments, the service time may include at least one of the following: a time threshold and a service cycle. In some embodiments, the time threshold may be the maximum duration for performing the first service. In some embodiments, the service cycle may be the execution period of the first service when it is performed periodically. In one example, the service cycle may be used to indicate the time interval between two executions of the first service.

[0271] In some embodiments, the topology type may be the topology used to implement the first service. In some embodiments, the topology type may include at least one of the following: a first-type topology, a second-type topology, a third-type topology, and a fourth-type topology. In some embodiments, a first-type topology may include a base station and an MC device. In one example, a first-type topology may be topology 1. In some embodiments, a second-type topology may include a base station, an intermediate node, and an MC device. In one example, a second-type topology may be topology 2. In some embodiments, a third-type topology may include a base station, an auxiliary node, and an MC device. In one example, a third-type topology may be topology 3. In some embodiments, a fourth-type topology may include a terminal and an MC device. In one example, a fourth-type topology may be topology 4.

[0272] In some embodiments, topology priority can be used to represent the priority of different types of topologies. In some embodiments, topology priority can be used to select from at least one type of topology. When multiple types of topologies exist, topology priority can be used to implement topology selection.

[0273] In some embodiments, topology priority may include absolute priority. In some embodiments, topology priority may include the priority corresponding to at least one of the following topologies: a first type of topology, a second type of topology, a third type of topology, and a fourth type of topology. In one example, topology priority may include the priority of each of the following topologies: a first type of topology, a second type of topology, a third type of topology, and a fourth type of topology.

[0274] In some embodiments, topology priority may include relative priority. In some embodiments, topology priority may include the priority relationship between any two types of topologies selected from the first type, second type, third type, and fourth type.

[0275] In some embodiments, topology priority can be used to determine the preferred topology among different types of topologies. In one example, topology priority can be used to indicate a topology that is the most preferred topology.

[0276] In some embodiments, the priority of different types of topologies can be the same or different. In some embodiments, in topology prioritization, the priority of different types of topologies can be the same or different.

[0277] In some embodiments, non-homogeneous network support may refer to whether a first service supports non-homogeneous networks.

[0278] In some embodiments, only one type of topology may be deployed in a homogeneous network. In some embodiments, the third node 103 and / or the fourth node 104 in the homogeneous network may be associated with the same type of topology.

[0279] In some embodiments, multiple types of topologies can be deployed in a non-homogeneous network. In some embodiments, a third node 103 and / or a fourth node 104 in a non-homogeneous network can be associated with at least two types of topologies.

[0280] In some embodiments, non-homogeneous network support can be indicated using indication information. In one example, the indication information may include one bit. For example, a bit value of 1 indicates that non-homogeneous networks are supported. For example, a bit value of 0 indicates that non-homogeneous networks are not supported. In one example, the presence or absence of the indication information can be used to indicate whether non-homogeneous networks are supported. For example, the presence of the indication information indicates that non-homogeneous networks are supported. For example, the absence of the indication information indicates that non-homogeneous networks are not supported.

[0281] In some embodiments, where heterogeneous networks are supported, terminal-type readers can be selected as intermediate nodes, and base station-type readers can also be selected to implement the first service. In some embodiments, other types of readers can be selected during the reader rewriting process.

[0282] In some embodiments, reader selection information can be used to indicate the association of reader selection.

[0283] In some embodiments, reader selection may be associated with a service group. In some embodiments, reader selection information may indicate a service group. During the reader selection process, readers whose subscription information pertains to the service group may be given priority.

[0284] In some embodiments, reader selection may be associated with a business area for a business group. In some embodiments, reader selection information may indicate a business area. During the reader selection process, readers whose subscription information pertains to a business area may be given priority.

[0285] In some embodiments, the service area may be the service area upon which the MC service is based. In some embodiments, the service area may include at least one of the following: the service area of ​​the first node 101, the service area of ​​the second node 102, and the service area of ​​the fourth node 104. In one example, a service group may correspond to one or more service areas of the first node 101. In one example, a service group may correspond to one or more service areas of the second node 102. In one example, a service group may correspond to one or more service areas of the fourth node 104.

[0286] In some embodiments, multi-network support can be for supporting readers and writers deployed in multiple networks. In the case of multiple networks, multiple fourth nodes 104 can belong to different networks, multiple third nodes 103 can belong to different networks, multiple second nodes 102 can belong to different networks, and first node 101, second node 102, and third node 103 can belong to different networks.

[0287] In some embodiments, where multiple networks are supported, the reader before and after selection can belong to different networks.

[0288] In some embodiments, multiple networks may include networks of multiple operators. In one example, multiple networks may consist of networks of multiple operators.

[0289] In some embodiments, multiple networks may include multiple types of networks. In one example, multiple networks may include public networks and private networks.

[0290] In some embodiments, the first node 101 may include at least one of AF and PCF. In some embodiments, the first information may be sent by at least one of AF and PCF.

[0291] In some embodiments, the second node 102 may include at least one of AMF, MCMF, UDM, NRF, and NEF. In some embodiments, the first information may be sent to at least one of AMF, MCMF, UDM, NRF, and NEF.

[0292] In some embodiments, the process of the first node 101 sending the first information to the second node 102 may include, but is not limited to: AF sending the first information to NEF; AF sending the first information to AMF; AF sending the first information to MCMF; PCF sending the first information to AMF; PCF sending the first information to MCMF.

[0293] In some embodiments, the second node 102 may include multiple network elements from AMF, MCMF, UDM, NRF, and NEF. In this case, the first information can be transmitted within the second node 102. For example, the first information can be transmitted between AMF, MCMF, UDM, NRF, and NEF. In one example, NEF can send the first information to AMF. In one example, NEF can send the first information to MCMF. In one example, AMF can send the first information to UDM. In one example, AMF can send the first information to NRF. In one example, MCMF can send the first information to UDM. In one example, MCMF can send the first information to NER. In one example, AMF can send the first information to MCMF. In one example, MCMF can send the first information to AMF.

[0294] In some embodiments, the first node 101 may be an AF. In some embodiments, the AF may send first information to the NEF. The NEF may perform discovery and selection of an AMF or MCMF to determine the AMF or MCMF. Subsequently, the NEF may send the received first information to the selected AMF or MCMF. In some embodiments, the MCAF may send the first information directly to the AMF or MCMF through the NEF.

[0295] In some embodiments, through step S302, the first node 101 can configure the subscription of the first event on the second node 102.

[0296] In some embodiments, while the first node 101 sends the first information to the second node 102, the first node 101 may also send service request information for the first service to the second node 102. For example, the service request information and the first information may be included in the same message. The service request information is used to request the execution of the first service. In some embodiments, the service request information may include at least one of the following: description information of the first service, and requirement information of the first service.

[0297] It is understood that business-related information can be included in business request information, and this disclosure does not specifically limit this.

[0298] In step S303, the second node 102 determines the third node 103.

[0299] In some embodiments, the second node 102 may determine the third node 103 based on the first information and / or service request information.

[0300] In some embodiments, the third node 103 may be determined by AMF or MCMF.

[0301] In some embodiments, the second node 102 may include an AMF (Advanced Management Function), and the third node 103 may be determined by the AMF. In some embodiments, the AMF may interact with a UDM (User Demographic Module) to verify the AF (Automatic Request) and the first service. In some embodiments, the AMF may interact with an NRF (Network Request Function) to verify the capabilities of the third node 103 and the first service. Based on the verification results from the UDM and / or NRF, the AMF may perform discovery and selection of the third node 103 according to service request information and / or service-related information to determine the third node 103.

[0302] In some embodiments, the second node 102 may include an MCMF, and the third node 103 may be determined by the MCMF. In some embodiments, the MCMF may interact with a UDM to verify the AF and the first service. In some embodiments, the MCMF may interact with an NRF to verify the capabilities of the third node 103 and the first service. Based on the verification results from the UDM and / or NRF, the MCMF may perform discovery and selection of the third node 103 according to service request information and / or service-related information to determine the third node 103.

[0303] In some embodiments, the second node 102 may authorize the AF to trigger services. In some embodiments, the second node 102 may authorize the AF as the triggerer of a first service. In this case, the second node 102 may authorize the AF to perform operations such as disk storage, reading, writing, and invalidation on the fourth node 104.

[0304] In some embodiments, authorization for the AF can be determined based on the contract information stored in the UDM.

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

[0306] In some embodiments, the third node 103 may receive fourth information.

[0307] In some embodiments, the fourth information can be used by the second node 102 to trigger the third node 103 to implement the first service.

[0308] In some embodiments, the fourth information may be used to request the third node 103 to perform the first service.

[0309] In some embodiments, the fourth information may be used to implement a subscription for the first event.

[0310] In some embodiments, the name of the fourth information is not limited, and it may be, for example, business request information, subscription instruction information, subscription information, subscription request information, etc.

[0311] In some embodiments, the second node 102 may determine to subscribe to the first event from the third node 103. In this case, the second node 102 may send fourth information to the third node 103 to subscribe to the first event.

[0312] In some embodiments, the fourth information may include at least one of the following: event type information, reporting parameter information, event triggering information, and business-related information.

[0313] It should be noted that the fourth information may include the first information, or a part of the first information, and this disclosure does not specifically limit this.

[0314] In some embodiments, through step S304, the second node 102 can configure the subscription of the first event on the third node 103.

[0315] In some embodiments, the third node 103 may include at least one of the following: a reader / writer, a master reader / writer, or a relay reader / writer.

[0316] In some embodiments, the reader can be used to perform operations on the first service of the fourth node 104, including inventory operations, command operations, etc.

[0317] In some embodiments, the master reader can be used to manage one or more readers.

[0318] In some embodiments, a relay reader / writer can be an intermediate node between the second node 102 and other readers / writers, responsible for the transmission of signaling and / or data between the second node 102 and other readers / writers. For example, a relay reader / writer can be an intermediate node in a second-type topology and / or a third-type topology.

[0319] In some embodiments, the third node 103 may be implemented by a terminal. In some embodiments, the third node 103 may be implemented by a base station.

[0320] In some embodiments, the number of third nodes 103 can be one or more.

[0321] In some embodiments, the number of third nodes 103 can be multiple. In one example, the second node 102 can configure a subscription to the first event for each third node 103 individually. For example, the second node 102 can send the fourth information individually to each third node 103. In one example, the second node 102 can configure a subscription to the first event for multiple third nodes 103 together. For example, the second node 102 can send the fourth information to multiple third nodes 103 simultaneously. For example, the fourth information can be sent in a multicast, broadcast, or other manner.

[0322] In step S305, the third node 103 interacts with the fourth node 104.

[0323] In some embodiments, the third node 103 can interact with the fourth node 104 to implement the first service.

[0324] In some embodiments, the fourth node 104 may be determined by the second node 102. In some embodiments, the fourth node 104 may be determined by the second node 102 based on information provided by the first node 101 and / or operator policies.

[0325] In some embodiments, the type of the first service may be determined by the second node 102. In some embodiments, the type of the first service may be determined by the second node 102 based on information provided by the first node 101 and / or operator policies.

[0326] In some embodiments, step S305 may include: the third node 103 sending a sixth message to the fourth node 104; and the fourth node 104 sending a seventh message to the third node 103.

[0327] In some embodiments, the sixth information can be used to trigger the fourth node 104 to perform the first service. In some embodiments, the sixth information can be used to trigger the fourth node 104 to perform inventory operations and / or command operations. In some embodiments, the sixth information can be used to trigger the fourth node 104 to perform read, write, invalidate, or other operations.

[0328] In some embodiments, the seventh information may be used to indicate the execution result of the fourth node 104 for the first service.

[0329] In some embodiments, the interaction between the third node 103 and the fourth node 104 can be performed multiple times to implement the execution flow of the first service multiple times. In some embodiments, the number of interactions between the third node 103 and the fourth node 104 can be determined based on service and / or operator policies.

[0330] In step S306, the third node 103 determines that the first event is triggered.

[0331] In some embodiments, the third node 103 may determine the triggering of the first event based on the execution result of the first service obtained in step S305.

[0332] In some embodiments, the third node 103 may determine the triggering of the first event based on the first information and the execution result of the first service. In some embodiments, the third node 103 may determine the triggering of the first event based on the execution result of the first service and taking into account the first information.

[0333] In some embodiments, the third node 103 can determine, based on the obtained execution result, that the triggering condition indicated by the event triggering information has been met, and determine that the first event has been triggered. In some embodiments, the triggering condition may include at least one of a first condition, a second condition, a third condition, and a fourth condition.

[0334] In some embodiments, if any one of the first condition, second condition, third condition, and fourth condition is satisfied, the third node 103 may determine that the first event is triggered.

[0335] In some embodiments, the first condition may include a service completion threshold. In some embodiments, the service completion may be related to the third node 103. In some embodiments, the number or percentage of fourth nodes 104 that successfully execute the first service implemented by the third node 103 is the service completion. If the service completion of the first service does not exceed (or does not reach) the service completion threshold of the first condition, the third node 103 may determine that a first event is triggered. For example, if the number of fourth nodes 104 that receive the execution result for the first service is less than the completion threshold, the first condition is satisfied. For example, if the number of fourth nodes 104 that successfully execute the first service is less than the completion threshold, the first condition is satisfied.

[0336] In some embodiments, the second condition may include a service latency threshold. In some embodiments, if the service time for the fourth node 104 to successfully execute the first service exceeds the service latency threshold, the third node 103 may determine that the first event has been triggered.

[0337] In some embodiments, the third condition may include reader coverage and / or reachability. In some embodiments, the first event is triggered when the second node 102 does not cover the third node 103. In some embodiments, the third node 103 may determine that the first event has been triggered when the third node 103 is unreachable from the second node 102.

[0338] In some embodiments, the fourth condition may include the maximum number of times the first service is executed. In some embodiments, if the number of times the third node 103 triggers the execution of the first service exceeds the maximum number, the third node 103 may determine that the first event has been triggered.

[0339] In some embodiments, any combination of the first condition, the second condition, the third condition, and the fourth condition can be used by the third node 103 to determine the triggering of the first event.

[0340] In some embodiments, the first condition and the second condition can be combined. In some embodiments, if the completion rate of the first service does not exceed (or does not reach) the completion rate threshold within the time window corresponding to the service delay threshold, the third node 103 can determine that the first event is triggered.

[0341] In step S307, the third node 103 sends third information to the second node 102.

[0342] In some embodiments, the second node 102 may receive third information.

[0343] In some embodiments, third information can be used to report the first event.

[0344] In some embodiments, the third information may include at least one of the following: first identification information, second identification information, first instruction information, second instruction information, reporting method, number of reports, maximum reporting duration, reporting conditions, and triggering conditions for the first event.

[0345] In some embodiments, the third information may be sent when the third node 103 determines that the first event has been triggered. In some embodiments, when the second node 102 sends fourth information to the third node 103 to configure the third node 103 to report the first event, the third node 103 may send the third information when the first event has been triggered.

[0346] In some embodiments, the third node 103 may determine whether the first event is triggered based on the execution result of the first service from the fourth node 104.

[0347] In some embodiments, while the third node 103 sends the third information to the second node 102, the third node 103 may also send the execution result of the first service to the second node 102. For example, the third information and the execution result of the first service may be included in the same message. In some embodiment sets, after receiving the execution result from the fourth node 104, the third node 103 may send the execution result to the second node 102.

[0348] In some embodiments, after receiving the execution result from the fourth node 104, the third node 103 can process the execution result to obtain a processed result. Then, the third node 103 can send the processed execution result to the second node 102.

[0349] In some embodiments, the execution result may include at least one of the following: the result of the inventory operation, the result of the command operation, and environmental data.

[0350] In some embodiments, the result of the inventory operation may include identification information of one or more fourth nodes 104.

[0351] In some embodiments, the command operation may include writing. For example, the result of the command operation may include whether the writing was successful.

[0352] In some embodiments, a command operation may include reading. For example, the result of a command operation may include the read data.

[0353] In some embodiments, the command operation may include invalidity. For example, the result of the command operation may include whether the fourth node 104 is invalid.

[0354] In some embodiments, the environmental data may include at least one of the following: environmental data of the third node 103 and environmental data of the fourth node 104.

[0355] It should be noted that in some embodiments, the second node 102 may not subscribe to the reporting of the first event from the third node 103. In this case, step S306 may not be executed. In one example, in step S307, the third node 103 may only send the execution result.

[0356] In step S308, the second node 102 determines the reader / writer selection.

[0357] In some embodiments, the second node 102 may determine the reader selection after receiving third information and / or the execution result of the first service from the third node 103.

[0358] In some embodiments, the second node 102 may obtain the execution result and / or third information of the first service from the third node 103. In this case, the second node 102 may determine the execution reader selection based on the first information and the execution result and / or third information of the first service. For example, the second node 102 may determine the execution reader selection based on the execution result and / or third information of the first service, taking the first information into consideration. In some embodiments, the second node 102 may not subscribe to the reporting of the first event from the third node 103. In this case, the third node 103 may send the execution result of the first service, and the second node 102 may determine the execution reader selection based on the first information and the execution result. In some embodiments, the second node 102 may subscribe to the reporting of the first event from the third node 103. In this case, the third node 103 may send third information, and the second node 102 may determine the execution reader selection based on the first information and the third information. In some embodiments, the second node 102 may subscribe to the reporting of the first event from the third node 103. In this case, the third node 103 can send the third information and the execution result of the first service, and the second node 102 can determine the execution reader selection based on the first information, the third information, and the execution result of the first service.

[0359] In some embodiments, the second node 102 may consider carrier policies and / or local configurations when determining the execution reader / writer selection process.

[0360] In some embodiments, the second node 102 may determine that the triggering condition indicated by the event triggering information has been met, and determine that a first event has been triggered. In some embodiments, the triggering condition may include at least one of a first condition, a second condition, a third condition, and a fourth condition.

[0361] In some embodiments, if any one of the first condition, second condition, third condition, or fourth condition is satisfied, the second node 102 may determine that the first event is triggered.

[0362] In some embodiments, the first condition may include a business completion threshold. In some embodiments, the business completion may be related to the second node 102. In some embodiments, the number or percentage of fourth nodes 104 that successfully execute the first business implemented by the second node 102 is the business completion. If the business completion of the first business does not exceed (or does not reach) the business completion threshold of the first condition, the second node 102 may determine that a first event is triggered. For example, if the second node 102 determines that the number of fourth nodes 104 with execution results for the first business is lower than the completion threshold, then the first condition is satisfied. For example, if the number of fourth nodes 104 that successfully execute the first business is lower than the completion threshold, then the first condition is satisfied.

[0363] In some embodiments, the second condition may include a service latency threshold. In some embodiments, if the service time for the second node 102 to perform the first service exceeds the service latency threshold, the second node 102 may determine that the first event has been triggered. In some embodiments, if the service time for the third node 103 to perform the first service exceeds the service latency threshold, the second node 102 may determine that the first event has been triggered.

[0364] In some embodiments, the third condition may include reader coverage and / or reachability. In some embodiments, the first event is triggered when the second node 102 does not cover the third node 103. In some embodiments, the third node 103 may determine that the first event has been triggered when the third node 103 is unreachable from the second node 102.

[0365] In some embodiments, the fourth condition may include the maximum number of times the first service is executed. In some embodiments, if the number of times the third node 103 triggers the execution of the first service exceeds the maximum number, the second node 102 may determine that the first event has been triggered. In some embodiments, if the number of times the second node 102 requests to execute the first service exceeds the maximum number, the second node 102 may determine that the first event has been triggered.

[0366] In some embodiments, any combination of the first condition, the second condition, the third condition, and the fourth condition can be used by the second node 102 to determine the triggering of the first event.

[0367] In some embodiments, the first condition and the second condition can be combined. In some embodiments, if the completion rate of the first service does not exceed (or does not reach) the completion rate threshold within the time window corresponding to the service delay threshold, the second node 102 can determine that the first event is triggered.

[0368] In some embodiments, the second node 102 can determine the triggering of the first event based on third information. In some embodiments, the third information can be used to report the triggering of the first event. In this case, the second node 102 can directly determine the triggering of the first event based on the third information.

[0369] In some embodiments, upon determining that a first event has been triggered, the second node 102 may determine to perform a reader / writer selection.

[0370] In some embodiments, the second node 102 may perform reader discovery and selection in response to a first event to identify another third node 103.

[0371] In step S309, the second node 102 sends the second information to the first node 101.

[0372] In some embodiments, the first node 101 may receive second information.

[0373] In some embodiments, the second information may be used to implement the reporting of the first event.

[0374] In some embodiments, the second information may be sent by the second node 102 upon the triggering of the first event. In some embodiments, the second information may be sent by the second node 102 upon determining that a reader / writer selection has been performed.

[0375] In some embodiments, the second information may include at least one of the following: first identification information, second identification information, first instruction information, second instruction information, reporting method, number of reports, maximum reporting duration, reporting conditions, and triggering conditions for the first event.

[0376] In some embodiments, the first node 101 may include at least one of AF and PCF. In some embodiments, second information may be sent to at least one of AF and PCF.

[0377] In some embodiments, the second node 102 may include at least one of AMF, MCMF, UDM, NRF, and NEF. In some embodiments, the second information may be sent by at least one of AMF, MCMF, UDM, NRF, and NEF.

[0378] In some embodiments, the process of the second node 102 sending the second information to the first node 101 may include, but is not limited to: the AMF sending the second information to the AF; the AF sending the second information to the PCF; the MCMF sending the second information to the AF; the MCMF sending the second information to the PCF; and the NEF sending the second information to the AF.

[0379] In some embodiments, the second node 102 may include multiple network elements from AMF, MCMF, UDM, NRF, and NEF. In this case, the second information can be transmitted within the second node 102. For example, the second information can be transmitted between AMF, MCMF, UDM, NRF, and NEF. In one example, AMF can send the second information to NEF. In one example, MCMF can send the second information to NEF. In one example, AMF can send the second information to MCMF. In one example, MCMF can send the second information to AMF.

[0380] In some embodiments, the first node 101 may be an AF. In some embodiments, the AMF or MCMF may send second information to the NEF upon determining that a first event has been triggered. The NEF may then send the received second information to the AF.

[0381] The communication method of this embodiment can be realized through the above steps S301 to S309.

[0382] It should be noted that steps S304 to S309 trigger and report the first event related to the third node 103. The third node 103 is the reader / writer selected and reselected before the selection. In some embodiments, after completing steps S304 to S309, the communication system 100 can continue to trigger and report the first event for the reader / writer selected or reselected in step S308 (e.g., the fifth node, not shown). For example, steps S304 to S309 can be executed again for the selected or reselected reader / writer. In this way, the second node 102 can send the eighth message to the first node 101 to report the first event related to the selected or reselected reader / writer. The specific details of the triggering and reporting of the first event for the selected or reselected reader / writer can be found in steps S304 to S309, and will not be repeated here.

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

[0384] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

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

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

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

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

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

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

[0391] In some embodiments, terms such as "service" and "business" can be used interchangeably.

[0392] The communication method involved in the embodiments of this disclosure may include at least one of steps S301 to S309. For example, step S302 may be implemented as a standalone embodiment. For example, step S304 may be implemented as a standalone embodiment. For example, step S306 may be implemented as a standalone embodiment. For example, step S307 may be implemented as a standalone embodiment. For example, step S309 may be implemented as a standalone embodiment. For example, a combination of steps S302 and S309 may be implemented as a standalone embodiment. For example, a combination of steps S304 and S307 may be implemented as a standalone embodiment. For example, a combination of steps S304, S306, and S307 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S301 to S309 are not limited thereto.

[0393] In some embodiments, steps S301, S303, S304, S305, S306, S307, S308, and S309 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S301, S302, S303, S304, S305, S306, S307, and S308 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0394] In some embodiments, see Figure 3 Other optional implementation methods described before or after the corresponding instruction manual.

[0395] Figure 4 This is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. This communication method is executed by a first node 101. For example... Figure 4 As shown, the above method includes steps S401 to S402.

[0396] In step S401, the first information is sent.

[0397] For optional implementations of step S401, please refer to [link / reference]. Figure 3 Optional implementations of step S302, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0398] In some embodiments, the first node 101 may send the first information to the second node 102, but is not limited thereto; it may also send the first information to other entities.

[0399] In some embodiments, the first information may be used to implement a subscription for a first event.

[0400] In step S402, the second information is obtained.

[0401] For optional implementations of step S402, please refer to [link / reference]. Figure 3 Optional implementations of step S309, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

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

[0403] The communication method involved in the embodiments of this disclosure may include at least one of steps S401 to S402. For example, step S401 may be implemented as a standalone embodiment. For example, a combination of steps S401 and S402 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S401 to S402 are not limited thereto.

[0404] In some embodiments, step S402 is optional and may be omitted or replaced in different embodiments.

[0405] Figure 5 This is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. This communication method is executed by the second node 102. For example... Figure 5 As shown, the above method includes steps S501 to S507.

[0406] In step S501, the fifth piece of information is obtained.

[0407] For optional implementations of step S501, please refer to [link / reference]. Figure 3 Optional implementations of step S301, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0408] In some embodiments, the second node 102 may receive the fifth information sent by the third node 103, but is not limited thereto, and may also receive the fifth information sent by other entities.

[0409] In step S502, the first information is obtained.

[0410] For optional implementations of step S502, please refer to [link / reference]. Figure 3 Optional implementations of step S302, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

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

[0412] In step S503, the third node is determined.

[0413] For optional implementations of step S503, please refer to Figure 3 Optional implementations of step S303, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0414] In step S504, the fourth message is sent.

[0415] For optional implementations of step S504, please refer to [link / reference]. Figure 3 Optional implementations of step S304, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0416] In some embodiments, the second node 102 may send fourth information to the third node 103, but is not limited thereto; it may also send fourth information to other entities.

[0417] In step S505, third information is obtained.

[0418] For optional implementations of step S505, please refer to [link / reference]. Figure 3 Optional implementations of step S307, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

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

[0420] In step S506, the reader selection is determined.

[0421] For optional implementations of step S506, please refer to [link / reference]. Figure 3 Optional implementations of step S308, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0422] In some embodiments, reader selection may be determined based on third-party information.

[0423] In step S507, the second information is sent.

[0424] For optional implementations of step S507, please refer to [link / reference]. Figure 3 Optional implementations of step S309, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0425] In some embodiments, the second node 102 may send second information to the first node 101, but is not limited thereto, and may also send second information to other entities.

[0426] The communication method involved in the embodiments of this disclosure may include at least one of steps S501 to S507. For example, step S502 may be implemented as a standalone embodiment. For example, step S504 may be implemented as a standalone embodiment. For example, step S505 may be implemented as a standalone embodiment. For example, step S507 may be implemented as a standalone embodiment. For example, a combination of steps S502 and S507 may be implemented as a standalone embodiment. For example, a combination of steps S504 and S505 may be implemented as a standalone embodiment. For example, a combination of steps S502, S506, and S507 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S501 to S507 are not limited thereto.

[0427] In some embodiments, steps S501, S503, S504, S505, S506, and S507 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S501, S502, S503, S505, S506, and S507 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S501, S502, S503, S504, S506, and S507 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S501, S502, S503, S504, S505, and S506 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0428] Figure 6 This is a flowchart illustrating a communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method. This communication method is executed by a third node 103. For example... Figure 6 As shown, the above method includes steps S601 to S604.

[0429] In step S601, the fourth information is obtained.

[0430] For optional implementations of step S601, please refer to [link / reference]. Figure 3 Optional implementations of step S304, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0431] In some embodiments, the third node 103 may receive fourth information sent by the second node 102, but is not limited thereto, and may also receive fourth information sent by other entities.

[0432] In step S602, interaction with the fourth node occurs.

[0433] For optional implementations of step S602, please refer to [link / reference]. Figure 3 Optional implementations of step S305, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0434] In step S603, the first event is determined to be triggered.

[0435] For optional implementations of step S603, please refer to [link / reference]. Figure 3 Optional implementations of step S306, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0436] In step S604, the third message is sent.

[0437] For optional implementations of step S604, please refer to [link / reference]. Figure 3 Optional implementations of step S307, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0438] The communication method involved in the embodiments of this disclosure may include at least one of steps S601 to S604. For example, step S602 may be implemented as a standalone embodiment. For example, step S603 may be implemented as a standalone embodiment. For example, step S604 may be implemented as a standalone embodiment. For example, a combination of steps S602 and S603 may be implemented as a standalone embodiment. For example, a combination of steps S601, S602, and S603 may be implemented as a standalone embodiment. It should be noted that the possible standalone embodiments consisting of one or more steps S601 to S604 are not limited thereto.

[0439] In some embodiments, steps S601, S603, and S604 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S601, S602, and S604 are optional, and one or more of these steps may be omitted or substituted in different embodiments. In some embodiments, steps S601, S602, and S603 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0440] Figure 7AThis is a flowchart illustrating a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. For example... Figure 7A As shown, the above method includes step S7101.

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

[0442] For optional implementations of step S7101, please refer to [link / reference]. Figure 3 Optional implementations of step S302, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0443] Figure 7B This is a flowchart illustrating a communication method provided according to an embodiment of this disclosure. Embodiments of this disclosure relate to communication methods. For example... Figure 7B As shown, the above method includes steps S7201 to S7203.

[0444] In step S7201, the third node 103 executes the first service.

[0445] For optional implementations of step S6701, please refer to [link / reference]. Figure 3 Optional implementations of step S305, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0446] In step S7202, the third node 103 determines that the first event is triggered.

[0447] For optional implementations of step S7202, please refer to [link / reference]. Figure 3 Optional implementations of step S306, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

[0448] In step S7203, the third node 103 sends third information to the second node 102.

[0449] For optional implementations of step S7203, please refer to [link / reference]. Figure 3 Optional implementations of step S307, and Figure 3 Other related parts in the embodiments involved will not be described in detail here.

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

[0451] In some embodiments, this disclosure provides a reader selection and reselection event subscription strategy (i.e., reader selection and / or reselection event subscription and triggering) for large-scale communications (e.g., AIoT) to support MC services and thereby effectively meet latency and accessibility requirements.

[0452] In some embodiments, for large-scale communications, the monitoring event is intended to be used to monitor reader selection and reselection in the 3GPP system, and to report the monitoring event via AMF, AioTF, UDM, reader (including RAN and UE determined by CN), NEF, and PCF.

[0453] In some embodiments, this feature sequentially detects specific events by the UE / NF (e.g., reader, AIoTF, AMF, PCF, NEF) and reports the events to the consumer (i.e., the requester).

[0454] In some embodiments, monitoring events related to reader selection and reselection can be provided by the reader, AIoTF, AMF, PCF, or NEF, and can be reported via NEF.

[0455] Figure 8 This is an interactive schematic diagram illustrating an exemplary implementation of the communication method provided according to embodiments of the present disclosure. This communication method can implement reader / writer selection and reselection subscriptions and notifications. For example... Figure 8 As shown, the method may include steps S801 to S814.

[0456] In step S801, the source reader and the target reader report or register MC capabilities with the network (e.g., AMF / MCMF (AIoTMF), UDM, NRF). It is understood that step S801 is optional.

[0457] In step S802, MCAF sends a service request (subscription event) to NEF.

[0458] In some embodiments, the MCMF sends service requests (e.g., inventory checks) for MC devices to the MC service (e.g., AIoT service) controller (e.g., directly or via NEF). The request message includes at least one of the information described below to support the reader selection and reselection event subscription strategy (i.e., the subscription and triggering of reader selection and reselection events). Furthermore, the reader is a device for large-scale communication, such as an AIoT device.

[0459] In some embodiments, the request message may include a subscription event or event type (i.e., event type information) indicating the content to be reported for reader selection and reselection, including: reader change (new reader information, reader change indication); device-reader association change (new device-reader association, device-reader association change indication).

[0460] In some embodiments, the request message may include event reporting information. Event reporting information may include: information about the new reader (e.g., reader ID); a reader change indication; a new device-reader association (e.g., device-reader association ID); a device-reader association change indication; an event reporting mode; the number of reports; the maximum reporting duration; and event reporting conditions (e.g., when the reader changes, when the device-reader association changes, or an immediate reporting flag for changes).

[0461] In some embodiments, an event filter (detection criterion) serves as an event triggering or reporting condition. An event filter may include:

[0462] - The reader / writer changes its threshold (i.e., the first condition) for completing a service, for example, when the service response rate is below 70% or the service is successful. For continuous services, if the device or network receives less than 70% of service responses or confirms less than 70% of services, a new reader / writer can be selected.

[0463] - A threshold (i.e., the second condition) is set for reader / writer latency, for example, a time window after the start of the service. After the time window has elapsed (e.g., 5 seconds), a new reader / writer can be selected.

[0464] - A threshold (i.e., a third condition) is changed for readers with no coverage and / or no available connection, for example, a time window with no coverage and / or no available connection. After the time window has expired, a new reader can be selected.

[0465] - For repeated transactions, the reader / writer threshold changes (i.e., the fourth condition). For example, if the number of repeated transactions exceeds the limit, a new reader / writer can be selected to continue the transaction.

[0466] In some embodiments, events can be detected by preferred network functions, such as AMF, AIoTF, UDM, a reader / writer including RAN and UE (determined by CN), NEF, and PCF.

[0467] In some embodiments, MCAF may include the following information to assist in the implementation of services:

[0468] - Device category / information, for example, 1) Device category, including general MC devices, high-latency devices, AIoT devices, NB-IoT devices, and high-capability devices; 2) Detailed device type, including machine-type communication devices, machine-type high-capability MC devices; Class 1, Class 2A, and Class 2B AIoT devices; latency level of high-latency devices; device mobility characteristics.

[0469] - Business type, such as inventory and commands (including read, write, invalid) for AIoT business.

[0470] - Device ID or ID group. The device ID can be the device ID of a single device, a group of device IDs, or multiple device IDs with mask filtering conditions (e.g., masking to identify manufacturers or vendors, or devices in a specific area).

[0471] - Business related to filtering criteria, such as group IDs and / or mask IDs, a list of device IDs defined by the AF or operator; group IDs and / or mask IDs can identify the type of device, or the application service provider, or a part of a type / AF of devices.

[0472] - Location information, such as business area (service area of ​​the business, service area of ​​the reader / writer, service area of ​​the business controller, or service area of ​​the application service provider).

[0473] - Thresholds or periodic values ​​for business execution.

[0474] - Supported topologies, connectivity topologies may include, for example: Topology 1, i.e., base station <—> AIoT device; Topology 2, i.e., base station <—> intermediate node <—> AIoT device (only UE can be used as an intermediate node under network control); Topology 3, i.e., base station <—> auxiliary node <—> AIoT device <—> base station; Topology 4, i.e., UE <—> AIoT device.

[0475] - Topology preferences (topology 1, topology 2, topology 3, topology 4) are applied to the deployment of multiple topology readers and topology selections in a network.

[0476] - Whether to allow services to support non-homogeneous networks. For example, if services to support non-homogeneous networks are allowed, then UE readers as intermediate nodes and base station readers can be selected to implement services, and different reader types can be selected during the reselection process.

[0477] - Reader selection associations, for example, associations with service groups, such as service areas for service groups. If a target service group is selected, the controller can preferentially select candidate readers, with the selected candidate readers subscribed to the service area (e.g., AIoT service capabilities) or the selected candidate readers subscribed to the service group.

[0478] - Support for readers on multiple networks. For example, if readers supporting multiple networks are allowed, AF can trigger services through readers and / or network functions on different carrier networks. For example, the reader for the service and the reader for reselection can belong to different carriers.

[0479] In step S803, if the request is sent to the network via NEF, NEF can query NRF to enable enhanced AMF and / or MCMF (AIoTMF) discovery and selection. It is understood that step S803 is optional.

[0480] In step S804, the NEF sends a service request for the MC service (e.g., an AIoT service) to the enhanced AMF and / or MCMF (AIoTMF). This request may include subscribed events, event reporting information, and filters from the MCAF in step S802.

[0481] In step S805, the enhanced AMF and / or MCMF interact with the UDM and / or NRF to select a service reader (source reader). For example, the enhanced AMF and / or MCMF interact with the UDM to verify capabilities and services. Taking into account the subscription information in the UDM (and / or NRF responses) and the requirements provided by the MCAF, the enhanced AMF and / or MCMF will discover and select a service reader. It is understood that step S805 is optional.

[0482] In some embodiments, the network (e.g., service controller) NF (e.g., reader, AIoTF, AMF, PCF, UDM, NEF) configures events, detects and reports events to consumers (e.g., requesters).

[0483] In some embodiments, the configuration / detection events may include: reader change, device-reader association change.

[0484] In some embodiments, the event reporting information may include: information about the new reader (e.g., reader ID); reader change indication; new device-reader association (e.g., device-reader association ID); device-reader association change indication; event reporting mode; number of reports; maximum reporting duration; event reporting conditions (e.g., when the reader changes, when the device-reader association changes, or an immediate reporting flag for changes).

[0485] In some embodiments, event filters (detection criteria) are provided as event triggering or reporting conditions. Event filters may include:

[0486] - The threshold for reader / writer completion is changed, for example, when the number of service responses or service successes falls below 70%. For continuous services, if the number of service responses received by the device or network falls below 70%, or the number of confirmed services falls below 70%, a new reader / writer can be selected.

[0487] - Reader latency thresholds for business operations can be adjusted, for example, by setting a time window after the business begins. After the time window expires (e.g., 5 seconds), a new reader can be selected.

[0488] - For readers with no coverage and / or no available connection, the threshold is changed, for example, a time window with no coverage and / or no available connection. After the time window has expired, a new reader can be selected.

[0489] - For readers with repeated business operations, the threshold can be changed. For example, if the number of repeated business operations exceeds the limit, a new reader can be selected to continue the business.

[0490] In some embodiments, when an event reporting condition is met (e.g., an event filter is triggered), the NF (e.g., a reader, AIoTF, AMF, PCF, UDM, NEF) reports the event to the consumer (e.g., the requester), including the event, event reporting information, etc.

[0491] In some embodiments, the AIoT controller (including enhanced AMF / MCMF, and / or UDM, and / or NRF, and / or NEF) authorizes the MCAF as a service trigger, for example, requesting an inventory of devices for an AIoT service.

[0492] In step S806, the enhanced AMF and / or MCMF (AIoTMF) sends service requests for MC devices (e.g., AIoT devices) to the selected reader. For example, if the enhanced AMF and / or MCMF (AIoTMF) determines that the reader and reader association in the subscribed reading has changed, the enhanced AMF and / or MCMF (AIoTMF) configures the relevant events in the reader or master / relay reader as described in step S805. If multiple readers are selected, they can be configured jointly or independently.

[0493] In step S807, the reader interacts with the device to implement the MC service. The service type and device can be determined by the MCMF (AIoTMF) / AMF / PCF, taking into account information provided by the MCAF and / or operator policies. Based on the service and operator policies, the service process for the reader and device can be executed once or multiple times.

[0494] In step S808, the reader replies with service results to the enhanced AMF and / or MCMF (AIoTMF), such as the stored device ID, command results, and environmental data collected by the device or reader. In some embodiments, if configured in step S806 and triggered by an event, the reader can also perform event reporting.

[0495] In step S809, the enhanced AMF and / or MCMF (AIoTMF) determine the reselected reader (target reader) after considering event reporting. For example, event triggers may include: less than 70% service response or service success, exceeding a time window (e.g., 5 seconds), exceeding a time window of no coverage and / or no available connection, exceeding the number of service repetitions, etc.

[0496] In step S810, the reader reselection event in the 3GPP system can be notified to consumers, such as third parties or MCAFs. If monitoring is performed by the reader, the event notification can be provided directly or via NEF through AMF / MCMF (AIoTMF), UDM, NEF, PCF, NRF, or the reader (including RAN and UE, determined by CN as an intermediate node or relay node).

[0497] In step S811, the enhanced AMF and / or MCMF (AIoTMF) sends a service request to the target reader. The enhanced AMF and / or MCMF (AIoTMF) sends the service request for the MC device (e.g., an AIoT device) to the selected reader. The relevant details are similar to those in step S806.

[0498] In step S812, the newly selected reader / writer interacts with the device to continue the MC service, for example, the same service type and device as determined in step S807 by MCMF (AIoTMF) / AMF / PCF. Based on service and operator policies, the service process for the reader / writer and device can be executed once or multiple times. It is understood that step S812 is optional.

[0499] In step S813, the newly selected reader / writer replies with a service result, such as the stored device ID, command result, or environmental data collected by the device or reader / writer. In some embodiments, if configured in step S810 and triggered by an event, the reader / writer can also report an event. It is understood that step S813 is optional.

[0500] In step S814, the enhanced AMF and / or MCMF (AIoTMF) notifications are sent to the subscribed events (event reporting). These reader reselection events are notified to consumers, such as third parties or MCAs. It is understood that step S814 is optional.

[0501] In some embodiments, as described in steps S802 and S804, if monitoring is performed by a reader, event notification can be provided directly or via NEF through AMF / MCMF (AIoTMF), UDM, NEF, PCF, NRF, or the reader (including RAN and UE, determined by CN as an intermediate node or relay node).

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

[0503] This disclosure also provides communication devices for implementing any of the above methods. For example, this disclosure provides a communication device including units or modules for implementing the steps performed by a first node in any of the above methods. For example, this disclosure provides a communication device including units or modules for implementing the steps performed by a second node in any of the above methods. For example, this disclosure provides a communication device including units or modules for implementing the steps performed by a third node in any of the above methods.

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

[0505] In this disclosure, 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.

[0506] Figure 9 This is a schematic diagram of the structure of a communication device provided according to an embodiment of this disclosure. Figure 9 As shown, the communication device 900 may include at least one of the following: a transceiver module 901 and a processing module 902.

[0507] In some embodiments, the communication device 900 may be a first node 101. In some embodiments, the transceiver module 901 is configured to send first information to a second node, wherein the first information is used to subscribe to a first event, the first event being related to reader / writer selection in large-scale communication. Optionally, the transceiver module 901 may be configured to perform at least one of the communication steps (e.g., steps S302, S309, but not limited thereto) performed by the first node 101 in any of the above methods, which will not be elaborated further here.

[0508] In some embodiments, the communication device 900 may be a second node 102. In some embodiments, the transceiver module 901 is configured to receive first information sent by a first node, wherein the first information is used to subscribe to a first event, the first event being related to reader / writer selection in large-scale communication. Optionally, the transceiver module 901 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second node 102 in any of the above methods (e.g., steps S301, S302, S304, S307, S309, but not limited thereto), which will not be elaborated here. Optionally, the processing module 902 may be configured to perform at least one of the other steps performed by the second node 102 in any of the above methods besides the communication steps such as sending and / or receiving (e.g., steps S303, S308, but not limited thereto), which will not be elaborated here.

[0509] In some embodiments, the communication device 900 may be a third node 103. In some embodiments, the processing module 902 is configured to: execute a first service associated with at least one large-scale communication device; and determine a first event trigger based on the execution result of the first service. The transceiver module 901 is configured to send third information to a second node, wherein the third information is used to report the first event, which is related to reader selection in large-scale communication. Optionally, the transceiver module 901 may be configured to execute at least one of the communication steps (e.g., steps S301, S304, S305, S307, but not limited thereto) executed by the third node 103 in any of the above methods, which will not be elaborated here. Optionally, the processing module 902 may be configured to execute at least one of the other steps (e.g., step S306, but not limited thereto) executed by the third node 103 in any of the above methods, excluding communication steps such as sending and / or receiving, which will not be elaborated here.

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

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

[0512] Figure 10AThis is a schematic diagram of the structure of a communication device provided according to an embodiment of this disclosure. The communication device 10100 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 10100 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.

[0513] like Figure 10A As shown, the communication device 10100 includes one or more processors 10101. The processor 10101 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 10100 can be used to execute any of the above methods. Optionally, one or more processors 10101 can be used to invoke instructions to cause the communication device 10100 to execute any of the above methods.

[0514] In some embodiments, the communication device 10100 further includes one or more transceivers 10102. When the communication device 10100 includes one or more transceivers 10102, the transceiver 10102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S301, S302, S304, S305, S307, S309, but not limited thereto), and the processor 10101 performs at least one of other steps (e.g., steps S303, S306, S308, 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.

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

[0516] The communication device 10100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 10100 described in this disclosure is not limited thereto, and the structure of the communication device 10100 may vary. Figure 10A 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.

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

[0518] Chip 10200 includes one or more processors 10201. Chip 10200 is used to perform any of the above methods.

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

[0520] In some embodiments, the interface circuit 10202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S301, S302, S304, S305, S307, S309, but not limited thereto). The interface circuit 10202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 10202 performing data interaction between the processor 10201, the chip 10200, the memory 10203, or the transceiver device. In some embodiments, the processor 10201 performs at least one of other steps (e.g., steps S303, S306, S308, but not limited thereto).

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

[0522] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 10100, cause the communication device 10100 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 is 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 is not limited thereto; it may also be a temporary storage medium.

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

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

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

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

Claims

1. A communication method, executed by a first node, wherein, The method includes: Send first information to the second node, wherein the first information is used to subscribe to a reader change event, the reader change event being related to reader selection or reselection in large-scale communication.

2. The method according to claim 1, wherein, The first information includes at least one of the following: Event type; Report parameters; Triggering conditions; Business information.

3. The method according to claim 2, wherein, The event type includes at least one of the following: The reader / writer has changed; The association between the device and the reader / writer has changed.

4. The method according to claim 2 or 3, wherein, The reported parameters include at least one of the following: Content to be reported; Reporting method; Number of reports; Maximum reporting duration; Reporting conditions.

5. The method according to claim 4, wherein, The reported content includes at least one of the following: The first identification information is used to indicate the selected or reselected reader / writer; The second identification information is used to indicate the changed association between the device and the reader; The first instruction message is used to indicate a change in the reader / writer; The second instruction information is used to indicate changes in the association between the device and the reader.

6. The method according to claim 4 or 5, wherein, The reporting conditions include at least one of the following: The reader has changed; The association between the device and the reader / writer has changed; Report the trigger flag.

7. The method according to any one of claims 2 to 6, wherein, The triggering condition includes at least one of the following: Conditions related to business completion; Conditions related to business delays; Conditions related to reader reachability; Conditions related to the number of times a business is repeated.

8. The method according to any one of claims 2 to 7, wherein, The service information includes at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: Receive second information sent by the second node, wherein the second information is used to report the reader change event related to the previous selection or reselection of the reader.

10. The method according to claim 9, wherein, The second information includes at least one of the following: The first identification information is used to indicate the selected or reselected reader / writer; The second identification information is used to indicate the changed association between the device and the reader; The first instruction message is used to indicate a change in the reader / writer; The second instruction information is used to indicate changes in the association between the device and the reader; Reporting method; Number of reports; Maximum reporting duration; Reporting conditions; The reader changes the triggering conditions of the event.

11. The method according to claim 9 or 10, wherein, The method further includes: The system receives an eighth message sent by the second node, wherein the eighth message is used to report the reader change event related to the selection or reselection of the reader.

12. The method according to any one of claims 1 to 11, wherein, The first node includes at least one of the following: Massive Communication Application Functionality (MCAF); Policy control function (PCF).

13. A communication method, executed by a second node, wherein, The method includes: Receive first information sent by the first node, wherein the first information is used to subscribe to a reader change event, the reader change event being related to reader selection or reselection in large-scale communication.

14. The method according to claim 13, wherein, The first information includes at least one of the following: Event type; Report parameters; Triggering conditions; Business information.

15. The method according to claim 13 or 14, wherein, The method further includes: Send a second message to the first node, wherein the second message is used to report the reader change event.

16. The method according to claim 15, wherein, The second information includes at least one of the following: The first identification information is used to indicate the selected or reselected reader / writer; The second identification information is used to indicate the changed association between the device and the reader; The first instruction message is used to indicate a change in the reader / writer; The second instruction information is used to indicate changes in the association between the device and the reader; Reporting method; Number of reports; Maximum reporting duration; Reporting conditions; The reader changes the triggering conditions of the event.

17. The method according to any one of claims 13 to 16, wherein, The method further includes: Determine the selected or reselected reader / writer.

18. The method according to claim 17, wherein, The method further includes: Send a fourth message to the third node, wherein the fourth message is used to subscribe to the reader change event; Receive the third information sent by the third node.

19. The method according to claim 18, wherein, The third node is the reader that was selected or reselected before the selection or reselection, and the fourth information is used to subscribe to the reader change events associated with the selected or reselected reader.

20. The method according to claim 18 or 19, wherein, The fourth piece of information includes at least one of the following: Event type; Report parameters; Triggering conditions; Business information.

21. The method according to claim 14 or 20, wherein, The event type includes at least one of the following: The reader / writer has changed; The association between the device and the reader / writer has changed.

22. The method according to claim 14 or 20, wherein, The reported parameters include at least one of the following: Content to be reported; Reporting method; Number of reports; Maximum reporting duration; Reporting conditions.

23. The method according to claim 22, wherein, The reported content includes at least one of the following: The first identification information is used to indicate the selected or reselected reader / writer; The second identification information is used to indicate the changed association between the device and the reader; The first instruction message is used to indicate a change in the reader / writer; The second instruction information is used to indicate changes in the association between the device and the reader.

24. The method according to claim 22 or 23, wherein, The reporting conditions include at least one of the following: The reader has changed; The association between the device and the reader / writer has changed; Report the trigger flag.

25. The method according to claim 14 or 20, wherein, The triggering condition includes at least one of the following: Conditions related to business completion; Conditions related to business delays; Conditions related to reader reachability; Conditions related to the number of times a business is repeated.

26. The method according to claim 14 or 20, wherein, The service information includes at least one of the following: device category, service type, device identifier, device selection criteria, service location, service time, topology type, topology priority, non-homogeneous network support, reader selection information, and multi-network support.

27. The method according to any one of claims 18 to 26, wherein, The third information includes at least one of the following: The first identification information is used to indicate the selected or reselected reader / writer; The second identification information is used to indicate the changed association between the device and the reader; The first instruction message is used to indicate a change in the reader / writer; The second instruction information is used to indicate changes in the association between the device and the reader; Reporting method; Number of reports; Maximum reporting duration; Reporting conditions; The reader changes the triggering conditions of the event.

28. The method according to any one of claims 17 to 19, wherein, The method further includes: Send a fourth message to the fifth node, wherein the fourth message is used to subscribe to the reader change event; Receive the third information sent by the fifth node; The fifth node is the selected or reselected reader / writer.

29. The method according to claim 28, wherein, The method further includes: Send an eighth message to the first node, wherein the eighth message is used to report the reader change event related to the selected or reselected reader.

30. The method according to any one of claims 13 to 29, wherein, The second node includes at least one of the following: Massive Communication Management Function (MCMF); Access and Mobility Management Functions (AMF); Unified Data Management Function (UDM); Network storage function (NRF); Network Open Function (NEF).

31. A communication device, disposed at a first node, wherein, The device includes: The transceiver module is configured to send first information to the second node, wherein the first information is used to subscribe to reader change events, which are related to reader selection or reselection in large-scale communication.

32. A communication device, disposed at a second node, wherein, The device includes: The transceiver module is configured to receive first information sent by the first node, wherein the first information is used to subscribe to reader change events, and the reader change events are related to reader selection or reselection in large-scale communication.

33. A communication device, comprising: One or more processors; A memory that stores instructions; When the instruction is executed by the communication device, it causes the communication device to implement the communication method as described in any one of claims 1-12 and 13-30.

34. A storage medium storing instructions, wherein, When the instruction is executed on the communication device, the communication device implements the communication method as described in any one of claims 1-12 and 13-30.

35. A computer program product comprising instructions, wherein, When the instruction is executed on the communication device, the communication device implements the communication method as described in any one of claims 1-12 and 13-30.

Images