WO2023110115A1

WO2023110115A1 - Gateway device, network node and methods in a communications network

Info

Publication number: WO2023110115A1
Application number: PCT/EP2021/086403
Authority: WO
Inventors: Afshin Abtin; Charles HEGARTY
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-12-17
Filing date: 2021-12-17
Publication date: 2023-06-22
Also published as: EP4449696A1

Abstract

A method performed by a network node for handling Internet Protocol Multimedia Subsystem (IMS) communication between a gateway device and a network node in a communications network is provided. The gateway device is a stationary device which is capable of handling IMS services transparently for a communication device connected to the gateway device. The network node receives (201) communication data from the gateway device. The communication data indicates any one out of: A) device information of the gateway device, or B) an identifier indicating how to retrieve the device information of the gateway device. The device information of the gateway device indicates a device type of the gateway device, and specifies whether the gateway device communicates in the communications network using a wireless or wired connection. The network node configures (204) the network node to adapt IMS services to be provided to the gateway device, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

Description

GATEWAY DEVICE, NETWORK NODE AND METHODS IN A COMMUNICATIONS

NETWORK

TECHNICAL FIELD

Embodiments herein relate to a gateway device, a network node, and methods therein. In some aspects, they relate to handling Internet Protocol Multimedia Subsystem (IMS) communication between the gateway device and the network node in a communications network.

BACKGROUND

In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.

3GPP is the standardization body for specify the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP). As a continued network evolution, the new releases of 3GPP specifies a 5G network also referred to as 5G New Radio (NR).

Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station, the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. Such systems and/or related techniques are commonly referred to as MIMO.

BBF (Broadband Forum), has defined a 5G Wireless Wireline Convergence (WWC) architecture for Fixed Mobile Convergence (FMC) which has been specifiedas part of 3GPP Release 16, e.g., WWC access support for 5G System (5GS) as discussed in 3GPP Technical Specification (TS) 23.316 R.16.0.0. Advances in 5G Core (5GC) have defined, e.g. in 3GPP TS 23.501 R.16.0.0, a transmission technology used in Access Networks (ANs) referred to as Wireline BBF Access Network (W-5GBAN). WWC as presently defined offers a seamless service experience to WWC devices such as 5G Residential Gateways (RG; 5G-RG) on wireless or wireline access connections. These gateways may further provide access over the wireline or wireless access connections for devices connected to a residential gateway.

Communication services, e.g. voice calls, are not currently defined as part of BBF, and have only been briefly mentioned as options in 5G WWC Architecture Technical Report (TR)-470 Issue 1 without details of how to implement such features.

To introduce voice services as part of the WWC in 5GC, an IMS project for Public Switched Telephone Network (PSTN) simulation on 5G-RGs has been initiated which is expected to define a profile, based on a minimum mandatory set of NG.114 services and procedures, of IMS behavior suitable for RGs attached to a 5G system and also outlining impacts on the network. Following this, BBF are likely to standardize IMS client requirements based on NG.114 for a 5G-RG acting as a proxy for a Plain Old Telephone Service (POTS) phone and further update 3GPP WWC specifications. However, how to implement such features remain unknown.

IMS as currently specified, e.g., in 3GPP TS.23.228 or TS 24.229, supports services for both mobile and fixed devices. Mobile devices access IMS services over wireless accesses, in these scenarios, e.g., access info can be gained by the IMS functions and/or IMS network functions from a P-Access-Network-Info header containing e.g. information of NR access using Frequency Division Duplex (FDD) “access-type” = 3GPP-NR-FDD. Fixed devices access IMS services over fixed accesses. In these scenarios, e.g., access info can be gained by the IMS functions from the P-Access-Network-Info header containing “access-type” = xDSL. Further device type information needed for various network functions in IMS that is dependent on access information and device type info can be determined from feature tags inserted by the device when communicating using IMS.

SUMMARY

As a part of developing embodiments herein a problem was identified by the inventors and will first be discussed.

BBF, e.g., in TR-470, and 5GC e.g. in 3GPP TS 23.316 and TS 23.501 , has defined 5G-RG as a residential gateway device capable of connecting to a 5GC playing the role of a UE with regard to the 5G core.

In this way, support for secure element and exchanges of data is achieved, e.g. over N1 and/or Uu interfaces, towards a Wireless Access Gateway Function (W-AGF), NR, or LTE signalling with 5GC. When voice over WWC will be introduced in BBF and subsequently in 3GPP, IMS will be the service engine whereby a single IMS core will serve WWC users on both wireline & wireless. From an IMS perspective, 5G-RG devices will display characteristics of a traditional fixed device, and will not roam, move, nor be subject to nomadism. However, the 5G-RG devices may still connect via wireless such as mobile 3GPP access, and may thus from a location perspective, e.g. for network nodes serving the 5G-RG devices, appear as a mobile devices. As there is no framework or mechanism available to aid IMS or other network functions to resolve these conflicting characteristics, providing services to such a device, will be inefficient, inaccurate, and cause errors for users and related services, nodes and functions. In addition, incorrect assumptions being made of the connection for the 5G-RG devices, e.g. what connection is used by the 5G-RG devices, will result in performance degradation for the end users. Furthermore, location-based services will assume that the 5G-RG device is a UE, and thus will try to locate it by triangulating its position, which leads to inaccurate locations as 5G-RG device is stationary, and should preferably be associated with a fixed position. In worst scenarios this may lead to dangerous situations for end-users, for example when an emergency call is made, and the emergency call is located to be associated with a different location from where the emergency call is made from, or a delay in setting up of an emergency due to lack of accurate location information.

An object of embodiments herein is to improve the efficiency and performance of providing services to devices in a communications network

According to an aspect of embodiments herein, the object is achieved by a method performed by a network node, for handling IMS communication between a gateway device, and a network node in a communications network. The gateway device is a stationary device which is capable of handling IMS services transparently for a communication device connected to the gateway device. The network node receives communication data from the gateway device. The communication data indicates any one out of:

A) device information of the gateway device, or

B) an identifier indicating how to retrieve the device information of the gateway device.

The device information of the gateway device indicates a device type of the gateway device, and specifies whether the gateway device communicates in the communications network using a wireless or wired connection. The network node configures the network node to adapt IMS services to be provided to the gateway device, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

According to another aspect of embodiments herein, the object is achieved by a method performed by a gateway device for handling IMS communication between the gateway device, and a network node in a communications network. The gateway device is a stationary device which is capable of handling IMS services transparently for a communication device connected to the gateway device. The gateway device signals communication data to the network node. The communication data indicates any one out of: A) device information of the gateway device, or

B) an identifier indicating how to retrieve the device information of the gateway device. The device information of the gateway device indicates a device type of the gateway device, and specifies whether the gateway device communicates in the communications network using a wireless or wired connection. Signaling the communication data configures the network node to adapt IMS services to be provided to the gateway device, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

According to another aspect of embodiments herein, the object is achieved by network node configured to handle IMS communication between a gateway device, and a network node in a communications network. The gateway device is arranged to be a stationary device which is capable of handling IMS services transparently for a communication device connected to the gateway device. The network node is further configured to:

