Access control method and device, communication system

Abstract

The present application relates to an access control method applicable to a short-range communication field, such as cockpit domain communication. The method comprises: a step of determining that the state of a first device is a first state; and a step of transmitting a first indication information, wherein the first indication information is used to indicate whether access by at least one second device to the first device is permitted. A system broadcast message containing system state information is transmitted, and after a non-vehicle-mounted device receives the system broadcast message, the non-vehicle-mounted device determines whether to initiate a random access request based on the system state information. This prevents the initiation of a random access request by the non-vehicle-mounted device at this stage from affecting the status check of the vehicle-mounted device and the self-check and access of the vehicle-mounted device performed by the CDC. Furthermore, this allows the vehicle-mounted device to operate normally and some basic services to operate normally.

Description

Technology Field

[0001] The present application relates to the field of communication, and in particular to a differentiated access control method and device and communication device used in short-range communication such as cockpit domain communication. Background Technology

[0002] Short-range communication technologies such as Bluetooth and Wi-Fi play a crucial role in people's daily lives. With the increased use and popularization of vehicles, the functions of short-range communication technologies are becoming even more prominent. Driven by advancements in science and technology, advanced driving assistance systems (ADAS) and automated driving systems (ADS) in vehicles are constantly evolving. In the future, it is highly likely that vehicle driving will be performed by machines, eliminating the need for humans to use their hands and feet. Vehicles are not merely a means of transportation for users but also serve as living spaces for daily life. By utilizing smart cockpit technology, numerous functions can be provided to those inside the vehicle, including rich entertainment activities, audio and video playback, and office environments. Consequently, people can work while in the vehicle, enjoy personalized audio and video entertainment services, and experience customized driving.

[0003] Currently, smart cockpits primarily consist of a Cockpit Domain Controller (CDC), on-board devices, and non-on-board devices. The CDC is mainly connected to on-board devices via wires, while the CDC is mainly connected to non-on-board devices via wirelesss. However, because the CDC is connected to on-board devices via wires, this method requires a large number of cables and is costly. In the confined space of a vehicle, cabling becomes more difficult as the number of on-board devices increases. The high cost of cabling and cables acts as a constraint on the development of smart cockpit technology. Therefore, wirelessly connecting the CDC to on-board or non-on-board devices has become an urgent challenge.

[0004] Embodiments of the present application provide an access control method applicable to the field of general-purpose transmission. An information element carrying system status information or access indication information is transmitted to indicate the current system status and determines whether a non-vehicle-mounted device initiates a random access request after receiving the aforementioned information. Access by the non-vehicle-mounted device is restricted at a specific stage. This prevents the impact on the CDC's vehicle-mounted device status check and vehicle-mounted device access caused by the initiation of a random access request by the non-vehicle-mounted device at this stage. Furthermore, this allows the vehicle-mounted device to operate normally and some basic services to operate normally.

[0005] According to a first aspect, the present application provides an access control method. The method comprises: determining that the state of a first device is a first state; and transmitting a first indication information, wherein the first indication information is used to indicate whether access by at least one second device to the first device is permitted. Optionally, the first indication information is carried in a system message or transmitted by broadcast. The first indication information may be a master information block (MIB), a system information block (SIB), or a broadcast frame. An MIB may be carried in a Physical Broadcast Channel (PBCH). An SIB is generally included in radio resource control (RRC) signaling. Optionally, the first indication information is transmitted by broadcasting.

[0006] In a possible implementation, the first state includes at least one of a system ready state and a vehicle-mounted device access state, and the first indication information is used to indicate that access by at least one second device is not permitted; or the first state includes at least one of a system running state and an access allowed state, and the first indication information is used to indicate that access by the second device is permitted. The system ready state and / or vehicle-mounted device access state may be used to indicate that a vehicle-mounted device is accessing the control domain cockpit CDC or that a vehicle-mounted device is performing a self-check, so that a non-vehicle-mounted device may choose not to access the control domain cockpit CDC according to these types of system states. The system running state and / or access allowed state may be used to indicate that a vehicle-mounted device has accessed the control domain cockpit CDC. In this case, a non-vehicle-mounted device may be permitted to access the control domain cockpit CDC.

[0007] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0008] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0009] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0010] In a possible implementation, the first display information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information.

[0011] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on priority information and access indicator information.

[0012] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that access by at least one second device to the first device is not allowed within the first time range.

[0013] In a possible implementation, the first time range is a time domain offset relative to the first reference frame or a time domain offset relative to the first signaling. The first reference frame may be a first system frame number agreed upon or consensual in advance between the control domain cockpit (CDC) and the non-vehicle-mounted device, or a first system frame number defined in the protocol. The first signaling may be a specific signaling agreed upon or consensual in advance between the control domain cockpit CDC and the non-vehicle-mounted device, or a specific signaling defined in the protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets.

[0014] In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0015] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0016] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0017] In a possible implementation, the device type includes at least one of a vehicle-mounted device and a non-vehicle-mounted device.

[0018] According to a second aspect, the present application provides an access method. The method comprises: receiving first indication information from a first device; and determining, based on the first indication information, whether access by a second device to the first device is permitted. Optionally, the first indication information may be included in a system message or transmitted by a broadcast. For example, the system message may be a system broadcast message. The first indication information may be an MIB, a SIB, or a broadcast frame. An MIB may be carried via a PBCH. A SIB is generally included in RRC signaling.

[0019] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0020] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0021] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0022] In a possible implementation, the first display information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information.

[0023] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on priority information and access indicator information.

[0024] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that access by at least one second device to the first device is not allowed within the first time range.

[0025] In a possible implementation, the first time range is a time domain offset relative to the first reference frame or a time domain offset relative to the first signaling. The first reference frame may be a first system frame number agreed upon or consensual in advance between the control domain cockpit (CDC) and the non-vehicle-mounted device, or a first system frame number defined in the protocol. The first signaling may be a specific signaling agreed upon or consensual in advance between the control domain cockpit CDC and the non-vehicle-mounted device, or a specific signaling defined in the protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets.

[0026] In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0027] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0028] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0029] In a possible implementation, the CDC is also referred to as a control domain cockpit or control domain cockpit CDC, the first device is a control domain cockpit CDC, the third device is a vehicle-mounted device, and the second device is a non-vehicle-mounted device.

[0030] In a possible implementation, the second device is a mobile phone.

[0031] According to a third aspect, the present application provides an access control device. The access control device may be a first device or a chip or integrated circuit of the first device. For example, the access control device may be a control domain cockpit (CDC) or the access control device is a chip or integrated circuit of the control domain cockpit (CDC). Certainly, the access control device may alternatively be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, mobile phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, vehicle-mounted device, smart home device, and / or smart city device. In this embodiment of the present application, the specific type of the first device is not limited. The device comprises: a processing unit configured to determine that the state of the first device is a first state; It includes a transmitting unit configured to transmit a first indication information, wherein the first indication information is used to indicate whether access by at least one second device to the first device is permitted. Optionally, the first indication information is carried in a system message or transmitted via broadcast. The first indication information may be an MIB, a SIB, or a broadcast frame. An MIB may be carried via a PBCH. A SIB is typically included in RRC signaling. Optionally, the first indication information is transmitted via broadcasting.

[0032] In a possible implementation, the first state includes at least one of a system ready state and a vehicle-mounted device access state, and the first indication information is used to indicate that access by at least one second device is not permitted; or the first state includes at least one of a system running state and an access allowed state, and the first indication information is used to indicate that access by the second device is permitted. The system ready state and / or vehicle-mounted device access state may be used to indicate that a vehicle-mounted device is accessing the control domain cockpit CDC or that a vehicle-mounted device is performing a self-check, so that a non-vehicle-mounted device may choose not to access the control domain cockpit CDC according to these types of system states. The system running state and / or access allowed state may be used to indicate that a vehicle-mounted device has accessed the control domain cockpit CDC. In this case, a non-vehicle-mounted device may be permitted to access the control domain cockpit CDC.

[0033] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0034] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0035] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0036] In a possible implementation, the first display information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information.

[0037] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on priority information and access indicator information.

[0038] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that access by at least one second device to the first device is not allowed within the first time range.

[0039] In a possible implementation, the first time range is a time domain offset for a first reference frame or a time domain offset for a first signaling. The first reference frame may be a first system frame number agreed upon or consensual in advance between the control domain cockpit (CDC) and a non-vehicle-mounted device, or a first system frame number defined in the protocol. The first signaling may be a specific signaling agreed upon or consensual in advance between the control domain cockpit CDC and a non-vehicle-mounted device, or a specific signaling defined in the protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets.

[0040] In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0041] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0042] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0043] In a possible implementation, the device type includes at least one of a vehicle-mounted device and a non-vehicle-mounted device.

[0044] According to a fourth aspect, the present application provides an access device. The access device may be a second device or a chip or integrated circuit of the second device. For example, the access device is a chip or integrated circuit of a vehicle-mounted device or a non-vehicle-mounted device. Certainly, the access device may alternatively be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, UMPC, netbook, cellular phone, PDA, AR device, VR device, AI device, wearable device, vehicle-mounted device, smart home device and / or smart city device. In this embodiment of the present application, the specific type of the first device is not limited. The device comprises a receiving unit and a processing unit. The receiving unit is configured to receive first indication information from the first device. The processing unit is configured to determine, based on the first indication information, whether access by the second device to the first device is permitted. Optionally, the first indication information may be included in a system message or transmitted by a broadcast. For example, the system message may be a system broadcast message. The first indication information may be an MIB, SIB, or broadcast frame. The MIB may be carried via the PBCH. The SIB is typically included in RRC signaling.

