Device and method for communicating traffic having multiple traffic components

By setting up separate radio bearers for each traffic component and separating traffic based on type, the method addresses the challenge of managing multiple QoS requirements in non-IP communication systems, ensuring efficient communication of signaling and voice data.

WO2026233615A1PCT designated stage Publication Date: 2026-11-12NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/059591
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-01
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing mobile radio communication systems struggle to efficiently handle multiple traffic components with different quality of service requirements, particularly in non-Internet Protocol communication scenarios, as the separation of traffic into components by the sender is not easily possible due to transport protocol limitations.

Method used

A method is provided to set up separate radio bearers for each traffic component, allowing the core network gateway component and the mobile terminal to separate traffic based on traffic type, ensuring each component is communicated using the appropriate bearer, with mechanisms for creating and mapping these bearers to meet specific quality of service requirements.

Benefits of technology

This approach effectively manages traffic components with varying QoS needs, ensuring efficient communication by assigning each component to the appropriate bearer, thereby meeting the specific requirements of signaling and voice data traffic in non-IP communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026059591_12112026_PF_FP_ABST
    Figure EP2026059591_12112026_PF_FP_ABST
Patent Text Reader

Abstract

According to one embodiment, a method is described for communicating traffic having multiple traffic components which differ in their required quality of service, over a mobile radio communication system for providing a communication service to a mobile terminal according to non-Internet Protocol communication, comprising setting up a radio bearer for each traffic component and communicating traffic between a core network gateway component of the mobile radio communication network and the mobile terminal using the radio bearers, wherein the core network gateway component and the mobile terminal separate the traffic into the traffic components based on traffic type and use, for communicating each traffic component, the radio bearer set up for the traffic component.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] P98143 PA766

[0002] 1

[0003] Description

[0004] Device and Method for Communicating Traffic Having Multiple Traffic Components

[0005] The present disclosure relates to devices and methods for communicating traffic having multiple traffic components which differ in their required quality of service, over a mobile radio communication system for providing a communication service to a mobile terminal according to non-Internet Protocol communication.

[0006] For providing a communication service, multiple traffic components may be necessary that may have different quality of service (QoS) requirements. An example is the provision of a call using the IMS (IP (Internet Protocol) Multimedia Subsystem) which requires SIP (Session Initiation Protocol) signalling as well as the transmission of voice data which typically differ in their required QoS. Different QoS can be provided by using multiple traffic flows, wherein each traffic flow is carried by a respective radio bearer. Still, efficient approaches to handle such scenarios are desirable, e.g. since the separation of traffic into traffic components by the respective sender (e.g. mobile terminal or core network gateway component) may, due to the transport protocol being used, not be easily possible.

[0007] According to one embodiment, a method is provided for communicating traffic having multiple traffic components which differ in their required quality of service, over a mobile radio communication system for providing a communication service to a mobile terminal according to non-Internet Protocol communication, comprising:

[0008] • setting up a radio bearer for each traffic component and

[0009] • communicating traffic between a core network gateway component of the mobile radio communication system and the mobile terminal using the radio bearers, wherein the core network gateway component and the mobile terminal separate the traffic into the traffic components based on traffic type and use, forP98143 PA766

[0010] 2

[0011] communicating each traffic component, the radio bearer set up for the traffic component.

[0012] In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various aspects are described with reference to the following drawings, in which:

[0013] Figure 1 shows a radio communication system.

[0014] Figure 2 shows a first option for usage of Control Plane CIoT (Cellular to Internet of Things) EPS (Evolved Packet System) optimization.

[0015] Figure 3 shows a second option for usage of Control Plane CIoT EPS optimization. Figure 4 shows a flow diagram illustrating a method for communicating traffic having multiple traffic components which differ in their required quality of service, over a mobile radio communication system for providing a communication service to a mobile terminal according to non-Internet Protocol communication.

[0016] The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and aspects of this disclosure in which the invention may be practiced. Other aspects may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the invention. The various aspects of this disclosure are not necessarily mutually exclusive, as some aspects of this disclosure can be combined with one or more other aspects of this disclosure to form new aspects.

[0017] Various examples corresponding to aspects of this disclosure are described below:P98143 PA766

[0018] 3

