Communication method and apparatus

Abstract

The present disclosure provides a communication method and device, a method performed by a first device comprises: sending a first request message to a second device, the first request message is used to request the second device to schedule an MC IoT device to execute an emergency application command. Therefore, the first device can request the second device to schedule the MC IoT device to execute the emergency application command to perform the detection and reporting of the emergency event, to provide reliable and efficient large-scale communication services, and to improve the performance of the communication system.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] In recent years, the Internet of Things (IoT) has attracted widespread attention in the field of wireless communication. It is anticipated that more "objects" will become interconnected to improve productivity and quality of life. Summary of the Invention

[0003] This disclosure provides a communication method and apparatus that supports multiple cellular IoT (MCIoT) devices in executing emergency application commands to enable the detection and reporting of emergency events. It can provide reliable and efficient large-scale communication services and improve the performance of communication systems.

[0004] This disclosure presents a communication method and apparatus.

[0005] According to a first aspect of the present disclosure, a communication method is proposed, executed by a first device, comprising: sending a first request message to a second device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command.

[0006] According to a second aspect of the present disclosure, a communication method is provided, executed by a second device, comprising: receiving a first request message sent by a first device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command; and sending a third request message to the MCIoT device, the third request message being used to request the MCIoT device to execute the emergency application command.

[0007] According to a third aspect of the present disclosure, a communication method is provided, executed by a third device, comprising: receiving a command request message sent by an application entity, the command request message being used to request an MCIoT device to execute an emergency application command; sending a second request message to a first device, the second request message being used to instruct the application entity to request the MCIoT device to execute an emergency application command, the second request message being used by the first device to determine and send a first request message to the second device, the first request message being used to request the second device to schedule the MCIoT device to execute the emergency application command.

[0008] According to a fourth aspect of the present disclosure, a first device is provided, comprising: a transceiver module, configured to send a first request message to a second device, the first request message being configured to request the second device to schedule an MCIoT device to execute an emergency application command.

[0009] According to a fifth aspect of the present disclosure, a second device is provided, comprising: a transceiver module configured to receive a first request message sent by a first device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command; the transceiver module is further configured to send a third request message to the MCIoT device, the third request message being used to request the MCIoT device to execute an emergency application command.

[0010] According to a sixth aspect of the present disclosure, a third device is provided, comprising: a transceiver module configured to receive a command request message sent by an application entity, the command request message being used to request an MCIoT device to execute an emergency application command; the transceiver module is further configured to send a second request message to a first device, the second request message being used to instruct the application entity to request the MCIoT device to execute an emergency application command, the second request message being used by the first device to determine and send a first request message to the second device, the first request message being used to request the second device to schedule the MCIoT device to execute the emergency application command.

[0011] According to a seventh aspect of the present disclosure, a first device is provided, comprising: one or more processors, wherein the first device is configured to perform the method described in the first aspect.

[0012] According to an eighth aspect of the present disclosure, a second device is provided, comprising: one or more processors, wherein the second device is configured to perform the method described in the second aspect.

[0013] According to a ninth aspect of the present disclosure, a third device is provided, comprising: one or more processors, wherein the third device is configured to perform the method described in the third aspect.

[0014] According to a tenth aspect of the present disclosure, a communication device is provided, comprising: one or more processors; and a memory coupled to the processors, the memory storing instructions which, when executed by the processors, cause the communication device to perform the method as described in at least one of the first, second, and third aspects.

[0015] According to an eleventh aspect of the present disclosure, a communication system is provided, comprising: a first device, a second device, and a third device; the first device performs the method as described in the first aspect, the second device performs the method as described in the second aspect embodiment, and the third device performs the method as described in the third aspect embodiment.

[0016] According to a twelfth aspect of the present disclosure, a computer storage medium is provided, wherein the computer storage medium stores computer-executable instructions; when executed by a processor, the computer-executable instructions are capable of implementing the method described in at least one of the first, second, and third aspects.

[0017] According to a thirteenth aspect of the present disclosure, a computer program product is provided, wherein the computer program product stores a computer program; after being executed by a processor, the computer program is capable of implementing the method described in at least one of the first, second, and third aspects.

[0018] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description

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

[0020] Figure 1 This is an architecture diagram of a communication system provided in an embodiment of this disclosure;

[0021] Figure 2 This is a flowchart of a communication method provided in an embodiment of this disclosure;

[0022] Figure 3A This is a flowchart of another communication method provided in an embodiment of this disclosure;

[0023] Figure 3B This is a flowchart of yet another communication method provided in this disclosure embodiment;

[0024] Figure 3C This is a flowchart of yet another communication method provided in this disclosure embodiment;

[0025] Figure 4 This is a flowchart of yet another communication method provided in this disclosure embodiment;

[0026] Figure 5A This is a structural diagram of a first device provided in an embodiment of this disclosure;

[0027] Figure 5B This is a structural diagram of a second device provided in an embodiment of this disclosure;

[0028] Figure 5C This is a structural diagram of a third device provided in an embodiment of this disclosure;

[0029] Figure 6A This is a structural diagram of a communication device provided in an embodiment of this disclosure;

[0030] Figure 6B This is a structural diagram of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0031] This disclosure presents a communication method and apparatus.

[0032] In a first aspect, embodiments of this disclosure propose a communication method executed by a first device, comprising: sending a first request message to a second device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command.

[0033] In the above embodiments, MCIoT devices are supported in executing emergency application commands to detect and report emergency events, providing reliable and efficient large-scale communication services and improving the performance of the communication system.

[0034] In some embodiments of the first aspect, the method further includes: a first device receiving a first response message sent by a second device, the first response message including a result report determined by the MCIoT device executing an emergency application command.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: a first device receiving a second request message sent by a third device, the second request message being used to instruct an application entity to request an MCIoT device to execute an emergency application command, the second request message being sent by the third device upon receiving a command request message sent by the application entity, the command request message being used to request the MCIoT device to execute an emergency application command; and determining a second device based on the second request message.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes: the first device determining that an authorized application entity initiates a request to instruct the MCIoT device to execute an emergency application command.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes: the first device sending a second response message to the third device, the second response message being used to indicate acceptance of the second request message.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: the first device sending a command notification message to the third device, the command notification message including a result report of the MCIoT device executing an emergency application command, the command notification message being used by the third device to send a command response message to the application entity, the command response message including the result report.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, at least one of the first request message, the second request message, and the command request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the UrgentApplication-Specific Command is used to instruct the detection of an emergency event. The UrgentApplication-Specific Command includes at least one of the following: the emergency event; the indicated alarm or urgent types; the priority level of the alarm or urgent types; and the required assistant datasets.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the type of emergency event includes at least one of: transient pressure spikes, acoustic leakage signatures, and early indicators of pipe failure; and / or the priority corresponding to the type of emergency event includes: priority for further analysis and prediction, priority for the alarm trigger, and priority for the urgent actions; and / or the auxiliary dataset to be provided includes at least one of: the measurement values, the maximum, the minimum values, the location information, the power status, the timeslot for actions, the timestamps for the abnormal events, the abnormal events frequency, and the abnormal events times.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the result report includes at least one of the following: the reported emergency event; the type of emergency event; the priority corresponding to the type of emergency event; the auxiliary dataset of the report; the identifier of the MCIoT device corresponding to the report; the identifier of the application entity corresponding to the report; the identifier of the group to which the MCIoT device corresponding to the report belongs; and the identifier of the group to which the application entity corresponding to the report belongs.

[0043] Secondly, embodiments of this disclosure propose a communication method executed by a second device, comprising: receiving a first request message sent by a first device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command; and sending a third request message to the MCIoT device, the third request message being used to request the MCIoT device to execute an emergency application command.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: the second device receiving a third response message sent by the MCIoT device, the third response message including a result report determined by the MCIoT device executing an emergency application command.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: the second device sending a first response message to the first device, the first response message including a result report determined by the MCIoT device executing an emergency application command.

[0046] In conjunction with some embodiments of the second aspect, in some embodiments, at least one of the first request message and the third request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the emergency application command is used to instruct the detection of an emergency event, and the emergency application command includes at least one of the following information: the emergency event; the type of the emergency event; the priority corresponding to the type of emergency event; and the auxiliary dataset to be provided.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the type of emergency event includes at least one of: transient pressure peak, acoustic leakage characteristics, and early warning signal of pipeline failure; and / or the priority corresponding to the type of emergency event includes: priority for indicating further analysis and prediction, priority for indicating alarm triggering, and priority for indicating emergency operation; and / or the auxiliary dataset to be provided includes at least one of: measured value, maximum value, minimum value, location information, power status, operation time period, timestamp of emergency event occurrence, frequency of emergency event occurrence, and number of emergency events.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the result report includes at least one of the following information: the reported emergency event; the type of the reported emergency event; the priority corresponding to the type of the reported emergency event; the auxiliary dataset of the report; the identifier of the MCIoT device corresponding to the report; the identifier of the application entity corresponding to the report; the identifier of the group to which the MCIoT device corresponding to the report belongs; and the identifier of the group to which the application entity corresponding to the report belongs.

[0050] Thirdly, embodiments of this disclosure propose a communication method executed by a third device, comprising: receiving a command request message sent by an application entity, the command request message being used to request an MCIoT device to execute an emergency application command; sending a second request message to a first device, the second request message being used to instruct the application entity to request the MCIoT device to execute an emergency application command, the second request message being used by the first device to determine and send a first request message to the second device, the first request message being used to request the second device to schedule the MCIoT device to execute the emergency application command.

[0051] In the above embodiments, the application entity can initiate a request to the MCIoT device to execute an emergency application command, so as to realize the detection and reporting of emergency events of the MCIoT device, provide reliable and efficient large-scale communication services, and improve the performance of the communication system.

[0052] In conjunction with some embodiments of the third aspect, in some embodiments, the second request message is used by the first device to determine that an authorized application entity initiates a request to instruct the MCIoT device to execute an emergency application command.

[0053] In some embodiments, in conjunction with the third aspect, the above method further includes: a third device receiving a second response message sent by a first device, the second response message being used to indicate acceptance of the second request message.

[0054] In some embodiments, in conjunction with the third aspect, the above method further includes: the third device sending indication information to the application entity, the indication information being used to indicate acceptance of the command request message.

[0055] In conjunction with some embodiments of the third aspect, in some embodiments, the above method further includes: a third device receiving a command notification message sent by a first device, the command notification message including a result report of the MCIoT device requested by the application entity to execute an emergency application command.

