Access method, apparatus, device, storage medium and program product of RedCap terminal

Abstract

The application relates to an access method and device of a RedCap terminal, equipment, a storage medium and a program product, and relates to the technical field of wireless communication. The method comprises the following steps: in response to searching for a target cell, receiving an SIB1 message issued by the target cell; determining whether the target cell supports RedCap according to the SIB1 message; in the case that the target cell does not support RedCap, determining whether the target cell supports eRedCap according to the SIB1 message; in the case that the target cell supports eRedCap, initiating an eRedCap initial access process for the target cell, and camping on the target cell in an eRedCap mode after the eRedCap initial access process is completed. The method makes the RedCap terminal capable of accessing the network and obtaining data services in an independently deployed eRedCap network, thereby effectively expanding the application scenarios and deployment range of the RedCap terminal.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to an access method, apparatus, computer device, computer-readable storage medium, and computer program product for a RedCap terminal. Background Technology

[0002] With the rapid development of IoT demand, the high price of eMBB (Enhanced Mobile Broadband) terminals and the performance limitations of mMTC (Massive Machine Type Communication) terminals have restricted the large-scale application of 5G terminals in IoT. To address this issue, the 3rd Generation Partnership Project (3GPP) introduced the Lightweight 5G RedCap (Reduced Capability) technology in Release 17. This technology reduces capabilities, costs, and power consumption by trimming eMBB terminal hardware, enabling the large-scale application of 5G technology in scenarios such as video surveillance, industrial sensing, and personal wearables. 3GPP R17 explicitly states that RedCap supports a maximum BWP (Bandwidth Part) bandwidth of 20MHz, antenna cutoff of 1T1R / 1T2R, and defines basic features such as camping, identification, access, and mobility, as well as features such as energy saving, SDT, and coverage enhancement. It also supports 5G native functions such as slicing, uRLLC (Ultra Reliable & Low Latency Communication), and 5G LAN (Local Area Network).

[0003] To further expand the applicability of 5G in lower-speed, lower-cost IoT scenarios (such as industrial wireless sensors and smart wearable devices), 3GPP introduced Enhanced Reduced Capability (eRedCap) terminal technology in Release 18. eRedCap further streamlines terminal hardware capabilities based on RedCap, with performance targets comparable to LTE Cat.1, achieving peak uplink and downlink rates of 10Mbps, significantly reducing terminal complexity and manufacturing costs.

[0004] In the actual deployment of 5G networks, considering initial network construction costs and business development strategies, operators typically only upgrade some 5G base stations to support RedCap or eRedCap functionality. RedCap and eRedCap can be deployed independently in the same 5G network or coexist according to business needs. However, due to protocol limitations, terminals with RedCap capability can only access 5G cells with RedCap enabled, while eRedCap terminals can only access 5G cells supporting eRedCap. The two are incompatible in terms of access mechanisms.

[0005] In this context, when a RedCap-enabled terminal is located in a 5G network coverage area that only has eRedCap functionality deployed, the RedCap terminal will be unable to complete cell selection and camping because the network does not have RedCap functionality enabled, and thus will be unable to obtain any network data services. This seriously affects the applicability of RedCap terminals. Summary of the Invention

[0006] Therefore, it is necessary to provide a RedCap terminal access method, device, computer equipment, computer-readable storage medium, and computer program product to address the aforementioned technical issues, enabling RedCap terminals to access the network and obtain data services in independently deployed eRedCap networks, thereby effectively expanding the applicable scenarios and deployment scope of RedCap terminals.

[0007] Firstly, this application provides a method for accessing a RedCap terminal, including:

[0008] In response to the discovery of the target cell, receive the SIB1 message sent by the target cell;

[0009] Determine whether the target cell supports RedCap based on the SIB1 message;

[0010] If the target cell does not support RedCap, determine whether the target cell supports eRedCap based on the SIB1 message;

[0011] If the target cell supports eRedCap, initiate an eRedCap initial access procedure for the target cell, and after the eRedCap initial access procedure is completed, stay in the target cell in eRedCap mode.

[0012] In one embodiment, after determining whether the target cell supports RedCap based on the SIB1 message, the method further includes:

[0013] If the target cell supports RedCap, initiate the RedCap initial access process for the target cell, and after the RedCap initial access process is completed, stay in the target cell in RedCap mode.

[0014] In one embodiment, after determining whether the target cell supports eRedCap based on the SIB1 message, the method further includes:

[0015] If the target cell does not support eRedCap, search for other cells that meet the signal quality requirements;

[0016] Once the searched cells that meet the signal quality requirements are identified as target cells, the process returns to the step of receiving SIB1 messages sent by the target cells and continues execution.

[0017] In one embodiment, the method further includes:

[0018] Receive system messages sent by the target cell;

[0019] Based on the system message, obtain the access resources corresponding to the current mode; the current mode is either eRedCap mode or RedCap mode.

[0020] Random access is performed based on access resources.

[0021] In one embodiment, after performing random access based on access resources, the method further includes:

[0022] After random access is completed, the terminal capabilities corresponding to the current mode are reported to the network;

[0023] Data transmission is based on terminal capabilities.

[0024] In one embodiment, camping the target cell in eRedCap mode includes:

