Wireless communication method, device, chip, storage medium, program product and program

Abstract

The invention provides a wireless communication method and device, a chip, a storage medium, a program product and a program, which can meet the access requirements of massive terminal equipment. The method comprises: receiving first configuration information from a network device, the first configuration information being used for configuring a first resource pool and / or a second resource pool, the first resource pool being used for the terminal device to perform random access based on a non-orthogonal signature, and the second resource pool being used for the terminal device to perform identification-free random access.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a wireless communication method, apparatus, chip, storage medium, program product, and program. Background Technology

[0002] To improve resource utilization, network devices can allocate resources to terminal devices based on multiple access technology. However, the spectral efficiency of this approach is limited by resource granularity and cannot fully meet the demands of ultra-high connection density and high throughput.

[0003] Next-generation communication systems (such as 6G communication systems) face challenges such as providing ultra-high capacity, ultra-low latency, and massive connectivity. For these communication systems, if access is still provided using the traditional random access method, the limited resources will not be able to meet the access needs of a massive number of terminal devices. Therefore, there is a need to provide an access method that can meet the access needs of a massive number of terminal devices. Summary of the Invention

[0004] This application provides a wireless communication method, apparatus, chip, storage medium, program product, and program that can meet the access needs of a massive number of terminal devices.

[0005] In a first aspect, a wireless communication method is provided, comprising: receiving first configuration information from a network device, the first configuration information being used to configure a first resource pool and / or a second resource pool, the first resource pool being used by the terminal device for random access based on non-orthogonal signatures, and the second resource pool being used by the terminal device for performing unsigned random access.

[0006] In a second aspect, a wireless communication method is provided, comprising: sending first configuration information to a terminal device, the first configuration information being used to configure a first resource pool and / or a second resource pool, the first resource pool being used by the terminal device for random access based on non-orthogonal signatures, and the second resource pool being used by the terminal device for performing unsigned random access.

[0007] Thirdly, a terminal device is provided, comprising: a receiving unit, configured to receive first configuration information from a network device, the first configuration information being configured to configure a first resource pool and / or a second resource pool, the first resource pool being used by the terminal device for random access based on non-orthogonal signatures, and the second resource pool being used by the terminal device for performing unsigned random access.

[0008] Fourthly, a network device is provided, comprising: a sending unit, configured to send first configuration information to a terminal device, the first configuration information being configured to configure a first resource pool and / or a second resource pool, the first resource pool being used by the terminal device for random access based on non-orthogonal signatures, and the second resource pool being used by the terminal device for performing unsigned random access.

[0009] Fifthly, a terminal device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory, causing the terminal device to perform some or all of the steps in the method of the first aspect.

[0010] In a sixth aspect, a network device is provided, including a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect.

[0011] Seventhly, embodiments of this application provide a communication system including the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device and network device as described in the embodiments of this application.

[0012] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device (e.g., a terminal device and a network device) to perform some or all of the steps in the methods described above.

[0013] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device (e.g., a first device or a second device) to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0014] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0015] The technical solution provided in this application configures a resource pool (i.e., the second resource pool) for unidentified random access and / or a resource pool (i.e., the first resource pool) for random access based on non-orthogonal signatures for terminal devices. This allows terminal devices to access the network without using traditional random access methods. Instead, they can use resources in the first or second resource pool for unidentified random access. When a terminal device needs to transmit data, it can directly select resources from the first or second resource pool to send the data. This method is not limited by resource granularity and can meet the access needs of a large number of terminal devices. Attached Figure Description

[0016] Figure 1 This is a system architecture diagram of a wireless communication system to which embodiments of this application can be applied;

[0017] Figure 2 This is a schematic flowchart of a competition-based random access method.

[0018] Figure 3 A schematic flowchart illustrating a communication method provided in an embodiment of this application;

[0019] Figure 4 A schematic block diagram of a terminal device provided in an embodiment of this application;

[0020] Figure 5 A schematic block diagram of a network device provided in an embodiment of this application;

[0021] Figure 6 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0022] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0023] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0024] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.

[0025] Figure 1 This is a schematic diagram of a communication system 100 used in an embodiment of this application. The communication system 100 may include network devices, such as... Figure 1 The network device 110 is shown. The communication system 100 may also include terminal devices, such as... Figure 1 The terminal device 120 is shown. The network device 110 and the terminal device 120 can communicate via a wireless link.

[0026] Figure 1 An exemplary network device 110 and a terminal device 120 are shown. Optionally, the communication system 100 may also include multiple network devices and / or multiple terminal devices.

[0027] The network equipment in this application can be network-side equipment such as access network equipment and core network equipment. Access network equipment is sometimes also called an access node. Access network equipment has wireless transceiver capabilities for communicating with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the aforementioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units capable of implementing some of the functions of a base station. Access network equipment can be a macro base station (such as...). Figure 1 110a), micro base stations or indoor stations (such as Figure 1 In the context of 110b), the access network device can be a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network device can also be a server, wearable device, or vehicle-mounted device, etc. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations in different access technologies. The embodiments of this application do not limit the specific technology or device form used in the access network device. In this application, the access network device is referred to as a network device.

[0028] In this application, the means for implementing the functions of a network device can be a network device itself, or a means capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This means can be installed in or connected to the network device. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0029] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.

[0030] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solutions provided in this application, the example of a terminal device being used to implement the functions of a terminal device is used to describe the technical solutions provided in this application.

[0031] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios; for example, both can be deployed on land; or the access network device can be deployed on land, and the terminal device on water, etc., and so on.

[0032] In practical applications, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0033] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0034] Terminal devices can achieve uplink synchronization with network devices through random access. A typical random access method is contention-based random access, which will be discussed below. Figure 2 This section provides a detailed introduction to the competition-based random access method.

[0035] See Figure 2 In step S210, the terminal device sends Msg1 during the random access process to the network device. Msg1 may include a preamble.

[0036] The terminal device can select a random access channel (RACH) resource and a preamble, and transmit the selected preamble on the selected resource. This RACH resource can also be called a physical random access channel (PRACH) resource.

[0037] Network devices can broadcast RACH configuration information to terminal devices. The RACH configuration information may include the configuration information for the RACH time and frequency resources, as well as the configuration information for the starting preamble root sequence.

[0038] The configuration information for RACH time-domain resources can be indicated by a RACH configuration index. This index may include at least one of the following: the RACH resource repetition period, the number of RACH opportunities (ROs) within a single RACH resource repetition period, and the duration of each RO. The configuration information for RACH frequency-domain resources may include a RACH start frequency-domain resource index and the number of RACH resources that can be frequency-division multiplexed at the same time (i.e., the number of consecutive RACH frequency-domain resources). A continuous range of frequency-domain resources can be determined using this RACH frequency-domain resource configuration information. The initial preamble root sequence can be broadcast by the cell; each cell can broadcast one preamble root sequence. Based on this configured initial preamble root sequence, the set of preambles available to the cell can be obtained through cyclic shifting.

[0039] RACH configuration information can be carried in system messages, meaning network devices can send RACH configuration information through system messages. System messages may include a synchronization signal / physical broadcast channel block (SSB), which the network device can broadcast to the terminal device. This SSB can be a cell-defining SSB (CD-SSB). The SSB may include the master indication block (MIB) and system information block (SIB) for the stationary cell. The SIB may include SIB1 and other SIBs. SIB1 may indicate the configuration information related to the initial bandwidth part (BWP) for initial access of the terminal device, which may include the initial uplink BWP and the initial downlink BWP. In the initial uplink BWP, the network device can configure random access resources for the terminal device initially accessing the network. There is a correspondence between these random access resources and SSBs. For example, the network device can control the terminal device's selection of random access resources by configuring a reference signal receiving power (RSRP) threshold. When a random access procedure is triggered, the terminal device can select an SSB whose RSRP measurement value meets the RSRP threshold, and select the corresponding random access resource to send the preamble according to the correspondence between the SSB and the random access resource.

[0040] In step S220, the network device sends Msg2 to the terminal device. This Msg2 can also be called a random access response (RAR). This Msg2 can be carried through the physical downlink control channel (PDCCH).

[0041] After the terminal device sends Msg1, it can open a random access response time window and monitor the PDCCH scrambled with random access-radio network temporary identifier (RA-RNTI) within the time window.

[0042] Msg2 may also include a preamble sent by the terminal device. If the terminal device receives a PDCCH scrambled with RA-RNTI and Msg2 contains its own preamble, the terminal device can consider that it has successfully received the random access response.

[0043] After successfully receiving the PDCCH, the terminal device can obtain the PDSCH scheduled by the PDCCH, which contains the RAR. The RAR can contain multiple pieces of information. For example, the subheader of the RAR can contain a backoff indicator (BI), which can be used to indicate the backoff time for retransmitting Msg1; the random access preamble identification (RAPID) in the RAR indicates the index of the received preamble in the network device's response; the payload in the RAR can contain a timing advance group (TAG), which can be used to adjust uplink timing; the RAR can also include an uplink grant (UL grant), used to schedule uplink resources for Msg3; and the RAR can also include a cell-radionetwork temporary identifier (C-RNTI), which the terminal device can use to decode the PDCCH of Msg4 for initial access.

[0044] In step S230, the terminal device sends Msg3 to the network device. The terminal device can send Msg3 on a ULgrant scheduled by the network device. This Msg3 can also be called a Radio Resource Control (RRC) Connection Establishment Request message.

[0045] In step S240, the network device sends Msg4 to the terminal device. Msg4 is carried in the PDSCH, therefore, Msg4 can also be called Msg4 PDSCH.

[0046] Msg4 serves two purposes: contention resolution and sending an RRC configuration message to the terminal device. If the terminal device carries a C-RNTI in Msg3, Msg4 uses a PDCCH scrambled with that C-RNTI for scheduling. The terminal device can then decode the PDCCH using the C-RNTI in Msg3 to obtain Msg4. If the terminal device does not carry a C-RNTI in Msg3, such as during initial access, Msg4 can use a PDCCH scrambled with a temporary C-RNTI for scheduling. The terminal device can then decode the PDCCH using the temporary C-RNTI in Msg2 to obtain Msg4. After successfully decoding the PDCCH, the terminal device obtains the PDSCH carrying Msg4. The terminal device can compare the Common Control Channel (CCCH) Service Data Unit (SDU) in this PDSCH with the CCCH SDU in Msg3. If they are the same, the contention resolution is successful.

[0047] Based on the reception status of Msg4, the terminal device can send a hybrid automatic repeat request (HARQ) response to the network device. HARQ responses include acknowledgement (ACK) and negative acknowledgement (NACK) messages.

[0048] If the terminal device receives Msg4 and successfully decodes it, it can also send an ACK feedback message to the network device. After receiving the ACK feedback from the terminal device, the network device can send downlink control information (DCI) to the terminal device. This DCI is used to schedule physical uplink shared channel (PUSCH) (or Msg5 PUSCH) resources. The terminal device can then send Msg5 to the network device on the PUSCH resources. This Msg5 includes an RRC connection setup complete message.

[0049] If the terminal device fails to decode Msg4, it can send a NACK feedback message to the network device. Upon receiving the NACK feedback message, the network device can schedule a retransmission of Msg4. For example, the network device can send a DCI to the terminal device, which is used to schedule PDSCH resources for retransmitting Msg4. The terminal device then receives Msg4 from the network device on the PDSCH resources. If the terminal device fails to receive Msg4 multiple times, the network device can instruct the terminal device to re-initiate random access.

