Abstract: Aspects of the subject disclosure may include, for example, obtaining CBRS information from SAS equipment, where the CBRS information includes channel assignments associated with different coverage locations; and providing the channel assignments to one or more EMSs according to the CBRS information to enable CBRS devices to provide communication services including handoffs via the channel assignments to one or more end user devices in coverage areas of the one or more CBRS device. Other embodiments are disclosed.

Abstract: A processing system including at least one processor may obtain network traffic data associated with an independent gateway that is connected to a telecommunication network, apply an input data set associated with the network traffic data of the independent gateway to at least a first detection model implemented by the processing system for detecting fake network usage, and may determine the fake network usage associated with the independent gateway from the input data set associated with the network traffic data of the independent gateway via the at least the first detection model. The processing system may then generate an alert of the fake network usage associated with the independent gateway, where the alert is generated in response to the determining.

Abstract: A processing system including at least one processor of a first surface-operating vehicle may obtain a request for wireless charging of a second surface-operating vehicle while in motion. The processing system may then navigate the first surface-operating vehicle in synchronization with the second surface-operating vehicle and provide the wireless charging to the second surface-operating vehicle while in motion.

Abstract: Prioritization and selection of signals and associated cells can be managed. User equipment module (UEM) of user equipment (UE) can determine a context associated with a communication session based on analyzing usage behavior information relating to usage behavior, and profile information relating to a profile, associated with the UE. The profile information can be determined by a core module based on information relating to the network or previous communication sessions. Based on analysis results, including context, UEM can determine a characteristic, other than signal strength, that can be more heavily weighted over other characteristics associated with UE or network to facilitate determining which cell, of a cell group, the UE is to connect to for the communication session. UEM can determine and select the cell of the cell group to which the UE is to connect, based on the context and the highest weighted characteristic.

Abstract: Concepts and technologies disclosed herein are directed to autonomous vehicle pairing management. According to one aspect disclosed herein, a fleet pairing management application executed by a processor of an autonomous vehicle can initiate a fleet pairing process with a plurality of other autonomous vehicles, each of which can execute one of a plurality of other fleet pairing management applications. The fleet pairing management application can send, over a network, an initiate network pairing request to the plurality of other autonomous vehicles. The fleet pairing management application can receive a confirm network pairing response from at least one other autonomous vehicle of the plurality of other autonomous vehicles. A fleet can then be established. The fleet can include the autonomous vehicle and the at least one other autonomous vehicle of the plurality of other autonomous vehicles. The autonomous vehicles in the fleet can then share data among the fleet.

Abstract: Call spoofing can be mitigated by providing geolocation information to the called device. For example, when a call rings, a geolocator can be invoked and the incoming call display screen can show a carrier logo and/or a geolocator globe illustrating the location of the call originator. The geolocation session initiation protocol data can be confirmed by a network device and compared against carrier specific data of the calling device to authenticate voice calls for called devices. In one embodiment location data of the calling device can purposely be shared in order to facilitate the mitigation of call spoofing.

Abstract: Intelligent hologram communication continuity (e.g., using a computerized tool) is enabled. A method can comprise: determining, by a device comprising a processor, a context associated with a live interaction, wherein the live interaction is associated with a user profile and transmitted via a network; determining, by the device, hardware data representative of hardware associated with transmission of the live interaction via the network; in response to a hardware criterion being determined to be threshold satisfied by the hardware data, generating, by the device, using a hologram generation model and based on the context, a synthetic hologram associated with the live interaction, wherein the hologram generation model has been generated based on machine learning applied to past context data representative of past contexts of past live interactions associated with the user profile, from prior to the live interaction; and transmitting, by the device, the synthetic hologram instead of the live interaction.

Abstract: Call spoofing can be mitigated by providing geolocation information to the called device. For example, when a call rings, a geolocator can be invoked and the incoming call display screen can show a carrier logo and/or a geolocator globe illustrating the location of the call originator. The geolocation session initiation protocol data can be confirmed by a network device and compared against carrier specific data of the calling device to authenticate voice calls for called devices. In one embodiment location data of the calling device can purposely be shared in order to facilitate the mitigation of call spoofing.

Abstract: Call spoofing can be mitigated by providing geolocation information to the called device. For example, when a call rings, a geolocator can be invoked and the incoming call display screen can show a carrier logo and/or a geolocator globe illustrating the location of the call originator. The geolocation session initiation protocol data can be confirmed by a network device and compared against carrier specific data of the calling device to authenticate voice calls for called devices. In one embodiment location data of the calling device can purposely be shared in order to facilitate the mitigation of call spoofing.

Abstract: In one example, a processing system including at least one processor may obtain a call request from a calling device to a destination device, identify a caller category associated with the calling device, and forward the call request to the destination device with an indicator of the caller category, where the indicator of the caller category is to cause the destination device to present at least one of: a first ringtone that is associated with the caller category or a first vibration pattern that is associated with the caller category.

