Method and apparatus for configured grant small data transmission in a communication network

Abstract

A user equipment (UE) (12) determines whether uplink (UL) data is restricted from transmission on configured grant small data transmission (CG-SDT) resources, and in response to the data being not restricted, initiates a CG-SDT procedure in which at least a portion of the data is transmitted on the CG-SDT resources. In response to the data being restricted, the UE transmits the data using a random access (RA) SDT or by connecting to an associated communications network. In one example arrangement, the UE receives information from a network used to determine whether the UL data is restricted from transmission on the CG-SDT resources, and the network includes a network node (10) configured to responsively generate and transmit a signaling message indicating the restriction.

Description

Technical Field

[0001] The methods and apparatuses disclosed herein relate to small data transmission in a communication network based on configured grants.

Background Art

[0002] In the 3rd Generation Partnership Project (3GPP (registered trademark)), a new work item (WI) RP-210870, "new Work Item on NR small data transmissions in INACTIVE state" (new WI regarding NR small data transmission in the INACTIVE state), was approved with the aim of optimizing the transmission of small data payloads by reducing signaling overhead. This WI includes the following related objectives to enable small data transmission by a user equipment (UE) in the radio resource control INACTIVE state (RRC_INACTIVE) as follows:

[0003] For the RRC_INACTIVE state: · Uplink (UL) small data transmission using a RACH-based scheme (i.e., 2-step RACH and 4-step RACH, where "RACH" indicates the random access channel): a. General procedures to enable the transmission of small data packets from the INACTIVE state (e.g., using MsgA or Msg3 of the random access (RA) procedure) [RAN2] (for examples of physical layer procedures including RA, see, for example, 3GPP TS 38.213 V16.5.0); b. Enable a flexible payload size larger than the Rel-16 common control channel (CCCH) message size currently possible in the INACTIVE state for MsgA and Msg3 to support user plane (UP) data transmission in UL (the actual payload size can be up to the network configuration) [RAN2]; Context fetching and data transfer in the non-active state of c.RACH-based solutions [RAN2, RAN3] (regardless of anchor relocation). Note 1: Regarding the security aspects of the above solutions, it is necessary to check with 3GPP SA3.

[0004] · Transmission of UL data on preconfigured physical uplink shared channel (PUSCH) resources (i.e., reuse of configured grant type 1) - when timing advance (TA) is valid: a. General procedure for small data transmission via configured grant type 1 resources from the non-active state [RAN2]; b. Configuration of configured grant type 1 resources for small data transmission in the UL of the non-active state [RAN2]; and · If necessary, specify the radio resource management (RRM) core requirements for small data transmission in RRC_INACTIVE [RAN4]

[0005] In narrowband Internet of Things (NB-IoT) and long-term evolution machine type communication (LTE-M), similar signaling optimizations for small data have been introduced through Rel-15 Early Data Transmission (EDT) and Rel-16 Preconfigured Uplink Resources (PUR). A similar solution can also be expected in 5th generation (5G) New Radio (NR), but Rel-17 NR small data is only supported in the RRC_INACTIVE state, includes 2-step RACH-based small data, and also includes normal complex mobile broadband (MBB) UEs, which is different. Both support only mobile-originated (MO) traffic.

[0006] In the context of SDT (Small Data Transmission), the possibility of transmitting subsequent data is being discussed, which means transmitting additional segments of data that cannot fit into the Msg3 transport block (TB). Such data segments can be transmitted in RRC_CONNECTED like the legacy approach after the 4-step RACH procedure is completed, or can be transmitted in RRC_INACTIVE before the associated UE transitions to RRC_CONNECTED. In the former case, since the gNB and UE are appropriately configured based on the current UE channel state, the transmission is more efficient. However, in the latter case, since some optimizations have not been carried out yet, especially when the UE has moved while not connected, and the contention has not been resolved yet, it may collide with transmissions from other UEs.

[0007] WI was already started at 3GPP meeting RAN2#111-e, and the following related agreements have already been made: · Small data transmission via Radio Resource Control (RRC) messages is supported as a baseline for both RA-based and Configured Grant (CG)-based schemes; · 2-step RACH or 4-step RACH should be applied to RACH-based uplink SDT in RRC_INACTIVE; · Uplink small data can be transmitted in MSGA of 2-step RACH or msg3 of 4-step RACH; · SDT is configured by the network for each Data Radio Bearer (DRB) Base ; · A data volume threshold is used to determine whether the UE performs SDT. The method for calculating the data volume is FFS (For Further Study); · Whether an "additional SDT-specific" RSRP threshold is used by the UE to determine whether the UE should perform SDT is FFS; · UL / DL transmission following UL SDT is supported without transitioning to RRC_CONNECTED. ·UE is In the case of RRC_INACTIVE, as part of the same SDT mechanism, it should be possible to send multiple UL and DL packets without transitioning to RRC_CONNECTED with a dedicated grant - whether additional details and network indication are required is FFS.

[0008] Some of the mechanisms discussed in this document have already been agreed upon and thus do not represent the purpose of the solutions presented in this document. Instead, it should be noted that they serve the purpose of presenting a complete practical solution. Regarding SDT by a UE using a Configured Grant (CG) in the inactive state in RAN2#112 - e, the following agreements were made: 1. The configuration of the CG resources for UE UL SDT is included in the RRC release message. Whether other dedicated messages can configure the CG with INACTIVE CG is FFS. The configuration is only for type 1 CG and there is no CG conflict resolution procedure. 2. The configuration of the CG resources can include one type 1 CG configuration. Whether multiple configured CGs are permitted is FFS. 3. A new TA timer (TAT) for TA maintenance, which is specified for CG - based SDT in RRC_INACTIVE, should be introduced. The procedure, the validity of TA, and how to handle the expiration of the TA timer are FFS. The TA timer is configured together with the CG configuration in the RRC release message.

[0009] 4. The configuration of the CG resources for UE SDT is only valid within the same serving cell. For other CG validity criteria ( Example: timer, UL / SUL (Supplemental UL) aspects, etc.) is FFS. 5. The UE can use CG-based SDT if at least the following criteria are met: (1) the user data is smaller than the data volume threshold, (2) the CG resources are configured and valid, and (3) the UE has a valid TA. The candidate beam criteria are FFS. 6. From the perspective of RAN2: For CG-based SDT, an association between CG resources and Synchronization Signal Blocks (SSBs) is required. How to configure or provide the association to the UE is FFS by RAN1. One of the options considered by RAN2 is explicit configuration by the RRC release message. 7. The threshold of the reference signal received power (RSRP) of the synchronization signal (SS) is configured for SSB selection. The UE selects one of the SSBs whose SS-RSRP exceeds the threshold and selects the associated CG resources for UL data transmission.

[0010] In RAN2#113-e, the following agreements were made: 1. Since the CG-SDT resource configuration is provided to the UE only within RRC_Connected in the RRC release message, there is no need to include it in the RRC reconfiguration message. 2. CG-PUSCH resources can be configured separately for normal UL (NUL) and supplementary UL (SUL). Whether to permit them simultaneously is FFS and is based on the Rel-16 alignment CR. 3. The RRC release message is used for the UE to reconfigure or release CG-SDT resources while in RRC_INACTIVE. 4. In the case of CG-SDT, subsequent data transmissions can use CG resources or DGs (i.e., DGs addressed to the UE's C-RNTI (Cell Radio Network Temporary Identifier)). The details of the C-RNTI may be the same as the previous C-RNTI or may be explicitly configured by the network.

[0011] 5. TAT-SDT can be started when it receives the TAT-SDT configuration from the gNB, i.e., when it is started in the RRC release message and can be (re)started when it receives the TA command. 6. From the perspective of RAN2, similar to PUR, it is assumed that a TA verification mechanism for SDT based on the change in RSRP is introduced, i.e., an RSRP-based threshold is configured. As for how to handle the CG configuration when the TA expires or becomes invalid due to the RSRP threshold, it is FFS.

[0012] 7. The basic assumption is a network configuration issue regarding whether to support multiple CG-SDT configurations per carrier in RRC_INACTIVE. 8. As another item of FFS, it is discussed how to specify in stage 3 the agreement that the CG-SDT resource is only valid in one cell (i.e., only valid in the cell where the RRC release is received). is shall be discussed. 9. When TAT expires in the RRC_Inactive state, the UE releases the CG-SDT resource. 10. In RA-SDT, the network can configure up to two preamble groups (corresponding to two different payload sizes of MSGA / WSG3).

[0013] 11. When the RACH procedure is started for SDT (i.e., RA-SDT is started), the UE first performs the selection of the RACH type as defined in the Media Access Control (MAC) (i.e., Rel-16). Whether the threshold is SDT-specific is FFS. 12. RAN2 continues to recommend work based on individual RACH resources for SDT (i.e., an explicit mechanism to support common resources is not pursued unless there is sufficient support). However, the use of common RACH resources is not prohibited if possible by the implementation.

[0014] 13. In the RAN2 design, it is assumed that an RRC release message is sent last to end the SDT procedure from the RRC perspective. The RRC release sent at the end of the SDT may include CG resources (in accordance with previous agreements). 14. The UE behavior regarding the handling of non-SDT data arrival after sending the first UL data packet is fully specified (i.e., not left to the UE implementation). 15. RAN2 is considering FFS for an additional option of using a dedicated control channel (DCCH) message to indicate the arrival of non-SDT data (details are under consideration).

[0015] 16. FFS: The RSRP threshold for selecting between the SDT procedure and the non-SDT procedure. 17. FFS regarding whether the RSRP threshold for selecting between the SDT procedure and the non-SDT procedure is used in CG-SDT, RA-SDT, or both, whether the RSRP threshold is the same in CG-SDT and RA-SDT, and when the RSRP threshold check is performed. 18. FFS regarding whether it is possible to select both carriers when CG resources are available on only one carrier. 19. In the case of SDT, the UE performs UL carrier selection (i.e., when SUL is configured within the cell, the UL carrier is selected based on the RSRP threshold). Whether the RSRP threshold for carrier selection is specific to SDT is FFS.)

[0016] 20. If the CG-SDT resources are configured on the selected UL carrier and are valid, CG-SDT is selected. Otherwise, · If the two-step RA-SDT resources are configured on the UL carrier and the criteria for selecting the two-step RA SDT are met, the two-step RA-SDT is selected. · Otherwise, if the 4-step RA-SDT resource is configured on the UL carrier and the criteria for selecting the 4-step RA SDT are met, the 4-step RA-SDT is selected. · Otherwise, the UE does not perform SDT (i.e., performs a resume procedure other than SDT). · If both the 2-step RA-SDT and 4-step RA-SDT resources are configured on the UL carrier, the selection of the RA type is performed based on the RSRP threshold. - For FFS regarding whether the RSRP threshold for selecting the RA type is common or different between SDT and non-SDT. - For FFS regarding whether the latency of the availability of the CG resource needs to be considered.

[0017] The working premise is as follows: 1. Support the configuration of Signaling Radio Bearer 1 (SRB1) and SRB2 for SDT to transmit RRC and NAS (Non-Access Stratum) messages. 2. When starting the RRC resume procedure for SDT start (i.e., for the first SDT transmission), the UE also resumes the SRB2 configured for SDT in addition to the SDT DRB configured for SDT. 3. RAN2 recommends including SRB2 in the WID.

[0018] In RAN2#113bis-e, the following agreements were made: 1. The RSRP threshold, if set, is used to select SDT procedures and non-SDT procedures (RSRP refers to the same RSRP measured for carrier selection). 2. The RSRP threshold for selecting SDT procedures and non-SDT procedures is used for both CG-SDT and RA-SDT. 3. The RSRP threshold for selecting SDT procedures and non-SDT procedures is the same for both CG-SDT and RA-SDT.