[0045] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0046] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0047] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0048] In a possible implementation, the first display information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information.

[0049] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on priority information and access indicator information.

[0050] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that access by at least one second device to the first device is not allowed within the first time range.

[0051] In a possible implementation, the first time range is a time domain offset relative to the first reference frame or a time domain offset relative to the first signaling. The first reference frame may be a first system frame number agreed upon in advance between the control domain cockpit (CDC) and the non-vehicle-mounted device, or a first system frame number defined in the protocol. The first signaling may be a specific signaling agreed upon in advance between the control domain cockpit CDC and the non-vehicle-mounted device, or a specific signaling defined in the protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets.

[0052] In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0053] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0054] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0055] In a possible implementation, the first device is a control domain cockpit CDC, the third device is a vehicle-mounted device, and the second device is a non-vehicle-mounted device.

[0056] In a possible implementation, the second device is a mobile phone.

[0057] According to a fifth aspect, the present application provides a computer storage medium, wherein the computer storage medium comprises computer instructions. When the computer instructions are executed by at least one processor, the methods of the first and second aspects are implemented.

[0058] According to the sixth aspect, the present application provides a computer program product. When program code included in the computer program product is executed by a processor of an electronic device, the methods of the first and second aspects are implemented.

[0059] According to the seventh aspect, the present application provides a communication system. The system includes an access control device according to any implementation of the third aspect.

[0060] In a possible implementation, an access device according to any implementation of the fourth aspect is further included.

[0061] The present application provides an access control method and apparatus and a communication system. An information element carrying system status information, a time threshold, and / or access indication information is transmitted to indicate the current system status, so that after a non-vehicle-mounted device receives the aforementioned new information, the non-vehicle-mounted device can determine whether to initiate a random access request. This prevents the CDC from affecting the vehicle-mounted device status check and vehicle-mounted device access due to the initiation of a random access request by the non-vehicle-mounted device at this stage. Additionally, this allows the vehicle-mounted device to operate normally and some basic services to operate normally. Brief explanation of the drawing

[0062] FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application. FIG. 2 is a diagram illustrating information exchange between a CDC, a vehicle-mounted device, and a non-vehicle-mounted device according to one embodiment of the present application. FIG. 3 is a diagram of different types of information exchange between a CDC, a vehicle-mounted device, and a non-vehicle-mounted device according to one embodiment of the present application. FIG. 4 is a diagram illustrating another type of information exchange between a CDC, a vehicle-mounted device, and a non-vehicle-mounted device according to one embodiment of the present application. FIG. 5 is a flowchart of an access control method according to an embodiment of the present application. FIG. 6 is a flowchart of another access control method according to an embodiment of the present application. FIG. 7 is a schematic diagram of an access control device according to an embodiment of the present application. FIG. 8 is a schematic diagram of an access device according to an embodiment of the present application. FIG. 9 is a schematic diagram of a communication system according to an embodiment of the present application. Specific details for implementing the invention

[0063] The following describes the technical solution of an embodiment of the present application with reference to the attached drawings of the embodiment of the present application.

[0064] For convenience of explanation, a smart cockpit scenario applied to a vehicle is used as an example. However, the present application is not limited to vehicle scenarios. The solution of the present application may also be used for short-range communication in other scenarios. FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application. As illustrated in FIG. 1, this scenario exists primarily in a smart cockpit environment inside a vehicle, and the smart cockpit environment may include a CDC, vehicle-mounted devices, and non-vehicle-mounted devices. Vehicle-mounted devices and non-vehicle-mounted devices are two types of nodes with different attributes. Vehicle-mounted devices may include, but are not limited to, electronic devices of the vehicle such as vehicle-mounted microphones, vehicle-mounted speakers, and vehicle-mounted screens. Generally, vehicle-mounted devices are integrated by the vehicle manufacturer (vehicle / automobile manufacturer). Since the integration of vehicle-mounted devices and the CDC is generally performed by a single vehicle manufacturer, the connection relationship between the vehicle-mounted devices and the CDC is fixed. The fixed connection relationship may be, for example, a fixed topology communication relationship. Of course, the fixed connection between the vehicle-mounted devices and the CDC can be wired or wireless. Non-vehicle-mounted devices are all portable electronic devices that do not belong to a vehicle, such as mobile phones, headsets, wearable devices, tablet computers, laptops, digital cameras, personal digital assistants (PDAs), or laptop computers. The CDC connects the vehicle-mounted devices and non-vehicle-mounted devices via wired or wireless means to control or manage them and provides various functions for the smart cockpit environment.

[0065] A vehicle is understood to be a transport device that moves on wheels on the ground, including, but not limited to, automobiles, scooters, trucks, buses, etc. The CDC is connected to infotainment products installed in the vehicle and controls the vehicle's infotainment products. In terms of function, the CDC enables a person to control infotainment facilities and related devices within the vehicle, and can also be used to implement information communication between the vehicle and the external environment. The CDC is generally understood to be referred to as a control domain cockpit or a control domain cockpit CDC. As used in this application, "CDC," "control domain cockpit CDC," and "control domain cockpit" all have the same meaning.

[0066] In the case of wireless connectivity, the Control Domain Cockpit CDC is responsible for the overall management and coordination of wireless resources and must deploy various types of devices for data transmission. Since vehicle-mounted devices and the Control Domain Cockpit CDC are typically integrated by a single vehicle manufacturer, relevant information for the Control Domain Cockpit CDC can be pre-configured in the vehicle-mounted devices, and information related to the vehicle-mounted devices can be pre-configured in the Control Domain Cockpit CDC. For example, vehicle-mounted devices possess vehicle attributes, allowing them to perform authentication and access quickly. However, the existence of non-vehicle-mounted devices is uncertain, and there is little pre-configured relevant information between non-vehicle-mounted devices and the Control Domain Cockpit CDC. When non-vehicle-mounted devices connect to the Control Domain Cockpit CDC, procedures such as discovery, connection, and security authentication are generally required for successful connection and communication. Therefore, a problem that needs to be solved is how to prioritize guaranteeing the status of vehicle-mounted devices and establishing a connection to the Control Domain Cockpit CDC while both the vehicle-mounted devices and the CDC are powered on. Generally, when power is turned on, the control domain cockpit CDC sends a system broadcast message to allow all on-board or non-on-board devices to initiate a connection. However, in this case, the control domain cockpit CDC must first check or learn the status of the on-board devices to establish a connection with them. The control domain cockpit CDC does not expect this process to be interrupted by access from non-on-board devices.

[0067] Accordingly, in the present application, the state of the control domain cockpit CDC is determined, and since the state is carried in the information element of a system broadcast message and transmitted to a non-vehicle-mounted device by broadcast, the non-vehicle-mounted device can determine whether to perform access based on the state of the control domain cockpit CDC. In this way, access to the control domain cockpit CDC by the vehicle-mounted device is ensured not to be affected by access by the non-vehicle-mounted device. Therefore, it is primarily ensured that the vehicle-mounted device operates normally and implements basic service functions.

[0068] In this application, "XX information" and "XX message" may be understood as having the same meaning.

[0069] The following describes the technical solutions in detail in the embodiments of the present application with reference to the attached drawings.

[0070] FIG. 2 is a diagram illustrating information exchange between a control domain cockpit (CDC), a vehicle-mounted device, and a non-vehicle-mounted device according to one embodiment of the present application.

[0071] The present application relates to a communication system comprising a master node and a slave node.

[0072] Master nodes and slave nodes are two types of nodes distinguished by logical function. The master node manages the slave nodes. The master node can schedule resources and is responsible for scheduling time-frequency resources for the slave nodes. The slave nodes communicate with the master node using the time-frequency resources scheduled by the master node. The master node may be an access control device, for example, a control domain cockpit CDC, or another device with access control functions. The slave nodes may be access devices, for example, on-vehicle devices or non-on-vehicle devices.

[0073] A person skilled in the art can learn that the technical solution of the present application may be applied to any type of first device, second device, and third device to which the communication method provided in the present application can be applied, and that the second device and third device are different types of devices capable of communicating with the first device.

[0074] The present application may be applied to the smart cockpit environment illustrated in FIG. 1, and may also be applied to a smart home environment, a smart office environment, or any other environment with similar device relationships. For example, the devices in the environment may be mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, UMPCs, netbooks, mobile phones, PDAs, AR devices, VR devices, AI devices, wearable devices, vehicle-mounted devices, smart home devices, and / or smart city devices. The specific types of the first, second, and third devices are not limited in the embodiments of the present application.

[0075] It should be noted that the interaction between the first device, the second device, and the third device is primarily described using the interaction between the control domain cockpit CDC, the vehicle-mounted device, and the non-vehicle-mounted device as examples in the following embodiments of this application. However, in this application, the first device is not limited to the control domain cockpit (CDC), the second device is not limited to the non-vehicle-mounted device, and the third device is not limited to the vehicle-mounted device. It can be understood that in the following embodiments, the control domain cockpit CDC may be replaced with the first device, the vehicle-mounted device may be replaced with the third device, and the non-vehicle-mounted device may be replaced with the second device.

[0076] As can be seen from Figure 2, generally, after the vehicle is ignited, the power to the control domain cockpit CDC and the vehicle-mounted equipment is turned on and the vehicle starts.

[0077] S201. Send the first indication message.

[0078] The control domain cockpit CDC transmits a first display message so that a vehicle-mounted device or a non-vehicle-mounted device receives the first display message and performs a corresponding operation.

