Network Nodes, User Equipment and Methods Performed Therein

A method performed by a first network node, such as an AMF, for providing an IMS service for a UE in a wireless communications network. The first network node obtains an IMS provider name for the UE (10) using the IMS service; and selects a second network node (14) for the IMS service based on the obtained IMS provider name.

TECHNICAL FIELD

Embodiments herein relate to a first network node, a second network node, a user equipment (UE) and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication, such as handling or enabling IP multimedia subsystem (IMS) service, in a wireless communications network.

BACKGROUND

In a typical wireless communications network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate, e.g., enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.

With the emerging 5G technologies such as new radio (NR), the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.

3GPP is currently working on Release 17 enhancements to first specifications of the 5G system (Release 15/16). These types of enhancements are made to functionality that was introduced in early releases of the 5G specification.

One such functionality is Non-Public Networks, also known as NPNs, that was introduced in Release 16.

3GPP introduced support for two non-public networks deployment options from Release 16. The first NPN option outlines how operators could support non-public networks or dedicated deployments by associating them directly to the operator network. Such improvements resulted in solutions for what is commonly referred to as Public Network Integrated NPN's (PNI-NPN).

The second NPN option is the stand-alone NPN, or SNPN for short. In almost all aspects, this is a network that carries the same functionality and characteristics as the more commonly known Public Land Mobile Network (PLMN), but it differs in some aspects, e.g., an SNPN is identified by an SNPN ID rather than a PLMN ID. The SNPN ID is composed of a PLMN ID and a Network ID (NID). Additionally, there is no support for mobility between SNPNs, in the same way as is possible between, equivalent, PLMNs.

For NPN, the enhancements currently addressed are described in 3GPP technical report (TR) 23.700-07 v1.2.0: Study on enhanced support of non-public networks, which outlines several key issues, which can be translated into enhancement areas.

SNPN access using credentials from a separate entity, Key issue #1. Key issue (KI) #1 describes a situation when a UE can access an SNPN using credentials not from the SNPN itself, but from another, separate entity, which can be another Service Provider, SP, or Subscription Provider.

The challenges related to KI #1 are described in TR 23.700-07 v1.2.0 as:

“This key issue aims at addressing the following points for SNPN along with subscription owned by an entity separate from the SNPN:How to identify the separate entity providing the subscription.Network selection enhancements, including UEs with multiple subscriptions;E.g., how does the UE discover and select an SNPN which provides authentication in an external entity;Architecture enhancements needed to support multiple separate entities, e.g.:What are the interfaces exposed and/or used by SNPN and the separate entity;What is the architecture and solution for a UE accessing a separate entity via SNPN access network;How to exchange authentication signalling between the SNPN and the separate entity, including:Authentication by the PLMN, based on PLMN identities and credentials, for access to the SNPN;Authentication via SNPN to separate entity based on non-3GPP identities (e.g. non-IMSI) and credentials;Mobility scenarios, including service continuity, for:UE moving from SNPN #1 with separate entity #1 to SNPN #2 with separate entity #1 available; andUE moving between SNPN #1 (where separate entity=PLMN) and PLMN. NOTE: Security aspects should be defined by SA WG3.” 3GPP TR 23.700-07 v1.2.0 indicates the following relevant conclusions for KI #1:Group ID as a specific case of SNPN ID reusing SNPN ID encoding in TS 23.003-g40, whereSIB will be enhanced as follows, for SNPN only:Indication that “access using credentials from a separate entity is supported”Optionally, supported Group identities (GIDs)Optionally, an indication whether the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN

In the following, it is explained the above conclusions for KI #1.

In order for a UE to discover and select an SNPN which provides authentication in an external entity, such as the SP, TR 23.700-07 v1.2.0 concludes that SNPNs need to indicate these new functionalities to UEs. Otherwise, the UEs would not know that they can access these networks with the credentials they possess from the service/subscriber provider (SP).