[0019] 4. The RSRP threshold for carrier selection is specific to the SDT (i.e., configured individually for the SDT). This is a network option. 5. Confirm that the cell selection mechanism has not been changed. 6. The RSRP threshold for RA type selection is specific to the SDT (i.e., configured individually for the SDT). 7. The data volume threshold is the same for CG-SDT and RA-SDT (this is checked for majority support during the stage discussion).

[0020] 8. The order and missing parts (e.g., failure, fallback) of the high-level procedures are FFS. The details of the procedures are left to the third stage. The following procedures are FFS but are copied for information. A. When data arrives only for DRBs / SRBs for which SDT is enabled, the high-level procedure for SDT and non-SDT selection is as follows: If the CG-SDT criteria are met: The UE selects CG-SDT. The UE starts the SDT procedure. Otherwise, if the RA-SDT criteria are met: The UE selects RA-SDT. The UE starts the SDT procedure. Otherwise: The UE starts the non-SDT procedure. B. The CG-SDT criteria are considered to be met when all of the following conditions are satisfied: 1) Available data volume <= data volume threshold 2) RSRP is greater than or equal to the configured threshold FFS 3) The CG-SDT resources are configured and valid on the selected UL carrier. C. The RA-SDT criteria are considered to be met when all of the following conditions are satisfied: 1) Available data volume <= data volume threshold 2) RSRP is configured performed Greater than or equal to the threshold 3) The 4-step RA-SDT resource is configured on the selected UL carrier and the criteria for selecting the 4-step RA SDT are met, or the 2-step RA-SDT resource is configured on the selected UL carrier and the criteria for selecting the 2-step RA SDT are met.

[0021] 9. The switch from SDT to non-SDT is supported. 10. The switch from FFS CG-SDT to RA-SDT is not possible. 11. In the following cases, the UE switches from SDT to non-SDT: - Case 1 (27 / 0): The UE receives an instruction to switch from the network to non-SDT procedure. - The network can send RRCResume. Whether the network can send an instruction to switch to non-SDT procedure with RAR / fallbackRAR / DCI is FFS. - FFS Case 2 (18 / 9): The first UL transmission (within msgA / msg3 / CG resource) fails the set number of times. 12. The gNB can only configure the MN-terminated MCG bearer type for SDT.

[0022] 13. The non-SDT radio bearer is resumed only when receiving RRCResume (the same as the current one). 14. Narrow down the scope to two solutions (CCCH or DCCH) and ask SA3 about the security issue (explain that the CCCH message is repeated within the same cell). 15. When the UE starts the SDT procedure, the UE implicitly performs the re-establishment of the Packet Data Convergence Protocol (PDCP), that is, without an explicit instruction for PDCP re-establishment. 16. Similar to legacy, whether to support the continuity of RObust Header Compression (ROHC) is explicitly set by the network.

[0023] 17. PDCP duplication is not supported in SDT. 18. Connected mode discontinuous reception (DRX) is not supported in SDT. 19. The power headroom report (PHR) function is supported in SDT. FFS in the PHR procedure. 20. SR resources are not configured for SDT. When a buffer status report (BSR) is triggered by SDT data, the UE triggers a RA because the scheduling request (SR) resources are not available, just as in the legacy procedure. 21. The SDT failure detection timer is started at the start of the SDT procedure.

[0024] 22. When an RRCResumeRequest or RRCResumeRequest1 is sent for SDT, T319 legacy is not started. 23. The T319 legacy stop condition also applies to the SDT failure detection timer. 24. The RRC re-establishment procedure is not supported in SDT. 25. To verify the feasibility / impact of temporarily reusing the same NCC / I-RNTI value in the RRC resume procedure of a new cell during the SDT procedure, LS is sent to SA3 (including the same cell question from 502).

[0025] 26. FFS-RAN2 shall select one of the following options for cell reselection during an ongoing SDT procedure at the next meeting: 1) The UE moves to IDLE and, optionally, performs a higher layer retransmission (8 / 25), or 2) The UE remains INACTIVE and sends an RRC Resume to the new cell. 27. When the FFS SDT failure detection timer expires, the same procedure as for T319 expiration is used (e.g., move to IDLE and attempt an RRC connection setup as when the T319 timer expires) (18 / 8). 28. CG-SDT resources can be configured simultaneously on NUL and SUL. 29. Implicit release of CG-SDT resources is not supported. 30. The UE starts a window after CG / DG transmission for CG-SDT. Whether to design a new timer or reuse an existing timer is FFS. 31. Support retransmission by the dynamic grant of CG-SDT. 32. Support multiple HARQ processes for uplink CG-SDT. 33. The availability delay of CG resources is not considered as a criterion for CG verification. 34. UL carrier selection is performed before CG-SDT selection. 35. FFS CG-SDT resources can be configured to BWPs other than the initial BWP.

[0026] In RAN1, the following agreement was reached on how to define the association between CG resources and SSBs in CG-based SDT. Agreement at RAN1#104bis-e meeting: · For each CG configuration, the CG resources are associated with the set of SSBs configured by explicit signaling. ○ How to define the SSB-to-PUSCH resource mapping within the CG configuration is FFS. ○ If there is FFS, give specific changes to the CG configuration to support additional SSB-to-PUSCH mappings.

[0027] Agreement at RAN1#105-e meeting: · The SSB-to-PUSCH resource mapping within the CG configuration is implicitly defined. ○ The order of SSB and CG PUSCH resources should be captured in the RAN1 specification. · The PUSCH resource refers to the transmission opportunity and DMRS resources used for PUSCH transmission · The order of SSBs can be reused from the mapping of SSB to R0. · The order of CG PUSCH resources can be reused as much as possible from the order of MsgA PUSCH resources. ○ Determination of the FFS mapping ratio and the associated period, e.g., explicitly signaled or implicitly derived ○ Restrictions on combinations of parameters of FFS CG resources In the NR Rel-17 SDT work item, two main solutions are planned to enable SDT in the RRC_INACTIVE state: RACH-based SDT (i.e., sending small data to the Message A PUSCH in the 2-step RACH procedure or sending small data to the Message 3 PUSCH in the 4-step RACH procedure), and Configured Grant (CG)-based SDT (i.e., SDT that uses the Configured Grant Type-1 PUSCH resource for UEs in the RRC inactive state).

[0028] The 4-step, 2-step RACH, and configured grant types are already defined as part of Rel-15 and Rel-16. Therefore, the SDT function defined in NR Rel-17 is built based on these components to enable small data transmission in the INACTIVE state in NR.

[0029] NR CG-based PUSCH transmission The CG PUSCH resource is a pre-configured PUSCH resource for the UE. When there is uplink data in the UE's buffer, the UE can start uplink transmission immediately using the pre-configured PUSCH resource without waiting for a UL grant from the gNB, thus reducing the waiting time. NR supports CG type 1 PUSCH transmission and CG type 2 PUSCH transmission. For both of these two types, the PUSCH resources (time and frequency allocation, periodicity, etc.) are pre-configured by dedicated RRC signaling. The CG type 1 PUSCH transmission is activated / deactivated by RRC signaling, and the CG type 2 PUSCH transmission is activated / deactivated by a UL grant using downlink control information (DCI) signaling. For small data transmission, it is agreed that CG type 1 should be the baseline.

[0030] According to the RAN2 agreement on CG-SDT, the CG-SDT configuration is sent to the UE in the RRC release message, specifying the association between the CG resource (transmission opportunity) and the SSB. When the UE starts the CG-SDT procedure, it selects an SSB with an SS-RSRP exceeding the set RSRP threshold. As shown in Figure 1, the UE can have one or more SSBs that meet the SS-RSRP threshold criteria. The circle indicates the area where the SS-RSRP exceeds the set RSRP threshold. Note the intersection (overlapping beam coverage area) where UE2 detects both SSB0 and SSB3 with SS-RSRP above the threshold.

[0031] When an SSB on the SS-RSRP is selected, the UE transmits on the CG resources associated with the selected SSB. Since it is possible to configure multiple CG-SDT configurations for the UE, one option is to configure one or a different set of SSBs in each CG-SDT configuration. Another option is that only one CG-SDT configuration is given to the UE and this configuration includes all the SSBs that the UE can use.

[0032] Restrictions on logical channel prioritization (LCP) mapping and restrictions on logical channels (LCHs) The possibility of excluding data belonging to a specific LCH from transmission on specific resources is controlled by parameters: - configuredGrantType1Allowd sets whether configured grant type 1 can be used for transmission; - allowedCG - list sets the configured grants that are permitted for transmission; These parameters are configured based on LCH. According to 3GPP TS 38.321 v16.5.0: 5.4.3.1 Logical channel prioritization 5.4.3.1.1 General The logical channel prioritization (LCP) procedure is applied each time a new transmission is performed. The RRC controls the uplink data scheduling by signaling for each logical channel for each MAC entity: - The larger the value of priority, the lower the priority level; - prioritizerdBitRate sets the priority bit rate (PBR); - bucketSizeDuration sets the bucket size duration (BSD). The RRC further controls the LCP procedure by configuring the mapping restrictions for each logical channel. - The allowed SCS list sets the subcarrier spacing allowed for transmission; - The max PUSCH - Duration sets the maximum PUSCH duration allowed for transmission; - The configured GrantType1Allowd sets whether configured grant type 1 can be used for transmission; - The allowed Serving Cells sets the cells allowed for transmission; - The allowed CG - List sets the configured grants allowed for transmission; - The allowed PHY - PriorityIndex sets the allowed PHY priority index for dynamic grants for transmission.

[0033] In the logical channel priority setting procedure, the following UE variables are used: - Bj is maintained for each logical channel j. The MAC entity shall initialize Bj of the logical channel to zero when the logical channel is established. For each logical channel j, the MAC entity shall do the following: 1> Before all instances of the LCP procedure, increment Bj by the product PBR×T, where T is the time elapsed since Bj was last incremented; 1> If the value of Bj is greater than the bucket size (i.e., PBR×BSD): 2> Set Bj to the bucket size. Note: The exact timing at which the UE updates Bj during the LCP procedure depends on the UE implementation as long as Bj is up - to - date when the grant is processed by the LCP.

[0034] 5.4.3.1.2 Selection of Logical Channels When a new transmission is to be performed, the MAC entity shall do the following: 1>For each UL grant, select a logical channel that satisfies all of the following conditions: 2>If allowedSCS-List is configured, the set of permitted subcarrier spacing index values includes the subcarrier spacing index associated with the UL grant; and 2>If maxPUSCH-Duration is configured, it is greater than or equal to the PUSCH transmission duration associated with the UL grant; and 2>If configuredGrantType1Allowed is configured, it is set to true if the UL grant is a configured grant type 1; and 2>If allowedServingCells is configured, it includes the cell information associated with the UL grant. It does not apply to logical channels associated with DRBs for which PDCP duplication is configured within the same MAC entity (i.e., duplication for CA); and 2>If allowedCG-List is set, it includes the configured grant index associated with the UL grant; and 2>If allowedPHY-PriorityIndex is set, it includes the priority index associated with the dynamic UL grant (as defined in Section 9 of TS 38.213). Note: The subcarrier spacing index, PUSCH transmission duration, cell information, and priority index are included in the uplink transmission information received from the lower layer for the corresponding scheduled uplink transmission.

[0035] This means that for data of an LCH where configuratedGrantType1Allowed is set but set to false, or for data of an LCH where allowedCG-List is set but does not include the configured grant index associated with the UL grant, the data is not transmitted on the CG resource.

