Equipment management method of calling system, calling system, equipment and storage medium

Abstract

The embodiment of the invention provides an equipment management method of a calling system, the calling system, equipment and a storage medium, and belongs to the technical field of medical treatment. The method comprises the following steps: acquiring pre-recorded and stored network information summarized data and bed information summarized data; obtaining a two-dimensional code of a calling device to be initialized; binding the target network information of the two-dimensional code with the target bed information of the bed corresponding to the calling device; and after the target network information of each calling device is bound with the corresponding target bed information, broadcasting the target network information of the calling device to be initialized through a preset transmission protocol so as to carry out network initialization on each calling device. According to the embodiment of the invention, automatic initialization of the calling equipment can be realized, and the difficulty of initializing the calling equipment in a calling system can be reduced.

Description

Technical Field

[0001] The present application relates to the field of medical technology, and in particular to a device management method for a call system, a call system, a device and a storage medium. Background Art

[0002] With the development of the Internet of Things, hospitals, nursing homes and other care facilities will all have real-time call systems. The real-time call system sets up call devices near each bed to help patients quickly and conveniently contact caregivers through the call devices. However, there are often hundreds or thousands of call devices in a real-time call system. After deployment, the call system often needs to be initialized on the network before it can operate normally. In related technologies, when initializing the call system, it is usually handled manually by the deployment personnel. However, the manual processing method will make the deployment process more time-consuming and prone to initialization errors during the deployment process. Therefore, how to reduce the difficulty of initializing the call device in the call system is a technical problem that needs to be solved urgently. Summary of the invention

[0003] The main purpose of the embodiments of the present application is to propose a device management method, a call system, a device and a storage medium for a call system, aiming to reduce the difficulty of initializing a call device in the call system.

[0004] To achieve the above-mentioned purpose, a first aspect of an embodiment of the present application proposes a device management method for a call system, which is applied to a management terminal; the method comprises: Obtaining the pre-entered and stored network information summary data and bed information summary data; Obtaining a QR code of a calling device to be initialized, wherein each calling device corresponds to a bed setting; Binding the target network information of the QR code and the target bed information of the bed corresponding to the calling device; wherein the target network information is one of the pre-entered and stored network information summary data; and the target bed information is one of the pre-entered and stored bed information summary data; After the target network information of each of the calling devices is bound to the corresponding target bed information, the target network information of the calling device to be initialized is broadcasted through a preset transmission protocol to perform network initialization on each of the calling devices.

[0005] In some embodiments, the binding of the network information summary data corresponding to the QR code and the bed information summary data of the bed corresponding to the calling device includes: Extracting a target device identifier from the QR code; Matching the target device identifier with the pre-entered and stored network information summary data to obtain target network information; Obtaining a bed identifier of a bed corresponding to the calling device; Acquiring target bed information, wherein the target bed information is selected from pre-entered and stored bed information summary data that matches the bed identifier; The target network information and the target bed information are bound.

[0006] In some embodiments, broadcasting the target network information of the calling device to be initialized through a preset transmission protocol includes: Obtaining the single packet length of the transmission protocol; According to the single packet length, the target network information is packetized to obtain a plurality of data sub-packets of each of the calling devices to be initialized, wherein each of the data sub-packets carries a device identification of the calling device to be initialized; Each of the data sub-packets is broadcasted via the transmission protocol.

[0007] In some embodiments, the target network information includes terminal address information, mask information, gateway information, server information and domain name information; the multiple data sub-packets of the calling device to be initialized are obtained by the following steps: including: Obtaining the device identifier, terminal address identifier, mask identifier, gateway identifier, server identifier and domain name identifier of the calling device to be initialized; Encapsulate the device identifier, the terminal address identifier and the terminal address information to obtain an address data sub-packet; Encapsulating the device identifier, the mask identifier and the mask information to obtain a mask data sub-packet; Encapsulate the device identifier, the gateway identifier and the gateway information to obtain a gateway data sub-packet; Encapsulate the device identifier, the server identifier and the server information to obtain a server data sub-packet; The device identifier, the domain name identifier and the domain name information are encapsulated to obtain a domain name data sub-packet.

