Access method, first device and second device

Abstract

The present application relates to an access method, a first device, a second device, a chip, a computer readable storage medium, a computer program product, a computer program, and a communication system. The access method comprises: upon sending a first access message to at least one second device, a first device receives a response message for the first access message sent by a target device among the at least one second device, the response message comprising a first parameter of the target device, and the first parameter being used for identifying the target device among the at least one second device; and the first device sends a second access message to the at least one second device, wherein the second access message comprises the first parameter. Embodiments of the present application realize the distinguishing of accessed second devices during initial access, and solve the conflict between different second devices.

Description

Access method, first device and second device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to an access method, a first device, a second device, a chip, a computer-readable storage medium, a computer program product, a computer program, and a communication system. Background Art

[0002] Interference between devices is ubiquitous in wireless communication systems. To address interference during initial access, random access resources used to access different cells are staggered in at least one of the time, frequency, or code domains. However, with the rise of the IoT (Internet of Things), new challenges have emerged in current wireless communications. Support for lower-capability devices to access nodes in the network is needed, and existing inter-cell interference mitigation methods may not be applicable. Therefore, it is necessary to consider how to avoid conflicts between different devices in the network.

[0003] Summary of the Invention

[0004] Embodiments of the present application provide an access method, a first device, a second device, a chip, a computer-readable storage medium, a computer program product, a computer program, and a communication system, which can be used to avoid conflicts between different devices during an initial access process.

[0005] This embodiment of the present application provides an access method, including:

[0006] After sending the first access message to the at least one second device, the first device receives a response message to the first access message sent by a target device in the at least one second device; wherein the response message includes a first parameter of the target device, and the first parameter is used to identify the target device in the at least one second device;

[0007] The first device sends a second access message to at least one second device, wherein the second access message includes a first parameter.

[0008] This embodiment of the present application provides an access method, including:

[0009] The second device receives a first access message from the first device;

[0010] The second device sends a response message to the first access message to the first device; wherein the response message includes a first parameter of the second device, and the first parameter is used to identify the second device; the response message is used to trigger the sending of the second access message;

[0011] The second device receives the second access message from the first device, and determines that the first device is accessed when the second access message includes the first parameter and the first identifier of the first device.

[0012] An embodiment of the present application provides a first device, including:

[0013] A first communication module, configured to, after sending a first access message to at least one second device, receive a response message to the first access message sent by a target device in the at least one second device; wherein the response message includes a first parameter of the target device, the first parameter being used to identify the target device in the at least one second device;

[0014] The first communication module is further configured to send a second access message to at least one second device; wherein the second access message includes the first parameter.

[0015] An embodiment of the present application provides a second device, including:

[0016] a second communication module, configured to receive a first access message from the first device, send a response message to the first access message to the first device, and receive a second access message from the first device; wherein the response message includes a first parameter of the second device, the first parameter being used to identify the second device; and the response message is used to trigger the sending of the second access message;

[0017] The second processing module is configured to determine that the first device has been accessed when the second access message includes the first parameter and the first identifier of the first device.

[0018] An embodiment of the present application provides a first device, comprising: a transceiver, a processor, and a memory. The memory is configured to store a computer program, the transceiver is configured to communicate with other devices, and the processor is configured to call and execute the computer program stored in the memory, so that the first device performs the above-mentioned access method.

[0019] An embodiment of the present application provides a second device, comprising: a transceiver, a processor, and a memory. The memory is configured to store a computer program, the transceiver is configured to communicate with other devices, and the processor is configured to call and execute the computer program stored in the memory, so that the second device performs the above-described access method.

[0020] An embodiment of the present application provides a chip for implementing the above-mentioned access method.

[0021] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned access method.

[0022] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which, when executed by a device, enables the device to perform the above-mentioned access method.

[0023] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned access method.

[0024] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned access method.

[0025] An embodiment of the present application provides a communication system, including a first device and a second device used for the above-mentioned access method.

[0026] In an embodiment of the present application, a first device initiates initial access by sending a first access message. Each second device in the network sends a response message containing a first parameter for identifying the second device. After receiving the response message, the first device sends a second access message containing the received first parameter, allowing each second device to perform corresponding processing based on the first parameter in the second access message. This enables differentiation of second devices during the initial access process and resolves conflicts between different second devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] FIG1 is a schematic diagram of a communication system in an embodiment of the present application.

[0028] FIG2A is a schematic diagram of the four-step CBRA process.

[0029] FIG2B is a schematic diagram of the two-step CBRA process.

[0030] Figure 3 is a schematic diagram of the basic structure of the A-IoT communication system.

[0031] FIG4A is a schematic diagram of a first topology network structure in an A-IoT communication system.

[0032] FIG4B is a schematic diagram of a second topology network structure in an A-IoT communication system.

[0033] FIG4C is a schematic diagram of a third topology network structure in an A-IoT communication system.

[0034] FIG4D is a schematic diagram of a fourth topology network structure in an A-IoT communication system.

[0035] FIG5A is a block diagram of a typical wideband receiver.

[0036] FIG5B is a block diagram of a typical intermediate frequency receiver.

[0037] FIG6 is a schematic diagram of an application scenario of an embodiment of the present application.

[0038] FIG7 is a schematic flowchart of an access method according to an embodiment of the present application.

[0039] FIG8 is a schematic flowchart of an access method according to another embodiment of the present application.

[0040] FIG9 is a schematic diagram of a distribution method of the first parameter in an application example.

[0041] FIG10 is a schematic diagram of application example 1 of the access method according to an embodiment of the present application.

[0042] FIG11 is a schematic diagram of application example 2 of the access method according to an embodiment of the present application.

[0043] FIG12 is a schematic block diagram of a first device according to an embodiment of the present application.

[0044] FIG13 is a schematic block diagram of a first device according to another embodiment of the present application.

[0045] FIG14 is a schematic block diagram of a second device according to an embodiment of the present application.

[0046] FIG15 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0047] FIG16 is a schematic block diagram of a chip according to an embodiment of the present application.

[0048] FIG17 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0049] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0050] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), Fifth Generation (5G) system or other communication systems.

[0051] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0052] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0053] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0054] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0055] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0056] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0057] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0058] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0059] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0060] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0061] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0062] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0063] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0064] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0065] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0066] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0067] (1) Random Access

