Authorizing third party specific user identity

By introducing NEF and AAA servers in the wireless communication system, using the mechanism of SIP INVITE messages and enterprise business card, third-party user identity authorization is carried out based on token verification, which solves the inefficient third-party user identity authentication and authorization in the prior art The problem improves the security of the system and the accuracy of user authentication.

CN118923080APending Publication Date: 2024-11-08QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093920.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-03-29
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing wireless communication systems have problems of inefficiency and insufficient security when authenticating and authorizing third-party specific user identities, especially in a multi-access technology environment, which is difficult to effectively verify and authorize third-party user identities.

Method used

By introducing network exposure function (NEF) and authentication, authorization and accounting (AAA) servers in wireless communication systems, using the mechanism of SIP INVITE messages and enterprise business cards, authorization and authentication of third-party user identity based on token verification. And implement authorization and indication of third-party specific user identities in the call session control function (CSCF).

Benefits of technology

It improves the efficiency and security of third-party user identity authentication and authorization in wireless communication systems, ensures the legitimacy of call sessions and the accuracy of user identity, and enhances the security and user experience of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923080A_ABST
    Figure CN118923080A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, an authentication, authorization, and accounting (AAA) server may authorize use of a third-party specific user identity based at least in part on verifying a token associated with a session initiation protocol (SIP) INVITE message having the third-party specific user identity. The (AAA) server may send an enterprise business card to a call session control function (CSCF) of an originating service provider via a network exposure function (NEF) of the originating service provider, the enterprise business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for authorizing a third party to identify a particular user. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] In some specific implementations, an apparatus for a call session control function (CSCF) of an originating service provider for wireless communications includes a memory, and one or more processors coupled to the memory, the one or more processors being configured to: receive a SIP INVITE message with a third-party specific user identity and a token from a Session Initiation Protocol (SIP) user agent (UA) of the originating service provider; send the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); and receive a corporate business card indicating the third-party specific user identity from the AAA server via the NEF, wherein the corporate business card is received based at least in part on verification of the token.

[0006] In some specific implementations, an authentication device includes a memory, and one or more processors coupled to the memory, the one or more processors configured to: authorize the use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message having the third-party specific user identity; and send a corporate business card to a CSCF of an originating service provider via an NEF of an originating service provider, the corporate business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.

[0007] In some specific implementations, a method of wireless communication performed by a CSCF of an originating service provider for wireless communication includes receiving a SIP INVITE message with a third-party specific user identity and a token from a SIP UA of the originating service provider; sending a SIP INVITE message to an AAA server via an NEF; and receiving a corporate business card indicating the third-party specific user identity from the AAA server via the NEF, wherein the corporate business card is received based at least in part on verification of the token.

[0008] In some specific implementations, a method of wireless communication performed by authentication includes authorizing the use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message with the third-party specific user identity; and sending a corporate business card to a CSCF of an originating service provider via an NEF of an originating service provider, the corporate business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.

[0009] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of the CSCF of an originating service provider, cause the CSCF of the originating service provider to: receive a SIP INVITE message with a third-party specific user identity and a token from the SIP UA of the originating service provider; send the SIP INVITE message to an AAA server via an NEF; and receive a corporate business card indicating the third-party specific user identity from the AAA server via the NEF, wherein the corporate business card is received based at least in part on verification of the token.

[0010] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of an AAA server, cause the AAA server to: authorize use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message having the third-party specific user identity; and send a corporate business card to a CSCF of an originating service provider via an NEF of an originating service provider, the corporate business card indicating the third-party specific user identity based at least in part on authorizing use of the third-party specific user identity.

[0011] In some specific implementations, an apparatus for wireless communication includes a component for receiving a SIP INVITE message with a third-party specific user identity and a token from a SIP UA of an originating service provider; a component for sending the SIP INVITE message to an AAA server via an NEF; and a component for receiving a corporate business card indicating the third-party specific user identity from the AAA server via the NEF, wherein the corporate business card is received based at least in part on verification of the token.

[0012] In some specific implementations, an apparatus for wireless communication includes a component for authorizing the use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message having the third-party specific user identity; and a component for sending a corporate business card to a CSCF of an originating service provider via an NEF of an originating service provider, the corporate business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.

[0013] The various aspects as a whole include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, AAA servers, CSCFs of originating service providers, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0014] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of a decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of a Signature-based Processing of Assertion Information Using Tokens (SHAKEN) framework according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of a SHAKEN reference call flow according to the present disclosure.

[0022] Figure 6 is a diagram illustrating an example associated with a SHAKEN framework including a third-party authentication, authorization, and accounting server and a call session control function according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example associated with authorizing a third-party specific user identity according to the present disclosure.

[0024] Figure 8 is a diagram illustrating an example of association with a business card indicating an identity of a third-party specific user according to the present disclosure.

[0025] Figures 9 and 10 is a diagram illustrating an example process associated with authorizing a third party specific user identity according to the present disclosure.

[0026] Figure 11 to Figure 12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0030] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0031] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0032] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0033] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0034] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG. 1 , BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0035] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0037] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0038] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0039] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0040] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0042] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. The latest 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0043] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] In some aspects, as described in more detail elsewhere herein, a call session control function (CSCF) of an originating service provider (e.g., CSCF 112) may receive a SIP INVITE message with a third-party specific user identity and a token from a Session Initiation Protocol (SIP) user agent (UA) of the originating service provider; send the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); and receive a business card indicating the third-party specific user identity from the AAA server via the NEF, wherein the business card is received based at least in part on the verification of the token. Additionally or alternatively, the CSCF of the originating service provider may perform one or more other operations described herein.

