Communication method, apparatus and system

Abstract

This application provides a communication method, apparatus, and system for quickly and conveniently acquiring device operating information. The method is applied to a first device equipped with a Near Field Communication (NFC) chip, and includes: acquiring the operating information of the first device; establishing communication with a second device equipped with an NFC chip; and sending the operating information of the first device to the second device. This application is applicable to the field of communication technology.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods, apparatus and systems. Background Technology

[0002] Typically, to understand the operational status of equipment, it is necessary to obtain its operational information, which may include, for example, the equipment's operation logs, problem logs, or usage records. This operational information reflects the equipment's operating or usage status. Currently, existing technologies often employ complex and cumbersome methods for obtaining this operational information. Taking the acquisition of problem logs and usage records as an example, existing technologies typically use the following methods:

[0003] When equipment malfunctions, technicians use specific software to export the problem logs and transfer them to a device capable of displaying the logs, such as a computer. By analyzing the logs, they can pinpoint the problem. However, this method requires technicians to use specialized software to export and transfer logs, which is complex and time-consuming. Therefore, this approach to obtaining problem logs is neither fast nor convenient.

[0004] Alternatively, when the device receives a monitoring start command, its pre-configured monitoring module records usage and displays this history on a specific page on the device, allowing users to view it. For example, some televisions automatically record power-on time and viewing schedules after the user turns them on, which can then be viewed on the television's history page. However, this approach requires the user to turn on the device and access a specific page to view the usage history, a cumbersome and inconvenient process.

[0005] Therefore, how to quickly and conveniently obtain equipment operating information is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method, apparatus, and system to solve the problem of how to quickly and conveniently obtain device operating information.

[0007] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0008] Firstly, a communication method is provided, applied to a first device having a Near Field Communication (NFC) chip. The method includes: acquiring operational information of the first device; establishing communication with a second device having an NFC chip; and sending the operational information of the first device to the second device. Based on the communication method provided in this application, the operational information of the first device can be sent to the second device via NFC technology, allowing users to conveniently obtain the operational information of the first device through the second device without relying on specific software or the state of the first device. For example, even when the first device is not powered on or connected to the internet, the user can still obtain the operational information of the first device quickly and conveniently.

[0009] In conjunction with the first aspect described above, in one possible implementation, the operational information of the first device includes the first device's problem log and / or the first device's usage record. Based on the communication method provided in the embodiments of this application, users can quickly and conveniently obtain the first device's problem log and / or the first device's usage record.

[0010] In conjunction with the first aspect described above, in one possible implementation, the first information includes a problem log of the first device. Before establishing communication with a second device having an NFC chip, the method further includes: obtaining the root cause of the problem log generated by the first device; after establishing communication with the second device having an NFC chip, the method further includes: sending the root cause of the problem to the second device. Based on the communication method provided in this application embodiment, the root cause of the problem log generated by the first device can be sent to the second device via NFC technology. This allows the user to obtain the possible causes of the problem with the first device through the second device, eliminating the need for the user to manually export the problem log using specific software and then analyze the log using appropriate technology to determine the root cause. This facilitates the user's quick location of the problem in the first device.

[0011] In conjunction with the first aspect described above, in one possible implementation, obtaining the root cause of the problem log generated by the first device includes: determining the root cause of the problem log generated by the first device based on the problem log of the first device. Based on the communication method provided in this application embodiment, the first device itself can analyze the problem log to obtain the root cause of the problem, eliminating the need to transmit the problem log to other devices for analysis. Therefore, this not only saves time in problem localization but also ensures the security of user data.

[0012] In conjunction with the first aspect described above, in one possible implementation, obtaining the root cause of the problem log generated by the first device includes: receiving the root cause of the problem log generated by the first device from a cloud server. Based on the communication method provided in this application embodiment, on the one hand, because the cloud server has sufficient computing resources and strong computing power, the root cause determined by the cloud server based on the problem log is highly accurate, and the problem is located more precisely. On the other hand, since this solution does not require the first device to locate the root cause, it not only saves the computing resources of the first device, but also ensures that the first device, which cannot analyze problem logs itself, obtains the root cause of the problem.

[0013] In conjunction with the first aspect described above, in one possible implementation, before receiving the root cause of the problem log generated by the first device from the cloud server, the method further includes: sending the problem log of the first device to the cloud server, whereby the cloud server determines the root cause of the problem log generated by the first device. Based on the communication method provided in this application embodiment, on the one hand, because the cloud server has sufficient computing resources and strong computing power, the root cause determined by the cloud server based on the problem log is highly accurate, and the problem is located more precisely. On the other hand, since this solution does not require the first device to locate the root cause, it not only saves the computing resources of the first device, but also ensures that the first device, which cannot analyze problem logs itself, obtains the root cause of the problem.

[0014] In conjunction with the first aspect described above, in one possible implementation, after establishing communication with a second device equipped with an NFC chip, the method further includes: authenticating the second device; and sending the operating information of the first device to the second device, including: if the second device passes the authentication, sending the operating information of the first device to the second device. Based on the communication method provided in this application embodiment, since the first device can decide whether to send operating information to the second device by authenticating the second device, only the second device that has passed the authentication can receive the operating information of the first device, thus improving the confidentiality and security of the operating information of the first device.

[0015] In conjunction with the first aspect described above, in one possible implementation, the method further includes: storing account information of the first device and the second device, wherein the account information of the first device and the second device is used to authenticate the second device. Based on the communication method provided in the embodiments of this application, the second device can be authenticated locally on the first device using the account information stored on the first device itself, thereby enabling authentication of the second device even when the first device is not connected to the network, without relying on the network.

[0016] In conjunction with the first aspect described above, in one possible implementation, the account information of the first device and the second device includes the binding relationship between the first device and the first account, and the binding relationship between the first account and the second account bound to the second device. Based on the communication method provided in the embodiments of this application, the second device can be authenticated through the binding relationship between accounts.

[0017] In conjunction with the first aspect described above, in one possible implementation, after establishing communication with a second device equipped with an NFC chip and before sending the operating information of the first device to the second device, the method further includes: receiving a first request from the second device, the first request being used to request the first device to send the operating information of the first device. Based on the communication method provided in the embodiments of this application, the first device can send the operating information of the first device to the second device according to the request sent by the second device, that is, it can send the operating information of the first device to the second device according to the needs of the second device, instead of automatically or randomly sending the operating information of the first device, which not only saves communication resources, but is also more user-friendly.

[0018] In conjunction with the first aspect described above, in one possible implementation, after obtaining the operating information of the first device, the method further includes: storing the operating information of the first device. Based on the communication method provided in the embodiments of this application, a user can obtain the historical operating information of the first device through the second device. Furthermore, the user can understand the historical operating status of the first device through the historical operating information, which better meets the user's needs.

[0019] In conjunction with the first aspect described above, in one possible implementation, the method further includes: deleting the stored operating information of the first device according to a management cycle, wherein the management cycle is used to manage the operating information of the first device. Based on the communication method provided in the embodiments of this application, the operating information of the first device can be deleted periodically according to the management cycle, ensuring the normal operation or operating efficiency of the first device with small storage space or no space to store operating information.

[0020] In conjunction with the first aspect described above, in one possible implementation, the method further includes: sending the operating information of the first device to a cloud server, whereby the cloud server stores the operating information of the first device. That is, in this embodiment, as the first device operates, it generates more and more operating information. The first device can send this generated operating information to a cloud server, where the cloud server stores a large amount of operating information. This saves storage space on the first device and ensures the normal operation or efficiency of the first device, even if its storage space is small or there is no space to store operating information.

[0021] In conjunction with the first aspect described above, in one possible implementation, the NFC chip of the first device is written with a first tag, which includes a general device tag, a debugging device tag, or a monitoring device tag. Based on the method provided in the embodiments of this application, tags of different types of devices can be written into the NFC chip of the first device, facilitating the manufacturer's classification of the first device.

[0022] In conjunction with the first aspect described above, in one possible implementation, the operating information of the first device further includes the operation log of the first device. Based on the communication method provided in the embodiments of this application, users can quickly and conveniently obtain the operation log of the first device through the second device, thereby gaining a more comprehensive understanding of the operating status of the first device by analyzing the operation log.

