Signaling optimizations for communication over non-terrestrial networks

The Gm* interface signaling protocol optimizes voice communication over non-terrestrial networks by transforming messages to standard SIP signaling, addressing bandwidth and latency issues, thereby enhancing communication efficiency and user experience.

WO2026233638A1PCT designated stage Publication Date: 2026-11-12NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

The challenge in supporting voice communications over non-terrestrial networks, particularly via GEO satellites, is the constrained bandwidth and long round-trip delay, which are exacerbated by verbose signaling overhead during call setup procedures.

Method used

A new signaling protocol, referred to as Gm* interface signaling, is introduced to reduce the number and size of messages exchanged between the terminal device and the network entity during initial registration and voice communication setup, utilizing a proxy function to transform Gm* interface signaling into standard SIP signaling, thereby optimizing communication over non-terrestrial networks.

Benefits of technology

This approach minimizes signaling overhead, reduces session establishment time, and enhances user experience by efficiently utilizing network resources, especially in environments with limited bandwidth, while reducing congestion and packet loss.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026060386_12112026_PF_FP_ABST
    Figure EP2026060386_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Example embodiments of the present disclosure are directed to signaling optimization for communication over non-terrestrial networks. A method comprises determining, based on information indicative of the capability of a network, support for the establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and transmitting, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request.
Need to check novelty before this filing date? Find Prior Art

Description

SIGNALING OPTIMIZATIONS FOR COMMUNICATION OVER NONTERRESTRIAL NETWORKSFIELD

[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for signaling optimization for communication over non-terrestrial networks (NTNs).BACKGROUND

[0002] A communication network may serve 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] The communication network may operate in accordance with standards such as those provided by Third Generation Partnership Project (3 GPP) or European Telecommunications Standards Institute (ETSI). Examples of standards provided by 3 GPP are the so-called 3 GPP standards for cellular technology generations, such as 3 GPP standards for 4G technology, 5G technology, 6G technology etc.SUMMARY

[0004] In a first aspect of the present disclosure, there is provided an apparatus. The apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and transmit, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on therequest.

[0005] In a second aspect of the present disclosure, there is provided a first network entity in an Internet protocol (IP) multimedia subsystem (IMS). The first network entity in an Internet protocol (IP) multimedia subsystem (IMS) comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network entity at least to: receive, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request; and create, based on the request, a SIP request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication.

[0006] In a third aspect of the present disclosure, there is provided a method. The method comprises: determining, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and transmitting, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request.

[0007] In a fourth aspect of the present disclosure, there is provided a method. The method comprises: receiving, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request; and creating, based on the request, a SIP request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication.

[0008] In a fifth aspect of the present disclosure, there is provided an apparatus. The apparatus comprises means for determining, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and means for transmitting, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the firstnetwork entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request.

[0009] In a sixth aspect of the present disclosure, there is provided a first network entity in an Internet protocol (IP) multimedia subsystem (IMS). The first network entity in an Internet protocol (IP) multimedia subsystem (IMS) comprises means for receiving, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request; and means for creating, based on the request, a SIP request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication.

[0010] In a seventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the third aspect.

[0011] In an eighth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.

[0012] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Some example embodiments will now be described with reference to the accompanying drawings, where:

[0014] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

[0015] FIG. 2 illustrates an example signaling process in accordance with some embodiments in the disclosure;

[0016] FIG. 3 illustrates an example signaling process in accordance with some embodiments in the disclosure;

[0017] FIG. 4 illustrates a flowchart of a method implemented at an apparatus inaccordance with some example embodiments of the present disclosure;

[0018] FIG. 5 illustrates a flowchart of a method implemented at a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in accordance with some example embodiments of the present disclosure;

[0019] FIG. 6 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

[0020] FIG. 7 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

[0021] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION

[0022] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

[0023] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0024] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0025] It shall be understood that although the terms “first,” “second,”..., etc. in front ofnoun(s) and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another and they do not limit the order of the noun(s). For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0026] 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.

[0027] 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.

[0028] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0029] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform variousfunctions) and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0030] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0031] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the fifth generation (5G), 5.5G, the sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0032] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referredto as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.

[0033] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0034] As used herein, the term “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between aterminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other combination of the time, frequency, space and / or code domain resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0035] As described herein, a core network function may be implemented as a core network entity that includes a combination of hardware processing circuit and software and / or firmware comprising machine-readable instructions, or software comprising machine-readable instructions that are executable by at least one processor of hardware processing circuit of an apparatus. A hardware processing circuit includes at least one processor and at least one memory storing machine-readable instructions that are executable by the at least one processor of the hardware processing circuit. A processor includes any or some combination of an accelerator, a microprocessor, a core of a multicore microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, a central processing unit, a graphic processing unit, a tensor processing unit. Memory includes any or some combination of volatile or non-volatile memory (e.g., a flash memory, cache, a random-access memory (RAM), and / or a read-only memory (ROM)). The memory stores the machine-readable instructions of the software and / or firmware for execution by the at least one processor of the hardware processing circuit. The machine-readable instructions are executable by the at least one processor of the hardware processing circuit cause the hardware processing circuit to perform the actions or operations of the methods described herein. For example, the session management function described herein may be implemented as a session management entity and the session management policy control function described herein may be implemented as a session management policy control entity, respectively.

[0036] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 100, a plurality of communication devices, including a terminal device 110, a network device 120 and a network entity 130, can communicate with each other. In the example of FIG. 1, the terminal device 110 may be a UE, the network device 120 may bea base station serving the UE and the network entity 130 may be one or more functions of the core network. The serving area of the network device 120 may be called a cell.

[0037] It is to be understood that the number of devices and their connections shown in FIG. 1 are only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell, and one or more additional cells may be deployed in the communication environment 100. It is noted that although illustrated as a network device, the network device 120 may be another device than a network device. Although illustrated as a terminal device, the terminal device 110 may be another device than a terminal device.

[0038] In the following, for the purpose of illustration, example embodiments are described with the terminal device 110 operating as a UE in non-terrestrial networks (NTNs), the network device 120 operating as a satellite or server device in NTNs and the network entity 130 operating as a proxy-call session control function (P-CSCF). However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other devices. In NTNs, the network device 120 may be a base station (an eNode B or gNode B) that is deployed at the satellite or a base station that is at a ground connected with a satellite via gateway. Also in the following, for the purpose of illustration, example embodiments are described in connection with evolved packet core (EPC) as the core network architecture supporting 3 GPP access technologies, it should be noted that embodiments may also be applied to other 3GPP core networks — 5G / 6G or future developed core network architectures by applying appropriate translation rules to account for the differences of corresponding architectures.

[0039] In some example embodiments, a transmission direction from the network device 120 to the terminal device 110 is referred to as a downlink (DL), while a transmission direction from the terminal device 110 to the network device 120 is referred to as an uplink (UL). In DL, the network device 120 is a transmitting (TX) device (or a transmitter) and the terminal device 110 is a receiving (RX) device (or a receiver). In UL, the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver).

[0040] Communications in the communication environment 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.

[0041] Non-terrestrial networks (NTNs) include wireless communication systems providing non-terrestrial wireless access to UEs by means of an NTN payload integrated either in airborne platforms (for example, high-altitude platforms (HAPs)) or space-borne NTN vehicles (for example, satellites), and an NTN-gateway (NTN Gateway (NTN-GW)). The NTN vehicle operates above Earth’s surface, using platforms in the air in Earth’s orbit. These platforms may include satellites in a low Earth orbit (LEO), medium Earth orbit (MEO), and geostationary orbit (GEO), HEO (highly elliptical orbit) as well as HAPs and drones. An orbit of a satellite can be a geosynchronous orbit (GSO) or non-geosynchronous orbit (NGSO).