[0045] In some aspects, as described in more detail elsewhere herein, an AAA server (e.g., AAA server 111) may authorize the use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message with the third-party specific user identity; and send a business card to the CSCF of the originating service provider via the NEF of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity. Additionally or alternatively, the AAA server may perform one or more other operations described herein.

[0046] As indicated above, Figure 1 Other examples can be found in the Figure 1 Different than described.

[0047] Figure 22 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0048] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0050] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0051] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0052] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 6 to 12 ) any aspects of any method described.

[0053] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 6 to 12 ) any aspects of any method described.

[0054] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the AAA server may perform one or more techniques associated with authorizing a third party specific user identity as described in more detail elsewhere herein. In some aspects, the third party AAA server and CSCF described herein are Figure 2 The base station 110 shown is included in the base station 110, or includes one or more components of the base station 110. In some aspects, the SIP UA described herein is Figure 2 The UE 120 shown is included in the UE 120, or includes one or more components of the UE 120. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Fig. 9 The process of 900 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, enable the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Fig. 9 The process of 900 Fig.10 The process 1000 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0055] In some aspects, the CSCF of the originating service provider (e.g., CSCF 112) includes a component for receiving a SIP INVITE message with a third-party specific user identity and a token from a SIP UA of the originating service provider; a component for sending the SIP INVITE message to an AAA server via the NEF; and / or a component for receiving a business card indicating a third-party specific user identity from the AAA server via the NEF, wherein the business card is received based at least in part on the verification of the token. In some aspects, the components for the CSCF of the originating service provider to perform the operations described herein may include, for example, one or more of a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0056] In some aspects, the AAA server (e.g., AAA server 111) includes a component for authorizing the use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message with the third-party specific user identity; and / or a component for sending a business card to the CSCF of the originating service provider via the NEF of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity. In some aspects, the components for the AAA server to perform the operations described herein may include, for example, one or more of the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0057] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0058] As indicated above, Figure 2 Other examples can be found in the Figure 2 Different than described.

[0059] Figure 3 is a diagram illustrating an example 300 of a disaggregated base station architecture according to the present disclosure.

[0060] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment (such as a base station (BS, e.g., base station 110) or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5G NB, an access node (AP), a TRP, a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone BS or a monolithic BS) or a decomposed base station.

[0061] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0062] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an IAB network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0063] Figure 3 The decomposed base station architecture shown may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0064] Each of these units (e.g., CU 310, DU 330, RU 340), as well as near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0065] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0066] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0067] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0068] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0069] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0070] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0071] As indicated above, Figure 3 Other examples can be found in the Figure 3 Different than described.

[0072] The SHAKEN framework can utilize a protocol that provides an end-to-end architecture for authentication and assertion of a caller identifier (ID) by an originating service provider and verification of the caller ID by a terminating service provider. The SHAKEN framework can be used by telephone service providers to deliver telephone calls over Voice over Internet Protocol (IP) (VoIP). The caller ID can be an originating or calling party telephone number that identifies the caller. The caller ID can be carried in a P-Asserted Identity or a form header of a Session Initiation Protocol (SIP) message.

[0073] Figure 4 is a diagram illustrating an example 400 of a SHAKEN framework according to the present disclosure.

[0074] The originating IP Multimedia Subsystem (IMS) network may be hosted by service provider A, and the terminating IMS network may be hosted by service provider B. In other words, the originating service provider may be service provider A, and the terminating service provider may be service provider B. The SIP User Agent (UA) may be authenticated by an originating service provider (OSP) network (e.g., associated with service provider A). When the SIP UA is under direct management control of the OSP network, the OSP network may assert the caller identity in an originating SIP INVITE request initiated by the SIP UA. The IMS / Call Session Control Function (CSCF) may represent a SIP registrar and routing function. The CSCF may be a SIP server or a CSCF server. The Interconnection Border Control Function (IBCF) / Transition Gateway (TrGW) may be a function at the edge of a service provider network (e.g., a service provider network associated with service provider A or service provider B), which represents a network-to-network interface (NNI) or peering point between telephone service providers, and the IBCF / TrGW may be an entry and exit point for SIP calls between providers.

[0075] A secure telephone identity (STI) authentication service (STI-AS) may be a SIP application server that performs the function of an authentication service. The STI-AS may be a secure key storage (SKS) that is secure and contains a secret private key, or have an authenticated transport layer security (TLS) encryption interface to the SKS that stores a secret private key for creating a personal assertion token (PASSporT) signature. The SKS may be a logically highly secure element that stores a secret private key for access by the STI-AS. The STI verification service (STI-VS) may be a SIP application server that performs the function of a verification service. The STI-VS may have a hypertext transfer protocol secure (HTTPS) interface to a secure telephone identity certificate repository that is referenced in an identity header field to retrieve a provider public key certificate. A call verification process (CVT) may be a logical function (e.g., an application server function or a third-party application) for applying call analysis and processing techniques after a signature is positively or negatively verified. A certificate provision service may be a logical service for providing certificates for STI. The Secure Phone Identity Certificate Repository (STI-CR) may be a publicly accessible store for public key certificates.