[0036] Furthermore, when the BSR is triggered for the LCH, the same situation applies (from 38.321, section 5.4.5): "The MAC entity shall perform the following: 1> When the buffer status reporting procedure determines that at least one BSR has been triggered and not cancelled: 2> When UL-SCH resources are available for a new transmission and, as a result of the logical channel prioritization, the UL-SCH resources can accommodate the BSR MAC CE and its sub-header: 3> Instruct the multiplexing and assembly procedures to generate the BSR MAC CE(s); 3> Start or restart the periodic BSR-Timer, except when all generated BSRs are long or short TruncatedBSRs; 3> Start or restart the retxBSR-Timer. 2> When a normal BSR is triggered and the logicalChannelISR-DelayTimer is not running: 3> When there are no UL-SCH resources available for a new transmission; or 3> When a normal BSR is triggered for a logical channel configured with the uplink grant set by the MAC entity and with the logicalChannelSR-Mask set to false; or 3> When the UL-SCH resources available for a new transmission do not meet the LCP mapping restrictions (see clause 5.4.3.1) set for the logical channel that triggered the BSR: 4> Trigger a scheduling request. Note 2: The UL-SCH resource is considered available when the MAC entity has an active configuration for any type of configured uplink grant, or when the MAC entity receives a dynamic uplink grant, or when both of these conditions are met. At a certain point in time, if the MAC entity determines that the UL-SCH resource is available, it does not necessarily mean that the UL-SCH resource is available at that time.

[0037] Therefore, if the LCH that triggered the BSR is not permitted to transmit on the CG resource, the triggered BSR may trigger a scheduling request (SR) instead of the BSR.

[0038] Currently, there is a problem. In the agreed-upon procedure for selecting the configured grant-based SDT (CG-SDT) and the random access-based SDT (RA-SDT), the CG-SDT is selected in the following cases. · The CG-SDT is available on the selected carrier (SUL or NUL carrier). · The timing advance timer (TAT) is running · The RSRP exceeds a specific threshold

[0039] Using these selection criteria, if there is an LCH restriction that does not permit transmission on the CG-SDT resource for the data triggering the SDT procedure, the CG-SDT procedure may be initiated. How to handle this is not specified, and if multiple SDT procedures are initiated, etc., which are not specified, it may lead to undesirable behavior.

[0040] Another aspect is how the operation should be when an SR is triggered during an ongoing SDT procedure due to data on an LCH that may not be transmitted on the CG-SDT resource.

SUMMARY OF THE INVENTION

[0041] Some aspects of the present disclosure and its embodiments can provide solutions to these or other problems. First, in the present disclosure, the terms LCH restriction and LCP mapping restriction are used to indicate that data mapped to a specific LCH, or the BSR indicating the amount of this data, shall not be transmitted on the CG-SDT resource. It should also be noted that similar restrictions can alternatively be applied to the DRB, in which case the mapping restriction means that the data on this DRB, or the BSR indicating the amount of this data, may not need to be transmitted on the CG-SDT resource.

[0042] According to one or more exemplary embodiments disclosed herein, the selection criteria for CG-SDT also include LCH restrictions. As a result, if the data triggering the SDT procedure cannot be transmitted on the CG-SDT resource due to the LCH restriction, CG-SDT is not selected.

[0043] When the CG-SDT procedure is in progress, i.e., when the RRCResumeRequest is transmitted on the first CG-SDT resource and data belonging to an LCH that cannot be transmitted on the CG-SDT resource due to the LCH restriction arrives at the UE's buffer, is the transmission of the BSR indicating this on the CG-SDT resource permitted (thus changing to the normal BSR rule), or is the RA started, and Msg3 or MsgA within this procedure includes the C-RNTI MAC CE and data, or the BSR indicating the amount of this data and in some cases a part of the data that can be transmitted in the TB.

[0044] Certain embodiments may provide some technical advantages. An exemplary advantage is that the SDT procedure is defined in an efficient way to handle data subject to LCH restrictions.

[0045] One embodiment comprises a method performed by a user equipment (UE) with respect to a communication network. The method includes: while the UE is in an inactive mode, receiving data in a UL transmission buffer of the UE; determining whether the data is restricted from transmission on a CG-SDT (Configured Grant Small Data Transmission) resource; and initiating a CG-SDT procedure in which at least a portion of the data is transmitted on the CG-SDT resource in response to the data not being restricted.

[0046] A related embodiment comprises a UE configured to operate with respect to a communication network. The UE includes a communication interface and a processing circuit. The communication interface includes a radio transmitter and a receiver configured to transmit signals for and receive signals from the communication network. The processing circuit is configured to: while the UE is in an inactive mode, receive data in a UL transmission buffer of the UE; determine whether the data is restricted from transmission on a CG-SDT resource; and initiate, via the communication interface, a CG-SDT procedure in which at least a portion of the data is transmitted on the CG-SDT resource in response to the data not being restricted. as configured.

[0047] Another embodiment includes a method performed by a network node of a communication network. The method includes: the network node generating a signaling message indicating a restriction for the UE to determine whether transmission of a given data arriving subsequently in a UL transmission buffer of the UE is restricted from using a CG-SDT procedure; and transmitting the signaling message to the UE.

[0048] The related embodiments comprise a network node configured to operate in a communication network. The network node includes a communication interface and a processing circuit. The processing circuit is configured to generate a signaling message indicating a restriction for a UE to determine whether transmission of predetermined data arriving subsequent to the UL transmission buffer of the UE is restricted using a CG-SDT procedure, and to transmit the signaling message to the UE via the communication interface.

Brief Description of the Drawings

[0049]

Figure 1

Figure 2

Figure 3

Figure 4

Figure QQ1

Figure QQ2

Figure QQ3

Figure QQ4

Figure QQ5

Figure QQ6

Modes for Carrying Out the Invention

[0050] Here, some of the embodiments contemplated herein will be described more fully with reference to the accompanying drawings. The embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0051] As described above, the terms "LCH restriction" and "LCP mapping restriction" are used to indicate that data mapped to a particular LCH, or a BSR indicating the amount of this data, cannot be transmitted on the CG-SDT resource. It has also been explained that similar restrictions apply to DRBs instead, in which case the mapping restriction means that data on the DRB, or a BSR indicating the amount of this data, cannot be transmitted on the CG-SDT resource. The described embodiments are valid in both of these cases.

[0052] This disclosure describes some embodiments in the case of transmitting on the CG-SDT resource data on an LCH that is subject to an LCH restriction that does not permit the transmission of this data, or a BSR indicating the amount of this data.

[0053] In a first embodiment, when the SDT procedure is started and some or all of the available UL data within a DRB configured for SDT is mapped to an LCH that is subject to an LCH restriction that does not permit transmission on the CG-SDT resource, the CG-SDT procedure is not selected. This embodiment can be implemented by adding a selection criterion for CG-SDT such that CG-SDT can only be selected when the data is on an LCH / DRB that is not restricted from CG-SDT. An LCH or DRB that is restricted from CG-SDT may be referred to as a "restricted LCH" or a "restricted DRB". Similarly, for convenience, data belonging to a restricted LCH or a restricted DRB may be referred to as "restricted data" to indicate that its transmission on the CG-SDT resource is restricted.

[0054] As an example of the selection criteria for CG-SDT, CG-SDT is selected in the following cases. 1. It is available on the carrier (SUL or NUL carrier) on which CG-SDT is selected, and 2. The Timing Advance Timer (TAT) is operating, and 3. The RSRP exceeds a specific threshold, and 4. The data to be transmitted belongs to an LCH or DRB that may be transmitted on the configured CG-SDT resource. In one option, if there is data mapping to multiple LCHs or DRBs, and at least one of them is restricted from using CG-SDT, the RA-SDT procedure is initiated.

[0055] In the second embodiment, when the CG-SDT procedure is initiated, i.e., when the RRCResumeRequest is transmitted on the first CG-SDT resource and data belonging to an LCH or DRB that cannot be transmitted on the CG-SDT resource due to LCH restrictions arrives at the UE buffer, the following occurs. The random access (RA) procedure is initiated, where msg3 or msgA includes the C-RNTI MAC CE and the data belonging to this LCH or DRB. In one option, msg3 or msgA also includes a BSR indicating the amount of this data. In one option, the RA procedure is executed on the RA resource configured for SDT. In one option, the RA procedure is executed on a legacy RA resource.

[0056] In the third embodiment, when the CG-SDT procedure is initiated, i.e., when the RRCResumeRequest is transmitted on the first CG-SDT resource and data belonging to an LCH or DRB that cannot be transmitted on the CG-SDT resource due to LCH restrictions arrives at the UE buffer, a BSR is transmitted on the CG-SDT resource to indicate the amount of data.

[0057] In the fourth embodiment, the selection of whether to use Embodiment 2 or Embodiment 3 is made based on the following: · Based on the time to the next CG-SDT resource, if the time is less than the threshold, Embodiment 3 is selected; · The priority of LCH or DRB; · The size of the data belonging to LCH or DRB that cannot be transmitted with the CG-SDT resource due to the limitation of LCH (for example, if all the data fits within msg3 or msgA, Embodiment 2 is selected); · The above combinations; or, · Left for UE implementation.

[0058] In the fourth embodiment, the restriction is signaled in the RRC release message that configures the CG SDT. In one option, the DRB or LCH that can use the CG-SDT resource is indicated by new parameters or by reinterpreting the legacy parameters configuredGrantType1Allowed and allowedCG-List. In one option, if these parameters are not configured, it means that all DRBs or LCHs available for SDT can use CG-SDT.

[0059] FIG. 2 shows an exemplary embodiment of network node 10 and wireless device 12. "Wireless device" and "user equipment" or "UE" are all interchangeable terms unless otherwise specified or indicated by the context of use. Therefore, the wireless device 12 depicted in the above figure can be understood as a UE configured to perform any of the UE-based operations described herein. Similarly, the network node 10 depicted in the figure can be understood as being configured to perform any of the network-side operations described herein.

[0060] Exemplary wireless device 12 includes one or more communication interfaces 20 that include at least a radio frequency (RF) transceiver consisting of a transmission circuit 22 and a reception circuit 24. Wireless device 12 further includes a processing circuit 26. In one or more embodiments, processing circuit 26 includes or is associated with a storage 28 that comprises one or more types of memory circuits or other computer-readable media. Storage 28 stores, for example, one or more computer programs (「CP(s)」) consisting of stored computer program instructions.

[0061] For example, in one or more embodiments, the processing circuit 26 of wireless device 12 is composed of one or more microprocessors or digital signal processors (DSPs) or other digital processing circuits that are programmatically configured according to the instructions of computer program instructions stored in the included or associated storage. As described above, storage 28 consists of one or more types of computer-readable media that store information with at least a certain degree of persistence. Examples of storage include any one or more of SRAM, DRAM, FLASH, solid state disk (SSD), EEPROM, or volatile storage or non-volatile storage, or other memory circuits or storage devices that provide both volatile storage and non-volatile storage. For example, storage 28 can include volatile working memory configured to hold program instructions for execution along with working data, and can also include non-volatile storage for long-term storage of program instructions and configuration data (shown as CFG.DATA32 in the figure).

[0062] A general understanding of processing circuit 26 is that it is composed of fixed circuits or programmatically configured circuits, or a combination of both, and is configured to perform UE-based operations described herein in any of various embodiments.

[0063] Similar implementation details also apply to the processing circuitry and storage implemented in network node 10, but it should be understood that network node 10 may have larger processing and storage resources, or more complex processing circuitry, suitable for potentially supporting a large number of wireless devices 12 at once.

[0064] More specifically, network node 10 according to one or more embodiments comprises one or more communication interfaces 30 including at least physical layer circuitry configured to transmit and receive signals - such as control signaling, data signals, etc. - for communicatively coupling network node 10 to one or more other entities. For example, communication interface 30 includes one or more network interfaces configured to communicate with other network nodes of the same or various types, and one or more wireless interfaces - such as wireless circuitry supporting downlink and uplink transmissions - for communicating with wireless devices 12, such circuitry including one or more wireless transmitters 32 and one or more wireless receivers 34.

[0065] Network node 10 further includes one or more types of processing circuitry 36 which, in one or more embodiments, includes or is associated with storage 38 including one or more types of memory circuitry or other computer-readable media. Processing circuitry 36 comprises one or more microprocessors or other digital processing circuitry specially adapted to operate as described herein based on execution of computer program instructions stored in storage 38 (e.g., CP(s) 40), such execution being configurable by or able to use one or more items of stored configuration data 42.