[0056] In conjunction with some embodiments of the third aspect, in some embodiments, the above method further includes: a third device sending a command response message to an application entity, the command response message including a result report, the result report being used by the application entity to determine whether to trigger the execution of a first operation, the first operation including at least one of the following: further analysis and prediction; alarm; emergency operation.

[0057] In the above embodiments, the third device can send a command response message back to the application entity based on the command request message, so as to realize the complete process of emergency event detection and reporting of MCIoT devices, provide reliable and efficient large-scale communication services, and improve the performance of the communication system.

[0058] In conjunction with some embodiments of the third aspect, in some embodiments, at least one of the command request message, the second request message, and the first request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0059] In conjunction with some embodiments of the third aspect, in some embodiments, the emergency application command is used to instruct the detection of an emergency event, and the emergency application command includes at least one of the following information: the emergency event; the type of the emergency event; the priority corresponding to the type of emergency event; and the auxiliary dataset to be provided.

[0060] In conjunction with some embodiments of the third aspect, in some embodiments, the type of emergency event includes at least one of: transient pressure peak, acoustic leakage characteristics, and early warning signal of pipeline failure; and / or the priority corresponding to the type of emergency event includes: priority for indicating further analysis and prediction, priority for indicating alarm triggering, and priority for indicating emergency operation; and / or the auxiliary dataset to be provided includes at least one of: measured value, maximum value, minimum value, location information, power status, operation time period, timestamp of emergency event occurrence, frequency of emergency event occurrence, and number of emergency events.

[0061] In conjunction with some embodiments of the third aspect, in some embodiments, the result report includes at least one of the following: the reported emergency event; the type of the reported emergency event; the priority corresponding to the type of the reported emergency event; the auxiliary dataset of the report; the identifier of the MCIoT device corresponding to the report; the identifier of the application entity corresponding to the report; the identifier of the group to which the MCIoT device corresponding to the report belongs; and the identifier of the group to which the application entity corresponding to the report belongs.

[0062] Fourthly, this disclosure provides a first device, including: a transceiver module, configured to send a first request message to a second device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command.

[0063] Fifthly, embodiments of this disclosure provide a second device, comprising: a transceiver module, configured to receive a first request message sent by a first device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command; the transceiver module is further configured to send a third request message to the MCIoT device, the third request message being used to request the MCIoT device to execute an emergency application command.

[0064] In a sixth aspect, embodiments of this disclosure provide a third device, comprising: a transceiver module, configured to receive a command request message sent by an application entity, the command request message being used to request an MCIoT device to execute an emergency application command; the transceiver module is further configured to send a second request message to a first device, the second request message being used to instruct the application entity to request the MCIoT device to execute an emergency application command, the second request message being used by the first device to determine and send a first request message to the second device, the first request message being used to request the second device to schedule the MCIoT device to execute the emergency application command.

[0065] In a seventh aspect, a first device is proposed, comprising: one or more processors, wherein the first device is configured to perform the method described in the first aspect.

[0066] In an eighth aspect, a second device is proposed, comprising: one or more processors, wherein the second device is configured to perform the method described in the second aspect.

[0067] A ninth aspect proposes a third device comprising: one or more processors, wherein the third device is configured to perform the method described in the third aspect.

[0068] In a tenth aspect, embodiments of this disclosure provide a communication device comprising: one or more processors; and a memory coupled to the processors, the memory storing instructions which, when executed by the processors, cause the communication device to perform the method described in at least one of the first, second, and third aspects.

[0069] Eleventhly, embodiments of this disclosure provide a communication system comprising: a first device, a second device, and a third device; the first device performs the method as described in the first aspect, the second device performs the method as described in the second aspect embodiment, and the third device performs the method as described in the third aspect embodiment.

[0070] In a twelfth aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in at least one of the first, second, and third aspects.

[0071] In a thirteenth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in at least one of the first, second, and third aspects.

[0072] In a fourteenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in at least one of the first, second, and third aspects.

[0073] In a fifteenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in at least one of the first, second, and third aspects described above.

[0074] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed 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.

[0075] This disclosure provides a communication method and apparatus. In some embodiments, the terms "communication method" and "information processing method" can be used interchangeably.

[0076] 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. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

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

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

[0079] In the embodiments disclosed herein, "multiple" refers to two or more.

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

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

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

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

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

[0085] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

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

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

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

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

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

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

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

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

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

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

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

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

[0098] Figure 1 This disclosure provides an architecture diagram of a communication system.

[0099] like Figure 1 As shown, the communication system 100 includes a terminal 101 and a network device 102.

[0100] In some embodiments, terminal 101 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, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, and wireless terminal in smart home.

[0101] In some embodiments, network device 102 may include at least one of access network device and core network device.

[0102] 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 or 6G 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.

[0103] In some embodiments, the access network device may be a satellite.

[0104] In some embodiments, the core network equipment may be a single device, multiple devices, or a group of devices, including all or part of a first network element, a second network element, a third network element, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a 6G Core Network (6GCN), and a Next Generation Core (NGC).

[0105] In some embodiments, the first network element is, for example, an access and mobility management function (AMF) network element.

[0106] In some embodiments, the second network element is, for example, a network exposure function (NEF) network element.

[0107] In some embodiments, the third network element is, for example, an application function (AF) network element.

[0108] In some embodiments, the first network element is used to implement terminal access management and mobility management. It is responsible for terminal state maintenance, terminal reachability management, mobility management (MM), forwarding of non-access stratum (NAS) messages, and forwarding of session management (SM) N2 messages.

[0109] In some embodiments, the second network element is used to securely expose services and capabilities provided by 3GPP network functions to the outside world.

[0110] In some embodiments, the third network element is used for data routing affected by applications, accessing network open functions, or interacting with the policy framework for policy control, etc.

[0111] In some embodiments, at least one of the first network element, the second network element, and the third network element can be independent of the core network equipment.

[0112] In some embodiments, at least one of the first network element, the second network element, and the third network element may be part of the core network equipment.

[0113] In some embodiments, the sensing function entity can be deployed on the base station side or on the core network. In some embodiments, when deployed on the core network side, the sensing function entity can also be referred to as a sensing function, a sensing function network element, or a sensing network element.

[0114] It should be noted that an AMF network element can also be called AMF, a NEF network element can also be called NEF, and an AF network element can also be called AF.

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

[0116] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part thereof, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1Other 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.

[0117] 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), 6th Generation Mobile Communication System (6G), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, ultra-wideband (UWB), Bluetooth (a registered trademark), public land mobile network (PLMN) networks, device-to-device (D2D) systems, machine-to-machine (M2M) systems, internet of things (IoT) systems, vehicle-to-everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0118] In recent years, the Internet of Things (IoT) has attracted widespread attention in the field of wireless communication. It is anticipated that more "objects" will become interconnected to improve productivity and quality of life.

[0119] In some embodiments, further reductions in the size, complexity, and power consumption of IoT devices could enable the deployment of tens or even hundreds of billions of IoT devices for various applications, providing added value across the entire value chain. However, with the rapid increase in the number of IoT devices, the need to manually replace or recharge all of them will result in high maintenance costs, serious environmental problems, and even security risks in certain use cases, such as IoT devices used as wireless sensors in the power, electricity, and oil industries.

[0120] Most IoT wireless communication devices rely on batteries that require manual replacement or charging. However, automation and digitalization across industries have created numerous new market demands that require new IoT technologies to support battery-free devices (without energy storage) or devices with energy storage that do not require manual replacement or charging.

[0121] To support a much higher local device distribution density than existing IoT technologies, new IoT technologies aim to provide significantly lower complexity and power consumption than existing IoT technologies (such as narrowband Internet of Things (NB-IoT) and enhanced machine type communication (eMTC)), while still meeting the use cases, scenario requirements, and A-IoT services required by Ambient-IoT (A-IoT) devices.

[0122] In some embodiments, from an architectural perspective, a network is required to support Ambient Internet of Things (A-IoT) services. The industry is researching architectural support for A-IoT devices, based on service requirements applicable to device type, traffic type, use case, and connection topology. In some embodiments, the overall architecture of A-IoT may include A-IoT devices, readers, AIoT controllers, and application functions (AFs).

[0123] In some embodiments, based on the service requirements of the environmental Internet of Things, a maximum one-way end-to-end latency target is proposed, such as a longer latency target (10 seconds) or a shorter latency target (1 second), and the availability of the communication service is 99% or 99.9%.

[0124] In some embodiments, large-scale communication (including, for example, cellular IoT services and environmental IoT services) is one of the key research areas. However, how to support large-scale communication services, such as cellular IoT and AIoT services, requires further research.

[0125] Based on this, this disclosure provides a communication method and apparatus, wherein the method executed by a first device includes: sending a first request message to a second device, the first request message being used to request the second device to schedule an MCIoT device to execute an emergency application command. Thus, the first device can request the second device to schedule the MCIoT device to execute an emergency application command to perform emergency event detection and reporting, thereby providing reliable and efficient large-scale communication services and improving the performance of the communication system.

[0126] Figure 2 This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 2 As shown, the embodiments of this disclosure relate to a communication method, which includes:

[0127] S201, The application entity sends a command request message to the third device.

[0128] In some embodiments, the third device receives a command request message sent by an application entity, but is not limited thereto. The third device may also receive a command request message sent by a subject other than the application entity, in which case S201 can be omitted.

[0129] In some embodiments, the third device obtains a command request message defined by the protocol, in which case S201 can be omitted.

[0130] In some embodiments, the third device obtains a command request message from the upper layer(s), in which case S201 can be omitted.

[0131] In some embodiments, the third device processes the request to obtain a command request message, in which case S201 can be omitted.

[0132] In some embodiments, the third device autonomously implements the function indicated by the command request message, or the above function is a default or default value, in which case S201 can be omitted.

[0133] In some embodiments, the application entity is an application function (AF), or an application layer function (APP) located in the terminal (including MCIoT devices), or an application function triggered by the operating system (OS) or underlying system in the terminal.

[0134] In some embodiments, the third device is a network exposure function (NEF).

[0135] In some embodiments, the command request message is used to request one or more MCIoT devices to execute an emergency application command.

[0136] In some embodiments, MCIoT devices include IoT devices and A-IoT devices.

[0137] In some embodiments, the command request message is used to request multiple MCIoT devices to execute their respective emergency application commands. In some embodiments, each MCIoT device corresponds to one emergency application command, and the emergency application commands corresponding to different MCIoT devices may be the same or different.

[0138] In some embodiments, the command request message is used to request the result report obtained by one or more MCIoT devices executing emergency application commands.

