Near field communication equipment management control method and device and vehicle

Abstract

The invention is suitable for the technical field of cabin control, and provides a management control method and device for near field communication devices and a vehicle, the method and device are applied to the vehicle, the vehicle is connected with a plurality of near field communication devices, each near field communication device connected with the vehicle corresponds to a flexible control ball, and the flexible control balls are displayed on a flexible control ball control interface. In response to the received vehicle control instruction, determining a target flexible control ball which sends the vehicle control instruction; according to a preset control function authority of a target near field communication device corresponding to the target spirit control ball, whether the target near field communication device has an operation authority of a vehicle control instruction is judged; and when it is determined that the target near field communication equipment has the operation authority of the vehicle control instruction, executing the vehicle control instruction. According to the invention, the problem of how to ensure the safety and high efficiency of a multi-person cooperative control scene through a visual control strategy when a plurality of near field communication devices interact with a vehicle at the same time in the prior art can be solved.

Description

Technical Field

[0001] This application belongs to the field of cockpit control technology, and in particular relates to a management and control method, device and vehicle for near-field communication equipment. Background Technology

[0002] With the development of intelligent connected vehicles, Near Field Communication (NFC) technology has been widely used for vehicle access control, vehicle start-up, and synchronization of personalized settings (such as seat position and air conditioning preferences) due to its convenience. However, in scenarios where multiple people share a vehicle, when a new NFC device attempts to connect, the system usually automatically disconnects from the old device and directly performs a replacement operation. This simple switching mechanism often leads to a poor user experience.

[0003] Furthermore, when multiple NFC devices interact with the vehicle simultaneously, it is easy for passengers to use the vehicle's driving functions (such as switching driving modes), meaning that passengers can also control the vehicle's driving functions through NFC devices, which also affects the safe driving of the vehicle. Summary of the Invention

[0004] This application provides a management and control method, device, and vehicle for near-field communication devices, aiming to ensure the safety and efficiency of multi-person collaborative control scenarios by allowing multiple near-field communication devices to interact with the same vehicle and by using a visual control strategy.

[0005] In a first aspect, embodiments of this application provide a management and control method for near-field communication devices, applied to a vehicle, wherein the vehicle is connected to multiple near-field communication devices, each near-field communication device connected to the vehicle corresponds to a control ball, and the control ball is displayed on the control ball control interface; The management and control method for the near-field communication device includes: In response to a vehicle control command issued by a near-field communication device, the target control ball that issued the vehicle control command is determined; Based on the preset control function permissions of the target near-field communication device corresponding to the target control ball, determine whether the target near-field communication device has the operation permission for the vehicle control command; When it is determined that the target near-field communication device has the operating authority for the vehicle control command, the vehicle control command is executed.

[0006] The vehicle is connected to multiple near-field communication (NFC) devices, each with a corresponding control ball. The control ball is displayed on the control ball's interface. Responding to received vehicle control commands, the system identifies the target control ball from which the command was issued. Based on the preset control function permissions of the target NFC device, it determines whether the target NFC device has the necessary operating permissions for the vehicle control command. If so, the command is executed. Each NFC device connected to the vehicle can be displayed on the control ball, and the command can be executed only when the device has the required permissions. This differentiates the control function permissions of different NFC devices, allowing passengers to issue vehicle control commands through the corresponding control ball, enabling visual vehicle control. Furthermore, by controlling the operation of the control ball based on the preset control function permissions of the NFC devices, the system effectively prevents passengers from using driving functions, ensuring safe vehicle operation and reducing the risk of accidents.

[0007] In one possible implementation of the first aspect, before determining the target control ball that issued the vehicle control command in response to a received vehicle control command, the method further includes: When the near-field communication device is within the preset sensing range of the near-field communication card reader, the total number of connected near-field communication devices is obtained; wherein, the total number of connected near-field communication devices is used to characterize the total number of near-field communication devices that are connected to the vehicle; When the total number of connected near-field communication devices is less than a preset threshold, a connection is established between the near-field communication devices and the vehicle; wherein, the preset threshold is determined based on the number of near-field communication card readers, the number of seats, or the number of in-vehicle screens.

[0008] The vehicle can connect to multiple near-field communication devices simultaneously. Before determining the target control ball to issue the vehicle control command in response to the received vehicle control command, when the near-field communication device is within the preset sensing range of the near-field communication reader, the total number of connected near-field communication devices is obtained. When the total number of connected near-field communication devices is less than a preset threshold, a connection is established between the near-field communication device and the vehicle. The total number of connected near-field communication devices is used to represent the total number of near-field communication devices that are connected to the vehicle. The preset threshold is determined based on the number of near-field communication readers, the number of seats, or the number of in-vehicle screens, which can control the total number of connected near-field communication devices, limit the number of near-field communication devices, and reduce unnecessary resource waste.

[0009] In one possible implementation of the first aspect, establishing a connection between the near-field communication device and the vehicle includes: Obtain the role identifier corresponding to the near-field communication card reader and the unique device code of the near-field communication device; The device role identifier of the near-field communication device is determined based on the role identifier corresponding to the near-field communication card reader; Configure an independent virtual channel for the near-field communication device; Based on the device role identifier, the device unique code, and the independent virtual channel, a control ball corresponding to the near-field communication device is constructed, and the control ball is displayed on the control ball control interface to complete the connection establishment between the near-field communication device and the vehicle.

[0010] The system obtains the role identifier corresponding to the near-field communication (NFC) card reader and the unique device code of the NFC device. Based on the role identifier of the NFC card reader, it determines the device role identifier of the NFC device, allowing the preset control function permissions of the NFC device to be determined according to the role identifier of the NFC card reader. For example, based on the role identifier of the NFC card reader at the armrest screen, the preset control function permissions of the NFC device at the armrest screen are determined. An independent virtual channel is configured for the NFC device. Based on the device role identifier, the unique device code, and the independent virtual channel, a control ball corresponding to the NFC device is constructed and displayed on the control ball control interface. A connection is established between the NFC device and the vehicle, enabling interaction between the NFC device and the vehicle, and enabling visual control of the vehicle through the control ball.