[0050] To improve resource utilization, network devices can allocate resources to terminal devices based on multiple access technologies. Currently, the mainstream multiple access method is orthogonal multiple access (OMA), which includes time division multiple access (TDMA), frequency division multiple access (FDMA), and orthogonal frequency division multiple access (OFDMA). Although OMA effectively avoids co-channel interference, its spectral efficiency is limited by resource granularity in high-load scenarios, failing to fully meet the demands of ultra-high connection density and high throughput. Next-generation wireless communication systems (such as 6G systems) face challenges in providing ultra-high capacity, ultra-low latency, and massive connectivity; therefore, multiple access technologies need to evolve accordingly.

[0051] For next-generation wireless communication systems, vehicle-to-everything (V2X), the Internet of Things (IoT), and large-scale sensor networks will bring about a demand for simultaneous access of millions to tens of millions of terminal devices per square kilometer. These networks are characterized by a massive number of devices connected to a single network device, small data transmissions per device, and most devices being in a dormant state, only transmitting data when triggered by specific events or periodically woken up. Most devices do not have high latency requirements and can tolerate a certain amount of retransmission.

[0052] For traditional scheduling-based orthogonal access, such as Figure 2 As shown, terminal devices need to send an access request first, and then the base station allocates resources. This process has high signaling overhead and high latency, making it difficult to support the uplink transmission of ultra-large-scale small packets. Therefore, for next-generation wireless communication systems, there is a need to provide an access method with low signaling overhead and low latency to meet the demands of massive access.

[0053] To address this issue, an unlicensed random access method, including unsourced random access (URA), was proposed. When a terminal device wants to send data, it does not need to pre-request resources; instead, it randomly sends data packets directly from a predefined pool of public resources. The principle of URA is that all terminals share the same codebook. Terminal devices map their messages to codewords in the codebook without sending their own identifiers. Network devices recover the message set by detecting the transmitted codewords, without needing to determine the message's origin. Compared to active random access (i.e., traditional random access), URA has higher spectral efficiency because it does not require sending pilot sequences for identity verification. Furthermore, URA has lower computational complexity, which depends only on the number of active (or active) terminal devices and is independent of the total number of potential devices. Therefore, URA is well-suited for wireless communication systems with a large number of access devices but a relatively small number of active devices.

[0054] However, there is currently no clear solution regarding how to use unlicensed random access technology.

[0055] Based on this, embodiments of this application provide a communication method that, by configuring a resource pool (i.e., a second resource pool) for unidentified random access and / or a resource pool (i.e., a first resource pool) for random access based on non-orthogonal signatures for a terminal device, enables the terminal device to access the network without using the traditional random access method, but instead to use the resources in the first or second resource pool for unauthorized random access, thereby providing a clear solution for the unauthorized random access method of the terminal device.

[0056] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0057] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0058] The network device in this application embodiment can be a base station or a RAN node. This network device can be an artificial intelligence (AI) based network device. RAN has traditionally been built as a dedicated infrastructure to provide mobile broadband services to terminal devices. However, with the surge in modern application demands and the proliferation of connected device types, the limitations of traditional RAN have become increasingly apparent. Therefore, RAN is evolving from simply supporting mobile broadband to a more general architecture supporting diverse vertical industry applications and heterogeneous workloads. One major shift is the convergence of communication and computing, enabling the network to not only provide connectivity services but also implement computing services at the network edge (i.e., edge computing). Edge computing moves some data / signal processing from the central cloud or terminal devices to the edge cloud, potentially achieving lower latency, lower transmission costs, and higher privacy protection. A key factor driving the development of edge computing is running RAN functions and AI workloads (especially large language models based on generative artificial intelligence) on the same edge infrastructure. This convergence transforms the traditional single-function RAN infrastructure into a unified AI-RAN architecture that integrates AI and RAN. This integration enables automation of zero-touch network and service management (ZSM), intelligent radio resource control, and improved spectrum efficiency of communication networks.

[0059] By using an AI-based RAN architecture, network devices can become more intelligent. This architecture can be applied to new mobile communication systems, such as 6G and subsequent mobile communication systems. Based on virtualized resource orchestration, this architecture can support multiple communication systems, including LTE and NR, through the allocation and orchestration of virtualized resource pools. The AI-based RAN architecture integrates RAN functions and AI workloads on the same infrastructure. AI-RAN not only meets the performance requirements of future networks but also improves resource utilization. AI-RAN can include three forms: AI-for-RAN, AI-on-RAN, and AI-and-RAN. Some of the solutions described below can be implemented using AI functions within network devices.

[0060] In some implementations, the terminal device in this application embodiment can be a terminal device in an RRC idle state. This terminal device accesses the network device via random access.

[0061] Figure 3 This is a schematic diagram of a communication method 300 according to an embodiment of this application. It can be understood that... Figure 3 The terminal device in the middle can be Figure 1Any terminal device in the context of network equipment can also refer to a component within that terminal device (such as a processor, chip, or chip system). Network equipment can be... Figure 1 Any access network device, or a component within an access network device (such as a processor, chip, or chip system). Figure 3 As shown, the method 300 includes step S310.

[0062] See Figure 3 In step S310, the network device sends first configuration information to the terminal device. This first configuration information is used to configure a first resource pool and / or a second resource pool. For example, the first configuration information may only configure the first resource pool. Alternatively, the first configuration information may only configure the second resource pool. Or, the first configuration information may configure both the first and second resource pools simultaneously. The first configuration information is sent via broadcast.

[0063] If the first configuration information configures a first resource pool, the terminal device can use the resources in the first resource pool for random access; if the first configuration information configures a second resource pool, the terminal device can use the resources in the second resource pool for random access. If the first configuration information configures both a first resource pool and a second resource pool, the terminal device can use the resources in either the first or second resource pool for random access, or the terminal device can select a resource pool based on the access conditions corresponding to the first and second resource pools. Specific solutions will be described below.

[0064] The resources in the first resource pool and the second resource pool are unauthorized resources. That is, the terminal device can directly use the resources in the first resource pool or the second resource pool to send data or access the network device without authorization from the network device, or without sending a PRACH request or RRC request to the network device.

[0065] In some implementations, the first resource pool is used for terminal devices to perform random access based on non-orthogonal signatures. A non-orthogonal signature can also be understood as a non-orthogonal sequence or non-orthogonal codebook. The role of a non-orthogonal signature is similar to the preamble in traditional random access schemes, except that the preamble in traditional schemes is an orthogonal code, while the signature in this application is a non-orthogonal signature. Non-orthogonal signatures can improve spectrum efficiency to meet the massive access demands of next-generation wireless communication systems.

[0066] In some implementations, the second resource pool can be used by terminal devices to perform unidentified random access. Terminal devices can use resources in this pool to send data without identifying themselves.

[0067] The implementation process of non-orthogonal signature random access and unidentified random access is described below. We will first introduce the non-orthogonal signature random access process.

[0068] For the first resource pool, data transmission methods include SCMA / signature + MPA / CS-MUD + RSMA common stream assistance. SCMA stands for Sparse Code Multiple Access, and MPA stands for Message Passing Algorithm. Both perform near-optimal multi-terminal detection / decoding on the factor graph and are often used in conjunction with SCMA. CS-MUD stands for Compressed Sensing-Multi-User Detection. Network devices utilize the sparse structure of active users and use sparse reconstruction for activity detection and data recovery. RSMA stands for Rate-Splitting Multiple Access. It divides the information of each terminal device into a common stream and a private stream. Network devices can first decode the common stream information of all terminal devices (reducing interference) and then decode the private stream information of each terminal device.

[0069] In some implementations, the network device can send second configuration information to the terminal device. This second configuration information is used to configure a non-orthogonal signature set. The second configuration information is sent via broadcast. The non-orthogonal signature set includes multiple signatures that are non-orthogonal to each other. Signatures can also be referred to as sequences or codebooks, etc.

[0070] In some implementations, there is a mapping relationship between signatures and resources. The terminal device can determine the resource corresponding to the signature. This resource can be, for example, a resource block (RB) or a resource element (RE).

[0071] In some implementations, the terminal device can randomly select a first signature from a non-orthogonal signature set, and based on the mapping relationship between the signature and resources, select a first resource corresponding to the first signature from a first resource pool, and transmit data on the first resource. Transmitting data on the first resource includes: the terminal device mapping data to the first resource for transmission. The first resource may include multiple REs or RBs.

[0072] The terminal device can randomly select the first signature in several ways, including by selecting the first signature based on a hash rule or a random rule. Since the resource selection by each terminal device is random, the probability of two terminal devices selecting the same resource is low. This can, to some extent, reduce the access conflict rate and improve the access success rate of terminal devices.

[0073] The data sent by the terminal device may include a header and a payload. The header includes one or more of the following information: a session token, a data length indicator, and integrity verification information. The session token may be, for example, a token.

[0074] In some implementations, the terminal device can also send the selected signature and data together to the network device so that the network device can identify the terminal device.

[0075] On the network side, network devices first perform active signature monitoring and coarse separation on signals received from the first resource pool. They then reuse existing reference signals (such as PUSCH-demodulation reference signal (DMRS), sounding reference signal (SRS), channel state information-reference signal (CSI-RS), etc.) or embedded pilot signals to complete channel estimation. The signals are then jointly decoded in the order of public stream first, followed by private stream. The received data is verified based on integrity check information. Based on the reception and verification results, a HARQ list and retransmission policy are broadcast on the downlink common channel. The HARQ list may include an ACK list and / or a NACK list.

[0076] Terminal devices can determine whether their data transmission was successful based on the HARQ list. If transmission fails, retransmission is performed according to a retransmission policy. This policy may include, for example, the number of retransmissions and the power ramp-up step size.

[0077] In some implementations, the aforementioned non-orthogonal signature set can be a multi-resolution signature set (MRSS). MRSS can be used to determine which signature or sparse pattern to overlay on which resources, such as REs, RBs, or symbols.

[0078] In some implementations, the signatures in the multi-resolution signature set correspond to at least two of the following dimensions of information: time domain, frequency domain, code domain, and spatial domain. In other words, multi-resolution can include at least two of the time domain, frequency domain, code domain, and spatial domain.

[0079] Taking multi-resolution, which includes both time and frequency domains, as an example, network devices can divide time-domain and frequency-domain resources into multiple resource blocks and establish a correspondence between these resource blocks and multiple signatures (i.e., signatures in a multi-resolution signature set). Terminal devices can randomly select a signature from the multi-resolution signature set and, based on the correspondence between resource blocks and signatures, determine the transmission resources (time-domain and frequency-domain resources) and send data on those transmission resources.

[0080] In some implementations, the second configuration information can be used to configure multiple multi-resolution signature sets, where one multi-resolution signature set corresponds to one BWP and / or one subcarrier spacing. For example, one multi-resolution signature set corresponds to one subcarrier spacing, and multiple multi-resolution signature sets correspond to multiple subcarrier spacings respectively. This allows resources to be divided into different granularities based on the different subcarrier spacings, thereby improving resource utilization and spectral efficiency. Subcarrier spacings can include 15kHz, 30kHz, 60kHz, 120kHz, etc. The terminal device can select the corresponding multi-resolution signature set according to the subcarrier spacing used.