[0139] In some embodiments, the command request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0140] In some embodiments, the command request message includes at least one of the following: the identifier of the application entity, the emergency application command, the type of the emergency application command, information about the MCIoT device, information about the external target area, the number of MCIoT devices, the size of the response message used by the MCIoT device to transmit the result report obtained by executing the emergency application command, emergency application command type-specific parameters, and the requested location information.

[0141] In some embodiments, the information of the MCIoT device includes the location of the MCIoT device.

[0142] In some embodiments, the type of emergency application command is an emergency application-specific command, and the emergency application command type-specific parameter contains details of the emergency application command. This parameter is an application-layer container.

[0143] In some embodiments, the information of the MCIoT device may be information about one or more MCIoT devices for which the command request message requests the execution of the emergency application command, or information about MCIoT devices other than those requested to execute the emergency application command by the command request message. In some embodiments, the information of the MCIoT device includes the device identifier of the MCIoT device.

[0144] In some embodiments, the number of MCIoT devices is used to indicate the number of MCIoT devices executing emergency application commands.

[0145] In some embodiments, the type of emergency application command is used to indicate the emergency application command that needs to be executed, and the emergency application command type-specific parameter is used to indicate the parameters required to execute the emergency application command.

[0146] In some embodiments, the emergency application command is used to instruct the detection of an emergency event. The emergency application command includes at least one of the following information: the emergency event; the type of the emergency event; the priority corresponding to the type of emergency event; and the auxiliary dataset to be provided.

[0147] In some embodiments, the emergency application command includes an emergency event. In some embodiments, the emergency application command includes an identifier of the emergency event. In this disclosure embodiment, the emergency application command including the emergency event is used to determine the type of emergency event and the priority corresponding to the type of emergency event.

[0148] In some embodiments, emergency events are distinguished by their identifiers, with different identifiers corresponding to different emergency event types. In some embodiments, emergency events are distinguished by their priority, with different priority emergency events corresponding to different emergency event types.

[0149] In some embodiments, the types of emergency events include at least one of: transient pressure peak, acoustic leakage characteristics, and early warning signals of pipeline malfunctions; and / or the priorities corresponding to the types of emergency events include: priorities for indicating further analysis and prediction, priorities for indicating alarm triggering, and priorities for indicating emergency operations; and / or the auxiliary datasets to be provided include at least one of: measured values, maximum values, minimum values, location information, power status, operation time period, timestamps of emergency events, frequency of emergency events, and number of emergency events.

[0150] In some embodiments, the type of emergency event is a transient pressure peak, indicating that the detection of transient pressure peaks is performed. The type of emergency event is an acoustic leakage characteristic, indicating that the detection of acoustic leakage characteristics is performed. The type of emergency event is a pipeline fault warning signal, indicating that the detection of pipeline fault warning signals is performed.

[0151] In some embodiments, the type of emergency event is a transient pressure peak, including reaching the maximum transient pressure peak, reaching 95% of the maximum transient pressure peak, reaching 90% of the maximum transient pressure peak, reaching 85% of the maximum transient pressure peak, and reaching 80% of the maximum transient pressure peak. In some embodiments, the type of emergency event is an acoustic leakage feature, including detecting an acoustic leakage feature reaching a warning value and detecting an acoustic leakage feature reaching an alarm value. In some embodiments, the type of emergency event is a pipeline fault warning signal, including detecting a pipeline fault warning signal as urgent, detecting a pipeline fault as moderate, and detecting a pipeline fault as minor. Of course, the emergency event can also be other events besides those described in the above embodiments, and this disclosure does not impose specific limitations on them.

[0152] In some embodiments, the priorities for indicating further analysis and prediction, for indicating alarm triggering, and for indicating emergency operation are ordered from high to low or from low to high. For example, the priority for indicating further analysis and prediction is the lowest, the priority for indicating alarm triggering is medium, and the priority for indicating emergency operation is the highest; or the priority for indicating further analysis and prediction is the highest, the priority for indicating alarm triggering is medium, and the priority for indicating emergency operation is the lowest.

[0153] In some embodiments, the priority corresponding to the type of emergency event is a priority used to indicate further analysis and prediction, indicating that the detection results obtained for that type of emergency event are used for further analysis and prediction. The priority corresponding to the type of emergency event is a priority used to indicate the triggering of an alarm, indicating that the detection results obtained for that type of emergency event are used to trigger an alarm. The priority corresponding to the type of emergency event is a priority used to indicate the performance of emergency operations, indicating that the detection results obtained for that type of emergency event are used to perform emergency operations.

[0154] In some embodiments, emergency operations include disconnecting a specified connection and turning off a specified switch. Exemplarily, the specified connection is a power connection, a pipe connection, a channel connection, etc. The specified switch is a power switch, a gas switch, or a water flow switch.

[0155] In some embodiments, the measured value, maximum value, and minimum value are the measured value, maximum value, and minimum value determined by detecting the emergency event corresponding to the type of emergency event. Location information refers to the location where the emergency event corresponding to the type of emergency event is detected. Power status refers to the power status at the time the emergency event corresponding to the type of emergency event is detected. Operation time period refers to the time period during which the emergency event corresponding to the type of emergency event is detected. Emergency event occurrence timestamp refers to the time point at which the emergency event corresponding to the type of emergency event is detected. Emergency event occurrence frequency refers to the detection frequency of the emergency event corresponding to the type of emergency event. Emergency event occurrence count refers to the number of times the emergency event corresponding to the type of emergency event has been detected.

[0156] For example, an emergency application command is used to instruct the execution of a transient pressure peak detection and to indicate its priority for further analysis and prediction. It requires the provided measurement values, maximum and minimum values, location information, operation time period, timestamp of the emergency event, frequency of the emergency event, and number of emergency events. For instance, an emergency application command instructing the detection of a transient pressure peak in a water pipe, prioritizing it for further analysis and prediction, requires the provided measurement values, maximum and minimum values, location, time period, specific time of detection, and the frequency and number of detections.

[0157] For example, an emergency application command used to instruct the execution of detection of this type of acoustic leak characteristic, and to indicate medium priority for triggering an alarm, requires at least one of the following: location information, operation time period, timestamp of the emergency event, frequency of the emergency event, and number of times the emergency event occurred. For instance, an emergency application command used to instruct the detection of a gas leak sound, with medium priority for triggering an alarm, requires providing the location, time period, and time at which the gas leak sound was detected, as well as the frequency and number of times it occurred.

[0158] It should be noted that the above examples are for illustrative purposes only and are not intended to limit the specific implementation of the present disclosure. The types of emergency events in the implementation of the present disclosure may also include other types besides the above examples, such as: high temperature warning, low temperature warning, rainfall warning, smoke warning, etc.

[0159] In some embodiments, when there is a need to detect an emergency event, the application entity determines an emergency application command that needs to be executed by one or more MCIoT devices and sends a command request message to a third device.

[0160] In some embodiments, an emergency event is an event that the MCIoT device can detect and that requires notification, reporting, or alarm.

[0161] In some embodiments, when an application entity determines that an MCIoT device needs to execute an emergency application command, it sends a command request message to a third device, requesting the MCIoT device to execute the emergency application command.

[0162] For example, the first MCIoT device is used to monitor whether the gas pipeline is leaking. When the application entity determines that it needs to know whether the gas pipeline is leaking, it generates an instruction to the first MCIoT device that supports monitoring whether the gas pipeline is leaking to execute an emergency application command to detect whether the gas pipeline is leaking, and sends a command request message to the third device to request the first MCIoT device that supports monitoring whether the gas pipeline is leaking to execute the emergency application command.

[0163] In this embodiment of the disclosure, the third device receives a command request message sent by the application entity and determines that the application entity requests the MCIoT device to execute an emergency application command. The third device can send a request to the network function that manages the MCIoT device to instruct the application entity to request the MCIoT device to execute the emergency application command, thereby ensuring that the command request message of the application entity can be executed accurately.

[0164] In some embodiments, the command request message is either an Nnef_6G MCIoT_(Urgent Application-Specific, UAS) command request message or an Nnef_MCIoT_UAS command request message. Here, Nnef is the interface between NEF and the application entity.

[0165] It should be noted that the command request message can also be referred to as a request message, first message, first information, instruction information, etc. Emergency application commands can also be referred to as commands, alarm application commands, alert application commands, emergency commands, alarm commands, alert commands, etc. Emergency events can also be referred to as first events, alarm events, alert events, reminder events, etc. This disclosure does not impose specific limitations in these respects.

[0166] S202, the third device sends a second request message to the first device.

[0167] In some embodiments, the first device receives a second request message sent by a third device, but is not limited thereto. The first device may also receive a second request message sent by a subject other than the third device, in which case S202 may be omitted.

[0168] In some embodiments, the first device obtains a second request message defined by the protocol, in which case S202 can be omitted.

[0169] In some embodiments, the first device obtains the second request message from the upper layer(s), in which case S202 can be omitted.

[0170] In some embodiments, the first device processes the data to obtain a second request message, in which case S202 can be omitted.

[0171] In some embodiments, the first device autonomously implements the function indicated by the second request message, or the above function is a default or default value, in which case S202 can be omitted.

[0172] In some embodiments, the first device is a network function for managing MCIoT devices. In some embodiments, the first device is a network function for managing emergency event execution. In some embodiments, the first device is a network function for managing emergency services. In some embodiments, the first device is a network function within a core network device or a network function independent of the core network device. In some embodiments, the first device is an MCIoT function (MCIoTF).

[0173] In this embodiment of the disclosure, when the third device receives a command request message sent by the application entity and determines that the application entity requests the MCIoT device to execute an emergency application command, it can send a second request message to the first device.

[0174] In some embodiments, before sending the second request message to the first device, the third device further includes: determining one or more first devices based on the command request message.