[0076] As indicated above, Figure 4 Other examples can be found in the Figure 4 Different than described.

[0077] Figure 5 is a diagram illustrating an example 500 of a SHAKEN reference call flow according to the present disclosure.

[0078] As shown in reference numeral 502, the SIP UA of the originating service provider, which may first be registered and authenticated with the CSCF of the originating service provider, may create a SIP INVITE message with a phone identity. The phone identity may be an identifier associated with the originator of the phone call. In the SHAKEN framework, the phone identity may be a SIP identity (e.g., a SIP Uniform Resource Identifier (URI)) from which a phone number may be derived. As shown in reference numeral 504, the CSCF of the originating service provider may add a "Private Extension of SIP for Asserted Identity" (P-Asserted-Identity) header field asserting the caller ID of the SIP UA of the originating service provider. The CSCF of the originating service provider may initiate an initiation trigger to the STI-AS of the originating service provider for the SIP INVITE message. As shown in reference numeral 506, the STI-AS of the originating service provider may use a service provider specific mechanism to determine the legitimacy of using the phone identity in the SIP INVITE message. The STI-AS of the originating service provider may securely request its private key from the SKS of the originating service provider.

[0079] As shown in reference numeral 508, the SKS of the originating service provider can provide a private key in the response, and the STI-AS of the originating service provider can sign the SIP INVITE message, and can use the caller ID in the identity header field of the P assertion to add the identity header field. As shown in reference numeral 510, the STI-AS of the originating service provider can provide the SIP INVITE message back to the CSCF of the originating service provider. As shown in reference numeral 512, the CSCF of the originating service provider can route the phone call and the SIP INVITE message to the IBCF (e.g., the egress IBCF) of the originating service provider. As shown in reference numeral 514, the SIP INVITE message can be routed on the NNI using a standard inter-domain routing configuration. As shown in reference numeral 516, the IBCF (e.g., the ingress IBCF) of the terminating service provider can receive the SIP INVITE message through the NNI. As shown in reference numeral 518, the CSCF of the terminating service provider can initiate a termination trigger to the STI-VS of the terminating service provider for the SIP INVITE message.

[0080] As shown in reference numeral 520, the STI-VS of the terminating service provider can use a field in the PASSport protection header to determine the STI certificate repository (STI-CR) URI and perform an HTTPS request to the referenced STI-CR. As shown in reference numeral 522, the STI-VS of the terminating service provider can verify the certificate and then extract the public key. The STI-VS of the terminating service provider can use the public key to verify the signature in the identity header field, which can verify the caller ID used when the SIP INVITE message is signed by the STI-AS of the originating service provider. As shown in reference numeral 524, the CVT can be an optional function that can be called to perform call analysis or other spam mitigation techniques. The CVT can be integrated within the service provider network of the terminating service provider, or can be integrated outside the service provider network by a third party. As shown in reference numeral 526, based on the result of the STI verification, the STI-VS of the terminating service provider can determine that the phone call is to be completed with an appropriate value, and the SIP INVITE message can be passed back to the CSCF of the terminating service provider, which can continue to establish a phone call to the SIP UA of the terminating service provider. As indicated by reference numeral 528, the SIP UA of the terminating service provider may receive the SIP INVITE message and normal SIP processing of the telephone call may continue.

[0081] As indicated above, Figure 5 Other examples can be found in the Figure 5 Different than described.

[0082] Illegal caller ID spoofing is a concern for both telephone service providers and customers. The Secure Telephone Identity Revalidation (STIR) / SHAKEN framework may provide an end-to-end architecture for authentication and assertion of caller ID by an originating service provider and verification of that identity by a terminating service provider. However, the STIR / SHAKEN framework does not provide a mechanism for authenticating other types of caller information by an originating service provider and validating such other types of caller information by a terminating service provider.

[0083] In various aspects of the techniques and devices described herein, the STIR / SHAKEN framework can be enhanced to support the use of third-party specific user identities. The STIR / SHAKEN framework can be modified to incorporate a third-party AAA server and a network exposure function (NEF). The third-party AAA server can authorize the use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message. The SIP INVITE message can be created by a SIP UA of an originating service provider to include a third-party specific user identity and a token. The third-party AAA server can send a business card to a CSCF of an originating service provider via the NEF, which indicates the third-party specific user identity based at least in part on authorizing the use of a third-party specific user identity. The business card can be sent to a SIP UA of a terminating service provider to be displayed on the SIP UA of the terminating service provider. The business card can indicate other types of caller information (e.g., information other than caller ID), such as a user, a photo of the user, a user identifier, and / or a company associated with the user, wherein the business card can be authorized using a third-party AAA server. Therefore, third-party specific user identities can be supported in the STIR / SHAKEN framework.

[0084] Figure 6 is a diagram illustrating an example 600 associated with a SHAKEN framework including a third-party AAA server (eg, AAA server 111) and a CSCF (eg, CSCF 112) according to the present disclosure. "Third-party AAA server" and "AAA server" are used interchangeably herein.

