TECHNICAL FIELD

The present disclosure relates generally to a first node and methods performed thereby for handling information pertaining to at least one of a device and a third node. The present disclosure also relates generally to a second node, and methods performed thereby for handling information pertaining to at least one of the device and the third node.

BACKGROUND

Computer systems in a communications network or system may comprise one or more network nodes. A node may comprise one or more processors which, together with computer program code may perform different functions and actions, a memory, a receiving port and a sending port. A node may be, for example, a server. Nodes may perform their functions entirely on the cloud.

The communications network may cover a geographical area which may be divided into cell areas, each cell area being served by another type of node, a network node in the Radio Access Network (RAN), radio network node or Transmission Point (TP), for example, an access node such as a Base Station (BS), e.g., a Radio Base Station (RBS), which sometimes may be referred to as e.g., Fifth Generation (5G) Node B (gNB), evolved Node B (“eNB”), “eNodeB”, “NodeB”, “B node”, or Base Transceiver Station (BTS), depending on the technology and terminology used. The base stations may be of different classes such as e.g., Wide Area Base Stations, Medium Range Base Stations, Local Area Base Stations and Home Base Stations, based on transmission power and thereby also cell size. A cell is the geographical area where radio coverage is provided by the base station at a base station site. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The communications network may also comprise network nodes which may serve receiving nodes, such as user equipments, with serving beams.

User Equipments (UEs) within the communications network may be e.g., devices, wireless devices, stations (STAs), mobile terminals, wireless terminals, terminals, and/or Mobile Stations (MS). UEs may be understood to be enabled to communicate wirelessly in a cellular communications network or wireless communication network, sometimes also referred to as a cellular radio system, cellular system, or cellular network. The communication may be performed e.g., between two UEs, between a wireless device and a regular telephone and/or between a wireless device and a server via a Radio Access Network (RAN) and possibly one or more core networks, comprised within the wireless communications network. UEs may further be referred to as mobile telephones, cellular telephones, laptops, or tablets with wireless capability, just to mention some further examples. The UEs in the present context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or vehiclemounted mobile devices, enabled to communicate voice and/or data, via the RAN, with another entity, such as another terminal or a server.

In 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), base stations, which may be referred to as eNodeBs or even eNBs, may be directly connected to one or more core networks. In the context of this disclosure, the expression Downlink (DL) may be used for the transmission path from the base station to the user equipment. The expression Uplink (UL) may be used for the transmission path in the opposite direction i.e. , from the wireless device to the base station.

The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a New Radio Interface called Next Generation Radio or New Radio (NR) or Fifth Generation (5G)-Universal Terrestrial Radio Access (UTRA), as well as a 5G Packet Core Network, which may be referred to as 5G Core Network (5GC), abbreviated as 5GC.

Internet Protocol Multimedia Subsystem Centralized Services (ICS) may be understood to enable the use of the Internet Protocol Multimedia Subsystem (IMS) telephony service engine for originating and terminating services if a User Equipment (UE) is connected via a Long-Term Evolution (LTE) Packet Switched (PS) access network, connected using a Global System for Mobile communications (GSM)/Wideband Code Division Multiple Access (WCDMA) Circuit Switched (CS) access network, or connected via a 5G NR access network.

For terminating calls, the ICS may determine the access network that may be currently in use by a device to deliver the call via the correct access network, LTE PS, GSM/WCDMA CS, or 5G. During a terminating call establishment of Voice over Long Term Evolution (VoLTE), Voice over NR (VoNR) call and Evolved Packet System (EPS) Fallback, an IMS telephony service engine Service Centralization and Continuity Application Server (SCC AS) may need to determine the latest radio access location e.g., LTE PS, GSM/WCDMA CS or 5G of a callee and also the IMS voice over PS session support information, in order to route the terminating voice call to the correct radio access where the user equipment (UE) may be currently camping.

Depending on each telecommunications network radio coverage configuration, the UE may move among different Radio Access Technologies (RATs) while remaining registered in the IMS. The session establishment for VoLTE, VoNR and EPS Fallback may require MultiMedia Telephony (MMTel) service, which may be provided by the IMS. The UE may conduct the registration towards the IMS network upon UE power-on, and after a successful attachment towards the packet domain network LTE or NR, and optionally also when the UE may be in GSM/WCDMA. The UE and the IMS core network may then be required to follow the Session Initiated Protocol (SIP) registration procedures defined in 3GPP TS 24.229, v. 17.7.0. The IMS may be understood to only have the IMS Registration state of the UE to rely on, according to e.g., 3GPP TS 24.229, v. 17.7.0, while a UE leaving Long Term Evolution (LTE) or 5G NR coverage to Second Generation (2G)/Third Generation (3G) may not remove its IMS Registration. For this, the IMS SCO AS may perform Terminating Access Domain Selection (T-ADS) as defined in 3GPP TS 23.292, v. 17.0.0 and 23.401 , v. 17.5.0 and 3GPP TS 23.501 , v. 17.5.0, §5.16.3.3, §5.16.3.6 and 3GPP TS 23.502, v. 17.5.0, §4.2.2. The T-ADS function may be executed to determine the latest radio access location e.g., 2G/3G/4G/5G of the callee and also the IMS voice over PS session support information, in order to route the terminating voice call to the correct radio access where a device may be currently camping.

The T-ADS procedure may imply that the SCO AS may contact the Home Subscriber Server (HSS). By the function T-ADS Support, the HSS may then provide the necessary information to the SCC-AS for routing the call to the correct Access Network, in LTE PS, OS domains, or 5G. The SCC-AS may request the TADS information from the HSS using the Sh Interface. The HSS may contact the Home Location Register (HLR), the Mobility Management Entity (MME), the Unified Data Management (UDM) and an external database (s), e.g., a Centralized User Database (CUDB) and Cloud Core Data-Storage Manager (CCDM), to get information about the latest Radio Access Technology (RAT) type serving the UE and IMS voice over Packet Switched (PS) session support capability in order to route the mobile terminating call to the proper access. The T-ADS information may then be sent by the HSS as part of the Sh-Pull. The HSS may provide the following to the SCC-AS: the RAT type serving the device, and the IMS voice over PS session support information.

According to the foregoing, multiple components and/or functions may be understood to be involved in the T-ADS operation: HSS, HLR, External DB, UDM, SCC-AS, and the MME. Furthermore, multiple data objects are involved in the T-ADS operation: Circuit Switch and Packet Switch DabaBase (CSPS DB) hosting the 2G/3G subscriber data, EPS Database (DB) hosting the LTE subscriber data, the 5G DB hosting the 5G subscriber data and the IMS DB hosting the IMS subscriber data.

Figure 1 is a schematic signalling diagram depicting the mobile terminating VoNR Call flow including the T-ADS operation, according to the existing implementation. Particularly, the TADS information request procedure is depicted, which may be understood to be based on a new service based interface (SBI) between the UDM 11 and the HSS 12 referred to as User Data Interworking, Coexistence and Migration (UDICOM). As depicted in Figure 1, the TADS function procedure signalling flow comprises interaction among multiple nodes, that is, the SCC-AS 13, the HSS 12, the HLR 14, the MME 15, an External DB 16, represented in the Figure as “CUDB/CCDM”, the and the UDM 11. In step 1, an SCC-AS 13 may request the TADS information for a Mobile Station Integrated Services Digital Network (MSISDN) or an IMS Public User Identity (PUI) from the HSS 12. The HSS 12, may then request the T- ADS information, e.g., the RAT type serving the UE and IMS voice over PS session support from the HLR 14, the MME 15, or the UDM 11. According to a first alternative, in step 2, if the configured TADS mechanism is Mobile Application Part (MAP), the HSS 12 may try to obtain the General Packet Radio Service (GPRS) Location Information using the MAP-ANY- TIM E-INTERROGATION (ATI) Mobile Application Part version 3 (MAPv3) operation from the HLR 14. In step 3, the HLR 14 may use the MAP-ANY-TIME-INTERROGATION Answer message to answer to the HSS 12. According to a second alternative, in step 4, if the configured TADS mechanism is DATABASE, the HSS 12 may try to obtain the General Packet Radio Service (GPRS) Location Information directly from the CS/PS database stored in an external database, by sending a Lightweight Directory Access Protocol (LDAP)Search 3G location. In step 5, HSS 12 may receive a LDAP response from the External DB 16. If the user is not located in a GPRS access Network, it may be located in LTE. In Steps 6, 8 and 10, the HSS 12 may send three LDAP requests to the External DB 16, specifically, towards the EPS DB, towards 3 different data objects. In Step 6, the HSS 12 may send a first LDAP request to check if the user exists or not with an LDAP Search (EpsStalnf). In Step 7, the HSS 12 may receive the answer to the request in step 6 as an LDAP Success. In Step 8, the HSS 12 may send a second LDAP request to retrieve the International Mobile Subscriber Identity (IMSI)Aux, in case IMSI Changeover may apply to the UE, or IMSI for the user, and check it may be matched with the one from the Subscription Data Access (SDA) if present. To do this, the HSS 12 may send an LDAP Search (mscld). In Step 9, the HSS 12 may receive the answer to the request in step 8 as an LDAP Success. In Step 9, the HSS 12 may send a third LDAP request to retrieve the mobility information, for example, location state, address of the MME 15, realm of the MME 15, etc. To do this, the HSS 12 may send an LDAP Search (EpsDynlnf). In Step 11 , the HSS 12 may receive the answer to the request in step 10 as an LDAP Success. Steps 12 and 13 are optional and may depend on the T-ADS information obtained from the EPS DB on steps from 6 to 11. In Step 12, if the T-ADS information is still not available to response, then the HSS 12 may send an Insert-Subscriber-Data-Request (I DR) to the MME 15 to retrieve the T-ADS information. Currently, a single registration may be assumed by HSS 12. For more information on the interface between the HSS 12 and the MME 15, see 3GPP TS 29.272, v. 17.3.0, HSS S6a/S6d Interface. It may be noted that there is an existing optimization to skip the IDR. In step 13, the MME 15 may answer the request from the HSS 12 with the current location information. In step 14, the HSS 12 may fetch the TADS information from the UDM 11 node using the Hypertext Transfer Protocol (HTTP)/REST Application Programming Interface (API) if the user is not located in a GPRS access Network nor in LTE and the HSS 12 may support the 5G voice function. Particularly, the HSS 12 may send a GET/nudm-mt/v1/imsi-XXX?field=tadsinfo request to the UDM 11. In Step 15, the UDM may send a GET am-data message to the UDR 17, which the UDR 17 may respond to with a 200 OK message in Step 16. In Step 17, the UDM 11 may respond to the HSS 12 with a 200 OK message. Finally, in Step 18, the HSS 12 may then provide a User-Data-Answer (UDA) to the SCC-AS 13.

