Communication method, apparatus, system, chip system, and computer readable storage medium

Abstract

The application provides a communication method, device, system, chip system and computer readable storage medium, which can be applied to an early sounding reference signal / channel state information reference signal frequency domain resource acquisition scene. In the method, in the process of establishing a connection between a terminal device and a cell, a target frequency domain template is determined from a locally stored frequency domain template set according to frequency domain template index information fed back by a network device through a system information block, then a target relative frequency domain resource index corresponding to an early sounding reference signal / channel state information reference signal is determined according to the target frequency domain template, and the frequency domain resource index is synchronized to the network device through a random access message MSG3. Thus, by using the system information block indication combined with the pre-defined template set in the random access stage, the terminal device can independently acquire the early frequency resource in the random access process, and the signaling overhead is low and the flexibility is high.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and in particular relates to a communication method, device, system, chip system and computer-readable storage medium. Background Technology

[0002] In mobile communication systems, such as 5G (new radioaccess technology) mobile communication systems, when a terminal device switches from an idle or inactive state to a connected state, due to the lack of prior channel measurement / reporting information (such as channel state information (CSI)), the network device can usually only use a degraded transmission scheme in downlink transmission. That is, it does not use closed-loop precoding on massive MIMO antenna arrays and uses a lower-level modulation and coding scheme (MCS), resulting in a significant decrease in instantaneous throughput after the handover.

[0003] To address the aforementioned issues, the 3rd Generation Partnership Project (3GPP) standard protocol Release-20 introduced the Early Sounding Reference Signal / Channel State Information Reference Signal (Early SRS / CSI-RS) mechanism. This mechanism aims to trigger channel measurements early in connection establishment, enabling network and terminal devices to acquire Channel State Information (CSI) as quickly as possible, perform link adaptation (using closed-loop precoding and high-level MCS), and complete accurate time-frequency tracking. This avoids the low throughput problem caused by degraded transmission schemes and quickly restores high-throughput transmission.

[0004] In related technologies, current standards explicitly trigger early SRS / CSI-RS through the medium access control-control element (MAC-CE) carried in the fourth message (MSG4) of the random access procedure. However, MAC-CE is a lightweight triggering signaling and cannot be used to carry complex resource allocation information. Furthermore, in existing NR procedures, SRS / CSI-RS resource configuration is configured through dedicated radio resource control (RRC) (i.e., the channel state information measurement configuration (CSI-MeasConfig) in the RRC reconfiguration message). Therefore, the first CSI acquisition or the first CSI-RS measurement can only be triggered after the terminal device successfully switches to connected state. Consequently, before the RRC connection is established, the terminal device cannot receive any terminal-specific RRC configurations (such as CSI-MeasConfig), thus preventing the terminal device from executing early SRS / CSI-RS. Therefore, how to obtain the frequency domain resource parameters required for early SRS / CSI-RS before the RRC connection is established becomes a pressing issue. Summary of the Invention

[0005] This application provides a communication method, apparatus, chip system, computer-readable storage medium, computer program product, and communication system that can solve the problem of how to obtain the frequency domain resource parameters required for early SRS / CSI-RS before the RRC connection is established.

[0006] In a first aspect, embodiments of this application provide a communication method. This method can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit this. The following description uses a terminal device as an example.

[0007] The method includes:

[0008] The system receives a target system information block (SIB) from the first cell, where the terminal device is in the process of establishing a connection with the first cell. The target SIB carries target frequency domain template index information. Based on the target frequency domain template index information, the system determines a target frequency domain template from a pre-stored set of frequency domain templates, where the set of frequency domain templates contains at least one frequency domain template, which is used to describe the determination rules of frequency domain resources. Based on the target frequency domain template, the system determines the target relative frequency domain resource index corresponding to the early SRS / CSI-RS. The system sends the target relative frequency domain resource index to the first cell, where the target relative frequency domain resource index is carried by the third message (MSG3) in the random access procedure.

[0009] Thus, during the connection establishment process between the terminal device and the cell, the target frequency domain template is determined from the locally stored frequency domain template set based on the frequency domain template index information fed back by the network device through the SIB. Then, based on the target frequency domain template, the target relative frequency domain resource index corresponding to the early sounding reference signal / channel state information reference signal is determined, and this frequency domain resource index is synchronized to the network device via the random access message MSG3. Therefore, by combining SIB indication with a predefined template set during the random access phase, the terminal device can not only autonomously acquire early frequency domain resources during the random access process, but also avoid broadcasting complete frequency domain resource parameters, resulting in low signaling overhead and high flexibility.

[0010] In one possible implementation of the first aspect, the target frequency domain template includes the target resource block (RB) index range, target RB granularity, target interleaving mode, number of optional offsets, and target hash algorithm; correspondingly, determining the target relative frequency domain resource index corresponding to the early SRS / CSI-RS based on the target frequency domain template includes:

[0011] The target relative frequency domain resource index is determined based on the target RB index range, target RB granularity, target interleaving mode, number of optional offsets, and target hash algorithm.

[0012] In this way, the frequency domain template divides the frequency domain resources by the RB index range, and limits the way the terminal device selects frequency domain resources by parameters such as RB granularity, interleaving mode, number of optional offsets and hash algorithm, so as to improve the randomness of the terminal device's selection of frequency domain resources. Thus, by broadcasting simple frequency domain resource index information, the terminal device can randomly select frequency domain resources within the RB range corresponding to the target frequency domain template. This not only has low signaling overhead and high flexibility, but also reduces the possibility of early SRS / CSI-RS frequency domain resource conflicts between different terminal devices, which can suppress the frequency domain resource conflict problem between multiple terminal devices and further improve the accuracy of channel estimation.

[0013] Optionally, in another possible implementation of the first aspect, determining the target relative frequency domain resource index based on the target RB index range, target RB granularity, target interleaving mode, optional offset number, and target hash algorithm includes:

[0014] Based on the target RB index range and target RB granularity, at least one optional RB index is selected from the target RB index range to generate an optional RB list;

[0015] Based on the target interleaving pattern, at least one available RB index is selected from the list of optional RBs to generate an available RB list and determine the number of available RBs;

[0016] The local offset index corresponding to the terminal device is determined based on the target hash algorithm and the number of optional offsets;

[0017] The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs and the local offset index.

[0018] Thus, by limiting the smallest unit of frequency domain resource allocation through RB granularity, terminal devices can determine available RBs from the RB index range based on the RB granularity in the frequency domain template to form a list of selectable RBs. Furthermore, the index of available RBs in the list of selectable RBs is limited by the interleaving mode, allowing terminal devices to select available RBs from the list of selectable RBs to form a list of available RBs. Therefore, the available RBs determined by terminal devices are usually different under different interleaving modes, thus initially suppressing the frequency domain resource conflict problem among multiple terminal devices. Subsequently, a hash algorithm is used to generate a random number, and the local offset index is randomly determined within the allowed range of selectable offsets based on this random number. This improves the randomness of the local offset index, reduces the probability of multiple terminal devices calculating the same frequency domain resource, and further reduces the possibility of frequency domain resource conflicts among multiple terminal devices.

[0019] Optionally, in another possible implementation of the first aspect, the target SIB further carries a first global frequency domain offset corresponding to the first cell; correspondingly, determining the target relative frequency domain resource index from the list of available RBs based on the number of available RBs and the local offset index includes:

[0020] The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs, the local offset index, and the first global frequency domain offset.

[0021] In this way, by broadcasting the global frequency domain offset corresponding to the cell in the SIB, the network side can dynamically adjust the resource allocation benchmark of the entire cell, and make unified adjustments to the resource allocation position at the cell level, which enhances the centralization and flexibility of resource management and facilitates resource coordination and interference avoidance among multiple cells.

[0022] Optionally, in another possible implementation of the first aspect, determining the target relative frequency domain resource index from the list of available RBs based on the number of available RBs, the local offset index, and the first global frequency domain offset includes:

[0023] The sum of the local offset index and the first global frequency domain offset is moduloed by the number of available RBs to determine the index of the target relative frequency domain resource index in the list of available RBs;

[0024] The target relative frequency domain resource index is determined from the list of available RBs based on the index of the target relative frequency domain resource index in the list of available RBs.

[0025] In this way, by using local offset index and global frequency domain offset, frequency domain resource conflicts between multiple terminal devices are suppressed at the terminal level and cell level, respectively. The final resource index is determined by modulo operation. The calculation is simple and easy to implement. This not only further reduces the possibility of resource conflicts between multiple terminal devices and maintains the uniform distribution of resources, but also reduces the computational complexity of resource allocation.

[0026] Optionally, in another possible implementation of the first aspect, determining the local offset index corresponding to the terminal device based on the target hash algorithm and the optional number of offsets includes:

[0027] The target random number is determined by hashing the random access preamble selected by the terminal device according to the target hash algorithm.

[0028] The local offset index is determined by performing a modulo operation between the target random number and the number of optional offsets.

[0029] Thus, since the random access preamble selected by terminal devices within the same cell is usually different, the local offset index determined by hash calculation based on the random access preamble is also usually different. Therefore, by utilizing the randomness of the random access preamble, frequency domain resources among terminal devices are naturally distributed, further reducing the probability of resource conflicts among multiple terminal devices, and without the need for additional signaling overhead.

[0030] Optionally, in another possible implementation of the first aspect, after sending the target relative frequency domain resource index to the first cell, the method further includes:

[0031] Receive MSG4 from the first cell, wherein MSG4 carries an acknowledgment command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell, wherein the acknowledgment command is used to indicate whether the target relative frequency domain resource index needs to be corrected.

[0032] If the confirmation command indicates that the target relative frequency domain resource index needs to be corrected, the target relative frequency domain resource index is corrected according to the second global frequency domain offset.

[0033] Thus, by introducing conflict detection and closed-loop correction on the frequency domain resource index reported by the network side, when conflicts occur in the frequency domain resources determined by different terminal devices, the base station is allowed to adjust the frequency domain resources selected by the terminal devices. This further enhances the network's control and reliability over resource allocation, avoids the problem of frequency domain resource conflicts between different terminal devices, and ensures the accuracy of channel estimation.

[0034] Optionally, in another possible implementation of the first aspect, the aforementioned confirmation command is further used to instruct the terminal device whether to trigger the early SRS / CSI-RS, wherein, when the value of the confirmation command is a first command value, it is used to instruct the terminal device not to trigger the early SRS / CSI-RS; when the value of the confirmation command is a second command value, it is used to instruct the terminal device to trigger the early SRS / CSI-RS without needing to correct the target relative frequency domain resource index; and when the value of the confirmation command is a third command value, it is used to instruct the terminal device to trigger the early SRS / CSI-RS and need to correct the target relative frequency domain resource index.

[0035] In this way, by mapping the confirmation command to different terminal device behaviors (not triggering early SRS / CSI-RS, triggering without needing to modify the resource index, and triggering with needing to modify the resource index), fine-grained control over early SRS / CSI-RS triggering and resource adjustment is achieved, enhancing the system's flexibility and robustness.

[0036] Optionally, in another possible implementation of the first aspect, the MSG3 is further used to carry a frequency domain capability support identifier corresponding to the terminal device, wherein the frequency domain capability support identifier is used to indicate whether the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index.

[0037] Thus, by carrying a frequency domain capability support identifier in the MSG3, the terminal device can report back to the network side whether it supports the calculated frequency domain resources. This avoids invalid resource allocation caused by the terminal device's frequency domain capability limitations, which would lead to early SRS / CSI-RS triggering failure. This not only improves the accuracy and efficiency of resource allocation, but also avoids the terminal device making invalid early SRS / CSI-RS attempts.

[0038] Optionally, in another possible implementation of the first aspect, the aforementioned frequency domain template set includes at least one frequency domain template subset, each frequency domain template subset includes at least one frequency domain template, and the target frequency domain template index information includes a target frequency domain template set identifier and a target frequency domain template index; correspondingly, determining the target frequency domain template from the pre-stored frequency domain template set based on the target frequency domain template index information includes:

