Internal communication management system

Abstract

An internal communication management system for managing operations and configurations, the system comprising an internal communication device, a peripheral device, an electronic processor configured to perform a bridging service configured to enable communication between the internal communication system and a computer over a connection. The computer is configured to: connect to the internal communication device via the connection; generating a user interface in response to receiving the first input via the user interface; assigning the peripheral devices to the ports; and assigning an identification to the peripheral device in response to receiving the second input via the user interface.

Description

[0001] Related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 582,682, filed September 14, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The embodiments, examples, and aspects described herein relate in particular to internal communication devices and methods for managing and operating internal communication devices. Summary of the Invention

[0004] Internal communication devices are typically standalone voice communication systems. Among other uses, they are also employed by special events production teams. For example, television staff use internal communication devices during sporting events. Some internal communication devices consist of a master station and multiple substations interconnected by a communication network that facilitates short-range, two-way audio and optional video communication. The master station provides control functions for initiating and receiving calls, configuring communication settings, and managing access control features, while the substations provide communication junctions and are strategically located within defined areas, allowing users to interact, exchange information, and potentially verify identity. Attached Figure Description

[0005] Figure 1A It is a schematic diagram based on some aspects of the internal communication device.

[0006] Figure 1B It is a schematic diagram of the peripheral equipment of the internal communication device in some aspects.

[0007] Figure 2 It is based on some aspects Figure 1A A schematic diagram of alternative configurations for the internal communication device.

[0008] Figure 3 It is a diagram of a user interface for an internal communication device, based on some aspects.

[0009] Figure 4 It is a diagram of a user interface for an internal communication device, based on some aspects.

[0010] Figure 5 It is a diagram of a user interface for an internal communication device, based on some aspects.

[0011] Figure 6 It is based on some aspects Figure 1A A block diagram of the software architecture of the internal communication device.

[0012] Figure 7 It is based on some aspects Figure 1AA block diagram of the software architecture of the internal communication device.

[0013] Figure 8 The diagram shows the configuration based on several aspects. Figure 1A A flowchart of the process of the internal communication device. Detailed Implementation

[0014] Before explaining any aspect, feature, or instance in detail, it should be understood that such aspect, feature, or instance in its application is not limited to the details of the construction and arrangement of the components set forth in the following description or illustrated in the following figures. Other instances are possible and can be practiced or performed in various ways.

[0015] Furthermore, it should be understood that the wording and terminology used herein are for descriptive purposes and should not be considered restrictive. The terms “installation,” “connection,” and “coupling” are used broadly and include both direct and indirect installation, connection, and coupling. Further, “connection” and “coupling” are not limited to physical or mechanical connections or couplings and may include direct or indirect electrical connections or couplings. Moreover, electronic communication and notification can be performed using any known means, including wired connections, wireless connections, etc.

[0016] Unless the context clearly indicates otherwise, the articles “a,” “an,” and “the” should not be interpreted as meaning “one” or “only one.” Instead, these articles should be interpreted as “at least one” or “one or more.” Similarly, when the terms “the” or “said” are used to refer to a noun previously introduced by the indefinite articles “a” or “an,” “the” and “said” mean “at least one” or “one or more,” unless the usage clearly indicates otherwise.

[0017] It should also be understood that, in various embodiments, multiple hardware and software-based devices and multiple different structural components may be utilized. Aspects, features, and examples may include hardware, software, and electronic components or modules, which, for the purposes of discussion, may be illustrated and described as if most components were implemented solely in hardware. However, those skilled in the art will recognize, based on reading this detailed description, that in at least one instance, the electronic-based aspects of the present invention may be implemented in a manner executable by one or more processors (e.g., stored on a non-transitory computer-readable medium).

[0018] Additionally, while some of the accompanying drawings illustrate hardware and software located within a particular device, these descriptions are for illustrative purposes only. In some embodiments, the illustrated components may be combined or divided into separate software, firmware, and / or hardware. For example, logic and processing may be distributed across multiple electronic processors, rather than residing in and being executed by a single electronic processor. Regardless of how the hardware and software components are combined or divided, they may reside on the same computing device or be distributed across different computing devices connected via one or more networks or other suitable communication links.

