Internet of Things message interaction method and device, terminal, network equipment and server

Abstract

The invention provides an Internet of Things message interaction method and device, a terminal, network equipment and a server, and relates to the technical field of communication, the Internet of Things message interaction method is applied to the network equipment, and the method comprises the following steps: receiving a first data channel DC message sent by a first terminal in a conversation process between the first terminal and a second terminal, the first DC message comprises a related message sent by the first terminal to the Internet of Things terminal; performing packaging processing on the first DC message to obtain an Internet of Things message; and sending the Internet of Things message to an Internet of Things message server, wherein the Internet of Things message server is used for sending the Internet of Things message to the Internet of Things terminal. According to the invention, the network equipment supporting the IMS data channel can support the transmission of the Internet of Things message, so that the interaction between the first terminal and the 5G Internet of Things message terminal in the conversation process between the first terminal (i.e., the DC terminal) and the second terminal is realized.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to an Internet of Things (IoT) message interaction method, apparatus, terminal, network device, and server. Background Technology

[0002] With the development of new 5G voice services, the demands for expanded communication capabilities are increasing, especially with the introduction of more terminal types, such as home terminals, and more diversified communication methods. For example, real-time messages can be sent to home voice terminals using IP Multimedia Subsystem (IMS) Data Channel (DC) technology, enabling interaction with multiple terminal types. Currently, IoT applications are also booming, introducing diverse IoT terminal devices in fields such as smart healthcare and smart homes. IoT messaging, as an important interaction method for terminal devices, features high capacity and low latency, leading to a growing demand from users for real-time interaction with IoT devices.

[0003] However, the DC technology involved in the existing technology is mostly used in smart terminals and in call-related business areas such as 5G new calls. It requires the terminal to support IMS call capabilities, but it is difficult to independently support interaction between other types of terminals (such as IoT devices) during a call. Summary of the Invention

[0004] This invention provides an IoT message interaction method, apparatus, terminal, network device, and server to solve the problem that existing DC technology cannot support the interaction between the terminal and the IoT device terminal during a call.

[0005] To address the aforementioned technical problems, the embodiments of the present invention provide the following technical solutions:

[0006] In a first aspect, embodiments of the present invention provide an Internet of Things (IoT) message interaction method, applied to a network device, the method comprising:

[0007] During a call between the first terminal and the second terminal, a first data channel DC message is received from the first terminal. The first DC message includes relevant messages sent by the first terminal to the IoT terminal.

[0008] The first DC message is encapsulated to obtain an IoT message;

[0009] The IoT message is sent to the IoT message server, which is used to send the IoT message to the IoT terminal.

[0010] Optionally, the method further includes:

[0011] Receive a first receipt message sent by the IoT message server, wherein the first receipt message is a receipt message for the IoT message;

[0012] The first receipt message is encapsulated to obtain the second DC message;

[0013] Send the second DC message to the first terminal.

[0014] Optionally, the method further includes:

[0015] If the application data channel ADC between the first terminal and the network device is detected to be unavailable or closed, a first indication message is sent to the IoT message server, the first indication message being used to indicate that the IoT message sending has failed.

[0016] Optionally, the method further includes:

[0017] Send a first request message to the IoT message server. The first request message is used to register with the IoT message server and carries the identifier of the application server AS of the network device.

[0018] The system receives a first response message from the IoT message server, which indicates that the network device has successfully registered.

[0019] Optionally, the IoT message includes at least one of the following:

[0020] The identifier of the first terminal;

[0021] The identifier of the IoT terminal;

[0022] The identifier of the IoT message;

[0023] The forwarding parameters of the IoT message;

[0024] The storage parameters of the IoT message.

[0025] Optionally, the first receipt message includes at least one of the following:

[0026] The identifier of the first terminal;

[0027] The identifier of the IoT terminal;

[0028] The identifier of the first receipt message;

[0029] The sending status information of the first receipt message.

[0030] Secondly, embodiments of the present invention also provide an Internet of Things (IoT) message interaction method, applied to a first terminal, the method comprising:

[0031] During a call with the second terminal, a first DC message is sent to the network device. The first DC message includes relevant messages sent by the first terminal to the IoT terminal.

[0032] Optionally, the method includes:

[0033] Receive the second DC message sent by the network device;

[0034] The second DC message is obtained by the network device encapsulating the first receipt message, which is a receipt message for an IoT message.

[0035] Optionally, the first receipt message includes at least one of the following:

[0036] The identifier of the first terminal;

[0037] Identification of IoT terminals;

[0038] The identifier of the first receipt message;

[0039] The sending status information of the first receipt message.

[0040] Thirdly, embodiments of the present invention also provide an Internet of Things (IoT) message interaction method, applied to an IoT message server, the method comprising:

[0041] Receive IoT messages sent by network devices;

[0042] Send the IoT message to the IoT terminal.

[0043] Optionally, the method further includes:

[0044] Send a first receipt message to the network device, wherein the first receipt message is a receipt message for the IoT message.

[0045] Optionally, the method further includes:

[0046] The system receives a first indication message sent by the network device, the first indication message being used to indicate that the IoT message transmission failed.