[0011] In one possible implementation of the first aspect, the method further includes: When it is determined that the target near-field communication device does not have the operating authority for the vehicle control command, a valid near-field communication device is determined from the near-field communication devices connected to the vehicle according to the vehicle control command; wherein, the valid near-field communication device is a near-field communication device that has the operating authority for the vehicle control command; Based on the unique device code and independent virtual channel of the effective near-field communication device, the vehicle control command is sent to the control ball corresponding to the effective near-field communication device for display.

[0012] When it is determined that the target near-field communication device does not have the authority to operate vehicle control commands, the valid near-field communication device is identified from among the near-field communication devices connected to the vehicle, based on the vehicle control commands. The valid near-field communication device is the one with the authority to operate vehicle control commands. Using the unique device code and independent virtual channel of the valid near-field communication device, the vehicle control commands are sent to the corresponding control ball for display. The vehicle control commands sent by the control ball that lack the necessary operating authority can be provided to the control ball with operating authority for prompting, allowing the valid near-field communication device with operating authority to confirm the vehicle control commands and determine whether to execute them. This ensures the safe execution of vehicle control commands and reduces the occurrence of safety accidents.

[0013] In one possible implementation of the first aspect, the near-field communication device corresponds to a priority; When a vehicle control command is received from each of the multiple controllers, and the near-field communication device corresponding to each controller has operating authority, executing the vehicle control command includes: Based on the time information carried by each vehicle control command, the priority of the destination control device and the near-field communication device, the execution scheduling information of each vehicle control command is determined; wherein, the execution scheduling information includes the scheduling result, and the execution order of the vehicle control commands when the scheduling result of the vehicle control command is allowed to be executed; According to the execution order, execute each vehicle control command whose scheduling result is allowed to be executed.

[0014] When multiple vehicle control commands are received from various controllers, and the corresponding near-field communication devices have operational permissions, the execution scheduling information for each vehicle control command is determined based on the time information carried by each command, the priority of the target control device, and the near-field communication device. The execution scheduling information includes the scheduling result and the execution order of the vehicle control commands when the scheduling result indicates that execution is permitted. This allows for determination of whether vehicle control commands with the same target control device are permitted to execute. If execution is permitted, the vehicle control commands with permitted scheduling results are executed in the order they are allowed. This prevents overlap or contradictions when different users control the same target control device through different controllers, and determines which vehicle control command to execute and the order in which they are executed.

[0015] In one possible implementation of the first aspect, determining the execution scheduling information of each vehicle control command based on the time information carried by each vehicle control command, the priority of the destination control device, and the priority of the near-field communication device includes: Based on the destination control device carried by each vehicle control command, all the vehicle control commands are grouped to obtain at least one vehicle control command group. Based on the number of vehicle control commands in each vehicle control command group, identify groups of vehicle control commands that are suspected of not being executed. Based on the time information and priority carried by each vehicle control instruction in the suspected non-execution vehicle control instruction group, determine the vehicle control instructions in the suspected non-execution vehicle control instruction group whose scheduling result is not allowed to be executed. Based on all the scheduling results indicating that the vehicle control commands are not allowed to be executed, determine all the scheduling results indicating that the vehicle control commands are allowed to be executed; Based on the time information, the execution order of all scheduling results for the vehicle control commands that are allowed to be executed is determined.

[0016] When determining the execution scheduling information for each vehicle control command, all vehicle control commands are grouped according to the destination control device carried by each command, resulting in at least one vehicle control command group. Based on the number of vehicle control commands in each group, a group of vehicle control commands suspected of not being executed is identified. This allows vehicle control commands with the same destination control device to form a group of vehicle control commands suspected of not being executed. Based on the time information and priority carried by each vehicle control command in the group of vehicle control commands suspected of not being executed, vehicle control commands whose scheduling result is not allowed to be executed are identified, thus selecting vehicle control commands that are not allowed to be executed in terms of time or priority. Based on all vehicle control commands whose scheduling result is not allowed to be executed, all vehicle control commands whose scheduling result is allowed to be executed are identified, thus selecting the allowed vehicle control commands. Based on the time information, the execution order of all vehicle control commands whose scheduling result is allowed to be executed is determined, so that vehicle control commands with the same destination control device can be executed sequentially according to time order.

[0017] In one possible implementation of the first aspect, determining the vehicle control commands in the suspected non-executable vehicle control command group whose scheduling result is not allowed to be executed, based on the time information and priority carried by each vehicle control command in the suspected non-executable vehicle control command group, includes: For each vehicle control command in the group of vehicle control commands that are suspected of not being executed, the vehicle control command at the same time is determined based on the time information. Based on the priority of the near-field communication devices corresponding to all the simultaneous vehicle control commands, the scheduling result determines the vehicle control commands that are not allowed to be executed.

[0018] For each vehicle control command in the suspected non-execution vehicle control command group, the simultaneous vehicle control commands are determined based on the time information. Based on the priority of the near-field communication devices corresponding to all simultaneous vehicle control commands, the vehicle control commands whose scheduling result is not allowed to be executed are determined. This can achieve the following when vehicle control commands with the same destination control device and the same time are issued, the scheduling result of the vehicle control command can be determined based on the priority of the target near-field communication device corresponding to the target spirit control ball that issued the vehicle control command, thereby selecting the vehicle control commands whose scheduling result is not allowed to be executed, and thus determining the vehicle control commands whose scheduling result is allowed to be executed.

[0019] In one possible implementation of the first aspect, the method further includes: The control interface of the control ball displays all the control balls, which are near-field communication devices connected to the vehicle. The shape information of each control ball is related to at least one of the device role identifier, signal strength and priority of its corresponding near-field communication device; the shape information includes color and size.

[0020] The control interface displays all the control balls, allowing visualization of the near-field communication devices connected to the vehicle. The shape information of each control ball is related to at least one of the device role identifier, signal strength, and priority of its corresponding near-field communication device. This enables passengers to quickly understand the priority and operating permissions of the near-field communication device corresponding to each control ball, allowing drivers or passengers to view and promptly understand the near-field communication devices with which they have operating permissions, truly realizing the function of visual vehicle control.

