New & Events

SUNRISE-6G actively participated in 3GPP meetings, showcasing our commitment to participate in standardisation activities.

Numerous SUNRISE-6G project partners actively participated in the 3GPP meetings between 26 February – 1 March 2024 in Athens, Greece, showcasing our commitment to participate in standardisation activities.

 

The main objective of the 3GPP Technical Specification Group Service and System Aspects (TSG SA) is to develop the overall 3GPP system architecture and services, including User Equipment, Access Networks, Core Networks, and IP Multimedia Subsystems.

 

SUNRISE-6G aims to integrate terrestrial and non-terrestrial networks seamlessly. Thus, our involvement in 3GPP focuses on enhancing multi-access connectivity, a cornerstone of the SUNRISE-6G project. Our efforts aim to create a robust framework that supports diverse access paths, ensuring reliable and ubiquitous connectivity. By contributing to 3GPP-relevant studies (e.g., Dual Steer and FS_MASSS), we are not only part of the conversation but also driving the evolution of next-generation networks.

 

Here’s a glimpse of the remarkable progress we’ve made:

1. Collection of Energy Consumption related information

As part of Functional-Test-02, SUNRISE-6G aims to demonstrate how an experimenter can deploy an edge application in a testbed and then receive energy consumption measurements. These measurements could be about the energy consumed by the app or the energy consumed for serving a UE or a group of UEs. Currently, a 5G network cannot obtain and expose energy consumption per UE or group of UEs, so a new solution is required.

 

SUNRISE-6G proposed a solution allowing the 5G network to calculate the energy consumed for servicing a UE (or a group of UEs) and expose this information to 3rd parties, such as verticals or experimenters.

 

2. MPQUIC steering functionality using IP proxying over HTTP

SUNRISE-6G aims to support multi-access connectivity using terrestrial and non-terrestrial access paths. To comply with the 3GPP specifications, multi-access connectivity should be based on the ATSSS solution, which supports Multipath TCP (TCP traffic) and Multipath QUIC (UDP traffic). This makes it difficult for the project to support multi-access for both TCP and UDP traffic flows because the deployment of both MPTCP and MPQUIC is required.

 

To alleviate this issue, a new solution (ATSSS steering functionality) is proposed that applies only the MPQUIC protocol for all types of IP traffic transmission (including TCP and UDP over HTTP/3 and QUIC.

 

3. ATSSS with Offloaded Non-3GPP Access

SUNRISE-6G aims to support multi-access connectivity using terrestrial and non-terrestrial access paths. To support multi-access connectivity based on the 3GPP standards, the testbeds must deploy at least an N3IWF function. However, this function is unavailable, making it challenging to support standards-compliant multi-access connectivity.

 

A new technical multi-access solution is proposed in 3GPP, entitled “ATSSS with Offloaded Non-3GPP Access.” It does not require the N3IWF function and is easier to support in the project. It enables multi-access communication between the UE and UPF without the need to deploy an N3IWF or TNGF on the non-3GPP access path.

 

 

These approvals underscore the commitment and expertise of our team within the 3GPP community. It reflects our shared goal of driving technological advancements and shaping the future of 6G initiatives. The collaborative spirit and enthusiasm demonstrated by each contributor have been truly commendable.

 

We extend gratitude to the dedicated members of our project who played a crucial role in shaping this contribution and this success…. and the list goes on!

Let’s continue this momentum and strive for even more remarkable achievements as we progress.

 

Subscribe to the SUNRISE-6G e-newsletter here and follow the project’s LinkedIn and Twitter profile for the latest information.

“Co-funded by the European Union. Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the Smart Networks and Services Joint Undertaking (SNS JU). Neither the European Union nor the granting authority can be held responsible for them.”