- Receive communication data from the gateway device, wherein the communication data is adapted to indicate any one out of:

A) Device information of the gateway device, or

B) an identifier indicating how to retrieve the device information of the gateway device, wherein the device information of the gateway device is adapted to indicate a device type of the gateway device, and adapted to specify whether the gateway device communicates in the communications network using a wireless or wired connection, and

- configure the network node to adapt IMS services to be provided to the gateway device, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

According to another aspect of embodiments herein, the object is achieved by a gateway device configured to handle IMS communication between the gateway device, and a network node in a communications network. The gateway device is arranged to be a stationary device which is capable of handling IMS services transparently for a communication device connected to the gateway device. The gateway device is further configured to:

- Signal communication data to the network node, wherein the communication data is adapted to indicate any one out of: A) Device information of the gateway device, or

B) an identifier indicating how to retrieve the device information of the gateway device, wherein the device information of the gateway device is adapted to indicate a device type of the gateway device, and adapted to specify whether the gateway device communicates in the communications network using a wireless or wired connection, and wherein the signaled communication data is adapted to configure the network node to adapt IMS services to be provided to the gateway device, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

Since the communication data indicative of the device information or how to retrieve the device information is received by the network node, the network node is configured to adapt the IMS services to the gateway device. In this way, the IMS services will be adapted to the IMS services which are available to a stationary gateway device depending on whether the gateway device is communicating using a wired or wireless connection. In particular, when the gateway device is transparently handling a call for the communication device, services will accurately be able to handle the call as being from a stationary location, which thus improves the accuracy of location based services and improves safety in emergency situations.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail with reference to attached drawings in which:

Figure 1 is a schematic block diagram illustrating prior art.

Figure 2 is a schematic block diagram illustrating embodiments of a communications network.

Figure 3 is a flowchart depicting an embodiment of a method in a network node.

Figure 4 is a flowchart depicting an embodiment of a method in a gateway device.

Figure 5 is a schematic block diagram illustrating embodiments herein.

Figure 6 is a sequence diagram illustrating embodiments herein.

Figure 7 is a sequence diagram illustrating embodiments herein. Figure 8 is a sequence diagram illustrating embodiments herein.

Figure 9a-b are schematic block diagrams illustrating embodiments of a network node.

Figure 10a-b are schematic block diagrams illustrating embodiments of a gateway device.

Figure 11 schematically illustrates a telecommunication network connected via an intermediate network to a host computer.

Figure 12 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection,

Figures 13-16 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.

DETAILED DESCRIPTION

An example scenario of a problem with prior art will first be discussed and is illustrated by Figure 1. A 5G-RG device 1 may transparently handle communication between a fax machine 2 and/or a legacy telephone 3, and an IMS node 7. In the example scenario, the 5G-RG device 1 is a stationary device which transparently handles communication from the fax machine 2 and/or legacy telephone 3 with the IMS node 7 via a 5GC node 6 using a wireline connection 4, i.e. wired connection, or a wireless connection 5. The 5G-RG device if connected using a wireless connection (5) will in the example scenario appear to the IMS node 7 as if it is a mobile UE, e.g. since a P-Access-Network-Info header relating to communication with the 5G-RG device 1 will contain information related to a wireless access, and hence the IMS node 7 will perform location based services for the 5G-RG device 1 as if it was mobile. Furthermore, the IMS node 7 has no knowledge whether the 5G-RG device is communicating using the wireline connection 4, or the wireless connection 5, and may thus schedule data in a non-optimal manner. In this way, services such as IMS services used by the 5G-RG device 1 for the fax machine 2 and/or the legacy telephone 3 will be performed based on wrong assumptions about the devices, and hence, performance of the services, in particular location-based services will perform poorly.

Embodiments herein may provide a framework and/or mechanisms for network functions, e.g. arranged in any suitable network node providing network services such as IMS services, or for network nodes which at least partially handles said network functions. Embodiments herein may also extend to non-IMS functions, e.g. Machine Type Communication (MTC) services.

Embodiments herein may enable to differentiate device types of devices for offering relevant services. This may relate to identifying that a request is sent from a device of a WWC device type, such as from a gateway device, e.g. a 5G-RG device, and not from a legacy phone or a mobile device, e.g. a device may display characteristics which may be assumed or falsely deduced by the network to be a device of another characteristic type, e.g. falsely deducing the device as a device displaying mobile characteristics and thus proving mobile services not supported by the said device.

In particular, some embodiments herein relate to that that a gateway device is indicated to be stationary and is communicating over a wireless or wired connection.

By using embodiments herein, a better performance of services, e.g. IMS services, is achieved. In particular, performance of services relying on location of a requesting device is improved. This is since it may be determined that the requesting device is a stationary gateway device, and thus location may be fixed and e.g. predetermined. The location may then be determined by exact knowledge instead of by dynamical measures e.g. triangulation. The indication of whether or not the stationary gateway device is communicating using a wireless or wired connection may further improve how communication is routed to the gateway device. For example, embodiments herein enables an enhancement of currently defined, e.g. and in most cases 3GPP standardized, network procedures such as a Location Retrieval Function (LRF), mechanism for handling emergency calls. Routing may be optimized based on the embodiments herein by optimizing Public Safety Answering Point (PSAP) routing selection tables, or by sending a Location Services (LCS) service report to the PSAP, e.g. based on identifying that the requesting device is a stationary gateway device communicating using wired or wireless communication. Since the location and capabilities of the gateway device is better attained by embodiments herein, emergency situations may be handled faster and with increased efficiency.

Hence, besides improving performance and accuracy of positioning methods, embodiments herein also provide an increased safety for emergency situations.

Figure 2 is a schematic overview depicting a communications network 100 wherein embodiments herein may be implemented. The communications network 100 comprises one or more ANs s and one or more CNs. The one or more ANs may comprise any suitable AN, e.g. any one or more out of a RAN, a Wireless 5G AN (W-5GAN), and a W-5GBAN. While depicted as a separation between the ANs and CNs in Figure 2, any suitable overlap may occur, e.g. any entity in a CN may be in an AN and vice versa. The communications network 100 may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, NR, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMAX), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. The communications network 100 may also comprise wired connection, also referred to as wireline connections.

Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are also applicable in further development of the existing wireless communication systems such as e.g. WCDMA and LTE.

A number of radio network nodes operate in the communications network 100 such as e.g. a first radio network node 141 and a second radio network node 142. The first and/or second radio network nodes 141, 142 may provide radio communication and/or wired communication to connected entities in the communications network 100, e.g. CN nodes, network nodes, IMS network entities, UEs, gateway devices, and/or other remote ends. The first and/or second network node 141, 142 may each be any of a NG-RAN node, a W-5GAN node, a W-5GBAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless device and/or a gateway device within the service area served by the respective network node depending e.g. on the first radio access technology and terminology used. In some embodiments, the first and/or second radio network nodes 141 , 142 may be any node which can provide wired and/or wireless communication between wired and/or wireless devices, and nodes operating in the core network and/or as part of IMS.