[0019] Therefore, in the claims, if the apparatus or system is claimed to include, for example, an electronic processor or other element configured in a certain way, for example, to make multiple determinations, then the claim or claim element should be interpreted as referring to one or more electronic processors (or other elements), wherein any one of the one or more electronic processors (or other elements) is configured as claimed, for example, to make some or all of the multiple determinations. To reiterate, these electronic processors and processes can be distributed.

[0020] For ease of description, some or all of the example systems presented herein are illustrated using a single sample of each of their components. Some examples may not describe or illustrate all components of the system. Other instances may include more or fewer of each illustrated component, may combine some components, or may include additional or alternative components.

[0021] Before providing additional details on various aspects, features, and examples, a brief overview of internal communication devices (sometimes referred to as internal communication systems) is provided. Generally, an internal communication device comprises multiple hardware and software elements connected within a network. Many internal communication systems include a master station, multiple substations (or hardware peripherals configured to send / receive automatic signals within the internal communication system), communication channels, audio and video components, call initiation devices, two-way communication devices, and access control features. The master station acts as a control unit with advanced functions for initiating and receiving calls, managing communication settings, and configuring system access controls or settings / features. Substations are distributed throughout a defined area, such as a stadium or news broadcasting facility, and are capable of communicating with the master station and other substations.

[0022] A communication channel establishes a communication link between the master station and the substations. Depending on the application, wired and / or wireless technologies can be used to transmit audio and video signals. Call initiation is achieved through an activation mechanism on the substation or via the master station, triggering an audible alarm upon call initiation. In many internal communication systems, two-way communication is achieved through integrated microphones and speakers. Users at the master station or substation can communicate verbally by speaking into the microphone, transmitting audio signals between the caller and receiver. The internal communication systems detailed below encompass applications in various environments and improve existing systems by enhancing the features of the master station and substations and providing an improved user interface.