[0023] Secondly, a communication method is provided, applied to a second device having a Near Field Communication (NFC) chip. The method includes: establishing communication with a first device having an NFC chip; receiving operational information from the first device; and displaying the operational information. Based on the communication method provided in this application, the second device can receive operational information from the first device via NFC technology and display the operational information on the second device. This allows users to conveniently view the operational information of the first device on the second device without relying on specific software or the status of the first device, for example, even when the first device is not powered on or connected to the internet, thus achieving quick and convenient access to the operational information of the first device.

[0024] In conjunction with the second aspect described above, in one possible implementation, the operational information of the first device includes the first device's problem log and / or the first device's usage record. Based on the communication method provided in the embodiments of this application, users can quickly and conveniently obtain and view the first device's problem log and / or the first device's usage record.

[0025] In conjunction with the second aspect described above, in one possible implementation, the first information includes a problem log of the first device. After establishing communication with the first device equipped with an NFC chip, the method further includes: receiving the root cause of the problem log generated by the first device; and displaying the root cause. Based on the communication method provided in this application embodiment, the root cause behind the problem log generated by the first device can be sent to a second device via NFC technology. This allows the user to obtain and view the possible causes of the problem with the first device through the second device, eliminating the need for the user to manually export the problem log using specific software and then analyze it using appropriate technology to determine the root cause. This facilitates the user's quick location of the problem in the first device.

[0026] In conjunction with the second aspect described above, in one possible implementation, after establishing communication with a first device equipped with an NFC chip and before receiving operating information from the first device, the method further includes: sending a first request to the first device, the first request being used to request the first device to send its operating information. Based on the communication method provided in this application embodiment, the first device can send its operating information to the second device according to a request sent by the second device, that is, it can send its operating information to the second device according to the needs of the second device, instead of automatically or randomly sending its operating information, which not only saves communication resources but is also more user-friendly.

[0027] In conjunction with the second aspect described above, in one possible implementation, the operating information of the first device further includes the operation log of the first device. Based on the communication method provided in the embodiments of this application, users can quickly and conveniently obtain and view the operation log of the first device through the second device, thereby gaining a more comprehensive understanding of the operating status of the first device by analyzing the operation log.

[0028] Thirdly, a communication device is provided for implementing the method described in the first aspect. The communication device includes modules, units, or means corresponding to the implementation of the method described in the first aspect. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functions.

[0029] In conjunction with the third aspect above, in one possible implementation, the communication device is applied to a first device having a near-field communication (NFC) chip. The communication device includes: a transceiver module and a processing module; the processing module is used to acquire the operating information of the first device; the processing module is also used to establish communication with a second device having an NFC chip; the transceiver module is used to send the operating information of the first device to the second device.

[0030] In conjunction with the third aspect mentioned above, in one possible implementation, the operational information of the first device includes the problem log of the first device and / or the usage record of the first device.

[0031] In conjunction with the third aspect mentioned above, in one possible implementation, the processing module is further configured to obtain the root cause of the problem that caused the problem log of the first device; the transceiver module is further configured to send the root cause of the problem to the second device.

[0032] In conjunction with the third aspect above, in one possible implementation, the processing module is further configured to obtain the root cause of the problem log generated by the first device, including: determining the root cause of the problem log generated by the first device based on the problem log of the first device.

[0033] In conjunction with the third aspect above, in one possible implementation, the processing module is further configured to obtain the root cause of the problem log generated by the first device by receiving the root cause of the problem log generated by the first device from the cloud server through the transceiver module.

[0034] In conjunction with the third aspect mentioned above, in one possible implementation, the transceiver module is also used to send the problem logs of the first device to the cloud server, so that the cloud server can determine the root cause of the problem logs generated by the first device.

[0035] In conjunction with the third aspect above, in one possible implementation, the processing module is further configured to authenticate the second device; the transceiver module is configured to send the operating information of the first device to the second device, including: if the second device passes the authentication, sending the operating information of the first device to the second device.

[0036] In conjunction with the first aspect described above, in one possible implementation, the communication device further includes a storage module for storing account information of the first device and the second device, which is used to authenticate the second device.

[0037] In conjunction with the first aspect mentioned above, in one possible implementation, the account information of the first device and the second device includes the binding relationship between the first device and the first account, as well as the binding relationship between the first account and the second account bound to the second device.

[0038] In conjunction with the third aspect mentioned above, in one possible implementation, the transceiver module is further configured to receive a first request from the second device, the first request being used to request the first device to send its operating information.

[0039] In conjunction with the third aspect mentioned above, in one possible implementation, the storage module is also used to store the operating information of the first device.

[0040] In conjunction with the third aspect mentioned above, in one possible implementation, the processing module is further configured to delete the stored operating information of the first device according to the management cycle, wherein the management cycle is used to manage the operating information of the first device.

[0041] In conjunction with the third aspect mentioned above, in one possible implementation, the transceiver module is further configured to send the operating information of the first device to a cloud server, whereby the cloud server stores the operating information of the first device.

[0042] In conjunction with the third aspect mentioned above, in one possible implementation, the NFC chip of the first device is written with a first tag, which includes a general device tag, a debugging device tag, or a monitoring device tag.

[0043] In conjunction with the third aspect mentioned above, in one possible implementation, the operating information of the first device also includes the operation log of the first device.

[0044] In conjunction with the third aspect above, in one possible implementation, the processing module can be a processor, the transceiver module can be a transceiver, and the storage module can be a memory.

[0045] The technical effects of any possible implementation of the third aspect mentioned above can be found in the technical effects of different implementations of the first aspect mentioned above, and will not be repeated here.

[0046] Fourthly, a communication device is provided for implementing the method described in the second aspect above. The communication device includes modules, units, or means corresponding to implementing the method described in the second aspect above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0047] In conjunction with the fourth aspect above, in one possible implementation, the communication device is applied to a second device having a near-field communication (NFC) chip. The communication device includes: a transceiver module, a processing module, and a display module; the processing module is used to establish communication with a first device having an NFC chip; the transceiver module is used to receive operating information from the first device; and the display module is used to display the operating information of the first device.

[0048] In conjunction with the fourth aspect above, in one possible implementation, the operating information of the first device includes the problem log of the first device and / or the usage record of the first device.

[0049] In conjunction with the fourth aspect above, in one possible implementation, the operating information of the first device includes the problem log of the first device, and the transceiver module is further configured to receive the root cause of the problem from the first device that caused the problem log of the first device; the display module is further configured to display the root cause of the problem.

[0050] In conjunction with the fourth aspect above, in one possible implementation, the transceiver module is further configured to send a first request to the first device, the first request being used to request the first device to send its operating information.

[0051] In conjunction with the fourth aspect mentioned above, in one possible implementation, the operating information of the first device also includes the operation log of the first device.

[0052] In conjunction with the fourth aspect above, in one possible implementation, the processing module can be a processor, the transceiver module can be a transceiver, and the display module can be a display.

[0053] The technical effects of any possible implementation of the fourth aspect mentioned above can be found in the technical effects of different implementations in the second aspect mentioned above, and will not be repeated here.

[0054] Fifthly, a communication device is provided, comprising: a processor; the processor being coupled to a memory and, after reading computer instructions stored in the memory, executing the method as described in any of the preceding aspects according to the instructions.

[0055] In conjunction with the fifth aspect above, in one possible implementation, the communication device further includes a memory for storing computer instructions.

[0056] In conjunction with the fifth aspect above, in one possible implementation, the communication device further includes a communication interface; this communication interface is used for communication between the communication device and other devices. For example, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc.

[0057] In conjunction with the fifth aspect above, in one possible implementation, the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0058] In conjunction with the fifth aspect above, in one possible implementation, when the communication device is a chip or chip system, the aforementioned communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The aforementioned processor can also be embodied as a processing circuit or logic circuit.

[0059] In a sixth aspect, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, cause the computer to perform the methods described in any of the preceding aspects.

[0060] In a seventh aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to perform the methods described in any of the preceding aspects.

[0061] The technical effects of any possible implementation of aspects five through seven can be found in the technical effects of different implementations of any of the above aspects, and will not be repeated here.

[0062] Eighthly, a communication system is provided, comprising a first device for performing the method described in the first aspect and a second device for performing the method described in the second aspect.