[0008] In some embodiments, broadcasting each of the data sub-packets through the transmission protocol includes: cyclically broadcasting each of the data sub-packets through the transmission protocol; When all data sub-packets of one of the device identifications are successfully received, the broadcasting of the successfully received data sub-packets of the calling device is stopped.

[0009] To achieve the above-mentioned purpose, a second aspect of an embodiment of the present application proposes a device management method of a call system, which is applied to a call device, and the method includes: In the case of uninitialized, after booting up, the QR code display page is entered and the QR code is displayed; Receive target network information broadcasted from the management terminal and perform network initialization according to the target network information, wherein the target network information is obtained by the method described in the first aspect.

[0010] In some embodiments, each of the target network information is encapsulated into a plurality of data sub-packets and sent via the transmission protocol, and the method further includes: Extracting a target device identifier, a target sub-packet type, and target network segmentation information from each of the received data sub-packets; When the extracted target device identifier matches the device identifier configured by itself, a data packet receiving step is performed on the data sub-packet; The data packet receiving step comprises: According to the target sub-packet type, updating the network segmentation information matching the sub-packet type in the preset cache to the target network segmentation information; When the network segmentation information corresponding to each sub-packet type in the preset data packet type list is cached in the cache, indication information is sent to the management terminal to indicate that the target network information has been received.

[0011] To achieve the above objective, a third aspect of an embodiment of the present application provides a calling system, the calling system comprising: A plurality of calling devices, each of which executes the device management method of the calling system as described in the second aspect; A management terminal, wherein the management terminal executes the device management method of the call system according to the first aspect of claim 1.

[0012] To achieve the above-mentioned purpose, the fourth aspect of an embodiment of the present application proposes an electronic device, which includes a memory and a processor, the memory stores a computer program, and the processor implements the method described in the first aspect and / or the second aspect when executing the computer program.

[0013] To achieve the above objectives, the fifth aspect of an embodiment of the present application proposes a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the method described in the first aspect and / or the second aspect.

[0014] The above-mentioned embodiment of the present application, by pre-entering and storing the network information summary data and the bed information summary data in the management terminal, and scanning the QR code of the calling device one by one, and then determining the target network information that each calling device needs to configure through the QR code and binding it with the target bed information of the bed corresponding to the calling device. At this time, when broadcasting the target network information, each calling device can select its own target network information for configuration according to its own device identification, and the operation method is simpler and less prone to errors. Therefore, compared with the related art, the embodiment of the present application can reduce the difficulty of initializing the calling device in the calling system. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a flowchart of a device management method for a call system of a management terminal provided by an embodiment of the present application; Figure 2 is a flow chart of a device management method for a calling system applied to a calling device provided by an embodiment of the present application; Figure 3 It is a business processing flow diagram of an embodiment of a device management method for a call system provided by an embodiment of the present application; Figure 4 A logical diagram of target network information transmission in a device management method of a call system provided in an embodiment of the present application; Figure 5 A schematic diagram of the structure of an embodiment of a call system provided in an embodiment of the present application; Figure 6 It is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0016] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0017] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0018] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0019] With the development of the Internet of Things, hospitals, nursing homes and other nursing places will all have real-time call systems. The real-time call system sets up call devices in the vicinity of each bed to help patients quickly and conveniently contact caregivers through the call devices. However, a real-time call system often has hundreds or thousands of call devices. After deployment, the call system often needs to be initialized on the network before it can operate normally. In related technologies, when initializing the call system, it is usually handled manually by the deployment personnel. However, the manual processing method will make the deployment process more time-consuming and prone to initialization errors during the deployment process. Therefore, how to reduce the difficulty of initializing the call device in the call system is a technical problem that needs to be solved urgently. Based on this, the embodiments of the present application provide a device management method, a call system, a device and a storage medium for a call system, aiming to reduce the difficulty of initializing the call device in the call system.

