Wireless communication method for data transmission in inactive state and related apparatus

Abstract

A wireless communication method and apparatus are provided. The method performed by a user equipment (UE) includes configuring, by a base station, UL grant resources for the UE for UL data transmission in an inactive state based on the configured UL grant resources, and performing the UL data transmission in the inactive state on the configured UL grant resources based on a transmission characteristic of the UL data transmission and at least one transmission threshold. This can solve the problems in the prior art, improve the problems of power consumption increase and signaling burden, and provide excellent communication performance and / or high reliability.

Description

Technical Field

[0001] This application relates to wireless communication technology, and in particular to a wireless communication method and related apparatus for transmitting data in an inactive state. Background Technology

[0002] Communication systems and networks have evolved into broadband and mobile systems. In cellular wireless communication systems developed by the Third Generation Partnership Project (3GPP), User Equipment (UE) connects to the Radio Access Network (RAN) via a radio link. The RAN comprises a set of Base Stations (BSs) that provide radio links to UEs located within the cells covered by those base stations, and includes an interface to the Core Network (CN), which has the function of controlling the overall network. It can be understood that the RAN and CN each perform corresponding functions related to the entire network. 3GPP has developed the so-called Long Term Evolution (LTE) system, namely the Evolved Universal Mobile Communications System Territorial Radio Access Network (E-UTRAN), for mobile access networks of one or more large cells supported by base stations called eNodeBs or eNBs (evolved NodeBs). Recently, LTE has further evolved into the so-called 5G or New Radio (NR) system, in which one or more cells are supported by base stations called gNBs.

[0003] In LTE, if a UE is inactive for a period of time, the network can command the UE to enter the RRC_IDLE state to reduce UE power consumption. Whenever the UE needs to perform some activity, it needs to transition from the RRC_IDLE state to the RRC_CONNECTED state. In current mobile communication applications, small amounts of data must be transmitted frequently, so frequent transitions between idle and connected states increase network signaling burden and latency. Therefore, 5G NR defines a new state called RRC_INACTIVE to reduce the network signaling burden and latency caused by transitioning to the RRC_CONNECTED state. In NR, when an RRC connection is established, the UE is in the RRC_CONNECTED state, and when the RRC connection is suspended, the UE is in the RRC_INACTIVE state. If neither of these conditions applies, the UE is in the RRC_IDLE state, meaning no RRC connection has been established.