[0047] Optionally, the method further includes:

[0048] The system receives a first request message sent by the network device, the first request message being used to register with the IoT message server, and the first request message carrying the identifier of the AS of the network device.

[0049] A first response message is sent to the network device, the first response message being used to indicate that the network device has successfully registered.

[0050] Optionally, the IoT message includes at least one of the following:

[0051] The identifier of the first terminal;

[0052] The identifier of the IoT terminal;

[0053] The identifier of the IoT message;

[0054] The forwarding parameters of the IoT message;

[0055] The storage parameters of the IoT message.

[0056] Fourthly, embodiments of the present invention also provide an Internet of Things (IoT) message interaction device, the device comprising:

[0057] The first receiving module is configured to receive a first data channel DC message sent by the first terminal, the first DC message including relevant messages sent by the first terminal to the Internet of Things terminal;

[0058] The first processing module is used to encapsulate and process the DC message from the first data channel to obtain an IoT message;

[0059] The first sending module is used to send the IoT message to the IoT message server, and the IoT message server is used to send the IoT message to the IoT terminal.

[0060] Fifthly, embodiments of the present invention also provide an Internet of Things (IoT) message interaction device, the device comprising:

[0061] The second sending module is used to send a first DC message to the network device, the first DC message including relevant messages sent by the first terminal to the Internet of Things terminal.

[0062] Sixthly, embodiments of the present invention also provide an Internet of Things (IoT) message interaction device, the device comprising:

[0063] The second receiving module is used to receive IoT messages sent by network devices;

[0064] The third sending module is used to send the IoT message to the IoT terminal.

[0065] In a seventh aspect, embodiments of the present invention also provide a network device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, it implements the steps of the Internet of Things message interaction method as described in any one of the first aspects.

[0066] Eighthly, embodiments of the present invention also provide a terminal, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the Internet of Things message interaction method as described in any one of the second aspects.

[0067] In a ninth aspect, embodiments of the present invention also provide an Internet of Things (IoT) message server, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the IoT message interaction method as described in any one of the third aspects.

[0068] In a tenth aspect, embodiments of the present invention also provide a readable storage medium storing a program, which, when executed by a processor, implements the steps of the IoT message interaction method as described in any one of the first aspects, or implements the steps of the IoT message interaction method as described in any one of the second aspects, or implements the steps of the IoT message interaction method as described in any one of the third aspects.

[0069] Eleventhly, embodiments of the present invention also provide a computer program product, including computer instructions, which, when executed by a processor, implement the steps in the IoT message interaction method as described in any one of the first aspects, or implement the steps in the IoT message interaction method as described in any one of the second aspects, or implement the steps in the IoT message interaction method as described in any one of the third aspects.

[0070] The beneficial effects of this invention are:

[0071] The IoT message interaction method provided by this invention involves a network device receiving a first DC message sent by the first terminal, encapsulating the first DC message to obtain an IoT message, and sending the IoT message to an IoT message server. The IoT message server is used to send the IoT message to the IoT terminal, thereby enabling network devices supporting IMS data channels to support the transmission of IoT messages. This facilitates interaction between the first terminal (i.e., the DC terminal) and the second terminal during a call. Attached Figure Description

[0072] Figure 1 A flowchart illustrating the IoT message interaction method for network devices provided in this embodiment of the invention;

[0073] Figure 2 A schematic diagram illustrating the MF function of the network device provided in an embodiment of the present invention;

[0074] Figure 3 A schematic diagram illustrating the AS function of the network device provided in an embodiment of the present invention;

[0075] Figure 4 A flowchart illustrating the IoT message interaction method applied to a first terminal provided in an embodiment of the present invention;

[0076] Figure 5 A flowchart illustrating the IoT message interaction method applied to an IoT message server provided in an embodiment of the present invention;

[0077] Figure 6 This is a flowchart illustrating the overall process of the network message interaction method provided in this embodiment of the invention.

[0078] Figure 7 This is a flowchart illustrating the specific process of MSGin5G Server sending ADC message receipt to MF according to an embodiment of the present invention.

[0079] Figure 8 This is one of the structural schematic diagrams of the Internet of Things (IoT) message interaction device provided in an embodiment of the present invention;

[0080] Figure 9 This is the second schematic diagram of the structure of the IoT message interaction device provided in the embodiment of the present invention;

[0081] Figure 10 This is the third schematic diagram illustrating the structure of the IoT message interaction device provided in this embodiment of the invention.

[0082] Figure 11 This is a schematic diagram of the structure of the network device provided in an embodiment of the present invention;

[0083] Figure 12 This is a schematic diagram showing the structure of the terminal provided in an embodiment of the present invention. Detailed Implementation

[0084] To make the technical problems, technical solutions, and advantages of this application clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments. In the following description, specific details such as particular configurations and components are provided merely to aid in a comprehensive understanding of the embodiments of this application. Therefore, those skilled in the art should understand that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Furthermore, for clarity and brevity, descriptions of known functions and structures have been omitted.

[0085] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0086] In the various embodiments of this application, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0087] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, without limiting the number of objects; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, "A or B" covers three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0088] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0089] Before describing the specific embodiments of the present invention, the following will be explained first:

[0090] Prior Art 1:

[0091] In existing technologies, Data Channel (DC) technology is introduced. By definition, a data channel is established based on the Session Initialization Protocol (SIP) and the Session Description Protocol (SDP). This establishes a data channel comprised of a protocol stack including User Datagram Protocol (UDP), Datagram Transport Layer Security (DTLS), and Stream Control Transmission Protocol (SCTP), enabling the transmission of data information of any protocol type and facilitating real-time data interaction with the user during a call.

[0092] Building upon this, a data channel capability has been defined for use in IMS calls. The Data Channel Signaling Function (DCSF) reports call events to the Application Server (AS) and, based on the AS's call control instructions, the Media Function (MF) prepares media resources. After the Stream Control Transmission Protocol (SCTP) link is established, the terminal sends Application Data Channel (ADC) messages to the Application Server through the Media Function and MF networks, interacting in the form of data channel applications (e.g., new call mini-programs).

[0093] Prior art 2:

[0094] Existing technologies have introduced IoT messaging capabilities into 5G systems, enabling IoT devices to transmit messages, effectively manage IoT device connections, and allowing the server to handle a large number of device connection requests, ensuring that each device can communicate stably with the network.

[0095] This messaging system supports message servers to open their messaging capabilities to application servers, enabling the server to interact with different types of terminals. It also supports various message types, including peer-to-peer (P2P), application-to-person (A2P), and person-to-application (P2A).

[0096] The existing technology 1 involves Data Channel technology that supports real-time interaction capabilities, requiring the maintenance of Data Channel session resources. If it only supports non-real-time message type services, it will consume significant resources in multi-terminal scenarios. Currently, Data Channel technology is mostly used in smart terminals and call-related service areas such as 5G new calls, which require the terminal to support IMS call capabilities. It is difficult to independently support interaction with other types of terminals (such as IoT devices) during a call.

[0097] In existing technology 2, the message flow is an independent process, which is difficult to apply to real-time interactive scenarios such as calls. It requires switching between call and messaging applications, which is difficult to meet user experience requirements. Furthermore, the IoT messaging flow cannot support scenarios where users cannot easily manage IoT devices via messages on the server side, requiring the development of related ASs, which has a high barrier to entry. In addition, for non-IoT messaging terminals, messages can only be sent through non-3rd Generation Partnership Project (3GPP) gateway proxies, which will increase the consumption of message transmission resources.

[0098] To address the problem that existing DC technology struggles to support interaction between terminals and IoT devices during calls, this invention provides an IoT message interaction method, apparatus, terminal, network device, and server.

[0099] like Figure 1 As shown, this embodiment of the invention provides an Internet of Things (IoT) message interaction method applied to network devices, the method comprising:

[0100] Step 101: Receive a first data channel DC message sent by the first terminal. The first DC message includes relevant messages sent by the first terminal to the IoT terminal.

[0101] The network devices include MF and AS.

[0102] In this step, during the call between the first terminal and the second terminal, the first terminal sends a Hypertext Transfer Protocol (HTTP) message, i.e., a first DC message, to the AS via the ADC. The message body of the first DC message carries the relevant message content sent by the first terminal to the IoT terminal (i.e., the 5G IoT terminal), and the AS of the network device receives the first DC message.

[0103] In other words, the first terminal is a terminal that communicates with network equipment through a DC (DC) terminal, and can also be called a DC terminal. Alternatively, the first terminal and the second terminal can also be called new calling terminals.

[0104] Step 102: Encapsulate the first DC message to obtain an IoT message.

[0105] In this step, the AS in the network device encapsulates the first DC message to obtain an IoT message for sending to the IoT terminal.

[0106] Step 103: Send the IoT message to the IoT message server, which is used to send the IoT message to the IoT terminal.

[0107] In this step, the network device sends an IoT message by calling the 5G IoT Message Server (i.e., the IoT Message Server, or MSGin5G Server) through the MF. That is, the MF sends the IoT message to the 5G IoT Message Server, and the 5G IoT Message Server sends the IoT message to the IoT terminal.

[0108] Specifically, network devices send A2P 5G IoT messages through the MSGin5G server interface.

[0109] In this embodiment of the invention, the network device enhances the ability to call the 5G IoT message server through the media plane device, enabling the IMS data channel network side to support the transmission of 5G IoT message content and realize the interaction between the DC terminal and the 5G IoT message terminal.

[0110] The IoT message includes at least one of the following:

[0111] The identifier of the first terminal, namely the sender identifier (ID);

[0112] The identifier of the IoT terminal, i.e., the receiver ID;

[0113] The identifier of the IoT message, i.e., the message ID;

[0114] The forwarding parameters of the IoT message;

[0115] The storage parameters of the IoT message.

[0116] Furthermore, the method also includes:

[0117] Receive a first receipt message sent by the IoT message server, wherein the first receipt message is a receipt message for the IoT message;

[0118] Specifically, the 5G IoT message server sends a message receipt (i.e., a first receipt message) of the IoT message to the MF of the network device. The MF of the network device receives the first receipt message, and the AS of the network device receives the first receipt message through the MF.