[0175] In some embodiments, if the third device determines, based on the command request message sent by the application entity, that the application entity is requesting the MCIoT device to execute an emergency application command, but cannot determine the first device or fails to determine the first device (i.e., the application entity's request for the MCIoT device to execute the emergency application command cannot be executed), the third device may send a rejection command request message to the application entity, indicating to the application entity that it refuses to execute the service requested in the command request message. In this case, the steps performed after S202 can be omitted.

[0176] In some embodiments, the third device obtains information on multiple candidate first devices from the MCIoT Data Management (MCIoT DM) function and determines one or more first devices from them.

[0177] In some embodiments, the MCIoT DM is used to handle the identification, subscription, access authentication, registration, or mobility management of MCIoT devices.

[0178] In this embodiment of the disclosure, the third device determines, based on the command request message sent by the application entity, that the application entity requests one or more MCIoT devices to execute an emergency application command, further determines one or more network functions that manage one or more MCIoT devices, identifies one or more first devices, and then sends a second request message to one or more first devices.

[0179] In this embodiment of the disclosure, the third device determines, based on the command request message sent by the application entity, that the application entity requests one or more MCIoT devices to execute an emergency application command, further determines one or more network functions that manage the execution of emergency events, determines one or more first devices, and then sends a second request message to one or more first devices.

[0180] In this embodiment of the disclosure, the third device determines, based on the command request message sent by the application entity, that the application entity requests the MCIoT device to execute an emergency application command, further determines one or more network functions for managing emergency services, determines one or more first devices, and then sends a second request message to one or more first devices.

[0181] In some embodiments, the second request message is used to instruct the application entity to request the MCIoT device to execute an emergency application command.

[0182] In some embodiments, the second request message is used to instruct an application entity to request an MCIoT device to execute an emergency application command.

[0183] In some embodiments, the second request message is used to instruct an application entity to request each of the multiple MCIoT devices to execute its corresponding emergency application command.

[0184] In some embodiments, the second request message is used to instruct each of the multiple application entities to request an MCIoT device to execute an emergency application command.

[0185] In some embodiments, the second request message is used to instruct each of the multiple application entities to request each of the multiple MCIoT devices to execute its corresponding emergency application command.

[0186] In some embodiments, the second request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0187] In some embodiments, the second request message includes at least one of the following: the identifier of the application entity, the emergency application command, the type of the emergency application command, information about the MCIoT device, information about the external target area, the number of MCIoT devices, the size of the response message used by the MCIoT device to transmit the result report obtained by executing the emergency application command, emergency application command type-specific parameters, and the requested location information.

[0188] The contents of the command request message are described in the relevant steps above and will not be repeated here.

[0189] In some embodiments, the second request message is an NMCIOTF_6G MCIoT_UAS command request message or an NMCIOTF_MCIoT_UAS command request message. Here, NMCIOTF is the interface between NEF and the third device.

[0190] It should be noted that the second request message may also be referred to as a request message, a second message, a second information, an instruction message, etc. This disclosure does not impose specific limitations in this regard.

[0191] S203, the first device determines that the authorized application entity initiates a request to instruct the MCIoT device to execute an emergency application command.

[0192] In this embodiment of the disclosure, the first device receives a second request message sent by the third device and determines that the application entity requests the MCIoT device to execute an emergency application command.

[0193] In some embodiments, the first device performs authorization of the application entity to check whether the application entity is authorized to initiate the operation of executing an emergency application, that is, whether the application entity is authorized to send a command request message requesting the MCIoT device to execute an emergency application command.

[0194] In some embodiments, if the first device determines that the application entity is not authorized to send a command request message requesting the MCIoT device to execute an emergency application command, it sends an indication to the third device to reject the command request. This indication may also carry a code indicating a rejection reason, namely that the application entity is not authorized to send a command request message requesting the MCIoT device to execute an emergency application command. In this case, the steps performed after S203 can be omitted. In some embodiments, upon receiving the indication to reject the command request from the first device, the third device sends a response message to the application entity, indicating that the application entity's command request message is rejected, and carrying a code indicating a rejection reason.

[0195] In some embodiments, if the first device determines that the application entity is authorized to send a command request message requesting the MCIoT device to execute an emergency application command, it continues to execute the steps after S203.

[0196] S204, the first device determines the second device based on the second request message.

[0197] S204 and S203 can be executed simultaneously or in reverse order.

[0198] In some embodiments, the second device is an intermediary device for communication between the MCIoT device and the first device.

[0199] In some embodiments, the second device is a reader.

[0200] In some embodiments, the second device is a terminal or an access network device.

[0201] In this embodiment of the disclosure, the first device checks the parameters included in the second request message sent by the third device and selects the second device.

[0202] In some embodiments, when the second device is an access network device, the first device determines the second device, and the first device and the second device communicate directly.

[0203] In some embodiments, when the second device is a terminal or an access network device, the first device obtains information about the second device from the AMF (Access Message Function) to identify the second device. The first device and the second device communicate via the AMF.

[0204] In some embodiments, when the second device is a terminal, the first device determines the AMF and the access network device, and then determines the second device. The first device and the second device communicate through the AMF and the access network device.

[0205] In some embodiments, if the first device cannot select the second device, i.e., cannot determine the second device, the first device sends an indication of a rejection command request to the third device. This indication may also carry a code indicating the reason for rejection, which is that the second device cannot be determined. In this case, the execution steps after S204 can be omitted. In some embodiments, upon receiving the indication of a rejection command request from the first device, the third device sends a response message to the application entity, indicating that the application entity's command request message is rejected, and carrying a code indicating the reason for rejection.

[0206] In some embodiments, the indications for rejecting the command request in S203 and S204 can be the same indication, which simultaneously carries a command request message indicating that the application entity is not authorized to send a request for the MCIoT device to execute an emergency application command, and a code indicating that the reason for rejection by the second device cannot be determined. In some embodiments, when the third device receives the indication for rejecting the command request sent by the first device, it sends a response message to the application entity, indicating that the command request message of the application entity is rejected, and carrying a code indicating the reason for rejection.

[0207] In some embodiments, if the first device determines that the second device is involved, it continues to execute the steps following S204.

[0208] S205, the first device sends a second response message to the third device.

[0209] In some embodiments, the third device receives a second response message sent by the first device, but is not limited thereto. The third device may also receive a second response message sent by a subject other than the first device, in which case S205 may be omitted.

[0210] In some embodiments, the third device obtains the second response message specified by the protocol, in which case S205 can be omitted.

[0211] In some embodiments, the third device obtains the second response message from the upper layer(s), in which case S205 can be omitted.

[0212] In some embodiments, the third device processes the data to obtain a second response message, in which case S205 can be omitted.

[0213] In some embodiments, the third device autonomously implements the function indicated by the second response message, or the above function is a default or default value, in which case S205 can be omitted.

[0214] In some embodiments, the second response message is used to indicate acceptance of the second request message.

[0215] In some embodiments, the second response message is used to indicate that the application entity's request to the MCIoT device to execute an emergency application command has been accepted.

[0216] In some embodiments, the second response message is used to instruct the MCIoT device that determines the application entity request to execute the emergency application command.

[0217] In some embodiments, the second response message is used to indicate that the second request message is rejected, or the application entity's request for the MCIoT device to execute an emergency application command is rejected, or the operation of the MCIoT device to execute an emergency application command requested by the application entity is rejected. In this case, the steps after S205 can be omitted.

[0218] In some embodiments, if the first device determines, based on the second request message sent by the third device, that the application entity is authorized to send a command request message requesting the MCIoT device to execute an emergency application command, then the first device sends a second response message to the third device.

[0219] In some embodiments, if the first device determines the second device based on the second request message sent by the third device, it sends a second response message to the third device.

[0220] In some embodiments, the first device determines, based on the second request message sent by the third device, that the application entity is authorized to send a command request message requesting the MCIoT device to execute an emergency application command, and if the second device is determined, sends a second response message to the third device.

[0221] In some embodiments, the third device receives a second response message sent by the first device. The second response message is used to indicate that if the second request message is rejected, an indication message is sent to the application entity, indicating that the command request message sent by the application entity is rejected.

[0222] In some embodiments, the method further includes a third device sending indication information to the application entity, the indication information being used to indicate acceptance of a command request message. In some embodiments, the indication information is used to indicate acceptance of the application entity's request for the MCIoT device to execute an emergency application command, or the indication information is used to indicate determining the operation of scheduling the MCIoT device to execute an emergency application command.

[0223] In some embodiments, the third device receives a second response message sent by the first device. The second response message is used to indicate that if it is determined that the second request message is accepted, an indication message is sent to the application entity to indicate that the command request message sent by the application entity is accepted.

[0224] In some embodiments, the first device generates an associated identifier (ID) for the operation requested by the command request message sent by the application entity requesting the MCIoT device to execute an emergency application command. In some embodiments, the first device creates an MCIoT session for the operation requested by the command request message sent by the application entity, and the MCIoT session is identified by the associated identifier.

[0225] In some embodiments, the second response message is an NMCIOTF_6G MCIoT_UAS command response message or an NMCIOTF_MCIoT_UAS command response message. Here, NMCIOTF is the interface between NEF and the third device.

[0226] It should be noted that the second response message may also be referred to as a response message, a third message, a third information, an indication message, etc. This disclosure does not impose specific limitations in this regard.

[0227] S206, the first device sends a first request message to the second device.

[0228] S206 and S205 can be executed simultaneously or in reverse order.

[0229] In some embodiments, the second device receives a first request message sent by the first device, but is not limited thereto. The second device may also receive a first request message sent by a subject other than the first device, in which case S206 may be omitted.

[0230] In some embodiments, the second device obtains a first request message defined by the protocol, in which case S206 can be omitted.

[0231] In some embodiments, the second device obtains the first request message from the upper layer(s), in which case S206 can be omitted.

[0232] In some embodiments, the second device processes the request to obtain the first request message, in which case S206 can be omitted.

[0233] In some embodiments, the second device autonomously implements the function indicated by the first request message, or the above function is a default or default value, in which case S206 can be omitted.

[0234] In some embodiments, the second device performs an inventory process with the first device. The first device includes a follow-up command instruction in the inventory request message to notify the second device to transmit commands after the inventory is completed. The second device also includes its Next Generation Application Protocol (NGAP) identifier (ID) for each MCIoT device in the inventory report. The first device updates the corresponding MCIoT device context to include the second device's NGPID.

[0235] In some embodiments, the second device acts as an intermediary device for communication between the MCIoT device and the first device, or as a reader / writer that needs to know which MCIoT devices it can communicate with.

[0236] In some embodiments, the second device performs an inventory process with the MCIoT device, thereby enabling the second device to obtain information about the MCIoT devices it can communicate with. The inventory process may be completed through a 3-step random access procedure or a 2-step random access procedure, triggered by an inventory trigger message R2D#1 (e.g., Paging) sent by the second device. Upon receiving the inventory trigger message, the MCIoT device generates and sends a random number message D2R#1. Upon receiving the random number message, the second device sends a random number response message R2D#2 to the MCIoT device, allocating time-domain and / or frequency-domain resources for the identification reporting message D2R#2 within the random number response message. Finally, the MCIoT device sends the identification reporting message D2R#2 based on the time-domain and / or frequency-domain resources allocated in the random number response message. In some embodiments, the signaling name of R2D#1 can be Paging, the signaling name of D2R#1 can be Msg1, the signaling name of R2D#2 can be Msg2, and the signaling name of D2R#2 can be Msg3.