[0020] The device management method of the call system, the call system, the electronic device and the storage medium provided in the embodiments of the present application are specifically illustrated through the following embodiments. First, the device management method of the call system in the embodiments of the present application is described.

[0021] The device management method of the call system provided in the embodiment of the present application relates to the field of medical technology. In the embodiment of the present application, the management terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.; the management terminal can be configured with a server, and the server side can be configured as an independent physical server, or a server cluster or distributed system composed of multiple physical servers, and can also be configured as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the device management method is software applied to the management terminal, and the software can be an application that implements the device management method of the call system, etc., but is not limited to the above forms.

[0022] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0023] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0024] Figure 1 is an optional flowchart of the device management method of the call system provided in the embodiment of the present application. Figure 1 The method may include but is not limited to steps S101 to S106. Figure 1 As shown, according to an embodiment of the present application, a device management method for a call system of a management terminal is applied, and the method includes: Step S101, obtaining the network information summary data and bed information summary data that are pre-entered and stored; Step S102: obtaining a QR code of a calling device to be initialized, wherein each calling device corresponds to a bed setting; Step S103, binding the target network information of the QR code and the target bed information of the bed corresponding to the calling device; wherein the target network information is one of the network information summary data pre-entered and stored; and the target bed information is one of the bed information summary data pre-entered and stored; Step S104: After the target network information of each calling device is bound to the corresponding target bed information, the target network information of the calling device to be initialized is broadcast through a preset transmission protocol to perform network initialization on each calling device.

[0025] Therefore, by pre-entering and storing the network information summary data and the bed information summary data in the management terminal, and scanning the QR code of the calling devices one by one, the target network information that needs to be configured for each calling device is determined through the QR code and bound to the target bed information of the bed corresponding to the calling device. At this time, when broadcasting the target network information, each calling device can select its own target network information for configuration according to its own device identification, and the operation method is simpler and less prone to errors. Therefore, compared with the related art, the embodiment of the present application can reduce the difficulty of initializing the calling device in the calling system.

[0026] The network information summary data records the network information of each calling device in the calling system, and the network information records the device identification of the calling device and the network information required for network initialization. The bed information summary data records the management information of each bed in the calling system, including but not limited to the bed identification, and in other embodiments, also includes the bed location information. In this regard, those skilled in the art can selectively set according to actual needs.

[0027] It is understandable that the QR code of the calling device is obtained by scanning. The QR code can extract the device identification, so the target network information can be uniquely determined from the network information summary data based on the device identification.

[0028] The binding method in step S103 can be to obtain the target network information through the QR code, and then select the target bed information from the bed information summary data displayed in the view interface of the management terminal for binding. It can also be achieved by scanning the QR code of the calling device after entering the binding interface of the corresponding bed. In this regard, the embodiment of the present application does not limit the operation method of the management terminal for binding, and those skilled in the art can selectively set it according to actual needs.

[0029] For step S104, when broadcasting, the target network information of multiple uninitialized calling devices in the calling system may be sent in a loop at the same time until the target network information corresponding to each calling device feedback has been received. If limited by the signal coverage of the management terminal, the calling device can be divided into multiple areas, and the calling device in each area is the calling device to be initialized. The target network information of the calling device in each area is sent in a loop, and when the initialization of the calling device in one area is completed, the initialization of the next area is performed. It can also be that each bound calling device is sent in a loop until the calling device is completed. If there are 1,000 calling devices in the calling device, step S103 can be executed for all 1,000 calling devices, and then step S104 can be executed separately. Step S104 can also be executed immediately after each calling device is bound.

[0030] The transmission protocol in step S104 is a communication protocol that supports broadcasting. For example, the management terminal and the calling device can transmit target network information via the Bluetooth protocol, thereby realizing automatic initialization of multiple calling devices.