[0081] For example, one multi-resolution signature set corresponds to one BWP, and multiple multi-resolution signature sets correspond to multiple BWPs respectively. In this way, different multi-resolution signature sets can be configured for different BWPs, so that the multi-resolution signature sets are matched with the BWPs, thereby improving resource utilization and spectrum efficiency. Terminal devices can select the corresponding multi-resolution signature set according to the BWP they are using.

[0082] For example, a multi-resolution signature set corresponds to a combination of a base station (BWP) and a subcarrier. Network devices can configure a multi-resolution signature set for each BWP and subcarrier combination, allowing for more flexible resource configuration and improving resource utilization and spectrum efficiency. Terminal devices can select the corresponding multi-resolution signature set based on the subcarrier spacing and BWP used.

[0083] In some implementations, network devices can be configured with semi-static or dynamic MRSS. For example, network devices can configure semi-static MRSS via SIB or RRC. Semi-static MRSS configuration information may include one or more of the following: MRSS resource pool list (MRSS-PoolList), MRSS signature set (MRSS-SignatureSet), MRSS unlicensed policy (MRSS-GF-Policy), and associated BWP (bwp-Assoc).

[0084] The MRSS resource pool list can be used to indicate which resource pools (such as the first, second, or third resource pool) can use MRSS, as well as the time-frequency location, BWP, and subcarrier spacing within the resource pool where MRSS can be used. The MRSS signature set can be used to indicate one or more of the following information: MRSS set identifier (setID), signature length (codeLen), code field sparsity, maximum concurrency value, and pilot pattern.

[0085] The MRSS set identifier can be used to indicate whether the terminal device uses coarse resolution or fine resolution. Coarse resolution means that a signature corresponds to only one resolution, while fine resolution means that a signature corresponds to multiple resolutions. Fine resolution is the multi-resolution mentioned above.

[0086] Code domain sparsity, also known as the sparsity factor, refers to the sparser the code domain sparsity. The finer the "fingerprint" sent by the terminal device, the easier it is to distinguish it from other devices. Code domain sparsity provides prior information for the sparse recovery algorithm used by network devices, which helps improve separability and convergence. Within a given bandwidth or time slot, code domain sparsity can be determined based on "multi-user separability" and "single-user reliability." The terminal device can use the sparsity factor to pseudo-randomly extract L RE or chip positions using a seed or token to form its own sparse mapping.

[0087] The maximum concurrency value can refer to the upper limit of the number of terminal devices (or the target concurrency level) that a network device can support within a MRSS detection window.

[0088] In some implementations, the network device can predict a first parameter related to MRSS based on second information. The first parameter includes one or more of the following: code domain sparsity, maximum concurrency, and the ratio between a multi-resolution signature set and a single-resolution signature set. The second information includes one or more of the following: resource utilization, random access collision rate, block error rate (BLER), tail latency, uplink load, downlink load, and power ramp-up retransmission ratio. The prediction process for the first parameter can be implemented by an AI model or an AI controller.

[0089] A multi-resolution signature set corresponds to a coarse-resolution signature set, and a single-resolution signature set corresponds to a fine-resolution signature set. The ratio between a multi-resolution signature set and a single-resolution signature set can be used to refer to the ratio between the size (or number) of the multi-resolution signature set and the size (or number) of the single-resolution signature set.

[0090] Uplink load refers to the load on the uplink channel, and downlink load refers to the load on the downlink channel. Power ramp retransmission ratio can be defined as the ratio of the number of terminal devices retransmitting via power ramp to the total number of terminal devices accessing the network.

[0091] The guidance pattern indicates whether DMRS or a dedicated pilot is being reused. The MRSS unlicensed policy can be used to indicate the available tiers, maximum number of retries, and power ramp-up step size for each service type. The associated BWP can be used to indicate the BWP and / or subcarrier spacing associated with the setID, allowing the terminal device to select the resolution based on its capabilities.

[0092] For example, network devices can configure dynamic MRSS via DCI. Dynamic MRSS configuration information can include authorized MRSS and / or HARQ configuration. Authorized MRSS includes one or more of the following: resource pool identifier (poolId), MRSS set identifier (setId), whether it is enabled, window start position, window length, mode ∈ {explicit or hash}, number of sub-resources (Nres), hash seed, open-loop power P0, power ramp step size, and modulation and coding scheme (MCS) set. Whether it is enabled indicates whether the MRSS is activated. The window start position and window length indicate the window positions where the MRSS can be used.

[0093] HARQ configuration is used to provide feedback methods and retry suggestions for successful or failed access. HARQ configuration includes one or more of the following: token, HARQ identifier, and retryHint.

[0094] The following describes the mapping methods between signatures and resources. In the time domain, MRSS can be enabled on multiple OFDM symbols within a time window. In the frequency domain, a frequency domain resource (such as a PRB) can be selected within the BWP as the MRSS subband. For the code domain or resolution dimension, it can be divided into coarse resolution (L0) and fine resolution (L1), where the signature length corresponding to coarse resolution is greater than that corresponding to fine resolution. Coarse resolution features long signatures, low code density, and strong pilot multiplexing, making it suitable for terminal equipment accessing the network for the first time or located at the cell edge. Fine resolution features short signatures, high code density, and higher capacity. In the spatial dimension or spatial domain, different beams or DMRS ports can be bound to different signatures, utilizing the spatial multiplexing characteristics of mMIMO to reduce collisions. For pilots, PUSCH-DMRS can be reused preferentially; if the signature uses a pilot design, it can be refined based on traditional DMRS.

[0095] In some implementations, the terminal device can determine whether to perform MRSS unlicensed access based on certain preset conditions. These preset conditions are related to one or more of the following: the terminal device's mobility, the size of the data packet, and the congestion level of the resource pool.

[0096] If the terminal device determines to perform MRSS unlicensed access, it can generate header information, which includes one or more of the following: session token, data length indicator, quality of service (QoS) level, and integrity verification information. The integrity verification information can be a cyclic redundancy check (CRC) or a message authentication code (MAC), etc.

[0097] The terminal device selects either a signature or a sub-resource. The terminal device can randomly select a sub-resource based on a hash rule; for example, it can select a sub-resource based on hash(Token, seed) mod Nres, where Nres is the number of sub-resources and mod represents the modulo operation. Then, the terminal device selects the signature length level (L0 or L1) and signature index under setId. setId is the identifier for the multi-resolution signature set.

[0098] The terminal device performs sparse mapping and data transmission. It maps the header and payload to the selected RE according to the signature sparse pattern and sends it to the network device. The data transmission power can start at P0+Δ and increase in increments of Δ, where Δ is the power increment step.

[0099] After data transmission, the terminal device can detect ACK feedback. The terminal device can search for its own token in the ACK window. If an ACK for its own token is detected in the ACK window, the data transmission is successful. If a NACK for its own token is detected in the ACK window, or if no ACK for its own token is detected in the ACK window, the data transmission has failed, and the terminal device needs to retransmit the data. The terminal device can change its signature, change its sub-resource, or increase its power according to the retransmission instruction to retransmit the data. If the number of retransmissions exceeds the limit, it will fall back to four-step random access.

[0100] On the network side, network devices can uniformly receive data. Network devices can perform frequency offset compensation and / or timing compensation on the MRSS sub-pool to align with the BWP.

[0101] Network devices perform activity detection. They can compress and sense the configured signature set and refine it step by step according to L0 or L1 to obtain active signature-sub-resource candidate signals and their corresponding confidence levels.

[0102] Network devices perform joint estimation and demodulation. They can reuse existing reference signals for channel estimation, including one or more of the following: PUSCH-DMRS, SRS, CSI-RS, etc. Additionally, network devices can execute approximate message passing (AMP), MPA, or factor graph message passing algorithms on the candidate subspace to jointly recover data from multiple terminal devices.

[0103] After receiving the data, the network device can perform consistency checks and / or integrity checks. For example, the network device can use data length indicators and / or integrity verification information to validate the data, deduplicate it, and form a message set.

[0104] Network devices broadcast ACK lists and / or NACK lists based on the message set. For example, if terminal device 1 successfully decodes a message, the network device can send an ACK for that message, which may carry the token used by terminal device 1. The terminal device can determine whether its message was successfully decoded based on the token in the ACK or NACK list.

[0105] In addition, network devices can broadcast retransmission instructions, enabling terminal devices to retransmit according to these instructions. Furthermore, network devices can determine the congestion level of the first resource pool based on the decoding results, and dynamically adjust the number of sub-resources and the allocation ratio of long and short signatures accordingly.

[0106] For the second resource pool, terminal devices can use tree coding to encode the data to be transmitted. The core of this method is to divide the message into blocks and then concatenate them according to the tree prefix verification rules. The integrity of the message is determined by forward verification dependency, avoiding decoding errors caused by interference from multiple terminals.

[0107] In some implementations, the terminal device can divide the data to be transmitted into multiple data blocks, and add a prefix checksum to each of these blocks, resulting in multiple sub-blocks. These sub-blocks are then transmitted at multiple time units. The prefix checksum in a sub-block has an association relationship with the data in adjacent sub-blocks, creating a tree-like constraint relationship between the sub-blocks. The network device can utilize this association relationship to concatenate multiple data blocks into a complete message. For example, the prefix checksum in the current data block may be generated based on the data blocks preceding it, or it may be generated based on the data blocks following it.

[0108] For example, a terminal device divides the data to be transmitted into data 1, data 2, data 3, and data 4. A checksum prefix is ​​added to data 1 (prefix check 1), to data 2 (prefix check 2), to data 3 (prefix check 3), and to data 4 (prefix check 4). Prefix check 2 is generated based on data 1, prefix check 3 is generated based on data 2, and prefix check 4 is generated based on data 3. Since there is no preceding data for data 1, prefix check 1 can be generated based on either data 1 or data 4.

[0109] The aforementioned time units can be time slots, or other time units such as sub-time slots, frames, or subframes. The terminal device transmits multiple sub-block representations in multiple time units, transmitting one sub-block in each time unit. These multiple time units can be adjacent or consecutive, facilitating data recovery by the network device.

[0110] For example, if a terminal device divides the data to be transmitted into B blocks and generates a prefix checksum corresponding to each of the B blocks, then combines each of the B blocks with one of the B prefix checksums to obtain B sub-blocks, the terminal device can transmit these B sub-blocks in B adjacent time slots, i.e., one sub-block per time slot. Here, B is greater than or equal to 2. The lengths of the B blocks can be equal. If the data to be transmitted is not divisible by B, the last block can be padded with zeros.

[0111] On the network side, after receiving sub-block signals superimposed from multiple terminals, network devices can recover the complete message from a massive number of candidate signals through tree path filtering. The core is to discard invalid paths by utilizing the constraint relationship of tree coding.

[0112] Network devices can perform sparse recovery of the observed signal in each time slot using either AMP or the Vector Message Passing Algorithm (VAMP) to obtain multiple sub-blocks and their corresponding confidence scores. A single time slot can contain multiple sub-blocks. A multi-way tree is constructed with the sub-block order (i.e., the order of the time slots containing the sub-blocks) as the tree hierarchy. For each cross-level path, each prefix checksum is verified to ensure it matches the previous sub-block. If a match is found, the path is retained; otherwise, it is discarded. By verifying the matching of sub-blocks at each level with those at the next level, paths where sub-blocks across different levels match can be filtered out.