[0237] In some embodiments, the first request message is used to request the second device to schedule one or more MCIoT devices to execute emergency application commands.

[0238] In some embodiments, the first request message is used to request the second device to schedule each of the multiple MCIoT devices to execute its corresponding emergency application command.

[0239] In some embodiments, the first request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0240] In some embodiments, the first request message includes at least one of the following: association identifier, identifier of the second device, NAS command request message, message size of MCIoT device feedback result report, and NGAP ID of the second device corresponding to each MCIoT device.

[0241] In some embodiments, the first device sends a first request message to the second device via AMF.

[0242] In some embodiments, the association identifier is the same as the association identifier generated by the first device in S205.

[0243] In some embodiments, the NGAP ID of the second device corresponding to each MCIoT device is used by the second device to determine the context of each MCIoT device in the second device.

[0244] In some embodiments, the NAS command request message is determined by the type of emergency application command and emergency application command type-specific parameters included in the second request message received by the first device in S202.

[0245] In some embodiments, the message size of the MCIoT device feedback result report is the same as that carried in the second request message received by the first device in S202.

[0246] In some embodiments, while the inventory process between the second device and the MCIoT device is in progress, the first request message of the first device may be sent to the second device.

[0247] In this embodiment of the disclosure, the second device receives a first request message sent by the first device and determines to schedule or instruct the MCIoT device to execute an emergency application command.

[0248] In some embodiments, the second device is a terminal, and the first device sends a first request message to the second device through the access network device, or through the AMF and the access network device.

[0249] In some embodiments, the second device is an access network device, and the first device sends a first request message directly to the second device or sends a first request message to the second device through the AMF.

[0250] S207, the second device sends a third request message to the MCIoT device.

[0251] In some embodiments, the MCIoT device receives a third request message sent by the second device, but is not limited thereto. The MCIoT device may also receive a third request message sent by a subject other than the second device, in which case S207 may be omitted.

[0252] In some embodiments, the MCIoT device obtains a third request message as defined by the protocol, in which case S207 can be omitted.

[0253] In some embodiments, the MCIoT device obtains a third request message from the upper layer(s), in which case S207 can be omitted.

[0254] In some embodiments, the MCIoT device processes the request to obtain a third request message, in which case S207 can be omitted.

[0255] In some embodiments, the MCIoT device autonomously implements the function indicated by the third request message, or the above function is a default or default setting, in which case S207 can be omitted.

[0256] In some embodiments, the third request message is used to request the MCIoT device to execute an emergency application command. The description of the emergency application command can be found in the preceding steps and will not be repeated here.

[0257] In this embodiment of the disclosure, the second device receives a first request message sent by the first device and sends a third request message to the MCIoT device.

[0258] In some embodiments, the third request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0259] In some embodiments, when the second device is a reader, the third request message is a reader to device (R2D) message.

[0260] S208, the MCIoT device sends a third response message to the second device.

[0261] In this embodiment of the disclosure, the MCIoT device receives a third request message sent by the second device and determines to execute an emergency application command based on the third request message.

[0262] In some embodiments, the MCIoT device executes an emergency application command, generates a result report, and then sends a third response message to a second device.

[0263] In some embodiments, the third response message includes a result report of the MCIoT device executing the emergency application command.

[0264] In some embodiments, the result report includes at least one of the following: the reported emergency event; the type of the reported emergency event; the priority corresponding to the type of the reported emergency event; the auxiliary dataset of the report; the identifier of the MCIoT device corresponding to the report; the identifier of the application entity corresponding to the report; the identifier of the group to which the MCIoT device corresponding to the report belongs; and the identifier of the group to which the application entity corresponding to the report belongs.

[0265] In some embodiments, the descriptions of emergency events, types of emergency events, priorities corresponding to types of emergency events, and auxiliary datasets can be found in the descriptions in the preceding steps, and will not be repeated here.

[0266] In some embodiments, different groups are formed based on the hardware or software version information of the MCIoT devices. In some embodiments, different groups are formed based on the identifier of the owner of the MCIoT devices.

[0267] In some embodiments, different groups are formed based on the hardware or software version information of the application entity. In some embodiments, different groups are formed based on the identifier of the owner of the application entity.

[0268] In some embodiments, when the second device is a reader, the third response message is a device-to-reader (D2R) message.

[0269] In some embodiments, the size of the third response message meets the message size requirement of the MCIoT device feedback result report. In some embodiments, the size of the third response message is less than or equal to the message size of the MCIoT device feedback result report.

[0270] In some embodiments, the third response message includes a NAS command response message, wherein the NAS command response message includes a result report determined by the MCIoT device executing the emergency application command.

[0271] S209, the second device sends a first response message to the first device.

[0272] In this embodiment of the disclosure, when the second device receives a third response message from the MCIoT device and determines the result report of the MCIoT device executing the emergency application command, it sends a first response message to the first device.

[0273] In some embodiments, the first response message includes a result report of the MCIoT device executing the emergency application command. The description of the result report is the same as described in the preceding steps and will not be repeated here.

[0274] In some embodiments, the first response message includes at least one of the following: an association identifier, an identifier of the second device, a NAS command response message, and the NGPID of the second device corresponding to each MCIoT device.

[0275] In some embodiments, the second device sends a first response message to the first device via AMF.

[0276] In some embodiments, if the MCIoT device does not support executing emergency application commands, a third response message is used to indicate that the MCIoT device does not support executing emergency application commands. In this case, a first response message is used to indicate that an acquisition error should be reported.

[0277] S210, the first device sends a command notification message to the third device.

[0278] In some embodiments, the command notification message includes a result report of the MCIoT device executing an emergency application command.

[0279] In some embodiments, when the first device receives a first response message from the second device, and the first response message includes a result report determined by the MCIoT device executing an emergency application command, the first device may release the MCIoT session created in S205.

[0280] In some embodiments, if the MCIoT device does not support executing emergency application commands, a third response message is used to indicate that the MCIoT device does not support executing emergency application commands. In this case, a first response message is used to indicate that an acquisition error should be reported. Based on this, a command notification message sent by the first device to the third device is used to indicate that an acquisition error should be reported. Furthermore, in subsequent processes, the first device can avoid initiating the same type of emergency application command to the MCIoT device again.

[0281] In some embodiments, the command notification message includes at least one of the following: a list of MCIoT device response information (MCIoT device ID, MCIoT data, location of each MCIoT device), application entity ID, and result report.

[0282] In some embodiments, when multiple first devices participate in the process, a third device may receive command notification messages from multiple first devices.

[0283] In some embodiments, if the command request message sent by the application entity in S201 requests to obtain the location of the MCIoT device and the location of the second device is configured, then the first device obtains the location of the MCIoT device from the second device during the inventory process in S206.

[0284] In some embodiments, the command notification message is the NMCIOTF_MCIoT_UAS command notification message.

[0285] S211, the third device sends a command response message to the application entity.

[0286] In this embodiment of the disclosure, the third device receives a command notification message sent by the first device and sends a command response message to the application entity.

[0287] In some embodiments, where the command notification message includes a result report determined by the MCIoT device executing an emergency application command, the command response message sent by the third device to the application entity includes the result report.

[0288] In some embodiments, the command response message includes a result report.

[0289] In some embodiments, the results report is used by the application entity to determine whether to trigger the execution of a first operation, the first operation including at least one of the following: further analysis and prediction; alarm; emergency operation.

[0290] In some embodiments, the application entity determines the type of emergency event reported and its corresponding priority based on the emergency events reported in the results report.

[0291] In some embodiments, the application entity determines the first action to be triggered based on the priority corresponding to the type of emergency event included in the results report.

[0292] In some embodiments, the priority corresponding to the type of emergency event included in the results report is used to indicate the priority for further analysis and prediction. Based on the results report, the application entity determines which further analysis and prediction to trigger.

[0293] In some embodiments, the priority corresponding to the type of emergency event included in the results report is used to indicate the priority for triggering an alarm. The application entity determines the trigger to execute the alarm based on the results report.

[0294] In some embodiments, the priority corresponding to the type of emergency event included in the results report is used to indicate the priority for emergency operations. The application entity determines the trigger for emergency operations based on the results report.

[0295] In some embodiments, the command response message includes at least one of the following: a list of MCIoT device response information (MCIoT device identifier, MCIoT data, location information of each MCIoT device), an application entity identifier, and a result report.

[0296] In some embodiments, the command response message is an Nnef_MCIoT_UAS command notification message.

[0297] By implementing embodiments of this disclosure, the first device can request the second device to schedule MCIoT devices to execute emergency application commands to perform emergency event detection and reporting, thereby providing reliable and efficient large-scale communication services and improving the performance of the communication system.

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

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

[0300] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

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

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

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

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

[0305] The communication method involved in the embodiments of this disclosure may include at least one of S201 to S211. For example, S201 can be implemented as an independent embodiment, S202 can be implemented as an independent embodiment, S203 can be implemented as an independent embodiment, S204 can be implemented as an independent embodiment, S205 can be implemented as an independent embodiment, S206 can be implemented as an independent embodiment, S207 can be implemented as an independent embodiment, S208 can be implemented as an independent embodiment, S209 can be implemented as an independent embodiment, S210 can be implemented as an independent embodiment, S211 can be implemented as an independent embodiment, S206+S207+S208+S209 can be implemented as an independent embodiment, and S201+S202+S204+S206+S207+S208+S209+S210+S211 can be implemented as an independent embodiment, but is not limited thereto.

[0306] In some embodiments, S203 and S204 may be executed in a different order or simultaneously, and S206 and S205 may be executed in a different order or simultaneously.

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

[0308] In some embodiments, steps S201, S202, S203, S204, S205, S210, and S211 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0309] In some embodiments, steps S203, S204, and S205 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0310] In some embodiments, S203 and S205 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0312] Figure 3A This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 3A As shown, the embodiments of this disclosure relate to a communication method, which includes:

[0313] S301A, the first device sends a first request message to the second device.

[0314] The optional implementations of S301A can be found in [reference needed]. Figure 2 Optional implementations of S206, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0315] In some embodiments, the first request message is used to request the second device to schedule the MCIoT device to execute an emergency application command.

[0316] In some embodiments, the method further includes: a first device receiving a first response message sent by a second device, the first response message including a result report determined by the MCIoT device executing an emergency application command.