In the communications network 100, one or more network nodes operate, such as e.g. the network node 130. The network node 130 may comprise, and/or be connected to any one or more out of: IMS functions, network functions, functionalities and/or network nodes handling these, e.g. Gateway Mobile Location Centre (GMLC), LRF, Call Session Control Functions (CSCFs), Proxy CSCF (P-CSCF), Serving CSCF (S-CSCF), Emergency CSCF (E-CSCF), Service Centralization and Continuity Application Server (SCC AS), Breakout Gateway Control Function (BGCF), Control Switched IMS Network to Network Interface (CS IMS NNI), PSAP. The network node 130 may at least partially control these functions, functionalities and nodes, e.g. by sending messages, requesting resources from them etc. The network node 130 may additionally or alternatively comprise any other suitable function or functionality. The network node 130 may at least partially handle IMS related communication and/or IMS related services between two end-points in the communications network 100, e.g. a remote end 121 and a gateway device 120. The network node 130 may e.g. be part of a radio network node such as any of the first and/or second radio network nodes 141 , 142, a server, or any suitable network entity in the communications network 100.

In the communications network 100, one or more home network nodes operate, such as e.g. the home network node 111. The home network node 130 may handle communication between gateway devices such as the gateway device 110 and the network node 130. The home network node 111 may comprise any one or more out of: Wireless Access Gateway Function (W-AGF), Access and Mobility management Function (AMF), Session Management Function (SMF), Packet Network Data Gateway Control (PGW-C), Policy Control Function (PCF), Unified Data Management (UDM), Home Subscriber Server (HSS). HSS as used herein is a network function typically arranged for use in 4G networks. UDM as used herein is a network function typically cloud-native and arranged for use in 5G networks and may comprise all the functionality of the HSS. Which of HSS or UDM may depend on which type of network is used, e.g. 4G or 5G. The home network node 111 may additionally or alternatively comprise any other suitable function or functionality. The home network node 111 may at least partially handle IMS related communication and/or IMS related services between the gateway device 110 and the network node 130. The home network node 111 may e.g. be part of a radio network node such as any of the first and/or second radio network nodes 141, 142, a server, or any suitable network entity in the communications network 100. The gateway device 110 may communicate directly with the home network node 111 , e.g. using a wired or wired connection, and/or via the first radio network node 141.

One or more gateway devices communicates with the communications network 100, such as e.g. the gateway device 110. The gateway device 110 is a stationary device which is capable of handling IMS services transparently on behalf of the communication device 120. Typically the gateway device 110 operate similarly as a UE in the context of IMS, and are able to connect to legacy, such as the communication device 120, to enable them to use IMS services. The gateway device 110 may be any suitable WWC device, such as e.g. a 5G-RG device. The gateway device 110 may provide and/or handle IMS services for the communication device 120 by communication with the network node 130. For example, the network node 130 may orchestrate a call between a remote end 121 connected to the network node 130, and the gateway device 110, wherein the gateway device 110 transparently forwards the call to the communication device 120. The gateway device 110 may communicate with the network node 130 via any one or both of the home network node 111 and the first radio network node 141.

In the communications network 100, one or more communication devices communicates with, such as e.g. the communication device 120. The communication device 120 may be a legacy device or a UE, e.g. any of: a fax machine, a point of sale machine, and a legacy telephone. The communication device 120 may not be capable to communicate, via IMS nor capable of using any IMS services directly. The communication device 120 may be any suitable device for communicating using IMS, or using IMS services by the use of a gateway device 110.

The communication device 120 may connect to the gateway device 110 via an Internet Protocol (IP) port, or any other suitable port at the gateway device 100. In this way, the communication device 120 gets a fixed network access to the communications network 100 via the gateway device 110, which transparently connects to the communications network 100 e.g. via wired or wireless connection.

In the communications network 100, one or more remote end devices operate, such as e.g. the remote end device 121. The remote end device 121 may be any suitable communication device and/or gateway device with an established communication to the communication device 120 and/or the gateway device 110, e.g. via IMS communications and/or the use of IMS services handled by the network node 130. The remote end device 121 may communicate with the network node 130, e.g. via the second radio network node 142. The remote end device 121 may e.g. be any suitable communication device, e.g. a legacy device and/or a UE.

In embodiments herein, any communication between the gateway device 110 and the network node 130 may be performed directly, e.g. using a wired or wired connection, and or via any one or more out of the first radio network node 141 , the second radio network node 142, and the home network node 111 , or any via any other suitable device.

Methods herein may be performed by the gateway device 110 and the network node 130. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 135 as shown in Figure 2, may be used for performing or partly performing the methods herein.

A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

Figure 3 shows example embodiments of a method performed by the network node 130, for handling IMS communication between the gateway device 110 and the network node 130 in the communications network 100. The gateway device 110 is a stationary device which is capable of handling IMS services transparently for the communication device 120 connected to the gateway device 110. The method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 3.

Action 301

The network node 130 receives communication data from the gateway device 110. The communication data indicates any one out of:

A) device information of the gateway device 110, or

B) an identifier indicating how to retrieve the device information of the gateway device 110.

The device information of the gateway device 110 indicates a device type of the gateway device 110, and specifies whether the gateway device 110 communicates in the communications network 100 using a wireless or wired connection. The device information may further comprise any suitable capability of the gateway device 110. For example, the device information may indicate which IMS services are suitable and/or available to the gateway device 110.

The indicated device type may be that the gateway device 110 is any one or more out of: a stationary WWC device, a stationary gateway device, a 5G-RG device.

In some embodiments, the device type indicates whether the gateway device 110 communicates in the communications network 100 using a wireless or wired connection.

In some embodiments, any of the communication data, device information, and/or device type is represented by a feature tag. In some embodiments, the device information and/or device type may indicate any suitable characteristics of a 5G-RG device, e.g. such that the gateway device 110 can be identified as a 5G-RG device.

Action 201a, 201b

In some embodiments, the receiving of the communication data is performed as part of any one or more out of:

- Receiving a request for registration, e.g. IMS registration, of the gateway device 110 with the network node 130, and

- receiving a request, e.g. a Session Initiation Protocol (SIP) or IMS invite, for the network node 130 to start a communication session between the network node 130 and the gateway device 110.

In other words, the communication data may be received when registering the gateway device 110 with the network node 130 and/or when they initiate their session.

In some embodiments, any one or more out of receiving the request for registration, and receiving the request to start a communications session, may indicate an emergency call by the communication device 120.

Action 302

In some embodiments, when the communication data indicates how to retrieve the device information of the gateway device 110, the network node 130 obtains the device information of the gateway device 110 as indicated by the received communication data. The identifier indicating how to retrieve the device information may e.g. comprise and index or other information which may indicate how to obtain the device information from any suitable database or index.