Figure 2 shows, for the existing methods for the T-ADS signalling flow, the interaction of all involved nodes with the external databases. The T-ADS procedure may be as the follows. In Step 1, the SCC-AS 13 sends a User Data Request for T-ADS information to the HSS 12 with the User Identity and optionally the UserName. In Step 2, the HSS 12 requests location data from the CSPS access using one of the following options: (a+b) or c . In Step 2a, the HSS 12 sends an Any Time Interrogation (ATI) request to the HLR 14 to retrieve the Serving GPRS Support Node (SGSN) number. At reception of this request, in Step 2b, the HLR 14 may send a LDAP query to the External Database 21 to obtain the subscriber location from the database objects of the CSPS 22 of the HLR 14. Once it may have obtained the information, the HLR 14 may include the SGSN number into an ATI response and send it to the HSS 12. In Step 2c, the HSS 12 may send the LDAP query to External DB 21 to obtain the subscriber location from the data objects of the HLR 14, according to an enhancement. In Step 3, if there is no SGSN number available in the ATI response, in Step 3a, the HSS 12 may send 3 LDAP requests to the External Database 21 , specifically, towards the EPS DB 23, towards 3 different data objects: i) to check the user exists or not, ii) to retrieve the International Mobile Subscriber Identity (IMSI)Aux, in case IMSI Changeover may apply to the UE, or IMSI for the user, and check it may be matched with the one from the Subscription Data Access (SDA) if present, and iii) to retrieve the mobility information, for example, location state, address of the MME 15, realm of the MME 15, etc. ... In Step 3b, if the T-ADS information is still not available to response, then the HSS 12 may send an Insert Subscriber Data request to the MME 15 to retrieve the T-ADS information, currently, a single registration may be assumed by HSS 12. In Step 4, the HSS 12 may fetch the TADS information from the UDM 15 node using the HTTP/REST API if the user is not located in a GPRS access Network or LTE and the HSS 12 support 5G voice function. In Step 5, the UDM 15 may query the 5G DB 24 to extract the subscriber TADSinfo. In Step 6, the HSS 12 may respond to the SCC-AS 13 with a User Data Answer with the T-ADS information. This step 6 may be understood to be performed if the T-ADS information is available at step 3, 4 and 5.

According to the foregoing, the T-ADS operation signalling flow may therefore be understood to require interaction among multiple functions, nodes and also interaction towards different data objects within the external database(s) in order to fetch the RAT type serving the UE and the IMS voice over PS session support information. Also, the procedure to fetch and validate the data from the different data objects may be understood to be taking place within the overall call setup procedure and, hence, it may be understood to represent a delay portion of the total call setup time measurement. The standard T-ADS operation signalling flow may contribute to an average delay budget between 100-300 ms into the total call setup time (CST).

The CST measurement points are between originating an outgoing Session Initiation Protocol (SIP) INVITE, and the incoming 180 ringing towards the originating UE.

The delay budget associated with the TADS signalling may be understood to be too long, which implies a degrading factor to the overall Call setup time Key Performance Indicator (KPI).

While some existing methods provide an enhancement to enforce the T-ADS procedure without contacting the HLR, or the MME under certain conditions. However, despite these enhancements, there are still LDAP signalling interactions in any case between HSS and the external database(s) which contribute to the overall T-ADS latency.

SUMMARY

As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed.

It is an object of embodiments herein to significantly decrease the delay incurred by the existing methods of T-ADS operation.

According to the foregoing, it is an object of embodiments herein to improve the handling of information pertaining to at least one of a device and a third node in a communications system.

According to a first aspect of embodiments herein, the object is achieved by a computer- implemented method, performed by a first node. The method is for handling information pertaining to at least one of a device and a third node. The first node operates in a communications system. The first node receives a first indication from another node operating in the communications system. The first indication indicates a request to receive information pertaining to at least one of the device and the third node operating in the communications system. The information is indicated by first information stored in one first memory storage, of a plurality of first memory storages. Each of the first memory storages in the plurality is different and independent. The first node also sends, based on the received first indication, a second indication to a second node operating in the communications system. The second indication requests second information indicating the information requested by the another node. The second information has been, prior to receiving the first indication: i) created as an indicator of the first information stored in any of the first memory storages, ii) stored in a single second memory storage, the second memory storage being different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages. The first node further receives, in response to the sent second indication, a third indication from the second node. The third indication indicates the second information. The first node then sends, in response to the received first indication, a fourth indication to the another node. The fourth indication indicates the requested information based on the retrieved second information.

According to a second aspect of embodiments herein, the object is achieved by a computer-implemented method, performed by the second node. The method is for handling information pertaining to at least one of the device and the third node. The second node operates in the communications system. The second node receives the second indication from the first node operating in the communications system. The second indication requests the second information indicating the information pertaining to the at least one of the device and the third node operating in the communications system. The information is indicated by the first information stored in the one first memory storage, of the plurality of first memory storages. Each of the first memory storages in the plurality is different and independent. The second information has been, prior to receiving the second indication: i) created as an indicator of the first information stored in any of the first memory storages, ii) stored in the single second memory storage, the second memory storage being different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages. The second node also sends, in response to the received second indication, the third indication to the first node. The third indication indicates the second information.

According to a third aspect of embodiments herein, the object is achieved by the first node, for handling the information pertaining to the at least one of the device and the third node. The first node is configured to operate in the communications system. The first node is further configured to receive the first indication from the another node configured to operate in the communications system. The first indication is configured to indicate the request to receive the information pertaining to at least one of the device and the third node configured to operate in the communications system. The information is configured to be indicated by the first information configured to be stored in the one first memory storage, of the plurality of first memory storages. Each of the first memory storages in the plurality is configured to be different and independent. The first node is further configured to send, based on the first indication configured to be received, the second indication to the second node configured to operate in the communications system. The second indication is configured to request the second information configured to indicate the information configured to be requested by the another node. The second information is configured to have been, prior to receiving the first indication: i) created as the indicator of the first information configured to be stored in any of the first memory storages, ii) stored in the single second memory storage, the second memory storage being configured to be different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages. The first node is further configured to receive, in response to the second indication configured to be sent, the third indication from the second node. The third indication is configured to indicate the second information. The first node is further configured to send, in response to the first indication being configured to be received, the fourth indication to the another node. The fourth indication is configured to indicate the information configured to be requested based on the second information configured to be retrieved.

According to a fourth aspect of embodiments herein, the object is achieved by the second node, for handling the information pertaining to the at least one of the device and the third node. The second node is configured to operate in the communications system. The second node is further configured to receive the second indication from the first node configured to operate in the communications system. The second indication is configured to request the second information indicating the information pertaining to at least one of the device and the third node operating in the communications system. The information is configured to be indicated by the first information configured to be stored in the one first memory storage, of the plurality of first memory storages. Each of the first memory storages in the plurality is configured to be different and independent. The second information is configured to have been, prior to receiving the second indication: i) created as the indicator of the first information configured to be stored in any of the first memory storages, ii) stored in the single second memory storage, the second memory storage being configured to be different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages. The second node is further configured to send, in response to the second indication configured to be received, the third indication to the first node. The third indication is configured to indicate the second information. By receiving the first indication, the first node may trigger fetching of the information requested by the another node.

By sending the second indication, the first node may be enabled to, with reduced signalling, retrieve the information requested by the another node. This may be understood to shorten and simplify the retrieval process. The new centralized second information may be understood to enable a significant reduction in the number of queries to gather the information, which may be e.g., tadsinfo data.

By receiving the third indication, the first node may be enabled to then provide the information requested to the another node, in response to the received first indication.

By sending the fourth indication to the another node, the first node may be enabled to provide the requested information to the another node.

The signalling associated to the data searching and data fetching that, in existing methods, may be executed by multiple queries and multiple nodes interactions, may be enabled to be significantly reduced by the new enhanced signalling flow. Furthermore, by having created, or updated the second information prior to receiving the first indication, a big portion of the data searching procedure may now be able to be executed ahead of time.

For example, in the particular embodiments wherein the method may be performed during a T-ADS procedure, a big portion of the data searching procedure may now be able to be executed outside the actual T-ADS operation execution, and hence may be understood to not represent a contribution delay for the overall procedure, e.g., the overall call setup time. This may be understood as an advantage compared with the existing methods, wherein all the searching and data fetch procedure may be understood to be imbedded in the TADS operation, and hence represents a contribution delay into the overall call setup time.

Embodiments herein may enable to maintain the same TADS information accuracy managed by the existing methods, while enabling to significantly decrease the TADS operation delay budget from current 100-300 ms range to below 70 ms.

The delay reduction may be achieved by retrieving the TADSinfo data from multiple data objects and relocating it into a single data object rather than having the data scattered across multiple data objects in the external database(s) as it may be done in existing methods.

A consolidation and centralization of TADSinfo data within a common data object may be understood to simplify the T-ADS operation which with the embodiments herein may require a maximum two queries towards one single data object in the second memory storage. BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

Figure 1 is a schematic diagram illustrating an example of a TADS information request procedure (II DICOM), according to existing methods.

Figure 2 is a schematic diagram illustrating another example of a TADS information request procedure (IIDICOM), according to existing methods.

Figure 3 is a schematic diagram illustrating a non-limiting example of a communications system, according to embodiments herein.

