Showing posts with label 3GPP. Show all posts
Showing posts with label 3GPP. Show all posts

Tuesday, November 26, 2024

Low Latency Power Saving with Low Power-Wake Up Signal/Receiver (LP-WUS/LP-WUR)

Power-saving methodologies have been integral to all generations of 3GPP technologies, aimed at reducing the power consumption of user equipment (UEs) and other battery-dependent devices. Some of the stringent requirements of 5G, such as achieving a 10-year battery life for certain IoT devices, have necessitated further optimisation of power consumption. To address this, 3GPP Release 16 introduced the Wake-Up Signal (WUS) power-saving mechanism, designed to significantly reduce energy usage in UEs. For a detailed technical explanation, ShareTechnote provides an excellent overview.

The concept of wake-up radios has been explored for over a decade. In a 2017 blog post, Ericsson highlighted how researchers had been working on designing wake-up radios and receivers, initially aimed at IEEE 802.11 (Wi-Fi) technologies. This idea later gained traction in 3GPP discussions, culminating in a study conducted during Release 18. The findings are comprehensively documented in 3GPP TR 38.869: Study on low-power wake-up signal and receiver for NR (Release 18).

Quoting from the introduction of 3GPP 38.869:

5G systems are designed and developed targeting for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, UE energy efficiency is also critical to 5G. Currently, 5G devices may have to be recharged per week or day, depending on individual's usage time. In general, 5G devices consume tens of milliwatts in RRC idle/inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is a necessity for improving energy efficiency as well as for better user experience. 

Energy efficiency is even more critical for UEs without a continuous energy source, e.g., UEs using small rechargeable and single coin cell batteries. Among vertical use cases, sensors and actuators are deployed extensively for monitoring, measuring, charging, etc. Generally, their batteries are not rechargeable and expected to last at least few years as described in TR 38.875. Wearables include smart watches, rings, eHealth related devices, and medical monitoring devices. With typical battery capacity, it is challenging to sustain up to 1-2 weeks as required. 

The power consumption depends on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, eDRX cycle with large value is expected to be used, resulting in high latency, which is not suitable for such services with requirements of both long battery life and low latency. For example, in fire detection and extinguishment use case, fire shutters shall be closed and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors, long eDRX cycle cannot meet the delay requirements. eDRX is apparently not suitable for latency-critical use cases. Thus, the intention is to study ultra-low power mechanism that can support low latency in Rel-18, e.g. lower than eDRX latency.

Currently, UEs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signalling or data traffic. If UEs are able to wake up only when they are triggered, e.g., paging, power consumption could be dramatically reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiver which has the ability to monitor wake-up signal with ultra-low power consumption. Main radio works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.

The power consumption for monitoring wake-up signal depends on the wake-up signal design and the hardware module of the wake-up receiver used for signal detecting and processing. 

The study should primarily target low-power WUS/WUR for power-sensitive, small form-factor devices including IoT use cases (such as industrial sensors, controllers) and wearables. Other use cases are not precluded, e.g.XR/smart glasses, smart phones. 

As opposed to the work on UE power savings in previous releases, this study will not require existing signals to be used as WUS. All WUS solutions identified shall be able to operate in a cell supporting legacy UEs. Solutions should target substantial gains compared to the existing Rel-15/16/17 UE power saving mechanisms. Other aspects such as detection performance, coverage, UE complexity, should be covered by the evaluation.

Qualcomm's blog post looking at 'How will wireless innovations foster a greener, more sustainable future?' is also worth reading on this topic.

Related Posts: 

Posted by Zahid Ghadialy at 5:35 PM Leave a comment...0 comments so far
Labels: , , , , , , , , , , , ,

Wednesday, August 14, 2024

3GPP Release 18 Description and Summary of Work Items

The first official release of 3GPP TR 21.918: "Release 18 Description; Summary of Rel-18 Work Items" has been published. It's the first official version of 5G-Advanced. Quoting from the report: 

Release 18 specifies further improvements of the 5G-Avanced system. 

These improvements consist both in enhancements of concepts/Features introduced in the previous Releases and in the introduction of new topics.