[0317] In some embodiments, the method further includes: a first device receiving a second request message sent by a third device, the second request message being used to instruct an application entity to request an MCIoT device to execute an emergency application command, the second request message being sent by the third device upon receiving a command request message sent by the application entity, the command request message being used to request the MCIoT device to execute an emergency application command; and determining a second device based on the second request message.

[0318] In some embodiments, the method further includes: the first device determining that an authorized application entity initiates a request to instruct the MCIoT device to execute an emergency application command.

[0319] In some embodiments, the method further includes: the first device sending a second response message to the third device, the second response message indicating that the second request message is accepted.

[0320] In some embodiments, the method further includes: a first device sending a command notification message to a third device, the command notification message including a result report of the MCIoT device executing an emergency application command, and the command notification message being used by the third device to send a command response message to the application entity, the command response message including the result report.

[0321] In some embodiments, at least one of the first request message, the second request message, and the command request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0322] In some embodiments, the emergency application command is used to instruct the detection of an emergency event. The emergency application command includes at least one of the following information: the emergency event; the type of the emergency event; the priority corresponding to the type of emergency event; and the auxiliary dataset to be provided.

[0323] In some embodiments, the types of emergency events include at least one of: transient pressure peak, acoustic leakage characteristics, and early warning signals of pipeline malfunctions; and / or the priorities corresponding to the types of emergency events include: priorities for indicating further analysis and prediction, priorities for indicating alarm triggering, and priorities for indicating emergency operations; and / or the auxiliary datasets to be provided include at least one of: measured values, maximum values, minimum values, location information, power status, operation time period, timestamps of emergency events, frequency of emergency events, and number of emergency events.

[0324] In some embodiments, the result report includes at least one of the following: the reported emergency event; the type of the reported emergency event; the priority corresponding to the type of the reported emergency event; the auxiliary dataset of the report; the identifier of the MCIoT device corresponding to the report; the identifier of the application entity corresponding to the report; the identifier of the group to which the MCIoT device corresponding to the report belongs; and the identifier of the group to which the application entity corresponding to the report belongs.

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

[0326] Figure 3B This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 3B As shown, the embodiments of this disclosure relate to a communication method, which includes:

[0327] S301B, the second device receives the first request message sent by the first device.

[0328] The optional implementations of S301B can be found in [reference needed]. Figure 2 Optional implementations of S206, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0329] In some embodiments, the first request message is used to request the second device to schedule the MCIoT device to execute an emergency application command.

[0330] S302B, the second device sends a third request message to the MCIoT device.

[0331] The optional implementation methods of S302B can be found in [reference needed]. Figure 2 Optional implementations of S207, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0332] In some embodiments, the third request message is used to request the MCIoT device to execute an emergency application command.

[0333] In some embodiments, the method further includes: a second device receiving a third response message sent by an MCIoT device, the third response message including a result report determined by the MCIoT device executing an emergency application command.

[0334] In some embodiments, the method further includes: the second device sending a first response message to the first device, the first response message including a result report determined by the MCIoT device executing an emergency application command.

[0335] In some embodiments, at least one of the first request message and the third request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0336] In some embodiments, the emergency application command is used to instruct the detection of an emergency event. The emergency application command includes at least one of the following information: the emergency event; the type of the emergency event; the priority corresponding to the type of emergency event; and the auxiliary dataset to be provided.

[0337] In some embodiments, the types of emergency events include at least one of: transient pressure peak, acoustic leakage characteristics, and early warning signals of pipeline malfunctions; and / or the priorities corresponding to the types of emergency events include: priorities for indicating further analysis and prediction, priorities for indicating alarm triggering, and priorities for indicating emergency operations; and / or the auxiliary datasets to be provided include at least one of: measured values, maximum values, minimum values, location information, power status, operation time period, timestamps of emergency events, frequency of emergency events, and number of emergency events.

[0338] In some embodiments, the result report includes at least one of the following: the reported emergency event; the type of the reported emergency event; the priority corresponding to the type of the reported emergency event; the auxiliary dataset of the report; the identifier of the MCIoT device corresponding to the report; the identifier of the application entity corresponding to the report; the identifier of the group to which the MCIoT device corresponding to the report belongs; and the identifier of the group to which the application entity corresponding to the report belongs.

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

[0340] Figure 3C This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 3C As shown, the embodiments of this disclosure relate to a communication method, which includes:

[0341] S301C, the third device receives a command request message sent by the application entity.

[0342] The optional implementations of S301C can be found in [reference needed]. Figure 2 Optional implementations of S201, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0343] In some embodiments, the command request message is used to request the MCIoT device to execute an emergency application command.

[0344] S302C, the third device sends a second request message to the first device.

[0345] The optional implementations of S302C can be found in [reference needed]. Figure 2 Optional implementations of S202, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0346] In some embodiments, the second request message is used to instruct the application entity to request the MCIoT device to execute an emergency application command. The second request message is used by the first device to determine and send a first request message to the second device. The first request message is used to request the second device to schedule the MCIoT device to execute the emergency application command.

[0347] In some embodiments, the second request message is used by the first device to determine that an authorized application entity has initiated a request to instruct the MCIoT device to execute an emergency application command.

[0348] In some embodiments, the method further includes: a third device receiving a second response message sent by a first device, the second response message indicating that the second request message is accepted.

[0349] In some embodiments, the method further includes: a third device receiving a command notification message sent by a first device, the command notification message including a result report of the MCIoT device executing an emergency application command requested by the application entity.

[0350] In some embodiments, the method further includes: a third device sending a command response message to an application entity, the command response message including a result report, the result report being used by the application entity to determine whether to trigger the execution of a first operation, the first operation including at least one of the following: further analysis and prediction; alarm; emergency operation.

[0351] In some embodiments, at least one of the command request message, the second request message, and the first request message includes at least one of the following: the message size of the MCIoT device feedback result report; the number of MCIoT devices.

[0352] In some embodiments, the emergency application command is used to instruct the detection of an emergency event. The emergency application command includes at least one of the following information: the emergency event; the type of the emergency event; the priority corresponding to the type of emergency event; and the auxiliary dataset to be provided.

[0353] In some embodiments, the types of emergency events include at least one of: transient pressure peak, acoustic leakage characteristics, and early warning signals of pipeline malfunctions; and / or the priorities corresponding to the types of emergency events include: priorities for indicating further analysis and prediction, priorities for indicating alarm triggering, and priorities for indicating emergency operations; and / or the auxiliary datasets to be provided include at least one of: measured values, maximum values, minimum values, location information, power status, operation time period, timestamps of emergency events, frequency of emergency events, and number of emergency events.

[0354] In some embodiments, the result report includes at least one of the following: the reported emergency event; the type of the reported emergency event; the priority corresponding to the type of the reported emergency event; the auxiliary dataset of the report; the identifier of the MCIoT device corresponding to the report; the identifier of the application entity corresponding to the report; the identifier of the group to which the MCIoT device corresponding to the report belongs; and the identifier of the group to which the application entity corresponding to the report belongs.

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

[0356] To facilitate understanding of the embodiments of this disclosure, an exemplary embodiment is provided.

[0357] This disclosure provides a method for supporting specific meters and result notifications for alarm and emergency communications, in order to reliably and efficiently support large-scale communication services.

[0358] Application functions (AF, or application functions located in the UE) and MCIoT devices support emergency application-specific commands (based on the indicated alarm or emergency type, the priority of the alarm or emergency type, and the required additional dataset) and emergency application-specific command results (measurements, alarm or emergency priority, assistant reports, including frequency, location information, power status, operation slots, event timestamps, etc.), which are transmitted in the application layer container.

[0359] -MCIoTF, application functions (AF, or application functions located in the UE), and NEF support the transmission of application layer containers (emergency application-specific commands and emergency application-specific command results as described above) in command request and notification messages.

[0360] -MCIoTF and MCIoT devices support emergency application-specific commands at the NAS layer.

[0361] - Emergency application-specific commands, including one or more of the following information:

[0362] a) Specified alarm or emergency types, such as instantaneous pressure peaks, acoustic leak signals, and early indications of pipeline failures;

[0363] b) Alarm or emergency type priority, for example, low priority is used for further analysis and prediction, medium priority is used to trigger alarms, and high priority is used for emergency operations such as disconnection or shutdown.

[0364] c) Required auxiliary datasets, such as measured values, maximum or minimum values, timestamps of abnormal events, frequency of abnormal events, number of abnormal events, location information, power status, operation time period, and timestamps of abnormal events.

[0365] - Results of emergency application-specific commands, including one or more of the following:

[0366] a) Reported alarm or emergency types, such as instantaneous pressure peaks, acoustic leak characteristics, early indications of pipeline failure;

[0367] b) The priority of the alarm or emergency type reported, such as low priority for further analysis and prediction, medium priority for alarm triggering, and high priority for emergency operations, including disconnection or shutdown, etc.

[0368] c) Auxiliary datasets for the report, such as measured values, maximum or minimum values, timestamps of abnormal events, frequency of abnormal events, number of times abnormal events occurred, location information, power status, operation time period, and timestamps of abnormal events;

[0369] d) The reported device ID;

[0370] e) The target application ID of the report;

[0371] f) Reported group / dependency IDs (e.g., hardware / software version information, owner ID, family or team ID).

[0372] like Figure 4 As shown, this is the emergency application-specific command flow.

[0373] 1. The application entity (AF, or application function located in the UE as shown in 1a) sends an Nnef_6G MCIoT_UAS command request (AF ID, command type, information about the target device, external target area information, approximate number of devices, approximate size of the D2R message, command type specific parameters, and requested location information) to the NEF.

[0374] In some embodiments, the Nnef_6G MCIoT_UAS command request can also be referred to as the Nnef_MCIoT_UAS command request. Here, Nnef is the interface between the application entity (application function in the AF or UE) and the NEF.

[0375] In some embodiments, in the Nnef_6G MCIoT_UAS command request, AF sets the command type to an emergency application-specific command and includes command details in the "Emergency Application Command Information" parameter, which is an application-layer container. AF also provides the size of the command response message.

[0376] In some embodiments, emergency application specific commands include one or more of the following information:

[0377] a) Specified alarm or emergency types, such as instantaneous pressure peaks, acoustic leak signals, and early indications of pipeline failures;

[0378] b) Alarm or emergency type priority, for example, low priority is used for further analysis and prediction, medium priority is used to trigger alarms, and high priority is used for emergency operations, including disconnection or shutdown, etc.