[0068] In the 3GPP (3rd Generation Partnership Project) communication system, there are generally two ways of initial access at the MAC (Medium Access Control) layer, namely two-step random access (2-step RACH) and four-step random access (4-step RACH). Regardless of the RACH (Random Access Channel) process, the resolution of random access conflicts is performed within a cell. This is because in the 3GPP cellular communication system (including 4G and 5G), before initiating the random access process, the terminal must first obtain frequency and time synchronization with the current serving cell, and then initiate the random access process on the random access radio resources broadcast by the serving cell. Generally speaking, different serving cells either have different frequencies (for example, there are low-frequency cells responsible for coverage and high-frequency cells with overlapping coverage with low-frequency cells), or the system time is not synchronized, or both are different. Even for frequency- and time-synchronized serving cells (e.g., different sectors of the same base station), to avoid interference, the PRACH (Physical Random Access Channel) resources used for random access are staggered in the time, frequency, and / or code domains (ZC (Zadoff-Chu) codes used to generate the preamble). This allows the base station to easily identify and discard preambles from terminals in neighboring cells when a terminal initiates random access in a covered cell, even if the preamble is received by a neighboring cell.

[0069] The four-step random access process was introduced in the LTE system and is also used in the NR system. As mentioned above, before initiating the RACH process, the terminal first needs to obtain the PRACH resource configuration from the network's system message or dedicated signaling. Figure 2A is a schematic diagram of the four-step CBRA (Contention Based Random Access, contention-based random access) process. As shown in Figure 2A, the four-step CBRA includes four steps:

[0070] Step 1: The terminal sends a random access preamble to the base station. This preamble is called message 1 in the MAC layer protocol. After sending the preamble, it waits for message 2 from the base station in a subsequent response window. The start and end times of the response window are set according to configuration parameters. From the base station's perspective, the base station is able to distinguish between preambulations received in different time-frequency domains, or different preambulations in the same time-frequency domain. However, the base station cannot distinguish between the same preamble sent by multiple terminals in the same time-frequency domain. In this case, an access conflict occurs.

[0071] Step 2: The base station feeds back message 2 to the terminal. Message 2 can be a group message, meaning it can include RAR (Random Access Response) messages addressed to multiple terminals. The addressing information for Message 2 is contained in a group identifier called RA-RNTI (Random Access-Radio Network Temporary Indentifier), which is used to identify the time domain, frequency domain, and carrier type information of the received preamble. In other words, preambles received from the same carrier at the same time and frequency point can be combined into the same message 2. The RAR IE (Information Elements) sent to each terminal includes the temporary identifier T_C_RNTI configured for the terminal, the timing advance (for uplink synchronization), the UL-grant used to send message 3, and the index (or sequence number) of the received preamble. Message 2 can also include a backoff parameter to mitigate uplink preamble conflicts. If the terminal decides to send the preamble again, it will generate a random time based on the backoff parameter so that the next preamble sending time is at least later than the generated random time.

[0072] Step 3: After comparing the RA-RNTI and the preamble index in the RAR, the terminal can determine whether the base station has received the preamble it sent. After confirming that the correct RAR has been received, the terminal sends message 3 (message3) based on the UL-grant, which at least includes the terminal identifier (UE ID). Message3 is addressed using T_C_RNTI on the physical layer. The terminal then starts a timer. While the timer is running, the downlink control channel PDCCH (Physical Downlink Control Channel) is detected. If two or more terminals collide in step 1, they will continue to collide in step 3 because they will send message3 based on the same information, but the terminal identifiers contained in the MAC CE (MAC Control Element) of message3 are different.

[0073] Step 4: If the base station correctly decodes message 3, it sends message 4 (message 4) to the terminal. This message 4 is addressed using the T_C_RNTI of message 3, and its MAC CE includes the terminal's identifier contained in message 3 and a newly assigned C-RNTI. If multiple terminals send message 3 on the same UL grant, the base station may correctly decode one or fail to decode it (for example, due to comparable interference levels). Upon receiving message 4, if the terminal finds that the T_C_RNTI convolved on the PDCCH matches the T_C_RNTI of its own message 3, it further checks whether the MAC CE in message 4 sent by the base station matches its terminal ID. If the terminal ID also matches, the terminal confirms the completion of the random access procedure and uses the newly assigned C-RNTI as its own identity. This identity is used for addressing information in subsequent PHY, MAC, and RRC layer protocols.

[0074] Logically, the two-step random access process combines steps 1 and 3 of the four-step random access process to transmit message A, and combines steps 2 and 4 of the four-step random access process to transmit message B. Figure 2B is a schematic diagram of the two-step CBRA process. As shown in Figure 2B, the two-step CBRA process includes two steps:

[0075] Step A: The terminal transmits message A to the base station, which includes a random access preamble and a data channel PUSCH (Physical Uplink Shared Channel). The PUSCH includes the UE ID of the terminal.

[0076] Step B: The base station sends a response message B. There are two ways to address the terminal in message B:

[0077] B1: If the UE ID in messageA is C-RNTI, then the convolution on the downlink control channel (PDCCH) of messageB is also C-RNTI. In this case, if the terminal can confirm that the C-RNTI of messageB matches its own C-RNTI, it is considered that the random access process has been completed correctly, that is, the conflict has been resolved. This situation of B1 is suitable for terminals in the RRC_CONNECTED state, that is, the terminal has completed the initial access and established an RRC connection with the network.

[0078] B2: If the UE ID in message A is something other than the C-RNTI, the RA-RNTI is convolved on the PDCCH of message B. B2 applies to all cases except B1. If the UE ID contained in the SuccessRAR message in message B matches the terminal's own UE ID, the terminal considers its random access procedure successful and the conflict resolved. Otherwise, the terminal either resends message A or falls back to the 4-step RACH and sends message GAE1.

[0079] (2) A-IoT (Ambient IoT)

[0080] The rise of the Internet of Things (IoT) has posed new challenges to communication systems. IoT terminals are used in applications such as logistics, warehousing, factory automation, and animal husbandry. These IoT terminals only need to intermittently communicate with the network or perform rough location tracking. Currently, even the simplest IoT terminals on the market, such as NB-IoT (Narrow Band IoT) terminals used for coal and electricity metering, require batteries for power. Although their energy consumption is low, the batteries in these terminals deplete after only a few years. This, at the very least, requires extensive manual labor to replace the batteries. Some industrial scenarios are too dangerous for manual operation. This is why battery-free IoT terminals have emerged.

[0081] Battery-free IoT terminals are plentiful, low-cost, and generally require no maintenance after installation. RFID (Radio Frequency Identification) terminals meet this need to some extent. However, the operation of RFID systems requires the use of handheld readers. Furthermore, the limited wireless coverage range of a single RFID reader (within 10 meters) means that inventory checks in, for example, a large supermarket still require considerable manpower, resources, and time.

[0082] Transplanting communication systems like RFID into 3GPP cellular networks effectively solves coverage issues. This is because already deployed cellular networks, such as 4G and 5G, generally achieve nationwide coverage, or at least coverage of major cities. The benefit of full coverage is that the communication and positioning process between IoT terminals and the network does not require human intervention, so it can operate 24 / 7 with high efficiency, even in environments unsuitable for human intervention (such as wilderness, mines, and factories). In this way, aside from the initial need to associate the IoT terminal with a specific object, subsequent data reading, writing, and operation and maintenance can be performed simply through an app on a smartphone, which is very convenient and efficient.