[0039] Based on the target frequency domain template set identifier, determine the target frequency domain template subset from the frequency domain template set;

[0040] The target frequency domain template is determined from the target frequency domain template subset based on the target frequency domain template index.

[0041] In this way, by organizing the frequency domain templates into multiple subsets and guiding the terminal devices to select them through template set identifiers and template indexes, differentiated resource configurations are supported in multi-band (such as FR1 / FR2) and multi-bandwidth part (BWP) scenarios, thereby improving the scalability and deployment adaptability of resource configuration.

[0042] Secondly, embodiments of this application provide a communication method. This method can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit this. The following description uses a network device (such as a base station) as an example.

[0043] The method includes: sending a target SIB of a first cell to a terminal device, wherein the terminal device is in the process of establishing a connection with the first cell, the target SIB carries target frequency domain template index information, the target frequency domain template index information is used to instruct the terminal device to determine the target relative frequency domain resource index corresponding to the early SRS / CSI-RS; and receiving the target relative frequency domain resource index from the terminal device, wherein the target relative frequency domain resource index is carried by MSG3 in the random access process.

[0044] In one possible implementation of the second aspect, the target SIB also carries a first global frequency domain offset corresponding to the first cell.

[0045] Optionally, in another possible implementation of the second aspect, after receiving the target relative frequency domain resource index from the terminal device, the method further includes:

[0046] Based on whether the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device in the first cell, an acknowledgment command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell are generated. The reference terminal device is any terminal device other than the terminal device in the first cell. The acknowledgment command is used to indicate whether the target relative frequency domain resource index needs to be corrected.

[0047] Send MSG4 to the terminal device, where MSG4 carries an acknowledgment command and a second global frequency domain offset.

[0048] Optionally, in another possible implementation of the second aspect, the MSG3 is further used to carry a frequency domain capability support identifier corresponding to the terminal device, wherein the frequency domain capability support identifier is used to indicate whether the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index.

[0049] Optionally, in another possible implementation of the second aspect, the aforementioned confirmation command is further used to indicate whether the terminal device triggers early SRS / CSI-RS; correspondingly, the generation of the confirmation command corresponding to the target relative frequency domain resource index and the second global frequency domain offset corresponding to the first cell based on whether the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device in the first cell includes:

[0050] When the frequency domain capability support flag indicates that the terminal device does not support the frequency domain resources corresponding to the target relative frequency domain resource index, the value of the confirmation command is determined as the first command value, so as to instruct the terminal device not to trigger earlySRS / CSI-RS;

[0051] When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is different from the reference relative frequency domain resource index corresponding to each reference terminal device, the value of the confirmation command is determined as the second command value, so as to instruct the terminal device to trigger early SRS / CSI-RS without needing to correct the target relative frequency domain resource index;

[0052] When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device, the value of the confirmation command is determined as the third command value, and a second global frequency domain offset is generated to indicate that the terminal device triggers early SRS / CSI-RS and that the target relative frequency domain resource index needs to be corrected.

[0053] The second aspect is the implementation on the network device side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0054] Thirdly, a communication device is provided, comprising a processing module and a communication module. The communication module is configured to receive a target SIB from a first cell, wherein the terminal device is in the process of establishing a connection with the first cell, and the target SIB carries target frequency domain template index information; the processing module is configured to determine a target frequency domain template from a pre-stored set of frequency domain templates based on the target frequency domain template index information, wherein the set of frequency domain templates contains at least one frequency domain template, which describes the determination rules for frequency domain resources; and to determine a target relative frequency domain resource index corresponding to the early SRS / CSI-RS based on the target frequency domain template; the communication module is further configured to send the target relative frequency domain resource index to the first cell, wherein the target relative frequency domain resource index is carried by MSG3 during the random access procedure.

[0055] Fourthly, a communication device is provided, comprising a communication module. The communication module is used to send a target SIB of a first cell to a terminal device, wherein the terminal device is in the process of establishing a connection with the first cell, the target SIB carries target frequency domain template index information, the target frequency domain template index information being used to instruct the terminal device to determine the target relative frequency domain resource index corresponding to earlySRS / CSI-RS; and to receive a target relative frequency domain resource index from the terminal device, wherein the target relative frequency domain resource index is carried by MSG3 during the random access procedure.

[0056] The third and fourth aspects are the implementation on the device side, which correspond to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third and fourth aspects, and will not be repeated here.

[0057] Fifthly, an apparatus is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the apparatus further includes a memory. Optionally, the apparatus further includes a communication interface, to which the processor is coupled.

[0058] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0059] In another implementation, the device is a chip configured in a terminal device. When the device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0060] In a sixth aspect, an apparatus is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the apparatus further includes a memory. Optionally, the apparatus further includes a communication interface, to which the processor is coupled.

[0061] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0062] In another implementation, the communication device is a chip configured in a network device (such as a base station). When the device is a chip configured in a base station, the communication interface can be an input / output interface.

[0063] In a seventh aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions) that, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0064] Eighthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods in any possible implementation of any of the preceding aspects.

[0065] Ninthly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

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

[0067] In a tenth aspect, a communication system is provided, including the aforementioned apparatus. As an example, the communication system may include a terminal device and a network device. Optionally, the communication system may also include other devices that communicate with the terminal device and / or the network device.

[0068] The explanations, supplements, and descriptions of beneficial effects regarding the first and second aspects also apply to the third through tenth aspects, and will not be repeated here. Attached Figure Description

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

[0070] Figure 1 This is a schematic diagram of a communication system provided in an embodiment of this application;

[0071] Figure 2 This is a schematic flowchart of a communication method provided in an embodiment of this application;

[0072] Figure 3 This is a flowchart illustrating a communication method provided in another embodiment of this application;

[0073] Figure 4 This is a schematic diagram illustrating the interaction between a network device and a terminal device according to an embodiment of this application;

[0074] Figure 5 This is a schematic diagram of the overall flow of a communication method provided in another embodiment of this application;

[0075] Figure 6 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0076] Figure 7 This is a schematic diagram of the structure of a device provided in another embodiment of this application. Detailed Implementation

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

[0078] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink 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.

[0079] 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 shown. The network device 110 and the terminal device 120 can communicate via a wireless link.

[0080] 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.

[0081] 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 access node. Access network equipment has wireless transceiver capabilities and is used to communicate with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the above-mentioned 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 functions of a base station. Access network equipment can be macro base stations, micro base stations, or indoor stations, relay nodes or donor nodes, or wireless controllers in cloud radioaccess network (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted equipment, etc. Multiple access network equipment in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly, or they can communicate with terminals through relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment. In this application, the access network equipment is referred to as a network device.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] Access network equipment and / or terminal equipment 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 equipment and terminal equipment. They can be deployed in the same or different scenarios; for example, both can be deployed on land simultaneously; or the access network equipment can be deployed on land while the terminal equipment is deployed on water, etc., and so on.

[0086] 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), CUs (control planes, CPs), CUs (user planes, 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).

[0087] 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.

[0088] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms may also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol.

[0089] 1. SIB: In mobile communication systems, such as 5G NR mobile communication systems, system information (SI) consists of a master information block (MIB) and several system information blocks (SIBs). System information can be further divided into minimum system information (MSI) and other system information (OSI). The MSI contains basic information required for initial access and information for obtaining the OSI. The MSI includes the MIB and SIB1. The MIB contains multiple physical layer information required for obtaining SIB1 for the current cell. The system sends the MIB to the terminal device through periodic broadcasts.

[0090] SIB1 carries information on whether terminal devices are allowed to access the cell and defines the OSI scheduling. In addition, it provides radio resource configuration information shared by all terminal devices and prohibition information required for unified access control. SIB1 is also called remaining minimum system information (RMSI), which means the remaining minimum system message other than MIB. The system usually sends SIB1 to terminal devices through periodic broadcasts.

[0091] Other SIBs (such as SIB2-SIB12) are scheduled by SIB1. For example, SIB2 contains common parameters for RRC and is the core configuration carrier, mainly including: random access channel (RACH) configuration, common parameters for uplink / downlink initial bandwidth portion (BWP), paging configuration, etc. SIB3 can mainly contain common parameters for cell reselection in the same frequency, different frequencies, and across systems (such as to LTE) (such as frequency priority, reselection threshold, etc.). SIB4 contains cell reselection information related to neighboring cells in the same frequency (such as the same frequency neighboring cell list and cell-specific offsets of each neighboring cell in the same frequency). SIB5 contains cell reselection information related to neighboring cells in different frequencies (such as the inter-frequency neighboring cell list and cell-specific offsets of each neighboring cell in different frequencies). SIB6 / 7 / 8 are mainly used for interoperability with different systems (such as LTE, UMTS, GSM, etc.). SIB9 is mainly used for transmitting public safety-related information (such as earthquake and tsunami warnings). SIB10-SIB12 are used for warning messages in earthquake and tsunami warning systems (ETWS) and commercial mobile alert systems (CMAS). After the terminal device is powered on or enters a new cell, it can first decode the MIB, then decode SIB1 based on the MIB, and then decode other SIBs (such as SIB2) as needed based on the scheduling information in SIB1 to obtain the complete configuration.

[0092] It should be noted that, in addition to the SIB2-SIB12 listed above, other SIBs may also be included in the OSI model, and this application does not limit them in this embodiment.

[0093] 2. SRS: An uplink reference signal transmitted by terminal equipment, primarily used to help network devices (such as gNBs) estimate uplink channel quality, supporting beamforming, multiple-input multiple-output (MIMO) optimization, and dynamic resource scheduling. In TDD systems, channel reciprocity can also be used to indirectly optimize downlink performance.

[0094] 3. CSI-RS: This is a key downlink reference signal in the 5G NR system. It is mainly used by terminal equipment to measure downlink channel quality and feed back Channel State Information (CSI) to network equipment to support optimization functions such as scheduling, beamforming, and link adaptation.

[0095] 4. Early SRS: This refers to a mechanism where the terminal device sends an SRS to the network device before the RRC connection establishment process is complete. The network device can obtain an estimate of the terminal device's uplink channel at the moment the connection is established. For example, in a TDD system, the network device can immediately use this information for precise downlink beam alignment and precoding, thereby employing high-order MCS and closed-loop precoding in the first downlink data transmission, thus improving throughput.

[0096] 5. Early CSI-RS: In 5G NR (New Radio) systems, to shorten link adaptation delays, network devices send CSI-RS signals before the RRC connection establishment process is complete, and terminal devices provide feedback on Channel State Information (CSI). The purpose is to allow network devices to obtain downlink channel state information from terminal devices the instant the connection is established, enabling faster modulation and coding scheme (MCS) selection during the initial communication phase, thereby improving the transmission efficiency and initial throughput of short-duration bursty services. For example, even in FDD systems (without channel reciprocity), network devices can immediately perform precise link adaptation based on the CSI report (selecting the optimal MCS, precoding, and transmission layer number), thus improving the transmission efficiency of the first downlink data.

[0097] 6. RRC: It is a key control layer in the wireless communication protocol stack, mainly responsible for managing the wireless resource configuration, connection control, mobility management and security functions between terminal devices and network devices (such as eNodeB, gNB).

[0098] 7. Channel State Information Measurement Configuration (CSI-MeasConfig): This is a key information element in the RRC reconfiguration message, used to configure the parameters related to CSI measurements performed by the terminal device. It mainly includes two parts: CSI Resource Configuration (CSI-ResourceConfig) and CSI Report Configuration (CSI-ReportConfig). CSI Resource Configuration defines the CSI-RS resources used for measurement, including information such as the resource's time-frequency location and port. CSI Report Configuration defines the reporting method for measurement results, including the reporting period, triggering conditions (e.g., event-triggered or periodic triggering), the reported quantity (e.g., CSI-RS RII, CSI-RS RI, CSI-RS CQI), and the reporting format. Through CSI-MeasConfig, the network can dynamically instruct the terminal device to measure specific wireless channel characteristics and report them as needed. This provides crucial feedback information for advanced functions such as downlink scheduling, beamforming, and link adaptation, thereby optimizing network performance and user experience.