[0063] In conjunction with the eighth aspect above, in one possible implementation, the communication system further includes a cloud server; the cloud server is used to authenticate the second device; if the second device passes the authentication, the cloud server sends the operating information of the first device to the first device. Attached Figure Description

[0064] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0065] Figure 2 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0066] Figure 3 This is a schematic diagram of the structure of a second device provided in an embodiment of this application;

[0067] Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application;

[0068] Figure 5 A flowchart illustrating another communication method provided in an embodiment of this application;

[0069] Figure 6 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0070] Figure 7 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0071] Figure 8 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0072] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0073] Figure 10 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0074] Before describing the embodiments of this application in detail, in order to facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technical terms of this application is given as follows:

[0075] 1. Near Field Communication (NFC)

[0076] NFC is a short-range, high-frequency wireless communication technology that combines inductive card reader, inductive card, and peer-to-peer functionality on a single NFC chip, allowing contactless peer-to-peer data transfer between NFC-enabled electronic devices. NFC primarily operates in three modes:

[0077] (1) Active mode: An NFC device can act as a card reader, emitting a radio frequency field to identify and read / write information from other NFC devices.

[0078] (2) Passive mode: The NFC device is simulated as a card, and it can only passively respond to the radio frequency field emitted by other NFC devices and have information read / written.

[0079] (3) Two-way mode: Both NFC devices emit radio frequency fields to establish point-to-point communication, which is equivalent to both NFC devices being in active mode.

[0080] NFC, as a convenient communication technology, is widely used in everything from mobile payments to the Internet of Things (IoT), and even in autonomous driving and smart manufacturing, for example, the following applications:

[0081] (1) Card emulation: NFC mobile phones can be used as public transport cards, bank cards or electronic access control, reducing the number of cards to carry when traveling.

[0082] (2) File transfer: After both phones have NFC enabled, they can be brought close together to establish a connection. At this time, you can select the file you want to transfer or receive.

[0083] (3) Smart tag: Write specified data into the NFC tag of the device. When the NFC mobile phone is brought close to the NFC tag of the device, the NFC mobile phone can read the specified information, thereby realizing a series of convenient operations such as making a phone call, starting an alarm clock, browsing a page or launching an application.

[0084] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0085] The technical solutions of this application can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems, or New Radio (NR) systems, etc. The 5G mobile communication systems involved in this application include non-standalone (NSA) 5G mobile communication systems and standalone (SA) 5G mobile communication systems. The technical solutions provided in this application can also be applied to future communication systems, such as 6th Generation (6G) mobile communication systems. In addition, the communication system can also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) communication system, or other communication systems.

[0086] Figure 1 This is a schematic diagram of the architecture of a communication system 10 that applies the communication method provided in the embodiments of this application. Figure 1 As shown, the communication system 10 includes a first device 20 and a second device 30. Both the first device 20 and the second device 30 have NFC chips. The first device 20 is used to acquire the operating information of the first device 20, establish communication with the second device 30 (which has an NFC chip), and then send the operating information of the first device 20 to the second device. The second device 30, after establishing communication with the first device 20 (which has an NFC chip), receives the operating information from the first device 20 and displays the operating information of the first device 20. The specific implementation of this scheme will be described in detail in subsequent method embodiments and will not be repeated here. Because in this scheme, the second device 30 can acquire and display the operating information of the first device 20 through NFC communication, the cumbersome and complex problem of acquiring device operating information in the prior art can be avoided, achieving fast and convenient acquisition of device operating information.

[0087] It should be understood that Figure 1 This is merely an exemplary schematic diagram of the architecture of a communication system 10 applying the communication method provided in the embodiments of this application, and does not limit the communication system 10 to include only one first device or one second device. In other words, the communication system 10 may include multiple first devices and multiple second devices, which will be uniformly described here and will not be repeated below.

[0088] Optional, such as Figure 1 As shown, the communication system 10 may further include a cloud server 40. The cloud server 40 can communicate directly with the first device 20 or the second device 30, or it can communicate through forwarding from other devices; this embodiment does not specifically limit this. The cloud server 40 is used to authenticate the second device 30. If the second device 30 passes authentication, the cloud server 40 sends the operating information of the first device 20 to the second device 30.

[0089] Optionally, the first device in this application embodiment can be any communication device with wireless transceiver function used to communicate with the second device.

[0090] Optionally, the second device in this application embodiment can be a device with a screen, which is a device with a display screen, such as terminal equipment with a screen. Terminal equipment can refer to access terminal, user unit, user station, mobile station, mobile station, relay station, remote station, remote terminal, mobile device, user terminal, UE, terminal, wireless communication equipment, user agent, user device, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, vehicle equipment, wearable device, terminal equipment in future 5G networks, terminal equipment in future evolved PLMNs, or terminal equipment in future vehicle networks, etc. This application embodiment does not limit this.

[0091] By way of example and not limitation, in the embodiments of this application, the terminal may be a mobile phone, tablet computer, computer with wireless transceiver function, virtual reality terminal device, augmented reality terminal device, wireless terminal in industrial control, wireless terminal in autonomous driving, wireless terminal in remote surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0092] As an example and not a limitation, in this application embodiment, wearable devices can also be called wearable smart devices. This is a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functionality without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific application function and require use with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0093] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technology, thereby realizing an intelligent network for human-machine interconnection and machine-to-machine interconnection. In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB).

[0094] Optionally, the first or second device in the embodiments of this application may also be referred to as a communication device, which may be a general-purpose device or a special-purpose device. The embodiments of this application do not specifically limit this.

[0095] Optionally, the relevant functions of the first or second device in the embodiments of this application can be implemented by one device, multiple devices working together, or one or more functional modules within a single device. This application does not specifically limit these functions. It is understood that the aforementioned functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0096] For example, the relevant functions of the first or second device in the embodiments of this application can be achieved through... Figure 2 This is achieved through the communication device 200. Figure 2 The diagram shown is a structural schematic of a communication device 200 provided in an embodiment of this application. The communication device 200 includes one or more processors 201, a communication line 202, and at least one communication interface. Figure 2 (This is merely an example illustration, using a communication interface 204 and a processor 201 as examples. Optionally, a memory 203 may also be included.)

[0097] The processor 201 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0098] The communication line 202 may include a path for connecting different components.

[0099] The communication interface 204 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. For example, the transceiver module can be a transceiver or similar device. Optionally, the communication interface 204 can also be a transceiver circuit located within the processor 201, used to implement the processor's signal input and signal output.

[0100] The memory 203 can be a device with storage functionality. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited to these. The memory can exist independently and be connected to the processor via communication line 202. The memory can also be integrated with the processor.

[0101] The memory 203 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 201. The processor 201 executes the computer execution instructions stored in the memory 203, thereby implementing the communication method provided in the embodiments of this application.

[0102] Alternatively, in this embodiment, the processor 201 may execute the processing-related functions of the communication method provided in the following embodiments of this application, and the communication interface 204 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0103] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0104] In a specific implementation, as one embodiment, the processor 201 may include one or more CPUs, for example... Figure 2 CPU0 and CPU1 in the CPU.

[0105] In a specific implementation, as one example, the communication device 200 may include multiple processors, such as... Figure 2 The processors 201 and 208 are described herein. Each of these processors may be a single-core processor or a multi-core processor. The processors herein may include, but are not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, and other computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0106] In a specific implementation, as one embodiment, the communication device 200 may further include an output device 205 and an input device 206. The output device 205 communicates with the processor 201 and can display information in various ways. For example, the output device 205 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 206 communicates with the processor 201 and can receive user input in various ways. For example, the input device 206 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0107] The aforementioned communication device 200 may sometimes be referred to as a communication device, which can be a general-purpose device or a special-purpose device. For example, the communication device 200 may be a desktop computer, a portable computer, a network server, a handheld digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the aforementioned terminal device, the aforementioned network device, or a device with... Figure 2 Devices with similar structures. This application does not limit the type of communication device 200 to any particular embodiment.

[0108] For example, taking a mobile phone as the second device, Figure 3 This is a specific structural form of the second device 30 provided in the embodiments of this application.

[0109] In some embodiments, Figure 2 The function of processor 201 in the middle can be achieved through Figure 3 The processor 110 is implemented in it.

