CN117177228A

CN117177228A - Equipment registration method, system and equipment

Info

Publication number: CN117177228A
Application number: CN202210580299.7A
Authority: CN
Inventors: 刘勇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-05-25
Filing date: 2022-05-25
Publication date: 2023-12-05
Also published as: WO2023226881A1

Abstract

The embodiment of the invention provides a device registration method, a device registration system and a device. In the technical scheme provided by the embodiment of the invention, the method comprises the following steps: the method comprises the steps that a terminal device sends a first message to a first service device, and receives a response message sent by the first service device, wherein the response message carries an IP address and option information of the terminal device; and sending a device registration message to a device management server according to the IP address of the terminal device and the option information, so that the device management server performs connection and device management on the terminal device according to the registration message. The embodiment of the invention can realize rapid device registration across subnets between the terminal device and the device management server, and has lower cost.

Description

Equipment registration method, system and equipment

[ field of technology ]

The present invention relates to the field of computer technologies, and in particular, to a device registration method, system, and device.

[ background Art ]

In the industrial internet, it is common that terminal devices need to be managed on a device management server after deployment. The premise that the device management server can manage the terminal device is that the device management server can find that the terminal device has been deployed on the network, and acquire an internet protocol (Internet Protocol, IP) address and an access port number of the terminal device, so that the terminal device can be connected to perform management by using a management protocol. However, in the cross-two-layer network scenario, the delay for the device management server to discover the new terminal device increases, and the operation and maintenance costs are high.

[ invention ]

In view of this, the embodiments of the present invention provide a device registration method, system, and device, so that a fast device registration across subnets can be implemented between a terminal device and a device management server, and the cost is low.

In a first aspect, an embodiment of the present invention provides a device registration method, applied to a terminal device, where the method includes:

sending a first message to a first service device;

receiving a response message sent by the first service equipment, wherein the response message carries the IP address and option information of the terminal equipment;

and sending a device registration message to a device management server according to the IP address of the terminal device and the option information, so that the device management server performs connection and device management on the terminal device according to the registration message.

With reference to the first aspect, in some implementations of the first aspect, the sending a first packet to the first service device specifically includes:

and sending the first message to the first service equipment through the second service equipment.

With reference to the first aspect, in some implementation manners of the first aspect, the receiving a response packet sent by the first service device specifically includes:

And receiving the response message sent by the first service equipment through the second service equipment.

With reference to the first aspect, in some implementation manners of the first aspect, receiving a response message sent by the first service device, where the response message carries an IP address and option information of the terminal device, and the method includes:

receiving a first response message sent by the first service equipment, wherein the first response message carries the IP address of the terminal equipment and the option information;

sending a second message to the first service equipment;

and receiving a second response message sent by the first service equipment, wherein the second response message carries the IP address of the terminal equipment and the option information.

With reference to the first aspect, in certain implementation manners of the first aspect, the option information includes an options 43 option field.

With reference to the first aspect, in certain implementation manners of the first aspect, the options 43 option field includes: the device manages IP address and port information of the server.

In a second aspect, an embodiment of the present invention provides a device registration method, applied to a first service device, where the method includes:

receiving a first message sent by terminal equipment;

Generating a response message according to the first message, wherein the response message carries the IP address and option information of the terminal equipment;

and sending the response message to the terminal equipment so that the terminal equipment sends an equipment registration message to an equipment management server according to the IP address of the terminal equipment and the option information.

With reference to the second aspect, in some implementations of the second aspect, the receiving a first packet sent by a terminal device specifically includes:

and receiving the first message sent by the terminal equipment through the second service equipment.

With reference to the second aspect, in some implementations of the second aspect, the sending the response packet to the terminal device specifically includes:

and sending the response message to the terminal equipment through the second service equipment.

With reference to the second aspect, in some implementation manners of the second aspect, generating a response message according to the first message, where the response message carries an IP address and option information of the terminal device, includes:

generating a first response message according to the first message, wherein the first response message carries the IP address of the terminal equipment and the option information;

Receiving a second message sent by the terminal equipment;

and generating a second response message according to the second message, wherein the second response message carries the IP address of the terminal equipment and the option information.

With reference to the second aspect, in certain implementations of the second aspect, the option information includes an options 43 option field.

With reference to the second aspect, in some implementations of the second aspect, the options 43 option field includes: the device manages IP address and port information of the server.

In a third aspect, an embodiment of the present invention provides a device registration method, applied to a device management server, where the method includes:

receiving a device registration message sent by a terminal device;

connecting and managing the terminal equipment according to the equipment registration message;

