# US 10,764,744 B2 · System and method for supporting shared service profiles between network devices of core network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,764,744 B2 - Document ID: US10764744B2 - Status: Granted - Kind: B2 - Application number: 16/023,208 - Filed: 2018-06-29 - Published: 2020-01-02 - Granted: 2020-09-01 - Earliest claimed: 2018-06-29 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Suzann Hua; Priscilla Lau; Sudhakar Reddy Patil - Web page: https://patentgrep.com/patent/US10764744B2 ## CPC - H04W 8/186: {Processing of subscriber group data} - H04W 4/08: User group management - H04W 8/12: between location registers or mobility servers - H04W 8/18: Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data - H04W 48/14: using user query {or user detection} - H04W 68/02: Arrangements for increasing efficiency of notification or paging channel - H04L 67/306: User profiles - H04W 8/20: Transfer of user or subscriber data - H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration - 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 Systems and method are provided to reduce redundant data transfers for service profiles within a wireless core network. A network device in the core network receives, from a mobility management entity (MME), a user profile request. The user profile request includes a user identifier for an end device. The network device determines that a user profile corresponding to the user identifier includes a shared service profile and determines, when the user profile includes a shared service profile, whether the MME has stored the shared service profile. When the MME has not stored the shared service profile, the network device sends, to the MME, the shared service profile and a shared profile identifier for the shared service profile. The network device sends, to the MME, a response to the user profile request, the response including the user identifier and the shared profile identifier for the shared service profile. ## Claims ### Claim 1 A method, comprising: receiving, by a first network device and from a second network device, a user profile request, the user profile request including a user identifier for an end device; determining, by the first network device, that a user profile corresponding to the user identifier includes a shared service profile, wherein the shared service profile includes parameters that apply to multiple subscriber profiles; determining, by the first network device and based on the determining that the user profile includes a shared service profile, whether the second network device has previously stored the shared service profile, wherein determining whether the second network device has previously stored the shared service profile comprises comparing, by the first network device, a mobility management entity (MME) identifier that corresponds to the second network device to the shared profile identifier in a data structure including multiple MME identifiers associated with the shared profile identifier; sending, by the first network device and to the second network device, the shared service profile and a shared profile identifier for the shared service profile, when it is determined that the second network device has not previously stored the shared service profile; and sending, by the first network device and to the second network device, a response to the user profile request, the response including the user identifier and the shared profile identifier for the shared service profile, wherein the response to the user profile request is sent separately from the shared service profile. ### Claim 2 (depends on 1) The method of claim 1, further comprising: associating, by the first network device and after sending the shared service profile, the MME identifier, corresponding to the second network device, with the shared profile identifier in a data structure of multiple MME identifiers and shared profile identifiers. ### Claim 3 (depends on 1) The method of claim 1, wherein the user profile request includes an Update-Location-Request message, and wherein the response to the user profile request includes an Update-Location-Answer message. ### Claim 4 (depends on 1) The method of claim 1, wherein sending the shared service profile and the shared profile identifier further comprises: sending the shared service profile and the shared profile identifier via a Diameter S6a interface. ### Claim 5 (depends on 4) The method of claim 4, wherein the shared service profile and a shared profile identifier are included within an Insert-Subscriber-Data-Request (IDR). ### Claim 6 (depends on 1) The method of claim 1, further comprising: receiving, by the first network device, an update to the shared service profile; identifying, by the first network device, one or more second network devices that have stored the shared service profile prior to the update; and sending, by the first network device, the update to the one or more second network devices. ### Claim 7 (depends on 6) The method of claim 6, wherein sending the update comprises: sending the update and the shared profile identifier via an Insert-Subscriber-Data-Request (IDR) over a Diameter S6a interface. ### Claim 8 (depends on 7) The method of claim 7, wherein the IDR includes an attribute value pair (AVP) to differentiate between a full download and the update for the shared service profile. ### Claim 9 (depends on 1) The method of claim 1, further comprising: receiving, by the first network device and from the second network device, another user profile request, the other user profile request including another user identifier for a different end device; determining, by the first network device, that another user profile corresponding to the other user identifier includes the shared service profile; and sending, by the first network device and to the second network device, another response to the user profile request, the other response including the other user identifier and the shared profile identifier for the shared service profile. ### Claim 10 A system comprising a first network device, the first network device including: one or more memories to store instructions; a communication interface configured to connect to one or more devices in a wireless core network; and one or more processors to execute the instructions to: receive, from a second network device, a user profile request, the user profile request including a user identifier for an end device, determine that a user profile corresponding to the user identifier includes a shared service profile, wherein the shared service profile includes parameters that apply to multiple subscriber profiles, determine, based on the determining that the user profile includes a shared service profile, whether the second network device has previously stored the shared service profile, wherein determining whether the second network device has previously stored the shared service profile comprises comparing, by the first network device, a mobility management entity (MME) identifier that corresponds to the second network device to the shared profile identifier in a data structure including multiple MME identifiers associated with the shared profile identifier, send, to the second network device, the shared service profile and a shared profile identifier for the shared service profile, when it is determined that the second network device has not stored the shared service profile, and send, to the second network device, a response to the user profile request, the response including the user identifier and the shared profile identifier for the shared service profile, wherein the response to the user profile request is sent separately from the shared service profile. ### Claim 11 (depends on 10) The system of claim 10, wherein the first network device is a home subscriber server (HSS) device for a Long Term Evolution network, and wherein the second network device is a MME for the Long Term Evolution network. ### Claim 12 (depends on 10) The system of claim 10, wherein the one or more processors are further to execute the instructions to: update, after sending the shared service profile, a data record to indicate the second network device received the shared service profile. ### Claim 13 (depends on 10) The system of claim 10, wherein the first network device is a Unified Data Management (UDM) function for a next generation core (NGC) network, and wherein the second network device is a Access and Mobility Management function (AMF) for the NGC network. ### Claim 14 (depends on 10) The system of claim 10, wherein, when sending the shared service profile and the shared profile identifier, the one or more processors are further to execute the instructions to: send the shared service profile and the shared profile identifier via an Insert-Subscriber-Data-Request (IDR). ### Claim 15 (depends on 10) The system of claim 10, further comprising the second network device, the second network device including a processor configured to: store the shared service profile and the shared profile identifier in a local memory, receive the response to the user profile request, retrieve the shared service profile from the local memory, and generate a user profile for the end device based on the user identifier and the shared service profile. ### Claim 16 (depends on 10) The system of claim 10, wherein the one or more processors are further to execute the instructions to: receive an update to the shared service profile, identify one or more second network devices that have stored the shared service profile prior to the update, and send the update to the one or more second network devices. ### Claim 17 (depends on 10) The system of claim 10, wherein the one or more processors are further to execute the instructions to: receive, from the second network device, another user profile request, the other user profile request including another user identifier for a different end device, determine that another user profile corresponding to the other user identifier includes the shared service profile, and send, to the second network device, another response to the user profile request, the other response including the other user identifier and the shared profile identifier for the shared service profile. ### Claim 18 A non-transitory computer-readable medium containing instructions executable by at least one processor, the computer-readable medium comprising the instructions to: receive, from a first network device, a user profile request, the user profile request including a user identifier for an end device; determine that a user profile corresponding to the user identifier includes a shared service profile; determine, based on the determining that the user profile includes a shared service profile, whether the first network device has stored the shared service profile, wherein the shared service profile include parameters that apply to multiple subscriber profiles, and wherein determining whether the first network device has previously stored the shared service profile comprises comparing a mobility management entity (MME) identifier that corresponds to the first network device to the shared profile identifier in a data structure including multiple MME identifiers associated with the shared profile identifier; send, to the first network device, the shared service profile and a shared profile identifier for the shared service profile, when it is determined that the first network device has not stored the shared service profile; and send, to the first network device, a response to the user profile request, the response including the user identifier and the shared profile identifier for the shared service profile, wherein the response to the user profile request is sent separately from the shared service profile. ### Claim 19 (depends on 18) The non-transitory computer-readable medium claim 18, further comprising instructions to: receive an update to the shared service profile; identify one or more first network devices that have stored the shared service profile prior to the update; and send the update to the one or more first network devices. ### Claim 20 (depends on 18) The non-transitory computer-readable medium claim 18, further comprising instructions to: receive, from the first network device, another user profile request, the other user profile request including another user identifier for a different end device, determine that another user profile corresponding to the other user identifier includes the shared service profile, and send, to the first network device, another response to the user profile request, the other response including the other user identifier and the shared profile identifier for the shared service profile.