[0083] Such a communication system is called an A-IoT communication system or a zero-power communication system. A-IoT communication uses energy harvesting and backscatter communication technology. The A-IoT communication network consists of network equipment and A-IoT terminals (also known as A-IoT devices, zero-power terminals, electronic tags, tags). Figure 3 shows a schematic diagram of the basic structure of the A-IoT communication system. The network equipment is used to send wireless power supply signals, downlink communication signals, and backscatter signals to the tag. A basic tag includes an energy harvesting module, a backscatter communication module, and a low-power computing module. In addition, the tag can also have a memory or sensor for storing some basic information (such as item identification, etc.) or obtaining sensor data such as ambient temperature and ambient humidity.

[0084] Currently, the A-IoT system primarily supports use cases such as inventory, sensors, tracking, and commands. Inventory refers to checking for missing items and replenishing missing items as they enter and leave the warehouse. Common sensors include temperature, pressure, and humidity, and are used in industrial, agricultural, and smart city applications. Sensor information is uploaded to a third-party app through the A-IoT system for monitoring and management. Tracking generally refers to obtaining the approximate location of an object at irregular intervals. For example, users can use their smartphones to track the location of their parcels in near real time. Commands, on the other hand, involve operating a servo mechanism connected to an A-IoT terminal through the A-IoT communication system. For example, during a break at the office, users can water their backyard plants using a mobile app. The watering servo mechanism is connected to an A-IoT terminal.

[0085] For the above use cases, four topological network structures are proposed in the relevant technology. Figures 4A to 4D show schematic diagrams of four topological network structures. As shown in Figure 4A, the A-IoT terminal can be connected to the network device for two-way communication. As shown in Figure 4B, the A-IoT terminal can be connected to the intermediate node for two-way communication, and the intermediate node is connected to the network device for two-way communication; optionally, the intermediate node can be a UE, which is connected to the network device for communication through the Uu interface. As shown in Figure 4C, the A-IoT terminal can receive the power supply signal / downlink communication signal sent by the auxiliary node, and send an uplink signal to the network device; optionally, the auxiliary node can be a UE, which is connected to the network device for communication through the Uu interface. As shown in Figure 4D, the A-IoT terminal can be connected to the UE for two-way communication.

[0086] A-IoT terminals (tags) derive their energy from the surrounding environment, such as radio frequency (RF) waves, solar energy, thermal energy, mechanical vibration, and wind energy. In the A-IoT system currently being researched by 3GPP, terminals are primarily categorized into three types: Type A, Type B, and Type C. Type A and Type B terminals can only communicate by reflecting and modulating received radio waves, a communication method known as backscattering. This means they cannot actively transmit radio signals, and their power range is between 1 and 10 microwatts (μW). Type A terminals have the lowest transmit power and the least hardware complexity, roughly comparable to RFID terminals. Type B has slightly more complex hardware, such as signal amplification devices and certain energy storage devices, allowing for longer communication distances with the network than Type A terminals. Type C terminals have the ability to actively transmit radio waves, with a transmit power of approximately 1 to 10 milliwatts (mW), and can also store a certain amount of energy. All three types of terminals can harvest energy from the environment and can operate continuously for several years or even over 10 years. To conserve energy, Type A and Type B terminals typically remain dormant until the network triggers a communication process. It will only wake up and work when stimulated by the network's wireless signal.

[0087] A-IoT receivers can be divided into two categories:

[0088] Receiver Type 1: Wideband Receiver. This type of receiver, also known as an RF receiver, uses an RF bandpass filter to obtain signals within the bandwidth to be received, then performs envelope detection and subsequent baseband processing. This architecture is the simplest, with power consumption as low as a few uW or even lower. However, due to the poor accuracy of the RF bandpass filter, even when the target signal occupies a narrow bandwidth, this receiver often receives signals within a wider bandwidth. Consequently, the reception process introduces a significant amount of noise and interference, resulting in poor receiver performance, and therefore, poor sensitivity. Figure 5A is a block diagram of a typical wideband receiver.

[0089] Receiver Type 2: Narrowband Receiver. Typical examples include IF receivers or zero-IF receivers. During signal reception, in addition to using an RF bandpass filter to obtain a signal within the intended bandwidth, the RF signal is down-converted and the baseband signal is further filtered using a low-pass filter to eliminate noise and interference. Therefore, the receiver has a narrow reception bandwidth and high reception performance, i.e., high sensitivity. However, this receiver requires an LO (local oscillator). Even the recommended LO consumes 100uW or more, so the receiver's power consumption is relatively high. However, due to its very low absolute power consumption, it is still suitable for use in zero-power devices. Figure 5B is a block diagram of a typical IF receiver.

[0090] The above-mentioned type A terminals usually use broadband receivers, type C terminals usually use narrowband receivers, and type B terminals may use one or both types of receivers.

[0091] For A-IoT systems and terminals, the random access process of LTE / NR systems is too complicated and needs further simplification and optimization.

[0092] Furthermore, when the RFID system's readers are operating, because reader coverage is prioritized and manual operation is generally employed, it can be assumed that a tag will only communicate with one reader. However, the A-IoT system is a 3GPP wide-coverage system. In other words, the distribution of different readers is essentially equivalent to the layout of existing base stations. Figure 6 is a schematic diagram of an application scenario of an embodiment of the present application. As shown in Figure 6, a tag is likely to be between the coverage areas of different readers.

[0093] Typical A-IoT system application scenarios often require a large number of tags to access the system within a short period of time. To maximize frequency reuse, different readers often utilize the same frequency resources and employ similar or identical channelization methods. Furthermore, the number of channels on a single carrier is limited. When a tag responds to a reader's trigger message and initiates the initial access process, its message can easily be received by multiple nearby readers. Similarly, signals from different readers can easily be received by the same tag. This problem generally does not exist in LTE / NR systems. This is because, in broadband systems, even if adjacent base stations utilize the same carrier, the PRACH resources used for initial access can easily stagger in the time-frequency domain. Even if there is overlap in the time-frequency domain, adjustments can be made to the preamble generation code to ensure orthogonality between the ZC codes generated by different cells for the preamble, for example by using different ZC root codes. Furthermore, even if collisions occur in broadband systems like LTE / NR, these systems have comprehensive inter-cell interference mitigation mechanisms to address the issue. However, narrowband systems like A-IoT are very sensitive to inter-cell interference due to their simple signal modulation and message interaction, and lack effective means to mitigate or eliminate it.