[0099] 8. Random Access (RA) Procedure: This is a crucial step in a mobile communication system where terminal devices and network devices establish uplink synchronization and acquire radio resources. It is mainly used to establish network connections in scenarios such as initial access, handover, and connection reconstruction. This process involves sending a preamble to request access, the network device responds and allocates resources, and finally, the signaling connection is established.

[0100] In contention-based random access, a four-step process is typically used, especially in LTE and 5G systems:

[0101] Step 1: Preamble transmission (MSG1)

[0102] The terminal device selects a preamble on the physical random access channel (PRACH) and sends it to the network device to initiate an access request. If no response is received, the terminal device will gradually increase the transmission power and retransmit until successful or a timeout occurs.

[0103] Step 2: Random Access Response (MSG2)

[0104] After detecting the preamble sent by the terminal device, the network device sends a random access response (RAR) through the downlink channel. The RAR contains information such as timing advance (TA) and uplink resource grant (UL-Grant) to adjust the timing and resources of the terminal device's transmission.

[0105] Step 3: RRC Connection Request (MSG3)

[0106] The terminal device uses the allocated uplink resources to send an RRC connection request, carrying its own identifier (such as the cell radio network temporary identifier (C-RNTI)) and the reason for access (such as initial access, data transmission, etc.).

[0107] Step 4: Race Condition Resolution (MSG4)

[0108] The network device verifies the identity of the terminal device and sends a contention resolution message. If the terminal device receives a message that matches its identifier, the access is successful; otherwise, it needs to re-initiate the access process to prevent conflicts caused by multiple terminal devices using the same preamble.

[0109] In addition, 5G NR introduced two-step random access (2-step RA) in Release-16, which merges Msg1 and Msg3 and Msg2 and Msg4, significantly reducing access latency and making it suitable for low-latency and high-reliability scenarios.

[0110] Random access includes two modes: contention-based random access (CBRA) and contention-free random access (CFRA). In CBRA, multiple terminal devices can share a preamble set, which may lead to preamble conflicts. These conflicts are resolved through contention using MSG4, making it suitable for scenarios where network devices cannot predict access needs, such as initial access and connection reconstruction. In CFRA, network devices assign dedicated preambles to terminal devices, avoiding preamble conflicts and resulting in a high access success rate. It is primarily used for predictable scenarios such as handover and downlink data arrival, and is triggered by commands from the physical downlink control channel (PDCCH).

[0111] 9. MSG1: Transmitted via PRACH, the terminal device sends a randomly selected preamble on the PRACH to initiate an access request to the base station. This preamble does not contain user identity or service data; it is only used by network devices to detect access intent and perform periodic calibration. Depending on the scenario, the terminal device can initiate MSG1 via RRC signaling, MAC layer triggering, or PDCCH command.

[0112] 10. MSG2: Transmitted by network devices on the physical downlink shared channel (PDSCH), scheduled via PDCCH scrambled with RA-RNTI. MSG2 may contain three key pieces of information: TA (adjusting the uplink transmission time of the terminal device to achieve synchronization), UL-Grant (allocating the uplink resources required for MSG3 transmission), and temporary C-RNTI (used for conflict resolution between subsequent MSG3 and MSG4).

[0113] 11. MSG3: In 5G NR (New Radio) systems, MSG3 is the crucial third step in the Random Access Procedure (RACH). It is transmitted via the Physical Uplink Shared Channel (PUSCH) and is used to establish or restore a connection between the terminal device and the network device. The content and function of MSG3 vary depending on the current state of the terminal device and the access scenario; therefore, it is not a fixed-format message but rather a PUSCH transmission carrying different higher-layer signaling.

[0114] The functions of MSG3 can include:

[0115] (1) Provide terminal device identity: MSG3 is the primary way for terminal devices to explicitly report their identity to the network for the first time, and is used by the network to identify and verify terminal devices;

[0116] (2) Reason for Access: MSG3 contains the reason why the terminal device initiates random access, such as initial access, connection reconstruction, or uplink data arrival;

[0117] (3) Preparation for contention resolution: In contention-based random access, MSG3 is the basis for subsequent contention resolution (MSG4). The network uses the information in MSG3 to determine whether there is a preamble conflict.

[0118] The specific information carried by MSG3 depends on the UE's access scenario, and the main types include:

[0119] (1) Initial access in RRC_IDLE state: MSG3 carries the RRCSetupRequest message, which contains the temporary identifier of the terminal device (such as 5G-S-TMSI) or a random value, as well as the access reason (Establishment Cause).

[0120] (2) RRC_INACTIVE state recovery access: MSG3 carries the RRCResumeRequest message, used to request the restoration of the previous connection;

[0121] (3) RRC connection reconstruction: MSG3 carries the RRCReestablishmentRequest message, which contains the terminal device's C-RNTI and cell identifier, and is used to reconstruct the connection after the connection is interrupted;

[0122] (4) Uplink synchronization failure and data pending transmission (competition scenario): MSG3 carries C-RNTI to inform the network of the identity of the terminal device;

[0123] (5) System Information Request: MSG3 carries the RRCSystemInfoRequest message, which is used to request specific system information.

[0124] In summary, MSG3 is the first PUSCH carrying key identity and control information sent by the terminal device on the uplink during the 5G NR random access process. It is a core step in establishing an RRC connection, completing identity verification, and resolving resource conflicts.

[0125] 12. MSG4: This is the contention resolution message in the random access procedure. It is sent by the network device to the terminal device to resolve access conflicts caused by multiple terminal devices using the same preamble, to confirm which terminal device's random access request was successful, and to assign a unique network identifier.

[0126] In the connected state, if the terminal device receives MSG4 scrambled with C-RNTI and successfully decodes the terminal device identity information contained therein (consistent with MSG3), then the contention is considered to have been resolved successfully.

[0127] In idle state, network devices scramble PDCCH using TC-RNTI, and terminal devices compare and compete to resolve ID mismatch. If successful, they upgrade TC-RNTI to C-RNTI.

[0128] MSG4, carried by PDSCH, is a MAC layer message that completes the final access confirmation.

[0129] 13. MAC-CE: Contention Resolution Identity. This element uniquely identifies and announces which terminal device's access request has been accepted by the network by comparing it with the original identifier sent by the terminal device. MAC-CE is the core mechanism for resolving contention conflicts; it contains the first 48 bits of the uplink common control channel service data unit (CCCH SDU) sent by the terminal device in MSG3. After receiving MSG4, the terminal device compares this identifier with its previously sent content. If they match, the contention resolution is considered successful, and the random access procedure is completed; if they do not match, the contention has failed, and the UE needs to re-initiate random access.

[0130] 14. C-RNTI: Its main function in a wireless network is to provide a unique temporary identifier within the current serving cell for terminal devices in connected state (RRC_CONNECTED). Each terminal device accessing a cell is assigned a unique C-RNTI for MAC layer scheduling and management, but this identifier is only valid within the current cell and needs to be reassigned when switching to a new cell. The C-RNTI is dynamically assigned by the network device, usually after the random access procedure (such as Msg4) or after the RRC connection is established, and is continuously used while the UE remains in connected state.

[0131] 15. Resource block (RB): The basic unit for resource allocation in mobile communication systems, widely used in wireless networks such as 4G LTE and 5G NR. It defines a fixed bandwidth resource in the frequency domain and is one of the smallest resource units for scheduling and data transmission, playing a key role in achieving efficient and flexible wireless resource management.

[0132] The frequency domain structure of an RB is as follows: an RB contains 12 consecutive subcarriers in the frequency domain, and the width of each subcarrier is usually 6 kHz (it can also be configured to 30 kHz, 60 kHz, etc. in 5G). Therefore, the total bandwidth of an RB is 12 × 6 kHz = 180 kHz. This structure is basically consistent in LTE and 5G, which facilitates system compatibility and resource scheduling.

[0133] The time-domain structure of an RB is as follows: In the time domain, one RB corresponds to one slot, which is 7 or 14 OFDM symbols (depending on the cyclic prefix type). Therefore, an RB is a two-dimensional time-frequency resource unit, often used to describe the resource size occupied by physical channels such as PUSCH, PDSCH, and PRACH.

[0134] As the core unit of resource scheduling, RB is widely used in scenarios such as uplink / downlink data transmission, random access procedures, and resource management in NB-IoT systems.

[0135] 16. First cell: This can refer to a cell that is currently establishing a connection with the terminal device.

[0136] 17. Target SIB: This can refer to an SIB that is periodically broadcast by network devices to all terminal devices within the cell, carrying parameters related to the early SRS / CSI-RS frequency resource configuration. Based on the preceding technical background analysis, SIB2 (System Information Block 2) is the most typical and reasonable carrier for such common parameters for radio resource control. Therefore, the "target SIB" is preferably SIB2, but the scope of protection of this invention is not limited to this, and it can also be other SIBs used for broadcasting common resource configuration.

[0137] In this embodiment, the purpose of this application is to enable terminal devices to obtain the frequency resource parameters of Early SRS / CSI-RS before the RRC connection is established (i.e., in the IDLE / INACTIVE state). Therefore, the SIB carrying these parameters needs to meet the following requirements: the terminal device can reliably and timely obtain them during the random access procedure (MSG1-MSG4); it is applicable to all terminal devices that may initiate access within the cell; and it allows the network side to perform a certain degree of dynamic configuration or updates. Based on this, a suitable SIB (such as SIB1, SIB2, etc.) can be selected as the target SIB according to actual needs and specific application scenarios, or a dedicated SIB can be added as the target SIB. This embodiment does not limit this.

[0138] 18. Target Frequency Domain Template Index Information: This refers to the identification information carried by the network device in the target SIB, used to indicate a specific "frequency domain template". The target frequency domain template index information itself may not be complete frequency resource parameters, but rather a "pointer" or "index" to a predefined set of rules. Its specific form can be a combination of one or more information elements.

[0139] As an example, when a predefined frequency domain template set stored locally on the terminal device contains at least one subset of frequency domain templates (e.g., template subsets configured for different frequency bands (such as FR1 band and FR2 band) or different BWPs), and each frequency domain template subset contains at least one frequency domain template, the target frequency domain template index information may include two parts: a target frequency domain template set identifier (TemplateSetID) and a target frequency domain template index (TemplateIndex). The target frequency domain template set identifier can be used to select a subset from multiple predefined frequency domain template subsets; the target frequency domain template index can be used to further specify a specific frequency domain template within the selected subset.

[0140] By broadcasting this target frequency domain template index information, network devices can dynamically specify a set of common rules for calculating early SRS / CSI-RS frequency domain resources for terminal devices within the cell with extremely low signaling overhead.

[0141] 19. Target Relative Frequency Domain Resource Index: This refers to the index value calculated by the terminal device based on the target frequency domain template index information, used to identify the specific frequency domain resources occupied by the early SRS / CSI-RS. It can be a "relative" index, and its physical meaning (such as the corresponding specific physical resource block number) needs to be interpreted in conjunction with the rules defined in the frequency domain template (such as starting position, granularity, interleaving mode, etc.). This index is a digital representation of the resource location that the terminal device intends to use and will be reported to the network device in subsequent steps. For example, the target relative frequency domain resource index can be an RB number, used to indicate the specific RB occupied by the early SRS / CSI-RS.

[0142] 20. During the process of establishing a connection between the terminal device and the first cell: This can refer to the period when the terminal device is in the random access procedure transitioning from the RRC_IDLE state or RRC_INACTIVE state to the RRC_CONNECTED state, and the RRC connection establishment has not yet been completed. At this time, the terminal device cannot receive any terminal-specific RRC configuration messages, and therefore can only rely on broadcast system information to obtain the necessary resource configuration.

