IP multimedia subsystem voice over narrow-band internet-of-things
By enabling UEs to transmit voice domain preferences and capability indicators for IMS voice over NB-loT, the method optimizes network coordination and reduces signaling, ensuring efficient resource allocation and timely IMS voice service setup in NB-loT networks.
Patent Information
- Application Number
- PCT/EP2026/062960
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-05
- Publication Date
- 2026-11-12
AI Technical Summary
Current 3GPP specifications do not provide clear guidelines for UE behavior regarding voice domain preference and usage settings when accessing NB-loT, leading to unclear network behavior and inefficient coordination between UEs and network elements, especially in supporting IMS voice over NB-loT, which results in unnecessary signaling and prolonged call setup times.
Implementing a method for UEs to transmit a NAS message indicating voice domain preference and capability for IMS voice over NB-loT, and for network entities to respond with support status, allowing for efficient coordination and authorization of IMS voice services, thereby reducing unnecessary signaling and optimizing call setup.
This approach reduces network load and signaling overhead, ensuring efficient resource allocation and timely IMS voice service setup, meeting the 30-second call setup time requirement in NB-loT networks.
Smart Images

Figure EP2026062960_12112026_PF_FP_ABST
Abstract
Description
IP MULTIMEDIA SUBSYSTEM VOICE OVER NARROW-BAND INTERNET-OF-THINGSTECHNICAL FIELD
[0001] Disclosed are embodiments related to Internet Protocol (IP) Multimedia Subsystem (IMS) voice over narrow-band (NB) internet-of-things (loT) (NB-loT).BACKGROUND
[0002] In the Third Generation Partnership Project (3GPP) release 20 (Rel-20) there is a new study in working group 2 (WG2) of 3GPP Technical Specification Group Service and System Aspects (TSG SA) (SA2) to enable the IMS voice call and emergency call support over the NB-loT geostationary Earth orbit (GEO) satellite access (see, e.g., reference [1]).
[0003] Currently, NB-loT is developed to enhance device power efficiency, system capacity, etc., by focusing on small and infrequent data transfers. As a result, NB-loT has fewer system features compared to other technologies that are essential for IMS voice over Long Term Evolution (LTE) (a.k.a., 3G). For example, in NB-loT there is no dedicated bearer support, no guaranteed bit rate (GBR) bearer support, and the maximum number of data radio bearers (DRBs) is only up to 2.
[0004] It is possible, however, that the final agreed solution for supporting IMS voice over NB-loT could be different than the existing solution for wideband Evolved Universal Terrestrial Radio Access Network (WB-E-UTRAN). For example, the existing solution for IMS voice over WB-E-UTRAN is to setup 1 default evolved packet system (EPS) bearer for IMS Session Initiation Protocol (SIP) signaling and 1 dedicated EPS bearer for voice media, while the scope of the SA2 study will also investigate the control plane based data transfer solution (i.e., Data over Non-Access Stratum (NAS)).
[0005] Today, user equipments (UEs) can support both NB-loT access and IMS voice over normal LTE access, such as, for example, WB-E-UTRAN or LTE Machine Type Communication (LTE-M). For instance, for loT devices out on the market, it is not uncommon that such device is also equipped with other cellular radio technology (e.g. LTE-M).
[0006] For the latest smartphones, there is a trend to support NB-loT access for satellite use case. Deutsche Telekom with partners, for example, have demonstrated smartphone sending SMS in NB-NTN (see, e.g., reference [2]). Such smartphones naturally have the support of IMS voice over the normal LTE access (i.e. WB-E-UTRAN).
[0007] Current 3GPP specifications do not restrict a UE that is accessing NB-loT from indicating to the network the UE's voice related information, such as the UE's voice domain preference and usage setting. According to 3GPP TS 23.401 v19.2.0 (“TS 23.401”) clause 4.3.5.9, "inter-RAT mobility to / from the NB-loT RAT is not supported, and GBR bearers are not supported in the NB-loT RAT. Hence the UE should not include the ‘Voice domain preference and UE's usage setting' [Information Element (IE)] when sending an Attach Request or Tracking Area Update Request on the NB-loT RAT.”
[0008] The "should not” in the quote above is merely a recommendation. In theory, such a UE is aware of the radio access technology (RAT) (e.g. based on NB-loT specific messages / IEs) and can refrain from sending voice related information to the network when using NB-loT access. But this is left up to the UE implementation and cannot be predicted.SUMMARY
[0009] Certain challenges presently exist. For instance, as noted above, a UE should not include the voice domain preference and UE's usage setting IE when sending an Attach Request or Tracking Area Update Request on the NB-loT RAT, but as also noted above, it cannot be certain that the UE will behave as it should. This creates an issue because there is no clear Mobility Management Entity (ME) behavior description if the UE anyhow sends its "Voice domain preference and UE's usage setting” to the ME when accessing NB-loT.
[0010] Another issue is that if the network side is upgraded to support IMS voice over NB-loT, then it is not clear how the network (e.g., the ME) will determine whether the UE accessing NB-loT is capable for IMS voice over normal LTE access, or capable of IMS voice over NB-loT access, and consequently whether to allow the UE to proceed with the IMS registration and call setup.
[0011] Another issue is that if IMS voice over NB-loT is supported, then there is no efficient method for the operators to differentiate the IMS voice over different RATs. A subscriber with the well-known IMS Access Point Name (APN) in its subscription can use IMS voice service no matter which RAT (WB-E-UTRAN or NB-loT), unless certain RAT (e.g. NB-loT) is restricted for the subscriber, meaning that the UE is not allowed to access the network via such RAT at all.
[0012] On the network side, the support of IMS voice over NB-loT is also assumed to be optional. So, there will be scenarios wherein a non-supporting base station (e.g., eNB) is connected to a supporting ME, and vice-versa.
[0013] Hence, another issue is how to coordinate the capability between eNB and ME to avoid: 1) signaling attempts in relation with IMS voice call, which will be beneficial for the satellite use case given the limited service / feeder link bandwidth over GEO satellite and 2) UE capable of IMS voice over NB-loT being served by a nonsupporting ME.
[0014] Furthermore, there are certain UE configurations that determine the UE behavior when originating calls according to 3GPP TS 23.221 v18.0.0 (“TS 23.221”) clause 7.2a, namely whether the UE is "Data centric” or "Voice centric.” These settings can be provisioned to the UE by the operator according to GSMA IR92 Annex C.2. Today, such configuration is not used in the context of NB-loT, as there is no voice service under NB-loT access. But there might be potential issues to just lift and shift such configuration to NB-loT access. NB-loT today is only capable of data service, while smartphones today are set to voice centric. Voice centric device will reselect another RAT and disable E-UTRA if no voice service is available. NB-loT access via GEO satellite is usually assumed as complementary radio coverage for the terrestrial network, then there is likely no other radio access available. NB-loT today does not support CS fallback according to 3GPP TS 36.300, and so far no plan in 3GPP to add that either. So even assume there is 2G / 3G at the same coverage of NB-loT, the EPS network is still not possible to offer voice service using CS fallback.
[0015] In short, when new UE (e.g., newsmartphone) is capable of IMS voice over NB-loT, but still configured in the same way as today for normal LTE access, there will be a problem for such device to access a NB-loT network, if such network is not yet upgraded to support IMS voice over NB-loT.
[0016] Another challenge that exists is that the call setup time should not exceed 30 seconds (as noted by 3GPP stage 1 key performance indicators (KPIs)); accordingly, considering the limited bandwidth in NB-loT GEO (e.g., 1 kbits - 3kbits), there is a need to implement optimizations to reduce the call setup time.
[0017] Accordingly, in one aspect there is provided a method performed by a UE. The method includes transmitting a first Non-Access Stratum, NAS, message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference. The method also includes receiving a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported. In some embodiments, the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE). In some embodiments, transmitting the first NAS message comprises the UE transmitting a Radio Resource Control (RRC) message comprising the first NAS message, wherein the RRC message further comprises a capability indicator indicating that the UE supports IMS voice over NB-loT. In some embodiments the method further comprises after transmitting the first NAS message and prior to receiving the second NAS message, receiving a request message requesting capability information and transmitting a response message responsive to the request message, the response message comprising information indicating that the UE supports IMS voice over NB-loT.
[0018] In another aspect there is provided a method performed by a management entity (ME). The method includes receiving a first NAS message generated by a UE, the first NAS message comprising information indicating that VoPS is a voice domain preference of the UE. The method also includes generating a second NASmessage responsive to the first NAS message, wherein the second NAS message indicates whether or not IMS voice over NB-loT is supported. The method also includes transmitting the seconds NAS message to the UE. In some embodiments, the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT. In some embodiments, the method further comprises, prior to receiving the first NAS message, receiving from a base station a message indicating that the base station supports IMS voice over NB-loT and the base station forwarded the first NAS message to the network node. In some embodiments, the method further comprises, in response to receiving the first NAS message, determining, based on subscription information associated with the UE, whether or not the UE is authorized to use IMS voice over NB-loT. In some embodiments, the method further comprises, in response to receiving the first NAS message, transmitting to the base station a request message and receiving from the base station a response message responsive to the request message wherein the response message indicates whether or not the UE supports IMS voice over NB-loT.
[0019] In another aspect there is provided a method performed by a base station (BS). The method includes receiving a first NAS message generated by a UE, the first NAS message comprising information indicating that VoPS is a voice domain preference of the UE. The method also includes forwarding the first NAS message to an ME. In some embodiments, I) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT, ii) the method further comprises, prior to receiving the first NAS message, broadcasting system information, wherein the broadcast system information comprises a capability indicator indicating that the base station supports IMS voice over NB-loT, ill) the method further comprises, prior to receiving the first NAS message, transmitting to the ME a control message for establishing a logical connection with the ME, wherein the control message comprises a capability indicator indicating that the base station supports IMS voice over NB-loT, iv) receiving the first NAS comprises receiving a Radio Resource Control, RRC, message comprising first NAS and further comprising a capability indicator indicating that the UE supports IMS voice over NB-loT, and / or v) the method further comprises, after forwarding the first NAS message to the ME: receiving from the ME a first request for information regarding the UE; after receiving the request from the ME, sending to the UE a request for information, and receiving from the UE a response responsive to the second request, wherein the response indicate whether or not the UE supports IMS voice over NB-loT; and after receiving the response from the UE, sending to the ME a response indicating whether or not the UE supports IMS voice over NB-loT.
[0020] In another embodiment, the method performed by the first network node includes receiving from a second network node (e.g., a network node implementing a policy function such as a PCRF or PCF) a message including at least a first pre-allocated TFT data element.
[0021] In another embodiment, the method performed by the first network node includes providing to a second network node (e.g., a network node implementing a PGW / SMF or PCRF or PCF) a message including at least a pre-allocated TFT data element.
[0022] In another embodiment, the method performed by the first network node includes receiving a request from a second network node (e.g., SGW, AMF) and, after receiving the request, creating a TFT based on a locally configured pre-allocated TFT data element. The method also includes sending to the second network node a response message responsive to the request message, wherein the response message comprises the created TFT.
[0023] In another aspect there is provided a computer program comprising instructions which when executed by processing circuitry of an apparatus causes the apparatus to perform any of the methods disclosed herein. In one embodiment, there is provided a carrier containing the computer program wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium. In another aspect there is provided an apparatus that is configured to perform the methods disclosed herein. The apparatus may include memory and processing circuitry coupled to the memory.
[0024] An advantage of the embodiments disclosed herein is that they reduce unnecessary signalling, thereby reducing load in the network, which can lead to an increased quality of service.BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.
[0026] FIG. 1 illustrates a system according to an embodiment.
[0027] FIG. 2 is a flow diagram illustrating a process according to an embodiment.
[0028] FIG. 3 is a flow diagram illustrating a process according to an embodiment.
[0029] FIG. 4 is a flow diagram illustrating a process according to an embodiment.
[0030] FIG. 5 is a flow diagram illustrating a process according to an embodiment.
[0031] FIG. 6 is a flow diagram illustrating a process according to an embodiment.
[0032] FIG. 7 is a flow diagram illustrating a process according to an embodiment.
[0033] FIG. 8 is a flowchart illustrating a process according to an embodiment.
[0034] FIG. 9 is a flowchart illustrating a process according to an embodiment.
[0035] FIG. 10 is a flowchart illustrating a process according to an embodiment.
[0036] FIG. 11 is a message flow diagram illustrating a process according to an embodiment.
[0037] FIG. 12 is a message flow diagram illustrating a process according to an embodiment.
[0038] FIG. 13 is a message flow diagram illustrating a process according to an embodiment.
[0039] FIG. 14 is a message flow diagram illustrating a process according to an embodiment.
[0040] FIG. 15 is a message flow diagram illustrating a process according to an embodiment.
[0041] FIG. 16 is a message flow diagram illustrating a process according to an embodiment.
[0042] FIG. 17 is a flowchart illustrating a process according to an embodiment.
[0043] FIG. 18 is a flowchart illustrating a process according to an embodiment.
[0044] FIG. 19 is a flowchart illustrating a process according to an embodiment.
[0045] FIG. ZZ1 is a block diagram of a UE according to an embodiment.
[0046] FIG. ZZ2 is a block diagram of a network node according to an embodiment.
[0047] FIG. ZZ3 is a block diagram of a base station according to an embodiment.DETAILED DESCRIPTION
[0048] FIG. 1 illustrates a system 100 according to an embodiment. System 100 includes a first UE 102, a second UE 103, a base station (BS) 104 (e.g., an eNB or gNB), and a core network 106, which includes multiple core network entities, such as management entity (ME) 108, which may be a Mobile Management Entity (MME) or an Access and Mobility Management Function (AMF), and a Home Subscriber Server (SDM) subscriber data manager (SDM) 109, which may be an Home Subscriber Server (SDM) or a Unified Data Manager (UDM). While only two UEs are shown, base station 104 may be capable of serving a large number of UEs. As used herein, a UE is any device capable of wireless communication with a base station. Accordingly, examples of a UE include: smartphones, laptops, sensors, appliances, loT devices, etc. In some embodiments, UE 102 and / or UE 103 may communicate with BS 104 via a satellite (not shown), while in other embodiments, BS 104 may be on board a satellite.
[0049] FIG. 2 is a message flow diagram illustrating an embodiment. In the embodiment shown in FIG. 2, ME 108 does not support IMS voice over NB-loT access, but does support IMS over normal LTE access, and BS 104 is serving the NB-loT RAT. UE 102 may be a UE that does not support IMS voice over NB-loT and is misbehaving or UE 102 may support IMS voice over NB-loT and wishes to obtain IMS service. NB-loT may have several variants, including, for example: NB-loT, NB-loT Non-Terrestrial Network (NTN), NB-loT (low Earth orbit (LEO)), NB-loT (medium Earth Orbit (MEO)), NB-loT (GEO), NB-loT (OTHERSAT), etc. Accordingly, when this disclosure refers to NB-loT, the disclosure refers to any one or more of the possible variants.
[0050] As shown in FIG. 2, BS 104 sends a request message m201 to ME 108. Request message m201 in this example is an S1 setup request. The S1 setup request is used to establish a logical connection between BS 104 and ME 108. The S1 setup request includes BS 104' s configuration details, including its identifier (ID),name, Track Assignment Code (TAG), and information indicating the type of RAT BS 104 is serving, which, in this example is NB-loT.
[0051] As further shown in FIG. 2, at some point, UE 102 sends to BS 104 a Radio Resource Control (RRC) message m203 comprising a Non-Access Stratum (NAS) message m205 to be processed by an ME selected by BS 104. RRC message m203 may be a message that is part of a connection establishment message exchange. For instance, RRC message m203 may be an RRC Connection Setup Complete message, which is transmitted by UE 102 to BS 104 in response to UE 102 receiving from BS 104 an RRC Connection Setup message, which is transmitted by BS 104 to UE 102 in response to BS 104 receiving from UE 102 an RRC Connection Request.
[0052] NAS message m205 may be a registration message such as, for example, an Attach Request message or a Tracking Area Update (TAU) message. BS 104, after receiving RRC message m203, selects an ME and forwards NAS message m205 to the selected ME, which in this case is ME 108. In this example, NAS message m205 includes information indicating UE 102's communication preferences. For instance, NAS message m205 may include information indicating one of a plurality of possible usage settings and information indicating one of a plurality of voice domain preferences. That is, as shown in FIG. 2, NAS message m205 includes information indicating a particular voice domain preference (VDP) and information indicating a particular usage setting (US). As a specific example, message m205 may be an Attach Request or a Tracking Area Update Request that includes the "Voice domain preference and UE's usage setting” information element (IE).
[0053] After receiving NAS message m205, ME 108 determines whether or not to indicate to UE 102 support for IMS voice. This determination is based on the RAT the request message m205 comes from and the UE's voice domain preference (VDP) indicated in message m205. For example, in one embodiment, ME 108 checks which RAT NAS message m205 comes from. In one embodiment, the NAS message m205 is contained within an S1 AP message that includes a TAG and ME 108 determines the RAT based on the TAG as BS 104 serves only single RAT per tracking area. If message m205 comes from the NB-loT RAT, then ME 108 checks if it supports IMS voice over NB-loT. If ME 108 does not support IMS voice over NB-loT, then ME 108 checks UE 102'sVDP. If voice over packet switched (VoPS) is indicated by the voice domain preference (e.g., UE's voice domain preference is set to: "IMS PS Voice only,” or "CS voice preferred, IMS PS Voice as secondary,” or "IMS PS voice preferred, CS Voice as secondary”), then ME 108 sets the "IMS VoPS” bit to ‘O' in "EPS network feature support” IE (see, e.g., TS 23.401 clause 4.3.5.8 and TS 24.301 clause 9.9.3.12A) in a response message m207 (e.g., an attach accept message) responsive to message m205 that is sent by ME 108 to UE 102.
[0054] Based on the content of response message m207 sent by ME 108 to UE 102, for example, based on the value of the IMS VoPS bit in response message m207, UE 102 determines that there is no IMS voice support in current serving network. The UE may take further actions if VoPS is not provided by NB-loT (e.g. select another other RAT, select another PLMN if possible, or remain in current RAT and receive only data service).
[0055] FIG. 3 is a message flow diagram illustrating another embodiment. In the embodiment shown in FIG. 3, ME 108 supports IMS voice over NB-loT access, BS 104 is serving the NB-loT RAT, UE 102 supports IMS voice over NB-loT and wishes to obtain IMS service, and UE 103 does not support IMS voice over NB-loT and is misbehaving. As shown in FIG. 3, BS 104 sends request message m201 to ME 108 as described above.
[0056] As also shown in FIG. 3, at some point, UE 102 sends to BS 104 RRC message m203 comprising a NAS message m305 to be processed by an ME selected by BS 104. Like NAS message m205, NAS message m305 may be a registration message such as, for example, an Attach Request message or a Tracking Area Update (TAU) message. BS 104, after receiving RRC message m203 selects an ME and forwards NAS message m305 to the selected ME, which in this case is ME 108. In this example, like NAS message m205, NAS message m305 includes information indicating UE 102's communication preferences. For example, message m305 incudes the "Voice domain preference and UE's usage setting” IE. Unlike NAS message m205, however, in this embodiment NAS message m305 further includes information indicating that UE 102 supports IMS voice over NB-loT. More specifically, in the embodiment shown in FIG. 3, NAS message m305 includes a voice capability (VC) information element (IE) to indicate that UE 102 supports IMS voice over NB-loT. The VC IE may be a 1 bit IE or a multi-bit IE to signal whether or not the UE supports IMS voice over NB-loT.
[0057] For example, message m305 may include a VC information element (IE) named "IMS voice over NB-loT supported” (which could be a 1 bit flag) or an IE named "voice domain preference and UE's usage setting for NB-loT” as described further herein with respect to the RAT aware UE configuration embodiment. In the embodiment in which the VC IE is named "voice domain preference and UE's usage setting for NB-loT,” then this IE would further include information indicating the VDP (e.g., PS only) and information indicating the US (e.g., Data centric), as described below. In another embodiment, the VC IE may be an APN IE containing an APN that indicates that UE supports IMS voice over NB-loT. In one embodiment, if UE has support for IMS voice over NB-loT, then the UE has support for one or more of: dedicated bearer, guaranteed bit rate (GBR) bearer, more than two data radio bearers (DRB), a new codec for voice media data, robust header compression (ROHC) for reducing protocol overhead, multiple signaling radio bearers (SRB) to run IMS signaling and IMS voice data, and mixed SRB and DRB to transport user data.
[0058] After receiving NAS message m305, if message m305 indicates that VoPS is UE 102's voice domain preference (e.g., UE's voice domain preference is set to: "IMS PS Voice only,” or "CS voice preferred, IMS PS Voice as secondary,” or "IMS PS voice preferred, CS Voice as secondary”), then ME 108 determines whether or not to indicate to UE 102 support for IMS voice. This determination is based on whether or not message m305 indicates that UE 102 supports IMS voice over NB-loT.
[0059] For example, in one embodiment, ME 108 checks which RAT NAS message m305 comes from, and, if message m305 comes from the NB-loT RAT, then ME 108 checks whether message m305 indicates that UE102 supports IMS voice over NB-loT. If UE 102 does not support IMS voice over NB-loT, then ME 108 set the "IMS VoPS” bit to ‘O' in "EPS network feature support” IE in response message m307 responsive to message m305 that is sent by ME 108 to UE 102.
[0060] On the other hand, if message m305 indicates that UE 102 supports IMS voice over NB-loT and zero or more other criterions are met, such as for example, that BS 104 also supports IMS voice over NB-loT, then ME 108 sets the "IMS VoPS” bit to T to inform UE 102 that IMS voice over NB-loT is available in the network.
[0061] As also shown in FIG. 3, at some point, UE 103 sends to BS 104 an RRC message comprising a NAS message m309 to be processed by an ME selected by BS 104. Like NAS message m305, NAS message m309 may be a registration message such as, for example, an Attach Request message or a Tracking Area Update (TAU) message. BS 104, after receiving the RRC message selects an ME (which in this case is ME 108) and forwards NAS message m309 to ME 108. In this example, like NAS message m305, NAS message m309 includes information indicating UE 102's communication preferences. Unlike NAS message m305, however, NAS message m309 does not include information indicating that UE 102 supports IMS voice over NB-loT.
[0062] After receiving NAS message m309, ME 108 determines whether or not to indicate to UE 103 support for IMS voice. This determination is based on whether or not message m309 indicates that UE 102 supports IMS voice over NB-loT.
[0063] For example, in one embodiment, ME 108 checks which RAT NAS message m309 comes from, and, if message m309 comes from the NB-loT RAT, then ME 108 checks whether message m309 indicates that UE 102 supports IMS voice over NB-loT. If UE 102 does not support IMS voice over NB-loT, then ME 108 does not set the "IMS VoPS” bit in "EPS network feature support” IE in response message m307 responsive to message m305 that is sent by ME 108 to UE 102. That is, ME 108 set the IMS VoPS bit to ‘O' in response message message m311, to inform the UE 103 that IMS voice service is not available in the network. Based on content of response message m311, UE 103 determines that there is no IMS voice support in current serving network. UE 103 may take further actions if VoPS is not provided by NB-loT (e.g. select another other RAT, select another PLMN if possible, or remain in current RAT and receive only data service).
[0064] A benefit of the embodiment is that ME can stop the signaling attempt in the very early stage from the UE which is only capable of IMS voice over normal LTE access, when the UE is accessing NB-loT.
[0065] FIG. 4 is a message flow diagram illustrating another embodiment. In the embodiment shown in FIG. 4, ME 108 supports IMS voice over NB-loT access, BS 104 is serving the NB-loT RAT, and UE 102 supports IMS voice over NB-loT and wishes to obtain IMS service. As shown in FIG. 4, BS 104 sends request message m201 to ME 108 as described above.
[0066] As also shown in FIG. 4, at some point, UE 102 sends to BS 104 RRC message m203 comprising NAS message m405 to be processed by an ME selected by BS 104. BS 104, after receiving RRC message m203 selects an ME and forwards to the selected ME (which in this case is ME 108) NAS message m405. NAS message m405includes information indicating UE 102's communication preferences (e.g., message m405 includes the Voice domain preference and UE's usage setting IE) and, in one embodiment, may further include information indicating that UE 102 supports IMS voice over NB-loT.
[0067] After receiving NAS message m405, if message m405 indicates that VoPS is UE 102's voice domain preference, then ME 108 determines whether or not to indicate to UE 102 support for IMS voice. This determination is based on i) whether or not message m305 indicates that UE 102 supports IMS voice over NB-loT and / or ii) subscription information associated with UE 102, wherein the subscription information indicates whether or not UE 102 is authorized to use IMS voice over NB-loT.
[0068] For example, in one embodiment, ME 108 checks which RAT NAS message m305 comes from, and, if message m305 comes from the NB-loT RAT, then ME 108 checks whether message m305 indicates that UE 102 supports IMS voice over NB-loT. If UE 102 does not support IMS voice over NB-loT, then ME 108 does not set the "IMS VoPS” bit in "EPS network feature support” IE in response message m307 responsive to message m305 that is sent by ME 108 to UE 102. On the other hand, if message m305 indicates that UE 102 supports IMS voice over NB-loT, then ME 108 sets the "IMS VoPS” bit to T in "EPS network feature support” IE in response message m307.
[0069] In another embodiment, ME 108 checks which RAT NAS message m305 comes from, and, if message m305 comes from the NB-loT RAT, then ME 108 obtains from SDM 109 subscription information associated with UE 102. For example, ME 108 may send to SDM 109 a request message m421, such as, for example, an update location request or an insert subscriber data request. SDM 109 responds to request message m421 by retrieving subscription data associated with UE 102 and sending to ME 108 a response message m422 comprising the retrieved subscription data, which indicates whether or not UE 102 is authorized to use IMS voice over NB-loT. If the appropriate conditions are satisfied (e.g., UE 102 is authorized to use IMS voice over NB-loT and BS 104 also supports IMS voice over NB-loT), then ME 101 sets the "IMS VoPS” bit to T in "EPS network feature support” IE in response message m307, otherwise the "IMS VoPS” bit to ‘O'.
[0070] In another embodiment, ME 108 checks which RAT NAS message m305 comes from, and, if message m305 comes from the NB-loT RAT, then ME 108 checks whether message m305 indicates that UE 102 supports IMS voice over NB-loT. If UE 102 does not support IMS voice over NB-loT, then ME 108 does not set the "IMS VoPS” bit. On the other hand, if message m305 indicates that UE 102 supports IMS voice over NB-loT, then ME 108 obtains from SDM 109 subscription information associated with UE 102. For example, ME 108 may send to SDM 109 a request message m421 and SDM 109 responds to request message m421 by retrieving subscriptiondata associated with UE 102 and sending to ME 108 a response message m422 comprising the retrieved subscription data, which indicates whether or not UE 102 is authorized to use IMS voice over NB-loT. If the appropriate conditions are satisfied (e.g., UE 102 both supports IMS voice over NB-loT and is authorized to use IMS voice over NB-loT and BS 104 also supports IMS voice over NB-loT), then ME 101 sets the "IMS VoPS” bit to ‘T, otherwise ME 108 sets the "IMS VoPS” bit to ‘O'.
[0071] FIG. 5 is a message flow diagram illustrating another embodiment. In the embodiment shown in FIG. 5, ME 108 supports IMS voice over NB-loT access, BS 104 is serving the NB-loT RAT, UE 102 supports IMS voice over NB-loT and wishes to obtain IMS service.
[0072] As shown in FIG. 5, BS 104 sends to ME 108 a request message m501. Request message m501 in this example is an extended version of the conventional S1 setup request that includes BS 104's configuration details, including its identifier (ID), name, Track Assignment Code (TAG), and information indicating the type of RAT BS 104 is using, which, in this example is NB-loT. In this embodiment, however, message m501 further indicates whether or not BS 104 is capable of IMS voice over NB-loT. For instance, message m501 may include a capability indicator that indicates whether or not BS 104 is capable of IMS voice over NB-loT. ME 108 will store this information and use it when responding to a registration request (e.g., attach request or TAU) from UE 102 as explained below.
[0073] ME 108 responds to message m501 by transmitting to BS 104 a response message m502 responsive to message m501, wherein response message m502 indicates whether or not ME 108 is capable of IMS voice over NB-loT. For instance, message m501 may include a capability indicator that indicates whether or not ME 108 is capable of IMS voice over NB-loT. BS 104 will store this information and use it when selecting an ME for processing a registration request. Response message m502 may be an extended version of the conventional S1 setup response message.
[0074] As also shown in FIG. 5, at some point, UE 102 sends to BS 104 an RRC message m503 comprising a NAS message m505 to be processed by an ME selected by BS 104. RRC message m503 may be an extended version of the conventional RRC Connection Setup Complete. For instance, as shown in FIG. 5, RRC message m503 further includes a voice capability (VC) indicator to indicate that UE 102 supports IMS voice over NB-loT.
[0075] After receiving RRC message m503, BS 104 determines that message m503 includes a VC indictor indicating that UE 102 supports IMS voice over NB-loT. As a result of determining, based on the VC indicator, that UE 102 supports IMS voice over NB-loT, BS 102 selects an ME that also supports IMS voice over NB-loT and forwards NAS message m505 to the selected ME, which in this case is ME 108. As noted above, because ME 108 has provide to BS 104 in message m502 information indicating that the ME supports IMS voice over NB-loTand because BS 104 stored this information, BS 104 is able to determine that the ME 108 supports IMS voice over NB-loT.
[0076] NAS message m505 includes information indicating UE 102's communication preferences. NAS message m505 may further include information indicating that UE 102 supports IMS voice over NB-loT. For example, message m505 may include an information element (IE) named "IMS voice over NB-loT supported” or an IE named "voice domain preference and UE's usage setting for NB-loT” as described further herein.
[0077] After receiving NAS message m505, if VoPS is UE 102's voice domain preference, then ME 108 determines whether or not to indicate to UE 102 support for IMS voice. This determination may be based on I) whether or not message m505 indicates that UE 102 supports IMS voice over NB-loT and / or ii) whether BS 102 supports IMS voice over NB-loT. The determination may further be based on whether or not UE 102 is authorized to use IMS voice over NB-loT as described above in connection with the embodiment illustrated in FIG. 4.
[0078] For example, in one embodiment, ME 108 checks which RAT NAS message m505 comes from, and, if message m505 comes from the NB-loT RAT, then ME 108 checks whether message m505 indicates that UE 102 supports IMS voice over NB-loT. If UE 102 does not support IMS voice over NB-loT, then ME 108 sets the "IMS VoPS” bit to ‘O' in "EPS network feature support” IE in response message m307 responsive to message m505 that is sent by ME 108 to UE 102. On the other hand, if message m505 indicates that UE 102 supports IMS voice over NB-loT (and zero or more other conditions are satisfied, such as the UE is authorized to user the IMS voice service NB-loT)), then ME 108 sets the "IMS VoPS” bit to T in "EPS network feature support” IE in response message m307.
[0079] In another embodiment, ME 108 checks which RAT NAS message m505 comes from, and, if message m505 comes from the NB-loT RAT, then ME 108 determines whether BS 104 supports IMS voice over NB-loT. As noted above, because BS 104 has provided to ME 108 in message m501 information indicating that the BS supports IMS voice over NB-loT and because ME 108 stored this information, at the time ME 108 receives NAS message m505, ME 108 is able to determine whether the BS 104 supports IMS voice over NB-loT. If the appropriate conditions are satisfied (e.g., UE 102 is capable of and authorized to use IMS voice over NB-loT and BS 104 also supports IMS voice over NB-loT), then ME 101 sets the "IMS VoPS” bit to T in "EPS network feature support” IE in response message m307, otherwise the "IMS VoPS” bit to ‘O'.
[0080] In another embodiment, ME 108 checks which RAT NAS message m505 comes from, and, if message m505 comes from the NB-loT RAT, then ME 108 checks whether message m505 indicates that UE 102 supports IMS voice over NB-loT. If UE 102 does not support IMS voice over NB-loT, then ME 108 does not set the "IMS VoPS” bit. On the other hand, if message m505 indicates that UE 102 supports IMS voice over NB-loT, then ME 108 determines whether BS 104 supports IMS voice over NB-loT. If the appropriate conditions are satisfied (e.g., UE 102 both supports IMS voice over NB-loT and is authorized to use IMS voice over NB-loT and BS 104 alsosupports IMS voice over NB-loT), then ME 101 sets the "IMS VoPS” bit to '1', otherwise ME 108 sets the "IMS VoPS” bit to ‘O’.
[0081] FIG. 6 is a message flow diagram illustrating another embodiment. In the embodiment shown in FIG. 6, ME 108 supports IMS voice over NB-loT access, BS 104 is serving the NB-loT RAT, and UE 102 supports IMS voice over NB-loT and wishes to obtain IMS service. As shown in FIG. 6, BS 104 sends request message m601 to ME 108 and ME responds with a response message m602. Message m601 contain the same information as message m201 or it may contain the same information as message m501. Likewise, message m602 contain the same information as message m502.
[0082] As also shown in FIG. 6, BS 104 broadcasts a System Information Block (SIB) m603. The SIB broadcast by BS 104 indicates that the BS 104 supports IMS voice over NB-loT. For example, the SIB may include an IE that indicates the BS 104 supports IMS voice over NB-loT. UE 102 receives the SIB m603 and, based on the SIB, determines that BS 104 supports IMS voice over NB-loT.
[0083] As further shown in FIG. 6, at some point, UE 102 sends to BS 104 RRC message m503 comprising NAS message m505 to be processed by an ME selected by BS 104. In one embodiment, as a result of UE 102 determining, based on the SIB m603, that BS 104 supports IMS voice over NB-loT, UE 102 i) UE 102 include a VC indicator in RRC message m503 and / or ii) includes a VC indicator in NAS message m505. That is, for example, if SIB has not indicated IMS voice support over NB-loT, then UE 102 does not indicate its IMS voice over NB-loT capability in neither RRC message m503 nor NAS message m505.
[0084] After receiving RRC message m503, BS 104 determines that message m503 includes a VC indictor indicating that UE 102 supports IMS voice over NB-loT. As a result of determining, based on the VC indicator, that UE 102 supports IMS voice over NB-loT, BS 102 selects an ME that also supports IMS voice over NB-loT and forwards NAS message m505 to the selected ME, which in this case is ME 108. As noted above, in one embodiment ME 108 has provide to BS 104 in message m602 information indicating that the ME supports IMS voice over NB-loT and because BS 104 stored this information, BS 104 is able to determine that the ME 108 supports IMS voice over NB-loT. In another embodiment, BS 105 is informed that ME 108 supports IMS voice over NB-loT based on an CAM configuration.
[0085] After receiving NAS message m505, if VoPS is UE 102's voice domain preference, then ME 108 determines whether or not to indicate to UE 102 support for IMS voice. This determination may be based on i) whether or not message m505 indicates that UE 102 supports IMS voice over NB-loT, ii) whether BS 102 supports IMS voice over NB-loT, and / or iii) whether or not UE 102 is authorized to use the IMS voice over NB-loT, as described above in connection with the embodiment illustrated in FIGs. 4 and 5. In one embodiment, ME derives that the eNB is capable of IMS voice over NB-loT as a result of NAS message m505 indicating that UE 102 supports theIMS voice over NB-loT because UE, in this embodiment, does not include its capability in NAS message m505 unless BS 104 support IMS voice over NB-loT. The ME can also derive that BS 104 supports IMS voice over NB-loT in embodiments in which this information is expressly provided to ME 108, such as the embodiment described above with reference to FIG. 5 in which message m501 includes a capability indicator indicating that BS support the IMS voice over NB-loT.
[0086] If ME 108 determines that appropriate conditions are met (e.g., UE and BS both support the IMS voice service and UE is authorized to use the service), then as described above ME 108 set the "IMS VoPS” bit to ‘T, otherwise the bit is set to ‘O'.
[0087] FIG. 7 is a message flow diagram illustrating another embodiment. In the embodiment shown in FIG. 7, ME 108 supports IMS voice over NB-loT access, BS 104 is serving the NB-loT RAT, and UE 102 supports IMS voice over NB-loT and wishes to obtain IMS service. As shown in FIG. 7, BS 104 sends request message m201 to ME 108 as described above.
[0088] As also shown in FIG. 7, at some point, UE 102 sends to BS 104 RRC message m203 comprising NAS message m205 to be processed by an ME selected by BS 104. BS 104, after receiving RRC message m203, selects an ME and forwards NAS message m205 to the selected ME, which in this case is ME 108.
[0089] After receiving NAS message m205, ME 108 determines whether or not to indicate to UE 102 support for IMS voice. This determination is based on the RAT the request message m205 comes from and the UE's voice domain preference (VDP) indicated in message m205. For example, in one embodiment, ME 108 checks which RAT NAS message m205 comes from, and, if message m205 comes from the NB-loT RAT, then ME 108 checks if it supports IMS voice over NB-loT. If ME 108 does not support IMS voice over NB-loT, then ME 108 checks UE 102's VDP. If VoPS is the UE's voice domain preference, then ME 108 sets the "IMS VoPS” bit to ‘O' in "EPS network feature support” IE in response message m207.
[0090] If ME 108 supports IMS voice over NB-loT, then, ME 108, in response to i) determining that message m205 comes from the NB-loT RAT and ii) determining that VoPS is UE 102's voice domain preference, triggers a procedure to request BS 104 to provide information indicating whether or not the UE and the BS are capable of IMS voice over NB-loT. The existing UE Radio Capability Match procedure (see T 23.401 clause 5.3.14, 36.413 clause 8.3.5) can be extended to accomplish this, or a new S1 procedure between the BS and ME can used.
[0091] For example, as shown in FIG. 7, after receiving NAS message m205, ME 108 sends to BS 104 a request message m702, which may be the existing UE Radio Capability Match request message.
[0092] If BS 104 does not support IMS voice over NB-loT, or the BS is not able to decode / process the request message m702, then the response message m708 responsive to request message m702, which is sent from the BS to the ME, includes an error indication. In response to receiving message m708 with the error indication, theME derives that the BS does not support IMS voice over NB-loT and, as a consequence, sets the IMS VoPS bit to ‘O' in the response message m207 to the UE.
[0093] If BS 104 supports IMS voice over NB-loT and is able to decode and process message m702, then, if the BS is not aware of UE 102's capability for IMS voice over NB-loT, then the BS may send to UE 102 a request message m702, such as, for example, an RRC message to query UE's capability. The existing‘U ECapability Enquiry’ message (see TS 36.331 clause 5.6.3) can be extended, or a new RRC message / procedure is used.
[0094] In response to receiving message m704, UE 102 transmits to BS 104 a response message m706. Response message m706 may be an extended version of the ‘U ECapabi lity I nformation' message (see TS 36.331 clause 5.6.3) or a new RRC message is used.
[0095] If the UE supports IMS voice over NB-loT, then UE includes in message m706 a capability indicator indicating that the UE supports IMS voice over NB-loT.
[0096] If the UE does not support IMS voice over NB-loT, then UE includes in message m706 a capability indicator indicating that the UE does not support IMS voice over NB-loT.
[0097] In response to receiving response message 706 from the UE, the BS generates response message m708, which indicates whether or not the BS and the UE support IMS voice over NB-loT, and transmits response message m708 to ME 108.
[0098] In response to receiving response message m708, ME sets the IMS VoIP bit according to the information included in message m708.
[0099] RAT aware UE configuration[000100] In one embodiment, for each RAT supported by the UE (e.g., normal LTE, NB-loT, etc.), the UE will have a corresponding "Voice domain preference and UE's usage setting.” The UE will use the RAT specific configuration when accessing the network. The configuration for normal LTE access will be the same as today. The configuration for NB-loT access will look as follows, but can be customized by operator: UE's usage setting: Data centric; Voice domain preference: PS only. As described above, if the UE uses the Voice domain preference and UE's usage setting IE that is specific for NB-loT (e.g., Voice domain preference and UE's usage setting for NB-loT), then the ME 108 will know, based on the presence of the IE, that the UE is capable of IMS voice over NB-loT.[000101] FIG. 8 is a flow chart illustrating a process 800 performed by a UE according to an embodiment. Process 800 may begin in step s802. Step s802 comprises transmitting a first NAS message (m205, m305, m405, m505) comprising information indicating that voice over packet switched, VoPS, is a voice domain preference. Step s804 comprises receiving a second NAS message responsive to the first NAS message, wherein the second NASmessage indicates whether or not IMS voice over NB-loT is supported. In some embodiments, I) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE), ii) transmitting the first NAS message comprises the UE transmitting a Radio Resource Control (RRC) message comprising the first NAS message, wherein the RRC message further comprises a capability indicator indicating that the UE supports IMS voice over NB-loT, and / or ill) the method further comprises: after transmitting the first NAS message and prior to receiving the second NAS message, receiving a request message requesting capability information; and transmitting a response message responsive to the request message, the response message comprising information indicating that the UE supports IMS voice over NB-loT.[000102] FIG. 9 is a flow chart illustrating a process 900 performed by a UE according to an embodiment. Process 900 may begin in step s902. Step s902 comprises receiving a first NAS message generated by a UE, the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE. Step s904 comprises generating a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported. Step s906 comprises transmitting the seconds NAS message to the UE. In some embodiments, I) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT, ii) the method further comprises, prior to receiving the first NAS message, receiving from a base station a message (m501) indicating that the base station supports IMS voice over NB-loT and the base station forwarded the first NAS message to the network node, ill) the method further comprises, in response to receiving the first NAS message, determining, based on subscription information associated with the UE, whether or not the UE is authorized to use IMS voice over NB-loT, and / or iv) the method further comprises, in response to receiving the first NAS message, transmitting to the base station a request message and receiving from the base station a response message responsive to the request message wherein the response message indicates whether or not the UE supports IMS voice over NB-loT.[000103] FIG. 10 is a flow chart illustrating a process 1000 performed by a base station according to an embodiment. Process 1000 may begin in step s1002. Step s1002 comprises receiving a first NAS message generated by a UE, the first NAS message comprising information indicating that VoPS is a voice domain preference of the UE. Step s1004 comprises forwarding the first NAS message to an ME. In some embodiments, I) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT, ii) the method further comprises, prior to receiving the first NAS message, broadcasting system information, wherein the broadcast system information comprises a capability indicator indicating that the base station supports IMS voice over NB-loT, ill) the method further comprises, prior to receiving the first NAS message, transmitting to the ME a control message for establishing a logical connection with the ME, wherein the control message comprises a capability indicator indicatingthat the base station supports IMS voice over NB-loT, iv) receiving the first NAS comprises receiving a Radio Resource Control, RRC, message comprising first NAS and further comprising a capability indicator indicating that the UE supports IMS voice over NB-loT, and / or v) the method further comprises, after forwarding the first NAS message to the ME: receiving from the ME a first request for information regarding the UE; after receiving the request from the ME, sending to the UE a request for information, and receiving from the UE a response responsive to the second request, wherein the response indicate whether or not the UE supports IMS voice over NB-loT; and after receiving the response from the UE, sending to the ME a response indicating whether or not the UE supports IMS voice over NB-loT.[000104] Optimizations to Reduce Call Setup Time[000105] As noted above, call set up times should, preferably, not exceed 30 seconds, But given the limited bandwidth in NB-loT GEO (e.g., 1 kbits - 3kbits), for IMS voice over NB-loT (GEO) access, the transmission of each message (e.g., SIP signaling and EPC signaling) to setup the IMS voice call between UE and network may take a long time, and thus lead to a long call setup time (approximately 90 seconds) unless optimizations are introduced. The EPC signaling refers to the dedicated bearer setup procedure, that is triggered by the Proxy Call Session Control Function (P-CSCF) towards the Policy Charging and Rules Function (PCRF) and then towards the Packet Gateway (PGW). In a normal IMS voice call setup signaling flow, there will be 3 RRC messages between the UE and the network to setup the dedicated bearer for voice media. These three RRC message are the: RRC connection reconfiguration message, RRC connection reconfiguration complete message, and the RRC direct transfer message.[000106] If the dedicated bearer is already activated in combination with the default bearer activation at attach procedure or PDN connectivity procedure as specified in TS 23.401 Annex F, there is no need to activate the dedicated bearer during voice call setup. Instead there will be only two RRC messages (two RRC direct transfer messages) during the call setup. These two RRC messages are used to update the UE's Traffic Flow Template (TFT) for uplink (UL) packet filter, see TS 24.301, clause 9.9.4.16 or TS 24.008, clause 10.5.6.12. The TFT contains a 5-tuple for the voice media flow and PGW creates the TFT based on the IP filter information in the Policy and Charging Control (PCC) rules received from PCRF. The 5-tuple consists of: source IP address, source port number, destination IP address, destination port number, and protocol identifier (e.g., Transmission Control Protocol (TCP) or User Datagram Protocol (UDP)). The PCRF creates the PCC rules based on session information received from P-CSCF when it receives the SIP message from the remote side. So, during the call setup, there will be only a need to modify the dedicated bearer, rather than creating a new one. But, with such pre-established dedicated bearer, the saving from 3 RRC messages to 2 RRC messages may still not be enough for the call setup time in NB-loT (GEO).[000107] This disclosure, therefore, proposes pre-allocating the TFT for the pre-established dedicated bearer so that the dedicated bearer establishment can be done earlier and that bearer modification during call setupis avoided, thereby reducing the call setup time. The TFT pre-allocation can take place: 1) at the attach procedure or UE request PDN connectivity request procedure; 2) at the SIP registration; or 3) at the SIP Invite.[000108] For example, this disclosure provide a method that enables the dedicated bearer establishment for IMS voice call before the SIP negotiation for the IMS voice call. This allows the dedicated bearer establishment to be skipped in the call setup flow to reduce the call setup time. Moreover, pre-allocated TFT does not cost network resources in IMS, as the IP or port number used for the call is still assigned during the call, it isjust the IP range / port range is specified and pre-allocated.[000109] 1. Pre-allocated TFT for dedicated bearer during attach procedure or UE requested PDN connectivity procedure[000110] FIG. 14 is a message flow diagram based on TS 23.401 Annex F, Figure F.1, where the dedicated bearer is activated in combination with the default bearer activation at UE attach or UE requested PDN connectivity procedure.[000111] Step 1: UE 102 transmits a NAS message m1401 (e.g., an Attach Request or PDN connectivity request), which is received by ME 108, which in this example, which is a 4G example, is an MME (if this were a 5G example, then ME 108 would be an AMF).[000112] Steps 2 and 3: MME 108, after receiving NAS message ml 401 , transmits a create session request message m1403 to a Serving Gateway (SGW) 191, which then transmits a create session request message m1405 to a PGW 192 (if this were a 5G example, then PGW 192 would be a Session Management Function (SMF)).[000113] Step 4: PGW 192, after receiving message m1405, transmits a Credit Control Request (CCR) message m1407 to a PCRF 193 (if this were a 5G example, then PCRF 193 would be a Policy Charging Function (PCF)). In this embodiment, PGW 192 includes a new indication in CCR message m1407 requesting the PCRF to provide one or more pre-allocated TFT data elements. Also included in CCR message m1407 may be one or more P-CSCF identifiers (e.g., one or more P-CSCF addresses).[000114] Step 5: In response to CCR message m1407, which requests at least one pre-allocated TFT data element (e.g., a pre-allocated TFT, a pre-allocated portion of a TFT, or pre-allocated TFT information that can be used to create a TFT), PCRF 193 sends to PGW 192 a Credit Control Answer (CCA) message m1409 containing at least a first pre-allocated TFT data element. For example, in one embodiment, a pre-allocated TFT data element comprises the following pieces of information: (I) a source network address (e.g., IP address), (II) a source port number, (ill) a destination network address or information specifying a range of network addresses, and (iv) a destination port number or information specifying a range of port numbers. In some embodiments, the pre-allocated TFT further includes a protocol identifier identifying a transport protocol; in such an embodiment the pre-allocatedTFT comprises a 5-tuple (i.e. , five pieces of information). Hence, a pre-allocated TFT data element may include one or more information elements (lEs).[000115] The pre-allocated TFT data element included in CCA message m1409 identifies one or more network addresses (e.g., a range of IP addresses) and / or more port numbers (e.g., a range of port numbers) used for the voice media traffic transmitted over the dedicated bearer.[000116] The pre-allocated TFT data element may be P-CSCF specific. For example, if CCR message m1407 includes a P-CSCF identifier (e.g., address), then, in response to receiving the CCR message, PCRF 193 may use the P-CSCF identifier to select one or more pre-allocated TFT data element associated with the P-CSCF identifier from the two or more pre-allocated TFT data elements locally configured at the PCRF.[000117] Step 6: After receiving the CCA message, the PGW creates a TFT for the UE's UL packet filter based on the pre-allocated TFT data element in the CCA message from the PCRF and includes the TFT in a Create Bearer Request message m1411 which is sent by the PGW to the SGW as a response to the create session request message m1405. If CCA message contains more than one pre-allocated TFF data element, then the PGW may create a TFT for each one of the pre-allocated TFF data elements and include the created TFTs in message m1411.[000118] In some embodiments, the PGW can also be locally configured with one or more pre-allocated TFT data elements and such pre-allocated TFT data elements can be per P-CSCF. Hence, in such an embodiment, for example, the PGW can use one of its locally configured pre-allocated TFT data elements to create the TFT that will be sent to the SGW. In some embodiments, however, a PCRF provided pre-allocated TFT data element, may overrider the PGW locally configured pre-allocated TFT data element.[000119] Steps 7-11: these steps are conventional call setup steps.[000120] Step 12: During the call setup, when the PGW receives a Re-Authorizaton Request (RAR) message ml 413 with a PCC rule containing a flow description (e.g., an n-tuple including at least a source network address, a source port number, a destination network address, and destination port number) for the voice media flow, the PGW verifies if the flow description in the PCC rule in the RAR matches at least one of the one or more preallocated TFT data elements received in message m1409. In one embodiment, the flow description in the PCC rule in the RAR matches a pre-allocated TFT data element if the flow defined by the flow description in the PCC rule is the same as a flow defined a pre-allocated TFT data element. As a specific example, if the flow description consist of a 5-tuple consisting of a specific source network address, a specific source port number, a specific destination network address, a specific destination port number, and a specific protocol identifier and if the pre-allocated TFT data element comprises a source network address, a source port number, information specifying a range of destination network addresses, information specifying a range of destination port numbers, and protocol identifier, then the flow description will "match” the pre-allocated TFT data element if: I) the specific source network address isthe same as the source network address in the pre-allocated TFT data element, ii) the specific source port address is the same as the source port address in the pre-allocated TFT data element, iii) the specific destination network address falls within the range of destination network addresses defined by the pre-allocated TFT data element, iv) the specific destination port address falls within the range of destination port numbers defined by the pre-allocated TFT data element, and v) the specific protocol identifier is the same as the protocol identifier included in the preallocated TFT date element.[000121] If the flow description in the PCC rule matches at least one of the pre-allocated TFT data element, then the PGW does not trigger the bearer modification procedure, otherwise the PGW triggers the bearer modification procedure to update UE's TFT in dedicated bearer.[000122] The rest of the steps are the same as existing procedure. The dedicated bearer is activated before the IMS voice call. When UE initiates the IMS voice call, the dedicated bearer establishment or the dedicated bearer modification are skipped.[000123] 2. Pre-allocated TFT for dedicated bearer during SIP REGISTRATION[000124] FIG. 15 is a message flow diagram showing the establishment of the dedicated bearer for IMS voice call during the SIP registration phase. In this embodiment, the call setup time can be reduced because there is already dedicated bearer established during SIP registration.[000125] Step 1: After performing the Attach and PDN Connection Establishment procedures, UE 102 transmits a SIP register message m1501, which is received by a P-CSCF 194.[000126] Step 2: After receiving the SIP register message m1501 (e.g., in response to receiving the SIP register message or in response to determining a successful SIP registration for the UE), the P-CSCF sends to the PCRF an Authorization Authentication Request (AAR) message m1503 to provision the pre-allocated TFT to EPC. The P-CSCF includes in the AAR message a pre-allocated TFT data element, which is described above. That is, for example, the pre-allocated TFT data element includes IP address range data identifying an IP address range and / or port range data identifying a port range that is used for voice media traffic later during the IMS voice call. For example, in one embodiment, in response to register message m1501, CF initiates the conventional IMS registration procedure and if this is successful (i.e., the UE is successfully registered), then CF sends AAR message with the preallocated TFT data element.[000127] Step 3: After receiving the AAR message, the PCRF sends to the PGW an RAR message m1505 comprising the pre-allocated TFT data element included in the AAR message to trigger the dedicated bearer setup procedure. For example, in some embodiments, in response to receiving the RAR message with the pre-allocated TFT data element, the PGW creates a TFT for the UE's UL packet filter based on the pre-allocated TFT data elementin the RAR message and includes the TFT in a Create Bearer Request message (see e.g., message m1411) which is sent by the PGW to the SGW.[000128] 3. Pre-allocated TFT for dedicated bearer during SIP INVITE[000129] Usually, the dedicated bearer establishment is triggered when the P-CSCF receives a SIP Progress from a called UE 195 (a.k.a., remote UE).[000130] FIG. 16 is a message flow diagram showing establishment of the dedicated bearer for IMS voice call when the P-CSCF receives the SIP INVITE message (based on 3GPP TS 29.213 Figure B.2.1.2) and skip the bearer operation when the P-CSCF receives the SDP answer from the called UE side. This embodiment allows the dedicated bearer setup to begin from the SIP INVITE, so that the time period between SIP INVITE and SIP Progress (from the called UE side) can be utilized to reduce the total call setup time. This option does not pre-activate the dedicated bearer before a voice call is triggered, but it triggers dedicated bearer establishment earlier during the voice call setup, before the remote party has replied and before the exact IP filters for voice media are known.[000131] Step 1: After performing the Attach, PDN Connection Establishment, and IMS registration procedures, UE 102 transmits a SIP invite message m1601, which is received by the P-CSCF.[000132] Step 2: In response to receiving the SIP invite message m1601, the P-CSCF sends to the PCRF an AAR message m1603 to provision the pre-allocated TFT to EPC. The P-CSCF includes in the AAR message a pre-allocated TFT data element, which is described above. That is, for example, the pre-allocated TFT data element includes IP address range data identifying an IP address range and / or port range data identifying a port range that is used for voice media traffic later during the IMS voice call.[000133] Step 3: After receiving the AAR message, the PCRF sends to the PGW an RAR message m1605 comprising the pre-allocated TFT data element included in the AAR message to trigger the dedicated bearer setup procedure. For example, in some embodiments, in response to receiving the RAR message with the pre-allocated TFT data element, the PGW creates a TFT for the UE's UL packet filter based on the pre-allocated TFT data element in the RAR message and includes the TFT in a Create Bearer Request message (see e.g., message m1411) which is sent by the PGW to the SGW.[000134] FIG. ZZ1 is a block diagram of UE 102, according to some embodiments. As shown in FIG. ZZ1, UE 102 may comprise: processing circuitry (PC) ZZ102, which comprises one or more processors (P) ZZ155 (e.g., one or more general purpose microprocessors and / or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like); communication circuitry ZZ148, which is coupled to an antenna arrangement ZZ149 comprising one or more antennas and which comprises a transmitter (Tx) ZZ145 and a receiver (Rx) ZZ147 for enabling UE 102 to transmit data and receive data (e.g., wirelessly transmit / receive data); and a storage unit (a.k.a., "data storage system”) ZZ108, which may include one ormore non-volatile storage devices and / or one or more volatile storage devices. In embodiments where PC ZZ102 includes a programmable processor, a computer readable storage medium (CRSM) ZZ142 may be provided. CRSM ZZ142 may store a computer program (CP) ZZ143 comprising computer readable instructions (CRI) ZZ144. CRSM ZZ142 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI ZZ144 of computer program ZZ143 is configured such that when executed by PC ZZ102, the CRI causes UE 102 to perform steps described herein (e.g., steps described herein with reference to the flow charts). In other embodiments, UE 102 may be configured to perform steps described herein without the need for code. That is, for example, PC ZZ102 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and / or software[000135] FIG. ZZ2 is a block diagram of a network node ZZ200, according to some embodiments, which can be used to implement any of the core network function described herein, including, for example, ME 108, PGW 192, PCRF 193, P-CSCF 194, etc. In embodiments where such a core network function consists of software, network node 600 may run the network function or execute a virtual machine that runs the network function. As shown in FIG. ZZ2, network node ZZ200 may comprise: processing circuitry (PC) ZZ202, which comprises one or more processors (P) ZZ255 (e.g., one or more general purpose microprocessors and / or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (e.g., network node ZZ200 may be a distributed, cloud computing system comprising two or more computers or a monolithic computing system consisting of a single computer); at least one network interface ZZ248 (e.g., a physical interface or air interface) comprising a transmitter (Tx) ZZ245 and a receiver (Rx) 7 2M for enabling network node ZZ200 to transmit data to and receive data from other nodes connected to network 110 (e.g., an Internet Protocol (IP) network) to which network interface ZZ248 is connected (physically or wirelessly) (e.g., network interface ZZ248 may be coupled to an antenna arrangement comprising one or more antennas for enabling network node ZZ200 to wirelessly transmit / receive data); and a storage unit (a.k.a., "data storage system”) ZZ208, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments where PC ZZ202 includes a programmable processor, a computer readable storage medium (CRSM) 7 2M may be provided. CRSM 7 2M may store a computer program (CP) ZZ243 comprising computer readable instructions (CRI) ZZ244. CRSM 7 2M may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI ZZ244 of computer program ZZ243 is configured such that when executed by PC ZZ202, the CRI causes network node ZZ200 to perform steps described herein (e.g., steps described herein with reference to the flow charts). In other embodiments, network node ZZ200 may be configured to perform steps described hereinwithout the need for code. That is, for example, PC ZZ202 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and / or software.[000136] FIG. ZZ3 is a block diagram of BS 104, according to some embodiments for performing the base station methods disclosed herein. As shown in FIG. ZZ3, BS 104 may comprise: processing circuitry (PC) ZZ302, which comprises one or more processors (P) ZZ355 (e.g., a general purpose microprocessor and / or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like), which processors may be co-located in a single housing or in a single data center or may be geographically distributed (e.g., BS 104 may be a distributed, cloud computing system comprising two or more computers or a monolithic computing system consisting of a single computer); a network interface ZZ368 comprising a transmitter (Tx) ZZ365 and a receiver (Rx) ZZ367 for enabling base station 104 to transmit data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network) to which network interface ZZ368 is connected; communication circuitry ZZ348 (e.g., radio transceiver circuitry comprising an Rx ZZ347 and a Tx ZZ345) coupled to an antenna system ZZ349 for wireless communication with UEs or other nodes; and a storage unit (a.k.a., "data storage system”) ZZ308, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments where PC ZZ302 includes a programmable processor, a computer readable storage medium (CRSM) ZZ342 may be provided. CRSM ZZ342 may store a computer program (CP) ZZ343 comprising computer readable instructions (CRI) ZZ344. CRSM ZZ342 may be a non-transitory computer readable medium, such as, magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory, flash memory), and the like. In some embodiments, the CRI ZZ344 of computer program ZZ343 is configured such that when executed by PC ZZ302, the CRI causes base station 104 to perform steps described herein (e.g., steps described herein with reference to one or more flow charts). In other embodiments, base station 104 may be configured to perform steps described herein without the need for code. That is, for example, PC ZZ302 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and / or software.[000137] Summary of Various EmbodimentsA1. A method performed by a user equipment, UE (102), the method comprising:transmitting a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) comprising information indicating that voice over packet switched, VoPS, is a voice domain preference; andreceiving a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported, characterized in that:I) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE),ii) transmitting the first NAS message comprises the UE transmitting a Radio Resource Control (RRC) message comprising the first NAS message, wherein the RRC message further comprises a capability indicator indicating that the UE supports IMS voice over NB-loT, and / orill) the method further comprises:after transmitting the first NAS message and prior to receiving the second NAS message, receiving a request message requesting capability information; andtransmitting a response message responsive to the request message, the response message comprising information indicating that the UE supports IMS voice over NB-loT.A2. The method of embodiment A1, whereintransmitting the first NAS message comprises the UE transmitting the RRC message comprising the first NAS message and the capability indicator indicating that the UE supports IMS voice over NB-loT,the RRC message is transmitted to a base station using an NB-loT radio access technology, RAT, the method further comprises receiving system information broadcast by the base station, and the UE is configured to include the capability indicator in the RRC message after determining that the system information indicates that the base station supports IMS voice over NB-loT.A3. The method of embodiment A1, whereintransmitting the first NAS message comprises the UE transmitting an RRC message to a base station using an NB-loT radio access technology, RAT.A4. The method of any previous embodiment, whereinthe second NAS message was transmitted by a management entity (ME) of a core network (e.g., an MME or an AMF), andthe second NAS message indicates whether or not the ME supports IMS voice over NB-loT.A5. The method of any previous embodiment, whereinthe first NAS message includes the capability indicator indicating that the UE supports IMS voice over NB-loT, andthe capability indicator is a RAT aware UE configuration.B1. A method performed by a network node, the method comprising:receiving a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE; andgenerating a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported; andtransmitting the seconds NAS message to the UE, characterized in that:i) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE),ii) the method further comprises, prior to receiving the first NAS message, receiving from a base station a message (m501) indicating that the base station supports IMS voice over NB-loT and the base station forwarded the first NAS message to the network node,ill) the method further comprises, in response to receiving the first NAS message, determining, based on subscription information associated with the UE, whether or not the UE is authorized to use IMS voice over NB-loT, and / oriv) the method further comprises, in response to receiving the first NAS message, transmitting to the base station a request message and receiving from the base station a response message responsive to the request message wherein the response message indicates whether or not the UE supports IMS voice over NB-loT.B2. The method of embodiment B1, wherein the method further comprises, in response to receiving the first NAS message:obtaining from a subscription data manager (e.g., HSS or UDM) subscription information associated with the UE; anddetermining, based on the subscription information associated with the UE, whether or not the UE is authorized to use IMS voice over NB-loT.B3.The method of embodiment B1 or B2, whereinthe method further comprises, prior to receiving the first NAS message, receiving from a base station a message (m501) indicating that the base station supports IMS voice over NB-loT, wherein the base station forwarded the first NAS message to the network node, andthe method further comprises, in response to receiving the message from the base station; sending a response message to the base station, wherein the response message indicates that the network node supports IMS voice over NB-loT.C1. A method performed by a base station, the method comprising:receiving a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE; andforwarding the first NAS message to a management entity, ME,characterized in that:i) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE), ii) the method further comprises, prior to receiving the first NAS message, broadcasting system information, wherein the broadcast system information comprises a capability indicator indicating that the base station supports IMS voice over NB-loT,ill) the method further comprises, prior to receiving the first NAS message, transmitting to the ME a control message for establishing a logical connection with the ME, wherein the control message comprises a capability indicator indicating that the base station supports IMS voice over NB-loT, iv) receiving the first NAS comprises receiving a Radio Resource Control, RRC, message comprising first NAS and further comprising a capability indicator indicating that the UE supports IMS voice over NB-loT, and / orv) the method further comprises, after forwarding the first NAS message to the ME:receiving from the ME a first request for information regarding the UE;after receiving the request from the ME, sending to the UE a request for information; receiving from the UE a response responsive to the second request, wherein the response indicate whether or not the UE supports IMS voice over NB-loT; andafter receiving the response from the UE, sending to the ME a response indicating whether or not the UE supports IMS voice over NB-loT.C2. The method of embodiment C1, whereinthe method further comprises, prior to receiving the first NAS message, transmitting to the ME the control message for establishing the logical connection with the network node; andthe method further comprises receiving from the ME a response message (m502) responsive to the control message, wherein the response message indicates that the ME supports IMS voice over NB-loT.C3.The method of embodiment C1 or C2, whereinreceiving the first NAS comprises receiving an RRC message comprising first NAS and further comprising a capability indicator indicating that UE supports IMS voice over NB-loT, andthe method further comprises:determining that the RRC message indicates that the UE supports IMS voice over NB-loT; as a result of determining that the RRC message indicates that the UE supports IMS voice over NB-loT, selecting an ME that supports IMS voice over NB-loT; andtransmitting the first NAS message to the selected ME.D1. A method 1700 (see FIG. 17) performed by a first network node (e.g., a network node implementing a PGW or SMF or other like management function), the method comprising:receiving (step s1702) from a second network node (e.g., a network node implementing a policy function such as a PCRF or PCF) a message including at least a first pre-allocated traffic flow template, TFT, data element.D2. The method of embodiment D1, wherein the method further comprises:creating a first TFT using the first pre-allocated TFT data element; andproviding to a third network node (e.g., network node implementing a serving gateway) a message comprising the first TFT.D3. The method of embodiment D1 or D2, whereinthe method further comprises, prior to receiving from the second network node the message comprising the first pre-allocated TFT data element, providing to the second network node a request message for triggering the second network node to provide to the first network node one or more pre-allocated TFT data elements, andthe request message comprises and indicator indicating that the first network node is requesting the second network node to provide to the first network node one or more pre-allocated TFT data elements (the request message may further include one or more P-CSCF identifiers).D4. The method of embodiment D3, whereinthe method further comprises prior to providing the request message to the third network node, receiving from the third network node a create session message, andthe create session message, triggers the first network node to transmit the request message to the second network node.D5. The method of any one of embodiments D1-D4, wherein the method further comprises:receiving from the second network node a message comprising a flow description;determining if the flow description matches the first pre-allocated TFT data element; andif the flow description matches the first pre-allocated TFT data element, then the first network node refrains from triggering a bearer modification procedure.D6. The method of embodiment D1 or D2, whereinthe message comprising the first pre-allocated TFT data element is a Re-Authorizaton Request, RAR, message for triggering a dedicated bearer setup procedure.E1. A method 1800 (see FIG. 18) performed by a first network node (e.g., PCRF / PCF or P-CSCF), the method comprising:providing (step s1802) to a second network node (e.g., a network node implementing a PGW / SMF or PCRF or PCF) a message including at least a pre-allocated traffic flow template (TFT) data element.E2. The method of embodiment E1, wherein the first network node implements a P-CSCF, and the second network node implements a policy function (e.g., a PCRF or a PCF).E3. The method of embodiment E2, whereinthe method further comprises prior to providing the first pre-allocated TFT data element to the policy function, receiving a session initiation protocol, SIP, message transmitted by a user equipment, UE, andthe SIP message triggers the P-CSCF to provide the first pre-allocated TFT data element to the policy function, orthe SIP message triggers a registration procedure, and a successful completion of the registration procedure triggers the P-CSCF to provide the pre-allocated TFT data element to the PCRF.E4. The method of embodiment E3, wherein the SIP message is a SIP register message for initiating the registration procedure and a successful completion of the registration procedure triggers the P-CSCF to provide the first pre-allocated TFT data element to the PCRF.E5. The method of embodiment E3, wherein the SIP message is a SIP invite message for initiating a SIP call and the SIP invite message triggers the P-CSCF to provide the first pre-allocated TFT data element to the policy function.E6. The method of embodiment E1, wherein the first network node implements a policy function, PF (e.g., a PCRF or PCF), and the second network node implements a PGW or SMF.E7. The method of embodiment E6, whereinthe method further comprises prior to providing the first pre-allocated TFT data element to the second network node, receiving a request from the second network node, andthe request from the second network node comprises an indicator that triggers the PF to provide the first pre-allocated TFT data element to the second network node.E8. The method of embodiment E6, whereinthe method further comprises prior to providing the first pre-allocated TFT data element to the second network node, receiving from a third network node a message comprising the first pre-allocated TFT, andthe message from the third network node triggers the PF to provide the first pre-allocated TFT data element to the second network node.F1. A method 1900 (see FIG. 19) performed by a first network node (e.g., PGW, SMF), the method comprising:receiving (step s1902) a request from a second network node (e.g., SGW, AMF);after receiving the request, creating (step s1904) a TFT based on a locally configured pre-allocated TFT data element; andsending (step s1906) to the second network node a response message responsive to the request message, wherein the response message comprises the created TFT.F2. The method of embodiments F1, wherein the method further comprises:receiving from a third network node a message comprising a flow description;determining if the flow description matches the locally configured pre-allocated TFT data element; and if the flow description matches the locally configured pre-allocated TFT data element, then the first network node refrains from triggering a bearer modification procedure.G1. A non-transitory computer readable storage medium storing a computer program comprising instructions for configuring an apparatus comprising processing circuitry capable of executing the instructions to perform the method of any one of the previous claims.G2. A carrier containing the computer program of claim G1, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.H1. A user equipment, UE (102), the UE being configured to perform a method comprising:transmitting a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) comprising information indicating that voice over packet switched, VoPS, is a voice domain preference; andreceiving a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported, characterized in that:i) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE),ii) transmitting the first NAS message comprises the UE transmitting a Radio Resource Control (RRC) message comprising the first NAS message, wherein the RRC message further comprises a capability indicator indicating that the UE supports IMS voice over NB-loT, and / orill) the method further comprises:after transmitting the first NAS message and prior to receiving the second NAS message, receiving a request message requesting capability information; andtransmitting a response message responsive to the request message, the response message comprising information indicating that the UE supports IMS voice over NB-loT.H2. The UE of embodiment H1, wherein the UE is further configured to perform the method of any one of embodiments A2-A5.11. A network node, the network node being configured to perform a method comprising:receiving a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE; andgenerating a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported; andtransmitting the seconds NAS message to the UE, characterized in that:i) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE),ii) the method further comprises, prior to receiving the first NAS message, receiving from a base station a message (m501) indicating that the base station supports IMS voice over NB-loT and the base station forwarded the first NAS message to the network node,iii) the method further comprises, in response to receiving the first NAS message, determining, based on subscription information associated with the UE, whether or not the UE is authorized to use IMS voice over NB-loT, and / oriv) the method further comprises, in response to receiving the first NAS message, transmitting to the base station a request message and receiving from the base station a response message responsive to the request message wherein the response message indicates whether or not the UE supports IMS voice over NB-loT.12. The network node of embodiment 11, wherein the network node is further configured to perform the method of embodiment B2 or B3.J1. A base station, the base station being configured to perform a method comprising:receiving a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE; andforwarding the first NAS message to a management entity, ME,characterized in that:i) the first NAS message includes a capability indicator indicating that the UE supports IMS voice over NB-loT (e.g., a 1 bit IE or a RAT specific Voice domain preference and UE's usage setting IE), ii) the method further comprises, prior to receiving the first NAS message, broadcasting system information, wherein the broadcast system information comprises a capability indicator indicating that the base station supports IMS voice over NB-loT,iii) the method further comprises, prior to receiving the first NAS message, transmitting to the ME a control message for establishing a logical connection with the ME, wherein the control message comprises a capability indicator indicating that the base station supports IMS voice over NB-loT, iv) receiving the first NAS comprises receiving a Radio Resource Control, RRC, message comprising first NAS and further comprising a capability indicator indicating that the UE supports IMS voice over NB-loT, and / orv) the method further comprises, after forwarding the first NAS message to the ME:receiving from the ME a first request for information regarding the UE, after receiving the request from the ME, sending to the UE a request for information, receiving from the UE a response responsive to the second request, wherein the response indicate whether or not the UE supports IMS voice over NB-loT; andafter receiving the response from the UE, sending to the ME a response indicating whether or not the UE supports IMS voice over NB-loT.J2. The base station of embodiment J1, wherein the base station is further configured to perform the method of embodiment C2 or C3.K1. A network node, the network node comprising a receiver for receiving (s1702) from a second network node (e.g., a network node implementing a policy function such as a PCRF or PCF) a message including at least a first pre-allocated traffic flow template, TFT, data element.K2. The network node of embodiment K1, wherein the network node is configured to perform the method of any one of embodiments D2-D6.L1. A network node, the network node being configured to:provide (s1802) to a second network node (e.g., a network node implementing a PGW / SMF or PCRF or PCF) a message including at least a first a pre-allocated traffic flow template (TFT) data element.L2. The network node of embodiment L1, wherein the network node is configured to perform the method of any one of embodiments E2-E8.M1. A network node being configured to perform a method comprising:receiving (s1902) a request from a second network node (e.g., SGW, AMF);after receiving the request, creating (s1904) a TFT based on a locally configured pre-allocated TFT data element; andsending (s1906) to the second network node a response message responsive to the request message, wherein the response message comprises the created TFT.M2. The network node of embodiment M1, wherein the method further comprises:receiving from a third network node a message comprising a flow description;determining if the flow description matches the locally configured pre-allocated TFT data element; and if the flow description matches the locally configured pre-allocated TFT data element, then the first network node refrains from triggering a bearer modification procedure.[000138] Additional Details[000139] This disclosure proposes providing support for IMS voice call over NB-loT NTN via GEO satellite connecting to an Evolved Packet Core (EPC).[000140] 6.x Solution #X: Reuse existing LTE user plane (UP) solution as baseline for IMS voice over NB-loT (GEO)[000141] 6.X.1 High level principles[000142] This solution proposes to use existing IMS voice support in WB-E-UTRAN as baseline to support IMS voice over GEO NB-loT.[000143] 6. x.2 Description[000144] NB-loT is specifically developed to enhance device power efficiency, system capacity etc., focusing on small and infrequent data transfers. As a result, it has fewer system features compared to WB-E-UTRAN. This solution suggests adding missing features needed for establishing the IP-CAN for IMS voice call in case of GEO NB-loT.[000145] Below are the key principles:[000146] UE indicates its support of IMS voice over NB-loT (GEO) in Attach / TAU request.[000147] MME indicates IMS voice over PS session is supported to UE.[000148] UE and network establish SGI PDN connection in IMS APN using S1-U, the default bearer with QCI 5.[000149] When initiating the IMS voice call, UE and the network establish dedicated bearer with QC1 1 (GBR bearer).[000150] Package Gateway (PGW) allows GBR bearer to be created in IMS APN for GEO NB-loT RAT.[000151] 6.X.3 Procedures[000152] 6.X.3.1 Initial Attach (UE attach in NB-loT (GEO)) (see FIG. 11)[000153] During the attach procedure:[000154] UE indicates its support of IMS voice over NB-loT (GEO) in the attach request message (e.g., as described above). It helps the network to distinguish the UE with only support of IMS voice over normal LTE access and the UE with enhanced functionality of supporting IMS voice over NB-loT (GEO) access.[000155] It is up to the operator's policy whether the well-known IMS APN is used as default APN in the attach procedure. Using well-known IMS APN during UE attach can reduce the time for UE to be ready for IMS voicecall and reduce the needed resources (e.g. number of DRBs), but consequently there is risk that UE may not get data service or even reject the network.[000156] If the well-known IMS APN is used during attach:[000157] I) The procedure described in clause 6.X.3.2 is skipped;[000158] ii) MME establishes default bearer with eNB using S1-U and UE (not shown in the figure);[000159] iii) The P-CSCF address is provided to the UE when activating the default bearer;[000160] iv) UE proceeds with IMS registration after successful attach. P-CSCF can obtain RAT of the IP-CAN by subscribing to the IP-CAN Type Change with PCRF during the SIP registration, as described in 3GPP TS 29.213 Annex B.1a.[000161] One optimization to reduce the call setup time is to activate the dedicated bearer prior to the IMS voice call setup (e.g. at the attach procedure as described in 3GPP TS 23.401 Annex F), with following considerations:[000162] (1) PGW creates uplink packet filter (see 3GPP TS 23.060 clause 15.3.3.4 for examples) effectively disallow useful packet flow in the uplink direction in this pre-established dedicated bearer for voice media; during the call setup phase, there will be a dedicated bearer modification procedure (see 3GPP TS 23.401 clause 5.4.3) for updating the TFT, where 2 RRC messages (direct transfer) are used between UE and eNB instead of 3 RRC messages (reconfiguration / complete / direct transfer) if the dedicated bearer is established during call setup phase; or[000163] (2) PGW is configured with a range of destination IP addresses and a range of destination port numbers that will be used for the IMS voice media traffic; and PGW creates uplink packet filter based on this configuration and provides to the UE- with this approach, the dedicated bearer modification is also skipped, thus leading to a saving of 3 RRC messages comparing to normal call setup signaling flow.[000164] The above EPC optimization requires E2E evaluation together with the rest of the system. For example, the IMS SIP signaling transmission currently contributes most of the CST, given the SIP signaling message size is larger than RRC message, whether saving of RRC messages would make comparable impact to CST is to be accessed. Also, it requires coordination with RAN whether it is feasible to grant a GBR bearer for each connected UE that using IMS APN.[000165] It is up to the operator's policy whether to enable attach without PDN connection to optimize the resources, e.g. reduce the total number of data radio bearers (DRBs) for the UE. If attach without PDN connection is enabled and used between UE and network, step 5-8 and step 11 / 12 are skipped.[000166] MME verifies with HSS if the subscription data allows the UE to use IMS voice over NB-loT (GEO) and indicates IMS voice over PS session is supported to the UE in attach accept.[000167] 6.X.3.2 PDN connection in IMS APN (see FIG. 12)[000168] This applies when there is no PDN connection established for the well-known IMS APN during attach and the subscriber is allowed to use IMS voice over NB-loT (GEO) according to subscription data:[000169] The NB-loT (GEO) RAT is passed to PGW during the create session procedure. The PGW can make use of this information to grant dedicated bearer to be created in IMS APN PDN connection.[000170] MME instructs eNB to setup E-RAB for the default bearer of the IMS APN PDN connection.[000171] QCI 5 is used for the default bearer.[000172] In case the UE is attached without PDN connection, S1-AP message in step 7 / 9 is replaced with initial context setup request / response.[000173] After PDN connection established in IMS APN, the UE performs IMS registration. P-CSCF can obtain RAT of the IP-CAN by subscribing to the IP-CAN Type Change with PCRF during the SIP registration, as described in 3GPP TS 29.213 Annex B.1a.[000174] The same optimization to activate the dedicated bearer during the PDN connection establishment described above can be applied here.[000175] 6.X.3.3 Dedicated Bearer Establishment for voice call (see FIG. 13)[000176] When IMS voice call is initiated: I) PCRF receives the request from IMS, triggers new PCC rule to be installed with PGW, ii) PGW verifies the new PCC rule is for IMS voice call in NB-loT (GEO) and proceeds to create dedicated bearer, ill) QC1 1 is used for the dedicated bearer (GBR bearer), iv) MME requests eNB to setup E-RAB with QC1 1 and activate dedicated EPS bearer with UE, v) If P-CSCF has requested access network location info (e.g. UE location) in step 3, the PCRF provides such information in step 16, as described in 3GPP TS 29.214 Annex A.10.[000177] If the dedicated bearer is already established at attach or PDN connection establishment, then step 0 additionally needs to include the UP setup for dedicated bearer and steps 7 to 14 can either be replaced by steps 2 to 9 described in TS 23.401 clause 5.4.3, or skipped.[000178] Impacts to Services, Entities and Interfaces[000179] The following are the new impact when UE is accessing NB-loT (GEO) via a satellite:[000180] UE: Indicating support of IMS voice over NB-loT (GEO) in Attach / TAU request; Support dedicated EPS bearer; and Optionally, support more than two simultaneous DRBs.[000181] RAN: Support GBR bearer with QC1 1 and Optionally, support more than two simultaneous DRBs per UE.[000182] MME: Support indicating IMS Voice over PS session supported to UE and Optionally, control the maximum number of radio bearer user plane to be created.[000183] HSS: Subscription data indicating whether IMS voice over NB-loT (GEO) is allowed.[000184] PGW: Allow voice bearer (i.e. GBR bearer with QCI=1) to be created in IMS APN.[000185] While various embodiments are described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of this disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.[000186] As used herein transmitting a message "to” or "toward” an intended recipient encompasses transmitting the message directly to the intended recipient or transmitting the message indirectly to the intended recipient (i.e., one or more other nodes are used to relay the message from the source node to the intended recipient). Likewise, as used herein receiving a message "from” a sender encompasses receiving the message directly from the sender or indirectly from the sender (i.e., one or more nodes are used to relay the message from the sender to the receiving node). Further, as used herein "a” means "at least one” or "one or more.”[000187] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.[000188] References[000189]
[0001] 3GPP Technical Document S2-2502778.[000190] [2] www.telekom.com / en / media / media-information / archive / telekom-and-partners-demonstrate-sms-via-satellite-1083916.[000191] [3] 3GPP TS 23.401 v19.2.0 (“TS 23.401”)[000192] [4] 3GPP TS 24.301 v19.2.0 (TS "24.301”)[000193] [5] 3GPP TS 36.413 v18.3.0 (TS "36.413”) [000194] [6] 3GPP TS 36.331 18.5.0 (TS "36.331”) [000195] [7] GSMA IR.92 V20.0 ("GSMA”)[000196] [8] 3GPP TS 23.221 v18.0.0 (TS "23.221”) [000197] [9] 3GPP TS 24.008 v18.8.0 (TS "24.008’)
Claims
CLAIMS1. A method performed by a user equipment, UE (102), the method comprising:transmitting (s802) a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) comprising information indicating that voice over packet switched, VoPS, is a voice domain preference; andreceiving (s804) a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported, characterized in that:i) the first NAS message includes a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, ii) transmitting the first NAS message comprises the UE (102) transmitting a Radio Resource Control, RRC, message (m203, m503) comprising the first NAS message, wherein the RRC message (m203, m503) further comprises a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, and / orill) the method further comprises: after transmitting the first NAS message and prior to receiving the second NAS message, receiving a request message (m704) requesting capability information; and transmitting a response message (m706) responsive to the request message (m704), the response message (m706) comprising information indicating that the UE (102) supports IMS voice over NB-loT.
2. The method of claim 1, wherein:transmitting the first NAS message comprises the UE (102) transmitting the RRC message (m503) comprising the first NAS message and the capability indicator indicating that the UE (102) supports IMS voice over NB-loT; the RRC message (m503) is transmitted to a base station (104) using an NB-loT radio access technology, RAT; the method further comprises receiving system information (m603) broadcast by the base station (104); and the UE (102) is configured to include the capability indicator in the RRC message (m503) after determining that the system information (m603) indicates that the base station (104) supports IMS voice over NB-loT.
3. The method of claim 1, wherein transmitting the first NAS message comprises the UE (102) transmitting an RRC message (m203, m503) to a base station (104) using an NB-loT radio access technology, RAT.
4. The method of any of claims 1 to 3, wherein the second NAS message was transmitted by a management entity, ME (108), of a core network (106), and the second NAS message indicates whether or not the ME (108) supports IMS voice over NB-loT.
5. The method of any of claims 1 to 4, wherein the first NAS message includes the capability indicator indicating that the UE (102) supports IMS voice over NB-loT, and the capability indicator is a RAT aware UE configuration.
6. A method performed by a network node (ZZ200), the method comprising:receiving (s902) a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE (102);generating (s904) a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported; andtransmitting (s906) the second NAS message to the UE (102), characterized in that:i) the first NAS message includes a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, ii) the method further comprises, prior to receiving the first NAS message, receiving from a base station (104) a message (m501) indicating that the base station (104) supports IMS voice over NB-loT and the base station (104) forwarded the first NAS message to the network node (ZZ200),ill) the method further comprises, in response to receiving the first NAS message, determining, based on subscription information associated with the UE (102), whether or not the UE (102) is authorized to use IMS voice over NB-loT, and / oriv) the method further comprises, in response to receiving the first NAS message, transmitting to the base station (104) a request message (m702) and receiving from the base station (104) a response message (m708) responsive to the request message (m702) wherein the response message (m708) indicates whether or not the UE (102) supports IMS voice over NB-loT.
7. The method of claim 6, wherein the method further comprises, in response to receiving the first NAS message: obtaining from a subscriber data manager (109) subscription information associated with the UE (102); and determining, based on the subscription information associated with the UE (102), whether or not the UE (102) is authorized to use IMS voice over NB-loT.
8. The method of claim 6 or 7, wherein:the method further comprises, prior to receiving the first NAS message, receiving from a base station (104) a message (m501) indicating that the base station (104) supports IMS voice over NB-loT, wherein the base station (104) forwarded the first NAS message to the network node (ZZ200); andthe method further comprises, in response to receiving the message (m501) from the base station (104), sending a response message (m502) to the base station (104), wherein the response message (m502) indicates that the network node (ZZ200) supports IMS voice over NB-loT.
9. A method performed by a base station (104), the method comprising:receiving (s1002) a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE (102); andforwarding (s1004) the first NAS message to a management entity, ME (108), characterized in that:i) the first NAS message includes a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, ii) the method further comprises, prior to receiving the first NAS message, broadcasting system information (m603), wherein the broadcast system information (m603) comprises a capability indicator indicating that the base station (104) supports IMS voice over NB-loT,ill) the method further comprises, prior to receiving the first NAS message, transmitting to the ME (108) a control message (m501) for establishing a logical connection with the ME (108), wherein the control message (m501) comprises a capability indicator indicating that the base station (104) supports IMS voice over NB-loT, iv) receiving the first NAS message comprises receiving a Radio Resource Control, RRC, message (m503) comprising the first NAS message and further comprising a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, and / orv) the method further comprises, after forwarding the first NAS message to the ME (108): receiving from the ME (108) a first request (m702) for information regarding the UE (102); after receiving the first request (m702) from the ME (108), sending to the UE (102) a second request (m704) for information; receiving from the UE (102) a response (m706) responsive to the second request (m704), wherein the response (m706) indicates whether or not the UE (102) supports IMS voice over NB-loT; and after receiving the response (m706) from the UE (102), sending to the ME (108) a response (m708) indicating whether or not the UE (102) supports IMS voice over NB-loT.
10. The method of claim 9, wherein:the method further comprises, prior to receiving the first NAS message, transmitting to the ME (108) the control message (m501) for establishing the logical connection with the ME (108); andthe method further comprises receiving from the ME (108) a response message (m502) responsive to the control message (m501), wherein the response message (m502) indicates that the ME (108) supports IMS voice over NB-loT.
11. The method of claim 9 or 10, wherein:receiving the first NAS message comprises receiving an RRC message (m503) comprising the first NAS message and further comprising a capability indicator indicating that the UE (102) supports IMS voice over NB-loT; and the method further comprises:determining that the RRC message (m503) indicates that the UE (102) supports IMS voice over NB-loT;as a result of determining that the RRC message (m503) indicates that the UE (102) supports IMS voice over NB-loT, selecting an ME (108) that supports IMS voice over NB-loT; andtransmitting the first NAS message to the selected ME (108).
12. A method (1700) performed by a first network node (PGW 192), the method comprising:receiving (s1702) from a second network node (PCRF 193) a message (m1409, m1505, m1605) comprising at least a first pre-allocated traffic flow template, TFT, data element.
13. The method of claim 12, further comprising:creating a first TFT using the first pre-allocated TFT data element; andproviding to a third network node (SGW 191) a message (m1411) comprising the first TFT.
14. The method of claim 12 or 13, further comprising, prior to receiving from the second network node (PCRF 193) the message comprising the first pre-allocated TFT data element:providing to the second network node (PCRF 193) a request message (m1407) for triggering the second network node (PCRF 193) to provide to the first network node (PGW 192) one or more pre-allocated TFT data elements, wherein the request message (m1407) comprises an indicator indicating that the first network node (PGW 192) is requesting the second network node (PCRF 193) to provide one or more pre-allocated TFT data elements.
15. The method of claim 14, further comprising, prior to providing the request message (m1407) to the second network node (PCRF 193):receiving from the third network node (SGW 191) a create session message (m1405),wherein the create session message (m1405) triggers the first network node (PGW 192) to transmit the request message (m1407) to the second network node (PCRF 193).
16. The method of any of claims 12 to 15, further comprising:receiving from the second network node (PCRF 193) a message (m1413) comprising a flow description; determining if the flow description matches the first pre-allocated TFT data element; andif the flow description matches the first pre-allocated TFT data element, refraining from triggering a bearer modification procedure.
17. The method of claim 12 or 13, wherein the message (m1505, m1605) comprising the first pre-allocated TFT data element is a Re-Authorization Request, RAR, message for triggering a dedicated bearer setup procedure.
18. A method (1800) performed by a first network node (P-CSCF 194, PCRF 193), the method comprising: providing (s1802) to a second network node (PCRF 193, PGW 192) a message (m1503, m1603, m1505, m1605) comprising at least a first pre-allocated traffic flow template, TFT, data element.
19. The method of claim 18, wherein the first network node implements a Proxy Call Session Control Function, P-CSCF (194), and the second network node implements a policy function (PCRF 193).
20. The method of claim 19, further comprising, prior to providing the first pre-allocated TFT data element to the policy function (PCRF 193):receiving a session initiation protocol, SIP, message (ml 501 , m1601) transmitted by a user equipment, UE (102), wherein the SIP message (m1501, m1601) triggers the P-CSCF (194) to provide the first pre-allocated TFT data element to the policy function (PCRF 193).
21. The method of claim 20, wherein the SIP message is a SIP register message (m1501) for initiating a registration procedure and a successful completion of the registration procedure triggers the P-CSCF (194) to provide the first pre-allocated TFT data element to the policy function (PCRF 193).
22. The method of claim 20, wherein the SIP message is a SIP invite message (m1601) for initiating a SIP call and the SIP invite message (m1601) triggers the P-CSCF (194) to provide the first pre-allocated TFT data element to the policy function (PCRF 193).
23. The method of claim 18, wherein the first network node implements a policy function (PCRF 193) and the second network node implements a packet gateway, PGW (192).
24. The method of claim 23, further comprising, prior to providing the first pre-allocated TFT data element to the second network node (PGW 192):receiving a request (m1407) from the second network node (PGW 192),wherein the request (m1407) from the second network node (PGW 192) comprises an indicator that triggers the policy function (PCRF 193) to provide the first pre-allocated TFT data element to the second network node (PGW 192).
25. The method of claim 23, further comprising, prior to providing the first pre-allocated TFT data element to the second network node (PGW 192):receiving from a third network node (P-CSCF 194) a message (m1503, m1603) comprising the first pre-allocated TFT data element,wherein the message from the third network node (P-CSCF 194) triggers the policy function (PCRF 193) to provide the first pre-allocated TFT data element to the second network node (PGW 192).
26. A method performed by a first network node (PGW 192), the method comprising:receiving a request (m1405) from a second network node (SGW 191);after receiving the request (m1405), creating a TFT based on a locally configured pre-allocated TFT data element; andsending to the second network node (SGW 191) a response message (m1411) responsive to the request (m1405), wherein the response message (m1411) comprises the created TFT.
27. The method of claim 26, further comprising:receiving from a third network node (PCRF 193) a message (m1413) comprising a flow description; determining if the flow description matches the locally configured pre-allocated TFT data element; andif the flow description matches the locally configured pre-allocated TFT data element, refraining from triggering a bearer modification procedure.
28. A computer program comprising instructions which when executed by processing circuitry (ZZ102, ZZ202, ZZ302) of an apparatus, cause the apparatus to perform the method of any of claims 1 to 27.
29. A carrier containing the computer program of claim 28, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium (ZZ142, ZZ242, ZZ342).
30. A user equipment, UE (102), the UE (102) being configured to perform a method comprising:transmitting a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) comprising information indicating that voice over packet switched, VoPS, is a voice domain preference; andreceiving a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported, characterized in that:I) the first NAS message includes a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, ii) transmitting the first NAS message comprises the UE (102) transmitting a Radio Resource Control, RRC, message (m203, m503) comprising the first NAS message, wherein the RRC message (m203, m503) further comprises a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, and / oriii) the method further comprises: after transmitting the first NAS message and prior to receiving the second NAS message, receiving a request message (m704) requesting capability information; and transmitting a response message (m706) responsive to the request message (m704), the response message (m706) comprising information indicating that the UE (102) supports IMS voice over NB-loT.
31. The UE (102) of claim 30, wherein the UE (102) is further configured to perform the method of any of claims 2 to 5.
32. A network node (ZZ200), the network node (ZZ200) being configured to perform a method comprising: receiving a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE (102);generating a second NAS message responsive to the first NAS message, wherein the second NAS message indicates whether or not Internet Protocol Multimedia Subsystem, IMS, voice over narrow-band internet-of-things, NB-loT, is supported; andtransmitting the second NAS message to the UE (102), characterized in that:i) the first NAS message includes a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, ii) the method further comprises, prior to receiving the first NAS message, receiving from a base station (104) a message (m501) indicating that the base station (104) supports IMS voice over NB-loT and the base station (104) forwarded the first NAS message to the network node (ZZ200),iii) the method further comprises, in response to receiving the first NAS message, determining, based on subscription information associated with the UE (102), whether or not the UE (102) is authorized to use IMS voice over NB-loT, and / oriv) the method further comprises, in response to receiving the first NAS message, transmitting to the base station (104) a request message (m702) and receiving from the base station (104) a response message (m708) responsive to the request message (m702) wherein the response message (m708) indicates whether or not the UE (102) supports IMS voice over NB-loT.
33. The network node (ZZ200) of claim 32, wherein the network node (ZZ200) is further configured to perform the method of claim 7 or 8.
34. A base station (104), the base station (104) being configured to perform a method comprising:receiving a first Non-Access Stratum, NAS, message (m205, m305, m405, m505) generated by a user equipment, UE (102), the first NAS message comprising information indicating that voice over packet switched, VoPS, is a voice domain preference of the UE (102); andforwarding the first NAS message to a management entity, ME (108), characterized in that:i) the first NAS message includes a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, ii) the method further comprises, prior to receiving the first NAS message, broadcasting system information (m603), wherein the broadcast system information (m603) comprises a capability indicator indicating that the base station (104) supports IMS voice over NB-loT,ill) the method further comprises, prior to receiving the first NAS message, transmitting to the ME (108) a control message (m501) for establishing a logical connection with the ME (108), wherein the control message (m501) comprises a capability indicator indicating that the base station (104) supports IMS voice over NB-loT, iv) receiving the first NAS message comprises receiving a Radio Resource Control, RRC, message (m503) comprising the first NAS message and further comprising a capability indicator indicating that the UE (102) supports IMS voice over NB-loT, and / orv) the method further comprises, after forwarding the first NAS message to the ME (108): receiving from the ME (108) a first request (m702) for information regarding the UE (102); after receiving the first request (m702) from the ME (108), sending to the UE (102) a second request (m704) for information; receiving from the UE (102) a response (m706) responsive to the second request (m704), wherein the response (m706) indicates whether or not the UE (102) supports IMS voice over NB-loT; and after receiving the response (m706) from the UE (102), sending to the ME (108) a response (m708) indicating whether or not the UE (102) supports IMS voice over NB-loT.
35. The base station (104) of claim 34, wherein the base station (104) is further configured to perform the method of claim 10 or 11.
36. A network node (PGW 192), the network node (PGW 192) being configured to perform a method comprising: receiving from a second network node (PCRF 193) a message (m1409, m1505, m1605) comprising at least a first pre-allocated traffic flow template, TFT, data element.
37. The network node (PGW 192) of claim 36, wherein the network node (PGW 192) is further configured to perform the method of any of claims 13 to 17.
38. A network node (P-CSCF 194, PCRF 193), the network node (P-CSCF 194, PCRF 193) being configured to perform a method comprising:providing to a second network node (PCRF 193, PGW 192) a message (m1503, m1603, m1505, m1605) comprising at least a first pre-allocated traffic flow template, TFT, data element.
39. The network node (P-CSCF 194, PCRF 193) of claim 38, wherein the network node (P-CSCF 194, PCRF 193) is further configured to perform the method of any of claims 19 to 25.
40. A network node (PGW 192), the network node (PGW 192) being configured to perform a method comprising: receiving a request (m1405) from a second network node (SGW 191);after receiving the request (m1405), creating a TFT based on a locally configured pre-allocated TFT data element; andsending to the second network node (SGW 191) a response message (m1411) responsive to the request (m1405), wherein the response message (m1411) comprises the created TFT.
41. The network node (PGW 192) of claim 40, wherein the network node (PGW 192) is further configured to perform the method of claim 27.