[0094] FIG7 is a schematic flow chart of an access method according to an embodiment of the present application. The method can optionally be applied to the network shown in FIG4A to FIG4C, but is not limited thereto. The method includes:

[0095] S710. After sending a first access message to at least one second device, the first device receives a response message to the first access message sent by a target device in the at least one second device; wherein the response message includes a first parameter of the target device, and the first parameter is used to identify the target device in the at least one second device;

[0096] S720. The first device sends a second access message to at least one second device; wherein the second access message includes the first parameter.

[0097] In the embodiment of the present application, the first device may be a terminal device. Optionally, the first device may be an IoT terminal, such as an A-IoT device, a zero-power terminal, or an electronic tag.

[0098] In an embodiment of the present application, the second device may be a node in the system / network. Optionally, the second device may be a node for communicating with the first device. The node may be a terminal device, a network device, or a node (power supply node) that separately provides backscattered radio waves. For example, the second device may be a network device (e.g., a base station) shown in FIG. 4A , an intermediate node shown in FIG. 4B , an auxiliary node shown in FIG. 4C , or a UE shown in FIG. 4D . It will be understood that the embodiment of the present application does not limit the topological structure in the network. Therefore, the second device is not limited to the various forms described above, and the second device may include any form of node capable of performing point-to-point communication with the first device.

[0099] The above access method can be applied to scenarios where the first device may be within the coverage range of multiple second devices, such as the scenario shown in Figure 6, and can resolve conflicts between multiple second devices. Specifically, in scenarios where the first device may be within the coverage range of multiple second devices, the first access message sent by the first device may be received by one or more second devices. Each second device can send a response message. Since the distance between each second device and the first device may be different, the first device may not be able to correctly receive the response message of each second device. When the first device receives a response message from one of the second devices (at this time, the response messages of other second devices are interference signals), the second device is the target device. The first device can compile the first parameter of the target device into the second access message and send it, so that each second device that receives the second access message can determine how to process the second access message by comparing its own first parameter with the first parameter in the second access message, thereby resolving interference / conflicts between multiple second devices. It can be understood that in actual applications, the target device is generally the second device that is closest to the first device.

[0100] It can be seen that the first parameter is introduced in the embodiment of the present application to distinguish different second devices, that is, to identify a specific second device in at least one second device. In some scenarios, the first parameter can be called an RCC (Reader Color Code) parameter. Based on the first parameter, it is possible to distinguish between multiple second devices during the initial access process, and resolve conflicts between different second devices. In addition, according to the above-mentioned access method, the first device will establish a wireless link with the closest second device, which helps to ensure the performance of the initial access and subsequent communication processes.

[0101] The present application also provides an access method from the perspective of a second device. Specifically, FIG8 is a schematic flow chart of an access method according to another embodiment of the present application. The method includes:

[0102] S810. The second device receives a first access message from the first device.

[0103] S820. The second device sends a response message to the first device in response to the first access message; wherein the response message includes a first parameter of the second device, where the first parameter is used to identify the second device; and the response message is used to trigger the sending of the second access message.

[0104] S830: The second device receives a second access message from the first device, and determines that the first device is accessed when the second access message includes the first parameter and the first identifier of the first device.

[0105] Optionally, the second device may determine whether the second access message is used to access the second device based on whether the second access message includes the first parameter of the second device. In other words, determine whether the second device is the target device for initial access. If the second access message includes the first parameter of the second device, the second device may determine, based on the first identifier in the second access message, that the first device corresponding to the first identifier is accessing.

[0106] It can be understood that according to the above method, each second device can determine whether the first device is connected based on the second access message, thereby distinguishing the second devices connected during the initial access process and resolving conflicts between different second devices.

[0107] Optionally, the second access message is further used to instruct other second devices other than the target device to release the context related to the first device. Accordingly, for any second device, the access method may further include:

[0108] When the second access message includes the first identifier of the first device but does not include the first parameter of the second device, the second device releases the context related to the first device.

[0109] Specifically, when the second access message does not include the first parameter of the second device, the second device can determine that the second access message is not used to access the second device. In this way, the relevant context can be released, and then the context related to the first device can be released according to the first identifier in the second access message.

[0110] In some embodiments, the first parameter of the target device is unique globally or locally within the communication system.

[0111] In one embodiment, the first parameter of the target device is unique globally within the communication system. That is, the first parameter of the target device is different from the first parameter of any other second device globally within the communication system. Similarly, for any second device, the first parameter of the second device is also unique globally within the communication system. This allows the target device to be globally distinguished from other second devices, ensuring conflict resolution.

[0112] In another embodiment, the first parameter of the target device is unique within the local scope of the communication system, that is, the first parameter of the target device is different from the first parameter of any other second device in the communication system. Similarly, for any second device, the first parameter of the second device is unique within the local scope of the communication system.

[0113] Figure 9 is a schematic diagram of the distribution method of the first parameter in an application example, in which a hexagon represents the range that can be covered by a second device, and the 3-bit information (000, 001, 010, 011, 100, 101, 110) in the hexagon is the first parameter of the second device represented by the hexagon. It can be seen that among the 7 second devices centered on any second device, the first parameters of each second device are different from each other, that is, each second device is unique within the local range of the 7 hexagons. Since the interference in the communication system is related to the distance between the devices, when the distance between different second devices increases, the possibility of conflict decreases. Therefore, the first parameter of the second device is unique within the local range of the communication system, and can distinguish the target device from other second devices within the local range. At the same time, devices that are farther away will not conflict with the target device, so conflict resolution can also be achieved.

[0114] In some embodiments, the number of bits of the first parameter of the target device or the second device is related to the number of second devices in the global scope or the local scope of the communication system.

[0115] Specifically, if the first parameter is unique globally, the number of bits of the first parameter is related to the number of second devices in the global scope. If the first parameter is unique locally, the number of bits of the first parameter is related to the number of second devices in the local scope.

[0116] In some embodiments, when the number of second devices increases, the number of bits of the first parameter increases or remains unchanged.

[0117] In actual applications, the number of second devices in a local range varies according to different application scenarios, so the number of bits or the bit length of the first parameter in different application scenarios can be set differently. Taking Figure 9 as an example, when the local range includes 7 second devices, a first parameter of 3 bits can be used. In actual engineering, some scenarios may be relatively simple. For example, in an indoor scenario, there may be only a limited number of readers, so the first parameter of the reader can be 2 bits or even 1 bit. However, in an outdoor scenario, the distribution of readers may be relatively dense, so the first parameter of the reader may require 4 bits. Using the above embodiment, the number of bits of the first parameter increases or remains unchanged as the number of second devices increases, so it can be ensured that each second device is assigned a unique first parameter in the local range within an appropriate bit length.