[0379] c) Required auxiliary datasets, such as measured values, maximum or minimum values, timestamps of abnormal events, frequency of abnormal events, number of abnormal events, location information, power status, operation time period, and timestamps of abnormal events.

[0380] In some embodiments, information about the target device may include filtering information or a complete device identifier.

[0381] In some embodiments, if an approximate number of devices is provided, it is used to indicate the number of devices expected to respond to this service operation request, which is sent by MCIOTF to the NG-RAN auxiliary information.

[0382] In some embodiments, the command type provides the operation to be performed, and the command type-specific parameters provide the parameters required for that operation.

[0383] 2. It is used for external target area information processing and MCIOTF selection, and the following description is provided:

[0384] - If MCIOTF fails, NEF will reject the command request and proceed to step 6 of this procedure.

[0385] 3. NEF sends an NMCIOTF_6G MCIoT_UAS command request (AF ID, command type, target device information, external target area information, approximate number of devices, approximate size of D2R message, command type specific parameters, and requested location information) to the selected MCIOTF.

[0386] In some embodiments, the NMCIOTF_6G MCIoT_UAS command request can also be referred to as the NMCIOTF_MCIoT_UAS command request. Here, NMCIOTF is the interface between NEF and MCIOTF.

[0387] In some embodiments, NEF sends a command request message to MCIOTF(s) containing emergency application-specific commands, including one or more of the following:

[0388] a) The type of alarm or emergency indicated, such as instantaneous pressure peaks, acoustic leak characteristics, or early indicators of pipeline failure;

[0389] b) Alarm or emergency type priority, such as low priority for further analysis and prediction, medium priority for triggering alarms, and high priority for emergency operations (including disconnection or shutdown).

[0390] c) Required auxiliary datasets, such as measured values, maximum or minimum values, timestamps of abnormal events, frequency of abnormal events, number of abnormal events, location information, power status, operation time period, and timestamps of abnormal events.

[0391] 4. MCIOTF receives the NMCIOTF_6G MCIoT_UAS command request and examines the parameters contained in the request. MCIOTF performs reader / writer selection. If it cannot select NG-RAN or a reader / writer, MCIOTF will reject the command request with an appropriate reason code.

[0392] In some embodiments, the NMCIOTF_6G MCIoT_UAS command request can also be referred to as the NMCIOTF_MCIoT_UAS command request.

[0393] In some embodiments, MCIOTF performs AF authorization to check whether the AF is authorized to send urgent application-specific commands.

[0394] In some embodiments, MCIOTF generates an association ID for the service operation request, and this association ID is used by MCIOTF to associate the service operation response received from NG-RAN with the request. MCIOTF creates an MCIoT session for the AF service operation request, and this session is identified by the association ID.

[0395] In some embodiments, MCIOTF performs reader / writer selection. If NG-RAN or a reader / writer cannot be selected, MCIOTF will reject the service operation request with an appropriate reason code.

[0396] In some embodiments, MCIOTF determines auxiliary information while taking into account parameters provided in the AIoT service operation request.

[0397] In some embodiments, MCIOTF performs AF authorization on service operation requests.

[0398] In some embodiments, MCIOTF can perform AMF selection.

[0399] 5. MCIOTF sends an NMCIOTF_6G MCIoT_UAS command response message to NEF (accept or reject, [reason code]).

[0400] 6. NEF sends an Nnef_6G MCIoT_UAS command response message (accept or reject, [reason code]) to AF. If the response is a rejection, the process stops here.

[0401] In some embodiments, the Nnef_6G MCIoT_UAS command response can also be referred to as the Nnef_MCIoT_UAS command response.

[0402] 7. The UAS command measures the device for confirmation or selection, such as performing an inventory process. MCIOTF includes subsequent command instructions in the inventory request message to notify NG-RAN to transmit commands after inventory is complete. NG-RAN also includes the RAN MCIoT device NGAID for each device in the inventory report. MCIOTF updates the corresponding device context in MCIOTF to include the RANMCIoT device NGAID.

[0403] In some embodiments, if no successful inventory response is received, steps 8-11 will not be executed, and MCIOTF will send a failure report to NEF in step 12.

[0404] 8. For each successfully received inventory response, MCIOTF sends a command request message directly to NG-RAN (association ID, [reader ID], NAS command request, [approximate D2R message size], and the RAN AIoT device NGAP ID for each AIoT device), or sends it via AMF as NGAP MCIoT information. The NAS UAS command request message contains MCIoT data. The association ID is the same as the association ID generated in step 4. The RAN MCIoT device NGAP ID for each device is used by NG-RAN to determine the MCIoT device context within NG-RAN.

[0405] In some embodiments, for emergency application-specific commands, MCIOTF constructs a NAS emergency application-specific command request and sends it to the MCIoT device. The NAS request message includes emergency application command information parameters. In the auxiliary information provided to NG-RAN, MCIOTF uses the command response message size from the AF.

[0406] In some embodiments, MCIOTF uses the command type and command type-specific parameters received in step 3 to determine the NAS command request to be sent to the AIoT device.

[0407] It should be noted that command requests can be sent to NG-RAN while the inventory process is in progress.

[0408] 9. The UAS container is provided by NG-RAN (e.g., via AS R2D messages). NG-RAN sends AS R2D messages (NAS command requests) to the MCIoT device.

[0409] In some embodiments, after receiving a NAS emergency application-specific command request in an AS R2D message, the MCIoT device will execute the command in the application command information parameters.

[0410] 10. UAS result reports are provided by the MCIoT device (e.g., via ASD2R messages). The MCIoT device performs a security check on the received NAS command request and sends an ASD2R message (including the NAS command response) to the NG-RAN. The NAS command response message may include MCIoT data.

[0411] 11. NG-RAN will respond to MCIOTF directly via a command response message (association ID, reader ID, NAS command response, RAN MCIoT device NGAP ID), or via AMF as NGAP MCIoT information. MCIOTF determines the MCIoT device context based on the received RAN MCIoT device NGPID.

[0412] In some embodiments, the MCIoT device constructs a NAS emergency application-specific command response message and includes the command execution result in the emergency application-specific command result parameter, which is also an application-layer container. The MCIoT device then sends the NAS emergency application-specific command response message to the MCIOTF.

[0413] In some embodiments, the results of an emergency application of a specific command include one or more of the following information:

[0414] a) Reported alarm or emergency types, such as instantaneous pressure peaks, acoustic leak characteristics, early indications of pipeline failure;

[0415] b) The priority of the alarm or emergency type reported, such as low priority for further analysis and prediction, medium priority for alarm triggering, and high priority for emergency operations, including disconnection or shutdown, etc.

[0416] c) Auxiliary datasets for the report, such as measured values, maximum or minimum values, timestamps of abnormal events, frequency of abnormal events, time of abnormal events, location information, power status, operation time period, and timestamps of abnormal events;

[0417] d) The reported device ID;

[0418] e) The target application ID of the report;

[0419] f) Reported group / dependency IDs (e.g., hardware / software version information, owner ID, family or team ID).

[0420] In some embodiments, if the NAS command response indicates that the NAS command type is not supported by the MCIoT device, MCIOTF will report an error result in steps 13 and 14.

[0421] It should be noted that MCIOTF can take this into account by implementing a process that avoids initiating further command flows of the same command type to MCIoT devices.

[0422] 12. After receiving the inventory completion indication from the previous inventory report from NG-RAN, when MCIOTF has completed sending command requests and all command responses have been received, MCIOTF initiates the MCIoT session release procedure to release the MCIoT session created during the inventory procedure.

[0423] 13. The MCIOTF reports the results of the NMCIOTF_MCIoT_UAS command request to the NEF by sending an NMCIOTF_MCIoT_UAS command notification message (including a list of MCIoT device response information (MCIoT device ID, MCIoT data, and optionally the location of each MCIoT device), and the AF ID [Final Report Indicator]). If multiple MCIOTFs are involved in this process, the NEF may receive NMCIOTF_MCIoT_UAS command notification messages from multiple MCIOTFs.

[0424] In some embodiments, MCIOTF includes the results of emergency application-specific commands as MCIoT data in the command notification message.

[0425] In some embodiments, depending on the operator policy, if the AF requests location information and the location of the reader is configured, the MCIOTF will use the reader ID reported from NG-RAN during the inventory process in step 7 to determine the location of the MCIoT device.

[0426] In some embodiments, MCIOTF terminates the MCIoT session when the last report is sent.

[0427] 14. The NEF notifies the application entity (AF, or application function 1a in the UE) of the result of the Nnef_MCIoT_UAS command request by sending an Nnef_MCIoT_UAS Command Notify message (a list of MCIoT device response information (MCIoT device ID, MCIoT data, and location information of each MCIoT device (optional)), AF ID, [last report indication], and emergency application-specific command result).

[0428] In some embodiments, NEF forwards the results of emergency application-specific commands as MCIoT data in command notification messages to trigger further analysis, prediction, or to trigger alarms or perform actions (disconnect, shut off gas).

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

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

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

[0432] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a 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 using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), 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), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0433] Figure 5A This is a schematic diagram of the structure of the first device 1 proposed in an embodiment of this disclosure. Figure 5A As shown, the first device 1 may include at least one of the following: a transceiver module 11, a processing module 12, etc.

[0434] In some embodiments, the transceiver module 11 is configured to send a first request message to the second device, the first request message being used to request the second device to schedule the MCIoT device to execute an emergency application command.

[0435] Optionally, the transceiver module 11 is used to perform at least one of the communication steps such as sending and / or receiving performed by the first device 1 in any of the above methods (e.g., the communication steps such as sending and / or receiving performed by the first device 1 in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto), which will not be elaborated here. Optionally, the processing module 12 is used to perform at least one of the other steps performed by the first device 1 in any of the above methods (e.g., other steps besides the communication steps such as sending and / or receiving performed by the first device 1 in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto), which will not be elaborated here.

[0436] In some embodiments, the transceiver module may include a sending module and / or a receiving module, which may be separate or integrated together.

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

[0438] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0439] Figure 5B This is a schematic diagram of the structure of the second device 2 proposed in an embodiment of this disclosure. (See attached diagram.) Figure 5B As shown, the second device 2 may include at least one of the following: transceiver module 21, processing module 22, etc.

[0440] In some embodiments, the transceiver module 21 is configured to receive a first request message sent by the first device, the first request message being used to request the second device to schedule the MCIoT device to execute an emergency application command; the transceiver module 21 is also configured to send a third request message to the MCIoT device, the third request message being used to request the MCIoT device to execute an emergency application command.