the device registration message is triggered and generated after the terminal device receives a response message carrying the IP address and option information of the terminal device, which is sent by the first service device.

With reference to the third aspect, in some implementations of the third aspect, the option information includes an options 43 option field.

With reference to the third aspect, in some implementations of the third aspect, the options 43 option field includes: the device manages IP address and port information of the server.

In a fourth aspect, an embodiment of the present invention provides a device registration system, where the system includes a terminal device according to any one of the first aspect, a first service device according to any one of the second aspect, and a device management server according to any one of the third aspect.

With reference to the fourth aspect, in some implementations of the fourth aspect, the method further includes: and a second service device.

In a fifth aspect, an embodiment of the present invention provides a terminal device, comprising a processor and a memory, wherein the memory is configured to store a computer program, the computer program comprising program instructions which, when executed by the processor, cause the terminal device to perform the steps of the method according to any of the first aspects.

In a sixth aspect, an embodiment of the present invention provides a first service device, comprising a processor and a memory, wherein the memory is configured to store a computer program, the computer program comprising program instructions which, when executed by the processor, cause the first service device to perform the steps of the method according to any of the second aspects.

In a seventh aspect, an embodiment of the present invention provides a device management server, including a processor and a memory, where the memory is configured to store a computer program, the computer program including program instructions that, when executed by the processor, cause the device management server to perform the steps of the method according to any one of the third aspects.

In an eighth aspect, embodiments of the present invention provide a computer readable storage medium storing a computer program comprising program instructions which, when executed by a computer, cause the computer to perform a method as described above.

In the technical scheme of the device registration method, the system and the device provided by the embodiment of the invention, the method comprises the following steps: the method comprises the steps that a terminal device sends a first message to a first service device, and receives a response message sent by the first service device, wherein the response message carries an IP address and option information of the terminal device; and sending a device registration message to a device management server according to the IP address of the terminal device and the option information, so that the device management server performs connection and device management on the terminal device according to the registration message. The embodiment of the invention can realize rapid device registration across subnets between the terminal device and the device management server, and has lower cost.

[ description of the drawings ]

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present invention;

FIG. 2 is a block diagram of the software architecture of an electronic device 100 according to an embodiment of the invention;

FIG. 3 is a schematic diagram of device registration across a current two-tier network scenario;

fig. 4 is a schematic diagram of a device registration system according to an embodiment of the present invention;

FIG. 5 is a block diagram of a device registration system according to an embodiment of the present invention;

fig. 6 is a signaling interaction diagram of a device registration method according to an embodiment of the present invention;

fig. 7 is a signaling interaction diagram of another device registration method according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a first service device according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a device management server according to an embodiment of the present invention.

[ detailed description ] of the invention

For a better understanding of the technical solution of the present invention, the following detailed description of the embodiments of the present invention refers to the accompanying drawings.

It should be understood that the described embodiments are merely some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be understood that the term "and/or" as used herein is merely one way of describing an association of associated objects, meaning that there may be three relationships, e.g., a and/or b, which may represent: the first and second cases exist separately, and the first and second cases exist separately. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Fig. 1 shows a schematic configuration of an electronic device 100.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc., respectively, through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, such that the processor 110 communicates with the touch sensor 180K through an I2C bus interface to implement a touch function of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface, to implement a function of answering a call through the bluetooth headset.

PCM interfaces may also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface to implement a function of answering a call through the bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus for asynchronous communications. The bus may be a bi-directional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through a UART interface, to implement a function of playing music through a bluetooth headset.