[0025] The software control strategy adjusts the current operating parameters from a first parameter set to a second parameter set; the first parameter set is used to adapt to the access requirements of the RedCap network, and the second parameter set is used to adapt to the access requirements of the eRedCap network.

[0026] Secondly, this application also provides an access device for a RedCap terminal, comprising:

[0027] The receiving module is used to receive SIB1 messages sent by the target cell in response to the discovery of the target cell;

[0028] The initial access module is used to determine whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, it determines whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, it initiates an eRedCap initial access procedure for the target cell, and after the eRedCap initial access procedure is completed, it camps on the target cell in eRedCap mode.

[0029] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in the first aspect above.

[0030] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect above.

[0031] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in the first aspect above.

[0032] The aforementioned RedCap terminal access method, apparatus, computer equipment, computer-readable storage medium, and computer program product, in response to the discovery of a target cell, receive an SIB1 message sent by the target cell; determine whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, determine whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, initiate an initial eRedCap access procedure for the target cell, and after the initial eRedCap access procedure is completed, camp on the target cell in eRedCap mode. Through this method, the RedCap terminal can adaptively switch its working mode according to the functions supported by the cell. When facing a network coverage area that only supports eRedCap, the RedCap terminal no longer directly disconnects from the network due to access failure or experiences a surge in power consumption due to continuous network searching; instead, it can actively adapt to the eRedCap network and complete camping. This enables the RedCap terminal to access the network and obtain data services in independently deployed eRedCap networks, thereby effectively expanding the applicable scenarios and deployment scope of the RedCap terminal. Attached Figure Description

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

[0034] Figure 1 This is a schematic diagram of the RedCap terminal access process in a traditional solution;

[0035] Figure 2 This is a flowchart illustrating the access method of a RedCap terminal in one embodiment;

[0036] Figure 3 This is a flowchart illustrating the access method for a RedCap terminal in another embodiment;

[0037] Figure 4 This is a structural block diagram of the access device for a RedCap terminal in one embodiment;

[0038] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0040] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the solutions, or any combination of multiple solutions. The term "in response to" used in the embodiments of this application indicates a state in which a corresponding event occurs or a condition is satisfied. It is understood that the timing of the execution of subsequent actions performed in response to the event or condition is not necessarily strongly correlated with the time when the event occurs or the condition is met.

[0041] Understandably, referring to Figure 1 In traditional technology, the RedCap terminal access process includes the following steps:

[0042] 1. After powering on, the RedCap terminal performs a cell search, reads the cell's SSB (Synchronization Signal Block), and receives SIB1 information. The RedCap terminal will determine whether the cell supports RedCap based on the intraFreqReselectionRedCap parameter configuration in the SIB1 (System Information Block 1) information.

[0043] 2. If SIB1 carries the intraFreqReselectionRedCap parameter, the RedCap terminal will determine whether the cell supports RedCap functionality based on the parameter value. If RedCap is detected, the terminal initiates an initial access procedure in that cell, completing terminal authentication, terminal capability reporting, and RRC (Radio Resource Control) reconfiguration. Finally, the terminal camps on that cell.

[0044] 3. If SIB1 does not carry the intraFreqReselectionRedCap parameter or if the parameter value indicates that the cell does not support the RedCap function, the RedCap terminal will be prohibited from accessing the cell. The terminal will search for other cells and determine if any cell supports RedCap. If a cell supports RedCap, the terminal will initiate the access procedure in that cell and camp on that cell. If none of the cells support RedCap, the terminal will be offline.

[0045] Therefore, traditional RedCap terminals can only access cells where RedCap is enabled, and cannot access 5G networks that only enable eRedCap. When a RedCap terminal is deployed on a 5G network with only eRedCap enabled, it cannot access the network, which seriously affects the applicability of RedCap terminals.

[0046] To address this issue, embodiments of this application provide a RedCap terminal access method, apparatus, computer device, computer-readable storage medium, and computer program product. In response to the discovery of a target cell, the method receives an SIB1 message from the target cell; determines whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, determines whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, initiates an initial eRedCap access procedure for the target cell, and camps on the target cell in eRedCap mode after the initial eRedCap access procedure is completed. Through this method, the RedCap terminal can adaptively switch its operating mode according to the functions supported by the cell. When facing a network coverage area that only supports eRedCap, the RedCap terminal no longer directly disconnects from the network due to access failure or experiences a surge in power consumption due to continuous network searching; instead, it can actively adapt to the eRedCap network and complete camping. This enables the RedCap terminal to access the network and obtain data services in independently deployed eRedCap networks, thereby effectively expanding the applicable scenarios and deployment scope of the RedCap terminal.

[0047] In one exemplary embodiment, such as Figure 2 As shown, a method for accessing RedCap terminals is provided. Taking the application of this method to RedCap terminals as an example, the method includes:

[0048] Step 202: In response to the discovery of the target cell, receive the SIB1 message sent by the target cell.