Figure 4 is a flowchart depicting embodiments of a method in a first node, according to embodiments herein.

Figure 5 is a flowchart depicting embodiments of a method in a second node, according to embodiments herein.

Figure 6 is a schematic diagram depicting a non-limiting example of signalling between nodes in a communications system, according to embodiments herein.

Figure 7 is a schematic diagram depicting another non-limiting example of signalling between nodes in a communications system, according to embodiments herein.

Figure 8 is a schematic diagram depicting yet another non-limiting example of signalling between nodes in a communications system, according to embodiments herein.

Figure 9 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a first node, according to embodiments herein.

Figure 10 is a schematic block diagram illustrating two non-limiting examples, a) and b), of a second node, according to embodiments herein.

DETAILED DESCRIPTION

Certain aspects of the present disclosure and their embodiments address one or more of the challenges identified with the existing methods and provide solutions to the challenges discussed.

Embodiments herein may be understood to aim to improve the call setup time, which may be understood to be one of the main key performance indicators (KPIs) for voice services over cellular networks such, as e.g., Voice over LTE (VoLTE), Voice over NR (VoNR) and EPS Fallback (EPS FB).

The improvement may be achieved by optimizing and significantly reducing the latency budget associated with the execution of the T-ADS procedure. As explained in the Background section, T-ADS may be understood to be one of the key functions and procedures to handle mobile terminating half calls when establishing Voice calls over Mobile networks. Embodiments herein may be understood to enhance the existing T-ADS procedure in order to reduce the latency, while still enabling to keep gathering the same TADSinfo response content and accuracy that may be provided when the standard current approach may be enforced.

The enhancement afforded by embodiments herein may be understood to avoid the multiple nodes interactions and data fetch from different data objects during establishment of a call setup.

Embodiments herein may be understood to relate in general to a centralization of storage of T-ADS information data and optimization of the signalling flow of the T-ADS procedure. More particularly, embodiments herein may be understood to provide a set of new mechanisms to reduce the delay associated to T-ADS, by enabling to fetch, consolidate and store the TADSinfo related to the last updated RAT type serving a device and the IMS voice over PS session support information in one common data object. By having the TADSinfo data stored and consolidated in a common database object, the number of signalling interaction for the T-ADS operation may be enabled to be significantly reduced. Furthermore, the mechanism to store and consolidated the TADSinfo data in a common database maybe executed prior to making the call, therefore, outside the call setup procedure. This may be understood to imply a reduction of the overall CST.

The embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which examples are shown. In this section, embodiments herein are illustrated by exemplary embodiments. It should be noted that these embodiments are not mutually exclusive. Components from one embodiment or example may be tacitly assumed to be present in another embodiment or example and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. All possible combinations are not described to simplify the description.

Figure 3 depicts two non-limiting examples, in panels “a” and “b”, respectively, of a communications system 100, in which embodiments herein may be implemented. In some example implementations, such as that depicted in the non-limiting example of Figure 3a, the communications system 100 may be a computer network. In other example implementations, such as that depicted in the non-limiting example of Figure 3b, the communications system 100 may be implemented in a telecommunications system, sometimes also referred to as a telecommunications network, cellular radio system, cellular network, or wireless communications system. In some examples, the telecommunications system may comprise network nodes which may serve receiving nodes, such as wireless devices, with serving beams. The communications system 100 may for example be a network such as a 5G system, or a newer system supporting similar functionality. The telecommunications system may also support other technologies, such as a Long-Term Evolution (LTE) network, e.g., LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), or LTE operating in an unlicensed band, Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM/Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising of any combination of Radio Access Technologies (RATs) such as e.g. Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 3 ^rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network/s (WLAN) or WiFi network/s, Worldwide Interoperability for Microwave Access (WiMax), IEEE 802.15.4-based low-power short-range networks such as Ipv6 over Low-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system. The telecommunications system may for example support a Low Power Wide Area Network (LPWAN). LPWAN technologies may comprise Long Range physical layer protocol (LoRa), Haystack, SigFox, LTE-M, and Narrow-Band loT (NB-loT).

The communications system 100 may comprise a plurality of nodes, whereof a first node 111, a second node 112, a third node 113 and a another node 114 are depicted in Figure 3. It may be understood that the communications system 100 may comprise more nodes than those represented on Figure 3.

Any of the first node 111, the second node 112, the third node 113 and the another node 114 may be understood, respectively, as a first computer system, a second computer system, a third computer system and a fourth computer system. In some examples, any of the first node 111, the second node 112, the third node 113 and the another node 114 may be implemented as a standalone server in e.g., a host computer in the cloud 115, as depicted in the non-limiting example depicted in panel b) of Figure 3. Any of the first node 111 , the second node 112, the third node 113 and the another node 114 may in some examples be a distributed node or distributed server, with some of their respective functions being implemented locally, e.g., by a client manager, and some of its functions implemented in the cloud 115, by e.g., a server manager. Yet in other examples, any of the first node 111, the second node 112, the third node 113 and the another node 114 may also be implemented as processing resources in a server farm.

Any of the first node 111, the second node 112, the third node 113 and the another node 114 may be independent and separate nodes. In other examples, any of the first node 111, the second node 112, the third node 113 and the another node 114 may be co-localized or be the same node.

In some embodiments, the some examples of embodiments herein, the first node 111 may be understood as a node that may have a capability to handle subscriber data by managing a storage where the data may be stored and may have a capability to provide such data to other entities operating in the communications system 100, such as the another node 114. In the non-limiting example of Figure 3, the first node 111 is an HSS.

The second node 112 may be a node that may have a capability to manage a database comprising subscriber data and provide such data to the first node 111. As depicted in the non-limiting example of Figure 3, a non-limiting example of the second node 112 may be a database of an IMS telephony service engine.

The third node 113 may be a node having a capability to manage service of an application to a wireless device. In the non-limiting example depicted in panel b) of Figure 3, the third node 113 is depicted as being the a radio network node, e.g., a base station. However, the third node 113 may be another node, such as a core network node.

In some embodiments, the another node 114 may be a node having a capability to facilitate centralization of service and coordination of handover procedures within the communications system 100. In some particular examples, the another node 114 may be an SCC-AS.

The communications system may comprise a plurality 120 of first memory storages. Each of the first memory storages may be e.g., a database.

In some embodiments, the plurality 120 of first memory storages may comprise at least two of: a first memory storage 121, another first memory storage 122 and a further first memory storage 123. Each of the first memory storages in the plurality 120 is different and independent.

In some embodiments, the first memory storage 121 may store the information pertaining to a first RAT, the another first memory storage 122 may store the information pertaining to a second RAT and the further first memory storage 123 may store the information pertaining to a third RAT.

In some particular embodiments, the plurality 120 of first memory storages may comprise at least two of: the first memory storage 121 storing the information pertaining to the first RAT, wherein the first RAT may be one of 2G and 3G, the another first memory storage 122 storing the information pertaining to the second RAT, wherein the second RAT may be 4G, and the further first memory storage 123 storing the information pertaining to the third RAT, wherein the third RAT may be 5G. The first memory storage 121 may be, e.g., a Circuit Switch and Packet Switch (CPSP)

DB.

The another first memory storage 122 may be, e.g., an EPS DB.

The further first memory storage 123 may be, e.g., a 5G DB.

The communications system 100 further comprises a second memory storage 124, the second memory storage 124 is different and independent from any of the first memory storages. The second memory storage 124 may be, e.g., an IMS DB.

In some examples, the second node 112 may be co-localized or be the same as the second memory storage 124.

The communications system 100 may comprise a plurality of devices, of which a device 130 is represented in Figure 3. The device 130 may be also known as e.g., user equipment (UE), a wireless device, mobile terminal, wireless terminal and/or mobile station, mobile telephone, cellular telephone, or laptop with wireless capability, an Internet of Things (loT) device, a sensor, or a Customer Premises Equipment (CPE), just to mention some further examples. The device 130 in the present context may be, for example, portable, pocket- storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and/or data, via a RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, a Machine-to-Machine (M2M) device, an Internet of Things (loT) device, e.g., a sensor or a camera, a device equipped with a wireless interface, such as a printer or a file storage device, modem, Laptop Embedded Equipped (LEE), Laptop Mounted Equipment (LME), USB dongles, CPE or any other radio network unit capable of communicating over a radio link in the communications system 100. The device 130 may be wireless, i.e., it may be enabled to communicate wirelessly in the communications system 100 and, in some particular examples, may be able support beamforming transmission. The communication may be performed e.g., between two devices, between a device and a radio network node, and/or between a device and a server. The communication may be performed e.g., via a RAN and possibly one or more core networks, comprised, respectively, within the communications system 100.

The communications system 100 may comprise a plurality of radio network nodes, whereof a radio network node 140 is depicted in Figure 3b. The radio network node 140 may typically be a base station or Transmission Point (TP), or any other network unit capable to serve a wireless device or a machine type node in the communications system 100. The radio network node 140 may be e.g., a 5G gNB, a 4G eNB, or a radio network node in an alternative 5G radio access technology, e.g., fixed or WiFi. The radio network node 140 may be e.g., a Wide Area Base Station, Medium Range Base Station, Local Area Base Station and Home Base Station, based on transmission power and thereby also coverage size. The radio network node 140 may be a stationary relay node or a mobile relay node. The radio network node 140 may support one or several communication technologies, and its name may depend on the technology and terminology used. The radio network node 140 may be directly connected to one or more networks and/or one or more core networks.

The communications system 100 may cover a geographical area which may be divided into cell areas, wherein each cell area may be served by a radio network node, although, one radio network node may serve one or several cells.