[0066] Another point of understanding regarding the processing circuitry in either or both of a network node and a wireless device is that the processing circuitry may be implemented or instantiated as one or "modules" or "processing units". Here, a module or processing unit is a functional or logical circuit realized via underlying physical processing resources. Of course, the processing circuitry of a network node may be realized using virtualization, meaning that its functionality may be instantiated in a virtualized processing environment that is itself realized on underlying physical processing resources.

[0067] The communication interface of network node 10 varies depending on its position within the communication network and its Operation responsibilities thereon. For example, network node 10 may be a "core network" (CN) node of the communication network, e.g., a specially configured server or other computing platform, and communicate indirectly with wireless device 12 via one or more intermediate nodes of the communication network, such as a wireless network node also referred to as an access node or base station.

[0068] In such a case, the communication interface(s) 30 of network node 10 according to an exemplary embodiment includes one or more computer data interfaces, such as one or more Ethernet interfaces, for communicating with one or more other nodes within the communication network. Such interfaces may be wired or wireless and generally include a receiver (RX) and transmitter (TX) circuit for receiving and transmitting signals on a physical medium, and a protocol processor for implementing the associated communication or signaling protocol.

[0069] In an implementation where network node 10 is a wireless network node that provides communication services to wireless device 12, the communication interface of network node 10 also includes a radio frequency transmitter and receiver for providing an air interface for communicating with wireless device 12. In an exemplary embodiment, network node 10 is configured to operate according to 3GPP specifications such as the 5th generation (5G) / New Radio (NR) specifications.

[0070] The communication interface 20 of wireless device 12 includes one or more radio frequency transmitters and receivers, such as a cellular broadband modem circuit. In one or more embodiments, the communication interface 20 of wireless device 12 includes any one or more of a Near Field Communication (NFC) circuit, a Bluetooth® or other personal area network circuit, a Wi-Fi® circuit, and a local wired communication interface for communicatively coupling with other devices. In an exemplary embodiment, wireless device 12 is configured to operate according to 3GPP specifications such as the 5G / NR specifications. Of course, the communication interface 20 of wireless device 12 can include a circuit that supports two or more Radio Access Technologies (RATs).

[0071] Figure 3 shows a method 300 executed by a UE with respect to a communication network. Method 300 includes receiving data in a UL transmission buffer of the UE while the UE is in an inactive mode (block 302), determining whether the data is restricted from transmission on CG-SDT resources (block 304), and starting a CG-SDT procedure in which at least a portion of the data is transmitted on CG-SDT resources in response to the data not being restricted (block 306).

[0072] After starting the CG-SDT procedure, method 300 may further include receiving additional data in the UL transmission buffer and performing a random access procedure for the purpose of transmitting a BSR in response to determining that the additional data is restricted. Determining whether the data is restricted may consist of, for example, determining whether the data belongs to a restricted DRB or a restricted LCH. As a more general example, determining whether the data is restricted comprises the UE determining whether the data is restricted from at least one of the perspectives of DRB association, LCH association, priority, or size.

[0073] Prior to receiving data into the UE's UL transmission buffer, method 300 may include the UE receiving a release message from the serving radio network node of the communication network in connection with the UE transitioning from the active mode to the inactive mode. The release message indicates criteria for determining data restrictions applicable to the UE with respect to CG-SDT resources. The release message may include, for example, an RRC release message. Determining whether the data is restricted may include, for example, determining whether the usage criteria for the CG-SDT resources are met. Determining whether the usage criteria for the CG-SDT resources are met may include the UE determining that, for example, the use of the CG-SDT procedure is possible on the relevant uplink (UL) carrier, which is a supplementary UL (SUL) carrier or a normal UL (NUL) carrier; the relevant timing advance timer (TAT) in the UE is in an active state; and the reference signal received power (RSRP) measured by the UE on the downlink reference signal received by the UE from the serving radio network node of the communication network exceeds a specified threshold.

[0074] In response to the criteria for using CG-SDT resources not being met, method 300 may further include that, in response to the criteria for random access SDT (RA-SDT) being met, the UE starts an RA-SDT procedure in which at least a part of the data is transmitted on RA-SDT resources. Here, the RA-SDT resources are the resources used by the UE for transmitting Msg3 or MsgA during the RA-SDT procedure. Determining whether the criteria for RA-SDT are met includes, for example, determining whether the data fits into the RA-SDT resources.

[0075] In at least one embodiment of method 300, in response to the criteria for RA-SDT not being met, method 300 includes that the UE starts an RA procedure without SDT to re-establish the connection mode with the communication network, and then transmits data in the connected mode. in

[0076] The CG-SDT resources, for example, recur periodically. In response to determining that data is restricted from being transmitted on the CG-SDT resources, method 300 may include that the UE selects either an RA SDT (RA-SDT) procedure or an RA procedure without SDT for transmitting the data based on at least one of the time until the next CG-SDT resource, the priority of the logical channel (LCH) or data radio bearer (DRB) associated with the data, or the size of the data.

[0077] Further details of the above method and its variations are shown in the "Embodiments of Group A" and "Embodiments of Group C" presented in the latter part of this disclosure.

[0078] ​An exemplary method 400 executed by network node 10 is shown in FIG. 4. The method 400 includes, at network node 10, generating a signaling message indicating a restriction for the UE to determine whether given data arriving subsequent to the UE's UL transmission buffer is restricted from transmission using the CG-SDT procedure (block 402); and transmitting the signaling message to the UE (block 404). The signaling message includes, for example, a release message transmitted to the UE as the UE transitions from a connected mode to an inactive mode. As a specific example, the release message includes an RRC release message. The restriction indicates, for example, one or more LCHs or DRBs for which related data is restricted from UL transmission using the CG-SDT procedure. In at least one embodiment, the network node 10 executing the method 400 is a radio network node operating as a serving radio network node with respect to the UE.

[0079] Details of the above method and its variations are shown in the "Embodiments of Group B" and "Embodiments of Group C" described later in this disclosure.

[0080] Any or all of the foregoing embodiments may be implemented in the context of a communication system, such as a communication system including an access node that transmits signaling to a UE as necessary to support the UE's use of CG SDT, taking into account or in accordance with the restriction of DRB or LCH. FIG. QQ1 shows an example of such a communication system QQ100 according to some embodiments.

[0081] In this example, the communication system QQ100 includes a communication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106 that includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may generally be referred to as network node QQ110), or other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. The network node QQ110 facilitates direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may sometimes generally be referred to as UE QQ112) to the core network QQ106 via one or more wireless connections.

[0082] Exemplary wireless communication via a wireless connection includes transmitting and / or receiving a wireless signal using electromagnetic waves, radio waves, infrared rays, and / or other types of signals suitable for transmitting information without using wires, cables, or other material conductors. Further, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that facilitate or may be involved in the communication of data and / or signals, whether via a wired connection or a wireless connection. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar types of systems.

[0083] UE Q112 may be any of a variety of communication devices, including a wireless device arranged, configured, and / or operable to wirelessly communicate with network node QQ110 and other communication devices. Similarly, network node QQ110 is arranged, enabled, configured, and / or operable to communicate directly or indirectly with UE Q112 and / or other network nodes or devices within telecommunication network QQ102 to enable and / or provide network access such as wireless network access and / or to perform other functions such as management within telecommunication network QQ102.

[0084] In the illustrated example, core network QQ106 connects network node QQ110 to one or more hosts such as host QQ116. These connections can be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. Core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) composed of hardware and software components. The functions of these components can be substantially similar to those described with respect to the UE, network node, and / or host, and thus the description of such components is generally applicable to the corresponding components of core network node QQ108. Exemplary core network nodes include one or more functions of a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscriber ID deconcealment function (SIDF), an integrated data management (UDM), a security edge protection proxy (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).

[0085] Host QQ116 is under the ownership or management of a service provider other than the operator or provider of access network QQ104 and / or telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. Host QQ116 can host various applications to provide one or more services. Examples of such applications include live and recorded audio / video content, data collection services such as acquiring and editing data on various ambient situations detected by multiple UEs, analytical functions, social media, functions to control or otherwise interact with remote devices, functions of alarm and monitoring centers, or any other such functions executed by the server.

[0086] Overall, communication system QQ100 of FIG. QQ1 enables connections between UEs, network nodes, and hosts. In that sense, the communication system can be configured to operate according to predefined rules or procedures, including but not limited to specific standards such as: Global System for Mobile Communications (GSM) for mobile communications, Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G), Wireless Local Area Network (WLAN) standards such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (Wi-Fi); and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMAX), Bluetooth (R), Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0087] In some examples, the telecommunications network QQ102 is a cellular network that implements 3GPP standardization functions. Thus, the telecommunications network QQ102 can support network slicing to provide different logical networks to different devices connected to the telecommunications network QQ102. For example, the telecommunications network QQ102 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs and / or massive machine type communication (mMTC) / massive IoT services to further UEs.

[0088] In some examples, the UE QQ112 is configured to transmit and / or receive information without direct human interaction. For example, the UE can be designed to transmit information to the access network QQ104 at a predetermined schedule when triggered by an internal or external event or in response to a request from the access network QQ104. Further, the UE can be configured to operate in single or multi-RAT or multi-standard mode. For example, the UE can be operated in any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multi-radio dual connection (MR-DC) such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio-Dual Connection (EN-DC).

[0089] In this example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UEs QQ112c and / or QQ112d) and a network node (e.g., network node QQ110b). In some examples, the hub QQ114 may be any of a controller, router, content source and analysis, or other communication device described herein with respect to the UE. For example, the hub QQ114 may be a broadband router that enables access to the core network QQ106 for the UE. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators within the UE. The commands or instructions may be received from the UE, network node QQ110, or executable code, script, process, or other instructions within the hub QQ114. As another example, the hub QQ114 may be a data collector that functions as a temporary storage for UE data, and in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, in the case of a UE that is a VR headset, display, loudspeaker, or other media delivery device, the hub QQ114 may obtain VR assets, video, audio, or other media or data related to sensory information via the network node, and then the hub QQ114 may provide it directly to the UE either after performing local processing and / or after adding additional local content. In yet another example, the hub QQ114 functions as a proxy server or orchestrator for the UE, particularly when one or more UEs are low-energy IoT devices.

[0090] Hub QQ114 can have a constant / persistent or intermittent connection to network node QQ110b. Hub QQ114 may also enable different communication methods and / or schedules between hub QQ114 and the UE (e.g., UE QQ112c and / or QQ112d), and between hub QQ114 and core network QQ106. In other examples, hub QQ114 is connected to core network QQ106 and / or one or more UEs via a wired connection. Further, hub QQ114 may be configured to connect to an M2M service provider via access network QQ104 and / or to another UE via a direct connection. In some scenarios, the UE can establish a wireless connection with network node QQ110 while remaining connected via hub QQ114 via a wired or wireless connection. In some embodiments, hub QQ114 may be a dedicated hub, i.e., a hub whose main function is to route communications between network node QQ110b and / or between the UE and network node QQ110b. In other embodiments, hub QQ114 may be a non-dedicated hub, i.e., a device that is operable to route communications between the UE and network node QQ110b but is additionally operable as a communication start point and / or communication end point for a specific data channel.

[0091] FIG. QQ2 shows a UE QQ200 according to some embodiments. As used herein, a UE refers to a device that is capable of wirelessly communicating with a network node and / or another UE, and is configured, arranged, and / or operable. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over Internet Protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), in-vehicle or in-vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communication (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0092] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standard specifications for sidelink communication, dedicated short range communication (DSRC), vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure communication (V2I), or vehicle-to-vehicle / vehicle-to-infrastructure communication (V2X). In other examples, the UE does not necessarily have to have a user in the sense of a human user who owns and / or operates the associated device. Instead, the UE may represent a device (e.g., a smart sprinkler control device) that is intended for sale to or operation by a human user but is not or may not initially be associated with a particular human user. Alternatively, the UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user but may be associated with a user or operated for the benefit of a user.