[0085] The SHAKEN framework may include an originating IMS network and a terminating IMS network. The originating IMS network may be hosted by an originating service provider (e.g., service provider A), and the terminating IMS network may be hosted by a terminating service provider (e.g., service provider B). The originating service provider may include a SIP UA, a CSCF, a STI-AS, a SKS, and an IBCF / TrGW. The terminating service provider may include a SIP UA, a CSCF, a STI-VS, a CVT, and an IBCF / TrGW. In addition, the SHAKEN framework may include a certificate provisioning service and an STI-CR. Figure 4 These elements and related functionality are further described.

[0086] In some aspects, the SHAKEN framework may include a third-party AAA server and NEF. The third-party AAA server, NEF, the SIP UA of the originating service provider, and the CSCF of the originating service provider may be used to support the use of third-party specific user identities.

[0087] In some aspects, the SIP UA of the originating service provider may initiate a telephone call with the SIP UA of the terminating service provider. The SIP UA of the originating service provider may create a SIP INVITE message with a third-party specific user identity and a token, which may be assigned to the SIP UA of the originating service provider by a third-party AAA server. The third-party AAA server may interact with the CSCF of the originating service provider via the NEF of the originating service provider to authorize the use of the third-party specific user identity by the SIP UA of the originating service provider. The third-party AAA server may verify the token of the SIP UA of the originating service provider to authorize the use of the third-party specific user identity. The verification of the token may be based at least in part on the signaling between the third-party AAA server and the CSCF of the originating service provider via the NEF of the originating service provider. When the third-party specific user identity is authorized, the third-party AAA server may issue a business card indicating the third-party specific user identity, wherein the business card may be associated with the SIP UA of the originating service provider. The business card may indicate the name of the user, the photo of the user, the user identifier, and / or the company associated with the user.

[0088] In some aspects, when the third-party specific user identity is authorized based at least in part on the verification of the token, the third-party AAA server may create a business card. The CSCF of the originating service provider may send the business card to the SIP UA of the terminating service provider. The business card may be indicated in the header of the SIP INVITE message, and the business card may be presented to the SIP UA of the terminating service provider for display based at least in part on the successful verification of the business card at the terminating service provider. When the third-party specific user identity is not authorized based at least in part on the unsuccessful verification of the token, the telephone call may continue without presenting the third-party specific user identity.

[0089] In some aspects, before the SIP UA of the originating service provider creates a SIP INVITE message with a third-party specific user identity and a token, the third-party AAA server may be authorized by the originating IMS network to provide the third-party specific user identity for the SIP UA of a particular group. The SIP UA of the originating service provider may be authorized by the third-party AAA server to use the third-party specific user identity. In some aspects, the SIP UA of the originating service provider may be assigned a token for verification. The SIP UA of the originating service provider may receive the token from the third-party AAA server based at least in part on the distribution of the token to the SIP UA of the originating service provider.

[0090] In some aspects, the NEF may support the authorization of a third-party AAA server and the establishment of a security association between the NEF and the third-party AAA server. The NEF may support the interaction between the originating IMS network (e.g., the CSCF of the originating service provider) and the third-party AAA server to authenticate and authorize the SIP UA using a third-party specific user identity.

[0091] As indicated above, Figure 6 Other examples can be found in the Figure 6 Different than described.

[0092] Figure 7 is a diagram illustrating an example 700 associated with authorizing a third-party specific user identity according to the present disclosure.

[0093] The SHAKEN framework may include an originating IMS network and a terminating IMS network. The originating IMS network may be hosted by an originating service provider (e.g., service provider A), and the terminating IMS network may be hosted by a terminating service provider (e.g., service provider B). The originating service provider may include a SIP UA, a CSCF (e.g., CSCF 112), a STI-AS, a SKS, and an IBCF / TrGW. The terminating service provider may include a SIP UA, a CSCF, a STI-VS, a CVT, and an IBCF / TrGW. The SHAKEN framework may include a certificate provisioning service and an STI-CR. In addition, the SHAKEN framework may include a third-party AAA server (e.g., a third-party AAA server 111) and a NEF. The NEF may be associated with the originating service provider.

[0094] As shown by reference numeral 702, the third-party AAA server may send a token to the SIP UA of the originating service provider. The third-party AAA server may assign the token to the SIP UA of the originating service provider. As shown by reference numeral 704, the SIP UA of the originating service provider may create a SIP INVITE message with a third-party specific user identity and the token. The third-party specific user identity may indicate identification information of the user, such as the name of the user, a photo of the user, a user identifier, and / or a company associated with the user. The user identity may be "third-party specific" because the user identity may indicate information associated with a third party, such as a company affiliated with the user. The SIP UA of the originating service provider may send a SIP INVITE message with a third-party specific user identity and the token to the CSCF of the originating service provider.

[0095] As shown by reference number 706, the CSCF of the originating service provider may send a SIP INVITE message with a third-party specific user identity and a token to the CSCF of the originating service provider to the NEF. As shown by reference number 708, the NEF may forward the SIP INVITE message with the third-party specific user identity and the token to the third-party AAA server. The CSCF of the originating service provider may send a SIP INVITE message with a third-party specific user identity and a token to the third-party AAA server via the NEF. The third-party AAA server may authorize the use of the third-party specific user identity based at least in part on verifying the token associated with the SIP INVITE message. As shown by reference number 710, the third-party AAA server may send a business card indicating the third-party specific user identity to the NEF based at least in part on authorizing the use of the third-party specific user identity. The business card indicating the third-party specific user identity may indicate the user's name, the user's photo, the user identifier, and / or the company associated with the user. The verification of the token may be based at least in part on signaling between the CSCF of the originating service provider and the AAA server via the NEF.