The first node 111 may communicate with the second node 112 over a first link 151 , e.g., a radio link or a wired link. The first node 11 may communicate with the another node 114 over a second link 152, e.g., a radio link or a wired link. The first node 111 may communicate with the first memory storage 121 over a third link 153, e.g., a radio link or a wired link. The first node 111 may communicate with the another first memory storage 122 over a fourth link 154, e.g., a radio link or a wired link. The first node 111 may communicate with the further first memory storage 123 over a fifth link 155, e.g., a radio link or a wired link. The another node 114 may communicate, directly or indirectly, with the device 130 or the third node 113 over a sixth link 156, e.g., a radio link or a wired link. The another node 114 may communicate with the radio network node 140 over a seventh link 157, e.g., a radio link or a wired link. The radio network node 140 may communicate with the device 130 over an eighth link 158, e.g., a radio link.

Any of the first link 151, the second link 152, the third link 153, the fourth link 154, the fifth link 155, the sixth link 156, the seventh link 157 and/or the eighth link 158 may be a direct link or it may go via one or more computer systems or one or more core networks in the communications system 100, or it may go via an optional intermediate network. The intermediate network may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network, if any, may be a backbone network or the Internet, which is not shown in Figure 3.

In general, the usage of “first”, “second”, “third”, “fourth”, “fifth”, “sixth”, “seventh”, “eighth” and/or “ninth” herein may be understood to be an arbitrary way to denote different elements or entities and may be understood to not confer a cumulative or chronological character to the nouns these adjectives modify.

Although terminology from Long Term Evolution (LTE)/5G has been used in this disclosure to exemplify the embodiments herein, this should not be seen as limiting the scope of the embodiments herein to only the aforementioned system. Other wireless systems supporting similar or equivalent functionality may also benefit from exploiting the ideas covered within this disclosure. In future telecommunication networks, e.g., in the sixth generation (6G), the terms used herein may need to be reinterpreted in view of possible terminology changes in future technologies.

Embodiments of a computer-implemented method, performed by the first node 111, will now be described with reference to the flowchart depicted in Figure 4. The method may be understood to be for handling information pertaining to at least one of the device 130 and the third node 113. The first node 111 operates in the communications system 100.

Several embodiments are comprised herein. The method may comprise one or more of the following actions. In some embodiments, all the actions may be performed. In some embodiments, two or more actions may be performed. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. A non-limiting example of the method performed by the first node 111 is depicted in Figure 4.

In Figure 4, optional actions are represented with dashed lines.

Action 401

During the course of operations of the communications system 100, the first node 111 may receive, as will be described later in regard to Action 403, a first indication from another node 114 operating in the communications system 100.

In some embodiments, the method may be performed during a T-ADS procedure. In some embodiments, the first node 111 may be an HSS. The another node 114 may be an SCC AS.

The first indication

The first indication may indicate a request to receive information pertaining to at least one of the device 130 and the third node 113 operating in the communications system 100. That is, the first indication may be understood as a request to receive information regarding, e.g., a UE, a radio network node or a different node, or both.

In some particular embodiments, the first indication may be, e.g., a Sh-Pull message, e.g., including an IMS Public User Identity (IMPU), Data Requested (DR): T-ADS, comprised in a User Data Request (UDR) message.

In some examples, the first indication may further comprise an identifier, User Identity, of the at least one of the device 130 and the third node 113 and, optionally, a Username of the device 130. The information

The information may be dynamic data, subject to change over time. In some embodiments, the information may indicate a RAT serving, respectively, the at least one of the device 130 and the third node 113. The RAT may be, for example, one of 2G, 3G, 4G or 5G.

In some examples, the information may particularly request the RAT type serving the device 130, and IMS voice over PS session support information.

In some particular embodiments, the information may be T-ADS information, e.g., Tadsinfo.

The first information

The information may be indicated by first information. In other words, a first type of information that the first node 111 may know it may correspond, or have the answer, to the information requested by the another node 114. For example, the first information may correspond to a particular data structure, e.g., a data object, which may indicate the information requested by the another node 114. Since the name of the data structure may vary based on RAT, which is unknown to the another node 114, the another node 114 requests the information in a generic way, and the first node 111 may then be tasked with fetching the particular data structure, the first information, that may have the answer the another node 114 may be looking for, hence the use of information and first information. The information may be in the request from the another node 114, and it may be indicated by the first information.

The first information may be, for example, location information of the at least one of the device 130 and the third node 113.

The first information may be stored in one first memory storage, of the plurality 120 of first memory storages. Each of the first memory storages in the plurality 120 is different and independent.

In some embodiments, the plurality 120 of first memory storages may comprise at least two of: a first memory storage 121 storing the information pertaining to a first RAT, another first memory storage 122 storing the information pertaining to a second RAT and a further first memory storage 123 storing the information pertaining to a third RAT.

In some particular embodiments, the plurality 120 of first memory storages may comprise at least two of: the first memory storage 121 storing the information pertaining to the first RAT, wherein the first RAT may be one of 2G and 3G, the another first memory storage 122 storing the information pertaining to the second RAT, wherein the second RAT may be 4G, and the further first memory storage 123 storing the information pertaining to the third RAT, wherein the third RAT may be 5G.

In some embodiments, at least one of the first memory storages may comprise support information regarding the IMS over PS session. In this Action 401 , the first node 111 may receive, prior to receiving the first indication just described, and based on a previous subscription by the first node 111 , a first prior indication. The first node 111 may receive the first prior indication from at least one first memory storage in the plurality 120 first memory storages.

The first prior indication

The first prior indication may indicate the first information.

The first prior indication may indicate the first information as an update to the information pertaining to the at least one of the device 130 and the third node 113.

The first prior indication may be, for example, a location update, such as e.g., a SOAP Notification or a REST Notification 5G location update and IMS voice over PS session support information, for example, supported, not supported or unknown.

The receiving of the first indication may be performed e.g., via any of the third link 153, the fourth link 154 and the fifth link 155.

The previous subscription

The first prior indication may be based on a mechanism to allow the first node 111 to collect the available latest information regarding the at least one of the device 130 and the third node 113, e.g., the latest access Location of the at least one of the device 130 and the third node 113. The first prior indication may be a notification received for the update to the information. The notification may be received in response to the prior subscription by the first node 111. The prior subscription may be towards each of the first memory storages in the plurality 120 of first memory storages to gather notification about modifications in the information, and therefore changes as well in the first information, e.g., user location data.

That is, according to embodiments herein, the first node 111 may have previously subscribed to receive updates to the information. For example, the first node 111 may have request to be notified of any change to the location of the at least one of the device 130 and the third node 113.

After any update to the location of at least one of the device 130 and the third node 113 in a 2G/3G network, the first memory storage 121 may send the first prior indication, e.g., as a SOAP Notification, to the first node 111 with the first information as subscriber location data in the 2G/3G network.

After any update performed to the subscriber location in a 4G network, the another first memory storage 122 may sends the first prior indication, e.g., as a SOAP notification to the first node 111 with the first information as subscriber location data in the 4G network and IMS voice over PS session support information, e.g., supported, not supported or unknown.

After any update performed to the subscriber location in a 5G network, the further first memory storage 123 may send the first prior indication, e.g., as a REST Notification 5G location update and IMS voice over PS session support information, e.g., supported, not supported or unknown.

Example

In the embodiments wherein the first node 111 may be an HSS, embodiments herein may take advantage of an existing mechanism which may allow the HLR, the HSS and the UDM to update in real time the external database(s) CSPS DB hosting 2G/3G subscriber data, EPS DB hosting the LTE subscriber data, 5G DB hosting the 5G subscriber data, with the latest access radio location of a UE upon initial attach, de-attach towards any access and upon mobility scenarios, such as e.g., 4G from/to 2G/3G, and 5G from/to 4G/3G/2G. Such mechanism already exists; however, these updates may be understood to be currently stored in the above mentioned different data objects within the external database(s).

In the embodiments wherein the first node 111 may be an HSS, embodiments herein may further take advantage of another existing mechanism which may allow the HSS to obtain notifications from the external database(s) about latest available data of a subscriber about the RAT type serving the UE and the IMS voice over PS session support information. Such mechanism may be understood to already exist and it may be based on an external database notification function, e.g., CUDB Notification and CCDM Notification, that may allow the HSS to subscribe towards the external database to gather notification about modifications in the user location data among other attributes.

After any update performed by an HLR about the subscriber location in a 2G/3G network, the first memory storage 121, e.g., a CPSP DB, may send the first prior indication, e.g., as a SOAP Notification to the first node 111 with the subscriber location data in the 2G/3G network.

After any update performed by an HSS about the subscriber location in a 4G network, the another first memory storage 122, e.g., an EPS DB, may send the first prior indication, e.g., as a SOAP notification to the first node 111 with the subscriber location data in the 4G network and the IMS voice over PS session support information , e.g., supported, not supported or unknown.

After any update performed by the UDM about the subscriber location in a 5G network, the further first memory storage 123, e.g., a 5G DB, may send the first prior indication, e.g., as a REST Notification 5G location update and the IMS voice over PS session support information, e.g., supported, not supported or unknown.

By receiving the first prior indication prior to receiving the first indication, the first node 111 may be made aware of any changes to the first information regarding at least one of the device 130 and the third node 113, as soon as they may take place. This may additionally enable the first node 111 to create an indication of the first information in a single memory storage, as will be described in Action 402, which may then enable the first node 111 to ultimately provide the requested information to the another node 114, in a manner involving a shorter latency and less signalling overhead than the existing methods.

In some embodiments, wherein the method may be performed during a T-ADS procedure, the receiving in this Action 401 of the first prior indication may be understood to be excluded from a call setup time measurement associated with the T-ADS selection procedure, thereby enabling that the call setup time may be advantageously shortened.

Action 402

In this Action 402, the first node 111 may create, or update, second information.

The second information may be, prior to receiving the first indication in Action 403: i) created as an indicator of the first information stored in any of the first memory storages, ii) stored in a single second memory storage 124, the second memory storage 124 being different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages .

The first node 111 may create or update the second information based on the received first prior indication in the second memory storage 124 prior to receiving the first indication.

In some embodiments, wherein the method may be performed during a T-ADS procedure, the receiving in Action 401 of the first prior indication and the creating or updating in this Action 402 of the second information may be excluded from a call setup time measurement associated with the T-ADS selection procedure, thereby enabling that the call setup time may be advantageously shortened.