[0118] It should be noted that in the embodiment of the present application, a message includes a first parameter. Specifically, the first parameter may be compiled in the physical layer information or compiled in the L2 (Layer 2) message, such as compiled in the MAC layer or RRC layer. Optionally, the first parameter may appear alone as a parameter in the message, or may be compiled in the message together with other parameters.

[0119] In some embodiments, the first access message includes a first identifier of the first device. The first device sends a second access message to at least one second device, including: when the first identifier in the response message is the same as the first identifier of the first device, the first device sends the second access message to the at least one second device; wherein the second access message also includes the first identifier of the first device, and the first identifier in the second access message is used by the target device to determine conflict resolution.

[0120] Accordingly, for the second device, a response message sent after receiving the first access message includes the first identifier of the first device, where the first identifier of the first device is determined based on the first access message. The access method further includes: the second device determining a conflict resolution for access of the first device when the second access message includes the first parameter of the second device and the first identifier of the first device.

[0121] Specifically, the first device carries its own first identifier when sending a first access message; at least one second device receives the first access message, and then each second device carries the first identifier of the first device in a response message; when the first device includes its own first identifier in the response message, it can be considered that in this initial access, the conflict between the first device and the other device (such as the IoT terminal) has been resolved. At this time, the first device sends a second access message to enable the second device to determine that the conflict with the other second device has been resolved.

[0122] In some embodiments, the response message received by the first device includes a second identifier assigned to the first device by the target device. The second identifier is used for message addressing after access. It is understood that the response message sent by any second device includes the second identifier assigned to the first device by the second device. This second identifier can be used in subsequent processes, that is, the second identifier is used in subsequent processes to distinguish the first device from other devices.

[0123] Optionally, the uplink message content to be sent by the first device may be carried by, or incorporated into, the first access message. In some scenarios, such as reporting or inventory of monitoring / sensing information, the uplink message content to be sent by the first device has already been sent to the second device via the first access message, and no subsequent process occurs. In this case, the response message may not include the second identifier, meaning that the second device does not need to allocate the second identifier to the first device.

[0124] In some embodiments, the second identifier in the response message received by the first device is determined based on at least the first parameter of the target device. That is, for any second device, the second identifier allocated to the first device in the response message is determined based on at least the first parameter of the second device.

[0125] Since the first parameter is compiled into the second identifier, the second identifiers allocated to the second devices with different first parameters must be different. Therefore, the above embodiment is conducive to achieving the uniqueness of the second identifier within the local range of the communication system, rather than being unique only within multiple first devices that access the target device at the same time, avoiding problems with message addressing between the first device and the target device after initial access.

[0126] In some embodiments, the first identifier of the first device may be determined based on a random number. Optionally, before the first device sends the first access message to the at least one second device, the access method may further include: the first device determining the first identifier of the first device based on the random number. For example, the first device may use a currently generated random number as the first identifier of the first device.

[0127] In order to more clearly understand the above technical solution, a specific application example is provided below, taking the initial access between a tag (first device) and a reader (second device) as an example.

[0128] FIG10 is a schematic diagram of an application example 1 of the access method of an embodiment of the present application. In this application example, the distance between the tag and reader B is smaller than the distance between the tag and reader A. As shown in FIG10 , the access method includes the following steps:

[0129] Step 1: After receiving the broadcast message triggering inventory from reader A, the tag triggers the initial access process. Specifically, the tag sends message A (msgA, first access message), which contains at least a tag-id (first identifier), which can be an internally generated random number.

[0130] Step 2: Both reader A and reader B receive msgA, and each sends a response message, which is message B (msgB, a response message to the first access message). msgB contains at least the tag-id, the Tag-RNTI (second identifier) ​​assigned to the tag by the reader, and the RCC parameter of the reader (first parameter). Since reader B is closer to reader A, when the two msgBs are received by the tag, the msgB from reader B has a higher signal strength, so the tag decodes the msgB from reader B. The msgB from reader A is an interference signal. The tag finds that the tag-id contained in msgB is equal to the tag-id it sent, and believes that the conflict of this initial access (the conflict between tags within the reader) has been resolved.

[0131] Step 3: The tag sends a message C (msgC, second access message). msgC includes at least the tag-id and the RCC parameter of reader B.

[0132] Step 4: After receiving msgC, reader A finds that the RCC parameter contained in the message is different from its own RCC parameter, so it releases the local context associated with the tag. After receiving msgC, reader B finds that the RCC parameter contained in the message is equal to its own RCC parameter, and considers that the conflict between readers has been resolved.

[0133] In the above application example, the tag doesn't actually know which reader is closest before the process begins. After the tag receives a response to its first message, the feedback signal from the closer reader is typically stronger (higher SINR). The stronger signal is correctly decoded, while the weaker signal is interpreted as interference. Therefore, the tag establishes a wireless link with the closest reader, helping to ensure performance during initial access and subsequent communication.

[0134] In other embodiments, the second access message also includes the first identifier of the first device; the first parameter in the second access message is used by the target device to determine conflict resolution, thereby triggering the target device to send an access confirmation message. Specifically, after determining the first parameter of the target device, the first device includes the first identifier of the first device and the first parameter of the target device in the second access message, so that the target device determines conflict resolution with the other second device based on the first parameter and sends an access confirmation message to the first device based on the first identifier.

[0135] In some embodiments, the access method further includes: after sending the second access message, the first device receives an access confirmation message, and when the access confirmation message includes the first identifier of the first device, determining that the initial access is successful.

[0136] Correspondingly, for any second device, the access method also includes: the second device sends an access confirmation message when the second access message includes the first parameter of the second device; wherein the access confirmation message includes the first identifier of the first device, and the first identifier of the first device is determined based on the second access message; the access confirmation message is used by the first device to determine that the initial access is successful.

[0137] That is, the second device carries the first identifier of the first device in the access confirmation message, so that the first device confirms that the conflict between it and other devices has been resolved, thereby determining that the initial access is successful.

[0138] In some embodiments, the access confirmation message received by the first device includes a second identifier assigned to the first device by the target device. The second identifier is used for message addressing after access. That is, when the second access message includes its own first parameter, the access confirmation message sent by the second device includes the second identifier assigned to the first device. This second identifier can be used in subsequent processes to distinguish the first device from other devices.

[0139] Optionally, the uplink message content to be sent by the first device may be carried by, or compiled into, the second access message. In some scenarios, such as reporting or inventory of monitoring / sensing information, the uplink message content to be sent by the first device has already been sent to the second device via the second access message, and no subsequent process occurs. In this case, the access confirmation message may not include the second identifier, meaning that the second device does not need to allocate the second identifier to the first device.

[0140] In some embodiments, the second identifier in the access confirmation message received by the first device is determined based on at least the first parameter of the target device. That is, for any second device, the second identifier allocated to the first device in the access confirmation message is determined based on at least the first parameter of the second device.

