Network supported validation of a caller
The network validation service and device lobby functionality address caller ID spoofing and vishing by verifying caller identities using verifiable credentials, reducing computational burden and enhancing security in wireless communication networks.
Patent Information
- Application Number
- PCT/EP2025/062444
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication networks lack effective tools to prevent caller ID spoofing and vishing attacks, particularly affecting vulnerable populations, and existing solutions impose computational burdens and require external services during call setup.
A network validation service and device lobby functionality that verify the identity of incoming calls by using verifiable credentials, allowing users to control the exposure of identity information and providing quick verification without external issuer involvement.
This approach reduces computational burden and enhances caller ID security, preventing spoofing and vishing attacks by ensuring rapid and accurate verification of caller identities within the network.
Smart Images

Figure EP2025062444_12112026_PF_FP_ABST
Abstract
Description
Attorney Docket P112437W001 / 9900-112437W001NETWORK SUPPORTED VALIDATION OF A CALLERTECHNICAL FIELD
[0001] The present disclosure relates to wireless communication networks, and in particular to validating an identity of a user of a communication device requesting a call to another communication device.BACKGROUND
[0002] A European Union (EU) Digital Identity Wallet is the European Union's response to the challenges of digital identification. Every EU Member State offers its own wallet app, built to the same specifications, to all citizens, residents, and businesses.
[0003] The wallet allows individuals as well as businesses to securely identify themselves online when accessing a wide range of public and private services, as well as store, present and share digital documents (e.g., university diplomas or train tickets) and electronically sign or seal documents.
[0004] Each Member State will be obligated to offer at least one wallet to citizens, residents, and businesses. Each will be interoperable, working with every other national wallet, accepting the same digital documents (e.g., mobile driving licenses, university diplomas, etc.) and a digital ID (e.g., your date of birth, nationality etc.).
[0005] In a 5G network, call setup includes a Non-Access Stratum (NAS) for control signaling between a User Equipment (UE) and a 5G Core (5GC) and a Session Initiation Protocol (SIP) used within an internet protocol multimedia subsystem (IMS) for call control. The process for setting up a voice call in a 5G network includes 5G Registration where a UE performs a registration procedure with the 5G Core to obtain access to the network and services. This involves exchanging NAS messages such as Registration Request and Registration Accept. The process further includes PDU Session Establishment where a Packet Data Unit (PDU) session is established to provide data connectivity. This involves exchanging NAS messages like PDU Session Establishment Request and PDU Session Establishment Accept.
[0006] Additionally, the process includes IP Multimedia Subsystem (IMS) Registration where, once connected to the 5GC, the UE registers with the IMS network. This involves sending a Session Initiation Protocol (SIP) REGISTER message to the IMS network to indicate that the UE is available for voice services. The process further includes the UE initiating a call by sending a SIP INVITE message to the IMSAttorney Docket P112437W001 / 9900-112437W001network. This message contains information about the intended recipient of the call and the media capabilities of the UE. The IMS network and the recipient's UE exchanges provisional SIP responses (e.g., 180 Ringing) indicating that the recipient is being alerted, and once the recipient answers the call, a SIP 200 OK response being sent back to the calling UE indicating that the call has been accepted. Then, the call setup includes the calling UE sending a SIP ACK message to confirm the establishment of the session.
[0007] A dedicated Quality-of-Service (QoS) flow may be established to ensure that the voice call receives the appropriate quality of service. This involves signaling between the UE and the 5G Core to set up a QoS Flow for voice traffic. Once the call is established, media (voice) packets are exchanged between the UEs using the established QoS Flow.
[0008] Verifiable Credentials (VCs) are a standardized way of defining credentials that are cryptographically secure, privacy respecting, and machine verifiable. A VC is in many ways very similar to a public key infrastructure (PKI) certificate. A VC has a set of tamper-evident claims related to the holder of the VC (e.g., PKI certificate attributes) and credential metadata including data that cryptographically proves who issued the VC (e.g., a signature). The credential metadata has an identifier and a set of properties such as the issuer, expiry date and time, a public key (e.g., PKI certificate public key) for verification purpose, or a revocation mechanism.
[0009] When dealing with VCs there are issuers, holders, and verifiers, as well as a verifiable data registry. Each issuer, holder, and verifier associate a set of public keys to their identifier. The issuer's public keys are made publicly available, so that the verifier can validate that a VC presented by the holder has been produced by the issuer. The issuer, holder, and verifier use a verifiable data registry which maintains identifiers and schemas. The schemas describe the data structure and content of the VC. The issuer can freely define the schema, i.e., content of VC, and the verifier can, by fetching the schema, parse the content. This is one of the differences between VCs compared to PKI certificates, which have more rigid structure and content. With VCs, the content carried by the VC can freely be defined and the verifier can, using the schema, understand the content. The verifiable data registry could be a trusted database, decentralized database, government ID database, blockchain, or some other secure and accessible service.
[0010] An issuer is an organization or entity which issues digitally signed VCs to holders. The holder stores the VC. The holder could be a user or a device. A verifier is an organization or entity which verifies the VC held by the holder. For example, a university (issuer in this example) issues university certificatesAttorney Docket P112437W001 / 9900-112437W001(e.g., VCs) to its students (holder in this example). A company (verifier in this example), where the student applies for a job, verifies the VC has been issued by the university.
[0011] When using a VC towards a verifier the VC is typically used in the form of a verifiable presentation (VP). The VP contains the VC and a holder proof of the content, i.e., the holder of the VC signs the data as proof that it has provided it. The proof can also contain / cover a challenge received from the verifier (e.g., server nonce) so the VP can act as the response message to a challenge-response based authentication.
[0012] VCs support selective disclosure of data, which means that the VC holder can choose to only reveal part of the data, carried by the VC, to the verifier. As an example, the holder can choose to not reveal his surname, even if it is part of the VC. An example implementation of this, is to have the issuer sign the VC by signing the hash values of the actual data instead of the data itself. The holder can present the verifier with hash values of the parts of the data the holder does not want to reveal and the actual values of the data for the parts the holder wants to reveal. The verifier can then calculate the hash values of the received data and then verify the VC signature (over the hash values) created by the issuer.
[0013] In another example of selective disclosure implemented with VCs, the VC contains the digital identity of the user, ID (e.g. public key, or hash of public key), and a signature generated by the issuer. The data the issuer has verified is in the VC presented as hash values of the data. When the user uses the VC towards a verifier, it can provide the VC and then the verifier only learns the ID of the holder. However, if the holder wants to reveal data A (e.g. holder name) to the verifier it can do that by providing the VC and the data A to the verifier. The verifier can then generate hash(A) and verify that the signature of the VC with Hash_A is correct and thereby it shows that the value A has been verified by the issuer.
[0014] Vishing is a type of cybersecurity attack in which the perpetrator attempts to gain access to sensitive data over the phone. They typically seek financial details or Social Security numbers, but passwords and other data can also be the goal. Scammers may pretend to be an authority figure (e.g., an Internal Revenue Service agent or bank official) and claim there is a time-sensitive matter that requires immediate attention from the call recipient. Vishing scams can target individuals or companies. As opposed to online scams that use malware, vishing schemes rely on social engineering, or psychological tactics to convince victims to take a certain action. While phone scams have existed for decades, cybersecurity experts say vishing is on the rise, due to technological advances Al-poweredAttorney Docket P112437W001 / 9900-112437W001software that can mimic specific human voices and weaknesses in caller authentication, due to the feasibility of caller ID spoofing.
[0015] Spoofing is a deceptive practice where cybercriminals impersonate another entity or source, often-always with malicious intent. It can involve various techniques such as forging email addresses, manipulating caller IDs or creating counterfeit websites to trick individuals or systems into believing the spoofed entity is legitimate. These deceptive tactics lead to unauthorized access and data theft.
[0016] Caller ID spoofing is a deceptive practice where callers manipulate the information displayed on the recipient's caller ID to disguise the caller's identity and make it appear as if the call is originating from a different phone number or entity. Scammers often use this technique to trick individuals into answering calls by displaying familiar or legitimate phone numbers, such as those belonging to banks, government agencies, or trusted contacts.
[0017] In voice over internet protocol (VoIP), unlike in 3GPP-based calls, where the identity is a part of the subscription, the caller ID originates at the client end (i.e., the clients may generate control packets with arbitrarily chosen caller IDs). VoIP software may provide an interface allowing a caller to specify the user's caller ID for each phone call, making caller ID spoofing trivial.
[0018] Some services even allow their subscribers to select their own caller IDs and will deliver the selected caller IDs for their subscribers regardless of their intention. This can also be used for legitimate purposes, e.g., business organizations which display one common caller ID for outgoing calls.
[0019] Users can attempt to prevent spoofing by utilizing call blocking or Caller ID spoofing detection apps and by following recommendations on how to act in case of a suspicious caller. However, these recommendations and guidelines are not obvious and easy to apply. This is especially true if a fraudulent caller deliberately puts a targeted person in a stressful context and into a supposed time-critical event.
[0020] Some previous solutions to these problems include automatic call-back solutions where a control message or SMS is sent to the caller ID which is presented. If it is the legitimate caller, an answer is received, otherwise it is rejected. Another previous solution includes a smartphone application that has features of caller ID, call-blocking, flash-messaging, call-recording, chat and voice by using the Internet. It requires users to provide a standard cellular mobile number for registering with the service.
[0021] Yet another previous solution includes UCBIocker which leverages an authentication code for accepted callers (i.e., a subscriber identity which is allowed to contact the callee) where the callee isAttorney Docket P112437W001 / 9900-112437W001given a code which can be presented during the call and thus allow the callee to know beforehand that the caller fulfills the established policy requirements for incoming calls.
[0022] However, in the fast advances in technology and for a growing elderly population, often vulnerable and targeted for scammers, there is a lack of tools and support from technology that may help to prevent spoofing and vishing.
[0023] Automatic call-back solutions may indicate the caller ID is not correct, but if the caller ID is an unknown number and the caller introduces themselves as a known person (e.g., using an Al-generated voice) there are still significant challenges for the callee to see through the fraudulent actions and react with appropriate actions.SUMMARY
[0024] Various embodiments of the present disclosure are directed to a device validation setup procedure, a caller validation procedure, and a callee notification procedure that enables validation of an identity of a user of a communication device requesting a call to another communication device.
[0025] Some embodiments of the present disclosure are directed to a method by a first communication device for processing a call request received from a second communication device. The method includes receiving an incoming call request originating from the second communication device. The incoming call request including an identity of a network subscription of the second communication device and identity information derived from an identity certificate associated with a second user of the second communication device. The method further includes providing, to a network function, a verification request requesting verification of the second user. The verification request including the identity of the network subscription and a fingerprint of the identity information. The method includes determining whether an indication of successful validation is received, from the network function, indicating the identity of the network subscription and the fingerprint of the identity information is validated. Responsive to determining that the indication of successful validation is received from the network function, the method includes informing a first user of the first communication device of the incoming call. Responsive to determining that the indication of successful validation is not received from the network function, the method includes rejecting the incoming call.
[0026] Some other embodiments of the present disclosure are directed to a method by a network function for validating an identity of a second user of a second communication device requesting a call to a first communication device. The method includes receiving, from the second communicationAttorney Docket P112437W001 / 9900-112437W001device, identity information derived from an identity certificate of the second user. The method further includes verifying the identity certificate as being associated with an identity of a network subscription of the second communication device and the identity information as being at least a subset of the identity certificate. Additionally, responsive to verifying the identity certificate as being associated with the identity of the network subscription and the identity information as being at least a subset of the identity certificate, the method includes storing the identity of the network subscription and a fingerprint of the identity information. In response to receiving, from a first communication device, a request to verify the identity of the network subscription and the fingerprint of the identity information, the method includes verifying the identity of the network subscription and the fingerprint of the identity information. Responsive to successfully verifying the identity of the network subscription and the fingerprint of the identity information, the method includes transmitting, to the first communication device, an indication of successful verification. Responsive to not successfully verifying the identity of the network subscription and the fingerprint of the identity information, the method includes transmitting, to the first communication device, an indication of a failed verification.
[0027] The previous solutions cause unnecessary computational burden in addition to requiring a service outside of the network to be involved during call setup. Potential advantages provided by various embodiments of the present disclosure include a less time extensive and less computationally burdensome verification process for verifying the combination of the identity of the network subscription and the identity information. Some other potential advantages provided by various embodiments of the present disclosure include an improvement of caller ID being tied to digital identity wallets, where the caller has control over which information is exposed to the callee and the callee can verify the correctness of the identity information supplied. Additionally, various embodiments of the present disclosure provide a security function operative in a device that can verify and identify a caller of an incoming call or message and prevent suspicious contact attempts to come through, and a network function which can provide quick verification. In some embodiments the network provides quick verification without having to contact an issuer to verify correctness of credentials. Further potential advantages may include a network function that can assist users and reduce the risk that users drop their guards and make mistakes that may result in harm to the user caused by vishing and spoofing attacks.
[0028] Other networks, network functions, communication devices, corresponding methods, and computer program products according to embodiments of the present disclosure will be or becomeAttorney Docket P112437W001 / 9900-112437W001apparent to one with skill in the art upon review of the following drawings and detailed description. Moreover, it is intended that all embodiments disclosed herein can be implemented separately or combined in any way and / or combination.BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Embodiments of the invention will be described in the following, reference being made to the appended drawings which illustrate non-limiting examples of how the inventive concept can be reduced into practice.
[0030] Figures 1A-C illustrates an example of operations performed by a network / cloud and communication devices to verify the identity of a user of a requesting communication device, according to embodiments of the present disclosure;
[0031] Figure 2 illustrates the first communication device configured to operate according to some embodiments of the present disclosure;
[0032] Figure 3 illustrates the network function configured to operate according to some embodiments of the present disclosure;
[0033] Figure 4 illustrates a flowchart of operations by the first communication device for handling, managing, or otherwise processing a call request received from a second communication device, according to some embodiment of the present disclosure;
[0034] Figure 5 illustrates a flowchart of operations by the network function for validating an identity of a second user of a second communication device requesting a call to a first communication device, according to some embodiment of the present disclosure;
[0035] Figure 6 illustrates another flowchart of operations by the first communication device for handling, managing, or otherwise processing a call request received from a second communication device, according to some embodiment of the present disclosure;
[0036] Figure 7 illustrates another flowchart of operations by the network function for validating an identity of a second user of a second communication device requesting a call to a first communication device, according to some embodiment of the present disclosure;
[0037] Figure 8 illustrates an example of a communication system, according to some embodiment of the present disclosure;
[0038] Figure 9 illustrates another example of a communication system, according to some embodiment of the present disclosure;Attorney Docket P112437W001 / 9900-112437W001
[0039] Figure 10 illustrates a wireless device, which may be configured to operate in communication system of Figure 8 or in communication system of Figure 9, according to some embodiment of the present disclosure;
[0040] Figure 11 illustrates a network node according to some embodiment of the present disclosure; and
[0041] Figure 12 illustrates a block diagram of a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION
[0042] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of various present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present or used in another embodiment.
[0043] Some embodiments of the present disclosure provides a solution and method comprising a network validation service, and a device lobby functionality (i.e., a device lobby application) operative in a communication device, that are capable of validating identity of an incoming call (e.g., voice call, video call, etc.) or message (e.g., text, email, etc.) before allowing the call or message to reach the targeted user.
[0044] Figures 1A-C illustrates an example of operations performed by a network / cloud and communication devices to verify the identity of a user of a requesting communication device, according to embodiments of the present disclosure.
[0045] A first communication device 16 may include a smartphone, tablet, laptop computer, desktop computer, etc. with a call-reception lobby function (native or downloadable software) operative within the device. A second communication device 10 may include a smartphone, tablet, laptop computer, desktop computer, etc. and may optionally include the call-reception lobby function (native or downloadable software) operative within the device. A network 12 includes one or more network functions that are configured to provide a network service for verifying the connection between aAttorney Docket P112437W001 / 9900-112437W001identity of a network subscription and identity information provided by the second communication device 10. The issuer 14 includes a certificate issuer that provides certificates to communication devices.
[0046] Figures 1A-C includes a registration phase (e.g., operations 102-114) and a call phase which includes a caller validation procedure (e.g., operations 116-132) and a callee notification procedure (e.g., operations 134-136). In the example of Figures 1A-C, a first user worried about the increasing vishing and spoofing attacks towards elderly people, has the first communication device 16 with the device lobby function.
[0047] In the example, if a scammer calls the first user with an identity of a network subscription (e.g., caller ID) indicative of a call coming from a nearby location or a reputable source (e.g., doctor, public healthcare, municipality, etc.), the scammer's call will not pass the device lobby function and hence not be shown the Ul for the user. If the validation request to the network 12 is not acknowledged, the identity of a network subscription may not be stored in a caller log or may be stored in a separate identified fraudulent caller repository.
[0048] A similar approach to that described below can be applicable for services including short message service (SMS), over-the-top messaging applications, or other types of message service.
[0049] During a registration phase, the second communication device 10 has at least one identity certificate (also referred herein as Cl) (e.g., a driver's license and / or an EU ID card) stored in a digital wallet that is associated with the second communication device. The identity certificate may further include an issuing number (e.g., a license registration number) that uniquely identifies the certificate. In this way, the identity certificate may contain information which a caller (in this example is a second user of the second communication device 10) does want to submit to the callee (i.e., the first user of the first communication device 16), that makes the information unsuitable to send as caller identification (e.g., sensitive information). Alternatively, the user may not want to expose the identity certificate in its entirety to the network.
[0050] To avoid this, in operation 102, the second user may use the second communication device to create at least one identity information (also referred herein as C2). The identity information includes a subset of identity information present in at least one Cl. In some embodiments, the identity information may further contain identity information from two or more identity certificates (i.e., plurality of Cis).
[0051] In some embodiments, C2 is a certificate which receives a signature from the issuer 14. Some embodiments include a method to re-use the same signature on Cl using verifiable credentials. C2Attorney Docket P112437W001 / 9900-112437W001may include an identifier to present to the receiver of a call (e.g., in a mobile network). For example, C2 may include a name, company, title, date-of-birth, etc. associated with the second user.
[0052] To create C2, the second user may utilize techniques of verifiable credentials to expose a subset(s) of Cl. In some embodiments, instead of creating a subset of Cl that requires a verification from the issuer 14, C2 includes a modified version of Cl where certain fields have been replaced by a corresponding hash of the field. In such an embodiment, the hash of each information (i.e., attribute / value) in Cl is signed by the issuer 14 and can be verified by checking signature of the hashed value with a public key of the issuer 14. Hence, certain information fields can be replaced with a hash value instead. This may allow the certain information fields to be hidden from the receiver. In some of these embodiments, C2 is not a certificate but rather a verifiable presentation (VP). The same signatures used to prove the authenticity of a respective attribute in Cl may be reused also in C2. C2 may include a signature of the holder (i.e., the second user).
[0053] For example, a name of the second user could be in cleartext, while a date-of-birth of the second user is replaced by the hash value of the date-of-birth.
[0054] The hash functions provides collision resistance, meaning that it is more difficult for an attacker to find an input which will provide a specific output. This could result in the hash of the certificate being a good identifier of a standardized size.
[0055] In operation 104, the second communication device 10 supplies C2, the issuing number of Cl, and / or a signature associated with Cl to the network 12 as proof of ownership of an identity of a network subscription (e.g., a caller ID -- a public identity in the network such as a mobile station / subscriber ISDN number (MSISDN) or internet protocol multimedia subsystem public user (IMPU)). The identification of the network subscription may be stored in a SIM / eSIM in the second communication device and provided to the network. The second communication device 10 optionally supplies a verification mechanism of Cl (e.g., a public key) to the network 12.
[0056] In operation 106, the network 12 validates that the identity of the network subscription belongs to a subscription identifier (ID) of the second communication device. For example, the network 12 could validate that the identity of the network subscription belongs to the subscription ID by using the verification mechanism of Cl. Optionally, the network 12 requests validation from the issuer 14 of Cl that C2 is indeed a subset of Cl. The network 12 may further supply a nonce (e.g., a single use randomly generated number or indication) to prove the freshness of the response from the issuer 14. In operation 108, the issuer 14 responds with a new version of C2 with the nonce included in C2. In someAttorney Docket P112437W001 / 9900-112437W001embodiments, the issuer 14 responds in operation 108 with a new version of C2 with the nonce not included in C2 but is included in the response.
[0057] Optionally, the network 12 also verifies, by querying the issuer 14, that the provided public key is connected to Cl (i.e., that the public key corresponds to a private key which belongs to Cl). This could later be used to help verify the second user.
[0058] In some embodiments, validation from the issuer 14 may be achieved directly by the second communication device 10 rather than the network 12, and the proof from the issuer 14 being sent instead (i.e., the second communication device gets a verification from the issuer 14). This may happen between operation 102 and operation 104.
[0059] If validated, in operation 110, network 12 stores a hash of C2, the issuing number, the public key of Cl, and / or the identity of the network subscription in a local or remote database. This database may be located in a network node. The network function may include an identity verification function. In some embodiments, the network stores the caller ID associated with the identity of the network subscription instead of, or in addition to, the identity of the network subscription.
[0060] A user requesting a call may have a plurality of different identity certificates representing different subsets of information (e.g., corporate roles and personal roles). An identity certificate may be registered with several different identities of the network subscription / subscriber IDs.
[0061] Moreover, an identity of the network subscription may have several hashes belonging to different information sets and from different users (e.g., to represent different users operating a telephone exchange).
[0062] Optionally, in operation 112, the second communication device 10 may pre-generate call identifiers (IDs) to enable the network 12 to detect replay attacks (e.g., a fraudulent call that uses a call ID that has already been used or is not a call ID of the pre-generated call IDs). In these embodiments, the call IDs are communicated from the second communication device 10 to the network 12. The network 12 may store, in operation 114, the call IDs to the database.
[0063] This may be beneficial as an additional replay protection that is applied to protect against replayed call initiations. If an adversary is able to observe the combination of signature and call ID, they may be able to successfully spoof the identity of the second user. By the second communication device 10 pre-generating the call IDs and communicating them to the network 12, the network 12 can know what call ID to expect next and makes sure that any already used call IDs will be not successfully verified and will be rejected.Attorney Docket P112437W001 / 9900-112437W001
[0064] This process of pre-generating the call IDs and providing them to the network may be repeated when the pre-generated call IDs have been depleted or at regular time intervals.
[0065] The call phase of the example of Figures 1A-C is described below.
[0066] In operation 116, the second user selects the created C2 for requesting a call on the second communication device 10. In operation 118, the second user instructs the second communication device 10 to request the call to the first communication device 16 (e.g., using the MSISDN). The second communication device 10 creates a call request message (e.g., a session initiation protocol (SIP) INVITE).
[0067] In some embodiments, the identity verification information (e.g., C2, the issuing number of Cl, and / or a signature associated with Cl) provided to the network 12 in operation 104 is supplied to the network in the SIP INVITE message as a part of a session description protocol (SDP) in the SIP INVITE message body or as a SIP INVITE header. In embodiments where the call ID is pre-generated, the call ID of the call request is included in the SIP INVITE header.
[0068] In some embodiments, the identity verification information is included in a P-Preferred-Identity field or Authorization field and a signature of the Call ID is included in the header. In some other embodiments, the identity verification information is included in a new field in the SDP in the SIP INVITE body.
[0069] In operation 120, the second communication device 10 includes C2 in the call request message, selects a call ID, signs the call ID with a secret key belonging to Cl, and includes the signed call ID in the call request message. Additionally or alternatively, the second communication device 10 may add one of the pre-defined call IDs or a time stamp. The second communication device 10 sends the call request message with an embedded C2 and signed call ID (Sig(Call ID)) or Sig(Call ID, time stamp).
[0070] In operation 122, the network 12 forwards the call request message to the first communication device 16. The first communication device 16 receives, in operation 124, the call request message originating from the second communication device and the second user.
[0071] In operation 126, the first communication device 16 (e.g., via the device lobby function in the first communication device 16) intercepts the call and checks (i.e., determines) if the identity of the network subscription (provided with or included in the call request message) and / or presented identity information (C2) is on an allowlist and / or not on a denylist (e.g., blocked caller list).
[0072] In operation 128, if the first communication device 16 determines that the identity of the network subscription and / or presented identity information is allowed (i.e., on allowlist and / or not on the denylist), the first communication device 16 determines or otherwise calculates a fingerprint of C2. IfAttorney Docket P112437W001 / 9900-112437W001the first communication device 16 determines that the identity of the network subscription and / or presented identity information is not allowed (i.e., not on allowlist and / or on denylist), the first communication device (e.g., via the device lobby function) sends a call reject to the network 12.
[0073] Additionally, in operation 128, the first communication device 16 requests validation of the identity of the network subscription and the hash of C2 from the network 12 and sends the request for validation to the network along with the identity of the network subscription and the hash of C2.
[0074] In operation 130, the network forwards the request to a network function (e.g., an identity verification function). The network function determines if the fingerprint of C2 (and in some embodiments, the identity of the network subscription) is present in the database. The network function further validates (in operation 132) the signature with the public key associated with Cl.Optionally, the network may verify the call ID if pre-generated and provided by the second communication device.
[0075] In operation 134, if the hash of C2 is associated with the identity of the network subscription in the database, the network 12 sends an indication of successful validation to the first communication device 16. Additionally, in an optional embodiment, if the call ID does match an expected call ID, the network 12 sends the indication of successful validation to the first communication device 16.
[0076] If no such hash of C2 is associated with the identity of the network subscription in the database, the network 12 sends an indication of not successful validation to the first communication device 16. Additionally, in an optional embodiment, if the call ID does not match an expected call ID, the network 12 sends the indication of not successful validation to the first communication device 16.
[0077] In some embodiments, the indication of successful validation is included in an acknowledged (ACK) message to the first communication device. Additionally, in some embodiments, the indication of not successful validation is included in a not okay (NOK) or a not acknowledged ( NACK) message to the first communication device.
[0078] In some embodiments, if the signature can be validated by the public key and the hash of C2 is associated with the identity of the network subscription, the network 12 sends the indication of successful validation (i.e., indication that the identity of the second user has been validated) to the first communication device 16.
[0079] In operation 136, the first communication device 16 receives the indication of successful validation from the network 12 and acts according to policy. For example, the first communicationAttorney Docket P112437W001 / 9900-112437W001device informs the first user of the first communication device 16 of the call request from the second communication device (e.g., updates a user interface (Ul) with incoming call with the information in C2).
[0080] If an indication of not successful validation is received from the network 12 or the first communication device 16 does not receive an indication of successful validation from the network 12 within a threshold time period, the first communication device 16 rejects the call (e.g., denies the call, activates voicemail, displays a warning to the first user, etc.).
[0081] In some embodiments, the issuer 14, or a third party service acting on behalf of the issuer 14, provides the network 12 with pre-generated validation tokens which are associated with a specific call ID. The issuer 14 may receive a set of signed call-1 Ds by the second communication device 10 and provides them to the network. The signed call IDs may be pre-generated by the second communication device 10 similar to the pre-generated call IDs in operation 112.
[0082] The pre-generated validation tokens may come in the form of (Salt, Hash(Sig(Call-ID), Salt)). This may allow the network 12 to verify that the signature is valid without knowing the public key to verify Sig(Call-ID). A token may be stored in association with the call ID in the database.
[0083] In some of these embodiments, when the network receives the request to verify (Call-ID, Sig(Call-ID)) the network 12 may calculate Hash(Sig(Call-ID), Salt) (i.e., instead of the network function verifying a signature with a public key, the network could do a direct comparison with the hash generated from the stored token).
[0084] In an embodiment, the call request may be presented to the user regardless of the results of the verification check with the network. However, when a first user response is received (i.e., acceptance / denial of the call request from the user), the first communication device informs the first user of an indication of the results of the identity verification check with the network.
[0085] Figure 2 illustrates the first communication device 200 configured to operate according to some embodiments of the present disclosure. The first communication device 200 can include a processor(s) 210, at least one memory circuit 220, and an interface 230. The interface 230 may include wireless communication circuitry, e.g., 3GPP radio technology, Bluetooth, WiFi, RFID, NFC, Zigbee, cellular, light fidelity (Li-Fi), visible light communication (VLC), etc. and / or wired communication circuitry, e.g., Ethernet. The processor 210 may be electrically connected to the interface 230 to communicate with the network, other communication devices, etc. The processor 210 may include one or more data processing circuits, such as a general purpose and / or special purpose processor (e.g., microprocessor, digital signal processor, and / or field-programmable gate array (FPGA)). The processorAttorney Docket P112437W001 / 9900-112437W001210 is configured to execute instructions in the memory circuitry 220 (e.g., a computer readable medium) to perform some or all of the operations and methods for one or more of the embodiments disclosed herein for the first communication device.
[0086] Although the components are illustrated as separate blocks for ease of illustration, any two or more of them may be integrated into a common circuit package.
[0087] In some embodiments, the second communication device is the same or similar to the first communication device 200 but optionally includes the device lobby function.
[0088] Figure 3 illustrates the network function 300 configured to operate according to some embodiments of the present disclosure. The network function 300 is configured to operate in a communications network and can include a processor(s) 310, at least one memory circuit 320, and an interface 330. The interface 330 may include wireless communication circuitry, e.g., 3GPP radio technology, Bluetooth, WiFi, RFID, NFC, Zigbee, cellular, light fidelity (Li-Fi), visible light communication (VLC), etc. and / or wired communication circuitry, e.g., Ethernet. The processor 310 may be electrically connected to the interface 330 to communicate with other network functions, communication devices, issuer's of certificates, etc. The processor 310 may include one or more data processing circuits, such as a general purpose and / or special purpose processor (e.g., microprocessor, digital signal processor, and / or field-programmable gate array (FPGA)). The processor 310 is configured to execute instructions in the memory circuitry 320 (e.g., a computer readable medium) to perform some or all of the operations and methods for one or more of the embodiments disclosed herein for the first communication device.
[0089] Although the components are illustrated as separate blocks for ease of illustration, any two or more of them may be integrated into a common circuit package.
[0090] Figure 4 illustrates a flowchart of operations by the first communication device (e.g., first communication device 16 of Figures 1A-C or first communication device 200) for handling, managing, or otherwise processing a call request received from a second communication device, according to some embodiment of the present disclosure.
[0091] Referring to Figure 4, the first communication device receives (in operation 402) an incoming call request, originating from the second communication device. The incoming call request includes an identity of a network subscription of the second communication device and identity information (e.g., C2) derived from an identity certificate (e.g., Cl) associated with a second user of theAttorney Docket P112437W001 / 9900-112437W001second communication device. In some embodiments, operation 402 may be similarly performed by the first communication device as operation 124 of Figure IB.
[0092] The identity of the network subscription may include a caller identifier, ID. The identity information derived from the identity certificate associated with the second user of the second communication device may include a subset of information of the identity certificate of the second communication device.
[0093] The first communication device provides (in operation 404), to a network function (e.g., a network function of the network 12 of Figures 1A-C), a verification request requesting verification of the second user. The verification request may include the identity of the network subscription and a fingerprint of the identity information (e.g., fingerprint of C2). The fingerprint of the identity information may include one or more hash values generated from a hash function of the identity information. In some embodiments, operation 404 may be similarly performed by the first communication device as operation 128 of Figure 1C.
[0094] The first communication device determines (in operation 406) whether an indication of successful validation is received, from the network function, indicating the identity of the network subscription and the fingerprint of the identity information is validated. Responsive to determining that the indication of successful validation is received from the network function, the first communication device informs (in operation 408) a first user of the first communication device of the incoming call. Informing the first user of the first communication device of the incoming call may include displaying through a display (e.g., a display of the first communication device or a display in communication with the first communication device) an indication of the call request. Additionally, in some embodiments, the first communication device further informs the first user of the results of the verification by the network function (e.g., display to the user that the second user of the second communication device has been verified by the network). Responsive to determining that the indication of successful validation is not received from the network function, the first communication device rejects (in operation 410) the incoming call. Determining that the indication of successful validation is not received from the network function may include receiving an indication of not successful or failed validation from the network function or not receiving an indication of successful validation from the network function (e.g., no indication is received from the network function as a result of a lost connection between the network and the first communication device).Attorney Docket P112437W001 / 9900-112437W001
[0095] In some embodiments, operations 406-410 may be similarly performed by the first communication device as operation 136 of Figure 1C.
[0096] In some embodiments, the first communication device determines whether the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device. For example, the policy defining criteria includes an allow and / or deny list that indicates whether the credential / identity of the network subscription of a user, company, country, etc. is allowed and / or denied from calling the first user. Additionally, providing, to the network function, the verification request may be responsive to determining that the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in the policy defining criteria for allowing a call request to the first communication device. The first communication device may calculate the fingerprint of the identity information. Additionally, the calculation of the fingerprint of the identity information may be responsive to determining that the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device.
[0097] Figure 5 illustrates a flowchart of operations by the network function (e.g., a network function of the network 12 of Figures 1A-C or network function 300) for validating an identity of a second user of a second communication device requesting a call to a first communication device, according to some embodiment of the present disclosure.
[0098] Referring to Figure 5, the network function receives (in operation 502), from the second communication device (e.g., second communication device 10), identity information (e.g., C2) derived from an identity certificate (e.g., Cl) of the second user. In operation 504, the network function verifies the identity certificate as being associated with an identity of a network subscription (e.g., a caller ID) of the second communication device and the identity information as being at least a subset of the identity certificate. In some embodiments, operation 504 is performed by the network function similar to operation 106 of Figure 1A.
[0099] In some embodiments, the verifying of the identity certificate as being associated with the identity of the network subscription includes the network function transmitting an identity information verification request, to an issuer (e.g., issuer 14 of Figures 1A-C) of the identity certificate, forAttorney Docket P112437W001 / 9900-112437W001verification from the issuer that the identity information is at least a subset of the identity certificate, and the network function receiving an identity information verification response, from the issuer of the identity certificate, including an indication whether the identity information is at least a subset of the identity certificate.
[0100] The network function stores (in operation 506) the identity of the network subscription and a fingerprint of the identity information. The network function may store the identity of the network subscription and the fingerprint of the identity information responsive to verifying the identity certificate as being associated with the identity of the network subscription and the identity information as being at least a subset of the identity certificate. The fingerprint of the identity information may include one or more hash values generated from a hash function of the identity information. In some embodiments, operation 506 is performed by the network function similar to operation 110 of Figure 1A.
[0101] The network function may receive a call request message from the second communication device requesting the call to the first communication device and forward the call request message to the first communication device. In some embodiments, the call request message includes a SIP invite.
[0102] In operation 508, the network function verifies the identity of the network subscription and the fingerprint of the identity information in response to receiving, from a first communication device, a request to verify the identity of the network subscription and the fingerprint of the identity information. In some embodiments, the request includes the identity of the network subscription and the fingerprint of the identity information. Operation 508 may be performed by the network function similar to operation 130 of Figure 1C.
[0103] Responsive to successfully verifying the identity of the network subscription and the fingerprint of the identity information, the network function transmits (in operation 510), to the first communication device, an indication of successful verification. Responsive to not successfully verifying the identity of the network subscription and the fingerprint of the identity information, the network function transmits (in operation 512), to the first communication device, an indication of a failed verification.
[0104] In some embodiments, the network function receives, from the second communication device, at least one of: an issuing number (e.g., a license registration number) of the identity certificate of the second user and a signature associated with the identity certificate of the second user.Attorney Docket P112437W001 / 9900-112437W001
[0105] Additionally, or alternatively, the network function may receive, from the second communication device, a public key associated with the identity certificate. In these embodiments, the network function transmits a public key verification request, to an issuer of the identity certificate, for verification from the issuer that the public key is associated with the identity certificate. In some of these embodiments, the network function verifies the identity of the network subscription and the fingerprint of the identity information using the public key associated with the identity certificate.
[0106] The network function may receive a plurality of call identifiers from the second communication device and store the plurality of call identifiers (e.g., similar to operation 114 of Figure 1A). The network function may verify a call identifier associated with the requested call to the first communication device. The call identifier may be associated with the request call because the call identifier was provided to the network function within the call request or around a same time as the call request. Transmitting, to the first communication device, the indication of a successful verification may be further responsive to successfully verifying that the call identifier is associated with the requested call to the first communication device. Additionally, transmitting an indication of a failed verification, to the first communication device, may be further responsive to not successfully verifying that the call identifier is associated with the requested call to the first communication device.
[0107] In some embodiments, the network may initiate validation of the second user's identity. These embodiments are described below and with reference to Figures 6-7.
[0108] In these embodiments, operations 102-120 may be similar to those described above.However, unlike the example of Figures 1A-C, the network validates C2 as the call is setup. In these embodiments, the first communication device does not request the validation but rather receives an identity verification indication as a part of the call metadata. The network may verify that the attached identity certificate in or associated with a call request is connected to a subscriber identity. If there is a mismatch between the identity certificate and the subscriber identity, the call is rejected by the network.
[0109] For example, when the network receives the call request from the second communication device, the network determines if a call ID is present in the database and is associated with a subscriber ID. The network executes a proof verifier for call ID. If the call ID is not present in the database or is not associated with the subscriber ID, then the network rejects the call. In other embodiments, call ID is not verified against entries in the database and instead a time stamp is checked to determine freshness of the call request, as described previously in the application.Attorney Docket P112437W001 / 9900-112437W001
[0110] If the call ID is present in the database and is associated with the subscriber I D, then the network adds an indication that the supplied identity information has been successfully verified to a header of the call and the network forwards the call request to the first communication device. The first communication device receives the call request, originating from the second communication device. The first communication device determines if an identity of a network subscription is in an allowlist and / or denylist. , If the first communication device determines that an indication of the identity information being successfully verified has been received and the identity of the network subscription and / or presented identity information is allowed (i.e., on allowlist and / or not on the denylist), the first communication device informs the user of the incoming call. If the first communication device determines that an indication of the identity information being successfully verified has not been received or if the identity of the network subscription and / or presented identity information is not allowed (i.e., not on allowlist and / or on denylist), the first communication device (e.g., via the device lobby function) sends a call reject to the network.
[0111] Figure 6 illustrates another flowchart of operations by the first communication device (e.g., first communication device 16 of Figures 1A-C or first communication device 200) for handling, managing, or otherwise processing a call request received from a second communication device, according to some embodiment of the present disclosure.
[0112] Referring to Figure 6, the first communication device receives (in operation 602) an incoming call request originating from the second communication device. The incoming call request may include an identity of a network subscription of the second communication device and identity information (e.g., C2) derived from a first identity certificate (e.g., Cl) associated with a second user of the second communication device. The identity of the network subscription may include a caller ID. The identity information derived from the identity certificate of the second communication device may include a subset of information of the identity certificate of the second communication device.
[0113] The first communication device receives (in operation 604), from a network function, an indication whether validation of the identity information was successful (e.g., whether the subset of information of the identity certificate was successful). The first communication device determines (in operation 606) whether the first communication device has received an indication of successful validation. Responsive to receiving the indication of successful validation of the identity information, the first communication device informs (in operation 608) a first user of the first communication device of the incoming call. Responsive to the first communication device not receiving the indication ofAttorney Docket P112437W001 / 9900-112437W001successful validation (e.g., not receiving the indication of successful validation or receiving an indication of not successful validation), the first communication device rejects (in operation 610) the incoming call.
[0114] In some embodiments, the first communication device determines whether the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device. The policy defining criteria may be similar to the policy defining criteria described above. In these embodiments, informing the first user of the first communication device of the incoming call is further responsive to determining that the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device.
[0115] Figure 7 illustrates another flowchart of operations by the network function (e.g., a network function of the network 12 of Figures 1A-C or network function 300) for validating an identity of a second user of a second communication device requesting a call to a first communication device, according to some embodiment of the present disclosure. Referring to Figure 7, the network function receives (in operation 702), from the second communication device, identity information derived from a first identity certificate of the second user. The network function verifies (in operation 704) the identity certificate as being associated with an identity of the network subscription of the second communication device and the identity information as being at least a subset of the identity certificate. The identity of the network subscription may include a caller ID.
[0116] In operation 706, responsive to verifying the identity certificate as being associated with the identity of the network subscription and the identity information as being at least a subset of the identity certificate, the network function stores the identity of the network subscription and a fingerprint of the identity information. Response to receiving, from the second first communication device, a call request requesting a call to a first communication device, the network function verifies (in operation 708) the identity of the network subscription and the fingerprint of the identity information.
[0117] Responsive to successfully verifying the identity of the network subscription and the fingerprint of the identity information, the network function transmits (in operation 710), to the first communication device, an indication of successful validation of the identity information. Optionally, responsive to not successfully verifying the identity of the network subscription and the fingerprint of the identity information, the network function rejects (in operation 712) transmission of the call requestAttorney Docket P112437W001 / 9900-112437W001to the first communication device. The fingerprint of the identity information may include one or more hash values generated from a hash function of the identity information.
[0118] In some embodiments, the network function receives a plurality of call identifiers from the second communication device and stores the plurality of call identifiers (e.g., similar to operation 114 of Figure 1A). The network function may verify a call identifier associated with the requested call to the first communication device. The call identifier may be associated with the request call because the call identifier was provided to the network function within the call request or around a same time as the call request. Transmitting, to the first communication device, an indication of successful validation of the identity information may be further responsive to successfully verifying that the call identifier is associated with the requested call to the first communication device. Additionally, in the operational operation of rejecting transmission of the call request to the first communication device, rejecting transmission of the call request may be further responsive to not successfully verifying that the call identifier is associated with the requested call to the first communication device.
[0119] The verifying of the identity certificate as being associated with the identity of the network subscription may include transmitting an identity information verification request, to an issuer of the identity certificate, for verification from the issuer that the identity information is at least a subset of the identity certificate. Additionally, verifying of the identity certificate as being associated with the identity of the network subscription may include receiving an identity information verification response, from the issuer of the identity certificate, comprising an indication whether the identity information is at least a subset of the identity certificate.
[0120] In some embodiments, the network function receives, from the second communication device, a public key associated with the identity certificate. The network function may transmit a public key verification request, to an issuer of the identity certificate, for verification for verification from the issuer that the public key is associated with the identity certificate. Additionally, the verifying of the identity of the network subscription and the fingerprint of the identity information may include using the public key associated with the identity certificate.
[0121] Further definitions and embodiments are described below.
[0122] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understoodAttorney Docket P112437W001 / 9900-112437W001by one of ordinary skill in the art to which present inventive concepts belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense expressly so defined herein.
[0123] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and / or clarity. The term "and / or" includes any and all combinations of one or more of the associated listed items.
[0124] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements / operations, these elements / operations should not be limited by these terms. These terms are only used to distinguish one element / operation from another element / operation. Thus, a first element / operation in some embodiments could be termed a second element / operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.
[0125] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.Attorney Docket P112437W001 / 9900-112437W001
[0126] Example embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices) and / or computer program products. It is understood that a block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and / or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and / or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions / acts specified in the block diagrams and / or flowchart block or blocks, and thereby create means (functionality) and / or structure for implementing the functions / acts specified in the block diagrams and / or flowchart block(s).
[0127] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions / acts specified in the block diagrams and / or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and / or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.
[0128] It should also be noted that in some alternate implementations, the functions / acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Moreover, the functionality of a given block of the flowcharts and / or block diagrams may be separated into multiple blocks and / or the functionality of two or more blocks of the flowcharts and / or block diagrams may be at least partially integrated. Finally, other blocks may be added / inserted between the blocks that are illustrated, and / or blocks / operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction ofAttorney Docket P112437W001 / 9900-112437W001communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
[0129] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts is to be determined by the broadest permissible interpretation of the present disclosure including the following examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
[0130] Figure 8 shows an example of a communication system QQ100 in accordance with some embodiments.
[0131] In the example, the communication system QQ100 includes a telecommunications network QQ102 (e.g., network 12 of Figures 1A-C) that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes or base stations of various types, access network nodes QQ110A and QQ110B are depicted (which may be collectively referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network QQ104 may include more than one access network technology. The network nodes QQ110 of access network QQ104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs) or communication devices herein, such as by connecting UEs QQ112A, QQ112B, QQ112C, and QQ112D (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.
[0132] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunicationsAttorney Docket P112437W001 / 9900-112437W001network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network QQ102, including one or more access network nodes QQ110 and / or core network nodes QQ108.
[0133] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective "open" designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.
[0134] The network nodes QQ110 facilitate direct or indirect connection of one or more UEs QQ112 to the core network QQ106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0135] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ108, QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices ofAttorney Docket P112437W001 / 9900-112437W001telecommunications network QQ102) with the UEs QQ112 and / or with other network nodes or equipment in the telecommunications network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network QQ102. More specifically, UEs QQ112 may send messages, data, and / or other signals to network nodes QQ108, QQ110 or other elements of the telecommunications network QQ102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes QQ108, QQ110 may send messages, data, and other signals to UEs QQ1122, other network nodes QQ108, QQ110, and other devices in telecommunications network QQ102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message (e.g., a message that includes the indication of successful verification) to a UE QQ112 by transmitting the message to an access network node QQ110 that will then transmit the message to the intended UE QQ112. Similarly, a core network node 108 may receive a particular message (e.g., the verification request) from a UE QQ112 by receiving the message from an access network node QQ110 that itself received the message from the UE QQ112.
[0136] In the depicted example, the core network QQ106 connects elements of the access network QQ104 (e.g., one or more of the network nodes QQ110) to one or more host computing systems, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) of various types, one or more of which may be generally referred to as network nodes QQ108. Network nodes QQ108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).Attorney Docket P112437W001 / 9900-112437W001
[0137] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunications network QQ102. The host QQ116 may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0138] As a whole, the communication system QQ100 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system QQ100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system QQ100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or subsystems within the communication system QQ100 supporting different standards, protocols, or rule sets.
[0139] As one example, in certain embodiments, access network QQ104 may contain some access network nodes QQ110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes QQ110 support (or the same access network nodes QQ110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network QQ102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.Attorney Docket P112437W001 / 9900-112437W001
[0140] Telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0141] In some examples, one or more of the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio -Dual Connectivity (EN-DC).
[0142] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112C and / or QQ112D) and network nodes (e.g., network node QQ110B). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114.
[0143] As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110B. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112C and / or QQ112D), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In someAttorney Docket P112437W001 / 9900-112437W001scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110B. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0144] Figure 9 is another example of a communication system QQ200 according to some embodiments. As used herein, the communication system QQ200 includes multiple access points (APs) QQ210 (with four exemplary APs QQ210A, QQ210B, QQ210C, and QQ210D being depicted) and multiple wireless devices, referred to in the context of communication system QQ200 as stations (STAs) QQ212 (referred to individually as STA QQ212A, STA QQ212B, STA QQ212C, STA QQ212D, and STA QQ212E). STA QQ212A is served by AP QQ210A in a first basic service set (BSS) QQ220A. STA QQ210B and STA QQ210C are served by AP QQ210B in a second BSS, BSS QQ220B. STA QQ212D is served by AP QQ210C in a third BSS, BSS QQ220C. STA QQ212E is served by AP QQ210D in a fourth BSS, BSS QQ220D. Stations QQ212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations QQ212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0145] Each of STAs QQ212 may connect through a radio link to one of APs QQ210. For example, depending on location or channel conditions experienced by a given STA QQ212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0146] Each AP QQ210 may provide data connectivity to STAs QQ212 connected to a particular AP QQ210. As illustrated, APs QQ210 may be connected to a data network QQ230. In this way, APs QQ210 may also provide data connectivity between STAs QQ212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio linkAttorney Docket P112437W001 / 9900-112437W001established between a given STA QQ212 and its serving AP QQ210 may be used for providing various kinds of services to STA QQ212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA QQ212 and / or on a device linked to STA QQ212. By way of example, Figure 9 illustrates an application service platform QQ232 provided in data network QQ230. The application(s) executed on STA QQ212 and / or on one or more other devices linked to STA QQ212 may use the radio link for data communication with one or more other STA QQ212 and / or the application service platform QQ232, thereby enabling utilization of the corresponding service(s) at STA QQ212.
[0147] Figure 10 shows a wireless device QQ300, which may be configured to operate in communication system QQ100 of Figure 8 or in communication system QQ200 of Figure 9. The communication devices described above may include the same or similar features as the wireless device QQ300. The wireless device QQ300 may be alternatively referred to as a UE QQ300, like a UE QQ112 within the context of communication system QQ100, or as a station (STA) QQ300 or as a non-access-point station (non-AP STA) QQ300, like a STA QQ212 within the context of the communication system QQ200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customerpremise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0148] In particular embodiments, wireless device QQ300 includes processing circuitry QQ302 that is operatively coupled via a bus QQ304 to an input / output interface QQ306, a power source QQ308, a memory QQ310, a communication interface QQ312, and / or any other component, or any combination thereof. Certain embodiments of wireless device QQ300 may include all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one embodiment of wireless device QQ300 to another. In general, in a particular embodiment of wireless device QQ300,Attorney Docket P112437W001 / 9900-112437W001processing circuitry QQ302, input / output interface QQ306, power source QQ308, memory QQ310, and communication interface QQ312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device QQ300. Further, certain embodiments of wireless devices QQ300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0149] The processing circuitry QQ302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ310. The processing circuitry QQ302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ302 may include multiple central processing units (CPUs).
[0150] In the example, the input / output interface QQ306 (e.g., the display that informs the user of the incoming call request from the second communication device) may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device QQ300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0151] In some embodiments, the power source QQ308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. TheAttorney Docket P112437W001 / 9900-112437W001power source QQ308 may further include power circuitry for delivering power from the power source QQ308 itself, and / or an external power source, to the various parts of wireless device QQ300 via input circuitry or an interface such as an electrical power cable. Power source QQ308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device QQ300 to which power is supplied.
[0152] The memory QQ310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ310 includes one or more programs QQ314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ316. The memory QQ310 may store, for use by wireless device QQ300, any of a variety of various operating systems or combinations of operating systems.
[0153] The memory QQ310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as 'SIM card.' The memory QQ310 may allow wireless device QQ300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ310, which may be or comprise a device-readable storage medium.
[0154] The processing circuitry QQ302 may be configured to communicate with an access network or other network via or using the communication interface QQ312. The communication interface QQ312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ322. The communication interface QQ312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another deviceAttorney Docket P112437W001 / 9900-112437W001capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter QQ318 and / or a receiver QQ320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).Moreover, the transmitter QQ318 and receiver QQ320 may be coupled to one or more antennas (e.g., antenna QQ322) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0155] In the illustrated embodiment, communication functions of the communication interface QQ312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, locationbased communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR) (also referred to as 5G), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0156] In particular embodiments, wireless device QQ300 may provide an output of data captured via a sensor (e.g., microphone, camera, etc.), through its communication interface QQ312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device QQ300 can be communicated through a wireless connection to a network node via another wireless device QQ300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a voice call).
[0157] Figure 11 shows a network node QQ400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node QQ400 may be configured to operate in communication system QQ100 of Figure 8, like network nodes QQ108 orAttorney Docket P112437W001 / 9900-112437W001QQ110, or in communication system QQ200 of Figure 9, like an AP QQ210 or a station QQ212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
[0158] Network nodes QQ400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node QQ.400 may be a relay node or a relay donor node controlling a relay. Network nodes QQ400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0159] Other examples of network nodes QQ400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0160] In particular embodiments, network node QQ400 includes a processing circuitry QQ402, a memory QQ404, a communication interface QQ406, and a power source QQ408. In general, in a particular embodiment of network node QQ400, processing circuitry QQ402, memory QQ404, communication interface QQ406, and power source QQ408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node QQ400.
[0161] The network node QQ400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node QQ400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such aAttorney Docket P112437W001 / 9900-112437W001scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories QQ404 or portions of memory QQ404 for different RATs) and some components may be reused (e.g., a same antenna QQ410 may be shared by different RATs). The network node QQ400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ400.
[0162] The processing circuitry QQ402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, applicationspecific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory QQ404, to provide network node QQ400 functionality.
[0163] In some embodiments, the processing circuitry QQ402 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ402 includes one or more of radio frequency (RF) transceiver circuitry QQ412 and baseband processing circuitry QQ414. In some embodiments, the RF transceiver circuitry QQ412 and the baseband processing circuitry QQ414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ412 and baseband processing circuitry QQ414 may be on the same chip or set of chips, boards, or units.
[0164] The memory QQ404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ402. The memory QQ404 may store any suitable instructions, data, or information, including a computer program, software, an applicationAttorney Docket P112437W001 / 9900-112437W001including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ402 and utilized by the network node QQ400. The memory QQ404 may be used to store any calculations made by the processing circuitry QQ402 and / or any data received via the communication interface QQ406. In some embodiments, the processing circuitry QQ402 and memory QQ404 is integrated.
[0165] The communication interface QQ406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface QQ406 comprises port(s) / terminal(s) QQ416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node QQ300 may be capable of wireless communication and communication interface QQ406 may also include radio front-end circuitry QQ418 that may be coupled to, or in certain embodiments a part of, an antenna QQ410. Particular embodiments of radio front-end circuitry QQ418 include filter(s) QQ420 and amplifier(s) QQ422. The radio front-end circuitry QQ418 may be connected to an antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry QQ418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters QQ420 and / or amplifiers QQ422. The radio signal(s) may then be transmitted via the antenna QQ410. Similarly, when receiving data, the antenna QQ410 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ418. The digital data may be passed to the processing circuitry QQ402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0166] In certain alternative embodiments, network node QQ400 may be capable of wireless communication but does not include separate radio front-end circuitry QQ418, instead, the processing circuitry QQ402 includes radio front-end circuitry and is connected to the antenna QQ410. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ412 is part of the communication interface QQ406. In still other embodiments, the communication interface QQ406 includes one or more ports or terminals QQ416, the radio front-end circuitry QQ418, and the RF transceiver circuitry QQ412, as part of a radio unit (not shown), and the communication interface QQ406 communicates with the baseband processing circuitry QQ414, which is part of a digital unit (not shown).Attorney Docket P112437W001 / 9900-112437W001
[0167] The antenna QQ410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ410 may be coupled to the radio front-end circuitry QQ418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ410 is separate from the network node QQ400 and connectable to the network node QQ400 through one or more interfaces or ports.
[0168] The antenna QQ410, communication interface QQ406, and / or the processing circuitry QQ402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node QQ400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ410, the communication interface QQ406, and / or the processing circuitry QQ402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node QQ400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0169] The power source QQ408 provides power to the various components of network node QQ400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ400 with power for performing the functionality described herein. For example, the network node QQ400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ408. As a further example, the power source QQ408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0170] Embodiments of the network node QQ400 may include additional components beyond those shown in Figure 11 for providing certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ400 may include user interface equipment to allow input of information into the network node QQ400 and to allow output of information from the network node QQ400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ400.Attorney Docket P112437W001 / 9900-112437W001
[0171] Figure 12 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0172] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0173] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM QQ508A and VM QQ508B (which may be collectively referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs QQ508.
[0174] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contextsAttorney Docket P112437W001 / 9900-112437W001referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
[0175] In the context of NFV, each of the VMs QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs QQ508 on top of the hardware QQ504 and corresponds to an application QQ502.
[0176] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.
[0177] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and asAttorney Docket P112437W001 / 9900-112437W001a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0178] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
Claims
Attorney Docket P112437W001 / 9900-112437W001CLAIMS:
1. A method by a first communication device for processing a call request received from a second communication device, the method comprising:receiving (402) an incoming call request, originating from the second communication device, comprising an identity of a network subscription of the second communication device and identity information derived from an identity certificate associated with a second user of the second communication device;providing (404), to a network function, a verification request requesting verification of the second user, the verification request comprising the identity of the network subscription and a fingerprint of the identity information;determining (406) whether an indication of successful validation is received, from the network function, indicating the identity of the network subscription and the fingerprint of the identity information is validated;informing (408) a first user of the first communication device of the incoming call, responsive to determining that the indication of successful validation is received from the network function; and rejecting (410) the incoming call, responsive to determining that the indication of successful validation is not received from the network function.
2. The method according to Claim 1, wherein the identity of the network subscription comprises a caller identifier, ID.
3. The method according to any of Claims 1 to 2, wherein the identity information derived from the identity certificate associated with the second user of the second communication device comprises a subset of information of the identity certificate of the second communication device.
4. The method according to any of Claims 1 to 3, further comprising:determining whether the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device, andAttorney Docket P112437W001 / 9900-112437W001wherein providing, to the network function, the verification request is responsive to determining that the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in the policy defining criteria for allowing a call request to the first communication device.
5. The method according to Claim 4, further comprising:calculating the fingerprint of the identity information, responsive to determining that the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device.
6. The method according to any of Claims 1 to 5, wherein the fingerprint of the identity information comprises one or more hash values generated from a hash function of the identity information.
7. A method by a network function for validating an identity of a second user of a second communication device requesting a call to a first communication device, the method comprising:receiving (502), from the second communication device, identity information derived from an identity certificate of the second user;verifying (504) the identity certificate as being associated with an identity of a network subscription of the second communication device and the identity information as being at least a subset of the identity certificate;storing (506) the identity of the network subscription and a fingerprint of the identity information, responsive to verifying the identity certificate as being associated with the identity of the network subscription and the identity information as being at least a subset of the identity certificate;verifying (508) the identity of the network subscription and the fingerprint of the identity information in response to receiving, from a first communication device, a request to verify the identity of the network subscription and the fingerprint of the identity information;transmitting (510), to the first communication device, an indication of successful verification, responsive to successfully verifying the identity of the network subscription and the fingerprint of the identity information; andAttorney Docket P112437W001 / 9900-112437W001transmitting (512), to the first communication device, an indication of a failed verification, responsive to not successfully verifying the identity of the network subscription and the fingerprint of the identity information.
8. The method according to Claim 7, further comprising:receiving, from the second communication device, at least one of: an issuing number of the identity certificate of the second user and a signature associated with the identity certificate of the second user.
9. The method according to any of Claims 7 to 8, wherein the identity of the network subscription comprises a caller identifier, ID.
10. The method according to any of Claims 7 to 8, wherein verifying the identity certificate as being associated with the identity of the network subscription comprises:transmitting an identity information verification request, to an issuer of the identity certificate, for verification from the issuer that the identity information is at least a subset of the identity certificate, andreceiving an identity information verification response, from the issuer of the identity certificate, comprising an indication whether the identity information is at least a subset of the identity certificate.
11. The method according to any of Claims 7 to 8, further comprising:receiving, from the second communication device, a public key associated with the identity certificate.
12. The method according to 11, further comprising:transmitting a public key verification request, to an issuer of the identity certificate, for verification from the issuer that the public key is associated with the identity certificate.Attorney Docket P112437W001 / 9900-112437W00113. The method according to any of Claims 11 to 12, wherein verifying the identity of the network subscription and the fingerprint of the identity information comprises using the public key associated with the identity certificate.
14. The method according to any of Claims 7 to 13, wherein the fingerprint of the identity information comprises one or more hash values generated from a hash function of the identity information.
15. The method according to any of Claims 7 to 14, further comprising:receiving a plurality of call identifiers from the second communication device;storing the plurality of call identifiers;verifying a call identifier associated with the requested call to the first communication device; wherein transmitting, to the first communication device, the indication of a successful verification is further responsive to successfully verifying that the call identifier is associated with the requested call to the first communication device; andwherein transmitting an indication of a failed verification, to the first communication device, is further responsive to not successfully verifying that the call identifier is associated with the requested call to the first communication device.
16. The method according to any of Claims 7 to 15, further comprising:receiving a call request message from the second communication device requesting the call to the first communication device, andforwarding the call request message to the first communication device.
17. The method according to Claim 16, wherein the call request message comprises a session initiation protocol (SIP) invite.
18. A first communication device (16, 200) for processing a call request received from a second communication device (10), the first communication device (16, 200) operative to:receive an incoming call request, originating from the second communication device (10), comprising an identity of a network subscription of the second communication device and identityAttorney Docket P112437W001 / 9900-112437W001information derived from an identity certificate associated with a second user of the second communication device (10);provide, to a network function (12, 300), a verification request requesting verification of the second user, the verification request comprising the identity of the network subscription and a fingerprint of the identity information;determine whether an indication of successful validation is received, from the network function, indicating whether at least one of the identity of the network subscription and the fingerprint of the identity information is validated;inform a first user of the first communication device (16, 200) of the incoming call, responsive to determining that the indication of successful validation is received from the network function (12, 300); andreject the incoming call, responsive to determining that the indication of successful validation is not received from the network function (12, 300).
19. The first communication device (16, 200) according to Claim 18, wherein the identity of the network subscription comprises a caller identifier, ID.
20. The first communication device (16, 200) according to any of Claims 18 to 21, wherein the identity information derived from the identity certificate associated with the second user of the second communication device (10) comprises a subset of information of the identity certificate of the second communication device (10).
21. The first communication device (16, 200) according to any of Claims 18 to 20, further operative to:determine whether the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device (10) is included in a policy defining criteria for allowing a call request to the first communication device (16, 200), andwherein providing, to the network function (12, 300), the verification request is responsive to determining that the identity of the network subscription or the identity information derived from theAttorney Docket P112437W001 / 9900-112437W001identity certificate associated with the second user of the second communication device (10) is included in the policy defining criteria for allowing a call request to the first communication device (16, 200).
22. The first communication device (16, 200) according to Claim 21, further operative to: calculate the fingerprint of the identity information, responsive to determining that the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device (10) is included in a policy defining criteria for allowing a call request to the first communication device (16, 200).
23. The first communication device (16, 200) according to any of Claims 18 to 22, wherein the fingerprint of the identity information comprises one or more hash values generated from a hash function of the identity information.
24. A network function (12, 300) for validating an identity of a second user of a second communication device (10) requesting a call to a first communication device (16, 200), the network function (12, 300) operative to:receive, from the second communication device (10), identity information derived from an identity certificate of the second user;verify the identity certificate as being associated with an identity of a network subscription of the second communication device and the identity information as being at least a subset of the identity certificate;store the identity of the network subscription and a fingerprint of the identity information, responsive to verifying the identity certificate as being associated with the identity of the network subscription and the identity information as being at least a subset of the identity certificate;verify the identity of the network subscription and the fingerprint of the identity information in response to receiving, from a first communication device (16, 200), a request to verify the identity of the network subscription and the fingerprint of the identity information;transmit, to the first communication device (16, 200), an indication of successful verification, responsive to successfully verifying the identity of the network subscription and the fingerprint of the identity information; andAttorney Docket P112437W001 / 9900-112437W001transmit an indication of a failed verification, to the first communication device (16, 200), responsive to not successfully verifying the identity of the network subscription and the fingerprint of the identity information.
25. The network function (12, 300) according to Claim 24, further operative to: receive, from the second communication device (10), at least one of: an issuing number of the identity certificate of the second user and a signature associated with the identity certificate of the second user.
26. The network function (12, 300) according to any of Claims 24 to 25, wherein the identity of the network subscription comprises a caller identifier, ID.
27. The network function (12, 300) according to any of Claims 24 to 25, wherein verifying the identity certificate as being associated with the identity of the network subscription comprises: transmitting an identity information verification request, to an issuer of the identity certificate, for verification from the issuer that the identity information is at least a subset of the identity certificate, andreceiving an identity information verification response, from the issuer of the identity certificate, comprising an indication whether the identity information is at least a subset of the identity certificate.
28. The network function (12, 300) according to any of Claims 24 to 25, further operative to:receive, from the second communication device (10), a public key associated with the identity certificate.
29. The network function (12, 300) according to 28, further operative to:transmit a public key verification request, to an issuer of the identity certificate, for verification for verification from the issuer that the public key is associated with the identity certificate.Attorney Docket P112437W001 / 9900-112437W00130. The network function (12, 300) according to any of Claims 28 to 29, wherein verifying the identity of the network subscription and the fingerprint of the identity information comprises using the public key associated with the identity certificate.
31. The network function (12, 300) according to any of Claims 24 to 30, wherein the fingerprint of the identity information comprises one or more hash values generated from a hash function of the identity information.
32. The network function (12, 300) according to any of Claims 24 to 31, further operative to: receive a plurality of call identifiers from the second communication device (10);store the plurality of call identifiers;verify a call identifier associated with the requested call to the first communication device (16, 200); andwherein transmitting, to the first communication device (16, 200), the indication of a successful verification is further responsive to successfully verifying that the call identifier is associated with the requested call to the first communication device (16, 200);wherein transmitting an indication of a failed verification, to the first communication device (16, 200), is further responsive to not successfully verifying that the call identifier is associated with the requested call to the first communication device (16, 200).
33. The network function (12, 300) according to any of Claims 24 to 32, further operative to:receive a call request message from the second communication device (10) requesting the call to the first communication device (12, 200), andforward the call request message to the first communication device (12, 200).
34. The network function (12, 300) according to Claim 33, wherein the call request message comprises a session initiation protocol (SIP) invite.
35. A method by a first communication device for processing a call request received from a second communication device, the method comprising:Attorney Docket P112437W001 / 9900-112437W001receiving (602) an incoming call request, originating from the second communication device, comprising an identity of a network subscription of the second communication device and identity information derived from a first identity certificate associated with a second user of the second communication device;receiving (604), from a network function, an indication whether validation of the identity information was successful;informing (608) a first user of the first communication device of the incoming call, responsive to an indication of successful validation of the identity information being received.; andrejecting (610) the incoming call, responsive to the indication of successful validation not being received.
36. The method according to Claim 35, wherein the identity of the network subscription comprises a caller identifier, ID.
37. The method according to any of Claims 35 to 36, wherein the identity information derived from the identity certificate of the second communication device comprises a subset of information of the identity certificate of the second communication device.
38. The method according to any of Claims 35 to 37, further comprising: determining whether the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device, andwherein informing (608) the first user of the first communication device of the incoming call is further responsive to determining that the identity of the network subscription or the identity information derived from the identity certificate associated with the second user of the second communication device is included in a policy defining criteria for allowing a call request to the first communication device.
39. A method by a network function for validating an identity of a second user of a second communication device requesting a call to a first communication device, the method comprising:Attorney Docket P112437W001 / 9900-112437W001receiving (702), from the second communication device, identity information derived from a first identity certificate of the second user;verifying (704) the identity certificate as being associated with an identity of the network subscription of the second communication device and the identity information as being at least a subset of the identity certificate;storing (706) the identity of the network subscription and a fingerprint of the identity information, responsive to verifying the identity certificate as being associated with the identity of the network subscription and the identity information as being at least a subset of the identity certificate;verifying (708) the identity of the network subscription and the fingerprint of the identity information in response to receiving, from the second first communication device, a call request requesting a call to a first communication device; andtransmitting (710), to the first communication device, an indication of successful validation of the identity information, responsive to successfully verifying the identity of the network subscription and the fingerprint of the identity information.
40. The method according to Claim 39, wherein the identity of the network subscription comprises a caller identifier, ID.
41. The method according to any of Claims 39 to 40, wherein verifying the identity certificate as being associated with the identity of the network subscription comprises:transmitting an identity information verification request, to an issuer of the identity certificate, for verification from the issuer that the identity information is at least a subset of the identity certificate, andreceiving an identity information verification response, from the issuer of the identity certificate, comprising an indication whether the identity information is at least a subset of the identity certificate.
42. The method according to any of Claims 39 to 40, further comprising:receiving, from the second communication device, a public key associated with the identity certificate.Attorney Docket P112437W001 / 9900-112437W00143. The method according to 42, further comprising:transmitting a public key verification request, to an issuer of the identity certificate, for verification for verification from the issuer that the public key is associated with the identity certificate.
44. The method according to any of Claims 42 to 43, wherein verifying the identity of the network subscription and the fingerprint of the identity information comprises using the public key associated with the identity certificate.
45. The method according to any of Claims 39 to 44, wherein the fingerprint of the identity information comprises one or more hash values generated from a hash function of the identity information.
46. The method according to any of Claims 39 to 45, further comprising:receiving a plurality of call identifiers from the second communication device;storing the plurality of call identifiers;verifying a call identifier associated with the requested call to the first communication device; andwherein transmitting, to the first communication device, the indication of successful validation of the identity information is further responsive to successfully verifying that the call identifier is associated with the requested call to the first communication device.
47. The method according to any of Claims 39 to 46, further comprising:rejecting (712) transmission of the call request to the first communication device, responsive to not successfully verifying the identity of the network subscription and the fingerprint of the identity information.