The second information

The second information may be a new data object.

The common data object may be a dynamic object used by an SDA module to store dynamic data for each subscriber.

In this object, a new attribute may need to be defined, which may be referred to herein as “access tracker”, to store the information, e.g., TADS location information.

This common data object may be created in the subscriber data structure in the single second memory storage 124, e.g., the IMS DB, inside an external database. The second memory storage 124 may be the second node 112. In some embodiments, the second node 112 may be a database of an IMS telephony service engine. In particular examples, the single second memory storage 124 may be comprised in the same external database as the plurality 120 first memory storages. The second information, a new subscriber data object, may host the current, latest RAT type serving the at least one of the device 130 and the third node 113, and also the IMS voice over PS session support information.

In some embodiments, the second information may be a common data object comprised in a set of bits. That is, its structure may be a bit array. Any bit position may provide the information, e.g., about the subscriber location, on each network access and additionally if the homogeneous VoIP may be supported or not. With this structure, the first node 111 may be enabled to know which may be the location status of the at least one of the device 130 and the third node 113 and may send the proper RAT-Type value in the UDA message towards the another node 114.

The bit array structure may also allow to use different bit positions for future purpose, avoiding having to define new attributes in the object. That is, while a new attribute on the IMS DB may be defined according to embodiments herein, which may be understood to not be present in existing methods, that attribute may be able to handle different information. Several bits may be selected for different access networks and more bits may be available for future network access types, so that no new object may be needed when more access types may be available.

The first node 111 may create or update the second information in this Action 402 by sending an LDAP Modify message to the single second memory storage 124 indicating e.g., ('Sh Dynlnfo) Access-Tracker (Location and VoiP support).

In some particular embodiments, the second information may have a smaller size than the first information.

The set of bits may comprise a first subset of bits indicating a first type of second information, e.g., network location. The first subset of bits may comprise a first bit indicating a location of the at least one of the device 130 and the third node 113 in a 2G/3G network, wherein e.g., Location: bitO= 0 or 1. The first subset of bits may comprise a second bit indicating a location of the at least one of the device 130 and the third node 113 in a 4G network, wherein, e.g., Location: bit1 =0 or 1. The first subset of bits may comprise a third bit indicating a location of the at least one of the device 130 and the third node 113 in a 5G network, wherein, e.g., Location: bit2=0 or 1.

Within the first subset of bits, which may comprise three bits, a first value, e.g, 0, may indicate Not Located and a second value, e.g., 1, may indicate Located.

The set of bits may comprise a second subset of bits indicating a second type of second information, e.g., Homogeneous VoIP support. The second subset of bits may comprise a first pair of bits indicating a Homogeneous VoIP support of the at least one of the device 130 and the third node 113 in a 4G network, wherein, e.g., bit17&bit18 == 00,01 or 10. The second subset of bits may comprise a second pair of bits indicating a Homogeneous VoIP support of the at least one of the device 130 and the third node 113 in a 5G network, wherein, e.g., bit17&bit18 == 00,01 or 10.

Within the second subset of bits, a first value, e.g, 00, may indicate Unknown, a second value, e.g., 01, may indicate Not supported and a third value, e.g., 10, may indicate Supported. These options may be understood to not apply to the at least one of the device 130 and the third node 113 in a 2G or 3G network.

To perform this Action 402, the first node 111 may send an instruction to the second node 112, which may manage the second memory storage 124, for every first prior indication received. For example, after a 4G initial attach, the first node 111 may send an LDAP Modify (Sh Dynlnfo) Access Tracker (5G=9 and Homogeneous support=00), a LDAP Modify (Sh Dynlnfo) Access Tracker (4G=1 and Homogeneous support), and an LDAP Modify (Sh Dynlnfo) Access Tracker (3G=0).

By creating, or updating the second information in this Action 402, the first node 111 may be enabled to use a new mechanism which may allow the first node 111 to, upon reception of notifications obtained from the at least one first memory storage in the plurality 120 of first memory storages, then push and store this information back to the single second memory storage 124, e.g., an external database, inside the new common data object defined within the single second memory storage 124, e.g., an IMS DB. That is, into a centralized location.

Since the first node 111 may create or update the second information prior to receiving the first indication, the first node 111 may then, upon receiving the first indication, be able to fetch the information from a single place, the second memory storage 124 with a single signalling action, thereby being enabled to significantly reduce latency and signalling overhead involved in providing the information requested by the another node 114.

In the particular embodiments wherein the method may be performed during a T-ADS procedure, this Action 402 may be understood to provide a centralization mechanism of storage of T-ADS information data, that may imply a relocation of the tadsinfo data from three different independent data objects into one common data object. The centralization and storage of the tadsinfo data within a common data structure and common data object may the be understood to enable to speed up the searching and fetching of the data. Which may be understood to result in a T-ADS procedure enhanced mechanism with less signalling interaction and hence shorter T-ADS procedure execution delay and shorter call setup time. Action 403 may also imply a design of a new data object inside the IMS database (IMS DB) in the external database and also new design for the HSS to push the data obtained in Action 401 towards the external database. Action 403

In this Action 403, the first node 111 receives the first indication from the another node 114 operating in the communications system 100. As described earlier, the first indication indicates the request to receive the information pertaining to the at least one of a device 130 and the third node 113 operating in the communications system 100. The information is indicated by the first information stored in the one first memory storage, of the plurality 120 of first memory storages. As also explained earlier, each of the first memory storages in the plurality 120 is different and independent.

The receiving of the first indication in this Action 403 may be performed e.g., via the second link 152.

Receiving the first indication in this Action 403 may be understood to trigger the first node 111 to fetch the information requested by the another node 114, which fetching the first node 111 may initiate in the next Action 404.

Action 404

In this Action 404, the first node 111 sends, based on the received first indication, a second indication to a second node 112 operating in the communications system 100. The second indication requests the second information indicating the information requested by the another node 114. The second information, as was described in Action 402, has been, prior to receiving the first indication: i) created as the indicator of the first information stored in any of the first memory storages, ii) stored in the single second memory storage 124, the second memory storage 124 being different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages.

In some embodiments, the second node 112 may be a database of an IMS telephony service engine.

The second indication may be, for example, a request for Tadsinfo.

In some examples, if the identity received in the first indication from the another node 114 is an MSISDN, the first node 111 may need to fetch the IMPII used identity from the single second memory storage 124, otherwise this step may be omitted. The first node 111 may search in the second memory storage 124 for the second information, e.g., the new attribute access tracker, to fetch the information requested by the another node 114, e.g., subscriber location information and homogeneous VoIP support.

The sending of the second indication in this Action 404 may be performed e.g., via the first link 151. The sending of the second indication may be performed upon receiving the first indication. In a particular example of embodiments herein, in this Action 404, the first node 111 may, upon reception of a Sh-Pull/User-Data-Request for TADSinfo from the another node 114, then to fetch the RAT type serving the at least one of the device 130 and the third node 113 and the IMS voice over PS session support information data stored in the second memory storage 124 within the second information, e.g., the new data object called “access tracker” which may have been updated with the latest TADSinfo data in Action 402.

By sending the second indication in this Action 404, the first node 111 may be enabled to, with reduced signalling, retrieve the information requested by the another node 114. This may be understood to shorten and simplify the retrieval process. The new centralized second information may be understood to enable a significant reduction in the number of queries to gather the information, e.g., tadsinfo data. The signalling associated to the data searching and data fetching that, in existing methods, is executed by multiple queries and multiple nodes interactions may be enabled to be significantly reduced by the new enhanced signalling flow. Furthermore, by having created, or updated the second information prior to receiving the first indication, a big portion of the data searching procedure may now be able to be executed ahead of time, e.g., outside the actual T-ADS operation execution, and hence does not represent a contribution delay for the overall procedure, e.g., the overall call setup time.

In the particular embodiments wherein the method may be performed during a T-ADS procedure, this may be understood as an advantage compared with the existing methods, wherein all the searching and data fetch procedure may be understood to be imbedded in the TADS operation, and hence represents a contribution delay into the overall call setup time.

Action 405

In this Action 405, the first node 111 receives, in response to the sent second indication, a third indication from the second node 112. The third indication indicates the second information. That is, the external database may answer to the second indication sent by the first node 111. The third indication may be an LDAP Success.

In some examples, if the identities may have been requested, the second node 112 may send to HSS all user identities. The second node 112 may send to the first node 111 the requested second information as e.g., the “access tracker” data.

The receiving of the third indication in this Action 405 may be performed e.g., via the first link 151.

By receiving the third indication in this Action 405, the first node 111 may be enabled to then provide the information requested to the another node 114, in response to the received first indication. As explained in the previous Action 405, the first node 111 may be enabled to, with reduced signalling, retrieve the information requested by the another node 114. This may be understood to shorten and simplify the retrieval process. The new centralized second information may be understood to enable a significant reduction in the number of queries to gather the information, e.g., tadsinfo data.

Action 406

In this Action 406, the first node 111 sends, in response to the received first indication, a fourth indication to the another node 114. The fourth indication indicates the requested information based on the retrieved second information.

The fourth indication may be, for example, a Sh-Pull Resp User-Data-Answer (UDA). The first node 111 may be understood to answer to the first indication, e.g., the T-ADS information request, after analyzing the content of the new attribute access tracker and preparing the proper answer with the requested information. Embodiments herein enable a new mechanism which may enable the first node 111 to process the fetched information from the new created data object “access tracker” which was stored in Action 402, and parse it into an information, e.g., TADSinfo, response format towards the another node 114 using, e.g., the standard diameter protocol Sh-Pull Resp User-Data-Answer.

The sending of the fourth indication in this Action 406 may be performed e.g., via the second link 152.

By sending the fourth indication to the another node 114 in this Action 406, the first node 111 may be enabled to achieve the benefits outlined earlier, in relation to Action 402, Action 405 and Action 406.

Embodiments of a computer-implemented method performed by the second node 112, will now be described with reference to the flowchart depicted in Figure 5. The method may be understood to be for handling information pertaining to at least one of the device 130 and the third node 113. The second node 112 operates in the communications system 100.