[0119] The first receipt message is encapsulated to obtain the second DC message;

[0120] Specifically, the AS receives the first receipt message and encapsulates it into a DC message (i.e., the second DC message).

[0121] Send the second DC message to the first terminal;

[0122] Specifically, the AS stores the second DC message and feeds it back to the new calling terminal (i.e., the first terminal) via the ADC.

[0123] The first receipt message includes at least one of the following:

[0124] The identifier of the first terminal, i.e., the receiver ID;

[0125] The identifier of the IoT terminal, i.e., the sender ID;

[0126] The identifier of the first receipt message, i.e., the message ID;

[0127] The sending status information of the first receipt message.

[0128] In an optional embodiment, the method further includes:

[0129] If the application data channel ADC between the first terminal and the network device is detected to be unavailable or closed, a first indication message is sent to the IoT message server, the first indication message being used to indicate that the IoT message sending has failed.

[0130] Specifically, the network device monitors the ADC SCTP keep-alive messages. If it detects that the ADC is unavailable or the app is closed, it will stop forwarding IoT messages and reply to the MSGin5G server with a transmission failure message (i.e., the first indication message). The MSGin5G server receives this first indication message.

[0131] In an optional embodiment, the method further includes:

[0132] Send a first request message to the IoT message server. The first request message is used to register with the IoT message server and carries the identifier of the application server AS of the network device.

[0133] Specifically, the network device registers with the MSGin5G server via an HTTP request (i.e., a first request message), which carries the ASID parameter. The MSGin5G server receives this first request message.

[0134] The system receives a first response message from the IoT message server, which indicates that the network device has successfully registered.

[0135] Specifically, the MSGin5G server sends a registration success response (i.e., the first response message) to the network device. Upon receiving the first response message, the network device confirms that the network device has successfully registered and maintains the registration information.

[0136] The following is combined with Figure 2 Explain the MF function of the network device:

[0137] MF includes a DC capability module, which includes DC media management function and DC data distribution function. The DC media management function is used to register with the MSGin5G server via HTTP request, and the DC data distribution function is used to send DC messages to 5G IoT messaging terminals or receive message receipts.

[0138] MF also includes a 5G IoT messaging module, which includes a DC channel monitoring function and an MSGin5G message transmission function. The DC channel monitoring function is used to monitor the terminal ADC SCTP keep-alive message, that is, to monitor whether the ADC is available or closed. The MSGin5G message transmission function is used to send IoT messages to the MSGin5G server or receive message receipts.

[0139] MF also includes other capabilities.

[0140] The following is combined with Figure 3 Explain the AS function of the network device:

[0141] AS includes a 5G IoT messaging module and other capabilities. The 5G IoT messaging module includes a DC / MSGin5G message switching function and an MSGin5G terminal management function. The DC / MSGin5G message switching function is used to encapsulate DC messages and IoT messages; the MSGin5G terminal management function is used to receive HTTP registration success responses and maintain registration information.

[0142] like Figure 4 As shown, this embodiment of the invention also provides an IoT message interaction method applied to a first terminal, the method comprising:

[0143] Step 401: During a call with the second terminal, send a first DC message to the network device. The first DC message includes relevant messages sent by the first terminal to the IoT terminal.

[0144] In this step, during the call between the first terminal and the second terminal, the first terminal sends a Hypertext Transfer Protocol (HTTP) message, i.e., a first DC message, to the AS via the ADC. The message body of the first DC message carries the relevant message content sent by the first terminal to the IoT terminal (i.e., the 5G IoT terminal), and the AS of the network device receives the first DC message.

[0145] In other words, the first terminal is a terminal that communicates with network equipment through a DC (DC) terminal, and can also be called a DC terminal. Alternatively, the first terminal and the second terminal can also be called new calling terminals.

[0146] The AS in the network device encapsulates the first DC message to obtain an IoT message for sending to the IoT terminal.

[0147] Furthermore, the method includes:

[0148] Receive the second DC message sent by the network device;

[0149] The second DC message is obtained by the network device encapsulating the first receipt message, which is a receipt message for an IoT message.

[0150] Specifically, the G IoT message server sends a message receipt (i.e., the first receipt message) of the IoT message to the MF of the network device. The MF of the network device receives the first receipt message, and the AS of the network device receives the first receipt message through the MF. The AS receives the first receipt message and encapsulates it into a DC message (i.e., the second DC message). The AS stores the second DC message and feeds it back to the new calling terminal (i.e., the first terminal) through the ADC.

[0151] The first receipt message includes at least one of the following:

[0152] The identifier of the first terminal, i.e., the receiver ID;

[0153] The identifier of the IoT terminal, i.e., the sender ID;

[0154] The identifier of the first receipt message, i.e., the message ID;

[0155] The sending status information of the first receipt message.

[0156] like Figure 5 As shown, this embodiment of the invention also provides an IoT message interaction method, applied to an IoT message server, the method comprising:

[0157] Step 501: Receive IoT messages sent by network devices;