[0021] Secondly, this application provides a management and control device for near-field communication devices, applied to a vehicle, wherein the vehicle is connected to multiple near-field communication devices, each near-field communication device connected to the vehicle corresponds to a control ball, and the control ball is displayed on the control ball control interface; The management and control device for the near-field communication equipment includes: The command response module is used to respond to a received vehicle control command and determine the target control ball that issued the vehicle control command. The permission determination module is used to determine whether the target near-field communication device has the operation permission for the vehicle control command based on the preset control function permissions of the target near-field communication device corresponding to the target control ball. The instruction execution module is used to execute the vehicle control instruction when it is determined that the target near-field communication device has the operation authority for the vehicle control instruction.

[0022] Thirdly, embodiments of this application provide a management and control device for a near-field communication device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any of the above-mentioned embodiments.

[0023] Fourthly, this application provides a vehicle including a management and control device for near-field communication devices. The vehicle is connected to multiple near-field communication devices, and each near-field communication device connected to the vehicle corresponds to a control ball, which is displayed on the control ball control interface.

[0024] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any of the preceding claims.

[0025] Sixthly, embodiments of this application provide a computer program product that, when run on a management and control device of a near-field communication device, causes the management and control device of the near-field communication device to execute the method described in any of the above-mentioned embodiments. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a flowchart illustrating a management and control method for a near-field communication device according to an embodiment of this application.

[0028] Figure 2 This is a schematic diagram of a control interface for a ball control device provided in one embodiment of this application.

[0029] Figure 3 This is a functional schematic diagram of a control ball provided in one embodiment of this application.

[0030] Figure 4 This is a schematic diagram of the structure of a management and control device for a near-field communication device provided in an embodiment of this application. Detailed Implementation

[0031] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0032] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0033] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0034] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0035] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0036] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0037] In this technology, a car can only be paired with and interact with one NFC device (such as a mobile phone or smart key) at a time. When a new NFC device attempts to connect to the car within range, the car typically disconnects from the old NFC device and directly performs a "replacement" operation, pairing and interacting with the new NFC device.

[0038] However, there are often scenarios where multiple users need to connect to the car. For example, during family trips, both the car owner (primary user) and passengers (guest users) want to connect their NFC devices to the car to enjoy personalized entertainment and air conditioning settings, but the primary user needs to retain control over the car's core security functions. When multiple users' NFC devices are connected to the vehicle, if all NFC devices control the car's core security functions, it could pose serious security risks. Guest users' misoperations could also cause traffic accidents, resulting in physical and property damage.

[0039] To address the aforementioned problems, this application provides a management and control method for near-field communication (NFC) devices, applied to a vehicle. The vehicle is connected to multiple NFC devices, each corresponding to a control ball, and the control ball displays information on its control interface. See also... Figure 1 , Figure 1 This is a flowchart illustrating a management and control method for a near-field communication device according to an embodiment of this application, including: Step S11: In response to the received vehicle control command, determine the target control ball that issued the vehicle control command.

[0040] Step S12: Based on the preset control function permissions of the target near-field communication device corresponding to the target control ball, determine whether the target near-field communication device has the operation permission for vehicle control commands.

[0041] Step S13: When it is determined that the target near-field communication device has the operating authority for vehicle control commands, execute the vehicle control commands.

[0042] It should be noted that the vehicle is equipped with a vehicle infotainment system (MCU), which includes a multi-NFC communication management module. The MCU is the core of in-vehicle audio-visual and information control, typically located on the center console. Its core functions include multimedia entertainment, navigation and positioning, vehicle function adjustment, and information display and interaction. Vehicle function adjustment mainly involves adjusting vehicle settings such as air conditioning temperature, seat position, and rearview mirror angle via the MCU interface, physical buttons, or other methods. When a near-field communication device (NFC device) connects to the vehicle, it is generally the NFC device that establishes communication with the MCU.

[0043] NFC devices can be NFC-enabled mobile phones, smartwatches, or other portable electronic devices.

[0044] The multi-NFC communication management module is a component that integrates multiple NFC (Near Field Communication) functions. It can be used to coordinate and manage communication between a vehicle and multiple NFC tags, readers, or other NFC devices, including device management, data exchange, security control, and mode switching. For example, in a vehicle, the multi-NFC communication management module can distinguish between different NFC devices such as mobile phone NFC keys, public transport cards, and payment terminals, enabling communication with multiple NFC tags, readers, or other NFC devices.

[0045] The vehicle is equipped with multiple Near Field Communication (NFC) readers, each of which can be an NFC module. Each NFC module has a corresponding NFC sensing area. When an NFC device activates its NFC function and approaches the NFC sensing area, the NFC module establishes a connection with the NFC device, reads the device information, and establishes a connection between the NFC device and the vehicle. When multiple NFC devices approach different NFC readers, each NFC device connects to the nearest NFC reader, allowing the NFC module to establish a connection with the NFC device, read the device information, and establish a connection between the various NFC devices and the vehicle.

[0046] In an optional example, the vehicle can also have only one near-field communication (NFC) reader. When an NFC device with its NFC function enabled approaches the NFC sensing area of ​​the NFC reader, the NFC reader connects to the NFC device, the NFC module establishes a connection with the NFC device, and reads the device information of the NFC device, thus establishing a connection between the NFC device and the vehicle. When multiple NFC devices approach the NFC sensing area, the NFC reader connects to all of them, the NFC module establishes a connection with all of them, and reads the device information of all of them, thus establishing a connection between all of the NFC devices and the vehicle.

[0047] Specifically, after an NFC device establishes a connection with a vehicle, a control sphere is created on the control interface. This control sphere can be manipulated to issue vehicle control commands, enabling visualized vehicle control. These vehicle control commands control functions on the vehicle. For example, a vehicle control command might be to set the rear air conditioning temperature to 26°C. The vehicle control command may also carry information about the control sphere that issued the command, the NFC device associated with the control sphere, and the NFC reader information of the NFC reader connected to the NFC device. The NFC device information may include a device role identifier, a unique device code, an independent virtual channel, and priority. The control sphere information includes a unique control sphere code and a unique near-field communication device code associated with the control sphere.

