Managing identity credentials in an IP multimedia subsystem
By implementing network entities within the IMS to manage and verify user credentials through certificate-based authentication, the IMS effectively addresses the challenge of false caller identities in wireless communications, enhancing security and reducing scam calls.
Patent Information
- Application Number
- PCT/EP2024/056285
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-02-21
- Filing Date
- 2024-03-08
- Publication Date
- 2024-11-28
AI Technical Summary
Current standards for IP multimedia subsystems (IMS) do not specify how to obtain or store user credentials for authenticating caller identities, leading to security issues such as scam calls where callers present false identities, and there is a need to enhance authentication and verification processes.
Implementing network entities within the IMS to register and authenticate user equipment (UE) with IMS identities, obtaining and storing certificates that certify user data, and using these certificates to sign outgoing communications, thereby enabling verification of caller identities by the terminating network.
Enhances security and authentication in wireless communications by ensuring that caller identities are verified, reducing the occurrence of scam calls and increasing trust in the authenticity of communications.
Smart Images

Figure EP2024056285_28112024_PF_FP_ABST
Abstract
Description
MANAGING IDENTITY CREDENTIALS IN AN IP MULTIMEDIA SUBSYSTEMTECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more specifically to managing identity credentials in an IP multimedia subsystem.BACKGROUND
[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).
[0003] Some wireless communications systems may comprise an internet protocol (IP) multimedia subsystem (IMS). The IMS provides a framework for delivering IP multimedia services, such as voice, video and text messaging, over IP networks. The IMS comprises a number of network entities to provide these features.SUMMARY
[0004] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates aninclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be constmed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
[0005] According to a first aspect, some implementations of the method and apparatuses described herein may further include a network entity for communication in an IP multimedia subsystem (IMS) , comprising at least one memory and at least one processor coupled with the at least one memory and configured to cause the network entity to: register a user equipment (UE) with the IMS, comprising authenticating an IMS identity of the UE; receive user data associated with the UE; request credentials for the user data, wherein the request comprises the user data and the IMS identity; receive a certificate for the IMS identity that certifies the user data; store the certificate at the network entity; and send the certificate to an application server (AS) of the IMS for signing outgoing communications from the UE via the IMS.
[0006] The network entity can be a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS. The AS can communicate with the HSS via the Diameter Sh interface. Typically, the IMS communicates with the UE via a Session Initiation Protocol (SIP) User Agent (UA) installed in the UE.
[0007] The user data normally comprise verified user data such as a user name and a telephone number. The verified user data may comprise data obtained from the user’spassport or another official identity document, such as driving license, when the user establishes a subscription. The network entity may also be configured to receive and store further user data (e.g. rich call data) that is not verified data.
[0008] The at least one processor can be configured to cause the network entity to receive the user data from the AS. This AS in the IMS may also be referred to as a telephony AS.
[0009] The at least one processor can be configured to cause the network entity to request credentials directly from a certificate issuer outside the IMS. Alternatively, the at least one processor can be configured to cause the network entity to request the credentials via the AS.
[0010] The at least one processor can be configured to cause the network entity to: receive a subscription request from the AS, wherein the subscription request comprises the IMS identity; and in response to receiving the subscription request, configure the network entity to automatically update the AS with information associated with the UE that is received by the network entity while the UE is registered to the IMS.
[0011] The at least one processor can be configured to cause the network entity to provide the certificate to a credentials repository outside the IMS.
[0012] The at least one processor can be configured to cause the network entity to: receive the user data as initial subscription data associated with the UE before registering the UE with the IMS; and store the initial subscription data at the network entity.
[0013] The at least one processor can be configured to cause the network entity to: request credentials for the initial subscription data before registering the UE with the IMS;receive a certificate for the IMS identity that certifies the initial subscription data; and after registering the UE with the IMS, send the certificate to the AS.
[0014] The at least one processor can be configured to cause the network entity to: in response to receiving the user data, determine if a certificate for the IMS identity that certifies the user data is stored at the network entity; and when the certificate is stored at the network entity, send the certificate to the AS.
[0015] According to a second aspect, some implementations of the method and apparatuses described herein further include a method of communication in in an IP multimedia subsystem (IMS), the method comprising, at a network entity (e.g. the HSS / UDM): registering a user equipment (UE) with the IMS, comprising authenticating an IMS identity of the UE; receiving user data associated with the UE; requesting credentials for the user data, wherein the request comprises the user data and the IMS identity; receiving a certificate for the IMS identity that certifies the user data; storing the certificate at the network entity; and sending the certificate to an application server (AS) of the IMS for signing outgoing communications from the UE via the IMS.
[0016] The method may be carried out at or by the network entity according to the first aspect.
[0017] The step of requesting credentials may comprise, at the network entity, requesting credentials directly from a certificate issuer outside the IMS. Alternatively, the step of requesting credentials may comprise, at the network entity, requesting credentials via the AS.
[0018] According to a third aspect, some implementations of the method and apparatuses described herein further include a network entity (e.g. an AS) for wireless communication in an IP multimedia subsystem (IMS), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive user data from a user equipment (UE), wherein the UE is registered with the IMS and has an IMS identity; send the user data with the IMS identity to a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS; receive a certificate for the IMS identity that certifies the user data; and store the certificate at the network entity while the UE is registered with the IMS; and sign outgoing communications from the UE via the IMS using the certificate.
[0019] The at least one processor can be configured to cause the network entity to send a subscription request to the HSS or UDM, to cause the HSS or UDM to update the network entity with information associated with the UE. The network entity can communicate with the HSS via the Diameter Sh interface. Typically, the IMS communicates with the UE via a SIP UA installed in the UE.
[0020] The user data normally comprise verified user data such as a user name and a telephone number. The verified user data may comprise data obtained from the user’s passport or another official identity document, such as a driving license, when the user establishes a subscription. The network entity may also be configured to receive and store further user data (e.g. rich call data) that is not verified data.
[0021] The at least one processor can be configured to cause the network entity to: receive a credential request from for the user data, wherein the request comprises the user data and the IMS identity;in response to receiving the request, send the credential request to a certificate issuer outside the IMS; and receive from the certificate issuer a certificate for the IMS identity that certifies the user data.
[0022] The at least one processor can be configured to cause the network entity to send the certificate to the HSS or UDM.
[0023] The at least one processor can be configured to cause the network entity to send the certificate to a credentials repository outside the IMS.
[0024] According to a fourth aspect, some implementations of the method and apparatuses described herein further include a method of communication in in an IP multimedia subsystem (IMS), the method comprising, at a network entity (e.g. an AS): receiving user data from a user equipment (UE), wherein the UE is registered with the IMS and has an IMS identity; sending the user data with the IMS identity to a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS; receiving a certificate for the IMS identity that certifies the user data; storing the certificate at the network entity while the UE is registered with the IMS; and signing outgoing communications from the UE via the IMS using the certificate.
[0025] The method may be carried out at or by the network entity of the third aspect described above. The method may further comprise, at the network entity, sending the certificate to the HSS or UDM.BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
[0027] Figure 2 illustrates an example of a part of a communication system in accordance with aspects of the present disclosure;
[0028] Figure 3 illustrates a signaling flowchart of a process for managing identity credentials in an IMS;
[0029] Figure 4 illustrates a signaling flowchart of an alternative process for managing identity credentials in an IMS.
[0030] Figure 5 illustrates an example of a user equipment (UE) 500 in accordance with aspects of the present disclosure.
[0031] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure.
[0032] Figure 7 illustrates an example of a network equipment (NE) 700 in accordance with aspects of the present disclosure.
[0033] Figure 8 illustrate a flowcharts of method performed by a NE in accordance with aspects of the present disclosure.
[0034] Figure 9 illustrate a flowcharts of method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION
[0035] A problem in wireless communications over IP networks is the growing number of scam calls, where a caller will present a falls identity to the receiver. The call may appear to originate from a trusted source, such as the receiver’s bank or a government agency. The false trust this creates can then allow the scammer to defraud the receiver. Hence, there is an ongoing need to increase the security and authentication of wireless communications.
[0036] For voice over IP (VoIP) systems, a new framework for authenticating the caller has been suggested, which is called STIR / SHAKEN. STTR / SHAKEN stands for Secure Telephone Identity Revisited (STIR) and Signature-based Handling of Asserted Information Using toKENs (SHAKEN) standards. The originating network (caller side) of a call authenticates the caller ID with a certificate, and the terminating network (receiverside) verifies the originating caller ID with the embedded certificate. One solution for adopting the SHR / SHAKEN framework for an IMS, relies on the electronic Identification, Authentication and Trust Services (EID AS) supported Self-Sovereign Identity. This involves the user itself receiving the digital identity from an issuer, which can then point to different credentials (e.g. passport, driving license etc.) in a credential repository.
[0037] However, it is not clear how the IMS obtains or stores such credentials for a user. In particular, the current standards do not specify when a certificate for a user ID is created, which entity requests the certificate associated with the user ID, or which entity adds additional authenticated information (e.g. rich call data).
[0038] Aspects of the present disclosure may at least partly solve these problems by providing one or more network entities (also referred to as network functions) in the IMS. The network entities are configured to register and authenticate a user equipment (UE) of a user (also referred to as subscriber) with an IMS identity, and to obtain a certificate for that IMS identity that certifies user data (e.g. name, photo, passport etc.) associated with the user. The certificate can then be used to sign outgoing communications from the UE via the IMS. The terminating network can then use the certificate to verify the caller data of incoming communications.
[0039] Aspects of the present disclosure are described in the context of a wireless communications system.
[0040] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or NE 102, one or more UE 104, and a core network (CN) 106, and an IMS 110. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.
[0041] The UEs 104 may communicate with the IMS 110 via the CN 106. For example, the CN 106 may relay IMS signalling and / or media traffic between the UE 104 and the IMS 110. The UE’s 104 typically have a SIP UA installed thereon for communication with the IMS 110.
[0042] The IMS 110 is a system for providing IP -based multimedia services, for example to the UE 104. The IMS 110 comprises a plurality of different network entities including an application server (“AS”) 112, a call session control function (“CSCF”) 114, and a Home Subscriber Server (HSS) or User Data Manager (UDM) 116. The AS 112 can host and / or execute multimedia services. In some embodiments, the AS 112 is a SIP application server. The CSCF 114 may comprise, or be divided into, a plurality of network functions such as a proxy-CSCF (“P-CSCF”), an interrogating-CSCF (“I-CSCF”), and a serving-CSCF (“S-CSCF”). The CSCF may be SIP functions providing control plane services for the IMS 110. The HSS / UDM 116 is configured to store subscription profile data, for example relating to one or more of the UEs 104, including authentication data, service profiles and user preferences.
[0043] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0044] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. Forexample, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
[0045] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Intemet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
[0046] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0047] An NE 102 may support communications with the CN 106, or with another NE102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more otheraccess network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).
[0048] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
[0049] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106). A UE 104 may establish a session (e.g. a PDU session) with the IMS 110 via the CN 106. For example, the UE 104 may establish a session with an application server of the IMS 110.
[0050] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single framestructure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0051] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0052] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0053] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively.Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0054] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0055] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.
[0056] Figure 2 illustrates an example of a part of a communication system 200 in accordance with aspects of the present disclosure. The communication system 200 may be the wireless communication system 100 described in relation to Figure 1 above. The same reference numerals have been used in different Figures for similar or equivalent features, which is intended to aid understanding of the present disclosure, and is not intended to limit the illustrated embodiments. The communication system 200 comprises a home IMS network 202 comprising a UE 104 (typically a mobile phone or personal computer) connected to an IMS 110 via the CSCF 114. The IMS 110 comprises a plurality of network entities including the CSCF 114, an AS 112 and an HSS / UDM 116. The IMS 110 communicates with an issuer 204 and a credentials repository (CR) in a trusted domain 208 outside the home IMS network 202. The IMS 110 can request and receive a certificate from the issuer for certifying user data associated with the UE 104 and can send the certificate to the CR 208. A terminating network (not shown) can access the public key of the certificate from the CR 208 in order to verify a communication from the UE 104 signed by the IMS 110 using the corresponding private key. Storing the certificate in a global CR 208 allows operators in different countries to verify the certificate securely.
[0057] The UE 104 is associated with an IMS identity (e.g. Tel URI, IMPI, (wildcarded) IMPU, GRUU, NAI), which is authenticated and authorized by the IMS 110. After registering the UE 104 or after establishing a subscription with the user (i.e. after the subscription is activated), the HSS / UDM 116 can check if it has a certificate for that IMS identity, which is associated with the subscription and the user. The user in this context may also be an enterprise that has established a subscription. The IMS 110 and / or the mobile operator owns the digital ID of the subscription in the form of an identity certificate with a private key, not the user. When the UE 104 registers with the IMS 110, the certificate can be loaded into the AS 112 from the HSS / UDM 116 for signing outgoing communications.
[0058] If the HSS / UDM 116 has no certificate for the IMS identity when registering the UE 104, the IMS 110 requests the certificate from the issuer 204. The request may comprise additional user data from the passport like the photo, name, address etc., theadditional user data may be either taken from the subscription or be provided by the user during or after registering the UE 104 with the IMS 110.
[0059] In one embodiment, the HSS / UDM 116 requests the certificate directly from the issuer 206. The HSS / UDM sends a credential request comprising the UE’s IMS identity and the user data. The issuer 206 then provides a certificate for the IMS identity back to the HSS / UDM 116. The HSS / UDM 116 stores the certificate and may also provide the certificate to the CR 208. For example, the HSS / UDM 116 can send an update credentials request to the CR208 with the certificate and the user data.
[0060] In another embodiment, the HSS / UDM 116 may request the certificate via the AS 112. The AS 112 then sends a certificate request to the issuer 206. The issuer 206 then provides the certificate to the AS 112, which sends it to the HSS / UDM 116 for storage. The AS 112 may also send the certificate to the CR 208.
[0061] After obtaining the certificate at the IMS 110, the AS 112 can sign outgoing calls from the UE 104. For example, the user data may comprise a name and a photo that is displayed on a receiving device in the terminating network, and the terminating network can then verify that the photo and name are those associated with the IMS identity of the UE 104 by using the certificate. The certificate may be provided with the outgoing call, or may be accessed from the CR 208. The AS 112 has access to the private key of the certificate for signing communications from the UE 104, and the terminating network receives or can obtain the corresponding public key to verify the signature.
[0062] The IMS 110 may request the certificate already at the point when the user signs up. At the point of establishment of the subscription, some verification of the real identity of the user will normally takes place, which can generate the user data (e.g. the user data may comprise information from scanning the user’s passport). The user may sign up to a contract with a subscription that includes one or more IMS services, which can prompt the IMS 110 to request a certificate for the IMS identity of the user. In that case, when the UE 104 comes to register with the IMS 110, the HSS / UDM 116 can determine that a certificate for the IMS identity that certifies the user data is already available to the IMS 110, and a further credentials request is not necessary.
[0063] When a private branch exchange (PBX) or other enterprise registers a UE 104 with the IMS 110, the certificate is for the enterprise and for the wildcarded nr range, i.e. the PBX can fetch rich call data for individual users of a specific nr, but the IMS cannot verify whether the included information is correct, it can only verify that it comes from that PBX.
[0064] Figure 3 illustrates a signaling flowchart of a process for managing identity credentials in an IMS 110. Optional steps, which are not necessary when the HSS / UDM has already got a certificate for the IMS identity of the UE (e.g. from initial user sign up to a contract), and therefore does not need to request a new one after registering the UE with the IMS, are shown with dashed lines.
[0065] At step 301, the UE, for example through a Session Initiation Protocol (SIP) User Agent (UA) of the UE, sends a registration request with the IMS identity to the IMS 110. The IMS identity may be a Tel URI, a SIP URI, a IMPI, IMPU GRUU or a specific NAI for example. In case the UE belongs to an enterprise (e.g. a PBX enterprise), the registration message may contain a wildcarded IMPU to register the number range of the enterprise. The CSCF of the IMS 110 receives the registration request from the UE.
[0066] At step 302, the UE performs authentication and authorization with the IMS 110. The HSS / UDM of the IMS 110 can authenticate the IMS identity.
[0067] At step 303, after successful authentication and authorization the CSCF sends a registration confirmation message (e.g. a 200 OK message) to the UE. The UE receives the registration confirmation message and is registered with the IMS 110.
[0068] At step 304, the user might want to register user data (e.g. rich call data) in the IMS 110, e.g. a profile photo, and sends a SIP message to the IMS 110 containing the IMS identity and the user data to be registered. The user data may be received by the AS via the CSCF. The IMS 110 cannot verify the additional data from the UE. That is, the IMS cannot tell if the profile photo is actually a photo of the user.
[0069] At step 305a, the AS provides the additional user data to the HSS / UDM where it is stored in the subscription profile together with the user information available from the subscription process of the user, e.g. the user had to present its passport information to themobile operator when signing up for the mobile network service contract. The AS can provide the additional user data in a Sh-Pull message containing the IMS identity and the user data.
[0070] At step 305b, the HSS / UDM acknowledges the storage of the user data to the AS. The HSS / UDM may send a Sh-Pull-Resp (4002) message to the AS.
[0071] At step 305c, the AS sends a subscription request to the HSS / UDM to subscribe to any update associated with the IMS identity, e.g. the certificate, so that the AS can sign outgoing communications from the UE. The AS may send a Sh-Subs-Notif message containing the IMS identity to the HSS / UDM.
[0072] At step 306, the IMS 110 sends a user data storage confirmation message (e.g. a 200 OK message) to the UE, confirming that the user data is successfully stored in the IMS 110. The AS can send the user data storage confirmation message to the UE via the CSCF. The UE receives the user data storage confirmation message.
[0073] At step 307, the HSS / UDM checks whether there are identity credentials available for the authenticated IMS identity (i.e. if there is a certificate for the IMS identity). The HSS / UDM checks the available user data (e.g. from the subscription process and / or provided by the UE in step 304). The HSS / UDM may request a certificate already at the point when the user signs up to the contract (e.g. if IMS services such as IMS voice services are included in the contract). In this case, the user data provided during the subscription process (e.g. passport information) of the user can be included in the certificate request. The HSS / UDM may only include verified user data in the request, e.g. user name and telephone number. Additional user data can be added as rich call data later (e.g. in a SIP INVITE), but the signature associated with the certificate would only cover the verified user data.
[0074] At step 308, when there is no certificate available for the IMS identity, the HSS / UDM sends a credential request to the issuer with the IMS identity and the available user data (i.e. the original subscription data or the user provided data).
[0075] At step 309, the issuer generates a certificate with the IMS identity and the available user data. The certificate is a digital identity certificate associated with a privatekey for signing communications, and a public key for verifying signatures. Hence, the certificate is usable to verify that the user data is that of user having the IMS identity.
[0076] At step 310, the issuer provides the certificate for the IMS identity to the HSS / UDM in the IMS 110. The issuer may send a credentials response with the certificate to the HSS / UDM.
[0077] At step 311, the HSS / UDM stores the certificate with the identity credentials (private and public key pair) for the IMS identity. The HSS / UDM may store the certificate in the subscription profile of the user.
[0078] At step 312, the HSS / UDM sends the certificate to the CR. The HSS / UDM may send an Update Credential Request to the CR containing the certificate, the IMS identity and the available user data.
[0079] At step 313, the CR acknowledges the storage of the identity certificate for the IMS identity. The CR may send an Update Credentials Response message to the HSS / UDM.
[0080] At step 314, the HSS / UDM provides the identity certificate to the AS. For example, when the AS subscribed to updates in step 305c. The HSS / UDM may say a Sh- Notif message containing the certificate to the AS.
[0081] At step 315, the AS stores the certificate for the time of the registration duration. The AS uses the certificate to sign the IMS identity and / or user data for outgoing IMS sessions (i.e. outgoing communications via the IMS) from the UE.
[0082] Figure 4 illustrates a signaling flowchart of an alternative process for managing user credentials in an IMS, wherein the HSS / UDM requests credentials via the AS. Steps 401 to 407 correspond the steps 301 to 307 of Figure 3 described above.
[0083] At step 401, the UE, for example through a Session Initiation Protocol (SIP) User Agent (UA) of the UE, sends a registration request with the IMS identity to the IMS 110. The IMS identity may be a Tel URI, a SIP URI, a IMPI, IMPU GRUU or a specific NAI for example. In case the UE belongs to an enterprise (e.g. a PBX enterprise), theregistration message may contain a wildcarded IMPU to register the number range of the enterprise. The CSCF of the IMS 110 receives the registration request from the UE.
[0084] At step 402, the UE performs authentication and authorization with the IMS 110. The HSS / UDM of the IMS 110 can authenticate the IMS identity.
[0085] At step 403, after successful authentication and authorization the CSCF send a registration confirmation message (e.g. a 200 OK message) to the UE. The UE receives the registration confirmation message and is registered with the IMS 110.
[0086] At step 404, the user might want to register user data (e.g. rich call data) in the IMS 110, e.g. a profile photo, and sends a SIP message to the IMS 110 containing the IMS identity and the user data to be registered. The user data may be received by the AS via the CSCF. The IMS 110 cannot verify the additional data from the UE. That is, the IMS cannot tell if the profile photo is actually a photo of the user.
[0087] At step 405a, the AS provides the additional user data to the HSS / UDM where it is stored in the subscription profile together with the user information available from the subscription process of the user, e.g. the user had to present its passport information to the mobile operator when signing up for the mobile network service contract. The AS can provide the additional user data in a Sh-Pull message containing the IMS identity and the user data.
[0088] At step 405b, the HSS / UDM acknowledges the storage of the user data to the AS. The HSS / UDM may send a Sh-Pull-Resp (4002) message to the AS.
[0089] At step 405c, the AS sends a subscription request to the HSS / UDM to subscribe to any update associated with the IMS identity, e.g. the certificate, so that the AS can sign outgoing communications from the UE. The AS may send a Sh-Subs-Notif message containing the IMS identity to the HSS / UDM.
[0090] At step 406, the IMS 110 sends a user data storage confirmation message (e.g. a 200 OK message) to the UE, confirming that the user data is successfully stored in the IMS 110. The AS can send the user data storage confirmation message to the UE via the CSCF. The UE receives the user data storage confirmation message.
[0091] At step 407, the HSS / UDM checks whether there are identity credentials available for the authenticated IMS identity (i.e. if there is a certificate for the IMS identity). The HSS / UDM checks the available user data (e.g. from the subscription process and / or provided by the UE in step 404). The HSS / UDM may request a certificate already at the point when the user signs up to the contract (e.g. if IMS services such as IMS voice services are included in the contract). In this case, the user data provided during the subscription process (e.g. passport information) of the user can be included in the certificate request. The HSS / UDM may only include verified user data in the request, e.g. user name and telephone number. Additional user data can be added as rich call data later (e.g. in a SIP INVITE), but the signature associated with the certificate would only cover the verified user data.
[0092] At step 408, when there is no certificate available for the IMS identity, the HSS / UDM sends a credential request to the AS (rather than directly to the issuer) with the IMS identity and the available user data (i.e. the original subscription data or the user provided data).
[0093] At steps 409, the AS sends a credential request to the issuer. The request contains the IMS identity and the available user data.
[0094] At step 410, the issuer generates a certificate with the IMS identity and the available user data. The certificate is a digital identity certificate associated with a private key for signing communications, and a public key for verifying signatures. Hence, the certificate is usable to verify that the user data is that of user having the IMS identity.
[0095] At step 411, the issuer provides the certificate for the IMS identity to the AS in the IMS 110. The issuer may send a credentials response with the certificate to the AS.
[0096] At step 412a, in response to the request in step 408, the AS provides the identity certificate to the HSS / UDM. The AS may send a Update Credentials Request containing the certificate to the HSS / UDM.
[0097] At step 412b, the AS sends the certificate to the CR. The AS may send a Update Credential Request to the CR containing the certificate, the IMS identity and the available user data.
[0098] At step 413a, the HSS / UDM stores the certificate with the identity credentials for the IMS identity. The HSS / UDM may store the certificate in the subscription profile of the user.
[0099] At step 413b, the AS stores the certificate for the time of the registration duration. The AS uses the certificate to sign the IMS identity and / or user data for outgoing IMS sessions (i.e. outgoing communications via the IMS) from the UE.
[0100] At step 414a, the HSS / UDM acknowledges the storage of the identity certificate for the IMS identity. The HSS / UDM may send an Update Credentials Response message to the AS.
[0101] At step 414b, the CR acknowledges the storage of the identity certificate for the IMS identity. The CR may send an Update Credentials Response message to the AS.
[0102] At step 414, the HSS / UDM provides the identity certificate to the AS. For example, when the AS subscribed to updates in step 405c. The HSS / UDM may say a Sh-Notif message containing the certificate to the AS.
[0103] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0104] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0105] The processor 502 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.
[0106] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the UE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
[0107] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein. The UE 500 may be configured to support a means for sending a registration request to an IMS, authenticating with the IMS, receiving registration confirmation from the IMS. The UE may further be configured support means for sending user data to the IMS.
[0108] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.
[0109] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. Thetransceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.
[0110] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 510 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0111] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0112] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606. One or more of these components may be in electronic communication orotherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0113] The processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).
[0114] The controller 602 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0115] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory address of instructions associated with the memory 604. The controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 602 may be configured to manage flowof data within the processor 600. The controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 600.
[0116] The memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600). In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600).
[0117] The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 602 and / or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions. For example, the processor 600 and / or the controller 602 may be coupled with or to the memory 604, the processor 600, the controller 602, and the memory 604 may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors and the memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0118] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 606 be configured with avariety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.
[0119] The processor 600 may support wireless communication in accordance with examples as disclosed herein. The processor 600 may be configured to or operable to support a means for registering a user equipment (UE) with the IMS, comprising authenticating an IMS identity of the UE, receiving user data associated with the UE, requesting credentials for the user data, wherein the request comprises the user data and the IMS identity, receiving a certificate for the IMS identity that certifies the user data, storing the certificate at the network entity, and sending the certificate to an application server (AS) of the IMS for signing outgoing communications from the UE via the IMS.
[0120] In an alternative embodiment, the processor 600 may be configured to or operable to support means for receiving user data from a user equipment (UE), wherein the UE is registered with the IMS and has an IMS identity, sending the user data with the IMS identity to a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS, receiving a certificate for the IMS identity that certifies the user data, storing the certificate at the network entity while the UE is registered with the IMS, and signing outgoing communications from the UE via the IMS using the certificate.
[0121] Figure 7 illustrates an example of a network entity (NE) 700 in the IMS in accordance with aspects of the present disclosure. For example, the NE 700 may be the AS 112 or the HSS / UDM 116 of the IMS 110 described in relation to Figure 1 or Figure 2 above. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces. The processor 702 may be the processor described in relation to Figure 6 above.
[0122] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0123] The processor 702 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the NE 700 to perform various functions of the present disclosure.
[0124] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the NE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
[0125] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein. The NE 700 may be configured to support a means for registering a user equipment (UE) with the IMS, comprising authenticating an IMS identity of the UE, receiving user data associated with the UE, requesting credentials for the user data, wherein the request comprises the user data and the IMS identity, receiving a certificate for the IMS identity that certifies the user data, storingthe certificate at the NE 700, and sending the certificate to an application server (AS) of the IMS for signing outgoing communications from the UE via the IMS.
[0126] The NE 700 may be a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS. The NE 700 may be configured to support a means for receiving the user data from the AS. The NE 700 may be configured to support a means for requesting credentials directly from a certificate issuer outside the IMS. The NE 700 may be configured to support a means for requesting the credentials via the AS. The NE 700 may be configured to support a means for receiving a subscription request from the AS, wherein the subscription request comprises the IMS identity, and in response to receiving the subscription request, configuring the NE 700 to automatically update the AS with information associated with the UE that is received by the NE 700 while the UE is registered to the IMS. The NE 700 may be configured to support a means for providing the certificate to a credentials repository outside the IMS. The NE 700 may be configured to support a means for receiving the user data as initial subscription data associated with the UE before registering the UE with the IMS, and storing the initial subscription data at the NE 700. The NE 700 may be configured to support a means for requesting credentials for the initial subscription data before registering the UE with the IMS, receiving a certificate for the IMS identity that certifies the initial subscription data, and, after registering the UE with the IMS, sending the certificate to the AS. The NE 700 may be configured to support a means for, in response to receiving the user data, determining if a certificate for the IMS identity that certifies the user data is stored at the NE 700, when the certificate is stored at the NE 700, sending the certificate to the AS.
[0127] In an alternative embodiment, the NE 700 may be configured to support a means for receiving user data from a user equipment (UE), wherein the UE is registered with the IMS and has an IMS identity, sending the user data with the IMS identity to a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS, receiving a certificate for the IMS identity that certifies the user data, storing the certificate at the NE 700 while the UE is registered with the IMS, and signing outgoing communications from the UE via the IMS using the certificate.
[0128] The NE 700 may be configured to support a means for sending a subscription request to the HSS or UDM, to cause the HSS or UDM to update the network entity with information associated with the UE. The NE 700 may be configured to support a means for receiving a credential request from for the user data, wherein the request comprises the user data and the IMS identity, in response to receiving the request, sending the credential request to a certificate issuer outside the IMS, and receiving from the certificate issuer a certificate for the IMS identity that certifies the user data. The NE 700 may be configured to support a means for sending the certificate to the HSS or UDM. The NE 700 may be configured to support a means for sending the certificate to a credentials repository outside the IMS.
[0129] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.
[0130] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireline transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.
[0131] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireline medium.
[0132] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets).
[0133] Figure 8 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
[0134] At 802, the method may include registering a user equipment (UE) with the IMS, comprising authenticating an IMS identity of the UE. The operations of 802 may beperformed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a NE as described with reference to Figure 7.
[0135] At 804, the method may include receiving user data associated with the UE. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a NE as described with reference to Figure 7.
[0136] At 806, the method may include requesting credentials for the user data, wherein the request comprises the user data and the IMS identity. The operations of 806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 806 may be performed by a NE as described with reference to Figure 7.
[0137] At 808, the method may include receiving a certificate for the IMS identity that certifies the user data. The operations of 808 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 808 may be performed by a NE as described with reference to Figure 7.
[0138] At 810, the method may include storing the certificate at the network entity. The operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a NE as described with reference to Figure 7.
[0139] At 812, the method may include sending the certificate to an application server (AS) of the IMS for signing outgoing communications from the UE via the IMS. The operations of 812 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 812 may be performed by a NE as described with reference to Figure 7.
[0140] Figure 9 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
[0141] At 902, the method may include receiving user data from a user equipment (UE), wherein the UE is registered with the IMS and has an IMS identity. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a NE as described with reference to Figure 7.
[0142] At 904, the method may include sending the user data with the IMS identity to a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS. The operations of 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a NE as described with reference to Figure 7.
[0143] At 906, the method may include receiving a certificate for the IMS identity that certifies the user data. The operations of 906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 906 may be performed by a NE as described with reference to Figure 7.
[0144] At 908, the method may include storing the certificate at the network entity while the UE is registered with the IMS. The operations of 908 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 908 may be performed by a NE as described with reference to Figure 7.
[0145] At 910, the method may include signing outgoing communications from the UE via the IMS using the certificate. The operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a NE as described with reference to Figure 7.
[0146] It should be noted that the method described herein describes A possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0147] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
CLAIMSWhat is claimed is:
1. A network entity for communication in an IP multimedia subsystem (IMS), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: register a user equipment (UE) with the IMS, comprising authenticating an IMS identity of the UE; receive user data associated with the UE; request credentials for the user data, wherein the request comprises the user data and the IMS identity; receive a certificate for the IMS identity that certifies the user data; store the certificate at the network entity; and send the certificate to an application server (AS) of the IMS for signing outgoing communications from the UE via the IMS.
2. The network entity of claim 1, wherein the network entity is a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS.
3. The network entity of claim 1 or 2, wherein the at least one processor is configured to cause the network entity to receive the user data from the AS.
4. The network entity of claim 1, 2 or 3, wherein the at least one processor is configured to cause the network entity to request credentials directly from a certificate issuer outside the IMS.
5. The network entity of claim 1, 2 or 3, wherein the at least one processor is configured to cause the network entity to request the credentials via the AS.
6. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to: receive a subscription request from the AS, wherein the subscription request comprises the IMS identity; and in response to receiving the subscription request, configure the network entity to automatically update the AS with information associated with the UE that is received by the network entity while the UE is registered to the IMS.
7. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to provide the certificate to a credentials repository outside the IMS.
8. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to: receive the user data as initial subscription data associated with the UE before registering the UE with the IMS; and store the initial subscription data at the network entity.
9. The network entity of claim 8, wherein the at least one processor is configured to cause the network entity to request credentials for the initial subscription data before registering the UE with the IMS; receive a certificate for the IMS identity that certifies the initial subscription data; and after registering the UE with the IMS, send the certificate to the AS.
10. The network entity of any one of the preceding claims, wherein the at least one processor is configured to cause the network entity to: in response to receiving the user data, determine if a certificate for the IMS identity that certifies the user data is stored at the network entity; and when the certificate is stored at the network entity, send the certificate to the AS.
11. A method of communication in in an IP multimedia subsystem (IMS), the method comprising, at a network entity: registering a user equipment (UE) with the IMS, comprising authenticating an IMS identity of the UE; receiving user data associated with the UE; requesting credentials for the user data, wherein the request comprises the user data and the IMS identity; receiving a certificate for the IMS identity that certifies the user data; storing the certificate at the network entity; and sending the certificate to an application server (AS) of the IMS for signing outgoing communications from the UE via the IMS.
12. The method of claim 11, where in the step of requesting credentials comprises, at the network entity, requesting credentials directly from a certificate issuer outside the IMS.
13. The method of claim 11, where in the step of requesting credentials comprises, at the network entity, requesting credentials via the AS.
14. A network entity for wireless communication in an IP multimedia subsystem (IMS), comprising: at least one memory; andat least one processor coupled with the at least one memory and configured to cause the network entity to: receive user data from a user equipment (UE), wherein the UE is registered with the IMS and has an IMS identity; send the user data with the IMS identity to a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS; receive a certificate for the IMS identity that certifies the user data; store the certificate at the network entity while the UE is registered with the IMS; and sign outgoing communications from the UE via the IMS using the certificate.
15. The network entity of claim 14, wherein the at least one processor is configured to cause the network entity to send a subscription request to the HSS or UDM, to cause the HSS or UDM to update the network entity with information associated with the UE.
16. The network entity of claim 14 or 15, wherein the at least one processor is configured to cause the network entity to: receive a credential request from for the user data, wherein the request comprises the user data and the IMS identity; in response to receiving the request, send the credential request to a certificate issuer outside the IMS; and receive from the certificate issuer a certificate for the IMS identity that certifies the user data.
17. The network entity of claim 16, wherein the at least one processor is configured to cause the network entity to send the certificate to the HSS or UDM.
18. The network entity of any one of claims 14 to 17, wherein the at least one processor is configured to cause the network entity to send the certificate to a credentials repository outside the IMS.
19. A method of communication in in an IP multimedia subsystem (IMS), the method comprising, at a network entity: receiving user data from a user equipment (UE), wherein the UE is registered with the IMS and has an IMS identity; sending the user data with the IMS identity to a Home Subscriber Server (HSS) or a Unified Data Manager (UDM) of the IMS; receiving a certificate for the IMS identity that certifies the user data; and storing the certificate at the network entity while the UE is registered with the IMS; and signing outgoing communications from the UE via the IMS using the certificate.
20. The method of claim 19, further comprising, at the network entity, sending the certificate to the HSS or UDM