[0019] Example 1 is a method for communicating traffic having multiple traffic components which differ in their required quality of service, over a mobile radio communication system for providing a communication service to a mobile terminal according to nonInternet Protocol communication, comprising setting up a radio bearer for each traffic component and communicating traffic between a core network gateway component of the mobile radio communication system and the mobile terminal using the radio bearers, wherein the core network gateway component and the mobile terminal separate the traffic into the traffic components based on traffic type and use, for communicating each traffic component, the radio bearer set up for the traffic component.

[0020] Example 2 is the method of example 1 , wherein separating the traffic into the traffic components based on traffic type comprises deciding, for data of the traffic to be communicated, based on traffic type, which radio bearer should be used to communicate the data.

[0021] Example 3 is the method of example 1 or 2, wherein separating the traffic into the traffic components based on traffic type comprises separating the traffic into signalling traffic and useful data traffic.

[0022] Example 4 is the method of any one of examples 1 to 3, wherein the traffic type is a communication protocol according to which data of the traffic are configured.

[0023] Example 5 is the method of any one of examples 1 to 4, comprising separating the traffic into traffic being configured according to Session Initiation Protocol or II protocol and into traffic being configured according to Real-Time Transport Protocol.

[0024] Example 6 is the method of any one of examples 1 to 5, comprising setting up a traffic flow for each traffic component, associating each traffic flow with a quality of service and associating each traffic flow with one of the radio bearers, wherein, for each traffic component, the radio bearer set up for the traffic component is the radio bearer associatedP98143 PA766

[0025] 4

[0026] with the traffic flow which is associated with the quality of service that the traffic component requires.

[0027] Example 7 is the method of example 6, comprising associating the traffic flows and the bearers in a one-to-one manner.

[0028] Example 8 is the method of any one of examples 1 to 7, wherein the radio bearers include one or more signalling radio bearers and / or one or more data radio bearers.

[0029] Example 9 is the method of any one of examples 1 to 8, wherein the non-Internet Protocol communication is communication using Reliable Data Service.

[0030] Example 10 is the method of any one of examples 1 to 9, wherein the communication service is a voice call.

[0031] Example 11 is the method of any one of examples 1 to 10, wherein the multiple traffic component include signalling traffic and include voice data traffic.

[0032] Example 12 is the method of any one of examples 1 to 11, wherein the signalling traffic is Internet Multimedia Subsystem traffic and the voice data traffic is Internet Multimedia Subsystem voice data.

[0033] Example 13 is the method of any one of examples 1 to 12, wherein the core network gateway component and the mobile terminal separate the traffic into the traffic components each using a traffic flow template filter.

[0034] Example 14 is the method of any one of examples 1 to 13, comprising receiving, by a mobility management entity of the mobile radio communication system, an indication from the mobile terminal that the mobile terminal supports usage of multiple signalling radio bearers for communication and, in response to the reception of the indication, theP98143 PA766

[0035] 5

[0036] mobility management entity requesting the radio access network of the mobile radio communication system to set up the at least one signalling radio bearer and communicating traffic between a network side of the mobile radio communication system and the mobile terminal using the at least one signalling radio bearer.

[0037] Example 15 is a communication system, configured to perform the method of any one of examples 1 to 14.

[0038] It should be noted that one or more of the features of any of the examples above may be combined with any one of the other examples. In particular, the examples described in context of the device are analogously valid for the method.

[0039] According to further embodiments, a computer program and a computer readable medium comprising instructions, which, when executed by a computer, make the computer perform the method of any one of the above Examples are provided.

[0040] In the following, various examples will be described in more detail.

[0041] Figure 1 shows a radio communication system 100.

[0042] The radio communication system 100 includes a radio communication terminal device 102 (i.e. a mobile terminal, ,in the following also referred to such UE (user equipment)).

[0043] Furthermore, the radio communication system 100 includes a Radio Access Network (RAN) 103, which may include a plurality of radio access network nodes, i.e. base stations (eNBs) 110 configured to provide radio access in accordance with LIE (Long Term Evolution) according to 3GPP (Third Generation Partnership Project) or another mobile radio communication standard. Each radio access network node may provide a radio communication with the radio communication terminal device 102 over a respective air interface 101 (which may operate according to different communicationP98143 PA766

[0044] 6

[0045] standards). It should be noted that the radio access network 103 may include any number of radio access network nodes.