The MIPI interface may be used to connect the processor 110 to peripheral devices such as a display 194, a camera 193, and the like. The MIPI interfaces include camera serial interfaces (camera serial interface, CSI), display serial interfaces (display serial interface, DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the photographing functions of electronic device 100. The processor 110 and the display 194 communicate via a DSI interface to implement the display functionality of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal or as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, an MIPI interface, etc.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transfer data between the electronic device 100 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices, etc.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and is not meant to limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also employ different interfacing manners in the above embodiments, or a combination of multiple interfacing manners.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 150 of electronic device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code including instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 100 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When electronic device 100 is answering a telephone call or voice message, voice may be received by placing receiver 170B in close proximity to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194.

The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device 100, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device 100 through the reverse motion, so as to realize anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, the electronic device 100 may range using the distance sensor 180F to achieve quick focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there is no object in the vicinity of the electronic device 100. The electronic device 100 can detect that the user holds the electronic device 100 close to the ear by using the proximity light sensor 180G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc.

The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the invention, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.

Fig. 2 is a software configuration block diagram of the electronic device 100 according to the embodiment of the present invention.

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The workflow of the electronic device 100 software and hardware is illustrated below in connection with capturing a photo scene.

When touch sensor 180K receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into the original input event (including information such as touch coordinates, time stamp of touch operation, etc.). The original input event is stored at the kernel layer. The application framework layer acquires an original input event from the kernel layer, and identifies a control corresponding to the input event. Taking the touch operation as a touch click operation, taking a control corresponding to the click operation as an example of a control of a camera application icon, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera driver by calling a kernel layer, and captures a still image or video by the camera 193.

At present, one mode of device registration is realized through an IP broadcast message, that is, a device management server periodically or manually triggers an IP broadcast message for sending a device discovery request to a network, and after receiving the IP broadcast message for the device discovery request, a terminal device on the network responds to the device management server with a response message, where the response message carries the IP address and port information of the terminal device. Thus, the terminal device performs device registration in the device management server, and the device management server can know the terminal device on the network and connect and manage the terminal device. The device management server discovers the terminal device by means of IP broadcasting messages, and the IP broadcasting is characterized by being only used in a two-layer broadcasting domain. For the scenario that the device management server and the terminal device to be managed are not in a two-layer network, communication between the device management server and the terminal device needs to cross one or more routers, so that the discovery of the terminal device by means of an IP broadcast message is not applicable. However, such a scenario that the device management server and the terminal device to be managed are not in a two-layer network is very common in practical applications.

For the scenario that the device management server and the terminal device to be managed are not in a two-layer network, the device registration is usually implemented by using a domain name server. The domain name server comprises a domain name resolution system server (Domain Name System, DNS). As shown in fig. 3, the device management server applies for the domain name of the device management server to the domain name service provider, for example, the domain name of the device management server is xx.com, and the IP of the device management server is 10.10.10.10. The domain name server provider performs domain name registration with the domain name server. The terminal device presets the domain name of the device management server, for example xx.com, before shipment. After the terminal equipment finishes deployment, the IP address of the terminal equipment is applied to the first service equipment. The first service device may be a separate dynamic host configuration protocol (Dynamic Host Configuration Protocol, DHCP) server (i.e., proprietary hardware+software implementing DHCP server functions), or a general purpose server+many software functions (one of which is a DHCP server function), or a network device with many functions (one of which is a DHCP server function), etc. The first service device assigns an IP address and a domain name server IP address to the terminal device. The terminal device applies for the IP address corresponding to the domain name of the resolution device management server, namely the IP address 10.10.10.10.10 corresponding to the domain name xx.com. The domain name server responds the IP address corresponding to the domain name of the equipment management server to the terminal equipment. The terminal equipment sends an equipment registration message of a unicast message to the equipment management server so as to register equipment, wherein the unicast message comprises an IP address of the terminal equipment. After the terminal equipment is registered by the equipment management server, the equipment management server connects and manages the equipment according to the service requirement through the IP address of the terminal equipment, such as system upgrade and the like.

In the industrial interconnection scenario, terminal devices, device management servers, first service devices and the like in an enterprise are generally deployed in an enterprise intranet, and are uniformly maintained by enterprise internet technology (Internet Technology, IT) personnel. If the device registration method shown in fig. 3 is adopted, the enterprise needs to separately deploy and maintain a domain name server in the intranet, which increases the operation and maintenance cost. Meanwhile, in the registration process of the terminal equipment, an additional domain name resolution process is also carried out, so that the time delay of the registration of the terminal equipment is increased.

In summary, in the cross-two-layer network scenario, the delay of the device management server for discovering the new terminal device increases, and the operation and maintenance costs are higher.

Based on the technical problems, the embodiment of the invention provides a device registration system. Fig. 4 is a schematic diagram of a device registration system according to an embodiment of the present invention.

As shown in fig. 4, the device registration system includes a terminal device 20, a first service device 30, and a device management server 40. The terminal device 20 is configured to send a first message to the first service device 30, where the first message includes a DHCPDISCOVER message. The first service device 30 is configured to generate a response message according to the first message, where the response message carries the IP address and option information of the terminal device 20, and send the response message to the terminal device 20. The response message comprises a first response message, and the first response message comprises a DHCPOFFER message. The terminal device 20 is further configured to send a second message to the first service device 30 after receiving the first response message, where the second message includes a DHCPDISCOVER message. The response message further includes a second response message including a DHCPACK message. The first service device 30 is specifically configured to generate a second response message according to the second message, and send the second response message to the terminal device 20. The second response message carries the IP address of the terminal device 20 and option information, where the option information includes an options43 option field, and the options43 option field includes: IP address and port information of the device management server 40. I.e. the terminal device 20 will acquire the IP address of the terminal device 20 from the first service device 30 at initial start-up. When the terminal device 20 is deployed in the enterprise network to acquire the IP address, when the first service device 30 allocates the IP to the terminal device 20, the response message carries the options43 field in addition to the information such as the normal IP address and mask of the terminal device 20. The terminal device 20 is further configured to parse the IP address of the terminal device 20, the IP address of the device management server 40, and the port information according to the response message, and generate a device registration message according to the IP address of the terminal device 20, the IP address of the device management server 40, and the port information. After receiving the response message sent by the first service device 30, the terminal device 20 needs to analyze options43 fields to obtain the IP address and port information of the device management server 40, in addition to analyzing the information such as the IP address and mask of the normal terminal device 20. The terminal device 20 is also configured to send a device registration message to the device management server 40 according to the option information. The device management server 40 performs connection and device management for the terminal device 20 according to the device registration message. Wherein, the device registration message is triggered and generated by the terminal device 20 after receiving a response message carrying the IP address and option information of the terminal device 20 sent by the first service device 30. After receiving the device registration message, the device management server 40 records device information (such as IP address, device type, etc.) of the terminal device 20, and then connects the terminal device based on the service requirement and performs operations such as device management.

The embodiment of the present invention configures the first service device 30, and its extension option capability (i.e., option 43 option field) is defined in the DHCP protocol, so that the first service device is used for enterprise custom messages, i.e., the enterprise can customize the fields and meanings as required. While most mainstream DHCP server systems are supported to configure this option. Meanwhile, after the terminal device 20 solves the content of the options field of the options 43 according to the DHCP protocol, the content is provided to the device discovery module for the terminal device 20 to register with the device management server 40. The enterprise manager configures on the first service device 30 such that the first service device 30 supports options 43 fields, such as: the options 43 field includes type=43, value= 0x0a0a0a0a 0x1000 (i.e., IP address of the device management server 40: 10.10.10.10, port information: 4096), length=6 (i.e., IP address 4 bytes+port information 2 bytes). It should be noted that, the format of the options 43 field is an example, and other formats with different definitions may be actually implemented.

For example, the terminal device 20 includes a host, a mobile phone, a tablet, a notebook, and the like. The first service device 30 may be a stand-alone DHCP server (i.e., proprietary hardware+software implementing DHCP server functions), a general-purpose server+many software functions (one of which is DHCP server functions), or a network device with many functions (one of which is DHCP server functions), etc. The first service device 30 may be deployed and configured on a certain router or switch within the enterprise.

The first service device 30 and the terminal device 20 are disposed in the same two-layer network, and the device management server 40 and the terminal device 20 may or may not be in the same two-layer network.

The embodiment of the invention multiplexes the existing equipment IP address allocation flow, and notifies the terminal equipment 20 of the IP address of the equipment management server 40 through the DHCP protocol expansion capability, so that the terminal equipment 20 can register equipment with the equipment management server 40 to finish equipment discovery, and no additional external system is needed in the whole equipment discovery process. The embodiment of the invention mainly uses lower cost in the enterprise intranet, so that automatic cross-subnet equipment discovery can be realized between the terminal equipment 20 and the equipment management server 40.

As shown in fig. 4, deploying one first service device 30 in each two-tier network increases the cost of network management and maintenance. Accordingly, an embodiment of the present invention provides a further device registration system, and fig. 5 is a schematic diagram of a further device registration system provided by an embodiment of the present invention.

As shown in fig. 5, the device registration system further includes: the second service device 50. The second service device 50 is wirelessly connected to the terminal device 20 and the first service device 30, respectively. The terminal device 20 is configured to send a first message to the first service device 30 through the second service device 50, where the first message includes a DHCPDISCOVER message. Specifically, the terminal device 20 is configured to send a first message to the second service device 50, and the second service device 50 is configured to send the first message to the first service device 30. The first service device 30 is configured to generate a response message according to the first message, and send the response message to the terminal device 20 through the second service device 50. The response message carries the IP address of the terminal device 20 and option information, where the option information includes an options 43 option field, and the options 43 option field includes: IP address and port information of the device management server 40. Specifically, the first service device 30 is configured to generate a response message according to the first message, where the response message carries the IP address and option information of the terminal device, and send the response message to the second service device 50; the second service device 50 is configured to send a response message to the terminal device 20. The response message comprises a first response message, and the first response message comprises a DHCPOFFER message. The terminal device 20 is further configured to send, after receiving the first response message, a second message to the first service device 30 through the second service device 50, where the second message includes a DHCPDISCOVER message. Specifically, the terminal device 20 is configured to send a second message to the second service device 50 after receiving the first response message; the second service device 50 is configured to send a second message to the first service device 30. The response message further includes a second response message including a DHCPACK message.

The first service device 30 is configured to generate a second response message according to the second message, and send the second response message to the terminal device 20 through the second service device 50, where the second response message carries the IP address and option information of the terminal device. Specifically, the first service device 30 is configured to generate a second response message according to the second message, and send the second response message to the second service device 50; the second service device 50 is configured to send a second response message to the terminal device 20. The terminal device 20 is also configured to send a device registration message to the device management server 40 according to the option information. The device management server 40 performs connection and device management for the terminal device 20 according to the device registration message. Wherein the device registration message is triggered and generated by the terminal device 20 after receiving a response message carrying option information sent by the first service device 30.

The second service device 50 is a software entity for the functions implemented by the protocol RFC 3046 (DHCP relay). The relevant protocol is RFC 3046DHCP Relay Agent Information Option. The DHCP partial message is a broadcast message, and typically the second service device 50 and the terminal device 20 are deployed in a local area network, such as a router of a home network. However, it is costly for the enterprise to deploy the first service device 30 per two-tier network, and the deployment and operation costs are high. Each two-layer network typically deploys an agent, i.e., a second service device 50, and forwards the broadcast message of the terminal device 20 to one of the second service devices 50 deployed in the enterprise set for IP address assignment.

Deployment of a first service device 30 within each two-tier network increases the cost of network management and maintenance. Thus, an enterprise typically deploys one second service device 50 (either deployed separately or integrated within a three-tier switch or router) within each two-tier network and then uniformly interfaces to one common first service device 30 within the enterprise to centrally perform network address allocation management.

In summary, in the embodiment of the present invention, the IP address and port information of the device management server 40 are carried in the DHCP protocol extension option, so that the terminal device 20 obtains the IP address and port information of the device management server 40, and completes device registration and automatic discovery; and the existing system and flow are expanded, the newly deployed DNS server is avoided, and the server deployment cost and the operation and maintenance cost of enterprises are saved.

Based on the device registration system shown in fig. 4, an embodiment of the present invention provides a device registration method, and fig. 6 is a signaling interaction diagram of the device registration method provided by the embodiment of the present invention. As shown in fig. 6, the method includes:

step 202, the terminal device sends a first message to the first service device.

In the embodiment of the present invention, the first message includes a DHCPDISCOVER message.

In the embodiment of the invention, when the terminal equipment is started initially, the IP address of the terminal equipment is acquired from the first service equipment.

For example, the terminal device includes a host, a mobile phone, a tablet, a notebook, and the like. The first service device may be a stand-alone DHCP server (i.e. proprietary hardware+software implementing DHCP server functions), or a general-purpose server+many software functions (one of which is DHCP server functions), or a network device with many functions (one of which is DHCP server functions), etc. The first service device may be deployed and configured on a certain router or switch within the enterprise.

The first service device and the terminal device are deployed in the same two-layer network, and the device management server and the terminal device may or may not be in the same two-layer network, i.e. cross the two-layer network.

Step 204, the first service device generates a first response message according to the first message, where the first response message carries the IP address and option information of the terminal device.

The first response message comprises a DHCPOFFER message, and the second response message comprises a DHCPACK message.

The option information includes an options43 option field, and the options43 option field includes: IP address and port information of the device management server 40. The embodiment of the invention configures the first service equipment, and the expansion option capability (namely option 43 option field) is defined in the DHCP standard protocol and is used for customizing the message by the enterprise, namely the enterprise can customize the field and the meaning according to the requirement. While most mainstream DHCP server systems are supported to configure this option. The enterprise manager configures on the first service device 30 such that the first service device 30 supports options43 fields, such as: the options43 field includes type=43, value= 0x0a0a0a0a 0x1000 (i.e., IP address of the device management server 40: 10.10.10.10, port information: 4096), length=6 (i.e., IP address 4 bytes+port information 2 bytes). It should be noted that, the format of the options43 field is an example, and other formats with different definitions may be actually implemented.

Step 206, the first service device sends the first response message to the terminal device.

Step 208, the terminal device sends the second message to the first service device.

The second message includes a DHCPDISCOVER message.

Step 210, the first service device generates a second response message according to the second message, where the second response message carries the IP address and option information of the terminal device.

The second response message includes a DHCPACK message.

When the terminal equipment is deployed in the enterprise network to acquire the IP address, the first service equipment carries an options43 field besides the normal IP address, mask and other information of the terminal equipment in the response message when the first service equipment distributes the IP to the terminal equipment.

Step 212, the first service device sends the second response message to the terminal device.

Step 214, the terminal device resolves the IP address of the terminal device, the IP address of the device management server, and the port information according to the response message, and generates a device registration message according to the IP address of the terminal device, the IP address of the device management server, and the port information. Meanwhile, after the terminal device 20 solves the content of the options field of the options43 according to the DHCP protocol, the content is provided to the device discovery module for the terminal device 20 to register with the device management server 40. The response message comprises a first response message and a second response message.

Step 216, the terminal device sends the device registration message to the device management server.

After receiving the response message sent by the first service device, the terminal device needs to analyze options 43 fields to obtain the IP address and port information of the device management server in addition to analyzing the information such as the IP address and mask of the normal terminal device. Then, the terminal device generates a device registration message according to the IP address of the terminal device, the IP address of the device management server, and the port information, and transmits the device registration message to the device management server.

Step 218, the device management server performs connection and device management on the terminal device according to the device registration message.

After receiving the device registration message, the device management server records the device information (such as IP address, device type, etc.) of the terminal device, and then connects the terminal device based on the service requirement and performs operations such as device management.

The embodiment of the invention multiplexes the existing equipment IP address allocation flow, and announces the IP address of the equipment management server to the terminal equipment through the DHCP protocol expansion capability, so that the terminal equipment can register equipment with the equipment management server to finish equipment discovery, and no additional external system is needed in the whole equipment discovery process. The embodiment of the invention mainly uses lower cost in the enterprise intranet, so that automatic cross-subnet equipment discovery can be realized between the terminal equipment and the equipment management server.

In the technical scheme of the device registration method provided by the embodiment of the invention, a terminal device sends a first message to a first service device, receives a response message sent by the first service device, and the response message carries option information; and sending a device registration message to a device management server according to the option information, so that the device management server connects and manages the terminal device according to the registration message. The embodiment of the invention can realize rapid device registration across subnets between the terminal device and the device management server, and has lower cost.

Based on the device registration system shown in fig. 5, an embodiment of the present invention provides a device registration method, and fig. 7 is a signaling interaction diagram of another device registration method provided by the embodiment of the present invention. As shown in fig. 7, the method includes:

step 302, the terminal device sends a first message to the second service device.

For example, the terminal device includes a host, a mobile phone, a tablet, a notebook, and the like. The first service device may be a stand-alone DHCP server (i.e. proprietary hardware+software implementing DHCP server functions), or a general-purpose server+many software functions (one of which is DHCP server functions), or a network device with many functions (one of which is DHCP server functions), etc. The first service device may be deployed and configured on a certain router or switch within the enterprise. Wherein the second service device is a software entity for a function implemented by the protocol RFC 3046 (DHCP relay). The relevant protocol is RFC 3046DHCP Relay Agent Information Option. The DHCP partial message is a broadcast message, and typically the second service device and the terminal device are deployed in a local area network, such as a router of a home network. However, for enterprises, deploying the first service device in each two-layer network is costly, and the deployment and operation costs are high. So, each two-layer network is generally deployed with one agent, namely a second service device, and the broadcast message of the terminal device is forwarded to one second service device deployed in the enterprise set for IP address allocation.

The second service device and the terminal device are deployed in the same two-layer network, and the device management server, the first service device and the terminal device are not in the same two-layer network, namely, a cross-layer network.

Step 304, the second service device sends a first message to the first service device.

Step 306, the first service device generates a first response message according to the first message, where the first response message carries the IP address and option information of the terminal device.

The option information includes an options 43 option field, and the options 43 option field includes: IP address and port information of the device management server 40. The embodiment of the invention configures the first service equipment, and the expansion option capability (namely option 43 option field) is defined in the DHCP standard protocol and is used for customizing the message by the enterprise, namely the enterprise can customize the field and the meaning according to the requirement. While most mainstream DHCP server systems are supported to configure this option. Meanwhile, after the terminal device 20 solves the content of the options field of the options 43 according to the DHCP protocol, the content is provided to the device discovery module for the terminal device 20 to register with the device management server 40. The enterprise manager configures on the first service device 30 such that the first service device 30 supports options 43 fields, such as: the options 43 field includes type=43, value= 0x0a0a0a0a 0x1000 (i.e., IP address of the device management server 40: 10.10.10.10, port information: 4096), length=6 (i.e., IP address 4 bytes+port information 2 bytes). It should be noted that, the format of the options 43 field is an example, and other formats with different definitions may be actually implemented.

Step 308, the first service device sends the first response message to the second service device.

Step 310, the second service device sends the first response message to the terminal device.

Step 312, the terminal device sends a second message to the second service device.

The second message includes a DHCPDISCOVER message.

Step 314, the second service device sends a second message to the first service device.

Step 316, the first service device generates a second response message according to the second message, where the second response message carries the IP address and option information of the terminal device.

The second response message includes a DHCPACK message.

When the terminal equipment is deployed in the enterprise network to acquire the IP address, the first service equipment carries an options43 field besides the normal IP address, mask and other information of the terminal equipment in the response message when the first service equipment distributes the IP to the terminal equipment. The response message comprises a first response message and a second response message.

Step 318, the first service device sends the second response message to the second service device.

Step 320, the second service device sends the second response message to the terminal device.

Step 322, the terminal device resolves the IP address of the terminal device, the IP address of the device management server, and the port information according to the response message, and generates a device registration message according to the IP address of the terminal device, the IP address of the device management server, and the port information.

The response message comprises a first response message and a second response message.

After receiving the response message sent by the first service device, the terminal device needs to analyze options 43 fields to obtain the IP address and port information of the device management server in addition to analyzing the information such as the IP address and mask of the normal terminal device. Then, the terminal device generates a device registration message according to the IP address of the terminal device, the IP address of the device management server, and the port information.

Step 324, the terminal device sends the device registration message to the device management server.

And 326, the device management server performs connection and device management on the terminal device according to the device registration message.

Deployment of a first service device within each two-tier network increases the cost of network management and maintenance. Thus, an enterprise typically deploys a second service device (either deployed separately or integrated within a three-tier switch or router) within each two-tier network and then uniformly interfaces to a common first service device within the enterprise, thereby centrally performing network address allocation management.

In the technical scheme of the device registration method provided by the embodiment of the invention, a terminal device sends a first message to a first service device through a second service device, and the second service device receives a response message sent by the first service device, wherein the response message carries option information; and sending a device registration message to a device management server according to the option information, so that the device management server connects and manages the terminal device according to the registration message. The embodiment of the invention can realize rapid device registration across subnets between the terminal device and the device management server, and has lower cost.

Fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present invention, and it should be understood that the terminal device 400 is capable of executing the steps of the terminal device in the device registration method described above, and will not be described in detail herein to avoid repetition. The terminal device 400 includes: a first transceiver unit 401.

The first transceiver 401 is configured to send a first message to a first service device; receiving a response message sent by the first service equipment, wherein the response message carries the IP address and option information of the terminal equipment; and sending a device registration message to a device management server according to the IP address of the terminal device and the option information, so that the device management server performs connection and device management on the terminal device according to the registration message.

Optionally, the first transceiver unit 401 is specifically configured to send the first packet to the first service device through the second service device.

Optionally, the first transceiver unit 401 is specifically configured to receive, by using the second service device, the response message sent by the first service device.

Optionally, the first transceiver unit 401 is specifically configured to receive a first response packet sent by the first service device, where the first response packet carries an IP address of the terminal device and the option information; sending a second message to the first service equipment; and receiving a second response message sent by the first service equipment, wherein the second response message carries the IP address of the terminal equipment and the option information.

Optionally, the option information includes an options 43 option field.

Optionally, the options 43 option field includes: the device manages IP address and port information of the server.

Fig. 9 is a schematic structural diagram of a first service device according to an embodiment of the present invention, and it should be understood that the first service device 500 is capable of performing the steps of the first service device in the device registration method described above, and in order to avoid repetition, details are not described herein. The first service apparatus 500 includes: a second transceiver unit 501 and a first processing unit 502.

The second transceiver 501 is configured to receive a first message sent by a terminal device.

The first processing unit 502 is configured to generate a response message according to the first message, where the response message carries the IP address and option information of the terminal device.

The second transceiver unit 501 is further configured to send the response message to the terminal device, so that the terminal device sends a device registration message to a device management server according to the option information.

Optionally, the second transceiver 501 is specifically configured to receive, through the second service device, the first message sent by the terminal device.

Optionally, the second transceiver unit 501 is specifically configured to send the response message to the terminal device through the second service device.

Optionally, the first processing unit 502 is specifically configured to generate a first response message according to the first message, where the first response message carries an IP address of the terminal device and the option information; the second transceiver 501 is further configured to receive a second packet sent by the terminal device; the first processing unit 502 is further specifically configured to generate a second response message according to the second message, where the second response message carries the IP address of the terminal device and the option information.

Optionally, the option information includes an options 43 option field.

Fig. 10 is a schematic structural diagram of a device management server according to an embodiment of the present invention, and it should be understood that the device management server 600 is capable of executing the steps of the device management server in the above device registration method, and will not be described in detail herein to avoid repetition. The device management server 600 includes: a third transceiver unit 601 and a second processing unit 602.

The third transceiver 601 is configured to receive a device registration message sent by a terminal device.

The second processing unit 602 is configured to connect and manage devices of the terminal device according to the device registration message.

Optionally, the option information includes an options 43 option field.

It should be understood that the terminal device 400 and the first service device 500 and the device management server 600 herein are embodied in the form of functional units. The term "unit" herein may be implemented in software and/or hardware, without specific limitation. For example, a "unit" may be a software program, a hardware circuit or a combination of both that implements the functions described above. The hardware circuitry may include application specific integrated circuits (application specific integrated circuit, ASICs), electronic circuits, processors (e.g., shared, proprietary, or group processors, etc.) and memory for executing one or more software or firmware programs, merged logic circuits, and/or other suitable components that support the described functions.

Thus, the elements of the examples described in the embodiments of the present invention can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The embodiment of the application provides electronic equipment which can be terminal equipment or circuit equipment built in the terminal equipment. The electronic device may be adapted to perform the functions/steps of the method embodiments described above.

Embodiments of the present application provide a computer readable storage medium having instructions stored therein which, when executed on a terminal device, cause the terminal device to perform the functions/steps as in the method embodiments described above.

Embodiments of the present application also provide a computer program product comprising instructions which, when run on a computer or any of the at least one processor, cause the computer to perform the functions/steps as in the method embodiments described above.

In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relation of association objects, and indicates that there may be three kinds of relations, for example, a and/or B, and may indicate that a alone exists, a and B together, and B alone exists. Wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of the following" and the like means any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

Those of ordinary skill in the art will appreciate that the various elements and algorithm steps described in the embodiments disclosed herein can be implemented as a combination of electronic hardware, computer software, and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In several embodiments provided by the present application, any of the functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing an electronic device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely exemplary embodiments of the present application, and any person skilled in the art may easily conceive of changes or substitutions within the technical scope of the present application, which should be covered by the present application. The protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A device registration method, applied to a terminal device, the method comprising:

sending a first message to a first service device;

2. The method of claim 1, wherein the sending the first message to the first service device specifically includes:

3. The method of claim 2, wherein the receiving the response message sent by the first service device specifically includes:

4. The method of claim 1, wherein receiving a response message sent by the first service device, where the response message carries the IP address and option information of the terminal device, includes:

sending a second message to the first service equipment;

5. The method of any of claims 1-4, wherein the option information comprises an options 43 option field.

6. The method of claim 5, wherein the options 43 option field comprises: the device manages IP address and port information of the server.

7. A device registration method, applied to a first service device, the method comprising:

receiving a first message sent by terminal equipment;

8. The method of claim 7, wherein the receiving the first message sent by the terminal device specifically includes:

9. The method of claim 8, wherein the sending the response message to the terminal device specifically includes:

10. The method of claim 7, wherein generating a response message according to the first message, the response message carrying the IP address and option information of the terminal device, comprises:

receiving a second message sent by the terminal equipment;

11. The method of any of claims 7-10, wherein the option information comprises an options 43 option field.

12. The method of claim 11, wherein the options 43 option field comprises: the device manages IP address and port information of the server.

13. A device registration method, applied to a device management server, comprising:

receiving a device registration message sent by a terminal device;

14. The method of claim 13, wherein the option information comprises an options 43 option field.

15. The method of claim 14, wherein the options 43 option field comprises: the device manages IP address and port information of the server.

16. A device registration system, characterized in that the system comprises a terminal device according to any of claims 1-6, a first service device according to any of claims 7-12 and a device management server according to any of claims 13-15.

17. The system of claim 16, further comprising: and a second service device.

18. A terminal device comprising a processor and a memory, wherein the memory is for storing a computer program comprising program instructions which, when executed by the processor, cause the terminal device to carry out the steps of the method according to any one of claims 1-6.

19. A first service device comprising a processor and a memory, wherein the memory is for storing a computer program comprising program instructions which, when executed by the processor, cause the first service device to perform the steps of the method according to any of claims 7-12.

20. A device management server comprising a processor and a memory, wherein the memory is for storing a computer program comprising program instructions that, when executed by the processor, cause the device management server to perform the steps of the method of any of claims 13-15.

21. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program comprising program instructions which, when executed by a computer, cause the computer to perform the method of any of claims 1-15.