The method may comprise the following actions. Several embodiments are comprised herein. In some embodiments, the method may comprise all the actions. In other embodiments, the method may comprise two or more actions. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. It should be noted that the examples herein are not mutually exclusive. Components from one example may be tacitly assumed to be present in another example and it will be obvious to a person skilled in the art how those components may be used in the other examples. In Figure 5, optional actions are depicted with dashed lines.

The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 111 and will thus not be repeated here to simplify the description. For example, in some embodiments, the first node 111 may be an HSS, the another node 114 may be an SCC-AS, and the second node 112 may be a database of an IMS telephony service engine.

Action 501

In this Action 501 , the second node 112 may receive, prior to receiving the second indication, a request from the first node 111 to create or update the second information in the second memory storage prior to receiving the second indication.

The receiving in this Action 501 may be performed e.g., via the first link 151.

Action 502

In this Action 502, the second node 112 may create, or update the second information in the second memory storage, based on the request from the first node 111. The creating or updating in this Action 502 may be performed prior to receiving the second indication.

In some embodiments, the second information may be the common data object comprised in the set of bits.

In some embodiments, the second information may have a smaller size than the first information.

In some embodiments wherein the method may be performed during a T-DAS procedure, the receiving in Action 501 of the second indication and the creating or updating in this Action 502 of the second information may be excluded from the call setup time measurement associated with the T-DAS procedure.

Action 503

In this Action 503, the second node 112 receives the second indication from the first node 111 operating in the communications system 100. The second indication requests the second information indicating the information pertaining to the at least one of the device 130 and the third node 113 operating in the communications system 100. The information is indicated by the first information stored in the one first memory storage, of the plurality 120 of first memory storages. Each of the first memory storages in the plurality 120 is different and independent. The second information has been, prior to receiving the second indication: i) created as the indicator of the first information stored in any of the first memory storages, ii) stored in the single second memory storage, the second memory storage being different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages. Action 504

In this Action 504, the second node 112 sends, in response to the received second indication, the third indication to the first node 111. The third indication indicates the second information.

In some embodiments, at least one of the following options may apply. According to a first option, the information may be dynamic data, subject to change over time. According to a second option, the information may indicate the RAT serving, respectively, the at least one of the device 130 and the third node 113. According to a third option, the method may be performed during a T-DAS procedure. According to a fourth option, the first node 111 may be an HSS. According to a fifth option, the second node 112 may be a database of an IMS telephony service engine. According to a sixth option, the another node 114 may be an SCC AS. According to a seventh option, the plurality 120 of first memory storages may comprise at least two of: the first memory storage 121 storing the information pertaining to a first RAT, the another first memory storage 122 storing the information pertaining to the second RAT and the further first memory storage 123 storing the information pertaining to the third RAT. According to an eighth option, the plurality 120 of first memory storages may comprises at least two of: the first memory storage 121 storing the information pertaining to the first RAT, wherein the first RAT may be one of 2G and 3G, the another first memory storage 122 storing the information pertaining to the second RAT, wherein the second RAT may be 4G, and the further first memory storage 123 storing the information pertaining to the third RAT, wherein the third RAT may be 5G. According to a ninth option, at least one of the first memory storages may comprise support information regarding IMS over PS session.

Next, non-limiting examples of a method embodiments of performed in the communications system 100, according to embodiments herein will be described in Figures 6- 9. To simplify the description of Figures 6-9, the information and procedures will be described as pertaining to the device 130. However, it may be understood that any reference to the device 130 may equally apply to the third node 113. To illustrate the embodiments herein, in the non-limiting examples depicted in Figures 6-9, the method may be understood to be performed performed during a T-ADS procedure.

Figure 6 is a first schematic signalling diagram depicting a non-limiting example of a method performed in the communications system 100, according to embodiments herein. The diagram furthest to the left illustrates what is referred to in the Figure as Step 1, corresponding to how the plurality 120 of first memory storages, an external database, may be updated, e.g., with location updates, upon attach, de-attach, mobility and/or purge procedures pertaining to the device 130. As described earlier, there is a mechanism in existing methods to allow the HLR, the HSS and the UDM to update in real time the external database(s) with the latest access radio location of the device 130 upon initial attach, de-attach towards 5G/4G/3G/2G access and upon mobility scenarios, e.g., 4G from/to 2G/3G, and 5G from/to 4G/3G/2G. Such mechanism already exists, however these updates may be understood to be currently stored in different data structure and data objects within the external database. 2G/3G data may be stored in the first memory storage 121, depicted as an CSPS DB, 4G data may be stored in the another first memory storage 122, depicted as an EPS DB, 5G data may be stored in the further first memory storage 123, depicted as an 5G DB and IMS data may be stored in the second memory storage 124, depicted as an IMS DB. Step 1 of Figure 6 describes the multiple scenarios about location update or cancellation signaling flow and the data stored in the DBs upon the standard procedures such as Registration, deregistration, Mobility or location purge. At 1 , a Mobile Switching Center (MSC) 601 may send an update location or purge Mobile Subscriber (MS) message to the HLR 602 to inform the HLR 602 about the subscriber attach or detach procedure into the 2G/3G networks. At 2, the HLR 602 may update the 2G/3G location status in the first memory storage 121 by sending an LDAP modify 3G location set or location clean message. At 3, an MME 603 may send an Update Location Request (ULR)/Notification Request (NOR) or Purge Request (PUR) message to the first node 111 , an HSS in this example, to inform the HSS 111 about the subscriber attach or detach procedure into the 4G network. At 4, the HSS 111 may update the 4G Location status in the another first memory storage 122, here an EPS DB, by sending an LDAP modify 4G location set or location clean. At 5, the HSS 111 may inform a UDM 604 about the attach procedure to cancel the 5G location in the UDM 604 by sending a Nudmirat4g5g_Cancel_AMF_Location message. It may trigger in the UDM the 5G DB location deletion. At 6A, the HSS 111 may inform the HLR 602 about the attach procedure performed by the subscriber in 4G to cancel the 3G subscriber location in the HLR by sending an ATI message. At 6B, the HLR 602 receives a notification from the another first memory storage 122 about the subscriber location set in 4G to cancel the 3G subscriber location in the HLR 602. At 7, the AMF 605 may send a Nudm_UECM_Registrarion or Nudm_UECM_Deregistration message to inform the UDM 604 about the subscriber attach or detach procedure into the 5G network. At 8, the UDM 604 may update the 5G Location status in the further first memory storage 123. At 9, the UDM 604 may inform the HSS 111 about the attach procedure performed by the subscriber in the 5G network to cancel the 4G subscriber location in the HSS 111 by sending an Nhss- iat4g5g_Cancel_EPC_Location to the HSS 111 . It may also trigger on the HSS 111 the 2G/3G location cancelation. The method may continue with Step 2, regarding the notification of updates towards the first node 111, e.g., the HSS, which may be understood to correspond to Action 401. A mechanism to allow the HSS to collect the available latest access location of a UE may be understood to already exist, and it may be based on External DB, e.g., CLIDB, Notification and UDR Notification functions that may allow the HSS to subscribe towards an external database to gather notification about modifications in the user location data. At 10, after any update performed by the HLR 602 about the subscriber location in the 2G/3G network, the first memory storage 121, e.g., the CPSP DB, may send the first prior indication, e.g., as a SOAP Notification to the first node 111 with the subscriber location data in the 2G/3G network. At 11, after any update performed by the HSS 111 about the subscriber location in a 4G network, the another first memory storage 122, e.g., an EPS DB, may send the first prior indication, e.g., as a SOAP notification to the first node 111 with the subscriber location data in the 4G network and the IMS voice over PS session support information , e.g., supported, not supported or unknown. At 12, after any update performed by the UDM 604 about the subscriber location in the 5G network, the further first memory storage 123, e.g., a 5G DB, may send the first prior indication to the first node 111 as a REST Notification 5G location update and the IMS voice over PS session support information, e.g., supported, not supported or unknown. The method may continue with Step 3, which may be understood to correspond to Action 402. At 13, the first node 111 may create or update the second information by sending an LDAP Modify message to the single second memory storage 124 indicating e.g., ('Sh Dynlnfo) Access-Tracker (Location and VoiP support).

Figure 7 is a signalling diagram depicting a continuation of the another non-limiting example of the method performed in the communications system 100, according to embodiments herein, depicted in Figure 6. Some of the elements in Figure 7 are the same as those in Figure 6, and their reference numbers are not depicted to avoid overcrowding the Figure. The example of Figure 7 depicts a scenario wherein the New T-ADS procedure enhancement may be executed as follows, in accordance with embodiments herein. At 1, the another node 114, here an SCC-AS, may send the first indication as a User Data Request (UDR) for T-ADS information with User Identity and optional User Name as a User Data Request (IMPU.DR: T-ADS). The first node 111 may receive the first indication in accordance with Action 403. At 2, the HSS 111 may, in accordance with Action 404, send the second indication to the second node 112, here the second memory storage 124, an external database IMS DB. The second indication may request the information, here Tadsinfo. At 2a, if the identity received in the UDR message from the SCC-AS 114 is an MSISDN, the HSS 111 may need to fetch the IMPU used identity from the second memory storage 124. Otherwise, this step may be omitted. At 2b, the first node 111 may search in the second memory storage 124 for the second information, e.g., the new attribute access tracker, to fetch the information requested by the another node 114, e.g., subscriber location information and homogeneous VoIP support. The second node 112 may receive the second indication in accordance with Action 503. At 3, the second node 112 may answer to the request from the first node 111. The third indication may be an LDAP Success. At 3a, if the identities may have been requested, the second node 112, in accordance with Action 504, may send to HSS all user identities. At 3b, the second node 112, in accordance with Action 504, may send to the first node 111 the requested second information as e.g., the “access tracker” data. At 4, the first node 111 may, in accordance with Action 406, answer the T-ADS information request from the another node 114 by sending the fourth indication as a User Data Answer (T-ADS), after analyzing the content of the new attribute access tracker and prepare the proper answer.

Figure 8 is a signalling diagram depicting some aspects of a non-limiting example of the method performed by the first node 111, according to embodiments herein. Particularly, Figure 8 depicts details of Step 3 as depicted in Figure 6, regarding the storage centralization of TADSinfo Data in the second memory storage 124, here the IMS DB. Some of the elements in Figure 8 are the same as those in Figure 6, and their reference numbers are not depicted to avoid overcrowding the Figure. As mentioned earlier, The common data object may be a dynamic object used by an SDA module to store dynamic data for each subscriber.

In this object, a new attribute may need to be defined, which may be referred to herein as “access tracker”, to store the information, e.g., TADS location information.

As explained earlier, the second information may be a common data object comprised in a set of bits. That is, its structure may be a bit array, so any bit position may provide the information, e.g., about the subscriber location, on each network access and, additionally, if the homogeneous VoIP may be supported or not. With this structure, the first node 111 may be enabled to know which may be the location status of the subscriber and may send the proper RAT-Type value in the UDA message towards the another node 114, there the SCC- AS. The bit array structure may also allow to use different bit positions for future purpose, avoiding having to define new attributes in the object. According to embodiments herein, Action 402 enables a new mechanism to allow the first node 111, e.g., the HSS, to, upon reception of the notifications in steps 10, 11 and 12 in Figure 6, then push and store this information back to the external database inside the new common data object, that is, the second information. This new subscriber data object may host the current, latest RAT type serving the device 130 and also the IMS voice over PS session support information. At 13, the first node 111 may create or update the second information, in accordance with Action 402, by sending an LDAP Modify message to the single second memory storage 124 indicating e.g., ('Sh Dynlnfo) Access-Tracker (Location and VoiP support). As described earlier, the set of bits 800 may comprise a first subset of bits 801 indicating a first type of second information, e.g., network location. The first subset of bits may comprise a first bit 802 indicating a location of the at least one of the device 130 and the third node 113 in a 2G/3G network, wherein e.g., Location: bitO= 0 or 1. The first subset of bits 801 may comprise a second bit 803 indicating a location of the at least one of the device 130 and the third node 113 in a 4G network, wherein, e.g., Location: bit1 =0 or 1. The first subset of bits 801 may comprise a third bit 804 indicating a location of the at least one of the device 130 and the third node 113 in a 5G network, wherein, e.g., Location: bit2=0 or 1. Within the first subset of bits 801 , which may comprise three bits, a first value, e.g, 0, may indicate Not Located and a second value, e.g., 1, may indicate Located. The set of bits 800 may comprise a second subset of bits 805 indicating a second type of second information, e.g., Homogeneous VoIP support. The second subset of bits 805 may comprise a first pair of bits 806 indicating a Homogeneous VoIP support of the at least one of the device 130 and the third node 113 in a 4G network, wherein, e.g., bit17&bit18 == 00,01 or 10. The second subset of bits 805 may comprise a second pair 807 of bits indicating a Homogeneous VoIP support of the at least one of the device 130 and the third node 113 in a 5G network, wherein, e.g., bit17&bit18 == 00,01 or 10.

Within the second subset of bits 805, a first value, e.g, 00, may indicate Unknown, a second value, e.g., 01, may indicate Not supported and a third value, e.g., 10, may indicate Supported. These options may be understood to not apply to the at least one of the device 130 and the third node 113 in a 2G or 3G network.

Certain embodiments disclosed herein may provide one or more of the following technical advantage(s), which may be summarized as follows.

As a first advantage, embodiments herein may be understood to enable the delay reduction to be achieved by retrieving the information, e.g., TADSinfo, data from multiple data objects and relocating it into a single data object rather than having the data scattered across multiple data objects in the external database(s) as it is done in the existing methods.

As a second advantage with regards to the T-ADS procedure, embodiments herein may be understood to enable to maintain the same T-ADS information accuracy managed by the existing methods, while enabling to significantly decrease the T-ADS operation delay budget from the current 100-300 ms range to below 70 ms.

A consolidation and centralization of information, e.g., TADSinfo, data within a common data object may enable to simplify the T-ADS operation which with embodiments herein may require a maximum of two queries towards one single data object in the external database.

Furthermore, with embodiments herein, the procedure to fetch and centralize the data used by the T-ADS operation may take place outside the call setup establishment procedure and hence may be understood to not be counted as a delay for the call setup time measurement.

Figure 9 depicts two different examples in panels a) and b), respectively, of the arrangement that the first node 111 may comprise to perform the method actions described above in relation to Figure 4 and/or Figures 6-8. In some embodiments, the first node 111 may comprise the following arrangement depicted in Figure 9a. The first node 111 may be understood to be for handling the information pertaining to the at least one of the device 130 and the third node 113. The first node 111 is configured to operate in the communications system 100.