[0049] In this process, after powering on or triggering cell reselection, the RedCap terminal executes a cell search procedure. This cell search procedure can be an initial cell search, i.e., the process by which the terminal establishes contact with the cell through the Synchronization Signal Block (SSB) after powering on, used to obtain downlink frequency, time synchronization, detect the cell ID, and decode broadcast channel system information. The target cell refers to the 5G candidate cell determined by the terminal through the cell search procedure, which it intends to read system information and attempt to access. The SIB1 message is a key system message read by the terminal when accessing a cell in a 5G NR (New Radio) network, and it includes at least access admission configuration parameters for different types of terminals. For example, the SIB1 message includes the intraFreqReselectionRedCap parameter and / or the intraFreqReselectioneRedCap parameter.

[0050] For example, the terminal decodes and reads the SIB1 message from the broadcast channel of the target cell. For instance, according to the scheduling instructions in the Master Information Block (MIB), the terminal demodulates and parses the access admission configuration parameters for different types of terminals carried in the SIB1 on the corresponding Physical Downlink Shared Channel (PDSCH) resource.

[0051] Step 204: Determine whether the target cell supports RedCap based on the SIB1 message.

[0052] Specifically, the terminal parses the access admission configuration parameters for different types of terminals in the SIB1 message and extracts the intraFreqReselectionRedCap field. If the intraFreqReselectionRedCap field exists and its value is allowed, the terminal determines that the target cell supports RedCap. If the intraFreqReselectionRedCap field does not exist or its value is not allowed, the terminal determines that the target cell does not support RedCap.

[0053] The `intraFreqReselectionRedCap` parameter is an indication carried in the SIB1 message, used to indicate whether the cell supports RedCap terminal access. When the `intraFreqReselectionRedCap` parameter is set to "allowed," it means the target cell supports RedCap terminal access, and the RedCap terminal can initiate a random access procedure in this cell. When the `intraFreqReselectionRedCap` parameter is set to "notAllowed," the target cell does not support RedCap terminal access, and the RedCap terminal cannot obtain service in this cell. Optionally, if the `intraFreqReselectionRedCap` parameter is not configured in the SIB1 message, the terminal will also determine that the target cell does not support RedCap.

[0054] Step 206: If the target cell does not support RedCap, determine whether the target cell supports eRedCap based on the SIB1 message.

[0055] In cases where the target cell does not support RedCap, the terminal extracts the intraFreqReselectioneRedCap parameter from the received SIB1 message and determines whether the target cell allows eRedCap terminal access based on the value of the intraFreqReselectioneRedCap parameter.

[0056] The `intraFreqReselectioneRedCap` parameter is an indication carried in the SIB1 message, used to indicate whether the cell supports eRedCap terminal access. When the `intraFreqReselectioneRedCap` parameter is set to "allowed," it means the target cell supports eRedCap terminal access, and the eRedCap terminal can initiate a random access procedure in this cell. When the `intraFreqReselectioneRedCap` parameter is set to "notAllowed," it means the target cell does not support eRedCap terminal access, and the eRedCap terminal cannot obtain service in this cell. Optionally, if the `intraFreqReselectioneRedCap` parameter is not configured in the SIB1 message, the terminal will also determine that the target cell does not support eRedCap.

[0057] The terminal parses the access admission configuration parameters for different types of terminals in the SIB1 message and extracts the intraFreqReselectioneRedCap field. If the intraFreqReselectioneRedCap field exists and its value is allowed, the terminal determines that the target cell supports eRedCap. If the intraFreqReselectioneRedCap field does not exist or its value is not allowed, the terminal determines that the target cell does not support eRedCap.

[0058] Step 208: If the target cell supports eRedCap, initiate the eRedCap initial access procedure for the target cell, and after the eRedCap initial access procedure is completed, camp on the target cell in eRedCap mode.

[0059] The eRedCap initial access procedure refers to a series of signaling interactions performed by the terminal to establish a radio connection with the network. eRedCap mode refers to the operational state in which the terminal operates according to the eRedCap terminal capability specifications. For example, in a 5G NR system, this initial access procedure includes: the terminal sending a preamble to the target cell based on the random access resource configuration information carried in the system message broadcast by the target cell; the target cell returning a random access response to the terminal after receiving the preamble, and allocating a temporary identifier and uplink transmission resources to the terminal; the terminal sending a connection establishment request to the target cell based on the uplink transmission resources; and the target cell returning a connection establishment confirmation to the terminal, completing the connection establishment. Since the terminal has determined that the target cell supports eRedCap, when initiating the initial access procedure, the terminal uses the dedicated access resources configured for eRedCap terminals in the system message broadcast by the target cell to ensure that the target cell can correctly identify the terminal type and perform subsequent scheduling upon receiving the access request.

[0060] When the terminal confirms that the intraFreqReselectioneRedCap field exists and its value is allowed, it enters the eRedCap initial access procedure. After the eRedCap initial access procedure is completed, the radio connection between the terminal and the target cell is successfully established, the terminal completes uplink synchronization with the network side, and has a signaling channel for bidirectional data transmission with the network side. After completing the initial access procedure, the terminal operates according to the eRedCap terminal capability specifications and locks the target cell as its designated camp cell.