[0096] As shown by reference number 712, the NEF may send a corporate business card to the CSCF of the originating service provider. The CSCF of the originating service provider may receive the corporate business card from the AAA server via the NEF, wherein the corporate business card may be received based at least in part on the verification of the token. As shown by reference number 714, the CSCF of the originating service provider may add a P-Asserted-Identity header field that asserts the third-party specific user identity of the SIP UA of the originating service provider. The CSCF of the originating service provider may initiate an initiation trigger to the STI-AS of the originating service provider for the SIP INVITE message. As shown by reference number 716, the STI-AS of the originating service provider may use a service provider specific mechanism to determine the legitimacy of using a third-party specific user identity in the SIP INVITE message. The STI-AS of the originating service provider may securely request its private key from the SKS of the originating service provider.

[0097] As shown in reference number 718, the SKS of the originating service provider can provide a private key in the response, and the STI-AS of the originating service provider can sign the SIP INVITE message and can add the identity header field using the caller ID and the third-party specific user identity in the identity header field of the P assertion. As shown in reference number 720, the STI-AS of the originating service provider can provide the SIP INVITE message back to the CSCF of the originating service provider. As shown in reference number 722, the CSCF of the originating service provider can route the phone call and the SIP INVITE message to the IBCF (e.g., the egress IBCF) of the originating service provider. The CSCF of the originating service provider can send a SIP INVITE message that can indicate a business card that indicates a third-party specific user identity. As shown in reference number 724, the SIP INVITE message can be routed on the NNI using a standard inter-domain routing configuration. As shown in reference number 726, the IBCF (e.g., the ingress IBCF) of the terminating service provider can receive the SIP INVITE message via the NNI. As indicated by reference numeral 728, the CSCF of the terminating service provider may initiate a termination trigger to the STI-VS of the terminating service provider for the SIP INVITE message.

[0098] As shown by reference number 730, the STI-VS of the terminating service provider can use a field in the PASSPORT protected header to determine the STI-CR URI and perform an HTTPS request to the referenced STI-CR. As shown by reference number 732, the STI-VS of the terminating service provider can verify the certificate and then extract the public key. The STI-VS of the terminating service provider can use the public key to verify the signature in the Identity header field, which can verify the identity of a third party specific user. As shown by reference number 734, CVT can be an optional function that can be called to perform call analysis or other spam mitigation techniques. CVT can be integrated within the service provider network of the terminating service provider, or can be integrated outside the service provider network by a third party.

[0099] As shown at reference numeral 736, based on the result of the STI verification, the STI-VS of the terminating service provider can determine that the phone call is to be completed with the appropriate values, and can pass the SIP INVITE message back to the CSCF of the terminating service provider, which can continue to establish the phone call to the SIP UA of the terminating service provider. As shown at reference numeral 738, the SIP UA of the terminating service provider can receive the SIP INVITE message, and normal SIP processing of the phone call can continue. The SIP UA of the terminating service provider can display a corporate business card indicating the identity of the third-party specific user.

[0100] As indicated above, Figure 7 Other examples can be found in the Figure 7 Different than described.

[0101] Figure 8 is a diagram illustrating an example 800 associated with a business card indicating a third-party specific user identity according to the present disclosure.

[0102] like Figure 8 As shown, a user interface of a SIP UA of a terminating service provider that may be associated with a UE (e.g., UE 120) may display a business card that may indicate a third-party specific user identity, the business card may include the user's name, a phone number associated with the user, a photo of the user, a user identifier, the user's position within the company (e.g., sales manager), and / or a company associated with the user. The business card may include an indication that the third-party specific user identity has been authenticated. The user interface may include a first option to answer the phone call and a second option to reject the phone call.

[0103] As indicated above, Figure 8 Other examples can be found in the Figure 8 Different than described.

[0104] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a CSCF of an originating service provider in accordance with the present disclosure. Example process 900 is an example in which a CSCF of an originating service provider (eg, CSCF 112) performs operations associated with authorizing a third-party specific user identity.