[0031] In some embodiments, the transmission protocol is Bluetooth transmission. In this case, only one calling device can be transmitted at a time. At the time of initialization, connections are established with the calling devices within the coverage of the Bluetooth signal in sequence, and network information is transmitted to each connected calling device. In other embodiments, multiple calling devices can be supported to establish communication links at the same time, and data packets corresponding to the network information of multiple connected calling devices can be sent cyclically.

[0032] It is understandable that the network information summary data corresponding to the QR code and the bed information summary data of the bed corresponding to the calling device are bound, including: Extract the target device ID from the QR code; Match the target device identification with the pre-entered and stored network information summary data to obtain the target network information; Get the bed ID of the bed corresponding to the calling device; Obtaining target bed information; wherein the target bed information is selected from the pre-entered and stored bed information summary data and the bed information matching the bed identification; Bind the target network information and target bed information.

[0033] It is understandable that binding can record network information and target bed information by creating a new record.

[0034] The target network information includes the target device identification. The target bed information includes the bed identification. The target device identification can uniquely identify a set of network configuration information, such as a set of network configuration information IP address, gateway, etc. The bed identification can uniquely identify the information of a bed.

[0035] It is understandable that the target network information of the calling device to be initialized is broadcasted through a preset transmission protocol, including: Get the single packet length of the transmission protocol; According to the single packet length, the target network information is divided into data packets to obtain multiple data sub-packets of each calling device to be initialized, wherein each data sub-packet carries the device identification of the calling device to be initialized; Each data sub-packet is broadcasted via a transport protocol.

[0036] It is understandable that the length of a single data packet of each transmission protocol is limited. Therefore, dividing the target network information into multiple data sub-packets and sending each data sub-packet includes a device identification, which can ensure that when broadcasting to multiple calling devices at the same time, each calling device can normally receive the complete target network information.

[0037] It is understandable that the target network information includes terminal address information, mask information, gateway information, server information and domain name information; multiple data sub-packets of the calling device to be initialized are obtained through the following steps: including: Obtaining the device identifier, terminal address identifier, mask identifier, gateway identifier, server identifier, and domain name identifier of the calling device to be initialized; Encapsulate the device identification, terminal address identification and terminal address information to obtain an address data sub-packet; Encapsulate the device identifier, mask identifier and mask information to obtain a mask data sub-packet; Encapsulate the device identification, gateway identification and gateway information to obtain a gateway data sub-packet; Encapsulate the device identifier, server identifier and server information to obtain a server data sub-packet; The device identifier, domain name identifier and domain name information are encapsulated to obtain a domain name data sub-package.

[0038] It is understandable that each data sub-packet is broadcasted via a transport protocol, including: Each data sub-packet is broadcasted cyclically through a transmission protocol; When the data sub-packets identified by one of the devices are successfully received, the broadcasting of the data sub-packets of the calling device that are successfully received will be stopped.

[0039] By separately encapsulating different types of data in the target network information to form data sub-packets, the difficulty of parsing can be reduced. By setting corresponding identifiers for different types of data, it can be ensured that the calling device can determine whether to accept the completion, thereby enabling the management terminal to automatically initialize the calling device and further reduce the probability of human participation.

[0040] Stopping the broadcast of the data sub-packets of the successfully received paging device can improve the initialization efficiency of the remaining initialized paging devices.

[0041] Reference Figure 2 As shown, refer to Figure 2 As shown, according to an embodiment of the present application, a device management method for a calling system applied to a calling device includes: Step S201: In the case of no initialization, after booting up, enter the QR code display page and display the QR code; Step S202: Receive target network information broadcasted from the management terminal and perform network initialization according to the target network information, wherein the target network information is obtained by the method of the first aspect.

[0042] By pre-entering and storing the network information summary data and the bed information summary data in the management terminal, and scanning the QR code of the calling devices one by one, the target network information that needs to be configured for each calling device is determined through the QR code and bound to the target bed information of the bed corresponding to the calling device. At this time, when broadcasting the target network information, each calling device can select its own target network information for configuration according to its own device identification, and the operation method is simpler and less prone to errors. Therefore, compared with the related art, the embodiment of the present application can reduce the difficulty of initializing the calling device in the calling system.