Some of the key improvements are:

  • a further integration of the Satellite (NTN) access (introduced in Rel-17) in the 5G System (5GS), 
  • a more efficient support of Internet of Things (IoT), Machine-Type Communication (MTC), including by satellite coverage
  • and also several aspects of proximity communication and location (Sidelink, Proximity, Location and Positioning, better support of the industrial needs (Verticals, Industries, Factories, Northbound API), Multicast and Broadcast Services (MBS), Network Slicing or Uncrewed Aerial Vehicles (UAV).

As for the new topics, some of the key aspects are:

  • Energy Efficiency (EE)
  • Artificial Intelligence (AI)/Machine Learning (ML)
  • eXtended, Augmented and Virtual Reality (XR, AR, VR), immersive communications

The following list is from the v1.0.0 table of contents to make it easier to find the list of topics. If it interests you, download the latest version technical report from the directory here.

5 Satellite / Non-Terrestrial Network (NTN)
5.1 General aspects
5.1.1 User plane: “5G system with satellite backhaul”
5.1.2 Discontinuous coverage: “Satellite access Phase 2”
5.1.3 Radio: "NR NTN enhancements"
5.1.4 Charging and Management aspects of Satelite
5.2 Specific aspects
5.2.1 IoT (Internet of Things) NTN enhancements
5.2.2 Guidelines for Extra-territorial 5G Systems
5.2.3 5G system with satellite access to Support Control and/or Video Surveillance
5.2.4 Introduction of the satellite L-/S-band for NR
5.2.5 Other band-related aspects of satellite

6 Internet of Things (IoT), Machine-Type Communication (MTC)
6.1 Personal IoT and Residential networks
6.2 Enhanced support of Reduced Capability (RedCap) NR devices
6.3 NR RedCap UE with long eDRX for RRC_INACTIVE State
6.4 Application layer support for Personal IoT Network
6.5 5G Timing Resiliency System
6.6 Mobile Terminated-Small Data Transmission (MT-SDT) for NR
6.7 Adding new NR FDD bands for RedCap in Rel-18
6.8 Signal level Enhanced Network Selection
6.9 IoT NTN enhancements

7 Energy Efficiency (EE)
7.1 Enhancements of EE for 5G Phase 2
7.2 Network energy savings for NR
7.3 Smart Energy and Infrastructure

8 Uncrewed Aerial Vehicles (UAV), UAS, UAM
8.1 Architecture for UAV and UAM Phase 2
8.2 Architecture for UAS Applications, Phase 2
8.3 NR support for UAV
8.4 Enhanced LTE Support for UAV

9 Sidelink, Proximity, Location and Positioning
9.1 5GC LoCation Services - Phase 3
9.2 Expanded and improved NR positioning
9.3 NR sidelink evolution
9.4 NR sidelink relay enhancements
9.5 Proximity-based Services in 5GS Phase 2
9.6 Ranging-based Service and sidelink positioning
9.7 Mobile Terminated-Small Data Transmission (MT-SDT) for NR
9.8 5G-enabled fused location service capability exposure

10 Verticals, Industries, Factories, Northbound API
10.1 Low Power High Accuracy Positioning for industrial IoT scenarios
10.2 Application enablement aspects for subscriber-aware northbound API access
10.3 Smart Energy and Infrastructure
10.4 Generic group management, exposure and communication enhancements
10.5 Service Enabler Architecture Layer for Verticals Phase 3
10.6 SEAL data delivery enabler for vertical applications
10.7 Rel-18 Enhancements of 3GPP Northbound and Application Layer interfaces and APIs
10.8 Charging Aspects of B2B
10.9 NRF API enhancements to avoid signalling and storing of redundant data
10.10 GBA_U Based APIs
10.11 Other aspects

11 Artificial Intelligence (AI)/Machine Learning (ML)
11.1 AI/ML model transfer in 5GS
11.2 AI/ML for NG-RAN
11.3 AI/ML management & charging
11.4 NEF Charging enhancement to support AI/ML in 5GS

12 Multicast and Broadcast Services (MBS)
12.1 5G MBS Phase 2
12.2 Enhancements of NR MBS
12.3 UE pre-configuration for 5MBS
12.4 Other MBS aspects

13 Network Slicing
13.1 Network Slicing Phase 3
13.2 Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection
13.3 Enhancement of Network Slicing UICC application for network slice-specific authentication and authorization
13.4 Charging Aspects of Network Slicing Phase 2
13.5 Charging Aspects for NSSAA
13.6 Charging enhancement for Network Slice based wholesale in roaming
13.7 Network Slice Capability Exposure for Application Layer Enablement
13.8 Other slice aspects

14 eXtended, Augmented and Virtual Reality (XR, AR, VR), immersive
14.1 XR (eXtended Reality) enhancements for NR
14.2 Media Capabilities for Augmented Reality
14.3 Real-time Transport Protocol Configurations
14.4 Immersive Audio for Split Rendering Scenarios  (ISAR)
14.5 Immersive Real-time Communication for WebRTC
14.6 IMS-based AR Conversational Services
14.7 Split Rendering Media Service Enabler
14.8 Extended Reality and Media service (XRM)
14.9 Other XR/AR/VR items

15 Mission Critical and emergencies
15.1 Enhanced Mission Critical Push-to-talk architecture phase 4
15.2 Gateway UE function for Mission Critical Communication
15.3 Mission Critical Services over 5MBS
15.4 Mission Critical Services over 5GProSe
15.5 Mission Critical ad hoc group Communications
15.6 Other Mission Critical aspects

16 Transportations (Railways, V2X, aerial)
16.1 MBS support for V2X services
16.2 Air-to-ground network for NR
16.4 Interconnection and Migration Aspects for Railways
16.5 Application layer support for V2X services; Phase 3
16.6 Enhanced NR support for high speed train scenario in frequency range 2 (FR2)

17 User Plane traffic and services
17.1 Enhanced Multiparty RTT
17.2 5G-Advanced media profiles for messaging services
17.3 Charging Aspects of IMS Data Channel
17.4 Evolution of IMS Multimedia Telephony Service
17.5 Access Traffic Steering, Switch and Splitting support in the 5G system architecture; Phase 3
17.6 UPF enhancement for Exposure and SBA
17.7 Tactile and multi-modality communication services
17.8 UE Testing Phase 2
17.9 5G Media Streaming Protocols Phase 2
17.10 EVS Codec Extension for Immersive Voice and Audio Services
17.11 Other User Plane traffic and services items

18 Edge computing
18.1 Edge Computing Phase 2
18.2 Architecture for enabling Edge Applications Phase 2
18.3 Edge Application Standards in 3GPP and alignment with External Organizations

19 Non-Public Networks
19.1 Non-Public Networks Phase 2
19.2 5G Networks Providing Access to Localized Services
19.3 Non-Public Networks Phase 2

20 AM and UE Policy
20.1 5G AM Policy
20.2 Enhancement of 5G UE Policy
20.3 Dynamically Changing AM Policies in the 5GC Phase 2
20.4 Spending Limits for AM and UE Policies in the 5GC
20.5 Rel-18 Enhancements of UE Policy

21 Service-based items
21.1 Enhancements on Service-based support for SMS in 5GC
21.2 Service based management architecture
21.3 Automated certificate management in SBA
21.4 Security Aspects of the 5G Service Based Architecture Phase 2
21.5 Service Based Interface Protocol Improvements Release 18

22 Security-centric aspects
22.1 IETF DTLS protocol profile for AKMA and GBA
22.2 IETF OSCORE protocol profiles for GBA and AKMA
22.3 Home network triggered primary authentication
22.4 AKMA phase 2
22.5 5G Security Assurance Specification (SCAS) for the Policy Control Function (PCF)
22.6 Security aspects on User Consent for 3GPP services Phase 2
22.7 SCAS for split-gNB product classes
22.8 Security Assurance Specification for AKMA Anchor Function Function (AAnF)
22.9 Other security-centric items

23 NR-only items
23.1 Not band-centric
23.1.1 NR network-controlled repeaters
23.1.2 Enhancement of MIMO OTA requirement for NR UEs
23.1.3 NR MIMO evolution for downlink and uplink
23.1.4 Further NR mobility enhancements
23.1.5 In-Device Co-existence (IDC) enhancements for NR and MR-DC
23.1.6 Even Further RRM enhancement for NR and MR-DC
23.1.7 Dual Transmission Reception (TxRx) Multi-SIM for NR
23.1.8 NR support for dedicated spectrum less than 5MHz for FR1
23.1.9 Enhancement of NR Dynamic Spectrum Sharing (DSS)
23.1.10 Multi-carrier enhancements for NR
23.1.11 NR RF requirements enhancement for frequency range 2 (FR2), Phase 3
23.1.12 Requirement for NR frequency range 2 (FR2) multi-Rx chain DL reception
23.1.13 Support of intra-band non-collocated EN-DC/NR-CA deployment
23.1.14 Further enhancements on NR and MR-DC measurement gaps and measurements without gaps
23.1.15 Further RF requirements enhancement for NR and EN-DC in frequency range 1 (FR1)
23.1.16 Other non-band related items
23.2 Band-centric
23.2.1 Enhancements of NR shared spectrum bands
23.2.2 Addition of FDD NR bands using the uplink from n28 and the downlink of n75 and n76
23.2.3 Complete the specification support for BandWidth Part operation without restriction in NR
23.2.4 Other NR band related topics

24 LTE-only items
24.1 High Power UE (Power Class 2) for LTE FDD Band 14
24.2 Other LTE-only items

25 NR and LTE items
25.1 4Rx handheld UE for low NR bands (<1GHz) and/or 3Tx for NR inter-band UL Carrier Aggregation (CA) and EN-DC
25.2 Enhancement of UE TRP and TRS requirements and test methodologies for FR1 (NR SA and EN-DC)
25.3 Other items

26 Network automation
26.1 Enablers for Network Automation for 5G phase 3
26.2 Enhancement of Network Automation Enablers

27 Other aspects
27.1 Support for Wireless and Wireline Convergence Phase 2
27.2 Secondary DN Authentication and authorization in EPC IWK cases
27.3 Mobile IAB (Integrated Access and Backhaul) for NR
27.4 Further NR coverage enhancements
27.5 NR demodulation performance evolution
27.6 NR channel raster enhancement
27.7 BS/UE EMC enhancements for NR and LTE
27.8 Enhancement on NR QoE management and optimizations for diverse services
27.9 Additional NRM features phase 2
27.10 Further enhancement of data collection for SON (Self-Organising Networks)/MDT (Minimization of Drive Tests) in NR and EN-DC
27.11 Self-Configuration of RAN Network Entities
27.12 Enhancement of Shared Data ID and Handling
27.13 Message Service within the 5G system Phase 2
27.14 Security Assurance Specification (SCAS) Phase 2
27.15 Vehicle-Mounted Relays
27.16 SECAM and SCAS for 3GPP virtualized network products
27.17 SECAM and SCAS for 3GPP virtualized network products
27.18 MPS for Supplementary Services
27.19 Rel-18 enhancements of session management policy control
27.20 Seamless UE context recovery
27.21 Extensions to the TSC Framework to support DetNet
27.22 Multiple location report for MT-LR Immediate Location Request for regulatory services
27.23 Enhancement of Application Detection Event Exposure
27.24 General Support of IPv6 Prefix Delegation in 5GS
27.25 5G Timing Resiliency System
27.26 MPS when access to EPC/5GC is WLAN
27.27 Data Integrity in 5GS
27.28 Security Enhancement on RRCResumeRequest Message Protection

28 Administration, Operation, Maintenance and Charging-centric Features
28.1 Introduction
28.2 Intent driven Management Service for Mobile Network phase 2
28.3 Management of cloud-native Virtualized Network Functions
28.4 Management of Trace/MDT phase 2
28.5 Security Assurance Specification for Management Function (MnF)
28.6 5G performance measurements and KPIs phase 3
28.7 Access control for management service
28.8 Management Aspects related to NWDAF
28.9 Management Aspect of 5GLAN
28.10 Charging Aspects of TSN
28.11 CHF Distributed Availability
28.12 Management Data Analytics phase 2
28.12 5G System Enabler for Service Function Chaining
28.13 Other Management-centric items

29 Other Rel-18 Topics

If you find them useful then please get the latest document from here.

Related Posts: 

Posted by Zahid Ghadialy at 7:35 AM Leave a comment...0 comments so far
Labels: , , , , , , , , , , , , , ,

Thursday, June 27, 2024

Short Tutorial on Mission Critical Services in LTE and 5G

Over the years we have looked at the standards development, infrastructure development and even country specific mission critical solutions development in various blog posts. In this post we are sharing this short new tutorial by Mpirical on mission critical services in LTE and 5G. The video is embedded below:

Related Posts: 

Posted by Zahid Ghadialy at 7:35 AM Leave a comment...0 comments so far
Labels: , , , , , , , , , , ,

Monday, May 6, 2024

6G and Other 3GPP Logos

The Project Coordination Group (PCG) of 3GPP recently approved a new logo for use on specifications for 6G, during their 52nd PCG meeting, hosted by ATIS in Reston, Virginia. As with previous logos, surely people in general will use them not just for 3GPP 6G compliant products, but for all kinds of things.

Over the years many people have reached out to me to ask for 3GPP logos, even though they are available publicly. All 3GPP logos, from 3G to 6G is available in the Marcoms directory here. In addition to the logo, each directory also lists guidance for use of the logos. For example, 3GPP does not allow the use of the logo as shown on the left in the image on top of the post while the one on the right is okay.

Surely there isn't an issue for general use but for anyone wishing to use the logos for their products, equipment, documentation or books, they will have to strictly comply with the rules.

Related Posts: 

Posted by Zahid Ghadialy at 2:35 PM Leave a comment...0 comments so far
Labels: , , , , , , ,

Wednesday, January 24, 2024

UE Assistance Information in LTE and 5G

I have been asked about the UE Assistance Information (UAI) RRC message a few times before. Generally I have always pointed people back to the LTE/5G specifications but here is a concise video that the telecoms technology training company Mpirical have shared recently:

If you want to dig further into details then please see the RRC specifications: 36.331 for LTE and 38.331 for 5G. 

Over the years I have added quite a few short tutorials from Mpirical on this blog, do check them out below.

Related Posts: 

Posted by Zahid Ghadialy at 7:33 AM Leave a comment...0 comments so far
Labels: , , , , , , , , , , ,

Thursday, August 3, 2023

Tutorial: A Quick Introduction to 3GPP

We recently made a beginners tutorial explaining the need for The 3rd Generation Partnership Project (3GPP), its working, structure and provides useful pointers to explore further. The video and slides are embedded below.

You can download the slides from here.

Related Posts: 

Posted by Zahid Ghadialy at 7:35 AM Leave a comment...0 comments so far
Labels: , , , , ,

Wednesday, July 12, 2023

Small Data Transmission (SDT) in LTE and 5G NR

One of the features that was introduced part of 5G NR 3GPP Release 17 is known as Small Data Transmission (SDT). When small amount of data, in case of an IoT device, needs to be sent, there is no need to establish data radio bearers. The information can be sent as part of signalling message. A similar approach is available in case of 4G LTE. 

Quoting from Ofinno whitepaper 'Small Data Transmission: PHY/MAC', 

The SDT in the 3GPP simply refers to data transmission in an inactive state. Specifically, the SDT is a transmission for a short data burst in a connectionless state where a device does not need to establish and teardown connections when small amounts of data need to be sent.

In the 3GPP standards, the inactive state had not supported data transmission until Release 15. The 3GPP standards basically allowed the data transmission when ciphering and integrity protection are achieved during the connection establishment procedure. Therefore, the data transmission can occur after the successful completion of the establishment procedure between the device and network.

The problem arises as a device stays in the connected state for a short period of time and subsequently releases the connection once the small size data is sent. Generally, the device needs to perform multiple transmissions and receptions of control signals to initiate and maintain the connection with a network. As a payload size of the data is relatively smaller compared with the amounts of the control signals, making a connection for the small data transmission becomes more of a concern for both the network and the device due to the control signaling overhead.

The 3GPP has developed the SDT procedure to enable data transmission in the inactive state over the existing LTE and NR standards. The device initiates the SDT procedure by transmitting an RRC request message (e.g., SDT request message) and data in parallel instead of transmitting the data after the RRC request message processed by a network. Additional transmission and/or reception are optional. The device performs this SDT procedure without transition to the connected state (i.e., without making a connection to the network).

The SDT enables for the network to accept data transmission without signaling intensive bearer establishment and authentication procedure required for the RRC connection establishment or resume procedure. For example, in the SDT procedure, the device needs only one immediate transmission of a transport block (TB) that contains data and RRC request message. Furthermore, the device does not need to perform procedures (e.g., radio link monitoring) defined in the connected state since the RRC state is kept as the inactive state. This results in improving the battery life of the device by avoiding control signaling unnecessary for transmission of small size data.

The principle of the SDT is very simple. The network configures radio resources beforehand for the data transmission in the inactive state. For example, if the conditions to use the configured radio resources satisfy, the device transmits data and the RRC request message together via the configured radio resources. In the 3GPP standards, there are two types of the SDT depending on the ways to configure the radio resources: (1) SDT using a random access (RA) and (2) SDT using preconfigured radio resources. 

Figure 2 (top) illustrates different types of the SDT referred in 3GPP LTE and NR standards. The SDT using the random access in LTE and NR standards is referred to as an EDT (early data transmission) and RA-SDT (Random Access based SDT), respectively. For both the EDT and the RA-SDT, the device performs data transmission using shared radio resources of the random access procedure. Thus, the contention with other devices can occur over the access to the shared radio resources. The shared radio resources for the SDT are broadcast by system information and are configured as isolated from the one for a nonSDT RA procedure, i.e., the legacy RA procedure. On the other hands, the CG-SDT uses the preconfigured radio resources dedicated to the device. The SDT using the preconfigured radio resource is referred to as transmission via PUR (Preconfigured Uplink Resource) in the LTE standards. The NR standards refers the SDT using the preconfigured radio resource as CG-SDT (Configured Grant based SDT). The network configures the configuration parameters of the preconfigured radio resources when transiting the device in the connected state to the inactive state. For example, an RRC release message transmitted from the network for a connection release contains the configuration parameters of PUR or CG-SDT. No contention is expected for the SDT using the preconfigured radio resource since the configuration parameters are dedicated to the device. 

You can continue reading the details in whitepaper here. Ofinno has another whitepaper on this topic, 'Small Data Transmission (SDT): Protocol Aspects' here.

3GPP also recently published an article on this topic here. Quoting from the article:

With SDT it is possible for the device to send small amounts of data while remaining in the inactive state. Note that this idea resembles the early GSM systems where SMS messages where sent via the control signalling; that is, transferring small amounts of data while the mobile did not have a (voice) connection.

SDT is a procedure which allows data and/or signalling transmission while the device remains in inactive state without transitioning to connected state. SDT is enabled on a radio bearer basis and is initiated by the UE only if less than a configured amount of UL data awaits transmission across all radio bearers for which SDT is enabled. Otherwise the normal data transmission scheme is used.

With SDT the data is transmitted quickly on the allocated resource. The IoT device initiates the SDT procedure by transmitting an RRC request message and payload data in parallel, instead of the usual procedure where the data is transmitted after the RRC request message is processed by a network.

It is not only the speed and the reduced size of the transmitted data which make SDT such a suitable process for IoT devices. Since the device stays in the inactive state, it does not have to perform many tasks associated with the active state. This further improves the battery life of the IoT device. Additional transmission and/or reception are optional.

There are two ways of performing SDT:

  1. via random access (RA-SDT)
  2. via preconfigured radio resources (CG-SDT)

Random Access SDT

With RA-SDT, the IoT device does not have a dedicated radio resource, and it is possible that the random access message clashes with similar RA-SDT random access messages from other IoT devices. The device gets to know the radio resources for the RA procedure from system information messages, in a similar way to non RA-SDT devices. However, the RA radio resources for SDT and non SDT devices are kept separate; that is, these device types do not interfere with each other in random access

The RA-SDT procedure can be a two-step or a four-step random access procedure. In two-step procedure the payload data is already sent with the initial random access message, whereas in four-step procedure the device first performs contention resolution with the random access request - random access response message pair, and then sends the UL payload with RRC Resume Request. The procedure may continue with further uplink and downlink small data transmissions, and then it is terminated with an RRC Release from the network.

Below are the signalling diagrams for both two-step and four-step RA-SDT procedures. Note that in both cases the UE stays in the RRC inactive state during the whole process.

Configured Grant SDT

For CG-SDT, the radio resources are allocated periodically based on the estimation of the UE’s traffic requirements. This uplink scheduling method is called Configured Grant (CG). With CG-SDT there will be no message clashes with other IoT devices since the radio resources are dedicated for each device. The resource allocation is signalled to the IoT device by the network when the device leaves the connected state.

If the amount of data in the UE's tx buffer is larger than a defined limit, then the data transmission is done using the normal non-SDT procedure.

For SDT process, the device selects the CG-SDT as the SDT type if the resources for the CG-SDT are configured on the selected uplink carrier. If the resources for the CG-SDT are unavailable or invalid, the RA-SDT or the non-SDT RA procedure will be chosen if those are configured. If no SDT type configuration is available then a normal non-SDT data transmission is performed.

With IoT devices proliferating, it makes sense to optimise data transfer and anything else that will reduce the power consumption and let the battery in the devices last for much longer.

Related Posts: 

Posted by Zahid Ghadialy at 7:35 PM Leave a comment...0 comments so far
Labels: , , , , , , , , , , , ,

Wednesday, June 21, 2023

3GPP TSG RAN and TSG SA Release-19 Workshop Summary

3GPP recently announced the milestone of reaching 100th plenaries of the three Technical Specification Groups (TSGs) in 3GPP which took place in Taipei last week. If you are unsure what TSGs are, we recently made a tutorial of 3GPP, available here.

During the plenary TSG SA and TSG RAN held workshops on Release 19. The top level link for RAN workshop is here while that for SA is here. SA also has HTML link of the documents here.

The slide above is from the RAN chair's summary provides list of topics that were discussed. The following is the executive summary from the draft workshop report:

The 3GPP TSG RAN Rel-19 face-to-face workshop was held June 15 - June 16, 2023 in Taipei hosted by TAICS (Taiwan Association of Information and Communication Standards) and MediaTek with 174 participants (see Annex A) and 491 Tdocs (see Annex B). A GotoWebinar conference call was carried out during the whole workshop to display discussed documents and to allow listen & talk access for people joining remotely.

The workshop agenda was provided in RWS-230001 and split into 3 main parts:

  • High-level overview proposals for Rel-19: 18 Tdocs handled, 46 not treated, 1 in the end endorsed (RP-230488)
  • Specific RAN1/2/3-led Rel-19 topics: 29 Tdocs handled, 369 not treated
  • RAN4-led Rel-19 topics (for information only): 20 not treated

Note: High-level overview proposals for Rel-19 and RAN4-led Rel-19 topics had the restriction of maximum one contribution led per company.

Some guidance about the workshop was provided on the RAN email reflector on 28.04.23 and 02.05.23.

Time plan versions of the workshop were provided on 02.05.23, 11.06.23 and on 15.06.23.

Workshop inputs were possible from 28.04.23 until the submission deadline 31.05.23 9pm UTC.

(Late Tdoc requests as well as revisions of Tdocs after the Tdoc request deadline 30.05.23 9pm UTC were avoided in order to not complicate the Tdoc handling, like quotas for AI 4 and 6, preparations of the workshop in parallel to RAN #100 and preparations of the summary etc.)

Originally, Thursday 15.06.23 and Friday 16.06.23 morning were planned for presentations of a limited set of 47 workshop contributions (selected by the RAN chair trying to achieve a fair coverage of the topics and interests and taking into account that there were many more inputs that can be handled in a 2 days workshop) and Friday afternoon was reserved for the discussion of a summary of the RAN chair (in RWS-230488). Note: Since the presentation part went faster and the Friday lunch break was skipped, the workshop ended on Friday afternoon earlier than originally planned.

Finally, the RAN chair's summary in RWS-230488 was endorsed indicating the motivations and handling of the workshop, the Rel-19 timeline and load plans and the management and categorization of topics.

TSG SA didn't have a summary slide but SWS-230002, output of drafting session on Consolidated SA WG2 Rel-19 Work, listed the following topics:

  • Satellite Architecure Enhancements
  • XRM Enhancements and Metaverse
  • AI/ML enhancements
  • Multi-access (Dual 3GPP + ATSSS Enh)
  • Integrated Sensing and Communication
  • Ambient IoT
  • Energy Efficiency / Energy Saving as a Service
  • IMS and NG_RTC enhancements
  • Edge Computing Enhancements
  • Proximity Services enhancements 
  • TSC/URLLC/TRS enhancements 
  • Network Sharing 
  • User identities + identification of device behind RG/AP
  • 5G Femto 
  • UAS enhancements 
  • VMR Enhancements 
  • UPEAS Enhancements 

Fattesinh Deshmukh has a summary of 3GPP RAN Rel-19 Workshop on LinkedIn here. Nokia has their summary of the workshop here.

Related Posts: 

Posted by Zahid Ghadialy at 7:35 AM Leave a comment...0 comments so far
Labels: , , ,

Wednesday, May 31, 2023

New 5G NTN Spectrum Bands in FR1 and FR2

Release-17 includes two new FR1 bands for NTN; n255 (a.k.a. NTN 1.6GHz) and n256 (a.k.a. NTN 2GHz). The picture is from a slide in Rohde & Schwarz presentation available here. Quoting from an article by Reiner Stuhlfauth, Technology Manager Wireless, Rohde & Schwarz:

Currently, several frequency ranges are being discussed within 3GPP for NTN. Some are in the FR1 legacy spectrum, and some beyond 10 GHz and FR2. The current FR1 bands discussed for NTN are:

  • The S-band frequencies from 1980 to 2010 MHz in uplink (UL) direction and from 2170 to 2200 MHz in downlink (DL) direction (Band n256).
  • The L-band frequencies from 1525 to 1559 MHz DL together with 1626.5 to 1660.5 MHz for the UL (Band n255).1

These frequency ranges have lower path attenuation, and they’re already used in legacy communications. Thus, components are available now, but the bands are very crowded, and the usable bandwidth is restricted. Current maximum bandwidth is 20 MHz with up to 40-MHz overall bandwidth envisaged in the future [TR 38.811].

As far as long-term NTN spectrum use is concerned, 3GPP is discussing NR-NTN above 10 GHz. The Ka-band is the highest-priority band with uplinks between 17.7 and 20.2 GHz and downlinks between 27.5 and 30 GHz, based on ITU information regarding satellite communications frequency use.2 Among current FR2 challenges, one is that some of the discussed bands fall into the spectrum gap between FR1 and FR2 and that NTN frequencies will use FDD duplex mode due to the long roundtrip time.

Worth highlighting again that the bands above, including n510, n511 and n512 are all FDD bands due to the long round trip times.

The latest issue of 3GPP highlight magazine has an article on NTN as well. Quoting from the article:

The NTN standard completed as part of 3GPP Release 17 defines key enhancements to support satellite networks for two types of radio protocols/interfaces:

  • 5G NR radio interface family also known as NR-NTN
  • 4G NB-IoT & eMTC radio interfaces family known as IoT-NTN

These critical enhancements including adaptation for satellite latency and doppler effects have been carefully defined to support a wide range of satellite network deployment scenarios and orbits (i.e., LEO, MEO and GEO), terminal types (handheld, IoT, vehicle mounted), frequency bands, beam types (Earth fixed/Earth moving) and sizes. The NTN standard also addresses mobility procedures across both terrestrial and non-terrestrial network components. Release 17 further includes Radio Frequency and Radio Resource Management specifications for terminals and satellite access nodes operating in two FR1 frequency ranges allocated to Mobile Satellite Services (i.e., n255 and n256).

You can read it here.

Related Posts: 

Posted by Zahid Ghadialy at 7:35 AM Leave a comment...0 comments so far
Labels: , , , , , , , ,

Thursday, April 6, 2023

ETSI's Summit on Sustainability: ICT Standards for a Greener World

The ETSI Summit on Sustainability - How ICT developments and standards can enable sustainability and have a positive impact on society, took place on 30 March 2023 and focused on the key role of the ICT industry and related standardization activities to support Green initiatives. The event brought a large and global audience of over 220 stakeholders including operators, solution providers, policy makers and standards bodies or fora working on the topic.

A multitude of presentations including two interactive panel sessions, rhythmed the day and succeeded to make it a highly interactive Summit, pointing out challenges and how ICT can be both the problem and the solution.

The opening session examined the sustainability challenges and global green initiatives from numerous global standards bodies and fora. One of the suggested actions was to adopt ESG (Environmental Social Governance) goals as an integral part of the company’s objectives. Another highlight from the session was the need for standards work on the measuring and reporting of “avoided emissions,” that is being covered by ongoing work in ETSI. Feedback from the audience pointed out that it would be beneficial to further investigate the balance of ICT deployments vs real needs. Do we really need to endlessly deploy new technologies, when exiting ones serve the need?

The following are presentations from the welcome address and session 1:

The second session focused on the role of ICT in sustainability and was animated by two panels. The first one addressed the operators’ objectives and their plans for sustainability. The second one dealt with various initiatives being taken by solutions providers to meet the needs expressed by the operators and society as a whole. Suggested actions emerging from the debate included putting sustainability criteria in the procurement phase towards the vendors and enhance collaboration between operators, to share their common requirements and provide them to the supply chain ecosystem. In an animated exchange between the Panellists and the audience it was highlighted that there is an urgent need to reduce energy consumption, extend the lifecycles of ICT equipment and systematically recycle and repurpose in order to reduce ICT waste.

The following are presentations from session 2:

  • Session 02 - The Role of ICT in Sustainability: The session comprises two interactive panel sessions examining 1) Operators objectives and plans for Sustainability and 2) several initiatives being taken by solutions providers to meet those objectives. Session Chaired by David Boswarthick, ETSI
    • Operators Panel Moderated by Anita Dohler, NGMN Alliance e.V.: The purpose of this panel is to examine what are the sustainability plans, challenges & priorities for Operators
      • Saima Ansari, Deutsche Telekom
      • P. Balaji, Vodafone Idea
      • Marc Grant, AT&T
      • Luca Pesando, TIM
    • Solution Providers Panel Moderated by Joe Barrett, GSA, Global Mobile Suppliers Association - The purpose is to examine what the current solutions and remaining challenges on Sustainability are.