Furthermore, it was also concluded to allow an SNPN to indicate whether it allows registration attempts from UEs that are not explicitly configured to select this SNPN, hence enabling UEs to perform blind registration attempts, which eventually, may fail if the SNPN does not have means to authenticate the UE.

FIG.1shows an association between SNPN and (group of) SPs, the latter being identified by a GID.

SUMMARY

As part of developing embodiments here one or more problems were first identified. There is a requirement for an SNPN outsourcing IP multimedia subsystem (IMS) voice services to a third party IMS provider to be able to support more than a single third party IMS provider. Current restriction is a 1 to 1 relationship.

An object herein is to provide a mechanism to handle communication in an efficient manner in the wireless communications network.

According to an aspect the object is achieved, according to embodiments herein, by providing a method performed by a first network node, such as an Access and Mobility Management Function (AMF), for handling communication or providing and/or enabling an IMS service for a UE in a wireless communications network. The first network node obtains an IMS provider name for the UE using the IMS service such as voice over LTE (VOLTE). The IMS provider name may be received from the UE, from a UE subscription, or from the third network node. The first network node selects a second network node for the IMS service based on the obtained IMS provider name.

According to another aspect the object is achieved, according to embodiments herein, by providing a method performed by a UE for handling communication or an IMS service in a wireless communications network. The UE provides to a first network node, an IMS provider name for the UE using the IMS service. For example, the UE may include an IMS provider name in a registration such as a 5GC Registration Procedure to the first network node.

According to yet another aspect the object is achieved, according to embodiments herein, by providing a method performed by a second network node, such as a Session Management Function (SMF), for handling communication or providing and/or enabling an IMS service for a UE in a wireless communications network. The second network node may obtain an IMS provider name for the UE using the IMS service. The second network node uses the IMS provider name to perform network repository function (NRF) discovery to discover one or more IMS nodes for the UE using the IMS service.

According to still another aspect the object is achieved, according to embodiments herein, by providing a first network node, a second network node and a UE configured to perform the methods herein, respectively.

Thus, it is herein provided a first network node for providing an IMS service for a UE in a wireless communications network. The first network node is configured to obtain an IMS provider name for the UE using the IMS service. The first network node is further configured to select a second network node for the IMS service based on the obtained IMS provider name.

It is also herein provided a UE for handling an IMS service in a wireless communications network. The UE is configured to provide to a first network node, an IMS provider name for the UE using the IMS service.

It is herein provided a second network node for providing an IMS service for a UE in a wireless communications network. The second network node is configured to use an IMS provider name to perform NRF discovery to discover one or more IMS nodes for the UE using the IMS service.

It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the first network node, the second network node, and the UE, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the first network node, the second network node, and the UE, respectively.

Hence, embodiments herein provide a mechanism to efficiently handle an IMS service in the wireless communications network.

DETAILED DESCRIPTION

Embodiments herein relate to wireless communications networks in general.FIG.2is a schematic overview depicting a wireless communications network1. The wireless communications network1comprises one or more RANs and one or more CNs. The wireless communications network1may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA).

In the wireless communications network1, a user equipment (UE)10, exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and/or a wireless terminal, is comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN). It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-IoT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

The wireless communications network1comprises a radio network node12providing radio coverage over a geographical area, a first service area11or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar. The radio network node12may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the radio network node depending e.g. on the first radio access technology and terminology used. The radio network node may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the UE in form of DL transmissions to the UE and UL transmissions from the UE. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