[0113] In some implementations, to avoid computational overload caused by traversing all paths, network devices can dynamically adjust the bundle width using an adaptive bundle width strategy. For example, the bundle width is 5 under high load and 10 under low load. Each level retains only the K paths with the highest confidence that have passed verification, where K is the bundle width, and low-confidence paths are gradually eliminated. Finally, all paths that have passed verification are traversed, and the data chunks on those paths are concatenated into a complete message. Additionally, the network device can use CRC to verify the concatenated message; messages that pass verification can be included in the success set.

[0114] In some implementations, the network device can send third configuration information to the terminal device. This third configuration information is used to configure a candidate resource set, which includes a set of sub-resources that the terminal device is allowed to use. These sub-resources include REs or RBs. A sub-resource set includes a group of REs or RBs. The terminal device can select the corresponding resource set for each time unit and transmit the corresponding sub-blocks on that resource set. Taking a first time unit among multiple time units as an example, the first time unit can be any one of the multiple time units. The terminal device can randomly select a first resource set from the candidate resource set and transmit the corresponding sub-blocks within that first resource set. The resource sets selected by the terminal device for different time units can be the same or different.

[0115] In some implementations, terminal devices can randomly select resources (REs or RBs) from a time slot to transmit sub-blocks, thereby reducing the collision rate with other terminal devices. For example, terminal devices can use sparse mapping to map sub-blocks to REs or RBs in a time slot, enabling multiple terminals to share resources non-orthogonally. This reduces the probability of multiple terminals selecting the same resources to send data, thus reducing interference between multiple terminals and lowering the collision rate. The following explanation uses mapping sub-blocks to REs in a time slot as an example.

[0116] Network devices can configure candidate sparse support sets for terminal devices. The sparse support set can include a set of allowed RE locations, such as 10% of the REs in a certain BWP. The terminal device can randomly select a sparse support set for each sub-block and transmit signals on the REs corresponding to the sparse support set, while keeping the remaining REs empty to reduce interference between multiple terminals.

[0117] The aforementioned sparse support set can also be a spreading code (such as a pseudo-noise code, PN code). A spreading code corresponds to a set of allowed RE positions. The terminal device can randomly select a spreading code. Once the spreading code is selected, it is equivalent to determining the RE position.

[0118] The terminal device can randomly select a sparse support set or a spreading code based on coded compressed sensing (CCS) rules or non-orthogonal code access (NOCA) rules. Of course, other methods can also be used to select a sparse support set or a spreading code. This application does not specifically limit this method.

[0119] Through the above mapping process, the signal in a time slot becomes sparsity. Therefore, the terminal device can use compressed sensing to convert the data on the sub-block into a sparse signal and send it at the corresponding RE position.

[0120] Network devices can leverage the sparsity of signals to separate signals from multiple terminals and recover messages using AMP or VAMP algorithms. For example, network devices can use AMP or VAMP algorithms to obtain candidate signals for each observed signal in a time slot, and then use bundle constraint splicing and bundle search to combine the candidate signals across time slots into a complete message.

[0121] In some implementations, if the network device successfully decodes the message, it can send an ACK to the terminal device; if the network device fails to decode, it can send a NACK to the terminal device.

[0122] If the terminal device does not receive an ACK within the ACK window, it can re-access the network by changing resource pools according to the retry policy broadcast by the network device. For example, it can select resources from the first resource pool and increase its transmit power to re-access; or the terminal device can still select resources from the second resource pool, but can change the random seed or add redundancy before retransmitting the data. If the terminal device reaches the maximum number of retries, or if the cell broadcast channel is congested, it will fall back to the third resource pool and use the resources in the third resource pool for random access.

[0123] In some implementations, both the first and second resource pools have corresponding access conditions. A terminal device can only use resources from either the first or second resource pool if these conditions are met. For example, the access condition corresponding to the first resource pool might be a first condition (or the condition for random access using the first resource pool might be the first condition), and the access condition corresponding to the second resource pool might be a second condition (or the condition for random access using the second resource pool might be the second condition). The terminal device can use resources from the first resource pool to send data if the first condition is met; and it can use resources from the second resource pool to send data if the second condition is met.

[0124] In some implementations, the second resource pool has a higher priority than the first resource pool. Terminal devices can preferentially use resources from the second resource pool; that is, if the second condition is met, the terminal device uses resources from the second resource pool for access. If the second condition is not met but the first condition is met, then resources from the first resource pool are used.

[0125] The terminal device can first determine whether the second condition is met. If the second condition is met, it can use the resources in the second resource pool to access the network. If the second condition is not met, it can then determine whether the first condition is met. If the first condition is met, it can use the resources in the first resource pool to access the network. If the first condition is not met, it can use the resources in the third resource pool (described below) to access the network.

[0126] In some implementations, the second condition includes: the data to be transmitted supports segmentation, and / or the length of the data to be transmitted is less than or equal to the first threshold.

[0127] In some implementations, the first condition includes one or more of the following: the length of the data to be transmitted is less than or equal to a second threshold, the transmission delay of the data to be transmitted is less than or equal to a third threshold, and the network device allows the terminal device to access the network without authorization.

[0128] In some implementations, the first threshold is less than the second threshold.

[0129] In some implementations, the second condition includes the first condition. That is, the second condition includes one or more of the following: the data to be transmitted supports segmentation; the length of the data to be transmitted is less than or equal to a first threshold; the length of the data to be transmitted is less than or equal to a second threshold; the transmission delay of the data to be transmitted is less than or equal to a third threshold; and the network device allows unauthorized access by the terminal device.

[0130] In some implementations, the first configuration information can also be used to configure a third resource pool, which is used by terminal devices to access network devices by sending Msg1.

[0131] As an example, a terminal device can utilize resources in a third resource pool to perform a four-step random access process, such as... Figure 2 The process is shown below.

[0132] As another example, a terminal device can use resources in the third resource pool to send Msg1. After authorization from the network device, it can directly send data to the network device, eliminating the need for Msg3 and Msg4, thus reducing signaling overhead. This data transmission method is also known as EDT transmission. For example, the terminal device can select the second resource from the third resource pool and send Msg1 on the second resource; if the network device allows the terminal device to access, the network device can send an uplink authorization to the terminal device, which can then use this uplink authorization to send data.

[0133] In some implementations, the terminal device can utilize resources from a third resource pool to perform lightweight random access. In other words, the Msg1 sent by the terminal device uses a short PRACH structure, including a short preamble, to reduce transmission overhead. The preamble can occupy less than one subframe; for example, it can occupy one or two OFDM symbols.

[0134] In some implementations, Msg1 may also include a small load, or Msg1 may include a load whose size is less than or equal to the fourth threshold.

[0135] In some implementations, lightweight random access can refer to the terminal device using a short PRACH for random access. The short PRACH structure includes a short preamble (e.g., 1-2 OFDM symbols) + micro-payload (e.g., 8-64 bits) + DMRS. The micro-payload can carry one or more of the following information: access level, URLLC identifier, small packet redirection indicator, and CRC. The small packet redirection indicator includes a signature or codebook ID. The terminal device can use a ZC root sequence or a Gold root sequence, and power control can employ open-loop power with power ramping based on the magnitude of Δ.

[0136] There are two ways for a terminal device to send Msg1: one is that Msg1 does not contain any data, and the other is that Msg1 can carry a small amount of data. These two methods are described below.

[0137] In some implementations, the terminal device sends Msg1 to the network device, which includes a short preamble and a small payload. Upon receiving Msg1, the network device can send an uplink grant to the terminal device. This uplink grant has a small resource size and can also be called a short grant. After receiving the uplink grant, the terminal device can send small data packets on top of it. The size of these data packets is less than or equal to a preset threshold. This method eliminates the need for transmitting Msg3 and Msg4.

[0138] In some implementations, the terminal device sends Msg1 to the network device. Msg1 includes a short preamble but no payload. Upon receiving Msg1, the network device can send an uplink grant to the terminal device, which then transmits data on that grant. Alternatively, the network device can reserve PUSCH resources for the terminal device to use for data transmission.

[0139] The uplink authorization time slot sent by the network device to the terminal device can be adjacent to the time slot in which the terminal device sends Msg1, or the time slot of the PUSCH resource reserved by the network device can be adjacent to the time slot in which the terminal device sends Msg1, so that the terminal device can transmit data as quickly as possible and reduce data transmission latency.

[0140] In some implementations, the network device can configure one or more of the following parameters to the terminal device in explicit mode: PRB_bitmap, T_ms, DMRS, MCS, PUSCH_P0, Δ. Alternatively, the network device can send one or more of the following parameters in hash mode: N_res, T_ms, hash seed, hash rule. Here, PRB_bitmap is the physical resource block mask (such as frequency domain location or size) configured by the network device for the terminal device; T_ms is the minimum sub-slot length, in the number of OFDM symbols or sub-slots; DMRS is the reference signal configuration used by the terminal device when transmitting data, including one or more of port, pattern, and symbol position information; MCS is used to control rate and robustness; PUSCH_P0 is the open-loop power reference for PUSCH; Δ is the licensed additional bias or power ramp step size, in dB; the initial transmit power of the terminal device can be P0+Δ, and ramps up according to the magnitude of Δ. N_res represents the number of available sub-resources within the window; seed is used by the terminal device for resource mapping; the hash rule is the rule for calculating the resource index based on the Token or seed. The Token is a random token reported by the terminal device in PRACH, used to bind authorization, uplink transmission, and ACK alignment. The Token can be generated by the terminal device.

[0141] The formula for calculating the resource index is: ResIdx = Hash(Token, seed) mod N_res.

[0142] In some implementations, the Msg1 sent by the terminal device may carry one or more of the following information: EDT identifier, data length indicator, QoS level, and token. After sending Msg1, if the terminal device receives an uplink grant, it can send an uplink small data packet after the start time (t_start) of the uplink grant has arrived. This uplink data packet may include a token and a CRC (e.g., Token||CRC), where Token||CRC means concatenating the token and CRC bits in sequence as a payload.

[0143] The terminal device can receive ACK or NACK sent by the network device within the receive window. These ACKs and NACKs are short ACKs and short NACKs, and include the token carried in the uplink data. If the terminal device receives a NACK, it can retransmit the uplink data after power ramping. The window in which the retransmitted uplink data is received can be the same as or different from the window in which the previous uplink data was received. If the number of retransmissions reaches a preset limit, a fallback will occur.

[0144] On the network side, network devices can perform Msg1 detection and parse the micro-payload within Msg1 to determine whether to allow terminal device access. If the network device allows terminal device access, it can send the corresponding parameters according to the display mode or hash mode described above. Additionally, the network device can detect uplink data within the receive window and associate the uplink data with a token (Mini-PUSCH). The network device can parse the uplink data and, based on the parsing result, send HARQ feedback to the terminal device, i.e., send ACK or NACK. If the network device sends NACK to the terminal device, it can also send a retransmission instruction, allowing the terminal device to retransmit according to the instruction.

[0145] In some implementations, network devices can also collect statistics on one or more of the following parameters: window utilization, collision rate, BLER, and transmission latency, and feed these statistics back to the AI ​​controller so that the AI ​​controller can adjust the parameters during the access process.

[0146] For example, if the network device detects that the URLLC tail latency exceeds a preset threshold, or that the computing power or graphics processing unit (GPU) usage is too high, the AI ​​controller can increase the proportion of the third resource pool, increase the number of preambles, reduce the EDT transmission enable rate, and trigger a fallback strategy. The fallback strategy is to use the traditional four-step random access procedure for access.