The afternoon opened with an  overview of ETSI, 3GPP and oneM2M activities supporting technologies for sustainability. One of the presentations highlighted that ICT should initially focus its own environmental impacts and consider digital sobriety as it is recognized that the cleanest energy is the one that is not consumed.

The following are presentations from session 3:

The summit concluded with a dynamic exchange around what more telecoms can do to move forward in the right direction. ICT and specifically data centres create a significant carbon footprint, and there was a call to use the ISO Net Zero guidelines in order to develop sustainable strategies. The industry should adopt an eco-design (sustainability by design) approach and seek to have products that are energy efficient, with longer life cycles, recyclable and repairable.

The following are presentations from session 4:

As a conclusion it was agreed that ICT is part of the sustainability problem and must seek to reduce its own emissions, whilst at the same time ICT is certainly part of the solution and should be applied to other domains in order to help them reach their own sustainability goals. As a first step, making ICT more sustainable should be the #01 priority for the industry today and ETSI groups TC EE (environmental engineering), TC ATTM (access, terminal and multiplexing) and ISG OEU (operational energy efficiency for users) are currently providing the standards to enable this transition to greener digital technologies.

Event Wrap-Up / Conclusions is available here.

Should you wish to learn more about the summit, all of the presentations including the conclusion slides are available here.

Related Posts: 

Posted by Zahid Ghadialy at 7:35 AM Leave a comment...0 comments so far
Labels: , , , , , , , , , ,
Subscribe to: Posts (Atom)