The wireless communication network1provides IMS services, such as voice over LTE (VOLTE) or similar, and comprises a first IMS node15and a second IMS node16of an IMS. The first IMS node15may be an application server provided by an IMS provider. The second IMS node16may be a Home Subscriber Server (HSS) or a Call Session Control Function (CSCF) node such as a P-CSCF or a S-CSCF node. The Call session control function, e.g., facilitates Session Internet Protocol (SIP) setup and teardown and the HSS plays the role of a location server in IMS, in addition to acting as an authentication, authorization, accounting (AAA) server. The CSCF may comprise one or more of distributed functions e.g. a proxy CSCF node (P-CSCF), an Interrogating CSCF (I-CSCF) node, and a Serving CSCF (S-CSCF) node. The P-CSCF acts as the entry point in the IMS network. The HSS is the main database of the current generation's cellular communications systems. It contains subscriber-related information, such as the authentication information and the list of services to which each user is subscribed.

As stated above the communication network comprises a number of core network nodes such as a first network node13for example an AMF and a second network node14such as an SMF, and a third network node17such as user data management (UDM) or another AMF.

The embodiments described herein provide a simple solution extending existing capabilities with enablers that provide important flexibility.

FIG.3is a combined signalling and flowchart scheme according to embodiments herein.

Action301. The UE10may maintain an association between an IMS provider name and an access provider name. The UE10may thus have a mapping between a first name indication indicating an IMS provider and a second name indication indicating an access provider. Thus, the UE10may maintain an association between IMS credentials and access credentials.

Action302. The UE10includes the IMS provider name in a registration such as a 5GC Registration Procedure.

Action303. The first network node13, i.e., the AMF, receives the IMS provider name or names, and stores it in the UE context. Thus, at 5GC registration the UE10provides the IMS provider name and this is stored in the UE context by the AMF13. Alternatively, the IMS provider name or names may be provided by an UDM during 5GC registration. Thus, the third network node17may provide the IMS provider name or names to the first network node13.

Action304. For local break out (LBO) and non-roaming case, the AMF13may pass the IMS provider name to the selected SMF in the Nsmf_PDUSession_CreateSMContext to the visiting SMF (vSMF). For Home routed case, vSMF passes the IMS provider name to the home SMF (hSMF) in Nsmf_PDUSession_Create to hSMF. Thus, when the UE10establishes an IMS session, the AMF may select the SMF that is dedicated for use with that specific IMS provider. The AMF selects an SMF configured in the AMF for the target IMS provider.

Action305. The second network node14, i.e., the SMF, may support the IMS provider name and use it to perform NRF discovery to discover one or more P-CSCFs such as the first or the second IMS node15,16. The SMF may include the IMS provider name in the charging information. Hence, the P-CSCF configured or discovered by the SMF, via the NRF, corresponds to the IMS provider. The SMFs corresponding to the different IMS providers are configured in the AMF. The IMS provider is configured in the selected SMF for discovery of P-CSCF.

Alternatively, or additionally, the AMF select may select any SMF and include the IMS provider name. The SMF may then discover the P-CSCF corresponding to the target IMS provider in the incoming request.

For home routed scenarios, the vSMF passes the IMS provider name to the hSMF.

In the example above, option one, the UE10is configured with the IMS provider name which is provided to the AMF during 5GC Registration.

In option two, the UE IMS provider name is configured in an UE access subscription. The AMF acquirers the IMS provider name, from the UE access subscription, at 5GC Registration and is stored in the UE context. Otherwise, the same actions apply.

There are two potential sub-options that are possible with option one and option two. In sub-option1the selected SMF by the AMF is assumed to be configured for use only with that IMS provider. Hence, a different SMF is used for each IMS provider. In the second sub-option the AMF passes to the SMF the IMS provider name. The SMF may then discover the P-CSCF corresponding to the target IMS provider. For home routed scenarios the vSMF passes the IMS provider name to the hSMF.

In another implementation, option three, a different IMS data network name (DNN) is configured in AMF subscription data in the subscribed DNN List in UDM for each IMS provider per UE. Each DNN name maps to a specific IMS provider configured in the AMF for that purpose. For example, DNN-IMS1maps to IMS provider1, DNN IMS2maps to IMS provider2. There will be one IMS DNN per UE in an AMF DNN Subscription List.