[0143] 21. Frequency Domain Template Set: This refers to a predefined set of frequency domain resource allocation rules stored locally on the terminal device (e.g., embedded in the protocol stack software or hardware). The frequency domain template set can be predefined by technical standards (such as 3GPP specifications) or pre-configured by the manufacturer, ensuring interoperability between devices from different manufacturers. Each entry within the frequency domain template set is a "frequency domain template." Each frequency domain template in the set can have a unique index (or identifier) ​​to uniquely identify it.

[0144] 22. Frequency domain template: can refer to a specific entry in a set of frequency domain templates. A frequency domain template can be a set of formal parameters that together define an algorithm or rule for mapping abstract indices to specific physical frequency resources.

[0145] As an example, a frequency domain template may include, but is not limited to, the following parameters: RB range, RB granularity, interlace pattern, allowed offset count, associated hash / randomization algorithm, etc.

[0146] The RB range can include the start and end indices of RBs that can be used in early SRS / CSI-RS.

[0147] Here, RB granularity refers to the basic unit of resource allocation. For example, RB granularity can be 1RB, 2RB, 4RB, 8RB, etc., and this application does not limit this.

[0148] Among them, the interleaving mode can be defined within the RB range, according to which mode (such as odd-even interleaving, fixed step size) is selected to achieve resource domain orthogonalization.

[0149] Among them, the number of selectable offsets defines the number of offsets that the terminal device can select within a frequency domain template. For example, if the number of selectable offsets corresponding to a frequency domain template is 12, then when the terminal device determines the local offset index based on the frequency domain template, it can select local offset indices of 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, and 11, for a total of 12.

[0150] Among them, hash / randomization algorithm: is used to indicate which algorithm the terminal device uses to calculate its local offset index.

[0151] 23. Target Frequency Domain Template: This refers to the specific frequency domain template uniquely determined by the terminal device from its local frequency domain template set based on the target frequency domain template index information received from the network device. It serves as the direct basis for the terminal device to perform autonomous resource calculations in subsequent steps.

[0152] It should be understood that the technical terms used in this application are for illustrative purposes only and not as limiting. For example, as technology evolves, technical terms may also change, and other technical terms that have the same technical meaning should also apply to this application.

[0153] First, the reasons for the technical problem that this application aims to solve will be explained:

[0154] In mobile communication systems, when a terminal device switches from an idle or inactive state to a connected state, due to the lack of prior channel measurement / reporting information (such as CSI), the base station (gNB) can usually only use a degraded transmission scheme in downlink transmission. That is, it does not use closed-loop precoding on the large-scale antenna array and uses a lower-level MCS, resulting in a significant decrease in instantaneous throughput after the handover.

[0155] To address the aforementioned issues, the early SRS / CSI-RS mechanism was introduced in the 3GPP standard protocol Release-20. This mechanism aims to trigger channel measurements early in the connection establishment process, enabling network and terminal devices to acquire channel state information (CSI) as quickly as possible, perform link adaptation (using closed-loop precoding and high-level MCS), and complete accurate time-frequency tracking. This avoids the low throughput problem caused by degraded transmission schemes and quickly restores high-throughput transmission.

[0156] In related technologies, current standards explicitly trigger early SRS / CSI-RS through MAC-CE carried by MSG4 during the random access process. However, MAC-CE is a lightweight triggering signaling and cannot be used to carry complex resource allocation information. Furthermore, in existing NR procedures, SRS / CSI-RS resource configuration is handled through dedicated RRC configuration (i.e., CSI-MeasConfig in the RRC reconfiguration message). Therefore, the first CSI acquisition or the first CSI-RS measurement can only be triggered after the terminal device successfully switches to connected state. Consequently, before the RRC connection is established, the terminal device cannot receive any terminal-specific RRC configuration (such as CSI-MeasConfig), preventing the terminal device from executing early SRS / CSI-RS. Therefore, how to obtain the frequency domain resource parameters required for early SRS / CSI-RS before the RRC connection is established becomes a pressing issue.

[0157] In view of this, this application provides a communication method that broadcasts simple frequency domain template index information via SIB, enabling terminal devices to autonomously acquire early frequency resources before the establishment of an RRC connection, with low signaling overhead and high flexibility.

[0158] 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.

[0159] 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.

[0160] Figure 2 This is a flowchart illustrating a communication method according to an embodiment of this application. It can be understood that... Figure 2 The terminal device in the middle can be Figure 1 Any terminal device in the context of network equipment can refer to any 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 2 As shown, the method includes the following steps:

[0161] Step 201: The network device sends the target SIB of the first cell to the terminal device. Correspondingly, the terminal device receives the target SIB. During the connection establishment process between the terminal device and the first cell, the target SIB carries target frequency domain template index information. The target frequency domain template index information is used to instruct the terminal device to determine the target relative frequency domain resource index corresponding to the early SRS / CSI-RS.

[0162] In this embodiment, the network device can predefine a set of frequency domain templates and store them locally, and synchronize them to the terminal device for local storage. The network device's operation and maintenance system or wireless resource management module can determine a set of frequency domain resource calculation rules that the terminal device is expected to use, based on the cell's frequency band, bandwidth, deployment scenario, and early SRS / CSI-RS policy. This set of rules can be mapped to a specific frequency domain template in the predefined frequency domain template set. The network device can then generate target frequency domain template index information corresponding to that specific template based on its index in the predefined set. When the network device broadcasts a target SIB (such as SIB1, SIB2, or a newly added proprietary SIB), it can encapsulate the target frequency domain template index information into the corresponding information element of the target SIB. Subsequently, according to the system information scheduling mechanism, this broadcast is periodically performed within the coverage area of ​​the first cell. This broadcast process can be independent of the access behavior of any specific terminal device, providing unified resource configuration guidance for all terminal devices that may initiate access.

[0163] Correspondingly, when a terminal device needs to establish a connection with the first cell (e.g., upon powering on, moving into a new cell, or recovering from an idle or inactive state to a connected state), the terminal device can read the MIB and SIB1 of the first cell and, based on the scheduling information in SIB1, locate and receive the target SIB. Then, the terminal device decodes the received target SIB and parses and extracts the target frequency domain template index information broadcast by the network device from the successfully decoded target SIB message. At this point, the terminal device obtains the key input parameters for subsequent autonomous calculation of early SRS / CSI-RS frequency domain resources.

[0164] Based on this, the network side completed the public configuration of early SRS / CSI-RS resource rules using a low-overhead broadcast method. Meanwhile, the terminal side, before initiating formal access, received the public broadcast information to obtain the basis for resource calculation in advance, preparing for subsequent calculations of early SRS / CSI-RS frequency domain resources and reporting resource requests in access messages. This solves the problem that terminal devices cannot obtain early SRS / CSI-RS frequency domain resource parameters through dedicated signaling before the RRC connection is established.

[0165] It should be noted that the explanations of the target SIB, first cell, target frequency domain template index information and target relative frequency domain resource index involved in the embodiments of this application can be found in the explanations of the aforementioned technical terms section, and will not be repeated here.

[0166] Step 202: The terminal device determines the target frequency domain template from the pre-stored frequency domain template set according to the target frequency domain template index information. The frequency domain template set contains at least one frequency domain template, which is used to describe the determination rules of frequency domain resources.

[0167] As one possible implementation, the target frequency domain template index information can be a single, globally unique index value (e.g., a frequency domain template index value TemplateIndex with a length of M bits), which directly points to a specific frequency domain template in a predefined set of frequency domain templates. After obtaining the target frequency domain template index information, the terminal device can search for this index value in the set of frequency domain templates and determine the frequency domain template that matches this index value as the target frequency domain template.

[0168] As another possible implementation, the frequency domain templates can be organized into multiple subsets, and each subset can be selected by the terminal device through a template set identifier and a template index. This supports differentiated resource configuration in multi-band (such as FR1 / FR2) and multi-bandwidth part (BWP) scenarios, improving the scalability and deployment adaptability of resource configuration. Specifically, in one possible implementation of this application embodiment, the aforementioned frequency domain template set may contain at least one frequency domain template subset, each subset containing at least one frequency domain template. The target frequency domain template index information may include a target frequency domain template set identifier and a target frequency domain template index. Correspondingly, step 202 may include:

[0169] Based on the target frequency domain template set identifier, determine the target frequency domain template subset from the frequency domain template set;

[0170] The target frequency domain template is determined from the target frequency domain template subset based on the target frequency domain template index.

[0171] In one possible implementation of this application, the predefined frequency domain template set can be hierarchically stored locally. That is, the frequency domain template set stored locally on the terminal device can be organized into multiple frequency domain template subsets, each uniquely identified by a frequency domain template set identifier (TemplateSetID). Different frequency domain template subsets are typically used to distinguish different application scenarios. For example, when the frequency domain template set identifier is 01, it corresponds to the frequency domain template subset of the FR1 band; when the frequency domain template set identifier is 10, it corresponds to the frequency domain template subset of the FR2 band. Furthermore, each frequency domain template subset can contain at least one specific frequency domain template, and each frequency domain template can be uniquely identified by a frequency domain template index (TemplateIndex).

[0172] Accordingly, when the frequency domain template set is stored hierarchically in the aforementioned manner, the target frequency domain template index information can consist of two parts: the target frequency domain template set identifier and the target frequency domain template index. This corresponds to a hierarchical template organization structure, which has better scalability and scenario adaptability.

[0173] Accordingly, after obtaining the target frequency domain resource index information, the terminal device can first parse the target frequency domain template index information, extract the target frequency domain template set identifier and the target frequency domain template index, and then search for the corresponding target frequency domain template subset in the local frequency domain template set based on the target frequency domain template set identifier. For example, if the target frequency domain template set identifier is 01, then the frequency domain template subset configured for the FR1 frequency band will be determined as the target frequency domain template subset. Next, within the determined target frequency domain template subset, the terminal device uses the target frequency domain template index as the key to perform a lookup, and determines the specific frequency domain template corresponding to the target frequency domain template index as the target frequency domain template.

[0174] It should be noted that the explanations of parameters such as frequency domain template set, frequency domain template, and target frequency domain template involved in the embodiments of this application can be found in the explanations of the aforementioned technical terms section, and will not be repeated here.

[0175] Step 203: The terminal device determines the target relative frequency domain resource index corresponding to the early SRS / CSI-RS based on the target frequency domain template.

[0176] As one possible implementation, the frequency domain template divides frequency domain resources by RB index range and limits the way terminal devices select frequency domain resources by parameters such as RB granularity, interleaving mode, number of optional offsets, and hash algorithm. This improves the randomness of frequency domain resource selection by terminal devices. Thus, by broadcasting simple frequency domain resource index information, terminal devices can randomly select frequency domain resources within the RB range corresponding to the target frequency domain template. This not only reduces signaling overhead and increases flexibility but also reduces the possibility of early SRS / CSI-RS frequency domain resource conflicts between different terminal devices, suppressing frequency domain resource conflicts between multiple terminal devices and further improving the accuracy of channel estimation. Specifically, in one possible implementation of this application embodiment, the target frequency domain template may include a target RB index range, target RB granularity, target interleaving mode, number of optional offsets, and target hash algorithm; correspondingly, step 203 may include:

[0177] The target relative frequency domain resource index is determined based on the target RB index range, target RB granularity, target interleaving mode, number of optional offsets, and target hash algorithm.

[0178] In one possible implementation of this application embodiment, determining the target relative frequency domain resource index based on the target RB index range, target RB granularity, target interleaving mode, optional offset quantity, and target hash algorithm may include:

[0179] Based on the target RB index range and target RB granularity, at least one optional RB index is selected from the target RB index range to generate an optional RB list;

[0180] Based on the target interleaving pattern, at least one available RB index is selected from the list of optional RBs to generate an available RB list and determine the number of available RBs;

[0181] The local offset index corresponding to the terminal device is determined based on the target hash algorithm and the number of optional offsets;

[0182] The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs and the local offset index.

[0183] The optional RB list can refer to a list of logical resource units generated based on the target RB range and RB granularity in the target frequency domain template. Each element in the optional RB list represents an allocable group of resource blocks whose size is an integer multiple of one "RB granularity" (e.g., blocks of 4 RBs). For example, each element in the optional RB list can be the starting index of the resource block group.