[0079] Optionally, the first indication message may be carried as a system message (system information) or transmitted by broadcasting. For example, the system message may be a system broadcast message. In the following description of this application, a system broadcast message is used as an example. To some extent, the first indication message may be considered a system broadcast message. The system broadcast message may be an MIB, a SIB, or a broadcast frame. An MIB may be carried via a PBCH. A SIB is generally transmitted via an RRC signal. It should be noted that in all embodiments of this application, there is no limitation that the first indication information is transmitted only in a system message or transmitted by broadcasting, and the first indication information may also be transmitted using other types of signaling.

[0080] Generally, Media Access Control (MAC) layer frames are classified into management frames and data frames. Data frames are used to transmit service data exchanged between a master node and a slave node. Before the master node and the slave node can communicate, a communication link must first be established between them so that corresponding operations, such as security authentication and resource allocation, can be performed over that communication link. Management frames are primarily used by the master node to manage the slave node, including, for example, establishing and disconnecting the connection between the master node and the slave node, performing security authentication, allocating communication resources, and enabling hibernation and wake-up. It can be understood that when the aforementioned management functions are implemented, messages sent by the slave node to the master node must also be carried in management frames.

[0081] From the perspective of the receiver of a MAC frame, the MAC frame can be classified into broadcast frames, multicast frames, and unicast frames. A unicast frame is a MAC frame transmitted to a single receiver; a multicast frame is a MAC frame transmitted to a group of receivers; and a broadcast frame is a MAC frame transmitted to all receivers. Certainly, the manner of transmitting the first indication message is not limited in this application, and it can be understood that the first indication message may be transmitted via broadcasting, multicasting, unicasting, or any other equivalent method.

[0082] In some embodiments, before the control domain cockpit CDC transmits a system broadcast message, the control domain cockpit CDC may further determine the system state and then allocate resources corresponding to a vehicle-mounted device or a non-vehicle-mounted device. The first indication message carries indication information, which may be resources allocated to a vehicle-mounted device or a non-vehicle-mounted device and is information used to indicate whether the vehicle-mounted device or the non-vehicle-mounted device can access the control domain cockpit CDC.

[0083] In some examples, the indication information may be expressed by indicating whether a vehicle-mounted device or a non-vehicle-mounted device is allowed to access the control domain cockpit (CDC). For example, a first indication message transmitted to vehicle-mounted device A conveys information indicating that "access to the control domain cockpit CDC is allowed," or a first indication message transmitted to non-vehicle-mounted device B conveys information indicating that "access to the control domain cockpit CDC is not allowed." This information may be expressed as an information element or multiple bits. As another example, the indication information may be system status indication information. A vehicle-mounted device or a non-vehicle-mounted device that receives system status indication information may determine whether access to the control domain cockpit CDC is allowed based on the system status.

[0084] For example, when the power to the control domain cockpit (CDC) is turned on, the control domain cockpit (CDC) may determine the system status of the system currently running in the control domain cockpit (CDC) and generate a first display message. The first display message may convey system status display information. The system status display information may be an element used for status display and may be an element used to display the system status of the system running in the control domain cockpit CDC. In an example, the system status display information may be a Boolean variable. For example, a different state of one bit may represent a different display. In another example, the system status display information may alternatively be an enumeration. Certainly, a person skilled in the art should know that the system status display information may alternatively be any other equivalent data type. This is not limited in the present application.

[0085] Certainly, in some other examples, the display information may alternatively be represented as a resource, e.g., a time domain resource, a frequency domain resource, a code domain resource, a time-frequency resource, or any other equivalent resource. This is not limited herein in this application. Assigning a resource corresponding to a vehicle-mounted device or a non-vehicle-mounted device means that the vehicle-mounted device or the non-vehicle-mounted device can access the control domain cockpit (CDC). Since the assigned corresponding resource can be used as a response resource for the vehicle-mounted device or the non-vehicle-mounted device, it can be understood that response information can be transmitted from the assigned resource to the vehicle-mounted device or the non-vehicle-mounted device.

[0086] For example, when the Control Domain Cockpit CDC allocates a response resource corresponding to a device to perform access, it may determine a response resource corresponding to each device to perform access. The response resource may be a determined specific time-frequency resource. A corresponding time-frequency resource is allocated to each device to ensure that the corresponding device can send response information to the Control Domain Cockpit CDC at the determined time-frequency resource. The response information may indicate the device state of the device performing access. Thus, the first indication message may further convey a correspondence between the response resource and the access device. In an example, the correspondence between the response resource and the access device may be explicit. For example, the correspondence between the response resource and the access device is conveyed directly in a system broadcast message. Certainly, in other examples, the correspondence between the response resource and the access device may be implicit. For example, the access device may obtain a response resource for the access device based on a preset identifier (e.g., ID), a time-frequency resource indicated in a system broadcast message, and a preset rule. In other words, the access device obtains that a preset identifier (e.g., ID), a time-frequency resource indicated in a system broadcast message, and a response resource satisfy a preset rule or mapping relationship. The preset rule may be agreed upon in advance in the protocol, and / or the preset identifier may be configured before the access device is shipped from the factory, or may be configured by the control domain cockpit CDC for the access device when the access device last connects to the control domain cockpit CDC. Certainly, the configured response resource may alternatively be negotiated in advance by the control domain cockpit CDC and the access device, and the control domain cockpit CDC does not use a system broadcast message to convey information about the response message.The corresponding access device can directly display the device status of the access device to the control domain cockpit CDC on the corresponding time-frequency resource based on the negotiated response message.

[0087] In some other embodiments, the control domain cockpit CDC may further group the terminal devices to perform access. It is understood that the terminal devices to perform access may be vehicle-mounted devices or non-vehicle-mounted devices. For example, devices may be grouped according to the location or type of the device. Generally, vehicle-mounted devices and non-vehicle-mounted devices in the same location are not classified into the same group. That is, terminal devices in the same group are all vehicle-mounted devices or non-vehicle-mounted devices, or devices of the same preset type. Optionally, each group has a corresponding multicast address. Of course, it is understood that grouping may be performed according to any standard. This is not limited herein.

[0088] The Control Domain Cockpit CDC groups terminal devices with the same function. Vehicle-mounted devices can be cited as an example. In a smart cockpit environment, rear speakers and microphones can be classified into one group, while front speakers and microphones located in the smart cockpit environment can be classified into another group. As another example, speakers in all locations in a smart cockpit environment can be classified into one group, and microphones in all locations can be classified into another group. The Control Domain Cockpit CDC then allocates response resources corresponding to each device group. The allocated response resources are used by all terminal devices in the group. For the corresponding resources allocated to each group, terminal devices within the group can understand that response resources for the terminal device can be determined from the response resources allocated to the group according to specific rules. Similarly, a similar grouping method can be implemented for non-vehicle-mounted devices.

[0089] In another example, the group may take the form of an array. For instance, speakers or microphones may be in the array. Typically, the physical locations of multiple terminal devices in the array are close together, and there is a central node to manage the devices in the array. In the case of an array, since one response resource may be allocated to each array, the array can provide feedback on the status of the devices in the array from the allocated response resource.

[0090] In one example, after the power to the vehicle-mounted device is turned on, a self-check of the vehicle-mounted device may be performed based on a pre-set program or command. The self-check of the vehicle-mounted device is primarily performed to check whether problems such as damage or errors occur in the vehicle-mounted device, and can be understood as ensuring that the vehicle-mounted device can operate normally. The pre-configured information may be configuration information stored in advance in the vehicle-mounted device. In one example, the configuration information of the vehicle-mounted device may be configured before the vehicle leaves the factory, or, of course, may be pre-configured in other ways before the power to the vehicle-mounted device is turned on.

[0091] In some examples, the device to perform access is a vehicle-mounted device. Since the probability of a vehicle-mounted device exception occurring is very low, when allocating response resources corresponding to vehicle-mounted devices or non-vehicle-mounted devices, the control domain cockpit CDC can be configured to use the response resources only for vehicle-mounted devices with abnormal device status, so that only abnormal devices transmit device status from the response resources to the control domain cockpit CDC.

[0092] S202. Receive the first indication message and additionally determine the corresponding resource.

[0093] In the case of a vehicle-mounted device, after receiving a first indication message transmitted by the control domain cockpit (CDC), the vehicle-mounted device may determine whether access to the control domain cockpit (CDC) is permitted based on the first indication message. If the vehicle-mounted device can obtain a response resource corresponding to the vehicle-mounted device from the first indication message, the vehicle-mounted device may be deemed to have access to the control domain cockpit (CDC). If the correspondence between the response resource and the access device is explicit, it can be understood that each vehicle-mounted device can obtain a response resource corresponding to the vehicle-mounted device directly from the first indication message. Certainly, if the correspondence between the response resource and the access device is implicit, each vehicle-mounted device may obtain a response resource for the access device through computing based on a pre-configured identifier (e.g., ID), a time-frequency resource indicated in a system broadcast message, and a pre-set rule. The response resources corresponding to different terminal devices may differ, that is, the control domain cockpit CDC may allocate response resources to different terminal devices respectively; Alternatively, the response resources may be identical; that is, it can be understood that different terminal devices share the same response resources.

[0094] In some examples, the vehicle-mounted device may generate a response message after receiving a first display message.

[0095] After acquiring a corresponding response resource, the vehicle-mounted device may generate a response message of the vehicle-mounted device. The response message includes device status information. Device status information is used to indicate the device status of the terminal device, for example, a normal state or an abnormal state. Certainly, in some examples, the device status information may be represented by 0 and 1. For example, 1 indicates the normal state of the device and 0 indicates the abnormal state of the device. Certainly, in some other examples, 0 indicates the normal state of the device and 1 indicates the abnormal state of the device. Certainly, other equivalent forms, such as values, characters, or words, may be used as alternatives. This is not limited to the present application.

