Methods, apparatuses and computer programs for accessing an internet protocol multimedia system
By allowing network nodes to manage IP headers on behalf of UE in satellite access, the method addresses inefficiencies in IMS signaling overhead, improving energy efficiency and network performance.
Patent Information
- Application Number
- PCT/EP2026/062865
- 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
In satellite-based network access scenarios, the use of IP protocol headers for IMS signaling results in significant overhead, which is inefficient due to limited link budget and high one-way delay, affecting battery life and network congestion.
A method where user equipment (UE) indicates its intention not to use IP protocol headers for IMS signaling, allowing network nodes to add and remove these headers on its behalf, thereby enabling IMS connectivity via narrowband access without an IP stack.
This approach reduces overhead, conserves energy, and optimizes network resources, particularly in satellite-based access, enhancing efficiency and battery life.
Smart Images

Figure EP2026062865_12112026_PF_FP_ABST
Abstract
Description
METHOD, APPARATUS AND COMPUTER PROGRAMTECHNICAL FIELD
[0001] Various embodiments of this disclosure relate to methods, apparatuses, systems and computer programs, and in particular - but not exclusively - to methods, apparatuses, systems and computer programs for accessing an Internet Protocol Multimedia System (IMS) while an Internet Protocol stack is suspended at a user equipment for IMS.BACKGROUND
[0002] A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network. A communication device may be provided with a service by an application server.
[0003] Such communication networks operate in according with standards such as those provided by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards are the so-called 5G (5th Generation) standards and 6G (6th Generation) standards provided by 3GPP.SUMMARY
[0004] Some embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various examples of this disclosure, nor are they intended to be used to limit the scope of thereof. Other features, aspects, and elements will be apparent to a person skilled in the art in view of this disclosure. For example, it should be appreciated that further aspects may be provided by the combination of any two or more of the various aspects described below or otherwise herein.
[0005] According to a first aspect, there is provided an apparatus comprising: at least one processor; and at least one memory comprising instructions that, when executed by the at least one processor, causes the apparatus at least to perform: determining that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellite-based network access node; transmitting, to a first network node via the satellite-based network access node, a request toconnect to the IMS, wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and receiving, from the first network node via the satellite-based network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.
[0006] According to a second aspect, there is provided an apparatus comprising means for performing: determining that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellitebased network access node; transmitting, to a first network node via the satellitebased network access node, a request to connect to the IMS, wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and receiving, from the first network node via the satellitebased network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.
[0007] According to a third aspect, there is provided a method for an apparatus, the method comprising: determining that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellite-based network access node; transmitting, to a first network node via the satellite-based network access node, a request to connect to the IMS, wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and
[0008] receiving, from the first network node via the satellite-based network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.
[0009] According to a fourth aspect, there is provided an apparatus comprising: determining circuitry for determining that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellitebased network access node; transmitting circuitry for transmitting, to a first network node via the satellite-based network access node, a request to connect to the IMS, wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and receiving circuitry forreceiving, from the first network node via the satellite-based network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.
[0010] The following may apply in respect of any (e.g., one or more, including all) of the above first to fourth aspects.
[0011] The acknowledgement may further comprise an identifier of a port to be used by the apparatus when exchanging IMS-signalling related data traffic.
[0012] The apparatus may be further caused to perform: transmitting, to a second network node, a request to register the apparatus with an IMS, wherein the request to register comprises the first IP address in a contact header, wherein the transmitting comprises abstaining from adding an IP header to the request; and receiving, from the second network node, signalling comprising an indication that the apparatus has been registered with the IMS, wherein receiving comprises suspending using an IP protocol level header when exchanging IMS-related data traffic signalling.
[0013] The request to register may further comprise the identifier of the first port.
[0014] The signalling comprising the indication that the apparatus has been registered with the IMS may comprise a session initiation protocol message.
[0015] The apparatus may be further caused to perform: receiving, from the first network node, signalling comprising an IMS mobile terminated signalling message payload, wherein said receiving comprises suspending using an IP protocol level header when exchanging IMS-related data traffic; and transmitting a bearer update message to the first network node, wherein the bearer update message comprises information indicating at least one of a second IP address or second port.
[0016] According to a fifth aspect, there is provided an apparatus comprising: at least one processor; and at least one memory comprising instructions that, when executed by the at least one processor, causes the apparatus at least to perform: receiving, from a user equipment via a satellite-based access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and transmitting an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.
[0017] According to a sixth aspect, there is provided an apparatus comprising means for performing: receiving, from a user equipment via a satellite-based access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and transmitting an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.
[0018] According to a seventh aspect, there is provided a method for an apparatus, the method comprising: receiving, from a user equipment via a satellite-based access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and transmitting an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.
[0019] According to an eighth aspect, there is provided an apparatus comprising: receiving circuitry for receiving, from a user equipment via a satellite-based access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling; and transmitting circuitry for transmitting an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.
[0020] The following may apply in respect of any (e.g., one or more, including all) of the above fifth to eighth aspects.
[0021] The acknowledgement may further comprise an identifier of a first port to be used by the user equipment when exchanging IMS-signall ing related data traffic.
[0022] The apparatus may be further caused to perform: receiving, from the user equipment, a request to register the apparatus with an IMS, wherein the request to register comprises the first IP address in a contact header and further comprises the identifier of the first port, wherein the request to register does not comprise an IP header; causing the user equipment to be registered with the IMS based on the IP address; storing first the IP address and the identifier of the first port; and transmitting,to the user equipment, signalling comprising an indication that the apparatus has been registered with the IMS, wherein transmitting comprises suspending using an IP protocol level header when exchanging IMS-related data traffic signalling.
[0023] The signalling comprising the indication that the apparatus has been registered with the IMS may comprise a session initiation protocol message.
[0024] The apparatus may be further caused to perform: transmitting, to the user equipment, signalling comprising an IMS mobile terminated signalling message payload, wherein transmitting comprises suspending an IP protocol level header; and receiving a bearer update message from the user equipment, wherein the bearer update message comprises at least one of a second IP address or a second port for the user equipment to receive an IMS service based on the IMS mobile terminated signalling message payload.
[0025] The apparatus may be further caused to perform: receiving, from the user equipment, first IMS-related data traffic signalling for the IMS; modifying the first IMS-related data traffic signalling to form first modified IMS-related data traffic signalling that comprises an IP header; and transmitting the first modified IMS-related data traffic signalling to the IMS.
[0026] The apparatus may be further caused to perform: receiving, from the IMS, second IMS-related data traffic signalling for the user equipment, wherein the second IMS-related data traffic signalling comprises an IP header; modifying the second IMS signalling by removing the IP header to form second modified IMS-related data traffic signalling; and transmitting the second IMS-related data traffic modified signalling to the user equipment.
[0027] The apparatus may comprise a control plane part that is configured to perform at least one control plane function, and a user plane part that is configured to perform at least one user plane function, wherein the apparatus may be further caused to perform: providing, from the control plane part to the user plane part, at least one of the first IP address or a port allocated to the user equipment for IMS-related data traffic.
[0028] The first IMS-related data traffic may correspond to at least one of: signalling for the IMS or media plane for IMS.
[0029] The second IMS-related data traffic may correspond to at least one of signalling for the IMS or media plane for IMS.
[0030] According to an aspect, there is provided a non-transitory computer readable medium comprising instructions that, when executed by an apparatus, cause the apparatus at least to perform at least the method according to any of the preceding aspects.
[0031] In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.BRIEF DESCRIPTION OF THE DRAWINGS
[0032] Some embodiments will now be described, by way of example only, with reference to the accompanying Figures (FIGs). in which:
[0033] FIG. 1 shows a schematic representation of an originating user equipment communicating with a terminating user equipment via a communication network comprising two internet protocol multimedia subsystem networks in accordance with some embodiments;
[0034] FIG. 2 shows a schematic representation of an apparatus implementing one or more network functions of an internet protocol multimedia subsystem network;
[0035] FIG. 3 shows a schematic representation of a user equipment;
[0036] FIG. 4 shows an example network access scenario;
[0037] FIGs. 5 to 7 illustrate example signalling; and
[0038] FIGs. 8 to 11 illustrate example methods that may be performed by apparatus described herein.DETAILED DESCRIPTION
[0039] In the following, various embodiments are explained with reference to mobile communication devices capable of communication via a wireless cellular system and mobile communication systems serving such mobile communication devices. Before explaining in detail, certain concepts of a wireless communication system, access systems thereof, and mobile communication devices are briefly explained with reference to FIGS. 1 , 2 and 3 to assist in understanding the technology underlying the described embodiments, and examples thereof.
[0040] FIG. 1 shows a schematic representation of a first user equipment (denoted UE-A) communicating with a second user equipment comprising a communication network that includes two IMS networks. The communication network may comprisea public land mobile network (PLMN). A communication network may comprise a (radio) access network ((R)AN) (not illustrated), a core network (5GC and / or a long term evolution (LTE) core network) (not illustrated) in addition to the two internet protocol multimedia subsystem (IMS) networks shown. The IMS network serving the first user equipment (e.g., IIE-A) may be referred to as an originating IMS network and the IMS network servicing the second user equipment (e.g., IIE-B) may be referred to as a terminating IMS network.
[0041] In this disclosure, the expressions “internet protocol multimedia subsystem” and “internet protocol multimedia subsystem network” may be used interchangeably.
[0042] Exemplary wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP). A latest 3GPP based development is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology (RAT). The various development stages of the 3GPP specifications are referred to as releases. More recent developments of the LTE are often referred to as LTE Advanced (LTE-A). The LTE (LTE-A) employs a radio mobile architecture known as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network known as the Evolved Packet Core (EPC). Base stations of such systems are known as evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features such as user plane Packet Data Convergence / Radio Link Control / Medium Access Control / Physical layer protocol (PDCP / RLC / MAC / PHY) and control plane Radio Resource Control (RRC) protocol terminations towards the communication devices. Other RAT examples comprise those provided by base stations of systems that are based on technologies such as WLAN and / or Worldwide Interoperability for Microwave Access (WiMax). A base station can provide coverage for an entire cell or similar radio service area. Core network elements include Mobility Management Entity (MME), Serving Gateway (S-GW) and Packet Gateway (P-GW).
[0043] An example of a suitable communications system is the 5G or NR, or the 6G concept. Network architecture in NR may be similar to that of LTE-A. Base stations of NR systems may be known as next generation or 6G Node Bs (gNBs). Changes to the network architecture may depend on the need to support various radio technologies and finer QoS support, and some on-demand requirements for QoS levels to support Quality of Experience (QoE) of user point of view. Also network aware services and applications, and service and application aware networks may bringchanges to the architecture. Those are related to Information Centric Network (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR may use multiple input-multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in cooperation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
[0044] Networks, like 6G, may utilize network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running instructions using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications, this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes, or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.
[0045] An example 5G core network (CN) comprises functional entities which may also be present in a 6G network. The CN is connected to a UE via the radio access network (RAN). A UPF (User Plane Function) whose role is called PSA (PDU Session Anchor) may be responsible for forwarding frames back and forth between the DN (data network) and the tunnels established over the 5G towards the UEs exchanging traffic with the data network (DN). The UPF is controlled by an SMF (Session Management Function) that receives policies from a PCF (Policy Control Function). The CN may also include an AMF (Access & Mobility Function).
[0046] Generally, all concepts disclosed herein may be applicable to different communication networks, comprising - but not limited to - LTE, LTE-A, 5G, 5G advanced, 6G, and future or already implemented networks.
[0047] An IMS network (e.g., the originating IMS network or the terminating IMS network) may comprise a proxy call session control function (P-CSCF), a serving call session control function (S-CSCF), an interrogating call session control function (I-CSCF), an IMS application level gateway (IMS-AGW), an IMS home subscriber server (IMS HSS), an IMS application server (IMS AS), a media function (MF) or mediarepository function (MRF), a transition gateway (TrGW), an interconnection border control function (IBCF), a terminating IMS core, a data channel signalling function (DCSF), an XR application server (AS), a digital asset container (DAC) or a web server (not represented).
[0048] Reference in the below is also made to a quality of class identifier (QCI). QCI is a mechanism used to more easily provide a defined quality of service within a network, based on a traffic type. A particular QCI is labelled by a number (e.g., 1 , 2, 3, 4, 65, etc.), with each number corresponding to particular combination of values relating to a resource type (e.g., guaranteed bit rate, non-guaranteed bit rate, a priority, a packet delay budge, and a packet error loss rate. Each defined combination of values (e.g., each QCI value) may be associated with a particular type of traffic (e.g., QCI=1 is associated with conversational voice, while QCI=5 is associated with IMS signalling).
[0049] A user equipment (UE) can connect and register to the IMS network in various ways through an access network (such as through a 5G and / or 6G access network). Registration with the IMS network currently uses Session Initiation Protocol (SIP) signalling mechanisms, which are defined by the Internet Engineering Task Force (IETF). SIP is a signalling protocol used for initiating, maintaining, and terminating communication sessions that include voice, video and messaging applications. SIP is located at an application layer.
[0050] A home subscriber server (HSS) and / or unified data management (UDM) located in the core network contains subscription-related information for users, performs authentication and / or authorisation of the user for the IMS network. An IMS subscriber comprises a user and / or user equipment that has an IMS subscription stored in the HSS. Each IMS subscription is linked to a single IP multimedia private user identity (IMP I), which is discussed further below.
[0051] The IMS network further comprises a plurality of IMS network-based identifies. For example, IMS user identities include at least IP multimedia private user identity (IMPI), IP multimedia public user identity (IMPU), globally routable user agent URI (GRUll), wildcarded public user identity. Both IMPI and IMPU are uniform resource identifiers (URIs), that can be digits or alphanumeric identifiers.
[0052] The IMPI is a unique permanently allocated global identity assigned by the home network operator. It has the form of a Network Access Identifier (NAI) (e.g.,user.name@domain), and is used, for example, for Registration, Authorization, Administration, and Accounting purposes.
[0053] The IMPU is used by any user for requesting communications to other users (e.g. this might be included on a business card). There can be multiple IMPU per IMPI.
[0054] In the IP Multimedia Subsystem (IMS), the Session Description Protocol (SDP) is used to describe and negotiate the parameters of multimedia sessions, such as voice and video calls. The SDP offer includes information about the user's capabilities and preferences for the session. For example, it may specify supported audio and video codecs, IP addresses, and port numbers for media transmission. SDP allows the inclusion of various media attributes, such as bandwidth constraints, media type (audio, video, etc.), codec selection, and encryption preferences.
[0055] FIG. 2 illustrates an example of a control apparatus 200 for controlling a function of the IMS as illustrated in FIG. 1. The control apparatus may comprise at least one random access memory (RAM) 211a, at least on read only memory (ROM) 211b, at least one processor 212, 213 and an input / output interface 214. The at least one processor 212, 213 may be coupled to the RAM 211 a and the ROM 211b. The at least one processor 212, 213 may be configured to execute an appropriate software code 215. The software code 215 may, for example, allow, enable, and / or facilitate to perform one or more steps of any of the methods described herein. The software code 215 may be stored in the ROM 211b. The control apparatus 200 may be interconnected with another control apparatus 200 controlling another function of the 5GRAN or the 5GC. In some embodiments, each function of the 5GRAN or the 5GC comprises a control apparatus 200. In alternative embodiments, two or more functions of the 5GRAN or the 5GC may share a control apparatus.
[0056] FIG. 3 illustrates an example of a terminal 300, such as the terminal illustrated on FIG. 1. The terminal 300, which is also referred to herein as a user equipment (UE) and / or communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a user equipment, a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, an Internet of things (loT) type communication device or any combinations of these or the like. The terminal 300 may provide, for example, communication of data forcarrying communications. The communications may be one or more of voice, electronic mail (email), text message, multimedia, data, machine data and so on.
[0057] The terminal 300 may receive signals over an air or radio interface 307 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In FIG. 3, a transceiver apparatus is designated schematically by block 306. The transceiver apparatus 306 may be provided, for example, by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally and / or externally to the mobile device.
[0058] The terminal 300 may be provided with at least one processor 301 , at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute an appropriate software code 308. The software code 308 may, for example, allow, enable, and / or facilitate to perform one or more steps of any of the methods described herein. The software code 308 may be stored in the ROM 302a.
[0059] The processor, storage and other relevant control apparatus can be provided on an appropriate circuit board and / or in chipsets. This feature is denoted by reference 304. The device may optionally have an interface (e.g., user interface), such as keypad 305, touch sensitive screen or pad, combinations thereof or the like. Optionally, one or more of a display, a speaker and a microphone may be provided depending on the type of the device.
[0060] In long term evolution (LTE) networks, the IMS is the framework that enables multimedia services like Voice over LTE (VoLTE) to be performed. IMS operates over an all-IP network, meaning it relies on the Internet Protocol for communication. This means that a UE needs an IP network communication to establish and participate in IMS services.
[0061] However, in the case of voice over GEO satellite (which is a proposed as part of Release 20), a UE is to obtain an IMS service over a narrow band (NB) internet of things (loT) satellite access connected to an LTE core network. In particular, the UE is to have IP packet data network (PDN) connection and use an IP stack (such as, forexample, the user datagram packet / IP (UDP / IP) stack and / or the transport connection protocol / IP (TCP / IP) stack for IMS registration and IMS call setup).
[0062] Stated differently, an IP PDN that uses UDP / IP signalling and media payload will transmit the UDP / IP signalling and media payload from a UE to a network access node satellite, before being passed from the network access node satellite to a ground station, crossing an LTE-radio access network (LTE-RAN), and LTE-Core network, and an IMS core network. This scenario is illustrated with respect to FIG. 4.
[0063] FIG. 4 illustrates a first UE 401 that is configured to access a network via a satellite network access node 402. The satellite network access node routes signalling from the first UE to a first ground-based network access node 403, which provides access to a first core network 404. The first core network 404 connects to an IMS core network 405, which, in turn, connects to a second core network 406 based on an intended recipient of the signalling from the first UE 401. The second core network 406 may cause communications to a second UE 408 to be routed to that second UE 408 through a second ground-based network access node 407.
[0064] IP headers, such as UDP / IP headers and / or TCP / IP headers, in each and every packet (whether signalling or media) that is transmitted through the setup of FIG. 4 adds additional size overhead. The size overhead may be large (e.g., an additional 40 bytes may be contributed to a payload of a packet that uses a UDP / IP header), which may be disadvantageous for certain use cases in NB-loT satellite access due to limited link budget.
[0065] One way of mitigating the IP stack overhead is to use a robust header compression (ROHC) mechanism for TCP, UDP, IP and even real-time transport protocol (RTP) header compression, where RTP is a network protocol located at the application layer for delivering audio and video over IP networks. Using ROHC mechanisms may help reduce a 20-60 byte header to 1-3 bytes.
[0066] However, the following recognizes that a ROHC mechanism may not always be suitable for use in a satellite access scenario (such as illustrated in FIG. 4).
[0067] For example, in such a satellite access scenario, a one-way delay between the UE and the satellite network access node is 290 msec (as specified in 3GPP TS 23.401), which means that every time the compressor wants to compress a payload with some efficiency (O mode) or robustness (R mode), it utilizes multiple cycles of feedback. However, the high one-way delay means the compressor has to wait for a longer feedback cycle from the decompressor to gain confidence that the compressiontechniques are working properly. The additional feedback payload will also add to the overall link budget available for efficient message exchange.
[0068] The following aims to address one or more of the above-mentioned issues and / or other technical issues recognized by a person ordinarily skilled in the relevant art(s).
[0069] In more detail, the following proposes at least one method in which a UE that intends to receive an IMS service does not use IMS headers for transmitting and / or IMS-based communications in respect of that IMS service.
[0070] For example, when establishing a connection to an IMS network, the UE may transmit, to a first network node, a request to connect to an, wherein the request indicates that the UE does not intend to use internet protocol (IP) protocol level headers for IMS signalling. The first network node (or some other network node in the signal path between the UE and the IMS system) may, based on this indication that the UE does not intend to use IP headers for IMS signalling, add IP headers on behalf of the UE when signalling upstream towards the IMS, and remove IP headers from signalling received from the IMS for the UE. In such a way, the UE may avoid using IP-based headers (and may therefore avoid using an IP protocol stack) for signalling transmitted over a radio access network.
[0071] Although the techniques described herein may be particularly useful in the context of satellite-based network access nodes, it is understood that similar benefits may be derived in other example network configurations. For example, when a ground-based radio access network is experiencing congestion, the described techniques may reduce the burden on the network access node. Further, as the computational burden of IP header-based processing at the UE is removed under the systems described herein, the methods described herein may provide energy efficient mechanisms for accessing IMS services at a UE. This may be useful given the limited battery life of a UE.
[0072] The following will illustrate one or more features of examples that utilize the techniques described with reference to FIGs. 5 to 7, before example features of these examples are highlighted with respect to FIGs. 8 to 11.
[0073] FIG. 5 illustrates example signalling that may be performed between apparatus described herein when a non-IP PDN is being established (e.g., for a quality of class identifier (QCI) =5).
[0074] In particular, FIG. 5 illustrates example signalling that may be performed between a UE 501 , a mobility management entity (MME) 502, an S-GW 503, a P-GW 504, and at least one of a policy control function (PCF) or a Policy and Charging Rules function (PCRF) 505. For clarity and brevity, where only a single on the PCF and PCRF are referred to herein, this may include a reference to the other entity. Further, the notation PCF / PCRF or PCRF / PCF may indicate that any of these functions may perform the described method.
[0075] During 5001, the UE 501 signals the MME 502. This signalling may comprise a PDN connectivity request (e.g., a request to connect to a PDN) in respect of an access point name (APN) being set to an IMS APN. The signalling of 5001 may further comprise a request for a P-CSCF address. This signaling may indicate that the PDN-type is not IP-based. This signalling may comprise a Protocol Configuration Option (PCO) parameter. For example, the PCO parameter may comprise an indication that the UE intends to access IMS services via a non-IP PDN. The purpose of PCOs is to transfer an external network protocol options associated with a packet data protocol (PDP) context activation.
[0076] The UE may determine to use a non-IP PDN type for IMS APN based on preconfigured condition being fulfilled.
[0077] For example, the condition may be that the UE is connected to a core network via a specific type of radio access network (e.g. NB-loT radio access type (RAT) type via a satellite cell). The RAT type information may be determined from information comprised at a lower layer during a radio resource control (RRC) connection establishment procedure.
[0078] As another example, the condition may be that the UE is experiencing a bit rate and / or quality of service that falls below a preconfigured threshold value.
[0079] As another example, the condition may be that the UE is operating off a battery supply that has less than a preconfigured percentage of power left for use.
[0080] The signalling of 5001 may be performed as part of an evolved packet system (EPS) Attach procedure, or as a standalone procedure. Example scenarios in which a PDN connection procedure is performed are discussed in 3GPP TS 23.401.
[0081] Although not shown, on receipt of the signalling of 5001, the MME 502 may check the UE’s subscription information (which may have been retrieved from, for example, a home subscriber system, HSS) to determine whether the UE is allowed for non-IP PDN for IMS APN. When the UE’s subscription indicates that this is allowed,the MME sends a create session request to the S-GW 503 during 5002. This create session request may comprise the PCO and APN information comprised in the signalling of 5001. For example, this signalling of 5002 may indicate that the UE will not use an IP header for signalling, and that the APN being requested is for an IMS service.
[0082] During 5003, the S-GW 503 forwards the request of 5002 to the P-GW 504.
[0083] During 5004, the control plane part of the P-GW(e.g., the P-GW-c) may request that the user plane part of the P-GW (e.g., P-GW-u) to provide the control plane part with an IP address that may be used for at least IMS signalling (e.g., labelled herein as a UE-IP-address-for-IMS-signaling). The control plane part may also request port information for the UE for receiving an IMS service (labelled herein as a UE port-for-IMS-signaling). The control plane part of the P-GW 504 may use this information from the user plane part to perform an IP Connectivity Access Network (IP-CAN) Session Establishment procedure to the PCRF / PCF 505 during 5005. As part of this procedure of 5005, the control plane part of the P-GW may indicate to the PCRF / PCF that the PDN being requested is an IP-type PDN connection for the future PCRF / PCF session binding when receiving N5 and / or RX requests for dedicated resources. N5 refers to the interface between the Policy Control Function (PCF) and the Application Function (AF) is used for exchanging flow-based charging control information between the Charging Rules Function (CRF) and the AF. An IP-CAN entity may be considered to be a network entity and / or interface that provides underlying IP connectivity between a user equipment and an IMS entity.
[0084] During 5006, the P-GW 504 signals a response to the create session request message of 5003. The Create Session Response may comprise information indicating at least one of: PDN gateway address for the user plane, a PDN gateway tunnel endpoint identifier (TEID) of the user plane, PDN gateway TEID of the control plane, PDN Type=non-IP, EPS Bearer Identity, EPS Bearer QoS, Protocol Configuration Options=UE-IP-address-for-IMS-signaling, or the UE port-for-IMS-signaling.
[0085] During 5007, the S-GW 503 signals a Create Session Response message to the MME 502, and further comprises the information of 5006.
[0086] During 5008, the MME 502 signals the UE 501. This signalling may comprise a confirmation that the requested PDN has been created. This may be performed, for example, by signalling, to the UE 501, an indication that the UE may activate a defaultEPS bearer. This signalling may comprise both an indication that a non-IP type of PDN has been established, and comprise the IP address determined during 5004.
[0087] Based on the signalling of 5008, the UE 501 may disable the UDP / IP stack for the IMS application and use the “UE-IP-address-for-IMS” (and possibly the UE port-for-IMS-signaling when provided during 5008) for IMS “contact” address in any subsequently performed registration request with the IMS.
[0088] FIG. 6 illustrates example signaling that may be performed when a registration is performed using the non-IP PDN connection established during the example of FIG.5.
[0089] FIG. 6 illustrates example signalling that may be performed between a UE 601, a mobility management entity (MME) 602, an S-GW 603, a P-GW 604, a PCF / PCRF 605, and a P-CSCF 606.
[0090] During 6001, the UE 601 signals a register request message towards the P-CSCF 606 to the P-GW 604. The register request message may comprise private-Access Network information (P-ANI) information corresponding to the UE’s known location. The register request message may comprise an identifier of the UE, such as an IMPU. The register request message may comprise a contact header that is based on the IP address received during 5008 and / or that is based on a port identified in the signalling of 5008. The UE will not use an IP stack (e.g., a UDP / IP stack and / or a TCP / IP stack) to send the register request to the P-GW 604. Where the session initiation protocol (SIP) is used to signal the P-GW 604 during 6001, the SIP application payload-header and / or Session Description Protocol (SDP) information are provided towards P-GW over a non-IP PDN.
[0091] Where multiple P-CSCF IP addresses were received in a P-CSCF IP address list (wherein the P-CSCF IP address may comprise multiple IP addresses that correspond to respective P-CSCF) during 5008, the UE may select a first P-CSCF IP address received in P-CSCF IP address list in PCO (e.g., when it is assumed that a default value of the intended P-CSCF IP address should be set to the first P-CSCF IP address in that list). When the first P-CSCF IP address is not user, the UE may issue a PDN connection update to send to the P-GW the IP address it is intending to use to reach the P-CSCF prior to the signalling of 6001.
[0092] During 6002, when the user plane part of the P-GW 604 receives the signalling of 6001 over the default EPS bearer for QCI=5, the user plane part of the P-GW 604 will add an IP header to the request (e.g., by setting the source IP address to the UE-IP-address-for-IMS). The user plane part of the P-GW may further set a destination IP address to be the first P-CSCF address (unless updated as described in the preceding paragraph), set a source port to either a UE port value (when the UE provided a port value during 6001) or a P-GW allocated port (as described herein), and set the destination power to a default value (e.g., 5060[default]).
[0093] During 6003, the P-GW 604 signals a registration request to the P-CSCF 606 based on the header details mentioned in the preceding paragraph. The registration request may comprise the IMPU, and the UE-IP-address-for-IMS. When the signalling of 6003 comprises a SIP register request, the signalling of 6003 comprises a SIP-UDP / IP payload.
[0094] During 6004, the P-CSCF 606 signals the P-GW 604 to indicate that the UE has been successfully registered with the IMS. For example, where this signalling comprises SIP signalling, the message of 6004 may comprise a 200 OK message.
[0095] During 6005, the P-GW 604 removes any IP header from the signaling of 6004. For example, the user plane part of the P-GW may remove a UDP / IP header from the received signalling of 6004.
[0096] During 6006, the user plane part of the P-GW 604 sends the UE 601 an indication that the UE has been registered with the IMS. Where this information is sent to the UE using the SIP, the signaling of 6006 may comprise the P-GW sending the UE only the SIP body and header (in addition to any lower protocol headers and body), while excluding an IP header (e.g., a UDP / IP header, a TCP-IP header, and / or any other type of IP header).
[0097] Once the UE is registered with the IMS, it may make and / or receive a call (e.g., respectively perform a mobile originated procedure or mobile terminated procedure).
[0098] The registration procedure of FIG. 6 may be considered to comprise at least one of the following method steps.
[0099] First, the UE initiates a PDN connection for IMS signalling by providing the following information to a P-GW core part: [APN=IMS; PDN type = non-IP; PCO = nonIP support for IMS].
[0100] Second, the P-GW accepts the PDN connection and provides an allocated IP address (e.g., (X.X.X.X)) via a PCO (even though the PDN is indicated as being nonIP based).
[0101] Optionally, the P-GW may additionally the UE with information indicating a UDP port for SIP signalling.
[0102] Third, the UE sends an IMS registration request to the P-GW (e.g., setting a contact as: <sip:user@X.X.X.X:port) without adding any IP header (e.g., without comprising any of an UDP / IP header or a TCP / IP header).
[0103] Fourth, the user plane part of the P-GW adds an IP header to the IMS registration request (e.g., source address=X.X.X.X; Destination address=P-CSCF-IP-Address), before sending the IMS registration request to the P-CSCF.
[0104] Fifth, when the response comes from P-CSCF to the registration request, the P-GW removes the IP header from the response and sends the remaining payload to the UE.
[0105] This is illustrated with respect to FIG. 7.
[0106] FIG. 7 illustrates example signalling that may be performed between a UE 701, a mobility management entity (MME) 702, an S-GW 703, a P-GW 704, a PCF / PCRF 705, a P-CSCF 706, and an IMS-AGW.
[0107] At least 7001 to 7006 relates to an operation for a mobile terminated call.
[0108] During 7001 , the P-CSCF 706 of the calling party sends a resource modification request to the PCF / PCRF 705. This resource modification request may request that dedicated resources be reserved for the media (e.g. for a voice call and / or a multimedia call) of the session being established.
[0109] During 7002, the PCRF / PCF 705 retrieves information corresponding to the IP-CAN session of the P-CSCF request of 7001. and negotiates the required IP-CAN session modification (media related bearer connection) with the P-GW 704.
[0110] During 7003, the P-GW 704 signals the S-GW 703. This signalling may comprise a request for a dedicated bearer (e.g., QCI=1) to be established. This signalling may comprise an indication that the request relates to a non-IP PDN. This signalling may comprise, for example, a General Packet Radio Service Tunnelling Protocol user plane Tunnel endpoint identifier (GTP-U-TEID). This signaling may not comprise an uplink traffic flow template (UL TFT). Although not used for signalling to the UE, the P-GW may create an IP header to be used for IMS signalling (e.g., an RTP media relay).
[0111] During 7004, the S-GW 703 forwards the create bearer request of 7003 to the MME 702.
[0112] During 7005, the MME 702 sends the UE 701 a request to activate a dedicated bearer. For example, the signalling of 7005 may signal an activate dedicated EPS bearer context request to the UE 701.
[0113] During 7006, the UE 701 signals the MME 702. This signalling may indicate that the UE has activated the dedicated bearer of 7005. For example, the signalling may comprise an activate dedicated EPS bearer context accept message.
[0114] During 7007, the MME signals the S-GW703. This signalling may indicate that the bearer requested during 7004 has been established.
[0115] During 7008, the SGW703 signals the P-GW704. This signalling may comprise an indication that the bearer requested during 7003 has been created.
[0116] During 7009, the P-GW 704 signals the PCF / PCRF 705. This signalling may comprise an indication that the requested bearer has been established.
[0117] During 7010, the P-GW704 receives IMS mobile terminated signalling from the P-CSCF 706. This signalling of 7010 may comprise an IP header (e.g., a UDP / IP transport header). This signalling may comprise the SDP (transport resources of the IMS-AGW).
[0118] During 7011, the P-GW 704 removes the IP header from the signalling of 7010 to form modified signalling.
[0119] During 7012, the P-GW 704 signals UE 701 using the established dedicated bearer. This signalling may comprise the modified signalling of 7011. Stated differently, during 7012, the P-GW 704 may signal the IMS MT signaling message payload of 7010 to the UE, where this IMS MT signalling message payload does not comprise an IP header.
[0120] The UE may extract the SDP from the signalling of 7012 to find out the transport resources required for receiving the IMS call. The UE may determine that at least one parameter of the bearer is to be updated (for example, to provide the UEs own UDP port for receiving downlink IMS media (unless the P-GW is allowed to allocate this port). Subsequently, the UE may, during 7013, signal a request to the P-GW 704 to cause the P-GW to update the bearer. This signaling may comprise a PCO that updates the port as mentioned above. The signalling may comprise the IMS-AGW IP address and UDP port information, although the signalling is transmitted without an IP header.
[0121] During 7014, the UE 701 signals an acknowledgement of the IMS MT signalling of 7012 to the P-GW 704.
[0122] During 7015, the user plane part of the P-GW 704 adds an IP header (e.g., a UDP / IP header, etc.) to the acknowledgement payload provided during 7014.
[0123] During 7016, the P-GW 704 sends the acknowledgement (comprising the IP header) to the P-CSCF 706.
[0124] Subsequently, when the media starts being exchanged between the UE 701 and the IMS-AGW, the P-GW strips the IP header (e.g., the UDP / IP header) from a payload received in downlink that is to be forwarded to the UE, and adds the an IP header to an RTP payload being sent uplink from the UE to the IMS. This may be performed based on the port and / or IP address information provided during 7013.
[0125] At least one step of the above example method of FIG. 7 is illustrated in the following.
[0126] During an MT call, the P-CSCF requests a dedicated bearer creation towards P-GW-control plane part I IP-CAN session via PCRF / PCF.
[0127] The P-GW-control plane part issues a dedicated bearer set up with a request for port allocation information in PCO (PCO needed to indicate the port allocation request); That way, the UE will allocate a local UDP port and send the details of the remote port (Media port of calling party) to P-GW latter.
[0128] The UE allocates a UDP port in advance and informs the P-GW via PCO (Bearer setup response) of this allocated UDP port.
[0129] The P-CSCF sends a SIP Invite (SDP) to the UE over the default bearer setup during reg call flows. The P-GW removes the TCP / IP header before forwarding the SIP Invite.
[0130] The UE provides a response to the P-CSCF that comprises the UEs allocated port and stores the remote port indicated in the SIP invite. The UE may provide this remote port in via PCO header in update PDN connection signaling sent to P-GW-control plane part.
[0131] The P-GW-control plane part provides the IP address and UDP port information to be used to exchange RTP packets with the IMS-AGW to the user plane part of the P-GW.
[0132] When the UE sends any media (e.g., when the UE sends RTP), the UE does not include any IP header along with the media. The P-GW-user plane part will instead add an IP header before this is passed to the IMS. For example, the P-GW user plane part may set [UDP source=UE allocated port, UDP Destination= remote port]
[0133] Similarly, when the downlink RTP media is received from the IMS-AGW for the UE, the P-GW-user plane part may remove the IP header and send the RTP payload to the UE using the corresponding EPS bearer.
[0134] The following illustrates how UDP ports may be handled in a network described herein.
[0135] For when IP-PDN connections are used for IMS, each UE has a different IP address and the UE allocates itself a UE source port to be used for IMS signaling (e.g., for control data traffic) and a UE source port to be used for IMS media (e.g., for user plane data traffic).
[0136] However, when a non-IP PDN connection is used for IMS (as described herein), as the UE may have no UDP / IP stack, the P-GW (or at least one of an SMF or UPF in 5G and beyond) may allocate at least one of:• A UE port-for-IMS-signaling on behalf of the UE. If this is not allocated by the P-GW (or a similar function), the UE may allocate itself its own UDP port for IMS signaling• the UE port-for-IMS-media on behalf of the UE. If this is not allocated by the P- GW (or a similar function), the UE may allocate itself its own UDP port for IMS media.
[0137] When a network node (such as the P-GW) allocates the source UDP ports on behalf of the UE, the network node may use the same user plane P-GW IP address for multiple UE(s).
[0138] The control plane part of the P-GW may be configured to provide the user plane part of the P-GW with at least one of an IP address assigned to the UE by the control plane part of the P-GW, or a power assigned to the UE by the control plane part of the P-GW.
[0139] An interface between the control plane (CP) part and the user plane (UP) part may therefore, in an example, be used by the CP entity to specify the source IP address and port that shall be used by the UP entity in respect of the UE.
[0140] As the interface between the control plane (CP) part of a P-GW and the user plane (UP) part of the P-GW is subject to standards (e.g. 3GPP TS 29.244), the following provides at least one example of how such a method may be expressed in the standards.
[0141] As a first example, a CP part of the P-GW may request the UP part of the P-GW to associate an UL GTP-user plane connection (or a quality of service flow when 5G or 6G core network functions are considered) related with IMS signaling with thefollowing information to be used by UP part when sending corresponding traffic to the network side interface of the UP entity• Source IP= UE-IP-address-for-IMS• Destination IP = intended P-CSCF address• Source port=UE or P-GW allocated port;• Destination port=e.g. 5060
[0142] The CP part of the P-GW may request the UP part of the P-GW to associate the UL GTP-u connection (Qos flow for 5G) related with IMS media (voice) with the following information to be used by UP entity when sending corresponding traffic to the network side interface of the UP entity• Source IP= UE-IP-address-for-IMS• Destination IP = IMS-AGW IP address• Source port=UE or P-GW allocated port• Destination port= IMS-AGW UDP port
[0143] At least one or more methods of the above examples are illustrated with respect to FIGs. 8 to 11 , with FIGs. 8 and 9 relating to a first set of interacting apparatus, and FIGs. 10 and 11 relating to a second set of interacting apparatus. It is understood that comments made in respect of terms and / or expressions in any of these FIGs. also apply in respect of the other FIGs.. For example, it is understood that the description indicating that the IP protocol level headers (also referred to herein as “IP headers”) may comprise at least one of: an IP header, a UDP / IP header, or a TCP / IP header applies in respect of any (e.g., one or more, including all) of FIGs. 8 to 11.
[0144] It is further understood in the following that the UE’s intention to not use an IP protocol level header and / or to not comprise an IP protocol level header in IMS-related data traffic signalling may be based on the UE determining that at least one condition has been fulfilled (e.g., that the access network through which an IMS service is to be received is a narrowband-loT access, that the UE’s remaining battery power is below a threshold amount, that a quality of service has dropped below a different threshold amount, etc.).
[0145] FIG. 8 illustrates at least one method that may be performed by an apparatus. The apparatus may comprise, or be comprised in, a UE. The apparatus may be as described in connection with any of FIGs. 1 and 3.
[0146] During 801, the apparatus transmits, to a first network node, a request to connect to an internet protocol multimedia system (IMS), wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers. The first network node may be as described below in relation to FIG. 9.
[0147] It is understood that the IP protocol level headers (also referred to herein as “IP headers”) may comprise at least one of: an IP header, a UDP / IP header, or a TCP / IP header.
[0148] The apparatus may receive, from the first network node based on the transmitted request, an indication to activate a bearer for a packet data network for which the IP protocol layer is suspended, wherein the indication further comprises an IP address for use by the apparatus when signalling IMS-related data traffic.
[0149] It is understood that IMS-related data traffic may comprise at least one of: IMS signalling (e.g., registration of the UE to the IMS, to establish an IMS service) and for the actual realization / operation of the IMS service (e.g., voice call). Stated differently, it us understood that IMS-related data traffic may comprise at least one of control-related signalling and user data-related signalling.
[0150] The indication may further comprise an identifier of a first port to be used by the apparatus when signalling IMS signalling-related data traffic. The first port may be a port that is used for IMS-signalling (e.g., control-related IMS signalling). The first port may not be used for IMS media-based signalling (e.g., user data-related signalling).
[0151] The apparatus may transmit, to a second network node, a request to register the apparatus with an IMS, wherein the request to register comprises the IP address. The second network node may comprise at least one of the first network node or a P-CSCF.
[0152] The request to register may further comprise the identifier of the first port.
[0153] The apparatus may receive, from the first network node, signalling comprising an indication that the apparatus has been registered with the IMS. The receiving may comprise suspending using IP protocol level header when exchanging IMS-related data traffic signalling. Stated differently, the signalling comprising an indication that the apparatus has been registered with the IMS may not comprise an IP header (e.g., UDP / IP header, etc.). Stated differently, the signalling comprising an indication that the apparatus has been registered with the IMS may be processed at the apparatus while the apparatus has suspended (e.g., disabled) an IP protocol level stack at the apparatus for processing IMS-related data traffic.
[0154] The apparatus may receive, from the second network node, signalling comprising an IMS mobile terminated signalling message payload. The receiving may comprise suspending an IP protocol level header when exchanging IMS-related data traffic signalling. This may be as described above. The apparatus may transmit a bearer update message to the first network node, wherein the bearer update message comprises information indicating at least one of a second IP address or second port.
[0155] The second port may be a port for the apparatus for receiving an IMS service based on the IMS mobile terminated signalling message payload. The second port may comprise a port of the IMS AGW,
[0156] FIG. 9 illustrates one or more methods that may be performed by an apparatus. The apparatus may comprise (or be comprised in) or be configured to implement a network node. For example, the apparatus may store instructions of a network node in at least one memory of the apparatus, which when executed by at least one processor of the apparatus, may cause the apparatus at least to perform one or more methods. The network node may comprise a packet gateway (e.g., a P-GW). The network node may be as described above in connection with FIG. 2.
[0157] The apparatus may be part of a distributed computing system that includes multiple computing devices (e.g., servers) in communication with each other over a data network, as well as optionally one or more additional components. The one or more methods described herein may be performed by different computing devices (e.g., servers) of the distributed computing system. The apparatus may be a virtual machine provided by the infrastructure (e.g., a hypervisor, processors, and memories) of a cloud computing system.
[0158] During 901, the apparatus receives, from a user equipment, a request to connect to an internet protocol multimedia system (IMS), wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers. The user equipment may correspond to the apparatus of FIG. 9. The IP protocol level headers may be as discussed above in connection with FIG. 8.
[0159] The apparatus may transmit, to the user equipment based on the received request, an indication to activate a bearer for a packet data network for which the IP protocol layer is suspended, wherein the indication further comprises a first IP address for use by the user equipment when signalling IMS-related data traffic. The indication to activate a bearer may not comprise an IP header.
[0160] The indication may further comprise an identifier of a first port to be used by the user equipment when exchanging IMS signalling-related data traffic. The first port may be a port that is used for IMS-signalling (e.g., control-related IMS signalling). The first port may not be used for IMS media-based signalling (e.g., user data-related signalling).
[0161] The apparatus may receive, from the user equipment, a request to register the user equipment with an IMS, wherein the request to register comprises the first IP address and further comprises the identifier of the first port. The apparatus may cause the user equipment to be registered with the IMS based on the first IP address. The apparatus may store the first IP address and the identifier of the first port.
[0162] The apparatus may transmit further IMS-signalling related data traffic towards the user equipment based on the stored first IP address and the identifier of the first port The IMS-signalling related data traffic may comprise IMS signalling traffic between the user equipment and a P-CSCF.
[0163] The apparatus may transmit, to the user equipment, signalling comprising an indication that the user equipment has been registered with the IMS. The transmitting may comprise suspending using IP protocol level header when exchanging IMS-related data traffic signalling. Stated differently, the transmitting may comprise formatting the signalling comprising the indication such that is does not comprise an IP header (e.g., does not comprise a UDP / IP header, etc.).
[0164] The apparatus may transmit, to the user equipment, signalling comprising an IMS mobile terminated signalling message payload, wherein transmitting comprises suspending an IP protocol level header (e.g., not comprising an IP header in the transmitted signalling to the UE).
[0165] The apparatus may receive a bearer update message from the user equipment, wherein the bearer update message comprises information indicating at least one of a second IP address and second port. The second IP address and second port may be as described above in relation to FIG. 8.
[0166] The apparatus may comprise a control plane part that is configured to perform at least one control plane function, and a user plane part that is configured to perform at least one user plane function. The apparatus may provide, from the control plane part to the user plane part, at least one of the first IP address or a port allocated to the user equipment for insertion into signalling of IMS-related data traffic to the user equipment.
[0167] The apparatus may receive, from the user equipment, first IMS-related data traffic, modify the first IMS-related data traffic to form first modified IMS-related data traffic that comprises an IP header (e.g., the first IP header), and transmit the first modified IMS-related data traffic to the IMS.
[0168] The apparatus may receive, from the IMS, second IMS-related data traffic for the user equipment, wherein the second IMS-related data traffic comprises an IP header (e.g., the first IP header). The apparatus may modify the second IMS-related data traffic by removing the IP header to form second modified IMS-related data traffic, and transmit the second modified IMS-related data traffic to the user equipment.
[0169] The first IMS-related data traffic may correspond to at least one of: signalling for the IMS or media plane for IMS.
[0170] The second IMS-related data traffic may correspond to at least one of signalling for the IMS or media plane for IMS.
[0171] FIG. 10 illustrates at least one method that may be performed by an apparatus. The apparatus may comprise, or be comprised in, a UE. The apparatus may be as described in connection with any of FIGs. 1 and 3.
[0172] During 1001, the apparatus determines that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellite-based network access node. The narrowband access may comprise an NB-loT access.
[0173] During 1002, the apparatus transmits, to a first network node via the satellitebased network access node, a request to connect to the IMS, wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling.
[0174] During 1003, the apparatus receives, from the first network node via the satellite-based network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.
[0175] The acknowledgement may further comprises an identifier of a first port to be used by the apparatus when exchanging IMS signalling-related data traffic. The first port may be a port that is used for IMS-signalling (e.g., control-related IMS signalling). The first port may not be used for IMS media-based signalling (e.g., user data-related signalling).
[0176] The apparatus may transmit, to a second network node, a request to register the apparatus with an IMS, wherein the request to register comprises the first IP address in a contact header. The second network node may comprise at least one of the first network node or a P-CSCF. The transmitting may comprise abstaining from adding an IP header to the request. Stated differently, the request to register may not comprise an IP header (while it does comprise the first IP address). Stated differently, the transmit chain of the apparatus may be configured to suspend an IP protocol stack when formatting the request to register for transmission.
[0177] The apparatus may receive, from the second network node, signalling comprising an indication that the apparatus has been registered with the IMS. The receiving may comprises suspending an IP protocol level header processing when processing the signalling. Stated differently, the receive processing of the signalling comprising the indication without use of an IP protocol level stack. Stated differently, the signalling comprising the indication does not comprise an IP header.
[0178] The request to register may further comprise the identifier of the first port.
[0179] The signalling comprising the indication that the apparatus has been registered with the IMS may comprise a session initiation protocol message (e.g., a 200 OK message).
[0180] The apparatus may receive, from the first network node, signalling comprising an IMS mobile terminated signalling message payload. The receiving may comprise suspending using an IP protocol level header when exchanging IMS-related data traffic. This may be as described above in relation to FIG. 8. It is understood in any of these examples that “exchanging” IMS-related data traffic may comprise at least one of transmitting or receiving IMS-related data traffic.
[0181] The apparatus may transmit a bearer update message to the first network node, wherein the bearer update message comprises information indicating at least one of a second IP address or second first port. The second IP address and / or second port may be as described above in relation to FIG. 8.
[0182] FIG. 11 illustrates one or more methods that may be performed by an apparatus. The apparatus may comprise (or be comprised in) or be configured to implement a network node. For example, the apparatus may store instructions of a network node in at least one memory of the apparatus, which when executed by at least one processor of the apparatus, may cause the apparatus at least to performone or more methods. The network node may comprise a packet gateway (e.g., a P-GW). The network node may be as described above in connection with FIG. 2.
[0183] The apparatus may be part of a distributed computing system that includes multiple computing devices (e.g., servers) in communication with each other over a data network, as well as optionally one or more additional components. The one or more methods described herein may be performed by different computing devices (e.g., servers) of the distributed computing system. The apparatus may be a virtual machine provided by the infrastructure (e.g., a hypervisor, processors, and memories) of a cloud computing system.
[0184] During 1101, the apparatus receives, from a user equipment via a satellitebased access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling.
[0185] During 1102, the apparatus transmits an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.
[0186] The acknowledgement may further comprise an identifier of a first port to be used by the user equipment when exchanging IMS-signall ing related data traffic. The first port may be a port that is used for IMS-signalling (e.g., control-related IMS signalling). The first port may not be used for IMS media-based signalling (e.g., user data-related signalling).
[0187] The apparatus may receive, from the user equipment, a request to register the apparatus with an IMS, wherein the request to register comprises the first IP address in a contact header and further comprises the identifier of the first port. The request to register may not comprise an IP header. The apparatus may cause the user equipment to be registered with the IMS based on the IP address (e.g., by forwarding the request to register (with an added IP header) to a P-CSCF. The apparatus may store the IP address and the identifier of the first port.
[0188] The apparatus may transmit, to the user equipment, signalling comprising an indication that the apparatus has been registered with the IMS. The transmitting may comprise suspending using an IP protocol level header when exchanging IMS-related data traffic signalling. Stated differently, the transmit chain of the apparatus may be configured to suspend an IP protocol level stack when formatting the signalling fortransmitting the indication that the apparatus has been registered. Stated differently, the signalling comprising the indication that the apparatus has been registered may not comprise an IP header.
[0189] The apparatus may transmit, to the user equipment, signalling comprising an indication that the user equipment has been registered with an internet protocol multimedia system (IMS. The transmitting may, wherein the transmitting comprises suspending using IP protocol level header when exchanging IMS-related data traffic signalling.
[0190] The signalling comprising the indication that the apparatus has been registered with the IMS comprises a session initiation protocol message.
[0191] The apparatus may transmit, to the user equipment, signalling comprising an IMS mobile terminated signalling message payload. The transmitting may comprise suspending an IP protocol level header. Stated differently, the transmit chain of the apparatus may be configured to suspend an IP protocol level stack when formatting the signalling for comprising an IMS mobile terminated signalling message payload. Stated differently, the signalling comprising an IMS mobile terminated signalling message payload may not comprise an IP header.
[0192] The apparatus may receive a bearer update message from the user equipment. The bearer update message may comprise at least one of a second IP address or a second port for the user equipment to receive an IMS service based on the IMS mobile terminated signalling message payload. The bearer update message may not comprise an IP header. The second IP address and / or second port may be as described above in relation to any of FIGs. 8 to 10.
[0193] The apparatus may comprise a control plane part that is configured to perform at least one control plane function, and a user plane part that is configured to perform at least one user plane function. The apparatus may provide, from the control plane part to the user plane part, at least one of the first IP address or a port allocated to the user equipment for insertion into signalling of IMS-related data traffic to the user equipment.
[0194] The apparatus may receive, from the user equipment, first IMS-related data traffic, modify the first IMS-related data traffic to form first modified IMS-related data traffic that comprises an IP header (e.g., the first IP header), and transmit the first modified IMS-related data traffic to the IMS.
[0195] The apparatus may receive, from the IMS, second IMS-related data traffic for the user equipment, wherein the second IMS-related data traffic comprises an IP header (e.g., the first IP header). The apparatus may modify the second IMS-related data traffic by removing the IP header to form second modified IMS-related data traffic, and transmit the second modified IMS-related data traffic to the user equipment.
[0196] The first IMS-related data traffic may correspond to at least one of: signalling for the IMS or media plane for IMS.
[0197] The second IMS-related data traffic may correspond to at least one of signalling for the IMS or media plane for IMS.
[0198] It is understood in the above that references to a P-GW may be replaced by references to at least one other type of core network node, as indicated in the implementation examples.
[0199] It is understood that although the above examples have been considered in the context of LTE-based communication systems, that similar methods may be applied in respect of other communication systems. For example, the following entities may be considered as performing one or more analogous functions of their corresponding / mapped apparatus. The mapping of LTE and 5G / 6G terms may be as follows:• P-GW-u (user plane part of the P-GW) UPF• P-GW-c (control plane part of theP-GW SMF (6G SM)• S-GW -> l-SMF if any• MME AMF (6G MM)• PCRF PCF• eNB gNB (RAN node for 6G)• EPS bearer QoS flow• APN DNN
[0200] It should be understood that the apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and / or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.
[0201] It is also noted herein that there are several variations and modifications, which may be made to the various embodiments described herein without departing from the scope of this disclosure.
[0202] It is noted that whilst some embodiments have been described in relation to 5G networks, similar concepts can be applied in relation to other networks and communication systems. Therefore, although certain embodiments were described above, by way of example, with reference to certain example architectures for wireless networks, technologies and standards, some embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0203] For example, the phrases “at least one of A or B”, “at least one of A and B”, and “A and / or B” means (A), (B), or (A and B). In another example, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
[0204] As used herein, the term “or” refers to a non-exclusive “or” unless otherwise indicated (e.g., use of “or else” or “or in the alternative”).
[0205] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included. Analogously, performing a step or functionality “based on A” does not indicate that the step or functionality.
[0206] In general, the various embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0207] As used herein, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in analog, digital, and / or quantum circuitry) and(b) combinations of hardware circuit(s) and software, such as (as applicable): 1. (i) a combination of analog, digital, and / or quantum hardware circuit(s) with software / firmware and2. (ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device, or server, to perform various functions); and3. (c) any or all portions of hardware circuit(s), such as a microprocessor(s), processor(s) and / or quantum processor(s), that require software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0208] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used in this disclosure, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0209] Some embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and / or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.
[0210] Further in this regard it should be noted that any blocks of the logic flow as in the FIGs. may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions.The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media.
[0211] The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).
[0212] The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.
[0213] Some embodiments of the disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.
[0214] The scope of protection sought for various embodiments of the disclosure is set out by the independent claims. The embodiments and features, if any, described in this disclosure that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the disclosure.
[0215] The foregoing description has provided, by way of non-limiting examples, a full and informative description of the embodiments of this disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this disclosure will still fall within the scope of this disclosure. Indeed, there are further embodiment(s) comprising a combination of oneor more embodiment(s) with any of the other embodiment(s) described in this disclosure.
Claims
CLAIMS1) An apparatus comprising:at least one processor; andat least one memory comprising instructions that, when executed by the at least one processor, causes the apparatus at least to perform:determining that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellitebased network access node;transmitting, to a first network node via the satellite-based network access node, a request to connect to the IMS, wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling; andreceiving, from the first network node via the satellite-based network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.2) An apparatus as claimed in claim 1, wherein the acknowledgement further comprises an identifier of a port to be used by the apparatus when exchanging IMS-signalling related data traffic.3) An apparatus as claimed in any preceding claim, wherein the apparatus is further caused to perform:transmitting, to a second network node, a request to register the apparatus with an IMS, wherein the request to register comprises the first IP address in a contact header, wherein the transmitting comprises abstaining from adding an IP header to the request; andreceiving, from the second network node, signalling comprising an indication that the apparatus has been registered with the IMS, wherein receiving comprises suspending using an IP protocol level header when exchanging IMS-related data traffic signalling.354) An apparatus as claimed claim 3 when dependent on claim 2, wherein the request to register further comprises the identifier of the first port.5) An apparatus as claimed in any of claims 3 to 4, wherein the signalling comprising the indication that the apparatus has been registered with the IMS comprises a session initiation protocol message.6) An apparatus as claimed in any preceding claim wherein the apparatus is further caused to perform:receiving, from the first network node, signalling comprising an IMS mobile terminated signalling message payload, wherein said receiving comprises suspending using an IP protocol level header when exchanging IMS- related data traffic; andtransmitting a bearer update message to the first network node, wherein the bearer update message comprises information indicating at least one of a second IP address or second port.7) An apparatus comprising:at least one processor; andat least one memory comprising instructions that, when executed by the at least one processor, causes the apparatus at least to perform:receiving, from a user equipment via a satellite-based access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling; andtransmitting an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.8) An apparatus as claimed in claim 7, wherein the acknowledgement further comprises an identifier of a first port to be used by the user equipment when exchanging IMS-signalling related data traffic.9) An apparatus as claimed in any of claims 7 to 8, wherein the apparatus is further caused to perform:receiving, from the user equipment, a request to register the apparatus with an IMS, wherein the request to register comprises the first IP address in a contact header and further comprises the identifier of the first port, wherein the request to register does not comprise an IP header;causing the user equipment to be registered with the IMS based on the IP address;storing first the IP address and the identifier of the first port; and transmitting, to the user equipment, signalling comprising an indication that the apparatus has been registered with the IMS, wherein the transmitting comprises suspending using an IP protocol level header when exchanging IMS- related data traffic signalling.10) An apparatus as claimed in any of claims 7 to 9, wherein the signalling comprising the indication that the apparatus has been registered with the IMS comprises a session initiation protocol message.11) An apparatus as claimed in any of claims 7 to 10 wherein the apparatus is further caused to perform:transmitting, to the user equipment, signalling comprising an IMS mobile terminated signalling message payload, wherein transmitting comprises suspending an IP protocol level header; andreceiving a bearer update message from the user equipment, wherein the bearer update message comprises at least one of a second IP address or a second port for the user equipment to receive an IMS service based on the IMS mobile terminated signalling message payload.12) An apparatus as claimed in any of claims 7 to 11, wherein the apparatus is further caused to perform:receiving, from the user equipment, first IMS-related data traffic signalling for the IMS;modifying the first IMS-related data traffic signalling to form first modified IMS-related data traffic signalling that comprises an IP header; andtransmitting the first modified IMS-related data traffic signalling to the IMS.13) An apparatus as claimed in any of claims 7 to 12, wherein the apparatus is further caused to perform:receiving, from the IMS, second IMS-related data traffic signalling for the user equipment, wherein the second IMS-related data traffic signalling comprises an IP header;modifying the second IMS signalling by removing the IP header to form second modified IMS-related data traffic signalling; andtransmitting the second IMS-related data traffic modified signalling to the user equipment.14) An apparatus as claimed in any of claims 7 to 13, wherein the apparatus comprises a control plane part that is configured to perform at least one control plane function, and a user plane part that is configured to perform at least one user plane function, wherein the apparatus is further caused to perform:providing, from the control plane part to the user plane part, at least one of the first IP address or a port allocated to the user equipment for IMS-related data traffic.15) An apparatus as claimed in any of claims 13 to 14, wherein:the first IMS-related data traffic corresponds to at least one of:signalling for the IMS or media plane for IMS, andwherein the second IMS-related data traffic corresponds to at least one of signalling for the IMS or media plane for IMS.16) A method for an apparatus, the method comprising:determining that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellitebased network access node;transmitting, to a first network node via the satellite-based network access node, a request to connect to the IMS, wherein the request indicatesthat the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling; andreceiving, from the first network node via the satellite-based network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.17) A method for an apparatus, the method comprising:receiving, from a user equipment via a satellite-based access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling; andtransmitting an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.18) A computer program comprising instructions which, when the program is executed by a computer of an apparatus, cause the apparatus to carry out: determining that the apparatus is to connect to an internet protocol multimedia system (IMS) via a narrowband access provided by a satellitebased network access node;transmitting, to a first network node via the satellite-based network access node, a request to connect to the IMS, wherein the request indicates that the apparatus does not intend to use internet protocol (IP) protocol level headers for IMS signalling; andreceiving, from the first network node via the satellite-based network access node, an acknowledgement to the request to connect to the IMS, wherein the acknowledgement comprises a first IP address for use by the apparatus when signalling IMS-related data traffic.19) A computer program comprising instructions which, when the program is executed by a computer of an apparatus, cause the apparatus to carry out:receiving, from a user equipment via a satellite-based access network node, a request to connect the user equipment to the IMS, wherein the request indicates that the user equipment does not intend to use internet protocol (IP) protocol level headers for IMS signalling; andtransmitting an acknowledgement to the request to connect to the IMS to the user equipment via the satellite-based access network node, wherein the acknowledgement comprises a first IP address for use by the user equipment when signalling IMS-related data traffic.40