[0184] The available RB list can refer to a list obtained by further filtering the optional RB list according to the target interleaving mode in the target frequency domain template. The interleaving mode defines the resource selection pattern (such as selecting every other cell), which is used to achieve orthogonality of resources in the frequency domain and initially suppress frequency domain resource conflicts between multiple terminal devices. The elements in the available RB list are the discrete logical resource locations that the terminal devices can actually request and occupy.

[0185] The local offset index can refer to an integer value generated by the terminal device by running a specific hash algorithm (the algorithm type is indicated or implicit by the target frequency domain template). The local offset index can be used to select a specific RB resource index (i.e., the target relative frequency domain resource index) from the list of available RBs.

[0186] The first global frequency domain offset can refer to the cell-level common frequency domain offset value broadcast by the network side through the target SIB. The first global frequency domain offset can be applied to the resource calculation of all terminal devices in the first cell. Its function is to allow the network to perform a unified "overall sliding" of the Early SRS / CSI-RS resource positions of all terminal devices without changing the structure of the frequency domain template itself, so as to achieve inter-cell interference coordination or resource planning adjustment.

[0187] In this embodiment of the application, the terminal device can read the target RB range in the target frequency domain template (for example, the target RB range is...). to That is, the starting index of the target RB range is RB_start, and the ending index is RB_end), and the granularity of the target RB (for example, the granularity of the target RB is...). Then, the list of optional RBs can be determined using the following formula 1:

[0188] (1)

[0189] in, For the optional RB list, Let m be the starting index of the target RB range, and m be the index of the element in the optional RB list. The range of values ​​for m satisfies... .

[0190] For example, if the target RB range is [0, 47] and the target RB granularity is 4, then the list of optional RBs is {0, 4, 8, 12, ..., 44}, containing the starting indices of 12 optional resource block groups. Each optional resource block group contains 4 RBs. For example, the first resource block group consists of 4 RBs with indices 0-4.

[0191] In this embodiment, after determining the list of selectable resource blocks (RBs), the terminal device can determine the indices of each available RB from the list of selectable RBs based on the target interleaving pattern read from the target frequency domain template, thus forming the available RB list. The target interleaving pattern can be a bitmap, a step size, or a predefined pattern index. Based on the target interleaving pattern, the terminal device can filter elements that conform to the target interleaving pattern from the list of selectable RBs to form the available RB list, and determine the length of the available RB list as the number of available RBs (i.e., the total number of available resource block groups). The terminal device can determine the available RB list using the following formula 2:

[0192] (2)

[0193] Where AvailableSlots is the list of available RBs, RBGrid[i] represents the i-th element in the list of available RBs, and I(i)=1 indicates that the i-th element in the list of available RBs (i.e., RBGrid[i]) is allowed in the target interleaving mode.

[0194] The number of available RBs is: .

[0195] For example, continuing from the previous example, the determined list of available RBs is {0, 4, 8, 12, ..., 44}. If the target interleaving mode is "select all available blocks with even indices" (i.e., step size is 2), then the list of available RBs will contain the 0th, 2nd, 4th, 6th, 8th, and 10th elements of the list of available RBs, for a total of 6 available resource block groups. That is, the list of available RBs is {0, 8, 16, 24, 32, 40}, and the number of available RBs is M=6.

[0196] In this implementation, the RB index is periodically interleaved using an interleaving mode, thereby distributing terminal devices to different subsets of RBs without adding signaling, which initially suppresses frequency domain resource conflicts between multiple terminal devices.

[0197] In this embodiment, after determining the list of available Resource Blocks (RBs), a resource block group can be selected from the list as the frequency domain resource of the RB for early SRS / CSI-RS. To avoid frequency domain resource conflicts between terminal devices, a random number can be generated using a hash algorithm to randomly select an offset from the available offsets as a local offset index, and then the frequency domain resource can be selected from the list of available RBs based on the local offset index.

[0198] One possible implementation is to generate a random number, perform a hash operation on this random number using a target hash algorithm to obtain its hash value, and then perform a modulo operation between this hash value and the number of optional offsets K to obtain the local offset index. That is, the local offset index can be determined using the following formula 4:

[0199] offsetIndex=H(seed) mod K(4)

[0200] Where offsetIndex is the local offset index, H is the target hash algorithm, seed is a random number, and K is the number of optional offsets.

[0201] For example, assuming the number of optional offsets K is 12, the range of values ​​for the local offset index is {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}. If H(seed) is 20, then the local offset index offsetIndex can be determined to be 8.

[0202] As one possible implementation, since terminal devices within the same cell typically select different random access preambles, the local offset indices determined by hash calculation based on these random access preambles are also usually different. Therefore, the randomness of the random access preamble can be utilized to naturally distribute frequency domain resources among terminal devices, further reducing the probability of resource conflicts between multiple terminal devices, without requiring additional signaling overhead. That is, in one possible implementation of this application embodiment, determining the local offset index corresponding to the terminal device based on the target hash algorithm and the number of selectable offsets may include:

[0203] The target random number is determined by hashing the random access preamble selected by the terminal device according to the target hash algorithm.

[0204] The local offset index is determined by performing a modulo operation between the target random number and the number of optional offsets.

[0205] As one possible implementation, the local offset index can be determined using the following formula 5:

[0206] offsetIndex=H(RAPID) mod K(5)

[0207] Where offsetIndex is the local offset index, H is the target hash algorithm, RAPID is the random access preamble selected by the terminal device, and K is the number of optional offsets.

[0208] In this embodiment, after determining the local offset index, an RB index can be selected from the list of available RBs as the target relative frequency domain resource index. However, since the value of the local offset index may exceed the number of available RBs, the index of the target relative frequency domain resource index in the list of available RBs can be determined by modulo operation, thereby determining the target relative frequency domain resource index. As an example, the target relative frequency domain resource index can be determined by formula (6):

[0209] (6)

[0210] in, The target relative frequency domain resource index is the first one in the list of available RBs. One element, This is the list of available RBs, where offsetIndex is the local offset index, and M is the number of available RBs.

[0211] For example, continuing from the previous example, the determined list of available RBs is {0, 8, 16, 24, 32, 40}, and the number of available RBs is M=6. If the local offset index is offsetIndex=11, then the target relative frequency domain resource index is the 5th element in the list of available RBs (i.e., 11 mod 6=5), which means the target relative frequency domain resource index is 32. Combining the target RB granularity of 4 and the target relative frequency domain resource index, we know that the frequency domain resources occupied by the early SRS / CSI-RS are the 4 RBs numbered 32-35.

[0212] As one possible implementation, the global frequency domain offset corresponding to the cell broadcast in the SIB can enable the network side to dynamically adjust the resource allocation benchmark of the entire cell. This allows for unified adjustment of resource allocation positions at the cell level, enhancing the centralization and flexibility of resource management and facilitating resource coordination and interference avoidance among multiple cells. Specifically, in one possible implementation of this application embodiment, the target SIB may also carry the first global frequency domain offset corresponding to the first cell; correspondingly, the determination of the target relative frequency domain resource index from the list of available RBs based on the number of available RBs and the local offset index may include:

[0213] The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs, the local offset index, and the first global frequency domain offset.

[0214] As one possible implementation, when broadcasting the target SIB, the network device can also carry the first global frequency domain offset corresponding to the first cell in the target SIB. When selecting the target relative frequency domain resource index from the list of available RBs, a cell-level global frequency domain offset is superimposed on the local offset index, so that the frequency domain resources between cells are naturally distributed, realizing resource coordination and interference avoidance between multiple cells, and improving the centralization and flexibility of resource management.

[0215] As an example, the sum of the local offset index and the first global frequency domain offset can be moduloed by the number of available RBs to determine the index of the target relative frequency domain resource index in the list of available RBs; and based on the index of the target relative frequency domain resource index in the list of available RBs, the target relative frequency domain resource index can be determined from the list of available RBs. Therefore, the target relative frequency domain resource index can be determined using Equation 7:

[0216] (7)

[0217] in, The target relative frequency domain resource index is the first one in the list of available RBs. One element, This is a list of available RBs, and offsetIndex is the local offset index. The first global frequency domain offset is M, where M is the number of available RBs.

[0218] For example, continuing from the previous example, the determined list of available RBs is {0, 8, 16, 24, 32, 40}, the number of available RBs is M=6, and if the local offset index offsetIndex=11, the first global frequency domain offset is... =2, then the target relative frequency domain resource index is the first element in the list of available RBs (i.e. (11+2) mod 6=1), that is, the target relative frequency domain resource index is 0. Combining the target RB granularity 4 and the target relative frequency domain resource index, it can be seen that the frequency domain resources occupied by early SRS / CSI-RS are 4 RBs with RB numbers 0-3.

[0219] In this implementation, the smallest unit of frequency domain resource allocation is defined by the RB granularity, allowing the terminal device to determine available RBs from the RB index range based on the RB granularity in the frequency domain template, thus forming a list of selectable RBs. Furthermore, the index of available RBs in the list of selectable RBs is defined based on the interleaving mode, allowing the terminal device to select available RBs from the list of selectable RBs, thus forming a list of available RBs. Therefore, the available RBs determined by the terminal device are usually different under different interleaving modes, thereby initially suppressing the frequency domain resource conflict problem among multiple terminal devices. Then, a hash algorithm is used to generate a random number, and the local offset index is randomly determined within the allowed range of selectable offsets based on this random number, thereby improving the randomness of the local offset index and reducing the probability of multiple terminal devices calculating the same frequency domain resource. Thus, through this dual conflict suppression mechanism, the possibility of frequency domain resource conflicts among multiple terminal devices is further reduced.

[0220] Step 204: The terminal device sends the target relative frequency domain resource index to the first cell. Correspondingly, the network device receives the target relative frequency domain resource index, which is carried by MSG3 in the random access process.

[0221] In this embodiment, when a terminal device switches from an idle or inactive state to a connected state, it initiates a random access procedure to establish a connection with the first cell. Therefore, after determining the target relative frequency domain resource index corresponding to the early SRS / CSI-RS, the terminal device can carry the target relative frequency domain resource index via MSG3 in the random access procedure to synchronize the target relative frequency domain resource index to the network device. After obtaining the target relative frequency domain resource index carried by MSG3, the network device can determine the frequency domain resources occupied by the early SRS / CSI-RS based on the target relative frequency domain resource index, send the early CSI-RS on that frequency domain resource, and receive the early SRS reported by the terminal device.

[0222] As one possible implementation, the terminal device can also carry a frequency domain capability support identifier in the MSG3, enabling it to report to the network whether it supports the calculated frequency domain resources. This avoids invalid resource allocation due to the terminal device's frequency domain capability limitations, preventing early SRS / CSI-RS triggering failures. This not only improves the accuracy and efficiency of resource allocation but also avoids invalid early SRS / CSI-RS attempts by the terminal device. Specifically, in one possible implementation of this application embodiment, the MSG3 can also carry a frequency domain capability support identifier corresponding to the terminal device, whereby the frequency domain capability support identifier indicates whether the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index.

[0223] In this embodiment, since some terminal devices may not support a wide range of frequency domain resources due to functional limitations, to avoid situations where the terminal device's frequency domain capabilities cannot support the aforementioned calculated frequency domain resources, after determining the target relative frequency domain resource index, the terminal device can determine the value of the frequency domain capability support flag based on whether the target relative frequency domain resource index belongs to the range of frequency domain resource indexes supported by the terminal device. That is: if the target relative frequency domain resource index belongs to the range of frequency domain resource indexes supported by the terminal device, the value of the frequency domain capability support flag is determined to be a first preset value (such as 1 or true); if the target relative frequency domain resource index does not belong to the range of frequency domain resource indexes supported by the terminal device, the value of the frequency domain capability support flag is determined to be a second preset value (such as 0 or false).

[0224] For example:

[0225]

[0226] in, As a frequency domain capability support identifier, For target relative frequency domain resource indexing, This refers to the range of frequency domain resources supported by the terminal device.

[0227] In this embodiment of the application, after determining the frequency domain capability support identifier, the target relative frequency domain resource index and the frequency domain capability support identifier can both be carried in MSG3 and transmitted to the network device so that the network device can determine the corresponding frequency domain resources or other decisions.

[0228] The communication method of this application embodiment, during the connection establishment process between the terminal device and the cell, determines the target frequency domain template from the locally stored frequency domain template set based on the frequency domain template index information fed back by the network device through the SIB. Then, based on the target frequency domain template, it determines the target relative frequency domain resource index corresponding to the early detection reference signal / channel state information reference signal, and synchronizes this frequency domain resource index to the network device through the random access message MSG3. Therefore, by combining SIB indication with a predefined template set during the random access phase, the terminal device can not only autonomously acquire early frequency domain resources during the random access process, but also avoids broadcasting complete frequency domain resource parameters, resulting in low signaling overhead and high flexibility.

[0229] Figure 3 This is a flowchart illustrating a communication method provided in another embodiment of this application. It can be understood that... Figure 3 The terminal device in the middle can be Figure 1 Any terminal device in the context of network equipment can refer to any 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 includes the following steps:

[0230] Step 301: The network device sends the target SIB of the first cell to the terminal device. Correspondingly, the terminal device receives the target SIB. During the connection establishment process between the terminal device and the first cell, the target SIB carries target frequency domain template index information. The target frequency domain template index information is used to instruct the terminal device to determine the target relative frequency domain resource index corresponding to the early SRS / CSI-RS.

[0231] Step 302: The terminal device determines the target frequency domain template from the pre-stored frequency domain template set according to the target frequency domain template index information. The frequency domain template set contains at least one frequency domain template, which is used to describe the determination rules of frequency domain resources.

[0232] Step 303: The terminal device determines the target relative frequency domain resource index corresponding to the early SRS / CSI-RS based on the target frequency domain template.

[0233] Step 304: The terminal device sends the target relative frequency domain resource index to the first cell. Correspondingly, the network device receives the target relative frequency domain resource index, wherein the target relative frequency domain resource index is carried by MSG3 in the random access process.

[0234] The specific implementation process and principle of steps 301-304 above can be found in the detailed description of the above embodiments, and will not be repeated here.

[0235] Step 305: The network device generates an acknowledgment command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell, based on whether the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device in the first cell. The reference terminal device is any terminal device other than the terminal device in the first cell. The acknowledgment command is used to indicate whether the target relative frequency domain resource index needs to be corrected.

[0236] The reference terminal devices can refer to all other terminal devices within the same random access window as the currently being processed "terminal device" that have successfully reported their relative frequency domain resource index to the network device in the first cell. These reference terminal devices are the reference objects for the network device in performing collision detection. It is worth noting that the "reference" here is dynamic and can change depending on the processing target.

[0237] The reference relative frequency domain resource index can refer to the target relative frequency domain resource index reported by the reference terminal device in its respective MSG3 and calculated independently. As an example, the network device can maintain a temporary list recording the terminal identifiers corresponding to all successfully decoded MSG3s and their reported target relative resource indices.

[0238] The acknowledgment command can refer to an instruction code generated by a network device to indicate the result of a resource request to a target terminal device. As an example, the acknowledgment command can be carried by MAC-CE in the subsequent MSG4.

[0239] In this embodiment, although the terminal device implements a dual resource conflict suppression mechanism through interleaving mode and the randomness of the local offset index, the possibility of conflict still exists between different terminal devices because the local offset index is random. However, the network device can obtain the relative frequency domain resource index determined by each terminal device in the first cell. Therefore, after receiving resource requests reported by all access terminal devices, the network device can perform global resource conflict detection and generate a clear "acknowledgment command" for each terminal device based on the detection results. It also calculates a "second global frequency domain offset" for terminal devices that have conflicts or need adjustment to guide the terminal devices to correctly use or correct their requested early SRS / CSI-RS frequency domain resources in subsequent steps. Thus, through triple resource conflict suppression, not only can the terminal device obtain early SRS / CSI-RS frequency domain resources before the RRC connection is established in a low-signaling-overhead and highly flexible manner, but resource conflicts between multiple terminal devices are also avoided.

[0240] As one possible implementation, when the target relative frequency domain resource index is different from the reference relative frequency domain resource indexes corresponding to each reference terminal device, the network device can determine that there is no resource conflict between the current terminal device and the other terminal devices in the first cell. In this case, the value of the confirmation command can be set to a second command value (e.g., 01) to indicate that the terminal device does not need to modify the target relative frequency domain resource index. When the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any one of the reference terminal devices, it can be determined that there is a resource conflict between the current terminal device and the other terminal devices in the first cell. In this case, the value of the confirmation command can be set to a third command value (e.g., 10), and a second global frequency domain offset can be generated to indicate that the terminal device needs to modify the target relative frequency domain resource index using the second global frequency domain offset.

[0241] As a possible implementation, if the terminal device carries a frequency domain capability support identifier and a target relative frequency domain resource index in the MSG3, the value of the confirmation command and the second global frequency domain offset can be determined by combining the two. That is, in one possible implementation of this application embodiment, the MSG3 is further used to carry a frequency domain capability support identifier corresponding to the terminal device, and the confirmation command can also be used to indicate whether the terminal device triggers early SRS / CSI-RS; correspondingly, step 305 may include:

[0242] When the frequency domain capability support flag indicates that the terminal device does not support the frequency domain resources corresponding to the target relative frequency domain resource index, the value of the confirmation command is determined as the first command value, so as to instruct the terminal device not to trigger earlySRS / CSI-RS;

[0243] When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is different from the reference relative frequency domain resource index corresponding to each reference terminal device, the value of the confirmation command is determined as the second command value, so as to instruct the terminal device to trigger early SRS / CSI-RS without needing to correct the target relative frequency domain resource index;

[0244] When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device, the value of the confirmation command is determined as the third command value, and a second global frequency domain offset is generated to indicate that the terminal device triggers early SRS / CSI-RS and that the target relative frequency domain resource index needs to be corrected.

[0245] As an example, a network device can first check the frequency domain capability support flag of the terminal device. If the value of the frequency domain capability support flag is a second preset value, indicating that the terminal device does not support the frequency domain resource corresponding to the target relative frequency domain resource index it reported (for example, the resource block exceeds the maximum bandwidth supported by the terminal device), then the network device can set the value of the confirmation command to a first command value (such as 00) to instruct the terminal device not to trigger earlySRS / CSI-RS. This means that the network device determines that the terminal device cannot use the frequency domain resource it requested, and early SRS / CSI-RS triggering is prohibited. This not only improves the accuracy and efficiency of resource allocation but also avoids the terminal device making invalid early SRS / CSI-RS attempts.

[0246] Accordingly, the value of the frequency domain capability support identifier is a first preset value, indicating that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index it reports, and can use the frequency domain resources to trigger early SRS / CSI-RS. Then, the network device can compare the target relative frequency domain resource index reported by the terminal device with the reference relative resource index reported by all other terminal devices (i.e., reference terminal devices) in the status table. If no index is found that is the same as the target relative frequency domain resource index, it means that the frequency domain resource corresponding to the target relative frequency domain resource index is currently exclusively occupied by the terminal device, and the terminal device can be allowed to occupy the frequency domain resource to trigger early SRS / CSI-RS. Therefore, the network device can determine the value of the confirmation command as the second command value (such as 01), and the allocated second global frequency domain offset can be kept empty, 0, or the same as the first global frequency domain offset (because in this case, there is no need to use the second global frequency domain offset for correction), so as to instruct the terminal device to trigger early SRS / CSI-RS without needing to correct the target relative frequency domain resource index.

[0247] Correspondingly, if an index with the same relative frequency domain resource index as the target exists, it means that the frequency domain resource corresponding to the target relative frequency domain resource index has conflicted with other terminal devices. Therefore, the target relative frequency domain resource index needs to be corrected to avoid resource conflicts. Thus, the network device can determine the value of the confirmation command as the third command value (e.g., 10), and calculate an available, idle resource position based on the current target frequency domain template and the occupied resource positions in the resource request status table to determine the second global frequency domain offset. For example, by iterating through the available offset indices, the first one that ensures the final resource index won't conflict with any other terminal devices can be found. The value is used to indicate to the terminal device, via the third command value and the second global frequency domain offset, that early SRS / CSI-RS needs to be triggered and that the target relative frequency domain resource index needs to be corrected.

[0248] As an example, the mapping relationship between the value of the confirmation command and the behavior of the terminal device is shown in Table 1, the second global frequency domain offset. The mapping relationship between the actual RB offset and the actual RB offset is shown in Table 2:

[0249] Table 1

[0250]

[0251] Table 2

[0252]

[0253] Step 306: The network device sends MSG4 to the terminal device. Correspondingly, the terminal device receives the MSG4, which carries an acknowledgment command and a second global frequency domain offset.

[0254] In this embodiment, MSG4 is the fourth message in the standard random access procedure, and its core function is contention resolution. In this application, MSG4 is given the function of carrying closed-loop confirmation and adjustment instructions for early SRS / CSI-RS resource allocation. This allows MSG4 to not only solve the identity contention problem of "who successfully accessed the network," but also simultaneously solve the resource allocation problem of "on which resources to trigger the early signal."

[0255] After determining the acknowledgment command and the second global frequency domain offset, the network device can encapsulate the acknowledgment command and the second global frequency domain offset in one or more bit fields of the MSG4 MAC-CE and send the MSG4 to the terminal device. After decoding the MSG4, the terminal device can determine its subsequent behavior based on the parsed acknowledgment command value and the second global frequency domain offset: abandon triggering early SRS / CSI-RS, trigger early SRS / CSI-RS on autonomously calculated resources, or trigger early SRS / CSI-RS on resources corrected by the network. This enables the acquisition of early SRS / CSI-RS resources during the random access phase.

[0256] Step 307: If the terminal device confirms that the command indicates that the target relative frequency domain resource index needs to be corrected, it corrects the target relative frequency domain resource index according to the second global frequency domain offset.

[0257] In this embodiment, after sending MSG3, the terminal device can listen to the PDCCH scrambled with its own temporary identifier. Once a schedule targeting itself is detected, it receives and decodes MSG4 on the corresponding PDSCH resource. The terminal device first checks whether MSG4 has successfully resolved contention (e.g., whether the message contains its own unique identifier). This is a prerequisite for continuing with subsequent steps. Based on successful contention resolution, the terminal device parses the payload of MSG4, finds and decodes the "early SRS / CSI-RS resource acknowledgment MAC CE" carried within it. From this MAC CE, the terminal device extracts two key pieces of information:

[0258] (1) Confirm command: Read its bit value and determine whether it is the first command value, the second command value or the third command value.

[0259] (2) Second global frequency domain offset (conditional): If the confirmation command is the third command value (such as "10"), the second global frequency domain offset can be extracted from the predefined fields of MAC CE. ).

[0260] The terminal device can execute the corresponding branch based on the value of the confirmation command. If the confirmation command value is the first command value, the terminal device can determine that its requested early SRS / CSI-RS resource request has not been approved or is inapplicable, and will not trigger early SRS / CSI-RS. If the confirmation command value is the second command value, the terminal device can determine that its requested resources and capabilities have been approved and there is no resource conflict with other terminal devices. Therefore, the terminal device can directly use the target relative frequency domain resource index calculated in the aforementioned steps to prepare to send SRS or measure CSI-RS on the corresponding frequency domain resources when subsequently triggered. If the confirmation command value is the third command value, the terminal device can determine that its requested resources have conflicted but have been corrected by the network. Therefore, the terminal device may need to recalculate the final resource, i.e., the corrected target relative frequency domain resource index, based on the extracted second global offset, combined with the target frequency domain template rules and its own target relative frequency domain resource index. Then, the terminal device uses the corrected target relative frequency domain resource index to trigger early SRS / CSI-RS.