[0096] It can be understood that the response message may further include the device ID.

[0097] It can be understood that in some examples, both parties may agree in their protocols that only devices in an abnormal state are reported. In this case, the response message may include only the device ID, and upon receiving the device ID, the CDC can determine that the device is in an abnormal state. Similarly, an alternative agreement may be reached in protocols where only devices in a normal state are reported, the details of which are not described here.

[0098] In some examples, the device may report both the device ID and the device status. If device 1 is in a healthy state, the response message may indicate the ID of device 1 and indicate that the status is healthy. If device 2 is in an unhealthy state, the response message may indicate the ID of device 2 and indicate that the status is unhealthy. For example, information such as "status is healthy" or "status is unhealthy" may be represented by information elements or multiple bits.

[0099] In some examples, the CDC requires only the unhealthy device to report a response message. Assume that Device 1 and Device 2 are classified into a single group and a shared response resource is allocated, and the group address is ID 1. Device 1 is in a healthy state and Device 2 is in an unhealthy state. In this case, Device 2 can transmit Device 2's ID or the group address ID 1 to which Device 2 belongs on the resource.

[0100] When the Control Domain Cockpit (CDC) groups vehicle-mounted devices, the device group may be in the form of an array. For multiple vehicle-mounted devices in the array, a single response message is jointly generated to indicate the device status of the devices in the array. For example, 1 indicates a normal state of a device in the array, and 0 indicates an abnormal state of a device in the array. Certainly, in some other examples, 0 indicates a normal state of a device in the array, and 1 indicates an abnormal state of a device in the array.

[0101] Regarding the state of the devices in the array, if all devices in the array are in a normal state, the devices in the device group are considered to be in a normal state; if any quantity of devices in the array are in an abnormal state, the devices in the array are considered to be in an abnormal state. Certainly, in other examples, the state of the devices in the array may alternatively be determined based on the ratio of normal devices or abnormal devices in the array. For example, if the ratio of normal devices or abnormal devices is higher than a preset ratio threshold, the devices in the array are considered to be in an abnormal state; otherwise, the devices in the array are considered to be in a normal state. Certainly, the state of the devices in the array may alternatively be determined based on the quantity of abnormal devices in the array. For example, if the number of abnormal devices in the array exceeds a preset quantity threshold, the devices in the array are considered to be in an abnormal state; otherwise, the devices in the array are considered to be in a normal state. The state of the devices in the array may be determined in an equivalent manner. This is not limited herein.

[0102] In some examples, when a vehicle-mounted device generates a response message, the device ID of the vehicle-mounted device may be further carried. When multiple vehicle-mounted devices form an array, the response message may further include at least one of an array address and a multicast address.

[0103] In some other examples, the response resource may be shared by multiple on-board devices. For a device in an abnormal state, the device may send its ID to the response resource, so when the control domain cockpit CDC receives the response message, the control domain cockpit CDC determines which on-board device is in an abnormal state. Generally, since both the control domain cockpit (CDC) and the on-board devices are manufactured by a single vehicle manufacturer and integrated into a single vehicle, the control domain cockpit (CDC) can store the IDs of the on-board devices in advance.

[0104] Generally, since the failure rate of onboard devices is low and the probability of two devices being in an abnormal state simultaneously is also low, it can be understood that it is appropriate to allocate shared response resources to multiple onboard devices.

[0105] S203. Send a response message from the corresponding resource. Note that this step is optional and is intended only for vehicle-mounted devices that are allowed access and can send response messages. Vehicle-mounted devices that are not allowed access do not need to send a response message.

[0106] Optionally, after generating corresponding response information, the vehicle-mounted device can transmit a response message for a response resource corresponding to the vehicle-mounted device to the control domain cockpit CDC.

[0107] S204. Receive a response message and additionally generate a second display message.

[0108] The execution of S204 corresponds to the execution of S203. It can be understood that after receiving a response message, the control domain cockpit CDC may redetermine the system state. If the control domain cockpit CDC does not receive a response message, there may be no need to redetermine the system state. Certainly, in other examples, alternatively, the control domain cockpit CDC may determine the system state periodically, semi-periodically, or non-periodically without determining whether a response message transmitted by a vehicle-mounted device has been received.

[0109] After receiving a response message sent by a vehicle-mounted device, if the corresponding response resource is assigned to a different vehicle-mounted device or array, the control domain cockpit CDC can determine which vehicle-mounted device or array will send the response message based on the different response resource. Then, it determines whether the vehicle-mounted device or array is in an abnormal state based on the device state of the response message or the device state of the array. Certainly, if the control domain cockpit CDC does not assign time-frequency resources to different vehicle-mounted devices respectively, the response information additionally carries a device ID. Therefore, whether a vehicle-mounted device or device group is in an abnormal state can be determined based on the device ID.

[0110] After determining the device status of the vehicle-mounted device, the control domain cockpit CDC may redetermine the system status and determine a second display message based on the new system status. The second display message is a new system broadcast message. The type of the new system broadcast message is the same as or different from the system broadcast message of S201. For convenience of explanation, details are not described again here.

[0111] If the control domain cockpit CDC receives a response message and determines that all expected vehicle-mounted devices are in a normal state, the control domain cockpit CDC may redetermine the system state and allow access to non-vehicle-mounted devices by transmitting a second indication message.

[0112] Of course, if the vehicle-mounted device expected by the control domain cockpit CDC is in an abnormal state or requires other processing, the control domain cockpit CDC may not re-determine the system state. Since system broadcast messages are generally transmitted periodically, non-vehicle-mounted devices still perform operations according to the instructions of the first indication message.

[0113] It can be understood that receiving response messages and re-determining the system state may be related to some extent or independent of each other.

[0114] For example, a system state may include any one of a system ready state, a vehicle-mounted device access state, a system running state, or an access allowed state. Of course, in other examples, other possible system states may be included. This is not limited to the present application. A system ready state and / or a vehicle-mounted device access state may be used to indicate that a vehicle-mounted device is accessing the control domain cockpit CDC or that a vehicle-mounted device is performing a self-check, so that a non-vehicle-mounted device may choose not to access the control domain cockpit CDC depending on these types of system states. A system running state and / or an access allowed state may be used to indicate that a vehicle-mounted device has accessed the control domain cockpit CDC. In this case, a non-vehicle-mounted device may be allowed to access the control domain cockpit CDC.

[0115] A person of ordinary skill in the field will understand that the process of the control domain cockpit CDC determining the status of the vehicle-mounted device can also be regarded as the process of the vehicle-mounted device accessing the control domain cockpit CDC. The response message sent by the vehicle-mounted device can be viewed to some extent as an access request message from the vehicle-mounted device.

[0116] Return to S201. After the control domain cockpit CDC transmits the first indication message, the non-vehicle-mounted device may also receive the first indication message transmitted by the control domain cockpit CDC. Thus, the following steps may be further performed after S201.

[0117] S205. Receive the first indication message.

[0118] In the case of a non-vehicle-mounted device, for example, when a first indication message transmitted by the control domain cockpit CDC is received, if the first indication message is a system broadcast message, the non-vehicle-mounted device may access the control domain cockpit CDC based on the system broadcast message. In one example, the system state of a system currently running in the control domain cockpit CDC may be determined based on system state indication information included in the system broadcast message, and whether access to the control domain cockpit CDC by the non-vehicle-mounted device is allowed is determined based on the system state. Of course, in another example, if the first indication message transmitted by the control domain cockpit CDC directly indicates whether the non-vehicle-mounted device is allowed to access the control domain cockpit CDC, based on the information of the first indication message, S207 may be performed if the non-vehicle-mounted device cannot access the control domain cockpit CDC; or S208 may be performed if the non-vehicle-mounted device is allowed to access the control domain cockpit CDC.

[0119] S206. Check if the system status is a preset system status. Note that this step is optional and applies only if the first display message includes system status display information. If the first display message includes information to directly indicate whether access is allowed, it is not necessary to determine the system status.

[0120] Specifically, in S205, the non-vehicle-mounted device determines whether the system state is a preset system state.

[0121] In one example, if the preset system state is the system ready state or the vehicle-mounted device access state, it is determined that the non-vehicle-mounted device is not allowed to access the control domain cockpit (CDC), and S207 is performed; otherwise, it is determined that the non-vehicle-mounted device can access the control domain cockpit CDC, and S208 is performed. Certainly, the system state may alternatively be other equivalent system states. This is not limited to the above. However, in this example, if the system state is the preset system state, it can be understood that the vehicle-mounted device is performing device access.

[0122] In another example, if the preset system state is the system running state or the access allowed state, it is determined that the non-vehicle-mounted device can access the control domain cockpit (CDC), and S208 is performed; otherwise, it is determined that the non-vehicle-mounted device cannot access the control domain cockpit CDC, and S207 is performed. Certainly, the system state may alternatively be other equivalent system states. This is not limited herein in this application. In this example, if the system state is the preset system state, the vehicle-mounted device may be understood as having completed device access.

[0123] S207. Prevent non-vehicle-mounted devices from initiating random access requests.

[0124] Non-vehicle-mounted devices are prohibited from initiating random access requests to the control domain cockpit CDC.

[0125] S208. Allows a non-vehicle-mounted device to initiate a random access request.

[0126] Non-vehicle-mounted devices can initiate random access requests to the control domain cockpit CDC.

[0127] In the present application, a system broadcast message carries system status indication information. When a vehicle-mounted device performs a self-check or establishes a connection to the control domain cockpit CDC, non-vehicle-mounted devices are prohibited from initiating random access requests. This prevents the initiation of random access requests by non-vehicle-mounted devices at this stage from affecting the status check of the vehicle-mounted device by the control domain cockpit CDC and the access of the vehicle-mounted device. In this way, it is ensured that the vehicle-mounted device operates normally and that some basic services can be executed normally.