[0048] The device role identifiers can be categorized based on whether the user is a driver (owner, guest), seat position (driver, front passenger, left rear, right rear, rear center, etc.), or user identity (husband, wife, child, etc.). Different device role identifiers correspond to different operating permissions. The vehicle's main unit system pre-stores the operating permissions corresponding to each device role identifier.

[0049] The device role identifier of an NFC device can be determined based on the location of the NFC reader when the connection is established, such as the location of the NFC reader on the seat or the vehicle screen, or the role identifier corresponding to the NFC reader. For example, the role identifier corresponding to the NFC reader could be the driver's door, window, or central control display screen. When the role identifier corresponding to the NFC reader is the driver's door, the device role identifier of the NFC device connected to the NFC reader can be determined as the owner.

[0050] The device unique code represents the unique code of an NFC device, and a unique NFC device can be identified based on this device unique code.

[0051] An independent virtual channel is a virtual channel defined when an NFC device establishes a connection with a vehicle. The vehicle's host system allows each connected NFC device to establish an independent virtual channel. Through this independent virtual channel, the NFC device can achieve parallel reception and parsing of data frames with the vehicle via the NFC sphere, enabling information interaction and visualization.

[0052] Priority indicates the priority level of an NFC device, which can be determined by the device's role identifier. For example, an NFC device with the device role identifier of the owner has a higher priority than an NFC device with the device role identifier of the guest.

[0053] The reader information for an NFC card reader includes location information, role identification, and installation device. For example, when an NFC card reader is installed in an armrest screen, the installation device is the armrest screen.

[0054] When a vehicle receives a vehicle control command, the command carries the unique code of the target control sphere that issued the command. The vehicle's main unit stores the unique device code of the near-field communication device corresponding to the control sphere. Through the target control sphere, the target near-field communication device corresponding to it can be identified. Then, based on the device role identifier of the target near-field communication device, the preset control function permissions of the target near-field communication device can be determined. The preset control function permissions represent the operating permissions for controlling the vehicle, or they can be a list of operating permissions for controlling the vehicle.

[0055] After parsing the vehicle control command, the device role identifier of the target near-field communication device can be obtained. This device role identifier is the device role identifier of the near-field communication device corresponding to the target control sphere that issued the vehicle control command. Based on the preset control function permissions of the near-field communication device corresponding to the target control sphere that issued the vehicle control command, it is determined whether the target near-field communication device has the operating authority for the vehicle control command. When the target near-field communication device has the operating authority for the vehicle control command, the vehicle host system executes the vehicle control command. When the target near-field communication device does not have the operating authority for the vehicle control command, the vehicle host system does not execute the vehicle control command.

[0056] At the same time, the vehicle host system can also send the result of whether the vehicle control command has been executed to the target control ball that issued the vehicle control command.

[0057] It should be noted that when a near-field communication (NFC) device is close to the sensing area of ​​an NFC reader and remains within the reader's preset sensing range, the NFC module maintains a connection with the NFC device, the corresponding smart ball is continuously displayed on the smart ball control interface, and the smart ball and vehicle remain in a communicable state (session remains active). When the NFC device is outside the reader's preset sensing range, the connection between the NFC module and the NFC device is lost, the corresponding smart ball disappears from the smart ball control interface, and the connection between the smart ball and vehicle is broken, resulting in a non-communicable state.

[0058] In one possible implementation, in step S11, in response to the received vehicle control command, the target control ball that issued the vehicle control command is determined. Before this, the method further includes: When a near-field communication device is within the preset sensing range of a near-field communication reader, the total number of connected near-field communication devices is obtained. The total number of connected near-field communication devices represents the total number of near-field communication devices that are connected to the vehicle. When the total number of connected near-field communication devices is less than a preset threshold, a connection is established between the near-field communication device and the vehicle. The preset threshold is determined based on the number of near-field communication readers, the number of seats, or the number of in-vehicle screens.

[0059] Specifically, the vehicle can be equipped with multiple NFC card readers, each capable of connecting to NFC devices. The number of NFC card readers can be matched to the number of seats or the number of in-vehicle screens. For example, each in-vehicle screen can be equipped with an NFC card reader, facilitating a connection between passengers using the screens and the vehicle.

[0060] When an NFC device is within the preset sensing range of an NFC reader (assuming the reader is located on the armrest screen), the NFC reader detects the signal strength of the NFC device, reads its device information, obtains its unique device code, and sends the signal strength and device information to the vehicle's main unit. The signal strength of the NFC device is related to the distance between the NFC device and the NFC reader.

[0061] After receiving the signal strength and device information from the NFC device, the vehicle's main unit system obtains the total number of connected NFC devices. This total number represents the number of NFC devices currently connected to the vehicle. To facilitate NFC device management, and to prevent permission confusion when there are too many NFC devices, a preset threshold can be set. When the total number of connected NFC devices is less than the preset threshold, a connection is established between the NFC device and the vehicle. When the total number of connected NFC devices is greater than or equal to the preset threshold, a connection is not established between the NFC device and the vehicle.

[0062] The preset threshold can be determined based on the number of NFC readers, the number of seats, or the number of in-vehicle screens. For example, the preset threshold can be set to 5. However, when the preset threshold is set based on the number of NFC readers, it can be less than the number of NFC readers. The maximum number of NFC devices that the vehicle can connect to is reached when all NFC readers are connected to NFC devices.

[0063] In one possible implementation, the above-mentioned connection between the near-field communication device and the vehicle includes: Obtain the role identifier corresponding to the near-field communication card reader and the unique device code of the near-field communication device; determine the device role identifier of the near-field communication device based on the role identifier corresponding to the near-field communication card reader; configure an independent virtual channel for the near-field communication device; construct a control ball corresponding to the near-field communication device based on the device role identifier, the unique device code, and the independent virtual channel, and display the control ball on the control ball control interface to complete the connection establishment between the near-field communication device and the vehicle.