[0042] GEOs, also referred to as a geosynchronous equatorial orbits, are circular orbits 35,786 km above Earth’s equator and follow the direction of Earth's rotation. GEO satellites appear stationary relative to a fixed point on Earth but still have slight orbital movement.

[0043] GSOs are a circular orbit about 35,786 kilometers above the Earth’s surface. At any inclination, a geosynchronous orbit synchronizes with the rotation of the Earth. More specifically, the time it takes for the Earth to rotate on its axis is 23 hours, 56 minutes, and 4.09 seconds, which is the same as a satellite in a geosynchronous orbit. The GSO can have any inclination, so the key difference with GEOs is the fact that GEOs always lie on the same plane as the equator of Earth.

[0044] Internet protocol (IP) multimedia subsystem (IMS) is a service framework for delivering multimedia services, such as voice, video and text messaging over IP networks. There are ongoing discussions on the support for IMS voice communications transmitted via narrowband Internet of things (NB-IoT) over NTNs, especially GEO satellites. The IMS includes well-defined procedures for initiating sessions.

[0045] A primary challenge for voice communication via GEO satellites is the constrained environment, in which only very limited bandwidth (typically around 1kbps) is provided. Another challenge is the long duration for establishing a voice call resulted from long round-trip delay due to the high altitude of GEO satellites. A typical duration for establishing a voice call via GEO satellites may reach 30 seconds or more. A delay of 30 seconds is typically set as the maximum acceptable duration excluding the time for a called party to answer.

[0046] Another important contributor to the long duration for establishing a voice call over GEO satellites aside from the long round-trip delay due to the high altitude of the satellites is the signaling overhead associated with call setup procedures. A standard procedure for voice call initiation may involve multiple signaling messages exchanged between the terminal device 110 and the network entity 130 and many of them are verbose and carry large payloads. For example, an IMS level registration in accordance with current standards may be initiated after the registration to the access network is performed and after IP connectivity for the signaling has been gained from the access network. A session origination (MO) procedure applied to users located in their home network may involve tens of signaling messages exchanged among the functions within the home network of the terminal device 110.

[0047] The disclosure aims to address at least one of the above challenges in supporting voice communications over NTNs, e.g., via GEO satellites which typically are associated with very limited available throughput and the fact that current session initiation protocol (SIP) signaling is quite verbose. The disclosure also aims to minimize changes to the core network by focusing on modifications primarily within the IMS, specifically at the proxy function responsible for session control.

[0048] Embodiments in the disclosure focus on tackling at least one of the above challenges by reducing both the number and the size of the messages exchanged betweenthe terminal device 110 and the network entity 130 during the initial registration stage and the voice communication initialization (or setup) stage.

[0049] Example embodiments will be described in connection with evolved packet core (EPC) as the core network architecture supporting 3GPP access technologies for the purpose of simplified illustration. However, it should be noted that embodiments may also be applied to other 3GPP core networks — 5G / 6G or future developed core network architectures by applying appropriate translation rules to account for the differences of corresponding architectures.

[0050] As discussed above, the primary principle in the disclosure is to reduce both the number and the size of the messages exchanged between the terminal device 110 and the network entity 130 during the initial registration stage and the voice communication setup stage, which minimize the modifications to the core network. Embodiments in the disclosure propose a new signaling protocol over a new proposed interface, which may be referred to as Gm* interface (the signaling over which may be referred to as Gm* interface signaling or IMS container, the actual naming may be different in future adopted standards) between the terminal device 110 and the network entity 130, specifically a proxy-call session control function (P-CSCF).

[0051] First, several terms used in the disclosure are listed below for easy reference, in which:

[0052] PCRF: Policy and Charging Rules Function (used in 4G networks)

[0053] PCF: Policy Control Function (used in 5G networks)

[0054] P-CSCF: Proxy-Call Session Control Function

[0055] I-CSCF: Interrogating-Call Session Control Function

[0056] HSS: Home Subscriber Server

[0057] S-CSCF: Serving-Call Session Control Function

[0058] PGW: Packet Data Network Gateway (used in 4G networks)

[0059] SMF: Session Management Function (used in 5G networks)

[0060] PGW-u: Packet Data Network Gateway - User Plane (used in 4G networks)

[0061] UPF: User Plane Function (used in 5G networks)

[0062] Gm interface: signaling interface between the terminal device and the P-CSCF in the IMS architecture

[0063] Cx interface: signaling interface between the S-CSCF and HSS in the IMS architecture

[0064] Mw interface: internal SIP signaling interface between call session control functions (CSCFs) in the IMS architecture.

[0065] As mentioned above, for the list above, functions involved the EPC may be well translated to corresponding functions in 5G / 6G and future developed core network architectures. For example, the PCRF in 4G may be translated to the PCF in 5G, the serving gateway control plane (SGW-C) / PDN gateway control plane (PGW-C) in 4G may be translated to the SMF in 5G, the PGW-U 4G may be translated to the UPF in 5G, etc. The above list is not a full list rather an example.

[0066] According to the principle in the disclosure, the proposed Gm* interface signaling enables the reduction of both the number and the size of the messages exchanged between the terminal device 110 and the network entity 130. Information associated with the terminal device 110 is provided to and stored by the network entity 130 before the call setup e.g., at a registration phase. Such information may include e.g., a list of codecs supported by the terminal device 110, contact address (e.g., IP address and port) associated with the terminal device 110, and route information associated with the terminal device that is provided by the IMS network, or IP multimedia public identity (IMPU) (IMPU may be stored in a HSS profile of the terminal device 110, and the terminal device 110 may not require transmitting the IMPU when initiating a voice communication), etc. Such information may be later used to populate related SIP headers to transform the Gm* interface signaling messages into standard SIP signaling protocol messages.

[0067] If an IP PDN connection is utilized to carry signaling messages between the terminal device 110 and the network entity 130 in the IMS, the PGW (not shown) may transmit an address of a specific network entity 130 that is optimized (or dedicated) for handling the proposed Gm* interface signaling if it is determined that the access used is NTNs over GEO satellites. The terminal device 110 transmits a REGISTER with additional information (e.g., the support for the proposed Gm* interface signaling) to the network entity 130. The network entity 130 may store the additional information and use the information to populate relevant SIP headers to transform Gm* interfacesignaling protocol message into standard SIP signaling protocol messages. The identity of the terminal device 110 may alternatively retrieved by the network entity 130 from the PCRF / PCF 131 if IP security protocol (IPSec) is not used between the terminal device 110 and the network entity 130. It has to be noted that there are 2 ways to for the terminal device 110 to transmit the REGISTER to the network entity 130: in a first way, the terminal device 110 may send a SIP REGISTER to the network entity 130 where the SIP REGISTER may further contain the extra information, such as a list of codecs supported by the terminal device 110; in the second way, the terminal device 110 may send a Gm* REGISTER to the network entity 130 where the Gm* REGISTER may contain the information listed above, such as a list of codecs supported by the terminal device 110, contact address (e.g., IP address and port) associated with the terminal device 110, and / or IP multimedia public identity (IMPU). In both cases, the network entity 130 does not communicate the terminal device 110 the route information associated with the terminal device 110 that is provided by the IMS network, but stores the information for future use during session establishment or messaging related interactions.

[0068] Upon receiving a REGISTER from the terminal device 110, the network entity 130 may need to get a mapping from the source IP address and port of the uplink IMS signaling to the identity of the terminal device 110. The network entity 130 may store this contact address (which includes the source IP address and port) and use this information to populate the contact address of the terminal device 110 in the SIP REGISTER message further transmitted to the IMS network.

[0069] In either scenario, only a minimum / small set of information that cannot be obtained or derived by the network entity 130 needs to be transmitted from the terminal device 110 to the network entity 130, while the network entity 130 may use information deduced from the REGISTER and deduced during the registration to create standard SIP requests (e.g. a SIP INVITE or SIP MESSAGE request) and standard SIP responses (e.g.200 OK) that are used during session establishment (or messaging transfer) with all necessary data and in accordance with the IMS standards.