[0128] FIG. 3 is a diagram illustrating different types of information exchange between a CDC, a vehicle-mounted device, and a non-vehicle-mounted device according to one embodiment of the present application.

[0129] Instead of the method of determining the system state described in S201 of FIG. 2, in other cases, a method of setting a time threshold may be used. For example, S301 may be performed.

[0130] S301. Send the first indication message.

[0131] The control domain cockpit CDC transmits a first indication message so that, after a non-vehicle-mounted device receives the first indication message, the non-vehicle-mounted device determines whether to allow access to the control domain cockpit CDC. Optionally, the first indication message may be a system broadcast message. Certainly, the manner of transmitting the first indication message is not limited in this application, and it is understood that the first indication message may be transmitted via broadcasting, multicasting, or any other equivalent method. It is understood that this application primarily describes a method to avoid the influence on the status check of the vehicle-mounted device and the access of the vehicle-mounted device by the control domain cockpit CDC resulting from the initiation of a random access request by the non-vehicle-mounted device at this stage. Accordingly, the vehicle-mounted device may ignore the time threshold information in the first indication message. Certainly, in some examples, the vehicle-mounted device may alternatively determine whether to access the control domain cockpit CDC based on the time threshold information.

[0132] In some embodiments, the first indication message may carry time threshold information. The time threshold information may be time domain indication information used to indicate the time threshold. The time threshold information may be a system frame number (SFN) or an offset from a specific fixed reference frame. For example, the fixed reference frame may be the first reference frame. The fixed reference frame may be frame 0, and certainly alternatively any other reference frame. Certainly, the time threshold may alternatively be a specific value or a time range. This is not limited herein.

[0133] In an optional implementation, the time threshold information may be a system frame number. For example, system frame number 256. If a non-vehicle-mounted device determines that the current system frame number is less than or equal to system frame number 256, the non-vehicle-mounted device cannot initiate access.

[0134] In other optional implementations, the time threshold information may be one or more time domain offsets for a specific fixed reference frame. For example, the time domain offset may be 256ms. The fixed reference frame may be agreed upon in advance between the unit with the CDC and the vehicle-mounted or non-vehicle-mounted device, or defined in the protocol. For example, assume the fixed reference frame is frame 64 and the time length of a single frame is 0.5ms. Assume the current frame number is 20 and the current absolute time is 10ms. The non-vehicle-mounted device cannot initiate access within an absolute time of 256ms + 64 x 0.5 = 288ms.

[0135] In another optional implementation, the time threshold information may alternatively be a time domain offset for the first signaling. The time domain offset may be a time threshold indicating that the initiation of random access is not permitted within a specific time range.

[0136] The first signaling may be a specific signaling or protocol defined in a protocol that is agreed upon or negotiated in advance between the control domain cockpit CDC and the non-vehicle-mounted device. A specific RRC signal is given as an example. The RRC signaling includes a SIB. For example, the SIB may be transmitted periodically. If the SIB is transmitted at a specific fixed time, in a possible implementation, the control domain cockpit CDC may not be allowed to allow the non-vehicle-mounted device to initiate access in a specific time window after the control domain cockpit CDC transmits the SIB, because the control domain cockpit CDC may need to handle other issues during this period. In this case, at the moment the CDC transmits the SIB + [time domain offset 1, time domain offset 2], the terminal is not allowed to initiate random access to the CDC in the time window [the moment the CDC transmits the SIB + time domain offset, the moment the CDC transmits the SIB + time domain offset 2]. It can be understood that the RRC signaling may be carried in a management frame. It should be noted that [time domain offset 1, time domain offset 2] can be represented as an information element or multiple bits.

[0137] As another example, in a possible implementation, because the control domain cockpit CDC may need to handle other issues during this period, a non-vehicle-mounted device may not be allowed to initiate access in a specific time window after acquiring a specific RRC signaling (e.g., the first RRC signaling). For example, if the moment when the non-vehicle-mounted device successfully receives the first RRC signaling is the first moment, the terminal is not allowed to initiate random access to the control domain cockpit (CDC) in the time window [first moment + time domain offset 1, first moment + time domain offset 2]. It can be understood that the RRC signaling may be carried in a control frame.

[0138] It can be understood that the time threshold information can be a single time domain offset or multiple time domain offsets.

[0139] When a vehicle-mounted device performs a self-check or accesses the control domain cockpit CDC, in order to ensure that the vehicle-mounted device is not affected by access from non-vehicle-mounted devices, the time threshold information carried in the first indication message may be for non-vehicle-mounted devices. In one example, different time thresholds may be set for different non-vehicle-mounted devices. Of course, if there is a device group containing multiple non-vehicle-mounted devices, the device group may be in the form of an array. Alternatively, different time thresholds may be set for different arrays of non-vehicle-mounted devices. This is not limited herein by this application. In other examples, the format of the expression of the time threshold in the system broadcast message may be explicit or certainly implicit. Refer to S201 for the implementation process. For convenience of explanation, details are not described again herein.

[0140] For setting the time threshold, the control domain cockpit (CDC) can be set based on the self-check status of the vehicle-mounted device or the connection setting status with the control domain cockpit (CDC).

[0141] S202 and S203 are performed after S301. The implementation process of S202 and S203 in Fig. 2 is identical to S202 and S203 in Fig. 3. For convenience of explanation, details are not described again here.

[0142] S302 can be performed after S203.

[0143] S302. Receive a response message and additionally generate a second display message.

[0144] The execution of S302 corresponds to the execution of S203. It can be understood that after receiving a response message, the control domain cockpit CDC may reset the time threshold for other non-vehicle-mounted devices. If the control domain cockpit CDC does not receive a response message, there may be no need to reset the time threshold. In another example, alternatively, the control domain cockpit CDC may set the time threshold periodically, semi-periodically, or non-periodically without determining whether a response message transmitted by a vehicle-mounted device is received.

[0145] Specifically, the time threshold may be reset after a response message is received. It can be understood that receiving a response message and resetting the time threshold may be somewhat related or independent of each other.

[0146] After receiving a response message transmitted from a vehicle-mounted device, the control domain cockpit CDC determines the device status of the vehicle-mounted device and resets the time threshold based on the device status of the vehicle-mounted device. Then, a second display message can be determined based on the new time threshold. The second display message is a new system broadcast message. The type of the new system broadcast message is the same as or different from the system broadcast message of S301. For convenience of explanation, details are not described again here.

[0147] Return to S301. After the control domain cockpit CDC transmits the first indication message, the non-vehicle-mounted device may also receive the first indication message transmitted by the control domain cockpit CDC. Thus, the following steps may be performed further after S301.

[0148] S303. Receive the first indication message.

[0149] In the case of a non-vehicle-mounted device, for example, when a first indication message transmitted by the control domain cockpit CDC is received, if the first indication message is a system broadcast message, whether the non-vehicle-mounted device can access the control domain cockpit CDC is determined based on the system broadcast message. In one example, a time threshold set by the control domain cockpit CDC for the non-vehicle-mounted device may be determined based on the time threshold information included in the system broadcast message and whether the non-vehicle-mounted device is allowed, and whether the non-vehicle-mounted device is allowed to access the control domain cockpit CDC is determined based on the time threshold of the non-vehicle-mounted device. Of course, in another example, if the first indication message transmitted by the control domain cockpit CDC directly indicates whether the non-vehicle-mounted device is allowed to access the control domain cockpit CDC, S207 is performed if the non-vehicle-mounted device cannot access the control domain cockpit CDC based on the information of the first indication message; Alternatively, S208 may be performed if a non-vehicle-mounted device is allowed to access the control domain cockpit CDC.

[0150] S304. Check whether the current moment reaches the time threshold. Note that this step is optional and applies only if the first indication message includes time threshold information. If the first indication message directly indicates whether access is allowed, there is no need to determine whether the time threshold is reached.

[0151] Specifically, a non-vehicle-mounted device determines whether the current moment reaches a time threshold.

[0152] In the example, if the current moment reaches the time specified by the time threshold, it is determined that the non-vehicle-mounted device cannot access the control domain cockpit CDC and S207 is performed; otherwise, it is determined that the non-vehicle-mounted device can access the control domain cockpit CDC and S208 is performed. Certainly, the time threshold may be a system frame number or an offset from a specific fixed reference frame.

[0153] The implementation process of S207 and S208 is the same as that of S207 and S208 in Fig. 2. For the convenience of explanation, details are not described again here.

[0154] In this application, a system broadcast message carries time threshold information to ensure that a non-vehicle-mounted device is prohibited from initiating a random access request before reaching a preset time threshold, or that a non-vehicle-mounted device is allowed to initiate a random access request after reaching a preset time threshold. This prevents, at this stage, the initiation of a random access request by a non-vehicle-mounted device from affecting the status verification of the vehicle-mounted device and vehicle-mounted device access by the CDC. In this way, it is ensured that the vehicle-mounted device operates normally and that some basic services can be executed normally.

[0155] FIG. 4 is a diagram illustrating another type of information exchange between a CDC, a vehicle-mounted device, and a non-vehicle-mounted device according to one embodiment of the present application.

[0156] Instead of the method for determining the system state described in S201 of FIG. 2 and the method for setting the time threshold described in S301 of FIG. 3, a method for setting access indication information in another case may be used. For example, S401 may be performed.

[0157] S401. Send the first indication message.