[0004] More specifically, in the RRC_INACTIVE state, the UE Access Stratum (AS) context is stored on both the UE and network sides, thereby maintaining the connection with the core network (i.e., the UE remains in the CM-CONNECTED state (CM stands for Connection Management) while disconnecting from the radio access network (RAN). The network can contact the inactive UE via RAN or CN paging messages. Except for the preamble in the random access (RA) procedure initiated when the UE needs to transition to the RRC_CONNECTED state for uplink (UL) data transmission, the inactive UE cannot transmit any UL data.

[0005] Currently, data transmission in the RRC_INACTIVE state is not supported. Therefore, inactive UEs must restore the connection (i.e., transition to the RRC_CONNECTED state) to perform DL (downlink) / UL data transmission. However, restoring and then returning to the RRC_INACTIVE state also occurs with the transmission of small, infrequent packets, resulting in unnecessary power consumption and signaling overhead. Summary of the Invention

[0006] One object of this application is to provide an apparatus (e.g., user equipment (UE) and / or base station) and a wireless communication method that can solve the problems in the prior art, improve the problems of increased power consumption and signaling burden, and provide excellent communication performance and / or high reliability.

[0007] In one aspect of this application, a wireless communication method performed by a user equipment includes: configuring UL licensed resources for the UE via a base station to perform UL data transmission in an inactive state based on the configured UL licensed resources; and performing UL data transmission on the configured UL licensed resources in the inactive state based on the transmission characteristics of the UL data transmission and at least one transmission threshold.

[0008] In a second aspect of this application, a wireless communication method performed by a base station includes: configuring uplink (UL) grant resources for a UE so that the UE performs UL data transmission in an inactive state based on the configured UL grant resources; and receiving the UL data transmission from the UE, the UL data transmission being performed on the configured UL grant resources in the inactive state based on the transmission characteristics of the UL data transmission and at least one transmission threshold.

[0009] In a third aspect of this application, a user equipment includes a memory, a transceiver, and a processor coupled to the memory and the transceiver, the processor being configured to call and execute program instructions stored in the memory to perform the aforementioned wireless communication method.

[0010] In a fourth aspect of this application, a base station includes a memory, a transceiver, and a processor coupled to the memory and the transceiver, the processor being configured to call and execute program instructions stored in the memory to perform the aforementioned wireless communication method.

[0011] In a fifth aspect of this application, a non-volatile computer-readable storage medium is provided, having instructions stored thereon that, when executed by a computer, cause the computer to perform the above-described method.

[0012] In a sixth aspect of this application, a chip includes a processor configured to call and run a computer program stored in a memory, causing a device on which the chip is installed to perform the above-described method.

[0013] In a seventh aspect of this application, a computer-readable storage medium is provided having a computer program stored thereon, wherein the computer program causes a computer to perform the above-described method.

[0014] In an eighth aspect of this application, a computer program product includes a computer program, wherein the computer program causes a computer to perform the above-described method.

[0015] In a ninth aspect of this application, a computer program is provided, wherein the computer program causes a computer to perform the above-described method. Attached Figure Description

[0016] To more clearly illustrate the embodiments of this application or related technologies, the following drawings will be described in conjunction with the embodiments, and will be briefly introduced below. It is obvious that the drawings represent only some embodiments of this application, and those skilled in the art can derive other drawings based on these drawings without making any presuppositions.

[0017] Figure 1A A schematic diagram of the communication control system according to this application is shown.

[0018] Figure 1B A block diagram showing one or more user equipments (UEs) and a base station performing wireless communication in a communication control system according to an embodiment of this application.

[0019] Figure 1C A flowchart showing a wireless communication method performed by a user equipment according to an embodiment of this application is displayed.

[0020] Figure 1D A flowchart showing a wireless communication method performed by a base station according to an embodiment of this application is displayed.

[0021] Figure 2A This diagram illustrates a small amount of data transmission based on a cell in the RRC_INACTIVE state of a UE according to an embodiment of this application.

[0022] Figure 2B for Figure 2A An example flowchart.

[0023] Figure 3A This flowchart illustrates a small amount of RNA-based data transmission of a UE in the RRC_INACTIVE state according to an embodiment of this application.

[0024] Figure 3B for Figure 3A An example flowchart.

[0025] Figure 4 This diagram shows a flowchart of a cell-based one-way indication scheme according to an embodiment of this application.

[0026] Figure 5 This diagram shows a flowchart of a cell-based bidirectional request scheme according to an embodiment of this application.

[0027] Figure 6 A flowchart showing an RNA-based one-way instruction scheme according to an embodiment of this application is displayed.

[0028] Figure 7 A flowchart showing an RNA-based bidirectional request scheme according to an embodiment of this application is displayed.

[0029] Figure 8 This flowchart illustrates a small amount of data transmission for an NPN application in an inactive state, according to an embodiment of this application.

[0030] Figure 9 This diagram illustrates a flowchart of a small amount of data transmission in an inactive state for a DC application according to an embodiment of this application.

[0031] Figure 10 This shows a block diagram of a system for wireless communication according to an embodiment of this application. Detailed Implementation

[0032] The embodiments of this application will now be described in detail with reference to the accompanying drawings, focusing on their technical solutions, structural features, achieved objectives, and effects. Specifically, the terminology used in the embodiments of this application is only used to describe certain embodiments and is not intended to limit the content of this application.

[0033] Some abbreviations used in certain parts of this application are included in the following table:

[0034]

[0035]

[0036]

[0037] In this article, " / " should be interpreted as "and / or".

[0038] This invention proposes an "inactive" UL grant provided to inactive UEs, allowing them to transmit small amounts of data on this inactive UL grant resource. Considering mobility, this inactive UL grant resource can be cell-based, RAN Notification Area (RNA)-based, contention-free, or contention-based. The configuration of the inactive UL grant can be obtained via RRC signaling, and activation of the "inactive" UL grant resource of the target cell / RNA can be achieved through one-way indication or two-way request schemes.

[0039] In this application embodiment, the low-latency, low-ultraviolet (UL) small data transmission (SDT) process in the RRC_INACTIVE state has the following two types:

[0040] • Transfer on pre-configured grant (PCG) resources

[0041] • Contention-free / contention-based random access (CFRA) / contention-based random access (CBRA) procedures

[0042] For a small amount of data transmission in the RRC_INACTIVE state, the network can provide pre-configured UL grant resources to inactive UEs with a UE context identifier (e.g., I-RNTI) (and optionally, a RAN notification area identifier (e.g., RNA ID)). When timing advance is active, two types of pre-configured grants can be used for inactive UEs.

[0043] For pre-configured grant type 1 (hereinafter referred to as PCG), when the UE enters the RRC_INACTIVE state, pre-configuration is performed via RRC signaling (e.g., RRC Release) for each BWP and each serving cell (i.e., cell-based). For a given active BWP in a serving cell, multiple PCGs can be configured for an inactive UE. When the inactive UE is stationary or stationary in the serving cell, the PCG is triggered by a small amount of UL data arriving at the inactive UE's transmission buffer, followed by the transmission of PCG PUSCH resources after RRC configuration. The following parameters can be configured for pre-configured grant type 1 (i.e., PCG), but are not limited to these:

[0044] οI-RNTI: Used to identify the UE context in the RRC_INACTIVE state.

[0045] οCS-RNTI: Optional, can be used for retransmission

[0046] ο Periodicity: The periodicity of PCG

[0047] Offset: The offset of a PCG resource in the time domain.

[0048] οstartAllocion: The starting resource of the PCG in the time domain (e.g., (sub)frame number, symbol number)

[0049] PCG Transmission Threshold: When configured, the maximum amount of data allowed to be transmitted on PCG resources (e.g., 32 bytes).

[0050] ο Activated BWP ID: When entering the RRC_INACTIVE state, PCG resources are allocated to a configured active BWP.

[0051] For pre-configured license type 2 (hereinafter referred to as RNA-based PCG, or RBPCG), when a UE enters the RRC_INACTIVE state, it is pre-configured under a predetermined BWP via RRC signaling (e.g., RRC Release) for each RNA. Multiple RBPCGs can be configured for an inactive UE for a predetermined BWP within an RNA. RBPCGs are triggered after an RNA update when an inactive UE leaves the coverage area of ​​the serving cell. RBPCG resources are configured for the RAN to notify the RAN of a small amount of UL data transmission within the area under a predetermined BWP in the RRC_INACTIVE state. Following RRC configuration and inter-node signaling transmission, the RBPCG PUSCH resources are then transmitted. The following parameters can be configured for pre-configured license type 2 (i.e., RBPCG), but are not limited to them:

[0052] οI-RNTI: Used to identify the UE context in the RRC_INACTIVE state.

[0053] οCS-RNTI: Optional, can be used for retransmission

[0054] ο Periodicity: The periodicity of PCG

[0055] Offset: The offset of a PCG resource in the time domain.

[0056] οstartAllocion: The starting resource of the PCG in the time domain (e.g., (sub)frame number, symbol number)

[0057] oRBPCG transfer threshold: When configured, the maximum amount of data allowed to be transferred on RBPCG resources (e.g., 16 or 256 bytes).

[0058] RAN notifications of relevant information for the region can consist of a list of cell IDs, RNA IDs, etc.

[0059] οPre-assigned BWP ID (Default BWP ID): In the RRC_INACTIVE state, RBPCG resources are allocated to a pre-assigned BWP.

[0060] When an inactive UE decides to transmit a small amount of UL data on RBPCG resources, it can switch to the pre-defined BWP to transmit RAN notification area-related information and / or UE context identifiers, which can be combined with the small amount of UL data. Furthermore, the active BWP ID used in the PCG can be the same as the pre-defined BWP ID used in the RBPCG, depending on the network configuration (e.g., BWP configuration).

[0061] Contention-Free Random Access (CFRA): In contention-free random access, the preamble is assigned by the gNB; this preamble is called a dedicated random access preamble. This dedicated preamble can be provided to the UE via RRC signaling (the allocation of the preamble can be configured within the RRC message). Therefore, the UE can transmit this dedicated preamble in a contention-free manner.

[0062] Contention-based Random Access (CBRA): In contention-based random access, the UE randomly selects a preamble from a preamble group shared with other UEs. This means there is a potential risk that a UE might choose the same preamble as another UE, which could subsequently lead to a conflict. The gNB uses a contention-based resolution mechanism to handle access requests. In this process, the result is random, and not all random access attempts will be successful.

[0063] The contention-free random access (CFRA) procedure in the RRC_INACTIVE state can be triggered by the following events:

[0064] • Inactive UEs are stationary or remain in the serving cell

[0065] • Inactive UEs leaving the coverage area of ​​the serving cell with seamless CFRA configuration

[0066] CFRA resources have been configured for inactive UEs.

[0067] • Non-periodic and / or low-latency UL small-volume data transmission in RRC_INACTIVE state

[0068] Unable to transfer on configured grant (CG) resources.

[0069] Contention-based random access (CBRA) procedures in the RRC_INACTIVE state can be triggered by the following events:

[0070] • Inactive UEs leaving the coverage area of ​​the serving cell without any CFRA configuration

[0071] CFRA resources were not allocated to inactive UEs.

[0072] • Non-periodic and / or low-priority UL small-volume data transmissions in RRC_INACTIVE state

[0073] • Unable to transfer or execute CFRA program on configured grant (CG) resources.

[0074] In this embodiment, in contention-free random access (CFRA), one or more dedicated preambles are pre-configured to the UE or configured by the gNB via RRC signaling for small-scale data transmission during inactive states. In contention-based random access, the UE randomly selects a preamble from a group of preambles associated with a small-scale data transmission threshold used to perform a two-step or four-step RA-SDT. Whether CFRA or CBRA is performed depends on the network configuration (e.g., PRACH configuration).

[0075] Contention-based random access procedures can be either a four-step or a two-step procedure. For the four-step procedure, the UE sends a contention-based PRACH preamble, also known as MSG1. Upon detecting this preamble, the gNB responds to the UE with a random-access response (RAR), also known as MSG2. This RAR includes the detected preamble ID, a time advance command, a provisional C-RNTI (TC-RNTI), and an uplink grant for scheduling a PUSCH transmission from the UE, called MSG3. In response to this RAR, the UE sends MSG3, which includes the contention resolution ID. Upon receiving MSG3, the network sends a contention resolution message with the contention resolution ID, also known as MSG4. The UE receives MSG4, and if it has found its contention resolution ID, it sends an acknowledgment on the PUCCH, thus completing the four-step random access procedure.

[0076] This two-step procedure aims to reduce latency and signaling burden by using a single round-trip cycle between the UE and the base station. This is achieved by combining the preamble (MSG1) and the scheduled PUSCH transmission (MSG3) into a single message (MSGA) from the UE to the gNB, referred to as the MSGA, and combining the random access response (MSG2) and the contention resolution message (MSG4) into a single message (MSGB) from the gNB to the UE. Both the two-step and four-step procedures can be applied to contention-free random access when the UE is provided with the dedicated preamble.

[0077] In this embodiment, two types of RACH procedures are supported in the RRC_INACTIVE state: a two-step RA type and a four-step RA type. In the two-step RA type, when the UE enters the RRC_INACTIVE state, at least one PRACH preamble group and a Resume ID are configured for the UE to perform a small amount of data transmission. In some cases, dedicated PRACH preambles and PUSCH resources are contention-free on the MSGA transmission. The MSGA of this two-step RA type includes the preamble configured on the PRACH and the payload on the PUSCH. The minimum payload size of the MSGA is assumed to be the same as the size of the MAC PDU used for initial access, for example, 56 bits or 72 bits based on the trigger condition. Contention resolution in the two-step RA type is handled by the UE context identifier in the MSGA, which is echoed in the MSGB. In other words, for contention resolution in the MSGB, the UE context identifier should be included in the MSGA. This UE context identifier is unique and can be implemented through, for example, I-RNTI, Resume ID, S-TMSI, C-RNTI, RandomValue, or SDT-RNTI. When a UE enters the RRC_INACTIVE state, the network should retain the I-RNTI or recovery ID, as well as the UE context, including the AS security context and bearer configuration. When the network receives a configured PRACH preamble combined with the UE context identifier from an inactive UE, the network retrieves the UE's context and UL data and responds with DL data in the MSGB if necessary. The MSGB may include responses to RA responses, contention resolution, fallback indications, DL data PDUs, etc. Unless the PUSCH transmission in the MSGA fails, the inactive UE can remain in the RRC_INACTIVE state and perform a small amount of data transmission. Once the PUSCH transmission in the MSGA fails under a two-step RA type, the inactive UE can either perform a fallback four-step RA type procedure in the RRC_INACTIVE state or perform a four-step random access procedure to enter the RRC_CONNECTED state.

[0078] In the four-step RA type, at least one set of PRACH preambles in the MSG1 transmission is configured by the network. Here, the PRACH preamble set in the four-step RA type can be the same as that configured in the two-step RA type. In other words, regardless of the RA type, the PRACH preamble will be selected from the PRACH preamble set configured by the network. In some cases, the dedicated PRACH preamble is contention-free in the MSG1 transmission. The inactive UE should, in the RRC_INACTIVE state, monitor the MSG2 for the RA response received from the network within the configured RA response window. When the RA response window expires, the inactive UE should retransmit the configured PRACH preamble until the maximum number of PRACH transmissions is reached. Upon receiving an RA response for the general UL data transmission procedure, the inactive UE will transition to the RRC_CONNECTED state. In other words, if the four-step RA type fails, the inactive UE should execute the four-step random access procedure to enter the RRC_CONNECTED state.

[0079] The dedicated PRACH preamble used in the MSGA of a two-step CFRA can be shared with the MSG1 in a four-step CFRA, which facilitates CFRA rollback. In some cases, the network cannot configure this shared CFRA resource for both two-step and four-step RA types simultaneously within a single Bandwidth Part (BWP). When network conditions and transmission thresholds permit, inactive UEs can transmit small amounts of UL data in the RRC_INACTIVE state by using either a two-step or four-step RA procedure.

[0080] In this embodiment, for low-latency, low-volume data transmission in the RRC_INACTIVE state under mobility considerations, the inactive UE should notify the network in advance of the need for UL authorized resources without performing a state transition. When the inactive UE moves outside the range of the serving cell / RNA, two schemes are provided to the inactive UE to activate the "inactive" UL authorized resources:

[0081] • One-way Indication Scheme: In this scheme, when an inactive UE transitions to the RRC_INACTIVE state, the serving cell can negotiate SDT configurations (e.g., PCG / RBPCG / RA resources, UE AS context, I-RNTI) with neighboring cells / RNAs. When the inactive UE moves across the boundary of the serving cell / RNA, it can send an indication (e.g., this indication can be carried in a proximity indication, RNA update, or some other new notification message used in the RRC_INACTIVE state) to the serving or target cell / RNA to activate the "inactive" UL authorized resources. For example, but not limited to, when the inactive UE detects a target serving cell ID located in the same RNA ID, it can send the proximity indication to obtain the PCG configuration of the target cell. Additionally, when the inactive UE detects that it is outside the RNA coverage area, it can send the RNA update to obtain the PCG configuration of the target cell. Upon receiving a proximity indication, if a neighboring cell / RNA can allocate the same time / frequency "inactive" UL grant resources, the serving cell / RNA can instruct the candidate / target cell / RNA to activate PCG / RBPCG / RA resources for seamless data transmission. Conversely, upon receiving a proximity indication, the target cell can activate the PCG / RBPCG / RA resources. If a neighboring cell / RNA cannot allocate the same time / frequency UL grant resources as the serving cell / RNA, the serving cell / RNA can respond to the inactive UE with RRC signaling (e.g., paging), specifically specifying the PCG / RBPCG / RA configuration of the neighboring cell / RNA. The network can perform RAN paging or CN paging, depending on whether the target cell is in the same RNA. Furthermore, if the network can determine the UE's location, it can unicast a response signaling to the inactive UE. Upon receiving this response signaling, the inactive UE can transmit a small amount of UL data on the PCG / RBPCG / RA resources in the target cell / RNA without a state transition.

[0082] • Two-way request scheme: In this scheme, PCG / RBPCG / RA configurations can be transmitted via RRC signaling (e.g., system information (SI), RRC Release). Inactive UEs can send RRC requests (e.g., on-demand system information request, RRC resume request) to the serving or target cell to obtain updated SDT configurations (e.g., PCG / RBPCG / RA configurations) in the RRC_INACTIVE state without a state transition. Upon receiving an RRC request from an inactive UE, the serving or target cell unicasts / broadcasts the information associated with the SDT configuration and then activates the “inactive” UL authorized resources. The transmission of this RRC request can be forwarded before / when the inactive UE wishes to initiate low-latency, small-volume data transmissions in the RRC_INACTIVE state. Furthermore, the transmission of the RRC request can be contention-based or contention-free, depending on the configuration of the physical random access channel (PRACH). Through negotiation between the serving cell and neighboring cells, the serving cell can transmit RRC responses not only with the serving cell's SDT configuration, but also with the neighboring cell's SDT configuration.

[0083] In this embodiment, for Multiple Radio (MR)-DC and New Radio (NR)-DC, if the network supports dual connectivity (DC) configuration, the DC configuration is maintained in the RRC_INACTIVE state to avoid unnecessary signaling burden and resource consumption. Inactive UEs can transmit URLLC data to the Master RAN node and Secondary RAN node on PCG / RBPCG / RA resources. When an inactive UE detects that one of the multiple Secondary RAN node configurations is about to fail due to mobility issues or poor channel conditions, it can apply the proposed one-way indication scheme or two-way request scheme to request inactive DC reconfiguration and inactive UL authorization reconfiguration. The inactive UE can send this indication or RRC request to the Master RAN node to request inactive DC reconfiguration and inactive UL authorization reconfiguration. Once the network receives the inactive UE's request for inactive DC reconfiguration and inactive UL authorization reconfiguration, it can apply the proposed one-way indication scheme or two-way request scheme to switch the PCG / RBPCG / RA configuration of the Secondary RAN node.

[0084] In this embodiment, for low-latency, low-volume data transmissions in the RRC_INACTIVE state on one or more non-public networks (NPNs) under mobility considerations, the proposed one-way indication scheme or two-way request scheme can be applied to NPN users (subscribers). Mobility of inactive NPN users is restricted based on the list of allowed cells. Therefore, when an NPN user enters the RRC_INACTIVE state, the allowed NPN cells listed in the mobility restrictions can be configured with PCG / RBPCG / RA resources.

[0085] Therefore, some embodiments of this application propose an apparatus (e.g., UE and / or base station) and a wireless communication method that can solve the problems in the prior art, improve power consumption, signaling burden, and resource allocation, and provide excellent communication performance and / or high reliability.

[0086] Figure 1A and Figure 1B A schematic diagram and a functional block diagram of the communication control system 1 according to this application are shown respectively. The communication control system 1 includes user equipment (UE) 10 and base station 20, which can communicate with each other wirelessly or via wired means. Base station 20 and next-generation core network 30 can also communicate with each other wirelessly or via wired means. When the communication control system 1 conforms to the New Radio (NR) standard of the 3rd Generation Partnership Project (3GPP), the next-generation core network 30 is a back-end service network system and may include Access and Mobility Management Function (AMF), User Plane Function (UPF), and Session Management Function (SMF). User equipment 10 may be a device that does not support NPN or a device that supports non-public network (NPN), but this application is not limited to these.

[0087] Figure 1BThe illustration shows one or more user equipments (UEs) 10 and a base station (e.g., gNB or eNB) 20 for wireless communication in a communication control system 1 according to embodiments of this application in some embodiments. The communication control system 1 includes one or more UEs 10 and a base station 20. One or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and transceiver 23. The processor 11 or 21 may be configured to implement the functions, programs, and / or methods proposed herein. A wireless interface protocol layer may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled to the processor 11 or 21 and stores various information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled to the processor 11 or 21 and transmits and / or receives wireless signals.

[0088] Processor 11 or 21 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices. Memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Transceiver 13 or 23 may include baseband circuitry for processing radio frequency signals. When these embodiments are implemented in software, the techniques described herein can be implemented by modules (e.g., programs, functions, etc.) that perform the functions described herein. These modules may be stored in memory 12 or 22 and executed by processor 11 or 21. Memory 12 or 22 may be implemented within processor 11 or 21 or external to processor 11 or 21, in which case those external components may be communicatively coupled to processor 11 or 21 in various ways known in the art.

[0089] In some embodiments, the processor 11 is configured with uplink (UL) grant resources, enabling the UE to perform UL data transmission in an inactive state based on the configured UL grant resources. Furthermore, the processor is configured to perform UL data transmission on the configured UL grant resources in the inactive state based on the transmission characteristics of the UL data transmission and at least one transmission threshold. This addresses problems in the prior art, improves the issues of increased power consumption and signaling burden, and provides superior communication performance and / or high reliability.

[0090] In some embodiments, the processor 21 configures uplink (UL) grant resources for the UE, enabling the UE to perform UL data transmission in an inactive state based on the configured UL grant resources, and is configured to receive the UL data transmission from the UE. The UL data transmission is based on the transmission characteristics of the UL data transmission and at least one transmission threshold, and is performed on the configured UL grant resources in the inactive state. This can solve the problems in the prior art, improve the issues of increased power consumption and signaling burden, and provide excellent communication performance and / or high reliability.

[0091] Figure 1C A wireless communication method 100 performed by a user equipment (UE) according to an embodiment of this application is illustrated. In some embodiments, the method 100 includes: block 102, configuring uplink (UL) licensed resources for the UE via a base station to perform UL data transmission in an inactive state based on the configured UL licensed resources; and block 104, performing UL data transmission on the configured UL licensed resources in the inactive state based on the transmission characteristics of the UL data transmission and at least one transmission threshold. This can solve the problems in the prior art, improve the problems of increased power consumption and signaling burden, and provide excellent communication performance and / or high reliability.

[0092] Figure 1D A wireless communication method 120 performed by a base station according to an embodiment of this application is illustrated. In some embodiments, the method 120 includes: block 122, configuring uplink (UL) grant resources for a UE to enable the UE to perform UL data transmission in an inactive state based on the configured UL grant resources; and block 124, receiving the UL data transmission from the UE, the UL data transmission being performed on the configured UL grant resources in the inactive state based on the transmission characteristics of the UL data transmission and at least one transmission threshold. This can solve the problems in the prior art, improve the problems of increased power consumption and signaling burden, and provide excellent communication performance and / or high reliability.

[0093] In some embodiments, the inactive state is an RRC_INACTIVE state, where RRC stands for Radio Resource Control. In some embodiments, the transmission characteristics include at least one of transmission priority, delay or periodicity, channel access priority class, and access class. In some embodiments, the transmission threshold includes a data volume threshold.

[0094] In some embodiments, the UL grant resource is a cell-based pre-configured grant (PCG) resource. In some embodiments, the UL grant resource is a pre-configured UL grant resource configured via RRC signaling for each Bandwidth Part (BWP) and each serving cell when the UE enters the inactive state. In some embodiments, the UL grant resource is configured by at least one PCG configuration. In some embodiments, the UL grant resource is pre-configured by a UE context identifier. In some embodiments, the UE context identifier includes an inactive-Radio Network Temporary Identifier (I-RNTI). In some embodiments, when the UE is stationary on a serving cell configured with the PCG resource, the PCG resource is available to the UE for UL data transmission in the inactive state. In some embodiments, the method further includes checking whether the UE is stationary on the same serving cell based on at least one of a cell identifier and a received signal strength threshold. In some embodiments, the UE is stationary on the same serving cell in response to checking based on the received signal strength threshold, where the received signal strength threshold is a reference signal received power (RSRP) threshold. In some embodiments, the method further includes: when the UE enters the inactive state for mobility considerations, checking whether the UE remains on the same serving cell.

[0095] In some embodiments, the UL grant resource is a RAN Notification Area-based (RNA-based) PCG (RBPCG) resource. In some embodiments, the UL grant resource is a pre-configured UL grant resource configured via RRC signaling for each RNA within a predetermined Bandwidth Part (BWP) when the UE enters the inactive state. In some embodiments, the UL grant resource is configured by at least one RBPCG configuration. In some embodiments, the UL grant resource is pre-configured by at least one of a UE context identifier and a RAN Notification Area identifier. In some embodiments, the RAN Notification Area identifier includes an RNA ID. In some embodiments, when the UE leaves the coverage area of ​​the serving cell but remains within the RAN Notification Area, the RBPCG resource is used by the UE within the RAN Notification Area for UL data transmission in the inactive state. In some embodiments, the method further includes checking whether the UE remains in the same Radio Access Network (RAN) Notification Area (RNA) based on at least one of an RNA identifier or a received signal strength threshold. In some embodiments, in response to checking whether the UE remains on the same RNA based on the received signal strength threshold, the received signal strength threshold being a reference signal received power (RSRP) threshold. In some embodiments, the method further includes: when the UE enters the inactive state for mobility considerations, checking whether the UE remains on the same RNA.

[0096] In some embodiments, the UL data transmission in the inactive state is a random access (RA) based transmission with a contention-free random access (CFRA) procedure triggered by at least one of the following events: the UE in the inactive state is stationary or stationary on a serving cell serving the UE; the UE in the inactive state leaves the coverage area of ​​the serving cell with a seamless CFRA configuration; CFRA resources are allocated to the UE in the inactive state; aperiodic and / or low-latency UL data transmission occurs in the inactive state; and transmission is not possible on configured grant (CG) resources. In some embodiments, the UL data transmission in the inactive state is a random access (RA) based transmission with a contention-based random access (CBRA) procedure triggered by at least one of the following events: the UE in the inactive state leaves the coverage area of ​​the serving cell without any CFRA configuration; CFRA resources are not configured for the UE in the inactive state; non-periodic and / or low-priority UL data transmission occurs in the inactive state; and the CFRA procedure cannot be executed on the configured grant (CG) resources.

[0097] In some embodiments, the UL data transmission in the inactive state is performed in a two-step RA procedure. In some embodiments, the UL data transmission in the inactive state is carried by the MSGA in the two-step RA procedure, and the MSGA in the two-step RA procedure carries a response from the base station. In some embodiments, the MSGA in the two-step RA procedure includes a dedicated preamble on the physical random access channel (PRACH) and a unique UE context identifier for contention resolution. In some embodiments, when the UE enters the inactive state, the UL grant resources are configured for MSGA transmission.

[0098] In some embodiments, the method further includes: performing a two-step RA procedure to implement the UL data transmission in the inactive state. In some embodiments, the method further includes: in response to the failure of the two-step RA procedure, performing a four-step RA procedure to implement the UL data transmission. In some embodiments, in the four-step RA procedure, the UL data transmission is implemented when the UE is in the inactive state. In some embodiments, in the four-step RA procedure, the UL data transmission is implemented when the UE is in a connected state. In some embodiments, the connected state is an RRC_CONNECTED state. In some embodiments, the method further includes: in response to the failure of the two-step RA procedure, performing a four-step CFRA procedure to implement the UL data transmission. In some embodiments, the dedicated PRACH preamble in the two-step RA procedure is shared with the four-step CFRA procedure. In some embodiments, the method further includes: in response to the failure of the four-step CFRA procedure, performing a four-step CBRA procedure to implement the UL data transmission. In some embodiments, the method further includes: in response to the failure of the two-step RA procedure, performing a four-step CBRA procedure to implement the UL data transmission.

[0099] In some embodiments, the method further includes negotiating the configuration of the UL licensed resources between a serving cell serving the UE and a target cell having the same RAN Notification Area (RNA) identifier as the serving cell. The method also includes: sending a notification to either the serving cell or the target cell to activate the configuration of the UL licensed resources when the UE moves across the boundary of the serving cell; and performing UL data transmission in the inactive state based on the configuration of the UL licensed resources in the target cell. In some embodiments, the method further includes performing seamless UL data transmission in the inactive state in response to the target cell allocating time / frequency UL licensed resources in the same manner as the serving cell. In some embodiments, the method further includes obtaining the configuration of the UL licensed resources of the target cell via RAN paging in response to the inability of the target cell and the serving cell to allocate the same time / frequency UL licensed resources. In some embodiments, the notification is carried in a proximity indication.

[0100] In some embodiments, the configuration of the UL licensed resources is negotiated between a serving RNA and a target RNA. The serving RNA has a serving cell serving the UE, and the target RNA has a target cell with an RNA identifier different from that of the serving cell. The method further includes: when the UE moves across the boundary of the serving cell, sending a notification to either the serving cell / RNA or the target cell / RNA to activate the configuration of the UL licensed resources; and performing UL data transmission in the inactive state based on the configuration of the UL licensed resources in the target cell within the target RNA. In some embodiments, the method further includes: in response to the target cell allocating time / frequency UL licensed resources in the same manner as the serving cell, performing seamless UL data transmission in the inactive state. In some embodiments, the method further includes: in response to the target cell and the serving cell being unable to allocate the same time / frequency UL licensed resources, obtaining the configuration of the UL licensed resources of the target cell through paging in the core network (CN). In some embodiments, the notification is carried in an RNA update.

[0101] In some embodiments, the method further includes: sending an RRC request to a serving cell serving the UE or a target cell with which the UE will communicate during the inactive state; and, without a state transition, obtaining the configuration of UL licensed resources of the serving cell or the target cell during the inactive state. In some embodiments, the RRC request is an on-demand system information (SI) request. In some embodiments, the configuration of the UL licensed resources is a contention-free configuration of the UL licensed resources. In some embodiments, the transmission of the RRC request is contention-based or contention-free. In some embodiments, the configuration of the UL licensed resources is negotiated between the UE's serving cell and neighboring cells.

[0102] In some embodiments, based on the dual connectivity (DC) configuration of the primary RAN node and the secondary RAN node, the UL data transmission on the UL licensed resources in the inactive state is provided to the primary RAN node and the secondary RAN node. In some embodiments, the method further includes: sending a notification to the primary RAN node to request DC reconfiguration and UL license reconfiguration; and performing the UL data transmission in the inactive state based on the reconfigured DC configuration of the primary RAN node and the new secondary RAN node and the UL licensed resources of the new secondary RAN node. In some embodiments, the method further includes: sending an RRC request to the primary RAN node in the inactive state to request DC reconfiguration and UL license reconfiguration; and, without a state transition, obtaining the reconfigured DC configuration of the primary RAN node and the new secondary RAN node and the UL licensed resources of the new secondary RAN node from the primary RAN node in the inactive state. In some embodiments, the RRC request is an on-demand system information (SI) request.

[0103] In some embodiments, UL data transmission on the UL licensed resources in the inactive state is performed on one or more non-public networks (NPNs). In some embodiments, the method further includes: checking whether the UE is residing in the same serving cell of the one or more NPNs based on at least one of a cell identifier and a received signal strength threshold. In some embodiments, in response to checking whether the UE is residing in the same serving cell based on the cell identifier, the cell identifier is listed in a list of allowed cells for an NPN user. In some embodiments, in response to checking whether the UE is residing in the same serving cell based on the received signal strength threshold, the received signal strength threshold being a reference signal received power (RSRP) threshold. In some embodiments, the method further includes: checking whether the UE is residing in the same serving cell when the UE enters the inactive state for mobility considerations. In some embodiments, the method further includes: sending a notification to the one or more NPNs to activate the configuration of the UL licensed resources of the NPN user in the one or more NPNs; and performing the UL data transmission in the inactive state based on the UL licensed resources of the NPN user. In some embodiments, the method further includes: sending an RRC request to the one or more NPNs in the inactive state; and, without a state transition, obtaining the configuration of UL authorization resources for NPN users in the one or more NPNs in the inactive state. In some embodiments, the RRC request is an on-demand system information (SI) request.

[0104] In some embodiments, the method further includes: determining, based on the transmission characteristics, whether to perform the UL data transmission in the inactive state on PCG resources or on two-step RA resources. In some embodiments, the at least one transmission threshold includes a first transmission threshold and a second transmission threshold, and the method includes: determining, based on the first transmission threshold, whether to perform the UL data transmission in the inactive state on the PCG resources; and determining, based on the second transmission threshold, whether to perform the UL data transmission in the inactive state on the two-step RA resources. In some embodiments, the method further includes: in response to the failure of the UL data transmission on the PCG resources, but the UL data transmission is below the second transmission threshold, performing the UL data transmission in the inactive state on the two-step RA resources. In some embodiments, the method further includes: in response to the UL data transmission exceeding the first transmission threshold or the second transmission threshold, performing the UL data transmission in a four-step RA procedure. In some embodiments, in the four-step RA procedure, the UE enters a connected state to perform the UL data transmission. In some embodiments, the method further includes: in response to the failure of the UL data transmission on the PCG resources or on the two-step RA resources, performing the UL data transmission in a four-step RA procedure. In some embodiments, during the four-step RA procedure, the UE enters a connected state to perform the UL data transmission. In some embodiments, the method further includes: determining, based on the transmission characteristics, whether to perform the UL data transmission in the inactive state on RBPCG resources or on two-step RA resources. In some embodiments, the at least one transmission threshold includes a first transmission threshold and a second transmission threshold, and the method includes: determining, based on the first transmission threshold, whether to perform the UL data transmission in the inactive state on RBPCG resources; and determining, based on the second transmission threshold, whether to perform the UL data transmission in the inactive state on two-step RA resources.

[0105] The first embodiment of this application, for example Figure 2A and Figure 2B As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. More specifically, Figure 2A This illustrates a small amount of data transmission by a UE in the RRC_INACTIVE state according to an embodiment of this application, based on a cell-based data transmission. Figure 2BThis illustrates an example of a UE transmitting small amounts of data in the RRC_INACTIVE state according to an embodiment of this application. The network supports small amounts of data transmission of PCG and RA types in the RRC_INACTIVE state. The PCG transmission threshold and the RA transmission threshold can be configured to be the same or different. Here, for example, but not limited to, the PCG transmission threshold and the two-step RA transmission threshold are assumed to be 32 bytes and 56 bits, respectively. In blocks 201 (and 210), for mobility considerations, when entering the RRC_INACTIVE state, an inactive UE checks (e.g., by monitoring the cell identifier and RSRP threshold) whether it remains in the same serving cell. In blocks 202 (and 211), when an inactive UE remains in the same serving cell and if UL data is transmitted to the UE's transmission buffer, the inactive UE detects the traffic characteristic (e.g., high priority, low latency, periodicity, aperiodicity, channel access priority category table, access category) in blocks 204 (and 212) to determine whether to transmit on the two-step RA or PCG resources. For example, but not limited to, if the UL data is periodic and below the PCG transmission threshold (e.g., the UL data size is less than 32 bytes), the PCG procedure can be used for UL data transmission, as in blocks 213 and 215. In some cases, as in block 216, when transmission on the PCG fails due to UL preemption and the UL data is less than the two-step RA transmission threshold (e.g., the UL data size is also less than 56 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission, as in block 217. Otherwise (as in block 218), an inactive UE can perform a four-step CFRA / CBRA to transmit a small amount of UL data in MSG3, as in blocks 219 and 220. On the other hand, if the UL data is infrequent and less than the two-step RA transmission threshold (e.g., the UL data size is also less than 56 bits), the inactive UE can perform a two-step CFRA / CBRA procedure for UL data transmission, as in block 214. Otherwise, the inactive UE can perform a four-step CFRA / CBRA to transmit a small amount of UL data in MSG3, as in blocks 219 and 220. Whether to perform CFRA or CBRA depends on the network configuration (e.g., PRACH configuration). The inactive UE is configured to perform UL data transmission based on the above-described determination method. PCG and RA resources can be configured when the UE enters the RRC_INACTIVE state. In some cases, as in block 203, once the serving cell changes, the inactive UE can use a one-way indication scheme or a two-way request scheme to activate the "inactive" UL authorized resources.

[0106] In some cases, upon receiving an RA response for UL data transmission, an inactive UE will transition to the RRC_CONNECTED state. If the four-step CFRA procedure fails, the inactive UE should execute a four-step CBRA procedure to enter the RRC_CONNECTED state, as shown in block 205. This transmission threshold may include, but is not limited to, a data volume threshold. In some cases, the gNB can configure different transmission thresholds for PCG resources, two-step RA resources, and four-step RA resources. In some cases, the gNB can configure the same transmission threshold for PCG resources, two-step RA resources, and four-step RA resources, where this threshold is used to determine the PCG first, then the two-step RA, and finally the four-step RA. In some cases, the gNB can configure different transmission thresholds for PCG resources and either the two-step RA resources or the four-step RA resources. In some cases, the gNB can configure the same transmission threshold for PCG resources and either the two-step RA resources or the four-step RA resources, where this threshold is used to determine the PCG first, then the RA. In some cases, the gNB can configure different transmission thresholds for the two-step RA resources and the four-step RA resources. In some cases, the gNB can configure the same transmission threshold for both two-step RA resources and four-step RA resources, and this threshold is used to determine the two-step RA first, followed by the four-step RA. In some cases, the gNB can configure PCG resources; if the threshold is met, data is transmitted in an inactive state. In some cases, the gNB can configure two-step RA resources; if the threshold is met, data is transmitted in an inactive state. In some cases, the gNB can configure four-step RA resources; if the threshold is met, data is transmitted in an inactive state.

[0107] The second embodiment of this application, for example Figure 3A and Figure 3B As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. More specifically, Figure 3A This illustrates a small amount of data transmission based on RNA in the RRC_INACTIVE state of a UE according to an embodiment of this application. Figure 3BThis illustrates an example of a small amount of RNA-based data transmission by a UE in the RRC_INACTIVE state according to an embodiment of this application. The network supports small amounts of RBPCG and RA type data transmission in the RRC_INACTIVE state. The RBPCG transmission threshold and the RA transmission threshold can be configured to be the same or different. Here, for example, but not limited to, the RBPCG transmission threshold and the two-step RA transmission threshold are assumed to be 256 bytes and 72 bits, respectively. In blocks 301 (and 310), for mobility considerations, upon entering the RRC_INACTIVE state, an inactive UE switches to a predetermined BWP and checks (e.g., by monitoring the RNA identifier and the RSRP threshold) whether it remains in the same RNA. In blocks 302 (and 311), when an inactive UE remains on the same serving RNA and if UL data is transmitted to the UE's transmission buffer, the inactive UE detects the traffic characteristic (e.g., high priority, low latency, periodicity, aperiodicity, channel access priority category table, access category) in blocks 304 (and 312) to determine whether to transmit on the two-step RA or RBPCG resources. For example, but not limited to, if the UL data is periodic and below the RBPCG transmission threshold (e.g., the UL data size is less than 256 bytes), the RBPCG procedure can be used for UL data transmission, as in blocks 313 and 315. In some cases, as in block 316, when transmission on the RBPCG fails due to UL preemption and the UL data is less than the two-step RA transmission threshold (e.g., the UL data size is also less than 72 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission, as in block 317. Otherwise (as in block 318), the inactive UE can perform a four-step CFRA / CBRA to transmit a small amount of UL data in MSG3, as in blocks 319 and 320. On the other hand, if the UL data is infrequent and less than the two-step RA transmission threshold (e.g., the UL data size is also less than 72 bits), the inactive UE can perform a two-step CFRA / CBRA procedure for UL data transmission, as in block 314. Otherwise, the inactive UE can perform a four-step CFRA / CBRA to transmit a small amount of UL data in MSG3, as in blocks 319 and 320. Whether to perform CFRA or CBRA depends on the network configuration (e.g., PRACH configuration). The inactive UE is configured to perform UL data transmission based on the above-described determination method. RBPCG and RA resources can be configured when the UE enters the RRC_INACTIVE state.In some cases, in block 303, once the RNA changes, an inactive UE can use a one-way indication scheme or a two-way request scheme to activate the "inactive" UL authorized resources.

[0108] In some cases, upon receiving an RA response for UL data transmission, an inactive UE will transition to the RRC_CONNECTED state. If the four-step CFRA procedure fails, the inactive UE should execute a four-step CBRA procedure to enter the RRC_CONNECTED state. This transmission threshold may include, but is not limited to, a data volume threshold. In some cases, the gNB can configure different transmission thresholds for RBPCG resources, two-step RA resources, and four-step RA resources. In some cases, the gNB can configure the same transmission threshold for RBPCG resources, two-step RA resources, and four-step RA resources, where this threshold is used to determine RBPCG first, then two-step RA, and finally four-step RA. In some cases, the gNB can configure different transmission thresholds for RBPCG resources and either two-step RA resources or four-step RA resources. In some cases, the gNB can configure the same transmission threshold for RBPCG resources and either two-step RA resources or four-step RA resources, where this threshold is used to determine RBPCG first, then RA. In some cases, the gNB can configure different transmission thresholds for two-step RA resources and four-step RA resources. In some cases, the gNB can configure the same transmission threshold for both two-step RA resources and four-step RA resources, and this threshold is used to determine the two-step RA first, followed by the four-step RA. In some cases, the gNB can configure RBPCG resources; if the threshold is met, data is transmitted in an inactive state. In some cases, the gNB can configure two-step RA resources; if the threshold is met, data is transmitted in an inactive state. In some cases, the gNB can configure four-step RA resources; if the threshold is met, data is transmitted in an inactive state.

[0109] The third implementation of this application, for example Figure 4 As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. Specifically, Figure 4This illustrates a cell-based one-way indication scheme for a UE in the RRC_INACTIVE state according to an embodiment of this application. The network supports limited data transmission of PCG and RA types in the RRC_INACTIVE state. The PCG transmission threshold and RA transmission threshold can be configured to be the same or different to transmit data via PCG or RA type. Here, for example, but not limited to, the PCG transmission threshold and the two-step RA transmission threshold are assumed to be 32 bytes and 56 bits, respectively. In block 420, for mobility considerations, when entering the RRC_INACTIVE state, an inactive UE checks (e.g., by monitoring the cell identifier, RSRP threshold) whether it is staying in the same serving cell. When the UE enters the RRC_INACTIVE state or detects that the cell ID is different from the serving cell ID, it can perform the one-way indication scheme in block 430 before / after moving to the target cell. When UL data arrives at the UE's transmission buffer, the inactive UE detects the traffic characteristics (e.g., high priority, low latency, periodicity, aperiodicity, channel access priority category table, access category) to determine whether to transmit on a two-step RA or PCG resource. For example, if the UL data is periodic and below the PCG transmission threshold (e.g., the UL data size is less than 32 bytes), the PCG procedure can be used for UL data transmission. In some cases, when transmission on the PCG fails due to UL preemption, and the UL data is less than the two-step RA transmission threshold (e.g., the UL data size is also less than 56 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, the inactive UE can execute a four-step CFRA / CBRA procedure for a small amount of UL data transmission in MSG3. On the other hand, if the UL data is infrequent and less than the two-step RA transmission threshold (e.g., the UL data size is also less than 56 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, an inactive UE can perform a four-step CFRA / CBRA to transmit a small amount of UL data in MSG3. Whether to perform CFRA or CBRA depends on the network configuration (e.g., PRACH configuration). The inactive UE is configured to perform UL data transmission based on the above-described determination method. PCG and RA resources can be configured when the UE enters the RRC_INACTIVE state. In this embodiment, the inactive UE uses a one-way indication scheme to activate the "inactive" UL grant resources of the target cell. Before receiving the one-way indication, the serving cell and the candidate / target cell should negotiate the PCG / CFRA configuration in block 410.

[0110] The fourth embodiment of this application, for example Figure 5As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. Specifically, Figure 5 This illustrates a cell-based bidirectional request scheme for a UE in the RRC_INACTIVE state according to an embodiment of this application. The network supports a small amount of data transmission of PCG and RA types in the RRC_INACTIVE state. The PCG transmission threshold and RA transmission threshold can be configured to be the same or different. Here, for example, but not limited to, the PCG transmission threshold and the two-step RA transmission threshold are assumed to be 32 bytes and 56 bits, respectively. In block 520, for mobility considerations, when entering the RRC_INACTIVE state, the inactive UE checks (e.g., by monitoring the cell identifier, RSRP threshold) whether it is staying in the same serving cell. When the inactive UE needs to obtain the PCG / RA configuration of the serving cell and / or the target cell, it can perform a bidirectional request scheme with the associated cell in block 530. If UL data is transmitted to the UE's transmission buffer, the inactive UE detects the traffic characteristic (e.g., high priority, low latency, periodicity, aperiodicity, channel access priority category table, access category) to determine whether to transmit on the two-step RA or PCG resources. For example, if the UL data is periodic and below the PCG transmission threshold (e.g., the UL data size is less than 32 bytes), the PCG procedure can be used for UL data transmission. In some cases, when transmission on the PCG fails due to UL preemption, and the UL data is less than the two-step RA transmission threshold (e.g., the UL data size is also less than 56 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, the inactive UE can execute a four-step CFRA / CBRA procedure for a small amount of UL data transmission in MSG3. On the other hand, if the UL data is infrequent and less than the two-step RA transmission threshold (e.g., the UL data size is also less than 56 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, the inactive UE can execute a four-step CFRA / CBRA procedure for a small amount of UL data transmission in MSG3. Whether to execute CFRA or CBRA depends on the network configuration (e.g., PRACH configuration). The inactive UE is configured to perform UL data transmission based on the above-described determination method. PCG and RA resources can be configured when the UE enters the RRC_INACTIVE state or receives an RRC request. In this embodiment, an inactive UE uses a two-way request scheme to obtain the PCG and RA configuration of the target cell. Before receiving the RRC request, the serving cell and the candidate / target cell can optionally negotiate the PCG / RA configuration in block 510.

[0111] The fifth implementation of this application, for example Figure 6 As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. Specifically, Figure 6This illustrates an RNA-based one-way indication scheme for a UE in the RRC_INACTIVE state according to an embodiment of this application. The network supports a small amount of data transmission of RBPCG and RA types in the RRC_INACTIVE state. The RBPCG transmission threshold and the RA transmission threshold can be configured to be the same or different. Here, for example, but not limited to, the RBPCG transmission threshold and the two-step RA transmission threshold are assumed to be 256 bytes and 72 bits, respectively. In block 620, for mobility considerations, when entering the RRC_INACTIVE state, an inactive UE checks (e.g., by monitoring the RNA identifier, RSRP threshold) whether it is staying in the same serving RNA. When the UE enters the RRC_INACTIVE state or detects that the candidate / target RNA ID is different from the serving RNA ID, it can perform the one-way indication scheme in block 630 before moving to the target RNA. When UL data arrives at the UE's transmission buffer, the inactive UE detects the traffic characteristic (e.g., high priority, low latency, periodicity, aperiodicity, channel access priority class table, access class) to determine whether to transmit on a two-step RA or RBPCG resource. For example, if the UL data is periodic and below the RBPCG transmission threshold (e.g., the UL data size is less than 256 bytes), the RBPCG procedure can be used for UL data transmission. In some cases, when transmission on the RBPCG fails due to UL preemption and the UL data is less than the two-step RA transmission threshold (e.g., the UL data size is also less than 72 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, the inactive UE can execute a four-step CFRA / CBRA procedure for a small amount of UL data transmission in MSG3. On the other hand, if the UL data is infrequent and less than the two-step RA transmission threshold (e.g., the UL data size is also less than 72 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, an inactive UE can perform a four-step CFRA / CBRA to transmit a small amount of UL data in MSG3. Whether to perform CFRA or CBRA depends on the network configuration (e.g., PRACH configuration). The inactive UE is configured to perform UL data transmission based on the above-described determination method. RBPCG and RA resources can be configured when the UE enters the RRC_INACTIVE state. In this embodiment, the inactive UE uses a one-way indication scheme to activate the "inactive" UL grant resources of the target RNA. Before receiving the one-way indication, the serving RNA and the candidate / target RNA should negotiate the RBPCG / CFRA configuration in block 610.

[0112] The sixth embodiment of this application, for example Figure 7 As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. Specifically, Figure 7This illustrates a bidirectional request scheme based on RNA for a UE in the RRC_INACTIVE state according to an embodiment of this application. The network supports a small amount of data transmission of RBPCG and RA types in the RRC_INACTIVE state. The RPCG transmission threshold and the RA transmission threshold can be configured to be the same or different. Here, for example, but not limited to, the RBPCG transmission threshold and the two-step RA transmission threshold are assumed to be 256 bytes and 72 bits, respectively. In block 720, for mobility considerations, when entering the RRC_INACTIVE state, an inactive UE checks (e.g., by monitoring the RNA identifier and RSRP threshold) whether it is residing in the same serving RNA. When the inactive UE needs to obtain the RBPCG / RA configuration of the serving RNA and / or the target RNA, it can perform a bidirectional request scheme in block 730 with the cell where it resides in the associated RNA. When UL data arrives at the UE's transmission buffer, the inactive UE detects the traffic characteristic (e.g., high priority, low latency, periodicity, aperiodicity, channel access priority class table, access class) to determine whether to transmit on a two-step RA or RBPCG resource. For example, if the UL data is periodic and below the RBPCG transmission threshold (e.g., the UL data size is less than 256 bytes), the RBPCG procedure can be used for UL data transmission. In some cases, when transmission on the RBPCG fails due to UL preemption and the UL data is less than the two-step RA transmission threshold (e.g., the UL data size is also less than 72 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, the inactive UE can execute a four-step CFRA / CBRA procedure for a small amount of UL data transmission in MSG3. On the other hand, if the UL data is infrequent and less than the two-step RA transmission threshold (e.g., the UL data size is also less than 72 bits), the inactive UE can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, an inactive UE can perform a four-step CFRA / CBRA to transmit a small amount of UL data in MSG3. Whether to perform CFRA or CBRA depends on the network configuration (e.g., PRACH configuration). The inactive UE is configured to perform UL data transmission based on the above-described determination method. RBPCG and RA resources can be configured when the UE enters the RRC_INACTIVE state or receives an RRC request. In this embodiment, the inactive UE uses a bidirectional request scheme to obtain the RBPCG and CFRA configuration of the target cell. Before receiving the RRC request, the serving RNA and candidate / target RNA can optionally negotiate the RBPCG / RA configuration in block 710.

[0113] The seventh embodiment of this application, for example Figure 8 As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. Specifically, Figure 8 This illustrates a small amount of data transmission by the UE in the RRC_INACTIVE state for an NPN application according to an embodiment of this application. A non-public network (also known as a private network) is a physical or virtual cellular system deployed for the private use of a subscriber. Non-public Network (NPN) is the term used by 3GPP for this type of network. An NPN is a 5GS system deployed in two types:

[0114] • Standalone NPN (SNPN): Operated by the NPN operator, it does not rely on network functionality provided by the PLMN. An SNPN is identified by a combination of the PLMN ID and a Network Identifier (NID). Optionally, a human-readable network name (HRNN) for each NID can be used for manual NPN selection.

[0115] • Public Network Integrated Non-Public Network (PNI-NPN): This is an integration supported by the PLMN. A PNI-NPN is identified by a combination of the PLMN ID and the Closed Access Group identifier (CAG ID). Optionally, a human-readable network name (HRNN) for each CAG ID can be used for manual NPN selection.

[0116] For low-latency, low-volume data transmission in the RRC_INACTIVE state on non-public networks (NPNs) under mobility considerations, the proposed one-way indication scheme or two-way request scheme can be applied to NPN subscribers. Mobility of inactive NPN subscribers can be restricted based on a list of allowed cells / RNAs. Therefore, the allowed NPN cells listed in the mobility restrictions can be used to configure PCG / RBPCG / RA resources for inactive NPN subscribers. Under mobility considerations, when entering the RRC_INACTIVE state, inactive NPN subscribers check (e.g., by monitoring NPN cell / RNA identifiers, which may include PLMN ID, NID, CAG ID, HRNN, etc., or RSRP thresholds) whether they are staying in the same serving cell / RNA, as shown in block 820. When an inactive NPN subscriber detects that the NPN cell / RNA ID is different from the serving cell / RNA ID, it can execute the one-way indication scheme or two-way request scheme in block 830 before / after moving to the target cell / RNA to activate inactive UL authorized resources. When UL data arrives at an NPN user's transmission buffer, the inactive NPN user detects the traffic characteristic (e.g., high priority, low latency, periodicity, aperiodicity, channel access priority category table, access category) to determine whether to transmit on a two-step RA or PCG / RBPCG resource. For example, if the UL data is periodic and below the PCG / RBPCG transmission threshold, the PCG / RBPCG procedure can be used for UL data transmission. In some cases, when transmission on the PCG / RBPCG fails due to UL preemption and the UL data is less than the two-step RA transmission threshold, the inactive NPN user can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, the inactive NPN user can execute a four-step CFRA / CBRA procedure for a small amount of UL data transmission in MSG3. On the other hand, if the UL data is infrequent and less than the two-step RA transmission threshold, the inactive NPN user can execute a two-step CFRA / CBRA procedure for UL data transmission. Otherwise, the inactive NPN user can execute a four-step CFRA / CBRA procedure for a small amount of UL data transmission in MSG3. Whether to perform CFRA or CBRA depends on the network configuration (e.g., PRACH configuration). Inactive NPN users are configured to perform UL data transmission based on the above-described determination method. Negotiation of PCG / RBPCG / RA configurations can be performed between NPN cells / RNAs in block 810.

[0117] The eighth embodiment of this application, for example Figure 9As shown, it illustrates an implementation scenario of signal transmission between UE 10 and base station 20 according to this application. Specifically, Figure 9 This illustrates a small amount of data transmission by a UE in the RRC_INACTIVE state, supporting DC applications according to embodiments of this application. For MR-DC and NR-DC, if the network supports at least a dual connectivity (DC) configuration, this DC configuration is maintained in the RRC_INACTIVE state to avoid unnecessary signaling burden and resource consumption. Inactive UEs can transmit URLLC data to the master RAN node and secondary RAN node on PCG / RBPCG / CFRA / CBRA resources. When an inactive UE detects in block 920 that one of the multiple secondary RAN node configurations is about to fail due to mobility or channel conditions (e.g., moving to a secondary RNA node, outside the coverage area of ​​the RNA, exceeding the RSPP threshold), in block 930, the proposed one-way indication scheme or two-way request scheme can be applied to request inactive DC reconfiguration and inactive UL authorization reconfiguration. The inactive UE can send this indication or on-demand SI request to the master RAN node to request inactive DC reconfiguration and inactive UL authorization reconfiguration. Once an inactive UE requests inactive DC reconfiguration and inactive UL authorization reconfiguration, the network can apply the proposed one-way indication scheme or two-way request scheme to switch the PCG / RBPCG / RA configurations of the secondary RAN node and the secondary RAN node. Negotiation of the PCG / RBPCG / RA configurations can be conducted between the primary RAN node and the secondary RAN node in block 910.

[0118] Some embodiments offer the following commercial benefits: 1. Solving problems in the prior art. 2. Improving the problems of increased power consumption and signaling burden. 3. Providing superior communication performance. 4. Providing high reliability. 5. Some embodiments of this application are used by 5G-NR chipset suppliers, V2X communication system development suppliers, automobile manufacturers (including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc.), drone (unmanned aerial vehicle) manufacturers, smartphone manufacturers, communication equipment manufacturers for public safety purposes, and AR / VR device manufacturers (e.g., for gaming, conferences / seminars, educational purposes). Some embodiments of this application are combinations of "technologies / processes" that can be adopted in 3GPP specifications to develop terminal products. Some embodiments of this application can be used in 5GNR unlicensed frequency band communications. Some embodiments of this application propose technical solutions.

[0119] Figure 10This is a block diagram of an example system 1000 for wireless communication according to an embodiment of this application. The embodiments described herein can be implemented in this system using any appropriately configured hardware and / or software. Figure 10 System 1000 is illustrated, comprising radio frequency (RF) circuitry 1010, baseband circuitry 1020, application circuitry 1030, memory / storage device 1040, display 1050, camera 1060, sensor 1070, and input / output (I / O) interface 1080, which are coupled to each other at least as shown. Application circuitry 1030 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors and application processors). The processor may be coupled to the memory / storage device and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems to run on the system.