[0070] In summary, when initiating a communication (e.g., voice communication or message interaction), the terminal device 110 may only transmit a minimum / small set of information that is necessary to establish a session, using the proposed Gm* interface signaling. The network entity 130 may transform Gm* interface signaling messages intostandard SIP signaling protocol messages for further processing within the IMS network, or with another IMS network. The network entity 130 may further transform standard SIP signaling protocol messages received from the IMS network into Gm* interface signaling messages and transmit to the terminal device 110. When receiving a voice communication using SIP from the IMS network, the network entity 130 may transform standard SIP signaling protocol messages into the Gm* interface signaling messages and transmit to the terminal device 110, and further transform the Gm* interface signaling messages received from the terminal device 110 into the standard SIP signaling protocol messages for further processing within the IMS network, or with another IMS network.

[0071] In short, the network entity 130 functions as a proxy between the terminal device 110 and the IMS core network that transforms the Gm* interface signaling messages into the standard SIP signaling protocol messages and vice versa using information stored in advance. Compared with the standard SIP messages, the proposed Gm* interface signaling messages are smaller in size with only necessary information included, which significantly reduces both the number and the size of signaling messages exchanged. By reducing the amount of information exchanged between the terminal device 110 and the network, the invention enables a more efficient use of network resources, this is particularly important for environments with limited bandwidth, e.g., the NTNs especially GEO / GSO NTN. With reduced signaling exchanges, the proposed Gm* interface signaling also reduces the time required to establish a session, further providing improved user experiences. By reducing the signaling overhead, the network is less prone to congestion and packet loss, this is particularly important in NTN scenarios where signal integrity can be more challenging due to the high latency and fluctuating network conditions.

[0072] Though embodiments in the disclosure will be described with voice communication, other types of communications, e.g., messaging interaction, may also be supported.

[0073] In some embodiments, the terminal device 110 determines, based on information indicative of the capability of a network, support for the establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request. The request is a request of proposed Gm* interface signaling (referred to as Gm* request in the following). In response to a determination that the establishment of the communication is supported, the terminaldevice 110 transmit to the network entity 130 in an IMS, the request for establishing the communication. The first network entity 130 is capable of facilitating the establishment of the communication initiated with the request by creating the SIP request based on the request. The first network entity 130 may be the P-CSCF.

[0074] In some embodiments, the network entity 130 receives a request for establishing a communication. The request comprises a different set of information with respect to a set of information comprised in the SIP request. The request is a request of proposed Gm* interface signaling (Gm* request). The network entity 130 creates the SIP request based on the request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication.

[0075] In some embodiments, the Gm* request may omit at least one of the following types of information:- a via header, which specifies the transport path taken by the request, including protocol and transport method,- a route header, which indicates the service route information,- a max-forward header, which limits the number of hops the request can make through the network, helping prevent infinite loops,- a from-header, which identifies the sender of the request (calling party), including display name and SIP URI,- a call-ID header, which is a unique identifier for the SIP session,- a CSeq header, which is a sequence number to order requests within a dialog, - a contact header, which specifies the URI of the sender where responses should be sent,- a content -type header, which specifies the type of body content,- a content-length header, which indicates the length of the body in the message, - version information, which indicates the version of the session description protocol (SDP),- session origin information, which is the session origin information,- session name information, which is the session name or description, - session time information, which is the start or end times of the session,- codec information, which is the codec supported by the terminal device, or - media type information, which specifies the media type.

[0076] Any, some or all of the information could be omitted in the Gm* request.

[0077] In some embodiments, the Gm* request may include at least one of the following types of information:- a message type, which identifies the SIP method, e.g., if it is a request to establish a SIP session, the SIP method is INVITE,- a called party number, which is the number of the called the party (the callee), - a codec offer, which is a list of audio codecs supported by the terminal device, - a text message to be sent, which includes the text message to be sent,- a port for audio media, which specifies the port where the terminal device is expected to receive audio media, or- an IP multimedia public identity (IMPU) of a user of the terminal device, which includes the IMS user ID of the terminal device 110 that corresponds to the voice call or message to be sent.

[0078] In some embodiments, the terminal device 110 may receive from the network entity 130, a response to the request. The information comprised in the response is different from information comprised in the SIP response. The response is a response of the proposed Gm* interface signaling (referred to as Gm* response in the following).

[0079] In some embodiments, the Gm* response may omit at least one of the following types of information:- a via header, which specifies the transport path for routing the response back, - a route header, which indicates the service route information,- a max-forward header, which limits the number of hops the response can make through the network, helping prevent infinite loops,- a from header, which identifies the sender of the response (calling party), - a to header, which identifies the recipient of the response (called party),- a call-ID header, which is a unique identifier for the SIP session,- a CSeq header, which is a sequence number to order requests within a dialog, - a contact header, which specifies the URI of the recipient where responses to the request should be sent,- a content -type header, which specifies the type of body content,- a content-length header, which indicates the length of the body in the message, - version information, which indicates the version of the SDP,- session origin information, which is the session origin information,- session name information, which is the session name or description,- session time information, which is the start or end times of the session, or - media type information, which specifies the media type.

[0080] Any, some or all of the information could be omitted in the Gm* response.

[0081] In some embodiments, the Gm* response may comprise at least one of the following types of information:- a message type, which indicates the type of the response, e.g., 200 OK as response code indicating a success,- an indication whether the call can be accepted,- a codec answer, which is a list of audio codecs selected by the terminal device in response to the received codec offer, or- a port for audio media, which specifies the port where the terminal device is expected to receive incoming audio media.

[0082] In some embodiments, the network entity 130 may transmit to the terminal device 110, a second request to establish a communication. The second request is transformed by the network entity 110 from a second SIP request. The information comprised in the second request is different of information comprised in the second SIP request. The secondrequest is a request of the proposed Gm* interface signaling (referred to as second Gm* request in the following).

[0083] In some embodiments, the terminal device 110 may receive from the network entity 130, the second Gm* request to establish the communication. The second request is transformed by the network entity 110 from a second SIP request. The information comprised in the second Gm*request is different from information comprised in the second SIP request.

[0084] In some embodiments, the second Gm* request may omit at least one of the following types of information:- a via header, which specifies the transport path taken by the request, including protocol and transport method,- a route header, which indicates the service route information,- a max-forward header, which limits the number of hops the request can make through the network, helping prevent infinite loops,- a to header, which identifies the recipient of the response (called party),- a call-ID header, which is a unique identifier for the SIP session,- a CSeq header, which is a sequence number to order requests within a dialog, - a contact header, which specifies the URI of the sender where responses should be sent,- a content -type header, which specifies the type of body content,- a content-length header, which indicates the length of the body in the message, - version information, which indicates the version of the session description protocol (SDP),- session origin information, which is the session origin information,- session name information, which is the session name or description,- session time information, which is the start or end times of the session, or - media type information, which specifies the media type.

[0085] Any, some or all of the information could be omitted in the second Gm* request.

[0086] In some embodiments, the second Gm* request may comprise at least one of the following types of information:- a message type, which identifies the SIP method, e.g., if it is a request to establish a SIP session, the SIP method is INVITE,- a calling party number, which is the number of the calling the party (the caller), - a text message intended for the user of the terminal device,- a codec offer, which is a list of audio codecs supported by the terminal device, or - a contact information for audio media, which specifies the port where the terminal device is expected to receive audio media.

[0087] In some embodiments, the terminal device 110 may transmit to the network entity 130, a second response in response to receiving the second request. The second response is transformed by the network entity to a second SIP response before passing to at least one other network entity in the IMS. The information comprised in the second response is different from the information comprised in the second SIP response. The second response is a Gm* response of the proposed Gm* interface signaling (referred to as second Gm* response in the following).

