Establishing one or more signaling radio bearers for data session
Enhancements to the CP C-IoT optimization procedure through dedicated signaling radio bearers with QoS parameters address the challenge of differentiated service handling in non-terrestrial networks, ensuring reliable IMS voice and signaling traffic over NB-IoT devices.
Patent Information
- Application Number
- PCT/CN2025/093195
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Current control-plane-based data transfer over non-access stratum in non-terrestrial networks, such as satellite communications, does not provide priority or guaranteed bit rate for differentiating service types like IMS signaling and voice, leading to race conditions and resource exhaustion.
Implementing enhancements to the CP C-IoT optimization procedure by establishing dedicated signaling radio bearers with specific QoS parameters for IMS voice and signaling traffic, allowing the MME or AMF to determine and the UE to map traffic types, ensuring end-to-end QoS control.
Ensures timely and reliable handling of IMS voice and signaling traffic over NB-IoT devices via satellites, preventing resource conflicts and maintaining call quality.
Smart Images

Figure CN2025093195_12112026_PF_FP_ABST
Abstract
Description
ESTABLISHING ONE OR MORE SIGNALING RADIO BEARERS FOR DATA SESSIONFIELD
[0001] The following example embodiments relate to wireless communication.BACKGROUND
[0002] A non-terrestrial network (NTN) refers to a communication network that uses space-based or airborne platforms, such as satellites, high-altitude platforms, or unmanned aerial vehicles, to provide connectivity. Unlike terrestrial networks that rely on ground-based infrastructure, NTNs can offer coverage in remote or underserved areas, enhance network resilience, and support a wide range of applications, including broadband internet, disaster recovery, and Internet of Things connectivity.SUMMARY
[0003] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS
[0004] In the following, various example embodiments will be described in greater detail with reference to the accompanying drawings, in which
[0005] FIG. 1A illustrates an example of a wireless communication network;
[0006] FIG. 1B illustrates an example of a non-terrestrial network;
[0007] FIG. 2 illustrates options for transmission of internet protocol multimedia subsystem voice traffic;
[0008] FIG. 3 illustrates an example of bearer mapping;
[0009] FIG. 4 illustrates an example flow of uplink traffic;
[0010] FIG. 5 illustrates a signal flow diagram;
[0011] FIG. 6 illustrates a signal flow diagram;
[0012] FIG. 7 illustrates a flow chart;
[0013] FIG. 8 illustrates a flow chart;
[0014] FIG. 9 illustrates a flow chart;
[0015] FIG. 10 illustrates an example of an apparatus;
[0016] FIG. 11 illustrates an example of an apparatus; and
[0017] FIG. 12 illustrates an example of an apparatus.DETAILED DESCRIPTION
[0018] The following embodiments are exemplifying. Although the specification may refer to “an” , “one” , or “some” embodiment (s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment (s) , or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments within the scope of the claims. Furthermore, the words "comprising" and "including" should be understood as not limiting the described embodiments to consist of only those features that have been mentioned, and such embodiments may also contain features that have not been specifically mentioned. Reference numbers, in the description and / or in the claims, serve to illustrate the embodiments with reference to the drawings, without limiting the embodiments to these examples only.
[0019] Further, it should be appreciated that, as used herein, the terms “the at least one” and “the one or more” mean “any one of the at least one” and “any one of the one or more” , respectively. Furthermore, as used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0020] Some example embodiments described herein may be implemented in a wireless communication network comprising an access network (e.g., a radio access network) based on one or more of the following radio access technologies (RATs) : long term evolution (LTE) , LTE-Advanced, fourth generation (4G) , fifth generation (5G) , 5G new radio (NR) , 5G-Advanced (i.e., 3GPP NR Rel-18 and beyond) , sixth generation (6G) , or seventh generation (7G) .
[0021] Some examples of radio access networks include the evolved universal terrestrial radio access network (E-UTRA) , and the next generation radio access network (NG-RAN) . The wireless communication network may further comprise a core network, and some example embodiments may also be applied to network functions of the core network.
[0022] It should be noted that the embodiments are not restricted to the wireless communication network given as an example, but they may also be applied to other wireless communication networks or systems provided with necessary properties.
[0023] FIG. 1A depicts an example of a simplified wireless communication network showing some physical and logical entities. The connections shown in FIG. 1A may be physical connections or logical connections. The wireless communication network may also comprise other physical and logical entities than those shown in FIG. 1A.
[0024] The example wireless communication network shown in FIG. 1A includes an access network and a core network 110. For example, the access network may be a radio access network (RAN) . FIG. 1A also shows user equipment (UE) 100, 102 configured to be in a wireless connection on one or more communication channels in a radio cell with an access node 104 of a radio access network. The access node 104 may comprise a computing device configured to control the radio resources of the access node 104 and to be in a wireless connection with one or more UEs 100, 102. The access node 104 may also be referred to as a base station, a base transceiver station (BTS) , an access point, a cell site, a network node, a radio access network node, a RAN node, or a network device. The access node 104 may be, for example, an evolved NodeB (abbreviated as eNB or eNodeB) , or a next generation evolved NodeB (abbreviated as ng-eNB) , or a next generation NodeB (abbreviated as gNB or gNodeB) , providing the radio cell. The access node 104 may include or be coupled to transceivers. From the transceivers of the access node 104, a connection may be provided to an antenna unit that establishes a bi-directional radio link to one or more UEs 100, 102. The antenna unit may comprise an antenna or antenna element, or a plurality of antennas or antenna elements.
[0025] The wireless connection (e.g., radio link) from a UE 100, 102 to the access node 104 may be called uplink (UL) or reverse link, and the wireless connection (e.g., radio link) from the access node 104 to the UE 100, 102 may be called downlink (DL) or forward link. A UE 100 may also communicate directly with another UE 102, and vice versa, via a wireless connection generally referred to as a sidelink (SL) . It should be appreciated that the access node 104 or its functionalities may be implemented by using any node, host, server, access point or other entity suitable for providing such functionalities.
[0026] The radio access network may comprise more than one access node 104, in which case the access nodes may also be configured to communicate with one another over wired or wireless links. These links between access nodes may be used for sending and / or receiving control plane signaling and also for routing data from one access node to another access node.
[0027] The access node 104 may further be connected to a core network (CN) 110. The core network 110 may comprise an evolved packet core (EPC) network and / or a 5th generation core network (5GC) . The EPC may comprise network entities, such as a serving gateway (S-GW) for routing and forwarding data packets, a packet data network gateway (P-GW) for providing connectivity of UEs to external packet data networks, and / or a mobility management entity (MME) . The 5GC may comprise one or more network entities, such as at least one of: a user plane function (UPF) , an access and mobility management function (AMF) , a location management function (LMF) , and / or a session management function (SMF) .
[0028] The core network 110 may also be able to communicate with one or more external networks 113, such as a public switched telephone network or the Internet, or utilize services provided by them. For example, in 5G wireless communication networks, the UPF of the core network 110 may be configured to communicate with an external data network via an N6 interface. In LTE wireless communication networks, the P-GW of the core network 110 may be configured to communicate with an external data network 113.
[0029] It should also be understood that the distribution of functions between core network operations and access node operations may differ in future wireless communication networks compared to that of the LTE or 5G, or even be non-existent.
[0030] The illustrated UE 100, 102 is one type of an apparatus to which resources on the air interface may be allocated and assigned. The UE 100, 102 may also be called a wireless communication device, a subscriber unit, a mobile station, a remote terminal, an access terminal, a user terminal, a terminal device, or a user device, just to mention but a few names. The UE 100, 102 may be a computing device operating with or without a subscriber identification module (SIM) , including, but not limited to, the following types of computing devices: a mobile phone, a smartphone, a personal digital assistant (PDA) , a handset, a computing device comprising a wireless modem (e.g., an alarm or measurement device, etc. ) , a laptop computer, a desktop computer, a tablet, a game console, a notebook, a multimedia device, a reduced capability (RedCap) device, a wearable device (e.g., a watch, earphones or eyeglasses) with radio parts, a household appliance with radio parts, a sensor comprising a wireless modem, or a computing device comprising a wireless modem integrated in a vehicle or in a house.
[0031] It should be appreciated that the UE 100, 102 may also be a nearly exclusive uplink-only device, of which an example may be a camera or video camera loading images or video clips to a network. The UE 100, 102 may also be a device having capability to operate in an Internet of Things (IoT) network, which is a scenario in which objects may be provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.
[0032] The wireless communication network may also be able to support the usage of cloud services. For example, at least part of core network operations may be carried out as a cloud service (this is depicted in FIG. 1A by “cloud” 114) . The UE 100, 102 may also utilize the cloud 114. In some applications, the computation for a given UE may be carried out in the cloud 114 or in another UE.
[0033] 5G enables using multiple-input and multiple-output (MIMO) antennas in the access node 104 and / or the UE 100, 102, many more base stations or access nodes than an LTE network (aso-called small cell concept) , including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and / or spectrum available. 5G wireless communication networks may support a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine-type applications, such as (massive) machine-type communications (mMTC) , including vehicular safety, different sensors and real-time control.
[0034] In 5G wireless communication networks, access nodes and / or UEs may have multiple radio interfaces, such as below 6 gigahertz (GHz) , centimeter wave (cmWave) and millimeter wave (mmWave) , and also being integrable with legacy radio access technologies, such as LTE. Integration with LTE may be implemented, for example, as a system, where macro coverage may be provided by LTE, and 5G radio interface access may come from small cells by aggregation to LTE. In other words, a 5G wireless communication network may support both inter-RAT operability (such as interoperability between LTE and 5G) and inter-RI operability (inter-radio interface operability, such as between below 6GHz, cmWave, and mmWave) .
[0035] 5G wireless communication networks may also apply network slicing, in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same physical infrastructure to run services that have different requirements on latency, reliability, throughput and mobility.
[0036] In one embodiment, an access node 104 may comprise: a radio unit (RU) comprising a radio transceiver (TRX) , i.e., a transmitter (Tx) and a receiver (Rx) ; one or more distributed units (DUs) that may be used for the so-called Layer 1 (L1) processing and real-time Layer 2 (L2) processing; and a central unit (CU) (also known as a centralized unit) that may be used for non-real-time L2 and Layer 3 (L3) processing. The CU may be connected to the one or more DUs for example via an F1 interface. Such an embodiment of the access node 104 may enable the centralization of CUs relative to the cell sites and DUs, whereas DUs may be more distributed and may even remain at cell sites. The CU and DU together may also be referred to as baseband or a baseband unit (BBU) . The CU and DU may also be comprised in a radio access point (RAP) .
[0037] The CU may be a logical node hosting radio resource control (RRC) , service data adaptation protocol (SDAP) and / or packet data convergence protocol (PDCP) , of the NR protocol stack for an access node 104. The CU may comprise a control plane (CU-CP) , which may be a logical node hosting the RRC and the control plane part of the PDCP protocol of the NR protocol stack for the access node 104. The CU may further comprise a user plane (CU-UP) , which may be a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol of the CU for the access node 104.
[0038] The DU may be a logical node hosting radio link control (RLC) , medium access control (MAC) and / or physical (PHY) layers of the NR protocol stack for the access node 104. The operations of the DU may be at least partly controlled by the CU. It should also be understood that the distribution of functions between the DU and the CU may vary depending on the implementation.
[0039] Cloud computing systems may also be used to provide the CU and / or DU. A CU provided by a cloud computing system may be referred to as a virtualized CU (vCU) . In addition to the vCU, there may also be a virtualized DU (vDU) provided by a cloud computing system. Furthermore, there may also be a combination, where the DU may be implemented on so-called bare metal solutions, for example application-specific integrated circuit (ASIC) or customer-specific standard product (CSSP) system-on-a-chip (SoC) .
[0040] The wireless communication network may also comprise a non-terrestrial communication network, such as a satellite communication network, to enhance or complement the coverage of the radio access network. For example, satellite communication may support the transfer of data between the radio access network and the core network 110, enabling more extensive network coverage. Possible use cases may include: providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future railway, maritime, or aeronautical communications. Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, or low earth orbit (LEO) satellite systems, such as mega-constellations (i.e., systems in which hundreds of (nano) satellites are deployed) . Alternatively, the satellites may be airborne devices, such as an unmanned aerial vehicle (UAV) , or a high-altitude platform system (HAPS) . A given satellite 106 may provide communication services on Earth via one or more satellite beams. The one or more satellite beams create one or more cells over a given service area that may be bounded by the field of view of the satellite 106.
[0041] It is obvious for a person skilled in the art that the access node 104 depicted in FIG. 1A is just an example of a part of a radio access network, and in practice the radio access network may comprise a plurality of access nodes 104, the UEs 100, 102 may have access to a plurality of radio cells, and the radio access network may also comprise other apparatuses, such as physical layer relay access nodes or other entities. At least one of the access nodes may be a Home eNodeB or a Home gNodeB. A Home gNodeB or a Home eNodeB is a type of access node that may be used to provide indoor coverage inside a home, office, or other indoor environment.
[0042] Additionally, in a geographical area of a radio access network, a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which may be large cells having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto-or picocells. The access node (s) 104 of FIG. 1A may provide any kind of these cells. A cellular radio network may be implemented as a multilayer access networks including several kinds of radio cells. In multilayer access networks, one access node may provide one kind of a radio cell or radio cells, and thus a plurality of access nodes may be needed to provide such a multilayer access network.
[0043] For fulfilling the need for improving performance of radio access networks, the concept of “plug-and-play” access nodes may be introduced. A radio access network, which may be able to use “plug-and-play” access nodes, may include, in addition to Home eNodeBs or Home gNodeBs, a Home Node B gateway (HNB-GW) (not shown in FIG. 1A) . An HNB-GW, which may be installed within an operator’s radio access network, may aggregate traffic from a large number of Home eNodeBs or Home gNodeBs back to a core network 110 of the operator.
[0044] FIG. 1B illustrates an example of a non-terrestrial network. A non-terrestrial network may refer to a network, or a segment of networks, using radio frequency (RF) resources managed / controlled by a satellite 106. The satellite 106 may provide communication services on Earth (or on another planet) via one or more satellite beams. The one or more satellite beams create one or more cells 121 over a given service area bounded by the field of view of the satellite 106. The beam footprints (i.e., the cells 121) may be elliptical in shape. The satellite 106 may be used to provide communication coverage over a very large area (e.g., with a diameter of tens, hundreds, or even thousands of kilometers) that may be otherwise unreachable by cellular networks.
[0045] The satellite 106 may be, for example, a low earth orbit (LEO) satellite, a geostationary earth orbit (GEO) satellite, an unmanned aerial vehicle (UAV) , a high-altitude platform system (HAPS) , or any other spaceborne or airborne device used for communication.
[0046] The satellite 106 may comprise a computing device configured to control the radio resources of the satellite 106 and to be in a wireless connection with one or more UEs 100. The satellite 106 may include or be coupled to transceivers. From the transceivers of the satellite 106, a connection may be provided to an antenna unit that establishes a bi-directional radio link to one or more UEs 100. The antenna unit may comprise an antenna or antenna element, or a plurality of antennas or antenna elements.
[0047] There may be a service link 130 (i.e., a radio link) between the satellite 106 and one or more UEs 100 within the targeted service area for communication between the satellite 106 and the one or more UEs 100.
[0048] Furthermore, there may be a feeder link 140 (i.e., another radio link or an optical link) between the satellite 106 and a ground-based NTN gateway (GW) 104 for communication between the satellite 106 and the gateway 104. In other words, the feeder link 140 is a connection between the satellite 106 and the NTN gateway 104. The NTN gateway 104 may comprise a base station (access node) , such as an evolved NodeB (abbreviated as eNB or eNodeB) , or a next generation evolved NodeB (abbreviated as ng-eNB) , or a next generation NodeB (abbreviated as gNB or gNodeB) . The NTN gateway 104 may be connected to the core network 110 and / or to an external data network 113 (e.g., the internet) .
[0049] In a transparent architecture of the non-terrestrial network, the access node (NTN gateway) 104 of the non-terrestrial network is located on ground (i.e., the base station 104 is on Earth) . In this case, the satellite 106 may just forward the signals it receives from the NTN gateway 104 to one or more UEs 100, and vice versa (i.e., the satellite 106 may act as a repeater between the one or more UEs 100 and the NTN gateway 104) . In the transparent architecture, there may be a feeder link (i.e., a radio link) 140 between the satellite 106 and the ground-based NTN gateway 104, as well as a service link 130 (i.e., another radio link) between the satellite 106 and the one or more UEs 100 within the targeted service area. The transparent architecture may also be referred to as a transparent payload architecture.
[0050] Alternatively, in a regenerative architecture of the non-terrestrial network, the access node of the non-terrestrial network (i.e., partial or full base station functionality) is onboard the satellite 106 itself (e.g., the satellite 106 may comprise a gNB) . In this architecture, no ground-based NTN gateway 104 or feeder link 140 is needed. This means that the satellite 106 does more than just forwards signals: it can process the signals it receives, perform functions such as decoding, demodulation, and remodulation, and then transmit the processed signals to one or more UEs 100 over the service link 130. The regenerative architecture may also be referred to as having regenerative payloads.
[0051] The internet protocol multimedia subsystem (IMS) is an architectural framework designed to deliver multimedia services over internet protocol (IP) networks. IMS was developed by the 3rd generation partnership project (3GPP) to provide a standardized way to offer services such as voice, video, messaging, and / or data over both fixed and mobile networks. IMS enables the convergence of voice and data networks, allowing operators to offer a wide range of services on a single platform.
[0052] IMS operates on the principle of separating the service layer from the transport layer, which means that services can be developed and deployed independently of the underlying network infrastructure. This separation allows for greater flexibility and innovation in service delivery. The core components of IMS include the call session control functions (CSCFs) , which manage session control, and the home subscriber server (HSS) , which stores user profiles and authentication information.
[0053] One of the advantages of IMS is its support for session initiation protocol (SIP) , which may be used for signaling and controlling multimedia communication sessions. SIP enables features like call setup, management, and teardown, making it easier to integrate various multimedia services. IMS also supports quality of service (QoS) mechanisms to ensure that multimedia services are delivered with the required performance levels.
[0054] IMS is designed to be access-agnostic, meaning it can work over different types of networks, such as LTE, 5G, Wi-Fi, and fixed broadband. This flexibility allows operators to offer consistent services across various access technologies. Additionally, IMS supports interoperability between different network operators, enabling seamless communication and service delivery.
[0055] An IMS voice call is a voice communication service delivered over IP networks using the IMS framework. The IMS voice call service comprises two types of data traffic: IMS signaling traffic (which uses QCI5) with high priority, and voice traffic (which uses QCI1) with a guaranteed bit rate. QCI1 and QCI5 refer to specific QoS class identifiers (QCIs) used in LTE networks to define the QoS characteristics for different types of data traffic. The equivalent QoS levels for 5G are 5QI5 and 5QI1
[0056] The IMS signaling traffic involves control messages used to establish, manage, and / or terminate the voice call. IMS signaling traffic may be assigned a high priority to ensure timely and reliable communication between the UE and the network components, such as the CSCFs.
[0057] The voice traffic comprises the actual voice media packets transmitted during the voice call. The voice traffic requires a guaranteed bit rate to maintain call quality, and it may be managed using dedicated bearers with specific QoS parameters to ensure smooth and uninterrupted voice communication.
[0058] QoS parameters (or requirements) refer to the specific criteria that define the performance level of a network service. These QoS parameters ensure that different types of data traffic receive the appropriate level of service to meet their performance needs. QoS parameters may include factors such as latency, jitter, bandwidth, and packet loss. For example, voice and video calls may require low latency and jitter to maintain call quality, while data transfers may prioritize bandwidth. By setting these QoS parameters, the network can manage resources effectively, prioritize critical traffic, and provide a consistent and reliable user experience.
[0059] Narrowband Internet of Things (NB-IoT) is a radio technology developed by the 3GPP to address the specific needs of IoT devices. NB-IoT is designed to provide efficient connectivity for devices that require low data rates, low power consumption, long battery life, and reliable coverage, for example in challenging environments such as deep indoors or rural areas. NB-IoT operates within a narrow bandwidth (e.g., 200 kilohertz) , which helps reduce device complexity, making it a suitable solution for massive IoT deployments, for example.
[0060] One of the features of NB-IoT is its low power consumption, which may allow devices to operate for several years on a single battery. This may be beneficial for applications such as smart metering, environmental monitoring, and asset tracking, where devices may be deployed in remote locations and need to function autonomously for extended periods. NB-IoT also supports a high connection density, enabling a large number of devices to connect to a single cell, which is beneficial for large-scale IoT implementations.
[0061] NB-IoT leverages the cellular infrastructure, allowing network operators to deploy it alongside their LTE and 5G networks, for example. This integration ensures seamless connectivity and interoperability, providing a consistent user experience across different access technologies. Additionally, NB-IoT supports various QoS mechanisms to ensure that data is transmitted with the required performance levels.
[0062] There is a challenge in how to provide IMS services (e.g., IMS voice calls) via a satellite (e.g., a GEO satellite) to UEs (e.g., NB-IoT devices) , as well as how to support QoS for the IMS services via the satellite.
[0063] The current control-plane-based data transfer over non-access stratum (NAS) was designed for small data transfers and does not provide any priority or guaranteed bit rate (i.e., no QoS) to differentiate service types (e.g., IMS signaling and IMS voice) . This lack of QoS control may lead to race conditions and resource exhaustion with other UEs, which are not using voice calls.
[0064] Race conditions refer to situations where the timing of events affects the behavior of the system, potentially leading to unpredictable or undesirable outcomes. For example, in the control-plane cellular Internet of Things (CP C-IoT) optimization procedure for IMS voice services over NB-IoT, race conditions may occur when multiple processes or data flows compete for the same resources without proper synchronization.
[0065] The CP C-IoT optimization procedure refers to enhancements made to cellular networks to efficiently support IoT devices. The CP C-IoT optimization procedure involves optimizing the evolved packet system (EPS) for small data transfers. The procedure may include both control plane and user plane optimizations. Control plane optimization involves transporting user data or short message service (SMS) messages through the MME by encapsulating them in NAS messages. This reduces the total number of control plane messages required for handling short data transactions. NAS messages are signaling messages exchanged between the UE 100 and the core network 110. NAS messages may be carried by NAS protocol data units (PDUs) , which are data packets used in the signaling between the UE 100 and the core network 110.
[0066] FIG. 2 illustrates options 201, 202, 203 for transmission of IMS voice traffic from a UE (e.g., an IoT device) in an LTE network. In FIG. 2, the home subscriber server (HSS) 211, the mobility management entity (MME) 212, the service capability exposure function (SCEF) 213, the serving gateway (S-GW) 214, and the packet data network gateway (P-GW) 215 may be part of the EPC 110 (i.e., the LTE core network) .
[0067] The HSS 211 is a central database in the LTE and IMS networks that contains user-related and subscription-related information. The HSS 211 may be responsible for functions such as user authentication, authorization, and mobility management. The HSS 211 may store user profiles, which include information about the user's services, QoS parameters, and access permissions.
[0068] The MME 212 is responsible for managing the control plane functions related to mobility, session management, and security. The MME 212 handles tasks such as user authentication, authorization, and tracking the location of the UE 100. The MME also manages the establishment, modification, and release of connections between the UE 100 and the network, ensuring seamless handovers and efficient resource allocation.
[0069] The SCEF 213 is a network function that provides a standardized interface for securely exposing the capabilities of the network to external applications and services. The SCEF 213 allows third-party service providers to interact with the network and utilize its features, such as sending and receiving data, managing device connectivity, and accessing location information. The SCEF ensures that these interactions are secure and comply with the network's policies and regulations.
[0070] The S-GW 214 is responsible for routing and forwarding user data packets within the EPC 110.
[0071] The P-GW 215 provides connectivity from the UE 100 to external packet data networks (PDNs) by assigning IP addresses and managing IP traffic. The P-GW 215 may also handle policy enforcement, charging, and packet filtering.
[0072] As mentioned above, the IMS voice call service involves two types of data to be exchanged between the UE 100 and the IMS: voice traffic which uses QCI1 and requires a guaranteed bit rate (GBR) bearer, and IMS signaling traffic which uses QCI5 and a non-GBR bearer. Both the IMS signaling and voice traffic may be carried over the path 201 shown in FIG. 2.
[0073] The usage of the CP C-IoT optimization procedure for the realization of the IMS voice call via a satellite (e.g., a GEO satellite) should also support the above two types of traffic. However, one issue is that the CP C-IoT optimization procedure (via NAS) , marked by the path 202 in FIG. 2, does not support different treatment between the voice (QCI1) and IMS signaling (QCI5) flows, whereas they have different priorities. Therefore, the following challenges may be identified.
[0074] How to create a control plane session for the transmission of IMS voice and IMS signaling data packets? How to enable end-to-end QoS to meet different scheduling priority for the IMS voice and IMS signaling traffic in case of the CP C-IoT optimization procedure? How can the MME (or AMF in 5G) become aware of the type of data traffic? How can the UE become aware of the traffic type for UL QoS? How can the RAN be made aware of the DL QoS based on the C-plane scenario?
[0075] Some example embodiments are described below using principles and terminology of LTE radio access technology without limiting the example embodiments to LTE radio access technology, however. For example, some example embodiments may also be applicable to 5G and 6G radio access technology (as well as beyond 6G) . Furthermore, some example embodiments are described below using IMS voice as an example of an IMS service. However, it should be noted that some example embodiments may also be applicable to any other IMS services.
[0076] Some example embodiments may relate to supporting, for example, IMS services (e.g., voice services) over NB-IoT using the control plane. To address the challenges mentioned above, some example embodiments may provide enhancements to the CP C-IoT optimization procedure at the UE, RAN, and MME (or AMF in 5G) to meet different QoS requirements (scheduling priorities) for IMS voice and IMS signaling traffic, for example. Some example embodiments may provide end-to-end QoS control for IMS voice services (or other IMS services) for example over NB-IoT, ensuring that both the IMS voice and signaling traffic are handled with the required priority (and guaranteed bit rate for IMS voice traffic) .
[0077] In some example embodiments, the MME (or AMF in 5G) may determine to trigger the establishment of end-to-end QoS control in CP C-IoT for IMS voice based on at least one of: the access type (e.g., in case of a GEO satellite) , the establishment cause, the access point name (APN) that the UE is requesting (if the destination APN is IMS) , or according to the UE’s capabilities advertised by the UE at the UE’s registration.
[0078] The IMS voice and / or signaling traffic (or other IMS traffic) may be carried over one or more signaling radio bearers (SRBs) , which may be mapped to one or more user plane flow identifiers. For example, one SRB may be dedicated for IMS voice traffic, and another SRB may be dedicated for IMS signaling traffic. The SRBs may also be configured with the appropriate QoS parameters (or requirements) . This may involve the MME 212 (or AMF) or RAN 104 or UE 100 mapping the user plane flow identifier (s) to the SRB (s) of different QoS.
[0079] SRBs are logical channels that may be used in mobile networks for transmitting control plane signaling messages between the UE 100 and the network. However, in some example embodiments, the SRBs may be used for carrying user plane traffic (e.g., IMS traffic) . The usage of the SRBs may be made transparent to the rest of the core network (e.g., the S-GW 214 and P-GW 215 in the EPC) . In other words, the S-GW 214 and the P-GW 215 do not need to be aware that the traffic on these user plane flow identifiers are actually carried over an SRB at the UE-network radio interface.
[0080] For example, the user plane flow identifiers may correspond to radio access bearer identifiers, such as E-UTRAN radio access bearer identifiers (E-RAB IDs) in an LTE network. The radio access bearer identifiers may be generated at the MME 212 (or AMF in 5G) . Alternatively, in 5G, the user plane flow identifiers may correspond to an association of a protocol data unit (PDU) session identifier with a QoS flow identifier generated by the SMF and relayed by the AMF. In other words, the user plane flow identifiers may be used to link a specific PDU session with its corresponding QoS flow.
[0081] A PDU session identifier is a unique identifier assigned to a PDU session, which is a logical connection between the UE 100 and the core network 110 for data transfer. The PDU session identifier helps in distinguishing between multiple PDU sessions that the UE 100 might have simultaneously.
[0082] A QoS flow identifier is used to differentiate between various QoS flows within a PDU session. Each QoS flow may have specific characteristics and requirements, such as latency and bandwidth, ensuring that different types of data (e.g., voice or video) receive appropriate handling and priority.
[0083] The NAS PDUs may comprise information about the user plane flow identifier that corresponds with a given IMS service. The data of the IMS services may be added or included in the NAS packets (i.e., NAS PDUs) .
[0084] In an example embodiment, the MME 212 (or AMF) may provide, to the RAN (e.g., eNB 104) , the QoS parameters for the establishment of the SRB dedicated for the IMS signaling and / or IMS voice traffic for the respective user plane flow identifier.
[0085] The RAN (e.g., eNB 104) may determine the configuration of the SRB dedicated for IMS voice and / or the SRB for IMS signaling traffic, and transmit an RRC request to the UE 100 to establish the respective dedicated SRB (s) , while mapping these SRB (s) to the user plane flow identifier (s) .
[0086] The UE 100 may establish the SRB dedicated for IMS voice and / or the SRB dedicated for IMS signaling traffic, and the MME 212 (or AMF) or the RAN (e.g., eNB 104) may map these SRB (s) to user plane flow identifier (s) .
[0087] For downlink traffic forwarding, the RAN (e.g., eNB 104) may transmit the NAS PDU including the downlink user plane traffic (e.g., IMS voice traffic or IMS signaling traffic) received from the S1-AP interface (from the MME 212) to the appropriate SRB dedicated for the IMS voice traffic or the SRB dedicated for the IMS signaling traffic. The RAN (e.g., eNB 104) may extend the DL NAS transport message transmitted from the MME 212 to include the evolved packet system (EPS) bearer identifier (ID) to help the RAN’s SRB selection. The UE 100 may route the received NAS packet (i.e., NAS PDU) with IMS voice or IMS signaling traffic to the appropriate application according to the user plane flow identifier (e.g., E-RAB ID) associated with the SRB over which the NAS packet was received.
[0088] For uplink traffic forwarding, the UE 100 may determine, at the NAS layer, the type of uplink traffic (e.g., IMS voice traffic or IMS signaling traffic) received from the application via the traffic flow template (TFT) . At the RRC layer, the UE 100 may determine over which SRB to transmit the NAS packet (i.e., NAS PDU) including the uplink user plane traffic (e.g., IMS voice or IMS signaling traffic) . The RAN (e.g., eNB 104) may extend the header of the UL NAS transport packet to include the EPS bearer ID, which may help the MME’s selection of the S11 bearer to transmit the IMS or voice packet too.
[0089] FIG. 3 illustrates an example of bearer mapping with SRB in an LTE network for the realization of QoS control via control plane for the transmission of user plane traffic (e.g., IMS voice and / or signaling traffic) . In FIG. 3, the path between the MME 212 and the P-GW 215 consists of an S11-U interface 302 between the MME 212 and the S-GW 214, and an S5-U interface 303 between the S-GW 214 and the P-GW 215.
[0090] An E-RAB 301 is a bearer service that provides the connection between the UE 100 and the EPC 110. The E-RAB 301 carries the user data and ensures that the data is transmitted with the required QoS. A given E-RAB 301 between the UE 100 and the MME 212 consists of one or more SRBs 304 (e.g., one SRB for IMS voice traffic and another SRB for IMS signaling traffic) between the UE 100 and the RAN (e.g., eNB 104) , and an S1-AP interface 305 between the RAN (e.g., eNB 104) and the MME 212.
[0091] An E-RAB ID is a unique identifier assigned to each E-RAB 301. The E-RAB IDs helps in distinguishing between multiple bearers that the UE 100 might have, ensuring that each data flow is managed according to its specific QoS requirements. For example, one E-RAB ID may be mapped to an SRB 304 used for IMS voice traffic, and another E-RAB ID may be mapped to another SRB 304 used for IMS signaling traffic.
[0092] An EPS bearer 306 is a logical channel that provides the path for data transfer between the UE 100 and the packet data network (PDN) within the EPC 110. The EPS bearer 306 ensures that data is transmitted with the required QoS. There may be one or more EPS bearers 306 (e.g., one for IMS voice traffic and another one for IMS signaling traffic) established between the UE 100 and the P-GW 215. A given EPS bearer 306 consists of an E-RAB 301 between the UE 100 and the MME 212, an S11-U interface 302 between the MME 212 and the S-GW 214, and an S5-U interface 303 between the S-GW 214 and the P-GW 215. The peer entity 300 in FIG. 3 may refer to the IMS.
[0093] The EPS bearer 306 for IMS signaling traffic may be established with an initial attach procedure (see FIG. 5) . The IMS 300 may trigger the P-GW 215 to establish the other EPS bearer for the IMS voice traffic (see FIG. 6) .
[0094] An EPS bearer ID is a unique identifier assigned to a given EPS bearer 306. The EPS bearer ID helps in distinguishing between multiple bearers that the UE 100 might have, ensuring that each data flow is managed according to its specific QoS requirements.
[0095] FIG. 4 illustrates an example flow of UL traffic at the UE 100 for IMS voice and signaling traffic via CP C-IoT. In FIG. 4, the second SRB 402 (denoted as SRB2 IMS-S) is an SRB dedicated for IMS signaling traffic. The third SRB 403 (denoted as SRB3 IMS-V) is another SRB dedicated for IMS voice traffic.
[0096] The NAS layer 410 at the UE 100 handles signaling between the UE 100 and the core network 110. The NAS layer 410 may manage functions such as mobility management, session management, and security control, ensuring that the UE 100 can maintain its connection and services with the network. The NAS-sig 411 refers to NAS signaling.
[0097] The RRC layer 400 is responsible for signaling between the UE 100 and the RAN (e.g., eNB 104) . The RRC layer 400 may manage the establishment, maintenance, and release of radio bearers, control the connection setup and release, as well as handle mobility within the RAN. The first SRB 401 (SRB1 NAS-SDoNAS) is a signaling radio bearer for the NAS signaling 411 and data over NAS (DoNAS) client 430.
[0098] For the UL transmission, after the establishment of the QoS control in CP C-IoT for IMS voice, the UE 100 may transmit the IMS signaling data packets for establishing the IMS session for the voice call and later start transmitting IMS voice data packets. The data packets from the UE application layer may be included as a payload of the NAS packet.
[0099] At the NAS layer 410, the UE 100 may map the IMS signaling and / or voice traffic to an EPS bearer based on the received TFT. The UE 100 may then identify the corresponding E-RAB ID from the EPS bearer ID. At the RRC layer 400, the UE 100 may then select the appropriate SRB 402, 403 based on the mapping between the EPS bearer ID and the E-RAB ID for transmitting the NAS PDU over the selected SRB 402, 403.
[0100] After the reception of the RRC message, the RAN (e.g., eNB 104) may provide the NAS PDU (NAS packet) to the MME 212 via an uplink NAS transport message, wherein the header of the S1-AP message transmitted from the RAN 104 to the MME 212 may include the respective E-RAB ID. Then the MME 212 may route the packet to the appropriate S11 bearer 302 (i.e., to the S-GW 214) according to the E-RAB ID. The S-GW 214 may then transmit the packet to the P-GW 215. The UE 100 may also include the EPS bearer ID within the EPS session management (ESM) payload for the MME 212 to identify or select the interface (e.g., S11-U tunnel 302) to the S-GW 214 in the UL direction.
[0101] For the DL transmission, once an IMS voice or IMS signaling packet arrives at the MME 212 from the S-GW 214, then the S11-U tunnel 302 over which the packet arrived may help the MME 212 to classify the packet as an IMS voice packet or an IMS signaling packet. Then the MME 212 may add the respective E-RAB ID (or indication of traffic type, e.g., IMS signaling or voice) into the S1-AP message transmitted from the MME 212 to the RAN (e.g., eNB 104) , so that the RAN 104 is able to transmit the NAS packet to the UE 100 via the appropriate SRB 402, 403.
[0102] At the UE 100, the RRC layer 400 may forward the received NAS packet to the NAS layer 410, which may the route the packet to the appropriate application (e.g., to the IMS client 420) according to the identified EPS bearer ID of the specific NAS PDU (NAS packet) .
[0103] As another option for the UL transmission, the UE 100 may indicate, in the header of the NAS PDU, the type of the message or traffic (e.g., indicating whether it is IMS voice or IMS signaling traffic) . This information may optionally be used by the MME 212 to route the data to the appropriate S11 bearer 302, as well as to help the lower layer at the UE 100 to forward the packet to the SRB. Then the RRC layer 400 at the UE 100 that receives a NAS PDU including IMS voice or signaling traffic may forward the NAS PDU to the appropriate SRB 402, 403, according to the traffic type indicated in the NAS header. After the reception of the RRC message, the RAN (e.g., eNB 104) may provide the NAS PDU to the MME 212 via an uplink NAS transport message. Based on the indicated NAS message type or the S1-AP message header information (e.g., indicated MME UE S1AP CP ID or traffic type) , the MME 212 may route the packet to the appropriate S11 bearer 302.
[0104] As another option for the DL transmission, the MME 212 may classify the packet as an IMS voice or IMS signaling packet according to the S11-U tunnel 302 on which the DL packet arrives. Alternatively, the MME 212 may associate the packet with an E-RAB ID or SRB ID to use over S1AP 305 towards the RAN (e.g., eNB 104) . The MME 212 may indicate, in the header of the NAS PDU, the type of the message or traffic (e.g., indicating whether it is IMS voice or IMS signaling traffic) . Alternatively, or additionally, the respective MME UE S1AP CP ID may be indicated in the header of the S1-AP message transmitted by the MME 212 to the RAN 104, so that the RAN 104 can route the NAS packet to the appropriate SRB 402, 403. At the UE 100, the RRC layer 400 may forward the packet to the NAS layer 410, which may route the packet to the appropriate application 420 according to the message type or traffic type indicated in the NAS PDU header.
[0105] FIG. 5 illustrates a signal flow diagram according to an example embodiment for initial attach with a default PDN connection (e.g., IMS PDN) . As illustrated in FIG. 5, at 501, a network node 104 of an access network (e.g., an eNB of a radio access network) broadcasts system information about supporting one or more IMS services via NB-IoT (i.e., the system information indicates that the network supports the one or more IMS services via NB-IoT) . For example, the one or more IMS services may comprise at least an IMS voice call service. In other words, the network node 104 may transmit a broadcast message (e.g., via the first SRB 401 or another dedicated system information block message) to inform UEs that the network supports CP C-IoT functionality that has been enhanced to transmit the one or more IMS services via CP C-IoT.
[0106] The network node 104 may provide or control a cell (e.g., an E-UTRAN cell of the eNB) for a public land mobile network (PLMN) that supports the CP C-IoT enhancement broadcasts. The network node 104 may be a base station onboard a satellite 106, in which case the access network may comprise a non-terrestrial network. Alternatively, the network node 104 may be a base station on the ground, in which case the access network may comprise a terrestrial network or a satellite that acts as a pure repeater of the signals generated for DL by the base station on the ground and generated for UL by the UE 100.
[0107] A UE 100 camping on the cell provided by the network node 104 receives the system information broadcast. The UE 100 determines whether it can connect to an MME 212, which supports PDN connectivity with voice support for NB-IoT. For example, the UE 100 may be an NB-IoT device, or any other type of UE such as a smartphone using NB-IoT when using a GEO orbit satellite to communicate with the network.
[0108] At 502, the UE 100 transmits, to the network node 104, a service request (or attach request) for the one or more IMS services (e.g., for the IMS voice service) . In the RRC connection establishment signaling associated with the attach request, the UE 100 may indicate its support for the CP C-IoT EPS optimization with voice support for NB-IoT (this may be relevant for the MME selection at 503) .
[0109] When creating the UE NAS PDN connection Request, if the UE 100 desires to benefit from IMS voice over GEO optimization, the UE 100 may indicate “Control Plane CIoT EPS Optimization supported” in the “Preferred Network Behaviour” . The UE 100 may include an ESM message container, which contains the PDN connection session establishment request. If the UE supports IMS voice, the PDN connection session establishment request may comprise the IMS APN and possibly the PDN type (e.g., IPv4, IPv6, IPv4v6, or non-IP) . ESM is a control plane function that supports signaling for PDN session management, such as EPS bearer activation and modification.
[0110] At 503, the network node 104 of the access network selects the MME 212 based on control plane optimization support and voice support for NB-IoT.
[0111] At 504, the MME 212 carries out identification, authentication and security mode procedures associated with the UE 100.
[0112] At 505, the MME 212 checks for the subscription with the HSS 211 and checks whether the UE 100 has requested for IMS related PDN connection, and whether the RAN access RAT type is NB-IoT via GEO, and whether the UE 100 supports CP C-IoT EPS optimization with voice support for NB-IoT. Based on the checking, the MME 212 determines whether CP C-IoT EPS optimization with voice support for NB-IoT is to apply for the PDN connection. The MME 212 selects an S-GW 214 and a P-GW 215 that supports CP C-IoT EPS optimization with voice support for NB-IoT. The S-GW 214 may, depending on the deployment, need to support a GPRS tunneling protocol user plane (GTP-u) tunnel not directed to the RAN IP address space but to the MME IP address space. GPRS is an abbreviation for the general packet radio service.
[0113] At 506, the MME 212 transmits a Create Session Request message (e.g., including an international mobile subscriber identity (IMSI) of the UE 100, mobile station international subscriber directory number (MSISDN) , MME tunnel end identifier (TEID) for control plane, P-GW address, PDN address, APN, RAT type, etc. ) to the S-GW 214. If the CP C-IoT EPS optimization applies (is supported) , then the MME 212 may also indicate S11-U tunneling of NAS user data and transmit its own S11-U IP address and MME DL TEID for DL data forwarding by the S-GW 214. If the MME 212 determines that the PDN connection shall only use the CP C-IoT EPS optimization (e.g., based on a capability indication from the UE 100) , the MME 212 may include a “Control Plane Only PDN Connection Indicator” in the Create Session Request (the use of this indicator is referred to in the example embodiment of FIG. 6) .
[0114] At 507, based on the received Create Session Request message, the S-GW 214 creates a new entry in its EPS bearer table and transmits a Create Session Request message (e.g., including the S-GW address for the user plane, S-GW TEID of the user plane, S-GW TEID of the control plane, EPS bearer Identity, and / or protocol configuration options) to the P-GW 215.
[0115] At 508, based on the received Create Session Request message, the P-GW 215 performs an IP connectivity access network (IP-CAN) Session Establishment procedure (e.g., as defined in TS 23.203 and TS 23.401 § 5.3.2.1 step 14) .
[0116] At 509, the P-GW 215 returns a Create Session Response message (e.g., including the P-GW address for the user plane, P-GW TEID of the user plane, P-GW UL TEID of the control plane, EPS bearer identity, EPS bearer QoS, and / or protocol configuration options) to the S-GW 214.
[0117] At 510, the S-GW 214 returns a Create Session Response message (e.g., including the PDN type, PDN address, S-GW address for the user plane, S-GW TEID for the user plane, S-GW TEID for the control plane, EPS bearer identity, EPS bearer QoS, and / or protocol configuration options) to the MME 212. The S-GW 214 may determine a fully qualified tunnel endpoint identifier (F-TEID) to receive UL user plane traffic associated with the default EPS bearer being created. For this purpose, the S-GW 214 may check if the data transfer on the PDN connection is “Control plane only” (based on the information received at 506) to determine whether the IP address to use is for an S11 interface (with the network node 104) or an S4 interface (with the MME 212) .
[0118] At 511, after receiving the Create Session Response message from the S-GW 214, the MME 212 generates and transmits, to the network node 104, a message comprising at least one of: a request for establishing one or more SRBs for a data session of the UE 100, or one or more QoS requirements for establishing the one or more SRBs for the data session of the UE 100. Herein, user plane traffic is to be transmitted over the one or more SRBs (i.e., the one or more SRBs carry user plane traffic) . The message may be generated and transmitted based on the service request (attach request) received from the UE 100 at 502. The network node 104 receives the message.
[0119] In this example embodiment, the one or more signaling radio bearers may comprise a signaling radio bearer for carrying IMS signaling traffic associated with the IMS voice call service.
[0120] The MME 212 may map a user plane flow identifier to the SRB dedicated for the IMS signaling traffic, and transmit, to the network node 104 (e.g., in the message) , information indicating the mapping. The user plane flow identifier may correspond to or comprise a radio access bearer identifier (e.g., E-RAB ID or EPS bearer ID) .
[0121] For example, the MME 212 may transmit an E-RAB SETUP REQUEST or a DL NAS TRANSPORT message to trigger the network node 104 (i.e., RAN) to create an additional SRB per E-RAB ID as per provided QoS. The E-RAB SETUP REQUEST or DL NAS TRANSPORT message may include the QoS profile for the dedicated EPS bearer identified by the EPS bearer ID or E-RAB ID, and an indication that this EPS bearer ID or E-RAB ID is to be mapped to the SRB. The E-RAB SETUP REQUEST or DL NAS TRANSPORT message may include an attach accept with ESM (PDN connection establishment) success to the UE 100.
[0122] At 512, the network node 104 determines, based on the message received from the MME 212, a configuration for establishing the SRB dedicated for carrying the IMS signaling traffic with the required QoS, and the network node 104 transmits the configuration to the UE 100. For example, the network node 104 may transmit an RRC Connection Reconfiguration message to the UE 100, including an SRB configuration to be associated with the E-RAB ID. The UE 100 receives the configuration.
[0123] The configuration may comprise, for example, at least one of the following parameters: a logical channel identifier, priority, logical channel group, radio link control (RLC) mode, or maximum retransmission threshold.
[0124] The logical channel identifier is a unique identifier for a logical channel, which helps in distinguishing between different channels used for data transmission. The logical channel identifier identifies the specific logical channel used for the SRB, ensuring that the data packets are correctly routed.
[0125] The priority is a parameter that defines the importance of the SRB compared to one or more other bearers.
[0126] The logical channel group comprises multiple logical channels that are grouped together, allowing for efficient management and scheduling of data transmission.
[0127] The RLC mode defines the mode of operation for the RLC layer, such as acknowledged mode (AM) , unacknowledged mode (UM) , or transparent mode (TM) , affecting how data is handled and error correction is performed. For example, the RLC mode may define how the RLC layer handles SRB data, including error correction and retransmission strategies.
[0128] The maximum retransmission threshold sets the maximum number of times a data packet can be retransmitted on the SRB, thus balancing reliability and efficiency.
[0129] At 513, the UE 100 establishes the SRB for the IMS signaling traffic based on the configuration received from the network node 104.
[0130] At 514, the UE 100 transmits a response message (e.g., an RRC Connection Reconfiguration Complete message) to the network node 104 to confirm the establishment of the SRB dedicated for the IMS signaling traffic with QoS.
[0131] At 515, the network node 104 transmits, to the UE 100, a DL NAS PDU message received from the MME 212 at step 511. This DL NAS PDU message may include the attach accept with ESM (PDN connection establishment) success to the UE 100. The DL NAS PDU of 515 may indicate an association of one or more application traffic filters (e.g., the IMS signaling traffic possibly identified based on the P-CSCF IP address) with the user plane flow identifier (e.g., E-RAB ID or EPS bearer ID) .
[0132] At 516, after the establishment of the control plane path, the UE 100 may transmit IMS signaling traffic to the MME 212 via the network node 104, and / or receive IMS signaling traffic from the MME 212 via the network node 104. The IMS signaling traffic may be included in a NAS PDU (different from the NAS PDU of 515) .
[0133] For UL traffic, based on the user plane flow identifier associated with one or more application traffic filters, the UE 100 may route the user plane traffic (e.g., IMS signaling traffic) to be transmitted to the network node 104 onto the signaling radio bearer established for the IMS signaling traffic. The MME 212 may route the IMS signaling traffic received from the network node 104 to the P-GW 215 (via the S-GW 214) , which is then transmitted to the IMS.
[0134] For DL traffic, the MME 212 may receive the IMS signaling traffic from the P-GW 215 via the S-GW 214, and then route it to the UE 100 via the network node 104.
[0135] For example, the MME 212 may transmit, to the network node 104, an additional message comprising a user plane data packet (e.g., an IMS signaling data packet) to be transmitted to the UE 100 via the signaling radio bearer established for the IMS signaling traffic. The user plane data packet of the additional message may be associated with the user plane flow identifier corresponding to the IMS signaling traffic (or corresponding to the SRB established for the IMS signaling traffic) . This user plane flow identifier may be included or indicated in the additional message (such as DOWNLINK NAS TRANSPORT) used by the MME 212 to request the network node 104 to transmit to the UE 100 IMS signaling traffic received from the P-GW 215 via the S-GW 214. In other words, in the additional message, the MME 212 may indicate, to the network node 104, which signaling radio bearer to use for transmitting the user plane data packet of the additional message to the UE 100.
[0136] The network node 104 may receive multiple instances of the additional message (such as DOWNLINK NAS TRANSPORT) used by the MME 212 to request the network node 104 to transmit to the UE 100 IMS signaling traffic received from the P-GW 215 via the S-GW 214. Based on the user plane flow identifier of the additional message, the network node 104 may transmit the user plane data packet of the additional messages to the UE 100 over the signaling radio bearer established for the IMS signaling traffic.
[0137] The signaling radio bearer established for the IMS signaling traffic may also be referred to as a first signaling radio bearer herein, and the user plane flow identifier corresponding to the IMS signaling traffic (or corresponding to the first signaling radio bearer) may be referred to as a first user plane flow identifier herein.
[0138] The mechanism described here is independent of whether the network node (e.g., eNB) 104 is physically located on a GEO satellite or is deployed on the ground and the GEO satellite is used as a mere radio relay.
[0139] The mechanisms described in FIG. 5 and FIG. 6 may apply equally when the P-GW 215 corresponds to a combination of SMF+P-GW as defined for 5GC-EPC interworking in 3GPP TS 23.501.
[0140] FIG. 6 illustrates a signal flow diagram according to an example embodiment for establishing a dedicated SRB for IMS voice traffic. The signaling illustrated in FIG. 6 may be performed after performing the signaling of FIG. 5 (i.e., after the SRB for the IMS signaling traffic has been established) .
[0141] Referring to FIG. 6, at 601, when an IMS voice call is being established for the UE 100, the IMS 300 requests an IP-CAN session modification to the policy and charging rules function (PCRF) 500 or policy control function (PCF) .
[0142] At 602, the PCRF 500 or PCF transmits a policy and charging control (PCC) decision provision (QoS policy) message to the P-GW 215.
[0143] At 603, the P-GW 215 uses this QoS policy to assign the EPS bearer QoS. That is, the P-GW 215 assigns the values to the bearer level QoS parameters: QoS class identifier (QCI) , allocation and retention priority (ARP) , guaranteed bit rate (GBR) and / or maximum bit rate (MBR) . The P-GW 215 transmits a Create Bearer Request message (e.g., including IMSI, procedure transaction ID (PTI) , EPS bearer QoS, maximum packet loss rate for UL and DL, TFT, S5 / S8 TEID, and / or protocol configuration options) to the S-GW 214. The linked EPS bearer identity (LBI) may be the EPS bearer identity of the default bearer (described in the example embodiment of FIG. 5) . For a QCI=1 bearer, the maximum packet loss rate (for UL and DL) may be provided by the P-GW 215 as described in TS 23.203.
[0144] At 604, the S-GW 214 determines a corresponding F-TEID (to receive UL user plane traffic associated with the dedicated EPS bearer being created) . For this purpose, the S-GW 214 may check if the data transfer on the PDN connection is set to “Control only” mode (information received during the default PDU creation, as explained in the example embodiment of FIG. 5) to determine whether the IP address to use is for an S11 interface (with the network node 104) or an S4 interface (with the MME 212) .
[0145] At 605, the S-GW 214 transmits the Create Bearer Request message (e.g., including IMSI, EPS Bearer QoS, Maximum Packet Loss Rate (UL, DL) , TFT, S11-TEID, PDN GW TEID (GTP-based S5 / S8) , LBI, and / or Protocol Configuration Options) to the MME 212. If the UE 100 is in EPC connection management (EPC) idle state, the MME 212 may trigger the Network Triggered Service Request from 603 (which is specified in clause 5.3.4.3 in TS 23.401) . In that case, the following operations 604 to 607 may be combined into a “Network Triggered Service Request” procedure or be performed stand-alone. The MME 212 may check if the UE 100 supports the establishment of an additional user plane radio bearer based on the maximum number of user plane radio bearers indicated by the UE 100 in the UE Network Capability information element and along with the UE capability indicating voice support (as explained in the example embodiment of FIG. 5) .
[0146] In other words, the MME 212 receives, from the S-GW 214 (i.e., from a network entity serving the data session of the UE 100) , a request for establishing a signaling radio bearer for carrying the IMS voice traffic associated with the IMS voice call service.
[0147] At 606, based on the request received from the S-GW 214, the MME 212 generates and transmits, to the network node 104, a message comprising at least one of: a request for establishing an additional SRB for the data session of the UE 100 (e.g., for the IMS voice traffic) , or one or more QoS requirements for establishing the additional SRB for the data session of the UE 100.
[0148] The MME 212 may map a user plane flow identifier to the additional SRB, and transmit, to the network node 104 (e.g., in the message) , information indicating the mapping. For example, the user plane flow identifier may correspond to or comprise a radio access bearer identifier (e.g., E-RAB ID or EPS bearer ID) .
[0149] For example, the MME 212 may select an EPS bearer ID, which has not yet been assigned to the UE 100. The MME 212 may then build a Session Management Request message including the TFT (application traffic filters) , EPS bearer QoS parameters (excluding ARP) , protocol configuration options, the EPS bearer identity, and / or the linked EPS bearer identity (LBI) . The MME 212 may transmit the Bearer Setup Request message (e.g., including the EPS bearer identity, EPS bearer QoS, and / or Session Management Request) to the network node 104 without including any information related to S1-U tunnel details (indicating that the corresponding traffic is to be transmitted over the S1AP interface) .
[0150] As another example, the MME 212 may at 606 transmit a DL NAS transport message (instead of a Bearer Setup Request message) to the network node 104 (e.g., including EPS bearer identity, LBI, and / or E-RAB ID) .
[0151] At 607, the network node 104 determines, based on the message received from the MME 212, a configuration for establishing the additional SRB dedicated for carrying the IMS voice traffic with the required QoS, and the network node 104 transmits the configuration to the UE 100. For example, the network node 104 may transmit an RRC Connection Reconfiguration message to the UE 100, including the SRB configuration to be associated with the E-RAB ID. The UE 100 receives the configuration.
[0152] For example, the network node 104 may map the EPS bearer QoS to the SRB QoS. The network node 104 may then transmit the RRC Connection Reconfiguration message (e.g., including radio bearer QoS, Session Management Request, and / or EPS bearer identity) to the UE 100, indicating also the mapping between the user plane flow identifier (e.g., EPS bearer identity) and the additional SRB. The UE 100 may store the QoS Negotiated received in the Session Management Request. The NAS layer at the UE 100 may store the user plane flow identifier (e.g., EPS bearer identity) and link the dedicated bearer to the default bearer indicated by the linked EPS bearer identity (LBI) . The UE 100 may use the uplink packet filter (UL TFT) to determine the mapping of traffic flows to the additional SRB. The UE 100 may provide the EPS bearer QoS parameters to the application handling the traffic flow. The application usage of the EPS bearer QoS may depend on the specific implementation.
[0153] At 608, the UE 100 establishes the additional SRB for the IMS voice traffic based on the configuration received from the network node 104.
[0154] At 609, the UE 100 transmits a response message (e.g., an RRC Connection Reconfiguration Complete message) to the network node 104 to confirm the establishment or activation of the additional SRB dedicated for the IMS voice traffic.
[0155] At 610, the network node 104 acknowledges the SRB activation to the MME 212, for example with a Bearer Setup Response (EPS Bearer Identity) message. The network node 104 may indicate whether the requested EPS bearer QoS could be allocated or not.
[0156] As another example, the network node 104 may transmit an UL NAS transport message (instead of the Bearer Setup response message) , if a DL NAS transport message was used at 606.
[0157] At 610, the MME 212 may be prepared to receive this message either before or after the Session Management Response message (transmitted in operation 612) . The NAS layer at the UE 100 may build a Session Management Response message including the EPS bearer identity. The UE 100 may then transmit a Direct Transfer (Session Management Response) message to the network node 104.
[0158] At 612, the network node 104 transmits an Uplink NAS Transport message (Session Management Response) message to the MME 212 indicating the E-RAB ID.
[0159] At 613, upon reception of the Bearer Setup Response message of 610 and the Session Management Response message of 612, the MME 212 acknowledges the bearer activation to the S-GW 214 by transmitting a Create Bearer Response message (e.g., including the EPS bearer identity, and / or S11-TEID) to the S-GW 214.
[0160] At 614, the S-GW 214 acknowledges the bearer activation to the P-GW 215 by transmitting a Create Bearer Response message (e.g., including the EPS bearer identity, and / or S5 / S8-TEID) .
[0161] At 615, if the dedicated bearer activation procedure was triggered by a PCC Decision Provision message from the PCRF, the P-GW 215 may indicate, to the PCRF, whether the requested PCC decision (QoS policy) could be enforced or not, allowing the completion of the PCRF-Initiated IP CAN Session Modification procedure or the PCRF-initiated IP-CAN Session Modification procedure (as defined in TS 23.203) , after the completion of IP CAN bearer signaling.
[0162] At 616, the UE 100 may start transmitting and / or receiving IMS service data packets (e.g., IMS voice traffic) via the CP C-IoT path that was created.
[0163] For example, the UE 100 may determine a type of uplink traffic received from an application (e.g., from the IMS client 420) . Based on the determination of the type of the uplink traffic (e.g., based on determining that it is IMS voice traffic based on TFT (application traffic filters in the Session Management Request message) , created by the MME 212 at 606) , the UE 100 may select a signaling radio bearer from the one or more signaling radio bearers (e.g., the UE 100 may select the additional SRB established for the IMS voice traffic) . The UE 100 may then transmit a user plane data packet (e.g., an IMS voice data packet) of the uplink traffic to the network node 104 via the signaling radio bearer selected.
[0164] The network node 104 may receive the user plane data packet from the UE 100 over the additional SRB established for the IMS voice traffic. The network node 104 may transmit, to the MME 212, a further message comprising the user plane data packet received from the UE 100, and the user plane flow identifier (e.g., E-RAB ID or EPS bearer ID) associated with the additional signaling radio bearer over which the user plane data packet was received from the UE 100. The network node 104 may determine the user plane flow identifier of the additional signaling radio bearer based on the mapping that was obtained previously. The further message comprising the user plane data packet received from the UE 100 may correspond to an UPLINK NAS TRANSPORT message, for example.
[0165] Based on the user plane flow identifier comprised in the further message, the MME 212 may select the data session of the UE 100 and an interface (e.g., the S11-U interface 302 to the S-GW 214) . The MME 212 may transmit the content of the user plane data packet to a network entity (e.g., to the S-GW 214) serving the data session of the UE 100 over the interface that is selected.
[0166] Alternatively, or additionally, the MME 212 may transmit, to the network node 104, an additional message (e.g., DOWNLINK NAS TRANSPORT) comprising a user plane data packet (e.g., an IMS voice data packet) to be transmitted to the UE 100 in the downlink via the additional signaling radio bearer. The user plane data packet of the additional message may be associated with the user plane flow identifier corresponding to the additional signaling radio bearer established for the IMS voice traffic. This user plane flow identifier may be included or indicated in the additional message. In other words, in the additional message, the MME 212 may indicate, to the network node 104, which signaling radio bearer to use for transmitting the user plane data packet of the additional message to the UE 100. Based on the user plane flow identifier, the network node 104 may transmit or forward the downlink user plane data packet to the UE 100 via the additional signaling radio bearer. The UE 100 may receive the downlink user plane data packet from the network node 104 via the additional signaling radio bearer.
[0167] The additional signaling radio bearer established for the IMS voice traffic may also be referred to as a second signaling radio bearer herein, and the user plane flow identifier corresponding to the IMS voice traffic (or corresponding to the second signaling radio bearer) may be referred to as a second user plane flow identifier herein.
[0168] Although LTE terminology is used above in the example embodiments of FIGS. 5 and 6, it should be noted that the example embodiments of FIGS. 5 and 6 may be applied to 5G and 6G networks as well. In case of 5G, the eNB 104 corresponds to a gNB, the MME corresponds to an AMF, the S-GW corresponds to an intermediate SMF (I-SMF) , the P-GW corresponds to an anchor SMF coupled with an UPF, the PDN session procedure corresponds to a PDU session procedure, the APN corresponds to a data network name (DNN) , the E-RAB corresponds to a data radio bearer (DRB) , and the QCI corresponds to 5G QoS identifier (5QI) .
[0169] FIG. 7 illustrates a flow chart according to an example embodiment of a method A1 (e.g., a computer-implemented method) for establishing one or more signaling radio bearers for a data session of a user equipment. The method A1 may be performed by an apparatus 1000 depicted in FIG. 10. For example, the apparatus 1000 may be, or comprise, or be comprised in, the user equipment (UE) 100, 102.
[0170] According to a first aspect, the method A1 comprises: receiving, from a network node of an access network, a configuration for establishing one or more signaling radio bearers for a data session for the user equipment; and establishing the one or more signaling radio bearers based on the configuration, wherein the one or more signaling radio bearers carry user plane traffic.
[0171] According to a second aspect, there is provided the method A1 of the first aspect, wherein the configuration received from the network node indicates a mapping between one or more user plane flow identifiers and at least one of: the one or more signaling radio bearers, or one or more quality of service requirements for establishing the one or more signaling radio bearers.
[0172] According to a third aspect, there is provided the method A1 of the first or second aspect, further comprising: receiving a non-access stratum protocol data unit from the network node, wherein the non-access stratum protocol data unit indicates an association of one or more application traffic filters with a user plane flow identifier; and routing the user plane traffic to be transmitted to the network node onto a signaling radio bearer of the one or more signaling radio bearers based on the user plane flow identifier.
[0173] According to a fourth aspect, there is provided the method A1 of the first or second aspect, further comprising: determining a type of uplink traffic received from an application; selecting, based on the determination of the type of the uplink traffic, a signaling radio bearer from the one or more signaling radio bearers; and transmitting a user plane data packet of the user plane traffic to the network node via the signaling radio bearer that is selected.
[0174] According to a fifth aspect, there is provided the method A1 of the first or second aspect, further comprising: inserting, into a header of another message carrying one or more user plane data packets, an indication indicating a type of traffic associated with the one or more user plane data packets; and determining, at a radio resource control layer of the user equipment, based on the header, a signaling radio bearer of the one or more signaling radio bearers to forward the one or more user plane data packets to.
[0175] According to a sixth aspect, there is provided the method A1 of any preceding aspect, wherein the user plane traffic is associated with one or more internet protocol multimedia subsystem services.
[0176] According to a seventh aspect, there is provided the method A1 of the sixth aspect, wherein the one or more internet protocol multimedia subsystem services comprise at least an internet protocol multimedia subsystem voice call service, wherein the one or more signaling radio bearers comprise at least: a first signaling radio bearer for carrying signaling traffic associated with the internet protocol multimedia subsystem voice call service, and a second signaling radio bearer for carrying voice traffic associated with the internet protocol multimedia subsystem voice call service.
[0177] According to an eighth aspect, there is provided the method A1 of the sixth or seventh aspect, further comprising: receiving, from the network node, system information about supporting the one or more internet protocol multimedia subsystem services via a narrowband internet of things radio technology; and transmitting, to a core network function, via the network node, based on receiving the system information, a service request for the one or more internet protocol multimedia subsystem services.
[0178] FIG. 8 illustrates a flow chart according to an example embodiment of a method A2 (e.g., a computer-implemented method) for establishing one or more signaling radio bearers for a data session of a user equipment. The method A2 may be performed by an apparatus 1100 depicted in FIG. 11. For example, the apparatus 1100 may be, or comprise, or be comprised in, a network node 104, 106 of an access network.
[0179] According to a ninth aspect, the method A2 comprises: receiving, from a core network function, a message comprising at least one of: a request for establishing one or more signaling radio bearers for a data session for a user equipment, and one or more quality of service requirements for the one or more signaling radio bearers for the data session for the user equipment; determining, based on the message, a configuration for establishing the one or more signaling radio bearers; and transmitting the configuration to the user equipment for establishing the one or more signaling radio bearers, wherein the one or more signaling radio bearers carry user plane traffic.
[0180] According to a tenth aspect, there is provided the method A2 of the ninth aspect, further comprising: receiving, from the core network function, information indicating a mapping between one or more user plane flow identifiers and at least one of: the one or more signaling radio bearers, or the one or more quality of service requirements, wherein the configuration transmitted to the user equipment indicates the mapping.
[0181] According to an eleventh aspect, there is provided the method A2 of the ninth aspect, further comprising: mapping one or more user plane flow identifiers to at least one of: the one or more signaling radio bearers, or the one or more quality of service requirements.
[0182] According to a twelfth aspect, there is provided the method A2 of the tenth or eleventh aspect, wherein each of the one or more user plane flow identifiers corresponds to a radio access bearer identifier, or to an association of a protocol data unit session identifier with a quality of service flow identifier.
[0183] According to a thirteenth aspect, there is provided the method A2 of any of the ninth to twelfth aspects, further comprising: receiving, from the core network function, a non-access stratum protocol data unit to be transmitted to the user equipment, wherein the non-access stratum protocol data unit indicates an association of one or more application traffic filters with a user plane flow identifier; and transmitting the non-access stratum protocol data unit to the user equipment.
[0184] According to a fourteenth aspect, there is provided the method A2 of any of the ninth to thirteenth aspects, further comprising: receiving a user plane data packet of the user plane traffic from the user equipment over a signaling radio bearer of the one or more signaling radio bearers; and transmitting, to the core network function, a further message comprising the user plane data packet received from the user equipment, and a user plane flow identifier associated with the signaling radio bearer over which the user plane data packet was received from the user equipment.
[0185] According to a fifteenth aspect, there is provided the method A2 of any of the ninth to fourteenth aspects, wherein the user plane traffic is associated with one or more internet protocol multimedia subsystem services.
[0186] According to a sixteenth aspect, there is provided the method A2 of the fifteenth aspect, wherein the one or more internet protocol multimedia subsystem services comprise at least an internet protocol multimedia subsystem voice call service, wherein the one or more signaling radio bearers comprise at least: a first signaling radio bearer for carrying signaling traffic associated with the internet protocol multimedia subsystem voice call service, and a second signaling radio bearer for carrying voice traffic associated with the internet protocol multimedia subsystem voice call service.
[0187] According to a seventeenth aspect, there is provided the method A2 of the fifteenth or sixteenth aspect, further comprising: broadcasting system information about supporting the one or more internet protocol multimedia subsystem services via a narrowband internet of things radio technology.
[0188] FIG. 9 illustrates a flow chart according to an example embodiment of a method A3 (e.g., a computer-implemented method) for establishing one or more signaling radio bearers for a data session of a user equipment. The method A3 may be performed by an apparatus 1200 depicted in FIG. 12. For example, the apparatus 1200 may be, or comprise, or be comprised, a core network function (e.g., MME or AMF) of the core network 110.
[0189] According to an eighteenth aspect, the method A3 comprises: generating a message comprising at least one of: a request for a network node of an access network to establish one or more signaling radio bearers for a data session for a user equipment, and one or more quality of service requirements for the one or more signaling radio bearers for the data session for the user equipment; and transmitting the message to the network node of the access network, wherein the one or more signaling radio bearers carry user plane traffic.
[0190] According to a nineteenth aspect, there is provided the method A3 of the eighteenth aspect, further comprising: mapping one or more user plane flow identifiers to at least one of: the one or more signaling radio bearers, or the one or more quality of service requirements; and transmitting, to the network node, information indicating the mapping.
[0191] According to a twentieth aspect, there is provided the method A3 of the nineteenth aspect, wherein each of the one or more user plane flow identifiers corresponds to a radio access bearer identifier, or to an association of a protocol data unit session identifier with a quality of service flow identifier.
[0192] According to a twenty-first aspect, there is provided the method A3 of any of the eighteenth to twentieth aspects, further comprising: transmitting, via the network node, a non-access stratum protocol data unit to be transmitted to the user equipment, wherein the non-access stratum protocol data unit indicates an association of one or more application traffic filters with a user plane flow identifier.
[0193] According to a twenty-second aspect, there is provided the method A3 of any of the eighteenth to twenty-first aspects, further comprising: receiving, from the network node, a further message comprising a user plane data packet of the user traffic received from the user equipment, and a user plane flow identifier associated with a signaling radio bearer over which the user plane data packet was received from the user equipment; selecting the data session of the user equipment and an interface, based on the user plane flow identifier comprised in the further message; and transmitting, over the interface that is selected, the content of the user plane data packet to a network entity serving the data session of the user equipment.
[0194] According to a twenty-third aspect, there is provided the method A3 of any of the eighteenth to twenty-second aspects, wherein the access network comprises a non-terrestrial network.
[0195] According to a twenty-fourth aspect, there is provided the method A1, A2 or A3 of any preceding aspect, wherein the user equipment is a narrowband internet of things device.
[0196] According to a twenty-fifth aspect, there is provided the method A3 of any of the eighteenth to twenty-fourth aspects, wherein the user plane traffic is associated with one or more internet protocol multimedia subsystem services.
[0197] According to a twenty-sixth aspect, there is provided the method A3 of the twenty-fifth aspect, wherein the one or more internet protocol multimedia subsystem services comprise at least an internet protocol multimedia subsystem voice call service, wherein the one or more signaling radio bearers comprise at least one of: a first signaling radio bearer for carrying signaling traffic associated with the internet protocol multimedia subsystem voice call service, or a second signaling radio bearer for carrying voice traffic associated with the internet protocol multimedia subsystem voice call service.
[0198] According to a twenty-seventh aspect, there is provided the method A3 of the twenty-sixth aspect, further comprising: transmitting, to the network node, an additional message comprising a user plane data packet to be transmitted to the user equipment via a signaling radio bearer of the one or more signaling radio bearers, wherein the user plane data packet of the additional message is associated with one of: a first user plane flow identifier corresponding to the signaling traffic, or a second user plane flow identifier corresponding to the voice traffic.
[0199] According to a twenty-eighth aspect, there is provided the method A3 of any of the twenty-fifth to twenty-seventh aspects, further comprising: receiving, from the user equipment, a service request for the one or more internet protocol multimedia subsystem services, wherein the message is generated and transmitted based on receiving the service request.
[0200] According to a twenty-ninth aspect, there is provided the method A3 of the twenty-sixth or twenty-seventh aspect, further comprising: receiving, from a network entity serving the data session of the user equipment, a request for establishing the second signaling radio bearer for carrying the voice traffic associated with the internet protocol multimedia subsystem voice call service, wherein the message is generated and transmitted based on receiving the request from the network entity serving the data session.
[0201] According to another aspect, there is provided an apparatus 1000 comprising means for causing the apparatus 1000 to perform at least the method A1 of any of the first to eighth aspects.
[0202] According to another aspect, there is provided an apparatus 1100 comprising means for causing the apparatus 1100 to perform at least the method A2 of any of the ninth to seventeenth aspects.
[0203] According to another aspect, there is provided an apparatus 1200 comprising means for causing the apparatus 1200 to perform at least the method A3 of any of the eighteenth to twenty-ninth aspects.
[0204] According to another aspect, there is provided an apparatus 1000 comprising at least one processor 1010, and at least one memory 1020 storing instructions that, when executed by the at least one processor 1010, cause the apparatus 1000 to perform at least the method A1 of any of the first to eighth aspects.
[0205] According to another aspect, there is provided an apparatus 1100 comprising at least one processor 1110, and at least one memory 1120 storing instructions 1122 that, when executed by the at least one processor 1110, cause the apparatus 1100 to perform at least the method A2 of any of the ninth to seventeenth aspects.
[0206] According to another aspect, there is provided an apparatus 1200 comprising at least one processor 1210, and at least one memory 1220 storing instructions 1222 that, when executed by the at least one processor 1210, cause the apparatus 1200 to perform at least the method A3 of any of the eighteenth to twenty-ninth aspects.
[0207] According to another aspect, there is provided a computer program or a computer-readable medium (e.g., a non-transitory computer-readable medium) comprising instructions which, when executed by an apparatus 1000, cause the apparatus 1000 to perform at least the method A1 of any of the first to eighth aspects.
[0208] According to another aspect, there is provided a computer program or a computer-readable medium (e.g., a non-transitory computer-readable medium) comprising instructions which, when executed by an apparatus 1100, cause the apparatus 1100 to perform at least the method A2 of any of the ninth to seventeenth aspects.
[0209] According to another aspect, there is provided a computer program or a computer-readable medium (e.g., a non-transitory computer-readable medium) comprising instructions which, when executed by an apparatus 1200, cause the apparatus 1200 to perform at least the method A3 of any of the eighteenth to twenty-ninth aspects.
[0210] The blocks, related functions, and information exchanges (messages) described above by means of FIGS. 5 to 9 are in no absolute chronological order, and some of them may be performed simultaneously or in an order differing from the described one. Other functions can also be executed between them or within them, and other information may be sent, and / or other rules applied. Some of the blocks or part of the blocks or one or more pieces of information can also be left out or replaced by a corresponding block or part of the block or one or more pieces of information.
[0211] FIG. 10 illustrates an example of an apparatus 1000 comprising means for performing one or more of the example embodiments described above. For example, the apparatus 1000 may be an apparatus such as, or comprising, or comprised in, a user equipment (UE) 100, 102.
[0212] The apparatus 1000 may comprise a circuitry or a chipset applicable for realizing one or more of the example embodiments described above. For example, the apparatus 1000 may comprise at least one processor 1010. The at least one processor 1010 interprets instructions (e.g., computer program instructions) and processes data. The at least one processor 1010 may comprise one or more programmable processors. The at least one processor 1010 may comprise programmable hardware with embedded firmware and may, alternatively or additionally, comprise one or more application-specific integrated circuits (ASICs) .
[0213] The at least one processor 1010 is coupled to at least one memory 1020. The at least one processor is configured to read and write data to and from the at least one memory 1020. The at least one memory 1020 may comprise one or more memory units. The memory units may be volatile or non-volatile. It is to be noted that there may be one or more units of non-volatile memory and one or more units of volatile memory or, alternatively, one or more units of non-volatile memory, or, alternatively, one or more units of volatile memory. Volatile memory may be for example random-access memory (RAM) , dynamic random-access memory (DRAM) or synchronous dynamic random-access memory (SDRAM) . Non-volatile memory may be for example read-only memory (ROM) , programmable read-only memory (PROM) , electronically erasable programmable read-only memory (EEPROM) , flash memory, optical storage or magnetic storage. In general, memories may be referred to as non-transitory computer readable media. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) . The at least one memory 1020 stores computer readable instructions that are executed by the at least one processor 1010 to perform one or more of the example embodiments described above. For example, non-volatile memory stores the computer readable instructions, and the at least one processor 1010 executes the instructions using volatile memory for temporary storage of data and / or instructions. The computer readable instructions may refer to computer program code.
[0214] The computer readable instructions may have been pre-stored to the at least one memory 1020 or, alternatively or additionally, they may be received, by the apparatus, via an electromagnetic carrier signal and / or may be copied from a physical entity such as a computer program product. Execution of the computer readable instructions by the at least one processor 1010 causes the apparatus 1000 to perform one or more of the example embodiments described above. That is, the at least one processor and the at least one memory storing the instructions may provide the means for providing or causing the performance of any of the methods and / or blocks described above.
[0215] In the context of this document, a “memory” or “computer-readable media” or “computer-readable medium” may be any non-transitory media or medium or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs.ROM) .
[0216] The apparatus 1000 may further comprise, or be connected to, an input unit 1030. The input unit 1030 may comprise one or more interfaces for receiving input. The one or more interfaces may comprise, for example, at least one of: one or more temperature, motion and / or orientation sensors, one or more cameras, one or more accelerometers, one or more microphones, one or more buttons and / or one or more touch detection units. Further, the input unit 1030 may comprise an interface to which external devices may connect to.
[0217] The apparatus 1000 may also comprise an output unit 1040. The output unit may comprise or be connected to one or more displays capable of rendering visual content, such as a light emitting diode (LED) display, a liquid crystal display (LCD) and / or a liquid crystal on silicon (LCoS) display. The output unit 1040 may further comprise one or more audio outputs. The one or more audio outputs may be for example loudspeakers.
[0218] The apparatus 1000 further comprises a connectivity unit 1050. The connectivity unit 1050 enables wireless connectivity to one or more external devices. The connectivity unit 1050 comprises at least one transmitter and at least one receiver that may be integrated to the apparatus 1000 or that the apparatus 1000 may be connected to. The at least one transmitter comprises at least one transmission antenna, and the at least one receiver comprises at least one receiving antenna. The connectivity unit 1050 may comprise an integrated circuit or a set of integrated circuits that provide the wireless communication capability for the apparatus 1000. Alternatively, the wireless connectivity may be a hardwired application-specific integrated circuit (ASIC) . The connectivity unit 1050 may also provide means for performing at least some of the blocks or functions of one or more example embodiments described above. The connectivity unit 1050 may comprise one or more components, such as: power amplifier, digital front end (DFE) , analog-to-digital converter (ADC) , digital-to-analog converter (DAC) , frequency converter, (de) modulator, and / or encoder / decoder circuitries, controlled by the corresponding controlling units.
[0219] It is to be noted that the apparatus 1000 may further comprise various components not illustrated in FIG. 10. The various components may be hardware components and / or software components.
[0220] FIG. 11 illustrates an example of an apparatus 1100 comprising means for performing one or more of the example embodiments described above. For example, the apparatus 1100 may be an apparatus such as, or comprising, or comprised in, a network node 104, 106 of an access network.
[0221] The apparatus 1100 may comprise, for example, a circuitry or a chipset applicable for realizing one or more of the example embodiments described above. The apparatus 1100 may be an electronic device comprising one or more electronic circuitries. The apparatus 1100 may comprise a communication control circuitry 1110 such as at least one processor, and at least one memory 1120 storing instructions 1122 which, when executed by the at least one processor, cause the apparatus 1100 to carry out one or more of the example embodiments described above. Such instructions 1122 may, for example, include computer program code (software) . The at least one processor and the at least one memory storing the instructions may provide the means for providing or causing the performance of any of the methods and / or blocks described above.
[0222] The processor is coupled to the memory 1120. The processor is configured to read and write data to and from the memory 1120. The memory 1120 may comprise one or more memory units. The memory units may be volatile or non-volatile. It is to be noted that there may be one or more units of non-volatile memory and one or more units of volatile memory or, alternatively, one or more units of non-volatile memory, or, alternatively, one or more units of volatile memory. Volatile memory may be for example random-access memory (RAM) , dynamic random-access memory (DRAM) or synchronous dynamic random-access memory (SDRAM) . Non-volatile memory may be for example read-only memory (ROM) , programmable read-only memory (PROM) , electronically erasable programmable read-only memory (EEPROM) , flash memory, optical storage or magnetic storage. In general, memories may be referred to as non-transitory computer readable media. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) . The memory 1120 stores computer readable instructions that are executed by the processor. For example, non-volatile memory stores the computer readable instructions, and the processor executes the instructions using volatile memory for temporary storage of data and / or instructions.
[0223] The computer readable instructions may have been pre-stored to the memory 1120 or, alternatively or additionally, they may be received, by the apparatus, via an electromagnetic carrier signal and / or may be copied from a physical entity such as a computer program product. Execution of the computer readable instructions causes the apparatus 1100 to perform one or more of the functionalities described above.
[0224] The memory 1120 may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and / or removable memory. The memory may comprise a configuration database for storing configuration data, such as a current neighbour cell list, and, in some example embodiments, structures of frames used in the detected neighbour cells.
[0225] The apparatus 1100 may further comprise or be connected to a communication interface 1130, such as a radio unit, comprising hardware and / or software for realizing communication connectivity with one or more wireless communication devices according to one or more communication protocols. The communication interface 1130 comprises at least one transmitter (Tx) and at least one receiver (Rx) that may be integrated to the apparatus 1100 or that the apparatus 1100 may be connected to. The communication interface 1130 may provide means for performing some of the blocks and / or functions (e.g., transmitting and receiving) for one or more example embodiments described above. The communication interface 1130 may comprise one or more components, such as: power amplifier, digital front end (DFE) , analog-to-digital converter (ADC) , digital-to-analog converter (DAC) , frequency converter, (de) modulator, and / or encoder / decoder circuitries, controlled by the corresponding controlling units.
[0226] The communication interface 1130 provides the apparatus with radio communication capabilities to communicate in the wireless communication network. The communication interface may, for example, provide a radio interface to one or more UEs 100, 102. The apparatus 1100 may further comprise or be connected to another interface towards a core network 110, such as the network coordinator apparatus or AMF, and / or to other access nodes of the wireless communication network.
[0227] The apparatus 1100 may further comprise a scheduler 1140 that is configured to allocate radio resources. The scheduler 1140 may be configured along with the communication control circuitry 1110 or it may be separately configured.
[0228] It is to be noted that the apparatus 1100 may further comprise various components not illustrated in FIG. 11. The various components may be hardware components and / or software components.
[0229] FIG. 12 illustrates an example of an apparatus 1200 of a core network 110, the apparatus 1200 comprising means for performing one or more of the example embodiments described above. For example, the apparatus 1200 may be, or comprise, or be comprised, a core network function (e.g., MME or AMF) of the core network 110.
[0230] The apparatus 1200 may comprise, for example, a circuitry or a chipset applicable for realizing one or more of the example embodiments described above. The apparatus 1200 may be an electronic device or computing system comprising one or more electronic circuitries. The apparatus 1200 may comprise a control circuitry 1210 such as at least one processor, and at least one memory 1220 storing instructions 1222 which, when executed by the at least one processor, cause the apparatus 1200 to carry out one or more of the example embodiments described above. Such instructions 1222 may, for example, include computer program code (software) . The at least one processor and the at least one memory storing the instructions may provide the means for providing or causing the performance of any of the methods and / or blocks described above.
[0231] In another embodiment, the means may be a network function (e.g., MME or AMF) of the core network 110, or the means may be network function virtualization infrastructure.
[0232] The processor is coupled to the memory 1220. The processor is configured to read and write data to and from the memory 1220. The memory 1220 may comprise one or more memory units. The memory units may be volatile or non-volatile. It is to be noted that there may be one or more units of non-volatile memory and one or more units of volatile memory or, alternatively, one or more units of non-volatile memory, or, alternatively, one or more units of volatile memory. Volatile memory may be for example random-access memory (RAM) , dynamic random-access memory (DRAM) or synchronous dynamic random-access memory (SDRAM) . Non-volatile memory may be for example read-only memory (ROM) , programmable read-only memory (PROM) , electronically erasable programmable read-only memory (EEPROM) , flash memory, optical storage or magnetic storage. In general, memories may be referred to as non-transitory computer readable media. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) . The memory 1220 stores computer readable instructions that are executed by the processor. For example, non-volatile memory stores the computer readable instructions, and the processor executes the instructions using volatile memory for temporary storage of data and / or instructions.
[0233] The computer readable instructions may have been pre-stored to the memory 1220 or, alternatively or additionally, they may be received, by the apparatus, via an electromagnetic carrier signal and / or may be copied from a physical entity such as a computer program product. Execution of the computer readable instructions causes the apparatus 1200 to perform one or more of the functionalities described above.
[0234] The memory 1220 may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and / or removable memory.
[0235] The apparatus 1200 may further comprise or be connected to a communication interface 1230 comprising hardware and / or software for realizing communication connectivity according to one or more communication protocols. The communication interface 1230 may comprise at least one transmitter (Tx) and at least one receiver (Rx) that may be integrated to the apparatus 1200 or that the apparatus 1200 may be connected to. The communication interface 1230 may provide means for performing some of the blocks and / or functions (e.g., transmitting and receiving) for one or more example embodiments described above. The communication interface 1230 may comprise one or more components, such as: power amplifier, digital front end (DFE) , analog-to-digital converter (ADC) , digital-to-analog converter (DAC) , frequency converter, (de) modulator, and / or encoder / decoder circuitries, controlled by the corresponding controlling units.
[0236] The communication interface 1230 provides the apparatus with communication capabilities to communicate in the wireless communication network. The communication interface 1230 may, for example, provide a radio, cable or fiber interface to one or more network nodes of a radio access network.
[0237] It is to be noted that the apparatus 1200 may further comprise various components not illustrated in FIG. 12. The various components may be hardware components and / or software components.
[0238] As used in this application, the term “circuitry” may refer to one or more or all of the following: a) hardware-only circuit implementations (such as implementations in analog, digital and / or quantum circuitry) ; and b) combinations of hardware circuit (s) and software, such as (as applicable) : i) a combination of analog, digital and / or quantum hardware circuit (s) with software / firmware and ii) any or all portions of hardware processor (s) (including digital and / or quantum processor (s) ) with software, and memory (ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform various functions; and c) any or all portions of hardware circuit (s) , such as microprocessor (s) , processor (s) and / or quantum processor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0239] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0240] The techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices) , firmware (one or more devices) , software (one or more modules) , or combinations thereof. For a hardware implementation, the apparatus (es) of example embodiments may be implemented within one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , graphics processing units (GPUs) , processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software, the implementation can be carried out through modules of at least one chipset (for example procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory unit and executed by processors. The memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art. Additionally, the components of the systems described herein may be rearranged and / or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.
[0241] It will be understood by a person skilled in the art that, as technology advances, the proposed concept may be implemented in various ways within the scope of the claims. The embodiments are not limited to the example embodiments described above, but may vary within the scope of the claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate, not to restrict, the embodiments.
Claims
1.A user equipment comprising at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the user equipment to perform operations, the operations comprising at least:receiving, from a network node of an access network, a configuration for establishing one or more signaling radio bearers for a data session for the user equipment; andestablishing the one or more signaling radio bearers based on the configuration,wherein the one or more signaling radio bearers carry user plane traffic.2.The user equipment of claim 1, wherein the configuration received from the network node indicates a mapping between one or more user plane flow identifiers and at least one of: the one or more signaling radio bearers, or one or more quality of service requirements for establishing the one or more signaling radio bearers.3.The user equipment of claim 1 or 2, wherein the operations further comprise:receiving a non-access stratum protocol data unit from the network node,wherein the non-access stratum protocol data unit indicates an association of one or more application traffic filters with a user plane flow identifier; androuting the user plane traffic to be transmitted to the network node onto a signaling radio bearer of the one or more signaling radio bearers based on the user plane flow identifier.4.The user equipment of claim 1 or 2, wherein the operations further comprise:determining a type of uplink traffic received from an application;selecting, based on the determination of the type of the uplink traffic, a signaling radio bearer from the one or more signaling radio bearers; andtransmitting a user plane data packet of the user plane traffic to the network node via the signaling radio bearer that is selected.5.The user equipment of claim 1 or 2, wherein the operations further comprise:inserting, into a header of another message carrying one or more user plane data packets, an indication indicating a type of traffic associated with the one or more user plane data packets; anddetermining, at a radio resource control layer of the user equipment, based on the header, a signaling radio bearer of the one or more signaling radio bearers to forward the one or more user plane data packets to.6.The user equipment of any preceding claim, wherein the user plane traffic is associated with one or more internet protocol multimedia subsystem services.7.The user equipment of claim 6, wherein the one or more internet protocol multimedia subsystem services comprise at least an internet protocol multimedia subsystem voice call service,wherein the one or more signaling radio bearers comprise at least:a first signaling radio bearer for carrying signaling traffic associated with the internet protocol multimedia subsystem voice call service, anda second signaling radio bearer for carrying voice traffic associated with the internet protocol multimedia subsystem voice call service.8.The user equipment of claim 6 or 7, wherein the operations further comprise:receiving, from the network node, system information about supporting the one or more internet protocol multimedia subsystem services via a narrowband internet of things radio technology; andtransmitting, to a core network function, via the network node, based on receiving the system information, a service request for the one or more internet protocol multimedia subsystem services.9.An apparatus comprising at least one processor, and at least one memory storing instructions of a radio access node which, when executed by the at least one processor, cause the apparatus to perform operations, the operations comprising at least:receiving, from a core network function, a message comprising at least one of:a request for establishing one or more signaling radio bearers for a data session for a user equipment, andone or more quality of service requirements for the one or more signaling radio bearers for the data session for the user equipment;determining, based on the message, a configuration for establishing the one or more signaling radio bearers; andtransmitting the configuration to the user equipment for establishing the one or more signaling radio bearers,wherein the one or more signaling radio bearers carry user plane traffic.10.The apparatus of claim 9, wherein the operations further comprise:receiving, from the core network function, information indicating a mapping between one or more user plane flow identifiers and at least one of: the one or more signaling radio bearers, or the one or more quality of service requirements,wherein the configuration transmitted to the user equipment indicates the mapping.11.The apparatus of claim 9, wherein the operations further comprise:mapping one or more user plane flow identifiers to at least one of: the one or more signaling radio bearers, or the one or more quality of service requirements.12.The apparatus of claim 10 or 11, wherein each of the one or more user plane flow identifiers corresponds to a radio access bearer identifier, or to an association of a protocol data unit session identifier with a quality of service flow identifier.13.The apparatus of any of claims 9 to 12, wherein the operations further comprise:receiving, from the core network function, a non-access stratum protocol data unit to be transmitted to the user equipment,wherein the non-access stratum protocol data unit indicates an association of one or more application traffic filters with a user plane flow identifier; andtransmitting the non-access stratum protocol data unit to the user equipment.14.The apparatus of any of claims 9 to 13, wherein the operations further comprise:receiving a user plane data packet of the user plane traffic from the user equipment over a signaling radio bearer of the one or more signaling radio bearers; andtransmitting, to the core network function, a further message comprising the user plane data packet received from the user equipment, and a user plane flow identifier associated with the signaling radio bearer over which the user plane data packet was received from the user equipment.15.The apparatus of any of claims 9 to 14, wherein the user plane traffic is associated with one or more internet protocol multimedia subsystem services.16.The apparatus of claim 15, wherein the one or more internet protocol multimedia subsystem services comprise at least an internet protocol multimedia subsystem voice call service,wherein the one or more signaling radio bearers comprise at least:a first signaling radio bearer for carrying signaling traffic associated with the internet protocol multimedia subsystem voice call service, anda second signaling radio bearer for carrying voice traffic associated with the internet protocol multimedia subsystem voice call service.17.The apparatus of claim 15 or 16, wherein the operations further comprise:broadcasting system information about supporting the one or more internet protocol multimedia subsystem services via a narrowband internet of things radio technology.18.An apparatus comprising at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform operations, the operations comprising at least:generating a message comprising at least one of:a request for a network node of an access network to establish one or more signaling radio bearers for a data session for a user equipment, andone or more quality of service requirements for the one or more signaling radio bearers for the data session for the user equipment; andtransmitting the message to the network node of the access network,wherein the one or more signaling radio bearers carry user plane traffic.19.The apparatus of claim 18, wherein the operations further comprise:mapping one or more user plane flow identifiers to at least one of: the one or more signaling radio bearers, or the one or more quality of service requirements; andtransmitting, to the network node, information indicating the mapping.20.The apparatus of claim 19, wherein each of the one or more user plane flow identifiers corresponds to a radio access bearer identifier, or to an association of a protocol data unit session identifier with a quality of service flow identifier.21.The apparatus of any claims 18 to 20, wherein the operations further comprise:transmitting, via the network node, a non-access stratum protocol data unit to be transmitted to the user equipment,wherein the non-access stratum protocol data unit indicates an association of one or more application traffic filters with a user plane flow identifier.22.The apparatus of any of claims 18 to 21, wherein the operations further comprise:receiving, from the network node, a further message comprising a user plane data packet of the user traffic received from the user equipment, and a user plane flow identifier associated with a signaling radio bearer over which the user plane data packet was received from the user equipment;selecting the data session of the user equipment and an interface, based on the user plane flow identifier comprised in the further message; andtransmitting, over the interface that is selected, the content of the user plane data packet to a network entity serving the data session of the user equipment.23.The apparatus of any of claims 18 to 22, wherein the access network comprises a non-terrestrial network.24.The apparatus of any of claims 18 to 23, wherein the user equipment is a narrowband internet of things device.25.The apparatus of any of claims 18 to 24, wherein the user plane traffic is associated with one or more internet protocol multimedia subsystem services.26.The apparatus of claim 25, wherein the one or more internet protocol multimedia subsystem services comprise at least an internet protocol multimedia subsystem voice call service,wherein the one or more signaling radio bearers comprise at least one of:a first signaling radio bearer for carrying signaling traffic associated with the internet protocol multimedia subsystem voice call service, ora second signaling radio bearer for carrying voice traffic associated with the internet protocol multimedia subsystem voice call service.27.The apparatus of claim 26, wherein the operations further comprise:transmitting, to the network node, an additional message comprising a user plane data packet to be transmitted to the user equipment via a signaling radio bearer of the one or more signaling radio bearers,wherein the user plane data packet of the additional message is associated with one of:a first user plane flow identifier corresponding to the signaling traffic, ora second user plane flow identifier corresponding to the voice traffic.28.The apparatus of any of claims 25 to 27, wherein the operations further comprise:receiving, from the user equipment, a service request for the one or more internet protocol multimedia subsystem services,wherein the message is generated and transmitted based on receiving the service request.29.The apparatus of claim 26 or 27, wherein the operations further comprise:receiving, from a network entity serving the data session of the user equipment, a request for establishing the second signaling radio bearer for carrying the voice traffic associated with the internet protocol multimedia subsystem voice call service,wherein the message is generated and transmitted based on receiving the request from the network entity serving the data session.