[0158] The control domain cockpit CDC transmits a first indication message, and after a vehicle-mounted device or a non-vehicle-mounted device receives the first indication message, determines whether the vehicle-mounted device or the non-vehicle-mounted device is allowed access to the control domain cockpit CDC. Optionally, the first indication message may be a system broadcast message. Certainly, the manner of transmitting the first indication message is not limited in this application, and it is understood that the first indication message may be transmitted by broadcasting, multicasting, or any other equivalent method.

[0159] In some embodiments, system broadcast messages may convey access indication information. Access indication information may be a mapping table for device types and access relationships; that is, access indication information may indicate a mapping relationship between device types and access relationships. The mapping table or mapping relationship is used to indicate device types that can initiate random access requests and device types that are prohibited from initiating random access requests. For example, device types may be classified into vehicle-mounted devices and non-vehicle-mounted devices; or may be classified into microphones, speakers, mobile phones, etc.; or may be classified into vehicle-mounted devices previously connected to the control domain cockpit CDC or vehicle-mounted devices not connected to the control domain cockpit CDC, etc. Device types may also be indicated by a corresponding type index or number. This is not limited herein.

[0160] Mapping tables for device types and access relationships may be explicit or implicit. For example, an explicit correspondence table may be constructed as shown in Table 1. All tables in the solution of this application are intended to reflect correspondences and are merely forms of representation of correspondences. Other forms of representation capable of reflecting correspondences may replace the tables. In this application, tables are generalized to all possible forms of representation.

[0161] terminal device Access relationships Vehicle-mounted microphone 0 Vehicle-mounted speakers 0 mobile phone 1

[0162] It is assumed that 0 indicates access is allowed and 1 indicates access is not allowed. From Table 1, it can be seen that access to vehicle-mounted microphones and vehicle-mounted speakers is allowed, while access to mobile phones is not allowed. Of course, it can be understood that the type of response device may also be indicated by the device type display information. For example, if "000" is used to identify a vehicle-mounted microphone, {000, 0} may indicate that access to the vehicle-mounted microphone is allowed.

[0163] For example, if a mapping table for device types and access relationships is implicit according to protocol agreement, a bitmap may be used to indicate the device types that are allowed access. Generally, according to protocol agreement, each bit of the bitmap can identify a device type. Assuming the length of the bitmap is 3 bits, each bit corresponds sequentially to a vehicle-mounted microphone, a vehicle-mounted speaker, and a mobile phone. When bitmap {001} is transmitted, it indicates that access to the vehicle-mounted microphone and the vehicle-mounted speaker is allowed, and access to the mobile phone is not allowed. Certainly, in other examples, or alternatively, 1 may indicate that access is allowed and 0 may indicate that access is not allowed, or any other number may be used for equivalent substitution. This is not limited herein.

[0164] In one example, different types of devices may also have different device priorities. A mapping table for device types and access relationships may be replaced with a mapping table based on device priorities and access relationships. The mapping table is used to indicate whether devices with different priorities can initiate random access requests. Certainly, it can be understood that different types of devices may have the same device priority. Optionally, the device priority may also be the access priority. Generally, a device with a higher priority may have a higher access priority. For example, the priority of a vehicle-mounted microphone and a vehicle-mounted speaker is 1, and the priority of a mobile phone is 2. Access to the vehicle-mounted microphone and a vehicle-mounted speaker is allowed when the device priority included in the first indication message is 1.

[0165] As another example, if there is a device group including multiple non-vehicle-mounted devices, the device group may be in the form of an array. For arrays of different non-vehicle-mounted devices, a mapping table for device types and access relationships, or a mapping table based on device priorities and access relationships, may be established. This is not limited herein by this application. In other examples, the form of expression of access indication information in system broadcast messages may be explicit or certainly implicit. Refer to S201 for the implementation process. For convenience of explanation, details are not described again herein.

[0166] S202 and S203 are performed after S401. The implementation process of S202 and S203 in FIG. 4 is the same as that of S202 and S203 in FIG. 2. For the convenience of explanation, details are not described again here.

[0167] S402 can be performed after S203.

[0168] S402. Receive a response message and additionally generate a second display message.

[0169] The execution of S402 corresponds to the execution of S203. It can be understood if the control domain cockpit CDC receives a response message and determines that all expected vehicle-mounted devices are in a normal state. In this case, the control domain cockpit (CDC) may reset the access indication information and transmit a second indication message to allow access to non-vehicle-mounted devices. Of course, if the vehicle-mounted devices expected by the control domain cockpit (CDC) are in an abnormal state or other processing needs to be performed, the control domain cockpit (CDC) may not reset the access indication information. Since system broadcast messages are generally transmitted periodically, non-vehicle-mounted devices still perform operations according to the instructions of the first indication message.

[0170] After receiving a response message transmitted from a vehicle-mounted device, the control domain cockpit CDC determines the device status of the vehicle-mounted device and resets the access display information based on the device status of the vehicle-mounted device. Then, a second display message can be determined based on the new display information. The second display message is a new system message. The type of the new system message is the same as or different from the system broadcast message of S301. For the convenience of explanation, details are not described again here.

[0171] Return to S401. After the control domain cockpit CDC transmits the first indication message, the non-vehicle-mounted device may also receive the first indication message transmitted by the control domain cockpit CDC. Thus, the following steps may be performed further after S401.

[0172] S403. Receive the first indication message.

[0173] In the case of a non-vehicle-mounted device, for example, when a first indication message transmitted by the control domain cockpit CDC is received, if the first indication message is a system broadcast message, whether the non-vehicle-mounted device can access the control domain cockpit CDC is determined based on the system broadcast message. In one example, the device type and access relationship of the non-vehicle-mounted device may be determined based on access indication information carried in the system broadcast message, and whether the non-vehicle-mounted device is allowed to access the control domain cockpit CDC is determined based on the device type and access relationship. Of course, in another example, if the first indication message transmitted by the control domain cockpit CDC directly indicates whether the non-vehicle-mounted device is allowed to access the control domain cockpit CDC, S207 may be performed if the non-vehicle-mounted device cannot access the control domain cockpit CDC based on the information of the first indication message; or S208 may be performed if the non-vehicle-mounted device is allowed to access the control domain cockpit CDC.

[0174] S404. Determine whether the access indicator information satisfies a preset condition. Note that this step is optional and applies only if the first indicator message contains the access indicator information. If the first indicator message directly indicates whether access is allowed, there is no need to determine whether the access indicator information satisfies the preset condition.

[0175] Specifically, the non-vehicle-mounted device determines whether the device type of the non-vehicle-mounted device can initiate a random access request based on the device type and access relationship determined in S403.

[0176] In one example, if the device type of the non-vehicle-mounted device does not allow the initiation of a random access request, it is determined that the non-vehicle-mounted device does not allow access to the control domain cockpit CDC, and S207 is performed; or if the device type of the non-vehicle-mounted device allows the initiation of a random access request, it is determined that the non-vehicle-mounted device is allowed to access the control domain cockpit CDC, and S208 is performed.

[0177] The implementation process of S207 and S208 is the same as that of S207 and S208 in Fig. 2. For the convenience of explanation, details are not described again here.

[0178] In this application, system broadcast messages carry access indication information to ensure that only devices whose device type meets preset conditions are allowed to send random access requests, and that devices whose device type does not meet preset conditions are prohibited from sending random access requests. This prevents the CDC from affecting the status check of the vehicle-mounted device and access to the vehicle-mounted device due to the initiation of random access requests by non-vehicle-mounted devices. In this way, it is ensured that the vehicle-mounted device operates normally and that some basic services can be executed normally.

[0179] Certainly, a person skilled in the art should know that the time threshold set in FIG. 3 and the access indicator information set in FIG. 4 can be used together with the system state determined in FIG. 2. Of course, by selecting any one or both of the time threshold, access indicator information, and system state, the control domain cockpit CDC can control access to vehicle-mounted devices and non-vehicle-mounted devices.

[0180] FIG. 5 is a flowchart of an access control method according to one embodiment of the present application.

[0181] As illustrated in FIG. 5, the present application provides an access control method. The interaction process of FIG. 2 through 4 can be implemented using this method. This method may include the following steps.

[0182] S501. Check if the state of the first device is the first state.

[0183] S502. Send first indication information. The first indication information is used to indicate whether access by at least one second device to the first device is allowed. Optionally, the first indication information may be included in a system message or transmitted by broadcast. For example, the system message may be a system broadcast message. The first indication information may be an MIB, a SIB, or a broadcast frame. An MIB may be carried via a PBCH. A SIB is typically included in RRC signaling.

[0184] In a possible implementation, the first state includes at least one of a system ready state and a vehicle-mounted device access state, and the first indication information is used to indicate that access by at least one second device is not permitted; or the first state includes at least one of a system running state and an access allowed state, and the first indication information is used to indicate that access by the second device is permitted. The system ready state and / or vehicle-mounted device access state may be used to indicate that the vehicle-mounted device is accessing the control domain cockpit CDC or that the vehicle-mounted device is performing a self-check, so that the vehicle-mounted device may choose not to access the control domain cockpit CDC according to these types of system states. The system running state and / or access allowed state may be used to indicate that the vehicle-mounted device has accessed the control domain cockpit CDC. In this case, non-vehicle-mounted devices may be permitted to access the control domain cockpit CDC.

[0185] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0186] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0187] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0188] In a possible implementation, the first indicator information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information. The first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on the priority information and the access indicator information.

[0189] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that at least one second device is not allowed to access the first device within the first time range.