In some embodiments, the network node 130 obtains the device information of the gateway device 110 as indicated by the received communication data by requesting and receiving the device information from a HSS or a UDM associated with the network node 130.

Action 303

In some embodiments, the network node 130 determines which IMS services are available for the indicated device type communicating using the specified wireless or wired connection. For example, the communication data, as obtained in actions 301-302, or the indicated device type may indicate which IMS services are available for the indicated device type. Determining which IMS services are available may further be based on the capabilities of the gateway device 110.

Based on any one or more out of device type of the gateway device 110, capabilities of the gateway device 110, and/or whether the gateway device 110 is communicating using a wired or wireless connection, suitable configuration for IMS services, e.g. which IMS services are available, may be predetermined, or may be looked up in a suitable table or database.

Action 304

The network node 130 configures the network node 130 to adapt IMS services to be provided to the gateway device 110, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection. In this way, the correct IMS services with best performance for the gateway device 110 is setup and may be provided to the network node 130.

In some embodiments, the network node 130 configures the network node 130 to adapt IMS services, by any one or more out of:

- Configuring the network node 130 to handle emergency calls via the IMS communication between the gateway device 110 and the network node 130, e.g. which improves how emergency calls is handled over IMS since better location and/or routing of traffic may be performed for emergency calls,

- configuring the network node 130 to disable or adapt location-based services, e.g. refraining from triangulating a location of the gateway device 110 and instead looking up a predetermined location of the gateway device 110 which improves the accuracy of the location-based services.

- configuring a Terminating Access Domain Selection, T-ADS, for the gateway device 110, wherein configuring the T-ADS for the gateway device 110 ensures that the gateway device 110 refrains from dynamically attaching and/or moving to another communications network. T-ADS may e.g. be hosted by an SCC AS network function, e.g. comprised in and/or at least partially controlled by the network node 130.

In this way, the communication handled by the gateway device, e.g. for the communication device 120, is predictable and thus routing of data may be optimized towards the gateway device 100. Figure 4 shows example embodiments of a method performed by the gateway device 110 for handling IMS communication between the gateway device 110, and the network node 130 in the communications network 100. The gateway device 110 is a stationary device which is capable of handling IMS services transparently for the communication device 120 connected to the gateway device 110. The method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 4.

Action 401

In some embodiments, the gateway device 110, obtains a call indication from the communication device 120. The call indication indicates a call type initiated by the communication device 120. For example, the call indication may indicate any one of: An emergency call, a normal voice call, and any other suitable call type.

Action 402

The gateway device 110, signals communication data to the network node 130. The communication data indicates any one out of:

A) Device information of the gateway device 110, or

The device information of the gateway device 110 indicates a device type of the gateway device 110. The device information further indicates and specifies whether the gateway device 110 communicates in the communications network 100 using a wireless or wired connection. The signaled communication data configures the network node 130 to adapt IMS services to be provided to the gateway device 110, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection. The device information may further comprise any suitable capability of the gateway device 110. For example, the device information may indicate which IMS services are suitable and/or available to the gateway device 110. The indicated device type may be that the gateway device 110 is any one or more out of: a stationary WWC device, a stationary gateway device, a 5G-RG device.

In some embodiments, the device information and/or device type may indicate any suitable characteristics of a 5G-RG device, e.g. such that the gateway device 110 can be identified as a 5G-RG device. In some embodiments when the gateway device 110 signals the communication data to the network node 130, the signalling may enable the network node 130 to adapt the IMS services and/or the signalling may trigger the network node to adapt the IMS services.

The communication data signaled to the network node 130 may further indicate the session request type initiated by the communication device 120. In other words, the communication data may comprise the call type. In this way, the network node 130 may adapt the IMS services to the call type, e.g. when there is an emergency session request, the signaling communication data will be used to establish the characteristic of the device type of the gateway device 110 and what access the gateway device 110 is using, which leads to a more accurate and efficient emergency location handling.

In some embodiments, any of the communication data, device information, and/or device type is represented by a feature tag.

When the call indication, e.g. of Action 401 above, indicates an emergency call, an emergency Protocol Data Unit (PDU) session may first be established and created by the gateway device 110, e.g. when it is going to establish an emergency call towards an emergency centre. Normal voice calls may be communicated over an IMS PDU session. PDU sessions may be the connectivity mechanism on a packet core of the communications network 100, while SIP procedures are used over these PDU session to IMS to create a call and similar communication services. The gateway device 110 may however need to provide its device information to IMS, e.g. the network node 130, regardless of type of call, normal or emergency, e.g. so that the network node 130 may adapt services to best serve the gateway device 110 and its connected communication device 120.

Action 402a, 402b

In some embodiments, the gateway device 110 signals the communication data to the network node 130, is performed as part of any one or more out of:

- Requesting a registration of the gateway device 110 with the network node 130, e.g. IMS registration, of the gateway device 110 with the network node 130, and

- requesting for the network node 130 to start a communication session between the network node 130 and the gateway device 110, e.g. a SIP or IMS invite. In other words, the communication data may be received when registering the gateway device 110 with the network node 130 and/or when they initiate their session.

In some embodiments, any one or more out of requesting the registration, and requesting to start the communication session, indicates an emergency call by the communication device 120.

The above embodiments will now be further explained and exemplified below. The embodiments below may be combined with any suitable embodiment above.

Embodiments herein may comprise a number of mechanisms that may be used to identify the device type of the gateway device 110 and/or any suitable WWC device type. The mechanism used may be predetermined and/or negotiated between the gateway device 110 and the network node 130 in any suitable manner

In some embodiments it is possible to use a tagging paradigm whereby a 5G-RG shall tag its SIP requests sent to the network node 130 with an indicator that shall be used by network functions of the network node 130 to identify that the request is from a WWC device, e.g. a stationary gateway device, and act accordingly, e.g. as in action 402 above.

In some embodiments it may additionally or alternatively be possible to, by the use of a subscription tagging paradigm, e.g. the subscriber profile of an WWC subscriber indicating use of the gateway device 110, identify the device type of the gateway device 110. This may e.g. be performed by identifying the device type of the gateway device 110 and/or the user of the gateway device 110 in any suitable manner. For example, an Internet Protocol Multimedia Private Identity (IMPI) of a user, a Subscriber Identity Module (SIM) and/or universal integrated circuit card (IIICC) of the user may be associated with a parameter and/or indicator in UDM or HSS indicating the device type of the gateway device, which may be obtained during the registration of the gateway device 110, e.g. as in action 302 above, and may be distributed to relevant network functions of the network node 130. The relevant network functions may each respectively adapt one or more IMS services to be provided to the gateway device 110 based on the parameter and/or indicator.

The device information indicated as in embodiments herein may, besides being used for identifying WWC devices, e.g. their device type, whether they communicate over a wired or wireless connection, and capabilities, may also be used to enhance existing network operations to provide regulatory services, e.g. improving emergency call handling and/or LRF. In some embodiments herein, which mechanism to use for identifying the device type may be configurable but may also be agreed prior to deployment. For example, when the device tagging paradigm is used, it may be agreed in advance a feature tag and/or indication identifier (ID) to be used by the gateway device 110 in the communications network 100. The device information, e.g. communicated in actions 301 , 402, may comprise the tag and/or ID e.g. to indicate the device type of the gateway device 110.

