# US 2021/0344730 A1 · Systems and methods for enhanced messaging for network- and user equipment-implemented call request handling > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0344730 A1 - Document ID: US20210344730A1 - Status: Published application - Kind: A1 - Application number: 16/865,614 - Filed: 2020-05-04 - Published: 2021-11-04 - Earliest claimed: 2020-05-04 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Yi Jing; Timothy M. Dwight; Lulia Ann Barakat - Web page: https://patentgrep.com/patent/US20210344730A1 ## CPC - H04L 65/1079: {of unsolicited session attempts, e.g. SPIT} - H04L 65/1016: IP multimedia subsystem [IMS] - H04L 65/1063: Application servers providing network services (systems providing special services to telephonic subscribers H04M3/42) - H04L 65/1104: Session initiation protocol [SIP] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system described herein may provide a technique for handling call requests, prior to the performance of a call setup procedure, based on attributes of a calling User Equipment (“UE”) and/or a called UE. A Messaging Application Server may receive a call request, from the calling UE and to the called UE, identify a category or event type associated with the call request, and notify the called UE of the call request, including the category or event type. Different categories or event types may be associated with different sets of eligible actions to perform. The called UE may indicate a particular action, associated with the identified category or event type, and the MAS may handle the call request according to the particular action (e.g., reject the call request or proceed with a call setup procedure). ## Claims ### Claim 1 A device, comprising: one or more processors configured to: maintain information associating each call request category, of a plurality of call request categories, to a respective set of actions of a plurality of sets of actions; receive, from a first User Equipment (“UE”), a request to establish a call between the first UE and a second UE; identify one or more attributes associated with at least one of the first UE or the second UE; determine, based on the one or more attributes associated with the at least one of the first UE or the second UE, that the call request is associated with a particular call request category, of the plurality of call request categories; provide, to the second UE, a notification of the request to establish the call between the first UE and the second UE, the notification including an indication of the determined particular call request category associated with the call request, wherein the second UE identifies a particular set of actions associated with the particular call request category and receives a selection of a particular action of the particular set of actions; receive, from the second UE, a response to the notification, the response indicating the selected particular action, of the particular set of actions associated with the particular call request category, to take with respect to the call request; and perform, based on receiving the response, the selected particular action with respect to the call request. ### Claim 2 (depends on 1) The device of claim 1, wherein the response indicates that the particular set of actions includes forgoing performing a call setup procedure between the first UE and the second UE, wherein performing the selected particular action includes forgoing performing the call setup procedure between the first UE and the second UE. ### Claim 3 (depends on 2) The device of claim 2, wherein forgoing performing the call setup procedure between the first UE and the second UE includes forgoing outputting a Session Initiation Protocol (“SIP”) INVITE message, associated with the requested call, to the second UE. ### Claim 4 (depends on 1) The device of claim 1, wherein providing the notification includes providing a Session Initiation Protocol (“SIP”) NOTIFY message to the second UE. ### Claim 5 (depends on 4) The device of claim 4, wherein indication of the determined category is indicated in an “Event” field of the SIP NOTIFY message. ### Claim 6 (depends on 1) The device of claim 1, wherein the response includes a Session Initiation Protocol (“SIP”) message and the particular set of actions are indicated in a body of the SIP message. ### Claim 7 (depends on 1) The device of claim 1, wherein identifying the one or more attributes associated with at least one of the first UE or the second UE includes determining a measure of undesirability of the requested call, wherein the call request is associated with the particular call request category associated includes identifying a particular category, of a plurality of categories that are associated with different measures of undesirability of call requests, that is associated with the determined measure of undesirability of the requested call, wherein providing the notification to the second UE includes an indication of the determined particular category of the plurality of categories that are associated with different measures of undesirability of call requests. ### Claim 8 A non-transitory computer-readable medium, storing a plurality of processor-executable instructions to: maintain information associating each call request category, of a plurality of call request categories, to a respective set of actions of a plurality of sets of actions; receive, from a first User Equipment (“UE”), a request to establish a call between the first UE and a second UE; identify one or more attributes associated with at least one of the first UE or the second UE; determine, based on the one or more attributes associated with the at least one of the first UE or the second UE, that the call request is associated with a particular call request category, of the plurality of call request categories; provide, to the second UE, a notification of the request to establish the call between the first UE and the second UE, the notification including an indication of the determined particular call request category associated with the call request, wherein the second UE identifies a particular set of actions associated with the particular call request category and receives a selection of a particular action of the particular set of actions; receive, from the second UE, a response to the notification, the response indicating the selected particular action, of the particular set of actions associated with the particular call request category, to take with respect to the call request; and perform, based on receiving the response, the selected particular action with respect to the call request. ### Claim 9 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the response indicates that the particular set of actions includes forgoing performing a call setup procedure between the first UE and the second UE, wherein performing the selected particular action includes forgoing performing the call setup procedure between the first UE and the second UE. ### Claim 10 (depends on 9) The non-transitory computer-readable medium of claim 9, wherein forgoing performing the call setup procedure between the first UE and the second UE includes forgoing outputting a Session Initiation Protocol (“SIP”) INVITE message, associated with the requested call, to the second UE. ### Claim 11 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein providing the notification includes providing a Session Initiation Protocol (“SIP”) NOTIFY message to the second UE. ### Claim 12 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein indication of the determined category is indicated in an “Event” field of the SIP NOTIFY message. ### Claim 13 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein the response includes a Session Initiation Protocol (“SIP”) message and the one or more actions are indicated in a body of the SIP message. ### Claim 14 (depends on 8) The non-transitory computer-readable medium of claim 8, wherein identifying the one or more attributes associated with at least one of the first UE or the second UE includes determining a measure of undesirability of the requested call, wherein the call request is associated with the particular call request category associated includes identifying a particular category, of a plurality of categories that are associated with different measures of undesirability of call requests, that is associated with the determined measure of undesirability of the requested call, wherein providing the notification to the second UE includes an indication of the determined particular category of the plurality of categories that are associated with different measures of undesirability of call requests. ### Claim 15 A method, comprising: maintaining information associating each call request category, of a plurality of call request categories, to a respective set of actions of a plurality of sets of actions; receiving, from a first User Equipment (“UE”), a request to establish a call between the first UE and a second UE; identify one or more attributes associated with at least one of the first UE or the second UE; determining, based on the one or more attributes associated with the at least one of the first UE or the second UE, that the call request is associated with a particular call request category, of the plurality of call request categories; providing, to the second UE, a notification of the request to establish the call between the first UE and the second UE, the notification including an indication of the determined particular call request category associated with the call request, wherein the second UE identifies a particular set of actions associated with the particular call request category and receives a selection of a particular action of the particular set of actions; receiving, from the second UE, a response to the notification, the response indicating the selected particular action, of the particular set of actions associated with the particular call request category, to take with respect to the call request; and performing, based on receiving the response, the selected particular action with respect to the call request. ### Claim 16 (depends on 15) The method of claim 15, wherein the response indicates that the particular set of actions includes forgoing performing a call setup procedure between the first UE and the second UE, wherein performing the selected particular action includes forgoing outputting a Session Initiation Protocol (“SIP”) INVITE message, associated with the requested call, to the second UE. ### Claim 17 (depends on 15) The method of claim 15, wherein providing the notification includes providing a Session Initiation Protocol (“SIP”) NOTIFY message to the second UE. ### Claim 18 (depends on 17) The method of claim 17, wherein indication of the determined category is indicated in an “Event” field of the SIP NOTIFY message. ### Claim 19 (depends on 15) The method of claim 15, wherein the response includes a Session Initiation Protocol (“SIP”) message and the one or more actions are indicated in a body of the SIP message. ### Claim 20 (depends on 15) The method of claim 15, wherein identifying the one or more attributes associated with at least one of the first UE or the second UE includes determining a measure of undesirability of the requested call, wherein the call request is associated with the particular call request category associated includes identifying a particular category, of a plurality of categories that are associated with different measures of undesirability of call requests, that is associated with the determined measure of undesirability of the requested call, wherein providing the notification to the second UE includes an indication of the determined particular category of the plurality of categories that are associated with different measures of undesirability of call requests.