[0064] Specifically, when an NFC device is connected to a vehicle, the vehicle's main system obtains the role identifier corresponding to the NFC reader and the unique device code of the NFC device. The role identifier corresponding to the NFC reader can be the armrest screen, the left rear seat, etc.

[0065] The device role identifier of an NFC device can be determined based on the role identifier corresponding to the NFC reader. For example, when the role identifier corresponding to the NFC reader is "passenger screen," since the passenger screen is the screen used by the passenger in the front passenger seat, the device role identifier of the NFC device corresponding to the passenger screen can be "guest," "wife," or "passenger."

[0066] The vehicle's main unit system also needs to configure a separate virtual channel for the NFC device, so that the vehicle and the NFC device can interact through this separate virtual channel.

[0067] Based on device role identification, unique device code, and independent virtual channel, a control ball corresponding to the near-field communication device is constructed, and the control ball control interface is displayed on the control ball to establish a connection between the near-field communication device and the vehicle. This allows the vehicle and the near-field communication device to achieve visual interaction through the control ball. Passengers only need to operate the control ball to issue vehicle control commands to adjust vehicle functions.

[0068] In one possible implementation, the above method also includes: When it is determined that the target near-field communication device does not have the operation authority for vehicle control commands, the valid near-field communication device is determined from the NFC devices connected to the vehicle according to the vehicle control commands; the valid near-field communication device is the near-field communication device with the operation authority for vehicle control commands; according to the device unique code and independent virtual channel of the valid near-field communication device, the vehicle control commands are sent to the control ball corresponding to the valid near-field communication device for display.

[0069] Specifically, when it is determined that the corresponding target near-field communication device does not have the operating authority to issue vehicle control commands to the target control ball, the target near-field communication device does not have the authority to control the vehicle to execute the vehicle control commands issued by the target control ball, and the vehicle does not execute the vehicle control commands.

[0070] For example, for sensitive function control commands related to vehicle driving safety, such as switching driving modes and turning off ESP (Electronic Stability Program), only the NFC device with the owner's device role identifier has the right to operate, while NFC devices with other device role identifiers do not have the right to operate.

[0071] Each NFC device can have a different priority based on its corresponding device role identifier. For example, the NFC device in the driver's seat has a higher priority than the NFC device in the passenger's seat.

[0072] When the target near-field communication device lacks the authority to control the vehicle and execute the vehicle control command, to ensure that the execution of the vehicle control command is not easily missed, the vehicle control command can be sent to the control ball corresponding to the valid near-field communication device. The valid near-field communication device can be a near-field communication device with a higher priority than the current near-field communication device, or it can be a near-field communication device with the highest priority. Furthermore, the valid near-field communication device must be connected to the vehicle and have the authority to execute the vehicle control command.

[0073] It should be noted that each near-field communication device connected to the vehicle can have a corresponding control ball, which is displayed on the control ball interface. By clicking on the control ball, you can obtain the device information of the near-field communication device corresponding to that control ball.

[0074] The vehicle's main unit system submits the vehicle control command to the PTZ controller corresponding to the valid near-field communication (NFC) device. Both the device information of the valid NFC device and the vehicle control command can be displayed on the PTZ controller interface (which can be located on the central control screen or other screens). For example, the valid NFC device can be displayed as a PTZ controller, and an alarm pop-up window will appear prompting for the vehicle control command. When the user corresponding to the valid NFC device confirms the prompt on the PTZ controller interface, if the user confirms to execute the vehicle control command, then the vehicle's main unit system executes the vehicle control command. If the user confirms not to execute the vehicle control command, then the vehicle's main unit system does not execute the vehicle control command.

[0075] In an optional example, when the device role is identified as a child's near-field communication device, the user of this near-field communication device clicks the corresponding smart controller and issues a vehicle control command to "switch driving mode to sport mode". The vehicle's main unit system recognizes that the command comes from a smart controller with the role identified as a child, and the near-field communication device corresponding to the device does not have the operation permission for this vehicle control command. Therefore, it refuses to execute the vehicle control command and displays a prompt on the smart controller: "Insufficient permissions, this operation has been rejected".

[0076] In one possible implementation, near-field communication devices are assigned priorities; When multiple near-field communication devices send vehicle control commands, and the near-field communication device corresponding to each control ball has operating authority, step S13 involves executing the vehicle control commands, including: Based on the time information carried by each vehicle control command, the priority of the destination control device and the near-field communication device, the execution scheduling information of each vehicle control command is determined. The execution scheduling information includes the scheduling result and the execution order of the vehicle control commands when the scheduling result of the vehicle control command is allowed to be executed. According to the execution order, each vehicle control command whose scheduling result is allowed to be executed is executed.

[0077] Specifically, when multiple control balls receive vehicle control commands, it determines whether the near-field communication devices corresponding to these control balls have the operating authority to execute the vehicle control commands they issued. Then, it selects the control ball corresponding to the near-field communication device that has the operating authority, as well as the vehicle control commands that have the operating authority.

[0078] When executing these vehicle control commands with operational authority, it is also necessary to re-evaluate these vehicle control commands to determine whether there is any overlap or contradiction between them, which vehicle control commands can be executed, and which vehicle control commands can be ignored.

[0079] For example, for vehicle control commands with the same target control device, the scheduling result of each vehicle control command can be determined as either allowed or disallowed based on the time information carried by each command with operating authority. When the scheduling result of a vehicle control command is allowed, the execution order of each vehicle control command can also be determined synchronously based on the time information carried by each command. For example, all vehicle control commands can be executed sequentially from beginning to end according to their chronological order.

[0080] In this context, the target control device refers to the device that the vehicle control command intends to control. For example, in the vehicle control command "Air conditioning, set the temperature to 26°C", the target control device is the air conditioner.

[0081] For any two vehicle control commands that are at the same time and have the same target control device, the vehicle control command to be executed can be determined according to the priority of the near-field communication device corresponding to the control ball that issued the vehicle control command.

[0082] Once the permitted vehicle control commands are determined, the execution order of the vehicle control commands is determined based on the time information, and the permitted vehicle control commands are executed sequentially according to the execution order.