[0441] Optionally, the transceiver module 21 is used to perform at least one of the communication steps such as sending and / or receiving performed by the second device 2 in any of the above methods (e.g., the communication steps such as sending and / or receiving performed by the second device 2 in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto), which will not be elaborated here. Optionally, the processing module 22 is used to perform at least one of the other steps performed by the second device 2 in any of the above methods (e.g., other steps besides the communication steps such as sending and / or receiving performed by the second device 2 in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto), which will not be elaborated here.

[0442] In some embodiments, the transceiver module may include a sending module and / or a receiving module, which may be separate or integrated together.

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

[0444] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0445] Figure 5C This is a schematic diagram of the structure of the third device 3 proposed in an embodiment of this disclosure. For example... Figure 5C As shown, the third device 3 may include at least one of the following: transceiver module 31, processing module 32, etc.

[0446] In some embodiments, the transceiver module 31 is configured to receive a command request message sent by an application entity, the command request message being used to request the MCIoT device to execute an emergency application command; the transceiver module 31 is also configured to send a second request message to the first device, the second request message being used to instruct the application entity to request the MCIoT device to execute an emergency application command, the second request message being used by the first device to determine and send a first request message to the second device, the first request message being used to request the second device to schedule the MCIoT device to execute the emergency application command.

[0447] Optionally, the transceiver module 21 is used to perform at least one of the communication steps such as sending and / or receiving performed by the third device 3 in any of the above methods (e.g., the communication steps such as sending and / or receiving performed by the third device 3 in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto), which will not be elaborated here. Optionally, the processing module 22 is used to perform at least one of the other steps performed by the third device 3 in any of the above methods (e.g., other steps besides the communication steps such as sending and / or receiving performed by the third device 3 in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto), which will not be elaborated here.

[0448] In some embodiments, the transceiver module may include a sending module and / or a receiving module, which may be separate or integrated together.

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

[0450] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0451] Figure 6A This is a schematic diagram of the structure of the communication device 5100 proposed in this embodiment. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 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.

[0452] like Figure 6A As shown, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0453] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceivers 5102 perform at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., the sending and / or receiving steps in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., steps other than sending and / or receiving in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto). In optional embodiments, the transceivers may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.

[0454] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

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

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

[0457] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

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

[0459] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., the sending and / or receiving steps in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, chip 5200, memory 5203, or transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps other than sending and / or receiving in S201-S211, S301A, S301B-S302B, S301C-S302C, but not limited thereto).

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

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

[0462] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

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

[0464] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0465] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0466] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method is performed by a first device and includes: A first request message is sent to the second device, the first request message being used to request the second device to schedule large-scale cellular Internet of Things (MCIoT) devices to execute emergency application commands.

2. The method as described in claim 1, characterized in that, The method further includes: The device receives a first response message sent by the second device, the first response message including a result report determined by the MCIoT device executing the emergency application command.

3. The method as described in claim 1 or 2, characterized in that, The method further includes: The system receives a second request message sent by a third device. The second request message is used to instruct the application entity to request the MCIoT device to execute the emergency application command. The second request message is sent by the third device after receiving a command request message sent by the application entity. The command request message is used to request the MCIoT device to execute the emergency application command. The second device is determined based on the second request message.

4. The method as described in claim 3, characterized in that, The method further includes: The application entity is authorized to initiate a request instructing the MCIoT device to execute the emergency application command.

5. The method as described in claim 3 or 4, characterized in that, The method further includes: A second response message is sent to the third device, the second response message indicating that the second request message is accepted.

6. The method according to any one of claims 3 to 5, characterized in that, The method further includes: A command notification message is sent to the third device. The command notification message includes a result report of the MCIoT device executing the emergency application command. The command notification message is used by the third device to send a command response message to the application entity. The command response message includes the result report.

7. The method according to any one of claims 1 to 6, characterized in that, At least one of the first request message, the second request message, and the command request message includes at least one of the following: The message size of the MCIoT device's feedback result report; The number of MCIoT devices.

8. The method according to any one of claims 1 to 7, characterized in that, The emergency application command is used to instruct the detection of an emergency event, and the emergency application command includes at least one of the following: Emergency; Types of emergencies; The priority corresponding to the type of emergency; Required auxiliary dataset.

9. The method as described in claim 8, characterized in that, The types of emergency events include at least one of the following: transient pressure peaks, acoustic leakage characteristics, and early warning signals of pipeline malfunctions; and / or The priorities corresponding to the types of emergency events include: priorities for indicating further analysis and prediction, priorities for indicating alarm triggering, priorities for indicating emergency operations; and / or The required auxiliary dataset includes at least one of the following: measured values, maximum values, minimum values, location information, power status, operation time period, timestamp of emergency event occurrence, frequency of emergency event occurrence, and number of emergency events.

10. The method as described in claim 2 or 6, characterized in that, The results report includes at least one of the following: Reported emergency; The type of emergency reported; The priority corresponding to the type of emergency reported; Auxiliary dataset for the report; The report corresponds to the identifier of the MCIoT device; The identifier of the application entity corresponding to the report; The report includes the identifier of the group to which the MCIoT device belongs; The identifier of the group to which the application entity corresponding to the report belongs.

11. A communication method, characterized in that, The method is performed by a second device and includes: Receive a first request message sent by the first device, the first request message being used to request the second device to schedule the MCIoT device to execute an emergency application command; A third request message is sent to the MCIoT device, the third request message being used to request the MCIoT device to execute the emergency application command.

12. The method as described in claim 11, characterized in that, The method further includes: Receive a third response message sent by the MCIoT device, the third response message including a result report determined by the MCIoT device executing the emergency application command.

13. The method as described in claim 11 or 12, characterized in that, The method further includes: Send a first response message to the first device, the first response message including a result report determined by the MCIoT device executing the emergency application command.

14. The method as described in claim 11 or 12, characterized in that, At least one of the first request message and the third request message includes at least one of the following: The message size of the MCIoT device's feedback result report; The number of MCIoT devices.

15. The method according to any one of claims 11 to 13, characterized in that, The emergency application command is used to instruct the detection of an emergency event, and the emergency application command includes at least one of the following: Emergency; Types of emergencies; The priority corresponding to the type of emergency; Required auxiliary dataset.

16. The method as described in claim 15, characterized in that, The types of emergency events include at least one of the following: transient pressure peaks, acoustic leakage characteristics, and early warning signals of pipeline malfunctions; and / or The priorities corresponding to the types of emergency events include: priorities for indicating further analysis and prediction, priorities for indicating alarm triggering, priorities for indicating emergency operations; and / or The required auxiliary dataset includes at least one of the following: measured values, maximum values, minimum values, location information, power status, operation time period, timestamp of emergency event occurrence, frequency of emergency event occurrence, and number of emergency events.

17. The method as described in claim 12 or 13, characterized in that, The results report includes at least one of the following: Reported emergency; The type of emergency reported; The priority corresponding to the type of emergency reported; Auxiliary dataset for the report; The report corresponds to the identifier of the MCIoT device; The identifier of the application entity corresponding to the report; The report includes the identifier of the group to which the MCIoT device belongs; The identifier of the group to which the application entity corresponding to the report belongs.

18. A communication method, characterized in that, The method is performed by a third device and includes: Receive a command request message sent by an application entity, the command request message being used to request the MCIoT device to execute an emergency application command; A second request message is sent to the first device. The second request message is used to instruct the application entity to request the MCIoT device to execute the emergency application command. The second request message is used by the first device to determine and send a first request message to the second device. The first request message is used to request the second device to schedule the MCIoT device to execute the emergency application command.

19. The method as described in claim 18, characterized in that, The second request message is used by the first device to determine and authorize the application entity to initiate a request instructing the MCIoT device to execute the emergency application command.

20. The method as described in claim 18 or 19, characterized in that, The method further includes: The device receives a second response message sent by the first device, the second response message indicating that it accepts the second request message.

21. The method as described in claim 20, characterized in that, The method further includes: Send an instruction message to the application entity, the instruction message being used to indicate acceptance of the command request message.

22. The method according to any one of claims 18 to 21, characterized in that, The method further includes: The system receives a command notification message sent by the first device, the command notification message including a result report of the MCIoT device executing the emergency application command as requested by the application entity.

23. The method as described in claim 22, characterized in that, The method further includes: A command response message is sent to the application entity, the command response message including the result report, the result report being used by the application entity to determine whether to trigger the execution of a first operation, the first operation including at least one of the following: further analysis and prediction; alarm; emergency operation.

24. The method according to any one of claims 18 to 23, characterized in that, At least one of the command request message, the second request message, and the first request message includes at least one of the following: The message size of the MCIoT device's feedback result report; The number of MCIoT devices.

25. The method according to any one of claims 18 to 24, characterized in that, The emergency application command is used to instruct the detection of an emergency event, and the emergency application command includes at least one of the following: Emergency; Types of emergencies; The priority corresponding to the type of emergency; Required auxiliary dataset.

26. The method as described in claim 25, characterized in that, The types of emergency events include at least one of the following: transient pressure peaks, acoustic leakage characteristics, and early warning signals of pipeline malfunctions; and / or The priorities corresponding to the types of emergency events include: priorities for indicating further analysis and prediction, priorities for indicating alarm triggering, priorities for indicating emergency operations; and / or The required auxiliary dataset includes at least one of the following: measured values, maximum values, minimum values, location information, power status, operation time period, timestamp of emergency event occurrence, frequency of emergency event occurrence, and number of emergency events.

27. The method as described in claim 22 or 23, characterized in that, The results report includes at least one of the following: Reported emergency; The type of emergency reported; The priority corresponding to the type of emergency reported; Auxiliary dataset for the report; The report corresponds to the identifier of the MCIoT device; The identifier of the application entity corresponding to the report; The report includes the identifier of the group to which the MCIoT device belongs; The identifier of the group to which the application entity corresponding to the report belongs.

28. A communication device, characterized in that, The communication device is used to perform the method according to any one of claims 1 to 10, 11 to 17, and 18 to 27.

29. A communication system, characterized in that, The device includes a first device, a second device, and a third device, wherein the first device is configured to implement the method of any one of claims 1 to 10, the second device is configured to implement the method of any one of claims 11 to 17, and the third device is configured to implement the method of any one of claims 18 to 27.

30. A storage medium storing instructions, characterized in that, When the instructions are executed on a communication device, the communication device performs the method as described in any one of claims 1 to 10, 11 to 17, and 18 to 27.

31. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the method according to any one of claims 1 to 10, 11 to 17, and 18 to 27.

Images