[0158] Network devices send IoT messages by calling the 5G IoT message server (i.e., IoT message server, or MSGin5GServer) through the MF. In other words, the MF sends the IoT message to the 5G IoT message server, and the 5G IoT message server sends the IoT message to the IoT terminal.

[0159] Specifically, network devices send A2P 5G IoT messages through the MSGin5G server interface.

[0160] Step 502: Send the IoT message to the IoT terminal.

[0161] Specifically, after the MSGin5G server receives the IoT message, it sends the IoT message to the IoT terminal (5G IoT terminal), and the IoT terminal receives the IoT message.

[0162] In an optional embodiment, the method further includes:

[0163] Send a first receipt message to the network device, wherein the first receipt message is a receipt message for the IoT message.

[0164] Specifically, the 5G IoT message server sends a message receipt (i.e., a first receipt message) of the IoT message to the MF of the network device. The MF of the network device receives the first receipt message, and the AS of the network device receives the first receipt message through the MF.

[0165] In an optional embodiment, the method further includes:

[0166] The system receives a first indication message sent by the network device, the first indication message being used to indicate that the IoT message transmission failed.

[0167] Specifically, the network device monitors the ADC SCTP keep-alive messages. If it detects that the ADC is unavailable or the app is closed, it will stop forwarding IoT messages and reply to the MSGin5G server with a transmission failure message (i.e., the first indication message). The MSGin5G server receives this first indication message.

[0168] In an optional embodiment, the method further includes:

[0169] The system receives a first request message sent by the network device, the first request message being used to register with the IoT message server, and the first request message carrying the identifier of the AS of the network device.

[0170] Specifically, the network device registers with the MSGin5G server via an HTTP request (i.e., a first request message), which carries the AS ID parameter. The MSGin5G server receives this first request message.

[0171] A first response message is sent to the network device, the first response message being used to indicate that the network device has successfully registered.

[0172] Specifically, the MSGin5G server sends a registration success response (i.e., the first response message) to the network device. Upon receiving the first response message, the network device confirms that the network device has successfully registered and maintains the registration information.

[0173] The IoT message includes at least one of the following:

[0174] The IoT message includes at least one of the following:

[0175] The identifier of the first terminal, i.e., the sender ID;

[0176] The identifier of the IoT terminal, i.e., the receiver ID;

[0177] The identifier of the IoT message, i.e., the message ID;

[0178] The forwarding parameters of the IoT message;

[0179] The storage parameters of the IoT message.

[0180] The following is combined with Figure 6 The overall process of the network message interaction method provided in the embodiments of the present invention is described in detail below:

[0181] Steps 1-20 constitute the IMS data channel proposal process based on existing technology 1:

[0182] Step 1: During the call between UE A and UE B, it is recommended to bootstrap the data channel and obtain a new call applet from the network. This applet is used to send messages to the 5G IoT messaging server.

[0183] Steps 2-20: The terminal initiates re-Invite media negotiation and negotiates ADC with the application server; the network reports the call event to the AS and issues control to prepare ADC establishment resources, while completing SDP negotiation with the calling and called parties. Only the terminal UE A and the calling network complete the establishment of P2A ADC.

[0184] Step 21: During the call between terminal UE A (first terminal) and terminal UE B (second terminal), terminal UE A sends an HTTP message (i.e., the first DC message) to AS through ADC. The message body contains relevant content of IoT messages.

[0185] Step 22: AS encapsulates the first DC message to obtain the IoT message, and sends the IoT message by calling the 5G IoT Message Server (MSGin5G Server) through MF.

[0186] Step 23: MF sends an IoT message to the MSGin5G server, and the MSGin5G server receives the IoT message;

[0187] Step 24: MSGin5G Server sends an ADC message receipt (i.e., the first receipt message) to MF.

[0188] Step 25: MF sends the ADC message receipt to terminal UE A.

[0189] The specific process by which MSGin5G Server sends ADC message receipts to MF is as follows: Figure 7 As shown:

[0190] AS encapsulates the first DC message into an IoT message; MF sends the IoT message to the MSGin5G server, the MSGin5G server sends the IoT message to the IoT terminal (MSGin5G UE(s)), the IoT terminal sends a message receipt (i.e., the first receipt message) of the IoT message to the MSGin5G server, the MSGin5G server sends the first receipt message to the MF, and AS encapsulates the first receipt message into a second DC message.

[0191] like Figure 8 As shown, this embodiment of the invention also provides an Internet of Things (IoT) message interaction device, the device comprising:

[0192] The first receiving module 801 is used to receive a first data channel DC message sent by the first terminal during a call between the first terminal and the second terminal. The first DC message includes relevant messages sent by the first terminal to the Internet of Things terminal.

[0193] The first processing module 802 is used to encapsulate and process the DC message from the first data channel to obtain an Internet of Things message;

[0194] The first sending module 803 is used to send the IoT message to the IoT message server, and the IoT message server is used to send the IoT message to the IoT terminal.

[0195] Optionally, the device further includes:

[0196] The first message receiving module is used to receive a first receipt message sent by the IoT message server, wherein the first receipt message is a receipt message for the IoT message;

[0197] The second processing module is used to encapsulate the first receipt message to obtain the second DC message;