[0046] The radio access network 103 is coupled with a core network 104, specifically a 4G core network in this example, i.e. an EPC (Evolved Packet Core) 104.

[0047] The 4G core network 104 has an MME (Mobility Management Entity) 105, an SGW (Serving Gateway) 106 and a PGW (Packet Data Gateway) 107 (which may or may not be separated into a PGW - Control Plane and a PGW - User Plane). The 4G core network 104 further includes an HSS (Home Subscriber Server) 108.

[0048] Via the mobile radio communication network (formed by the RAN 103 and the 4G core network (EPC) 104) the mobile terminal 102 may in particular use IMS (Internet Protocol Multimedia Subsystem) services offered by an IMS 109, in particular an IMS voice service.

[0049] Various embodiments address a case when more than one separate Service Data Flows (SDFs) are needed to provide a communication service to a mobile terminal 102. This for example occur, when the mobile terminal 102 is served by a geostationary satellite (GEO satellite), i.e. the radio access network node 110 serving the mobile terminal 102 (i.e. providing RAN coverage to the mobile terminal 102) is implemented by a GEO satellite. For example, the mobile terminal uses NB(Narrowband)-IoT(Internet of Things) communication via a GEO satellite (i.e. the RAN 103 acts as NB-IoT RAN). In that case two separate Service Data Flows (SDFs) are needed: one to carry IMS signalling and one to carry IMS voice packets. Both these data flows have different requirements in terms of delay and reliability, i.e. different QoS (quality of service) requirements.

[0050] If Control Plane (CP) CIoT (Cellular to Internet of Things) EPS (Evolved Packet System) optimization is used, these two SDFs need to be carried over two separate SRBs (signalling radio bearers) over the air interface 101 to meet the respective requirements. IfP98143 PA766

[0051] 7

[0052] User Plane (UP) CIoT EPS optimization is used, these two SDFs need to be carried over two separate DRBs (data radio bearers) over the air interface 101 to meet the respective requirements.

[0053] For the case that Control Plane CIoT EPS optimization is used, there are two options to have more than one SRB for IMS voice communication, as illustrated in figure 2 and figure 3.

[0054] Figure 2 shows a first option for usage of Control Plane CIoT EPS optimization where two SRBs 201, 202 are introduced (one for IMS signalling and one for IMS voice data) into a 3 GPP mobile communication network. RRC (radio resource control) and NAS (non-access stratum) signalling is performed via existing SRBs 203, 204.

[0055] Figure 3 shows a second option for usage of Control Plane CIoT EPS optimization where a single SRBs 302 is introduced (for IMS voice data) into a 3GPP mobile communication network. The IMS signalling is done via an existing (i.e. a default) SRB bearer 301. RRC (radio resource control) and NAS (non-access stratum) signalling is performed via existing SRBs 303, 304.

[0056] It should be noted that both options require bearer mapping and both options require filters on the UE side to differentiate between different flows.

[0057] It should further be noted that it is possible (with either CP or UP CIoT optimization) to use non-IP (Internet Protocol) data: a key issue for carrying voice traffic over NB-IoT NTN via GEO satellite is typically to meet the requirements of data rate and call setup time accounting for round trip time from earth to GEO satellite. Therefore, it may be desirable to us a non-IP PDN (public data network) type instead of an IP PDN type to reduce the signalling overhead in order to meet the requirements. In case of usage of a non-IP PDN type (i.e. a non-IP communication), suitable filters are needed on the UEP98143 PA766

[0058] 8

[0059] side for EPS (Evolved Packet System Bearer) bearer mapping (since there is no IP destination address or port).

[0060] To have one or more additional SRBs (see e.g. the two options of figure 2 and 3), according to various embodiments, a mechanism is provided what allows the MME 105 to instruct a RAN node (eNB 110) of the RAN 103 to set up (i.e. initiate) one or more SRBs (one to be used for IMS voice data and possibly another one to be used for IMS signalling). In this manner, the network side may initiate the creation of one or more SRBs.

[0061] In both cases, the IE includes an E-SRAB (Evolved Signal Radio Access Bearer) ID (see table 1) which allows the respective eNB 110 to setup the SRB (described in more detail below). For example, an E-SRAB ID=0 corresponds to SRB-x and an E-SRAB ID=1 corresponds to SRB-y.

[0062]

[0063] Table 1