[0120] The baseband circuit 1020 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry can handle various wireless control functions that enable communication with one or more wireless networks via RF circuitry. Wireless control functions may include, but are not limited to, signal modulation, encoding, decoding, and radio frequency shifting. In some embodiments, the baseband circuitry can provide communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other Wireless Wide Area Networks (WMAN), Wireless Local Area Networks (WLAN), and Wireless Personal Area Networks (WPAN). Embodiments in which the baseband circuitry is configured to support wireless communication using more than one wireless protocol may be referred to as a multi-mode baseband circuitry.

[0121] In various embodiments, the baseband circuit 1020 may include circuitry for operating with signals that are not strictly considered to be in the baseband frequency range. For example, in some embodiments, the baseband circuitry may include circuitry for operating with signals having an intermediate frequency between the baseband frequency and the radio frequency (RF). The RF circuitry 1010 may use modulated electromagnetic radiation through a non-solid-state medium to achieve communication with a wireless network. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. In various embodiments, the RF circuitry 1010 may include circuitry for operating with signals that are not strictly considered to be in the RF range. For example, in some embodiments, the RF circuitry may include circuitry for operating with signals having an intermediate frequency between the baseband frequency and the RF frequency.

[0122] In various embodiments, the transmitting, control, or receiving circuitry discussed above with respect to user equipment, eNB, or gNB may be implemented, in whole or in part, in one or more of the RF circuitry, baseband circuitry, and / or application circuitry. As used herein, “circuit” may refer to, be part of, or include: application-specific integrated circuits (ASICs), electronic circuitry executing one or more software or firmware programs, processors and / or memory (shared, dedicated, or grouped), combined logic circuitry, and / or other suitable hardware components providing the described functionality. In some embodiments, the electronic device circuitry system may be implemented in one or more software or firmware modules, or the functionality associated with the circuitry system may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and / or memory / storage device may be implemented together on a system-on-a-chip (SOC). The memory / storage device 1040 may be used to load and store, for example, data and / or instructions for the system. The memory / storage device of one embodiment may include any combination of suitable volatile memory (e.g., dynamic random access memory (DRAM)) and / or non-volatile memory (e.g., flash memory).