[0105] like Fig. 9 As shown, in some aspects, process 900 may include receiving a SIP INVITE message with a third-party specific user identity and token from a SIP UA of an originating service provider (block 910). For example, the CSCF of the originating service provider (e.g., using Fig.11 The receiving component 1102 depicted in FIG. 1 may receive a SIP INVITE message with a third-party specific user identity and token from a SIP UA of an originating service provider, as described above.

[0106] like Fig. 9 As further shown, in some aspects, process 900 may include sending a SIP INVITE message to an AAA server via the NEF (block 920). For example, the CSCF of the originating service provider (e.g., using Fig.11 The sending component 1104 depicted in FIG. 10A can send a SIP INVITE message to the AAA server via the NEF, as described above.

[0107] like Fig. 9 As further shown, in some aspects, process 900 may include receiving, via the NEF, a business card indicating the identity of a third-party specific user from the AAA server, wherein the business card is received based at least in part on the verification of the token (block 930). Fig.11 The receiving component 1102 depicted in FIG. 1 may receive a business card indicating the identity of a third-party specific user from the AAA server via the NEF, wherein the business card is received based at least in part on the verification of the token, as described above.

[0108] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in conjunction with one or more other processes described elsewhere herein.

[0109] In a first aspect, process 900 includes sending a business card indicating a third-party specific user identity to a SIP UA of a terminating service provider for display on the SIP UA of the terminating service provider.

[0110] In a second aspect, either alone or in combination with the first aspect, a token is assigned by an AAA server to a SIP UA of an originating service provider.

[0111] In a third aspect, alone or in combination with one or more of the first and second aspects, a business card indicating the identity of a third-party specific user indicates one or more of the user's name, the user's photo, a user identifier, or a company associated with the user.

[0112] In a fourth aspect, alone or in combination with one or more of the first to third aspects, verification of the token is based at least in part on signaling between a CSCF of the originating service provider and an AAA server via the NEF.

[0113] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the derivation of a business card indicating a third-party specific user identity is based at least in part on a SHAKEN framework.

[0114] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the AAA server is a third party AAA server, and the authorization of the AAA server is based at least in part on the NEF.

[0115] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more of the blocks in the process 900 may be performed in parallel.

[0116] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by an AAA server according to the present disclosure. Example process 1000 is an example in which an AAA server (eg, AAA server 111) performs operations associated with authorizing a third party specific user identity.

[0117] like Fig.10 As shown, in some aspects, process 1000 may include authorizing use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message having the third-party specific user identity (block 1010). For example, an AAA server (e.g., using Fig.12 The authorization component 1208 depicted in FIG. 1204 may authorize use of a third-party specific user identity based at least in part on verifying a token associated with a SIP INVITE message having the third-party specific user identity, as described above.

[0118] like Fig.10 As further shown, in some aspects, process 1000 may include sending, via the NEF of the originating service provider, a business card to the CSCF of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing use of the third-party specific user identity (block 1020). For example, the AAA server (e.g., using Fig.12 The sending component 1204 depicted in FIG. 1204 may send a business card to the CSCF of the originating service provider via the NEF of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity, as described above.

[0119] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0120] In a first aspect, process 1000 includes sending a token to a SIP UA of an originating service provider, wherein the token is assigned to the SIP UA of the originating service provider by a AAA server.

[0121] In a second aspect, either alone or in combination with the first aspect, a SIP INVITE message is created using a third party specific user identity and a token.

[0122] In a third aspect, alone or in combination with one or more of the first and second aspects, a business card indicating a third-party specific user identity is used for display on a SIP UA of a terminating service provider.

[0123] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, a business card indicating the identity of a third-party specific user indicates one or more of the user's name, the user's photo, a user identifier, or a company associated with the user.

[0124] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1000 includes authorizing use of a third-party specific user identity based at least in part on signaling between an AAA server and a CSCF of an originating service provider via an NEF of an originating service provider.

[0125] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the derivation of a business card indicating a third-party specific user identity is based at least in part on a SHAKEN framework.

[0126] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the AAA server is a third party AAA server, and the authorization of the AAA server is based at least in part on the network exposure function.

[0127] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0128] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication. Apparatus 1100 may be a CSCF of an originating network provider, or a CSCF of an originating network provider may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and sending component 1104.

[0129] In some aspects, the apparatus 1100 may be configured to perform Figures 6 to 8 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 In some aspects, the apparatus 1100 and / or Fig.11 One or more of the components shown may include a combination of Figure 2 One or more components of the CSCF of the originating network provider. Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0130] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories or combinations thereof of the CSCF of the originating network provider.

[0131] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the CSCF of the originating network provider. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0132] The receiving component 1102 may receive a SIP INVITE message with a third-party specific user identity and a token from a SIP UA of an originating service provider. The sending component 1104 may send the SIP INVITE message to an AAA server via the NEF. The receiving component 1102 may receive a business card indicating the third-party specific user identity from the AAA server via the NEF, wherein the business card is received based at least in part on the verification of the token. The sending component 1104 may send the business card indicating the third-party specific user identity to the SIP UA of a terminating service provider for display on the SIP UA of the terminating service provider.

[0133] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The component set (one or more components) shown may be described as being executable by Fig.11 Another set of components shown performs one or more functions.

[0134] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication. Apparatus 1200 may be an AAA server, or an AAA server may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include an authorization component 1208, among other things.

[0135] In some aspects, the apparatus 1200 may be configured to perform Figures 6 to 8 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10 In some aspects, the apparatus 1200 and / or Fig.12 One or more of the components shown may include a combination of Figure 2 One or more components of the AAA server. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0136] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the AAA server.

[0137] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the AAA server. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0138] The authorization component 1208 can authorize the use of the third-party specific user identity based at least in part on verifying a token associated with the SIP INVITE message with the third-party specific user identity. The sending component 1204 can send a business card to the CSCF of the originating service provider via the NEF of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity. The sending component 1204 can send a token to the SIP UA of the originating service provider, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

[0139] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The component set (one or more components) shown may be described as being executable by Fig.12 Another set of components shown performs one or more functions.

[0140] The following provides an overview of some aspects of the disclosure:

[0141] Aspect 1: A method of wireless communication performed by a call session control function (CSCF) of an originating service provider for wireless communication, the method comprising: receiving a SIP INVITE message with a third-party specific user identity and a token from a Session Initiation Protocol (SIP) user agent (UA) of the originating service provider; sending the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); and receiving a corporate business card indicating the third-party specific user identity from the AAA server via the NEF, wherein the corporate business card is received at least in part based on verification of the token.