[0190] In a possible implementation, the first time range is a time domain offset relative to the first reference frame or a time domain offset relative to the first signaling. The first reference frame may be a first system frame number agreed upon or consensual in advance between the control domain cockpit (CDC) and the non-vehicle-mounted device, or a first system frame number defined in the protocol. The first signaling may be a specific signaling agreed upon or consensual in advance between the control domain cockpit CDC and the non-vehicle-mounted device, or a specific signaling defined in the protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets.

[0191] In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0192] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0193] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0194] In a possible implementation, the device type includes at least one of a vehicle-mounted device and a non-vehicle-mounted device.

[0195] FIG. 6 is a flowchart of another access control method according to an embodiment of the present application.

[0196] As illustrated in FIG. 6, the present application provides another access control method. The interaction process of FIGS. 2 through 4 can be implemented using this method. This method may include the following steps.

[0197] S601. Receive first indication information from the first device. Optionally, the first indication information is included in a system message or transmitted as a broadcast. For example, the system message may be a system broadcast message. The first indication information may be an MIB, a SIB, or a broadcast frame. An MIB may be carried via a PBCH. A SIB is typically included in RRC signaling.

[0198] S602. Based on the first indication information, determine whether access of the second device to the first device is allowed.

[0199] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0200] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0201] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0202] In a possible implementation, the first indicator information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information. The first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on the priority information and the access indicator information.

[0203] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that at least one second device is not allowed to access the first device within the first time range.

[0204] In a possible implementation, the first time range is a time domain offset for a first reference frame or a time domain offset for a first signaling. The first reference frame may be a first system frame number agreed upon in advance between a control domain cockpit (CDC) and a non-vehicle-mounted device, or a first system frame number defined in a protocol. The first signaling may be a specific signaling agreed upon in advance between a control domain cockpit CDC and a non-vehicle-mounted device, or a specific signaling defined in a protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets. In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0205] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0206] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0207] In a possible implementation, the first device is a control domain cockpit CDC, the third device is a vehicle-mounted device, and the second device is a non-vehicle-mounted device.

[0208] In a possible implementation, the second device is a mobile phone.

[0209] FIG. 7 is a schematic diagram of an access control device according to an embodiment of the present application.

[0210] As illustrated in FIG. 7, the present application provides an access control device (700). The access control device (700) may be a first device, e.g., a control domain cockpit (CDC), or the access control device may be a chip, internal component, etc. of the first device. Certainly, the access control device may alternatively be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, mobile phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, vehicle-mounted device, smart home device, and / or smart city device. In this embodiment of the present application, the specific type of the first device is not limited.

[0211] The access control device (700) can implement the interaction process of FIGS. 2 through 7. The access control device (700) includes: a processing unit (701) configured to determine that the state of a first device is a first state; and a transmitting unit (702) configured to transmit first indication information, wherein the first indication information is used to indicate whether access by at least one second device to the first device is allowed. Optionally, the first indication information is included in a system message or transmitted via broadcast. The first indication information may be an MIB, a SIB, or a broadcast frame. An MIB may be carried via a PBCH. A SIB is generally included in RRC signaling. Optionally, the first indication information is transmitted by broadcasting.

[0212] In a possible implementation, the first state includes at least one of a system ready state and a vehicle-mounted device access state, and the first indication information is used to indicate that access by at least one second device is not allowed; or the first state includes at least one of a system running state and an access allowed state, and the first indication information is used to indicate that access by the second device is allowed. The system ready state and the vehicle-mounted device access state may be used to indicate that the vehicle-mounted device is accessing the control domain cockpit CDC or that the vehicle-mounted device is performing a self-check, so that a non-vehicle-mounted device may choose not to access the control domain cockpit CDC according to these types of system states. The system running state and the access allowed state may be used to indicate that the vehicle-mounted device has accessed the control domain cockpit CDC. In this case, access by a non-vehicle-mounted device to the control domain cockpit CDC is allowed.

[0213] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0214] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0215] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0216] In a possible implementation, the first indicator information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information. The first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on the priority information and the access indicator information.

[0217] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that at least one second device is not allowed to access the first device within the first time range.

[0218] In a possible implementation, the first time range is a time domain offset for a first reference frame or a time domain offset for a first signaling. The first reference frame may be a first system frame number agreed upon or consensual in advance between the control domain cockpit (CDC) and a non-vehicle-mounted device, or a first system frame number defined in the protocol. The first signaling may be a specific signaling agreed upon or consensual in advance between the control domain cockpit CDC and a non-vehicle-mounted device, or a specific signaling defined in the protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets.

[0219] In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0220] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0221] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0222] In a possible implementation, the device type includes at least one of a vehicle-mounted device and a non-vehicle-mounted device.

[0223] FIG. 8 is a schematic diagram of an access device according to an embodiment of the present application.

[0224] As illustrated in FIG. 8, the present application provides an access device (800). The access device (800) may be a second device or a third device, e.g., a vehicle-mounted device or a non-vehicle-mounted device, or the access device may be a chip or internal component of the second device or the third device, e.g., a chip or internal component of the vehicle-mounted device or a non-vehicle-mounted device. Certainly, the access device may alternatively be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, a UMPC, a netbook, a cellular phone, a PDA, an AR device, a VR device, an AI device, a wearable device, a vehicle-mounted device, a smart home device and / or a smart city device. In this embodiment of the present application, the specific type of the first device is not limited.

[0225] The access device (800) may be configured to implement the interaction process of FIGS. 2 through 4. The access device (800) includes a receiving unit (801) and a processing unit (802). The receiving unit (801) is configured to receive first indication information from a first device. The processing unit (802) is configured to determine whether access by a second device to the first device is permitted based on the first indication information. Optionally, the first indication information may be included in a system message or transmitted by broadcast. For example, the system message may be a system broadcast message. The first indication information may be an MIB, a SIB, or a broadcast frame. An MIB may be carried via a PBCH. A SIB is generally included in RRC signaling.

[0226] In a possible implementation, the first indication information is used to indicate whether access by at least one third device is allowed.

[0227] In a possible implementation, the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Additionally, the second device determines whether to access the first device based on the device type information.

[0228] In a possible implementation, the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed.

[0229] In a possible implementation, the first indicator information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information. The first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Additionally, the second device determines whether to access the first device based on the priority information and the access indicator information.

[0230] In a possible implementation, the first indication information includes first time information, and the first time information is used to indicate that access by at least one second device to the first device is not allowed within the first time range.

[0231] In a possible implementation, the first time range is a time domain offset for a first reference frame or a time domain offset for a first signaling. The first reference frame may be a first system frame number agreed upon or consensual in advance between the control domain cockpit (CDC) and a non-vehicle-mounted device, or a first system frame number defined in the protocol. The first signaling may be a specific signaling agreed upon or consensual in advance between the control domain cockpit CDC and a non-vehicle-mounted device, or a specific signaling defined in the protocol. For example, the first signaling may be an RRC signaling. There may be one or more time domain offsets.

[0232] In a possible implementation, the first indication information includes resource indication information, and the resource indication information indicates a resource used by at least one third device; or the resource indicated by the resource indication information is not used by at least one second device.

[0233] In a possible implementation, there exists a correspondence between the resource indicated by the resource indication information, the device type, and / or the priority of at least one third device.

[0234] In a possible implementation, the first indication information includes a Boolean variable or an enumerated variable. Certainly, alternatively, other equivalent types of variables may be included.

[0235] In a possible implementation, the first device is a control domain cockpit CDC, the third device is a vehicle-mounted device, and the second device is a non-vehicle-mounted device.

[0236] In a possible implementation, the second device is a mobile phone.

[0237] FIG. 9 is a schematic diagram of a communication system according to an embodiment of the present application.

[0238] As illustrated in FIG. 9, the present application provides a communication system (900). The communication system (900) includes an access control device (700) illustrated in FIG. 7.

[0239] The access control device (700) includes at least one processor and a communication interface. Additionally, the access control device (700) may further include at least one memory. Optionally, the processor, memory, and communication interface of the access control device (700) may establish a communication connection via a bus. The communication interface provides information input and / or output to at least one processor.

[0240] At least one processor may include at least one of a central processing unit (CPU), a graphics processing unit (GPU), and a digital signal processing (DSP) chip.

[0241] This memory may be volatile memory such as random-access memory (RAM); or the memory may include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD); or the memory (2002) may further include a combination of the aforementioned types of memory.

[0242] At least one processor is connected to memory and configured to read and execute instructions from memory. When the processor is running, the processor executes instructions to enable the processor to implement the functions of the access control device (700).

[0243] In a possible implementation, the access control device (700) may be a chip capable of implementing the function of FIG. 7 or a vehicle capable of implementing the function of FIG. 7.

[0244] In a possible implementation, the communication system (900) further includes the access device (800) illustrated in FIG. 8.

[0245] The access device (800) includes a processor, memory, a communication interface, and a bus. The processor, memory, and communication interface of the access device (800) can establish a communication connection through the bus.

[0246] The processor can be a central processing unit (CPU).

[0247] This memory may be volatile memory such as random-access memory (RAM); or the memory may include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD); or the memory (2002) may further include a combination of the aforementioned types of memory.

[0248] The processor is connected to memory and configured to read and execute instructions from memory. When the processor is running, the processor executes instructions to enable the processor to implement the functions of the access device (800).

[0249] In a possible implementation, the access device (800) may be a chip capable of implementing the function of FIG. 8.

[0250] The present application further provides a transport device or intelligent device, e.g., an unmanned aerial vehicle, an automobile, an automated guided vehicle, or a robot. The transport device or intelligent device includes the aforementioned access control device. Additionally, optionally, the transport device further includes the aforementioned access device.