[0261] As an example, if the network device did not carry the first global frequency domain offset in the target SIB during the aforementioned steps, the corrected target relative frequency domain resource index can be calculated using Equation 8:

[0262] (8)

[0263] in, The corrected target relative frequency domain resource index is the first one in the list of available RBs. One element, This is a list of available RBs, and offsetIndex is the local offset index. is the second global frequency domain offset, and M is the number of available RBs.

[0264] As an example, if the network device did not carry the first global frequency domain offset in the target SIB during the aforementioned steps, the corrected target relative frequency domain resource index can be calculated using Equation 9:

[0265] (9)

[0266] in, The corrected target relative frequency domain resource index is the first one in the list of available RBs. One element, This is a list of available RBs, and offsetIndex is the local offset index. This is the first global frequency domain offset. is the second global frequency domain offset, and M is the number of available RBs.

[0267] It should be noted that in formulas 8 and 9... The actual RB offset can be determined based on the mapping relationship between the second global offset and the actual RB offset (e.g., the mapping relationship in Table 2). Taking Table 2 as an example, if the second global offset is 001, then the values ​​in Formulas 8 and 9 can be determined. It is "+1".

[0268] The communication method provided in this application introduces a network-side mechanism to perform conflict detection and closed-loop correction on the frequency domain resource index reported by the terminal device. This allows the base station to adjust the frequency domain resources selected by the terminal device when conflicts occur in the frequency domain resources determined by different terminal devices. This further enhances the network's control and reliability over resource allocation, avoids the problem of frequency domain resource conflicts between different terminal devices, and ensures the accuracy of channel estimation.

[0269] The following is passed Figure 4 and Figure 5 The overall flow of the communication method in the embodiments of this application will be described in detail.

[0270] Figure 4 This is a schematic diagram illustrating the interaction between a network device and a terminal device according to an embodiment of this application. Figure 5 This is a schematic diagram of the overall process of a communication method provided in another embodiment of this application.

[0271] For example, such as Figure 4 and Figure 5 As shown, frequency domain template sets can be predefined in 3GPP standard protocols and stored in terminal devices and network devices. When broadcasting a target SIB, the network device can broadcast the target frequency domain template set identifier (TemplateSetID), the target frequency domain template index (TemplateIndex), and the first global frequency domain offset. The terminal device reads a predefined frequency domain template set based on TemplateSetID and TemplateIndex to obtain the target frequency domain template. Then, the terminal device performs a hash calculation based on RAPID to determine the target relative frequency domain resource index UE_RB. Subsequently, the terminal device reports Capability (which can be used to carry the frequency domain resource range supported by the terminal device), UE_RB, and SupportFlag via MSG3 during the random access process. The network device receives UE_RBs from multiple terminal devices for conflict detection. If a conflict is detected, it sends a MAC-CE (including an acknowledgment command and a second global frequency domain offset) via MSG4. If no conflict is confirmed, confirmation is sent via MSG4 using MAC-CE (including a confirmation command (Confirmed_Command)). In the event of a conflict, the terminal device uses overlay... This yields the final target relative frequency domain resource index, Final_RB. For example... Figure 4 As shown, the terminal device and network device complete the acquisition of frequency domain resources for earlySRS / CSI-RS during the random access process, and can trigger earlySRS / CSI-RS at the beginning of the RRC connection.

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

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

[0274] 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.

[0275] Figure 6 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 6 As shown, the communication device 600 may include a communication module 620. The communication module 620 can implement corresponding communication functions, which can be internal communication functions of the communication device 600 or communication functions between the communication device 600 and other devices. Optionally, the communication module 620 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 600 further includes a processing module 610. The processing module 610 can implement corresponding processing functions.

[0276] Optionally, the communication device 600 further includes a storage module, which can be used to store instructions and / or data; the processing module 610 can read the instructions and / or data in the storage module so that the communication device 600 can implement the aforementioned method embodiments.

[0277] In one possible design, the communication device 600 may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 600 can be used to perform the steps or processes performed by the terminal device in any of the above method embodiments.

[0278] For example, the communication module 620 is used for:

[0279] Receive a target SIB from the first cell, wherein the terminal device is in the process of establishing a connection with the first cell, and the target SIB carries target frequency domain template index information;

[0280] Processing module 610 is used for:

[0281] Based on the target frequency domain template index information, a target frequency domain template is determined from a pre-stored set of frequency domain templates, wherein the set of frequency domain templates contains at least one frequency domain template, which is used to describe the rules for determining frequency domain resources; and is used to determine the target relative frequency domain resource index corresponding to early SRS / CSI-RS based on the target frequency domain template.

[0282] Communication module 620 is also used for:

[0283] Send the target relative frequency domain resource index to the first cell, wherein the target relative frequency domain resource index is carried by MSG3 in the random access process.

[0284] Thus, during the connection establishment process between the terminal device and the cell, the target frequency domain template is determined from the locally stored frequency domain template set based on the frequency domain template index information fed back by the network device through the SIB. Then, based on the target frequency domain template, the target relative frequency domain resource index corresponding to the early sounding reference signal / channel state information reference signal is determined, and this frequency domain resource index is synchronized to the network device via the random access message MSG3. Therefore, by combining SIB indication with a predefined template set during the random access phase, the terminal device can not only autonomously acquire early frequency domain resources during the random access process, but also avoid broadcasting complete frequency domain resource parameters, resulting in low signaling overhead and high flexibility.

[0285] For example, the target frequency domain template mentioned above includes the target resource block (RB) index range, target RB granularity, target interleaving mode, optional offset quantity, and target hash algorithm; correspondingly, the processing module 610 mentioned above is also used for:

[0286] The target relative frequency domain resource index is determined based on the target RB index range, target RB granularity, target interleaving mode, number of optional offsets, and target hash algorithm.

[0287] In this way, the frequency domain template divides the frequency domain resources by the RB index range, and limits the way the terminal device selects frequency domain resources by parameters such as RB granularity, interleaving mode, number of optional offsets and hash algorithm, so as to improve the randomness of the terminal device's selection of frequency domain resources. Thus, by broadcasting simple frequency domain resource index information, the terminal device can randomly select frequency domain resources within the RB range corresponding to the target frequency domain template. This not only has low signaling overhead and high flexibility, but also reduces the possibility of early SRS / CSI-RS frequency domain resource conflicts between different terminal devices, which can suppress the frequency domain resource conflict problem between multiple terminal devices and further improve the accuracy of channel estimation.

[0288] For example, the processing module 610 described above is also used for:

[0289] Based on the target RB index range and target RB granularity, at least one optional RB index is selected from the target RB index range to generate an optional RB list;

[0290] Based on the target interleaving pattern, at least one available RB index is selected from the list of optional RBs to generate an available RB list and determine the number of available RBs;

[0291] The local offset index corresponding to the terminal device is determined based on the target hash algorithm and the number of optional offsets;

[0292] The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs and the local offset index.

[0293] Thus, by limiting the smallest unit of frequency domain resource allocation through RB granularity, terminal devices can determine available RBs from the RB index range based on the RB granularity in the frequency domain template to form a list of selectable RBs. Furthermore, the index of available RBs in the list of selectable RBs is limited by the interleaving mode, allowing terminal devices to select available RBs from the list of selectable RBs to form a list of available RBs. Therefore, the available RBs determined by terminal devices are usually different under different interleaving modes, thus initially suppressing the frequency domain resource conflict problem among multiple terminal devices. Subsequently, a hash algorithm is used to generate a random number, and the local offset index is randomly determined within the allowed range of selectable offsets based on this random number. This improves the randomness of the local offset index, reduces the probability of multiple terminal devices calculating the same frequency domain resource, and further reduces the possibility of frequency domain resource conflicts among multiple terminal devices.

[0294] For example, the target SIB also carries the first global frequency domain offset corresponding to the first cell; correspondingly, the processing module 610 is also used for:

[0295] The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs, the local offset index, and the first global frequency domain offset.

[0296] In this way, by broadcasting the global frequency domain offset corresponding to the cell in the SIB, the network side can dynamically adjust the resource allocation benchmark of the entire cell, and make unified adjustments to the resource allocation position at the cell level, which enhances the centralization and flexibility of resource management and facilitates resource coordination and interference avoidance among multiple cells.

[0297] For example, the processing module 610 described above is also used for:

[0298] The sum of the local offset index and the first global frequency domain offset is moduloed by the number of available RBs to determine the index of the target relative frequency domain resource index in the list of available RBs;

[0299] The target relative frequency domain resource index is determined from the list of available RBs based on the index of the target relative frequency domain resource index in the list of available RBs.

[0300] In this way, by using local offset index and global frequency domain offset, frequency domain resource conflicts between multiple terminal devices are suppressed at the terminal level and cell level, respectively. The final resource index is determined by modulo operation. The calculation is simple and easy to implement. This not only further reduces the possibility of resource conflicts between multiple terminal devices and maintains the uniform distribution of resources, but also reduces the computational complexity of resource allocation.

[0301] For example, the processing module 610 described above is also used for:

[0302] The target random number is determined by hashing the random access preamble selected by the terminal device according to the target hash algorithm.

[0303] The local offset index is determined by performing a modulo operation between the target random number and the number of optional offsets.

[0304] Thus, since the random access preamble selected by terminal devices within the same cell is usually different, the local offset index determined by hash calculation based on the random access preamble is also usually different. Therefore, by utilizing the randomness of the random access preamble, frequency domain resources among terminal devices are naturally distributed, further reducing the probability of resource conflicts among multiple terminal devices, and without the need for additional signaling overhead.

[0305] For example, the communication module 620 described above is also used for:

[0306] Receive MSG4 from the first cell, wherein MSG4 carries an acknowledgment command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell, wherein the acknowledgment command is used to indicate whether the target relative frequency domain resource index needs to be corrected.

[0307] Accordingly, the aforementioned processing module 610 is also used for:

[0308] If the confirmation command indicates that the target relative frequency domain resource index needs to be corrected, the target relative frequency domain resource index is corrected according to the second global frequency domain offset.

[0309] Thus, by introducing conflict detection and closed-loop correction on the frequency domain resource index reported by the network side, when conflicts occur in the frequency domain resources determined by different terminal devices, the base station is allowed to adjust the frequency domain resources selected by the terminal devices. This further enhances the network's control and reliability over resource allocation, avoids the problem of frequency domain resource conflicts between different terminal devices, and ensures the accuracy of channel estimation.

[0310] For example, the above confirmation command is also used to instruct the terminal device whether to trigger the early SRS / CSI-RS, wherein, when the value of the confirmation command is a first command value, it is used to instruct the terminal device not to trigger the early SRS / CSI-RS; when the value of the confirmation command is a second command value, it is used to instruct the terminal device to trigger the early SRS / CSI-RS without needing to correct the target relative frequency domain resource index; and when the value of the confirmation command is a third command value, it is used to instruct the terminal device to trigger the early SRS / CSI-RS and need to correct the target relative frequency domain resource index.

[0311] In this way, by mapping the confirmation command to different terminal device behaviors (not triggering early SRS / CSI-RS, triggering without needing to modify the resource index, and triggering with needing to modify the resource index), fine-grained control over early SRS / CSI-RS triggering and resource adjustment is achieved, enhancing the system's flexibility and robustness.

[0312] For example, the MSG3 mentioned above is also used to carry a frequency domain capability support identifier corresponding to the terminal device, wherein the frequency domain capability support identifier is used to indicate whether the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index.

[0313] Thus, by carrying a frequency domain capability support identifier in the MSG3, the terminal device can report back to the network side whether it supports the calculated frequency domain resources. This avoids invalid resource allocation caused by the terminal device's frequency domain capability limitations, which would lead to early SRS / CSI-RS triggering failure. This not only improves the accuracy and efficiency of resource allocation, but also avoids the terminal device making invalid early SRS / CSI-RS attempts.