[0093] UE QQ200 includes A processing circuit QQ20 operably connected via a bus QQ204 to an input / output interface QQ206, a power supply QQ208, a memory QQ210, a communication interface QQ212, and / or any other components, or any combination thereof is Specific UEs can utilize all or a subset of the components shown in FIG. QQ2. The level of integration between components can vary from UE to UE. Further, a specific UE can include multiple instances of components such as multiple processors, memories, transceivers, transmitters, receivers, etc. configured can include.

[0094] The processing circuit QQ202 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in the memory QQ210. The processing circuit QQ202 can be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field programmable gate array (FPGA), application specific integrated circuit (ASIC), etc.), programmable logic with appropriate firmware, one or more stored computer programs, a general-purpose processor such as a microprocessor or a digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit QQ202 can include multiple central processing units (CPUs).

[0095] In this embodiment, the input / output interface QQ206 may be configured to provide an interface to an input device, an output device, or one or more input devices and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. An input device may enable a user to capture information into the UE QQ200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, scroll wheels, smart cards, and the like. A presence-sensitive display may include a capacitive touch sensor or a resistive film touch sensor for sensing input from a user. The sensor may be, for example, an acceleration sensor, a gyroscope, an inclination sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biosensor, or any combination thereof. The output device may use the same type of interface port as the input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0096] In some embodiments, the power supply QQ208 is configured as a battery or a battery pack. Other types of power supplies such as an external power supply (e.g., an electrical outlet), a photovoltaic device, or a power cell may be used. The power supply QQ208 may further include a power circuit for supplying power from the power supply QQ208 itself and / or an external power supply to various parts of the UE QQ200 via an interface such as an input circuit or a power cable. The power supply may be, for example, for charging the power supply QQ208. The power circuit may perform any formatting, conversion, or other modification of the power from the power supply QQ208 to make it suitable power for each component of the UE QQ200 to which power is supplied.

[0097] Memory QQ210 can be, or can be configured to include, memories such as random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, etc. In one example, memory QQ210 includes one or more application programs QQ214, such as an operating system, a web browser application, widgets, a gadget engine, or other applications, and corresponding data QQ216. Memory QQ210 can store any one, or a combination of operating systems, for use by UE QQ200. to provide functionality of a network node QQ300 either alone or in cooperation with components of other network nodes QQ300 such as a memory QQ304,

[0098] ​Memory QQ210 can be configured to include a number of physical drive units, such as redundant array of inexpensive disks (RAID), flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high density digital versatile disc (HD-DVD) optical disc drives, internal hard disk drives, Blu-ray optical disc drives, holographic digital data storage (HDDS) optical disc drives, external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, one or more subscriber identity modules (SIMs) such as USIM and / or ISIM in the form of a universal integrated circuit card (UICC) including a tamper resistant module such as a smart card memory, other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". With the memory QQ210, the UE QQ200 can access instructions, application programs, etc. stored in a temporary or non-temporary memory medium, offload data, or upload data. A manufactured product such as one that utilizes a communication system may be embodied as the memory QQ210 or within the memory QQ210, which may be a device-readable storage medium or may be composed of a device-readable storage medium.

[0099] The processing circuit QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may include one or more communication subsystems, may include the antenna QQ222, or may be communicatively coupled to the antenna QQ222. The communication interface QQ212 may include one or more transceivers used for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node within an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Further, the transmitter QQ218 and the receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software, or firmware, or may be implemented separately.

[0100] In the illustrated embodiment, the communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, proximity communication, location-based communication such as the use of the Global Positioning System (GPS) for determining location, another similar communication function, or any combination thereof. The communication may be implemented according to one or more communication protocols and / or standards such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA (registered trademark)), GSM, LTE, New Radio (NR), UMTS, WiMAX, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP).

[0101] Regardless of the type of sensor, the UE can provide, via its communication interface QQ212, the output of data acquired by the sensor to a network node via a wireless connection. Data acquired by the sensors of the UE can be communicated to the network node via a wireless connection, through another UE. The output can be periodic (e.g., once every 15 minutes when reporting the sensed temperature), random (e.g., to equalize the load from reports from multiple sensors), in response to a trigger event (e.g., an alert is sent when moisture is detected), in response to a request (e.g., a request initiated by the user), or a continuous stream (e.g., a live video feed of a patient).

[0102] As another example, the UE is associated with a communication interface configured to receive a wireless input from a network node via a wireless connection and is composed of an actuator, a motor, or a switch. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can constitute a motor that adjusts the control surfaces or rotors of a drone in flight in response to the received input, or a robotic arm that performs a medical procedure in response to the received input.

[0103] When the UE is in the form of an Internet of Things (IoT) device, it can be a device for use in one or more application areas, which may include, but are not limited to, urban wearable technologies, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include devices such as: connected refrigerators or freezers, televisions, connected lighting fixtures, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion sensors, thermostats, smoke detectors, door / window sensors, flood / moisture sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable for tactile or sensory augmentation, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and all kinds of medical devices such as heart rate monitors and remote surgical robots. The UE in the form of an IoT device is equipped with circuits and / or software according to the intended use of the IoT device, in addition to other components as described in relation to UE QQ200 shown in FIG. QQ2.

[0104] As yet another specific example, in an IoT scenario, the UE can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device and may be referred to as an MTC device in the context of 3GPP. As a specific example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, the UE can represent vehicles such as cars, buses, trucks, ships, and aircraft, or other devices that can monitor and / or report on their operating status or other functions related to their operation.

[0105] In practice, any number of UEs can be used together for a single use case. For example, a first UE can be a drone or integrated into a drone and provide speed information of the drone (obtained via a speed sensor) to a second UE that is a remote controller for operating the drone. When the user makes a change from the remote controller, the first UE can adjust the throttle of the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first UE and / or the second UE can include one or more of the functions described above. For example, a UE can be equipped with sensors and actuators and can handle the communication of data from both the speed sensor and the actuator.

[0106] Figure QQ3 shows a network node QQ300 according to some embodiments. As used herein, a network node refers to a device that can communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network and is configured, arranged, and / or operable. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., wireless base stations, Node B, evolved Node B (eNB), NR Node B (gNB)).

[0107] Base stations can be classified based on the amount of coverage provided (or, put another way, the transmission power level), and thus may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations depending on the amount of coverage provided. The base station may be a relay node or a relay donor node that controls the relay. The network node may also include one or more (or all) parts of a distributed radio base station such as a centralized digital unit and / or a remote radio unit (RRU), sometimes called a remote radio head (RRH). Such a remote radio unit may or may not be integrated with the antenna as an antenna-integrated radio. A part of the distributed radio base station may also be called a node of a distributed antenna system (DAS).

[0108] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNS) and base station controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile location center (E-SMLC), etc.), and / or minimization of drive tests (MDT).

[0109] The network node QQ300 includes a processing circuit QQ302, a memory QQ304, a communication interface QQ306, and a power supply QQ308. The network node QQ300 may be composed of a plurality of physically separated components (such as a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), and each may have its own components. In a specific scenario where the network node QQ300 includes a plurality of distinct components (such as BTS and BSC components), one or more of the distinct components may be shared among network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique pair of NodeB and RNC may, in some cases, be regarded as a single distinct network node. In some embodiments, the network node QQ300 may be configured to support a plurality of radio access technologies (RATs). In such embodiments, some components may overlap (such as separate memories QQ304 for different RATs), and some components may be reused (such as the same antenna QQ310 being shared by different RATs). The network node QQ300 may also include a plurality of sets of various illustrated components for different wireless technologies integrated into the network node QQ300, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID (Radio Frequency Identification), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same chip or different chip sets within the network node QQ300, as well as other components.

[0110] The processing circuit QQ302 is operable , a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field programmable gate array toOne or more of any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic that are possible can be included.

[0111] In some embodiments, processing circuit QQ302 includes a system-on-chip (SOC). In some embodiments, processing circuit QQ302 includes one or more of a radio frequency (RF) transceiver circuit QQ312 and a baseband processing circuit QQ314. In some embodiments, the radio frequency (RF) transceiver circuit QQ312 and the baseband processing circuit QQ314 can be on separate chips (or sets of chips), substrates, or units such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 can be on the same chip or chip set, substrate, or unit.

[0112] Memory QQ304 can be any form of volatile or non-volatile computer-readable memory, including, but not limited to, a persistent storage device, solid-state memory, remote mount memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that can store information, data, and / or instructions used by processing circuit QQ302. Memory QQ304 can store any appropriate instructions, data, or information, including an application that includes one or more of a computer program, software, logic, rules, code, tables, and / or other instructions that can be executed by processing circuit QQ302 and utilized by network node QQ300. Memory QQ304 can be used to store any operations performed by processing circuit QQ302 and / or any data received via communication interface QQ306. In some embodiments, processing circuit QQ302 and memory QQ304 are integrated.

[0113] The communication interface QQ306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface QQ306 comprises ports / terminals QQ316 for transmitting and receiving data to and from a network, for example via a wired connection. The communication interface QQ306 may also include a radio front-end circuit QQ318 that can be coupled to antenna QQ310 or, in certain embodiments, can be part of antenna QQ310. The radio front-end circuit QQ318 comprises a filter QQ320 and an amplifier QQ322. The radio front-end circuit QQ318 may be connected to antenna QQ310 and processing circuit QQ302. The radio front-end circuit may be configured to condition signals communicated between antenna QQ310 and processing circuit QQ302. The radio front-end circuit QQ318 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. The radio front-end circuit QQ318 may use a combination of filter QQ320 and / or amplifier QQ322 to convert the digital data into a radio signal having appropriate channel and bandwidth parameters. The radio signal is then transmitted via antenna QQ310. Similarly, when receiving data, antenna QQ310 collects the radio signal, which is converted into digital data by radio front-end circuit QQ318. The digital data may be passed to processing circuit QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0114] In some alternative embodiments, the network node QQ300 does not include a separate radio front-end circuit QQ318. Instead, the processing circuit QQ302 includes a radio front-end circuit and is connected to the antenna QQ310. Similarly, in some embodiments, all or part of the RF transceiver circuit QQ312 is part of the communication interface QQ306. Further, in other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, a radio front-end circuit QQ318, and an RF transceiver circuit QQ312 as part of a wireless unit (not shown), and the communication interface QQ306 communicates with a baseband processing circuit QQ314 that is part of a digital unit (not shown).

[0115] The antenna QQ310 may include one or more antennas, or an antenna array, configured to transmit and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuit QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and is connectable to the network node QQ300 via an interface or port.

[0116] The antenna QQ310, the communication interface QQ306, and / or the processing circuit QQ302 may be configured to perform any of the receive operations and / or certain acquisition operations described herein as being performed by a network node. Any information, data, and / or signal may be received from a UE, another network node, and / or any other network device. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuit QQ302 may be configured to perform any of the transmit operations described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a UE, another network node, and / or any other network device.

[0117] Power supply QQ308 supplies power to various components of network node QQ300 in a form suitable for each component (e.g., at the voltage and current levels required for each component). The power supply QQ308 may further comprise, or be coupled to, a power management circuit for supplying power to the components of the network node QQ300 for performing the functions described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to the power circuit of the power supply QQ308. As a further example, the power supply QQ308 may be composed of a power source in the form of a battery or a battery pack that is connected to or incorporated into the power circuit. The battery can provide backup power in the event of a failure of the external power source.

[0118] Embodiments of the network node QQ300 may include additional components other than those shown in FIG. QQ3 to provide certain aspects of the functionality of a network node, including any of the functions described herein and / or functions necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface devices that enable the input of information to the network node QQ300 and the output of information from the network node QQ300. Thereby, a user can perform diagnostic, maintenance, repair, and other management functions of the network node QQ300.