[0123] In various embodiments, I / O interface 1080 may include one or more user interfaces and / or peripheral component interfaces, the user interfaces being designed to enable a user to interact with the system, and the peripheral component interfaces being designed to enable peripheral components to interact with the system. User interfaces may include, but are not limited to, physical keyboards or keypads, touchpads, speakers, microphones, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory interfaces, universal serial bus (USB) interfaces, audio jacks, and power interfaces. In various embodiments, sensor 1070 may include one or more sensing devices for determining environmental conditions and / or location information relevant to the system. In some embodiments, sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. Positioning units may also be part of or interact with baseband circuitry and / or RF circuitry to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites).

[0124] In various embodiments, display 1050 may include displays such as liquid crystal displays and touch displays. In various embodiments, system 1000 may be a mobile computing device, such as, but not limited to, a laptop computer, tablet computer, notebook computer, ultra-thin notebook computer, smartphone, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as computer programs. The computer programs may be stored on storage media such as non-transitory storage media.

[0125] Those skilled in the art will understand that each unit, algorithm, and step described and disclosed in the embodiments of this application may be implemented using electronic hardware or a combination of software and electronic hardware for computers. Whether these functions operate in hardware or software depends on the application conditions and design requirements of the technical solution. Those skilled in the art may implement the functions of each specific application in different ways, and such implementation should not exceed the scope of this application. Those skilled in the art should understand that the working processes of the systems, devices, and units in the above embodiments can be referred to, as the working processes of the above systems, devices, and units are substantially the same. For ease of description and brevity, these working processes will not be described in detail.