The existing feature tag SIP. Mobility, e.g. as described in Internet Engineering Task Force (IETF) Request For Comments (RFC) 3840, indicates whether a device is fixed, e.g. meaning that it is associated with a fixed point of contact with the network, or mobile, e.g. meaning that it is not associated with a fixed point of contact, may in some embodiments be used and modified to the embodiments herein. For example, the feature tag may be updated to indicate for example, “WWC-Wireline-BBF” and be used in embodiments herein, e.g. indicating that the gateway device 110 is a WWC Wireline BBF device, i.e. a stationary WWC device communicating over a wired connection.

In some embodiments herein, e.g. as in action 304, when determining that the gateway device 110 is stationary, location-based services may be adapted and or disabled, e.g. by the network node 130. This may involve communication with network functions, e.g. located in a remote node and/or co-located with the network node 130, that they need to adapt their location-based services, e.g. IMS services, to that the gateway device 110 is stationary. For example, this may comprise ensuring that Mobile Telephony Application Server (MMTel-AS) services, or any similar services, e.g. barring and/or roaming shall not be invoked. Instead, some location-based services may need to be access and/or device aware. Furthermore, in some embodiments, MMTel AS shall not invoke NetLoc for WWC devices on a wireline, e.g. as NetLoc is related to location on wireless access and the WWC device location is stationary and may be known to the network node.

In some embodiments herein, e.g. as in action 304, SCC AS shall not be invoked e.g. by the network node 130, because T-ADS is not required for 5G-RG devices such as the gateway device 110 as they will not attach and/or move to 3G.

In some embodiments herein, when handling of emergency calls, LRF, e.g. associated with, or performed at least partially by the network node 130, needs to differentiate between a 5G-RG device on BBF, e.g. the gateway device 110, in comparison to a wireline device on a Digital Subscriber Line (DSL; xDSL). LRF and/or the network node 130 may also need to determine that the gateway device 110 on using a wireless connection is not a mobile device. This is solved by the device information e.g. as actions 301 , 402.

Two example scenarios of embodiments herein is illustrated by Figure 5. Gateway device 110 may be connected to one or more communication devices, in these scenarios a fax machine 520 and a legacy phone 521. The fax machine 520 and/or the legacy phone 521 may represent the communication device 120.

The gateway device 110 communicate to a an IMS node 530 via a 5GC node 511 , wherein the gateway device 110 uses a wireless or wired connection towards the 5GC node 511. The 5GC node 511 may represent the home network node 111. The IMS node 530 may be, or be part of the network node 130. The IMS node 530 and the 5GC node 511 is connected to a HSS and/or UDM node 505 of the IMS node 530. The HSS and/or UDM node 505 may be a HSS and/or UDM node associated with the network node 130 and/or be part of the network node 130.

The first example scenario of Figure 5 exemplifies a device tagging mechanism. The gateway device 110 populates 501 a “Wireline-WWC-BBF” feature tag, e.g. creates the tag for identifying the device in upcoming communications. The gateway device 110 sends the tag, e.g. as in action 402. The IMS node 530 receives the populated tag, e.g. as in action 301. The IMS node 530, informs 504 IMS functions associated with the IMS node 530 e.g. CSCFs such as P-CSCF, of the feature tag and may further adapt their behavior.

The second example scenario of Figure 5 exemplifies a subscription tagging mechanism. The IMS node 530 downloads 502 a parameter indicating the device type of the gateway device 110 from the HSS and/or UDM node 505. The parameter may be mapped to a similar feature tag as in the first example scenario. The IMS node 530, informs 503 IMS functions associated with the IMS node 530 e.g. CSCFs such as P- CSCF, of the parameter and may further adapt their behavior.

Figure 6 illustrates an example scenario of a device tagging mechanism, e.g. as in Figure 5. Embodiments herein may in particular be related to the underlined text in the figures. Some communication flows which are obvious to a skilled person may not be shown in Figure 6. The example scenario may exemplify the indication of a device type and/or whether the gateway device 110 is communication using a wired or wireless connection using a feature tag. While a feature tag may be exemplified in the example scenario, any other suitable indication or representation of a device type may be sent and/or obtained, e.g. as in actions 301-304, 401-402 above instead of the feature tag. The example scenario may comprise any one or more out of the following actions in any suitable order.

The gateway device 110 issues 601 a 5GC Registration via a W-5GAN, e.g. via the first radio network node 141 and/or the home network node 111.

The gateway device 110 initiates 602 an IMS registration, e.g. as in action 301a. Avails of Device ID, e.g. the device type of the gateway device 110. Includes a feature tag "Mobility=WWC-Wireline-BBF", e.g. the device type of the gateway device 110.

The gateway device 110 sends 603, e.g., as in action 301a, a message, e.g. comprising any one or more out of the following parameters or similar suitable parameters:

Register, sip:example.com SIP/2.0,

To: sip:Y@example.com,

Contact: sip:Y1@WWC. example. com, and

Feature Tag="WWC-Wireline-BBF".

IMS functions, e.g. P-CSCF, MMtel AS, SCC AS etc., e.g. comprised in or partially controlled by the network node 130, stores 604 the Mobility="WWC-Wireline-BBF" tag, which is used for identification of the gateway device 110 and its device type.

The gateway device 110 is now registered 605 with IMS, e.g. the network node 130, and has indicated that is a device of type "WWC-Wireline-BBF".

A user initiates 606 a call.

The gateway device 110 initiates 607 an invite, e.g. to the network node 130. Avails of Device ID framework, e.g. comprising the device type of the gateway device 110. Includes a feature tag "Mobility=WWC-Wireline-BBF", e.g. the device type of the gateway device 110.

The gateway device 110 sends 608 an INVITE message, e.g. comprising any one or more out of the following parameters or similar suitable parameters: sip:RemoteEnd.com SIP/2.0, and feature tag="WWC-Wireline-BBF.

The IMS functions of the network node 130 e.g., P-CSCF, MMtel AS, SCC AS, LRF etc. uses 609 the received feature tag, e.g. or stored tag from the registration, to provide the relevant services to the gateway device 110.

Call and media is established 610 from the gateway device 110 towards the remote end 121. Figure 7 illustrates a network procedure of embodiments herein comprising enhancements made to an IMS emergency call for WWC devices such as the gateway device 110. Figure 7 is based on the device tagging mechanism but any applicable mechanism for providing the device type may be applicable, e.g. as the subscriber tagging mechanism describes above. While a feature tag may be exemplified in the example scenario, any other suitable indication or representation of a device type may be sent and/or obtained, e.g. as in actions 301-304, 401-402 above instead of the feature tag. The example scenario may comprise any one or more out of the following actions in any suitable order.

A user initiates 701 an Emergency Call (EC), e.g. calls 911 or 112 or other emergency number.

