Patent Grant
12035169
The present disclosure relates to a mobile communication system with data transfer in RRC_INACTIVE state. More specifically, the present disclosure relates to resume procedure initiation for data transfer during RRC_INACTIVE and determination on radio bearers for data transfer during RRC_INACTIVE.
To meet the increasing demand for wireless data traffic since the commercialization of 4th generation (4G) communication systems, the 5th generation (5G) system is being developed. For the sake of high data rate, 5G system introduced millimeter wave (mmW) frequency bands (e. g. 60 GHz bands). In order to increase the propagation distance by mitigating propagation loss in the 5G communication system, various techniques are introduced such as beamforming, massive multiple-input multiple output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna. In addition, base station is divided into a central unit and plurality of distribute units for better scalability. To facilitate introduction of various services, 5G communication system targets supporting higher data rate and smaller latency.
Aspects of the present disclosure are to address the problems of state transition from RRC_INACTIVE to RRC_CONNECTED for data transfer. Accordingly, an aspect of the present disclosure is to provide a method and an apparatus for data transfer in RRC_INACTIVE state. In accordance with an aspect of the present disclosure, a method of a terminal in mobile communication system is provided. In the method, UE receives RRC Reconfiguration message, receives RRC Release message and triggers BSR the second BSR configuration and the second LCGs for the logical channels of second set and the first LCGs for the logical channels of the first set.
The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.
Exemplary embodiments of the present invention are described with reference to the accompanying drawings in details.
Descriptions on the technical details well-known in the art and not related directly to the present disclosure are omitted herein. This aims to omit unnecessary description so as to make the subject matter of the present invention clear.
Detailed description of well-known functions and structures incorporated herein may be omitted to avoid obscuring the subject matter of the present invention.
The terms used in the following are defined with consideration of functionalities and could be different according to the intention of user or operator and conventions. Therefore, the definition should be understood based on the contents across the specification.
The terms used, in the following description, for indicating access nodes, network entities, messages, interfaces between network entities, and diverse identity information is provided for convenience of explanation. Accordingly, the terms used in the following description are not limited to specific meanings but may be replaced by other terms equivalent in technical meanings.
In the following descriptions, the terms and definitions given in the 3GPP standards are used for convenience of explanation. However, the present disclosure is not limited by use of these terms and definitions and other arbitrary terms and definitions may be employed instead.
Table 1 lists the acronyms used throughout the present disclosure.
Table 2 lists the terminologies and their definition used throughout the present disclosure.
In the present invention, “trigger” or “triggered” and “initiate” or “initiated” may be used in the same meaning.
In the present invention, “radio bearers allowed for the second resume procedure”, “radio bearers for which the second resume procedure is set”, and “radio bearers for which the second resume procedure is enabled” may all have the same meaning.
5G system consists of NG-RAN 1A-01 and 5GC 1A-02. An NG-RAN node is either:
The gNBs 1A-05 or 1A-06 and ng-eNBs 1A-03 or 1A-04 are interconnected with each other by means of the Xn interface. The gNBs and ng-eNBs are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF (Access and Mobility Management Function) and to the UPF (User Plane Function). AMF 1A-07 and UPF 1A-08 may be realized as a physical node or as separate physical nodes.
A gNB 1A-05 or 1A-06 or an ng-eNBs 1A-03 or 1A-04 hosts the functions listed below.
Functions for Radio Resource Management such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in uplink, downlink and sidelink (scheduling); and
The AMF 1A-07 hosts the functions such as NAS signaling, NAS signaling security, AS security control, SMF selection, Authentication, Mobility management and positioning management.
The UPF 1A-08 hosts the functions such as packet routing and forwarding, transport level packet marking in the uplink, QoS handling and the downlink, mobility anchoring for mobility etc.
User plane protocol stack consists of SDAP 1B-01 or 1B-02, PDCP 1B-03 or 1B-04, RLC 1B-05 or 1B-06, MAC 1B-07 or 1B-08 and PHY 1B-09 or 1B-10. Control plane protocol stack consists of NAS 1B-11 or 1B-11B-, RRC 1B-13 or 1B-14, PDCP, RLC, MAC and PHY.
Each protocol sublayer performs functions related to the operations listed in the table 3.
The terminal supports three RRC states. Table 4 lists the characteristics of each state.
Between RRC_CONNECTED 1C-11 and RRC_INACTIVE 1C-13, a state transition occurs due to the exchange of the Resume message and the Release message containing the Suspend IE.
A state transition occurs between RRC_CONNECTED 1C-1I and RRC_IDLE 1C-15 through RRC connection establishment and RRC connection release.
The state transition from RRC_INACTIVE to RRC_CONNECTED involves not only signal exchange between the terminal and the base station, but also context transfer and data path change between the base stations. If the terminal has enough data to transmit, these additional procedures can be sufficiently justified, but if not, excessive overhead can reduce the efficiency of the network.
The present invention introduces a new resumption procedure capable of transmitting and receiving data without transition to RRC_CONNECTED. Hereinafter, a resume procedure for the purpose of transitioning the terminal to the RRC_CONNECTED state from the RRC_INACTIVE state is referred to as a first resume procedure, and a procedure for transmitting and receiving data while the terminal is in the RRC_INACTIVE state is referred to as a second resume procedure. Through the first resume procedure, the terminal may resume the suspended RRC connection, and through the second resumption procedure, the terminal may resume data transmission and reception. The terminal may switch to the first resume procedure while performing the second resume procedure.
In a wireless communication system including a terminal 2A-01, a first base station 2A-03, and a second base station 2A-05, the terminal and the base station operate as follows.
In steps 2A-11, the terminal reports capability to the first base station or another base station. The UE capability information transfer procedure consists of transmitting an RRC control message called UECapabilityInformation containing UE capability information to the serving base station if the serving base station transmits an RRC message requesting UE capability information. UECapabilityInformation includes the following information.
<UECapabilityInformation>
1. First information related to RRC_INACTIVE: 1-bit information indicating whether the terminal supports RRC_INACTIVE. Only one 1-bit is reported regardless of the number of bands supported by the terminal.
2. Second information related to RRC_INACTIVE: information indicating whether the second resume procedure is supported or not. It may indicate whether the second resume procedure is supported for each band supported by the terminal. When the terminal supports n bands, n 1-bit information is reported.
3. Various pieces of capability information related to data transmission/reception between the terminal and the base station (for example, whether specific decoding is supported, etc.).
The terminal supporting RRC_INACTIVE supports the first resumption procedure in all frequency bands supported by the terminal. That is, the first information related to RRC_INACTIVE support is information applied to a plurality of bands, and the second information related to RRC_INACTIVE is information applied to one band. A terminal that does not support RRC_INACTIVE does not support the second resumption procedure in any frequency band that it supports. The serving base station provides appropriate NR configuration information to the UE by referring to the capability of the UE. The UE and the serving base station transmit and receive data in the RRC_CONNECTED state, and when the data transmission and reception are completed, the serving base station determines to transition the terminal state to the RRC_INACTIVE state.
In step 2A-13, the first base station transmits an RRCRelease message to the terminal. The RRCRelease message includes SuspendConfig 1E, and SuspendConfig includes the following information.
<SuspendConfig>
1. The first terminal identifier: an identifier of a terminal that may be included in the ResumeRequest when a state transition to RRC_CONNECTED is made. It has a 40-bit length.
2. The second terminal identifier: an identifier of a terminal that may be included in the Resume Request when a state transition to RRC_CONNECTED is made. It has a 24-bit length.
3. ran-Paging Cycle: Paging cycle to be applied in RRC_INACTIVE state.
4. ran-Notification AreaInfo: Configuration information of a ran-Notification Area consisting of a list of cells and the like. The terminal initiates a resume procedure when the ran_Notification Area is changed.
5. t380: Timer related to the periodic resumption procedure.
6. NextHopChangingCount (NCC): Counter used to derive new security keys after performing the resume procedure.
7. Second resume procedure related information: List of DRBs configured with second resume procedures, 1-bit information indicating whether the second resume procedure is configured for SRB2, 1-bit information indicating whether the second resume procedure is configured for SRB4, Data volume threshold of the second resume procedure (hereinafter referred to as dedicated data threshold), reference signal received power threshold of the second resume procedure (hereinafter referred to as dedicated reference signal received power threshold).
Since SRB1 among SRB1, SRB2, SRB3, and SRB4 transmits and receives the most important RRC control message, it is important to quickly transmit the RRC control message as the second resumption procedure, and the second resumption procedure is highly effective for SRB1. SRB2 and SRB4 are less important than SRB1 because relatively large messages can occur, but they still transmit important control messages, so the second resumption procedure is effective for SRB2 and SRB4. SRB3 is not used when multiple connections are not established. Accordingly, in the present invention, a second resumption procedure can be explicitly configured for SRB2 and SRB4. A second resumption procedure is not explicitly configured for SRB1 and SRB3. If a second resumption procedure is configured for at least one radio bearer, a second resumption procedure is implicitly configured for SRB1. A second resumption procedure is not configured for SRB3 under any conditions.
In step 2A-14, the terminal performs the SuspendConfig operation set. The SuspendConfig operation set is applied at a predetermined first or second time point. For the SuspendConfig operation set is performed, the following operations are sequentially performed.
<SuspendConfig Operation Set>
1. Apply suspendConfig.
2. Reset MAC.
3. Reset SRB1's RLC entity.
4. All SRBs and DRBs are suspended.
5. Start T380 set to t380.
6. Enter RRC_INACTIVE state.
The terminal applies the first time point for SuspendConfig operation set when the second resume related information is included, and the second time point if not included.
The first time point is as follows.
Earlier time point between a time point at which 100 ms has elapsed since receiving the RRCRelease message and a time point at which the lower layer successfully acknowledged the reception of the RRCRelease message.
The second time point is as follows.
Earlier time point between a time point at which 60 ms has elapsed since receiving the RRCRelease message and a time point at which the lower layer successfully acknowledged the reception of the RRCRelease message.
Different time points are used because the reliability of the RRC Release message including the second resume-related information should be higher than that of the RRC Release message not including the second resume information.
In step 2A-15, the terminal moves to a new cell. The terminal may compare the radio signal quality of the serving cell and the neighboring cell to reselect the neighboring cell having a better radio signal quality. Alternatively, a cell in which the radio signal quality is greater than or equal to a certain threshold may be selected.
In steps 2A-17, the terminal receives system information including SIB1 in a new cell. The SIB1 may include at least two types of information below.
<SIB1>
1. The value of t319
2. 1-bit information indicating whether the second resume procedure is allowed (or whether the second resume procedure is configured or possible).
If the second resume procedure is allowed, the following information is included and broadcast in system information (hereinafter, SIBX) other than SIB1.
<SIBX>
1. Data volume threshold of the second resume procedure (hereinafter, referred to as common data threshold)
2. Reference signal received power threshold of the second resume procedure (hereinafter, referred to as a common reference signal received power threshold)
3. Random access transmission resource information for the second resume procedure.
4. t319ext
The terminal receives the SIBX if there is at least one radio bearer configured with a second resume procedure, i.e., if the second resume procedure is configured for at least one DRB or if the second resume procedure is configured for SRB2 or SRB4.
The terminal receiving the necessary system information including SIB1 performs the RRC_INACTIVE operation shown in Table 4 in the cell.
In step 2A-19, an event that triggers the resume procedure occurs. When the upper layer or AS requests the resumption of the suspended RRC connection or when new data occurs, the resume procedure may be triggered.
In step 2A-21, the terminal triggers one of the first resume procedure and the second resume procedure. If any one of the first resumption condition sets is satisfied, the first resume procedure is triggered.
<First Resume Condition Set>
1. The upper layer requests the resumption of the suspended RRC connection.
2. RAN paging including the first identifier is received.
3. RNA update occurs.
4. Data has been generated in the radio bearer that is allowed to trigger the second resumption procedure, but at least one of the second resume condition set is not satisfied.
If all of the second resume condition sets are satisfied, the second resume procedure is triggered.
<Second Resume Condition Set>
1. Data available for transmission is generated in a bearer belonging to the first bearer set.
2. The amount of data available for transmission from the bearer belonging to the first bearer set is less than the final data threshold.
3. The reference signal received power of the current serving cell is higher than the final reference signal received power threshold.
4. The current serving cell provides transmission resource for the second resume procedure.
A radio bearer that allows to trigger second resume procedure is DRB a second resume procedure is allowed and SRB a second resumption procedure is allowed. SRB3 does not allow the second resume procedure, and SRB2 and SRB4 are indicated by explicit information whether the second resume procedure is allowed. When the second resume procedure is allowed in at least one radio bearer, the second resume procedure is automatically allowed in the SRB 1.
The final data threshold is the lower of the dedicated data threshold and the common data threshold or alternatively the dedicated data threshold, if there are both dedicated data thresholds and common data thresholds. If there is only one, it is the final data threshold. Alternatively, if there are both dedicated data thresholds and common data thresholds, the common data threshold is the final data threshold, and if there is only one, it is the final data threshold.
The final reference signal received power threshold is a higher of the dedicated reference signal received power threshold and the common reference signal received power threshold or the dedicated reference signal received power threshold, if there are both dedicated reference signal received power threshold and common reference signal received power threshold. If there is only one, it is the final data threshold. Or, if there are both dedicated reference signal received power threshold and common reference signal received power threshold, the common reference signal received power threshold is the final reference signal received power threshold, and if there is only one, it is the final data threshold.
When at least one of the first condition set is satisfied and all of the second condition sets are satisfied, that is, when both the first resume procedure and the second resume procedure are triggered, the terminal selects the second resume procedure.
In step 2A-23, the terminal performs a first resume procedure or a second resume procedure with the base station.
The first resumption procedure is as follows.
In step 2B-11, the terminal performs the first resume operation set 1. The first resume operation set 1 is operations taken when the first resume procedure is started. By performing the first operation set 1, the terminal may receive a downlink control message from the base station through SRB1.
<First Resume Operation Set 1>
1. Apply default SRB1 configuration.
2. Apply default MAC Cell Group configuration
3. Start T319 set to t319 received from SIB1.
The default SRB1 configuration is as follows.
The default MAC Cell Group configuration is as follows.
T319 set to t319 is a timer to perform follow-up measures, for example, transition to RRC_IDLE, etc., when the first resume procedure fails. T319 set to t319 is stopped when RRCResume is received. If the RRCResume is not received until the T319 set to t319 expires, the terminal performs the T319 expiration operation set.
<T319 Expiration Operation Set>
1. Reset MAC.
2. Discard UE Inactive AS Context.
3. Release suspendConfig.
4. Discard the security key.
5. Release all RLC entities, PDCP entities, and SDAP entities.
6. Transition to RRC_IDLE and perform cell selection operation.
In step 2B-13, the terminal performs the first resume procedure operation set 2. The first resume procedure operation set 2 is operations taken before transmitting the ResumeRequest.
<First Resume Procedure Operation Set 2>
0. Restore RRC configurations of UE Inactive AS context except masterCellGroup and PDCP-config.
1. ResumeMAC-I calculation: Calculate a 16-bit message verification code using the first security key (a security key used in the RRC_CONNECTED state or a security key used at the time of receiving RRC Release).
2. Deriving the second base station security key using the second base station security key. From the second base station security key, the second security key, the third security key, the fourth security key, and the fifth security key are derived.
3. All radio bearers except SRB0 are configured to use second security key and third security key or fourth security key and fifth security key.
3. Reestablish the PDCP entity of SRB 1.
4. Resume SRB1.
In step 2B-15, the terminal transmits a ResumeRequest message to the second base station. The MAC PDU containing the ResumeRequest message does not include data from other radio bearers. ResumeRequest includes the information below.
<ResumeRequest>
1. The first identifier or the second identifier: an identifier indicated in the system information among the first and second identifiers given in SuspendConfig is included.
2. ResumeMAC-I: 16-bit message verification code to ensure integrity of the resume request message. The terminal calculates the resume MAC-I using the previous security key (a security key used in the RRC_CONNECTED state or a security key used at the time of receiving the RRC Release).
3. resumeCause: Indicating one of emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, mcs-PriorityAccess and smallDataTransfer.
The terminal performing the first resume procedure selects one of the remaining values except for smallDataTransfer as the resumeCause. This is to enable the base station to determine whether the second resume procedure is performed through the resumeCause.
In step 2B-17, the terminal receives the RRC Resume. RRCResume includes the following information.
<RRCResume>
1. MasterCellGroup: CellGroupConfig for masterCellGroup includes RLC bearer information, MAC configuration information, PHY configuration information, and SpCell configuration information.
2. RadioBearrConfig: It is radio bearer configuration information and includes SRB configuration information and DRB configuration information.
In step 2B-19, the terminal performs the first resume procedure operation set 3.
<First Resume Procedure Operation Set 3>
1. Stop T319.
2: Stop T380.
3: Restore and apply masterCellGroup of UE Inactive AS Context
4: Apply CellGroupConfig and radioBearerConfig in RRCResume
5. Resume SRB2, SRB3, and all DRBs.
6. Transition to RRC_CONNECTED state.
7. Stop cell reselection procedure.
In step 2B-21, the terminal transmits an RRCResumeComplete message to the second base station. The RRCResumeComplete message includes PLMN identifier information selected by the terminal.
In step 2B-23, the terminal and the second base station transmit and receive data. In this case, the terminal may transmit a MAC CE such as BSR or PHR to the base station together. When the BSR trigger condition is satisfied, the terminal multiplexes the BSR in the uplink MAC PDU and transmit the MAC PDU. When the PHR trigger condition is satisfied, the terminal multiplexes the PHR MAC CE in the uplink MAC PDU and transmit the MAC PDU. BSR trigger conditions include arrival of new data with high priority and expiration of periodic timers. PHR trigger conditions include change of reference signal received power more than a predefined threshold, activation of a new secondary cell, and the like.
In step 2B-25, when data transmission/reception with the terminal is completed, the second base station transmits an RRC Release including SuspendConfig to the terminal to transition the terminal to the RRC_INACTIVE state.
In step 2B-27, the terminal receiving the RRCRelease message including SuspendConfig starts T380.
The second resume procedure is as follows.
In steps 2B-31, the terminal performs the second resume operation set 1. The second resume operation set 1 is operations taken when the second resume procedure is triggered as follows. By performing the second resume operation set 1, the terminal may receive a downlink control message from the base station through the SRB1 and transmit uplink data of the radio bearer (or data transmission in the INACTIVE state, or in which the second resume procedure is configured).
<Second Resume Operation Set 1>
0: Restore all RRC configuration of UE Inactive AS Context (including radio bearer settings of the first set of bearers, masterCellGroup, and PDCP-config).
1. start T319ext set to t319ext
2. stop T380
3. ResumeMAC-I calculation: A 16-bit MAC-I is calculated using the previous K_RRCint that is, the first security key (K_RRCint used in the previous RRC_CONNECTED state or K_RRCint used at the time of receiving RRCRelease).
4. Deriving the second base station security key using the first base station security key and the NCC. From the second base station security key, the second security key, the third security key, the fourth security key, and the fifth security key are derived.
5. Configure the first bearer set to apply the second security key and the third security key or the fourth security key and the fifth security key.
6. Reestablish the PDCP entity of the first bearer set.
7. Resume the radio bearer of the first bearer set.
8. Stop cell reselection procedure
9. Start the second cell reselection procedure.
T319ext set to t319ext is a timer to perform follow-up measures, for example, transition to RRC_IDLE, etc., when the second resume procedure fails. T319, T319ext, and T380 have the following characteristics.
In the first resume procedure, T380 and T319 stops before configuring cell group information after receiving the RRCResume message to prevent unnecessary subsequent operation due to the timer expiration by stopping the timers as a first operation after receiving the RRCResume message.
In the first resume procedure, starting T319 between the time point when the default SRB1 configuration is applied and the time point when SRB1 resumes is to start T319 as close as possible to the time point when SRB 1 becomes available.
In the second resume procedure, starting T319ext between the time point when SRB1 configuration stored in UE Inactive AS Context is applied and the time point when SRB1 resumes is to start T319ext as close as possible to the time point when SRB 1 becomes available.
In the second resume procedure, starting T380 between the time point when SRB1 configuration stored in UE Inactive AS Context is applied and the time point when SRB1 resumes is to start T380 as close as possible to the time point when T319ext starts so that the processing load for timer handling in UE is reduced.
The time point when SRB1 configuration stored in UE Inactive AS Context is applied and the time point when radio bearer configuration for first bearer set stored in UE Inactive AS Context is applied are same.
If the RRCResume is not received until the T319ext set to t319ext expires, the terminal may perform the T319ext expiration operation set or the T319 expiration operation set. The base station may set in SuspendConfig or in system information which one to select between the T319ext expiration operation set and the T319 expiration operation set.
<T319ext Expiration Operation Set>
1. Reset MAC
2. Keep UE Inactive AS Context
3. Keep suspendConfig
4. Discard first base station security key and first security key in UE and store second base station security key and third security key
5. Suspend all SRBs and DRBs
6. Start T380 set to t380
7. Stop second cell reselection procedure
8. Start cell reselection procedure
9. Perform RNA update after selecting a suitable cell
The first bearer set is a set of radio bearers for which the second resume procedure is explicitly or implicitly configured and consists of SRB1 and radio bearers related to the second resume procedure. The radio bearer related to the second resume procedure refers to a radio bearer in which the second resume procedure is explicitly allowed or a radio bearer in which the second resume procedure is explicitly configured.
Stopping the cell reselection procedure means stopping the existing cell reselection procedure performed before the second resume procedure starts.
UE preferentially selects, in the existing cell reselection procedure, a frequency to camp on by considering cell reselection priority provided by base station, ranks each cell of the selected frequency by considering reference signal received power and various offsets, and reselects a highest ranked cell.
When the second cell reselection procedure starts, the terminal stops using the cell reselection priority and offsets indicated by the base station and uses the following parameters.
<Second Cell Reselection Procedure>
1. Increase the cell reselection priority of the current serving frequency to the highest priority.
2. Increase the first Qhyst by a predetermined value. Or apply the second Qhyst.
When the terminal determines the cell ranking, the current serving cell is weighted by Qhyst. That is, the ranking is determined by adding Qhyst to the reference signal received power of the current serving cell. The first Qhyst is included in the SIB2 and broadcasted. The second Qhyst or the predetermined value is included in the SIBX and broadcasted.
In steps 2B-33, the terminal transmits a MAC PDU including a first SDU including a ResumeRequest message and data of first bearer set (or data of a bearer in which a second resume procedure is configured) to the second base station. The terminal performing the second resume procedure selects smallDataTransfer as ResumeCause. The terminal may include a priority-based BSR MAC CE and a PHR MAC CE in the MAC PDU. If the BSR/PHR inclusion condition is satisfied and the BSR/PHR cancellation condition is not satisfied, the terminal includes and transmits the priority-based BSR MAC CE and the PHR MAC CE in the MAC PDU. The terminal transmits MAC PDUs that do not include the priority-based BSR and PHR when the BSR/PHR cancellation condition is satisfied even if the BSR/PHR inclusion condition is satisfied.
<BSR/PHR Inclusion Condition>
There is more data for transmission after transmission of the MAC PDU (or first uplink MAC PDU of the second resume procedure) including ResumeRequest, or uplink grant (or first uplink grant of the second resume procedure) for transmission of MAC PDU including ResumeRequest does not accommodate all pending data available for transmission.
<BSR/PHR Cancellation Condition>
An uplink grant (or the first uplink grant of the second resume procedure) for transmission of MAC PDU including ResumeRequest can accommodate all pending data available for transmission if at least one of a triggered BSR and corresponding subheader or a triggered PHR are not included in the MAC PDU but cannot accommodate all pending data available for transmission if both triggered BSR and corresponding subheader and triggered PHR and corresponding PHR are included in the MAC PDU.
In steps 2B-35, the terminal and the base station transmit and receive data of the first bearer set. Data of the first bearer set is scheduled by C-RNTI, and the terminal monitors a frequency region and a time interval, indicated in SIBX, for transmitting and receiving small amounts of data (or for transmitting and receiving data in the second resume procedure).
When the data transmission is completed, the base station determines to terminate the second resume procedure.
In steps 2B-37, the second base station transmits an RRCRelease including SuspendConfig to the terminal to terminate the second resume procedure. When receiving an RRCRelease including SuspendConfig, the terminal performs the second resume procedure operation set 2 to terminate the second resume procedure.
<Second Resume Operation Set 2>
1. Stop monitoring frequency region and time interval for small data transmission indicated in SIBX
2. Reset MAC
3. Update suspendConfig
4. Discard first base station security key and first security key in UE and store second base station security key and third security key
5. Suspend all SRBs and DRBs except SRB0
6. Start T380 set to t380
7. Stop second cell reselection procedure
8. Start cell reselection procedure
The MAC SDU (first SDU) 2C-15 including the ResumeRequest message is located at the front of the MAC PDU 2C-11 and the MAC SDU (second SDU) 2C-19 including the data of the first bearer set (data of the bearer where second resume procedure is configured) is located at the rear of the MAC PDU. This is to enable the base station receiving the MAC PDU to recognize as quickly as possible that the MAC PDU is a MAC PDU related to the second resume procedure. The first SDU includes a part of the MAC-I calculated by the first security key (K_RRCint previously used), and the second SDU includes a MAC-I calculated by the fifth security key (new K_UPenc derived from the second base station security key). The MAC sub-header 2C-13 of the first SDU includes two R bits and an LCID field, and the MAC sub-header 2C-17 of the second SDU includes one R bit, a F field, a LCID field, and a L field. The LCID field indicates which logical channel the corresponding MAC SDU belongs to or which MAC CE is the corresponding MAC CE, and the L field indicates how many bytes the corresponding MAC SDU or MAC CE is. A MAC SDU or MAC CE and corresponding MAC subheader is referred to as a MAC subPDU. The MAC PDU 2C-11 shown in 2C includes two MAC subPDUs 2C-21 and 2C-23. Hereinafter, a structure of the MAC PDU shown in
The first SDU 2C-15 is a first RRC control message received by the base station. Therefore, the base station and the terminal need to process the first SDU by applying the same configuration without prior consultation. On the other hand, the second SDU 2C-20 may be processed after the base station processes the first SDU and may be processed after the base station restores the UE Inactive AS Context. Accordingly, the second SDU may be processed according to the configuration stored in UE Inactive AS Context.
In the present invention, a first configuration is applied to the first SDU and a second configuration is applied to the second SDU. The first configuration refers to a configuration predetermined in the standard (or a configuration standardized with one value), and the second configuration refers to a configuration stored in the UE Inactive AS Context. Usually, one MAC PDU includes only the MAC SDU to which the first configuration is applied or only the MAC SDU to which the second configuration is applied, but in the present invention, the MAC SDU to which the first configuration is applied and the MAC SDU to which the second configuration is applied are transmitted together in a single MAC PDU. This is to more quickly transmit the MAC SDU to which the second configuration is applied.
The first configuration and the second configuration may include at least PDCP configuration, RLC configuration, and logical channel configuration. The PDCP configuration of the first configuration is PDCP unused, the RLC configuration of the first configuration is RLC TM, the logical channel configuration of the first configuration is the highest priority, LCG ID 0, LCID 0, etc. Alternatively, the first configuration may be a default SRB1 configuration.
The second configuration of a bearer where the second resume procedure is configured is as follows. The PDCP configuration is the PDCP configuration of the corresponding bearer stored in the UE Inactive AS Context, the RLC configuration is the RLC configuration of the RLC bearer associated with the corresponding bearer stored in the UE Inactive AS Context (e.g., various timer values), and the logical channel configuration is the RLC bearer's logical channel configuration. The terminal applies, to the PDCP configuration and the RLC configuration, the configuration stored in the UE Inactive AS Context as it is. The terminal applies, to the logical channel configuration, only some of the configurations stored in the UE Inactive AS Context and does not apply the rest as if they were not configured. The logical channel configuration of the radio bearer belonging to the first bearer set consists of an LCID, an LCG ID, a priority, and various restriction-related configurations. In transmitting data of the first bearer set during the second resume procedure, the terminal uses stored values and processes various restriction-related configurations as if they were not configured. Various restriction-related configurations include, for example, allowedServingCells, allowedSCS-List, and maxPUSCH-Duration. If this restriction-related configuration is not configured, the terminal determines that there is no restriction on the corresponding logical channel in transmitting and receiving data of the logical channel. The stored restriction-related configuration may be applied when the first resume procedure is initiated.
When the first SDU 2C-15 and the second SDU 2C-19 are multiplexed in one MAC PDU during the second resume procedure, the terminal applies a predefined configuration for the first SDU, that is, PDCP not used, RLC TM, highest priority, LCID0 and LCG ID0. The terminal applies, to the second SDU, whole PDCP configuration of the corresponding bearer, whole RLC configuration of the RLC bearer of the corresponding bearer and some of logical channel configuration of the RLC bearer of the corresponding bearer stored in UE Inactive AS Context and does not apply the rest of logical channel configuration of the RLC bearer of the corresponding bearer. The applied logical channel configuration may be an LCID, a priority and an LCG ID, and the non-applied logical channel configuration may be allowedServingCells, allowedSCS-List, maxPUSCH-Duration, and the like.
The terminal generates SDU1 by applying the first configuration, and generates SDU2 by applying the second configuration.
The uplink MAC PDU may include a MAC SDU or a MAC CE. The MAC CE collectively refers to control information generated and transmitted by a MAC layer such as BSR or PHR. MAC CE may have a fixed size or a variable size. The field L is not used for the MAC subheader of the MAC CE having a fixed size. A general MAC SDU has a variable size and an L field is used for a corresponding sub header. The MAC subPDU including the MAC CE is always located behind the MAC subPDU including the MAC SDU. Therefore, in a general uplink MAC PDU in which at least two MAC subPDUs are multiplexed, a MAC subPDU having an L field is located in front and a MAC subPDU having no L field is located in rear. In general, all MAC SDUs included in one uplink MAC PDU are protected by a security key derived from the same base station security key.
2E is a diagram illustrating a hierarchical structure of security keys.
The terminal and the base station perform integrity protection and ciphering using security keys derived from the KgNB 2E-11. Four sub-security keys, K_UPenc 2E-21, K_UPint 2E-23, K_RRCenc 2E-25 and K_RRCint 2E-27 are derived from KgNB 2E-21. KgNB derives KgNB*2E-33 by inputting NCC 2E-31 or the like during a handover or resume procedure, and new sub-security keys are derived from the KgNB*.
In
That is, some of the MAC SDUs included in one MAC PDU during the second resume process are protected by a security key derived from KgNB, and the other MAC SDU is protected by a security key derived from KgNB*.
MAC SDUs multiplexed in the MAC PDU 2D-11 of
KgNB previously used or used at the time of receiving RRCRelease is the first base station security key. K_RRCint derived from the first base station security key is the first security key. KgNB* or derived from the first base station security key and NCC or KgNB derived from the second resumption procedure operation set 1) is the second base station security key. K_RRCenc, K_RRCint, K_UPenc and K_UPint derived from the second security key are denoted as the second security key, the third security key, the fourth security key and fifth security key.
Conventionally, one MAC PDU is ciphered or integrity protected with security keys derived from one base station security key. In the present invention, by multiplexing MAC SDUs protected with security keys derived from different base station security keys into one MAC PDU, the MAC SDUs are transmitted more quickly.
The receiving end also calculates XMAC-I 2H-25 by inputting the security key 2H-19, COUNT 2H-11, message 2H-13, DIRECTION 2H-15, and BEARER 2H-17 into the NR integrity algorithm NIA 2H-21, and determines that the received MAC-I is the same. MAC-I and XMAC-I may be the same only when the same NR integrity algorithm NIA 2H-21, the same security key 2H-19, the same COUNT 2H-11, the same message 2H-13, the same DIRECTION 2H-15, and the same BEARER 2H-17 are used at the transmitting end and receiving ends. MAC-I has a 32-bit size.
MAC-I included in the first SDU 2C-15 of the uplink MAC PDU 2C-11 of the second resume process is the last 16 bits of MAC-I calculated using a first security key, a COUNT set to all 0s, a DIRECTION set to 0 and a message consisting of an identifier of a terminal and an identifier of a cell.
The MAC-I included in the second SDU 2C-19 of the uplink MAC PDU 2C-11 of the second resume process is for a PDCP SDU belonging to the first bearer set, and is calculated using a fifth security key, a COUNT of the PDCP SDU, a DIRECTION set to 0, and a DRB identifier, and a message that is the PDCP SDU.
The transmitting end 2H-31 processes a simple text to a ciphered block as follows and transmits the same to the receiving end 2H-32. The transmitting end generates a keystream block 2H-53 by inputting a security key 2H-49, a COUNT 2H-41, a BEARER 2H-43, a DIRECTION 2H-45, and a LENGTH 2H-47 into the NR Encryption Algorithm (NEA) 2H-51. The transmitting end generates a ciphered block 2H-35 by applying exclusively OR calculation to the generated keystream block with simple text 2H-33, and transmits the generated ciphered block to the receiving end. The LENGTH is the length of the simple text. The receiving end inversely converts the received ciphered block into simple text using the same input and the same security key.
The second SDU 2C-19 of the uplink MAC PDU 2C-11 of the second resume process may include a ciphered PDCP SDU of the first bearer set. The PDCP SDU is ciphered using a fourth security key, a COUNT of the PDCP SDU, a DIRECTION set to 0, a DRB identifier BEARER, and a PDCP SDU length LENGTH.
2F is a diagram illustrating structures of a first BSR MAC CE and a second BSR MAC CE, which are BSR based on a logical channel group.
The first BSR MAC CE includes one logical channel group identifier field 2F-01 and one first buffer size field 2F-03. The logical channel group identifier field 2F-01 has a size of 3 bits and indicates one of the logical channel group identifiers between 0 and 7. The first buffer size field 2F-03 has a 5-bit size and indicates one of the first buffer size indexes between 0 and 31. The first buffer size index 0 means that there is no data available for transmission in the logical channels belonging to the corresponding logical channel group. The first buffer size index 31 means that the sum of data available for transmission of the logical channels belonging to the corresponding logical channel group is greater than the 30th first buffer size. The first buffer size index 1 means that sum of data available for transmission of the logical channels belonging to the corresponding logical channel group is greater than 0 and less than or equal to the first buffer size. The first buffer size index n (2<=n<=30) indicates that sum of data available for transmission of the logical channels belonging to the corresponding logical channel group is greater than or equal to the n−1th first buffer size and less than or equal to the nth first buffer size. The 30 first buffer sizes are defined in the standard.
The second BSR MAC CE includes eight LCGi bits 2F-11 and a plurality of second buffer size fields 2F-13. The LCGi bit indicates whether a second buffer size field exists for the logical channel group i. For example, it indicates whether a second buffer size field exists for LCG1 logical channel group 1. If this field is 1, a second buffer size field exists for the corresponding LCG. The second buffer size field has an 8-bit size and indicates one of the second buffer size indexes between 0 and 255. The second buffer size index 0 means that there is no data available for transmission in the logical channels belonging to the corresponding logical channel group. The second buffer size index 254 means that the sum of data available for transmission of the logical channels belonging to the corresponding logical channel group is greater than the 253rd second buffer size. The second buffer size index 1 means that sum of data available for transmission of the logical channels belonging to the corresponding logical channel group is greater than 0 and less than or equal to the first second buffer size. The second buffer size index n (2<=n<=253) indicates that the sum of data available for transmission of the logical channels belonging to the corresponding logical channel group is greater than or equal to the n−1th second buffer size and less than or equal to the nth second buffer size. The second buffer size index 255 is not used. The 252 second buffer sizes are defined in the standard.
The logical channel group is configured when the logical channel is configured. The logical channel and the logical channel group are configured by RRC control messages.
The fourth BSR MAC CE includes PGi bits and a plurality of second buffer size fields. PGi indicates whether a second buffer size field of the priority group identifier i exists. The priority group consists of at least one priority, and eight groups could be configured from priority group 0 to priority group 7 in one cell. The priority for each logical channel is configured by a predetermined RRC control message received from the first NR cell, and the mapping relationship between the priority and the priority group is configured by a predetermined system information received from the second NR cell. The system information may be SIBX. For example, a list of priorities mapped per priority group may be broadcast through the SIBX.
In 2I-11, The terminal 2A-01 transmits UECapabilityInformation to the base station 2I-01. UECapabilityInformation includes first information related to RRC_INACTIVE and second information related to RRC_INACTIVE. The second resume procedure is also called SDT (Small Data Transmission). Accordingly, the second information related to RRC_INACTIVE is information indicating whether SDT is supported for each band supported by the terminal.
The base station determines the configurations to be applied to the terminal by referring to the terminal's performance information.
In 2I-21, the base station transmits RRCReconfiguration to the terminal The RRCReconfiguration includes various configuration information to be applied by the terminal. The RRCReconfiguration includes a cell group configuration (CellGroupConfig) used for configuring MCG (Master Cell Group) or SCG (Secondary Cell Group).
The cell group configuration includes MAC-CellGroupConfig and RLC bearer list, and MAC-CellGroupConfig includes BSR configuration and PHR configuration.
RLC bearer list consists of a plurality of RLC bearer configurations, and each RLC bearer configuration includes a logical channel configuration. The logical channel configuration includes information such as a logical channel identifier, RLC configurations, identifiers of related bearers and LCGs. RLC configuration includes information such as RLC operation mode, sequence number length, and various timers related to ARQ operation. LCG is an integer between 0 and 3 and indicates the logical channel group to which the logical channel of the corresponding RLC bearer belongs. The LCG may be understood as mapping information between a logical channel and an LCG. LCG or mapping information between an LCG and a logical channel included in the RLC bearer configuration of the RRCReconfiguration message is referred to as first LCG or first LCG logical channel mapping information.
The BSR configuration includes information such as a periodic BSR timer and a retransmission BSR timer. The timers control the BSR trigger operation. The BSR configuration included in the MAC-CellGroupConfig of the RRCReconfiguration message is referred to as a first BSR configuration. The BSR configuration included in the SDT configuration of the RRCRelease is called the second BSR configuration.
PHR configuration consists of periodic PHR timer, PHR prohibit timer, MPE-PHR prohibit timer, multiplePHR, etc. The periodic PHR timer is a timer that controls periodic transmission of the PHR. The PHR prohibit timer is a timer that controls so that frequent PHR transmission does not occur. The MPE-PHR prohibit timer is a timer that controls so that frequent transmission of the MPE (Maximum Permissible Emission) does not occur. In PHR configuration, periodic PHR timer, PHR prohibition timer, and MPE-PHR prohibition timer are mandatory present and multiplePHR is present optionally. The PHR configuration included in the MAC-CellGroupConfig of the RRCReconfiguration message is referred to as a first PHR configuration. The PHR configuration included in the SDT configuration of RRCRelease is referred to as a second PHR configuration.
The terminal and the base station perform data transmission/reception based on the configuration information of the RRCReconfiguration message. When data transmission/reception is completed, the base station may decide to transition the terminal to the inactive state, and may transmit an RRCRelease message.
In step 2I-31, the base station transmits an RRCRelease message to the terminal. The RRCRelease message may include SuspendConfig. The small data transmission configuration may include sdt-DRBList, sdt-SRB2Indication, sdt-LCGList, second BSR configuration, and second PHR configuration.
The first BSR configuration and the first PHR configuration are applied, for example, to the RRC_CONNECTED state when the base station knows the context of the terminal. The second BSR configuration and the second PHR configuration are applied, for example, to the RRC_INACTIVE state when the base station does not know the context of the terminal.
sdt-LCGList is a list of LCGs, and indicates second LCGs of LCHs related to DRBs included in sdt-DRBList and second LCGs of LCHs related to SRBs for which SDT is configured. For example, if DRB 10 and DRB 11 are included in sdt-DRBList, DRB 10 and DRB 11 are related to LCH 8 and LCH 9, both sdt-SRB2Indication and sdt-SRB4Indication exist, and SRB1 is LCH1 and SRB2 is LCH2 and SRB4 is related to LCH4, LCHs related to radio bearers for which SDT is configured are LCH1, LCH2, LCH4, LCH8, and LCH9.
The sdt-LCGList includes 5 LCGs for 5 LCHs related to radio bearers for which the SDT is configured. The mapping information between the LCG and the logical channel included in the sdt-LCGList of the RRCRelease message is called second LCG or second LCG logical channel mapping information. The second LCG or second LCG logical channel mapping information may be provided in SIB1 instead of RRCRelease. In this case, the UE acquires the second BSR configuration from the RRCRelease message and the second LCG from SIB1. Mapping information provided in SIB1 may be mapping information between LCG and priority.
In the second PHR configuration, phr-ProhibitTimer is included and the mpe-ProhibitTimer is not included. The multiplePHR of the second PHR configuration is set to false.
Upon receiving the RRCRelease, the UE stores in the SuspendConfig the first BSR configuration, the first PHR configuration, and the first LCGs in the UE Inactive AS context, and stores and applies the second BSR configuration, the second PHR configuration, and the second LCGs.
When the second resume procedure is started in the inactive state, the UE may trigger and transmit BSR and PHR.
When the first resumption procedure is initiated in the inactive state, the UE may trigger and transmit the BSR and the PHR after transitioning to the RRC connected state.
When the second resume procedure is ongoing and when the second resume procedure is not ongoing or when SDT is ongoing and SDT is not on going, the UE applies different configurations respectively to trigger and generate and transmits BSR and PHR.
In step 2I-41, BSR is triggered. BSR may be triggered when new data arrives in a logical channel belonging to a logical channel group, a periodic timer expires, or a retransmission timer expires.
In step 2I-43, the terminal generates a BSR and transmits it to the base station.
The operation of terminal could be different when the first configuration application condition is fulfilled and when the second configuration application condition is fulfilled.
Table below lists the valid operations presented in the present invention.
The first configuration application condition is satisfied in the following cases.
1: The state of the UE is RRC_CONNECTED when the BSR is triggered and when the BSR is transmitted.
2: T319ext is not running when BSR is triggered and when BSR is transmitted.
3: The second resume procedure is not ongoing when the BSR is triggered and when the BSR is transmitted.
The second configuration application condition is satisfied in the following cases.
1: The state of the UE is RRC_INACTIVE when the BSR is triggered and when the BSR is transmitted.
2: T319ext is running when BSR is triggered and when BSR is transmitted.
3: The second resume procedure is ongoing when the BSR is triggered and when the BSR is transmitted.
In valid operation combination 1, Upon receiving the RRCRelease, the UE stores all of the first BSR configuration, the second BSR configuration, and the first LCGs and the second LCGs. When both the first LCGs and the second LCGs are stored, one logical channel may be associated with two LCGs (the first LCG and the second LCG). The terminal applies, in the inactive state or when the SDT procedure starts and before the SDT procedure ends, the second BSR configuration and the second LCGs in determining whether BSR is triggered and applies the second LCGs in transmitting the triggered BSR. The terminal applies, after transitioning to RRC_CONNECTED by initiating a first RRC resume procedure after completion of SDT procedure, the first BSR configuration and the first LCG in determining whether BR is triggered and applies the first LCGs in transmitting the BSR. Determining whether to trigger BSR by applying the first BSR configuration or the second BSR configuration means that the BSR is triggered according to running and expiration of the periodic timer or the retransmission timer of the first BSR configuration or of the second BSR configuration. Determining the BSR trigger by applying the first LCG or the second LCG means that the BSR is triggered in consideration of whether new data is generated in the logical channel mapped to the first LCG or the logical channel mapped to the second LCG. The UE discards the second BSR configuration and the second LCGs when transitioning to the connected state or to the idle state.
In valid operation combination 2, upon receiving the RRCRelease, the UE replaces the first BSR configuration with the second BSR configuration and stores only the second BSR configuration and stores both the first LCGs and the second LCGs. The terminal applies, in the inactive state or when the SDT procedure starts and before the SDT procedure ends, the second BSR configuration and the second LCGs in determining whether BSR is triggered and applies the second LCGs in transmitting the triggered BSR. The terminal applies, after transitioning to RRC_CONNECTED by initiating a first RRC resume procedure after completion of SDT procedure, the second BSR configuration and the first LCG in determining whether BR is triggered and applies the first LCGs in transmitting the BSR. The UE discards the second LCGs when transitioning to the connected state or transitioning to the idle state.
In valid operation combination 3, upon receiving the RRCRelease, the first BSR configuration, the second BSR configuration, and the first LCGs and the second LCGs are all stored. The terminal applies, in the inactive state or when the SDT procedure starts and before the SDT procedure ends, the second BSR configuration and the second LCGs and default LCGs in determining whether BSR is triggered. The terminal applies the second LCGs to the DRBs configured with SDT and applies to SDT SRBs default LCGs predefined in the standard. Default LCG of SRB1 and of SRB2 is 0 and default LCG of SRB4 is 1. In this operation combination, sdt-LCGList of RRCRelease includes the second LCGs related to the logical channels associated with SDT DRBs. The terminal applies in transmitting triggered BSR the second LCG to the logical channel associated with SDT DRB and default LCG to the logical channel associated with SDT SRB. The terminal applies, after transitioning to RRC_CONNECTED by initiating a first RRC resume procedure after completion of SDT procedure, the first BSR configuration and the first LCG in determining whether BR is triggered and applies the first LCGs in transmitting the BSR. The UE discards the second LCGs when transitioning to the connected state or transitioning to the idle state.
In valid operation combination 4, upon receiving the RRCRelease, the first BSR configuration, the second BSR configuration, and the first LCGs and the second LCGs are all stored. The terminal stores first LCG for the logical channel of the first set and second LCG for the logical channel of the second set. The first set includes logical channels associated with DRBs not configured with SDT and logical channels associated with SRBs not configured with SDT. The second set includes logical channels associated with DRBs configured with SDT and logical channels associated with SRBs configured with SDT. The terminal applies, in the inactive state or when the SDT procedure starts and before the SDT procedure ends, the second BSR configuration and the second LCGs in determining whether BSR is triggered. Terminal applies the second LCG in transmitting the triggered BSR. The terminal applies, after transitioning to RRC_CONNECTED by initiating a first RRC resume procedure after completion of SDT procedure, the first BSR configuration and the first LCG s and the second LCGs in determining whether BR is triggered and applies the first LCGs and the second LCGs in transmitting the BSR. The terminal applies the first LCG to the logical channel of the first set and the second LCG to the logical channel of the second set. The UE discards the second LCGs when transitioning to the connected state or transitioning to the idle state.
In step 2I-51, the PHR is triggered.
In step 2I-53, the terminal generates a PHR and transmits it to the base station.
When the first configuration application condition is satisfied, the UE triggers, generates, and transmits the PHR by applying the first PHR configuration. When the second configuration application condition is satisfied, the UE triggers, generates, and transmits the PHR by applying the second PHR configuration. If the UE can accommodate all available pending data in the uplink grant but cannot additionally accommodate the PHR MAC CE and subheader, the terminal judges whether the PHR is triggered based on the second PHR configuration or the first PHR configuration. If it is triggered based on the second PHR configuration (or if it is triggered in a situation where the second configuration application condition is satisfied), the triggered PHR is canceled without being transmitted.
When one of the following events occurs, the UE performs an operation related to discarding the second BSR configuration, the second PHR configuration, and the second LCG.
1: A message belonging to the first downlink RRC message set is received while the first resume procedure is being performed or the second resume procedure is being performed. The first downlink RRC message set includes RRC resume, RRC setup, RRC release including suspendConfig, and RRC rejection. Upon receiving RRC resume or RRC setup, the UE transitions to the RRC connected state. Upon receiving the RRC rejection, the UE transitions to the RRC idle state. Upon reception of RRC release including suspendConfig, the UE transits to the RRC inactive state. When a state transition occurs, the terminal needs to adjust the configuration information currently being used in the inactive state.
2: Cell reselection occurs or connection establishment cancellation by a higher layer occurs while the first resume procedure is being performed or the second resume procedure is being performed. In this case, the terminal transits to the idle state.
3: Receive a paging including the first terminal identifier in the inactive state. The first terminal identifier is a temporary terminal identifier provided in the 5G core network. It is normal that the paging generated in the LAN is provided for the terminal in the inactive state. The paging including the first terminal identifier has occurred in the core network, and that the inactive terminal receives such a paging means that an unexpected error has occurred, and the terminal transits to the idle state.
The value of T319ext is provided in SIB X or is provided in SIB1. In addition to Table 8, T319ext is also stopped when the above event occurs. Accordingly, even when T319ext is stopped, the UE performs an operation related to discarding the second BSR configuration, the second PHR configuration, and the second LCG.
Operations related to discarding of the second BSR configuration, the second PHR configuration, and the second LCG are as follows.
1: In valid operation combinations 1 and 3, the second BSR configuration, the second PHR configuration, and the second LCG are discarded.
2: In the valid operation combination 2, the second BSR configuration is maintained and the second PHR configuration and the second LCG are discarded.
3: In valid operation combination 4, the second LCG is maintained and the second BSR configuration and the second PHR configuration are discarded.
In step 3A-03, a RRC Reconfiguration including one first BSR configuration and a plurality of first LCGs is received from the base station.
In step 3A-05, RRC Release including one second BSR configuration and a plurality of second LCGs is received from the base station.
In step 3A-07, the BSR is triggered based on the first BSR configuration and the first LCG or based on the second BSR configuration and the second LCG.
If it is the second resume procedure, the BSR is triggered based on the second BSR configuration and the second LCG, and if it is not the second resume procedure, the BSR is triggered based on the second BSR configuration and the second LCGs for the logical channels of second set and the first LCGs for the logical channels of the first set.
RRC Reconfiguration includes cell group configuration, cell group configuration includes a first BSR configuration and a plurality of logical channel configurations, each logical channel configuration of the plurality of logical channel configurations includes a first LCG, and each logical channel configuration of the plurality of logical channel configurations is associated with one DRB (Data Radio Bearer) or one SRB (Signaling Radio Bearer).
RRC Release includes SDT (Small Data Transmission) configuration, the SDT configuration includes SDT-DRB list, SDT-SRB2 indicator, SDT-LCG list and second BSR configuration, SDT-DRB list indicates DRBs in which SDT is configured, and the SDT-LCG list includes a plurality of LCGs for SDT-configured DRBs and SDT-configured SRBs, and each LCG of the plurality of LCGs indicates a second LCG of a SDT-configured SRB or a SDT-configured DRB.
When the resume procedure for SDT is started, the first timer is started, and when RRC Resume is received, the first timer is stopped.
Upon receiving RRC Release, the second BSR configuration and the plurality of first LCGs and second LCGs are stored in a UE inactive access stratum context, and the second BSR configuration and the plurality of second LCGs are applied.
The first set includes logical channels configured for DRBs and associated with DRBs not indicated in the SDT-DRB list, and the second set includes logical channels configured for DRB and associated with DRBs indicated in the SDT-DRB list and logical channels associated with SRB SDT is configured.
The SRB in which SDT is configured is SRB1 and, if the SDT-SRB2 indicator is true, SRB2.
Referring to the diagram, the UE includes a controller 4A-01, a storage unit 4A-02, a transceiver 4A-03, a main processor 4A-04 and I/O unit 4A-05.
The controller 4A-01 controls the overall operations of the UE in terms of mobile communication. For example, the controller 4A-01 receives/transmits signals through the transceiver 4A-03. In addition, the controller 4A-01 records and reads data in the storage unit 4A-02. To this end, the controller 4A-01 includes at least one processor. For example, the controller 4A-01 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls the upper layer, such as an application program. The controller controls storage unit and transceiver such that UE operations illustrated in
The storage unit 4A-02 stores data for operation of the UE, such as a basic program, an application program, and configuration information. The storage unit 4A-02 provides stored data at a request of the controller 4A-01.
The transceiver 4A-03 consists of a RF processor, a baseband processor and plurality of antennas. The RF processor performs functions for transmitting/receiving signals through a wireless channel, such as signal band conversion, amplification, and the like. Specifically, the RF processor up—converts a baseband signal provided from the baseband processor into an RF band signal, transmits the same through an antenna, and down—converts an RF band signal received through the antenna into a baseband signal. The RF processor may include a transmission filter, a reception filter, an amplifier, a mi10r, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like. The RF processor may perform MIMO and may receive multiple layers when performing the MIMO operation. The baseband processor performs a function of conversion between a baseband signal and a bit string according to the physical layer specification of the system. For example, during data transmission, the baseband processor encodes and modulates a transmission bit string, thereby generating complex symbols. In addition, during data reception, the baseband processor demodulates and decodes a baseband signal provided from the RF processor, thereby restoring a reception bit string.
The main processor 4A-04 controls the overall operations other than mobile operation. The main processor 4A-04 process user input received from I/O unit 4A-05, stores data in the storage unit 4A-02, controls the controller 4A-01 for required mobile communication operations and forward user data to I/O unit 4A-05.
I/O unit 4A-05 consists of equipment for inputting user data and for outputting user data such as a microphone and a screen. I/O unit 4A-05 performs inputting and outputting user data based on the main processor's instruction.
As illustrated in the diagram, the base station includes a controller 4B-01, a storage unit 4B-02, a transceiver 4B-03 and a backhaul interface unit 4B-04.
The controller 4B-01 controls the overall operations of the main base station. For example, the controller 4B-01 receives/transmits signals through the transceiver 4B-03, or through the backhaul interface unit 4B-04. In addition, the controller 4B-01 records and reads data in the storage unit 4B-02. To this end, the controller 4B-01 may include at least one processor. The controller controls transceiver, storage unit and backhaul interface such that base station operation illustrated in
The storage unit 4B-02 stores data for operation of the main base station, such as a basic program, an application program, and configuration information. Particularly, the storage unit 4B-02 may store information regarding a bearer allocated to an accessed UE, a measurement result reported from the accessed UE, and the like. In addition, the storage unit 4B-02 may store information serving as a criterion to deter mine whether to provide the UE with multi-connection or to discontinue the same. In addition, the storage unit 4B-02 provides stored data at a request of the controller 4B-01.
The transceiver 4B-03 consists of a RF processor, a baseband processor and plurality of antennas. The RF processor performs functions for transmitting/receiving signals through a wireless channel, such as signal band conversion, amplification, and the like. Specifically, the RF processor up—converts a baseband signal provided from the baseband processor into an RF band signal, transmits the same through an antenna, and down—converts an RF band signal received through the antenna into a baseband signal. The RF processor may include a transmission filter, a reception filter, an amplifier, a mi10r, an oscillator, a DAC, an ADC, and the like. The RF processor may perform a down link MIMO operation by transmitting at least one layer. The baseband processor performs a function of conversion between a baseband signal and a bit string according to the physical layer specification of the first radio access technology. For example, during data transmission, the baseband processor encodes and modulates a transmission bit string, thereby generating complex symbols. In addition, during data reception, the baseband processor demodulates and decodes a baseband signal provided from the RF processor, thereby restoring a reception bit string.
The backhaul interface unit 4B-04 provides an interface for communicating with other nodes inside the network. The backhaul interface unit 4B-04 converts a bit string transmitted from the base station to another node, for example, another base station or a core network, into a physical signal, and converts a physical signal received from the other node into a bit string.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0140635 | Oct 2021 | KR | national |
This application is a continuation of International Application No. PCT/KR2022/014797, filed on Sep. 30, 2022, which claims priority to and the benefit of Korean Patent Application No. 10-2021-0140635, filed on Oct. 21, 2021, the disclosure of which is incorporated herein by reference in its entirety.
| Number | Date | Country |
|---|---|---|
| 1020180109986 | Oct 2018 | KR |
| 1020190123578 | Nov 2019 | KR |
| 1020210088414 | Jul 2021 | KR |
| 1020210123264 | Oct 2021 | KR |
| 1020210125883 | Oct 2021 | KR |
| Entry |
|---|
| 3GPP TS 38.323 V16.5.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 16). |
| 3GPP TS 38.331 V16.6.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network;NR;Radio Resource Control (RRC) protocol specification(Release 16). |
| 3GPP TS 38.321 V16.6.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network;NR;Medium Access Control (MAC) protocol specification(Release 16). |
| 3GPP TS 38.300 V16.7.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2(Release 16). |
| 3GPP TS 38.306 V16.6.0 (Sep. 2021); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR;User Equipment (UE) radio access capabilities(Release 16). |
| Samsung, “Control Plane Common Aspects of RACH and CG based SDT,” 3GPP TSG-RAN2 Meeting #115 Electronic, R2-2107003, Aug. 9-27, 2021. |
| Intel Corporation, “Report of email discussion [Post114-e][507][SData] Non-SDT data arrival handling,” 3GPP TSG RAN WG2 Meeting #115-e, Electronic meeting, R2-2107292, Aug. 16-27, 2021. |
| Intel Corporation, “Control Plane leftover issues on SDT mechanism,” 3GPP TSG RAN WG2 Meeting #115e, Electronic meeting, R2-2107293, Aug. 16-27, 2021. |
| Intel Corporation, “Expected duration and applicable features for SDT procedure,” 3GPP TSG RAN WG2 Meeting #115e, Electronic meeting, R2-2107294, Aug. 16-27, 2021. |
| ZTE Corporation et al., “Control plane common aspects of SDT,” 3GPP TSG-RAN2#115-e, Electronic meeting, R2-2107488, Aug. 16-28, 2021. |
| Qualcomm Incorporated, “CP common aspects of SDT,” 3GPP TSG-RAN WG2 Meeting #115 electronic, Online, R2-2107992 Revision of R2-2105885, Aug. 16-27, 2021. |
| Ericsson, “Failure handling for SDT,” 3GPP TSG-RAN WG2 #115-e, Electronic meeting, R2-2108088, Aug. 16 -27, 2021. |
| Ericsson, “CP aspects for SDT, ” 3GPP TSG-RAN WG2 #115-e, Electronic meeting, R2-2108089, Aug. 16-27, 2021. |
| Xiaomi Communications, “Paging reception during SDT,” 3GPP TSG-RAN WG2 Meeting #115 electronic, E-Meeting, R2-2108790, Aug. 9-27, 2021. |
| Samsung, “User Plane Common Aspects of RACH and CG based SDT,” 3GPP TSG-RAN2 Meeting #115 Electronic R2-2107002, Aug. 9-27, 2021. |
| Intel Corporation, “User plane leftover issues on SDT mechanism,” 3GPP TSG RAN WG2 Meeting #115e, Electronic meeting, R2-2107295, Aug. 16-27, 2021. |
| Zte et al., “The issues on user plane common aspects for SDT,” 3GPP TSG-RAN WG2 #115-e, eMeeting, R2-2107487, Aug. 16-27, 2021. |
| InterDigital, “User plane aspects of small data transmission,” 3GPP RAN WG2 Meeting #115-e, eMeeting, R2-2107844, Aug. 9-27, 2021. |
| Qualcomm Incorporated, “UP common aspects of SDT,” 3GPP TSG-RAN WG2 Meeting #115 electronic, Online, R2-2107991, Aug. 16-27, 2021. |
| Ericsson, “Common aspects for SDT,” 3GPP TSG-RAN WG2 #115-e, Electronic meeting, R2-2108087, Aug. 16 Aug. 16, 2021-Aug. 27, 2021. |
| Xiaomi Communications, “Discussion on the data volume computation,” 3GPP TSG-RAN WG2 Meeting #115 electronic, E-Meeting, R2-2108788, Aug. 9-27, 2021. |
| Xiaomi Communications, “Handling of MAC CE,” 3GPP TSG-RAN WG2 Meeting #115 electronic, E-Meeting, R2-2108789, Aug. 9-27, 2021. |
| ZTE Corporation, “[Post114-e][505][SData] RRC/MAC modeling and RRC running CR (ZTE): Modeling discussion,” 3GPP TSG-RAN2 Meeting #115-e, e-Meeting, R2-210xxxx(R2-2107486), Aug. 16-27, 2021. |
| Huawei et al., “Summary of [Post114-e][506][SData] Running MAC CR review issue list,” 3GPP TSG-RAN2 Meeting #115e, Electronic, R2-2107496, Aug. 9-27, 2021. |
| ZTE Coroporation (rapporteur), “Introduction of SDT” 3GPP TSG-RAN WG2 Meeting #115e, Electronic, R2-2107478, Aug. 16-27, 2021. |
| Huawei et al., “Running MAC CR for Small Data,” 3GPP TSG-RAN2 Meeting #115e, Electronic, R2-2107494, Aug. 9-27, 2021. |
| Huawei et al., “Summary of [Post114-e][506][SData] Running MAC CR review issue list,” 3GPP TSG-RAN2 Meeting #115e, Electronic, R2-2107495, Aug. 9-27, 2021. |
| LG Electronics (Rapporteur), “[AT115-e][501][SData] UP SDT open issues (LG),” 3GPP TSG-RAN2 #115-e, Electronic meeting, R2-2109079, Aug. 16-27, 2021. |
| International Search Report for International Patent Application No. PCT/KR2022/014797, dated Dec. 27, 2022. |
| Number | Date | Country | |
|---|---|---|---|
| 20240163716 A1 | May 2024 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/KR2022/014797 | Sep 2022 | WO |
| Child | 18423348 | US |