[0088] In some embodiments, the network entity 130 may receive from the terminal device 110, the second Gm* response to the second Gm* request. The second Gm* response is transformed by the network entity 130 to the second SIP response before passing to at least one other network entity in the IMS. The information comprised in the second Gm* response is different from information comprised in the second SIP response.

[0089] In some embodiments, the second Gm* response may omit at least one of the following types of information:- a via header, which specifies the transport path for routing the response back, - a max-forward header, which limits the number of hops the response can make through the network, helping prevent infinite loops,- a from header, which identifies the sender of the response (calling party), - a to header, which identifies the recipient of the response (called party),- a call-ID header, which is a unique identifier for the SIP session,- a CSeq header, which is a sequence number to order requests within a dialog, - a contact header, which specifies the URI of the recipient where responses to the request should be sent,- a content -type header, which specifies the type of body content,- a content-length header, which indicates the length of the body in the message, - version information, which indicates the version of the SDP,- session origin information, which is the session origin information,- session name information, which is the session name or description,- session time information, which is the start or end times of the session, or - media type information, which specifies the media type.

[0090] Any, some or all of the information could be omitted in the second Gm* response.

[0091] In some embodiments, the second Gm* response may comprise at least one of the following types of information:- a message type, which indicates the type of the response, e.g., 200 OK as response code indicating a success,- an indication whether the call can be accepted,- a codec answer, which is a list of audio codecs selected by the terminal device in response to the received codec offer, or- a port for audio media, which specifies the port where the terminal device is expected to receive incoming audio media.

[0092] In some embodiments, the terminal device 110 may transmit to a second network entity (e.g., a PGW or a P-CSCF), a third request comprising information indicative of support for the establishment of the communication using the request. The request is a request of proposed Gm* interface signaling. The information indicative of the support ensures the network is aware of the capability of the terminal device 100 of supporting the proposed Gm* interface signaling. The transmission of this information also enablesthe network entity to handle the processing of such request responsive to receiving the Gm* request to establish the voice communication.

[0093] In some embodiments, the terminal device 110 may receive information indicative of a contact address of the network entity 130 from the second network entity (e.g. a PGW or a P-CSCF) (not shown). The network entity 130 is capable of facilitating the establishment of the communication initiated with a Gm* request by creating the SIP request based on the Gm* request.

[0094] In some embodiments, the information indicative of the contact address of the network entity 130 is received from the second network entity as part of data connection establishment to support access to the IMS.

[0095] In some embodiments, the information indicative of the contact address of the network entity 130 is received from the second network entity as part of an IMS registration and the second network entity acts as the network entity 130.

[0096] In the following, detailed example signaling processes will be described with reference to FIG. 2 and 3. Referring now to FIG. 2, which illustrates an example signaling process 200 in accordance with some embodiments in the disclosure. The example signaling process 200 illustrates a registration process in accordance with some embodiments in the disclosure. The registration process may be initiated by a SIP REGISTER or a Gm* REGISTER.

[0097] The terminal device 110 (e.g., an NB-IoT UE) may communicate, via any 3GPP access network, to the network of e.g., a constrained NTN environment. The registration process may be initiated by the terminal device 110 establishing 201 a packet data network (PDN) connection with the network. The terminal device 110 may receive information (e.g., an IP address and corresponding port) of the P-CSCF 132 from the network. The information of the P-CSCF 132 may be provided, e.g., via dynamic host configuration protocol (DHCP), protocol configuration options ((e)PCO) or any other appropriate manner. In the context of an NTN GEO satellite, one or more specific P-CSCF 132 may be provided by the PGW. A P-CSCF that is optimized for the constrained NTN environment may be selected as the P-CSCF 132.

[0098] Next, the terminal device 110 transmits the SIP REGISTER message to the P-CSCF 132 to register with the IMS, in which the terminal device 110 indicates itscapability of supporting the Gm* interface signaling proposed in the disclosure. The Gm* interface signaling may refer to a signaling protocol over the proposed Gm* interface that enables an optimized signaling exchange between the terminal device 110 and the P-CSCF 132 for the low-bandwidth GEO link. The terminal device 110 may also transmit in the SIP REGISTER message a list of its supported codecs.

[0099] In response, the P-CSCF 132 transmits information indicative of a signaling entity designated for handling Gm* interface signaling messages (e.g., IP address and corresponding port) to the terminal device 110. The terminal device 110 may transmit Gm* interface signaling messages to the signaling entity after. The signaling entity designated for handling Gm* interface signaling messages may be the P-CSCF 132.

[0100] As an alternative the IMS registration from the terminal device 110 to the network may directly use Gm* REGISTER. In that case, the terminal device 110 may establish 201 a packet data network (PDN) connection with the network indicating support of Gm* interface signaling, e.g. in NAS SM Protocol Configuration Option ((e)PCO). In the context of a NTN GEO satellite, information about one or more specific P-CSCF 132 may be provided by the PGW. The terminal device 110 may receive information (e.g., an IP address and corresponding port) of the P-CSCF 132 from the network. The information of the P-CSCF 132 may be provided, e.g., via dynamic host configuration protocol (DHCP), protocol configuration options ((e)PCO) or any other appropriate manner and may be associated with an indication that the P-CSCF 132 supports the proposed Gm* interface signaling. A P-CSCF that is optimized for the constrained NTN environment may be selected as the P-CSCF 132. Next, the terminal device 110 transmits the Gm* REGISTER message to the P-CSCF 132 to register with the IMS, including at least its contact address. The terminal device 110 may also transmit in the Gm* REGISTER message a list of its supported codecs. The P-CSCF 132, upon receiving the Gm* REGISTER message, may process this message by interacting with the S-CSCF 134 (e.g., sending 211 a SIP REGISTER message to the S-CSCF 134) and the S-CSCF 134 interacts with the HSS 133 (e.g., interaction 212 between the HSS 133 and the CSCF 134 over Cx interface) to get subscription data associated with the IMPU registered by the terminal device 110. The S-CSCF 134 may respond with a SIP 200 OK 213 to the P-CSCF 132.

[0101] In scenarios where IMS-level authentication is not enforced, e.g., the verification of the identity of the terminal device 110 using credentials is not required, the P-CSCF 132 retrieves in step 203 a public identifier associated with the IP address of the terminaldevice 110, e.g., from the PCRF / PCF 131. The public identifier may be a mobile station international subscriber directory number (MSISDN), a generic public subscription identifier (GPSI) or any other appropriate public identifier. In some embodiments, each terminal device 110 may be allocated with a dedicated IP address and in some other embodiments, a plurality of terminal devices 110 may share an IP address but use different ports to differentiate from each other. If the terminal device 110 is allocated with a dedicated IP address, the PCRF / PCF 131 may retrieve the subscription permanent identifier (SUPI) and the MSISDN via a session binding process which links the IP address of the terminal device 110 to its identity (similar binding process may be performed by PCRF 131 using corresponding messages). If the terminal device 110 shares the same IP address with other terminal devices and is identified with an unique port number, which often is the case for NTN, the PCRF / PCF 131 may interrogate the UPF, via e.g., Nupf GetUEPrivatelPaddrAndldentifiers Get, including the IP address and port of the terminal device 110 and optionally the IP domain to receive the SUPI or GPSI from the UPF. This process allows the PCRF / PCF 131 to identify the terminal device 110. The GPSI of the terminal device 110 may be mapped by the P-CSCF 132 onto the IMPU being registered while the SUPI of the terminal device 110 may be mapped to the IMPI