Three sub-options can support the above option three:

In the first sub-option the operator identifier (OI) in the AMF Subscription data for the UE is configured in the DNN part, hence the operator identifier identifies the IMS operator. In this case the selected SMF by the AMF is assumed to be configured for use only with that IMS provider and will be based on the OI in the DNN. Hence this requires a different SMF for each IMS provider. The SMF fetches the IMS provider from the SMF UE DNN subscribed list, so it can discover the corresponding P-CSCF. In this sub-option there are no impacts on the AMF beyond the configuration of the SMF to use with a specific IMS provider.

The second sub-option is similar to the first sub-option with the difference that the selected SMF by the AMF is assumed to be used for all IMS providers. The SMF either receives the IMS provider name from AMF as in option one and option two or SMF fetches the IMS provider from the SMF UE DNN subscribed list, so it can discover the corresponding P-CSCF. The SMF has the option in this case to also use a separate UPF for every IMS provider to isolate the traffic.

The third sub-option is used in case it is not possible to use the OI of the DNN. Hence a different DNN Network Identifier (NI) for every IMS provider may be used in this case. Hence, the AMF may be configured with mapping between DNN NI and IMS provider. In this sub-option, at 5GC Registration, the AMF, configured with the mapping between DNN NI and IMS provider, determines the IMS provider from the AMF Subscription data and the remaining aspects of option one and option two can be reused as is.

SMF in option3may also include the IMS provider name to the charging records.5GC Impacted procedures.Registration is shown inFIG.4
For option one sub-option1:Changes are in the following steps:Step1, and3where the IMS provider name is conveyed to the AMF.Step5where IMS provider name can be transferred from an old AMF to a new AMFAMF is impacted to store the IMS provider name in the UE context.AMF selects an SMF configured in the AMF for the target IMS provider.
For option one Sub-option2:
Changes are in the following steps:Step1, and3where the IMS provider name is conveyed to the AMF.Step5where IMS provider name can be transferred from an old AMF to a new AMFAMF is impacted to store the IMS provider name in the UE context.

FIG.5shows PDU Session Establishment Procedure LBO and non-roaming caseFor option one sub-option1: No impactSMF includes the IMS provider name in the charging dataFor option one sub-option2:The main change is in step3carrying the IMS provider nameSMF includes the IMS provider name in the charging dataSMF stores the needed information in the PDU session state.

FIG.6_option one Home Routed case;

The main change in steps3aand step6carrying the IMS provider name.

SMF new behavior is described above.

AMF: Receives the IMS provider names from UDM, stores it in the UE context.

In option2sub-option1, AMF selects an SMF configured in the AMF for the target IMS provider.

In option2sub-option2, for LBO, and non-roaming case, AMF passes the IMS provider name to the selected SMF in the Nsmf_PDUSession_CreateSMContext to the vSMF

For both above services this will be an optional incoming attribute.

UDM: Stores the IMS provider name in the AMF subscription data and send it to the AMF during 5GC registration:

AMF Subscription Data is updated to include support for IMS provider name.

SMF: SMF has to support the IMS provider name in option2sub-option2and use it to perform NRF discovery to discover P-CSCFs

For Home routed case, vSMF passes the IMS provider name to the hSMF in Nsmf_PDUSession_Create to hSMF.

Also SMF have to include the IMS provider name in the charging information

For option2sub-option1:

Changes are in the following steps:Step5where IMS provider name can be transferred from an old AMF to a new AMFUDM passes the IMS provider name from UDM to AMF where it gets stored in the UE context.AMF is impacted to store the IMS provider name in the UE context.AMF selects an SMF configured in the AMF for the target IMS provider.

For option2Sub-option2: Changes are in the following steps:Step5where IMS provider name can be transferred from an old AMF to a new AMFUDM passes the IMS provider name from UDM to AMF where it gets stored in the UE context.AMF is impacted to store the IMS provider name in the UE context.