[0119] FIG. QQ4 is a block diagram of a host QQ400 that can be an embodiment of the host QQ116 of FIG. QQ1 according to various aspects described herein. As used herein, the host QQ400 can be or comprise various combinations of hardware and / or software, including a stand-alone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources within a server farm. The host QQ400 can provide one or more services to one or more UEs.

[0120] The host QQ400 includes a processing circuit QQ402 operably coupled to an input / output interface QQ406, a network interface QQ408, a power supply QQ410, and a memory QQ412 via a bus QQ404. In other embodiments, other components may be included. The features of these components may be substantially similar to those described for the devices in previous figures such as FIGS. QQ2 and QQ3, and in such cases, that description is generally applicable to the corresponding components of the host QQ400.

[0121] Memory QQ412 can include one or more computer programs including one or more host application programs QQ414 and data QQ416, and the data QQ416 can include user data, for example, data generated by the UE for the host QQ400 or data generated by the host QQ400 for the UE. Embodiments of the host QQ400 can utilize only a subset or all of the shown components. The host application program QQ414 can be implemented in a container-based architecture and can provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (such as mobile terminals, desktop computers, wearable display systems, head-up display systems, etc.). The host application program QQ414 can also provide user authentication and license checking and can periodically report the health, path, and content availability to a central node such as a device within the core network or at the edge of the core network. Thus, the host QQ400 can select and / or direct different hosts for the user top services of the UE. The host application program QQ414 can support various protocols such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH).

[0122] FIG. QQ5 is a block diagram showing a virtualization environment QQ500 in which functions implemented by some embodiments can be virtualized. As used herein, virtualization means creating a virtual version of a device or apparatus, which may include virtualizing a hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to any device or its components described herein, and relates to implementations in which at least some of the functions are implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) hosted by one or more virtual environments QQ500 implemented on one or more hardware nodes such as a hardware computing device operating as a network node, UE, core network node, or host. Further, in embodiments where the virtual node does not require a wireless connection (e.g., a core network node or host), the node can be fully virtualized.

[0123] Application QQ502 (alternatively, may also be referred to as a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) is executed in the virtualization environment Q400 to implement some of the features, functions, and / or advantages of some of the embodiments disclosed herein.

[0124] Hardware QQ504 includes a processing circuit, a memory storing software and / or instructions executable by the hardware processing circuit, and / or other hardware devices described herein, such as a network interface, an input / output interface. The software is executed by the processing circuit to instantiate one or more virtualization layers QQ506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs QQ508a and QQ508b (one or more of which can generally be referred to as VM QQ508), and / or perform any of the functions, features, and / or advantages described in connection with several embodiments herein. The virtualization layer QQ506 can present a virtual operating platform that appears to the VMs QQ508 as network hardware.

[0125] VM QQ508 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be executed by the corresponding virtualization layer QQ506. Different embodiments of instances of the virtual appliance QQ502 may be implemented on one or more of the VMs QQ508, and the implementation may be done in different ways. Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to integrate many types of network equipment into industry-standard high-volume server hardware, physical switches, physical storage, and customer premise equipment that can be located in a data center.

[0126] In the context of NFV, VM QQ508 can be a software implementation of a physical machine that executes programs as if they were running on a physical, non-virtualized machine. Each of VMQ508, and a part of the hardware QQ504 that runs that VM, is either hardware dedicated to that VM and / or hardware shared by that VM with other VMs, forming separate virtual network elements. Still, in the context of NFV, the virtual network functions are executed on one or more VMs QQ508 on the hardware QQ504 and serve to process specific network functions corresponding to the application QQ502.

[0127] Hardware QQ504 can be implemented as a stand-alone network node with general-purpose or specific components. Hardware QQ504 may implement some functions by virtualization. Alternatively, hardware QQ504 may be part of a larger hardware cluster (such as a data center or CPE, etc.) where many hardware nodes cooperate and are managed via a management and orchestration QQ510 that particularly oversees the life cycle management of the application QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units each including one or more receivers that can be coupled to one or more transmitters and one or more antennas. The radio units can communicate directly with other hardware nodes via one or more appropriate network interfaces and can be used in combination with virtual components to provide virtual nodes with radio functions such as radio access nodes or base stations. In some embodiments, some signaling can be provided by the use of a control system QQ512 that can alternatively be used for communication between the hardware node and the radio unit.

[0128] Figure QQ6 shows a communication diagram of host QQ602 communicating partially via a wireless connection with UE QQ606 via network node QQ604, according to some embodiments. Next, exemplary implementations according to various embodiments of the UE (such as UE QQ112a in Figure QQ1 and / or UE QQ200 in Figure QQ2), network node (such as network node QQ110a in Figure QQ1 and / or network node QQ300 in Figure QQ3), and host (such as host QQ116 in Figure QQ1 and / or host QQ400 in Figure QQ4) will be described with reference to Figure QQ6.

[0129] Similar to host QQ400, embodiments of host QQ602 include hardware such as a communication interface, processing circuitry, and memory. Host QQ602 also includes software stored on or accessible by host QQ602 and executable by the processing circuitry. This software may include a host application operable to provide services to remote users such as UE QQ606 connected via an over-the-top (OTT) connection QQ650 extending between UE QQ606 and host QQ602. When providing services to a remote user, the host application may be able to provide user data transmitted using OTT connection QQ650.

[0130] Network node QQ604 includes hardware that enables communication with host QQ602 and UE QQ606. Connection QQ660 may be direct or via a core network (such as core network QQ106 in Figure QQ1) and / or one or more other intermediate networks (such as one or more public, private, or hosted networks). For example, the intermediate network may be a backbone network or the Internet.

[0131] UE QQ606 includes hardware and software that is stored in or accessible by UE QQ606 and executable by the processing circuitry of the UE. The software can include client applications such as a web browser or an operator-specific "app" that, with the support of host QQ602, can be operable to provide services to a human or non-human user via UE QQ606. In host QQ602, a running host application can communicate with a running client application via an OTT connection QQ650 that terminates at UE QQ606 and host QQ602. When providing services to a user, a client application of the UE can receive request data from a host application of the host and can provide user data in response to the request data. The OTT connection QQ650 can transfer both request data and user data. A client application of the UE can interact with the user to generate user data to provide to the host application via the OTT connection QQ650.

[0132] The OTT connection QQ650 can extend via a connection QQ660 between host QQ602 and network node QQ604 and via a wireless connection QQ670 between network node QQ604 and UE QQ606 to provide a connection between host QQ602 and UE QQ606. The connection QQ660 and wireless connection QQ670 through which the OTT connection QQ650 can be provided are abstractly depicted to illustrate communication between host QQ602 and UE QQ606 via network node QQ604 and do not explicitly refer to intermediary devices and the exact routing of messages through these devices.

[0133] As an example of sending data via the OTT connection QQ650, at step QQ608, the host QQ602 provides user data that can be executed by running a host application. In some embodiments, the user data is associated with a particular human user who interacts with the UE QQ606. In other embodiments, the user data is associated with the UE QQ606 that shares data with the host QQ602 without explicit human interaction. At step QQ610, the host QQ602 initiates a transmission to convey the user data towards the UE QQ606. The host QQ602 can initiate the transmission in response to a request sent by the UE QQ606. The request can be caused by human interaction with the UE QQ606 or by an operation of a client application running on the UE QQ606. The transmission can pass through the network node QQ604 according to the teachings of the embodiments described throughout this disclosure. Thus, at step QQ612, the network node QQ604 transmits the user data conveyed in the transmission initiated by the host QQ602 to the UE QQ606 according to the teachings of the embodiments described throughout this disclosure. At step QQ614, the UE QQ606 receives the user data conveyed by the transmission, which can be executed by a client application running on the UE QQ606 and associated with the host application executed by the host QQ602.

[0134] In some examples, UE QQ606 runs a client application that provides user data to host QQ602. The user data may be provided as a reaction or response to data received from host QQ602. Thus, at step QQ616, UE QQ606 can provide user data that can be executed by running the client application. When providing the user data, the client application may further consider user input received from the user via the input / output interface of UE QQ606. Regardless of the particular way the user data is provided, at step QQ618, UE QQ606 begins transmitting the user data towards host QQ602 via network node QQ604. At step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, network node QQ604 receives the user data from UE QQ606 and begins transmitting the received user data towards host QQ602. At step QQ622, host QQ602 receives the user data carried in the transmission initiated by UE QQ606.

[0135] One or more of various embodiments use OTT connection QQ650 in which wireless connection QQ670 forms the last segment to improve the performance of the OTT service provided to UE QQ606. More precisely, the teachings of these embodiments can improve any one or more of data latency, responsiveness, battery life in the UE, and determinism in the operation of the UE regarding the execution of the CG-SDT procedure.

[0136] As an exemplary scenario, factory status information can be collected and analyzed by host QQ602. As another example, host QQ602 can process audio and video data that can be obtained from a UE for use in creating a map. As another example, host QQ602 can collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic signals). As another example, host QQ602 can store surveillance videos uploaded by a UE. As another example, host QQ602 can control the storage or access of media content such as video, audio, VR, or AR that can be broadcast, multicast, or unicast to a UE. As another example, host QQ602 can be used for energy price setting, remote control of important electrical loads independent of time to balance power generation needs, location information services, presentation services (such as editing diagrams from data collected from remote devices), or other functions of data collection, search, storage, analysis, and / or transmission.

[0137] In some examples, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that are improved in one or more embodiments. Additionally, there may be optional network functions for reconfiguring the OTT connection QQ650 between the host QQ602 and the UE QQ606 in response to variations in the measurement results. The measurement procedures and / or the network functions for reconfiguring the OTT connection may be implemented in the software and hardware of the host QQ602 and / or the UE QQ606. In some embodiments, a sensor (not shown) may be disposed on or associated with other devices through which the OTT connection QQ650 passes, and the sensor may participate in the measurement procedure by providing values of the monitoring quantities exemplified above, or by providing values of other physical quantities from which software can calculate or estimate the monitoring quantities. The reconfiguration of the OTT connection QQ650 can include message format, retransmission settings, priority routing, etc., and the reconfiguration does not necessarily directly change the operation of the network node QQ604. Such procedures and functionality are known in the art and may be implemented. In certain embodiments, the measurement may include unique UE signaling that facilitates measurement of throughput, propagation time, latency, etc. by the host QQ602. The measurement can be implemented such that software causes messages, particularly empty messages or "dummy" messages, to be transmitted using the OTT connection QQ650 while monitoring propagation time, errors, etc.

[0138] The computing devices (e.g., UEs, network nodes, hosts) described in this specification may include the illustrated combinations of hardware components, but other embodiments may include computing devices having different combinations of components. It should be understood that these computing devices may be composed of any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods disclosed herein. The determinations, calculations, acquisitions, or similar operations described herein may be performed by a processing circuit, which may, for example, convert acquired information into other information, compare the acquired information or the converted information with information stored in a network node, and / or process the information by performing one or more operations based on the acquired information or the converted information, and make a determination as a result of the processing. Further, although the components are depicted as a single box placed within a larger box or as boxes nested within multiple boxes, in reality, a computing device may comprise multiple different physical components that make up a single illustrated component, and the functions may be divided among separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functions of the components may be divided between a processing circuit and a communication interface. In another example, non-computation-intensive functions of any of such components may be implemented in software or firmware, and computation-intensive functions may be implemented in hardware.

[0139] In certain embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored in a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether or not executing instructions stored in a non-transitory computer-readable storage medium, the processing circuit may be configured to perform the described functions. The advantages provided by such functionality are not limited to the processing circuit alone or to other components of a computing device, but are enjoyed by the computing device as a whole and / or by the end user and the wireless network in general.