[0043] By directly turning on the device and displaying the QR code page without initialization, it is easy to identify the uninitialized device, and there is no restriction on the installation location of the calling device. For example, the QR code can be quickly and conveniently obtained when it is hung on the wall. And by viewing the interface of the calling device, you can quickly identify whether the initialization is completed.

[0044] After the calling device is initialized, the QR code display page will no longer be displayed automatically. The user needs to operate the calling device to display the QR code before it can be displayed.

[0045] The QR code is generated based on the device ID of the calling device.

[0046] It is understandable that each target network information is encapsulated into multiple data sub-packets and sent through a transmission protocol. The method further includes: Extracting target device identification, target sub-packet type and target network segmentation information from each received data sub-packet; When the extracted target device identifier matches the self-configured device identifier, a data packet receiving step is performed on the data sub-packet; The steps of receiving data packets include: According to the target sub-packet type, the network segmentation information matching the sub-packet type in the preset cache is updated to the target network segmentation information; When the network segmentation information corresponding to each sub-packet type in the preset data packet type list is cached in the cache, an indication message is sent to the management terminal to indicate that the target network information has been received.

[0047] By introducing the judgment of the target device identification, it can be ensured that the network information required for initialization is consistent with the pre-configuration, reducing the probability of network conflicts during the network configuration process.

[0048] The target sub-packet type is used to characterize the type of the target network segmentation information. According to the target sub-packet type, it can be identified whether the target network information is received completely.

[0049] The embodiment of the present application does not limit the type of cache. The indication information is used to make the management terminal stop receiving the call device transmitter data sub-packet that has been received.

[0050] For example, it is assumed that there are calling devices A, B and C that need to be initialized, the target network information of calling device A is information 1, the target network information of calling device B is information 2; the target network information of calling device C is information 3, and the target network information is information 1, the target network information is information 2 and the target network information is information 3, which are respectively encapsulated into data sub-packets 1 to 9. Then, for calling device A, when it receives data sub-packets 1 to 9, it will match the target device identifiers in data sub-packets 1 to 9 respectively. When the target device identifiers in data sub-packets 4, 5 and 6 are consistent with the device identifier of calling device A, the data packet receiving step is performed on data sub-packets 4, 5 and 6 respectively. For data sub-packet 4, the target network segmentation information in data sub-packet 3 is directly overwritten with the existing received one. When the target network segmentation information in data sub-packets 4, 5 and 6 has been recorded in the cache, indicating that the reception has been completed, an indication message will be sent to the management terminal. Correspondingly, after receiving the indication message, the management terminal will stop sending data sub-packets 4, 5 and 6.

[0051] For example, refer to Figure 3 and Figure 4The method of describing the embodiment of the present application is as follows: In the calling system, each calling device generates a QR code based on the unique device ID (i.e., device identification) on the initialization page and starts searching for Bluetooth broadcasts. The QR code of the calling device is scanned separately at the management terminal, and the network information of the calling device and the bed information are associated. The management terminal sends the corresponding network information of the calling device via Bluetooth broadcast. After the calling device receives the corresponding network information, the initial action is completed. The specific implementation steps are as follows: S1. Enter the initialization information of all devices into a table; wherein the initialization information includes network information summary data and bed information summary data.

[0052] S2, packetizing the network information of each calling device according to the data packet format of the broadcast data protocol; S3. The sub-packets of the sub-packets are broadcasted cyclically to enable each calling device to complete initialization.

[0053] Wherein, step S1 is specifically as follows: The unique ID of each calling device is matched with the network information (IP, subnet mask, gateway, DNS, server IP, server port) one by one and saved in the network information summary table.

[0054] Save the bed information provided by the hospital to the bed information summary.