[0142] Aspect 2: The method according to aspect 1, further comprising: sending the corporate business card indicating the identity of the third-party specific user to a SIP UA of a terminating service provider, for display on the SIP UA of the terminating service provider.

[0143] Aspect 3: The method according to any one of aspects 1 to 2, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

[0144] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the business card indicating the identity of the third-party specific user indicates one or more of the following: the user's name, a photo of the user, a user identifier, or a company associated with the user.

[0145] Aspect 5: The method according to any one of aspects 1 to 4, wherein the verification of the token is based at least in part on signaling between the CSCF of the originating service provider and the AAA server via the NEF.

[0146] Aspect 6: The method according to any one of aspects 1 to 5, wherein the derivation of the enterprise business card indicating the third-party specific user identity is based at least in part on a signature-based processing of assertion information using tokens (SHAKEN) framework.

[0147] Aspect 7: The method according to any one of aspects 1 to 6, wherein the AAA server is a third-party AAA server, and wherein the authorization of the AAA server is based at least in part on the NEF.

[0148] Aspect 8: A method of wireless communication performed by an authentication, authorization, and accounting (AAA) server, the method comprising: authorizing the use of a third-party specific user identity based at least in part on verifying a token associated with a Session Initiation Protocol (SIP) INVITE message having the third-party specific user identity; and sending a corporate business card to a call session control function (CSCF) of the originating service provider via a network exposure function (NEF) of the originating service provider, the corporate business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.

[0149] Aspect 9: The method according to aspect 8, the method further comprising: sending the token to a SIP user agent (UA) of the originating service provider, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

[0150] Aspect 10: The method according to any one of aspects 8 to 9, wherein the SIP INVITE message is created using the third-party specific user identity and the token.

[0151] Aspect 11: The method according to any one of aspects 8 to 10, wherein the corporate business card indicating the identity of the third-party specific user is used to be displayed on a SIP UA of a terminating service provider.

[0152] Aspect 12: A method according to any one of Aspects 8 to 11, wherein the business card indicating the identity of the third-party specific user indicates one or more of the following: the user's name, a photo of the user, a user identifier, or a company associated with the user.

[0153] Aspect 13: A method according to any one of aspects 8 to 12, wherein authorizing the use of the third-party specific user identity is based at least in part on signaling between the AAA server and the CSCF of the originating service provider via the NEF of the originating service provider.

[0154] Aspect 14: The method according to any one of aspects 8 to 13, wherein the derivation of the enterprise business card indicating the third-party specific user identity is based at least in part on a Signature-based Processing of Assertion Information Using Tokens (SHAKEN) framework.

[0155] Aspect 15: The method according to any one of aspects 8 to 14, wherein the AAA server is a third-party AAA server, and wherein the authorization of the AAA server is based at least in part on a network exposure function.

[0156] Aspect 16: An apparatus for performing wireless communications at a device, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 7.

[0157] Aspect 17: A device for wireless communication, the device comprising a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 7.

[0158] Aspect 18: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 7.

[0159] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 7.

[0160] Aspect 20: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 7.

[0161] Aspect 21: An apparatus for wireless communication at a device, the apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 8 to 15.

[0162] Aspect 22: A device for wireless communication, the device comprising a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 8 to 15.

[0163] Aspect 23: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 8 to 15.

[0164] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 8 to 15.

[0165] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 8 to 15.

[0166] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0167] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0168] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0169] Although the specific combination of features is described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0170] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly described as such. In addition, as used herein, the article "one" is intended to include one or more entries, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries, and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. In addition, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless otherwise clearly stated. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise clearly stated (for example, if used in combination with "any" or "only one").

Claims

1. An apparatus for a call session control function (CSCF) of an originating service provider for wireless communications, the apparatus comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: receiving a SIP INVITE message with a third-party specific user identity and a token from a Session Initiation Protocol (SIP) User Agent (UA) of the originating service provider; sending the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); as well as A business card indicating the identity of the third-party specific user is received from the AAA server via the NEF, wherein the business card is received based at least in part on the verification of the token.

2. The apparatus of claim 1 , wherein the one or more processors are configured to: The corporate business card indicating the identity of the third-party specific user is sent to the SIP UA of the terminating service provider for display on the SIP UA of the terminating service provider.

3. The apparatus of claim 1, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server. 4 . The apparatus of claim 1 , wherein the business card indicating the third-party specific user identity indicates one or more of: a user's name, a photo of the user, a user identifier, or a company associated with the user.

5. The apparatus of claim 1, wherein the verification of the token is based at least in part on signaling between the CSCF of the originating service provider and the AAA server via the NEF.

6. The apparatus of claim 1, wherein the derivation of the corporate business card indicating the third-party specific user identity is based at least in part on a Signature-based Processing of Assertion Information Using Tokens (SHAKEN) framework.

7. The apparatus of claim 1, wherein the AAA server is a third-party AAA server, and wherein authorization of the AAA server is based at least in part on the NEF.

8. An apparatus for an authentication, authorization, and accounting (AAA) server, the apparatus comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: authorizing use of the third party specific user identity based at least in part on verifying a token associated with a Session Initiation Protocol (SIP) INVITE message having the third party specific user identity; as well as A business card is sent via a network exposure function (NEF) of the originating service provider to a call session control function (CSCF) of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.