Remaining AMF and SMF impacts are as in option1

FIG.8shows a signalling scheme according to embodiments herein.

AMF Impacts: AMF identifies the IMS operator based on the OI and selects the SMF accordingly, either preconfigured SMF per IMS operator or just passing the IMS provider to any SMF.

SMF Impacts: SMF locates the IMS provider corresponding to the DNN received from UDM, then performs the NRF discovery to locate the corresponding P-CSCF. SMF stores the needed information in the PDU session state. Or alternatively the SMF receives from AMF the IMS provider name.

AMF impacts: Maps the DNN name to IMS provider name, stores it in the UE context. AMF is configured with mapping between IMS DNN names and IMS provider name.

In option3, sub-option1, AMF selects an SMF configured in the AMF for the target IMS provider.

In option3, sub-option2, for LBO, and non-roaming case, AMF passes the IMS provider name to the selected SMF in the Nsmf_PDUSession_CreateSMContext to the vSMF

For Home routed case, vSMF passes the IMS provider name to the hSMF in Nsmf_PDUSession_Create to hSMF.

For both above services this will be an optional incoming attribute

SMF: SMF has to support the IMS provider name in sub-option2and use it to perform NRF discovery to discover P-CSCFs

Also SMF may have to include the IMS provider name in the charging information

For sub-option1:

Changes are in the following steps:Step5where IMS provider name can be transferred from an old AMF to a new AMFAMF is impacted to store the IMS provider name in the UE context.Step14, AMF receives the subscribed DNN list and locates the IMS provider corresponding to the IMS DNN. IMS provider name is stored in the UE context.AMF selects an SMF configured in the AMF for the target IMS provider.

For Sub-option2: Changes are in the following steps:Step5where IMS provider name can be transferred from an old AMF to a new AMFAMF is impacted to store the IMS provider name in the UE context.

AMF and SMF impacts are as in option1for PDU session establishment.

SMF in option3with all its sub-options1,1,2and3also includes the IMS provider name in the charging records.

P-CSCF and SMF Behavior Applicable to all options1,2, and3.

In order to select the proper P-CSCF, P-CSCF may have to include the IMS provider it is associated with when it registers its profile in NRF (section Y.12 TS 23.228-g40).

The SMF may also acquire the information and compare it to the IMS provider of interest to locate the correct CSCF, see section 5.16.3.11 TS 23.501-g40. The method actions performed by the first network node, such as an AMF, for handling communication or providing an IMS service for the UE10in the wireless communications network1according to embodiments will now be described with reference to a flowchart depicted inFIG.9. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

Action401. The first network node13obtains an IMS provider name for the UE10using the IMS service such as VOLTE. The IMS provider name may be received from the UE10, from a UE subscription or from the third network node17.

Action402. The first network node13selects the second network node14for the IMS service based on the obtained IMS provider name.

Action403. The first network node13may store the IMS provider name in a UE context of the UE10.

The method actions performed by the UE10for handling the IMS service in the wireless communications network1according to embodiments will now be described with reference to a flowchart depicted inFIG.10. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Dashed boxes indicate optional features.

Action501. The UE10may maintain an association between the IMS provider name and an access provider name. The UE10may thus have a mapping between a first name indication indicating an IMS provider and a second name indication indicating an access provider. The UE10may maintain an association between the IMS credentials and the access credentials and/or an association between IMS provider and IMS credentials.

Action502. The UE10provides to the first network node13, the IMS provider name for the UE10using the IMS service. The IMS provider name may be provided in a 5GC Registration Procedure. Hence, the UE10may include the IMS provider name in a registration such as a 5GC Registration Procedure.

The method actions performed by the second network node14, such as an SMF, for providing the IMS service for the UE10in the wireless communications network1according to embodiments will now be described with reference to a flowchart depicted inFIG.11. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