[0061] It should be noted that the terminal in this embodiment was originally a RedCap terminal, whose hardware capabilities met the RedCap requirements. eRedCap further reduces hardware capabilities based on RedCap, specifically by: removing support for the FR2 band, locking uplink and downlink peak rates to 10Mbps by limiting the number of physical resource blocks, reducing baseband processor and memory requirements, simplifying modulation, adopting a single-antenna transmission scheme, and optimizing power consumption design. Since the hardware capabilities of eRedCap are not higher than those of RedCap, the hardware capabilities of the RedCap terminal can fully cover the communication requirements of the eRedCap mode. Based on this, the eRedCap mode can be adapted to the eRedCap network by reducing RedCap capabilities. For example, through software control strategies, the terminal's current operating parameters are adjusted from the first parameter set corresponding to RedCap capabilities to the second parameter set corresponding to eRedCap capabilities, so that the terminal presents the eRedCap terminal capability characteristics to the network side during access and camping, thereby achieving normal access and camping in target cells that only support eRedCap.

[0062] For example, after a 5G terminal powers on, it determines the operator network (PLMN, Public Land Mobile Network) and corresponding frequency point to be accessed. It then performs a cell search on the selected frequency point, reads system information broadcast by the base station, and completes downlink synchronization. Based on the system information, it determines whether the cell allows the terminal to access; if so, it camps on that cell. The terminal then initiates a random access procedure, establishes an RRC connection through signaling interaction, completes uplink synchronization, and enters the connected state. After completing uplink and downlink synchronization and establishing the RRC connection, the terminal further completes authentication (verifying the legitimacy of the terminal's identity), encryption (negotiating encryption algorithms to protect signaling and data), terminal capability reporting (informing the network side of the maximum bandwidth, modulation method, and other capability parameters supported by the terminal), and security mode activation. After all the above processes are completed, a service channel is established to realize uplink and downlink data transmission.

[0063] In the aforementioned RedCap terminal access method, in response to the discovery of a target cell, the system receives an SIB1 message from the target cell; determines whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, it determines whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, it initiates an initial eRedCap access procedure for the target cell, and after the initial eRedCap access procedure is completed, it camps on the target cell in eRedCap mode. Through this method, the RedCap terminal can adaptively switch its working mode according to the functions supported by the cell. When facing a network coverage area that only supports eRedCap, the RedCap terminal no longer directly disconnects from the network due to access failure or experiences a surge in power consumption due to continuous network searching; instead, it can actively adapt to the eRedCap network and complete camping. This enables the RedCap terminal to access the network and obtain data services in independently deployed eRedCap networks, thereby effectively expanding the applicable scenarios and deployment scope of the RedCap terminal.

[0064] In an exemplary embodiment, after step 204, the method further includes: if the target cell supports RedCap, initiating a RedCap initial access procedure for the target cell, and after the RedCap initial access procedure is completed, camping on the target cell in RedCap mode.

[0065] If the `intraFreqReselectionRedCap` field exists and its value is "allowed", the terminal determines that the target cell supports RedCap. In this case, the terminal ignores the `intraFreqReselectioneRedCap` parameter and initiates an initial RedCap access procedure for the target cell. The specific process of the initial RedCap access procedure is explained in the aforementioned description of the `eRedCap` initial access procedure, and will not be repeated here. Since the terminal has determined that the target cell supports RedCap, when initiating the initial access procedure, the terminal uses the dedicated access resources configured for RedCap terminals in the system messages broadcast by the target cell to ensure that the target cell can correctly identify the terminal type and perform subsequent scheduling upon receiving the access request.

[0066] After the initial RedCap access procedure is completed, a wireless connection is successfully established between the terminal and the target cell. The terminal completes uplink synchronization with the network side and has a signaling channel for bidirectional data transmission with the network side. After completing the initial access procedure, the terminal operates according to the RedCap terminal capability specifications and locks the target cell as its designated cell.

[0067] In this embodiment, the RedCap terminal can adaptively select the working mode according to the RedCap and eRedCap deployment of the 5G network to adapt to different network deployments and improve the compatibility of the RedCap terminal.

[0068] In an exemplary embodiment, after step 206, the method further includes: if the target cell does not support eRedCap, searching for other cells that meet the signal quality requirements; determining the searched cells that meet the signal quality requirements as the target cell, returning to the step of receiving the SIB1 message sent by the target cell, and continuing execution.

[0069] In this case, if the target cell does not support eRedCap, it means that the target cell is incompatible with both of the terminal's lightweight capabilities, and the terminal cannot access the target cell in either RedCap or eRedCap mode. The terminal restarts the frequency sweep and synchronization signal detection process to search for other cells that meet the signal quality requirements and support RedCap or eRedCap. Optionally, other cells refer to adjacent 5G cells other than the target cell that has been determined to not support RedCap and not support eRedCap. These other cells can be co-frequency neighboring cells, inter-frequency neighboring cells, or inter-system neighboring cells, and the terminal searches based on the measurement frequency information configured in the network.

[0070] After the terminal finds other cells that meet the signal quality requirements, it re-identifies these cells as target cells. In other words, the terminal uses these newly found candidate cells as the objects of subsequent processing. After re-identifying the target cell, the terminal returns to step 202 and continues with the following steps, starting a new round of the loop: re-receiving the SIB1 message of the newly identified target cell, re-determining whether it supports RedCap or eRedCap, until an available cell capable of providing services to the terminal is found.

[0071] Understandably, if the terminal finds a cell that meets the signal quality requirements and supports RedCap or eRedCap, the terminal will camp on that cell according to the corresponding mode. If none of the cells that meet the signal quality requirements support RedCap or eRedCap, the terminal will be unable to camp on the network.

[0072] The terminal performs signal quality measurements on newly discovered candidate cells and compares the results with preset threshold values. If the measurement result meets or exceeds the threshold value, the candidate cell is determined to meet the signal quality requirements. For example, the terminal measures the reference signal received power (RSRP) and / or the signal to interference plus noise ratio (SINR) of the candidate cell. RSRP reflects the strength of the reference signal received by the terminal and is a basic indicator of cell coverage strength; SINR reflects the power ratio of the useful signal received by the terminal to interference and noise and is a comprehensive indicator of signal quality. A higher RSRP value indicates better signal coverage, and a higher SINR value indicates better signal quality. The terminal compares the measured RSRP value with the cell selection receive level threshold broadcast in the system message, and / or compares the measured SINR value with the minimum signal quality threshold broadcast in the system message. If RSRP is not lower than the corresponding threshold and SINR is not lower than the corresponding threshold, the candidate cell is determined to meet the signal quality requirements; if RSRP is lower than the corresponding threshold or SINR is lower than the corresponding threshold, the candidate cell is determined not to meet the signal quality requirements. Optionally, the terminal can also determine whether the candidate cell meets the signal quality requirements based on RSRP (i.e., the S criterion), while using SINR as an auxiliary reference, without requiring simultaneous compliance.

[0073] In this embodiment, through a cyclic search and judgment mechanism, the RedCap terminal can automatically discover and access any available cell that supports RedCap or eRedCap in a fragmented 5G lightweight network deployment environment, thereby maximizing the terminal's network coverage and access success rate.

[0074] In one exemplary embodiment, refer to Figure 3 The RedCap terminal access method includes the following steps:

[0075] 1. After powering on, the RedCap terminal performs a cell search, reads the cell's SSB (Synchronization Signal Block), and receives SIB1 information. The RedCap terminal will determine whether the cell supports RedCap based on the intraFreqReselectionRedCap parameter configuration in the SIB1 (System Information Block 1) information.

[0076] 2. If SIB1 carries the intraFreqReselectionRedCap parameter, the RedCap terminal will determine whether the cell supports the RedCap function based on the parameter value. If the cell supports RedCap, the terminal will initiate an initial access procedure in the cell, complete the terminal authentication, terminal capability reporting, RRC reconfiguration, etc., and finally the terminal will camp in the cell in RedCap mode.

[0077] 3. If SIB1 does not carry the intraFreqReselectionRedCap parameter or if the parameter value indicates that the cell does not support the RedCap function, the RedCap terminal will determine whether the cell supports eRedCap based on the intraFreqReselectioneRedCap parameter configuration in the SIB1 information.

[0078] 4. If SIB1 carries the intraFreqReselectioneRedCap parameter, the RedCap terminal will determine whether the cell supports the eRedCap function based on the parameter value. If the cell supports eRedCap, the terminal will initiate an initial access procedure in the cell, complete the terminal authentication, terminal capability reporting, RRC reconfiguration, etc., and finally the terminal will camp in the cell in eRedCap mode.

[0079] 5. If SIB1 does not carry the intraFreqReselectioneRedCap parameter or if the parameter value indicates that the cell does not support the eRedCap function, the RedCap terminal will search for other cells to determine if there are other cells that meet the signal quality requirements, and continue to determine whether the searched cells support RedCap or eRedCap, until an available cell that can provide services to the terminal is found.

[0080] 6. If the terminal finds a cell that meets the signal quality requirements and supports RedCap or eRedCap, the terminal will camp on that cell in the corresponding mode. If none of the cells that meet the signal quality requirements support RedCap or eRedCap, the terminal will be unable to access the network.

[0081] In an exemplary embodiment, the method further includes: receiving a system message sent by the target cell; obtaining access resources corresponding to the current mode according to the system message; the current mode being eRedCap mode or RedCap mode; and performing random access based on the access resources.

[0082] System messages are periodically broadcast by the target cell via the physical downlink shared channel, carrying configuration parameters related to cell access. For terminals camped in the target cell in eRedCap or RedCap mode, the system messages allocate resources such as the Preamble (MSG1, the first message) and Paging Opportunity (PO) or the LCID (Logical Channel Identity) (MSG3, the third message) for RedCap / eRedCap access. For example, the terminal obtains the access resource allocation for eRedCap or RedCap mode from the initialUplinkBWP-RedCap field of the system message. When data transmission is required, the RedCap terminal performs random access using RedCap or eRedCap access resources based on its current mode (RedCap or eRedCap mode) in the target cell.

[0083] In this embodiment, when data transmission is required, the terminal sends the corresponding preamble on the time-frequency resources of the corresponding physical random access channel according to the access resource configuration corresponding to the current mode to initiate the random access procedure. By configuring different access resources for different operating modes, the base station of the target cell can identify the terminal type according to the resource group to which the preamble belongs when it receives the preamble, and respond with a scheduling strategy adapted to that type, thereby ensuring the smooth progress of the subsequent random access procedure.

[0084] In an exemplary embodiment, after random access is performed based on access resources, the method further includes: after the random access is completed, reporting the terminal capabilities corresponding to the current mode to the network; and performing data transmission based on the terminal capabilities.

[0085] After successfully completing the random access procedure based on the access resources, the terminal reports its capability information corresponding to the current operating mode to the network side via Radio Resource Control (RRC) signaling. Upon confirmation from the network side, data is transmitted based on this capability information. After random access is completed, the terminal completes the random access procedure with the target cell, including preamble transmission, random access response reception, RRC establishment request transmission, and RRC establishment message reception. An RRC connection is successfully established, and the terminal enters the Radio Resource Control (RRC) connection state, gaining the ability to interact with the network side via dedicated signaling.

[0086] For example, after receiving a terminal capability query message from the network side, the terminal reports its own capability parameters to the network side via a terminal capability information message. If the current mode is RedCap mode, the capability information reported by the terminal includes RedCap capability features defined in 3GPP Release 17, such as maximum support for 20MHz bandwidth, support for 2 receive antennas and 1 transmit antenna, and support for a maximum of 256QAM modulation scheme. If the current mode is eRedCap mode, the capability information reported by the terminal includes eRedCap capability features defined in 3GPP Release 18, such as narrower operating bandwidth (e.g., maximum support for 5MHz), uplink and downlink peak rates of 10Mbps, and support for ultra-long discontinuous reception periods. The capability information reported by the terminal strictly corresponds to the actual operating mode used, ensuring that the network side subsequently schedules the network with the correct parameter configuration.

[0087] After receiving and confirming the capability information reported by the terminal, the network side configures suitable radio resources for the terminal based on this information. The terminal then transmits and receives uplink and downlink service data based on the resources configured by the network side. The entire data transmission process follows the scheduling and transmission mechanism for RedCap or eRedCap capabilities defined by the 3GPP protocol.

[0088] In this embodiment, through capability reporting and data transmission processes, the network side can accurately identify the actual working mode and corresponding capability level of the terminal, thereby configuring wireless resources and scheduling strategies that precisely match the capabilities of the terminal. This avoids resource waste caused by over-configuration and transmission failure caused by insufficient resource configuration, ensuring the reliability and efficiency of data transmission.

[0089] In an exemplary embodiment, camping on a target cell in eRedCap mode includes: adjusting the current operating parameters from a first parameter set to a second parameter set through a software control policy; wherein the first parameter set is used to adapt to the access requirements of the RedCap network, and the second parameter set is used to adapt to the access requirements of the eRedCap network.

[0090] Software control strategy refers to a control method in which the terminal adjusts its working state and operating parameters by executing preset software instructions or algorithms. This process does not involve changes to the terminal's hardware architecture, replacement of the radio frequency antenna, or addition or removal of hardware components. It is loaded and executed by the terminal's processor, and parameter adjustments are achieved by modifying the configuration parameters in the protocol stack. Compared with hardware modification solutions, this strategy has advantages such as low implementation cost, flexible deployment, and strong reversibility, and can complete capability adaptation without changing the terminal's physical structure.

[0091] Current operating parameters refer to the various protocol layer configuration parameters used by the terminal during its current operation, including but not limited to: physical layer operating bandwidth parameters (such as maximum supported bandwidth), radio frequency front-end antenna configuration parameters (such as the number of downlink receiving antennas), MAC (Medium Access Control) layer scheduling parameters (such as maximum transport block size), and RRC layer capability reporting parameters (such as terminal type identifier and bandwidth combination identifier). These parameters collectively determine the terminal's capability level and behavioral characteristics when accessing the network.

[0092] The first parameter set refers to the set of parameter configurations used by a RedCap terminal in its default operating state or when running in RedCap mode. This parameter set is used to adapt to the access requirements of the RedCap network. When the terminal runs with the first parameter set, it uses RedCap-specific preamble packets and physical random access channel resources during the random access phase. On the network side, it appears as a standard R17 RedCap terminal and can normally access cells with RedCap enabled.

[0093] The second parameter set refers to the set of parameter configurations adopted by the RedCap terminal after adjustment by the software control strategy. This parameter set is used to adapt to the access requirements of the eRedCap network. When the terminal operates with the second parameter set, it uses eRedCap-dedicated preamble packets and physical random access channel resources during the random access phase. On the network side, it appears as a terminal conforming to the R18 eRedCap standard, capable of normally accessing cells with only eRedCap functionality enabled, and submitting matching capability parameters to the network side in the subsequent capability reporting process.

[0094] It should be noted that since the terminal hardware itself possesses RF and baseband processing capabilities that meet the RedCap capability specifications, and the eRedCap capability standard is a subset of RedCap capabilities, adjusting from the first parameter set to the second parameter set is a capability degradation operation, which is fully supported at the hardware level and requires no physical modification. Software control strategies are implemented only by modifying protocol stack configuration parameters and limiting scheduling resources; the hardware processing capabilities themselves do not change, but are constrained within a smaller range during use. For example, the terminal can disable some baseband processing channels to limit the receive bandwidth, or limit the maximum transmit block size scheduled by the MAC layer through software algorithms, thereby reducing the peak rate.

[0095] For example, the terminal limits the uplink / downlink operating bandwidth from 20MHz to 5MHz by modifying the bandwidth configuration register value stored in the baseband chip; the terminal modifies the bandwidth factor parameter in the RRC layer capability information field to make the terminal capability information reported subsequently exhibit eRedCap characteristics; the terminal modifies the MAC layer scheduling parameters to limit the maximum transport block size corresponding to the scheduling request (SR) and buffer status report (BSR); and the terminal modifies the terminal type identifier field in the NV storage to make the terminal run with the eRedCap parameter set by default during subsequent power-on or reselection processes.

[0096] In this embodiment, through software control strategies, the terminal achieves a smooth downgrade adaptation from RedCap capability to eRedCap capability, enabling the terminal, which originally only supports RedCap mode, to complete access and camping in a 5G cell with only eRedCap function enabled, thus expanding the network applicability of the terminal.

[0097] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0098] Based on the same inventive concept, this application also provides an access device for a RedCap terminal to implement the access method for the RedCap terminal described above. The solution provided by this device is similar to the implementation described in the above method. Therefore, the specific limitations of one or more RedCap terminal access device embodiments provided below can be found in the limitations of the RedCap terminal access method described above, and will not be repeated here.