The gateway device 110 establishes 702 an emergency PDU Session. The gateway device 110 uses Request Type = Emergency Request.

The gateway device 110 initiates 703 an IMS emergency registration. Avails of Device ID framework, e.g. comprising the device type of the gateway device 110. Includes a feature tag "Mobility=WWC-Wireline-BBF", e.g. the device type of the gateway device 110.

The gateway device 110 sends 704 to a P-CSCF 732 of the network node 130, a SIP Register messages e.g. comprising: Mobility="WWC-Wireline-BBF".

The P-CSCF 732 sends 705 to a S-CSCF 733 of the network node 130, a SIP Register messages e.g. comprising: feature tag="WWC-Wireline-BBF".

The gateway device 110 initiates 706 an IMS emergency invite. Avails of Device ID framework, e.g. comprising the device type of the gateway device 110. Includes a feature tag "Mobility=WWC-Wireline-BBF", e.g. the device type of the gateway device 110.

The gateway device 110 sends 707 to the P-CSCF 732 of the network node 130, a SIP Register messages e.g. comprising: Mobility="WWC-Wireline-BBF".

The P-CSCF 732 sends 708 to the S-CSCF 733 of the network node 130, a SIP Register messages e.g. comprising: P-Access-Network-lnfo(PANI)=location feature tag="WWC-Wireline-BBF".

An E-CSCF or BGCF 734 of the network node 130 ensures 709 that a message e.g. comprising "Mobility=WWC-Wireline-BBF" is sent e.g. on an Mi interface between the E-CSCF 734 and the LRF 731 , wherein the Ml interface is arranged for passing emergency location information. The E-CSCF or BGCF 734 sends 710 to a GMLC or LRF 731 of the network node 130, a message, e.g. comprising any one or more out of the following parameters or similar suitable parameters: lnvite/300,

PANI: location, and

Mobility="WWC-Wireline-BBF".

GMLC or LRF 731 determines 711 that the gateway device 110 is a WWC device, and not a legacy fixed device, e.g. using parameters: "feature tag=WWC-Wireline-BBF". This enables an optimized selection of PSAP routing tables & sending LCS report to PSAP.

GMLC or LRF 731 sends 712 an LCS service report to a PSAP 736 of the network node 130. The LCS service report may comprise location and/or device details such as the device type of the gateway device 110.

GMLC or LRF 731 sends 713a to the E-CSCF or BGCF 734 a (PSAP) message, e.g. address of the PSAP, e.g. which triggers the E-CSCF or BGCF 734 to send an Invite: (PSAP) to the PSAP 736.

In this way, a call set up, e.g. SIP, procedures and media are established

714.

Figure 8 illustrates an example scenario of a subscription tagging mechanism, e.g. as in Figure 5. Embodiments herein may in particular be related to the underlined text in the figures. Some communication flows which are obvious to a skilled person may not be shown in Figure 8. While a feature tag may be exemplified in the example scenario, any other suitable indication or representation of a device type may be sent and/or obtained, e.g. as in actions 301-304, 401-402 above instead of the feature tag. The example scenario may comprise any one or more out of the following actions in any suitable order

A feature tag "BBF-Wireline", e.g. used to identify the gateway device 110, is configured 801a as part of the gateway device 110s SIM/UICC.

A feature tag "BBF-Wireline", e.g. used to identify the gateway device 110 is provisioned as part of a user service profile. The feature tag may e.g. be tied to the users IMPI.

The gateway device 110 registers 802 a first SIP register with IMPI and Tag, e.g. UAA & MAA to a HSS 834 of the network node 130, the gateway device 110 may receive 401. The gateway device 110 registers 803 e.g. with IM PI & Tag with a P-CSCF 832 of the network node 130.

The P-CSCF 832 sends the register message to an l-CSCF with an l-CSCF 831 of the network node 130.

The l-CSCF 831 sends 805 User-Authorization-Request (UAR) to the HSS 834. The HSS 834 responds 806 with a User-Authorization-Answer (UAA).

The l-CSCF 831 sends 807 UAA to a S-CSCF 833 of the network node 130.

The S-CSCF 833 sends 808 Server-Assignment-Request & Answer (SAR) to the HSS 834, e.g. on a Cx interface. The HSS 834 responds 809 with an SAA.

The S-CSCF 833 downloads 810 a profile, the profile comprises a "BBF-Wireline" feature tag and/or the device type of the gateway device. The S-CSCF 833 stores the Tag "BBF-Wireline".

The S-CSCF 833 sends 811 a 200 OK, e.g. indicating a success, to the P-CSCF 832. The 200 OK message may include the "BBF-Wireline" feature tag and/or the device type of the gateway device 110.

The P-CSCF 832 stores 812 "BBF-Wireline" feature tag and/or device type of the gateway device 110 for later use, e.g. to determine the device type for normal and/or emergency calls.

The P-CSCF 832 sends 813 a 200 OK to the gateway device 110, e.g. indicating a success.

The S-CSCF 833 perform 814 a 3rd party registration with an MMtel AS 835 of the network node 130. The registration may comprise a "BBF-Wireline" feature tag.

The MMtel AS 835 stores 815 the "BBF-Wireline" tag for later use, e.g. to determine device type of the gateway device 110.

To perform the method actions above, the network node 130 is configured to handle IMS communication between the gateway device 110, and the network node 130 in the communications network 100. The gateway device 110 is arranged to be a stationary device which is capable of handling IMS services transparently for the communication device 120 connected to the gateway device 110. The network node 130 may comprise an arrangement depicted in Figures 9a and 9b.

The network node 130 may comprise an input and output interface 900 configured to communicate in the communication network 100 , e.g. with any one or more out of the gateway device 110, the home network node 111 , the first and/or second radio network node 141, 142, and the remote end 121. The input and output interface 900 may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).

The network node 130 may further be configured to, e.g. by means of a receiving unit 901 in the network node 130, receive communication data from the gateway device 110, wherein the communication data is adapted to indicate any one out of:

A) device information of the gateway device 110, or

B) an identifier indicating how to retrieve the device information of the gateway device 110, wherein the device information of the gateway device 110 is adapted to indicate a device type of the gateway device 110, and adapted to specify whether the gateway device 110 communicates in the communications network 100 using a wireless or wired connection.

The network node 130 may further be configured to, e.g. by means of a configuring unit 902 in the network node 130, configure the network node 130 to adapt IMS services to be provided to the gateway device 110, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

The network node 130 may further be configured to, e.g. by means of an obtaining unit 903 in the network node 130, when the communication data indicates the identifier indicating how to retrieve the device information of the gateway device 110, obtain the device information of the gateway device 110 as indicated by the received communication data.

The network node 130 may further be configured to, e.g. by means of the obtaining unit 903 in the network node 130, obtain the device information of the gateway device 110 as indicated by the received communication data by further comprising requesting and receiving the device information from a Home Subscriber Server, HSS, or a Unified Data Management, UDM, associated with the network node 130.