[0083] In an optional example, the device role is identified as the wife's near-field communication device. The wife, by clicking its corresponding silver controller, issues the vehicle control command, "Air conditioning, set the temperature to 26°C." The air conditioning temperature then changes to 26°C. Subsequently, the device role is identified as the husband's near-field communication device. The husband, by clicking its corresponding gold controller, issues the vehicle control command, "Air conditioning, set the temperature to 23°C." The air conditioning temperature then changes from 26°C to 23°C. That is, for non-safety-related vehicle control commands, the execution order can be determined based on the time information carried by the command; a new vehicle control command will overwrite an older one.

[0084] In one possible implementation, the execution scheduling information for each vehicle control command is determined based on the time information carried by each vehicle control command, the priority of the destination control device, and the near-field communication device, including: Based on the destination control device carried by each vehicle control command, all vehicle control commands are grouped to obtain at least one vehicle control command group. Based on the number of vehicle control commands in each group, groups of vehicle control commands suspected of being non-executable are identified. Based on the time information and priority carried by each vehicle control command in the suspected non-executable vehicle control command group, vehicle control commands whose scheduling results are not allowed to be executed are identified within the suspected non-executable vehicle control command group. Based on all vehicle control commands whose scheduling results are not allowed to be executed, all vehicle control commands whose scheduling results are allowed to be executed are identified. Based on the time information, the execution order of all vehicle control commands whose scheduling results are allowed to be executed is determined.

[0085] Specifically, based on the destination control device carried by each vehicle control command, all vehicle control commands can be grouped. For example, vehicle control commands with the same destination control device can be grouped together to obtain a vehicle control command group. In this way, all vehicle control command groups are obtained. The vehicle control commands in each vehicle control command group carry the same destination control device.

[0086] For each vehicle control command group, it is necessary to filter out vehicle control commands that may be contradictory, that is, multiple vehicle control commands in the vehicle control command group are contradictory.

[0087] When filtering potentially conflicting vehicle control commands, groups of commands suspected of not being executed are identified based on the number of commands in each command group. Command groups with more than one command are designated as suspected non-execution groups. Command groups with one or fewer commands are designated as execution groups, where commands can be executed directly.

[0088] For each suspected non-execution vehicle control command group, based on the time information and priority carried by each vehicle control command in the suspected non-execution vehicle control command group, the vehicle control command whose scheduling result is not allowed to be executed is determined. For example, for two vehicle control commands with the same time information, based on the priority of the near-field communication device corresponding to the control sphere that issued the vehicle control command, the vehicle control command issued by the control sphere corresponding to the near-field communication device with the lower priority is determined to be the vehicle control command not allowed to be executed. Thus, all vehicle control commands whose scheduling result is not allowed to be executed are determined in all suspected non-execution vehicle control command groups.

[0089] For all vehicle control commands, those that are not allowed to be executed are filtered out, and all vehicle control commands that are allowed to be executed are obtained.

[0090] For all permitted vehicle control commands, the execution order of these commands is determined according to the time information they carry, in a sequential order from beginning to end.

[0091] In one possible implementation, based on the time information and priority carried by each vehicle control instruction in the suspected non-execution vehicle control instruction group, the vehicle control instructions whose scheduling result is not allowed to be executed are determined, including: For each vehicle control command in the suspected non-execution vehicle control command group, determine the simultaneous vehicle control command based on the time information; and determine the vehicle control command that is not allowed to be executed based on the priority of the near-field communication device corresponding to all simultaneous vehicle control commands.

[0092] Specifically, for any group of vehicle control commands suspected of not being executed, each vehicle control command in that group can be used to determine the concurrent vehicle control commands within that group based on its time information. Concurrent vehicle control commands refer to vehicle control commands with consistent time information. These concurrent vehicle control commands are grouped into a queue, resulting in a concurrent vehicle control command queue. For any concurrent vehicle control command queue, based on the priority of the near-field communication devices corresponding to all vehicle control commands in the queue, vehicle control commands issued by near-field communication devices with lower priority than the highest priority are selected. These vehicle control commands issued by near-field communication devices with lower priority are determined to be disallowed vehicle control commands.

[0093] In one possible implementation, the above method also includes: All the spheres are displayed through the sphere control interface. The shape information of each sphere is related to at least one of the device role identifier, signal strength and priority of its corresponding near-field communication device; the shape information includes color and size.

[0094] Specifically, the central control screen displays the near-field communication (NFC) devices connected to the vehicle. Each NFC device is represented by a NFC sphere. For example, the central control screen has a main NFC sphere representing the vehicle itself, surrounded by multiple secondary NFC spheres, each corresponding to a NFC device connected to the vehicle. Each connected NFC device adds one secondary NFC sphere, and the number of secondary NFC spheres visually indicates the total number of NFC devices currently connected to the vehicle. Figure 2 As shown, Figure 2 This is a schematic diagram of a control interface for a spirit ball provided in an embodiment of this application. There is a main spirit ball on the central control screen, and five clone spirit balls around it, namely clone spirit ball 1, clone spirit ball 2, clone spirit ball 3, clone spirit ball 4 and clone spirit ball 5.

[0095] In an optional example, three near-field communication (NFC) devices are sequentially identified and connected by multiple NFC card readers. The central control screen's control interface immediately displays a main control ball and three secondary control balls. The control ball corresponding to the NFC device identified as the husband is gold and the largest (highest priority); the control ball corresponding to the NFC device identified as the wife is silver and medium (second priority); and the control ball corresponding to the NFC device identified as the child is blue and the smallest (lowest priority).

[0096] The size of the NFC sphere displayed on the central control screen can also represent the priority or signal strength of the near-field communication (NFC) device. For example, the larger the sphere, the higher the priority and the stronger the signal of the corresponding NFC device. Users can set the priority of the NFC device corresponding to the NFC sphere by controlling its size.

[0097] In an optional example, the distance between the clone sphere and the main sphere can also represent the signal strength of the near-field communication device. Users can set the priority of the NFC device corresponding to the clone sphere by controlling the distance between the clone sphere and the main sphere.