[0110] In some embodiments, Figure 2 The function of the communication interface 204 in the middle can be achieved through Figure 3 The second device 30 is implemented using antenna 1, antenna 2, mobile communication module 150, and wireless communication module 160. Mobile communication module 150 can provide solutions for wireless communication technologies such as LTE, NR, or future mobile communication technologies applied to the second device 30. Wireless communication module 160 can provide solutions for wireless communication technologies such as WLAN (e.g., Wi-Fi), Bluetooth, Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), and infrared technologies applied to the second device 30. In some embodiments, antenna 1 of the second device 30 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling the second device 30 to communicate with networks and other devices via wireless communication technologies.

[0111] In some embodiments, Figure 2 The function of memory 203 in the middle can be achieved through Figure 3 It can be implemented by internal memory 51 or external memory connected to external memory interface 50, etc.

[0112] In some embodiments, Figure 2 The function of the output device 205 can be achieved through Figure 3 The display screen 194 is implemented in the middle.

[0113] In some embodiments, Figure 2 The input device 206 can function through a mouse, keyboard, touch screen device, or Figure 3 This is achieved through the sensor module 180.

[0114] In some embodiments, such as Figure 3 As shown, the second device 30 may also include one or more of the following: an audio module 170, a camera 193, a button 190, a SIM card interface 195, a USB interface 40, a charging management module 140, a power management module 141, and a battery 142.

[0115] Understandable, Figure 3 The structure shown does not constitute a specific limitation on the second device 30. For example, in other embodiments of this application, the second device 30 may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0116] The following will combine Figures 1 to 3 The communication method provided in the embodiments of this application will be described in detail.

[0117] like Figure 4 The diagram illustrates a communication method provided in an embodiment of this application. This communication method includes the following steps S401-S403:

[0118] S401, The first device obtains the operating information of the first device.

[0119] S402, The first device establishes communication with the second device, which has an NFC chip.

[0120] S403, The first device sends its operating information to the second device.

[0121] In this embodiment, the first device has an NFC chip, that is, it has NFC capability and can make point-to-point wireless communication connections with devices that also have NFC capability. For details, please refer to the above introduction of NFC in the prior art, which will not be repeated here.

[0122] The following describes steps S401-S404.

[0123] Regarding step S401 above, in this embodiment of the application, the first device, such as a router or base station, can obtain its own generated operating information during operation, and this operating information can reflect the operating status of the first device.

[0124] Optionally, the following description will be given using the operational information of the first device, including the problem log and / or usage record of the first device, as an example. Regarding the problem log, in this embodiment, when an anomaly occurs during the operation of the first device, such as a malfunction of the first device itself, an anomaly in the network connected to the first device, or an attack on the first device while connected to the network, the first device will generate a problem log. The problem log records information about the anomaly. Users can analyze the problem log to determine the cause of the first device malfunction or discover traces of attackers; that is, users can locate the problem by analyzing the problem log. Regarding the usage record, in this embodiment, the first device is used by the user during operation, generating a usage record that reflects the usage of the first device. For example, the usage record can record the corresponding operation information when the user uses the first device, such as key presses and input information. The usage record can also record information such as the usage duration of the first device.

[0125] In step S402, in this embodiment of the application, the second device has an NFC chip, i.e., it has NFC capability. Therefore, the first device can establish wireless communication with the second device via NFC to transmit data.

[0126] Optionally, the first device can establish NFC communication with the second device through a method such as "tap-to-pay". Specifically, "tap-to-pay" can be achieved by bringing the NFC chip of the second device close to or touching the NFC chip of the first device, so that the first device and the second device meet the short-range condition for establishing NFC communication.

[0127] In step S403, in this embodiment of the application, after the first device and the second device establish NFC communication, the operating information of the first device can be sent to the second device so that the user can obtain the operating information of the first device through the second device.

[0128] The communication method provided in this application embodiment can send the operating information of the first device, such as the problem log and / or usage record of the first device, to the second device via NFC. The process of transmitting the operating information of the first device does not require specific software or must be transmitted when the first device is powered on or connected to the network, as in the prior art. Therefore, it reduces the operation actions of obtaining the device's operating information, saves the time of obtaining the device's operating information, and makes it possible to obtain the device's operating information more quickly and conveniently.

[0129] The operation of the first device in steps S401 to S403 can be performed by... Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the first device to execute; the actions of the second device in the above steps S401 to S403 can be performed by... Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the second device to execute, and this embodiment does not impose any limitations on this.

[0130] As can be seen from the above, the cause of the abnormal situation of the first device that caused the problem log can be obtained by analyzing the problem log of the first device. Therefore, optionally, in this embodiment of the application, if the operating information of the first device includes the problem log of the first device, before step S402, the communication method provided in this embodiment of the application further includes: the first device obtaining the root cause of the problem that caused the problem log of the first device; after step S402, the communication method provided in this embodiment of the application further includes: the first device sending the root cause of the problem to the second device.

[0131] In this embodiment of the application, the cause of the device malfunction located based on the problem log can be referred to as the root cause of the problem.

[0132] In one possible implementation, the first device obtains the root cause of the problem log that caused the problem log, including: the first device determining the root cause of the problem log based on the problem log. That is, the first device analyzes the problem log itself to obtain the root cause. For example, the first device can analyze the problem log according to a pre-configured analysis model to obtain the root cause of the problem log, so as to locate the problem on the first device. Since the first device can determine the root cause of the problem log itself in this scheme, there is no need to transmit the problem log to other devices for analysis, thus saving time in problem location and ensuring the security of user data. On the other hand, considering that the storage space of some first devices is insufficient to store the root cause, the root cause analyzed by the first device when the first device malfunctions can be stored on a cloud server. When the first device needs to send the root cause to a second device (e.g., when the user selects the desired root cause on the second device), the cloud server sends the required root cause to the first device. In other words, in this embodiment of the application, after the first device determines the root cause of the problem log based on the problem log of the first device, and before the first device sends the root cause to the second device, the method further includes: the first device sending the root cause to a cloud server, whereby the cloud server stores the root cause; the first device receiving a first request message from the second device, the first request message being used to request the root cause of the problem log of the first device; and the first device sending a second request message to the cloud server, the second request message being used to request the root cause of the problem log of the first device. Based on this scheme, the root cause analyzed by the first device does not occupy the storage space of the first device.

[0133] In another possible implementation, the first device obtains the root cause of the problem log generated by the first device, including: the first device receiving the root cause of the problem log generated by the first device from the cloud server. Optionally, before the first device receives the root cause of the problem log generated by the first device from the cloud server, the solution further includes: the first device sending its problem log to the cloud server, whereby the cloud server determines the root cause of the problem log generated by the first device. That is, in this solution, the cloud server analyzes the first device's problem log, determines the root cause of the problem log generated by the first device, and then sends the root cause to the first device. On the one hand, because the cloud server has sufficient computing resources and strong computing power, the root cause determined by the cloud server based on the problem log is highly accurate, and the problem is located more precisely. On the other hand, since this solution does not require the first device to locate the root cause, it not only saves the first device's computing resources but also ensures that the first device, which cannot analyze its own problem logs, obtains the root cause of the problem. Alternatively, before the first device receives the root cause of the problem log generated by the cloud server, the method may include: the first device sending the problem log to another device besides the cloud server, whereby the other device determines the root cause and then sends it to the cloud server. This application embodiment does not limit how the root cause of the problem received by the first device from the cloud server is determined.

[0134] Optionally, the first device can choose different methods to obtain the root cause of the problem based on its network conditions. For example, when the first device is offline or has a poor network connection, it can analyze the problem logs itself to determine the root cause. When the first device has a good network connection, the cloud server can analyze the problem logs to determine the root cause and send it to the first device. This solution allows for flexible selection of the method to obtain the root cause based on the first device's network conditions. When the network is good, the cloud server with strong computing power determines the root cause, resulting in a more accurate diagnosis. When the network is poor or offline, the first device can determine the root cause independently of the network.

[0135] Based on the above solution, users can directly obtain the root cause of the problem log generated by the first device through the second device, without the need for users to manually export the problem log using specific software and then analyze the problem log using appropriate technology to determine the root cause. Therefore, it is possible to conveniently and quickly locate the problem of the first device.

[0136] To ensure the security of the operating information of the first device, optionally, in this embodiment, after step S402, the method further includes: the first device authenticating the identity of the second device. Further, the first device sending its operating information to the second device includes: if the second device passes authentication, the first device sending its operating information to the second device.