[0198] The first message sending module is used to send the second DC message to the first terminal.

[0199] Optionally, the device further includes:

[0200] The second message sending module is used to send a first indication message to the IoT message server when it detects that the application data channel ADC between the first terminal and the network device is unavailable or closed. The first indication message is used to indicate that the IoT message sending has failed.

[0201] Optionally, the device further includes:

[0202] The third message sending module is used to send a first request message to the IoT message server. The first request message is used to register with the IoT message server and carries the identifier of the application server AS of the network device.

[0203] The second message receiving module is used to receive a first response message sent by the IoT message server, the first response message being used to indicate that the network device has successfully registered.

[0204] Optionally, the IoT message includes at least one of the following:

[0205] The identifier of the first terminal;

[0206] The identifier of the IoT terminal;

[0207] The identifier of the IoT message;

[0208] The forwarding parameters of the IoT message;

[0209] The storage parameters of the IoT message.

[0210] Optionally, the first receipt message includes at least one of the following:

[0211] The identifier of the first terminal;

[0212] The identifier of the IoT terminal;

[0213] The identifier of the first receipt message;

[0214] The sending status information of the first receipt message.

[0215] It should be noted that the IoT message interaction device provided in the embodiments of the present invention is a device capable of executing the above-described IoT message interaction method applied to network devices. Therefore, all embodiments of the above-described IoT message interaction device method are applicable to this device and can achieve the same or similar technical effects.

[0216] like Figure 9 As shown, this embodiment of the invention also provides an Internet of Things (IoT) message interaction device, the device comprising:

[0217] The second sending module 901 is used to send a first DC message to a network device during a call with the second terminal. The first DC message includes relevant messages sent by the first terminal to the Internet of Things terminal.

[0218] Optionally, the device includes:

[0219] The third message receiving module is used to receive the second DC message sent by the network device;

[0220] The second DC message is obtained by the network device encapsulating the first receipt message, which is a receipt message for an IoT message.

[0221] Optionally, the first receipt message includes at least one of the following:

[0222] The identifier of the first terminal;

[0223] Identification of IoT terminals;

[0224] The identifier of the first receipt message;

[0225] The sending status information of the first receipt message.

[0226] It should be noted that the IoT message interaction device provided in the embodiments of the present invention is a device capable of executing the above-described IoT message interaction method applied to the first terminal. Therefore, all embodiments of the above-described IoT message interaction device method are applicable to this device and can achieve the same or similar technical effects.

[0227] like Figure 10 As shown, this embodiment of the invention also provides an Internet of Things (IoT) message interaction device, the device comprising:

[0228] The second receiving module 1001 is used to receive IoT messages sent by network devices;

[0229] The third sending module 1002 is used to send the IoT message to the IoT terminal.

[0230] Optionally, the device further includes:

[0231] The fourth message sending module is used to send a first receipt message to the network device, wherein the first receipt message is a receipt message for the IoT message.

[0232] Optionally, the device further includes:

[0233] The fourth message receiving module is used to receive first indication information sent by the network device, the first indication information being used to indicate that the IoT message sending failed.

[0234] Optionally, the device further includes:

[0235] The fifth message receiving module is used to receive a first request message sent by the network device. The first request message is used to register with the Internet of Things message server and carries the identifier of the AS of the network device.

[0236] The fifth message receiving module is used to send a first response message to the network device, the first response message being used to indicate that the network device has successfully registered.

[0237] Optionally, the IoT message includes at least one of the following:

[0238] The identifier of the first terminal;

[0239] The identifier of the IoT terminal;

[0240] The identifier of the IoT message;

[0241] The forwarding parameters of the IoT message;

[0242] The storage parameters of the IoT message.

[0243] It should be noted that the IoT message interaction device provided in the embodiments of the present invention is a device capable of executing the above-described IoT message interaction method applied to an IoT message server. Therefore, all embodiments of the above-described IoT message interaction device method are applicable to this device and can achieve the same or similar technical effects.

[0244] like Figure 11As shown, this embodiment of the invention also provides a network device, including: a processor 1101; and a memory 1103 connected to the processor 1101 via a bus interface 1102, the memory 1103 being used to store programs and data used by the processor 1101 when performing operations, and the processor 1101 calling and executing the programs and data stored in the memory 1103.

[0245] The transceiver 1104 is connected to the bus interface 1102 and is used to receive and send data under the control of the processor 1101. Specifically, the processor 1101 is used to read the program in the memory 1103, and the transceiver 1104 is used to execute the following processes:

[0246] During a call between the first terminal and the second terminal, a first data channel DC message is received from the first terminal. The first DC message includes relevant messages sent by the first terminal to the IoT terminal.

[0247] The processor 1101 is used to perform the following processes:

[0248] The first DC message is encapsulated to obtain an IoT message;

[0249] The transceiver 1104 is also used to perform the following processes:

[0250] The IoT message is sent to the IoT message server, which is used to send the IoT message to the IoT terminal.

[0251] Optionally, the transceiver 1104 is further configured to:

[0252] Receive a first receipt message sent by the IoT message server, wherein the first receipt message is a receipt message for the IoT message;