9. The apparatus of claim 8, wherein the one or more processors are configured to: The token is sent to a SIP user agent (UA) of the originating service provider, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

10. The apparatus of claim 8, wherein the SIP INVITE message is created using the third party specific user identity and the token.

11. The apparatus of claim 8, wherein the business card indicating the third-party specific user identity is for display on a SIP UA of a terminating service provider.

12. The apparatus of claim 8, wherein the business card indicating the third-party specific user identity indicates one or more of: a user's name, a photo of the user, a user identifier, or a company associated with the user.

13. An apparatus according to claim 8, wherein the one or more processors are configured to authorize the use of the third-party specific user identity based at least in part on signaling between the AAA server and the CSCF of the originating service provider via the NEF of the originating service provider.

14. The apparatus of claim 8, wherein the derivation of the enterprise business card indicating the third-party specific user identity is based at least in part on a Signature-based Processing of Assertion Information Using Tokens (SHAKEN) framework.

15. The apparatus of claim 8, wherein the AAA server is a third-party AAA server, and wherein authorization of the AAA server is based at least in part on a network exposure capability.

16. A method of wireless communication performed by a call session control function (CSCF) of an originating service provider for wireless communication, the method comprising: receiving a Session Initiation Protocol (SIP) User Agent (UA) of the originating service provider with a third-party specific user identity and token; sending the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); as well as A business card indicating the identity of the third-party specific user is received from the AAA server via the NEF, wherein the business card is received based at least in part on the verification of the token.

17. The method according to claim 16, further comprising: The corporate business card indicating the identity of the third-party specific user is sent to the SIP UA of the terminating service provider for display on the SIP UA of the terminating service provider.

18. The method of claim 16, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

19. The method of claim 16, wherein the business card indicating the third-party specific user identity indicates one or more of: a user's name, a photo of the user, a user identifier, or a company associated with the user.

20. The method of claim 16, wherein the verification of the token is based at least in part on signaling between the CSCF of the originating service provider and the AAA server via the NEF.

21. The method of claim 16, wherein the derivation of the enterprise business card indicating the third-party specific user identity is based at least in part on a Signature-based Processing of Assertion Information Using Tokens (SHAKEN) framework.

22. The method of claim 16, wherein the AAA server is a third party AAA server, and wherein authorization of the AAA server is based at least in part on the NEF.

23. A method of wireless communication performed by an authentication, authorization, and accounting (AAA) server, the method comprising: authorizing use of the third party specific user identity based at least in part on verifying a token associated with a Session Initiation Protocol (SIP) INVITE message having the third party specific user identity; as well as A business card is sent via a network exposure function (NEF) of the originating service provider to a call session control function (CSCF) of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.

24. The method according to claim 23, further comprising: The token is sent to a SIP user agent (UA) of the originating service provider, wherein the token is assigned to the SIP UA of the originating service provider by the AAA server.

25. The method of claim 23, wherein the SIP INVITE message is created using the third-party specific user identity and the token.

26. The method of claim 23, wherein the business card indicating the third-party specific user identity is for display on a SIP UA of a terminating service provider.

27. The method of claim 23, wherein the business card indicating the third-party specific user identity indicates one or more of: a user's name, a photo of the user, a user identifier, or a company associated with the user.

28. The method of claim 23, wherein authorizing the use of the third-party specific user identity is based at least in part on signaling between the AAA server and the CSCF of the originating service provider via the NEF of the originating service provider.

29. The method of claim 23, wherein the derivation of the enterprise business card indicating the third-party specific user identity is based at least in part on a Signature-based Processing of Assertion Information Using Tokens (SHAKEN) framework.

30. The method of claim 23, wherein the AAA server is a third party AAA server, and wherein authorization of the AAA server is based at least in part on a network exposure capability.

31. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a call session control function (CSCF) of an originating service provider, cause the CSCF of the originating service provider to: receiving a Session Initiation Protocol (SIP) User Agent (UA) of the originating service provider with a third-party specific user identity and token; sending the SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); as well as A business card indicating the identity of the third-party specific user is received from the AAA server via the NEF, wherein the business card is received based at least in part on the verification of the token.

32. A non-transitory computer readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of an authentication, authorization, and accounting (AAA) server, cause the AAA server to: authorizing use of the third party specific user identity based at least in part on verifying a token associated with a Session Initiation Protocol (SIP) INVITE message having the third party specific user identity; as well as A business card is sent via a network exposure function (NEF) of the originating service provider to a call session control function (CSCF) of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.

33. An apparatus for wireless communication, the apparatus comprising: means for receiving a Session Initiation Protocol (SIP) User Agent (UA) of an originating service provider with a SIP INVITE message having a third party specific user identity and token; means for sending said SIP INVITE message to an authentication, authorization, and accounting (AAA) server via a network exposure function (NEF); and Means for receiving, from the AAA server via the NEF, a business card indicating the identity of the third-party specific user, wherein the business card is received based at least in part on the verification of the token.

34. An apparatus for wireless communication, the apparatus comprising: means for authorizing use of a third party specific user identity based at least in part on verifying a token associated with a Session Initiation Protocol (SIP) INVITE message having the third party specific user identity; and Means for sending a business card to a call session control function (CSCF) of an originating service provider via a network exposure function (NEF) of the originating service provider, the business card indicating the third-party specific user identity based at least in part on authorizing the use of the third-party specific user identity.