[0141] Since the first parameter is compiled into the second identifier, the second identifiers allocated to the second devices with different first parameters must be different. Therefore, the above embodiment is conducive to achieving the uniqueness of the second identifier within the local range of the communication system, rather than being unique only within multiple first devices that access the target device at the same time, avoiding problems with message addressing between the first device and the target device after initial access.

[0142] In some embodiments, the first identifier of the first device may be determined based on a random number. Optionally, before the first device sends the second access message to the at least one second device, the access method may further include: the first device determining the first identifier of the first device based on the random number. For example, the first device may use a currently generated random number as the first identifier of the first device.

[0143] In order to more clearly understand the above technical solution, a specific application example is provided below, taking the initial access between a tag (first device) and a reader (second device) as an example.

[0144] FIG11 is a schematic diagram of an application example 2 of the access method of an embodiment of the present application. In this application example, the distance between the tag and reader B is smaller than the distance between the tag and reader A. As shown in FIG11 , the access method includes the following steps:

[0145] Step 1: After receiving the broadcast message from reader A triggering the inventory, the tag triggers the initial access process. Specifically, the tag sends message 1 (msg1, the first access message), which contains a randomly selected preamble. A sequence is modulated on the preamble. The number of these sequences is limited, for example, there are 16 in total, and each sequence has a fixed serial number. The reader can demodulate preambles of different sequences. If preambles modulated with the same sequence are received from different tags, the reader cannot distinguish between different tags, that is, they may be demodulated as one preamble.

[0146] Step 2: After receiving the preamble, reader A and reader B each send message 2 (msg2, a response message to the first access message). msg2 includes at least the preamble index (preamble sequence number / index) and the reader's RCC parameter (the first parameter). Because the signal strength of msg2 from reader B is higher, the tag ultimately correctly decodes msg2 from reader B. msg2 from reader A becomes an interference signal.

[0147] Step 3: After receiving the preamble index, the tag compares it with the index of the preamble it just sent. If the two indices are the same, the tag sends Message 3 (msg3, the second access message) to the reader, which contains at least the tag-id (the first identifier) ​​and the RCC parameters. Otherwise, the initial access is considered a failure. The tag-id can be a random number generated by the tag itself.

[0148] Step 4: Reader A finds that the RCC in the received msg3 is not equal to its own RCC, so it considers that the initial access process has ended and releases the tag context. Reader B finds that the RCC in msg3 is equal to its own RCC, and feeds back a message 4 (msg4, access confirmation message) containing at least the received tag-id and the identifier Tag-RNTI (second identifier) ​​assigned to the tag to the tag. After the tag receives this message, if it finds that the received tag-id is equal to the one it sent, it considers that the initial access has been successful, and uses the received Tag-RNTI as its own identifier for subsequent processes.

[0149] In the above application example, the tag doesn't actually know which reader is closest before the process begins. After the tag receives a response to its first message, the feedback signal from the closer reader is typically stronger (higher SINR). The stronger signal is correctly decoded, while the weaker signal is interpreted as interference. Therefore, the tag establishes a wireless link with the closest reader, helping to ensure performance during initial access and subsequent communication.

[0150] FIG12 is a schematic block diagram of a first device 1200 according to an embodiment of the present application. The first device 1200 may include:

[0151] The first communication module 1210 is configured to receive, after sending a first access message to the at least one second device, a response message sent by a target device in the at least one second device to the first access message; wherein the response message includes a first parameter of the target device, and the first parameter is used to identify the target device in the at least one second device;

[0152] The first communication module 1210 is further configured to send a second access message to at least one second device; wherein the second access message includes the first parameter.

[0153] In one embodiment, the first parameter of the target device is unique in a global scope or a local scope of the communication system.

[0154] In one embodiment, the number of bits of the first parameter of the target device is related to the number of second devices in the global scope or the local scope of the communication system.

[0155] In one embodiment, when the number of second devices increases, the number of bits of the first parameter increases or remains unchanged.

[0156] In one embodiment, the second access message is further used to instruct other second devices except the target device to release the context related to the first device.

[0157] In one embodiment, the first access message includes a first identifier of the first device;

[0158] The first communication module 1210 is also used to send a second access message when the first identifier in the response message is the same as the first identifier of the first device; wherein the second access message also includes the first identifier of the first device, and the first identifier in the second access message is used by the target device to determine conflict resolution.

[0159] In one implementation, the response message further includes a second identifier allocated by the target device to the first device, and the second identifier is used for message addressing after access.

[0160] In one embodiment, the second access message further includes a first identifier of the first device; the first parameter in the second access message is used by the target device to determine conflict resolution to trigger the target device to send an access confirmation message.

[0161] In one embodiment, the first communication module 1210 is further configured to receive an access confirmation message after sending the second access message. As shown in FIG13 , the first device 1200 further includes a first processing module 1310, which is configured to:

[0162] When the access confirmation message includes the first identifier of the first device, it is determined that the initial access is successful.

[0163] In one embodiment, the access confirmation message includes a second identifier allocated by the target device to the first device, and the second identifier is used for message addressing after access.

[0164] In one embodiment, the second identifier is determined based on at least a first parameter of the second device.

[0165] In one embodiment, the first identifier of the first device is determined based on a random number.

[0166] The first device 1200 of the embodiment of the present application can implement the corresponding functions of the first device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first device 1200 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first device 1200 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0167] FIG14 is a schematic block diagram of a second device 1400 according to an embodiment of the present application. The second device 1400 may include:

[0168] The second communication module 1410 is configured to receive a first access message from the first device, send a response message to the first access message to the first device, and receive a second access message from the first device; wherein the response message includes a first parameter of the second device, the first parameter being used to identify the second device; and the response message is used to trigger the sending of the second access message;

[0169] The second processing module 1420 is configured to determine that the first device has been accessed when the second access message includes the first parameter and the first identifier of the first device.

[0170] In one embodiment, the first parameter of the second device is unique globally or locally in the communication system.

[0171] In one embodiment, the number of bits of the first parameter of the second device is related to the number of second devices in the global scope or the local scope of the communication system.

[0172] In one embodiment, when the number of second devices increases, the number of bits of the first parameter increases or remains unchanged.

[0173] In one embodiment, the second processing module 1420 is further configured to:

[0174] In a case where the second access message includes the first identifier of the first device but does not include the first parameter of the second device, the context related to the first device is released.

[0175] In one embodiment, the response message includes a first identifier of the first device, where the first identifier of the first device is determined based on the first access message;

[0176] The second processing module 1420 is further configured to:

[0177] In a case where the second access message includes the first parameter of the second device and the first identifier of the first device, conflict resolution for access of the first device is determined.

