SYSTEMS AND METHODS FOR NETWORK-BASED IDENTIFICATION OF PRIORITY SERVICES
A network device may receive, from a user device, a call associated with a telephone number, where the call is intended for a priority service associated with the telephone number. The network device may identify the call as a priority call based on the telephone number associated with the call, and may determine that a network overload condition exists. The network device may associate a priority tag with the call based on identifying the call as a priority call. The network device may cause the call to be provided preferential treatment, while the call is transmitted for the priority service during the network overload condition, based on the priority tag.
Latest Verizon Patent and Licensing Inc. Patents:
- SYSTEMS AND METHODS FOR DETECTING A DRIVING AREA IN A VIDEO
- SYSTEMS AND METHODS FOR NETWORK SECURITY CONFLICT RESOLUTION
- METHOD AND SYSTEM FOR AUTOMATED Q&A VIA ENRICHED TEXT SIMILARITY
- SYSTEMS AND METHODS FOR ENABLING AND UTILIZING RADAR CAPABILITY ON A WIRELESS COMMUNICATION
- SYSTEMS AND METHODS FOR FAST SWITCHING FROM A PRIVATE NETWORK TO A PUBLIC NETWORK FOR EMERGENCY SERVICES
A network, such as a fourth generation (4G) network or a fifth generation (5G) network, may experience a network overload condition when particular events (e.g., floods, earthquakes, hurricanes, blizzards, terrorist attacks, and/or the like) occur.
The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
Currently, some calls that are high priority in nature (e.g., a 988 suicide hotline call, a call to a local police department, a call to a local fire department, and/or the like), are not identified at the network level as high priority calls. When these calls are initiated by users on user equipment (UE) during a network overload condition, a network may most likely drop these types of calls regardless of their actual priority because they are not designated as prioritized at a network level. The network fails to identify such priority calls as high priority calls since the network currently does not provide an end-to-end priority call identification mechanism during network overload conditions. Thus, the network fails to ensure that the priority calls are identified and handled as high priority calls when the network is in an overload condition. Thus, lack of existing mechanisms for handling priority calls during a network overload condition cause the network to excessively consume computing resources (e.g., processing resources, memory resources, communication resources, and/or the like), networking resources, and/or other resources associated with causing user devices to place priority calls multiple times before connecting to priority services, handling multiple priority calls from the same user devices, handling dropped priority calls, failing to connect priority calls to priority services, and/or the like.
Some implementations described herein provide a network device (e.g., a proxy call session control function (P-CSCF)) that provides network-based identification of priority services. For example, the P-CSCF may receive, from a user device, a call associated with a telephone number, where the call is intended for a priority service associated with the telephone number. The P-CSCF may identify the call as a priority call based on the telephone number associated with the call, and may determine that a network overload condition exists. The P-CSCF may associate a priority tag with the call based on identifying the call as a priority call. The P-CSCF may cause the call to be provided preferential treatment, while the call is transmitted for the priority service during the network overload condition, based on the priority tag, in contrast to untagged calls that do not receive this preferential treatment.
In this way, the P-CSCF provides network-based identification of priority services. For example, the P-CSCF may ensure that a priority call (e.g., a 988 suicide hotline call, a call to a local police department, a call to a local fire department, and/or the like) has an increased probability of call completion and is not dropped when a network experiences an overload condition. Thus, the P-CSCF may conserve computing resources, networking resources, and/or other resources that would otherwise have been consumed by causing user devices to place priority calls multiple times before connecting to priority services, handling multiple priority calls from the same user devices, handling dropped priority calls, failing to connect priority calls to priority services, and/or the like.
As shown in
As further shown in
As shown in
As further shown in
The P-CSCF 120 may associate the priority tag with the call so that all subsequent steps in a delivery setup of the call may receive preferential treatment during the network overload condition. All subsequent call steps for different protocols may include priority tags indicating that the call is a priority call. The subsequent network devices may identify the call as a priority call, may mark the call accordingly (e.g., based on the different protocols), and may provide preferential treatment to the call during the network overload condition. For example, the P-CSCF 120 may utilize the reservation priority AVP and the multimedia priority service AVP, as the priority tag, to indicate the priority of the call to the PCRF via an Rx interface between the P-CSCF 120 and the PCRF. The P-CSCF 120 may utilize the reservation priority AVP and the multimedia priority service AVP, as the priority tag, to indicate the priority of the call to the SGW via a Gm interface between the P-CSCF 120 and the SGW. The P-CSCF 120 may utilize the reservation priority AVP and the multimedia priority service AVP, as the priority tag, to indicate the priority of the call to the I/S-CSCF via an Mw interface between the P-CSCF 120 and the I/S-CSCF. The I/S-CSCF may utilize the SIP resource priority header, as the priority tag, to indicate the priority of the call to the TAS via an ISC interface between the I/S-CSCF and the TAS. The I/S-CSCF may utilize the session priority AVP, as the priority tag, to indicate the priority of the call to the HSS via a Cx interface between the I/S-CSCF and the HSS. The HSS may utilize the session priority AVP, as the priority tag, to indicate the priority of the call to the TAS via an Sh interface between the HSS and the TAS. The TAS may utilize the session priority AVP, as the priority tag, to indicate the priority of the call to the OCS/CCF via an Ro interface between the TAS and the OCS/CCF.
As further shown in
As shown in
As further shown in
As shown in
As further shown in
As further shown in
As shown at step 2 of
As shown at steps 9 and 10 of
As shown at step 16 of
As shown at step 40 of
As shown at steps 44 and 45 of
As shown at step 51 of
In this way, the P-CSCF 120 provides network-based identification of priority services. For example, the P-CSCF 120 may ensure that a priority call (e.g., a 988 suicide hotline call, a call to a local police department, a call to a local fire department, and/or the like) has an increased probability of call completion and is not dropped when a network experiences an overload condition. The P-CSCF 120 may ensure that priority calls receive preferential treatment by the network during a network overload condition. Therefore, the P-CSCF 120 may increase call completion rates for any newly-defined priority calls. Thus, the P-CSCF 120 may conserve computing resources, networking resources, and/or other resources that would otherwise have been consumed by causing user devices 105 to place priority calls multiple times before connecting to priority services, handling multiple priority calls from the same user devices 105, handling dropped priority calls, failing to connect priority calls to priority services, and/or the like.
As indicated above,
The user device 105 includes one or more devices capable of receiving, generating, storing, processing, and/or providing information, such as information described herein. For example, the user device 105 can include a mobile phone (e.g., a smart phone or a radiotelephone), a laptop computer, a tablet computer, a desktop computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smart watch or a pair of smart glasses), a mobile hotspot device, a fixed wireless access device, customer premises equipment, an autonomous vehicle, or a similar type of device.
The RAN 110 may support, for example, a cellular radio access technology (RAT). The RAN 110 may include one or more base stations (e.g., base transceiver stations, radio base stations, node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cellular sites, cellular towers, access points, transmit receive points (TRPs), radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar types of devices) and other network entities that can support wireless communication for the user device 105. The RAN 110 may transfer traffic between the user device 105 (e.g., using a cellular RAT), one or more base stations (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and/or the core network 115. The RAN 110 may provide one or more cells that cover geographic areas.
In some implementations, the RAN 110 may perform scheduling and/or resource management for the user device 105 covered by the RAN 110 (e.g., the user device 105 covered by a cell provided by the RAN 110). In some implementations, the RAN 110 may be controlled or coordinated by a network controller, which may perform load balancing, network-level configuration, and/or other operations. The network controller may communicate with the RAN 110 via a wireless or wireline backhaul. In some implementations, the RAN 110 may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. In other words, the RAN 110 may perform network control, scheduling, and/or network management functions (e.g., for uplink, downlink, and/or sidelink communications of the user device 105 covered by the RAN 110).
Some implementations are described herein as being performed within a long-term evolution (LTE) network for explanatory purposes. Some implementations may be performed within a network that is not an LTE network, such as a third generation (3G) network or a 5G network.
The environment 200 may include an evolved packet system (EPS) that includes an LTE network and/or an evolved packet core (EPC) (e.g., the core network 115) that operate based on a third-generation partnership project (3GPP) wireless communication standard. The LTE network may include a RAN that includes one or more RANs 110 that take the form of evolved Node Bs (eNBs) via which the user device 105 communicates with the EPC 115. The EPC 115 may include the P-CSCF 120, the MME 205, the SGW 210, the PGW 215, the PCRF 220, the OCS/CCF 225, the TAS 230, and/or the I/S-CSCF 235 to enable the user device 105 to communicate with the network 250 and/or an Internet protocol (IP) multimedia subsystem (IMS) core. The IMS core may include the HSS 240 and/or the AAA 245, and may manage device registration and authentication, session initiation, and/or other operations associated with user devices 105. The HSS 240 and/or the AAA 245 may reside in the EPC 115 and/or the IMS core.
The P-CSCF 120 includes one or more devices that manage all signaling from an end user to services and other networks. The P-CSCF 120 may control both fixed and mobile IMSs, may allocate application servers, may establish emergency connections, and may control communication with other networks.
The MME 205 includes one or more devices, such as one or more server devices, capable of managing authentication, activation, deactivation, and/or mobility functions associated with the user device 105. In some implementations, the MME 205 may perform operations relating to authentication of the user device 105. Additionally, or alternatively, the MME 205 may facilitate the selection of a particular SGW 210 and/or a particular PGW 215 to provide traffic to and/or from the user device 105. The MME 205 may perform operations associated with handing off the user device 105 from a first RAN 110 to a second RAN 110 when the user device 105 is transitioning from a first cell associated with the first RAN 110 to a second cell associated with the second RAN 110. Additionally, or alternatively, the MME 205 may select another MME (not pictured), to which the user device 105 should be handed off (e.g., when the user device 105 moves out of range of the MME 205).
The SGW 210 includes one or more devices capable of routing packets. For example, the SGW 210 may include one or more data processing and/or traffic transfer devices, such as a gateway, a router, a modem, a switch, a firewall, a network interface card (MC), a hub, a bridge, a server device, an optical add/drop multiplexer (OADM), or any other type of device that processes and/or transfers traffic. In some implementations, the SGW 210 may aggregate traffic received from one or more RANs 110 associated with the LTE network, and may send the aggregated traffic to the network 250 (e.g., via the PGW 215) and/or other network devices associated with the EPC 115 and/or the IMS core. The SGW 210 may receive traffic from the network 250 and/or other network devices, and may send the received traffic to the user device 105 via the RAN 110. Additionally, or alternatively, the SGW 210 may perform operations associated with handing off the user device 105 to and/or from an LTE network.
The PGW 215 includes one or more devices capable of providing connectivity for the user device 105 to external packet data networks (e.g., other than the depicted EPC 115 and/or the LTE network). For example, the PGW 215 may include one or more data processing and/or traffic transfer devices, such as a gateway, a router, a modem, a switch, a firewall, a MC, a hub, a bridge, a server device, an OADM, or any other type of device that processes and/or transfers traffic. In some implementations, the PGW 215 may aggregate traffic received from one or more SGWs 210, and may send the aggregated traffic to the network 250. Additionally, or alternatively, the PGW 215 may receive traffic from the network 250, and may send the traffic to the user device 105 via the SGW 210 and the RAN 110. The PGW 215 may record data usage information (e.g., byte usage), and may provide the data usage information to the AAA 245.
The PCRF 220 includes one or more devices, such as one or more server devices, capable of providing policy control decision and flow-based charging control functionalities. For example, the PCRF 220 may provide network control regarding service data flow detection, gating, and/or quality of service (QoS) and flow-based charging, among other examples. In some implementations, the PCRF 220 may determine how a certain service data flow is to be treated, and may ensure that user plane traffic mapping and treatment is in accordance with a user subscription profile.
The OCS/CCF 225 includes one or more devices, such as one or more server devices, that enable a cellular network service provider to charge customers (e.g., user devices 105), in real time, based on service usage. The OCS/CCF 225 may enable offline charging of network devices of the IMS core to report accounting information. The OCS/CCF 225 may utilize the accounting information to construct and format a call detail recording.
The TAS 230 includes one or more devices, such as one or more server devices, that provide telephony applications and additional multimedia functions. The TAS 230 may be deployed in the core network 115 and/or the IMS core, and may provide call control and media transformation, such as a soft switch or a media gateway. The TAS 230 may emulate calling features, such as call forwarding, voicemail and conference bridges, and may provide additional multimedia features, such as unified messaging, video calling, and the integration of softphone clients on multiple devices.
The I/S-CSCF 235 includes one or more devices that manage all signaling from an end user to services and other networks. The I/S-CSCF 235 may control both fixed and mobile IMSs, may allocate application servers, may establish emergency connections, and may control communication with other networks.
The HSS 240 includes one or more devices, such as one or more server devices, capable of managing (e.g., receiving, generating, storing, processing, and/or providing) information associated with the user device 105. For example, the HSS 240 may manage subscription information associated with the user device 105, such as information that identifies a subscriber profile of a user associated with the user device 105, information that identifies services and/or applications that are accessible to the user device 105, location information associated with the user device 105, a network identifier (e.g., a network address) that identifies the user device 105, information that identifies a treatment of the user device 105 (e.g., quality of service information, a quantity of minutes allowed per time period, a quantity of data consumption allowed per time period, etc.), and/or similar information. The HSS 240 may provide this information to one or more other devices of the environment 200 to support the operations performed by those devices.
The AAA 245 includes one or more devices, such as one or more server devices, that perform authentication, authorization, and/or accounting operations for communication sessions associated with the user device 105. For example, the AAA 245 may perform authentication operations for the user device 105 and/or a user of the user device 105 (e.g., using one or more credentials), may control access, by the user device 105, to a service and/or an application (e.g., based on one or more restrictions, such as time-of-day restrictions, location restrictions, single or multiple access restrictions, read/write restrictions, etc.), may track resources consumed by the user device 105 (e.g., a quantity of voice minutes consumed, a quantity of data consumed, etc.), and/or may perform similar operations.
The network 250 includes one or more wired and/or wireless networks. For example, the network 250 may include a cellular network (e.g., a 5G network, an LTE network, a 3G network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, and/or a combination of these or other types of networks.
The number and arrangement of devices and networks shown in
In some implementations, the core network 115 may include an example functional architecture in which systems and/or methods described herein may be implemented. For example, the core network 115 may include an example architecture of a 5G next generation (NG) core network included in a 5G wireless telecommunications system. While the example architecture of the core network 115 shown in
As shown in
The NSSF 305 includes one or more devices that select network slice instances for the user device 105. By providing network slicing, the NSSF 305 allows an operator to deploy multiple substantially independent end-to-end networks potentially with the same infrastructure. In some implementations, each slice may be customized for different services.
The AUSF 310 includes one or more devices that act as an authentication server and support the process of authenticating the user device 105 in the wireless telecommunications system.
The UDM 315 includes one or more devices that store user data and profiles in the wireless telecommunications system. The UDM 315 may be used for fixed access and/or mobile access in the core network 115.
The PCF 320 includes one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and/or mobility management, among other examples.
The AF 325 includes one or more devices that support application influence on traffic routing, access to a network exposure function (NEF), and/or policy control, among other examples.
The AMF 330 includes one or more devices that act as a termination point for non-access stratum (NAS) signaling and/or mobility management, among other examples.
The SMF 335 includes one or more devices that support the establishment, modification, and release of communication sessions in the wireless telecommunications system. For example, the SMF 335 may configure traffic steering policies at the UPF 340 and/or may enforce user equipment IP address allocation and policies, among other examples.
The UPF 340 includes one or more devices that serve as an anchor point for intraRAT and/or interRAT mobility. The UPF 340 may apply rules to packets, such as rules pertaining to packet routing, traffic reporting, and/or handling user plane QoS, among other examples.
The message bus 345 represents a communication structure for communication among the functional elements. In other words, the message bus 345 may permit communication between two or more functional elements.
The data network 350 includes one or more wired and/or wireless data networks. For example, the data network 350 may include an IMS, a PLMN, a LAN, a WAN, a MAN, a private network such as a corporate intranet, an ad hoc network, the Internet, a fiber optic-based network, a cloud computing network, a third party services network, an operator services network, and/or a combination of these or other types of networks.
The number and arrangement of devices and networks shown in
The bus 410 includes one or more components that enable wired and/or wireless communication among the components of the device 400. The bus 410 may couple together two or more components of
The memory 430 includes volatile and/or nonvolatile memory. For example, the memory 430 may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory). The memory 430 may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection). The memory 430 may be a non-transitory computer-readable medium. Memory 430 stores information, instructions, and/or software (e.g., one or more software applications) related to the operation of the device 400. In some implementations, the memory 430 includes one or more memories that are coupled to one or more processors (e.g., the processor 420), such as via the bus 410.
The input component 440 enables the device 400 to receive input, such as user input and/or sensed input. For example, the input component 440 may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and/or an actuator. The output component 450 enables the device 400 to provide output, such as via a display, a speaker, and/or a light-emitting diode. The communication component 460 enables the device 400 to communicate with other devices via a wired connection and/or a wireless connection. For example, the communication component 460 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.
The device 400 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., the memory 430) may store a set of instructions (e.g., one or more instructions or code) for execution by the processor 420. The processor 420 may execute the set of instructions to perform one or more operations or processes described herein. In some implementations, execution of the set of instructions, by one or more processors 420, causes the one or more processors 420 and/or the device 400 to perform one or more operations or processes described herein. In some implementations, hardwired circuitry may be used instead of or in combination with the instructions to perform one or more operations or processes described herein. Additionally, or alternatively, the processor 420 may be configured to perform one or more operations or processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
The number and arrangement of components shown in
As shown in
In some implementations, the network device is a P-CSCF. In some implementations, the network device is associated with a fourth generation network or a fifth generation network.
As further shown in
As further shown in
As further shown in
As further shown in
In some implementations, process 500 includes storing, in a data structure, a mapping of session priority AVP values associated with priority services, session initiation protocol resource priority headers associated with the priority services, and reservation priority AVP values associated with the priority services, and generating the priority tag based on the mapping.
Although
As used herein, the term “component” is intended to be broadly construed as hardware, firmware, or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware, firmware, and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code—it being understood that software and hardware can be used to implement the systems and/or methods based on the description herein.
As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.
To the extent the aforementioned implementations collect, store, or employ personal information of individuals, it should be understood that such information shall be used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage, and use of such information can be subject to consent of the individual to such activity, for example, through well known “opt-in” or “opt-out” processes as can be appropriate for the situation and type of information. Storage and use of personal information can be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various implementations includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. 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, as well as any combination with multiple of the same item.
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items), and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of”).
In the preceding specification, various example embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense.
Claims
1. A method, comprising:
- receiving, by a network device and from a user device, a call associated with a telephone number, the call being intended for a priority service associated with the telephone number;
- identifying, by the network device, the call as a priority call based on the telephone number associated with the call;
- determining, by the network device, that a network overload condition exists;
- associating, by the network device, a priority tag with the call based on identifying the call as a priority call; and
- causing, by the network device, the call to be provided preferential treatment, while the call is transmitted for the priority service during the network overload condition, based on the priority tag.
2. The method of claim 1, wherein the telephone number is associated with one or more of:
- a suicide hotline,
- a police department,
- a fire department,
- a hospital, or
- a poison control service.
3. The method of claim 1, wherein causing the call to be provided preferential treatment during the network overload condition based on the priority tag comprises:
- causing, based on the priority tag, one or more other network devices to identify the call as a priority call and to provide preferential treatment for the call during the network overload condition.
4. The method of claim 3, wherein the one or more other network devices include one or more of:
- user plane function,
- a policy control function,
- a home subscriber server,
- an interrogating or serving call session control function,
- a telephony application server, or
- an online charging system/charging collection function.
5. The method of claim 1, wherein associating the priority tag with the call comprises:
- associating a reservation priority attribute-value pair (AVP) and a multimedia priority service AVP, as the priority tag, with the call.
6. The method of claim 1, wherein associating the priority tag with the call comprises:
- associating a session initiation protocol resource priority header, as the priority tag, with the call.
7. The method of claim 1, wherein associating the priority tag with the call comprises:
- associating a session priority attribute-value pair, as the priority tag, with the call.
8. A network device, comprising:
- one or more processors configured to: receive, from a user device, a call associated with a telephone number and generated during a network overload condition; identify the call as a priority call based on the telephone number associated with the call; associate a priority tag with the call based on identifying the call as a priority call; and cause the call to be provided preferential treatment during the network overload condition throughout a network associated with the network device and based on the priority tag.
9. The network device of claim 8, wherein the one or more processors are further configured to:
- store, in a data structure, a mapping of session priority attribute-value pair (AVP) values associated with priority services, session initiation protocol resource priority headers associated with the priority services, and reservation priority AVP values associated with the priority services; and
- generating the priority tag based on the mapping.
10. The network device of claim 8, wherein the one or more processors, to identify the call as a priority call based on the telephone number associated with the call, are configured to:
- compare digits of the telephone number with a list of telephone numbers associated with priority services; and
- identify the call as a priority call based on the digits matching digits of a telephone number in the list of telephone numbers associated with priority services.
11. The network device of claim 8, wherein the network device is a proxy call session control function.
12. The network device of claim 8, wherein the network device is associated with a fourth generation network or a fifth generation network.
13. The network device of claim 8, wherein the priority tag causes one or more other network devices to modify the priority tag based on one or more protocols associated with the one or more other network devices.
14. The network device of claim 8, wherein a connection is established between the user device and a priority service associated with the telephone number based on causing the call to be provided preferential treatment during the network overload condition.
15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
- one or more instructions that, when executed by one or more processors of a network device, cause the network device to: determine that a network overload condition exists in a network associated with the network device; receive, from a user device, a call associated with a telephone number; identify the call as a priority call based on the telephone number associated with the call; associate a priority tag with the call based on identifying the call as a priority call; and cause the call to be provided preferential treatment during the network overload condition based on the priority tag, wherein a connection is to be established between the user device and a priority service associated with the telephone number based on causing the call to be provided preferential treatment during the network overload condition.
16. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the network device to cause the call to be provided preferential treatment during the network overload condition based on the priority tag, cause the network device to:
- cause, based on the priority tag, one or more other network devices to identify the call as a priority call and to provide preferential treatment for the call during the network overload condition.
17. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the network device to associate the priority tag with the call, cause the network device to:
- associate a reservation priority attribute-value pair (AVP) and a multimedia priority service AVP, as the priority tag, with the call.
18. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the network device to associate the priority tag with the call, cause the network device to:
- associate a session initiation protocol resource priority header, as the priority tag, with the call.
19. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions further cause the network device to:
- store, in a data structure, a mapping of session priority attribute-value pair (AVP) values associated with priority services, session initiation protocol resource priority headers associated with the priority services, and reservation priority AVP values associated with the priority services, wherein the priority tag is generated based on the mapping.
20. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the network device to identify the call as a priority call based on the telephone number associated with the call, cause the network device to:
- compare the telephone number with a list of priority telephone numbers associated with priority services; and
- identify the call as a priority call based on the telephone number matching a priority telephone number in the list of priority telephone numbers associated with priority services.
Type: Application
Filed: May 24, 2022
Publication Date: Nov 30, 2023
Applicant: Verizon Patent and Licensing Inc. (Basking Ridge, NJ)
Inventors: Kashif KHAN (Keller, TX), Danysel BARTHELME (Frisco, TX), Ronald E. COLLIER, II (Arlington, TX), Ertao LI (Plano, TX), Steve L. PADILLA (Grapevine, TX), Gaurav PATEL (McKinney, TX), Shawn R. PUGH (Easton, PA), Shujaat Ali SIDDIQUE (Hillsborough, NJ), Daniel L. WALKER (Wall Township, NJ), John Cao Vinh NGUYEN (Trophy Club, TX)
Application Number: 17/664,740