[0099] In one exemplary embodiment, such as Figure 4 As shown, an access device for a RedCap terminal is provided, comprising:

[0100] The receiving module 402 is used to receive the SIB1 message sent by the target cell in response to the search for the target cell;

[0101] The initial access module 404 is used to determine whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, it determines whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, it initiates an eRedCap initial access procedure for the target cell, and after the eRedCap initial access procedure is completed, it camps on the target cell in eRedCap mode.

[0102] In the aforementioned RedCap terminal access device, the RedCap terminal can adaptively switch its working mode according to the functions supported by the cell. When facing a network coverage area that only supports eRedCap, the RedCap terminal no longer directly disconnects from the network due to access failure or experiences a surge in power consumption due to continuous network searching. Instead, it can actively adapt to the eRedCap network and complete its camping. This enables the RedCap terminal to access the network and obtain data services in an independently deployed eRedCap network, thereby effectively expanding the applicable scenarios and deployment scope of the RedCap terminal.

[0103] In an exemplary embodiment, the initial access module 404 is further configured to initiate a RedCap initial access procedure for the target cell if the target cell supports RedCap, and to camp on the target cell in RedCap mode after the RedCap initial access procedure is completed.

[0104] In an exemplary embodiment, the initial access module 404 is further configured to search for other cells that meet the signal quality requirements if the target cell does not support eRedCap; determine the searched cell that meets the signal quality requirements as the target cell; return to the step of receiving the SIB1 message sent by the target cell and continue execution.