[0147] In some implementations, network devices can leverage AI to predict and dynamically configure random access from a third resource pool, thereby achieving guaranteed access and simplified random access. Guaranteed access can, for example, ensure the access needs of both URLLC scenarios and traditional terminal devices. In some implementations, for terminal devices in URLLC scenarios, resources from the third resource pool can be prioritized for access.

[0148] As an example, network devices can predict the access arrival rate and congestion level of a third resource pool based on the first information. This first information can be information within a first window, which is a time period preceding the current time. For example, the first window could be a window adjacent to the current time, or it could be a historical window. The access arrival rate can refer to the number of terminal devices initiating access requests per unit of time.

[0149] The first information includes one or more of the following: PRACH arrivals, access success rate, access conflict rate, number of terminal devices waiting for access, capacity of the first resource pool, capacity of the second resource pool, processor utilization, and tail latency.

[0150] The number of preambles received by a network device can be considered as the number of preambles received. Access success rate refers to the ratio of the number of successfully accessed terminal devices to the total number of terminal devices attempting random access. Access collision rate refers to the ratio of the number of failed accessed terminal devices to the total number of terminal devices attempting random access; alternatively, it refers to the probability that a terminal device will encounter a collision while using resources from the target resource pool. The number of terminal devices waiting for access can also be referred to as the random access queue length. The capacity of the first resource pool is related to its size; a larger first resource pool has a stronger capacity. The capacity of the second resource pool is related to its size; a larger second resource pool has a stronger capacity. Processor utilization refers to the processor usage of the network device in processing random access from terminal devices; here, the processor can be a GPU. Tail latency refers to the access latency of the terminal device with the longest access time over a given period.

[0151] Network devices can predict the access arrival rate and / or congestion level in the second window based on the first information in the first window. The second window is the window after the current time.

[0152] The prediction models used by network devices can be one or more of the following: autoregressive integrated moving average (ARIMA) model, long short-term memory (LSTM) network, temporal fusion transformer (TFT), reinforcement learning model, etc.

[0153] In some implementations, the network device may send fifth configuration information to the terminal device based on the predicted access arrival rate and / or congestion level. This fifth configuration information is used to configure PRACH parameters. The PRACH parameters include one or more of the following: root sequence, cyclic shift number, time-domain position of the PRACH resource, and period of the PRACH resource.

[0154] In some implementations, the network device can determine a second parameter related to the third resource pool based on the access arrival rate and / or congestion level of the third resource pool. The second parameter includes one or more of the following: window length for random access, HARQ list window length, maximum number of retransmissions, power ramp step size, and probability of random access by the terminal device.

[0155] The window length for random access refers to the length of the window within which a terminal device can use resources from the third resource pool for lightweight random access. The HARQ list can include an ACK list and / or a NACK list; the probability of a terminal device experiencing random access can be used to indicate within which window the terminal device checks the HARQ list. The maximum number of retransmissions indicates the upper limit of the number of retransmissions a terminal device can perform using resources from the third resource pool. The power ramp step size can refer to Δ mentioned above. The probability of a terminal device experiencing random access can refer to what percentage of terminal devices within the network device's coverage area will experience random access.

[0156] In some implementations, network devices can directly predict PRACH parameters and / or second parameters based on the first information. For example, the network device can input the first information into an AI model to obtain the PRACH parameters and / or second parameters.

[0157] The parameter adjustments made to the network devices mentioned above can be performed at the cell level, beam level, BWP level, or network slice level, and can be cascaded or superimposed between different levels.

[0158] In some implementations, network devices can use ALOHA's formula to calculate the number of preambles that satisfy the target conflict constraint. The target conflict constraint is... P is the predicted conflict rate. This is the conflict rate threshold. If... A value of 1% indicates that the conflict rate needs to be less than or equal to 1%.

[0159] Let G=γ / K, S=Ge -G The target load G that satisfies the target conflict constraint can be obtained. * Then based on The number of preambles can be determined. Here, K represents the number of preambles, G represents the load (the ratio of the number of access requests to the number of preambles), γ represents the access arrival rate or the number of access requests, and S represents the throughput.

[0160] The formula for calculating the conflict rate is approximately: P = 1 - e -G (1+G).

[0161] In some implementations, network devices can set a minimum time slot and priority threshold for latency-sensitive services, so that data for these services can be transmitted in a timely manner.

[0162] In some implementations, network devices can be configured with long and short preambles. Short preambles are characterized by low latency and are suitable for cells with smaller radii, such as densely populated urban areas or indoor environments. Long preambles are suitable for scenarios with large coverage, rural areas, macro base station edges, high-frequency offsets, and high-speed mobile applications. Network devices can configure coverage or speed thresholds for terminal devices. If a terminal device meets one or both thresholds, it can choose a long preamble; otherwise, it chooses a short preamble.

[0163] In some implementations, network devices can configure root sequence and cyclic shift number for terminal devices based on access arrival rate and / or congestion level.

[0164] The cyclic shift number is determined based on the transmission delay and guard interval. The cyclic shift number must be greater than the associated main lobe broadening caused by the transmission delay and guard interval. The calculation formula is as follows: Where δ represents the cyclic shift number; τ max Indicates transmission delay, such as the maximum effective delay spread of the uplink channel, which is the last multipath or propagation delay (including timing margin) that the network device can perceive within the same uplink access opportunity; τ guard Indicates the guard interval, such as absorbing the spread caused by carrier frequency offset (CFO) or timing errors; f s Indicates the sampling frequency.

[0165] τ max and τ guardThis determines how wide the main lobe of the preamble will be stretched, thus affecting the size of the cyclic shift interval, in order to avoid the superposition of correlation peaks of different preambles at the receiver.

[0166] The number of root sequences can be determined using the following formula: And K = Nroot·S.

[0167] Where Nroot represents the number of root sequences, S represents the number of preambles that a single root sequence can provide, K represents the number of preambles that the network device needs to configure, and L... ZC δ represents the length of the preamble, and δ represents the number of cyclic shifts.

[0168] In some implementations, network devices can configure different root sequence sets for terminal devices in different coverage layers or different TA intervals. Furthermore, when configuring root sequence sets, coprime roots or roots with low cross-correlation can be assigned to different sets; that is, coprime roots or roots with low cross-correlation are preferentially assigned to terminal devices in different coverage layers or different TA intervals to reduce near-far effect conflicts.

[0169] In some implementations, network devices can dynamically adjust the number of cyclic shifts and root sequences based on the size of the cell coverage area. This process can be implemented using AI, meaning an AI model can be deployed on the network device to dynamically adjust the number of cyclic shifts and root sequences based on the size of the cell coverage area.

[0170] In some implementations, network devices can configure the time-domain location of PRACH resources for terminal devices. The network device can set the time-domain location of PRACH resources at a point with a high access arrival rate, based on the access arrival rate, to ensure a higher access success rate for terminal devices. In other implementations, transmission resources can be allocated at times before the peak access arrival rate to ensure uniform coverage and reduce the waiting time for terminal devices.

[0171] In some implementations, network devices can configure the PRACH resource period for terminal devices. If the average arrival rate of terminal devices increases, the PRACH resource period can be shortened to ensure the access success rate of terminal devices; if the average arrival rate of terminal devices decreases, the PRACH resource period can be increased to reduce resource waste and improve resource utilization.

[0172] For latency-sensitive services, such as URLLC, a higher priority can be assigned to ensure priority transmission of their data. For example, dedicated PRACH opportunities can be allocated for URLLC services within each window or frame, such as a separate root, a smaller cyclic shift, or a larger Ki. For non-latency-sensitive services Where Kfree is the non-guaranteed available leading number, βi is the service weight, the base station broadcasts pi, and the terminal device participates in the current RACH with probability pi; when the URLCC tail delay is observed to be critical or the conflict increases, pi is reduced, or the terminal device is directly redirected to use the first resource pool or the second resource pool.

[0173] In some implementations, if the terminal device retransmits data using the first or second resource pool a predetermined number of times, the terminal device can fall back to the third resource pool, i.e., use the resources in the third resource pool for random access, in order to avoid affecting the data transmission latency. The predetermined number of times corresponding to the first resource pool and the predetermined number of times corresponding to the second resource pool can be the same or different; this application embodiment does not specifically limit this.

[0174] In some implementations, the network device can send configuration information to the terminal device, which is used to configure a preset number of times.

[0175] In some implementations, the network device can adjust the size of the target resource pool based on the following information: access success rate, average access latency, power consumption, processor utilization, overload factor baseline, and backoff trigger frequency. The target resource pool can be any one of a first resource pool, a second resource pool, and a third resource pool. The network device can send fourth configuration information to the terminal device, which is used to configure the adjusted size of the target resource pool.

[0176] Access success rate refers to the probability that a terminal device successfully accesses the network using resources from the target resource pool. Average access latency refers to the average latency required for a terminal device to successfully access the network using resources from the target resource pool. Power consumption is the power consumption of the network device over a period of time. Processor utilization refers to the processor usage of the network device when processing random access from terminal devices; the processor here can be a GPU. Overload factor baseline is a benchmark for processor utilization, used to measure processor usage; for example, the overload factor baseline could be 90% of the processor's processing capacity. For instance, if the processor utilization remains above 90% for a period of time, or if the number of times the processor utilization reaches 90% or above reaches a preset number, the network device needs to adjust the size of the target resource pool, such as increasing its size. Fallback trigger frequency refers to the number of times a terminal device fails to access the network using resources from the target resource pool and falls back to another resource pool for access.

[0177] As mentioned earlier, terminal devices can obtain system messages by detecting SSBs. These system messages can include RACH configuration information, allowing the terminal device to perform random access based on the RACH configuration. For SSB detection, terminal devices typically scan in steps to detect SSBs.

[0178] In some implementations, embodiments of this application can narrow the instantaneous occupied bandwidth of the SSB, allowing the grating step size to increase. The terminal device only needs to scan sparser frequency points and fill in the frequency points through fine-grained indications within the frame or SSB, thereby reducing the overall number of scans and reducing the power consumption of the terminal device.

[0179] Traditional SSBs occupy a bandwidth of 240 subcarriers. In this embodiment, the subcarriers occupied by the SSB can be sparsified according to a certain scaling factor Q, where Q is greater than or equal to 1. For example, the value of Q can be 2 or 4. If Q is 2, the number of subcarriers occupied by the sparsified SSB is 120, equivalent to 10 RBs; if Q is 4, the number of subcarriers occupied by the sparsified SSB is 60, equivalent to 5 RBs. In this way, the bandwidth occupied by a single SSB transmission is narrowed, and the frequency search step size of the terminal device can be proportionally increased, thereby reducing the number of grid points.

[0180] In some implementations, the network device can send sixth configuration information to the terminal device. This sixth configuration information can be used to configure a first scaling factor. The first scaling factor is the scaling ratio of the subcarriers occupied by the SSB, and it is greater than or equal to 1. This first scaling factor is the scaling factor Q mentioned above. The number of subcarriers currently occupied by the SSB is the ratio of 240 to the first scaling factor. If the scaling factor is 1, it indicates that the traditional SSB detection method is used, meaning the SSB occupies 240 subcarriers.

[0181] In some implementations, the sixth configuration information can be used to configure a second scaling factor, which is the partial bandwidth ratio (PBR) of the SSB, and the second scaling factor is less than or equal to 1. The second scaling factor matches the first scaling factor, and its value can be, for example, 1, 0.5, or 0.25. For instance, when the first scaling factor is 1, the second scaling factor can also be 1; when the first scaling factor is 2, the second scaling factor can be 0.5; and when the first scaling factor is 4, the second scaling factor can be 0.25.