Several embodiments are comprised herein. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. In Figure 9, optional boxes are indicated by dashed lines. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first node 111 and will thus not be repeated here. For example, in some embodiments, the first node 111 may be configured to be an HSS, the another node 114 may be configured to be an SCC-AS, and the second node 112 configured to be the database of an IMS telephony service engine.

The first node 111 is configured to, e.g., by means of a receiving unit 901 within the first node 111 configured to, receive the first indication from the another node 114 configured to operate in the communications system 100. The first indication is configured to indicate the request to receive the information pertaining to the at least one of the device 130 and the third node 113 configured to operate in the communications system 100. The information is configured to be indicated by the first information configured to be stored in the one first memory storage, of the plurality 120 of first memory storages. Each of the first memory storages in the plurality 120 is configured to be different and independent.

The first node 111 is also configured to, e.g., by means of a sending unit 902 within the first node 111 configured to, send, based on the first indication configured to be received, the second indication to the second node 112 configured to operate in the communications system 100. The second indication is configured to request the second information configured to indicate the information configured to be requested by the another node 114. The second information is configured to have been, prior to receiving the first indication: i) created as the indicator of the first information configured to be stored in any of the first memory storages, ii) stored in the single second memory storage 124, the second memory storage 124 being configured to be different and independent from any of the first memory storages, and iii) updated after, and according to, any update to the first information in any of the first memory storages.

In some embodiments, the first node 111 is further configured to, e.g., by means of the receiving unit 901 within the first node 111 configured to, receive, in response to the second indication configured to be sent, the third indication from the second node 112. The third indication is configured to indicate the second information.

In some embodiments, the first node 111 is further configured to, e.g., by means of the sending unit 902 within the first node 111 configured to, send, in response to the first indication being configured to be received, the fourth indication to the another node 114. The fourth indication is configured to indicate the information configured to be requested based on the second information configured to be retrieved.

In some embodiments, the first node 111 may be further configured to, e.g., by means of the receiving unit 901 within the first node 111 configured to, receive, prior to receiving the first indication, and based on the previous subscription by the first node 111 , the first prior indication from at least the one first memory storages in the plurality 120 first memory storages. The first prior indication is configured to indicate the first information as an update to the information pertaining to the at least one of the device 130 and the third node 113.

The first node 111 may be also configured to, e.g., by means of a creating unit 903 within the first node 111 configured to, create, or update, the second information based on the first prior indication configured to be received in the second memory storage 124 prior to receiving the first indication.

In some embodiments, at least one of the following options may apply: a) the information may be configured to be dynamic data, subject to change over time; b) the information may be configured to indicate the RAT, configured to serve, respectively, the at least one of the device 130 and the third node 113; c) the first node 111 may be configured to perform the actions it may be configured to perform during a T-ADS procedure; d) the first node 111 may be configured to be a HSS; e) the second node 112 may be configured to be the database of an IMS telephony service engine; f) the another node 114 may be configured to be an SCC AS; g) the plurality 120 of first memory storages may be configured to comprise at least two of: the first memory storage 121 configured to store the information pertaining to the first RAT, the another first memory storage 122 configured to store the information pertaining to the second RAT and the further first memory storage 123 configured to store the information pertaining to the third RAT; h) the plurality 120 of first memory storages may be configured to comprise at least two of: the first memory storage 121 configured to store the information pertaining to the first RAT, wherein the first RAT may be configured to be one of 2G and 3G, the another first memory storage 122 configured to store the information pertaining to the second RAT, wherein the second RAT may be configured to be 4G, and the further first memory storage 123 configured to store the information pertaining to the third RAT, wherein the third RAT may be configured to be 5G; and i) at least one of the first memory storages may be configured to comprise support information regarding an IMS over PS session.

In some embodiments, the first node 111 may be configured to perform its actions during a T-ADS procedure, and the receiving of the first prior indication and the creating or updating of the second information may be configured to be excluded from the call setup time measurement associated with the T-ADS procedure.

In some embodiments, the second information may be configured to be the common data object configured to be comprised in the set of bits.

In some embodiments, the second information may be configured to have the smaller size than the first information.

The embodiments herein may be implemented through one or more processors, such as a processor 904 in the first node 111 depicted in Figure 9, together with 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 first node 111. 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 first node 111.

The first node 111 may further comprise a memory 905 comprising one or more memory units. The memory 905 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the first node 111.

In some embodiments, the first node 111 may receive information from, e.g., the second node 112, the third node 113, the another node 114, the plurality 120 of first memory storages, the first memory storage 121, the another first memory storage 122, the further first memory storage 123, the second memory storage 124, the radio network node 140, the device 130 and/or another node through a receiving port 906. In some examples, the receiving port 906 may be, for example, connected to one or more antennas in the first node 111. In other embodiments, the first node 111 may receive information from another structure in the communications system 100 through the receiving port 906. Since the receiving port 906 may be in communication with the processor 904, the receiving port 906 may then send the received information to the processor 904. The receiving port 906 may also be configured to receive other information. The processor 904 in the first node 111 may be further configured to transmit or send information to e.g., the second node 112, the third node 113, the another node 114, the plurality 120 of first memory storages, the first memory storage 121 , the another first memory storage 122, the further first memory storage 123, the second memory storage 124, the radio network node 140, the device 130, another node and/or another structure in the communications system 100, through a sending port 907, which may be in communication with the processor 904, and the memory 905.