[0105] In an exemplary embodiment, the apparatus further includes a random access module, which is configured to receive system messages sent by the target cell; obtain access resources corresponding to the current mode according to the system messages; the current mode is eRedCap mode or RedCap mode; and perform random access based on the access resources.

[0106] In one exemplary embodiment, the device further includes a data transmission module, which is used to report the terminal capabilities corresponding to the current mode to the network after random access is completed; and to perform data transmission based on the terminal capabilities.

[0107] In an exemplary embodiment, the initial access module 404 is further configured to adjust the current operating parameters from a first parameter set to a second parameter set through a software control strategy; wherein the first parameter set is used to adapt to the access requirements of the RedCap network, and the second parameter set is used to adapt to the access requirements of the eRedCap network.

[0108] Each module in the aforementioned multi-objective path planning device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0109] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 5As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a RedCap terminal access method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0110] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0111] In one exemplary embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps: in response to the discovery of a target cell, receiving an SIB1 message sent by the target cell; determining whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, determining whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, initiating an eRedCap initial access procedure for the target cell, and camping on the target cell in eRedCap mode after the eRedCap initial access procedure is completed.

[0112] In one embodiment, when the processor executes the computer program, it further performs the following steps: if the target cell supports RedCap, it initiates a RedCap initial access procedure for the target cell, and after the RedCap initial access procedure is completed, it camps on the target cell in RedCap mode.