[0098] Different effects can also be set for each clone spirit control ball through visual classification (such as color, halo effect) to distinguish the priority and device role identification of the near-field communication device corresponding to the clone spirit control ball. For example, a gold spirit control ball represents a near-field communication device with the device role identification "master", and a silver spirit control ball represents a near-field communication device with the device role identification "guest".

[0099] Each spirit control ball can be configured with different functions. For example, the original functions of the "master spirit control ball" remain unchanged and can still be adjusted normally. The "clone spirit control balls" allow users to actively set the level of their current near-field communication device. A "personality selection" switch can also be set on the spirit control ball, allowing users to actively choose their identity. Regardless of the number of clone spirit control balls, only one near-field communication device with the device role identifier "master" can be associated with a spirit control ball. Different device role identifiers can also have their corresponding colors pre-stored. For example, the spirit control ball with the device role identifier "master" is gold, and the spirit control ball with the device role identifier "guest" is silver.

[0100] like Figure 3 As shown, Figure 3 This is a functional diagram of a smart controller provided in one embodiment of this application. When a user long-presses the cloned smart controller, a dedicated control menu for the near-field communication device corresponding to that smart controller can be expanded. The menu content can be dynamically generated based on the preset control function permissions and priority levels of the near-field communication device. For example, clicking on the smart controller with the device role identifier "Owner" will bring up the preset control function permissions of the near-field communication device with the device role identifier "Owner". Clicking on the smart controller with the device role identifier "Guest" will only bring up control options for limited functions such as entertainment, air conditioning, and windows (only on the non-driver's side).

[0101] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0102] Corresponding to the method described in the above embodiments, Figure 4 This paper shows a schematic diagram of the structure of a management and control device for a near-field communication device provided in an embodiment of this application. For ease of explanation, only the parts related to the embodiment of this application are shown.

[0103] Reference Figure 4 The near-field communication (NFC) device management and control device 4 is applied to a vehicle. The vehicle is connected to multiple NFC devices, each of which corresponds to a control ball. The control ball displays information on its control interface. The NFC device management and control device 4 includes: The instruction response module 41 is used to respond to the received vehicle control instruction and determine the target control that issued the vehicle control instruction. The permission judgment module 42 is used to determine whether the target near-field communication device has the operation permission for vehicle control commands based on the control function permission of the target near-field communication device corresponding to the target control ball. The instruction execution module 43 is used to execute vehicle control instructions when it is determined that the target near-field communication device has the operation authority for vehicle control instructions.

[0104] In one possible implementation, the near-field communication device management and control device 4 further includes: a connection establishment module 44, used to determine the target control ball that issued the vehicle control command in response to the received vehicle control command. Before that, when the near-field communication device is within the preset sensing range of the near-field communication reader, the total number of connected near-field communication devices is obtained; wherein, the total number of connected near-field communication devices is used to represent the total number of near-field communication devices that are connected to the vehicle; when the total number of connected near-field communication devices is less than a preset number threshold, a connection is established between the near-field communication device and the vehicle; wherein, the preset number threshold is determined based on the number of near-field communication readers, the number of seats, or the number of in-vehicle screens.

[0105] In one possible implementation, the connection establishment module 44 is further used to obtain the role identifier corresponding to the near-field communication card reader and the unique device code of the near-field communication device; determine the device role identifier of the near-field communication device based on the role identifier corresponding to the near-field communication card reader; configure an independent virtual channel for the near-field communication device; construct a control ball corresponding to the near-field communication device based on the device role identifier, the unique device code, and the independent virtual channel, and display the control ball on the control ball control interface to complete the connection establishment between the near-field communication device and the vehicle.

[0106] In one possible implementation, the instruction execution module 43 is further configured to, when it is determined that the target near-field communication device does not have the operating authority for vehicle control instructions, determine a valid near-field communication device from the near-field communication devices connected to the vehicle according to the vehicle control instructions; wherein, the valid near-field communication device is a near-field communication device with the operating authority for vehicle control instructions; and send the vehicle control instructions to the corresponding control ball for display according to the unique device code and independent virtual channel of the valid near-field communication device.

[0107] In one possible implementation, the near-field communication devices are assigned priorities. When multiple vehicle control commands are received from various control sphere devices, and the near-field communication devices corresponding to each control sphere have operational permissions, the command execution module 43 is further configured to determine the execution scheduling information of each vehicle control command based on the time information carried by each vehicle control command, the priority of the destination control device, and the near-field communication device. The execution scheduling information includes the scheduling result and the execution order of the vehicle control commands when the scheduling result of the vehicle control command is allowed to be executed. The vehicle control commands whose scheduling result is allowed to be executed are executed according to the execution order.

[0108] In one possible implementation, the instruction execution module 43 is further configured to: group all vehicle control instructions according to the destination control device carried by each vehicle control instruction to obtain at least one vehicle control instruction group; determine suspected non-execution vehicle control instruction groups based on the number of vehicle control instructions in each vehicle control instruction group; determine vehicle control instructions in the suspected non-execution vehicle control instruction group whose scheduling result is not allowed to be executed based on the time information and priority carried by each vehicle control instruction in the suspected non-execution vehicle control instruction group; determine all vehicle control instructions whose scheduling result is not allowed to be executed based on all vehicle control instructions whose scheduling result is allowed to be executed; and determine the execution order of all vehicle control instructions whose scheduling result is allowed to be executed based on the time information.

[0109] In one possible implementation, the instruction execution module 43 is further configured to, for each vehicle control instruction in the suspected non-execution vehicle control instruction group, determine the simultaneous vehicle control instruction based on time information; and determine the vehicle control instruction whose scheduling result is not allowed to be executed based on the priority of the near-field communication devices corresponding to all simultaneous vehicle control instructions.

[0110] In one possible implementation, the management and control device 4 of the near-field communication device further includes: a display module for displaying all the near-field communication spheres through the near-field communication sphere control interface, wherein the shape information of each near-field communication sphere is related to at least one of the device role identifier, signal strength and priority of its corresponding near-field communication device; the shape information includes color and size.

[0111] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0112] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0113] This application also provides a management and control device for a near-field communication device, the device comprising: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor executes the computer program to implement the steps in any of the above method embodiments.