[0314] For example, the aforementioned frequency domain template set contains at least one frequency domain template subset, each frequency domain template subset contains at least one frequency domain template, and the target frequency domain template index information includes a target frequency domain template set identifier and a target frequency domain template index; correspondingly, the aforementioned processing module 610 is also used for:

[0315] Based on the target frequency domain template set identifier, determine the target frequency domain template subset from the frequency domain template set;

[0316] The target frequency domain template is determined from the target frequency domain template subset based on the target frequency domain template index.

[0317] In this way, by organizing the frequency domain templates into multiple subsets and guiding the terminal devices to select them through template set identifiers and template indexes, differentiated resource configurations are supported in multi-band (such as FR1 / FR2) and multi-bandwidth part (BWP) scenarios, thereby improving the scalability and deployment adaptability of resource configuration.

[0318] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0319] In one possible design, the communication device 600 may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device 600 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0320] For example, the communication module 620 is used for:

[0321] In one possible design, the communication module 620 described above is used for:

[0322] Send the target SIB of the first cell to the terminal device. The terminal device is in the process of establishing a connection with the first cell. The target SIB carries the target frequency domain template index information. The target frequency domain template index information is used to instruct the terminal device to determine the target relative frequency domain resource index corresponding to the early SRS / CSI-RS.

[0323] Receive the target relative frequency domain resource index from the terminal device, wherein the target relative frequency domain resource index is carried by MSG3 in the random access procedure. Send the SIB1 corresponding to the target NES cell to the terminal device.

[0324] For example, the target SIB also carries the first global frequency domain offset corresponding to the first cell.

[0325] For example, the processing module 610 described above is also used for:

[0326] Based on whether the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device in the first cell, an acknowledgment command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell are generated. The reference terminal device is any terminal device other than the terminal device in the first cell. The acknowledgment command is used to indicate whether the target relative frequency domain resource index needs to be corrected.

[0327] Accordingly, the aforementioned communication module 620 is also used for:

[0328] Send MSG4 to the terminal device, where MSG4 carries an acknowledgment command and a second global frequency domain offset.

[0329] For example, the MSG3 mentioned above is also used to carry a frequency domain capability support identifier corresponding to the terminal device, wherein the frequency domain capability support identifier is used to indicate whether the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index.

[0330] For example, the above confirmation command is also used to indicate whether the terminal device triggers early SRS / CSI-RS; correspondingly, the above processing module 610 is also used to:

[0331] When the frequency domain capability support flag indicates that the terminal device does not support the frequency domain resources corresponding to the target relative frequency domain resource index, the value of the confirmation command is determined as the first command value, so as to instruct the terminal device not to trigger earlySRS / CSI-RS;

[0332] When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is different from the reference relative frequency domain resource index corresponding to each reference terminal device, the value of the confirmation command is determined as the second command value, so as to instruct the terminal device to trigger early SRS / CSI-RS without needing to correct the target relative frequency domain resource index;

[0333] When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device, the value of the confirmation command is determined as the third command value, and a second global frequency domain offset is generated to indicate that the terminal device triggers early SRS / CSI-RS and that the target relative frequency domain resource index needs to be corrected.

[0334] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

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

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

[0337] Figure 7 This is another schematic block diagram of the apparatus 700 provided in the embodiments of this application. The apparatus 700 may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. The apparatus 700 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.

[0338] like Figure 7As shown, the device 700 may include one or more processors 710, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 710 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 device 700 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

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

[0340] In another alternative design, the device 700 may include a communication interface 720 for implementing receiving and transmitting functions. For example, the communication interface 720 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.

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

[0342] 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.

[0343] In one implementation, the device 700 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 710 may be used to execute instructions stored in the memory 730, and when the processor 710 executes the instructions stored in the memory, the processor 710 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0344] In another implementation, the device 700 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 710 may be used to execute instructions stored in the memory 730, and when the processor 710 executes the instructions stored in the memory, the processor 710 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0345] 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.

[0346] 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.

[0347] 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.

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

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

[0350] 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.

[0351] 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.

[0352] 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.

[0353] 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.

[0354] 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.

[0355] 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.

[0356] 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.

[0357] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to terminal devices, including: The terminal device receives a target system information block (SIB) from a first cell, wherein the terminal device is in the process of establishing a connection with the first cell, and the target SIB carries target frequency domain template index information. Based on the target frequency domain template index information, a target frequency domain template is determined from a pre-stored set of frequency domain templates, wherein the set of frequency domain templates contains at least one frequency domain template, and the frequency domain template is used to describe the determination rules of frequency domain resources; Based on the target frequency domain template, determine the target relative frequency domain resource index corresponding to the early detection reference signal / channel state information reference signal (early SRS / CSI-RS); The target relative frequency domain resource index is sent to the first cell, wherein the target relative frequency domain resource index is carried by the third message MSG3 in the random access procedure.

2. The method as described in claim 1, characterized in that, The target frequency domain template includes the target resource block (RB) index range, target RB granularity, target interleaving mode, number of optional offsets, and target hash algorithm. Determining the target relative frequency domain resource index corresponding to the early SRS / CSI-RS based on the target frequency domain template includes: The target relative frequency domain resource index is determined based on the target RB index range, the target RB granularity, the target interleaving mode, the number of optional offsets, and the target hash algorithm.

3. The method as described in claim 2, characterized in that, The step of determining the target relative frequency domain resource index based on the target RB index range, the target RB granularity, the target interleaving mode, the number of optional offsets, and the target hash algorithm includes: Based on the target RB index range and the target RB granularity, at least one optional RB index is selected from the target RB index range to generate an optional RB list; Based on the target interleaving pattern, at least one available RB index is selected from the list of optional RBs to generate an available RB list and determine the number of available RBs; Based on the target hash algorithm and the number of optional offsets, the local offset index corresponding to the terminal device is determined; The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs and the local offset index.

4. The method as described in claim 3, characterized in that, The target SIB also carries the first global frequency domain offset corresponding to the first cell. The step of determining the target relative frequency domain resource index from the list of available RBs based on the number of available RBs and the local offset index includes: The target relative frequency domain resource index is determined from the list of available RBs based on the number of available RBs, the local offset index, and the first global frequency domain offset.

5. The method as described in claim 4, characterized in that, The step of determining the target relative frequency domain resource index from the list of available RBs based on the number of available RBs, the local offset index, and the first global frequency domain offset includes: The sum of the local offset index and the first global frequency domain offset is moduloed by the number of available RBs to determine the index of the target relative frequency domain resource index in the list of available RBs; The target relative frequency domain resource index is determined from the list of available RBs based on the index of the target relative frequency domain resource index in the list of available RBs.

6. The method as described in claim 3, characterized in that, The step of determining the local offset index corresponding to the terminal device based on the target hash algorithm and the number of optional offsets includes: The target random number is determined by hashing the random access preamble selected by the terminal device according to the target hash algorithm. The target random number is moduloed with the optional offset number to determine the local offset index.

7. The method according to any one of claims 1-6, characterized in that, After sending the target relative frequency domain resource index to the first cell, the method further includes: Receive a fourth message MSG4 from the first cell, wherein the MSG4 carries an acknowledgment command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell, wherein the acknowledgment command is used to indicate whether the target relative frequency domain resource index needs to be corrected; If the confirmation command indicates that the target relative frequency domain resource index needs to be corrected, the target relative frequency domain resource index is corrected according to the second global frequency domain offset.

8. The method as described in claim 7, characterized in that, The confirmation command is further used to instruct the terminal device whether to trigger the early SRS / CSI-RS, wherein, when the confirmation command is set to a first command value, it instructs the terminal device not to trigger the early SRS / CSI-RS; when the confirmation command is set to a second command value, it instructs the terminal device to trigger the early SRS / CSI-RS without needing to correct the target relative frequency domain resource index; and when the confirmation command is set to a third command value, it instructs the terminal device to trigger the early SRS / CSI-RS and requires correction of the target relative frequency domain resource index.

9. The method as described in any one of claims 1-6 or 8, characterized in that, The MSG3 is also used to carry a frequency domain capability support identifier corresponding to the terminal device, wherein the frequency domain capability support identifier is used to indicate whether the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index.

10. The method as described in any one of claims 1-6 or 8, characterized in that, The frequency domain template set contains at least one subset of frequency domain templates, and each subset of frequency domain templates contains at least one frequency domain template. The target frequency domain template index information includes a target frequency domain template set identifier and a target frequency domain template index. Determining the target frequency domain template from the pre-stored frequency domain template set based on the target frequency domain template index information includes: Based on the target frequency domain template set identifier, determine a target frequency domain template subset from the frequency domain template set; The target frequency domain template is determined from the target frequency domain template subset based on the target frequency domain template index.

11. A communication method, characterized in that, Applied to network devices, including: Sending the target SIB of the first cell to the terminal device, wherein the terminal device is in the process of establishing a connection with the first cell, the target SIB carries target frequency domain template index information, and the target frequency domain template index information is used to instruct the terminal device to determine the target relative frequency domain resource index corresponding to the early SRS / CSI-RS; The target relative frequency domain resource index is received from the terminal device, wherein the target relative frequency domain resource index is carried by MSG3 during the random access procedure.

12. The method as described in claim 11, characterized in that, The target SIB also carries the first global frequency domain offset corresponding to the first cell.

13. The method as described in claim 11 or 12, characterized in that, After receiving the target relative frequency domain resource index from the terminal device, the method further includes: Based on whether the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device in the first cell, a confirmation command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell are generated. The reference terminal device is any other terminal device in the first cell other than the terminal device mentioned above. The confirmation command is used to indicate whether the target relative frequency domain resource index needs to be corrected. MSG4 is sent to the terminal device, wherein MSG4 carries the confirmation command and the second global frequency domain offset.

14. The method as described in claim 13, characterized in that, The MSG3 is also used to carry a frequency domain capability support identifier corresponding to the terminal device, wherein the frequency domain capability support identifier is used to indicate whether the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index.

15. The method as described in claim 14, characterized in that, The confirmation command is further used to instruct the terminal device whether to trigger the early SRS / CSI-RS. The step of generating a confirmation command corresponding to the target relative frequency domain resource index and a second global frequency domain offset corresponding to the first cell based on whether the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any reference terminal device in the first cell includes: When the frequency domain capability support identifier indicates that the terminal device does not support the frequency domain resources corresponding to the target relative frequency domain resource index, the value of the confirmation command is determined as the first command value to instruct the terminal device not to trigger the early SRS / CSI-RS; When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is different from the reference relative frequency domain resource index corresponding to each of the reference terminal devices, the value of the confirmation command is determined as the second command value, so as to instruct the terminal device to trigger the early SRS / CSI-RS without needing to correct the target relative frequency domain resource index; When the frequency domain capability support identifier indicates that the terminal device supports the frequency domain resources corresponding to the target relative frequency domain resource index and the target relative frequency domain resource index is the same as the reference relative frequency domain resource index corresponding to any of the reference terminal devices, the value of the confirmation command is determined as the third command value, and the second global frequency domain offset is generated to indicate that the terminal device triggers the early SRS / CSI-RS and that the target relative frequency domain resource index needs to be corrected.

16. one A device characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, wherein the processor executes the program or instructions to cause the device to perform the method as claimed in any one of claims 1 to 10, or the processor executes the program or instructions to cause the device to perform the method as claimed in any one of claims 11 to 15.

17. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 10, or cause the computer to perform the method as described in any one of claims 11 to 15.

18. A communication system, characterized in that, Includes the apparatus as described in claim 16.

19. A chip system, characterized in that, The chip system includes one or more processors, the one or more processors being configured to retrieve and execute instructions stored in memory, such that the method as claimed in any one of claims 1 to 10 is executed, or that the method as claimed in any one of claims 11 to 15 is executed.

20. A computer program product, characterized in that, The computer program product includes: a computer program that, when run, causes a computer to perform the method as described in any one of claims 1 to 10, or causes a computer to perform the method as described in any one of claims 11 to 15.

Images