[0137] For example, assuming the second device is bound to a second account and the first device is bound to a first account (e.g., a mobile phone is bound to a user account at the factory, and a smart home device is bound to a platform account), when a user uses the first device for the first time, they can bind the second account on the second device to the first account on the first device by means such as scanning a QR code or logging into a specific platform application. The second account bound to the first account can be called the authorized account of the first device, or the administrator account. Therefore, after establishing an NFC connection with the second device, the first device can authenticate the second device by verifying whether the account bound to the second device is the authorized account of the first device.

[0138] Optionally, the account information of the first and second devices can be stored on the first device. For example, the binding relationship between the first device and the first account, and the binding relationship between the first account and the second account, can be stored in the storage space of the first device. Further, the first device can use the aforementioned account information to authenticate the second device locally. Specifically, after the second device establishes an NFC connection with the first device, the second device sends its bound second account to the first device. The first device verifies that the second account sent by the second device is a stored authorized account bound to the first account, and based on the binding relationship between the first device and the first account, determines that the first account is an account bound to the first device, thereby authenticating the second device. This solution can authenticate the second device locally using account information stored on the first device itself, thus enabling authentication of the second device even when the first device is not connected to the internet, without relying on a network. Optionally, the account information of the first and second devices can be stored on a cloud server. For example, the binding relationship between the first device and the first account is stored on the cloud server corresponding to the first device, and the binding relationship between the second device and the second account is stored on the cloud server corresponding to the second device. After binding the first account and the second account, both the first device and the second device upload this binding relationship to their respective cloud servers. Furthermore, when the first device authenticates the second device, it can determine whether the second device's account is an authorized account of the first device by querying the account information in the corresponding cloud server. Alternatively, the first and second devices can also upload this binding relationship to a common third-party server, and the first device queries this third-party server when authenticating the second device. In this solution, the first device can authenticate the second device through the cloud server without needing to store account information itself, thus not occupying the first device's storage space.

[0139] Optionally, authentication can be performed by combining local storage on the first device and cloud server access. For example, the account information of the first and second devices can be stored locally on the first device and on a cloud server. The first device can query its own storage space or the cloud server based on its own status or network conditions to authenticate the second device.

[0140] Optionally, users can modify or delete account information stored on the first device and / or cloud server by, for example, logging into a specific application or platform. This embodiment does not specifically limit this. Further, if account information stored locally on the first device is modified or deleted, the first device can automatically upload the updated account information to the cloud server after connecting to the network. Further, if the second device passes authentication—for example, if the first device verifies that the account bound to the second device is a valid account of the first device—the first device will send its operating information to the second device. If the second device fails authentication, the first device will not send its operating information to the second device until authentication is successful. Optionally, if the second device fails authentication n times consecutively, where n is a positive integer greater than or equal to 1, the first device will stop NFC communication with the second device.

[0141] Based on the above scheme, since the first device can determine whether to send operation information to the second device by authenticating the second device, only the second device that has passed the authentication can receive the operation information of the first device, thus improving the confidentiality and security of the operation information of the first device.

[0142] Optionally, in this embodiment of the application, after step S402 and before step S403, the method further includes: the first device receiving a first request from the second device, the first request being used to request the first device to send the operating information of the first device.

[0143] That is, in this embodiment of the application, after the first device and the second device establish NFC communication, the user can operate the second device according to their own needs, causing the second device to send a first request to the first device to request the first device to send operating information. Further, after receiving the first request, the first device sends its own operating information to the second device. For example, after the first device and the second device establish NFC communication, the second device's display page shows the operating information that the first device can send. The user can click on the operating information they want to obtain (such as a problem log) according to their own needs. Then, based on the user's click operation, the second device sends a first request to the first device to request the user-selected operating information. After receiving the first request, the first device sends the corresponding operating information to the second device via NFC communication.

[0144] Optionally, the first request can also be used to request the root cause of the problem log generated by the first device. For a detailed implementation, please refer to the above description of how the first device sends its operational information to the second device after receiving the first request; this will not be repeated here.

[0145] Based on the above scheme, the first device can send its own operating information to the second device according to the request information sent by the second device. That is, the first device can send its own operating information to the second device according to the second device's needs, instead of sending the first device's operating information automatically or randomly. This not only saves communication resources, but is also more user-friendly.

[0146] Optionally, in this embodiment of the application, after step S401, the method further includes: the first device storing the operating information of the first device.

[0147] Specifically, after acquiring the operating information of the first device, the first device can store the operating information, that is, the first device can store the historical operating information of the first device. Based on this scheme, the user can obtain the historical operating information of the first device through the second device. Furthermore, the user can understand the historical operating status of the first device through the historical operating information of the first device, which is more in line with user needs.

[0148] Optionally, the communication method provided in this application embodiment further includes: the first device deleting the stored operating information of the first device according to a management cycle, wherein the management cycle is used to manage the operating information of the first device.

[0149] Specifically, because the amount of data related to the operation information of the first device is large, in order to save storage space, the first device can periodically delete its operation information according to a set management cycle. Optionally, in this embodiment, the management cycle can be the default management cycle pre-configured in the first device; or, the user can set the management cycle of the first device through a second device bound to a second account. This embodiment does not specifically limit this. This solution can periodically delete the operation information of the first device according to the management cycle, ensuring the normal operation or efficiency of the first device with limited storage space or no space to store operation information.

[0150] Optionally, in this embodiment, the management cycle can be used to manage a certain type of information in the first device's operation information. For example, the first device can periodically delete its usage records according to the management cycle, while retaining problem logs.

[0151] Optionally, in this embodiment, the management cycle can be divided according to the type of the first device's operating information. For example, the first device's usage record corresponds to the first management cycle, and the first device's problem log corresponds to the second management cycle. This embodiment does not specifically limit this.

[0152] Optionally, the communication method provided in this application embodiment further includes: the first device sending its operating information to a cloud server, and the cloud server storing the operating information of the first device.

[0153] That is, in this embodiment of the application, as the first device operates, more and more operational information is generated. The first device can send the generated operational information to a cloud server, where the cloud server stores a large amount of operational information. Based on this solution, the storage space of the first device can be saved, ensuring the normal operation or operational efficiency of the first device with limited or no storage space for operational information.

[0154] Optionally, in this embodiment of the application, the NFC chip of the first device is written with a first tag, which includes a general device tag, a debugging device tag, or a monitoring device tag.

[0155] As can be seen from the above, this application provides multiple optional solutions in its embodiments. However, the operational information required by the user for different first devices generally varies. Manufacturers of the first devices can classify them by writing different tags into the NFC tags of the first devices according to user needs. Specifically, the relationship between the first tag and the first device type will be described below in conjunction with specific scenarios, and will not be elaborated upon here.

[0156] Optionally, in this embodiment, the operating information of the first device may further include the operation log of the first device. The operation log of the first device can record all operation information and status information of the first device during use in the form of a log. The problem log in this embodiment is the operation log that records the abnormal situation of the first device when an anomaly occurs. Users can quickly and conveniently obtain the operation log of the first device through the second device, and thus gain a more comprehensive understanding of the operating status of the first device by analyzing the operation log.

[0157] like Figure 5 As shown, another communication method provided in this application embodiment includes the following steps S501-S503:

[0158] S501, The second device establishes communication with the first device, which has an NFC chip.

[0159] S502, The second device receives the operating information of the first device from the first device.

[0160] S503, the second device displays the operating information of the first device.

[0161] For the specific implementation of steps S501 and S502 above, please refer to the introduction of steps S402 and S403 above.

[0162] Regarding step S503 above, in this embodiment of the application, after the second device obtains the operating information from the first device, it will display the operating information of the first device so that the user can obtain and view the operating information of the first device through the second device.

[0163] Optionally, in order for users to conveniently view the operating information of the first device through the second device, the second device can be a device that is easy for users to carry and view, such as a mobile phone or wearable device with a display screen.

[0164] In this embodiment, the second device can receive the operating information of the first device through NFC technology and display the operating information on the second device, so that the user can conveniently view the operating information of the first device on the second device without relying on specific software or the status of the first device. For example, when the first device is not powered on or connected to the Internet, the user can quickly and conveniently obtain the operating information of the first device.