[0114] This application embodiment also provides a vehicle including the management and control device for the aforementioned near-field communication device. The vehicle is connected to multiple near-field communication devices, and each near-field communication device connected to the vehicle corresponds to a control ball, which is displayed on the control ball control interface.

[0115] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.

[0116] This application provides a computer program product that, when run on the management and control device of a near-field communication device, enables the management and control device of the near-field communication device to implement the steps described in the above-described method embodiments.

[0117] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0118] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0119] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0120] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

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

[0122] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A management and control method for a near-field communication device, applied to a vehicle, characterized in that, The vehicle is connected to multiple near-field communication devices, and each near-field communication device connected to the vehicle corresponds to a control ball, which is displayed on the control ball control interface. The management and control method for the near-field communication device includes: In response to a received vehicle control command, the target control ball that issued the vehicle control command is determined; Based on the preset control function permissions of the target near-field communication device corresponding to the target control ball, determine whether the target near-field communication device has the operation permission for the vehicle control command; When it is determined that the target near-field communication device has the operating authority for the vehicle control command, the vehicle control command is executed.

2. The management and control method for near-field communication devices as described in claim 1, characterized in that, Before determining the target control ball that issued the vehicle control command in response to a received vehicle control command, the method further includes: When the near-field communication device is within the preset sensing range of the near-field communication card reader, the total number of connected near-field communication devices is obtained; wherein, the total number of connected near-field communication devices is used to characterize the total number of near-field communication devices that are connected to the vehicle; When the total number of connected near-field communication devices is less than a preset threshold, a connection is established between the near-field communication devices and the vehicle; wherein, the preset threshold is determined based on the number of near-field communication card readers, the number of seats, or the number of in-vehicle screens.

3. The management and control method for near-field communication devices as described in claim 2, characterized in that, Establishing a connection between the near-field communication device and the vehicle includes: Obtain the role identifier corresponding to the near-field communication card reader and the unique device code of the near-field communication device; The device role identifier of the near-field communication device is determined based on the role identifier corresponding to the near-field communication card reader; Configure an independent virtual channel for the near-field communication device; Based on the device role identifier, the device unique code, and the independent virtual channel, a control ball corresponding to the near-field communication device is constructed, and the control ball is displayed on the control ball control interface to complete the connection establishment between the near-field communication device and the vehicle.

4. The management and control method for near-field communication devices as described in claim 1, characterized in that, The method further includes: When it is determined that the target near-field communication device does not have the operating authority for the vehicle control command, a valid near-field communication device is determined from the near-field communication devices connected to the vehicle according to the vehicle control command; wherein, the valid near-field communication device is a near-field communication device that has the operating authority for the vehicle control command; Based on the unique device code and independent virtual channel of the effective near-field communication device, the vehicle control command is sent to the control ball corresponding to the effective near-field communication device for display.

5. The management and control method for near-field communication devices as described in claim 1, characterized in that, The near-field communication devices are assigned priorities. When a vehicle control command is received from each of the multiple control balls, and the near-field communication device corresponding to each control ball has operating authority, executing the vehicle control command includes: Based on the time information carried by each vehicle control command, the priority of the destination control device and the near-field communication device, the execution scheduling information of each vehicle control command is determined; wherein, the execution scheduling information includes the scheduling result, and the execution order of the vehicle control commands when the scheduling result of the vehicle control command is allowed to be executed; According to the execution order, execute each vehicle control command whose scheduling result is allowed to be executed.

6. The management and control method for near-field communication devices as described in claim 5, characterized in that, The step of determining the execution scheduling information of each vehicle control command based on the time information carried by each vehicle control command, the priority of the destination control device, and the priority of the near-field communication device includes: Based on the destination control device carried by each vehicle control command, all the vehicle control commands are grouped to obtain at least one vehicle control command group. Based on the number of vehicle control commands in each vehicle control command group, identify groups of vehicle control commands that are suspected of not being executed. Based on the time information and priority carried by each vehicle control instruction in the suspected non-execution vehicle control instruction group, determine the vehicle control instructions in the suspected non-execution vehicle control instruction group whose scheduling result is not allowed to be executed. Based on all the scheduling results indicating that the vehicle control commands are not allowed to be executed, determine all the scheduling results indicating that the vehicle control commands are allowed to be executed; Based on the time information, the execution order of all scheduling results for the vehicle control commands that are allowed to be executed is determined.

7. The management and control method for near-field communication devices as described in claim 6, characterized in that, The step of determining the vehicle control commands in the suspected non-execution vehicle control command group that are not allowed to be executed based on the time information and priority carried by each vehicle control command in the group includes: For each vehicle control command in the group of vehicle control commands that are suspected of not being executed, the vehicle control command at the same time is determined based on the time information. Based on the priority of the near-field communication devices corresponding to all the simultaneous vehicle control commands, the scheduling result determines the vehicle control commands that are not allowed to be executed.

8. The management and control method for a near-field communication device as described in any one of claims 1-7, characterized in that, The method further includes: All the control balls are displayed through the control ball interface. The shape information of each control ball is related to at least one of the device role identifier, signal strength and priority of its corresponding near-field communication device. The shape information includes color and size.

9. A management and control device for a near-field communication device, applied to a vehicle, characterized in that, The vehicle is connected to multiple near-field communication devices, and each near-field communication device connected to the vehicle corresponds to a control ball, which is displayed on the control ball control interface. The management and control device for the near-field communication equipment includes: The command response module is used to respond to a received vehicle control command and determine the target control ball that issued the vehicle control command. The permission determination module is used to determine whether the target near-field communication device has the operation permission for the vehicle control command based on the preset control function permissions of the target near-field communication device corresponding to the target control ball. The instruction execution module is used to execute the vehicle control instruction when it is determined that the target near-field communication device has the operation authority for the vehicle control instruction.

10. A vehicle, characterized in that, The system includes a management and control device for near-field communication devices as described in claim 9, wherein the vehicle is connected to multiple near-field communication devices, each near-field communication device connected to the vehicle corresponds to a control ball, and the control ball is displayed on the control ball control interface.

Images