CN113518453A - Data transmission method and user equipment - Google Patents
Data transmission method and user equipment Download PDFInfo
- Publication number
- CN113518453A CN113518453A CN202010283207.XA CN202010283207A CN113518453A CN 113518453 A CN113518453 A CN 113518453A CN 202010283207 A CN202010283207 A CN 202010283207A CN 113518453 A CN113518453 A CN 113518453A
- Authority
- CN
- China
- Prior art keywords
- bwp
- sdt
- data transmission
- rrc
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 101
- 238000000034 method Methods 0.000 title claims abstract description 72
- 230000004044 response Effects 0.000 claims description 12
- 238000011144 upstream manufacturing Methods 0.000 claims description 9
- 230000008859 change Effects 0.000 description 16
- 230000011664 signaling Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 230000007246 mechanism Effects 0.000 description 8
- 238000011084 recovery Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 238000005259 measurement Methods 0.000 description 6
- 230000004913 activation Effects 0.000 description 5
- 239000011159 matrix material Substances 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000009849 deactivation Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000011160 research Methods 0.000 description 4
- 238000005265 energy consumption Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 108700026140 MAC combination Proteins 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000000737 periodic effect Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 101150071746 Pbsn gene Proteins 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 239000013256 coordination polymer Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The present disclosure provides a data transmission method and a user equipment, wherein the data transmission method includes: user Equipment (UE) receives a Radio Resource Control (RRC) message containing a small data transmission configuration permission (SDT CG) configuration from a base station; and the UE initiates data transmission based on the SDT CG mode.
Description
Technical Field
The present disclosure relates to the field of wireless communication technologies, and in particular, to a small size data transmission method in an inactive state and a corresponding user equipment.
Background
The third Generation Partnership Project (3rd Generation Partnership Project: 3GPP) RAN #86 approved a new research title of Release 17 at the Council (see non-patent document: RP-193252: Work Item on NR small data transmissions in InACTIVE state), referred to as the small data transmission Project. The purpose of this research project is to optimize for the signaling overhead and power consumption caused by small data traffic that is infrequently sent by users. For a User Equipment (UE) in a Radio Resource Control Inactive state (RRC _ Inactive), some infrequent small data services (such as instant information, heartbeat signals kept online, cycle information of an intelligent wearable device or a sensor, and a cycle reading table service brought by an intelligent metering device) are transmitted, so that the UE needs to enter a Radio Resource Control connected state RRC _ connected to perform transmission of a small-size data packet, and thus signaling overhead brings about reduction of network performance, and energy consumption of the UE is greatly consumed. In the new research project, the aim is mainly achieved by adopting a means of carrying small data in the random access process (for example, carrying the small data in the message 3 accompanying or contained in the four-step random access process or carrying the small data in the message a accompanying or contained in the two-step random access process) and sending the small data by using the pre-configured uplink resource in the RRC _ inactive state without entering the RRC _ connected state to acquire the uplink sending resource, so that the signaling overhead and the UE energy consumption are reduced.
In the NR system of release 15 and later, there is support for providing band size adaptation to a UE by a mechanism of dividing one wide-band carrier into a plurality of BandWidth parts (BWPs). The UE may be configured with one or more BWPs in the RRC _ connected state, and the BWPs may be in an activated state or a deactivated state under the control of the network side, and the UE in the connected state performs transmission on the BWPs in the activated state. The present disclosure proposes a solution to the problem of how to manage and maintain preconfigured uplink data transmission resources, such as BWP, and how to configure preconfigured uplink data resources for a UE in RRC _ Inactive state.
Disclosure of Invention
The purpose of the embodiment of the present disclosure is to provide a solution to the problem of how to maintain the activated and deactivated state of the bandwidth part and how to configure the preconfigured uplink data resource when the UE is in the RRC _ Inactive state. Specifically, the embodiment of the disclosure provides a data transmission method performed in a user equipment or a MAC entity of the user equipment and a corresponding user equipment.
According to a first aspect of the present disclosure, a data transmission method is provided, including: user Equipment (UE) receives a Radio Resource Control (RRC) message containing a small data transmission configuration permission (SDT CG) configuration from a base station; and the UE initiates data transmission based on the SDT CG mode.
In the data transmission method according to the first aspect, the method may further include: altering the currently used bandwidth portion BWP to the associated BWP of the SDT CG configuration.
In the data transmission method according to the first aspect, the method may further include: and under the condition that the UE finishes the uplink transmission by using the SDT CG resource, changing the currently used BWP into the initial BWP.
In the data transmission method according to the first aspect, when the UE determines that the currently used BWP is not the BWP associated with the SDT CG configuration, the currently used bandwidth part BWP may be changed to the BWP associated with the SDT CG configuration.
In the data transmission method of the first aspect, the currently used BWP may be an upstream BWP and/or a downstream BWP.
In the data transmission method of the first aspect, the ending of the uplink transmission using the SDT CG resource by the UE may refer to failure of the uplink transmission caused by the UE receiving a downlink response of the uplink transmission or the UE not receiving a downlink response of the uplink transmission or an uplink time alignment invalidation associated with the SDT.
In the data transmission method of the first aspect described above, the SDT CG configuration is included in an associated BWP configuration.
In the data transmission method of the first aspect, the SDT CG may include a BWP identifier, where the BWP identifier is used to indicate a bandwidth portion BWP corresponding to the SDT CG resource.
In the data transmission method according to the first aspect, the RRC message may be an RRC release message, and when the UE receives the radio resource control RRC message including the SDT CG configuration, the UE enters a radio resource control INACTIVE RRC _ INACTIVE state, and before the UE initiates data transmission based on the SDT CG scheme, the UE in the RRC _ INACTIVE state operates on an initial BWP.
According to a second aspect of the present disclosure, there is provided a user equipment comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, perform the data transfer method as described above and below.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
fig. 1 shows a process flow of a data transmission method as an example in embodiment 1.
Fig. 2 shows a process flow of a data transmission method as another example in embodiment 1.
Fig. 3 shows a process flow of the data transmission method according to the embodiment 2 as an example.
Fig. 4 is a block diagram showing a user equipment UE according to the present invention.
In the drawings, the same or similar structures are identified by the same or similar reference numerals.
Detailed Description
Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the disclosure.
In the present disclosure, the terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the term "or" is inclusive, meaning and/or.
In this specification, the various embodiments described below which are used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but such details are to be regarded as illustrative only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Moreover, descriptions of well-known functions and constructions are omitted for clarity and conciseness. Moreover, throughout the drawings, the same reference numerals are used for similar functions and operations.
Various embodiments according to the present disclosure are described in detail below with an LTE mobile communication system and its subsequent evolution as an example application environment. However, it is to be noted that the present disclosure is not limited to the following embodiments, but is applicable to more other wireless communication systems.
Some concepts related to the present disclosure are described below. It is noted that some of the nomenclature used in the following description is merely exemplary and not limiting, and that other nomenclature may be used.
Primary Cell (PCell): refers to a cell operating on a primary frequency. Which is the cell where the UE performs the initial connection establishment or initiates the connection re-establishment procedure, or the primary cell indicated in the handover command. In the embodiment of the present disclosure, the primary Cell may also refer to a primary secondary Cell (PSCell), that is, a secondary Cell group Cell on which the UE is instructed to perform random access or where the initial PUSCH transmission is located if the random access procedure is ignored when the secondary Cell group is changed. For the primary and secondary cells, the base station informs the UE of the primary and secondary cell identity, frequency and other primary and secondary cell configuration information through RRC signaling. PCell and PSCell are generally collectively referred to as a special Cell (specell).
Secondary Cell (SCell): a cell for providing additional radio resources. It is configured to the UE after a Radio Resource Control (RRC) connection is established.
A serving cell: the method includes the steps of indicating a main cell in a non-carrier aggregation or non-dual-connection scene, and indicating all cells serving UE in a carrier aggregation or dual-connection scene.
RRC state: collectively, three RRC states are defined in NR systems: RRC IDLE state RRC IDLE, RRC INACTIVE state RRC INACTIVE and RRC CONNECTED state RRC CONNECTED. RRC _ IDLE refers to a state when the UE does not establish an RRC connection, RRC _ INACTIVE refers to a state when the UE has established an RRC connection but the RRC connection is suspended/suspended, and RRC _ CONNECTED refers to a state when the UE has established an RRC connection and the RRC connection is not suspended. In the RRC _ INACTIVE state, the UE stores a UE INACTIVE access stratum context (UE INACTIVE AS context), monitors Paging based on a Radio access Network or Paging based on a core Network, monitors a short message (short message) sent by Paging-Radio Network temporary Identifier (P-RNTI) for Paging and notifying of system Information update through Downlink Control Information (DCI), acquires system Information through broadcasting, performs a periodic Radio access Network-based Notification Area (RNA) update, or performs an RNA update when a configured RNA is moved. Currently, the UE of RRC _ INACTIVE cannot implement unicast data communication with the network side, and performs an RRC recovery procedure (RRC resume procedure) by sending an RRC recovery request message to recover the RRC connection with the network side.
Bandwidth Part (Bandwidth Part): in NR systems, operation is possible over wide bandwidths of the order of up to 100M and even GHz. One Wideband (Wideband) carrier may be divided into a plurality of parts in the frequency domain, and these parts are referred to as bandwidth parts BWP. The BWP is also called carrier bandwidth part (carrier bandwidth part) and comprises a set of consecutive physical resource block PRBs selected from a consecutive subset of carrier resource blocks on one wideband carrier with a certain carrier property (i.e. OFDM numerology, which is one carrier property defined by subcarrier spacing and CP type/length, see in particular section 4.2 of 3GPP protocol specification 38211). The division of the BWP can be adapted to the UE supporting different bandwidth ranges, and at the same time, the energy consumption of UE transmission on the broadband carrier can be reduced. The different BWPs may or may not overlap. Different BWPs may employ different parameter values (numerologies), e.g., subcarrier spacing, TTI length, bandwidth, cyclic prefix (cyclic prefix), etc. may be different.
In the present disclosure, BWP refers to upstream BWP or downstream BWP, as not specifically indicated.
Initial BWP: the initial BWP refers to an initial downlink BWP and/or an initial uplink BWP, and for the PCell, refers to a BWP for initial access; for SCell, refer to the first activated BWP (indicated by information element first active downlink BWP-Id and/or first mctivepinkbwp-Id) used after SCell activation, configured to the UE by RRC. For a UE in RRC idle or RRC inactive state, it is generally considered to camp on the initial BWP. It is understood that the initial BWP is, for a UE, the BWP available before explicit configuration or reconfiguration of the BWP, which may occur during or after RRC connection establishment, and each BWP is configured with a BWP id, and the BWP id corresponding to the initial BWP is 0. For a given band, the initial BWP is often limited to the minimum bandwidth of the UE. The initial BWP is generally used for the initial access procedure, but may continue to be used after the initial access is completed. The initial BWP is typically configured by an initialUplinkBWP and/or initialdlinkbwp information element in system information or other dedicated RRC messages.
The configuration of the initial BWP for the primary cell is included in the system information.
The UE may also be configured with a default BWP. Including a default upstream BWP and/or a default downstream BWP. After the UE accesses the network using the initial BWP, the base station may configure one or more BWPs for a serving cell of the UE through RRC dedicated signaling, such as RRC (connection) reconfiguration message. The base station may configure one of these BWPs as a default BWP (with explicit default BWP indication information). Preferably, a Synchronization Signal Block (SSB) is included on the default BWP. For the UE, if a serving cell is not configured with the default BWP, the initial BWP is considered as the default BWP. The BWP with the explicit default BWP indication information is the default BWP. In general, a default BWP generally has a relatively small bandwidth, so that the UE can operate on the default BWP when the data rate is small, for the purpose of power saving; and when the data rate of the UE is larger, the BWP of other configurations which can change to a larger bandwidth can work to improve the transmission efficiency.
BWP activation/deactivation (activation/deactivation): for a UE in RRC _ connected state, the base station may configure a plurality of BWPs for one serving cell. But not all of these configured BWPs are available to the UE. The base station decides which BWPs the UE is currently using by controlling the activation/deactivation state of the BWPs. The BWP activation/deactivation state is for one particular UE. For an active BWP, which the UE considers to be available, the UE may perform one or more of the following operations on the active BWP: the method comprises the steps of PDCCH monitoring, Physical Downlink Shared Channel (PDSCH) (or downlink shared Channel (DL-SCH)) receiving, PUCCH transmitting, Physical Uplink Shared Channel (PUSCH) transmitting, Random Access Channel (RACH) transmitting, Channel State Information (CSI) reporting corresponding to the BWP, uplink Sounding Reference Signal (SRS) transmitting and the like. For inactive BWP, the UE performs one or more of the following operations thereon: the method comprises the steps of not sending an uplink PUSCH (or called UL-SCH), not sending a PUCCH (physical uplink control channel), not sending a RACH (random access channel), not monitoring a PDCCH (physical downlink control channel), not receiving a PDSCH (or called DLL-SCH), not reporting Channel State Information (CSI) corresponding to the BWP, not sending an uplink Sounding Reference Signal (SRS) and the like. The BWP in the activated state is referred to as an activated BWP and the BWP in the deactivated state is referred to as a deactivated BWP.
In the release 15 NR system, although multiple BWPs can be configured for the RRC _ inactive UE, only one active BWP is supported for one serving cell at the same time. The system can change the active state of the BWP through RRC signaling (active BWP is configured through information element first resultant downlink BWP-Id and/or first resultant uplink BWP-Id), and also support more dynamic BWP change. By BWP change, one active BWP is deactivated and one deactivated BWP is activated at the same time. There are two ways of dynamic BWP change: BWP change indicated by Downlink Control Information (DCI) signaling and BWP change based on a timer. The DCI signaling is carried on a PDCCH channel, and the base station indicates the UE to deactivate the current activated BWP and activate one deactivated BWP through the DCI signaling. Under the timer-based BWP change mechanism: the UE starts the timer when it changes to an active BWP different from the default BWP; restarting the timer when a DCI containing an uplink grant or downlink assignment is successfully decoded on an active BWP; when the timer expires, the UE changes to the default BWP for transmission, and considers the active BWP as the default BWP. This timer may be referred to as a BWP inactivity timer (BWPinactivity timer). Further, BWP changes may also occur when the random access procedure triggers. When the random access procedure is triggered, if no random access resource (PRACH instances) is configured on the active uplink BWP of the UE, the UE changes the active uplink BWP to the uplink initial BWP (indicated by the initial uplink BWP information element), and, for the spCell, the UE changes the active downlink BWP to the downlink initial BWP (indicated by the initial downlink BWP information element). If the activated uplink BWP of the UE has the configured random access resource, but the BWP identifier of the activated downlink BWP is different from the activated uplink BWP, the UE changes the activated downlink BWP to the downlink BWP with the same identifier as the activated uplink BWP.
Configuration Grant (CG): configuration permissions are relative to dynamic scheduling. In dynamic scheduling, each UE uses DCI in an uplink grant PDCCH channel for scheduling. The configuration permission refers to uplink permission configuration without dynamic permission, and is equivalent to semi-static scheduling. The uplink grant allocated by the base station to the UE through DCI or RRC signaling may be used multiple times in a periodic manner. Type1 if the actual uplink grant is Configured by RRC, and type 2 if the actual uplink grant is provided by PDCCH addressed with Configured Scheduling-Radio Network temporary Identifier (CS-RNTI). In the CG type1, the corresponding CG information is configured by a configuredgontnfig information element in the RRC message, and includes physical layer parameters such as time domain and frequency domain allocation of uplink grant, time domain offset, frequency hopping offset, period, resource allocation mode, modulation coding mode, transport block size, and path loss reference indication.
As mentioned before, one of the research goals of small data transmission items is to enable the RRC _ INACTIVE state UE to send small data packets on the preconfigured PUSCH resources without entering RRC _ CONNECTED. Preferably, the preconfigured PUSCH is a dedicated resource, i.e. not shared with other UEs, one way is to implement the preconfigured PUSCH transmission by configuring CG type 1. The present disclosure refers to a small data Transmission CG (SDT CG), and may also refer to a preconfigured uplink Transmission, a preconfigured small data Transmission, and the like, and the present disclosure does not limit the nomenclature thereof. The CG configuration is included in the BWP configuration, that is, if a BWP configuration includes a CG configuration, the CG resource uses the resource on the corresponding BWP.
The following embodiments present a solution for how a UE manages used upstream resources, such as BWP, with SDT CG configured.
Example 1
This embodiment considers a case: the BWP associated with the SDT CG with which the UE is configured is not the initial BWP or does not contain the initial BWP. The absence of the initial BWP means that the time-frequency resource of the initial BWP does not partially or completely overlap with the BWP associated with the SDT CG. Alternatively, not including an initial BWP may also mean that the BWP is not configured with resources for common channel reception, such as a common search space. After the UE enters the RRC _ INACTIVE state, the UE needs to monitor a common channel such as paging, system information, or a short message addressed by a P-RNTI on an initial BWP, and also needs to perform unicast data transmission such as downlink transmission for responding to small data transmission on the dedicated BWP, that is, the RRC _ INACTIVE UE needs to manage two BWPs in one direction. Based on this, embodiment 1 provides a method for changing the BWP being used to the BWP associated with the SDT CG by the UE when triggering the transmission mode on the SDT CG, which is performed on the UE or the MAC entity of the UE. Fig. 1 shows a process flow of a data transmission method as an example in embodiment 1. As shown in fig. 1, the data transmission method in embodiment 1 of the present disclosure may include the following steps.
Step 1: the UE receives an RRC message from the base station containing the SDT CG configuration. Preferably, the RRC message is an RRC release message. Wherein, preferably, the SDT CG configuration is contained in an associated BWP configuration; alternatively, a BWP id is included in the SDT CG for indicating the BWP corresponding to the CG resource. The SDT CG configuration may also be referred to as a pre-configured data transmission resource configuration, or the like.
Step 2: and the UE initiates data transmission based on the SDT CG mode.
Preferably, when the current data transmission of the UE RRC layer meets the condition of transmitting in the SDT CG manner, the UE RRC layer initiates data transmission based on the SDT CG manner, and indicates to the lower layer to use the SDT CG manner, or applies the SDT CG configuration received in step 1 to the lower layer.
Fig. 2 shows a process flow of a data transmission method as another example in embodiment 1. As shown in fig. 2, the data transmission method in embodiment 1 of the present disclosure may further include the following steps.
And step 3: the currently used BWP is changed to the BWP associated with the SDT CG configuration in step 1. In this step, the UE activates and restores the uplink grant configured by the SDT CG.
Preferably, step 3 is performed when the UE determines that the currently used BWP is not the BWP associated with the SDT CG configuration in step 1.
Preferably, the BWP is a Downlink BWP (e.g., configured using a BWP-Downlink information element); alternatively, the BWP is an upstream BWP (e.g., configured using a BWP-Uplink information element), or an upstream BWP and a downstream BWP. That is, in step 3, the UE may change only the downlink BWP or the uplink BWP, or may change both the uplink BWP and the downlink BWP. The currently used BWP may also be referred to as a currently operating BWP or multiplexing the term in the RRC _ CONNECTED state in the existing mechanism, referred to as active BWP.
Obviously, between step 1 and step 2, the UE enters RRC _ INACTIVE state. Before step 2, the UE in RRC _ INACTIVE state operates on initial BWP.
Example 2
This embodiment is based on the same scenario as embodiment 1. Embodiment 2 provides a method for changing the BWP being used to the initial BWP when the UE ends the transmission mode on the SDT CG, which is performed on the UE or the MAC entity of the UE. Fig. 3 shows a process flow of the data transmission method according to the embodiment 2 as an example. As shown in fig. 3, the data transmission method in embodiment 2 of the present disclosure may include the following steps.
Step 1: the UE finishes the uplink transmission using the SDT CG resource.
The ending of the uplink transmission using the SDT CG resource may be successful ending or may be a failure ending considered by the UE. Preferably, the successful ending means that the UE successfully receives a downlink response corresponding to the uplink transmission after performing uplink transmission on the resource corresponding to the SDT CG, for example, the UE receives a PDCCH addressed by one radio network temporary identifier RNTI specific to the UE, successfully decodes the received downlink MAC protocol data unit PDU, receives an Acknowledgement (ACK) of a corresponding downlink hybrid automatic repeat request (HARQ), or receives a corresponding downlink response RRC message, such as an RRC release message. Preferably, the RNTI is an RNTI dedicated to the SDT CG transmission mode and is included in the configuration of the SDT CG. Preferably, the failure end means that the UE does not receive the corresponding downlink response after performing the uplink transmission on the resource corresponding to the SDT CG, for example, does not receive the corresponding downlink response after the whole downlink response monitoring time window or the time of the timer is ended. Alternatively, it may also be indicated that the received response indicates that the UE falls back to the conventional manner to perform data transmission. The conventional method refers to a non-SDT CG method, and obtains contact with a network side to send uplink data by using a random access method instead of using a pre-configured CG resource. Alternatively, it may also refer to that the UE considers that it is in an uplink asynchronous state, or referred to as uplink Advance (TA) invalid, such as an uplink Alignment Timer (TAT) for SDT times out or is not running. The timer is used for uplink time alignment maintenance of the SDT in the RRC _ INACTIVE state, when the timer runs, the UE considers uplink synchronization and TA is effective, and SDT transmission can be executed; otherwise, the UE considers the uplink is out of step, the TA is invalid, and the SDT transmission can not be executed.
Step 2: the currently used BWP is changed to the initial BWP.
Preferably, the BWP is a downlink BWP; alternatively, the BWP also comprises an upstream BWP. That is, in step 2, the UE may change only the downlink BWP or the uplink BWP, or may change both the uplink BWP and the downlink BWP. The currently used BWP may also multiplex terms in the RRC _ CONNECTED state in existing mechanisms, referred to as active BWP.
Obviously, before step 1, the UE further receives the SDT CG configuration, enters an RRC _ INACTIVE state, and initiates operations such as sending uplink data in an SDT CG manner. This embodiment is not described in detail.
Example 3
This embodiment considers another case: the BWP associated with the SDT CG with which the UE is configured is or contains the initial BWP. The containing of the initial BWP means that part or all of the time-frequency resources of the initial BWP are overlapped with the BWP associated with the SDT CG. The data transmission method in embodiment 3 of the present disclosure may include the following steps.
Step 1: the UE receives an RRC message from the base station containing the SDT CG configuration. Preferably, the RRC message is an RRC release message. Wherein, preferably, the SDT CG configuration is contained in an associated BWP configuration; alternatively, a BWP id is included in the SDT CG for indicating the BWP corresponding to the CG resource. The SDT CG configuration may also be referred to as a pre-configured data transmission resource configuration, or the like.
Step 2: the UE leaves the RRC _ CONNECTED state and enters the RRC _ INACTIVE state.
Optionally, step 2 further includes the UE applying (to the lower layer) the SDT CG configuration in step 1. The lower layer refers to a MAC layer or a physical layer.
And step 3: if the currently used BWP of the UE is not the BWP configured in the RRC message in message 1, the UE changes the currently used BWP to the BWP indicated in the RRC message. Preferably, the BWP is a downlink BWP; alternatively, the BWP also comprises an upstream BWP. That is, in step 2, the UE may change only the downlink BWP or the uplink BWP, or may change both the uplink BWP and the downlink BWP. The currently used BWP may also multiplex terms in the RRC _ CONNECTED state in existing mechanisms, referred to as active BWP. After the UE performs BWP change, the uplink grant corresponding to the configured CG is activated/recovered.
The UE performs step 3 based on step 2, i.e. the UE performs step 3 when step 2 occurs.
In this embodiment, in order to avoid BWP change caused by performing data transmission on the preconfigured resource when the UE is in the RRC _ INACTIVE state, the network side must configure the preconfigured resource for RRC _ INACTIVE state data transmission on the initial BWP or the BWP including the initial BWP when configuring the SDT CG. That is, the BWP associated with the SDT CG has Common Search Space (CSS) configuration, and/or Synchronization Signal Block (SSB) configuration, and/or random access resource (PRACH) configuration, etc., so that the UE can perform reception or transmission of a Common channel thereon. The CSS refers to a CSS for receiving system information or paging. The UE having the above configuration changes its operating BWP to the associated BWP in the SDT CG configuration when leaving the RRC _ CONNECTED state and entering the RRC _ INACTIVE state.
The SDT CG configuration in each embodiment described above not only refers to the configuration of uplink resource grant, but also may be used to refer to other parameter configurations used for sending data on a preconfigured uplink resource in RRC _ INACTIVE state, for example, the uplink resource configuration includes an uplink resource configuration used for sending uplink data, such as uplink grant CG configuration, uplink BWP configuration, and the like, and also includes a downlink resource configuration used for receiving a corresponding downlink response, such as parameter configuration used for monitoring PDCCH, downlink BWP configuration, and the like, and may also include configurations such as a downlink response receiving window/timer. Preferably, the BWP configuration includes a BWP identifier, and if the BWP identifier in the BWP configuration does not exist, the UE considers that the BWP is an active BWP when receiving the RRC message including the configuration, or the UE considers that the BWP is an initial BWP.
Example 4
The embodiment provides a management method of SDT CG configuration, which is executed on UE. In this embodiment, it is considered that the UE stores the configured preconfigured uplink resource configuration for transmitting the uplink small data in the UE inactive access stratum context.
When the UE receives the SDT CG configuration contained in the RRC message, the UE saves it in the UE inactive access stratum context. Preferably, the RRC message is an RRC release message. The value of the SDT CG configuration is not set to release.
When the UE receives the SDT CG configuration contained in the RRC message, if the stored SDT CG configuration exists in the context of the UE non-activated access layer, the UE replaces the stored SDT CG configuration with the newly received SDT CG configuration in the context of the UE non-activated access layer.
Optionally, in the RRC recovery process, the UE sends an RRC recovery request message to initiate an RRC recovery process, and when the UE receives an RRC recovery message responded by the network, the UE releases the UE inactive access stratum context, where the UE inactive access stratum context does not include the SDT CG configuration.
Optionally, when the UE receives the RRC resume message and enters the RRC _ CONNECTED state, the UE suspends the configured SDT CG. That is to say, the uplink grant corresponding to the SDT CG is invalid in the RRC _ CONNECTED state.
Optionally, when the UE fails to transmit data in the SDT CG manner, for example, receives an SDT CG transmission failure indication from a lower layer, or receives a rollback indication or a rejection message from the network side, the UE abandons the SDT CG manner, where the abandoning includes suspending the uplink grant corresponding to the configured SDT CG.
Optionally, in an initialization phase of the RRC recovery procedure, such as when performing a sending operation of the RRC recovery message, the UE recovers the UE inactive access stratum context including the SDT CG configuration.
Example 5
The embodiment provides a configuration mode of the SDT CG, which utilizes the existing CG configuration mode to the maximum extent and reduces signaling overhead.
In this embodiment, the SDT CG configuration received by the UE from the base station multiplexes the CG type1 configuration in the existing mechanism, i.e. obtained by RRC reconfiguration message. In the ConfiguredGrantConfig information element for configuring CG type1, if an indication information 1 is included, the UE considers that the CG is configured as an SDT CG configuration. The indication information 1 is used for indicating that the CG type1 configuration is used as the SDT CG configuration of the UE after the UE enters the RRC _ INACTIVE state.
Example 6
In the existing mechanism, not all data types or service types are suitable for being transmitted through the resource configuration mode of CG type1, therefore, when configuring a transmission channel of a data type, i.e. a logical channel in the current protocol specification, a configured (logical channel config information element) thereof includes a configured gradentrtylallowed information element for indicating whether data from the logical channel can be transmitted on CG type 1.
Considering that the SDT CG configuration also adopts a CG type1 manner, but the scenarios and data types used by the configured CG type1 and the SDT CG type1 in the existing mechanism may be different, so in this embodiment, it is further defined that, if there is a logical channel configuration in the configured CG type1Allowed information element, the configured CG type1Allowed information element is only used to indicate that data from the logical channel may be sent on a non-SDT CG type 1. The non-SDT CG type1 refers to a preconfigured CG type1 that is not used for performing uplink data transmission on RRC _ INACTIVE. As previously described, in one approach, the non-SDT CG type1 may be a CG type1 that does not contain the indication information 1. The indication information 1 is used for indicating that the CG type1 configuration is used as the SDT CG configuration of the UE after the UE enters the RRC _ INACTIVE state.
Further, the logical channel configuration received by the UE from the base station may include an indication information 2, and if the indication information 2 exists, it indicates that data from the logical channel may be sent on SDT CG type 1. For example, the indication information 2 is identified with sdtconfigured granttype1Allowed information element.
Example 7
In NR systems, beam (beam) techniques are generally employed to achieve more reliable transmission due to high frequencies. At initial access, a random access procedure is used between the UE and the base station to establish a transmit and receive beam pair, after which the used beam or beam pair may be continuously adjusted or refined based on measurements. The beam refers to a transmission having a specific direction formed using a beamforming technique (beamforming) in a multi-antenna system. May be considered to be determined by a specific codeword in a pmi (precoding matrix indicator) codebook; or by reference signal resources or reference signal resource indications (e.g., a beam is determined by a reference signal resource or reference signal resource indication); or by a block of synchronization signals (SS block) (e.g., a block of synchronization signals may define a beam); or may be considered as a beam determined by a set of time-frequency resources (e.g., a set of time-frequency resources may correspond to a beam); or determined jointly by the reference signal resource and the precoding matrix indicator (e.g., one beam is determined jointly by the reference signal resource and the precoding matrix indicator); or determined jointly by the Reference Signal Resource indication and the precoding matrix indication (e.g. one beam is determined jointly by the Reference Signal Resource indication and the precoding matrix indication), the Reference Signal may be a Channel state Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a Mobility Reference Signal (MRS), i.e. a Reference Signal used for Mobility such as layer 3 Mobility or Mobility based on radio Resource management rrm (radio Resource management) measurements), a demodulation Reference Signal (dmrs Signal), etc.
In this embodiment, the configuration of the SDT CG includes configuration information of an uplink beam used. For example, the configuration information may be a reference signal identifier for identifying an uplink beam. Considering mobility and channel diversity of the UE, there is a case that when the UE uses the SDT CG to send small-size uplink data on the preconfigured uplink resource, the preconfigured uplink beam is not suitable, and if the UE sends data on the uplink beam, it is likely to cause data transmission failure.
Based on the consistency of the beams in the uplink and downlink directions, in one mode, when determining whether the uplink data is sent by using the SDT CG mode, the UE needs to determine whether the quality of a downlink receiving channel in the uplink beam direction included in the configuration of the SDT CG is good enough, and if so, the UE meets the condition of sending the uplink data by using the SDT CG mode; otherwise, the condition of using the SDT CG mode is not satisfied, and the UE may select to transmit data using a process of performing random access in a conventional manner. Said sufficiently good means that its downlink channel quality exceeds a certain configured threshold value.
In one mode, when the UE sends uplink data on the uplink grant corresponding to the SDT CG, the UE may include, in the MAC protocol data unit, channel quality measurement result information corresponding to one or more downlink beams, for example, the channel quality measurement result information is carried in a form of a MAC control element. In another approach, a UE in RRC _ connected state may request the base station to allocate SDT CG preconfigured resources to the UE by sending a request RRC message or provide the base station with assistance information such as transport block size, transmission period, etc. to allocate the SDT CG preconfigured resources. The RRC message may include channel quality measurement result information corresponding to one or more downlink beams. Preferably, the channel measurement result information includes a plurality of bits, each bit corresponds to one downlink beam, if the bit is 1, the channel quality result of the downlink beam is considered to be greater than a certain configured threshold, otherwise, if the bit is 0, the channel quality result of the downlink beam is considered to be less than a certain configured threshold.
Example 8
This embodiment explains the user equipment UE of the present disclosure. Fig. 4 is a block diagram showing a user equipment UE according to the present invention. As shown in fig. 4, the user equipment UE40 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like. The memory 402 may include, for example, volatile memory (e.g., random access memory RAM), a Hard Disk Drive (HDD), non-volatile memory (e.g., flash memory), or other memory, among others. The memory 402 has stored thereon program instructions. Which when executed by the processor 401 may perform the above-described data transmission method described in detail in the present invention.
In the present disclosure, various embodiments may be coordinated, and some definitions or terms may be common among the various embodiments without specific explanations.
In the present application, a "base station" refers to a mobile communication data and control switching center having a large transmission power and a wide coverage area, and includes functions of resource allocation scheduling, data reception and transmission, and the like. "user equipment" refers to a user mobile terminal, and includes, for example, a mobile phone, a notebook, and other terminal equipment that can wirelessly communicate with a base station or a micro base station.
The method of the present disclosure and the related apparatus have been described above in connection with preferred embodiments. Those skilled in the art will appreciate that the methods illustrated above are exemplary only. The methods of the present disclosure are not limited to the steps or sequences shown above. The base station and the user equipment shown above may comprise further modules, for example, modules that may be developed or developed in the future, which may be available for the base station, MME, or UE, etc. The various identifiers shown above are merely exemplary and not limiting, and the present disclosure is not limited to the specific information elements that are examples of these identifiers. Many variations and modifications may occur to those skilled in the art in light of the teachings of the illustrated embodiments.
The program running on the apparatus according to the present disclosure may be a program that causes a computer to realize the functions of the embodiments of the present disclosure by controlling a Central Processing Unit (CPU). The program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a Hard Disk Drive (HDD), a nonvolatile memory (such as a flash memory), or other memory system.
A program for implementing the functions of the embodiments of the present disclosure may be recorded on a computer-readable recording medium. The corresponding functions can be realized by causing a computer system to read the programs recorded on the recording medium and execute the programs. The term "computer system" as used herein may be a computer system embedded in the device and may include an operating system or hardware (e.g., peripheral devices). The "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium that stores a program for short-term dynamics, or any other recording medium that is readable by a computer.
Various features or functional blocks of the devices used in the above-described embodiments may be implemented or performed by circuitry (e.g., a single or multiple chip integrated circuits). Circuitry designed to perform the functions described herein may include a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The circuit may be a digital circuit or an analog circuit. Where new integrated circuit technology has emerged as a replacement for existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using such new integrated circuit technology.
Further, the present disclosure is not limited to the above-described embodiments. While various examples of the embodiments have been described, the present disclosure is not so limited. Fixed or non-mobile electronic devices installed indoors or outdoors may be used as terminal devices or communication devices, such as AV devices, kitchen devices, cleaning devices, air conditioners, office devices, vending machines, and other home appliances.
As above, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings. However, the specific configuration is not limited to the above embodiment, and the present disclosure also includes any design modification without departing from the gist of the present disclosure. In addition, various modifications can be made to the present disclosure within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. Further, components having the same effects described in the above embodiments may be substituted for each other.
Claims (10)
1. A method of data transmission, comprising:
user Equipment (UE) receives a Radio Resource Control (RRC) message containing a small data transmission configuration permission (SDT CG) configuration from a base station; and
and the UE initiates data transmission based on an SDT CG mode.
2. The data transmission method according to claim 1,
the data transmission method further comprises: altering the currently used bandwidth portion BWP to the associated BWP of the SDT CG configuration.
3. The data transmission method according to claim 1,
the data transmission method further comprises: and under the condition that the UE finishes the uplink transmission by using the SDT CG resource, changing the currently used BWP into the initial BWP.
4. The data transmission method according to claim 2,
and when the UE judges that the currently used BWP is not the BWP associated with the SDT CG configuration, changing the currently used bandwidth part BWP to the BWP associated with the SDT CG configuration.
5. The data transmission method according to claim 2 or 3,
the BWPs currently used are upstream BWPs and/or downstream BWPs.
6. The data transmission method according to claim 3,
the UE ending the uplink transmission using the SDT CG resource means that the uplink transmission fails due to the UE receiving the downlink response of the uplink transmission or the UE not receiving the downlink response of the uplink transmission or the uplink time alignment related to the SDT is invalid.
7. The data transmission method according to any one of claims 1 to 3,
the SDT CG configuration is included in an associated BWP configuration.
8. The data transmission method according to any one of claims 1 to 3,
BWP identification is contained in the SDT CG and is used for indicating a bandwidth part BWP corresponding to the SDT CG resource.
9. The data transmission method according to any one of claims 1 to 3,
the RRC message is an RRC release message,
in the event that the UE receives a Radio Resource Control (RRC) message including the SDT CG configuration, the UE enters a radio resource control INACTIVE (RRC _ INACTIVE) state,
before the UE initiates data transmission based on an SDT CG mode, the UE in the RRC _ INACTIVE state works on the initial BWP.
10. A user equipment, UE, comprising:
a processor; and
a memory storing instructions;
wherein the instructions, when executed by the processor, perform the data transmission method of any one of claims 1 to 9.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010283207.XA CN113518453A (en) | 2020-04-10 | 2020-04-10 | Data transmission method and user equipment |
| PCT/CN2021/085802 WO2021204148A1 (en) | 2020-04-10 | 2021-04-07 | Data transmission method and user equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010283207.XA CN113518453A (en) | 2020-04-10 | 2020-04-10 | Data transmission method and user equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113518453A true CN113518453A (en) | 2021-10-19 |
Family
ID=78022810
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010283207.XA Pending CN113518453A (en) | 2020-04-10 | 2020-04-10 | Data transmission method and user equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113518453A (en) |
| WO (1) | WO2021204148A1 (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022237143A1 (en) * | 2021-05-11 | 2022-11-17 | 展讯通信（上海）有限公司 | Data processing method and apparatus, and user equipment |
| WO2023065316A1 (en) * | 2021-10-22 | 2023-04-27 | Oppo广东移动通信有限公司 | Small data transmission method and apparatus based on preconfigured resource, device, and medium |
| WO2023070661A1 (en) * | 2021-11-01 | 2023-05-04 | Oppo广东移动通信有限公司 | Data transmission method, terminal device, computer storage medium, and program product |
| WO2023098854A1 (en) * | 2021-12-03 | 2023-06-08 | Qualcomm Incorporated | Method and apparatus for synchronization for rach and sdt in ssb-less dl bwp |
| WO2023102922A1 (en) * | 2021-12-10 | 2023-06-15 | Nec Corporation | Method, device and computer storage medium of communication |
| WO2023102748A1 (en) * | 2021-12-07 | 2023-06-15 | Oppo广东移动通信有限公司 | Method and apparatus for reporting small data transmission failure, and device and storage medium |
| WO2023108476A1 (en) * | 2021-12-15 | 2023-06-22 | Oppo广东移动通信有限公司 | Communication method and apparatus |
| WO2023116410A1 (en) * | 2021-12-23 | 2023-06-29 | 华为技术有限公司 | Communication method and device |
| WO2023131245A1 (en) * | 2022-01-10 | 2023-07-13 | 大唐移动通信设备有限公司 | Information transmission method and apparatus, configuration optimization method and apparatus, terminal, and network device |
| WO2023133760A1 (en) * | 2022-01-13 | 2023-07-20 | Oppo广东移动通信有限公司 | Method and apparatus for uplink retransmission in small-data transmission process, and device and medium |
| WO2023133839A1 (en) * | 2022-01-14 | 2023-07-20 | Oppo广东移动通信有限公司 | Communication method and device |
| WO2023143226A1 (en) * | 2022-01-26 | 2023-08-03 | 上海朗帛通信技术有限公司 | Method and apparatus used in wireless communication |
| WO2023155119A1 (en) * | 2022-02-18 | 2023-08-24 | Nokia Shanghai Bell Co., Ltd. | Procedure selection for small data transmission |
| WO2023207685A1 (en) * | 2022-04-25 | 2023-11-02 | 华为技术有限公司 | Information transmission method and apparatus |
| WO2023231005A1 (en) * | 2022-06-02 | 2023-12-07 | 上海移远通信技术股份有限公司 | Wireless communication method and apparatus |
| WO2024065285A1 (en) * | 2022-09-28 | 2024-04-04 | Nec Corporation | Methods, devices, and medium for communication |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023087243A1 (en) * | 2021-11-19 | 2023-05-25 | Qualcomm Incorporated | Channel state information reports during a small data transfer session |
| CN114503751A (en) * | 2021-12-31 | 2022-05-13 | 北京小米移动软件有限公司 | Method and device for determining time domain resource transmission position |
| WO2023130273A1 (en) * | 2022-01-05 | 2023-07-13 | Nokia Shanghai Bell Co., Ltd. | Configured grant resource handling for small data transmission |
| CN116489715A (en) * | 2022-01-14 | 2023-07-25 | 华为技术有限公司 | Communication method and system |
| WO2023150952A1 (en) * | 2022-02-10 | 2023-08-17 | Qualcomm Incorporated | Small data transmission configuration for non-terrestrial network |
| WO2023160787A1 (en) * | 2022-02-24 | 2023-08-31 | Nokia Technologies Oy | Small data transmission failure reporting |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016032077A1 (en) * | 2014-08-25 | 2016-03-03 | Lg Electronics Inc. | Method and apparatus for scheduling request in a wireless communication system |
| US11483810B2 (en) * | 2017-04-03 | 2022-10-25 | Huawei Technologies Co., Ltd. | Methods and systems for resource configuration of wireless communication systems |
| CN111490863B (en) * | 2017-11-16 | 2021-05-11 | 华为技术有限公司 | Measurement configuration method, network equipment and terminal equipment |
| EP3791688B1 (en) * | 2018-05-10 | 2022-11-23 | IPLA Holdings Inc. | Small data transmission with non-orthogonal multiple access |
-
2020
- 2020-04-10 CN CN202010283207.XA patent/CN113518453A/en active Pending
-
2021
- 2021-04-07 WO PCT/CN2021/085802 patent/WO2021204148A1/en active Application Filing
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022237143A1 (en) * | 2021-05-11 | 2022-11-17 | 展讯通信（上海）有限公司 | Data processing method and apparatus, and user equipment |
| WO2023065316A1 (en) * | 2021-10-22 | 2023-04-27 | Oppo广东移动通信有限公司 | Small data transmission method and apparatus based on preconfigured resource, device, and medium |
| WO2023070661A1 (en) * | 2021-11-01 | 2023-05-04 | Oppo广东移动通信有限公司 | Data transmission method, terminal device, computer storage medium, and program product |
| WO2023098854A1 (en) * | 2021-12-03 | 2023-06-08 | Qualcomm Incorporated | Method and apparatus for synchronization for rach and sdt in ssb-less dl bwp |
| WO2023097682A1 (en) * | 2021-12-03 | 2023-06-08 | Qualcomm Incorporated | Synchronization for rach and sdt in ssb-less dl bwp |
| WO2023102748A1 (en) * | 2021-12-07 | 2023-06-15 | Oppo广东移动通信有限公司 | Method and apparatus for reporting small data transmission failure, and device and storage medium |
| WO2023102922A1 (en) * | 2021-12-10 | 2023-06-15 | Nec Corporation | Method, device and computer storage medium of communication |
| WO2023108476A1 (en) * | 2021-12-15 | 2023-06-22 | Oppo广东移动通信有限公司 | Communication method and apparatus |
| WO2023116410A1 (en) * | 2021-12-23 | 2023-06-29 | 华为技术有限公司 | Communication method and device |
| WO2023131245A1 (en) * | 2022-01-10 | 2023-07-13 | 大唐移动通信设备有限公司 | Information transmission method and apparatus, configuration optimization method and apparatus, terminal, and network device |
| WO2023133760A1 (en) * | 2022-01-13 | 2023-07-20 | Oppo广东移动通信有限公司 | Method and apparatus for uplink retransmission in small-data transmission process, and device and medium |
| WO2023133839A1 (en) * | 2022-01-14 | 2023-07-20 | Oppo广东移动通信有限公司 | Communication method and device |
| WO2023143226A1 (en) * | 2022-01-26 | 2023-08-03 | 上海朗帛通信技术有限公司 | Method and apparatus used in wireless communication |
| WO2023155119A1 (en) * | 2022-02-18 | 2023-08-24 | Nokia Shanghai Bell Co., Ltd. | Procedure selection for small data transmission |
| WO2023207685A1 (en) * | 2022-04-25 | 2023-11-02 | 华为技术有限公司 | Information transmission method and apparatus |
| WO2023231005A1 (en) * | 2022-06-02 | 2023-12-07 | 上海移远通信技术股份有限公司 | Wireless communication method and apparatus |
| WO2024065285A1 (en) * | 2022-09-28 | 2024-04-04 | Nec Corporation | Methods, devices, and medium for communication |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021204148A1 (en) | 2021-10-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113518453A (en) | Data transmission method and user equipment | |
| CN110383898B (en) | Effective bandwidth adaptation method for broadband carrier | |
| US11997517B2 (en) | Synchronization detection based on radio link monitoring in power saving mode | |
| US20220069966A1 (en) | Method and apparatus for radio link monitoring measurements in a system using bandwidth parts | |
| US20220022067A1 (en) | Method and apparatus for controlling activation of cell group in wireless communication system | |
| RU2752659C1 (en) | Method for processing semi-persistent scheduling, communication apparatus and data storage medium | |
| CN107431592B (en) | Method for transmitting channel state information and apparatus therefor | |
| JP2022529889A (en) | Sending and receiving power saving commands | |
| JP2022521827A (en) | Power saving active BWP | |
| US20220030578A1 (en) | Infrastructure equipment for determining whether a communications device is within a radio coverage area | |
| JP2022527303A (en) | Multiplexing and prioritizing new radios | |
| JP2022531228A (en) | Multiple SPS and preconfigured grant configurations | |
| JP2020515157A (en) | Radio access network notification area update failure | |
| JP2022521821A (en) | Cell information for access control | |
| JP2019140634A (en) | Base station device, terminal device, and method | |
| CN111183667B (en) | Radio network node, wireless device and method performed therein | |
| WO2016121631A1 (en) | Terminal device and base station device | |
| WO2020225031A1 (en) | Discovery of and recovery from missed wake-up signal (wus) reception | |
| US11729637B2 (en) | Enhancement to expedite secondary cell (SCell) or primary SCell (PSCell) addition or activation | |
| JP2018050088A (en) | Terminal, base station device, and communication method | |
| CN113711659A (en) | Bandwidth portion specific scheduling configuration | |
| WO2016121637A1 (en) | Terminal device and base station device | |
| WO2016121665A1 (en) | Terminal device and base station device | |
| EP4017083A1 (en) | Method and apparatus for providing heat generation related information of terminal in mobile communication system supporting multiple connections | |
| CN113692070A (en) | Method executed by user equipment and user equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20211019 |
|
| WD01 | Invention patent application deemed withdrawn after publication |