# US 10,455,453 B2 · Service enablement based on access network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,453 B2 - Document ID: US10455453B2 - Status: Granted - Kind: B2 - Application number: 15/858,517 - Filed: 2017-12-29 - Published: 2019-02-21 - Granted: 2019-10-22 - Earliest claimed: 2017-08-16 - Assignees: T-Mobile USA, Inc. - Applicants: T-Mobile USA, Inc. - Inventors: Shujaur Mufti; Khurram Ahmad Mirza - Web page: https://patentgrep.com/patent/US10455453B2 ## CPC - H04W 28/18: Negotiating wireless communication parameters - H04L 65/00: Network arrangements, protocols or services for supporting real-time applications in data packet communication (real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00) - H04L 65/1016: IP multimedia subsystem [IMS] - H04L 65/1069: Session establishment or de-establishment - H04L 65/1073: Registration or de-registration - H04L 65/1104: Session initiation protocol [SIP] - H04W 36/00226: {wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]} - H04W 48/02: Access restriction performed under specific conditions - H04W 48/18: Selecting a network or a communication service - H04W 80/10: adapted for {application} session management, e.g. SIP [Session Initiation Protocol] {(connection management H04W76/00; arrangements for session management H04L67/14)} - H04W 84/042: {Public Land Mobile systems, e.g. cellular systems} - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract In some examples, an anchoring network system (e.g., PCSCF) of a telecommunications network can receive first data requesting a network service (e.g., eSRVCC) from a network terminal (e.g., UE). The anchoring system can determine that the network service is not supported in an access network to which the terminal is connected. The anchoring system can determine second data that does not request the predetermined network service, and transmit the second data to a core network system (e.g., SCSCF). In some examples, an application server can retrieve location information (e.g., LAC) of the terminal and determine that the service is not supported based on the location information. In some examples, an anchoring network system can remove a network-service system (e.g., ATCF or SCCAS) from a signaling chain associated with the terminal. In some examples, the terminal can determine whether SRVCC is supported based on an attach result. ## Claims ### Claim 1 A method comprising, by an anchoring network system of a telecommunications network: receiving first data from a terminal of the telecommunications network via a communications interface; determining that the first data includes a request for a predetermined network service; determining that the predetermined network service is not supported in an access network to which the terminal is connected; determining second data that does not request the predetermined network service; and transmitting the second data to a core network system via the communications interface. ### Claim 2 (depends on 1) The method according to claim 1, wherein: the first data comprises a registration request; and the method further comprises, after transmitting the second data: receiving third data from the terminal via the communications interface; determining that the third data includes a second request for the predetermined network service; determining that the terminal is connected to a second access network; determining that the predetermined network service is supported in the second access network; and transmitting an indication of the second request to the core network system. ### Claim 3 (depends on 2) The method according to claim 2, wherein: the first data comprises a Session Initiation Protocol (SIP) REGISTER request; the predetermined network service comprises at least Single-Radio Voice Call Continuity (SRVCC) or Evolved SRVCC (eSRVCC); the third data comprises a SIP INVITE request; the anchoring network system comprises a Proxy Call Session Control Function (P-CSCF); and the core network system comprises an Access Transfer Control Function (ATCF). ### Claim 4 (depends on 2) The method according to claim 2, further comprising, in response to the determination that the predetermined network service is supported in the second access network, allocating resources in the anchoring network system to support the predetermined network service. ### Claim 5 (depends on 1) The method according to claim 1, the anchoring network system comprises an Access Transfer Control Function (ATCF); the core network system comprises a Serving Call Session Control Function (S-CSCF); the first data comprises a first Session Initiation Protocol (SIP) request; and the second data comprises a second SIP request specifying a signaling chain that omits the ATCF. ### Claim 6 (depends on 1) The method according to claim 1, further comprising: retrieving a location identifier from the first data, the location identifier associated with the access network; and determining that the predetermined network service is not supported in the access network based at least in part on the location identifier. ### Claim 7 (depends on 6) The method according to claim 6, wherein: the first data comprises a Session Initiation Protocol (SIP) header that includes an access-network-information (ANI) value; the ANI value comprises location information that includes at least one of a Location Area Code (LAC) or a Tracking Area Code (TAC); and the location identifier comprises at least a portion of the location information. ### Claim 8 (depends on 6) The method according to claim 6, wherein the first data comprises a location header comprising the location identifier. ### Claim 9 (depends on 6) The method according to claim 6, further comprising, before determining the second data, determining that the first data includes authenticity information. ### Claim 10 (depends on 1) The method according to claim 1, wherein: the first data comprises a first Session Initiation Protocol (SIP) Feature-Caps header; the request for the predetermined network service comprises a capability value in the first Feature-Caps header; and the method further comprises determining, as the second data, a SIP request that either: comprises a second Feature-Caps header that does not include the capability value; or does not include a Feature-Caps header. ### Claim 11 (depends on 1) The method according to claim 1, further comprising determining, as the second data, a Session Initiation Protocol (SIP) registration request addressed to the core network system. ### Claim 12 A telecommunications network comprising: a first device comprising at least a Service Centralization and Continuity Application Server (SCCAS) or Telephony Application Server (TAS) and configured to perform first operations comprising: receiving first data associated with a terminal of the telecommunications network; determining that the first data includes a request for a predetermined network service, wherein the predetermined network service comprises at least Single-Radio Voice Call Continuity (SRVCC), Evolved SRVCC (eSRVCC), or aSRVCC; retrieving location information of the terminal from a location provider system; determining, based at least in part on the location information, that the predetermined network service is not supported in an access network to which the terminal is connected; and transmitting second data indicating that the predetermined network service is not supported in the access network; and a Proxy Call Session Control Function (P-CSCF) configured to perform second operations comprising: receiving the second data; and in response, removing an Access Transfer Control Function (ATCF) from a signaling chain associated with the terminal, the ATCF associated with the predetermined network service. ### Claim 13 (depends on 12) The telecommunications network according to claim 12, wherein: the telecommunications network further comprises a Serving Call Session Control Function (S-CSCF) configured to relay messages between the P-CSCF and the first device; and the second operations comprise removing the ATCF from the signaling chain by transmitting a Session Initiation Protocol (SIP) REGISTER request to the S-CSCF, wherein the SIP REGISTER request is not routed through the ATCF. ### Claim 14 (depends on 12) The telecommunications network according to claim 12, wherein the first data comprises a Session Initiation Protocol (SIP) INVITE request, and the second data comprises a SIP MESSAGE request. ### Claim 15 (depends on 12) The telecommunications network according to claim 12, wherein the first data comprises a Session Initiation Protocol (SIP) INVITE request, and the second data comprises a SIP one hundred eighty-three response. ### Claim 16 (depends on 12) The telecommunications network according to claim 12, wherein: the telecommunications network further comprises the location provider system; the location provider system is configured to: receive identification information associated with the terminal from the first device; query a Mobility Management Entity (MME) for a location code associated with the identification information, the location code including at least one of a Location Area Code (LAC) or a Tracking Area Code (TAC); and provide the location information indicating whether or not the location code was provided by the MME in response to the query; and the first device is configured to determine that the predetermined network service is not supported in response to the location information indicating the location code was not provided by the MME. ### Claim 17 Long Term Evolution (LTE) user equipment (UE) comprising: a radio; and a controller connected with the radio and configured to: transmit an attach-request message requesting a combined Evolved Packet System (EPS)/International Mobile Subscriber Identity (IMSI) attach to an LTE access network via the radio; receive an attach-result message associated with the attach-request message via the radio; determine, based at least in part on the attach-result message, data indicating whether single-radio voice call continuity (SRVCC) is supported in the access network; and transmit, via the radio, a Session Initiation Protocol (SIP) request including the data. ### Claim 18 (depends on 17) The LTE UE according to claim 17, wherein: the SIP request includes at least a REGISTER or an INVITE request; and the data consists essentially of: a header name; and a header value indicating whether SRVCC is supported. ### Claim 19 (depends on 17) The LTE UE according to claim 17, wherein: the SIP request comprises a P-Access-Network-Info (PANI) header; and the data comprises an access-info header field of the PANI header. ### Claim 20 (depends on 17) The LTE UE according to claim 17, wherein the controller is configured to: determine, in response to the attach-result message indicating a combined result of attach, that SRVCC is supported; and determine, in response to the attach-result message indicating other than a combined result of attach, that SRVCC is not supported.