[0182] In some implementations, the sixth configuration information can be used to configure the number of times the SSB is repeated. This number of repetitions can be, for example, 1 or 2. If the fifth configuration information configures the number of SSB repetitions to 2, it means that the SSB is transmitted twice within a half-frame to ensure the reliability of the PBCH. Of course, this number of repetitions can also be other values, and this application embodiment does not specifically limit this.

[0183] In some implementations, the number of repetitions of the SSB can be replaced by the number of repetitions of the PBCH. That is, the network device can only retransmit the PBCH in the SSB without retransmitting other signals in the SSB (such as PSS, SSS and DMRS), which can reduce the cell load.

[0184] In some implementations, the sixth configuration information can be used to configure the PBCH rate adjustment strategy to indicate the level of the PBCH retransmission strategy. For example, the strategy is to enable PBCH retransmission when the cell load is low, and to disable PBCH retransmission when the cell load is high. That is, when the cell load is low, SSBs can be retransmitted according to the above-mentioned number of SSB retransmissions; when the cell load is high, SSBs are only transmitted once within a half-frame.

[0185] In some implementations, the SSB signal (PSS, SSS, PBCH, and DMRS) can still be mapped onto the “mother grid” of 240 subcarriers in the traditional way, but only one subcarrier per Q subcarrier is activated, while the rest remain empty. In this way, the bandwidth occupied by the SSB can be narrowed proportionally by Q.

[0186] In some implementations, the sequences of PSS and SSS signals can remain unchanged, that is, consistent with the sequences of traditional PSS and SSS signals, and a frequency domain spreading method is adopted. The terminal device uses the aforementioned first scaling factor for detection during matched filtering.

[0187] In some implementations, the PBCH can remain unchanged while the DMRS remains constant, and the terminal device can perform sparse sampling according to the first scaling factor mentioned above. In some implementations, the network device can compensate for the attenuation of the PBCH signal by repeatedly transmitting the PBCH in the time domain.

[0188] In some implementations, the terminal device can perform a coarse search for SSBs using an amplified step size. Once a candidate SSB frequency is found, the terminal device can perform fine frequency offset tracking or traditional CFO estimation near that candidate frequency to obtain the accurate SSB frequency location. Because the number of grating points searched is reduced according to a first scaling factor, the network search energy consumption and search latency of the terminal device are significantly reduced. On the network side, the frequency domain energy of a single SSB transmission is "sparser," and the reliability of the PBCH may decrease under weak coverage. This application embodiment can compensate for this by increasing the number of PBCH repetitions, or by using a lower MCS or increasing the transmission power.

[0189] The accurate frequency point of the SSB is determined by the terminal device through frequency offset tracking. In some implementations, the network device can also send some indication information to the terminal device, so that the terminal device can determine the accurate frequency point of the SSB based on the indication information. This method is described below.

[0190] In some implementations, the network device can also send first indication information and / or CFO compensation information to the terminal device. The first indication information indicates the offset of the SSB frequency point. After obtaining the coarse frequency point position of the SSB through scanning, the terminal device can determine the accurate frequency point of the SSB based on the offset. The CFO compensation information is used by the terminal device to adjust the oscillator frequency; CFO compensation is applicable to the FR2 band. The first indication information can also be called a fine frequency bit indication.

[0191] In some implementations, network devices can add an additional synchronization assistance symbol (SAS) before and / or after the SSB symbol (occupying 4 symbols). This SAS carries a fine frequency index (FFI) and / or CFO compensation information. In this way, the network device can map the SSB onto a coarser grid, and the terminal device only needs to scan a small number of frequency points and jump directly to the precise frequency indicated by the FFI after reading it. Since the time-frequency resources occupied by the SAS (e.g., 1-2 symbols) are small, it will not have a significant impact on transmission overhead.

[0192] For example, a SAS can be added before the four SSB symbols. Alternatively, a SAS can be added after the four SSB symbols. Or, a SAS can be added both before and after the four SSB symbols.

[0193] In some implementations, the SAS can be carried in the MIB, or the SAS can be carried in the reserved bits of the PBCH.

[0194] In some implementations, the sixth configuration information can be used to configure the number of SAS (which can be represented by ssb-ExtraSym). The number of SAS can be 0, 1, or 2. If the number of SAS is 0, it means no additional SAS will be added; if the number of SAS is 1, it means one SAS will be added; if the number of SAS is 2, it means two SAS will be added.

[0195] Regarding the insertion position of the SAS, it can be inserted at any position of the SSB symbol, and this application does not specifically limit this. As an example, a SAS can be inserted before the 0th symbol of the SSB, and / or after the last symbol of the SSB.

[0196] In some implementations, the sixth configuration information can be used to configure the FFI occupancy bits, which can be, for example, 3 to 5 bits. The value of the FFI occupancy bits can be used by the terminal device to determine the subdivision index within the coarse grid. In some implementations, the number of FFI occupancy bits can be carried in the MIB, or the number of FFI occupancy bits can be carried in the reserved bits of the PBCH.

[0197] FFI can be used to indicate the index of a finer frequency point within a coarse grid. As mentioned earlier, after narrowing the instantaneous bandwidth of the SSB, the terminal device can only locate the coarse-grained frequency point position and cannot obtain the precise frequency point of the SSB. Therefore, the network device can send FFI to the terminal device so that the terminal device can locate the precise frequency point based on the FFI.

[0198] For example, if the coarse search step size is 60kHz, FFI occupies 3 bits, which can represent 8 subdivision frequency points, each with a compensation of 7.5kHz. If the value of FFI is 2, then the precise frequency point calculated by the terminal device is: 60 + 2 * 7.5 = 75kHz.

[0199] After successfully detecting the PSS or SSS, the terminal device parses the SAS based on its location to obtain the FFI and / or CFO. The precise frequency position can be located using the FFI, and then the PBCH is decoded. If the terminal device operates in the FR2 band, it can also extract the coarse CFO position information and adjust the local oscillator frequency according to the corresponding frequency offset range. This prevents large frequency offsets from disrupting the orthogonality of the OFDMA subcarriers, providing a stable carrier foundation for PBCH demodulation.

[0200] For PBCH decoding, the terminal device can decode the PBCH signal in the SSB according to the traditional PBCH decoding process. Since frequency point calibration is completed in the early stage through FFI and frequency offset step size is completed through CFO settings, the demodulation reference signal-to-noise ratio of PBCH can be improved. For FR2 scenarios, the demodulation failure rate of PBCH can also be improved.

[0201] For FR2s with a larger CFO, a coarser CFO level can be carried through FFI to further stabilize the PBCH. The grid can be further widened without sacrificing the bandwidth occupied by the PBCH. This solution is more suitable for weak coverage or high-speed CFOs.

[0202] In some implementations, the sixth configuration information can be used to configure the number of times the FFI is repeated, which can be, for example, 1 or 2. If the number of times the FFI is repeated is 1, it means that one FFI is sent for each SSB sent, that is, the FFI is not sent repeatedly; if the number of times the FFI is repeated is 2, it means that two FFIs are sent for each SSB sent, that is, the FFI is sent repeatedly.

[0203] In some implementations, the sixth configuration information can be used to configure the CRC checksum of the FFI to improve decision reliability. This CRC checksum can, for example, occupy 3 bits. Using this checksum, the terminal device can verify the correctness of the FFI information, avoiding PBCH demodulation failure due to incorrect calibration.

[0204] In some implementations, the sixth configuration information can also be used to configure the subcarrier or symbol pattern of the FFI, which can be interleaved with the DMRS to ensure a low peak-to-average power ratio (PAPR) and robustness.

[0205] In the above scheme, on the terminal side, the terminal device can obtain the first scaling factor and SAS level. For power-sensitive scenarios, the level can be assumed according to the operator's default strategy or obtained by reading neighbor cell information. The terminal device performs a coarse search, for example, scanning a small number of frequency points with a search step size of raster_step = step_legacy × ssb-Comb. Candidate signals for PSS and SSS are obtained through matched filtering. In addition, the terminal device can read the FFI and / or CRC on the SAS to obtain the fine frequency bit indication and the CFO coarse level. The precise frequency point is calculated based on the fine frequency bit indication, and the local oscillator is adjusted and the CFO is removed based on the CFO to lock onto the precise center of the SSB. After the above operations, the terminal device demodulates PBCH and / or DMRS. If the PBCH is repeated multiple times, the multiple received PBCHs can be merged and received. If demodulation fails, a retry is performed, such as trying adjacent fine frequency bits on the same coarse frequency point or trying on the next coarse frequency point. If the number of attempts reaches the upper limit, it falls back to the traditional random access procedure.

[0206] On the network side, network devices can broadcast a narrowband SSB + 1 FFI symbol to reduce the number of grids. Network devices can also broadcast a MIB, which can indicate the sb-Comb / ssb-ExtraSym / ffi-Bits / ffi-Rep / pbch-RateAdj level encoded in the reserved bits of the PBCH. Terminal devices can use default parameters during the initial search, switching to the parameter values ​​indicated by the network device after successful PBCH decoding. Network devices can set these parameters according to cell type. For example, for macrocells or cells with weak coverage, the SSB repetition count can be 2, and the PBCH rate can be a low-rate level; for dense hotspots or indoor scenarios, the first scaling factor can be 4, and PBCH repetition is unnecessary.

[0207] In some implementations, adjacent cells with the same frequency can be set with the same parameters to avoid repeated learning by the terminal device during inter-cell handover, thereby reducing the power consumption of the terminal device. For example, the search step size of co-frequency neighboring cells can be set to be the same as the first scaling factor.

[0208] In summary, the embodiments of this application can narrow the instantaneous bandwidth of SSB by sparsifying the national frequency domain, allowing terminal devices to perform coarse synchronization based on the amplified grid, or carry fine frequency bit indication or frequency offset indication through a small number of SAS, combining coarse search with fewer scan points and fine alignment into a complete process, or superimpose the above schemes, and significantly reduce the synchronization grid, reduce network search power consumption and latency without compromising NR compatibility.

[0209] It should be understood that Figures 1 to 3The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 3 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0210] The above text combined Figures 1 to 3 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 4 to 6 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0211] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0212] Figure 4 This is a schematic block diagram of a terminal device provided in an embodiment of this application. Figure 4 As shown, the terminal device 400 may include a receiving unit 410.

[0213] The receiving unit 410 is configured to: receive first configuration information from the network device, wherein the first configuration information is used to configure a first resource pool and / or a second resource pool, wherein the first resource pool is used by the terminal device to perform random access based on non-orthogonal signatures, and the second resource pool is used by the terminal device to perform unsigned random access.

[0214] In some implementations, the receiving unit 410 is further configured to: receive second configuration information from the network device, the second configuration information being used to configure a non-orthogonal signature set; the terminal device 400 further includes a processing unit and a sending unit, the processing unit being configured to randomly select a first signature from the non-orthogonal signature set, and select a first resource corresponding to the first signature from the first resource pool based on the mapping relationship between the signature and the resource; the sending unit is configured to: send data on the first resource.

[0215] In some implementations, the non-orthogonal signature set is a multi-resolution signature set, wherein the signatures in the multi-resolution signature set correspond to at least two dimensions of information: time domain, frequency domain, spatial domain, and code domain.