[0102] The P-CSCF 132, upon receiving the SIP REGISTER message, may process this message by interacting with the S-CSCF 134 (e.g., forwarding 211 the SIP REGISTER message to the S-CSCF 134) and the S-CSCF 134 interacting with the HSS 133 (e.g., interaction 212 between the HSS 133 and the CSCF 134 over Cx interface) to get subscription data associated with the IMPU registered by the terminal device 110. The S-CSCF 134 may respond with a SIP 200 OK 213 to the P-CSCF 132. If the Gm* REGISTER is received by the P-CSCF 132, the Gm* REGISTER may be first transformed by the P-CSCF 132 before interacting with the S-CSCF 134.

[0103] In response to receiving a REGISTER 200 OK response 213, the P-CSCF 132 may store the route information (e.g., service-route header). The route information may contain the path to the S-CSCF 134 for future IMS signaling. The P-CSCF 132 further replaces the service-route information received from the S-CSCF 134 with its own information (e.g., IP address and port) and transmits a Gm* REGISTER 200 OK* response 204 to the terminal device 110 including its own information for future Gm* interface signaling. The Gm* REGISTER 200 OK* response include a minimum / small set ofinformation as discussed in the above. In the case of figure 2’ the P-CSCF 132 transmits a Gm* REGISTER 200 OK* response 204 to the terminal device 110.

[0104] After the completion of the registration, the terminal device 110 may only transmit necessary information using the Gm* interface signaling to establish a session. The network may use information deduced from the REGISTER and deduced during the registration to create SIP requests (e.g., a SIP INVITE) and SIP responses (e.g., 200 OK) that are used during session establishment with all necessary information and in accordance with current standards. This may be applied to the mobile-originated (MO) call setup which will be described with reference to FIG. 3 in below. For the mobile-terminated (MT) call setup, the network (e.g., the P-CSCF 132) may transform the received SIP signaling that complies the current standards into signaling complies the proposed Gm* interface signaling protocol which will be described later.

[0105] Referring now to FIG. 3, which illustrates an example signaling process 300 in accordance with some embodiments in the disclosure. The example signaling process 300 illustrates a scenario of MO call setup in accordance with some embodiments in the disclosure in which the terminal device 110 is the originating party of a voice call.

[0106] The terminal device 110 may initiate, as the originating party, a voice call by transmitting a Gm* interface signaling message INVITE* 301 that complies the proposed Gm* interface signaling protocol to the network, e.g., using the IP address and port of the P-CSCF 132 that have been provided to the terminal device 110 in the REGISTER 200 OK message 204 or as part of PDN connection establishment 201 . In some embodiments, the Gm* interface signaling message INVITE* 301 may include necessary information including:

[0107] message type = INVITE: different from regular SIP where the INVITE is a textbased sequence of characters, the message type may be encoded (shortened) as a single byte that represents the sequence to reduce the overhead,

[0108] request-unified resource identifier (R-URI) with the dialed number: which may include the number of the called party,

[0109] codec offer: which may be a list of audio codecs supported by the terminal device 110. If such information has been provided during the SIP registration, codec offer may be removed from the message,

[0110] port for audio media: which may specify the port where the terminal device 110 is expected to receive audio media,

[0111] (optionally) IP multimedia public identity (IMPU): which may include the IMS user ID of the terminal device 110 that corresponds to the voice call.

[0112] In some embodiments, the Gm* interface signaling message INVITE* 301 may be transmitted as an IP packet over the signaling data bearer of the IMS PDN connection which is the IP connection established for IMS signaling. The P-CSCF 132 may query the PCRF / PCF 131 to retrieve the MSISDN associated with the IP address of the terminal device 110, if the terminal device is allocated with a dedicated IP address. If the terminal device 110 shares the same IP address with other terminal devices and is identified with a unique port number, the port number may also be included to uniquely identify the terminal device 110. In some embodiments, to avoid the overhead of IP security protocol (IPSec) between the terminal device 110 and the P-CSCF 132, a secure connection between the PGW-u (4G) or UPF (5G) and the P-CSCF 132 may be assumed, in which security mechanisms defined for general packet radio service (GPRS) IMS-bundled authentication (GIB A) may be used to leverage the authentication of the core network to secure IMS access.

[0113] The P-CSCF 132, upon receiving the Gm* interface signaling message INVITE* 301, transforms the Gm* interface signaling message INVITE* 301 into a standard SIP message - SIP INVITE 302 and forwards it to the IMS core via e.g., the Mw interface. During the transformation, the P-CSCF 132 may:

[0114] a) add the MSISDN received from the PCRF / PCF 131 into relevant standard SIP headers, such as FROM or P-Asserted-Identity if the terminal device 110 provides no IMPU. If the terminal device 110 has provided an IMPU in the Gm* interface signaling message INVITE*, the P-CSCF 132 may validate whether the IMPU corresponds to the subscription associated with the IP address and port of the terminal device 110 in the core network,

[0115] b) create relevant standard SIP headers including Call ID and CSeq,

[0116] c) add the route information (e.g., route header) based on service-route header that was stored during the SIP registration process,

[0117] d) create a session description protocol (SDP) message based on the information received in the Gm* interface signaling message including the codec offer, the port for audio media, etc.

[0118] After transforming the Gm* interface signaling message INVITE* 301 to the standard SIP message SIP INVITE 302, standard SIP signaling messages 303, 304, and 305 may be exchanged within the IMS network, e.g., among the P-CSCF 132, the S-CSCF 134, and other IMS elements (not shown). Standard SIP signaling may also be exchanged with other IMS networks if the called party is in a different IMS network. This may follow the current standards.

[0119] In response to receiving the SIP response (e.g., 200 OK message or other response message indicating the call setup status) from the IMS core network via e.g., Mw interface, the P-CSCF 132 may transform the SIP response back into a Gm* interface signaling message 200 OK*, which contains the necessary information needed by the terminal device 110. The information may include the address of the IMS access gateway (AGW) that handles the media path for the voice call. The P-CSCF 132 transmits the Gm* interface signaling message to the terminal device 110 as the response for the call setup initiated by the terminal device 110.

[0120] With the proposed Gm* interface signaling, the signaling exchange between the terminal device and the network is reduced to only include the necessary information that the network cannot obtain or derive when the terminal device is the originating party of the voice call. The signaling overhead is significantly reduced in terms of both message size and the number of messages exchanged to adapt to the constrained environment, e.g. NTNs over GEO satellites.

[0121] Now a scenario of MT call setup in accordance with some embodiments in the disclosure in which the terminal device 110 is the terminating party (recipient) of a voice call will be described. As discussed above, for MT call setup, the network (e.g., the P-CSCF 132) may translate the received SIP signaling that complies the current standards into signaling complies the proposed Gm* interface signaling protocol.

[0122] The MT call setup procedure may follow the IMS registration and MO call setup procedure described earlier. The terminal device 110 may establish a PDN connection in the registration phase to register with the IMS via a SIP REGISTER message and receive the IP address and port of the P-CSCF 132 for Gm* interface signaling. For the MO callsetup procedure, the terminal device 110, as the originating party, may transmit the Gm* interface signaling message INVITE* to initiate a voice call, and the P-CSCF 132 may transform the Gm* interface signaling message into a standard SIP INVITE for the IMS call and optimize the response sent back to the terminal device 110. The MT call setup procedure addresses the reverse scenario in which a call is initiated toward the terminal device 110 from the network.

[0123] The P-CSCF 132 may receive a standard SIP INVITE from the IMS core network intended for the terminal device 110 that has previously registered with the IMS network. The P-CSCF 132 may transform the standard SIP INVITE into a Gm* interface signaling message INVITE* and transmit it to the terminal device 110 e.g., via the registered IP address (and port) of the terminal device 110. The P-CSCF 132 may transform the standard SIP INVITE into the Gm* interface signaling message INVITE* including:

[0124] message type = INVITE: the text-based sequence of characters for the message type in the standard SIP INVITE may be encoded as a single byte that represents the sequence,

[0125] calling party number: which may include the number of the calling party initiating the session,