[0055] Wherein, step S2 is specifically as follows: Since the data sent by Bluetooth broadcasting at one time is limited, when sending multiple data, the data needs to be divided into packets and sent out multiple times. In order to implement packet sending, the protocol data format of each data sub-packet is defined as follows:

[0056] Among them, ID represents the unique ID of the device; type represents the type of data; data represents the corresponding data value; for example, network information includes: ip, subnet mask, gateway, DNS, server ip, server port. Then the initialization information is identified as follows: 0: represents ip, 1: subnet mask, 2: gateway, 3: DNS, 4: server ip, 5: server port. That is, the terminal address identifier is set to 0; the mask identifier is set to 1; the gateway identifier is set to 2; there are two server identifiers, which are set to 4 and 5 respectively; the domain name identifier is set to 3. The corresponding data sub-packets are as follows: Address data sub-packet: device ID + 0 + ip; Mask data sub-packet: device ID + 1 + subnet mask; Gateway data sub-packet: device ID + 2 + gateway; Domain name data sub-packet: device ID + 3 + DNS; Server data sub-packet 1: device ID + 4 + server IP; Server data sub-packet 2: device ID + 5 + server port.

[0057] Wherein, step S3 is specifically as follows: Reference Figure 4 As shown, since the management terminal uses Bluetooth protocol broadcasting, it can only establish a connection with the calling device within the Bluetooth signal range at a time. Therefore, each data sub-packet of the calling device to establish a connection will be broadcast and sent in sequence in a loop until all the calling devices prompt that the data has been received successfully. Then the sending will be stopped and the connection will be re-established with the uninitialized calling devices within the signal range and initialized.

[0058] When the management terminal can establish communication connections with multiple calling devices at the same time, the data sub-packets of the multiple calling devices will be sent cyclically. When a calling device prompts that the data is received successfully, the sending of the data sub-packets of the calling device will be stopped, and the cyclic sending of the data sub-packets of the remaining calling devices that have not prompted success will continue.

[0059] It is understandable that, since automatic initialization can be achieved after the network information and bed information are bound, automatic initialization of batch calling devices can be achieved by setting scripts, thereby further improving the convenience of initialization.

[0060] To achieve the above-mentioned purpose, a third aspect of an embodiment of the present application proposes a calling system, the calling system comprising: A plurality of calling devices, each calling device executes the device management method of the calling system according to the second aspect; A management terminal, wherein the management terminal executes the device management method of the call system according to the first aspect of claim 1.

[0061] See also Figure 5 The embodiment of the present application further provides a calling system, which can implement the device management method of the calling system, and the calling system includes: A plurality of calling devices 100, each calling device 100 executes the device management method of the calling system applied to the calling device 100; The management terminal 200 executes the device management method of the calling system applied to the management terminal 200 as described above.

[0062] The specific implementation of the calling system is basically the same as the specific implementation of the device management method of the calling system mentioned above, and will not be repeated here.

[0063] The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the device management method of the above-mentioned call system when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a car computer, etc.

[0064] See also Figure 6 , Figure 6 The hardware structure of an electronic device of another embodiment is illustrated, and the electronic device includes: The processor 601 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application; The memory 602 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 602 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 602, and the processor 601 calls and executes the device management method of the call system in the embodiment of this application; Input / output interface 603, used to implement information input and output; Communication interface 604, used to realize communication interaction between the device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.); A bus 605 that transmits information between various components of the device (e.g., processor 601, memory 602, input / output interface 603, and communication interface 604); The processor 601 , the memory 602 , the input / output interface 603 and the communication interface 604 are connected to each other in communication within the device via a bus 605 .

[0065] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the device management method of the above-mentioned call system is implemented.

[0066] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0067] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0068] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0069] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0070] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0071] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0072] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0073] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0074] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0075] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0076] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes multiple instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store programs.