[0216] In some implementations, the second configuration information is used to configure multiple sets of multi-resolution signature sets, wherein one set of multi-resolution signature sets corresponds to a BWP and / or a subcarrier.

[0217] In some implementations, the terminal device further includes a processing unit and a transmission unit. The processing unit is configured to: divide the data to be transmitted into multiple data blocks, and add a prefix checksum to each of the multiple data blocks to obtain multiple sub-blocks, wherein the prefix checksum in the current data block is generated based on the data blocks preceding the current data block. The transmission unit is configured to: transmit the multiple sub-blocks at multiple time units respectively.

[0218] In some implementations, the receiving unit is further configured to: receive third configuration information from the network device, the third configuration information being used to configure a candidate resource set, the candidate resource set including a set of sub-resources allowed for use by the terminal device, the sub-resources including REs or RBs; the terminal device further includes a processing unit and a transmission unit, the processing unit being configured to: randomly select a first resource set from the candidate resource set for a first time unit among the plurality of time units, the first time unit being any one of the plurality of time units; the transmission unit being configured to: transmit a corresponding sub-block within the first resource set in the first time unit.

[0219] In some implementations, the condition for using the first resource pool for random access is a first condition, and the condition for using the second resource pool for random access is a second condition; the terminal device further includes a processing unit, configured to: use resources in the second resource pool for access at any time when the second condition is met; and use resources in the first resource pool for random access when the second condition is not met but the first condition is met.

[0220] In some implementations, the first condition includes: the data to be transmitted supports segmentation, and / or the length of the data to be transmitted is less than or equal to a first threshold; the second condition includes one or more of the following: the length of the data to be transmitted is less than or equal to a second threshold, the transmission delay of the data to be transmitted is less than or equal to a third threshold, and the network device allows the terminal device to perform unlicensed random access.

[0221] In some implementations, the first configuration information is also used to configure a third resource pool, which is used by the terminal device to access the network device by sending Msg1.

[0222] In some implementations, the receiving unit is further configured to: receive fourth configuration information from the network device, the fourth configuration information being used to configure the size of the adjusted target resource pool, the target resource pool including one or more of the first resource pool, the second resource pool, and the third resource pool, the fourth configuration information being determined based on one or more of the following information of the target resource pool: access success rate, average access latency, power consumption, processor utilization, overload factor baseline, and fallback trigger frequency.

[0223] In some implementations, the receiving unit is further configured to: receive fifth configuration information from the network device, the fifth configuration information being used to configure PRACH parameters, the PRACH parameters being determined based on the access arrival rate and / or congestion level of the third resource pool predicted by the network device, the access arrival rate and / or congestion level of the third resource pool being predicted based on first information, the first information including one or more of the following: PRACH arrivals, access success rate, access conflict rate, number of terminal devices waiting for access, carrying capacity of the first resource pool, carrying capacity of the second resource pool, processor utilization, and tail latency.

[0224] In some implementations, the PRACH parameters include one or more of the following: root sequence, cyclic shift number, time-domain position of the PRACH resource, and period of the PRACH resource.

[0225] In some implementations, Msg1 includes a preamble, which occupies a time length of one or two OFDM symbols.

[0226] In some implementations, Msg1 also includes a load whose size is less than or equal to a fourth threshold.

[0227] In some implementations, the terminal device further includes a processing unit and a sending unit: the processing unit is configured to: select a second resource from the third resource pool; the sending unit is configured to: send Msg1 on the second resource; the receiving unit 410 is further configured to: receive an uplink grant from the network device; the sending unit is further configured to: send data using the uplink grant.

[0228] In some implementations, the terminal device further includes a processing unit, which is configured to: if the number of retransmissions using the first resource pool or the second resource pool reaches a preset number, then use resources in the third resource pool for random access.

[0229] In some implementations, the receiving unit is further configured to: receive sixth configuration information from the network device, the sixth configuration information being used to configure a first scaling factor, the first scaling factor being the scaling ratio of the subcarrier occupied by the SSB; the terminal device further includes a processing unit configured to: determine the scanning step size of the SSB according to the first scaling factor; and scan the SSB according to the scanning step size.

[0230] In some implementations, the receiving unit is further configured to: receive first indication information and / or CFO compensation information from the network device, wherein the first indication information is used to indicate the offset of the SSB frequency point, and the CFO compensation information is used by the terminal device to adjust the frequency of the oscillator.

[0231] The aforementioned communication units (such as receiving units, sending units, and transmitting units) can implement corresponding communication functions. These communication functions can be internal communication functions of the terminal device 400 or communication functions between the terminal device 400 and other devices. Optionally, the communication unit can also be referred to as a communication interface or transceiver module.

[0232] Figure 5 This is a schematic block diagram of a network device provided in an embodiment of this application. Figure 5 As shown, the network device 500 may include a transmitting unit 510.

[0233] The sending unit 510 is configured to: send first configuration information to the terminal device, wherein the first configuration information is used to configure a first resource pool and / or a second resource pool, wherein the first resource pool is used by the terminal device for random access based on non-orthogonal signatures, and the second resource pool is used by the terminal device for performing unidentified random access.

[0234] In some implementations, the sending unit 510 is further configured to: send second configuration information to the terminal device, the second configuration information being used to configure a non-orthogonal signature set; the network device 500 further includes a receiving unit configured to receive data from the terminal device on a first resource in the first resource pool; wherein the first resource is determined by the terminal device based on a first signature and the mapping relationship between the signature and the resource, and the first signature is randomly selected by the terminal device.

[0235] In some implementations, the non-orthogonal signature set is a multi-resolution signature set, wherein the signatures in the multi-resolution signature set correspond to at least two dimensions of information: time domain, frequency domain, spatial domain, and code domain.

[0236] In some implementations, the second configuration information is used to configure multiple sets of multi-resolution signature sets, wherein one set of multi-resolution signature sets corresponds to a BWP and / or a subcarrier.

[0237] In some implementations, the network device 500 further includes a processing unit, which is configured to: predict a first parameter related to the multi-resolution signature set based on second information, the first parameter including one or more of the following: code domain sparsity, maximum concurrency value, ratio between the multi-resolution signature set and the single-resolution signature set, the second configuration information including the first parameter; the second information including one or more of the following: resource utilization, access collision rate, BLER, tail latency, uplink load, downlink load, power ramp-up retransmission ratio.

[0238] In some implementations, the network device 500 further includes a receiving unit and a processing unit. The receiving unit is used to receive multiple sub-blocks from the terminal device at multiple time units, and the sub-blocks include block data and prefix checksums. The processing unit is used to concatenate the multiple sub-blocks into data according to the matching relationship between the prefix checksums and the block data of the multiple sub-blocks.

[0239] In some implementations, the sending unit 510 is further configured to: send third configuration information to the terminal device, the third configuration information being used to configure a candidate resource set, the candidate resource set including a set of sub-resources that the terminal device is allowed to use in a time unit, the sub-resources including REs or RBs.

[0240] In some implementations, the condition for using the first resource pool for random access is a first condition, which includes: the data to be transmitted supports segmentation, and / or the length of the data to be transmitted is less than or equal to a first threshold; the condition for using the second resource pool for random access is a second condition, which includes one or more of the following: the length of the data to be transmitted is less than or equal to a second threshold, the transmission delay of the data to be transmitted is less than or equal to a third threshold, and the network device allows the terminal device to perform unauthorized random access.

[0241] In some implementations, the first configuration information is also used to configure a third resource pool, which is used by the terminal device to access the network device by sending Msg1.

[0242] In some implementations, the sending unit is further configured to: send fourth configuration information to the terminal device, the fourth configuration information being used to configure the size of the adjusted target resource pool, the target resource pool including one or more of the first resource pool, the second resource pool, and the third resource pool, the fourth configuration information being determined based on one or more of the following information of the target resource pool: access success rate, average access latency, power consumption, processor utilization, overload factor baseline, and fallback trigger frequency.

[0243] In some implementations, the network device further includes a processing unit, which is configured to: predict the access arrival rate and / or congestion level of the third resource pool based on first information, and determine PRACH parameters based on the access arrival rate and / or congestion level of the third resource pool; the sending unit is configured to: send fifth configuration information to the terminal device, the fifth configuration information being used to configure the PRACH parameters; wherein, the first information includes one or more of the following: PRACH arrival rate, access success rate, access conflict rate, number of terminal devices waiting for access, carrying capacity of the first resource pool, carrying capacity of the second resource pool, processor utilization, tail delay, BLER, power ramp retransmission ratio, uplink load, and downlink load.

[0244] In some implementations, the PRACH parameters include one or more of the following: root sequence, cyclic shift number, time-domain position of the PRACH resource, and period of the PRACH resource.

[0245] In some implementations, the processing unit is further configured to: determine a second parameter related to the third resource pool based on the access arrival rate and / or congestion level of the third resource pool, the second parameter including one or more of the following: window length for random access, HARQ list window length, maximum number of retransmissions, power ramp step size, and probability of random access by the terminal device.

[0246] In some implementations, Msg1 includes a preamble, which occupies a time length of one or two OFDM symbols.

[0247] In some implementations, Msg1 also includes a load whose size is less than or equal to a fourth threshold.

[0248] In some implementations, the network device 500 further includes a receiving unit, which is configured to: receive Msg1 from the terminal device using the second resource in the third resource pool; the sending unit 510 is further configured to: send an uplink authorization to the terminal device in response to Msg1, the uplink authorization being used to carry uplink data.

[0249] In some implementations, the sending unit 510 is further configured to: send sixth configuration information to the terminal device, the sixth configuration information being used to configure a first scaling factor, the first scaling factor being the scaling ratio of the subcarrier occupied by the SSB, and the first scaling factor being used to determine the scanning step size of the SSB.

[0250] In some implementations, the transmitting unit 510 is further configured to: transmit first indication information and / or CFO compensation information to the terminal device, wherein the first indication information is used to indicate the offset of the SSB frequency point, and the CFO compensation information is used by the terminal device to adjust the frequency of the oscillator.

[0251] The aforementioned communication units (such as receiving units and transmitting units) can implement corresponding communication functions. These communication functions can be internal communication functions of the network device 500 or communication functions between the network device 500 and other devices. Optionally, the communication unit can also be referred to as a communication interface or transceiver module.

[0252] Figure 6 This is another schematic block diagram of the communication device 600 provided in the embodiments of this application. The communication device 600 may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. The communication device 600 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0253] like Figure 6 As shown, the communication device 600 may include one or more processors 610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 610 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 600 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0254] In an alternative design, the processor 610 may also store instructions and / or data that can be executed by the processor 610 to cause the communication device 600 to perform the methods described in the above method embodiments.

[0255] In another alternative design, the communication device 600 may include a communication interface 620 for implementing receiving and transmitting functions. For example, the communication interface 620 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0256] Optionally, the communication device 600 may include one or more memories 630, which may store instructions that can be executed on the processor 610, causing the communication device 600 to perform the methods described in the above method embodiments. Optionally, the memories 630 may also store data. Optionally, the processor 610 may also store instructions and / or data. The processor 610 and the memories 630 may be provided separately or integrated together.

[0257] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0258] In one implementation, the communication device 600 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0259] In another implementation, the communication device 600 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0260] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0261] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as 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 linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0262] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0263] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0264] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0265] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0266] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0267] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0268] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0269] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

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

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

[0272] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A wireless communication method, characterized in that, include: The network device receives first configuration information, which is used to configure a first resource pool and / or a second resource pool. The first resource pool is used for the terminal device to perform random access based on non-orthogonal signatures, and the second resource pool is used for the terminal device to perform unsigned random access.