[0064] It should be noted that this mechanism may also be applied to a hybrid scenario where one traffic flow (IMS Signalling) uses CP based optimization and other (voice media) uses UP based optimization. In such scenario the “Initial Context Setup” or “Bearer Setup” request / response may include both E-RAB and E-SRAB. It is also possible to create an E-SRAB with “Initial Context Setup” procedure, and an E-RAB with "Bearer Setup" procedure.

[0065] So, a radio access bearer identity , namely an E-SRAB ID, is created also for SRBs. The epsBearerldentity (according to in 3GPP TS 36.331) and the SRAB identity (E-SRABP98143 PA766

[0066] 9

[0067] ID) do not need to have a 1-to-l correspondence, e.g. multiple EPS bearers could be mapped to a single SRB.

[0068] This eps-Bearerldentity is in particular included in the SRB-ToADDModList in the RadioResourceConfigDedicated IE in the RRC Connection Reconfiguration message (sent from the RAN 103, i.e. the respective RAN node, to the UE 102). The same eps-Bearerldentity in NAS communication to the UE 102, e.g. in particular in in the TFT (Traffic Flow Templates).

[0069] In the following, an excerpt of the RadioResourceConfigDedicated information element (IE) is given (see 3GPP TS 36.331). The IE RadioResourceConfigDedicated is used to setup, modify and / or release radio bearers, to modify the MAC (medium access control) main configuration, to modify the SPS (semi persistent scheduling) configuration and to modify dedicated physical configuration. According to various embodiments, the underlined part is added / modified.