[0126] It should be understood that the systems, apparatuses, and methods disclosed in the embodiments of this application can be implemented in other ways. The embodiments described above are merely illustrative. The division of units is based solely on logical function, and other divisions may exist during implementation. Multiple units or components may be combined or integrated into another system. Some features may also be omitted or skipped. On the other hand, the mutual coupling, direct coupling, or communication coupling shown or discussed may be indirect coupling or electrical, mechanical, or other forms of communication coupling through some interfaces, apparatuses, or units.

[0127] The units described as separate components may or may not be physically separate. The units shown may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be used depending on the purpose of the embodiment. Furthermore, the functional units in various embodiments may be integrated into one processing unit, or they may be physically independent, or two or more units may be integrated into one processing unit.

[0128] If software functional units are implemented and sold or used as independent products, they can be stored in a readable storage medium within a computer. Based on this understanding, the technical solutions proposed in this application can be implemented essentially or partially as software products. Alternatively, a portion of a technical solution beneficial to the prior art can be implemented as a software product. Software products in a computer are stored in a storage medium and include multiple commands for a computing device (e.g., a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this application. This storage medium includes a USB flash drive, a portable hard drive, read-only memory (ROM), random access memory (RAM), a floppy disk, or other media capable of storing code.

[0129] Although this application has been described in conjunction with what are considered to be the most practical and preferred embodiments, it should be understood that this application is not limited to the disclosed embodiments, but is intended to cover various arrangements made without departing from the broadest interpretation of the appended claims.

Claims

1. A wireless communication method performed by a user equipment (UE), characterized in that, The method includes: Receive uplink UL authorized resource configuration from the base station, wherein the UL authorized resource configuration is carried by radio resource control (RRC) signaling; The base station configures the UL licensed resource for the UE to perform UL data transmission in an inactive state based on the configured UL licensed resource, wherein the UL licensed resource is configured based on the UL licensed resource; and When the advance TA is valid, the UL data transmission is performed on the configured UL licensed resources in the inactive state based on the transmission characteristics of the UL data transmission and at least one transmission threshold. The UL licensed resources are either pre-configured licensed PCG resources based on the cell or PCG resources based on the radio access network notification area (RAN) RNA, which are RBPCG resources. The transmission characteristics include at least one of priority, delay or periodicity, channel access priority category, and access category. The transmission threshold includes a data volume threshold.

2. The method according to claim 1, characterized in that, The UL authorized resource is the cell-based PCG resource, wherein the UL authorized resource is a pre-configured UL authorized resource configured by RRC signaling for each bandwidth portion (BWP) and each serving cell when the UE enters the inactive state.

3. The method according to claim 1, characterized in that, The UL authorized resource is the RBPCG resource, wherein the UL authorized resource is a pre-configured UL authorized resource configured by RRC signaling in the predetermined bandwidth portion BWP according to each RNA when the UE enters the inactive state.

4. The method according to claim 3, characterized in that, When the UE leaves the coverage area of ​​the serving cell but remains within the RAN notification area, the RBPCG resources are available for the UE to use within the RAN notification area to perform the UL data transmission in the inactive state.

5. The method according to claim 1, characterized in that, In contention-based random access, the UE randomly selects a preamble from a preamble group associated with the transmission threshold of the small data transmission SDT to perform a two-step or four-step random access RA-SDT procedure.

6. The method according to claim 1, characterized in that, The method further includes: Perform a two-step RA procedure to achieve the UL data transmission in this inactive state; and In response to the failure of the two-step RA procedure, a four-step RA procedure is executed to realize the UL data transmission, wherein the UL data transmission is realized when the UE is in the inactive state or when the UE is in the connected state.

7. The method according to claim 1, characterized in that, The method further includes: Perform a two-step RA procedure to enable the UL data transmission in this inactive state; In response to the failure of the two-step RA procedure, a four-step RA procedure is executed to achieve the UL data transmission, wherein at least one PRACH preamble group in the two-step RA procedure is identical to that in the four-step RA procedure; and In response to the failure of the four-step RA procedure, a four-step random access procedure is executed to enter the connection state to realize the UL data transmission.

8. The method according to claim 1, characterized in that, The method further includes negotiating the UL licensed resource configuration between the serving cell serving the UE and a target cell having the same RAN notification area RNA identifier as the serving cell: When the UE moves across the boundary of the serving cell, a notification is sent to the serving cell or the target cell to activate the UL authorized resource configuration; and Based on the UL authorized resource configuration in the target cell, the UL data transmission is performed in the inactive state. The method further includes: In response to the target cell, time / frequency UL licensed resources are allocated in the same manner as the serving cell, enabling seamless UL data transmission during this inactive state; or In response to the inability to allocate the same time / frequency UL authorized resources to the target cell and the serving cell, the UL authorized resource configuration of the target cell is obtained through RAN paging.

9. The method according to claim 1, characterized in that, The method further includes negotiating the UL-authorized resource configuration between a serving RNA and a target RNA, wherein the serving RNA has a serving cell serving the UE, and the target RNA has a target cell with an RNA identifier different from the serving cell; the method also includes: When the UE moves across the boundary of the serving cell, a notification is sent to the serving cell / RNA or the target cell / RNA to activate the UL authorized resource configuration; and Based on the UL authorized resource configuration in the target cell within the target RNA, the UL data transmission is performed during the inactive state. The method further includes: In response to the target cell, time / frequency UL licensed resources are allocated in the same manner as the serving cell, enabling seamless UL data transmission during this inactive state; or In response to the inability to allocate the same time / frequency UL authorized resources to the target cell and the serving cell, the UL authorized resource configuration of the target cell is obtained through paging in the core network CN.

10. The method according to claim 1, characterized in that, The method further includes: In this inactive state, an RRC request is sent to the serving cell that serves the UE or the target cell with which the UE will communicate; and In the absence of a state transition, during this inactive state, the UL authorized resource configuration of the serving cell or the target cell is obtained from the serving cell or the target cell. The UL-authorized resource configuration is a non-competitive configuration of the UL-authorized resource.

11. The method according to claim 1, characterized in that, Based on the dual-connection DC configuration of the primary RAN node and the secondary RAN node, the UL data transmission on the UL authorized resource in the inactive state is provided to the primary RAN node and the secondary RAN node.

12. The method according to claim 11, characterized in that, The method further includes: Send a notification to the primary RAN node to request DC reconfiguration and UL authorization reconfiguration; and Based on the reconfigured DC configuration of the primary RAN node and the new secondary RAN node, and the UL authorized resources of the new secondary RAN node, the UL data transmission is performed in this inactive state. Alternatively, the method may further include: In this inactive state, an RRC request is sent to the primary RAN node to request DC reconfiguration and UL authorization reconfiguration; and Without a state transition, in this inactive state, obtain the reconfigured DC configuration of the primary RAN node and the new secondary RAN node, as well as the UL authorized resources of the new secondary RAN node, from the primary RAN node.

13. The method according to claim 1, characterized in that, UL data transmission on the UL-authorized resource in this inactive state is performed on one or more non-public network NPNs.

14. The method according to claim 13, characterized in that, The method further includes: Send a notification to one or more NPNs to activate the UL authorization resource configuration for NPN users within those NPNs; and Based on the UL authorized resources of this NPN user, the UL data transmission is performed in this inactive state. Alternatively, the method may further include: In this inactive state, send an RRC request to one or more NPNs; and Without a state transition, in the inactive state, obtain the UL authorization resource configuration of the NPN user from the one or more NPNs.

15. The method according to claim 1, characterized in that, The method further includes: When the UE enters this inactive state for mobility considerations, it is checked whether the UE is staying in the same serving cell based on at least one of the cell identifier and the received signal strength threshold.

16. The method according to claim 15, characterized in that, In response to checking whether the UE remains on the same serving cell based on the received signal strength threshold, the received signal strength threshold is the Reference Received Power (RSRP) threshold.

17. The method according to claim 15, characterized in that, The at least one transmission threshold includes a first transmission threshold and a second transmission threshold, and the method includes: Based on the first transmission threshold, it is determined whether to transmit the UL data in the inactive state on the PCG resource; Based on the second transmission threshold, it is determined whether the UL data transmission in the inactive state should be performed on the two-step RA resource; In response to the failure of UL data transmission on the PCG resource, but the UL data transmission is below the second transmission threshold, the inactive UL data transmission is performed on the two-step RA resource; and If the UL data transmission exceeds the first transmission threshold or the second transmission threshold, the UL data transmission is performed in the four-step RA procedure.

18. The method according to claim 15, characterized in that, The method further includes: In response to a failure of the UL data transmission on the PCG resource or on the two-step RA resource, the UL data transmission is performed in a four-step RA procedure, wherein the UE enters a connected state to perform the UL data transmission.

19. The method according to claim 1, characterized in that, The method further includes: When the UE enters the inactive state for mobility considerations, it is checked whether the UE is staying in the same RAN notification area based on at least one of the RAN notification area RNA identifier and the received signal strength threshold.

20. The method according to claim 19, characterized in that, In response to checking whether the UE remains in the same RAN notification area based on the received signal strength threshold, the received signal strength threshold is the Reference Signal Received Power (RSRP) threshold.

21. The method according to claim 1, characterized in that, The UL data transmission in this inactive state is a random access (RA) based transmission, which is a contention-based random access (CBRA) procedure triggered by at least one of the following events: In this inactive state, the UE leaves the coverage area of ​​the serving cell without any contention-free random access (CFRA) configuration. CFRA resources were not allocated to this UE in this inactive state; Non-periodic and / or low-priority UL data transmission during this inactive state; and Unable to transfer on the configured licensed CG resources or unable to execute the CFRA procedure.

22. A wireless communication method performed by a base station, characterized in that, The method includes: Send the uplink UL grant resource configuration to the user equipment (UE), wherein the UL grant resource configuration is carried by radio resource control (RRC) signaling; Based on this UL licensed resource configuration, configure the UL licensed resource for the UE so that the UE can perform UL data transmission in an inactive state based on the configured UL licensed resource; and The UE receives the UL data transmission, which is performed on the configured UL licensed resources in the inactive state when the advance time TA is valid, based on the transmission characteristics of the UL data transmission and at least one transmission threshold. The UL licensed resources are either pre-configured licensed PCG resources based on the cell or PCG resources based on the radio access network notification area RNA, which are RBPCG resources. The transmission characteristics include at least one of priority, delay or periodicity, channel access priority category and access category. The transmission threshold includes a data volume threshold.

23. A user equipment, comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, characterized in that, The processor is configured to call and execute program instructions stored in memory to perform the wireless communication method according to any one of claims 1 to 21.

24. A base station, comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, characterized in that, The processor is configured to call and execute program instructions stored in memory to perform the wireless communication method according to claim 22.

Images