2. The method according to claim 1, characterized in that, The method further includes: Receive second configuration information from the network device, the second configuration information being used to configure a non-orthogonal signature set; Randomly select a first signature from the non-orthogonal signature set; Based on the mapping relationship between signatures and resources, select the first resource corresponding to the first signature from the first resource pool; Send data on the first resource.

3. The method according to claim 2, characterized in that, The non-orthogonal signature set is a multi-resolution signature set, and the signatures in the multi-resolution signature set correspond to at least two dimensions of information: time domain, frequency domain, spatial domain, and code domain.

4. The method according to claim 3, characterized in that, The second configuration information is used to configure multiple sets of multi-resolution signature sets, wherein one set of multi-resolution signature sets corresponds to a bandwidth portion (BWP) and / or a subcarrier.

5. The method according to claim 1, characterized in that, The method further includes: The data to be transmitted is divided into multiple data chunks; A prefix check is added to each of the multiple data blocks to obtain multiple sub-blocks, wherein the prefix check in the current data block is generated based on the data blocks preceding the current data block; The multiple sub-blocks are transmitted separately on multiple time units.

6. The method according to claim 5, characterized in that, The method further includes: The network device receives third configuration information, which is used to configure a candidate resource set. The candidate resource set includes a set of sub-resources that the terminal device is allowed to use. The sub-resources include resource elements (RE) or resource blocks (RB). For a first time unit among the plurality of time units, a first resource set is randomly selected from the candidate resource set, wherein the first time unit is any one of the plurality of time units; The first resource is transmitted in the first time unit, corresponding to the sub-block.

7. The method according to any one of claims 1-6, characterized in that, The condition for using the first resource pool for random access is the first condition, and the condition for using the second resource pool for random access is the second condition; the method further includes: If the second condition is met, resources in the second resource pool can be used for access at any time. If the second condition is not met but the first condition is met, random access is performed using resources from the first resource pool.

8. The method according to claim 7, characterized in that, The first condition includes: the data to be transmitted supports segmentation, and / or the length of the data to be transmitted is less than or equal to a first threshold; The second condition includes one or more of the following: the length of the data to be transmitted is less than or equal to a second threshold, the transmission delay of the data to be transmitted is less than or equal to a third threshold, and the network device allows the terminal device to perform unauthorized random access.

9. The method according to any one of claims 1-8, characterized in that, The first configuration information is also used to configure a third resource pool, which is used by the terminal device to access the network device by sending message Msg1.

10. The method according to claim 9, characterized in that, The method further includes: The network device receives fourth configuration information, which is used to configure the size of the adjusted target resource pool. The target resource pool includes one or more of the first resource pool, the second resource pool, and the third resource pool. The fourth configuration information is determined based on one or more of the following information of the target resource pool: access success rate, average access latency, power consumption, processor utilization, overload factor baseline, and fallback trigger frequency.

11. The method according to claim 9 or 10, characterized in that, The method further includes: The network device receives fifth configuration information, which is used to configure Physical Random Access Channel (PRACH) parameters. The PRACH parameters are determined based on the access arrival rate and / or congestion level of the third resource pool predicted by the network device. The access arrival rate and / or congestion level of the third resource pool are predicted based on first information, which includes one or more of the following: PRACH arrivals, access success rate, access conflict rate, number of terminal devices waiting for access, capacity of the first resource pool, capacity of the second resource pool, processor utilization, tail latency, block error rate (BLER), power ramp retransmission ratio, uplink load, downlink load.

12. The method according to claim 11, characterized in that, The PRACH parameters include one or more of the following: root sequence, cyclic shift, time-domain position of the PRACH resource, and period of the PRACH resource.

13. The method according to claim 9 or 10, characterized in that, Msg1 includes a preamble, which occupies a time length of one or two Orthogonal Frequency Division Multiple Access (OFDM) symbols.

14. The method according to any one of claims 9-13, characterized in that, Msg1 also includes a load, the size of which is less than or equal to a fourth threshold.

15. The method according to any one of claims 9-14, characterized in that, The method further includes: Select a second resource from the third resource pool; Send Msg1 on the second resource; Receive uplink authorization from the network device; Data is sent using the aforementioned uplink authorization.

16. The method according to any one of claims 9-15, characterized in that, The method further includes: If the number of retransmissions using the first or second resource pool reaches a preset number, then resources from the third resource pool will be used for random access.

17. The method according to any one of claims 9-16, characterized in that, The method further includes: The network device receives sixth configuration information, which is used to configure a first scaling factor, wherein the first scaling factor is the scaling ratio of the subcarriers occupied by the synchronization signal / physical broadcast channel block (SSB). The scan step size of the SSB is determined based on the first scaling factor; The SSB is scanned according to the stated scan step size.

18. The method according to claim 17, characterized in that, The method further includes: The terminal device receives first indication information and / or carrier frequency offset (CFO) compensation information from the network device. The first indication information is used to indicate the offset of the SSB frequency point, and the CFO compensation information is used by the terminal device to adjust the frequency of the oscillator.

19. A wireless communication method, characterized in that, include: Send first configuration information to the terminal device. The first configuration information is used to configure a first resource pool and / or a second resource pool. The first resource pool is used by the terminal device to perform random access based on non-orthogonal signatures, and the second resource pool is used by the terminal device to perform unidentified random access.

20. The method according to claim 19, characterized in that, The method further includes: Send second configuration information to the terminal device, the second configuration information being used to configure a non-orthogonal signature set; Receive data from the terminal device on a first resource in the first resource pool; The first resource is determined by the terminal device based on the first signature and the mapping relationship between the signature and the resource, and the first signature is randomly selected by the terminal device.

21. The method according to claim 20, characterized in that, The non-orthogonal signature set is a multi-resolution signature set, and the signatures in the multi-resolution signature set correspond to at least two dimensions of information: time domain, frequency domain, spatial domain, and code domain.

22. The method according to claim 21, characterized in that, The second configuration information is used to configure multiple sets of multi-resolution signature sets, wherein one set of multi-resolution signature sets corresponds to a BWP and / or a subcarrier.

23. The method according to claim 21 or 22, characterized in that, The method further includes: Based on the second information, a first parameter related to the multi-resolution signature set is predicted. The first parameter includes one or more of the following: code domain sparsity, maximum concurrency value, and the ratio between the multi-resolution signature set and the single-resolution signature set. The second configuration information includes the first parameter. The second information includes one or more of the following: resource utilization, random access collision rate, block error rate (BLER), tail delay, uplink load, downlink load, and power ramp-up retransmission ratio.

24. The method according to any one of claims 19-23, characterized in that, The method further includes: Multiple sub-blocks from the terminal device are received at multiple time units, each sub-block including block data and prefix check; Based on the matching relationship between the prefix checksum of the multiple sub-blocks and the block data, the multiple sub-blocks are concatenated into data.

25. The method according to claim 24, characterized in that, The method further includes: Send third configuration information to the terminal device. The third configuration information is used to configure a candidate resource set. The candidate resource set includes a set of sub-resources that the terminal device is allowed to use in a time unit. The sub-resources include REs or RBs.

26. The method according to any one of claims 19-25, characterized in that, The condition for using the first resource pool for random access is the first condition, which includes: the data to be transmitted supports segmentation, and / or the length of the data to be transmitted is less than or equal to a first threshold. The condition for using the second resource pool for random access is the second condition, which includes one or more of the following: the length of the data to be transmitted is less than or equal to a second threshold, the transmission delay of the data to be transmitted is less than or equal to a third threshold, and the network device allows the terminal device to perform unauthorized random access.

27. The method according to any one of claims 19-26, characterized in that, The first configuration information is also used to configure a third resource pool, which is used by the terminal device to access the network device by sending Msg1.

28. The method according to claim 27, characterized in that, The method further includes: Send fourth configuration information to the terminal device. The fourth configuration information is used to configure the size of the adjusted target resource pool. The target resource pool includes one or more of the first resource pool, the second resource pool, and the third resource pool. The fourth configuration information is determined based on one or more of the following information of the target resource pool: access success rate, average access latency, power consumption, processor utilization, overload factor baseline, and fallback trigger frequency.

29. The method according to claim 27 or 28, characterized in that, The method further includes: Based on the first information, predict the access arrival rate and / or congestion level of the third resource pool; Based on the access arrival rate and / or congestion level of the third resource pool, determine the PRACH parameters; Send fifth configuration information to the terminal device, the fifth configuration information being used to configure PRACH parameters; The first information includes one or more of the following: Physical random access channel (PRACH) arrivals, access success rate, access collision rate, number of terminal devices waiting for access, carrying capacity of the first resource pool, carrying capacity of the second resource pool, processor utilization, tail delay, BLER, power ramp retransmission ratio, uplink load, downlink load.

30. The method according to claim 29, characterized in that, The PRACH parameters include one or more of the following: root sequence, cyclic shift, time-domain position of the PRACH resource, and period of the PRACH resource.

31. The method according to claim 29, characterized in that, The method further includes: Based on the access arrival rate and / or congestion level of the third resource pool, a second parameter related to the third resource pool is determined. The second parameter includes one or more of the following: window length for random access, window length for the Hybrid Automatic Repeat Request (HARQ) list, maximum number of retransmissions, power ramp step size, and probability of random access by the terminal device.

32. The method according to any one of claims 27-31, characterized in that, Msg1 includes a preamble, which occupies a time length of one or two Orthogonal Frequency Division Multiple Access (OFDM) symbols.

33. The method according to any one of claims 27-32, characterized in that, Msg1 also includes a load, the size of which is less than or equal to a fourth threshold.

34. The method according to any one of claims 27-33, characterized in that, The method further includes: The second resource in the third resource pool is used to receive Msg1 from the terminal device; In response to Msg1, an uplink authorization is sent to the terminal device, the uplink authorization being used to carry uplink data.

35. The method according to any one of claims 27-34, characterized in that, The method further includes: The sixth configuration information is sent to the terminal device. The sixth configuration information is used to configure a first scaling factor, which is the scaling factor of the subcarrier occupied by the SSB. The first scaling factor is used to determine the scanning step size of the SSB.

36. The method according to claim 35, characterized in that, The method further includes: Send a first indication message and / or CFO compensation message to the terminal device, wherein the first indication message is used to indicate the offset of the SSB frequency point, and the CFO compensation message is used by the terminal device to adjust the frequency of the oscillator.

37. A terminal device, characterized in that, include: A receiving unit is configured to receive first configuration information from a network device. The first configuration information is used to configure a first resource pool and / or a second resource pool. The first resource pool is used by the terminal device for random access based on non-orthogonal signatures, and the second resource pool is used by the terminal device for performing unsigned random access.

38. A network device, characterized in that, include: The sending unit is configured to send first configuration information to the terminal device. The first configuration information is used to configure a first resource pool and / or a second resource pool. The first resource pool is used by the terminal device for random access based on non-orthogonal signatures, and the second resource pool is used by the terminal device for performing unidentified random access.

39. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory is used to store a program, and the processor is used to invoke the program in the memory and control the transceiver to receive or send signals so that the terminal performs the method as described in any one of claims 1-18.

40. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 19-36.

41. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method as described in any one of claims 1-18 or 19-36.

42. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-18 or 19-36.

43. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-18 or 19-36.

44. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-18 or 19-36.

45. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-18 or 19-36.

Images