[0113] In one embodiment, when the processor executes the computer program, it further implements the following steps: if the target cell does not support eRedCap, it searches for other cells that meet the signal quality requirements; it identifies the searched cells that meet the signal quality requirements as the target cell, returns to the step of receiving the SIB1 message sent by the target cell, and continues execution.

[0114] In one embodiment, when the processor executes the computer program, it further performs the following steps: receiving a system message sent by the target cell; obtaining the access resources corresponding to the current mode according to the system message; the current mode is eRedCap mode or RedCap mode; and performing random access based on the access resources.

[0115] In one embodiment, when the processor executes the computer program, it also performs the following steps: after random access is completed, it reports the terminal capabilities corresponding to the current mode to the network; and performs data transmission based on the terminal capabilities.

[0116] In one embodiment, when the processor executes the computer program, it further performs the following steps: adjusting the current operating parameters from a first parameter set to a second parameter set through a software control strategy; wherein the first parameter set is used to adapt to the access requirements of the RedCap network, and the second parameter set is used to adapt to the access requirements of the eRedCap network.

[0117] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon. When executed by a processor, the computer program performs the following steps: in response to the discovery of a target cell, receiving an SIB1 message sent by the target cell; determining whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, determining whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, initiating an eRedCap initial access procedure for the target cell, and camping on the target cell in eRedCap mode after the eRedCap initial access procedure is completed.