[0165] The operation of the first device in steps S501 to S503 can be performed by... Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the first device to execute; the actions of the second device in the above steps S501 to S503 can be performed by... Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the second device to execute, and this embodiment does not impose any limitations on this.

[0166] Optionally, in this embodiment, the operating information of the first device includes the problem log and / or usage record of the first device. See the description of the problem log and / or usage record of the first device in step S401 above for details.

[0167] To facilitate users in obtaining and viewing the possible causes of the abnormal situation of the first device that led to the problem log of the first device, optionally, in this embodiment of the application, when the operating information of the first device includes the problem log of the first device, after step S501, the method further includes: the second device receiving the root cause of the problem that led to the problem log of the first device from the first device. Related descriptions can be found in [reference needed]. Figure 4 The embodiments described herein will not be repeated here.

[0168] Optionally, in this embodiment of the application, after the second device receives the root cause of the problem log generated by the first device, the method further includes: the second device displaying the root cause. That is, after obtaining the root cause from the first device, the second device displays the obtained root cause on itself, such as on the second device's display screen or display interface, so as to facilitate the user to view the root cause of the problem in the first device.

[0169] In order to receive the operating information of the first device according to the user's needs, this application embodiment optionally also provides the following solution:

[0170] After step S501 and before step S502, the method further includes: the second device sending a first request to the first device, the first request being used to request the first device to send its operating information. (See relevant descriptions.) Figure 4 The embodiments described herein will not be repeated here.

[0171] Optionally, in this embodiment, the operating information of the first device may further include the operation log of the first device. For details, please refer to the above description of the operation log of the first device, which will not be repeated here.

[0172] As can be seen from the above, optionally, in the embodiments of this application, the NFC chip of the first device is written with a first tag, which includes a general device tag, a debugging device tag, or a monitoring device tag. For ease of understanding, the following will specifically describe the scheme of writing a first tag into the NFC chip of the first device provided in the embodiments of this application, combined with specific scenarios.

[0173] by Figure 4 or Figure 5 In this embodiment of the method, the second device is a user's mobile phone. Figure 6 This is a flowchart illustrating a communication method provided in this application embodiment when an NFC chip of a first device writes to a universal device tag. For convenience, in the following description, the first device whose NFC chip is written to the universal device tag is referred to as the universal device. The universal device includes an identity binding and determination module, a periodic management module, an information recording module, an NFC module, and a problem location module. For example, as shown... Figure 6 As shown, the communication method includes the following steps:

[0174] S6011. Upon initial use of the universal device, the user's mobile phone binds to the universal device through the identity binding and verification module within the universal device. For detailed binding procedures, please refer to [link / reference needed]. Figure 4 The relevant descriptions in the embodiments described herein will not be repeated here.

[0175] Optionally, in this embodiment of the application, when the general-purpose device connects to the network for the first time, the general-purpose device can upload its tag to the cloud server and register the general-purpose device on the cloud server.

[0176] S6012 The periodic management module in the general device has a default management period set. The periodic management module will periodically delete the usage records stored in the general device according to the management period. After the user's mobile phone is bound to the general device, the user can adjust the management period through the mobile phone.

[0177] S6021. The information recording module in the general equipment automatically records and stores the operating information generated by the general equipment during operation, such as the operation log or usage record of the general equipment.

[0178] S6022, The information recording module in the general equipment sends the recorded problem log to the problem location module.

[0179] S6023. After the problem location module in the general equipment analyzes the root cause of the abnormality of the general equipment based on the problem log, it sends the root cause to the information recording module, which stores the root cause.

[0180] It should be noted that, in this embodiment of the application, the problem localization process, including steps S6022 and S6023, in one possible implementation, begins when the information recording module discovers an anomaly in the general-purpose device. Specifically, after the general-purpose device malfunctions, the information recording module discovers the anomaly based on the recorded operation logs and sends the problem log from the operation logs to the problem localization module for localization. In another possible implementation, the problem localization process starts periodically according to a certain cycle. Specifically, the information recording module periodically sends all operation logs recorded within the pre-configured cycle to the problem localization module, which then analyzes all operation logs to determine if there are any problem logs and the corresponding root causes. In yet another possible implementation, such as... Figure 6 In step S6041, the problem localization process begins with a "tap-to-tap" between the user's mobile phone and the universal device, that is, the establishment of NFC communication between the user's mobile phone and the universal device. Specifically, after the "tap-to-tap," the information recording module sends the recorded problem log to the problem localization module for problem localization.

[0181] S603. When the general-purpose device is connected to the network, the information recording module uploads the relevant data of the general-purpose device to the cloud server for storage. The relevant data of the general-purpose device stored in the information recording module includes the operating information of the general-purpose device and the root cause of abnormal situations.

[0182] S6041. The user's mobile phone initiates a "tap-to-connect" with the NFC module of the general-purpose device, that is, the user's mobile phone establishes NFC communication with the general-purpose device.

[0183] S6042. After the user's mobile phone is tapped against the universal device, the NFC module in the universal device authenticates the user's mobile phone through the identity binding and determination module. If the user's mobile phone passes the authentication, the next step S6043 can be executed.

[0184] S6043. The user selects the relevant data of the general device that he / she wants to obtain through the mobile phone, such as the problem log, usage record or root cause of the problem of the general device, and sends a request to the NFC module in the general device to request the selected data.

[0185] S6044, The information recording module in the general device sends the data selected by the user to the user's mobile phone.

[0186] S6051. When a user logs into the application via their mobile phone, the cloud server verifies the user's identity using the mobile phone. If the verification is successful, the user can select the relevant data of the universal device bound to the mobile phone to view on the mobile phone.

[0187] S6052, The cloud server sends relevant data of the general device selected by the user to the user's mobile phone.

[0188] Based on the solution in steps S6051 to S6052, users can log in to their mobile phones via the internet to obtain the data of the general-purpose devices they want to view from the cloud server. In other words, users can conveniently obtain the data of general-purpose devices using only their mobile phones.

[0189] Figure 6 For the technical effects of the communication method provided in the illustrated embodiment, please refer to [link / reference]. Figure 4 The technical effects of the embodiments shown will not be repeated here.

[0190] Among them, the actions of the mobile phone in steps S6011 to S6052 above can be performed by... Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the mobile phone to execute; the actions of the general-purpose device in the above steps S6011 to S6052 can be performed by Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the general-purpose device to execute it; this embodiment does not impose any limitations on this.

[0191] by Figure 4 or Figure 5 In this embodiment of the method, the second device is a user's mobile phone. Figure 7This is a flowchart illustrating a communication method provided in this application embodiment when an NFC chip of a first device writes to a debugging device tag. For convenience, in the following description, the first device for writing the NFC chip to the debugging device tag is referred to as the debugging device. The debugging device includes an information recording module, an NFC module, and a problem location module. For example, as... Figure 7 As shown, the communication method includes the following steps:

[0192] S701 The information recording module in the debugging equipment will automatically record and store the operation logs generated by the debugging equipment during operation.

[0193] S7021, The information recording module in the debugging equipment sends the problem log to the problem location module.

[0194] S7022. After analyzing the problem log to determine the root cause of the debugging equipment malfunction, the problem location module in the debugging equipment sends the root cause to the information recording module, which stores the root cause. The specific implementation of steps S7021 and S7022 can be found in the description of steps S6022 and S6023 above, and will not be repeated here.

[0195] S7031. The user's mobile phone initiates a "tap-to-connect" with the NFC module of the debugging device, establishing NFC communication between the user's mobile phone and the debugging device. The user then selects the desired problem log or root cause of the problem on their mobile phone.

[0196] S7032, The information recording module in the debugging equipment sends the user-selected problem log or root cause of the problem to the user's mobile phone.

[0197] like Figure 7 As shown, the debugging equipment primarily outputs data related to problem localization. The problem localization module within the debugging equipment can analyze the root cause of the problem based on the problem logs recorded by the information recording module. After the user's mobile phone establishes NFC communication with the debugging equipment via the NFC module, the user can select the problem logs or root causes to view on their phone. Therefore, users do not need to use specific software to retrieve problem logs on a computer; they can quickly and conveniently obtain problem logs and localize anomalies in the debugging equipment, thereby understanding the equipment's operational status. Furthermore, users can directly obtain the root causes of equipment anomalies for timely repair, simplifying the problem localization process without needing to analyze the problem logs themselves.

