# US 12,193,110 B2 · Event handling of subscriber entities > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,193,110 B2 - Document ID: US12193110B2 - Status: Granted - Kind: B2 - Application number: 17/637,861 - Filed: 2019-09-17 - Published: 2022-09-08 - Granted: 2025-01-07 - Earliest claimed: 2019-09-17 - Assignees: Telefonaktiebolaget LM Ericsson (publ) - Applicants: Telefonaktiebolaget LM Ericsson (publ) - Inventors: Kazi Wali Ullah; Patrik Salmela; Abu Shohel Ahmed - Web page: https://patentgrep.com/patent/US12193110B2 ## CPC - H04W 8/183: {Processing at user equipment or user record carrier} - H04W 8/205: {Transfer to or from user equipment or user record carrier} - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract There is provided mechanisms for event handling for at least one subscriber entity. A method is performed by an event handling server. The method comprises obtaining, from an RSP entity, an event registration message of the event. The event registration message comprises an identifier field containing a string of characters identifying the at least one subscriber entity. The string of characters comprises at least one marker character specifying an event type and/or indicating that the event is valid for more than one subscriber entity. The method comprises storing an event record of the event. The event record comprises the identifier field and an address of that RSP entity from which data of the event is to be fetched. The method comprises providing the event record to the at least one subscriber entity. ## Claims ### Claim 1 A method performed by an event handling server in a communication network for event handling for at least one subscriber entity in the communication network, the method comprising: obtaining, from a remote subscriber identity module provisioning (RSP) entity in the communication network, an event registration message for an event associated with RSP, wherein: the event registration message comprises an identifier field containing a string of characters identifying the at least one subscriber entity, and the string of characters comprises at least one marker character that indicates one or more of the following: an event type for the event, and that the event is valid for at least one subscriber entity; storing an event record of the event, wherein the event record comprises the identifier field and an address of the RSP entity from which data of the event is to be fetched; receiving from a subscriber entity a query for any event intended for the subscriber entity, wherein the query comprises an identifier of the subscriber entity; and in response to the query, providing the event record to the subscriber entity. ### Claim 2 (depends on 1) The method of claim 1, wherein: the query includes an indicator of one of the following: a point in time when the subscriber entity most recently queried the event handling server for events intended for the subscriber entity, or an event record most recently received by the subscriber entity; and providing the event record comprises refraining from providing, to the subscriber entity, any event records older than the indicated point in time or the indicated event record. ### Claim 3 (depends on 1) The method of claim 1, wherein: the event is associated with a timestamp indicating when the event was obtained, and the method further comprises purging the event record after a predetermined amount of time following the timestamp. ### Claim 4 (depends on 1) The method of claim 1, wherein: the event registration message comprises an event type field with contents that specify the event type; and the contents of the event type field is included in the event record. ### Claim 5 (depends on 1) The method of claim 1, wherein: all characters of the string of characters are ordered from most significant character to least significant character; and one of the following applies: the at least one marker character fills the string of characters in continuous sequence starting from the least significant character and towards the most significant character, or the at least one marker character fills the string of characters in continuous sequence starting from the most significant character and towards the least significant character. ### Claim 6 (depends on 5) The method of claim 5, wherein: there are at least two marker characters that fill the string of characters in continuous sequence starting from the most significant character and towards the least significant character, and the two marker characters filling the two most significant characters in the string of characters are different from “89”. ### Claim 7 (depends on 1) The method of claim 1, wherein one or more of the following applies: the at least one marker characters are represented by respective wildcard characters when the event is valid for more than one subscriber entity; and the at least one marker character is placed in the string of characters as being surrounded by other characters of the string of characters. ### Claim 8 A method performed by a remote subscriber identity module provisioning (RSP) entity in a communication network for event handling for at least one subscriber entity in the communication network, the method comprising: providing, to an event handling server in the communication network, an event registration message for an event associated with RSP, wherein the event registration message comprises an identifier field containing a string of characters identifying the at least one subscriber entity, and wherein the string of characters comprises at least one marker character that indicates one or more of the following: an event type for the event, and that the event is valid for at least one subscriber entity; and in response to a fetch from a subscriber entity to an address of the RSP entity included in an event record of the event, providing data of the event to the subscriber entity. ### Claim 9 (depends on 8) The method of claim 8, wherein the event registration message comprises an event type field with contents that specify the event type. ### Claim 10 (depends on 8) The method of claim 8, wherein: all characters of the string of characters are ordered from most significant character to least significant character; and one of the following applies: the at least one marker character fills the string of characters in continuous sequence starting from the least significant character and towards the most significant character, or the at least one marker character fills the string of characters in continuous sequence starting from the most significant character and towards the least significant character. ### Claim 11 (depends on 10) The method of claim 10, wherein; there are at least two marker characters that fill the string of characters in continuous sequence starting from the most significant character and towards the least significant character, and the two marker characters filling the two most significant characters in the string of characters are different from “89”. ### Claim 12 (depends on 8) The method of claim 8, wherein one or more of the following applies: the at least one marker characters are represented by respective wildcard characters when the event is valid for more than one subscriber entity; and the at least one marker character is placed in the string of characters as being surrounded by other characters of the string of characters. ### Claim 13 A method for event handling performed by a subscriber entity in a communication network, the method comprising: querying an event handling server in the communication network for any event intended for the subscriber entity, wherein the query includes an identifier of the subscriber entity; and obtaining, from the event handling server in response to the querying, an event record for an event associated with remote subscriber identity module provisioning (RSP), wherein the event record comprises an identifier field containing a string of characters identifying the subscriber entity, and wherein the string of characters comprises at least one marker character that indicates one or more of the following: an event type for the event, and that the event is valid for at least one subscriber entity. ### Claim 14 (depends on 13) The method of claim 13, wherein the event record includes an event type for the event. ### Claim 15 (depends on 13) The method of claim 13, wherein the query includes an indicator of one of the following: a point in time when the subscriber entity most recently queried the event handling server for events intended for the subscriber entity, or an event record most recently received by the subscriber entity. ### Claim 16 (depends on 13) The method of claim 13, wherein: the subscriber entity is associated with an embedded universal integrated circuit card (eUICC) identity (EID); and the string of characters, except for the at least one marker character, is composed of the EID. ### Claim 17 (depends on 13) The method of claim 13, wherein: all characters of the string of characters are ordered from most significant character to least significant character; and one of the following applies: the at least one marker character fills the string of characters in continuous sequence starting from the least significant character and towards the most significant character, or the at least one marker character fills the string of characters in continuous sequence starting from the most significant character and towards the least significant character. ### Claim 18 (depends on 17) The method of claim 17, wherein: there are at least two marker characters that fill the string of characters in continuous sequence starting from the most significant character and towards the least significant character, and the two marker characters filling the two most significant characters in the string of characters are different from “89”. ### Claim 19 (depends on 13) The method of claim 13, wherein one or more of the following applies: the at least one marker characters are represented by respective wildcard characters when the event is valid for more than one subscriber entity; and the at least one marker character is placed in the string of characters as being surrounded by other characters of the string of characters. ### Claim 20 (depends on 1) An event handling server configured for event handling for at least one subscriber entity in a communication network, the event handling server comprising processing circuitry configured to perform the method of claim 1. ### Claim 21 (depends on 8) A remote subscriber identity module provisioning (RSP) entity configured for event handling for at least one subscriber entity in a communication network, the RSP entity comprising processing circuitry configured to perform the method of claim 8. ### Claim 22 (depends on 13) A subscriber entity configured for event handling in a communication network, the subscriber entity comprising processing circuitry configured to perform the method of claim 13.