The network node 130 may further be configured to, e.g. by means of the receiving unit 901 in the network node 130, receive the communication data by receiving the communication data as part of any one or more out of:

- receiving a request for registration of the gateway device 110 with the network node 130,

- receiving a request for the network node 130 to start a communication session between the network node 130 and the gateway device 110. In some embodiments, any one or more out of: the received request for registration and the received request to start a communications session, are adapted to indicate an emergency call by the communication device 120.

The network node 130 may further be configured to, e.g. by means of the configuring unit 902 in the network node 130, configure the network node 130 to adapt IMS services, by comprising any one or more out of:

- configuring the network node 130 to handle emergency calls via the IMS communication between the gateway device 110 and the network node 130,

- configuring the network node 130 to disable or adapt location-based services,

- configuring a Terminating Access Domain Selection, T-ADS, for the gateway device 110, wherein configuring the T-ADS for the gateway device 110 is adapted to ensure that the gateway device 110 refrains from dynamically attaching and/or moving to another communications network.

The network node 130 may further be configured to, e.g. by means of a determining unit 904 in the network node 130, determine which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

The embodiments herein may be implemented through a respective processor or one or more processors, such as the processor 960 of a processing circuitry in the network node 130 depicted in Figure 9a, together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the network node 130. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the network node 130.

The network node 130 may further comprise a memory 970 comprising one or more memory units. The memory 970 comprises instructions executable by the processor in network node 130. The memory 970 is arranged to be used to store e.g. information, indications, data, configurations, device types, device information, feature tags, communication data, and applications to perform the methods herein when being executed in the network node 130.

In some embodiments, a computer program 980 comprises instructions, which when executed by the respective at least one processor 960, cause the at least one processor of the network node 130 to perform the actions above.

In some embodiments, a respective carrier 990 comprises the respective computer program 980, wherein the carrier 990 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

Those skilled in the art will appreciate that the units in the network node 130 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the network node 130, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry ASIC, or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a- chip SoC.

To perform the method actions above, the gateway device 110 configured to handle IMS communication between the gateway device 110, and a network node 130 in a communications network 100. The gateway device 110 is arranged to be a stationary device which is capable of handling IMS services transparently for a communication device 120 connected to the gateway device 110. The gateway device 110 may comprise an arrangement depicted in Figures 10a and 10b.

The gateway device 110 may comprise an input and output interface 1000 configured to communicate in the communication network 100 , e.g. with any one or more out of the network node 130, the home network node 111 , the first and/or second radio network node 141 , 142, and the communication device 120. The input and output interface 1000 may comprise a wireless receiver not shown and a wireless transmitter not shown. The gateway device 110 may further be configured to, e.g. by means of a signaling unit 1001 in the gateway device 110, signal communication data to the network node 130, wherein the communication data is adapted to indicate any one out of:

A) device information of the gateway device 110, or

B) an identifier indicating how to retrieve the device information of the gateway device 110, wherein the device information of the gateway device 110 is adapted to indicate a device type of the gateway device 110, and adapted to specify whether the gateway device 110 communicates in the communications network 100 using a wireless or wired connection, and wherein the signaled communication data is adapted to configure the network node 130 to adapt IMS services to be provided to the gateway device 110, based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

The gateway device 110 may further be configured to, e.g. by means of the signaling unit 1001 in the gateway device 110, to signal the communication data to the network node 130, by signalling the communications data as part of any one or more out of:

- requesting a registration of the gateway device 110 with the network node 130,

- requesting for the network node 130 to start a communication session between the network node 130 and the gateway device 110.

In some embodiments, any one or more out of the registration request, and the request to start the communication session, are adapted to indicate an emergency call by the communication device 120.

The gateway device 110 may further be configured to, e.g. by means of an obtaining unit 1002 in the gateway device 110, obtain from the communication device 120 a call indication indicating a call type initiated by the communication device 120, and wherein the communications data signaled to the network node 130, is adapted to indicate the call type initiated by the communication device 120.

The embodiments herein may be implemented through a respective processor or one or more processors, such as the processor 1060 of a processing circuitry in the gateway device 110 depicted in Figure 10a, together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the gateway device 110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the gateway device 110.

The gateway device 110 may further comprise a memory 1070 comprising one or more memory units. The memory 1070 comprises instructions executable by the processor in gateway device 110. The memory 1070 is arranged to be used to store e.g. information, device information, device type, communication data, feature tags, indications, data, configurations, and applications to perform the methods herein when being executed in the gateway device 110.

In some embodiments, a computer program 1080 comprises instructions, which when executed by the respective at least one processor 1060, cause the at least one processor of the gateway device 110 to perform the actions above.

In some embodiments, a respective carrier 1090 comprises the respective computer program 1080, wherein the carrier 1090 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

Those skilled in the art will appreciate that the units in the gateway device 110 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the gateway device 110, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a- chip (SoC).

With reference to Figure 11 , in accordance with an embodiment, a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, e.g. communication network 100, which comprises an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c, e.g. radio network nodes 141 ,142, is connectable to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE), e.g. remote end 121 or gateway device 110, such as a Non-AP STA 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 such as a Non-AP STA in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291 , 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.

The telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220. The intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).

The communication system of Figure 11 as a whole enables connectivity between one of the connected UEs 3291 , 3292 and the host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291 , 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211 , the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 12. In a communication system 3300, a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.

The communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Figure 12) served by the base station 3320. The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct or it may pass through a core network (not shown in Figure 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

The communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, applicationspecific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310. In the host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that it provides. It is noted that the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 12 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291 , 3292 of Figure 11, respectively. This is to say, the inner workings of these entities may be as shown in Figure 12 and independently, the surrounding network topology may be that of Figure 11.

In Figure 12, the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the RAN effect: data rate, latency, power consumption and thereby provide benefits such as e.g. the applicable corresponding effect on the OTT service: reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311 , 3331 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.

Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional sub step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

Figure 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional sub step (not shown) the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step 3530, the UE receives the user data carried in the transmission.

Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In an optional sub step 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional sub step 3611 of the first step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third sub step 3630, transmission of the user data to the host computer. In a fourth step 3640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as an AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In an optional first step 3710 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second step 3720, the base station initiates transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used.

Claims

1. A method performed by a network node (130), for handling Internet Protocol Multimedia Subsystem, IMS, communication between a gateway device (110), and a network node (130) in a communications network (100), wherein the gateway device (110) is a stationary device which is capable of handling IMS services transparently for a communication device (120) connected to the gateway device (110), the method comprising:

- receiving (301) communication data from the gateway device (110), wherein the communication data indicates any one out of:

A) device information of the gateway device (110), or

B) an identifier indicating how to retrieve the device information of the gateway device (110), wherein the device information of the gateway device (110) indicates a device type of the gateway device (110), and specifies whether the gateway device (110) communicates in the communications network (100) using a wireless or wired connection, and

- configuring (304) the network node (130) to adapt IMS services to be provided to the gateway device (110), based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

2. The method according to claim 1 further comprises:

- when the communication data indicates the identifier indicating how to retrieve the device information of the gateway device (110), obtaining (302) the device information of the gateway device (110) as indicated by the received communication data.

3. The method according to claim 2, wherein obtaining (302) the device information of the gateway device (110) as indicated by the received communication data further comprises requesting and receiving the device information from a Home Subscriber Server, HSS, or a Unified Data Management, UDM, associated with the network node (130).

4. The method according to any of claims 1-3 wherein receiving (301) the communication data, is performed as part of any one or more out of: - receiving (301a) a request for registration of the gateway device (110) with the network node (130),

- receiving (301b) a request for the network node (130) to start a communication session between the network node (130) and the gateway device (110).

5. The method according to claim 4, wherein any one or more out of receiving (301a) the request for registration, and receiving (301b) the request to start a communications session, indicates an emergency call by the communication device (120).

6. The method according to any of claims 1-5, wherein configuring (304) the network node (130) to adapt IMS services, comprises any one or more out of:

- configuring the network node (130) to handle emergency calls via the IMS communication between the gateway device (110) and the network node (130),

- configuring the network node (130) to disable or adapt location-based services,

- configuring a Terminating Access Domain Selection, T-ADS, for the gateway device (110), wherein configuring the T-ADS for the gateway device (110) ensures that the gateway device (110) refrains from dynamically attaching and/or moving to another communications network.

7. The method according to any of claims 1-6, wherein the method further comprises:

- determining (303) which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

8. A computer program (980) comprising instructions, which when executed by a processor (960), causes the processor to perform actions according to any of the claims 1-7.

9. A carrier (990) comprising the computer program (980) of claim 8, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

10. A method performed by a gateway device (110) for handling Internet Protocol Multimedia Subsystem, IMS, communication between the gateway device (110), and a network node (130) in a communications network (100), wherein the gateway device (110) is a stationary device which is capable of handling IMS services transparently for a communication device (120) connected to the gateway device (110), the method comprising:

- signaling (402) communication data to the network node (130), wherein the communication data indicates any one out of:

A) device information of the gateway device (110), or

B) an identifier indicating how to retrieve the device information of the gateway device (110), wherein the device information of the gateway device (110) indicates a device type of the gateway device (110), and specifies whether the gateway device (110) communicates in the communications network (100) using a wireless or wired connection, and wherein signaling (402) the communication data configures the network node (130) to adapt IMS services to be provided to the gateway device (110), based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

11. The method according to claim 10 wherein, signaling (402) the communication data to the network node (130), is performed as part of any one or more out of:

- requesting (402a) a registration of the gateway device (110) with the network node (130),

- requesting (402b) for the network node (130) to start a communication session between the network node (130) and the gateway device (110).

12. The method according to claim 11 , wherein any one or more out of requesting (302a) the registration, and requesting (402b) to start the communication session, indicates an emergency call by the communication device (120).

13. The method according to any of claims 10-12, further comprising:

- obtaining (401) from the communication device (120), a call indication indicating a call type initiated by the communication device (120), and wherein signaling (402) the communication data to the network node (130) further indicates the call type initiated by the communication device (120).

14. A computer program (1080) comprising instructions, which when executed by a processor (1060), causes the processor to perform actions according to any of the claims 10-13.

15. A carrier (1090) comprising the computer program (1080) of claim 14, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

16. A network node (130) configured to handle Internet Protocol Multimedia Subsystem, IMS, communication between a gateway device (110), and a network node (130) in a communications network (100), wherein the gateway device (110) is arranged to be a stationary device which is capable of handling IMS services transparently for a communication device (120) connected to the gateway device (110), the network node (130) further being configured to:

- receive communication data from the gateway device (110), wherein the communication data is adapted to indicate any one out of:

A) device information of the gateway device (110), or

B) an identifier indicating how to retrieve the device information of the gateway device (110), wherein the device information of the gateway device (110) is adapted to indicate a device type of the gateway device (110), and adapted to specify whether the gateway device (110) communicates in the communications network (100) using a wireless or wired connection, and

- configure the network node (130) to adapt IMS services to be provided to the gateway device (110), based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

17. The network node (130) according to claim 16 further configured to:

- when the communication data indicates the identifier indicating how to retrieve the device information of the gateway device (110), obtain the device information of the gateway device (110) as indicated by the received communication data.

18. The network node (130) according to claim 17, further configured to obtain the device information of the gateway device (110) as indicated by the received communication data by further comprising requesting and receiving the device information from a Home Subscriber Server, HSS, or a Unified Data Management, UDM, associated with the network node (130).

19. The network node (130) according to any of claims 16-18 further configured to receive the communication data by receiving the communication data as part of any one or more out of:

- receiving a request for registration of the gateway device (110) with the network node (130),

- receiving a request for the network node (130) to start a communication session between the network node (130) and the gateway device (110).

20. The network node (130) according to claim 19, wherein any one or more out of: the received request for registration and the received request to start a communications session, are adapted to indicate an emergency call by the communication device (120).

21. The network node (130) according to any of claims 16-20, further configured to configure the network node (130) to adapt IMS services, by comprising any one or more out of:

- configuring a Terminating Access Domain Selection, T-ADS, for the gateway device (110), wherein configuring the T-ADS for the gateway device (110) is adapted to ensure that the gateway device (110) refrains from dynamically attaching and/or moving to another communications network.

22. The network node (130) according to any of claims 16-21, further configured to:

- determine which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

21. A gateway device (110) configured to handle Internet Protocol Multimedia Subsystem, IMS, communication between the gateway device (110), and a network node (130) in a communications network (100), wherein the gateway device (110) is arranged to be a stationary device which is capable of handling IMS services transparently for a communication device (120) connected to the gateway device (110), the gateway device (110) further being configured to:

- signal communication data to the network node (130), wherein the communication data is adapted to indicate any one out of:

A) device information of the gateway device (110), or

B) an identifier indicating how to retrieve the device information of the gateway device (110), wherein the device information of the gateway device (110) is adapted to indicate a device type of the gateway device (110), and adapted to specify whether the gateway device (110) communicates in the communications network (100) using a wireless or wired connection, and wherein the signaled communication data is adapted to configure the network node (130) to adapt IMS services to be provided to the gateway device (110), based on which IMS services are available for the indicated device type communicating using the specified wireless or wired connection.

22. The gateway device (110) according to claim 21 further configured to signal the communication data to the network node (130), by signalling the communications data as part of any one or more out of:

- requesting a registration of the gateway device (110) with the network node (130),

- requesting for the network node (130) to start a communication session between the network node (130) and the gateway device (110).

23. The gateway device (110) according to claim 22, wherein the any one or more out of the registration request, and the request to start the communication session, are adapted to indicate an emergency call by the communication device (120).

24. The gateway device (110) according to any of claims 21-23, further configured to:

- obtain from the communication device (120) a call indication indicating a call type initiated by the communication device (120), and wherein the communications data signaled to the network node (130), is adapted to indicate the call type initiated by the communication device (120).