[0198] because Figure 7In this example, the debugging device does not include an identity binding and judgment module, eliminating the need for user authentication. Therefore, all users can view the device's problem logs or root causes, allowing for quick identification and resolution of issues. Optionally, the debugging device may include an identity binding and judgment module. It may also include a periodic management module, the functionality of which is similar to that in general-purpose devices. Furthermore, the debugging device may be used in scenarios involving cloud servers, the functionality of which is similar to that in general-purpose devices and will not be elaborated upon here.

[0199] Among them, the actions of the mobile phone in steps S701 to S7032 above can be performed by... Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the mobile phone to execute; the debugging device actions in steps S701 to S7032 above can be performed by Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the debugging device to execute, and this embodiment does not impose any limitations on this.

[0200] by Figure 4 or Figure 5 In this embodiment of the method, the second device is a user's mobile phone. Figure 8 This is a flowchart illustrating a communication method provided in this application embodiment when the NFC chip of a first device writes to a tag of a monitoring device. For convenience, in the following description, the first device whose NFC chip is written to the tag of the monitoring device is referred to as the monitoring device. The monitoring device includes an identity binding and determination module, a periodic management module, an information recording module, and an NFC module. For example, as shown... Figure 8 As shown, the communication method includes the following steps:

[0201] S8011. When the monitoring equipment is used for the first time, the user's mobile phone is bound to the monitoring equipment through the identity binding and verification module in the monitoring equipment. For specific binding procedures, please refer to [link / reference]. Figure 4 The relevant descriptions in the embodiments described herein will not be repeated here.

[0202] Optional ( Figure 8 (Not shown in the image) When the monitoring device connects to the network for the first time, it uploads its tag to the cloud server and registers the device on the cloud server.

[0203] The S8012 monitoring device's periodic management module has a default management cycle set. This module periodically deletes the operational information stored within the monitoring device according to the management cycle. After a user binds their mobile phone to the monitoring device, the user can adjust the management cycle via their phone.

[0204] S802. The information recording module in the monitoring equipment automatically records and stores operational information generated during the operation of the monitoring equipment, such as the monitoring equipment's operation log or usage record. Optionally, the information recording module also records and stores the monitoring equipment's problem log as operational information.

[0205] S803: When the monitoring equipment is connected to the network, the information recording module in the monitoring equipment uploads the stored operation information to the cloud server for storage.

[0206] S8041, The user's mobile phone initiates a "tap-to-connect" with the NFC module of the monitoring device, that is, the user's mobile phone establishes NFC communication with the monitoring device.

[0207] S8042. After the user's mobile phone is "touch-to-touch" with the monitoring device, the NFC module in the monitoring device authenticates the user's mobile phone through the identity binding and judgment module. If the user's mobile phone passes the authentication, the next step S8043 can be executed.

[0208] S8043. The user selects the desired operating information of the monitoring device via mobile phone, such as the monitoring device's problem logs and / or usage records, and sends a request for the selected operating information to the NFC module in the monitoring device.

[0209] S8044, The information recording module in the monitoring equipment sends the operating information selected by the user to the user's mobile phone.

[0210] S8051. Users log in to the application via their mobile phones. The cloud server authenticates the user's mobile phone. If the authentication is successful, the user can select the operating information of the monitoring device bound to the mobile phone to view on the mobile phone.

[0211] S8052, the cloud server sends the operating information of the monitoring device selected by the user to the user's mobile phone.

[0212] like Figure 8As shown, for data confidentiality reasons, the monitoring device includes an identity binding and determination module. Only users with designated accounts can access and view the device's usage records and other operational information. The device also includes a periodic management module, an information recording module, and an NFC module. The monitoring device primarily outputs data related to its usage. After the user's mobile phone establishes NFC communication with the monitoring device via the NFC module, the user can select the desired usage records and other data on their phone. This allows users to access the monitoring device's usage records and other data without needing to power on the device, access a specific page on the device, or connect to the internet. Therefore, this solution simplifies the process of obtaining monitoring device operational information, providing a quick and convenient way to understand the device's usage status.

[0213] Among them, the actions of the mobile phone in the above steps S8011 to S8052 can be performed by Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the mobile phone to execute; the actions of the monitoring device in the above steps S8011 to S8052 can be performed by Figure 2 The processor 201 in the communication device 200 shown calls the application code stored in the memory 203 to instruct the monitoring device to execute, and this embodiment does not impose any restrictions on this.

[0214] In summary, in this embodiment, the first device can be categorized based on the classification of the first tag written into its NFC chip. Different types of first devices output different data. For example, when the first tag includes a general device tag, a debugging device tag, or a monitoring device tag, the general device tag outputs the most comprehensive data types, such as problem logs, usage records, and root cause data. Debugging devices primarily output data related to device problem localization, such as problem logs and root cause data. Monitoring devices primarily output data related to device usage, such as usage records. Therefore, manufacturers of the first device can enable it to provide different types of output data based on the chip written into its NFC chip.

[0215] Optionally, in this embodiment, the first tag may include other tags, and the first device may be classified into other device types, depending on the user's needs. For example, the first tag may include a basic device tag. If the basic device tag is written into the NFC chip of the first device, the first device will also send basic information of the first device to the second device, such as the production date and / or place of production of the first device. This embodiment does not specifically limit this.

[0216] Optionally, in this embodiment, the number of first tags written in the NFC chip of the first device can be one, or the number of first tags written in the NFC chip of the first device can be greater than one. That is, in this embodiment, the type of a first device can include one or more. For example, if a debugging device tag is written in the NFC tag of the first device, the type of the first device is a debugging device; if the NFC tag of the first device contains both debugging device and monitoring device tags, the type of the first device includes both debugging device and monitoring device. This embodiment does not limit the scope of the application.

[0217] In this embodiment of the application, the operation of the first device in steps S401 to S403 above can be performed by... Figure 2 The processor 201 in the communication device 200 shown executes the application code stored in the memory 203, and the operation of the second device in steps S501 to S503 can be performed by... Figure 2 The processor 201 in the communication device 200 shown executes the application code stored in the memory 203.

[0218] It is understood that, in the above embodiments, the methods and / or steps implemented by the first device can also be implemented by components (e.g., chips or circuits) that can be used in the first device; and the methods and / or steps implemented by the second device can also be implemented by components (e.g., chips or circuits) that can be used in the second device.

[0219] This application also provides a communication device for implementing the various methods described above. This communication device can be a first device in the above method embodiments, or a device including the first device, or a component usable in the first device; alternatively, the communication device can be a second device in the above method embodiments, or a device including the second device, or a component usable in the second device. It is understood that, in order to implement the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware 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 application.

[0220] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0221] Figure 9 A schematic diagram of a communication device 90 is shown. The communication device 90 includes a transceiver module 901 and a processing module 902. The transceiver module 901, also known as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver, a transceiver device, or a communication interface.

[0222] Taking the communication device 90 applied to the first device in the above method embodiment as an example, then:

[0223] Processing module 902 is used to acquire the operating information of the first device. Processing module 902 is also used to establish communication with a second device having an NFC chip. Transceiver module 901 is used to send the operating information of the first device to the second device.

[0224] Optionally, the operational information of the first device includes the problem logs and / or usage records of the first device.

[0225] Optionally, the operating information of the first device includes the problem log of the first device. The processing module 902 is also used to obtain the root cause of the problem that caused the problem log of the first device. The transceiver module 901 is also used to send the root cause of the problem to the second device.

[0226] Optionally, the processing module 902 is also used to obtain the root cause of the problem log generated by the first device, including: determining the root cause of the problem log generated by the first device based on the problem log of the first device.

[0227] Optionally, the processing module 902 is also used to obtain the root cause of the problem log generated by the first device, including: receiving the root cause of the problem log generated by the first device from the cloud server via the transceiver module 901.

[0228] Optionally, the transceiver module 901 is also used to send the problem log of the first device to the cloud server, so that the cloud server can determine the root cause of the problem log of the first device.

[0229] Optionally, the processing module 902 is also used to authenticate the second device; the transceiver module 901 is used to send the operating information of the first device to the second device, including: if the second device passes the authentication, sending the operating information of the first device to the second device.