[0118] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: if the target cell supports RedCap, initiates a RedCap initial access procedure for the target cell, and after the RedCap initial access procedure is completed, camps on the target cell in RedCap mode.

[0119] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: if the target cell does not support eRedCap, searching for other cells that meet the signal quality requirements; determining the searched cell that meets the signal quality requirements as the target cell, returning to the step of receiving the SIB1 message sent by the target cell and continuing execution.

[0120] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: receiving a system message sent by the target cell; obtaining the access resources corresponding to the current mode according to the system message; the current mode is eRedCap mode or RedCap mode; and performing random access based on the access resources.

[0121] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: after random access is completed, it reports the terminal capabilities corresponding to the current mode to the network; and performs data transmission based on the terminal capabilities.

[0122] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: adjusting the current operating parameters from a first parameter set to a second parameter set through a software control strategy; wherein the first parameter set is used to adapt to the access requirements of the RedCap network, and the second parameter set is used to adapt to the access requirements of the eRedCap network.

[0123] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps: in response to the discovery of a target cell, receiving an SIB1 message sent by the target cell; determining whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, determining whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, initiating an eRedCap initial access procedure for the target cell, and camping on the target cell in eRedCap mode after the eRedCap initial access procedure is completed.

[0124] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: if the target cell supports RedCap, initiates a RedCap initial access procedure for the target cell, and after the RedCap initial access procedure is completed, camps on the target cell in RedCap mode.

[0125] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: if the target cell does not support eRedCap, searching for other cells that meet the signal quality requirements; determining the searched cell that meets the signal quality requirements as the target cell, returning to the step of receiving the SIB1 message sent by the target cell and continuing execution.

[0126] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: receiving a system message sent by the target cell; obtaining the access resources corresponding to the current mode according to the system message; the current mode is eRedCap mode or RedCap mode; and performing random access based on the access resources.

[0127] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: after random access is completed, it reports the terminal capabilities corresponding to the current mode to the network; and performs data transmission based on the terminal capabilities.

[0128] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: adjusting the current operating parameters from a first parameter set to a second parameter set through a software control strategy; wherein the first parameter set is used to adapt to the access requirements of the RedCap network, and the second parameter set is used to adapt to the access requirements of the eRedCap network.

[0129] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0130] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0131] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0132] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for accessing a RedCap terminal, characterized in that, The method includes: In response to the discovery of a target cell, receive the SIB1 message sent by the target cell; Determine whether the target cell supports RedCap based on the SIB1 message; If the target cell does not support RedCap, determine whether the target cell supports eRedCap based on the SIB1 message; If the target cell supports eRedCap, initiate an eRedCap initial access procedure for the target cell, and after the eRedCap initial access procedure is completed, camp on the target cell in eRedCap mode.

2. The method according to claim 1, characterized in that, After determining whether the target cell supports RedCap based on the SIB1 message, the method further includes: If the target cell supports RedCap, initiate a RedCap initial access procedure for the target cell, and after the RedCap initial access procedure is completed, camp on the target cell in RedCap mode.

3. The method according to claim 1, characterized in that, After determining whether the target cell supports eRedCap based on the SIB1 message, the method further includes: If the target cell does not support eRedCap, search for other cells that meet the signal quality requirements; Once the searched cell that meets the signal quality requirements is identified as the target cell, the process returns to the step of receiving the SIB1 message sent by the target cell and continues execution.

4. The method according to claim 2, characterized in that, The method further includes: Receive system messages sent by the target cell; According to the system message, obtain the access resources corresponding to the current mode; the current mode is the eRedCap mode or the RedCap mode; Random access is performed based on the access resources.

5. The method according to claim 4, characterized in that, After performing random access based on the access resources, the method further includes: After random access is completed, the terminal capabilities corresponding to the current mode are reported to the network; Data transmission is performed based on the terminal's capabilities.

6. The method according to any one of claims 1 to 5, characterized in that, The method of camping the target cell in eRedCap mode includes: The software control strategy adjusts the current operating parameters from a first parameter set to a second parameter set; wherein the first parameter set is used to adapt to the access requirements of the RedCap network, and the second parameter set is used to adapt to the access requirements of the eRedCap network.

7. An access device for a RedCap terminal, characterized in that, The device includes: The receiving module is used to receive the SIB1 message sent by the target cell in response to the search for the target cell; The initial access module is used to determine whether the target cell supports RedCap based on the SIB1 message; if the target cell does not support RedCap, it determines whether the target cell supports eRedCap based on the SIB1 message; if the target cell supports eRedCap, it initiates an eRedCap initial access procedure for the target cell, and after the eRedCap initial access procedure is completed, it camps on the target cell in eRedCap mode.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images