[0178] In one implementation, the response message includes a second identifier allocated by the second device to the first device, and the second identifier is used for message addressing after access.

[0179] In one embodiment, the second communication module 1410 is further configured to:

[0180] In the case where the second access message includes the first parameter of the second device, an access confirmation message is sent to the first device; wherein the access confirmation message includes the first identifier of the first device, and the first identifier of the first device is determined based on the second access message; the access confirmation message is used by the first device to determine that the initial access is successful.

[0181] In one implementation, the access confirmation message includes a second identifier allocated by the second device to the first device, and the second identifier is used for message addressing after access.

[0182] In one embodiment, the second identifier is determined based on at least a first parameter of the second device.

[0183] In one embodiment, the first identifier of the first device is determined based on a random number.

[0184] The second device 1400 of the embodiment of the present application can implement the corresponding functions of the second device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the second device 1400 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the second device 1400 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0185] Figure 15 is a schematic structural diagram of a communication device 1500 according to an embodiment of the present application. The communication device 1500 includes a processor 1510, which can call and execute a computer program from a memory to enable the communication device 1500 to implement the method in the embodiment of the present application.

[0186] In one embodiment, the communication device 1500 may further include a memory 1520. The processor 1510 may call and execute a computer program from the memory 1520 to enable the communication device 1500 to implement the method in the embodiment of the present application.

[0187] The memory 1520 may be a separate device independent of the processor 1510 , or may be integrated into the processor 1510 .

[0188] In one embodiment, the communication device 1500 may further include a transceiver 1530 , and the processor 1510 may control the transceiver 1530 to communicate with other devices. Specifically, the transceiver 1530 may send information or data to other devices, or receive information or data sent by other devices.

[0189] The transceiver 1530 may include a transmitter and a receiver. The transceiver 1530 may further include an antenna, and the number of antennas may be one or more.

[0190] In one embodiment, the communication device 1500 may be the first device of the embodiment of the present application, and the communication device 1500 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0191] In one embodiment, the communication device 1500 may be the second device of the embodiment of the present application, and the communication device 1500 may implement the corresponding processes implemented by the second device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0192] 16 is a schematic structural diagram of a chip 1600 according to an embodiment of the present application. The chip 1600 includes a processor 1610, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0193] In one embodiment, the chip 1600 may further include a memory 1620. The processor 1610 may call and execute a computer program from the memory 1620 to implement the method performed by the first device or the second device in the embodiment of the present application.

[0194] The memory 1620 may be a separate device independent of the processor 1610 , or may be integrated into the processor 1610 .

[0195] In one embodiment, the chip 1600 may further include an input interface 1630. The processor 1610 may control the input interface 1630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0196] In one embodiment, the chip 1600 may further include an output interface 1640. The processor 1610 may control the output interface 1640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0197] In one embodiment, the chip can be applied to the first device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0198] In one embodiment, the chip can be applied to the second device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the second device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0199] The chips used in the first device and the second device may be the same chip or different chips.

[0200] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0201] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0202] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0203] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0204] FIG17 is a schematic block diagram of a communication system 1700 according to an embodiment of the present application. The communication system 1700 includes a first device 1710 and a second device 1720 .

[0205] After sending the first access message, the first device 1710 receives a response message to the first access message; wherein the response message includes a first parameter of a target device, the target device being the second device 1720 that sends the response message, and the first parameter is used to identify the target device in at least one second device 1720;

[0206] The first device 1710 sends a second access message, wherein the second access message includes the first parameter.

[0207] The second device 1720 receives the first access message;

[0208] The second device 1720 sends a response message to the first access message; wherein the response message includes a first parameter of the second device 1720, and the first parameter is used to identify the second device 1720; the response message is used to trigger the sending of the second access message;

[0209] The second device 1720 receives the second access message, and when the second access message includes the first parameter and the first identifier of the first device 1710 , determines that the first device 1710 is accessed.

[0210] The first device 1710 can be used to implement the corresponding functions implemented by the first device in the above method, and the second device 1720 can be used to implement the corresponding functions implemented by the second device in the above method. For the sake of brevity, they are not described here in detail.

[0211] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0212] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0213] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0214] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. An access method, comprising: After a first device sends a first access message to at least one second device, the first device receives a response message for the first access message sent by a target device among the at least one second device; wherein, the response message includes a first parameter of the target device, and the first parameter is used to identify the target device among the at least one second device; The first device sends a second access message to the at least one second device; wherein, the second access message includes the first parameter.

2. The method according to claim 1, wherein, The first parameter of the target device is unique within the global scope or a local scope of the communication system.

3. The method according to claim 1 or 2, wherein, The number of bits of the first parameter of the target device is related to the number of second devices within the global scope or a local scope of the communication system.

4. The method according to claim 3, wherein, When the number of the second devices increases, the number of bits of the first parameter increases or remains unchanged.

5. The method according to any one of claims 1-4, wherein, The second access message is further used to instruct other second devices except the target device to release the context related to the first device.

6. The method according to any one of claims 1-5, wherein, The first access message includes a first identifier of the first device; The first device sends a second access message to the at least one second device, including: When the first identifier in the response message is the same as the first identifier of the first device, the first device sends the second access message to the at least one second device; wherein, the second access message further includes the first identifier of the first device, and the first identifier in the second access message is used for the target device to determine conflict resolution.

7. The method according to claim 6, wherein, The response message further includes a second identifier assigned by the target device to the first device, and the second identifier is used for message addressing after access.

8. The method according to any one of claims 1-5, wherein, The second access message further includes the first identifier of the first device; the first parameter in the second access message is used for the target device to determine conflict resolution to trigger the target device to send an access confirmation message.

9. The method according to claim 8, wherein, The method further includes: After sending the second access message, the first device receives the access confirmation message, and when the access confirmation message includes the first identifier of the first device, determines that the initial access is successful.

10. The method according to claim 9, wherein, The access confirmation message includes a second identifier assigned by the target device to the first device, and the second identifier is used for message addressing after access.

11. The method according to claim 7 or 10, wherein, The second identifier is at least determined based on the first parameter of the target device.

12. The method according to any one of claims 6-11, wherein, The first identifier of the first device is determined based on a random number.

13. An access method, comprising: A second device receives a first access message from a first device; The second device sends a response message to the first device for the first access message; wherein, the response message includes a first parameter of the second device, and the first parameter is used to identify the second device; the response message is used to trigger the sending of a second access message; The second device receives a second access message from the first device, and determines that the first device accesses when the second access message includes the first parameter and the first identifier of the first device.

14. The method according to claim 13, wherein, The first parameter of the second device is unique within the global or local scope of the communication system.

15. The method according to claim 13 or 14, wherein, The number of bits of the first parameter of the second device is related to the number of second devices within the global or local scope of the communication system.