[0126] codec offer: which may be a list of audio codecs supported by the calling party or defined by the IMS core,

[0127] IP address and port for audio media: which may be the IP address and port the IMS network expects to receive the audio media from the terminal device.

[0128] In some embodiments, the Gm* interface signaling message INVITE* may be transmitted as an IP packet over the signaling data bearer of the IMS PDN connection which is the IP connection established for IMS signaling. The P-CSCF 132 may associate the IP packet with an appropriate differentiated services code point (DSCP) value to support paging policy differentiation. Additionally, the P-CSCF 132 may store relevant information received from the IMS core network, including SIP session identifier (Call ID), sequence number (CSeq), route information, etc. for correlating and constructing a SIP response in a later phase.

[0129] Upon receiving the Gm* interface signaling message INVITE*, the terminal device 110 may process the message and respond with a Gm* interface signaling message 200 OK* which may include:

[0130] message type = 200 OK: which may indicate a successful acceptance of the call,

[0131] codec answer: which may include the codecs selected by the terminal device 110 in response to the received codec offer,

[0132] port for audio media: which may be the port where the terminal device 110 expects to receive incoming audio media.

[0133] In response to receiving the Gm* interface signaling message 200 OK*, the P-CSCF 132 may transform the Gm* interface signaling message 200 OK* into a standard SIP message 200 OK and transmit it to the IMS core via e.g., the Mw interface. During the transformation, the P-CSCF 132 may:

[0134] a) add the Call ID and CSeq previously stored,

[0135] b) add the route information (e.g., service-route header) previously stored,

[0136] c) create a session description protocol (SDP) message based on the information received in the Gm* interface signaling message including the codec answer, the port for audio media, etc.

[0137] After transforming the Gm* interface signaling message 200 OK* to the standard SIP message 200 OK, standard SIP signaling messages may be exchanged within the IMS network, e.g., among the P-CSCF 132, the S-CSCF 134, and other IMS elements (not shown). Standard SIP signaling may also be exchanged with other IMS networks if the calling party is in a different IMS network. This may follow the current standards.

[0138] It should be noted that though the description of example embodiments are with reference to voice communication establishment, similar mechanisms may also be adopted in SIP messaging where Gm* interface signaling may be used for messaging interactions (which contain text messages to be exchanged). In this case, there is no need to include codec information and the P-CSCF 132 may translate between Gm* interface signaling messages and standard SIP messages. For example, to establish a messaging interaction communication, the P-CSCF 132 may translate a Gm* request into a standard SIP message to be exchanged within the rest of the IMS network or with another IMS network.

[0139] With the proposed Gm* interface signaling, the signaling exchange between the terminal device and the network is reduced to only include the necessary information that the network cannot obtain or derive when the terminal device is the terminating party of the voice call. The signaling overhead is significantly reduced in terms of both message size and the number of messages exchanged to adapt to the constrained environment, e.g. NTNs over GEO satellites.

[0140] FIG. 4 shows a flowchart of an example method 400 implemented at an apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 400 will be described from the perspective of the terminal device 110 in FIG. 1.

[0141] At block 410, determining, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request.

[0142] At block 420, transmitting, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request. This enables the apparatus to establish a communication with information reducing the signaling overhead exchanged between the apparatus and the first network entity.

[0143] In some example embodiments, the request does not comprise at least one of a via header, a route header, a max-forward header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, codec information, or media type information. By not including at least one type of the listed information when establishing the communication, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0144] In some example embodiments, the request comprises at least one of a message type, a called party number, a codec offer, a port for audio media, a text message to be sent, or an IP multimedia public entity (IMPU) of a user of the apparatus. By including only at least one type of information listed in the small set when establishing the communication, signaling overhead exchanged between the apparatus and the firstnetwork entity is reduced.

[0145] In some example embodiments, the method 400 further comprises: receiving, from the first network entity, a response to the request, wherein information comprised in the response is different from information comprised in a SIP response. This reduces the signaling overhead exchanged between the apparatus and the first network entity.

[0146] In some example embodiments, the response does not comprise at least one of a via header, a route header, a max-forward header, a to header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information. By not including at least one type of the listed information, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0147] In some example embodiments, the response comprises at least one of a message type, an indication whether the call can be accepted, a codec answer, or a port for audio media. By including only at least one type of information listed in the small set, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0148] In some example embodiments, the method 400 further comprises: receiving, from the first network entity, a second request to establish a communication, wherein the second request is transformed from a second SIP request by the first network entity and information comprised in the second request is different of information comprised in the second SIP request. This reduces the signaling overhead exchanged between the apparatus and the first network entity when receiving a request from the network.

[0149] In some example embodiments, the second request does not comprise at least one of: a via header, a route header, a max-forward header, a to header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information. By not including at least one type of the listed information, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0150] In some example embodiments, the second request comprises at least one of: a message type, a calling party number, a text message intended for the user of the apparatus,a codec offer, or contact information for audio media. By including only at least one type of information listed in the small set, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0151] In some example embodiments, the method 400 further comprises: transmitting, to the first network entity, a second response in response to receiving the second request, wherein the second response is transformed by the first network entity to a second SIP response before passing to at least one other network entity in the IMS and information comprised in the second response is different from information comprised in the second SIP response. This reduces the signaling overhead exchanged between the apparatus and the first network entity when transmitting a response to the network.

[0152] In some example embodiments, the second response does not comprise at least one of a via header, a max-forward header, a to header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information. By not including at least one type of the listed information, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0153] In some example embodiments, the second response comprises at least one of a message type, an indication whether the call can be accepted, a codec answer, or a port for audio media. By including only at least one type of information listed in the small set, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0154] In some example embodiments, the method 400 further comprises: transmitting, to a second network entity, a third request comprising information indicative of support for the establishment of the communication using the request; receiving, from the second network entity, a response to the third request indicating that the network supports the establishment of the communication initiated with the request by creating the SIP request based on the request. This ensures the network is aware of the capability of the apparatus of supporting the establishment of the communication with reduced overhead.

[0155] In some example embodiments, the method 400 further comprises: receiving, from the second network entity, information indicative of a contact address of the first network entity being capable of facilitating the establishment of the communicationinitiated with the request by creating the SIP request based on the request. This enables the apparatus to be aware of the signaling endpoint capable of handling the establishment of the communication with reduced overhead.

[0156] In some example embodiments, the information indicative of the contact address of the first network entity is received from the second network entity as part of data connection establishment to support access to the IMS. This enables the apparatus to be aware of the signaling endpoint capable of handling the establishment of the communication with reduced overhead.

[0157] In some example embodiments, the information indicative of the contact address of the first network entity is received from the second network entity as part of an IMS registration and the second network entity acts as the first network entity. This enables the apparatus to be aware of the signaling endpoint capable of handling the establishment of the communication with reduced overhead.

[0158] In some example embodiments, the communication is a voice call or a messaging interaction. This enables the support for different types of communications.

[0159] FIG. 5 shows a flowchart of an example method 500 implemented at a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 500 will be described from the perspective of the network entity 130 in FIG.1.

[0160] At block 510, receiving, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request.

[0161] At block 520, creating, based on the request, a SIP request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication. This enables the apparatus to establish a communication with information reducing the signaling overhead exchanged between the apparatus and the first network entity.

[0162] In some example embodiments, the request does not comprise at least one of a via header, a route header, a max-forward header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, versioninformation, session origin information, session name information, session time information, codec information, or media type information. By not including at least one type of the listed information when establishing a communication, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0163] In some example embodiments, the request comprises at least one of: a message type, a called party number, a codec offer, a port for audio media, a text message to be sent, or an IP multimedia public entity (IMPU) of a user of the apparatus. By including only at least one type of information listed in the small set when establishing a communication, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0164] In some example embodiments, the first network entity is caused to: transmitting, to the apparatus, a response to the request, wherein the response is transformed by the first network entity from a SIP response and information comprised in the response is different from information comprised in the SIP response. This reduces the signaling overhead exchanged between the apparatus and the first network entity when receiving a request from the network.