[0253] The processor 1101 is also used for:

[0254] The first receipt message is encapsulated to obtain the second DC message;

[0255] The transceiver 1104 is also used for:

[0256] Send the second DC message to the first terminal.

[0257] Optionally, the transceiver 1104 is further configured to:

[0258] If the application data channel ADC between the first terminal and the network device is detected to be unavailable or closed, a first indication message is sent to the IoT message server, the first indication message being used to indicate that the IoT message sending has failed.

[0259] Optionally, the transceiver 1104 is further configured to:

[0260] Send a first request message to the IoT message server. The first request message is used to register with the IoT message server and carries the identifier of the application server AS of the network device.

[0261] The system receives a first response message from the IoT message server, which indicates that the network device has successfully registered.

[0262] Optionally, the IoT message includes at least one of the following:

[0263] The identifier of the first terminal;

[0264] The identifier of the IoT terminal;

[0265] The identifier of the IoT message;

[0266] The forwarding parameters of the IoT message;

[0267] The storage parameters of the IoT message.

[0268] Optionally, the first receipt message includes at least one of the following:

[0269] The identifier of the first terminal;

[0270] The identifier of the IoT terminal;

[0271] The identifier of the first receipt message;

[0272] The sending status information of the first receipt message.

[0273] Among them, Figure 11In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1101) and memory (memory 1103). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1104 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. Processor 1101 is responsible for managing the bus architecture and general processing, and memory 1103 may store data used by processor 1101 during operation.

[0274] like Figure 12 As shown, this embodiment of the invention also provides a terminal, which is a first terminal, including: a processor 1201; and a memory 1203 connected to the processor 1201 via a bus interface 1202. The memory 1203 is used to store programs and data used by the processor 1201 when performing operations, and the processor 1201 calls and executes the programs and data stored in the memory 1203.

[0275] The transceiver 1204 is connected to the bus interface 1202 and is used to receive and send data under the control of the processor 1201. Specifically, the processor 1201 is used to read the program in the memory 1203, and the transceiver 1204 is used to execute the following processes:

[0276] During a call with the second terminal, a first DC message is sent to the network device. The first DC message includes relevant messages sent by the first terminal to the IoT terminal.

[0277] Optionally, the transceiver 1204 is further configured to:

[0278] Receive the second DC message sent by the network device;

[0279] The second DC message is obtained by the network device encapsulating the first receipt message, which is a receipt message for an IoT message.

[0280] Optionally, the first receipt message includes at least one of the following:

[0281] The identifier of the first terminal;

[0282] Identification of IoT terminals;

[0283] The identifier of the first receipt message;

[0284] The sending status information of the first receipt message.

[0285] Among them, Figure 12 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1201) and memory (memory 1203). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1202 provides user interface 1205. Transceiver 1204 may be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over a transmission medium. Processor 1201 is responsible for managing the bus architecture and general processing, and memory 1203 may store data used by processor 1201 during operation.

[0286] This invention also provides an Internet of Things (IoT) message server, comprising: a processor; and a memory connected to the processor via a bus interface, the memory being used to store programs and data used by the processor during operation, and the processor calling and executing the programs and data stored in the memory.

[0287] The transceiver is connected to the bus interface and is used to receive and send data under the control of the processor.

[0288] It should be noted that the IoT message server provided in this embodiment of the invention is related to... Figure 12 The structures of the terminals shown are basically the same, so they will not be described in detail here.

[0289] Specifically, the processor is used to read the program from the memory, and the transceiver is used to execute the following processes:

[0290] Receive IoT messages sent by network devices;

[0291] Send the IoT message to the IoT terminal.

[0292] Optionally, the transceiver is further used for:

[0293] Send a first receipt message to the network device, wherein the first receipt message is a receipt message for the IoT message.

[0294] Optionally, the transceiver is further used for:

[0295] The system receives a first indication message sent by the network device, the first indication message being used to indicate that the IoT message transmission failed.

[0296] Optionally, the transceiver is further used for:

[0297] The system receives a first request message sent by the network device, the first request message being used to register with the IoT message server, and the first request message carrying the identifier of the AS of the network device.

[0298] A first response message is sent to the network device, the first response message being used to indicate that the network device has successfully registered.

[0299] Optionally, the IoT message includes at least one of the following:

[0300] The identifier of the first terminal;

[0301] The identifier of the IoT terminal;

[0302] The identifier of the IoT message;

[0303] The forwarding parameters of the IoT message;

[0304] The storage parameters of the IoT message.

[0305] In addition, specific embodiments of the present invention also provide a readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the steps in the IoT message interaction method as described above.

[0306] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0307] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated unit described above can be implemented in hardware or in the form of hardware plus software functional units.

[0308] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions that cause a computer device (which may be a personal computer, server, or network device, etc.) to execute partial steps of the resource selection method described in the various embodiments of the present invention, or to execute partial steps of the information transmission method described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0309] A specific embodiment of the present invention also provides a computer program product, including computer instructions, which, when executed by a processor, implement the above-described functionality. Figure 1 , Figure 4 or Figure 5 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0310] The above describes the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also within the scope of protection of the present invention.