Those skilled in the art will also appreciate that any of the units 901-903 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 memory, that, when executed by the one or more processors such as the processor 904, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (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).

Any of the units 901-903 described above may be the processor 904 of the first node 111, or an application running on such processor.

Thus, the methods according to the embodiments described herein for the first node 111 may be respectively implemented by means of a computer program 908 product, comprising instructions, i.e. , software code portions, which, when executed on at least one processor 904, cause the at least one processor 904 to carry out the actions described herein, as performed by the first node 111. The computer program 908 product may be stored on a computer- readable storage medium 909. The computer-readable storage medium 909, having stored thereon the computer program 908, may comprise instructions which, when executed on at least one processor 904, cause the at least one processor 904 to carry out the actions described herein, as performed by the first node 111. In some embodiments, the computer- readable storage medium 909 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, a memory stick, or stored in the cloud space. In other embodiments, the computer program 908 product may be stored on a carrier containing the computer program, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 909, as described above.

The first node 111 may comprise an interface unit to facilitate communications between the first node 111 and other nodes or devices, e.g., the second node 112, the third node 113, the another node 114, the plurality 120 of first memory storages, the first memory storage 121, the another first memory storage 122, the further first memory storage 123, the second memory storage 124, the radio network node 140, the device 130, another node and/or another structure in the communications system 100. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the first node 111 may comprise the following arrangement depicted in Figure 9b. The first node 111 may comprise a processing circuitry 904, e.g., one or more processors such as the processor 904, in the first node 111 and the memory 905. The first node 111 may also comprise a radio circuitry 910, which may comprise e.g., the receiving port 906 and the sending port 907. The processing circuitry 904 may be configured to, or operable to, perform the method actions according to Figure 4 and/or Figures 6-8, in a similar manner as that described in relation to Figure 9a. The radio circuitry 910 may be configured to set up and maintain at least a wireless connection with the second node 112, the third node 113, the another node 114, the plurality 120 of first memory storages, the first memory storage 121, the another first memory storage 122, the further first memory storage 123, the second memory storage 124, the radio network node 140, the device 130, another node and/or another structure in the communications system 100.

Hence, embodiments herein also relate to the first node 111 operative for handling information pertaining to at least one of the device 130 and the third node 113, the first node

111 being operative to operate in the communications system 100. The first node 111 may comprise the processing circuitry 904 and the memory 905, said memory 905 containing instructions executable by said processing circuitry 904, whereby the first node 111 is further operative to perform the actions described herein in relation to the first node 111 , e.g., in Figure 4 and/or Figures 6-8.

Figure 10 depicts two different examples in panels a) and b), respectively, of the arrangement that the second node 112, may comprise to perform the method actions described above in relation to Figure 5 and/or Figures 6-8. In some embodiments, the second node 112 may comprise the following arrangement depicted in Figure 10a. The second node

112 may be understood to be for handling the information pertaining to the at least one of the device 130 and the third node 113. The second node 112 is configured to operate in the first communications system 100.

Several embodiments are comprised herein. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. In Figure 10, optional boxes are indicated by dashed lines. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the second node 112 and will thus not be repeated here. For example, in some embodiments, the first node 111 may be configured to be an HSS, the another node 114 may be configured to be an SCC-AS, and the second node 112 configured to be the database of an IMS telephony service engine.

The second node 112 is configured to, e.g., by means of a receiving unit 1001 within the second node 112 configured to, receive the second indication from the first node 111 configured to operate in the communications system 100, the second indication being configured to request second information indicating information pertaining to at least one of the device 130 and the third node 113 operating in the communications system 100, wherein the information is configured to be indicated by first information configured to be stored in one first memory storage, of a plurality 120 of first memory storages, wherein each of the first memory storages in the plurality 120 is configured to be different and independent, the second information being configured to have been, prior to receiving the second indication: i. created as an indicator of the first information configured to be stored in any of the first memory storages, ii. stored in a single second memory storage 124, the second memory storage 124 being configured to be different and independent from any of the first memory storages, and updated after, and according to, any update to the first information in any of the first memory storages.

The second node 112 is also configured to, e.g., by means of a sending unit 1002 within the second node 112 configured to, send, in response to the second indication configured to be received, a third indication to the first node 111, the third indication being configured to indicate the second information.

The second node 112 may also be configured to, e.g., by means of the receiving unit 1001 within the second node 112 configured to, receive, prior to receiving the second indication, a request from the first node 111 to create or update the second information in the second memory storage 124 prior to receiving the second indication.

The second node 112 may also be configured to, e.g., by means of a creating unit 1003 within the second node 112 configured to, create, or update the second information in the second memory storage 124, based on the request from the first node 111, wherein the creating or updating is performed prior to receiving the second indication.

In some embodiments, at least one of the following options may apply: a) the information may be configured to be dynamic data, subject to change over time; b) the information may be configured to indicate the RAT, configured to serve, respectively, the at least one of the device 130 and the third node 113; c) the second node 112 may be configured to perform the actions it may be configured to perform during a T-ADS procedure; d) the first node 111 may be configured to be a HSS; e) the second node 112 may be configured to be the database of an IMS telephony service engine; f) the another node 114 may be configured to be an SCC AS; g) the plurality 120 of first memory storages may be configured to comprise at least two of: the first memory storage 121 configured to store the information pertaining to the first RAT, the another first memory storage 122 configured to store the information pertaining to the second RAT and the further first memory storage 123 configured to store the information pertaining to the third RAT; h) the plurality 120 of first memory storages may be configured to comprise at least two of: the first memory storage 121 configured to store the information pertaining to the first RAT, wherein the first RAT may be configured to be one of 2G and 3G, the another first memory storage 122 configured to store the information pertaining to the second RAT, wherein the second RAT may be configured to be 4G, and the further first memory storage 123 configured to store the information pertaining to the third RAT, wherein the third RAT may be configured to be 5G; and i) at least one of the first memory storages may be configured to comprise support information regarding an IMS over PS session.

In some embodiments, the second node 112 may be configured to perform its actions during the T-ADS procedure, and the receiving of the second indication and the creating or updating of the second information may be configured to be excluded from the call setup time measurement associated with the T-ADS procedure.

In some embodiments, the second information may be configured to be the common data object configured to be comprised in the set of bits.

In some embodiments, the second information may be configured to have the smaller size than the first information.

The embodiments herein may be implemented through one or more processors, such as a processor 1004 in the second node 112 depicted in Figure 10, together with 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 second node 112. 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 second node 112.

The second node 112 may further comprise a memory 1005 comprising one or more memory units. The memory 1005 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the second node 112. In some embodiments, the second node 112 may receive information from, e.g., the first node 111 and/or different node, through a receiving port 1006. In some examples, the receiving port 1006 may be, for example, connected to one or more antennas in the second node 112. In other embodiments, the second node 112 may receive information from another structure in the communications system 100 through the receiving port 1006. Since the receiving port 1006 may be in communication with the processor 1004, the receiving port 1006 may then send the received information to the processor 1004. The receiving port 1006 may also be configured to receive other information.

The processor 1004 in the second node 112 may be further configured to transmit or send information to e.g., the first node 111 , a different node and/or another structure in the communications system 100, through a sending port 1007, which may be in communication with the processor 1004, and the memory 1005.

Those skilled in the art will also appreciate that any of the units 1001-1003 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 memory, that, when executed by the one or more processors such as the processor 1004, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (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).

Any of the units 1001-1003 described above may be the processor 1004 of the second node 112, or an application running on such processor.

Thus, the methods according to the embodiments described herein for the second node 112 may be respectively implemented by means of a computer program 1008 product, comprising instructions, i.e. , software code portions, which, when executed on at least one processor 1004, cause the at least one processor 1004 to carry out the actions described herein, as performed by the second node 112. The computer program 1008 product may be stored on a computer-readable storage medium 1009. The computer-readable storage medium 1009, having stored thereon the computer program 1008, may comprise instructions which, when executed on at least one processor 1004, cause the at least one processor 1004 to carry out the actions described herein, as performed by the second node 112. In some embodiments, the computer-readable storage medium 1009 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, a memory stick, or stored in the cloud space. In other embodiments, the computer program 1008 product may be stored on a carrier containing the computer program, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 1009, as described above.

The second node 112 may comprise an interface unit to facilitate communications between the second node 112, a different node and/or another structure in the communications system 100. In some particular examples, the interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

In other embodiments, the second node 112 may comprise the following arrangement depicted in Figure 10b. The second node 112 may comprise a processing circuitry 1004, e.g., one or more processors such as the processor 1004 in the second node 112 and the memory 1005. The second node 112 may also comprise a radio circuitry 1010, which may comprise e.g., the receiving port 1006 and the sending port 1007. The processing circuitry 1004 may be configured to, or operable to, perform the method actions according to Figure 5 and/or Figures 6-8, in a similar manner as that described in relation to Figure 10a. The radio circuitry 1010 may be configured to set up and maintain at least a wireless connection with the first node 111, a different node and/or another structure in the communications system 100.

Hence, embodiments herein also relate to the second node 112 operative for handling the information pertaining to at least one of the device 130 and the third node 113. The second node 112 may comprise the processing circuitry 1004 and the memory 1005, said memory 1005 containing instructions executable by said processing circuitry 1004, whereby the second node 112 is further operative to perform the actions described herein in relation to the second node 112, e.g., in Figure 5 and/or Figures 6-8.

When using the word "comprise" or “comprising”, it shall be interpreted as non- limiting, 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. Therefore, the above embodiments should not be taken as limiting the scope of the invention.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

As used herein, the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “and” term, may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “or” term. Any of the terms processor and circuitry may be understood herein as a hardware component.

As used herein, the expression “in some embodiments” has been used to indicate that the features of the embodiment described may be combined with any other embodiment or example disclosed herein. As used herein, the expression “in some examples” has been used to indicate that the features of the example described may be combined with any other embodiment or example disclosed herein.