[0077] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A device management method for a call system, characterized in that: Applied to a management terminal; the method comprises: Obtaining the pre-entered and stored network information summary data and bed information summary data; Obtaining a QR code of a calling device to be initialized, wherein each calling device corresponds to a bed setting; Binding the target network information of the QR code and the target bed information of the bed corresponding to the calling device; wherein the target network information is one of the pre-entered and stored network information summary data; and the target bed information is one of the pre-entered and stored bed information summary data; After the target network information of each of the calling devices is bound to the corresponding target bed information, the target network information of the calling device to be initialized is broadcasted through a preset transmission protocol to perform network initialization on each of the calling devices.

2. The device management method of the call system according to claim 1, characterized in that: The step of binding the network information summary data corresponding to the QR code and the bed information summary data of the bed corresponding to the calling device includes: Extracting a target device identifier from the QR code; Matching the target device identifier with the pre-entered and stored network information summary data to obtain target network information; Obtaining a bed identifier of a bed corresponding to the calling device; Acquiring target bed information, wherein the target bed information is selected from pre-entered and stored bed information summary data that matches the bed identifier; The target network information and the target bed information are bound.

3. The device management method of the calling system according to claim 1, characterized in that: The step of broadcasting the target network information of the calling device to be initialized through a preset transmission protocol includes: Obtaining the single packet length of the transmission protocol; According to the single packet length, the target network information is packetized to obtain a plurality of data sub-packets of each of the calling devices to be initialized, wherein each of the data sub-packets carries a device identification of the calling device to be initialized; Each of the data sub-packets is broadcasted via the transmission protocol.

4. The device management method of the calling system according to claim 3, characterized in that: The target network information includes terminal address information, mask information, gateway information, server information and domain name information; the multiple data sub-packets of the calling device to be initialized are obtained by the following steps: including: Obtaining the device identifier, terminal address identifier, mask identifier, gateway identifier, server identifier and domain name identifier of the calling device to be initialized; Encapsulate the device identifier, the terminal address identifier and the terminal address information to obtain an address data sub-packet; Encapsulating the device identifier, the mask identifier and the mask information to obtain a mask data sub-packet; Encapsulate the device identifier, the gateway identifier and the gateway information to obtain a gateway data sub-packet; Encapsulate the device identifier, the server identifier and the server information to obtain a server data sub-packet; The device identifier, the domain name identifier and the domain name information are encapsulated to obtain a domain name data sub-packet.

5. The device management method of the call system according to claim 3, wherein the broadcasting of each of the data sub-packets through the transmission protocol comprises: cyclically broadcasting each of the data sub-packets through the transmission protocol; When all data sub-packets of one of the device identifications are successfully received, the broadcasting of the successfully received data sub-packets of the calling device is stopped.

6. A device management method for a call system, characterized in that: Applied to a calling device, the method comprises: In the case of uninitialized, after booting up, the QR code display page is entered and the QR code is displayed; Receive target network information broadcasted from the management terminal and perform network initialization according to the target network information, wherein the target network information is obtained by the method described in claim 1.

7. The device management method of the calling system according to claim 6, characterized in that: Each of the target network information is encapsulated into a plurality of data sub-packets and sent via the transmission protocol, and the method further comprises: Extracting a target device identifier, a target sub-packet type, and target network segmentation information from each of the received data sub-packets; When the extracted target device identifier matches the device identifier configured by itself, performing a data packet receiving step on the data sub-packet; The data packet receiving step comprises: According to the target sub-packet type, updating the network segmentation information matching the sub-packet type in the preset cache to the target network segmentation information; When the network segmentation information corresponding to each sub-packet type in the preset data packet type list is cached in the cache, indication information is sent to the management terminal to indicate that the target network information has been received.

8. A calling system, characterized in that: The device comprises: A plurality of calling devices, each of which executes the device management method of the calling system according to claim 6 or 7; A management terminal, wherein the management terminal executes the device management method of the call system according to any one of claims 1 to 5.

9. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the device management method of the call system described in any one of claims 1 to 5 and / or the device management method of the call system described in any one of claims 6 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the device management method for a call system according to any one of claims 1 to 5 and / or the device management method for a call system according to any one of claims 6 to 7 is implemented.

Images