Abstract: Call spoofing can be mitigated by providing geolocation information to the called device. For example, when a call rings, a geolocator can be invoked and the incoming call display screen can show a carrier logo and/or a geolocator globe illustrating the location of the call originator. The geolocation session initiation protocol data can be confirmed by a network device and compared against carrier specific data of the calling device to authenticate voice calls for called devices. In one embodiment location data of the calling device can purposely be shared in order to facilitate the mitigation of call spoofing.

Abstract: In one example, a processing system including at least one processor may obtain a call request from a calling device to a destination device, identify a caller category associated with the calling device, and forward the call request to the destination device with an indicator of the caller category, where the indicator of the caller category is to cause the destination device to present at least one of: a first ringtone that is associated with the caller category or a first vibration pattern that is associated with the caller category.

Abstract: Concepts and technologies are disclosed herein for screening and selectively blocking private calls. A processor executing instructions associated with a private call blocking service can detect a call from a calling device directed to a called device. The processor can determine that the call has a caller identification blocking marker indicating that a fixed label should be provided to the called device to prevent the called device from presenting caller identification data associated with the calling device. In response to determining that the call has the caller identification blocking marker, the processor can obtain a custom private caller identification mask instead of the fixed label. The processor can provide the custom private caller identification mask to the called device for the call, where the custom private caller identification mask can be presented to a called party associated with the called device without revealing the caller identification data.

Abstract: Concepts and technologies are disclosed herein for screening and selectively blocking private calls. A processor executing instructions associated with a private call blocking service can detect a call from a calling device directed to a called device. The processor can determine that the call has a caller identification blocking marker indicating that a fixed label should be provided to the called device to prevent the called device from presenting caller identification data associated with the calling device. In response to determining that the call has the caller identification blocking marker, the processor can obtain a custom private caller identification mask instead of the fixed label. The processor can provide the custom private caller identification mask to the called device for the call, where the custom private caller identification mask can be presented to a called party associated with the called device without revealing the caller identification data.

Abstract: Concepts and technologies are disclosed herein for screening and selectively blocking private calls. A processor executing instructions associated with a private call blocking service can detect a call from a calling device directed to a called device. The processor can determine that the call has a caller identification blocking marker indicating that a fixed label should be provided to the called device to prevent the called device from presenting caller identification data associated with the calling device. In response to determining that the call has the caller identification blocking marker, the processor can obtain a custom private caller identification mask instead of the fixed label. The processor can provide the custom private caller identification mask to the called device for the call, where the custom private caller identification mask can be presented to a called party associated with the called device without revealing the caller identification data.

Abstract: Concepts and technologies are disclosed herein for screening and selectively blocking private calls. A processor executing instructions associated with a private call blocking service can detect a call from a calling device directed to a called device. The processor can determine that the call has a caller identification blocking marker indicating that a fixed label should be provided to the called device to prevent the called device from presenting caller identification data associated with the calling device. In response to determining that the call has the caller identification blocking marker, the processor can obtain a custom private caller identification mask instead of the fixed label. The processor can provide the custom private caller identification mask to the called device for the call, where the custom private caller identification mask can be presented to a called party associated with the called device without revealing the caller identification data.

Abstract: A system and method make quality measurements in a network to determine if a Service Level Agreement is breached. The system includes a plurality of routers for routing traffic through the network, means for taking measurements on a path between a first router and a second router, and means for charging at least one of the plurality of routers when data related to the measurements falls below a target value.

Abstract: In one embodiment, the present invention is a method and apparatus for testing backup sites in a Voice over Internet Protocol network. In one embodiment, a method for testing a backup site in a communications network includes simulating, in the network, a failed customer call and outputting an indicator to indicate whether the failed customer call was successfully re-routed from a primary site to the backup site. The testing of the backup site occurs in a manner that minimizes impact to the routing of customer calls destined for the primary site.

Abstract: A method employs call detail records for developing a report on the usage of VoIP calling along a network path or through a network location. By utilizing, for example, a call-beginning record and a call-ending record for each connection, a report is created of the number of concurrent VoIP calls that a specified equipment or network path carries at any given instance by retrieving batches of stored call detail records, culling the records that are relevant to the specified equipment or network path, considering the culled records in a time sorted manner, and incrementing or decrementing a counter based on whether a considered record is a call-beginning record or a call-ending record, respectively. The state of the counter is reported, illustratively, as a line entry each time the counter's state is modified.

Abstract: A method employs call detail records for developing a report on the usage of VoIP calling along a network path or through a network location. By utilizing, for example, a call-beginning record and a call-ending record for each connection, a report is created of the number of concurrent VoIP calls that a specified equipment or network path carries at any given instance by retrieving batches of stored call detail records, culling the records that are relevant to the specified equipment or network path, considering the culled records in a time sorted manner, and incrementing or decrementing a counter based on whether a considered record is a call-beginning record or a call-ending record, respectively. The state of the counter is reported, illustratively, as a line entry each time the counter's state is modified.