A cooperative calling method, door lock and system
By introducing edge intelligence technology into the queuing terminal, changes in user status are automatically detected and multi-room collaborative management is achieved, solving the problems of low efficiency and accuracy caused by the reliance on manual operation of service queues, and improving the automation and user experience of the queuing system.
Patent Information
- Application Number
- CN202511044340.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-29
- Publication Date
- 2025-10-17
- Estimated Expiration
- 2045-07-29
AI Technical Summary
In large indoor queuing scenarios, changes in the service queue status rely heavily on manual operations by service personnel, resulting in low efficiency, high error rates, increased management difficulty, and difficulty in ensuring the synchronization and fairness of the queue status with the actual service progress.
By expanding the queuing terminal into a collaborative queuing terminal with edge intelligence technology, and using information collection rules to automatically detect changes in user status, manual intervention is reduced, dynamic collaborative management of multiple rooms is achieved, and the automation and intelligence level of queue updates are improved.
It improved the resource utilization and service fairness of the queuing system, reduced manual intervention, ensured the accuracy and real-time performance of queue management, and optimized the user's business processing experience.
Smart Images

Figure CN120544305B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of information technology, in particular to a cooperative call number method, a door lock and a system. BACKGROUND
[0002] In a large indoor call number scene, the same service can be handled in multiple rooms. In order to facilitate users to observe the call number situation of the service handling room, an independent call number display device (such as an LED screen or a liquid crystal screen) is set for each room. After completing the current user service, the service personnel need to manually operate the service terminal to trigger the update of the queue, such as clicking the "next" button to call the next user. When the service queue state changes, the system will push the updated queue information of the room to the corresponding call number display device for real-time display to inform the waiting users.
[0003] The above scheme can realize the visualization of the queue information to a certain extent, but the change of the service queue state highly depends on the manual operation of the service personnel, which has the problems of low efficiency and easy error. SUMMARY
[0004] Therefore, one or more embodiments of the present application provide a cooperative call number method, a door lock and a system.
[0005] To achieve the above object, one or more embodiments of the present application provide the technical solutions as follows.
[0006] According to a first aspect of the embodiments of the present application, a cooperative call number method is provided, which is applied to a cooperative call number system including a plurality of call number terminals. The plurality of call number terminals respectively maintain a service queue containing user data. Any call number terminal in the plurality of call number terminals performs the following steps: determining a target user in the service queue; performing information collection on the target user according to a corresponding information collection rule determined according to the queue attribute of the target user, and obtaining an information collection result of the target user; in the case where the state of the target user changes according to the information collection result, updating the service queue according to the changed state of the target user and generating a cooperative processing message; and sending the cooperative processing message to other call number terminals in the system, so as to make the other call number terminals update the service queue maintained by them synchronously.
[0007] According to a second aspect of the embodiments of the present application, a call number terminal for cooperative call number is provided, which includes: an information storage unit for storing the call number terminal information of itself, user data and a service queue constructed according to the user data; an information processing unit for executing the method of the first aspect and determining to-be-output information; an image collection unit for collecting information of a target user; an information output unit for outputting the to-be-output information; and a communication unit for realizing the communication function of the call number terminal.
[0008] According to a third aspect of the embodiments of the present specification, a cooperative call number system is provided, comprising: a plurality of call number terminals, each of the plurality of call number terminals corresponding to a different room, and any of the plurality of call number terminals being configured to implement the method of the first aspect; and one or more routing nodes configured to implement communication between the plurality of call number terminals.
[0009] According to a fourth aspect of the embodiments of the present specification, an electronic device is provided, comprising a processor and a memory for storing processor-executable instructions; wherein the processor is configured to implement the cooperative call number method of the first aspect.
[0010] According to a fifth aspect of the embodiments of the present specification, a computer-readable storage medium is provided, having stored thereon a computer program, the computer program being executed by a processor to implement the cooperative call number method of the first aspect.
[0011] According to a sixth aspect of the embodiments of the present specification, a computer program product is provided, comprising computer programs / instructions, the computer programs / instructions being executed by a processor to implement the cooperative call number method of the first aspect.
[0012] In the technical solution of the present application, the call number terminal is expanded from a data display end to a cooperative call number terminal with edge intelligence technology, improving the resource utilization rate, system automation rate and service fairness of the cooperative call number system; that is, the technical solution uses the call number terminal to determine the information collection rule applicable to the target user to collect key data strongly related to the next state, and uses the information collection result of the target user to accurately detect the change of the user state, so that the call number terminal can manage the service queue locally according to the detection result of the user state change, reduce the degree of dependence on manual intervention of the system, and improve the automation level and intelligent level of queue management, and after detecting the state change of the target user, the service queue between the plurality of call number terminals is also updated synchronously using the cooperative processing message, realizing dynamic cooperative call number management of multiple rooms, avoiding congestion in some rooms, ensuring that users can preferentially handle business in receivable rooms, and providing business handling experience for users.
[0013] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the embodiments of the present application. BRIEF DESCRIPTION OF DRAWINGS
[0014] Figure 1 is an architecture schematic diagram of a cooperative call number system provided by an exemplary embodiment;
[0015] Figure 2 is a flowchart of a cooperative call number method provided by an exemplary embodiment;
[0016] Figure 3 FIG. 1 is a schematic diagram of a multicast group member join process according to an example embodiment;
[0017] Figure 4 FIG. 2 is a schematic diagram of a reverse join process according to an example embodiment;
[0018] Figure 5 FIG. 3 is a schematic diagram of a number synchronization release process according to an example embodiment;
[0019] Figure 6 FIG. 4 is a schematic diagram of a number reassignment process according to an example embodiment;
[0020] Figure 7 FIG. 5 is a schematic diagram of a parallel call terminal location request process according to an example embodiment;
[0021] Figure 8 FIG. 6 is a block diagram of a door lock for coordinated calling according to an example embodiment;
[0022] Figure 9 FIG. 7 is a block diagram of a coordinated calling system according to an example embodiment;
[0023] Figure 10 FIG. 8 is a schematic diagram of an electronic device according to an example embodiment;
[0024] Figure 11 FIG. 9 is a block diagram of a coordinated calling apparatus according to an example embodiment. DETAILED DESCRIPTION
[0025] The example embodiments will be described in detail herein with reference to the attached drawings. The description of the example embodiments is intended to apply to all alternative modifications and embodiments, and is not limited to the example embodiments described herein. In other words, the description of the example embodiments is not intended to be exhaustive or to limit the example embodiments to the precise forms disclosed. Suitable modifications and embodiments will be apparent to those skilled in the art in light of the description and will be governed by the full scope of the disclosure and the appended claims.
[0026] It should be noted that the order of the steps of the methods described herein is not necessarily the order in which the steps are performed. In some other embodiments, the steps of the methods described herein can include more or fewer steps than those described. Also, the individual steps described herein can be split into multiple steps in other embodiments, and multiple steps described herein can be combined into a single step in other embodiments.
[0027] The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.
[0028] In related technologies, in large indoor service scenarios such as hospital clinics, government service centers, and bank branches, in order to improve the efficiency of business handling, the same type of business is usually deployed in multiple service windows or rooms (hereinafter collectively referred to as rooms) for parallel processing, and an independent call display device is set up in each room. The call display device is mainly used for queue display, and the change of the service queue highly depends on the manual operation of the service personnel. Manual operation has the possibility of accidental touch, such as mistakenly skipping a user, repeated calling, etc., which can easily disrupt the queue order and increase the difficulty of on-site management. Moreover, after the service personnel handle complex business during the peak period, they may not operate the service terminal in time to trigger queue updating due to being busy or careless, which causes the system to fail to perceive the service completion status in real time, and the next user cannot be called in time, thus artificially prolonging the actual waiting time of the user. In addition, this mode highly depends on the active operation of the service personnel, which not only increases their work burden, but also makes it difficult to ensure that all rooms can trigger updating in time when the service is completed, resulting in a delay or even deviation between the queue state managed by the system and the actual service progress, which affects the accuracy and fairness of the overall queue scheduling.
[0029] To solve the above problems, the present application proposes a collaborative call scheme, which extends the call terminal from a data display end to a terminal with edge intelligent technology for assuming the function of collaborative calling, effectively reducing the dependence on manual intervention, improving the automation and intelligent level of queue updating, and realizing dynamic collaborative call management of multiple rooms. In order to facilitate the understanding of the following embodiments of the present application, the system architecture of the collaborative call system of the embodiments of the present application is first described.
[0030] As shown in Figure 1 The collaborative call system includes a plurality of call terminals 110, at least one call management platform 120, and at least one number taking terminal 130, and the plurality of call terminals 110 correspond to a plurality of different service rooms. Among them, the call terminal 110 and the call management platform 120, the call terminal 110 and the call terminal 110, and the number taking terminal 130 and the call management platform 120 can interact information through their own communication network, or can interact information through the same communication network. The communication mode adopted by the communication network can be wireless communication mode or wired communication mode, or based on wireless communication mode and wired communication mode at the same time.
[0031] In the related art, the calling terminal 110 only undertakes the task of data display, and its hardware and location resources are not deeply developed and utilized, and the function is too single. Based on this, the embodiments of the present application deeply mine the potential of the calling terminal 110, use the widely deployed calling terminal 110 to reduce the dependence of manual intervention in the calling process, improve the automation level and intelligent level of the queue update, and realize the dynamic cooperation of the calling management of multiple rooms. In the embodiments of the present application, the calling terminal 110 includes but is not limited to terminal devices such as intelligent door locks, intelligent robots, and visual large screens. The calling terminal at least has hardware resources such as a camera, a loudspeaker, a display screen, a processor, and a communication component. The camera can provide face recognition and iris recognition functions. The loudspeaker can provide voice broadcast functions. The display screen can provide information display functions. The processor can realize edge intelligent functions. The communication component is used to realize communication with a remote device.
[0032] In the embodiments of the present application, the calling terminal 110 pre-stores service personnel information and calling terminal information. The service personnel information includes an identity ID of a service personnel, an iris feature vector, a on-duty state label, etc. The calling terminal information includes terminal identification information (for example, including a terminal ID), room information (for example, including a room ID) to which the calling terminal belongs, service information (for example, including a service ID) of the calling terminal, and location information (for example, a terminal floor ID) of the calling terminal, etc.
[0033] In some application scenarios, after the service personnel arrives at the post, the service personnel opens the room door lock through the iris recognition function of the calling terminal 110 first. The calling terminal 110 reports the identity ID of the service personnel, the terminal ID, the room ID, the service ID, and the floor ID, etc. to the calling management platform 120. When the service personnel logs in to the service terminal, the calling management platform 120 determines that the service personnel of the calling terminal is in the on-duty state according to the reporting information of the calling terminal and the service terminal login success information, sets the on-duty state label to tag=1, and then issues it to the calling terminal.
[0034] When a user takes a number at a service center, the call number management platform 120 prompts the user to input preset multiple biometric feature information such as facial feature and iris feature through the number taking terminal 130. The number taking terminal 130 extracts the facial feature registration information and the iris feature registration information of the user and uploads the number taking information of the user to the call number management platform 120. The call number management platform 120 generates user data, which includes personal information such as name and biometric feature registration information (facial feature registration information, iris feature registration information, etc.) and service reservation information such as service reservation time, reservation service information, reservation queuing information, number taking location information (which can be a number taking terminal ID), and number taking time. The call number management platform 120 determines a candidate call number terminal according to the reservation service information in the service reservation information. The service ID of the candidate call number terminal information is consistent with the reservation service information, and the on-duty state label of the service personnel is tag = 1. The call number management platform 120 filters the candidate call number terminal based on the principle of proximity according to the service reservation information of the user and the call number terminal information, and issues the user data to all candidate call number terminals that meet the principle of proximity as target call number terminals, and displays the waiting position on the number taking terminal 130, for example, the user's waiting area on the display screen of the number taking terminal 130, and the user's waiting on the outputted number taking sheet. The principle of proximity refers to the call number management platform 120 filtering the candidate call number terminal according to the number taking location information and the call number terminal location information, and determining the target call number terminal that belongs to the same area as the user's number taking location. The same area can be the same floor area or the same grid area. The grid area can be a grid unit that is divided in advance based on a certain division strategy.
[0035] The call number terminal 110 constructs a service queue according to the user data issued by the call number management platform 120. The service queues of all call number terminals that provide the same service and belong to the same area are dynamically the same.
[0036] Next, the embodiments of the present specification will be described in detail.
[0037] The embodiments of the present application provide a cooperative call number method. Figure 2 FIG. 2 is a flowchart of a cooperative call number method 200 provided by an exemplary embodiment. The method 200 is applied to a cooperative call number system, which includes multiple call number terminals that respectively maintain a service queue containing user data. Any call number terminal in the multiple call number terminals performs the following steps S210 to S240:
[0038] Step S210, determining a target user in the service queue.
[0039] The service queue can include a queuing queue and a state display queue. The calling terminal calls according to the queuing queue, and displays service queuing information to the user according to the state display queue. Generally, the state display queue can be a sub-queue of the queuing queue, and the sub-queue is a sub-queue corresponding to the first N users of the queuing queue, where N is a value greater than 2. In actual application, the value of N can be set according to requirements, for example, the first three users in the queuing queue are set as display objects of the state display queue.
[0040] The target user refers to a user whose service state can change. The queue position and the queue state are queue attributes that can represent the real-time service state of the user. In this embodiment, the target user in the service queue can be determined according to the queue attributes of the user. For example, the first user in the queuing queue (i.e., the current calling user) can be set as the target user, the third user (i.e., the number skipping early warning user) can be set as the target user, the user whose queuing order is extended (i.e., the number skipping user) can be set as the target user, or the user in the service state in the state display queue can be set as the target user.
[0041] In step S220, information collection rules corresponding to the target user are determined according to the queue attributes of the target user, and information collection is performed on the target user to obtain information collection results of the target user.
[0042] In one service period, the service state of the user is dynamically changed, and the state transition follows a predefined state machine model. The state machine model can be set according to actual application requirements. For example, the subsequent state of “waiting” is “in service” or “number skipping”. The subsequent state of “number skipping” is “local extension” or “step rearrangement”, which means that the user reenters the queuing queue, and the subsequent state transition rule is the same as the initial “waiting” state. The “service end” state marks the end of the current service period, and has no subsequent state transition.
[0043] In this embodiment, information collection rules are set in advance, and the necessary and high-quality data required for state change detection are accurately provided through the information collection rules. The current service state of the target user directly determines the applicable information collection rule of the target user. Therefore, in this embodiment, the applicable information collection rule of the target user is determined through the queue attributes of the target user, so as to collect key data strongly related to the next state, improve the detection accuracy of the state change, and improve the response capability of the calling terminal, for example, more timely trigger the number skipping early warning and the number skipping rearrangement, and more accurately detect the service end time to optimize the subsequent calling.
[0044] It should be noted that in the case of multiple target users in the service queue, the information collection order can be determined according to the priority of the target users, for example, the target users such as the service-in user and the current called number user have high priority, and the target users such as the over-number warning user and the over-number user have low priority. The priority of each target user can be flexibly designed by those skilled in the art without special limitation in this embodiment.
[0045] In step S230, in the case where the state of the target user changes according to the information collection result, the service queue is updated according to the changed state of the target user, and a cooperative processing message is generated.
[0046] The information collection result of the embodiment includes key data of the target user entering the next state. According to the information collection result, whether the service state of the target user changes can be detected. In the case where the state changes, the service queue maintained by the current called number terminal is updated according to the preset update rule, and a cooperative processing message is generated. The preset update rule can be set according to actual business needs. The update rule includes, for example, the target user's number release rule, the target user's number postponement rule, the target user's over-number rearrangement rule, and the target user's state prompt rule. The cooperative processing message instructs the related called number terminal to update the service queue maintained by the called number terminal. For example, the cooperative processing message includes a synchronous removal message corresponding to the "service-in" state, a synchronous postponement message corresponding to the "over-number" state, a synchronous prompt message corresponding to the "service-end" state, and a synchronous rearrangement message corresponding to the "rearrangement" state. The generation mode, transmission mode and effect of each cooperative processing message will be further introduced in subsequent embodiments.
[0047] In step S240, the cooperative processing message is sent to other called number terminals in the system, so that the other called number terminals update the service queue maintained by the called number terminals.
[0048] Reference Figure 2 As shown in the cooperative calling method, the technical solution uses the called number terminal to determine the information collection rule suitable for the target user to collect key data strongly related to the next state, and accurately detects the change of the user state by using the information collection result of the target user. The called number terminal can manage the service queue locally according to the detection result of the change of the user state, reduce the dependence on manual intervention of the system, and improve the automation level and intelligent level of the queue management. In addition, after detecting the change of the state of the target user, the technical solution also uses the cooperative processing message to update the service queue between multiple called number terminals, and realizes the dynamic cooperative calling management in multiple rooms. It can be seen that the technical solution can improve the resource utilization rate, system automation rate and service fairness of the cooperative calling system by expanding the called number terminal from the data display end to the cooperative calling terminal with edge intelligent technology.
[0049] In an illustrated embodiment, Figure 2 The illustrated method 200 further includes: receiving user data; determining whether the user is a service object of the current calling terminal according to the user data and the current calling terminal information; and adding the user into a service queue maintained by the current calling terminal according to the user data if the user is a service object of the current calling terminal. For example, the reservation service ID and the service ID of the current calling terminal, and the floor ID of the number taking terminal and the floor ID of the current calling terminal are matched respectively. If the reservation service ID is the same as the service ID of the current calling terminal, and the floor ID of the number taking terminal and the floor ID of the current calling terminal match each other, it is determined that the user is a service object of the current calling terminal. Here, the floor ID matching each other means that the number taking terminal and the current calling terminal are in the same floor area or the same grid area. In this way, the current calling terminal can provide nearby service for the user in the same floor, thereby improving the service experience of the user.
[0050] In an embodiment of the present embodiment, if the reservation service ID of the user is not the same as the service ID of the current calling terminal, it is determined that the user is not a service object of the current calling terminal, and the current calling terminal does not add the user into the service queue maintained thereby. At this time, the current calling terminal can feed back to the calling management platform to request the calling management platform to re-allocate a receivable room for the user.
[0051] In another embodiment of the present embodiment, if the reservation service ID of the user is the same as the service ID of the current calling terminal, but the floor ID of the number taking terminal and the floor ID of the current calling terminal do not match each other, for example, the user takes the number at the first floor of the service center, and the room to which the current calling terminal belongs is located at the third floor of the service center. At this time, the floor ID of the number taking terminal and the floor ID of the current calling terminal do not match each other. The current calling terminal obtains the information of the parallel calling terminals (the parallel calling terminals refer to all other calling terminals having the same service ID as the current calling terminal) from the plurality of calling terminals, calculates the position matching degree of the user and the parallel calling terminals, and determines that the room to which the current calling terminal belongs is the nearest serviceable room for the user if the position matching degree of the user and the parallel calling terminals is not higher than the position matching degree of the user and the current calling terminal. In this case, the user is taken as a service object of the current calling terminal. If the position matching degree of the user and the parallel calling terminals is higher than the position matching degree of the user and the current calling terminal, it is determined that the room to which the current calling terminal belongs is not the nearest serviceable room for the user, and the current calling terminal does not add the user into the service queue maintained thereby.
[0052] In an illustrated embodiment, the information collection rule in the above step S220 includes at least one of the following four rules:
[0053] Rule one: collecting the on-site identity information through near-field collection, including: sending a service invitation message and collecting the on-site identity information through the image collection device of the current calling terminal within a first preset time;
[0054] Rule two: collecting the off-site identity information through near-field collection, including: collecting the off-site identity information through the image collection device of the current calling terminal;
[0055] Rule three: collecting the repositioning information through far-field collection, including: collecting the repositioning information through message broadcasting;
[0056] Rule four: collecting the repositioning information through cooperative collection, including: collecting the positioning information through the image collection device of the current calling terminal, and collecting the repositioning information through message broadcasting if the current calling terminal does not locate the target user within a second preset time.
[0057] In the case that the queue attribute of the target user includes a queue position being a calling position, the on-site identity information is collected through rule one, the on-site identity information includes face feature detection information and / or iris feature detection information, and the on-site identity information is authenticated according to the biological feature registration information, and the information collection result of the target user is obtained according to the identity authentication result. That is, rule one is applicable to the target user whose current queue position is a calling position. Assuming that the target user X1 is due to handle business in the current room, the current calling terminal of the current room sends a service invitation about the target user X1, the current calling terminal can display the service invitation through the display screen, can broadcast the service invitation through the loudspeaker, or can send the service invitation to the personal mobile terminal (such as a mobile phone, a watch, etc.) of the target user X1. If a response to the service invitation is received within a preset time, for example, the face feature and / or iris feature of the target user X1 is collected by the camera of the current calling terminal within 2 minutes, it is indicated that the target user X1 has arrived at the camera of the current calling terminal within 2 minutes to perform near-field identity authentication, and at this time, it can be determined that the target user X1 has changed from the "waiting" state to the "serving" state. If the response to the service invitation is not received within the preset time, that is, the face feature or iris feature of the target user X1 is not collected by the camera within 2 minutes, it is indicated that the target user X1 has not arrived at the camera of the current calling terminal within 2 minutes to perform near-field identity authentication, and at this time, it can be determined that the target user X1 has changed from the "waiting" state to the "over number" state.
[0058] In a case where the queue attribute of the target user includes a queue state as in service, off-site identity information including face feature detection information and / or iris feature detection information is collected by rule two, the off-site identity information is authenticated according to the biometric feature registration information, and an information collection result of the target user is obtained according to an identity authentication result. Rule two is applicable to a target user whose current queue state is in service. If the target user X2 is currently handling business in the current room, the current calling terminal continuously monitors whether the real-time collection image of the camera of the current calling terminal includes the face feature and / or iris feature of the target user X2. If it is monitored that the real-time collection image includes the face feature or iris feature of the target user X2, it indicates that the target user X2 has completed business handling and off-site identity authentication. At this time, it can be determined that the target user X2 has changed from the “in service” state to the “service end” state. If the real-time collection image does not include the face feature or iris feature of the target user X2 within a second preset time (for example, within 10 minutes), for example, because the head of the target user X2 is blocked, or the camera of the calling terminal is blocked, causing the calling terminal to not collect the face feature or iris feature of the target user X2, the calling terminal can send a state feedback request about the target user X2 to the service terminal in the room. After receiving the state feedback request, the service terminal sends the service state information of the target user X2 to the calling terminal. The calling terminal can manage the state of the target user X2 according to the feedback information of the service terminal, avoiding the calling terminal from not being able to update the service state of the target user X2 in time due to environmental factors such as blocking.
[0059] In a case where the queue attribute of the target user includes a queue state of overnumbering, repositioning information is collected by a far-field collection manner, the repositioning information including face feature detection information and repositioning terminal information, and position matching is performed according to the repositioning terminal information and current calling terminal information, and an information collection result is obtained according to a position matching result. Rule three is applicable to a target user whose current queue state is overnumbering. After the target user X1 does not reach the camera of the current calling terminal for near-field identity authentication within 2 minutes, the current calling terminal determines that the target user X1 has overnumbered, at which time a broadcast message carrying face feature registration information of the target user X1 and a specified message type is generated and broadcast to all other calling terminals. The specified message type is used to instruct the receiving end to locate the target user X1 according to the face feature registration information of the target user X1, and to unicast a reply response message after successful location. After the other calling terminals of the service center receive the broadcast message, the face feature detection information of the nearby user is captured by the camera of each calling terminal and compared with the face feature registration information of the target user X1. If the face feature detection information of the nearby user captured by a certain calling terminal matches the face feature registration information of the target user X1, the calling terminal can directly unicast an overnumbering response message to the broadcast source. The overnumbering response message carries repositioning terminal information and face feature detection information matching the face feature registration information of the target user X1. The current calling terminal performs position matching between the current calling terminal and the repositioning terminal according to the repositioning terminal information and the current calling terminal information, and uses the position matching result as the information collection result of the target user X1. The repositioning terminal is a calling terminal that locates the target user X1. It is worth noting that when a certain calling terminal captures face feature detection information of a nearby user that matches the face feature registration information of the target user X1, the repositioning terminal can further perform position matching according to its own position and the position of the broadcast source. If they belong to the same area, it indicates that the target user X1 is already within the service range of the current calling terminal. In this case, the current calling terminal does not need to allocate other service rooms for the target user X1, and therefore the repositioning terminal does not need to reply the overnumbering response message to the broadcast source. Only when they are in different areas, the repositioning terminal replies the overnumbering response message to the broadcast source, so as to save communication resources and computing resources.
[0060] In a case where the queue attribute of the target user includes a queue position being an over-numbering early warning position, the repositioning information is collected in a cooperative collection manner, the repositioning information including face feature detection information and repositioning terminal information, and position matching is performed according to the repositioning terminal information and current calling terminal information, an information collection result is obtained according to a position matching result, in a case where the information collection result indicates that the repositioning terminal information and the current calling terminal information are not matched, it is determined that the target user meets an early warning condition, and an over-numbering early warning message is sent to a calling management platform, so that the calling management platform prompts that the target user has an over-numbering risk. Rule four is applicable to a target user whose queue position is an over-numbering early warning position. If the target user X3 has two users waiting for service in the front, it is determined that the queue position of the target user X3 is an over-numbering early warning position. At this time, the current calling terminal generates a broadcast message carrying the face feature registration information of the target user X3 and a message type and broadcasts the broadcast message to all calling terminals in the service center. The message type carried in the broadcast message is used to instruct the receiving end to locate the target user according to the face feature registration information of the target user X3, and after successful location, further match the position of the receiving end with the position of the broadcast source. If the two positions belong to different areas, an over-numbering early warning response message is replied in unicast. After receiving the over-numbering early warning response message, the current calling terminal matches the positions of the current calling terminal and the repositioning terminal according to the repositioning terminal information and the current calling terminal information, and takes the position matching result as the information collection result of the target user X3. In a case where the positions of the current calling terminal and the repositioning terminal are not matched, it is determined that the target user X3 has an over-numbering risk, an over-numbering early warning message is reported to the calling management platform, and the message content of the over-numbering early warning message includes the current calling terminal information, the user data of the target user X3 and the current queuing order information of the target user X3. The calling management platform sends instant messaging information to the target user X3 according to the over-numbering early warning message, for example, sends a short message "Dear X3, your queuing order for handling XX business in XX room of my center is coming, there are only 2 users waiting in front, please return to the room in time to avoid over-numbering".
[0061] The above embodiments of the present application collect information of the target user according to the information collection rule applicable to the target user, and perform identity authentication or position authentication on the collected information according to the biological feature registration information of the target user, and take the identity authentication result or the position authentication result as the information collection result of the target user.
[0062] In an illustrated embodiment, the step S230 of determining that the state of the target user changes according to the information collection result includes: in a case where the queue position of the target user is a called position and the information collection result indicates that the target user is authenticated, determining that the state of the target user changes and changing the state of the target user from a waiting state to a service state; in a case where the queue position of the target user is a called position and the information collection result indicates that the target user is not authenticated, determining that the state of the target user changes and changing the state of the target user from the waiting state to a missed position state; in a case where the queue state of the target user is in service and the information collection result indicates that the target user is authenticated, determining that the state of the target user changes and changing the state of the target user from the service state to a service end state; and in a case where the queue state of the target user is in a missed position and the information collection result indicates that the reposition terminal information does not match the current called terminal information, determining a first position matching degree between the target user and each other called terminal in the system and a second position matching degree between the target user and the current called terminal, and in a case where the first position matching degree is greater than the second position matching degree, determining that the state of the target user changes and changing the state of the target user from the missed position state to a rearrangement state.
[0063] In a case where the target user is not authenticated, no identity information containing facial features or iris features is collected, or the facial features or iris features contained in the collected identity information do not match the facial feature registration information or the iris feature registration information of the target user, so as to determine that the target user does not arrive at the camera of the current called terminal for near-field identity authentication within 2 minutes. The position matching degree can be calculated according to the distance or the convenience of travel of the target user. The shorter the path between the called terminal and the target user, the higher the position matching degree. The fewer the floor intervals between the target user and the called terminal, the more convenient the missed position object is to go, and the higher the position matching degree. In a case where the floor intervals are the same, the position matching degree can be further calculated according to the relative position relationship of the floors. For example, the position matching degree of the called terminal on the floor below the target user is higher than that of the called terminal on the floor above the target user. In this way, in a case where it is determined that the target user X1 is in a missed position, it can be further determined whether there is a called terminal that is closer to the target user X1 in the called terminal in parallel. If there is a called terminal that is closer to the target user, it is determined that the state of the target user changes, and the state of the target user X1 is changed from the missed position state to the rearrangement state.
[0064] Continuing with the previous example, in the case where the service queue includes a queuing queue and a status display queue, if the status of the target user X1 changes to being in service, the current calling terminal can change the status of the target user X1 in the status display queue from waiting to being in service, and remove the target user X1 from the queuing queue, and the queuing order of subsequent users will be reduced by 1 respectively; if the status of the target user X1 changes to being passed, the current calling terminal can change the status of the target user X1 in the status display queue from waiting to being passed, and postpone the queuing order of the target user X1 in the queuing queue by M places, M is a positive integer, and its value can be set according to actual needs. When there is a mobile calling terminal closer to the target user X1 among the parallel calling terminals of the target user X1, the current calling terminal adds the target user X1 to the service queue of the mobile calling terminal, removes the target user X1 from the queuing queue of the current calling terminal, and reduces the queuing order of subsequent users by 1. The status of the target user X1 in the status display queue is changed from the passed state to the requeued state; the status of the target user X1 in the status display queue is changed from the in-service state to the service ended state.
[0065] In an illustrated embodiment, the target user's status is changed from a missed call status to a re-arranged call status. Method 200 further includes: sending a mobile call reminder message to the re-location terminal. The mobile call reminder message instructs the re-location terminal to send a reminder message to the target user to go to the room associated with the mobile call terminal for service. For example, if the current call terminal sends the mobile call reminder message to the re-location terminal A, one prompt method of the re-location terminal A is to announce the missed call, such as "Dear X1, your service number in room XX of our service center has been missed. Since your current location is far from the original queue room, you have been re-arranged to a closer room. Rooms E, F, etc. on a certain floor are available for service. Please click the confirmation button on the screen to close the voice reminder." Another prompt method is to report the missed call re-arrangement message to the call management platform. The missed call re-arrangement message includes information about the source call terminal, the mobile call terminal, the target user, and the re-arranged queue order. The call management platform then sends an instant messaging reminder to the target user's personal mobile terminal based on the missed call re-arrangement message.
[0066] In an illustrated embodiment, when the target user's status changes to being in service or being finished, the method 200 further includes: unlocking the door lock of the room to which the current calling terminal belongs, so that the target user can enter or leave the room.
[0067] In addition, in the technical solution, each calling terminal only stores its own information, does not store information of other calling terminals, if the current calling terminal sends the cooperative processing message to other calling terminals in a broadcast mode, will cause communication resource consumption, and occupy the computing resource of other calling terminals, cause unnecessary terminal busy, and since each calling terminal does not store information of other calling terminals, also cannot transmit information through a unicast mode.
[0068] In view of this, in an illustrated embodiment, Figure 2 The illustrated method 200 further includes: generating a join message of a multicast group according to the current calling terminal information; sending the join message to the multicast group, so that a corresponding routing node of the multicast group saves the current calling terminal information carried by the join message in an out-interface of a table entry of a multicast forwarding table, for matching with a routing locator identifier carried by a multicast message. Wherein, the current calling terminal information at least includes terminal identification information, service information of the calling terminal and location information of the calling terminal, the join message instructs the routing node to store the current calling terminal information in the out-interface of the table entry of the multicast forwarding table of the routing node itself, through joining multiple calling terminals in the same multicast group and improving the content of the join message, the first calling terminal can realize the multicast forwarding of the cooperative processing message to the specified receiving end without carrying the address information of the specified receiving end.
[0069] In one scenario of the embodiment, after the service personnel of the room to which each call terminal belongs arrives at the post, the call terminal sends a join message to a designated multicast group address based on an Internet Group Management Protocol (IGMP). The join message based on the IGMP protocol further adds a service ID (Department ID), a call terminal location ID (abbreviated as Floor ID), and a terminal ID (abbreviated as Lock ID) of the current call terminal on the original message structure, so that the routing nodes of the multicast group store the call terminal information in the interface-out of the multicast forwarding table. It should be noted that all call terminals in the embodiment join the same multicast group, and each call terminal can be a sender or a receiver, and therefore the routing nodes of the technical solution adopt a bidirectional Protocol Independent Multicast (PIM) protocol to forward the multicast message. In the bidirectional PIM protocol, the message is sent along a path pointing to a rendezvous point (RP), and after the message is sent to the RP, it is forwarded according to the PIM multicast forwarding table. In the bidirectional PIM network, there is a (*, G) multicast forwarding table, where G represents a multicast group, * represents any, and (*, G) represents a message sent to G. Unlike related technologies, the interface-out of the multicast forwarding table in the embodiment stores information such as Lock ID, Department ID, and Floor ID, which is used to match the routing locator carried by the multicast message.
[0070] As shown in FIG. 1, Figure 3 For example, as shown in FIG. 2, the service 1 of the service center has a total of five rooms, of which room A, room B, and room C are located on the first floor, and room E and room F are located on the second floor; the service 2 of the service center has a total of two rooms, namely room G and room H, which are both located on the third floor. Each room is provided with a corresponding call terminal. Assuming that the service personnel of all rooms of the service 1 and the service 2 have arrived at the post, all call terminals send join messages carrying their Department ID, Floor ID, and Lock ID to the multicast group address 226.1.1.1 to join the multicast group with the IP address 226.1.1.1. The switches on the first floor, the second floor, and the third floor send (*, G) PIM join messages to the RP to join the multicast group. In this process, the multicast forwarding table generated by the switch on the first floor is as follows:
[0071] (*, 226.1.1.1), RP 192.168.10.1
[0072] Incoming interface: GigabitEthernet0 / 1 (State: Active) / / Incoming interface: GigabitEthernet 0 / 1. "GigabitEthernet" refers to the Gigabit Ethernet port. The same applies below.
[0073] Outgoing Interfaces: / / Table outgoing interface list
[0074] GigabitEthernet0 / 2 (Device: Department 1, Floor 1, Lock A, State: Forwarding)
[0075] GigabitEthernet0 / 3 (Device: Department 1, Floor 1, Lock B, State: Forwarding)
[0076] GigabitEthernet0 / 4 (Device: Department 1, Floor 1, Lock C, State: Forwarding)
[0077] After the RP receives the (*, G) PIM join message from the switch on the first floor, it generates the following multicast forwarding table:
[0078] (*, 226.1.1.1), RP 192.168.10.1
[0079] Incoming interface: NULL
[0080] Outgoing Interfaces: / / Table outgoing interface list
[0081] GigabitEthernet0 / 1 (Device: Department 1, Floor 1, Lock A, B, C, State: Forwarding)
[0082] GigabitEthernet0 / 2 (Device: Department 1, Floor 2, Lock E, F, State: Forwarding)
[0083] GigabitEthernet0 / 3 (Device: Department 2, Floor 3, Lock G, H, State: Forwarding)
[0084] Thus, in the process of joining the multicast group by the call terminal, the routing node of the multicast group generates the corresponding multicast forwarding table, and stores the Department ID, Floor ID and Lock ID and other information of the call terminal into the table entry out interface of the multicast forwarding table. When a call terminal needs to send a multicast message to a specified call terminal, a routing positioning identifier can be added in the multicast message, and the field value of the routing positioning identifier is specified according to the type of the multicast message. The fields of the routing positioning identifier include, for example, Department ID field + Floor ID field, so as to associate the current call terminal with the parallel call terminal. In this way, the routing node can determine the out interface corresponding to the routing positioning identifier in its multicast forwarding table to perform directional forwarding of the multicast message.
[0085] In an embodiment, in the case that the routing node receives the join message sent by the downstream routing node and saves the call terminal information carried by the join message in the table entry out interface of the multicast forwarding table maintained by the routing node, the routing node further queries the multicast forwarding table maintained by the routing node according to the service information in the call terminal information. If the table entry out interface of the multicast forwarding table maintained by the routing node also saves other call terminal information with the same service information, the routing node generates a reverse join message and sends the reverse join message to the downstream routing node. The reverse join message carries other call terminal information with the same service information, and is used to instruct the downstream routing node to save the other call terminal information in the table entry in interface of the multicast forwarding table of the downstream routing node. The reason why the message is called a reverse join message is that the processing flow of the traditional PIM protocol is to send a PIM join message only to the out interface in the RP direction, but not to the out interface in other directions. The reverse join message of the embodiment is sent to the out interface in the non-RP direction, so it is called a reverse join message. The reverse join message of the embodiment does not affect the forwarding mechanism of the original bidirectional PIM.
[0086] In an embodiment, in the case that the routing node receives the join message sent by the downstream routing node and saves the call terminal information carried by the join message in the table entry out interface of the multicast forwarding table maintained by the routing node, the routing node further queries the multicast forwarding table maintained by the routing node according to the service information in the call terminal information. If the table entry out interface of the multicast forwarding table maintained by the routing node also saves other call terminal information with the same service information, the routing node generates a reverse join message and sends the reverse join message to the downstream routing node. The reverse join message carries other call terminal information with the same service information, and is used to instruct the downstream routing node to save the other call terminal information in the table entry in interface of the multicast forwarding table of the downstream routing node. The reason why the message is called a reverse join message is that the processing flow of the traditional PIM protocol is to send a PIM join message only to the out interface in the RP direction, but not to the out interface in other directions. The reverse join message of the embodiment is sent to the out interface in the non-RP direction, so it is called a reverse join message. The reverse join message of the embodiment does not affect the forwarding mechanism of the original bidirectional PIM. Figure 4Taking the scenario shown above as an example, upon receiving a (*, G) PIM join message from the first-floor switch, the RP checks its multicast forwarding table (*, G) and finds that the department ID carried in the entry for outbound interface GigabitEthernet0 / 2 is 1, which is the same as the service ID in the (*, G) PIM join message received from the interface connected to the first-floor switch. The RP then sends a reverse join message to the outbound interface connected to the first-floor switch. The reverse join message carries the service ID, location ID, and terminal ID corresponding to the entry for outbound interface GigabitEthernet0 / 2. Upon receiving the reverse join message, the first-floor switch updates its multicast forwarding table (*, G) and stores the service ID, floor ID, and terminal ID in the reverse join message in the inbound interface of the entry in the first-floor switch's multicast forwarding table (*, G). The inbound interface of the entry in the first-floor switch's multicast forwarding table (*, G) now stores the call terminal information for call terminal E and call terminal F. The reverse join identifier is set for this inbound interface in the first-floor switch's multicast forwarding table (*, G). During this reverse join process, the multicast forwarding table generated by the switch on the first floor is as follows:
[0087] (*, 226.1.1.1), RP 192.168.10.1
[0088] Incoming interface: GigabitEthernet0 / 1 (Device: Department 1, Floor 2, Lock E, F, State: Active, TAG: Reverse Join) / / Incoming interface
[0089] Outgoing Interfaces: / / Table outgoing interface list
[0090] GigabitEthernet0 / 2 (Device: Department 1, Floor 1, Lock A, State: Forwarding)
[0091] GigabitEthernet0 / 3 (Device: Department 1, Floor 1, Lock B, State: Forwarding)
[0092] GigabitEthernet0 / 4 (Device: Department 1, Floor 1, Lock C, State: Forwarding)
[0093] In this way, the multicast source routing node (also called the first hop routing node, corresponding to Figure 4The floor exchange of the illustrated scenario stores all the calling terminal information of the same service. When a calling terminal needs to obtain the positions of all the calling terminals of the same service, a first multicast message carrying service information and a reverse identifier is sent to the multicast network, so that Figure 4 For example, if calling terminal A needs to obtain the positions of all the other calling terminals of the same service, a first multicast message is generated. The message content of the first multicast message includes the IP of calling terminal A, a service ID, a position ID, a terminal ID and a reverse identifier tag=1. The destination address of the first multicast message can be 224.0.0.2, so as to directly send the first multicast message to the corresponding multicast source end routing node, avoiding interference with other nodes in the multicast network. When the multicast source end routing node receives the first multicast message, it can provide all the calling terminal information of the same service to the calling terminals corresponding to the multicast source according to the calling terminal information stored in the table entry of the multicast forwarding table.
[0094] In an embodiment, the step of updating the service queue and generating a cooperative processing message according to the changed state of the target user in step S230 includes adding a routing positioning identifier in the message content of the cooperative processing message. Correspondingly, the step of sending the cooperative processing message to other calling terminals in the system in step S240 includes encapsulating the cooperative processing message into a multicast message and sending it to the multicast group. The multicast message instructs the routing node corresponding to the multicast group to determine the table entry out-interface of the multicast message according to the routing positioning identifier, so as to send the cooperative processing message to each other calling terminal matching the routing positioning identifier.
[0095] In an embodiment, adding a routing positioning identifier in the message content of the cooperative processing message includes determining the field information of the routing positioning identifier, which includes a service field and a terminal position field. The field value of the service field is determined according to the service information of the current calling terminal, and the field value of the terminal position field is determined according to the changed state of the target user. Since multiple calling terminals join the same multicast group, and the routing node corresponding to the multicast group stores the calling terminal information in the respective multicast forwarding table, when the current calling terminal needs to send a multicast message to a destination calling terminal, it does not need to rely on the receiving end address. It only needs to add a routing positioning identifier in the multicast message and set the field value of the routing positioning identifier according to the service state of the target user after the change. The field value of the routing positioning identifier is used to associate the current calling terminal with the destination calling terminal, so that the routing node can quickly determine the out-interface of the multicast message based on the spatial topology relationship between the room nodes, and quickly forward the multicast message to the destination calling terminal.
[0096] Next, the queue synchronization process between the current calling terminal and other calling terminals is described according to the service state of the target user Y in a service period. As described above, the technical solution provided by the embodiments of the present application can be applied to large indoor service scenarios, such as hospital diagnosis area, government service center and bank outlets, etc. For the sake of description, the hospital diagnosis area scenario will be taken as an example in the following description.
[0097] (1) The treatment state of the target user Y is changed to service in progress:
[0098] With Figure 5In the illustrated scenario, if the calling terminal A determines that it is the turn of the target user Y to be treated, the calling terminal A can send a treatment invitation through the display screen and / or the loudspeaker of the calling terminal A. If the target user Y performs face recognition authentication and iris recognition authentication at the camera of the calling terminal A within 2 minutes after the sending of the treatment invitation to complete the near-field identity authentication, in the case where the near-field identity authentication is completed, the calling terminal A opens the door lock of the treatment room A. After the opening of the door lock, the calling terminal A removes the target user Y from the queue maintained by the calling terminal A and reduces the queue numbers of the subsequent users by 1, changes the treatment state of the target user Y in the state display queue maintained by the calling terminal A to be in treatment, and generates a synchronization removal message about the target user Y. The synchronization removal message carries the state change information of the target user Y (including the changed treatment state and the changed treatment state) and the routing locator identifier. The calling terminal A takes the department ID of the department to which the calling terminal A belongs as the department ID field value of the routing locator identifier, takes the floor ID of the calling terminal A as the terminal position ID field value of the routing locator identifier, and then encapsulates the synchronization removal message into a multicast packet according to the multicast source information and the multicast address information for sending. When the first floor switch receives the multicast packet, it identifies that the multicast packet carries the routing locator identifier. Since the first floor switch is directly connected to the multicast source and all the treatment rooms in the first floor are connected to the PIM network through the first floor switch, the first floor switch can directly query the table entries of the multicast forwarding table maintained by the first floor switch. At this time, it can be determined that the department ID carried by the three table entry out interfaces GigabitEthernet0 / 2, GigabitEthernet0 / 3 and GigabitEthernet0 / 4 is Department 1 and the position ID is Floor 1, which is consistent with the routing locator identifier in the multicast packet. The table entry out interface GigabitEthernet0 / 2 corresponds to the multicast source of the multicast packet, and the synchronization removal message does not need to be sent to the table entry out interface. Only the synchronization removal message needs to be sent to the two table entry out interfaces GigabitEthernet0 / 3 and GigabitEthernet0 / 4. The calling terminal B and the calling terminal C receiving the synchronization removal message parse the synchronization removal message and remove the target user Y from the queue maintained by each of the calling terminal B and the calling terminal C according to the state change information of the target user Y, reduce the queue numbers of the subsequent users by 1, and modify the treatment state of the target user Y to be in treatment in the state display queue maintained by each of the calling terminal B and the calling terminal C and mark that the target user Y has been treated in the treatment room A.According to the bidirectional PIM protocol rules, the multicast message corresponding to the synchronization removal message is also forwarded to the RP. The RP analyzes the multicast message and finds that only the department ID and location ID saved by the GigabitEthernet 0 / 1 are consistent with the department ID and location ID carried by the multicast message. However, since the GigabitEthernet 0 / 1 is also the entry interface of the table item receiving the multicast message, according to the multicast protocol rules, the multicast message is not forwarded out from the entry interface of the table item, and the RP discards the multicast message and no longer performs multicast forwarding.
[0099] (2) The treatment state of the target user Y is changed to service end:
[0100] In the previous example, when the target user Y completes the treatment, the face recognition authentication and the iris recognition authentication are performed at the camera of the calling terminal A to complete the off-site identity authentication. In the case of completing the off-site identity authentication, the calling terminal A opens the door lock of the clinic and changes the treatment state of the target user Y to treatment end in the state display queue thereof. Meanwhile, the next invitation object is determined according to the maintained queuing queue, and a treatment invitation is issued, and a synchronization prompt message is generated. The synchronization prompt message carries the state change information of the target user Y and the routing locator identifier. The routing locator identifier, the message encapsulation, and the message forwarding of the synchronization prompt message can refer to the synchronization removal message shown in Figure 5 The embodiments of the present application do not repeat here. The calling terminal B and the calling terminal C receiving the synchronization prompt message modify the treatment state of the target user Y to treatment end and mark that the target user Y has completed the treatment in the clinic A in the state display queue maintained by each of the calling terminal B and the calling terminal C. Meanwhile, a prompt message of the next patient is added in the state display queue to prompt the next patient to go to the clinic A for treatment. The content and the prompting method of the prompt message can be set according to the requirements of the person skilled in the art.
[0101] (3) The treatment state of the target user Y is changed to over number:
[0102] In the previous example, after the calling terminal A issues the treatment invitation to the target user Y, the target user Y does not perform the near-field identity authentication at the camera of the calling terminal A within 2 minutes. The calling terminal A moves the treatment object X by 5 positions backward from the maintained queuing queue, and the queuing orders of the subsequent patients are reduced by 1. Meanwhile, the treatment state of the target user Y is changed to over number in the state display queue maintained by the calling terminal A, and a synchronization delay message about the target user Y is generated. The message content, the message encapsulation, and the message forwarding of the synchronization delay message can refer to Figure 5The synchronization removal message is shown. In this embodiment, the modification of the target user Y's treatment state to a missed call in the state display queue maintained by the call terminal B and the call terminal C, the backward shift of the target user Y by 5 positions in the queue maintained by the call terminal B and the call terminal C, and the decrease of the subsequent users' queue numbers by 1, make the service queue maintained by the call terminal B and the call terminal C synchronized with the service queue maintained by the call terminal A.
[0103] In the case where the target user Y's treatment state is changed to a missed call, the call terminal A acquires the target user Y's reposition information according to rule three. If the reposition information of the target user Y indicates that the reposition terminal is located on the second floor of the hospital, the call terminal A needs to acquire the parallel call terminal information. In an embodiment, the method 200 further comprises the following steps of acquiring the parallel call terminal information of the current call terminal: generating a first multicast message, wherein the first multicast message carries a reverse identifier and service information to which the current call terminal belongs, and the reverse identifier indicates that the target routing node in the multicast group replies to the current call terminal with a reply message carrying the parallel call terminal information; and sending the first multicast message to the routing node and acquiring the parallel call terminal information according to the received reply message. Figure 6 For example, the call terminal A sends the first multicast message to the switch on the first floor, and the message content of the first multicast message includes the department ID of the call terminal A and the reverse identifier. After receiving the first multicast message, the switch on the first floor extracts the department ID in the message and queries the multicast forwarding table (G) to obtain the parallel call terminal information of all floors of the same department and returns the information to the call terminal A. The return message content includes the department ID, the terminal position ID list and the terminal ID list.
[0104] (4) The target user Y's treatment state is changed to a rearrangement:
[0105] For example, the call terminal A sends the first multicast message to the switch on the first floor, and the message content of the first multicast message includes the department ID of the call terminal A and the reverse identifier. After receiving the first multicast message, the switch on the first floor extracts the department ID in the message and queries the multicast forwarding table (G) to obtain the parallel call terminal information of all floors of the same department and returns the information to the call terminal A. The return message content includes the department ID, the terminal position ID list and the terminal ID list. Figure 7The shown scenario is an example, the calling terminal A generates a synchronization rearrangement message of the target user Y and encapsulates the synchronization rearrangement message into a multicast message according to the multicast source information and the multicast address information for sending, wherein the synchronization rearrangement message carries a routing positioning identifier and rearrangement sequence information, the terminal position ID field value of the routing positioning identifier is the position ID of the moving calling terminal, the department ID field value is the department ID to which the calling terminal A belongs, and the rearrangement sequence information is used for indicating the rearrangement position of the target user Y in the service queue of the moving calling terminal. After receiving the multicast message of the synchronization rearrangement message, the first floor switch forwards the multicast message from the GigabitEthernet 0 / 1 to the RP according to the bidirectional PIM protocol. After receiving the multicast message of the synchronization rearrangement message, the RP queries the multicast forwarding table maintained by the RP, determines that the department ID carried by the GigabitEthernet 0 / 2 is Department 1 and the calling terminal position ID is Floor 2, which are consistent with the field values of the routing positioning identifier in the synchronization rearrangement message, and then the RP forwards the multicast message of the synchronization rearrangement message from the GigabitEthernet 0 / 2, the second floor switch performs the same steps, and finally the calling terminal E and the calling terminal F receive the synchronization rearrangement message and add the target user Y into the queue maintained by each calling terminal according to the rearrangement sequence information. It should be noted that in actual application, the rearrangement sequence information can be set according to the number of users in the state display queue, if the calling terminal only displays 3 users, the target user Y can be added to the 4th position in the queue, so that the users waiting in the queue behind the target user Y will not feel that someone is cutting in line.
[0106] The embodiment of the present application also provides a door lock for cooperative calling. Figure 8 Fig. 8 is a block diagram of a door lock 800 for cooperative calling provided by an example embodiment, as shown in the figure, the calling terminal 800 comprises: Figure 8
[0107] an information storage unit 810, configured to store calling terminal information of itself, user data and a service queue constructed according to the user data;
[0108] an information processing unit 820, configured to execute the method 200 and determine to-be-output information;
[0109] an image acquisition unit 830, configured to acquire information of a target user;
[0110] an information output unit 840, configured to output the to-be-output information;
[0111] a communication unit 850, configured to realize a communication function of the door lock.
[0112] Reference Figure 8 The door lock shown can know that the technical scheme expands the door lock from a data display end to a collaborative door lock with edge intelligence technology by setting the door lock to include an information storage unit, an information processing unit, an image acquisition unit, an information output unit, and a communication unit, effectively reducing the dependence on manual intervention, improving the automation and intelligence level of queue updating, and realizing dynamic collaboration of the calling number management of multiple rooms.
[0113] In an illustrated embodiment, the image acquisition unit 830 includes one or more cameras, which can be disposed on the door lock body or off the door lock body. For example, the door lock body is fixed at the door of the room, the image acquisition unit 830 includes multiple cameras, part of which are disposed inside the room for acquiring off-site identity information of the target user, part of which are disposed outside the room, and part of which can be distributed in different areas outside the room, such as cameras disposed on the door lock body for acquiring near-field identity information of the target user, and cameras disposed in the waiting area outside the room for acquiring positioning information of the target user.
[0114] In an illustrated embodiment, the information output unit 840 includes a display screen and a voice playback module, which can be disposed on the door lock body or off the door lock body. For example, the door lock body is fixed at the door of the room, the display screen is disposed on the door of the room, and the voice playback module is disposed on the door lock body.
[0115] In an illustrated embodiment, the information processing unit 820 is configured to determine the to-be-output information according to the information acquisition rule of the target user, such as determining the service invitation as the to-be-output information when the target user meets rule one, and determining the to-be-output information according to the service queue, such as determining the state display queue in the service queue as the to-be-output information.
[0116] In an illustrated embodiment, the communication unit 850 includes multiple communication modules supporting different communication protocols, for near-field wireless communication with a service terminal in the room, near-field wireless communication with a room door lock, and wireless communication with an access device (such as a switch or wireless router) in the area where the door lock belongs. For example, the information processing unit 820 generates an unlocking information and sends it to the communication unit 850 when the state of the target user changes to in-service or service ends, the communication unit 850 sends the unlocking information to the room door lock to control the room door lock to switch the door lock state to unlocked; or, the information processing unit 820 generates a collaborative processing message and sends it to the communication unit 850, the communication unit 850 sends the collaborative processing message to the access device in the area where the door lock belongs, and the access device forwards the collaborative processing message to the target door lock.
[0117] The embodiments of the present application also provide a cooperative call-in system. Figure 9 FIG. 9 is a block diagram of a cooperative call-in system 900 according to an example embodiment, which is provided by an example embodiment, as shown in the figure, the system 900 comprises: a plurality of call-in terminals 920 and one or more routing nodes 930, the plurality of call-in terminals 920 correspond to different rooms respectively, and each call-in terminal 920 is configured to implement the method 200; and the one or more routing nodes 930 are configured to implement communication between the plurality of call-in terminals 920. Figure 9
[0118] In an example embodiment, any routing node 930 is configured to: receive and identify a multicast message; in a case that the multicast message carries a routing locator identifier, determine a forwarding message corresponding to the multicast message according to a message type of the multicast message, and determine an out interface corresponding to the forwarding message according to the routing locator identifier; and send the forwarding message through the out interface.
[0119] In an example embodiment, any routing node 930 is further configured to: in a case that a join message sent by a downstream routing node is received, save call-in terminal information carried by the join message in an out interface of a multicast forwarding table maintained by the routing node, and query the multicast forwarding table of the routing node according to service information in the call-in terminal information; in a case that the out interface of the multicast forwarding table further saves other call-in terminal information with the same service information, generate a reverse join message, the reverse join message carries the other call-in terminal information with the same service information; and send the reverse join message to the downstream routing node, so that the downstream routing node saves the other call-in terminal information in an in interface of a multicast forwarding table maintained by the downstream routing node.
[0120] In an example embodiment, the system 900 further comprises a call-in management platform 910, the call-in management platform 910 is configured to: obtain user data and call-in terminal information, the user data comprises service reservation information; determine serviceable call-in terminals from the plurality of call-in terminals according to the service reservation information and the call-in terminal information; and distribute the user data to all serviceable call-in terminals respectively.
[0121] Figure 10 FIG. 1 is a schematic diagram of an electronic device according to an example embodiment, as shown in the figure, the electronic device comprises: a processor 1001, a memory 1002, a communication interface 1003, and a power supply 1004. Figure 10 At the hardware level, the device includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, a hardware acceleration device 1010, and a non-volatile memory 1012, and of course can also include other hardware required by functions. One or more embodiments of the present application can be implemented in a software manner, such as reading a corresponding computer program from the non-volatile memory 1012 into the memory 1008 by the processor 1002 and then running. Of course, in addition to the software implementation, one or more embodiments of the present application do not exclude other implementation manners, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the above processing flow is not limited to each logic unit, but can also be hardware or a logic device.
[0122] Corresponding to the above-mentioned embodiments of the cooperative calling method for the calling terminal, the present application also provides corresponding device embodiments. Please refer to Figure 11 The cooperative calling device can be applied to the calling terminal as described in any of the above embodiments, and in the case of the electronic device as shown in Figure 10 , the cooperative calling device can be specifically applied to the electronic device as shown in Figure 10 to implement the technical solutions of the present application. The cooperative calling device can include a user determination unit 1101, an information collection unit 1102, a queue management unit 1103, and a synchronization control unit 1104, wherein:
[0123] The user determination unit 1101 is configured to determine a target user in the service queue;
[0124] The information collection unit 1102 is configured to collect information of the target user according to a corresponding information collection rule determined according to the queue attribute of the target user, and obtain an information collection result of the target user;
[0125] The queue management unit 1103 is configured to update the service queue according to the changed state of the target user in the case where it is determined that the state of the target user has changed according to the information collection result;
[0126] The synchronization control unit 1104 is configured to generate a cooperative processing message according to the changed state of the target user and send it to other calling terminals in the cooperative calling system, so as to synchronize the update of the service queue maintained by the other calling terminals.
[0127] For the apparatus embodiments, since they basically correspond to the method embodiments, the relevant parts are described in the part of the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purposes of the present application. Those skilled in the art can understand and implement without creative labor.
[0128] Correspondingly, the present application also provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method according to any one of the above embodiments.
[0129] Correspondingly, the embodiments of the present application also provide a computer program product configured to execute the method according to any one of the above embodiments.
[0130] The system, apparatus, module or unit illustrated in the above embodiments can be specifically implemented by a computer chip or entity, or by a product with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
[0131] In a typical configuration, the computer includes one or more processors (CPU), input / output interface, network interface and memory.
[0132] The memory can include non-persistent memory in computer readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer readable medium.
[0133] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology for storing information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, disk storage, quantum memory, graphene-based storage medium or other magnetic storage device, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.
[0134] It is also important to note that the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.
[0135] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown or sequential order in order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.
Claims
1. A collaborative calling method, characterized in that: The method is applied to a collaborative calling system, which includes multiple calling terminals and a calling management platform. The calling management platform sends user data of a user to a calling terminal in the same area as the location where the user picked up the number. The multiple calling terminals respectively maintain a service queue containing the user data. Any of the multiple calling terminals performs the following steps: Determining target users in the service queue; Determine a corresponding information collection rule according to the queue attribute of the target user to collect information from the target user, and obtain the information collection result of the target user; When it is determined according to the information collection result that the status of the target user has changed, updating the service queue according to the changed status of the target user and generating a collaborative processing message; Sending the collaborative processing message to other calling terminals in the system so that the other calling terminals synchronously update the service queues they maintain; The determining of a corresponding information collection rule according to the queue attribute of the target user to collect information from the target user and obtaining the information collection result of the target user includes: If the queue attribute of the target user includes a queue status of "passed", relocation information is collected through a remote field collection method, the relocation information including relocation terminal information, and location matching is performed based on the relocation terminal information and the current calling terminal information to obtain the information collection result of the target user, where the relocation terminal refers to the calling terminal located at the target user; The determining, based on the information collection result, that the status of the target user has changed includes: When the queue status of the target user is passed and the information collection result indicates that the relocation terminal information does not match the current calling terminal information, determine the first position matching degree between each other calling terminal with the same service ID as the current calling terminal and the target user, and the second position matching degree between the target user and the current calling terminal. When the first position matching degree is greater than the second position matching degree, determine that the status of the target user has changed and change the status of the target user from passed status to re-queued status.
2. The method according to claim 1, characterized in that The information collection rules include at least one of the following rules: Collecting the presence identity information by near-field collection, including: sending a service invitation message and collecting the presence identity information by using an image collection device of the current calling terminal within a first preset time; Collecting the departure identity information through near-field collection, including: collecting the departure identity information through the image collection device of the current calling terminal; Collecting relocation information through far-field collection, including: collecting relocation information through message broadcasting; The relocation information is collected through a collaborative collection method, including: collecting positioning information through an image collection device of the current calling terminal, and collecting relocation information through message broadcasting when the current calling terminal fails to locate the target user within a second preset time.
3. The method according to claim 2, characterized in that The user data includes biometric registration information, and the determining of corresponding information collection rules based on the queue attributes of the target user to collect information from the target user further includes: When the queue attribute of the target user includes a queue position being a call position, collecting presence identity information through a near-field collection method, the presence identity information including facial feature detection information and / or iris feature detection information, and authenticating the presence identity information based on the biometric registration information; When the queue attribute of the target user includes a queue status of "in service", collecting departure identity information through a near-field collection method, the departure identity information including facial feature detection information and / or iris feature detection information, and authenticating the departure identity information according to the biometric registration information; When the queue attributes of the target user include that the queue position is a passed-number warning position, relocation information is collected through collaborative collection. The relocation information includes facial feature detection information and relocation terminal information, and position matching is performed based on the relocation terminal information and the current calling terminal information.
4. The method according to claim 3, characterized in that The determining, based on the information collection result, that the status of the target user has changed further includes: If the queue position of the target user is a calling position and the information collection result indicates that the target user has passed authentication, determining that the status of the target user has changed and changing the status of the target user from a waiting state to a service state; When the queue position of the target user is a calling position and the information collection result indicates that the target user is not authenticated, determining that the status of the target user has changed and changing the status of the target user from a waiting state to a passed state; When the queue status of the target user is in service and the information collection result indicates that the target user has passed authentication, it is determined that the status of the target user has changed and the status of the target user is changed from in service to service-end.
5. The method according to claim 3, characterized in that: The queue attribute of the target user includes a queue position being a queue overage warning position, and the method further includes: When the information collection result indicates that the relocation terminal information does not match the current calling terminal information, it is determined that the target user meets the warning conditions, and a missed call warning message is sent to the calling management platform so that the calling management platform prompts the target user that there is a risk of missed call.
6. The method according to claim 1, characterized in that The multiple calling terminals join the same multicast group, and the updating of the service queue according to the changed state of the target user and the generating of the collaborative processing message include: adding a routing location identifier to the message content of the collaborative processing message; The step of sending the collaborative processing message to other calling terminals in the system includes: The collaborative processing message is encapsulated into a multicast message and sent to the multicast group; wherein, the multicast message instructs the routing node corresponding to the multicast group to determine the outgoing interface of the multicast message according to the routing location identifier, so as to send the collaborative processing message to each other calling terminal that matches the routing location identifier.
7. The method according to claim 6, characterized in that Adding a routing location identifier to the message content of the collaborative processing message includes: Determine field information of the routing location identifier, where the field information includes a service field and a terminal location field; The field value of the service field is determined according to the service information currently served by the calling terminal, and the field value of the terminal location field is determined according to the changed state of the target user.
8. The method according to claim 1, characterized in that: The method further comprises: Generate a join message for the multicast group based on the current calling terminal information; The join message is sent to the multicast group, so that the routing node corresponding to the multicast group saves the current calling terminal information carried by the join message in the table entry outbound interface of the multicast forwarding table for matching with the routing location identifier carried by the multicast message.
9. A door lock for collaborative calling, characterized in that: The door lock comprises: An information storage unit, used to store its own calling terminal information, user data, and a service queue constructed based on the user data; An information processing unit, configured to execute the method according to any one of claims 1 to 8 and determine information to be output; An image acquisition unit, used to collect information about the target user; An information output unit, configured to output the information to be output; The communication unit is used to realize the communication function of the door lock.
10. A collaborative calling system, characterized in that: The collaborative calling system includes: A plurality of call terminals, each corresponding to a different room, wherein any one of the plurality of call terminals is configured to implement the method according to any one of claims 1 to 8; One or more routing nodes are used to implement communication between the multiple call terminals.
11. The system according to claim 10, characterized in that: The routing node is used to: Receive and identify multicast messages; In the case of identifying that the multicast message carries a routing locator identifier, determining a forwarding message corresponding to the multicast message according to a message type of the multicast message, and determining an outgoing interface corresponding to the forwarding message according to the routing locator identifier; The forwarding message is sent through the outgoing interface.
12. The system according to claim 11, characterized in that: The routing node is further configured to: Upon receiving a join message sent by a downstream routing node, the calling terminal information carried by the join message is saved in the outbound interface of the multicast forwarding table maintained by the node, and the multicast forwarding table of the current routing node is queried based on the service information in the calling terminal information; If the outbound interface of the multicast forwarding table also stores information of other calling terminals with the same service information, generating a reverse join message, wherein the reverse join message carries information of other calling terminals with the same service information; The reverse join message is sent to the downstream routing node, so that the downstream routing node stores the other calling terminal information in the entry input interface of the multicast forwarding table maintained by the downstream routing node.
13. The system according to claim 10, characterized in that: It also includes a call number management platform, which is used to: Acquiring user data and calling terminal information, wherein the user data includes service reservation information; Determining a serviceable calling terminal from the plurality of calling terminals according to the service reservation information and the calling terminal information; The user data is sent to each service call terminal respectively.
14. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to implement the method according to any one of claims 1 to 8.
15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.
16. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 8 is implemented.
Citation Information
Patent Citations
Self-service number-arranging method and device, medium, electronic equipment and self-service number-arranging system
CN109215208A
Catering management method and system, equipment and storage medium
CN114154665A