Claims

1. An Internet of Things (IoT) message interaction method, characterized in that, Applied to network devices, the method includes: During a call between the first terminal and the second terminal, a first data channel DC message is received from the first terminal. The first DC message includes relevant messages sent by the first terminal to the IoT terminal. The first DC message is encapsulated to obtain an IoT message; The IoT message is sent to the IoT message server, which is used to send the IoT message to the IoT terminal.

2. The method according to claim 1, characterized in that, The method further includes: Receive a first receipt message sent by the IoT message server, wherein the first receipt message is a receipt message for the IoT message; The first receipt message is encapsulated to obtain the second DC message; Send the second DC message to the first terminal.

3. The method according to claim 1, characterized in that, The method further includes: If the application data channel ADC between the first terminal and the network device is detected to be unavailable or closed, a first indication message is sent to the IoT message server, the first indication message being used to indicate that the IoT message sending has failed.

4. The method according to claim 1, characterized in that, The method further includes: Send a first request message to the IoT message server. The first request message is used to register with the IoT message server and carries the identifier of the application server AS of the network device. The system receives a first response message from the IoT message server, which indicates that the network device has successfully registered.

5. The method according to claim 1, characterized in that, The IoT message includes at least one of the following: The identifier of the first terminal; The identifier of the IoT terminal; The identifier of the IoT message; The forwarding parameters of the IoT message; The storage parameters of the IoT message.

6. The method according to claim 2, characterized in that, The first receipt message includes at least one of the following: The identifier of the first terminal; The identifier of the IoT terminal; The identifier of the first receipt message; The sending status information of the first receipt message.

7. An Internet of Things (IoT) message interaction method, characterized in that, Applied to a first terminal, the method includes: During a call with the second terminal, a first DC message is sent to the network device. The first DC message includes relevant messages sent by the first terminal to the IoT terminal.

8. The method according to claim 7, characterized in that, The method includes: Receive the second DC message sent by the network device; The second DC message is obtained by the network device encapsulating the first receipt message, which is a receipt message for an IoT message.

9. The method according to claim 8, characterized in that, The first receipt message includes at least one of the following: The identifier of the first terminal; Identification of IoT terminals; The identifier of the first receipt message; The sending status information of the first receipt message.

10. An Internet of Things (IoT) message interaction method, characterized in that, The method, applied to an IoT message server, includes: Receive IoT messages sent by network devices; Send the IoT message to the IoT terminal.

11. The method according to claim 10, characterized in that, The method further includes: Send a first receipt message to the network device, wherein the first receipt message is a receipt message for the IoT message.

12. The method according to claim 10, characterized in that, The method further includes: The system receives a first indication message sent by the network device, the first indication message being used to indicate that the IoT message transmission failed.

13. The method according to claim 10, characterized in that, The method further includes: The system receives a first request message sent by the network device, the first request message being used to register with the IoT message server, and the first request message carrying the identifier of the AS of the network device. A first response message is sent to the network device, the first response message being used to indicate that the network device has successfully registered.

14. The method according to claim 10, characterized in that, The IoT message includes at least one of the following: The identifier of the first terminal; The identifier of the IoT terminal; The identifier of the IoT message; The forwarding parameters of the IoT message; The storage parameters of the IoT message.

15. An Internet of Things (IoT) message interaction device, characterized in that, The device includes: The first receiving module is used to receive a first data channel DC message sent by the first terminal during a call between the first terminal and the second terminal. The first DC message includes relevant messages sent by the first terminal to the Internet of Things terminal. The first processing module is used to encapsulate and process the DC message from the first data channel to obtain an IoT message; The first sending module is used to send the IoT message to the IoT message server during a call with the second terminal, and the IoT message server is used to send the IoT message to the IoT terminal.

16. An Internet of Things (IoT) message interaction device, characterized in that, The device includes: The second sending module is used to send a first DC message to the network device, the first DC message including relevant messages sent by the first terminal to the Internet of Things terminal.

17. An Internet of Things (IoT) message interaction device, characterized in that, The device includes: The second receiving module is used to receive IoT messages sent by network devices; The third sending module is used to send the IoT message to the IoT terminal.

18. A network device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the IoT messaging interaction method as described in any one of claims 1 to 6.

19. A terminal, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the IoT messaging interaction method as described in any one of claims 7 to 9.

20. An Internet of Things (IoT) message server, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the IoT messaging interaction method as described in any one of claims 10 to 14.

21. A readable storage medium, characterized in that, The readable storage medium stores a program that, when executed by a processor, implements the steps of the IoT message interaction method as described in any one of claims 1 to 6, or implements the steps of the IoT message interaction method as described in any one of claims 7 to 9, or implements the steps of the IoT message interaction method as described in any one of claims 10 to 14.

22. A computer program product, characterized in that, The method includes computer instructions that, when executed by a processor, implement the steps in the IoT message interaction method as described in any one of claims 1 to 6, or implement the steps in the IoT message interaction method as described in any one of claims 7 to 9, or implement the steps in the IoT message interaction method as described in any one of claims 10 to 14.

Images