[0230] Optional, such as Figure 9 As shown, the communication device 90 also includes a storage module 903, which is used to store account information of the first device and the second device. The account information of the first device and the second device is used to authenticate the identity of the second device.

[0231] Optionally, the account information for the first device and the second device includes the binding relationship between the first device and the first account, and the binding relationship between the first account and the second account bound to the second device. Optionally, the transceiver module 901 is further configured to receive a first request from the second device, the first request being used to request the first device to send its operating information.

[0232] Optionally, the storage module 903 is also used to store the operating information of the first device.

[0233] Optionally, the processing module 902 is also used to delete the stored operating information of the first device according to the management cycle, the management cycle being used to manage the operating information of the first device.

[0234] Optionally, the transceiver module 901 is also used to send the operating information of the first device to the cloud server, whereby the cloud server stores the operating information of the first device.

[0235] Optionally, the NFC chip of the first device is written with a first tag, which may include a general device tag, a debugging device tag, or a monitoring device tag.

[0236] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0237] In this embodiment, the communication device 90 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the communication device 90 can employ... Figure 2 The communication device 200 shown is in the form of [example device].

[0238] for example, Figure 2The processor 201 in the communication device 200 shown can execute the communication method in the above method embodiment by calling the computer execution instructions stored in the memory 203.

[0239] Specifically, Figure 9 The functions / implementation process of the transceiver module 901 and the processing module 902 can be obtained through... Figure 2 The processor 201 in the communication device 200 shown calls computer execution instructions stored in the memory 203 to implement the communication. Figure 9 The function / implementation process of the storage module 903 can be obtained through Figure 2 This is implemented using the memory 203 in the communication device 200 shown. Alternatively, Figure 9 The function / implementation process of the processing module 902 can be achieved through... Figure 2 The processor 201 in the communication device 200 shown calls computer execution instructions stored in the memory 203 to implement the communication. Figure 9 The function / implementation process of the transceiver module 901 can be obtained through Figure 2 This is achieved through the communication interface 204 in the communication device 200 shown. Figure 9 The function / implementation process of the storage module 903 can be obtained through Figure 2 This is implemented using the memory 203 in the communication device 200 shown.

[0240] Since the communication device 90 provided in this embodiment can execute the communication method in the above method embodiment, the technical effects it can obtain can be referred to the above method embodiment, and will not be repeated here.

[0241] Figure 10 A schematic diagram of another communication device 100 is shown. This communication device 100 includes a transceiver module 1001, a processing module 1002, and a display module 1003. The transceiver module 1001, also referred to as a transceiver unit, is used to implement transceiver functions; for example, it can be a transceiver circuit, transceiver, transceiver device, or communication interface.

[0242] Taking the communication device 100 applied to the second device in the above method embodiment as an example, then:

[0243] Processing module 1002 is used to establish communication with a first device having an NFC chip. Transceiver module 1001 is used to receive operating information from the first device. Display module 1003 is used to display the operating information of the first device.

[0244] Optionally, the operational information of the first device includes the problem logs and / or usage records of the first device.

[0245] Optionally, the operating information of the first device includes the problem log of the first device. The transceiver module 1001 is also used to receive the root cause of the problem that caused the problem log of the first device from the first device; the display module 1002 is also used to display the root cause of the problem.

[0246] Optionally, the transceiver module 1001 is also used to send a first request to the first device, the first request being used to request the first device to send the operating information of the first device.

[0247] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0248] In this embodiment, the communication device 100 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above-mentioned functions.

[0249] for example, Figure 2 The processor 201 in the communication device 200 shown can execute the communication method in the above method embodiment by calling the computer execution instructions stored in the memory 203.

[0250] Specifically, Figure 10 The functions / implementation process of the transceiver module 1001 and the processing module 1002 can be obtained through... Figure 2 The processor 201 in the communication device 200 shown calls computer execution instructions stored in memory 203 to implement the function. Alternatively, Figure 10 The function / implementation process of the processing module 1002 can be achieved through... Figure 2 The processor 201 in the communication device 200 shown calls computer execution instructions stored in the memory 203 to implement the communication. Figure 10 The function / implementation process of the transceiver module 1001 can be obtained through Figure 2 This is achieved through the communication interface 204 in the communication device 200 shown. Figure 10 The function / implementation process of the display module 1003 can be achieved through... Figure 2 This is achieved through the output device 205 in the communication device 200 shown.

[0251] Since the communication device 100 provided in this embodiment can execute the communication method in the above method embodiment, the technical effects it can obtain can be referred to the above method embodiment, and will not be repeated here.

[0252] Optionally, embodiments of this application also provide a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. Optionally, the chip system may be composed of chips, or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0253] It should be noted that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC (System-on-a-Chip) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), PLDs (Programmable Logic Devices), or logic circuits that implement dedicated logic operations.

[0254] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0255] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0256] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0257] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method applied to a first device having a Near Field Communication (NFC) chip, characterized in that, The method includes: Obtain the operating information of the first device, which includes the problem log of the first device; wherein, the NFC chip of the first device has a first tag written into it, which is a debug device tag or a general device tag; The first device selects different methods for obtaining the root cause of the problem based on the network conditions of the first device. When the first device is disconnected from the network or the network status is poor, the first device itself analyzes the problem log of the first device to find the root cause of the problem log generated by the first device. When the network of the first device is good, the cloud server analyzes the problem log to find the root cause of the problem log generated by the first device and sends it to the first device. Establish communication with a second device having the NFC chip; When the first tag is a general device tag, the second device is authenticated. If the second device passes authentication, the root cause of the problem will be sent to the second device; When the first tag is a debugging device tag, the root cause of the problem is directly sent to the second device.

2. The method according to claim 1, characterized in that, Before receiving the root cause of the problem log that caused the first device from the cloud server, the method further includes: The problem log of the first device is sent to the cloud server, and the cloud server determines the root cause of the problem log generated by the first device.

3. The method according to claim 1 or 2, characterized in that, After establishing communication with the second device having the NFC chip and before sending the root cause of the problem to the second device, the method further includes: A first request is received from the second device, the first request being used to request the first device to send the root cause of the problem.

4. The method according to claim 1 or 2, characterized in that, After obtaining the operating information of the first device, the method further includes: Store the operating information of the first device.

5. The method according to claim 4, characterized in that, The method further includes: The stored operating information of the first device is deleted according to the management cycle, which is used to manage the operating information of the first device.

6. The method according to claim 1 or 2, characterized in that, The method further includes: The operating information of the first device is sent to the cloud server, and the cloud server stores the operating information of the first device.

7. A communication device, said communication device being applied to a first device having a near field communication (NFC) chip, characterized in that, The communication device includes: a transceiver module and a processing module; The processing module is used to obtain the operating information of the first device, which includes the problem log of the first device; wherein, a first tag is written into the NFC chip of the first device, and the first tag is a debugging device tag or a general device tag; The processing module is further configured to allow the first device to select different methods for obtaining the root cause of the problem based on the network conditions of the first device. When the first device is disconnected from the network or the network status is poor, the first device itself analyzes the problem log of the first device to find the root cause of the problem log generated by the first device. When the network of the first device is good, the cloud server analyzes the problem log to find the root cause of the problem log generated by the first device and sends it to the first device. The processing module is also used to establish communication with a second device having the NFC chip; The processing module is also used to authenticate the second device when the first tag is a general device tag; The transceiver module is configured to send the root cause of the problem to the second device if the second device passes the identity authentication. The transceiver module is also used to directly send the root cause of the problem to the second device when the first tag is debugging the device tag.

8. The communication device according to claim 7, characterized in that, The transceiver module is further configured to send the problem logs of the first device to the cloud server, whereby the cloud server determines the root cause of the problem logs generated by the first device.

9. The communication device according to claim 7 or 8, characterized in that, The transceiver module is further configured to receive a first request from the second device, the first request being used to request the first device to send the root cause of the problem.

10. The communication device according to claim 7 or 8, characterized in that, The communication device also includes a storage module; The storage module is used to store the operating information of the first device.

11. The communication device according to claim 10, characterized in that, The processing module is further configured to delete the stored operating information of the first device according to a management cycle, wherein the management cycle is used to manage the operating information of the first device.

12. The communication device according to claim 7 or 8, characterized in that, The transceiver module is also used to send the operating information of the first device to the cloud server, whereby the cloud server stores the operating information of the first device.

Images