[0165] In some example embodiments, the response does not comprise at least one of: a via header, a route header, a max-forward header, a to header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information. By not including at least one type of the listed information, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0166] In some example embodiments, the response comprises at least one of: a message type, an indication whether the call can be accepted, a codec answer, or a port for audio media. By including only at least one type of information listed in the small set, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0167] In some example embodiments, the first network entity is caused to: transmitting, to the apparatus, a second request to establish a communication, wherein the second request is transformed by the first network entity from a second SIP request and information comprised in the second request is different of information comprised in the second SIP request. This reduces the signaling overhead exchanged between the apparatusand the first network entity when receiving a request from the network.

[0168] In some example embodiments, the second request does not comprise at least one of: a via header, a route header, a max-forward header, a to header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information. By not including at least one type of the listed information, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0169] In some example embodiments, the second request comprises at least one of a message type, a calling party number, a text message intended for the user of the apparatus, a codec offer, or contact information for audio media. By including only at least one type of information listed in the small set, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0170] In some example embodiments, the first network entity is caused to: receiving, from the apparatus, a second response to the second request, wherein the second response is transformed by the first network entity to a second SIP response before passing to at least one other network entity in the IMS and information comprised in the second response is different from information comprised in the second SIP response. This reduces the signaling overhead exchanged between the apparatus and the first network entity when transmitting a response to the network.

[0171] In some example embodiments, the second response does not comprise at least one of: a via header, a max-forward header, a to header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information. By not including at least one type of the listed information, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0172] In some example embodiments, the second response comprises at least one of: a message type, an indication whether the call can be accepted, a codec answer, or a port for audio media. By including only at least one type of information listed in the small set, signaling overhead exchanged between the apparatus and the first network entity is reduced.

[0173] In some example embodiments, the communication is a voice call or a messaging interaction. This enables the support for different types of communications.

[0174] In some example embodiments, an apparatus capable of performing any of the method 400 (for example, the terminal device 110 in FIG. 1) may comprise means for performing the respective operations of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The apparatus may be implemented as or included in the terminal device 110 in FIG. 1.

[0175] In some example embodiments, the apparatus comprises means for determining, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and means for transmitting, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request.

[0176] In some example embodiments, the request does not comprise at least one of a via header, a route header, a max-forward header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, codec information, or media type information.

[0177] In some example embodiments, the request comprises at least one of a message type, a called party number, a codec offer, a port for audio media, a text message to be sent, or an IP multimedia public entity (IMPU) of a user of the apparatus.

[0178] In some example embodiments, the apparatus further comprises: means for receiving, from the first network entity, a response to the request, wherein information comprised in the response is different from information comprised in a SIP response.

[0179] In some example embodiments, the response does not comprise at least one of a via header, a route header, a max-forward header, a to header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header,version information, session origin information, session name information, session time information, or media type information.

[0180] In some example embodiments, the response comprises at least one of: a message type, an indication whether the call can be accepted, a codec answer, or a port for audio media.

[0181] In some example embodiments, the apparatus further comprises: means for receiving, from the first network entity, a second request to establish a communication, wherein the second request is transformed from a second SIP request by the first network entity and information comprised in the second request is different of information comprised in the second SIP request.

[0182] In some example embodiments, the second request does not comprise at least one of: a via header, a route header, a max-forward header, a to header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information.

[0183] In some example embodiments, the second request comprises at least one of: a message type, a calling party number, a text message intended for the user of the apparatus, a codec offer, or contact information for audio media.

[0184] In some example embodiments, the apparatus further comprises: means for transmitting, to the first network entity, a second response in response to receiving the second request, wherein the second response is transformed by the first network entity to a second SIP response before passing to at least one other network entity in the IMS and information comprised in the second response is different from information comprised in the second SIP response.

[0185] In some example embodiments, the second response does not comprise at least one of: a via header, a max-forward header, a to-header, a from-header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information.

[0186] In some example embodiments, the second response comprises at least one of: a message type, an indication whether the call can be accepted, a codec answer, or a portfor audio media.

[0187] In some example embodiments, the apparatus further comprises: means for transmitting, to a second network entity, a third request comprising information indicative of support for the establishment of the communication using the request; means for receiving, from the second network entity, a response to the third request indicating that the network supports the establishment of the communication initiated with the request by creating the SIP request based on the request.

[0188] In some example embodiments, the apparatus further comprises: means for receiving, from the second network entity, information indicative of a contact address of the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating the SIP request based on the request.

[0189] In some example embodiments, the information indicative of the contact address of the first network entity is received from the second network entity as part of data connection establishment to support access to the IMS.

[0190] In some example embodiments, the information indicative of the contact address of the first network entity is received from the second network entity as part of an IMS registration and the second network entity acts as the first network entity.

[0191] In some example embodiments, the communication is a voice call or a messaging interaction.

[0192] In some example embodiments, a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) capable of performing any of the method 500 (for example, the network entity 130 in FIG. 1) may comprise means for performing the respective operations of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first network entity in an Internet protocol (IP) multimedia subsystem (IMS) may be implemented as or included in the network entity 130 in FIG. 1.

[0193] In some example embodiments, the first network entity in an Internet protocol (IP) multimedia subsystem (IMS) comprises means for receiving, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request; and means for creating, based on the request, a SIP request to be exchanged with at least one othernetwork entity in the IMS to facilitate the establishment of the communication.

[0194] In some example embodiments, the request does not comprise at least one of: a via header, a route header, a max-forward header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, codec information, or media type information.

[0195] In some example embodiments, the request comprises at least one of: a message type, a called party number, a codec offer, a port for audio media, a text message to be sent, or an IP multimedia public entity (IMPU) of a user of the apparatus.

[0196] In some example embodiments, the first network entity is caused to: means for transmitting, to the apparatus, a response to the request, wherein the response is transformed by the first network entity from a SIP response and information comprised in the response is different from information comprised in the SIP response.

[0197] In some example embodiments, the response does not comprise at least one of: a via header, a route header, a max-forward header, a to header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information.

[0198] In some example embodiments, the response comprises at least one of: a message type, an indication whether the call can be accepted, a codec answer, or a port for audio media.

[0199] In some example embodiments, the first network entity is caused to: means for transmitting, to the apparatus, a second request to establish a communication, wherein the second request is transformed by the first network entity from a second SIP request and information comprised in the second request is different of information comprised in the second SIP request.

[0200] In some example embodiments, the second request does not comprise at least one of: a via header, a route header, a max-forward header, a to header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information.

[0201] In some example embodiments, the second request comprises at least one of: a message type, a calling party number, a text message intended for the user of the apparatus, a codec offer, or contact information for audio media.

[0202] In some example embodiments, the first network entity is caused to: means for receiving, from the apparatus, a second response to the second request, wherein the second response is transformed by the first network entity to a second SIP response before passing to at least one other network entity in the IMS and information comprised in the second response is different from information comprised in the second SIP response.

[0203] In some example embodiments, the second response does not comprise at least one of: a via header, a max-forward header, a to header, a from header, a call-ID header, a CSeq header, a contact header, a content-type header, a content-length header, version information, session origin information, session name information, session time information, or media type information.

[0204] In some example embodiments, the second response comprises at least one of: a message type, an indication whether the call can be accepted, a codec answer, or a port for audio media.

[0205] In some example embodiments, the communication is a voice call or a messaging interaction

[0206] FIG. 6 is a simplified block diagram of a device 600 that is suitable for implementing example embodiments of the present disclosure. The device 600 may be provided to implement a communication device, for example, the terminal device 110 or the network entity 130 as shown in FIG. 1. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more communication modules 640 coupled to the processor 610.

