Direct communication discovery method and device for lightweight terminal, equipment and medium
By obtaining the SIB12 message sent by the base station, it determines whether the NW side supports NR SL discovery, which solves the problem that the RedCap UE cannot perform NR SL discovery due to the failure of the NW side to support NR SL discovery, and realizes the effective execution of the NR SL discovery connection establishment/recovery process of the RedCap UE.
Patent Information
- Application Number
- CN202311680871.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-07
- Publication Date
- 2025-06-10
AI Technical Summary
In the prior art, if the NW side does not support NR SL discovery, it will cause the RedCap UE to ultimately fail to perform NR SL discovery.
By obtaining the SIB12 message sent by the base station, it is determined whether the base station side supports new air-port direct connection communication of the lightweight terminal. If supported, the NR Sidelink communication/discovered RRC connection establishment or recovery process will be performed.
It effectively avoids NR SL discovery transmission failure, ensuring that the RedCap UE can perform the NR SL RRC connection establishment/recovery process.
Smart Images

Figure CN120129090A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technologies, and in particular, to a direct communication discovery method, apparatus, device, and medium for lightweight terminals. Background Art
[0002] With the continuous deployment and wide application of 5G systems, in order to better meet the specific requirements of mid-range Internet of Things applications such as industrial wireless sensors, video surveillance, and wearable devices for reducing device complexity and cost, reducing size, and lowering energy consumption, in Release 17, in order to further reduce terminal complexity and cost, 3GPP defined lightweight terminals (RedCap UEs).
[0003] In the prior art, according to the current definition of 3GPP, when a RedCap UE is configured for transmitting NR SL discovery and the SIB12 message contains the authorized frequency for NR SL discovery transmission, the RedCap UE will perform an RRC connection establishment / resumption process to request NR SL discovery resources.
[0004] However, if the NW side (gNB) does not support NR SL discovery, it will inevitably result in the RedCap UE ultimately being unable to perform NR SL discovery. Summary of the Invention
[0005] This application provides a direct communication discovery method, apparatus, device, and medium for lightweight terminals, which is used to solve the problem that if the existing NW side does not support NR SL discovery, the RedCap UE will ultimately be unable to perform NR SL discovery.
[0006] In a first aspect, an embodiment of this application provides a direct communication discovery method for lightweight terminals, which is applied to lightweight terminals. The method includes:
[0007] Obtain the SIB12 message sent by the base station;
[0008] Before the lightweight terminal performs a target operation, determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message. The target operation is an RRC connection establishment process for NR Sidelink communication / discovery or an RRC connection resumption process for NR Sidelink communication / discovery;
[0009] When the base station side supports the new radio direct communication of the lightweight terminal, perform the target operation.
[0010] In a possible design of the first aspect, the determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message includes:
[0011] Check the SIB12 message to determine whether the base station side supports at least one of layer 2 terminal-to-network relay discovery, layer 3 terminal-to-network relay discovery, and non-relay discovery;
[0012] If the base station side supports at least one of layer 2 terminal-to-network relay discovery, layer 3 terminal-to-network relay discovery, and non-relay discovery, it is determined that the base station side supports the new radio direct communication of the lightweight terminal.
[0013] In another possible design of the first aspect, before the lightweight terminal executes the RRC connection establishment process for NR Sidelink communication / discovery, according to the SIB12 message, determining whether the base station side supports the new radio direct communication of the lightweight terminal includes:
[0014] Check the SIB12 message. If the first condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The first condition includes in sequence:
[0015] (1) The sl-FreqInfoList field is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0016] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink communication and the relevant data for transmission is available;
[0017] (3) The frequency points configured for the lightweight terminal to transmit NR Sidelink communication are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell of the relevant frequency points is not included in the valid version of the SIB12 message
[0018] In yet another possible design of the first aspect, before the lightweight terminal executes the RRC connection establishment process for NR Sidelink communication / discovery, according to the SIB12 message, determining whether the base station side supports the new radio direct communication of the lightweight terminal includes:
[0019] Check the SIB12 message. If the second condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The second condition includes in sequence:
[0020] (1) The side link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0021] (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0022] (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the sl-L2U2N-Relay field is included in the SIB12 message;
[0023] (4) The layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1.
[0024] In another possible design of the first aspect, before the lightweight terminal performs the RRC connection establishment procedure for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message includes:
[0025] Checking the SIB12 message, if the third condition is satisfied, it is determined that the base station side supports the new radio direct communication of the lightweight terminal, and the third condition includes in sequence:
[0026] (1) The side link frequency list is included in the cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal;
[0027] (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0028] (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink layer 3 U2N relay discovery message, and the sl-L3U2N-RelayDiscovery field is included in the SIB12 message.
[0029] In another possible design of the first aspect, before the lightweight terminal performs the RRC connection establishment procedure for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message includes:
[0030] Checking the SIB12 message, if the fourth condition is satisfied, it is determined that the base station side supports the new radio direct communication of the lightweight terminal, and the fourth condition includes in sequence:
[0031] (1) The side link frequency list is included in the cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal;
[0032] (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0033] (3) The lightweight terminal is configured by the higher layer to transmit NR Sidelink non-relay discovery messages, and the sl-NonRelayDiscovery field is included in the SIB12 message;
[0034] (4) The frequency points configured for the lightweight terminal to transmit NR Sidelink discovery are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and sl-TxPoolSelectedNormal cell of the relevant frequency points are not included in the valid version of the SIB12 message.
[0035] In another possible design of the first aspect, before the lightweight terminal performs the RRC connection recovery process for NR Sidelink communication / discovery, determining whether the base station side supports the New Radio Sidelink communication of the lightweight terminal according to the SIB12 message includes:
[0036] Checking the SIB12 message, if the fifth condition is met, it is determined that the base station side supports the New Radio Sidelink communication of the lightweight terminal. The fifth condition includes in turn:
[0037] (1) The sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0038] (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink communication and the relevant data for transmission is available;
[0039] (3) The frequency points configured for the lightweight terminal to transmit NR Sidelink communication are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell of the relevant frequency points is not included in the valid version of the SIB12 message.
[0040] In another possible design of the first aspect, before the lightweight terminal performs the RRC connection recovery process for NR Sidelink communication / discovery, determining whether the base station side supports the New Radio Sidelink communication of the lightweight terminal according to the SIB12 message includes:
[0041] Check the SIB12 message. If the sixth condition is satisfied, it is determined that the base station side supports the New Radio (NR) sidelink direct communication of the lightweight terminal. The second condition includes, in sequence:
[0042] (1) The cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0043] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0044] (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the SIB12 message contains the sl-L2U2N-Relay field.
[0045] In another possible design of the first aspect, before the lightweight terminal performs the RRC connection restoration process for NR Sidelink communication / discovery, determining whether the base station side supports the NR sidelink direct communication of the lightweight terminal according to the SIB12 message includes:
[0046] Check the SIB12 message. If the seventh condition is satisfied, it is determined that the base station side supports the NR sidelink direct communication of the lightweight terminal. The seventh condition includes, in sequence:
[0047] (1) The cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0048] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0049] (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 3 U2N relay discovery message, and the SIB12 message contains the sl-L3U2N-RelayDiscovery field.
[0050] In another possible design of the first aspect, before the lightweight terminal performs the RRC connection restoration process for NR Sidelink communication / discovery, determining whether the base station side supports the NR sidelink direct communication of the lightweight terminal according to the SIB12 message includes:
[0051] Check the SIB12 message. If the eighth condition is satisfied, it is determined that the base station side supports the NR sidelink direct communication of the lightweight terminal. The eighth condition includes, in sequence:
[0052] (1) The cell sl-ConfigCommonNR in the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0053] (2) The lightweight terminal is configured by a higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0054] (3) The lightweight terminal is configured by a higher layer to transmit an NR Sidelink non-relay discovery message, and the SIB12 message contains the sl-NonRelayDiscovery field;
[0055] (4) The frequency points configured for the lightweight terminal to transmit NR Sidelink discovery are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell related to the frequency points are not included in the valid version of the SIB12 message.
[0056] In a second aspect, an apparatus for direct communication discovery of a lightweight terminal provided by an embodiment of the present application includes:
[0057] An information acquisition module, configured to acquire the SIB12 message sent by the base station;
[0058] A determination module, configured to determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message before the lightweight terminal performs a target operation, where the target operation is an RRC connection establishment process for NR Sidelink communication / discovery or an RRC connection recovery process for NR Sidelink communication / discovery;
[0059] An operation execution module, configured to perform the target operation when the base station side supports the new radio direct communication of the lightweight terminal.
[0060] In a third aspect, an embodiment of the present application provides a terminal device, including: a processor, and a memory communicatively connected to the processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the method as described above.
[0061] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored, and when the computer execution instructions are executed by a processor, they are used to implement the method as described above.
[0062] The direct communication discovery method, apparatus, device, and medium for a lightweight terminal provided by an embodiment of this application improve the operations of a RedCap UE after receiving an SIB12 message, and redefine the connection establishment / resumption execution mechanism for NR SL discovery, enabling the RedCap UE to effectively execute the RRC connection establishment / resumption process for NR SL and avoiding NR SL discovery transmission failures. Description of the Drawings
[0063] The drawings herein are incorporated into the specification and form a part of this specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application;
[0064] Figure 1 It is a schematic diagram of the application scenario of the RedCap UE provided by an embodiment of this application;
[0065] Figure 2 It is a schematic flowchart of the direct communication discovery method for a lightweight terminal provided by an embodiment of this application;
[0066] Figure 3 It is a schematic diagram of the RRC connection establishment process provided by an embodiment of this application;
[0067] Figure 4 It is a schematic diagram of the RRC connection resumption process provided by an embodiment of this application;
[0068] Figure 5 It is a schematic diagram of the structure of the direct communication discovery apparatus for a lightweight terminal provided by an embodiment of this application;
[0069] Figure 6 It is a schematic diagram of the structure of the terminal device provided by an embodiment of this application;
[0070] Through the above drawings, the clear embodiments of this application have been shown, and there will be more detailed descriptions later. These drawings and textual descriptions are not intended to limit the scope of the concept of this application in any way, but to illustrate the concept of this application to those skilled in the art by referring to specific embodiments. Detailed Embodiments
[0071] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the drawings in the embodiments of this application. Obviously, the described embodiments are some, but not all, of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without creative efforts shall fall within the scope of protection of this application.
[0072] With the continuous deployment and wide application of 5G systems, in order to better meet the specific requirements of mid-range Internet of Things applications such as industrial wireless sensors, video surveillance, and wearable devices for reduced device complexity, cost, size, and lower energy consumption, in Release 17, the 3GPP defined Reduced Capability User Equipment (RedCap UE) to further reduce the complexity and cost of terminals. In addition, sidelink (SL) communication, that is, direct communication, has also been widely applied with the development of 5G mobile communication technology. Introducing the sidelink function in Reduced Capability User Equipment (RedCap UE), namely Sidelink RedCap, as the clearly defined RedCap evolution (eRedCap) technology direction by the 3GPP, is beneficial to expanding the usage scenarios of RedCap terminals. For example, RedCap UE can directly perform short-range information interaction through sidelink technology. In addition, using sidelink technology can also help RedCap UE relay information to network devices, enhance coverage, and achieve the purpose of power saving.
[0073] Currently, according to the definition of the 3GPP, when a RedCap UE is configured to transmit New Radio (NR) SL discovery and the SIB12 message contains the authorized frequency for NR SL discovery transmission, the RedCap UE will perform a Radio Resource Control (RRC) connection establishment / resumption procedure to request NR SL discovery resources. However, if the network (NW) side (the network side can be a 5G base station (next generation Node B, gNB)) does not support NR SL discovery, it will inevitably lead to the RedCap UE ultimately being unable to perform NR SL discovery.
[0074] In response to the above situation where the NW does not support the NR SL discovery of the RedCap UE, resulting in the ineffective execution of the connection establishment / resumption procedure for NR SL discovery, the inventor creatively improved the operation of the RedCap UE after receiving the SIB12 message, redefining the connection establishment / resumption execution mechanism for NR SL discovery, enabling the RedCap UE to effectively execute the RRC connection establishment / resumption procedure for NR SL and avoiding the failure of NR SL discovery transmission.
[0075] Exemplarily, Figure 1 This is a schematic diagram of the application scenario of the RedCap UE provided in the embodiment of this application. RedCap focuses on application scenarios such as industrial wireless sensors, wearable devices, and video surveillance, such asFigure 1 As shown, taking the lightweight terminal as a wearable device as an example, when the lightweight terminal is configured to transmit NR SL discovery and the SIB12 message contains the authorized frequency for NR SL discovery transmission, the lightweight terminal will perform the RRC connection establishment / resumption process to request NR SL discovery resources.
[0076] Next, the technical solution of the present application will be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.
[0077] Figure 2 FIG. is a schematic flowchart of a direct communication discovery method for a lightweight terminal provided by an embodiment of the present application. This method can be applied to a lightweight terminal, where the lightweight terminal can specifically include a wearable device (such as a watch), a video surveillance device (such as a wireless camera). As Figure 2 shown, the method can specifically include the following steps:
[0078] Step S201, obtain the SIB12 message sent by the base station.
[0079] In this embodiment, the system message is the system configuration and access messages broadcast by the wireless network to the terminal through the broadcast control channel (BCCH). The system message is the link connecting the UE and the network. Through the transmission of the system message, the completion of wireless communication can be ensured. There are different types of system information blocks, which can be specifically distinguished according to SIB1, SIB2,..., SIB12, etc. Among them, the SIB12 message contains information related to NR sidelink communication. The lightweight terminal can receive and store the SIB12 message sent by the gNB, and based on the SIB12 message, perform the connection establishment / resumption process for NR SL discovery.
[0080] Step S202, before the lightweight terminal performs the target operation, determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message. The target operation is the RRC connection establishment process for NR Sidelink communication / discovery, or the RRC connection resumption process for NR Sidelink communication / discovery.
[0081] Step S203, when the base station side supports the new radio direct communication of the lightweight terminal, perform the target operation.
[0082] In this embodiment, since the SIB12 message contains information related to NR sidelink communication, based on the SIB12 message, it can be confirmed whether the NW side (gNB) supports NR SL discovery. If the base station side does not support NR SL discovery, it will inevitably lead to the RedCap UE being unable to perform NR SL discovery ultimately, resulting in the ineffective execution of the connection establishment / recovery process of NR SL discovery.
[0083] Furthermore, in some other embodiments, it can be based on the operations defined by 3GPP after the UE side receives the SIB12 message, specifically including at least one of the following operations:
[0084] Definition 1: During the RRC connection establishment process for NR Sidelink communication / discovery, add a conditional judgment to check the SIB12 message to determine whether the network (gNB) supports layer 2 UE to Network (U2N) relay discovery, or layer 3 U2N relay discovery, or non-relay discovery.
[0085] Definition 2: During the RRC connection recovery process for NR Sidelink communication / discovery, add a conditional judgment to check the SIB12 message to determine whether the network (gNB) supports layer 2 U2N relay discovery, or layer 3 U2N relay discovery, or non-relay discovery.
[0086] In this embodiment, taking the NW side as a 5G base station as an example, using the Sidelink technology can help the RedCap UE relay information to network devices, enhance coverage, and achieve the purpose of power saving. If the NW side does not support NR SL discovery, it will inevitably lead to the RedCap UE being unable to perform NR SL discovery ultimately, resulting in the ineffective execution of the connection establishment / recovery process of NR SL discovery. Among them, by adding a conditional judgment, if the conditions in Definition 1 or Definition 2 are met, the subsequent RRC connection establishment process or RRC connection recovery process can be continued, and the ineffective execution of the connection establishment / recovery process of NR SL discovery can be avoided.
[0087] Embodiment 1
[0088] This embodiment will elaborate on the conditions in the above definitions. First, after the RedCap UE receives and stores the SIB12 message sent by the gNB, before sending the RRC connection establishment request for NR Sidelink communication / discovery, perform the conditional determination in Definition 1 above:
[0089] (1) Determine whether the sl-FreqInfoList field is included in the sl-ConfigCommonNR cell of the SIB12 message received by the RedCap UE;
[0090] (2) Determine that the RedCap UE is configured by the higher layer to transmit NR Sidelink communication and the relevant data for transmission is available;
[0091] (3) Determine that the frequency band configured for the UE to transmit NR Sidelink communication is included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located; and the sl-TxPoolSelectedNormal cell of the relevant frequency band is not included in the valid version of the SIB12 message;
[0092] (2) Determine that the RedCap UE is configured by the higher layer to transmit NR Sidelink discovery and the relevant data for transmission is available;
[0093] (3) Determine that the UE is configured by the higher layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the sl-L2U2N-Relay field is included in the SIB12 message; or
[0094] (4) Determine that the layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1;
[0095] (3) Determine that the UE is configured by the higher layer to transmit the NR Sidelink layer 3 U2N relay discovery message and the sl-L3U2N-RelayDiscovery field is included in the SIB12 message; or
[0096] (3) Determine that the UE is configured by the higher layer to transmit the NR Sidelink non-relay discovery message and the sl-NonRelayDiscovery field is included in the SIB12 message:
[0097] (4) Determine that the frequency band configured for the UE to transmit NR Sidelink discovery is included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located; and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell of the relevant frequency band are not included in the valid version of the SIB12 message.
[0098] Among them, according to the determination hierarchy, it can be divided into four layers. The first layer includes condition (1), the second layer includes condition (2), the third layer includes condition (3), and the fourth layer includes condition (4). There may be parallel conditions in each layer. For example, there are two parallel conditions (2) in the second layer. According to the upper and lower order of the conditions, after any condition in the upper layer is satisfied, then enter the lower layer to determine whether any condition in the lower layer is satisfied. Thus, from the top layer to the bottom layer step by step, the entire determination process is completed.
[0099] In this embodiment, "sl-FreqInfoList" is a configuration item mainly used for setting frequency-related information of NR Sidelink communication. "TxPoolSelectedNormal" means the transmission resource pool is normal (Transmission PoolSelected Normal, TxPoolSelectedNormal), and the RRC_IDLE state means that the layer 2 U2N relay UE is in the idle state. Both SL-RLC0 and SL-RLC1 are data link layer protocols in the Sidelink communication protocol. Their main function is to provide a reliable transmission service for the transmission of data packets, ensuring the orderliness, reliability, etc. of the data packets.
[0100] In this embodiment, according to the above method of making layer-by-layer determination of conditions from the top layer to the bottom layer, due to the different conditions configured in each layer (for example, there are two parallel conditions configured in the second layer, and only one of them needs to be satisfied to enter the next layer), multiple paths can be divided when making condition determination from the top layer to the bottom layer, taking four paths (represented by the first condition, the second condition, the third condition, and the fourth condition). Among them, the first condition includes:
[0101] (1) The sl-FreqInfoList field is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0102] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink communication and the relevant data for transmission is available;
[0103] (3) The frequency points configured for the lightweight terminal to transmit NR Sidelink communication are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell of the relevant frequency points is not included in the valid version of the SIB12 message.
[0104] The second condition includes:
[0105] (1) The cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0106] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0107] (3) The lightweight terminal is configured by the upper layer to transmit an NR Sidelink layer 2 U2N relay discovery message and the SIB12 message contains the sl-L2U2N-Relay field;
[0108] (4) The layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1.
[0109] The third condition includes:
[0110] (1) The cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0111] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0112] (3) The lightweight terminal is configured by the upper layer to transmit an NR Sidelink layer 3 U2N relay discovery message, and the SIB12 message contains the sl-L3U2N-RelayDiscovery field.
[0113] The fourth condition includes:
[0114] (1) The cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0115] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0116] (3) The lightweight terminal is configured by the upper layer to transmit an NR Sidelink non-relay discovery message, and the SIB12 message contains the sl-NonRelayDiscovery field;
[0117] (4) It is configured to lightweight the frequency points for terminal transmission of NR Sidelink discovery, which are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell related to the frequency points are not included in the valid version of the SIB12 message.
[0118] Figure 3 The figure is a schematic diagram of the RRC connection establishment process provided by the embodiments of this application. As Figure 3 shown, it includes step S301 where the UE initiates an RRC connection establishment request. Step S302 where the network side sends RRC settings. Step S303 where the RRC connection establishment is completed.
[0119] Among them, the UE sends an RRCSetupRequest message to the NW. The RRCSetupRequest message carries the RRC establishment reason and the UE identifier, and requests to establish an RRC connection. The NW feeds back an RRC setup message, which carries detailed information about resource configuration. The UE performs radio resource configuration based on the resource information indicated by the RRCSetup message. Among them, before performing the above steps, the RedCap UE makes the above conditional determination based on the SIB12 message sent by the network side, and then executes the subsequent steps after determining that the conditions are met.
[0120] The embodiments of this application can avoid the invalid execution of the connection establishment process for NR SL discovery and avoid the transmission failure of NR SL discovery by making a conditional determination based on the SIB12 message sent by the network side before the UE executes the RRC connection establishment request and then initiating the RRC connection establishment request after the conditional determination is successful. At the same time, since only the RRC connection establishment conditions for NR SL communication / discovery are described in the current 3GPP definition, and only need to judge whether there is an indication of resource pool occupation or abnormality, by making a determination according to the above determination conditions in the embodiments of this application, the RRC connection establishment conditions for NR SL communication / discovery can be described more accurately and completely, improving the accuracy of the determination.
[0121] Embodiment 2
[0122] After the RedCap UE receives and stores the SIB12 message sent by the gNB in this embodiment, before sending an RRC connection resume request for NR Sidelink communication / discovery, the conditional determination in Definition 2 above is made:
[0123] (1) If the sl-FreqInfoList field is included in the sl-ConfigCommonNR cell of the SIB12 message received by the RedCap UE:
[0124] (2) If the UE is configured by a higher layer to transmit NR Sidelink communication and the relevant data for transmission is available:
[0125] (3) If the frequency band configured for the UE to transmit NR Sidelink communication is included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located; and the sl-TxPoolSelectedNormal cell of the relevant frequency band is not included in the valid version of the SIB12 message;
[0126] (2) If the UE is configured by a higher layer to transmit NR Sidelink discovery and the relevant data for transmission is available:
[0127] (3) If the UE is configured by a higher layer to transmit an NR Sidelink layer 2 U2N relay discovery message and the sl-L2U2N-Relay field is included in the SIB12 message; or
[0128] (4) If the layer 2 U2N relay UE is in the RRC_INACTIVE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1;
[0129] (3) If the UE is configured by a higher layer to transmit an NR Sidelink layer 3 U2N relay discovery message and the sl-L3U2N-RelayDiscovery field is included in the SIB12 message; or
[0130] (3) If the UE is configured by a higher layer to transmit an NR Sidelink non-relay discovery message and the sl-NonRelayDiscovery field is included in the SIB12 message:
[0131] (4) If the frequency band configured for the UE to transmit NR Sidelink discovery is included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located; and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell of the relevant frequency band are not included in the valid version of the SIB12 message.
[0132] In this embodiment, there are three RRC states in NR: RRC idle state (RRC_IDLE), RRC inactive state (RRC_INACTIVE), and RRC connected state (RRC_CONNECTED). In the RRC_INACTIVE state, the UE has only one RRC state at a certain moment. When the UE is in the RRC_INACTIVE state, the UE can request recovery through RRC signaling and initiate an RRC connection recovery request. Generally speaking, being in the RRC inactive state means that the RRC connection has been established but is in an idle state, that is, there is no data transmission.
[0133] In this embodiment, similar to the above-mentioned first embodiment, according to the determination hierarchy, it can be divided into four layers. The first layer includes condition (1), the second layer includes condition (2), the third layer includes condition (3), and the fourth layer includes condition (4). There may be parallel conditions in each layer. For example, there are two parallel conditions (2) in the second layer. According to the upper and lower order of the conditions, after any condition in the upper layer is satisfied, then enter the lower layer to determine whether any condition in the lower layer is satisfied. Thus, from the top layer to the bottom layer step by step, the entire determination process is completed.
[0134] In this embodiment, according to the above-mentioned step-by-step determination of conditions from the top layer to the bottom layer, due to the different conditions configured in each layer (for example, there are two parallel conditions configured in the second layer, and only one of them needs to be satisfied to enter the next layer), multiple paths can be divided when making condition determinations from the top layer to the bottom layer, represented by four paths (using the fifth condition, the sixth condition, the seventh condition, and the eighth condition). Among them, the fifth condition includes in sequence:
[0135] (1) The side-link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0136] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink communication and the relevant data for transmission is available;
[0137] (3) The frequency point configured for the lightweight terminal to transmit NR Sidelink communication is included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell of the relevant frequency point is not included in the valid version of the SIB12 message.
[0138] The sixth condition includes in sequence:
[0139] (1) The side-link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0140] (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0141] (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the sl-L2U2N-Relay field is included in the SIB12 message;
[0142] (4) The layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1.
[0143] The seventh condition includes in sequence:
[0144] (1) The side link frequency list is included in the cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal;
[0145] (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0146] (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink layer 3 U2N relay discovery message, and the sl-L3U2N-RelayDiscovery field is included in the SIB12 message.
[0147] The eighth condition includes in sequence:
[0148] (1) The side link frequency list is included in the cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal;
[0149] (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0150] (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink non-relay discovery message, and the sl-NonRelayDiscovery field is included in the SIB12 message;
[0151] (4) The frequency points configured for the lightweight terminal to transmit NR Sidelink discovery are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell of the relevant frequency points are not included in the valid version of the SIB12 message.
[0152] Figure 4 This is a schematic diagram of the RRC connection restoration process provided by the embodiments of this application. As Figure 4 shown, it includes step S401 where the UE initiates a connection restoration request. Step S302 where the network side sends an RRCResume message. Step S303 where the RRC connection restoration is completed.
[0153] Among them, the UE sends an RRCResumeRequest / RRCResumeRequest1 message to the NW. The RRCResumeRequest / RRCResumeRequest1 message carries the RRC restoration reason and the UE identifier, requesting the RRC connection restoration. The NW feeds back the RRCResume message, and the UE performs connection restoration based on the RRCResume message. Among them, before performing the above steps, the RedCap UE performs the above conditional determination based on the SIB12 message sent by the network side, and then executes the subsequent steps after determining that the conditions are met.
[0154] In the embodiments of this application, by performing a conditional determination based on the SIB12 message sent by the network side before the UE executes the RRC connection restoration request, and initiating the RRC connection restoration request after the conditional determination is successful, it is possible to avoid the ineffective execution of the connection restoration process discovered by NR SL and avoid the transmission failure discovered by NR SL. At the same time, since only the RRC connection restoration conditions for NRSL communication / discovery are described in the current 3GPP definition, and only need to determine whether a resource pool is occupied or an abnormal indication exists, by making a determination based on the above determination conditions in the embodiments of this application, the RRC connection restoration conditions for NRSL communication / discovery can be described more accurately and completely, improving the accuracy of the determination.
[0155] The following are the device embodiments of this application, which can be used to execute the method embodiments of this application. For the details not disclosed in the device embodiments of this application, please refer to the method embodiments of this application.
[0156] Figure 5 This is a schematic diagram of the structure of the direct communication discovery device of the lightweight terminal provided by the embodiments of this application. As Figure 5As shown in the figure, the direct communication discovery device 500 includes an information acquisition module 510, a determination module 520, and an operation execution module 530. Among them, the information acquisition module 510 is used to acquire the SIB12 message sent by the base station. The determination module 520 is used to determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message before the lightweight terminal executes the target operation. The target operation is the RRC connection establishment process for NR Sidelink communication / discovery or the RRC connection restoration process for NR Sidelink communication / discovery. The operation execution module 530 is used to execute the target operation when the base station side supports the new radio direct communication of the lightweight terminal.
[0157] Optionally, the determination module may specifically be used to: check the SIB12 message to determine whether the base station side supports at least one of layer 2 terminal-to-network relay discovery, layer 3 terminal-to-network relay discovery, and non-relay discovery; if the base station side supports at least one of layer 2 terminal-to-network relay discovery, layer 3 terminal-to-network relay discovery, and non-relay discovery, then determine that the base station side supports the new radio direct communication of the lightweight terminal.
[0158] Optionally, the determination module may specifically be used to: before the lightweight terminal executes the RRC connection establishment process for NR Sidelink communication / discovery, determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, including:
[0159] Check the SIB12 message. If the first condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The first condition includes in turn:
[0160] (1) The sl-FreqInfoList field is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0161] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink communication and the relevant data for transmission is available;
[0162] (3) The frequency points configured for the lightweight terminal to transmit NR Sidelink communication are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell of the relevant frequency points is not included in the valid version of the SIB12 message.
[0163] Optionally, the determination module may specifically be used to: before the lightweight terminal executes the RRC connection establishment process for NR Sidelink communication / discovery, determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, including:
[0164] Check the SIB12 message. If the second condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The second condition includes, in sequence:
[0165] (1) The cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0166] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0167] (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the SIB12 message contains the sl-L2U2N-Relay field;
[0168] (4) The layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1.
[0169] Optionally, the determination module may specifically be used to: before the lightweight terminal executes the RRC connection establishment process for NR Sidelink communication / discovery, determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, including:
[0170] Check the SIB12 message. If the third condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The third condition includes, in sequence:
[0171] (1) The cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0172] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0173] (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 3 U2N relay discovery message, and the SIB12 message contains the sl-L3U2N-RelayDiscovery field.
[0174] Optionally, the determination module can specifically be used to: before the lightweight terminal executes the RRC connection establishment process for NR Sidelink communication / discovery, determine whether the base station side supports the New Radio (NR) direct communication of the lightweight terminal according to the SIB12 message, including:
[0175] Check the SIB12 message. If the fourth condition is met, it is determined that the base station side supports the NR direct communication of the lightweight terminal. The fourth condition includes, in sequence:
[0176] (1) The cell sl-ConfigCommonNR in the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0177] (2) The lightweight terminal is configured by a higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0178] (3) The lightweight terminal is configured by a higher layer to transmit NR Sidelink non-relay discovery messages, and the SIB12 message contains the sl-NonRelayDiscovery field;
[0179] (4) The frequency points configured for the lightweight terminal to transmit NR Sidelink discovery are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and sl-TxPoolSelectedNormal cell of the relevant frequency points are not included in the valid version of the SIB12 message.
[0180] Optionally, the determination module can specifically be used to: before the lightweight terminal executes the RRC connection recovery process for NR Sidelink communication / discovery, determine whether the base station side supports the NR direct communication of the lightweight terminal according to the SIB12 message, including:
[0181] Check the SIB12 message. If the fifth condition is met, it is determined that the base station side supports the NR direct communication of the lightweight terminal. The fifth condition includes, in sequence:
[0182] (1) The cell sl-ConfigCommonNR in the SIB12 message received by the lightweight terminal contains a sidelink frequency list;
[0183] (2) The lightweight terminal is configured by a higher layer to transmit NR Sidelink communication and the relevant data for transmission is available;
[0184] (3) The frequency points configured to be used by the lightweight terminal for transmitting NR Sidelink communication are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell related to the frequency points is not included in the valid version of the SIB12 message.
[0185] Optionally, the determination module may specifically be used to: before the lightweight terminal executes the RRC connection restoration process for NR Sidelink communication / discovery, determine whether the base station side supports the New Radio (NR) sidelink direct communication of the lightweight terminal according to the SIB12 message, including:
[0186] Check the SIB12 message. If the sixth condition is met, it is determined that the base station side supports the NR sidelink direct communication of the lightweight terminal. The second condition includes the following in sequence:
[0187] (1) The side link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0188] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0189] (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the sl-L2U2N-Relay field is included in the SIB12 message;
[0190] (4) The layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1.
[0191] Optionally, the determination module may specifically be used to: before the lightweight terminal executes the RRC connection restoration process for NR Sidelink communication / discovery, determine whether the base station side supports the NR sidelink direct communication of the lightweight terminal according to the SIB12 message, including:
[0192] Check the SIB12 message. If the seventh condition is met, it is determined that the base station side supports the NR sidelink direct communication of the lightweight terminal. The seventh condition includes the following in sequence:
[0193] (1) The side link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0194] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0195] (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 3 U2N relay discovery message, and the sl-L3U2N-RelayDiscovery field is included in the SIB12 message.
[0196] Optionally, the determination module can specifically be used to: before the lightweight terminal executes the RRC connection restoration process for NR Sidelink communication / discovery, determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, including:
[0197] Check the SIB12 message. If the eighth condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The eighth condition includes in sequence:
[0198] (1) The side link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal;
[0199] (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available;
[0200] (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink non-relay discovery message, and the sl-NonRelayDiscovery field is included in the SIB12 message;
[0201] (4) The frequency points configured for the lightweight terminal to transmit NR Sidelink discovery are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell of the relevant frequency points are not included in the valid version of the SIB12 message.
[0202] The device provided by the embodiments of the present application can be used to execute the methods in the above embodiments, and its implementation principle and technical effects are similar, which will not be elaborated here.
[0203] It should be noted that the division of each module of the above device is only a division of logical functions. In actual implementation, it can be fully or partially integrated into a physical entity, or physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also all be implemented in the form of hardware; or some modules can be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the information acquisition module can be a separately established processing element, or can be integrated in a certain chip of the above device. In addition, it can also be stored in the memory of the above device in the form of program code, and the function of the above information acquisition module is called and executed by a certain processing element of the above device. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together or can be independently implemented. Here, the processing element can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by the integrated logic circuit in the processor element or the instruction in the form of software.
[0204] Figure 6 This is a schematic structural diagram of the terminal device provided by the embodiment of the present application. As Figure 6 shown, the terminal device 600 includes: at least one processor 601, a memory 602, a bus 603, and a communication interface 604. Among them: the processor 601, the communication interface 604, and the memory 602 complete mutual communication through the bus 603. The communication interface is used to communicate with other devices. The communication interface includes a communication interface for data transmission and a display interface or an operation interface for human-computer interaction, etc. The processor is used to execute computer execution instructions, and specifically can execute the relevant steps in the method described in the above embodiment.
[0205] The processor may be a central processing unit, or a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. One or more processors included in the terminal device can be of the same type of processor, such as one or more CPUs; or they can be of different types of processors, such as one or more CPUs and one or more ASICs.
[0206] The memory is used to store computer execution instructions. The memory may include a high-speed RAM memory, and may also include non-volatile memory, such as at least one disk memory.
[0207] This embodiment also provides a computer-readable storage medium. Computer instructions are stored in the readable storage medium. When at least one processor of the terminal device executes the computer instructions, the terminal device executes the direct communication discovery method of the lightweight terminal provided by the above various embodiments.
[0208] In this application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after; in a formula, the character " / " represents a "division" relationship between the associated objects before and after. "At least one (item)" or a similar expression thereof refers to any combination of these items, including any combination of single item (s) or plural item (s). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.
[0209] It can be understood that the various numerical numbers involved in the embodiments of this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application. In the embodiments of this application, the magnitudes of the serial numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of this application.
[0210] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of this application.
Claims
1. A method for direct communication discovery of a lightweight terminal, characterized in that, applied to a lightweight terminal, the method includes: Obtain the SIB12 message sent by the base station; Before the lightweight terminal performs a target operation, determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, where the target operation is an RRC connection establishment process for NR Sidelink communication / discovery, or an RRC connection restoration process for NR Sidelink communication / discovery; When the base station side supports the new radio direct communication of the lightweight terminal, perform the target operation.
2. The method according to claim 1, characterized in that, The determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message includes: Check the SIB12 message to determine whether the base station side supports at least one of layer 2 terminal-to-network relay discovery, layer 3 terminal-to-network relay discovery, and non-relay discovery; If the base station side supports at least one of layer 2 terminal-to-network relay discovery, layer 3 terminal-to-network relay discovery, and non-relay discovery, it is determined that the base station side supports the new radio direct communication of the lightweight terminal.
3. The method according to claim 1, characterized in that, Before the lightweight terminal performs an RRC connection establishment process for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message includes: Check the SIB12 message, and if the first condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The first condition includes in sequence: (1) The sl-FreqInfoList field is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink communication and the relevant data for transmission is available; (3) The frequency points configured for the lightweight terminal to transmit NR Sidelink communication are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell of the relevant frequency points is not included in the valid version of the SIB12 message.
4. The method according to claim 1, characterized in that, Before the lightweight terminal performs an RRC connection establishment process for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message includes: Check the SIB12 message, and if the second condition is met, it is determined that the base station side supports the new radio direct communication of the lightweight terminal. The second condition includes in sequence: (1) The side-link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available; (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the sl-L2U2N-Relay field is included in the SIB12 message; (4) The layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1.
5. The method according to claim 1, wherein, before the lightweight terminal performs the RRC connection establishment process for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, includes: checking the SIB12 message, if the third condition is satisfied, determining that the base station side supports the new radio direct communication of the lightweight terminal, and the third condition successively includes: (1) The side link frequency list is included in the cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available; (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink layer 3 U2N relay discovery message, and the sl-L3U2N-RelayDiscovery field is included in the SIB12 message.
6. The method according to claim 1, wherein, before the lightweight terminal performs the RRC connection establishment process for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, includes: checking the SIB12 message, if the fourth condition is satisfied, determining that the base station side supports the new radio direct communication of the lightweight terminal, and the fourth condition successively includes: (1) The side link frequency list is included in the cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the higher layer to transmit NR Sidelink discovery, and the relevant data for transmission is available; (3) The lightweight terminal is configured by the higher layer to transmit the NR Sidelink non-relay discovery message, and the sl-NonRelayDiscovery field is included in the SIB12 message; (4) The frequency points configured for the lightweight terminal to transmit NR Sidelink discovery are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell of the relevant frequency points are not included in the valid version of the SIB12 message.
7. The method according to claim 1, wherein, Before the lightweight terminal performs the RRC connection restoration procedure for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct connection communication of the lightweight terminal according to the SIB12 message includes: Checking the SIB12 message, if the fifth condition is met, it is determined that the base station side supports the new radio direct connection communication of the lightweight terminal, and the fifth condition successively includes: (1) The side link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink communication and the relevant data for transmission is available; (3) The frequency points configured for the lightweight terminal to transmit NR Sidelink communication are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the lightweight terminal is located, and the sl-TxPoolSelectedNormal cell of the relevant frequency points is not included in the valid version of the SIB12 message.
8. The method according to claim 1, wherein, before the lightweight terminal performs the RRC connection restoration procedure for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct connection communication of the lightweight terminal according to the SIB12 message includes: Checking the SIB12 message, if the sixth condition is met, it is determined that the base station side supports the new radio direct connection communication of the lightweight terminal, and the second condition successively includes: (1) The side link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery and the relevant data for transmission is available; (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 2 U2N relay discovery message and the sl-L2U2N-Relay field is included in the SIB12 message; (4) The layer 2 U2N relay UE is in the RRC_IDLE state and receives any message from the layer 2 U2N remote UE via SL-RLC0 or SL-RLC1.
9. The method according to claim 1, wherein, before the lightweight terminal performs the RRC connection restoration procedure for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct connection communication of the lightweight terminal according to the SIB12 message includes: Checking the SIB12 message, if the seventh condition is met, it is determined that the base station side supports the new radio direct connection communication of the lightweight terminal, and the seventh condition successively includes: (1) The side link frequency list is included in the sl-ConfigCommonNR cell of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery and the relevant data for transmission is available; (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink layer 3 U2N relay discovery message, and the sl-L3U2N-RelayDiscovery field is included in the SIB12 message.
10. According to the method described in claim 1, characterized in that, before the lightweight terminal executes the RRC connection restoration process for NR Sidelink communication / discovery, determining whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message, includes: Checking the SIB12 message, if the eighth condition is satisfied, it is determined that the base station side supports the new radio direct communication of the lightweight terminal, and the eighth condition includes in turn: (1) The side link frequency list is included in the cell sl-ConfigCommonNR of the SIB12 message received by the lightweight terminal; (2) The lightweight terminal is configured by the upper layer to transmit NR Sidelink discovery, and the relevant data for transmission is available; (3) The lightweight terminal is configured by the upper layer to transmit the NR Sidelink non-relay discovery message, and the sl-NonRelayDiscovery field is included in the SIB12 message; (4) The frequency points configured for the lightweight terminal to transmit NR Sidelink discovery are included in the sl-FreqInfoList field of the SIB12 message provided by the cell where the RedCap UE is located, and the sl-DiscTxPoolSelected cell and the sl-TxPoolSelectedNormal cell related to the frequency points are not included in the valid version of the SIB12 message.
11. A direct communication discovery device for a lightweight terminal, characterized in that, including: An information acquisition module, configured to acquire the SIB12 message sent by the base station; A determination module, configured to determine whether the base station side supports the new radio direct communication of the lightweight terminal according to the SIB12 message before the lightweight terminal executes the target operation, and the target operation is the RRC connection establishment process for NR Sidelink communication / discovery or the RRC connection restoration process for NR Sidelink communication / discovery; An operation execution module, configured to execute the target operation when the base station side supports the new radio direct communication of the lightweight terminal.
12. A terminal device, characterized in that, including: A processor, and a memory communicatively connected to the processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the method described in any one of claims 1-10.
13. A computer-readable storage medium, characterized in that, computer execution instructions are stored in the computer-readable storage medium, and when the computer execution instructions are executed by a processor, they are used to implement the method described in any one of claims 1 to 10.