[0251] The present application provides an access control method and apparatus and a communication system. A system broadcast message carrying system status information, a time threshold, and / or access indication information is transmitted, and after a non-vehicle-mounted device receives the system broadcast message, it can determine whether to initiate a random access request based on the system status information, the time threshold, and / or access indication information. This prevents, at this stage, the initiation of a random access request by the non-vehicle-mounted device from affecting the CDC's status check of the vehicle-mounted device and access to the vehicle-mounted device. In this way, it is ensured that the vehicle-mounted device operates normally and that some basic services can be executed normally.

[0252] A person skilled in the art should recognize that in one or more of the examples described above, the function described in the embodiments of the present application may be implemented by hardware, software, firmware, or any combination thereof. Where the function is implemented by software, the function may be stored on a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium and a communication medium, and a communication medium includes any medium that facilitates the transmission of a computer program from one place to another. A storage medium may be any available medium accessible by a general-purpose computer or a dedicated computer.

[0253] The steps of the method or algorithm described in the embodiments disclosed herein may be implemented by hardware, a software module executed by a processor, or a combination thereof. The software module may be configured in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk drive, a removable disk, a CD-ROM, or any other form of storage medium well known in the art.

[0254] The purpose, technical solution, and beneficial effects of this application are described in more detail in the specific embodiments described above. It should be understood that the foregoing description is merely a specific embodiment of this application and is not intended to limit the scope of protection of this application. All modifications, equivalent replacements, improvements, etc., based on the technical solution of this application fall within the scope of protection of this application.

Claims

Claim 1 An access control method performed by a first device, comprising: determining that the state of the first device is a first state; and transmitting a first indication information, wherein the first indication information is used to indicate whether access by at least one second device to the first device is allowed, wherein the first state includes at least one of a system ready state and a vehicle-mounted device access state, and the first indication information is used to indicate that access by the at least one second device is not allowed. Claim 2 An access control method according to claim 1, wherein the first indication information is used to indicate whether access by at least one third device is allowed. Claim 3 An access control method according to claim 1, wherein the first display information includes device type information, and the device type of the at least one second device belongs to at least one device type indicated by the device type information. Claim 4 An access control method according to paragraph 3, wherein the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed. Claim 5 An access control method according to claim 1, wherein the first display information includes priority information, and the priority of the at least one second device belongs to at least one priority indicated by the priority information. Claim 6 An access control method according to claim 5, wherein the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is allowed. Claim 7 An access control method according to paragraph 3, wherein the first display information includes first time information, and the first time information is used to indicate that at least one second device is not allowed to access the first device within a first time range. Claim 8 An access control method according to claim 7, wherein the first time range is a time domain offset relative to a first reference frame or a time domain offset relative to a first signaling. Claim 9 An access control method according to claim 1, wherein the first indicator information includes resource indicator information, and the resource indicator information indicates a resource used by at least one third device; or the resource indicated by the resource indicator information is not used for the at least one second device. Claim 10 An access control method according to claim 9, wherein a correspondence exists between the resource indicated by the resource indication information and the priority and / or device type of at least one third device. Claim 11 An access method performed by a second device, comprising: receiving first indication information from a first device; and determining whether access by the second device to the first device is permitted based on the first indication information, wherein the first indication information indicates that access is not permitted based on the state of the first device, and the state includes at least one of a system ready state and a vehicle-mounted device access state. Claim 12 In paragraph 11, the access method used to indicate whether the first indication information is allowed access to at least one third device. Claim 13 In paragraph 11, the above-mentioned first indicator information includes access indicator information, and the access indicator information is used to indicate a mapping relationship between a device type and an access relationship, an access method. Claim 14 An access method according to claim 13, wherein the access indicator information identifies a device type corresponding to one bit of a bitmap, and the access indicator information identifies whether access is allowed for a device of the device type using the value of one bit of the bitmap. Claim 15 An access method according to claim 11, wherein the first display information includes device type information, and the device type of the second device belongs to at least one device type indicated by the device type information. Claim 16 In paragraph 15, the above-mentioned first indicator information further comprises access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted, an access method. Claim 17 An access method according to claim 11, wherein the first display information includes priority information, and the priority of the second device belongs to at least one priority indicated by the priority information. Claim 18 In paragraph 17, the above-mentioned first indicator information further comprises access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted, an access method. Claim 19 In paragraph 11, the above-mentioned first indication information includes first time information, and the above-mentioned first time information is used to indicate that the second device is not allowed to access the first device within the first time range, an access method. Claim 20 An access method according to claim 19, wherein the first time range is a time domain offset relative to a first reference frame or a time domain offset relative to a first signaling. Claim 21 In paragraph 11, the first indicator information includes resource indicator information, and the resource indicator information indicates a resource used in at least one third device; or the resource indicated by the resource indicator information is not used for the second device, access method. Claim 22 An access method according to claim 21, wherein a correspondence exists between the resource indicated by the resource indication information and the priority and / or device type of at least one third device. Claim 23 In paragraph 11, the access method, wherein the first display information includes a Boolean variable or an enumerated variable. Claim 24 An access method according to claim 12, wherein the first device is a control domain cockpit CDC, the at least one third device is a vehicle-mounted device, and the second device is a non-vehicle-mounted device. Claim 25 In paragraph 24, the access method, wherein the second device is a mobile phone. Claim 26 An access control device comprising: a processing unit configured to determine that the state of a first device is a first state; and a transmitting unit configured to transmit first indication information—the first indication information is used to indicate whether access by at least one second device to the first device is permitted—wherein the first state includes at least one of a system ready state and a vehicle-mounted device access state, and the first indication information is used to indicate that access by the at least one second device is not permitted. Claim 27 In paragraph 26, the access control device used to indicate whether the first indication information is allowed access to at least one third device. Claim 28 An access control device according to claim 26, wherein the first display information includes device type information, and the device type of at least one second device belongs to at least one device type indicated by the device type information. Claim 29 An access control device according to claim 28, wherein the first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Claim 30 An access control device according to claim 26, wherein the first display information includes priority information, and the priority of at least one second device belongs to at least one priority indicated by the priority information. Claim 31 In paragraph 30, the above-mentioned first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted, an access control device. Claim 32 An access control device according to claim 28, wherein the first display information includes first time information, and the first time information is used to indicate that at least one second device is not allowed to access the first device within a first time range. Claim 33 An access control device according to paragraph 32, wherein the first time range is a time domain offset relative to a first reference frame or a time domain offset relative to a first signaling. Claim 34 In paragraph 26, the above-mentioned first indication information includes resource indication information, said resource indication information indicates a resource used by at least one third device; or the resource indicated by said resource indication information is not used by said at least one second device, access control device. Claim 35 An access control device according to paragraph 34, wherein a correspondence exists between the resource indicated by the resource indication information and the priority and / or device type of at least one third device. Claim 36 An access device comprising a receiving unit and a processing unit, wherein the receiving unit is configured to receive first display information from a first device; and the processing unit is configured to determine whether access by a second device to the first device is permitted based on the first display information, wherein the first display information indicates that access is not permitted based on the state of the first device, and the state includes at least one of a system ready state and a vehicle-mounted device access state. Claim 37 In paragraph 36, the access device used to indicate whether the first indication information is allowed access to at least one third device. Claim 38 In paragraph 36, the above-mentioned first indicator information includes access indicator information, and the access indicator information is used to indicate a mapping relationship between a device type and an access relationship, an access device. Claim 39 An access device according to paragraph 38, wherein the access indicator information identifies a device type corresponding to one bit of a bitmap, and the access indicator information identifies whether access is permitted for a device of said device type using the value of one bit of the bitmap. Claim 40 In paragraph 36, the above-mentioned first display information includes device type information, and the device type of the above-mentioned second device belongs to at least one device type indicated by the device type information, an access device. Claim 41 In paragraph 40, the above-mentioned first indicator information further includes access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted, an access device. Claim 42 In paragraph 36, the access device, wherein the first display information includes priority information, and the priority of the second device belongs to at least one priority indicated by the priority information. Claim 43 In paragraph 42, the access device, wherein the first indicator information further comprises access indicator information, and the access indicator information is used to indicate whether access to the first device is permitted. Claim 44 In paragraph 36, the above-mentioned first indication information includes first time information, and the above-mentioned first time information is used to indicate that the above-mentioned second device is not allowed to access the above-mentioned first device within the first time range, an access device. Claim 45 An access device according to claim 44, wherein the first time range is a time domain offset relative to a first reference frame or a time domain offset relative to a first signaling. Claim 46 In paragraph 36, the above-mentioned first indication information includes resource indication information, said resource indication information indicates a resource used by at least one third device; or the resource indicated by said resource indication information is not used for the second device, access device. Claim 47 An access device according to claim 46, wherein a correspondence exists between the resource indicated by the resource indication information and the priority and / or device type of at least one third device. Claim 48 In paragraph 36, the above-mentioned first display information is an access device comprising a Boolean variable or an enumerated variable. Claim 49 An access device according to claim 37, wherein the first device is a control domain cockpit CDC, the at least one third device is a vehicle-mounted device, and the second device is a non-vehicle-mounted device. Claim 50 In paragraph 49, the second device is an access device that is a mobile phone. Claim 51 A computer storage medium, wherein the computer storage medium comprises computer instructions, and when the computer instructions are executed by at least one processor, the method according to claim 1 is implemented. Claim 52 A computer storage medium, wherein the computer storage medium comprises computer instructions, and when the computer instructions are executed by at least one processor, the method according to claim 11 is implemented. Claim 53 A communication system including an access control device according to paragraph 26. Claim 54 In paragraph 53, the communication system further comprises an access device according to paragraph 36. Claim 55 delete Claim 56 delete

Images