[0140] Further exemplary embodiments Embodiments of Group A 1. A method performed by a user equipment (UE) with respect to a communication network, the method comprising: controlling execution of a configured grant small data transmission (CG-SDT) procedure by the UE according to whether data to be transmitted is restricted from transmission on a CG-SDT resource. 2. The method of embodiment 1, further comprising determining whether the data is restricted by determining whether the data belongs to a restricted data radio bearer (DRB) or a restricted logical channel (LCH). 3. The method of embodiment 1 or 2, wherein the data includes all or part of the uplink (UL) data available at the UE, and controlling the execution of the CG-SDT procedure includes determining that at least a portion of the available UL data is restricted in connection with starting the CG-SDT procedure. 4. Controlling the execution of the CG-SDT procedure includes not using the CG-SDT procedure to transmit the available UL data in response to determining that at least a part of the available UL data is restricted, according to the method described in Embodiment 3. 5. Controlling the execution of the CG-SDT procedure includes selecting the CG-SDT procedure for transmitting the data according to the following, according to the method described in any one of Embodiments 1 to 4: Use of a CG-SDT procedure available on a related uplink (UL) carrier that can be an SUL or NUL carrier, A related timing advance timer (TAT) in an execution state, and The reference signal received power (RSRP) measured by the UE on a downlink reference signal transmitted by a serving radio network node of the communication network exceeding a specified threshold. 6. Controlling the execution of the CG-SDT procedure includes transmitting the data on the CG-SDT resource in response to the data not being restricted, or not transmitting the data on the CG-SDT resource in response to the data being restricted, according to the method described in any one of Embodiments 1 to 5. 7. Controlling the execution of the CG-SDT procedure includes not executing the CG-SDT procedure and instead executing a random access (RA) procedure in response to determining that the data is restricted. Msg3 or MsgA of the RA procedure includes a UE identifier and at least a part of the above, according to the method described in any one of Embodiments 1 to 6. data 8. Controlling the execution of the CG-SDT procedure includes the UE transmitting a buffer status report (BSR) of the data on a CG-SDT resource in response to the data being restricted and arriving at the uplink (UL) transmission buffer of the UE after the start of the CG-SDT procedure, according to the method described in any one of Embodiments 1 to 7. 9. Controlling the execution of the CG-SDT procedure includes, when the UE determines that the data is restricted, the method according to any one of Embodiments 1 to 8, including: Selecting either a first approach or a second approach depending on at least one of the following items The time to the next CG-SDT resource The priority of the LCH or DRB related to the data, or The amount of the data Here, the first approach consists of starting a random access (RA) procedure instead of the CG-SDT procedure The Msg3 or MsgA of the RA procedure includes a UE identifier and at least a part of the data. The second approach consists of transmitting a buffer status report (BSR) of the data on a CG-SDT resource. 10. The method according to Embodiment 9, including that the UE selects the second approach in response to the time to the next CG-SDT resource being less than a threshold. 11. The method according to Embodiment 9, including that the UE selects the first approach according to the conformity of the data in the Msg3 or MsgA used in the RA procedure. 12. The method according to any one of Embodiments 1 to 11, further including receiving an instruction of restriction via signaling from a radio network node of the communication network, where the instruction indicates a DRB or LCH that can or cannot use a CG-SDT resource. 13. The method according to Embodiment 12, where the signaling includes an RRC release message, and "RRC" indicates radio resource control. 14. The method according to any one of Embodiments 1 to 13, where the UE is configured to operate according to 3rd Generation Partnership Project (3GPP) specifications. 15. The method according to any one of the previous embodiments, further including: Providing user data, and Transferring the user data to a host via transmission to the network node

[0141] Embodiments of Group B 16. A method performed by a network node of a communication network, the method comprising: Generating a signaling message comprising an indication of one or more restrictions corresponding to one or more logical channels (LCHs) or data radio bearers (DRBs), wherein the restrictions mean that uplink data of a user equipment (UE) associated with the one or more LCHs or DRBs is restricted from being transmitted on configured grant small data transmission (CG-SDT) resources; Transmitting the signaling message to the UE; A method comprising. 17. The method according to embodiment 16, wherein the signaling message comprises an RRC release message, and "RRC" indicates radio resource control. 18. The method according to embodiment 16 or 17, wherein the network node is a radio network node. 19. The method according to any one of embodiments 16 to 18, wherein the network node operates according to 3rd Generation Partnership Project (3GPP) specifications. 20. The method according to any of the previous embodiments, further comprising the following steps: User data by Obtaining, and Transferring the user data to a host or a user equipment.

[0142] Embodiments of Group C 21. A processing circuit configured to perform any of the steps of the embodiments of Group A, and any A power supply circuit configured to supply power to the processing circuit, A user equipment (UE) comprising. A user equipment (UE) comprising. 22. Of the Group B anyA processing circuit configured to execute any step of the embodiments, A power supply circuit configured to supply power to the processing circuit, A network node including the above. 23. An antenna configured to transmit and receive wireless signals, A radio front-end circuit connected to the antenna and the processing circuit and configured to adjust signals communicated between the antenna and the processing circuit, The processing circuit is configured to execute any step of the embodiments of Group A, any An input interface connected to the processing circuit and configured to enable input of information processed by the processing circuit to a UE, An output interface connected to the processing circuit and configured to output information from the UE processed by the processing circuit, A battery connected to the processing circuit and configured to supply power to the UE, A user equipment (UE) including the above. 24. A host configured to operate in a communication system to provide an over-the-top (OTT) service, A processing circuit configured to provide user data, A network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), including the above, Here, the UE includes a communication interface and a processing circuit, and the communication interface and the processing circuit of the UE are configured to execute any step of the embodiments of Group A to receive the user data from the host, any A host configured as above. 25. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the host to the UE. ​​26. The processing circuit of the host is configured to execute a host application, thereby providing the user data, and the host application is configured to interact with a client application executed on the UE, and the client application is associated with the host application, The host according to the previous two embodiments. 27. A method implemented by a host operating in a communication system further including a network node and a user equipment (UE), providing user data to the UE; and initiating a transmission to carry the user data to the UE via a cellular network including the network node, wherein the UE performs any of the operations of the embodiments of Group A any to receive the user data from the host, A method comprising: 28. The method according to the previous embodiment, executing, in the host, a host application associated with a client application running on the UE to receive the user data from the UE; being further including. 29. The method according to the previous embodiment, transmitting input data to the client application running on the UE in the host, further including, wherein the user data is provided by the client application in response to the input data from the host application, A method. 30. A host configured to operate in a communication system to provide an over-the-top (OTT) service, a processing circuit configured to provide user data; and A network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE). Here, the UE comprises a communication interface and a processing circuit, and the communication interface and processing circuit of the UE are configured to execute any of the steps of the embodiments of Group A to transmit the user data to the host. any A host. 31. The host according to the previous embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to transmit the user data from the UE to the host. 32. The processing circuit of the host is configured to execute a host application, thereby providing the user data, and the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application. The host according to the previous two embodiments. 33. A method implemented by a host configured to operate in a communication system further comprising a network node and a user equipment (UE), the method comprising: receiving, at the host, the user data transmitted to the host by the UE via the network node, wherein the UE is configured to execute any of the steps of the embodiments of Group A to transmit the user data to the host. any Including. A method. 34. The method according to the previous embodiment, further comprising: executing, at the host, a host application associated with a client application running on the UE to receive the user data from the UE. A method further comprising. 35. The method according to the previous embodiment, further comprising: On the host, to a client application executed on the UE executing and provided by a host application further including transmitting input data, wherein the user data is provided by the client application according to the input data from the host application, Method. 36. A host configured to operate in a communication system to provide an over-the-top (OTT) service, a processing circuit configured to provide user data, a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and a processing circuit, and the processing circuit of the network node being configured to perform operations of any of the embodiments of Group B any to transmit the user data from the host to the UE, the network interface; Host, including. 37. The host according to the previous embodiment, wherein the processing circuit of the host is configured to execute a host application that provides the user data, the UE includes a processing circuit configured to execute a client application associated with the host application to receive transmission of the user data from the host, Host. 38. A method implemented on a host configured to operate in a communication system further including a network node and a user equipment (UE), providing user data to the UE; initiating a transmission to carry the user data to the UE via a cellular network including a network node, the network node being configured to perform operations of any of the embodiments of Group B anyPerforming any of the operations of the embodiments, A method comprising. 39. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE. 40. The method according to any of the previous two embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application running on the UE, and the client application is associated with the host application. 41. A communication system configured to provide an over-the-top service, A processing circuit configured to provide user data to a user equipment (UE), the user data being related to the over-the-top service, and a processing circuit, A network interface configured to initiate transmission of the user data towards a cellular network node for transmission to the UE, the network node having a communication interface and a processing circuit, and the processing circuit of the network node being configured to perform any of the operations of the any Embodiments of Group B for transmitting the user data from the host to the UE, and a network interface, a host comprising. A communication system comprising. 42. The communication system of the previous embodiment, further comprising The network node and The user equipment and A communication system comprising. 43. A host configured to operate in a communication system to provide an over-the-top (OTT) service, A processing circuit configured to initiate reception of user data, and A network interface configured to receive the user data from a network node within a cellular network, wherein the network node has a communication interface and a processing circuit, and the processing circuit of the network node is for the group B to receive the user data from a user equipment (UE) for the host any A network interface configured to perform any operation of any of the embodiments; A host comprising the above. 44. The host according to the previous two embodiments, wherein the processing circuit of the host is configured to execute a host application, thereby providing user data; the host application is configured to interact with the client application executed on the UE, and the client application is associated with the host application; A host. 45. The host according to any of the previous two embodiments, wherein starting to receive the user data consists of requesting the user data. 46. A method implemented by a host configured to operate in a communication system further including a network node and a user equipment (UE), wherein in the host, starting to receive user data from the UE, wherein the user data is derived from a transmission received by the network node from the UE, and the network node is for the group B to receive the user data from the UE for the host any performing any step of any of the embodiments; A method comprising the above. 47. The method of the previous embodiment, further comprising, in the network node, transmitting the received user data to the host.