Action601. The second network node14may obtain the IMS provider name for the UE using the IMS service such as VOLTE. The IMS provider name may be received from the first network node13or from the third network node17. Thus, the third network node17may provide the IMS provider name or names to the second network node14. Action602. The second network node14(may support or may have a mapping for the IMS provider name to the one or more IMS nodes) uses the IMS provider name to perform network repository function (NRF) discovery to discover one or more IMS nodes for the UE10using the IMS service, for example, one or more P-CSCFs such as the first or the second IMS node15,16.

FIG.12ais a block diagram depicting embodiments of the first network node13for handling communication or the IMS service for the UE10in the wireless communications network1according to embodiments herein.

The first network node13may comprise processing circuitry1101, e.g., one or more processors, configured to perform the methods herein.

The first network node13may comprise a receiving unit1102, e.g., a receiver. The first network node13, the processing circuitry1101and/or the receiving unit1102is configured to obtain the IMS provider name for the UE10using the IMS service such as VOLTE. The IMS provider name may be received from the UE10, from a UE subscription or from the third network node17and may then be stored at the first network node13in associating it with the UE10. Thus, the first network node13may be configured to store the IMS provider name in the UE context of the UE10.

The first network node13may comprise a selecting unit1103. The first network node13, the processing circuitry1101and/or the selecting unit1103is configured to select the second network node14for the IMS service based on the obtained IMS provider name.

The first network node13may comprise a memory1105. The memory1105comprises one or more units to be used to store data on, such as data packets, mapping, name indication, type indication, mapping of IMS provider names and access provider names/UEs, networks, mobility events, measurements, sizes related to types of data transmissions, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the first network node13may comprise a communication interface1108such as comprising a transmitter, a receiver, a transceiver and/or one or more antennas.

The methods according to the embodiments described herein for the first network node13are respectively implemented by means of e.g., a computer program product1106or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first network node13. The computer program product1106may be stored on a computer-readable storage medium1107, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium1107, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first network node13. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a first network node13for handling communication in a wireless communications network, wherein the first network node13comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said first network node13is operative to perform any of the methods herein.

FIG.12bis a block diagram depicting the UE10for handling communication or an IMS service in the wireless communications network1according to embodiments herein.

The UE10may comprise processing circuitry1201, e.g., one or more processors, configured to perform the methods herein.

The UE10may comprise a maintaining unit1202, e.g., a memory unit. The UE10, the processing circuitry1201and/or the maintaining unit1202may be configured to maintain the association between an IMS provider name and an access provider name. The UE10may thus have the mapping between the first name indication indicating the IMS provider and the second name indication indicating the access provider. Thus, the UE10, the processing circuitry1201and/or the maintaining unit1202may be configured to maintain the association between the IMS credentials and the access credentials and/or the association between IMS provider and IMS credentials.

The UE10may comprise a providing unit1203, e.g., a transmitter or a transceiver. The UE10, the processing circuitry1201and/or the providing unit1203is configured to provide to the first network node13, the IMS provider name for the UE10using the IMS service. The IMS provider name may be provided in a 5GC Registration Procedure. Hence, the UE10may be configured to provide the IMS provider name to the first network node13such as to include the IMS provider name in a registration such as a 5GC Registration Procedure.

The UE10may comprise a memory1205. The memory1205comprises one or more units to be used to store data on, such as data packets, grants, name indication(s), type indication(s), indices, bitmap, indications, IMS provider names, IMS provider names mapped to access providers, mobility events, measurements, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the UE10may comprise a communication interface1208such as comprising a transmitter, a receiver, a transceiver and/or one or more antennas.

The methods according to the embodiments described herein for the UE10are respectively implemented by means of e.g. a computer program product1206or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE10. The computer program product1206may be stored on a computer-readable storage medium1207, e.g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium1207, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE10. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a UE10for handling communication in a wireless communications network, wherein the UE10comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said UE10is operative to perform any of the methods herein.