[0207] The communication module 640 is for bidirectional communications. The communication module 640 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 640 may include at least one antenna.

[0208] The processor 610 may be of any type suitable to the local technical network andmay include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 600 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0209] The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 624, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 622 and other volatile memories that will not last in the power-down duration.

[0210] A computer program 630 includes computer executable instructions that are executed by the associated processor 610. The instructions of the program 630 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 630 may be stored in the memory, e.g., the ROM 624. The processor 610 may perform any suitable actions and processing by loading the program 630 into the RAM 622.

[0211] The example embodiments of the present disclosure may be implemented by means of the program 630 so that the device 600 may perform any process of the disclosure as discussed with reference to FIGs. 2 to 5. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0212] In some example embodiments, the program 630 may be tangibly contained in a computer readable medium which may be included in the device 600 (such as in the memory 620) or other storage devices that are accessible by the device 600. The device 600 may load the program 630 from the computer readable medium to the RAM 622 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. 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).

[0213] FIG. 7 shows an example of the computer readable medium 700 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 700 has the program 630 stored thereon.

[0214] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method 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.

[0215] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computerexecutable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0216] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0217] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[0218] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0219] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.

[0220] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

44WHAT IS CLAIMED IS:

1. An apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:determine, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and transmit, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request.

2. The apparatus of claim 1, wherein the request does not comprise at least one of: a via header,a route header,a max-forward header,a from header,a call-ID header,a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information,codec information, ormedia type information.

3. The apparatus of any of claims 1 to 2, wherein the request comprises at least45one of:a message type,a called party number,a codec offer,a port for audio media,a text message to be sent, oran IP multimedia public entity (IMPU) of a user of the apparatus.

4. The apparatus of any of claims 1 to 3, wherein the apparatus is caused to: receive, from the first network entity, a response to the request, wherein the information comprised in the response is different from the information comprised in a SIP response.

5. The apparatus of any of claims 1 to 4, wherein the response does not comprise at least one of:a via header,a route header,a max-forward header,a to header,a from header,a call-ID header,a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information, ormedia type information.

6. The apparatus of any of claims 1 to 5, wherein the response comprises at least one of:a message type,46an indication whether the call can be accepted,a codec answer, ora port for audio media.

7. The apparatus of claim 1, wherein the apparatus is caused to:receive, from the first network entity, a second request to establish a communication, wherein the second request is transformed from a second SIP request by the first network entity and information comprised in the second request is different of information comprised in the second SIP request.

8. The apparatus of claim 7, wherein the second request does not comprise at least one ofa via header,a route header,a max-forward header,a to header,a call-ID header,a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information, ormedia type information.

9. The apparatus of any of claims 7 to 8, wherein the second request comprises at least one ofa message type,a calling party number,a text message intended for the user of the apparatus,a codec offer, orcontact information for audio media.

10. The apparatus of any of claims 7 to 9, wherein the apparatus is caused to: transmit, to the first network entity, a second response in response to receiving the second request, wherein the second response is transformed by the first network entity to a second SIP response before passing to at least one other network entity in the IMS and information comprised in the second response is different from information comprised in the second SIP response.

11. The apparatus of any of claims 7 to 10, wherein the second response does not comprise at least one of:a via header,a max-forward header,a to header,a from header,a call-ID header,a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information, ormedia type information.

12. The apparatus of any of claims 7 to 11, wherein the second response comprises at least one of:a message type,an indication whether the call can be accepted,a codec answer, ora port for audio media.

13. The apparatus of any of claims 1 to 12, wherein the apparatus is caused to: transmit, to a second network entity, a third request comprising informationindicative of support for the establishment of the communication using the request; receive, from the second network entity, a response to the third request indicating that the network supports the establishment of the communication initiated with the request by creating the SIP request based on the request.

14. The apparatus of claim 13, wherein the apparatus is caused to:receive, from the second network entity, information indicative of a contact address of the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating the SIP request based on the request.

15. The apparatus of claim 14, wherein the information indicative of the contact address of the first network entity is received from the second network entity as part of data connection establishment to support access to the IMS.

16. The apparatus of claim 14, wherein the information indicative of the contact address of the first network entity is received from the second network entity as part of an IMS registration and the second network entity acts as the first network entity.

17. The apparatus of any of claims 1 to 16, wherein the communication is a voice call or a messaging interaction.

18. A first network entity in an Internet protocol (IP) multimedia subsystem (IMS) comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the network entity at least to:receive, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request; andcreate, based on the request, a SIP request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication.

19. The first network entity of claim 18, wherein the request does not comprise at least one of:49a via header,a route header,a max-forward header,a from header,a call-ID header,a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information,codec information, ormedia type information.

20. The first network entity of any of claims 18 to 19, wherein the request comprises at least one of:a message type,a called party number,a codec offer,a port for audio media,a text message to be sent, oran IP multimedia public entity (IMPU) of a user of the apparatus.

21. The first network entity of any of claims 18 to 20, wherein the first network entity is caused to:transmit, to the apparatus, a response to the request, wherein the response is transformed by the first network entity from a SIP response and information comprised in the response is different from the information comprised in the SIP response.

22. The first network entity of any of claims 18 to 21, wherein the response does not comprise at least one of:a via header,50a route header,a max-forward header,a to header,a from header,a call-ID header,a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information, ormedia type information.

23. The first network entity of any of claims 18 to 22, wherein the response comprises at least one of:a message type,an indication whether the call can be accepted,a codec answer, ora port for audio media.

24. The first network entity of claim 18, wherein the first network entity is caused to:transmit, to the apparatus, a second request to establish a communication, wherein the second request is transformed by the first network entity from a second SIP request and information comprised in the second request is different of information comprised in the second SIP request.

25. The first network entity of claim 24, wherein the second request does not comprise at least one of:a via header,a route header,a max-forward header,51a to header,a call-ID header,a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information, ormedia type information.

26. The first network entity of any of claims 24 to 25, wherein the second request comprises at least one of:a message type,a calling party number,a text message intended for the user of the apparatus,a codec offer, orcontact information for audio media.

27. The first network entity of any of claims 24 to 26, wherein the first network entity is caused to:receive, from the apparatus, a second response to the second request, wherein the second response is transformed by the first network entity to a second SIP response before passing to at least one other network entity in the IMS and information comprised in the second response is different from information comprised in the second SIP response.

28. The first network entity of any of claims 24 to 27, wherein the second response does not comprise at least one of:a via header,a max-forward header,a to header,a from header,a call-ID header,52a CSeq header,a contact header,a content-type header,a content-length header,version information,session origin information,session name information,session time information, ormedia type information.

29. The first network entity of any of claims 24 to 28, wherein the second response comprises at least one of:a message type,an indication whether the call can be accepted,a codec answer, ora port for audio media.

30. The apparatus of any of claims 18 to 29, wherein the communication is a voice call or a messaging interaction31. A method comprising:determining, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and transmitting, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request.

32. A method comprising:receiving, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request; and53creating, based on the request, a SIP request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication.

33. An apparatus comprising:means for determining, based on information indicative of capability of a network, support for establishment of a communication using a request comprising a different set of information with respect to a set of information comprised in a SIP request, and means for transmitting, to a first network entity in an Internet protocol (IP) multimedia subsystem (IMS) in response to a determination that the establishment of the communication is supported, the request for establishing the communication, the first network entity being capable of facilitating the establishment of the communication initiated with the request by creating a SIP request based on the request.

34. A first network entity in an Internet protocol (IP) multimedia subsystem (IMS) comprising:means for receiving, from an apparatus, a request for establishing a communication, wherein the request comprises a different set of information with respect to a set of information comprised in a SIP request; andmeans for creating, based on the request, a SIP request to be exchanged with at least one other network entity in the IMS to facilitate the establishment of the communication.

35. A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 31 or the method of claim 32.