[0143] Abbreviations In the present disclosure, at least some of the following abbreviations can be used. If there are contradictions between the abbreviations, the above usage method shall take precedence. If described multiple times below, the first description shall take precedence over subsequent descriptions. 1x RTT CDMA2000 1x Radio Transmission Technology (CDMA2000 1x radio transmission technology) 3GPP 3rd Generation Partnership Project (3rd Generation Partnership Project) 5G 5th Generation (5th Generation) 6G 6th Generation (6th Generation) ABS Almost Blank Subframe (almost blank subframe) ARQ Automatic Repeat Request (automatic repeat request) AQGN Additive White Gaussian Noise (additive white Gaussian noise) BCCH Broadcast Control Channel (broadcast control channel) BCH Broadcast Channel (broadcast channel) BSR Buffer Status Report (buffer status report) CA Carrier Aggregation (carrier aggregation) CC Carrier Component (carrier component) CCCH SDU Common Control Channel SDU (common control channel SDU) CDMA Code Division Multiplexing Access (code division multiplexing access) CG Configured Grant (configured grant) CGI Cell Global Identifier (cell global identifier) CIR Channel Impulse Response (Channel Impulse Response) CP Cyclic Prefix (Cyclic Prefix) CPICH Common Pilot Channel (Common Pilot Channel) CPICH Ec / No CPICH Received energy per chip divided by the power density in the band (Received energy per chip divided by the power density in the band) CQI Channel Quality information (Channel Quality Information) C-RNTI Cell RNTI (Cell RNTI) CSI Channel State Information (Channel State Information) DCCH Dedicated Control Channel (Dedicated Control Channel) DL Downlink (Downlink) DM Demodulation (Demodulation) DMRS Demodulation Reference Signal (Demodulation Reference Signal) DRB Data Radio Bearer (Data Radio Bearer) DRX Discontinuous Reception (Discontinuous Reception) DTX Discontinuous Transmission (Discontinuous Transmission) DTCH Dedicated Traffic Channel (Dedicated Traffic Channel) DUT Device Under Test (Device Under Test) E-CID Enhanced Cell-ID (positioning method) (Enhanced Cell-ID (positioning method)) eMBMS evolved Multimedia Broadcast Multicast Services (Evolved Multimedia Broadcast Multicast Services) E-SMLC Evolved-Serving Mobile Location Centre (Evolved Serving Mobile Location Center) ECGI Evolved CGI (Evolved CGI) eNB E-UTRAN NodeB (E-UTRAN Node B) ePDCCH Enhanced Physical Downlink Control Channel (Enhanced Physical Downlink Control Channel) E-SMLC Evolved Serving Mobile Location Center (Evolved Serving Mobile Location Center) E-UTRA Evolved UTRA (Evolved UTRA) E-UTRAN Evolved UTRAN (Evolved UTRAN) FDD Frequency Division Duplex (Frequency Division Duplex) FFS For Further Study (For Further Study) gNB Base station in NR (Base station in NR) GNSS Global Navigation Satellite System (Global Navigation Satellite System) HARQ Hybrid Automatic Repeat Request (Hybrid Automatic Repeat Request) HO Handover (Handover) HSPA High Speed Packet Access (High Speed Packet Access) HRPD High Rate Packet Data (High Rate Packet Data) LCH Logical Channel (Logical Channel) LOS Line of Sight (Line of Sight) LPP LTE Positioning Protocol (LTE Positioning Protocol) LTE Long-Term Evolution (Long-Term Evolution) MAC Medium Access Control (Medium Access Control) MAC Message Authentication Code (Message Authentication Code) MBSFN Multimedia Broadcast multicast service Single Frequency Network (Multimedia Broadcast Multicast Service Single Frequency Network) MBSFN ABS MBSFN Almost Blank Subframe (Almost Blank Subframe) MDT Minimization of Drive Tests (Minimization of Drive Tests) MIB Master Information Block (Master Information Block) MME Mobility Management Entity (Mobility Management Entity) MSC Mobile Switching Center (Mobile Switching Center) NPDCCH Narrowband Physical Downlink Control Channel (Narrowband Physical Downlink Control Channel) NR New Radio (New Radio) NUL Normal Uplink (Normal Uplink) OCNG OFDMA Channel Noise Generator (OFDMA Channel Noise Generator) OFDM Orthogonal Frequency Division Multiplexing (Orthogonal Frequency Division Multiplexing) OFDMA Orthogonal Frequency Division Multiple Access (Orthogonal Frequency Division Multiple Access) OSS Operations Support System (Operations Support System) OTDOA Observed Time Difference of Arrival (Observed Time Difference of Arrival) O&M Operation and Maintenance (Operation and Maintenance) PBCH Physical Broadcast Channel (Physical Broadcast Channel) P-CCPCH Primary Common Control Physical Channel (Primary Common Control Physical Channel) PCell Primary Cell (Primary Cell) PCFICH Physical Control Format Indicator Channel (Physical Control Format Indicator Channel) PDCCH Physical Downlink Control Channel (Physical Downlink Control Channel) PDCP Packet Data Convergence Protocol (Packet Data Convergence Protocol) PDP Power Delay Profile (Power Delay Profile) PDSCH Physical Downlink Shared Channel (Physical Downlink Shared Channel) PGW Packet Gateway (Packet Gateway) PHICH Physical Hybrid-ARQ Indicator Channel (Physical Hybrid-ARQ Indicator Channel) PLMN Public Land Mobile Network (Public Land Mobile Network) PMI Precoder Matrix Indicator (Precoder Matrix Indicator) PRACH Physical Random Access Channel (Physical Random Access Channel) PRS Positioning Reference Signal (Positioning Reference Signal) PSS Primary Synchronization Signal (Primary Synchronization Signal) PUCCH Physical Uplink Control Channel (Physical Uplink Control Channel) PUSCH Physical Uplink Shared Channel (Physical Uplink Shared Channel) RACH Random Access Channel (Random Access Channel) QAM Quadrature Amplitude Modulation (Quadrature Amplitude Modulation) RA Random Access (Random Access) RACH Random Access Channel (Random Access Channel) RAN Radio Access Network (Wireless Access Network) RAT Radio Access Technology (Radio Access Technology) RLC Radio Link Control (Radio Link Control) RLM Radio Link Management (Radio Link Management) RNC Radio Network Controller (Radio Network Controller) RNTI Radio Network Temporary Identifier (Radio Network Temporary Identifier) RRC Radio Resource Control (Radio Resource Control) RRM Radio Resource Management (Radio Resource Management) RS Reference Signal (Reference Signal) RSCP Received Signal Code Power (Received Signal Code Power) RSRP Reference Symbol Received Power (Reference Symbol Received Power) Reference Signal Received Power (Reference Signal Received Power) RSRQ Reference Signal Received Quality Reference Symbol Received Quality RSSI Received Signal Strength Indicator (Received Signal Strength Indicator) RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDAP Service Data Adaptation Protocol SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self Optimized Network SR Scheduling Request SS Synchronization Signal SSS Secondary Synchronization Signal SUL Supplementary Uplink TAT Timing Advance Timer TDD Time Division Duplex (Time Division Duplex) TDOA Time Difference of Arrival (Time Difference of Arrival) TOA Time of Arrival (Time of Arrival) TSS Tertiary Synchronization Signal (Tertiary Synchronization Signal) TTI Transmission Time Interval (Transmission Time Interval) UE User Equipment (User Equipment) UL Uplink (Uplink) USIM Universal Subscriber Identity Module (Universal Subscriber Identity Module) UTDOA Uplink Time Difference of Arrival (Uplink Time Difference of Arrival) WCDMA Wide CDMA (Wide CDMA) WLAN Wide Local Area Network (Wide Local Area Network)

Claims

1. A method (300) performed by a user equipment, UE, (12) with respect to a communication network, the method comprising: receiving, from a serving radio network node of the communication network, a release message in connection with the UE transitioning from an active mode to an inactive mode, before receiving data in an uplink, UL, transmission buffer of the UE, the release message indicating criteria for determining data restrictions to be applied by the UE with respect to configured grant small data transmission, CG-SDT, resources, the release message consisting of an RRCRelaseMessage, where RRC indicates radio resource control; receiving, from the UE, data in the UL transmission buffer of the UE while the UE is in the inactive mode (302); determining (304) whether the data is restricted from transmission on CG-SDT resources, where determining whether the data is restricted from transmission on CG-SDT resources comprises determining whether usage criteria for the CG-SDT resources are met; and initiating, in response to the data not being restricted from transmission on CG-SDT resources, a CG-SDT procedure in which at least a portion of the data is transmitted on CG-SDT resources (306). A method comprising the above.

2. The method according to claim 1, further comprising, after initiating the CG-SDT procedure, receiving further data in the UL transmission buffer and, in response to determining that the further data is restricted from transmission on CG-SDT resources, performing a random access procedure for the purpose of transmitting a buffer status report, BSR.

3. Determining whether the data is restricted from transmission on the CG-SDT resource includes determining whether the data belongs to a restricted data radio bearer, DRB, or a restricted logical channel, LCH, and the method according to claim 1.

4. Determining whether the data is restricted from transmission on the CG-SDT resource includes determining whether the data is restricted from at least one of an association between a data radio bearer, DRB, and the data, an association between a logical channel, LCH, and the data, priority, or size, and the method according to claim 1.

5. Before receiving data in the UL transmission buffer of the UE, further includes receiving a release message from a serving radio network node of the communication network in connection with the UE transitioning from an active mode to the non-active mode, and the release message indicates a criterion for determining a data restriction to be applied by the UE with respect to the CG-SDT resource, and the method according to claim 1.

6. Determining whether the usage criterion of the CG-SDT resource is satisfied, the UE the use of the CG-SDT procedure is available on a related uplink, UL, carrier that is a supplementary UL, SUL, carrier or a normal UL, NUL, carrier, the related timing advance timer, TAT, of the UE is running, the reference signal received power, RSRP, measured by the UE for a downlink reference signal received by the UE from a serving radio network node of the communication network is greater than or equal to a specified threshold, and the method according to claim 1.

7. In response to the usage criteria of the CG-SDT resource not being met, the method includes the UE starting a RA-SDT procedure in which at least a part of the data is transmitted using RA-SDT resources, in response to the criteria of random access SDT, RA-SDT, being met, according to the method of claim 1.

8. The RA-SDT resource is a resource used by the UE for transmitting Msg3 or MsgA during the RA-SDT procedure, according to the method of claim 7.

9. Determining whether the criteria of the RA-SDT are met includes determining whether the data conforms to the RA-SDT resource, according to the method of claim 7.

10. In response to the criteria of the RA-SDT not being met, the method includes the UE starting a RA procedure without SDT to re-establish the connection mode with the communication network and then transmitting the data in the connection mode, according to the method of claim 7.

11. In response to determining that the CG-SDT resource recurs periodically and that the transmission of the data is restricted on the CG-SDT resource, the method includes, for transmitting the data, one of the following items: The time until the next CG-SDT resource, The priority of the logical channel, LCH, or data radio bearer, DRB, associated with the data, or The size of the data, Selecting either a random access SDT, RA-SDT, procedure or a RA procedure without SDT based on at least one of the above, according to the method of claim 1.

12. A method (400) performed by a network node (10) of a communication network, A user equipment, UE, (12) generates (402) a signaling message indicating a restriction on whether predetermined data input following the uplink, UL, transmission buffer of the UE is restricted from transmission using a configured grant small data transmission, CG-SDT, procedure. Transmits (404) the signaling message to the UE. including The signaling message includes a release message transmitted to the UE as the UE transitions from a connected mode to an inactive mode. The release message consists of an RRCRelaseMessage, where RRC indicates radio resource control. Method.

13. The method according to claim 12, wherein the restriction indicates one or more logical channels, LCH, or data radio bearers, DRB, for which related data is restricted from UL transmission using the CG-SDT procedure.

14. The method according to claim 12, wherein the network node is a radio network node operating as a serving radio network node for the UE.

15. A user equipment, UE, (12) configured to operate with respect to a communication network, including a communication interface (20) including a radio transmitter and receiver configured to transmit signals for the communication network and receive signals from the communication network. A processing circuit (26), Before receiving data in the uplink, UL, transmission buffer of the UE, receiving a release message from a serving radio network node of the communication network in connection with the UE transitioning from an active mode to an inactive mode, wherein the release message indicates criteria for determining data restrictions to be applied by the UE with respect to configured grant small data transmission, CG-SDT, resources, and the release message consists of an RRCReleseMessage, where RRC indicates radio resource control, receiving, While the UE is in the inactive mode, receiving data from the UE into the UL transmission buffer of the UE, Determining whether the data is restricted from transmission on CG-SDT resources, and determining whether the data is restricted from transmission on CG-SDT resources is determining whether the usage criteria for the CG-SDT resources are met, determining, In response to the data not being restricted from transmission on CG-SDT resources, starting a CG-SDT procedure via the communication interface for transmitting at least a portion of the data on CG-SDT resources, A processing circuit configured as such, A UE comprising.

16. A UE according to claim 15, configured to execute the method according to any one of claims 2 to 11.

17. A network node (10) configured to operate in a communication network, A communication interface (30), A processing circuit (36), Generating a signaling message indicating a restriction for determining whether predetermined data subsequently input into the uplink, UL, transmission buffer of the user equipment, UE, (12) is restricted from transmission using a configured grant small data transmission, CG-SDT, procedure, A processing circuit (36) configured to transmit the signaling message to the UE via the communication interface. The signaling message includes a release message transmitted to the UE as the UE transitions from a connected mode to an inactive mode. The release message consists of an RRCRelaseMessage, where RRC indicates radio resource control. Network node.

18. The network node according to claim 17, configured to execute the method according to claim 13 or 14.

Images