FIG.12cis a block diagram depicting the second network node for handling the IMS service for the UE10in the wireless communications network1according to embodiments herein.

The second network node14may comprise processing circuitry1401, e.g., one or more processors, configured to perform the methods herein.

The second network node14may comprise a receiving unit1402, e.g., a receiver. The second network node14, the processing circuitry1401and/or the receiving unit1402may be configured to obtain an IMS provider name for the UE10using the IMS service such as VOLTE. The IMS provider name may be received from the first network node13associating it with the UE10or the third network node17.

The second network node14may comprise a discovering unit1403. The second network node14, the processing circuitry1401and/or the discovering unit1403is configured to perform NRF discovery using the IMS provider name to discover the one or more IMS nodes for the UE using the IMS service, such as one or more P-CSCFs such as the first or the second IMS node15,16. The second network node14may be configured to support or have a mapping for the IMS provider name to the one or more IMS nodes. The second network node14may comprise a memory1405. The memory1405comprises one or more units to be used to store data on, such as data packets, mapping, name indication, type indication, mapping of IMS provider names and access provider names/UEs/P-CSCFs, networks, mobility events, measurements, sizes related to types of data transmissions, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the second network node14may comprise a communication interface1408such as comprising a transmitter, a receiver, a transceiver.

The methods according to the embodiments described herein for the second network node14are respectively implemented by means of e.g., a computer program product1406or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second network node14. The computer program product1406may be stored on a computer-readable storage medium1407, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium1407, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second network node14. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a second network node14for handling communication in a wireless communications network, wherein the second network node14comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said second network node14is operative to perform any of the methods herein.

In some embodiments a more general term “network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a wireless device and/or with another network node. Examples of network nodes are NodeB, MeNB, SeNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc.

In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and/or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and/or program or application data. Other hardware, conventional and/or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

The communication system3300further includes the UE3330already referred to. Its hardware3335may include a radio interface3337configured to set up and maintain a wireless connection3370with a base station serving a coverage area in which the UE3330is currently located. The hardware3335of the UE3330further includes processing circuitry3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE3330further comprises software3331, which is stored in or accessible by the UE3330and executable by the processing circuitry3338. The software3331includes a client application3332. The client application3332may be operable to provide a service to a human or non-human user via the UE3330, with the support of the host computer3310. In the host computer3310, an executing host application3312may communicate with the executing client application3332via the OTT connection3350terminating at the UE3330and the host computer3310. In providing the service to the user, the client application3332may receive request data from the host application3312and provide user data in response to the request data. The OTT connection3350may transfer both the request data and the user data. The client application3332may interact with the user to generate the user data that it provides.

It is noted that the host computer3310, base station3320and UE3330illustrated inFIG.14may be identical to the host computer3230, one of the base stations3212a,3212b,3212cand one of the UEs3291,3292ofFIG.13, respectively. This is to say, the inner workings of these entities may be as shown inFIG.14and independently, the surrounding network topology may be that ofFIG.13.

The wireless connection3370between the UE3330and the base station3320is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE3330using the OTT connection3350, in which the wireless connection3370forms the last segment. More precisely, the teachings of these embodiments may improve the performance of using an IMS service efficiently and thereby provide benefits such as reduced user waiting time, and better responsiveness since interference is reduced.

ABBREVIATION EXPLANATION

5GC 5th Generation Core NetworkBSR Buffer Status ReportCORESET Control Resource SetCN Core NetworkCSS Common Search SpaceDCI Downlink Control IndicatorDVT Data Volume Threshold EDT MIB Master Information Block Early Data TransmissionMsg MessageNR New RadioPBCH Physical Broadcast ChannelPDCCH Physical Downlink Control ChannelPDSCH Physical Downlink Shared ChannelPRACH Physical Random Access ChannelRACH Random Access ChannelRAR Random Access ResponseSDT Small Data TransmissionSSB Synchronization Signal Block

REFERENCES