[0023] Figure 1A An internal communication system 100 is schematically illustrated according to some aspects. In some cases, the internal communication system 100 includes a management application 105, a bridging service 110, and an internal communication device 115. In some cases, the internal communication device 115 is illustrated as a device network (e.g., Figure 1B (As illustrated), and the management application 105 enables the configuration of various devices connected to the internal communication device 115. For example, as described in more detail below, the management application 105 can configure a keypad used on an assigned port, assign labels or descriptors to the keypad, or similar customizable configurations.

[0024] The management application 105 runs or executes on the computer 120. Incidentally, it should be noted that, as used herein, "run" and "execute" are used interchangeably when referring to various software applications. The computer 120 includes an electronic processor 125, an input / output interface 130, and a memory 135. In other examples, the electronic processor 125 may be implemented as a microcontroller (with the memory 135 on the same chip). In other examples, the electronic processor 125 may be implemented using multiple processors.

[0025] Additionally, the electronic processor 125 may be implemented partially or entirely as, for example, a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc., and may not require memory 135 or may modify that memory accordingly. In some examples, memory 135 includes non-transitory computer-readable storage that stores instructions received and executed by the electronic processor 125 to perform the methods described herein. In one example, memory 135 stores a management application 105. Input / output interface 130 may include one or more input mechanisms and one or more output mechanisms (e.g., general purpose input / output (GPIO), analog input, digital input, etc.). Bridging service 110 runs on computer 120 or a separate server (e.g., server 175, as described in detail below).

[0026] The management application 105 includes application components. In one example, these components include a software architecture 145 and an application programming interface (API) 150. In some cases, the software architecture 145 is an arrangement of components that enables the functionality of the management application 105, such as... Figures 6 to 7 As described in detail below. API 150 utilizes protocol link 155 (e.g., a WebSocket link) to provide communication between management application 105 and bridging service 110. Protocol link 155 is a computer communication protocol that provides a full-duplex communication channel over a single Transmission Control Protocol (TCP) connection. The WebSocket protocol supports interaction between a user interface (such as a web browser) and the server. Full-duplex communication is more cost-effective than half-duplex communication (such as HTTP polling). Bridging service 110 includes API 150, middleware 160, and library 165. Middleware 160 is a service that exists outside of management application 105. This allows the service to run in a variety of configurations. For example, the bridging service can run on a client desktop (e.g., computer 120), a centralized server, and / or a client desktop acting as a self-organizing server.

[0027] Library 165 is responsible for establishing and maintaining communication sessions with internal communication device 115. Library 165 includes modules that provide access to internal communication settings and properties. When management application 105 connects to bridging service 110, this module initializes and connects to internal communication device 115 via User Datagram Protocol (UDP 170). This connection includes determining authorization for internal communication device 115, such as user authorization. Once authorization is granted, the module then establishes and maintains the session until it is closed and begins processing data between management application 105 and internal communication device 115. Architecture 145 hosts the user interface of management application 105. In some examples, architecture 145 includes a unidirectional data flow within architecture 145. This detail will be further described below, and... Figure 6 The diagram shows the bridging service 110. In some cases, bridging service 110 is stored and run by server 175. Server 175 includes an electronic processor 180, an input / output interface 185, and memory 190. The electronic processor 180, input / output interface 185, and memory 190 may be structurally similar to the examples provided with respect to electronic processor 125, input / output interface 130, and memory 135. In some cases, bridging service 110 is stored and run by computer 120. In some cases, some functions of bridging service 110 are performed by server 175, while others are performed by computer 120.

[0028] API 150 handles all messaging on protocol link 155. For example, API 150 handles API requests initiated by clients (e.g., requests sent from management application 105 or computer 120) and services configured to fulfill API requests (e.g., bridging service 110 or server 175). API 150 also handles inbound responses and updates. API 150 communicates with library 165. Components of library 165 are implemented using entity objects or entities. An entity is a pure data storage object and does not contain any logic. In some examples, an entity contains status information about various states of management application 105. Status information includes various visual states in management application 105, such as dialog boxes, pop-ups, error windows, connection status, and application version strings. All entities are stored and managed by an entity database. Instances of the entity database allow for simple and fast retrieval of entities. Each entity can be uniquely addressed using a universally unique identifier (UUID). The entity's UUID and any other initial values ​​are set when the entity is created. After creation, it is attached to the entity database. In some cases, updates to state information in the model will immediately update elements of the management application 105's user interface. In others, state is handled via boolean values ​​in the model, while still others contain various strings and states that are crucial to the application or visual elements of the management application 105. Visual elements in Figures 3 to 5 The diagram is shown in the image below and described in detail.

[0029] Figure 1B This is a schematic diagram of peripheral devices for an internal communication device, based on some aspects. In the example shown, the internal communication device 115 is connected to peripheral devices, such as keypad 191, via a wired or wireless connection. In some cases, multiple peripheral devices are connected to the internal communication device 115 simultaneously. For example, the first keypad 191 and the second keypad 192 can be connected to the internal communication device 115 simultaneously. The connection of each keypad 191, 192 is configured and permitted by the management application 105, as described in detail below. In some cases, peripheral devices are configured to communicate with each other in addition to communicating with the internal communication device 115. For example, the third keypad 193 and the fourth keypad 194 can be configured to communicate with the internal communication device 115 and communicate directly with each other. Additional peripheral devices can also be connected to the internal communication device 115, including digital waistbands, access points, in-ear audio devices, or dedicated devices. For example, a user can wear a digital waistband, allowing them to move while connected to the internal communication device 115.

[0030] A keypad (such as keypad 191) includes multiple key assignments, each for each physical listener key and talk key on the keypad. Additional key assignments may also exist, and a typical keypad may have 2 to 36 key assignments. In some cases, a keypad will have 16 key assignments. In other cases, a keypad will have 32 key assignments. By selecting one or more of the key assignments, the user of the keypad can select the functions they prefer to enable. For example, when a keypad user activates a specific listener key, the keypad receives audio from the resource associated with the key assignment. The user will then hear a mixture of all the audio corresponding to the activated listener key through the keypad speaker and / or connected headphones. Similarly, when a keypad user activates a specific talk key, audio from their microphone (via a microphone attached to the keypad or via connected headphones) is sent to internal communication device 115, where it is routed to all ports / keypads currently listening to that resource. In some cases, the talk key has multiple levels, allowing a single physical talk key to enable multiple resources. Figures 3 to 5 The document describes the keypad assignments, call keys, and listen-in keys in more detail.

[0031] Figure 2 yes Figure 1A A schematic diagram of an alternative configuration of system 200 for the internal communication system 100. As previously described with respect to system 100, system 200 includes a management application 105, a bridging service 110, and an internal communication device 115. System 200 illustrates multiple management applications 105 executing on multiple computers 205, and a bridging service 110 executing on server 210. In some cases, the multiple computers 205 are similar to computer 120, and each computer includes an electronic processor, input / output interface, and memory. In some cases, server 210 is similar to server 175 and also includes an electronic processor, input / output interface, and memory as previously described. Additionally or alternatively, computers 120, 205 may perform the tasks of server 210 and perform bridging service 110.

[0032] Figure 3This is an illustration of a user interface 300 for an internal communication device, based on several aspects. The user interface 300 (also referred to as a window) includes a main title bar 305, an internal communication manager 310 (also referred to as an internal communication manager window), and a keypad editor 315 (also referred to as a keypad editor window). The management application 105 includes action handlers associated with API 150. The main title bar 305 includes a button 320 and an information array 325 located to the left of the main title bar 305. The selection button 320 displays a main application menu for opening new widgets and saving / loading custom widget layouts. The information array 325 may include connection information, such as address information of one or more peripheral devices (such as a keypad), or the connection status of devices connected to the internal communication device 115.

[0033] The internal communication manager 310 provides the user of the management application 105 with a display of port 330 and its properties. The properties of port 330 are provided in a list, and the user is allowed to configure port 330 (in... Figure 5 (Further illustration) allows for searching, categorizing, and filtering. In some cases, the internal communication manager 310 displays a list of additional resource types available to the internal communication device 115, such as shared lines, special lists, interruptible backflips (IFB), IFB special lists, general inputs / outputs, etc. The internal communication manager 310 additionally allows port 330 information to be transmitted to the keypad editor 315. In some embodiments, the internal communication manager 310 comprises multiple components, including a search bar 335 where the user can search by name, IP address, or other filters. The search bar 335 updates results in real time as the user types, allowing the editor to refresh rapidly during use. The search bar 335 examines the text in the search bar 335 and then combines it with an action handler to display output corresponding to the input text. The internal communication manager 310 also includes a row of additional buttons with different functions.

[0034] The filter button 340 allows users to filter results displayed on the keypad editor 315 (e.g., by port 330 used, resource type, etc.). The filter button 340 may include additional drop-down options, where the filter list dynamically expands or collapses as needed based on the application window size into a drop-down menu for the filter button 340. For example, any port 330 can be selected in the list view, and selecting one or more ports from the list allows users to drag and drop selections throughout the management application 105. Once selected in the keypad editor 315, any port in the resource list view can also be dragged and dropped to configure and interact with the value of the port 330. Values ​​may include, for example, connection status, live status, group status, tags, etc. Additionally, the internal communication manager 310 may include a matrix filter button that allows users to filter resources by the keypad they are connected to, whether via a remote or local connection. In some examples, the matrix filter button is only displayed when connected to a supported keypad.

[0035] Figure 4 It is based on some aspects Figure 3 Alternative illustrations of the user interface 400 are provided. The user interface 400 includes a keypad editor 315 as previously described and additional elements. The user interface 400 includes assigned ports 330, which may include labels for organizing peripheral devices connected to the internal communication device 115. For example, when the internal communication device 115 is configured for use in a media studio, group labels may include identifiers for the director 405, camera 410, sound system 415, cast and crew 420, or other such identifiers. The user interface 400 also includes separate identifiers for the call key 425 and the listen key 430. Users of the interface 400 can configure the current state of key options for each call and listen key. As shown, each key option assignment has a color to facilitate identification of the assigned group. In some examples, this color assignment may be toggled via the keypad editor 315. Assignments may also be shown / hide, filtered (e.g., by utilizing filter buttons 340), searched, or edited by the user.

[0036] Assignments can be entered directly by the user or copied / pasted from a previously assigned port 330. Additionally, assignments can be copied between the keypanel editor 315 windows. Key assignments can also be dragged and dropped from one window to another, or from one port 330 to another, or from one key assignment to another. For example, a user can partially or completely copy the keypanel editor 315 window or key assignments. If a specific key is restricted, the user is prevented from changing the assignment directly from the keypanel editor 315. For example, when the listen key or call key is restricted, the user of the keypanel cannot change the assignment. In some cases, the volume level illustrated in the keypanel editor 315 affects the volume of the resource associated with the listen key 430 during point-to-point or shared-line listening. In this case, the restriction does not affect the audio sent to other keypanels. In some cases, the user can change the state of one or more assignments in the assignment. For example, a user can mute / unmute the actor 420, or modify the volume of the call key or listen key assignment. Modifications to any or all assignments in the keypanel editor 315 can be saved and reloaded later.

[0037] Different assignments can include different levels of usage. For example, the call key 425 identifier allows one keypad (such as keypad 193) to send audio broadcasts to another keypad (such as keypad 194), and the listen key 430 identifier allows receiving audio broadcasts. The same keypad can have both call key and listen key assignments simultaneously, or only one assignment. For example, the director 405 assignment could enable the director 405 keypad to both send and receive broadcasts. Another assignment (such as camera 410) might only be able to receive broadcasts. In some examples, more than one keypad is assigned to the same group label (or group). For example, there can be more than one keypad with the camera 410 identifier. The group label is determined by the user of the management application 105 and can be customized by the user.

[0038] Figure 5 It is based on some aspects Figure 3Alternative illustrations of the user interface 500. As previously described, the internal communication manager 310 includes a search bar 335 that allows the user to search the management application 105. For example, the user can search for available ports 330 to assign specific ports to peripherals connected to the internal communication device, such as the keypad 191. The user can search by name, IP address, port, or other filters. In some cases, the search bar updates results in real time as the user types, rather than requiring the user to press "enter" or a similar key. During a query, the search examines the text in the search bar 335 and then works as previously described. Once complete, the search results populate the internal communication manager 310. For example, if the user searches for "dir," (e.g., an abbreviation for "director"), the search results will return the directory letters of "dir" as well as any descriptions that include at least "dir."

[0039] Figure 6 It is based on some aspects Figure 1A This is a block diagram of the software architecture 600 of the internal communication device. As previously described, architecture 145 hosts the user interface of the management application 105, such as the previously illustrated user interfaces 300 and 400. In some examples, architecture 145 includes unidirectional data flow within the architecture. Architecture 145 includes five main components: view 605, action 610, action handler 615, service 620, and model 625. View 605 contains elements of user interface 300 and 400, such as windows or pages displaying the internal communication manager 310. Action 610 is a command object generated from the user interface when the user makes a change to the user interface. Action handler 615 is a logical component that routes and processes action 610. Service 620 is a logical component that interacts with external systems (e.g., makes changes from management application 105 to internal communication device 115, or to one or more peripheral devices). Model 625 is a data object that stores information necessary for view 605, such as assigned port 330 or key identifiers.

[0040] For example, when a user interacts with view 605, view 605 propagates action 610 through action handler 615 to various models 625 that store data and logic for the management application 105. The affected view 605 is then updated based on changes to model 625. Action handler 615, model 625, and view 605 are independent nodes with different inputs and outputs. Action 610 is an object that contains new data and identifies attributes. As previously described, view 605, action handler 615, and model 625 communicate via a unidirectional data flow. Service 620 can be invoked from action handler 615, but communicates with the rest of the system only via action 610.

[0041] Figure 7 It is based on some aspects Figure 6 The extended block diagram of the 600 software architecture. As previously shown in Figure 6 As described and illustrated, architecture 145 includes view 605, action 610, action handler 615, service 620, and model 625. View 605 is the graphical portion of management application 105, which displays information and accepts input from the user. The elements of view 605 are the previously described user interface 300, main title 305, internal communication manager 310, and keypad editor 315. View 605 sends actions to action handler 615, which implements the logic required to process the triggered actions. In some examples, these actions include sending messages via API 150 based on certain events, or directly updating the state information of management application 105 in model 625.

[0042] Actions are provided to action handler 615 and originate from user interactions with view 605. All data flows through action handler 615. When an action handler receives action 610, action handler 615 executes the functions that model 625 has registered with action 610. Model 625 responds to any action 610 related to the state of the management application 105 that it maintains. Model 625 then emits change events to alert view 605 that a change has occurred in the data layer. In some cases, there are four action handlers: application action handler 705, resource finder action handler 710, port editor action handle 715, and API action handler 720. Application action handler 705 contains actions generated from the main window (e.g., opening or closing the application) or changes in the visibility state of application dialog boxes. For example, application action handler 705 may handle actions such as user interactions with main title 305, internal communication manager 310, or keypad editor 315, or actions 610 (e.g., opening or closing management application 105).

[0043] Resource finder action handler 710 includes actions 610 related to searching or filtering key-assignable resources, such as search queries generated from internal communication manager 310. These actions 610 are generated when a user searches with a text string, filters a port list using a resource type filter, or sorts a resource list view. Port editor action handle 715 generates actions 610 from keypad editor 315. Port editor action handle 715 includes actions 610, such as setting / changing individual fields in the keypad or assigning call key 425 and listen key 430. In some cases, API action handler 720 handles actions 610 associated with API 150. These actions 610 cover a wide range of functions in management application 105 and include managing the connection status of bridging service 110 and internal communication device 115, managing keypad authentication, and populating the state of management application 105 based on data received from API 150.

[0044] In some examples, service 620 is responsible for handling the logic of managing application 105. Service 620 performs actions 610, such as filtering and validating inbound data changes from view 605, creating new entities with default values, and setting relationships between entities. Each service in service 620 has an identifier for accessing service 620. For example, one service in service 620 is application settings service 722, which is responsible for reading and writing configuration files stored in storage 135. Application settings service 722 handles actions 610, such as opening settings files from specified file paths and saving settings files to specified file paths. Service 620 also includes API 150 service, which is responsible for handling requests and receiving updates from API 150 drivers. In some examples, service 620 is also responsible for handling external resources 745, such as application settings 750 from external settings managed by application 105.

[0045] Model 625 includes an application state model 725, an internal communication model 730, a resource model 735, and a port editor model 740. The application state model 725 handles state information, including various visual states within the management application 105 as previously described. The internal communication model 730 stores information about the keypad communicating with system 100, such as the keypad's connection status and device type. The keypad's connection status informs the management application 105 which states should be changed, for example, when a peripheral device (such as keypad 191) requires authentication, or if internal communication device 115 or keypad 191 is attempting to connect to the management application 105. The internal communication model 730 also stores information stored by keypad 191 itself, such as its description, frame / port count, or its maximum session. The internal communication model 730 also stores Boolean values ​​that determine whether settings on the keypad, such as text or single-code support, are enabled. Resource model 735 includes information about one or more resources in the internal communication device 115 resources (such as peripheral device type, configurable-length name of resource type, or description contained in resource model 735). Additionally, resource model 735 includes Boolean values ​​that store information about whether various attributes (such as key assignment) are enabled for a given resource. Port editor model 740 stores information about which port 330 and settings page are currently active within management application 105, and also stores information about currently connected key assignments, such as call and listener assignments within key panel editor 315. Utility 755 is responsible for logging, such as changes made via view 605 or actions 610 performed by action handler 615.

[0046] Figure 8 This is the configuration shown in the diagram. Figure 1AA flowchart of process 800 for an internal communication device. Process 800 includes, for example, connecting (805) a management application 105 to an internal communication device 115 via bridging service 110 as described above. In some cases, management application 105 is also connected to a peripheral device, such as a keypad 191. In some cases, more than one peripheral device is connected simultaneously or sequentially. Process 800 includes assigning (810) a port 330 to a peripheral device via management application 105. As previously described, the assignment of port 330 enables the peripheral device to communicate with other connected peripheral devices. Process 800 includes assigning (815) an identifier to a peripheral device via management application 105. For example, an identifier may include a call key or a listen key. The identifier can be copied from a previously configured peripheral device. For example, a user can drag and drop an identifier onto one or more peripheral devices simultaneously. Optionally or additionally, process 800 includes assigning (820) a tag to a peripheral device. The tag can be any previously described assignment, such as a camera. Optionally, a tag can also be copied, dragged, dropped, or moved from one peripheral device to another via management application 105. Process 800 also includes enabling (825) the operation of peripheral devices based on previous assignments (810, 815, 820). For example, keypad 191 can send and / or receive audio broadcasts based on one or more of the assignments (810, 815, 820). Process 800 can also be used to configure additional peripheral devices such that the additional peripheral devices can communicate with each other or with a specific peripheral device among other peripheral devices connected via internal communication device 115.

[0047] Therefore, this paper provides, in particular, systems and methods for internal communication systems.

Claims

1. An internal communication system, comprising: intercom; Peripheral equipment; as well as An electronic processor configured to perform a bridging service, the bridging service being configured to enable communication between the internal communication device and a computer via a connection; The computer is configured as follows: Connected to the internal communication device via the connection; Generate user interface; In response to receiving a first input via the user interface, the peripheral device is assigned to the port; as well as In response to receiving a second input via the user interface, an identifier is assigned to the peripheral device.

2. The system of claim 1, wherein the computer is further configured to enable operation of the peripheral device based on the assigned port and the assigned identifier.

3. The system according to any one of claims 1 to 2, wherein the operation of the peripheral device includes a call function and a listening function.

4. The system according to any one of claims 1 to 3, wherein the computer is further configured to perform the bridging service.

5. The system according to any one of claims 1 to 4, wherein the electronic processor is located on a server separate from the computer.

6. The system according to any one of claims 1 to 5, wherein the user interface includes an internal communication manager window and a key panel editor window.

7. The system according to any one of claims 1 to 6, wherein the first input is a drag-and-drop function.

8. The system according to any one of claims 1 to 7, wherein the second input is a user-defined tag for the peripheral device, and wherein the identifier includes the user-defined tag.

9. The system according to any one of claims 1 to 8, wherein the peripheral device is a keypad or a waist pack.

10. The system according to any one of claims 1 to 9, the system further comprising a first peripheral device and a second peripheral device, and wherein the computer is further configured to: In response to receiving a first input via the user interface, the first peripheral device is assigned to the first port; and In response to receiving a second input via the user interface, the second peripheral device is assigned to a second port, wherein the second input is a drag-and-drop function.

11. The system according to any one of claims 1 to 10, wherein the identifier includes a listening key and a call key.

12. A method for activating an internal communication device, the method comprising: Connecting internal communication devices to a computer, including an electronic processor, via a Transmission Control Protocol (TCP) connection; The electronic processor assigns peripheral devices to the ports; as well as The peripheral device is assigned an identifier via the electronic processor.

13. The method according to claim 12, wherein the method further comprises: The operation of the peripheral device is enabled via the electronic processor, based on the assigned port and the assigned identifier.

14. The method according to any one of claims 12 to 13, wherein the operation of the peripheral device includes a call function and a listening function.

15. The method of any one of claims 12 to 14, the method further comprising performing a bridging service via the electronic processor, wherein the bridging service is configured to enable communication between the internal communication device and the computer via a connection.

16. The method according to any one of claims 12 to 15, wherein the electronic processor is located on a server separate from the computer.

17. The method according to any one of claims 12 to 16, the method further comprising: It provides a user interface that includes an internal communication manager window and a key panel editor window; as well as Receive user input, wherein the user input is a drag-and-drop function.

18. The method according to any one of claims 12 to 17, wherein the peripheral device is a keypad or a waist bag.

19. An internal communication system, comprising: intercom; First peripheral equipment; Second peripheral equipment; as well as An electronic processor configured to perform a bridging service, the bridging service being configured to enable full-duplex communication between the first peripheral device, the second peripheral device, and a plurality of computers via a Transmission Control Protocol (TCP) connection; At least one of the plurality of computers is configured to: Connect the first peripheral device to the internal communication device; Connect the second peripheral device to the internal communication device; Generate user interface; In response to receiving a first input via the user interface, the first port is assigned to the first peripheral device; In response to receiving a second input via the user interface, the second port is assigned to the second peripheral device; In response to receiving a third input via the user interface, at least one identifier is assigned to the first peripheral device, the identifier including a listening key and a call key; In response to receiving a fourth input via the user interface, at least one identifier is assigned to the second peripheral device, the identifier including a listening key and a call key; as well as Based on the assigned port and at least one assigned identifier, enable at least one operation of the first peripheral device and the second peripheral device.

20. The system of claim 19, wherein at least one of the first input, the second input, the third input, and the fourth input is a drag-and-drop function.

Images