[0070] SRB-ToAddMod ::= SEQUENCE {

[0071] eps-Bearer Identity INTEGER (0 , 15) OPTIONAL - COND SRB-Setup

[0072] srb-Identity INTEGER (L.2^4), rlc-Config CHOICE { explicitValue RLC-Config, defaultValue NULL } OPTIONAL,

[0073] — Cond Setup logicalChannelConfig CHOICE {

[0074] explicitValue

[0075] LogicalChannelConfig,

[0076] defaultValue NULLP98143 PA766

[0077] 10

[0078] } OPTIONAL,

[0079] — Cond Setup

[0080] [[ pdcp-verChange-rl5 ENUMERATED {true} OPTIONAL, - Cond NR- PDCP

[0081] rlc-Config-vl 530 RLC-Config-vl530 OPTIONAL, - Need ON

[0082] rlc-BearerConfigSecondary-r 15 RLC-BearerConfig-rl 5 OPTIONAL, - Need ON

[0083] srb-Identity- v 1530 INTEGER (4) OPTIONAL - Need ON

[0084] ]],

[0085] [[ rlc-Config-vl 560 RLC-Config-vl510 OPTIONAL - Need ON

[0086] ]],

[0087] [[ rlc-Config-vl 700 RLC-Config-vl700 OPTIONAL - Need ON

[0088] ]]

[0089] So, multiple SRBs can be created and there each SRB is mapped to an E-SRAB. So, by assigning traffic to the SRBs (e.g. IMS signalling traffic to one SRB and IMS voice data to another SRB), i.e. having a traffic flow per type of traffic (signalling or voice data) and carrying each traffic flow by a respective SRB (and, by the mapping of SRB to E-SRAB, an EPS bearer), a QoS mapping of traffic can be performed, i.e. different QoS requirements of the different traffic types can be fulfilled.

[0090] Further, the Traffic flow template (TFT) information element (according to 3 GPP TS 24.008) is updated to include separation in the filters for different traffic flows (to provide separation of different SRBs (mapped to identities, i.e. the TFT is associated withP98143 PA766

[0091] 11

[0092] an EPS bearer ID and given to the UE when the EPS bearer (and the SRB) is created), e.g. to have a TFT Filter for carrying voice traffic in addition to IMS signalling over NB loT NTN via GEO satellite connecting to EPC.

[0093] If IP traffic is used (i.e. an IP type PDN connection), this separation can be done based on the destination IP address and port of the traffic:

[0094] • When the MME 105 initiates the creation of a (default) bearer for SIP traffic (i.e.

[0095] IMS signalling traffic), the MME 105 indicates the EPS-Bearer-ID=x and the UL TFT matching the SIP traffic (i.e. IP address of the P-CSCF (Proxy Call Session Control Function)).

[0096] • When the MME 105 initiates the creation a dedicated bearer for media traffic, the MME 105 indicates EPS-Bearer-ID=y and the UL TFT matching the voice media (e.g. IP address of the IMS-AGW (Access Media Gateway) in the UL TFT to the UE 102.

[0097] • In the UL direction, the UE 102 maps the UL traffic based on the TFT to the EPS- Bearer-ID and EPS bearer ID to the corresponding SRB (as indicated in the RRC request from the respective eNB 110).

[0098] • In the DL direction, the PGW 107 maps the DL traffic to the corresponding EPS- Bearer-ID as configured by the MME 105. The eNB 110 maps the DL traffic to the corresponding SRB as configured by the MME 105.

[0099] The priority of scheduling of the different SRBs can be as follows:

[0100] • The priority of scheduling between the SRBs (SRBx vs SRBy) is for example hardcoded in the UE 102 (in UL direction) and eNB 110 (in DL direction).

[0101] • For example, the SRBx has a higher scheduling priority than SRBy, and SRBx is used for IMS signalling and SRBy for media.

[0102] • If only one SRB is introduced in 3 GPP, the existing SRBs are shared with all NAS / RRC traffic and IMS signalling, and the newly introduced SRBx can be used for RTP / RTCP voice media.P98143 PA766

[0103] 12

[0104] The above approaches are applicable to the case that Control Plane CIoT EPS optimization is used.

[0105] In the following an approach is described which is applicable to both Control Plane and User Plane CIoT EPS optimization and targets the case that non-IP traffic is used.

[0106] Specifically, it is addressed how, in in case of non-IP traffic, the UE 102 maps the UL traffic (voice media or IMS signalling) to the corresponding DRBs or SRBs.

[0107] In the case of usage of non-IP traffic (i.e. a non-IP type PDN connection), regarding the separation of different DRB / SRBs (mapped to identities) and, for this, regarding the traffic flow template information element in TS 24.008 including separation in the filters for different traffic flows, according to various embodiments, the separation of IMS signalling vs. voice media is done based on the traffic type (e.g. SIP or II vs RTP).

[0108] • In UL direction, the UE 102 maps the UL traffic based on the traffic type to the corresponding EPS Bearer-ID and uses the corresponding SRB / DRB for the EPS bearer as configured in the RRC.

[0109] • In DL direction, the PGW 107 maps the DL traffic based on the traffic type to the corresponding EPS Bearer-ID as configured by the MME 105. The eNB 110 maps the DL traffic to the corresponding SRB DRB or as configured by the MME 105.

[0110] It should be noted that the II protocol is specified in 3GPP TS 24.294. It defines a simplified, call control signalling based on SIP, which uses binary encoding and can use non-IP transport (or communication) protocol (e.g. USSD (Unstructured Supplementary Service Data)) between UE and the IMS network.

[0111] The priority of scheduling between the SRBs is for example as described above. The priority of scheduling between DRBs is for example done according to the existing 3 GPP specifications.P98143 PA766

[0112] 13

[0113] It should be noted that while the approaches given herein have been described in context of an NTN use case, they may also be applied to other use cases such as for example sensing (e.g. according to IS AC (Integrated Sensing and Communication).

[0114] In summary, according to various embodiments, a method is provided as illustrated in figure 4.

[0115] Figure 4 shows a flow diagram 400 illustrating a method for communicating traffic having multiple traffic components which differ in their required quality of service, over a mobile radio communication system for providing a communication service to a mobile terminal according to non-Internet Protocol communication.

[0116] In 401, a radio bearer is set up for each traffic component.

[0117] In 402, traffic is communicated between a core network gateway component of the mobile radio communication system and the mobile terminal using the radio bearers, wherein the core network gateway component and the mobile terminal separate the traffic into the traffic components based on traffic type and use, for communicating each traffic component, the radio bearer set up for the traffic component.

[0118] According to various embodiments, in other words, separation of traffic components is done based on traffic type, i.e. a mobile terminal or a core network component may determine based on traffic type to which traffic component a part of traffic (i.e. traffic data to be sent) belongs. In other words, elements of traffic (or parts of traffic, i.e. data or data elements of the traffic) are assigned to bearers and / or traffic flows depending on the traffic type they are or contain (in particular the protocol according to which they are configured), i.e. taking into account their traffic type. For example, each traffic flow or bearer is assigned (in a one-to-one relation) with a traffic type, i.e. there a correspondence between traffic type and bearer is set and traffic is distributed to the bearers by the mobile terminal and the core network gateway component accordingly.P98143 PA766

[0119] 14

[0120] The approach of figure 4 bearer mapping for non-IP transmission, e.g. a non-IP PDN type, e.g. USSD or Reliable Data Service according to 3GPP TS 23.682.

[0121] The method is performed by a mobile communication system, i.e. one or more components of a mobile communication system, e.g. according to 4G, in particular according to 3 GPP.

[0122] It should be noted that signalling bearers may be used as the radio bearers and one or more signalling bearers may be set up and used for communication in response to a capability indication provided by the mobile terminal indicating that it supports usage of multiple signalling radio bearers for communication.

[0123] The core network gateway component is for example a Packet Data Gateway.

[0124] The components of the mobile communication system may for example be implemented by one or more circuits. A "circuit" may be understood as any kind of a logic implementing entity, which may be special purpose circuitry or a processor executing software stored in a memory, firmware, or any combination thereof. Thus a "circuit" may be a hard-wired logic circuit or a programmable logic circuit such as a programmable processor, e.g. a microprocessor. A "circuit" may also be a processor executing software, e.g. any kind of computer program. Any other kind of implementation of the respective functions described above may also be understood as a "circuit".

[0125] While specific aspects have been described, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the aspects of this disclosure as defined by the appended claims. The scope is thus indicated by the appended claims and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced.

Claims

P98143 PA76615Claims1. A method for communicating traffic having multiple traffic components which differ in their required quality of service, over a mobile radio communication system for providing a communication service to a mobile terminal according to non-Internet Protocol communication, comprising:setting up a radio bearer for each traffic component;communicating traffic between a core network gateway component of the mobile radio communication system and the mobile terminal using the radio bearers , wherein the core network gateway component and the mobile terminal separate the traffic into the traffic components based on traffic type and use, for communicating each traffic component, the radio bearer set up for the traffic component, wherein separating the traffic into the traffic components based on traffic type comprises separating the traffic into signalling traffic and useful data traffic.

2. The method of claim 1 , wherein separating the traffic into the traffic components based on traffic type comprises deciding, for data of the traffic to be communicated, based on traffic type, which radio bearer should be used to communicate the data.

3. The method of claim 1 or 2, wherein the traffic type is a communication protocol according to which data of the traffic are configured.

4. The method of any one of claims 1 to 3, comprising separating the traffic into traffic being configured according to Session Initiation Protocol or II protocol and into traffic being configured according to Real-Time Transport Protocol.

5. The method of any one of claims 1 to 4, comprising setting up a traffic flow for each traffic component, associating each traffic flow with a quality of service and associating each traffic flow with one of the radio bearers , wherein, for each traffic component, the radio bearer set up for the traffic component is the radio bearerP98143 PA76616associated with the traffic flow which is associated with the quality of service that the traffic component requires.

6. The method of claim 5, comprising associating the traffic flows and the bearers in a one-to-one manner.

7. The method of any one of claims 1 to 6, wherein the radio bearers include one or more signalling radio bearers and / or one or more data radio bearers.

8. The method of any one of claims 1 to 7, wherein the non-Internet Protocol communication is communication using Reliable Data Service.

9. The method of any one of claims 1 to 8, wherein the communication service is a voice call.

10. The method of any one of claims 1 to 9, wherein the multiple traffic component include signalling traffic and include voice data traffic.

11. The method of any one of claims 1 to 10, wherein the signalling traffic is Internet Multimedia Subsystem traffic and the voice data traffic is Internet Multimedia Subsystem voice data.

12. The method of any one of claims 1 to 11, wherein the core network gateway component and the mobile terminal separate the traffic into the traffic components each using a traffic flow template filter.

13. The method of any one of claims 1 to 12, comprising receiving, by a mobility management entity of the mobile radio communication system, an indication from the mobile terminal that the mobile terminal supports usage of multiple signalling radio bearers for communication and, in response to the reception of theP98143 PA76617indication, the mobility management entity requesting the radio access network of the mobile radio communication system to set up the at least one signalling radio bearer and communicating traffic between a network side of the mobile radio communication system and the mobile terminal using the at least one signalling radio bearer .

14. A communication system, configured to perform the method of any one of claims 1 to 13.