16. The method according to claim 15, wherein, When the number of second devices increases, the number of bits of the first parameter increases or remains unchanged.

17. The method according to any one of claims 13-16, wherein, The method further comprises: The second device releases the context related to the first device when the second access message includes the first identifier of the first device but does not include the first parameter of the second device.

18. The method according to any one of claims 13-17, wherein, The response message includes the first identifier of the first device; The method further comprises: The second device determines conflict resolution for the first device access when the second access message includes the first parameter of the second device and the first identifier of the first device.

19. The method according to claim 18, wherein, The response message includes a second identifier assigned by the second device to the first device, and the second identifier is used for message addressing after access.

20. The method according to any one of claims 13-17, wherein, The method further comprises: The second device sends an access confirmation message to the first device when the second access message includes the first parameter of the second device; wherein, the access confirmation message includes the first identifier of the first device, and the first identifier of the first device is determined based on the second access message; the access confirmation message is used for the first device to determine that the initial access is successful.

21. The method according to claim 20, wherein, The access confirmation message includes a second identifier assigned by the second device to the first device, and the second identifier is used for message addressing after access.

22. The method according to claim 19 or 21, wherein, The second identifier is determined at least based on the first parameter of the second device.

23. The method according to any one of claims 13-22, wherein, The first identifier of the first device is determined based on a random number.

24. A first device, including: A first communication module, configured to receive, after sending a first access message to at least one second device, a response message sent by a target device among the at least one second device in response to the first access message; wherein, the response message includes a first parameter of the target device, and the first parameter is used to identify the target device among the at least one second device; The first communication module is further configured to send a second access message to the at least one second device; wherein, the second access message includes the first parameter.

25. The first device according to claim 24, wherein, The first parameter of the target device is unique within the global or local scope of the communication system.

26. The first device according to claim 24 or 25, wherein, The number of bits of the first parameter of the target device is related to the number of second devices within the global or local scope of the communication system.

27. The first device according to claim 26, wherein, When the number of second devices increases, the number of bits of the first parameter increases or remains unchanged.

28. The first device according to any one of claims 24 - 27, wherein, The second access message is further configured to instruct other second devices except the target device to release the context related to the first device.

29. The first device according to any one of claims 24 - 28, wherein, The first access message includes a first identifier of the first device; The first communication module is further configured to send the second access message when the first identifier in the response message is the same as the first identifier of the first device; wherein, the second access message further includes the first identifier of the first device, and the first identifier in the second access message is used for the target device to determine conflict resolution.

30. The first device according to claim 29, wherein, The response message further includes a second identifier assigned by the target device to the first device, and the second identifier is used for message addressing after access.

31. The first device according to any one of claims 24 - 28, wherein, The second access message further includes the first identifier of the first device; the first parameter in the second access message is used for the target device to determine conflict resolution to trigger the target device to send an access confirmation message.

32. The first device according to claim 31, wherein, The first communication module is further configured to receive an access confirmation message after sending the second access message; The first device further includes a first processing module, and the first processing module is configured to: Determine that the initial access is successful when the access confirmation message includes the first identifier of the first device.

33. The first device according to claim 32, wherein, The access confirmation message includes a second identifier assigned by the target device to the first device, and the second identifier is used for message addressing after access.

34. The first device according to claim 30 or 33, wherein, The second identifier is determined at least based on the first parameter of the target device.

35. The first device according to any one of claims 29 - 34, wherein, the first identifier of the first device is determined based on a random number.

36. A second device, comprising: a second communication module, configured to receive a first access message from the first device, send a response message to the first device for the first access message, and receive a second access message from the first device; wherein the response message includes a first parameter of the second device, the first parameter being used to identify the second device; the response message is used to trigger the sending of the second access message; a second processing module, configured to determine that the first device accesses in the case that the second access message includes the first parameter and the first identifier of the first device.

37. The second device according to claim 36, wherein, the first parameter of the second device is unique within the global or local scope of the communication system.

38. The second device according to claim 36 or 37, wherein, the number of bits of the first parameter of the second device is related to the number of second devices within the global or local scope of the communication system.

39. The second device according to claim 38, wherein, in the case that the number of second devices increases, the number of bits of the first parameter increases or remains unchanged.

40. The second device according to any one of claims 36 - 39, wherein, the second processing module is further configured to: release the context related to the first device in the case that the second access message includes the first identifier of the first device but does not include the first parameter of the second device.

41. The second device according to any one of claims 36 - 40, wherein, the response message includes the first identifier of the first device; the second processing module is further configured to: determine the conflict resolution of the first device access in the case that the second access message includes the first parameter of the second device and the first identifier of the first device.

42. The second device according to claim 41, wherein, the response message includes a second identifier assigned by the second device to the first device, the second identifier being used for message addressing after access.

43. The second device according to any one of claims 36 - 40, wherein, the second communication module is further configured to: send an access confirmation message to the first device in the case that the second access message includes the first parameter of the second device; wherein the access confirmation message includes the first identifier of the first device, the first identifier of the first device being determined based on the second access message; the access confirmation message is used for the first device to determine that the initial access is successful.

44. The second device according to claim 43, wherein, the access confirmation message includes a second identifier assigned by the second device to the first device, the second identifier being used for message addressing after access.

45. The second device according to claim 42 or 44, wherein, the second identifier is determined at least based on the first parameter of the second device.

46. The second device according to any one of claims 36 - 45, wherein, the first identifier of the first device is determined based on a random number.

47. A first device, comprising: a transceiver, a processor, and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory, so that the first device executes the method according to any one of claims 1 to 12.

48. A second device, comprising: a transceiver, a processor, and a memory, the memory being used to store a computer program, the transceiver being used to communicate with other devices, and the processor being used to call and run the computer program stored in the memory, so that the second device executes the method according to any one of claims 13 to 23.

49. A chip, comprising: a processor, which is used to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 12.

50. A chip, comprising: a processor, which is used to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 13 to 23.

51. A computer - readable storage medium for storing a computer program, which when run by a device causes the device to execute the method according to any one of claims 1 to 12.

52. A computer - readable storage medium for storing a computer program, which when run by a device causes the device to execute the method according to any one of claims 13 to 23.

53. A computer program product comprising computer program instructions, which cause a computer to execute the method according to any one of claims 1 to 12.

54. A computer program product comprising computer program instructions, which cause a computer to execute the method according to any one of claims 13 to 23.

55. A computer program, which causes a computer to execute the method according to any one of claims 1 to 12.

56. A computer program, which causes a computer to execute the method according to any one of claims 13 to 23.

57. A communication system, comprising: a first device for executing the method according to any one of claims 1 to 12; a second device for executing the method according to any one of claims 13 to 23.

Images