Method, apparatus and computer program

Abstract

There is provided an apparatus comprising means for: receiving an indication of a permanent device identifier from a second network function; storing information associated with the indication of the permanent device identifier received from the second network function; receiving an indication of a state associated with the permanent device identifier; and providing an indication to the second network function related to the status associated with the permanent device identifier based on the information.

Description

Technical Field

[0001] Various example embodiments of the present disclosure relate to methods, apparatuses, and computer programs for communication networks. Background Art

[0002] A communication system can be regarded as a facility that enables communication between two or more communication devices or provides access to a communication device for a data network. A mobile or wireless communication network is an example of a communication network. A communication device can be served by an application server.

[0003] Such communication networks operate according to standards provided, for example, by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). An example of a standard is the so-called 5G (Fifth Generation) standard promulgated by 3GPP. Summary of the Invention

[0004] Some example embodiments of the present disclosure will be described with respect to certain aspects. These aspects are not intended to indicate the key or essential features of the example embodiments of the present disclosure, nor are they intended to limit its scope. Given the present disclosure, other features, aspects, and units will be readily apparent to those skilled in the art. For example, it should be understood that further aspects can be provided by a combination of any two or more of the various aspects described below.

[0005] According to a first aspect, there is provided an apparatus, the apparatus comprising means for: receiving an indication of a permanent device identifier from a second network function; storing information associated with the indication of the permanent device identifier received from the second network function; receiving an indication of a state associated with the permanent device identifier; and providing, based on the information, an indication related to the state associated with the permanent device identifier to the second network function.

[0006] In some example embodiments, the indication of the state associated with the permanent device identifier is an indication that the state has changed to an indication that the permanent device identifier is prohibited.

[0007] In some example embodiments, the means is further for: generating or updating a record associated with the permanent device identifier based on the received indication of the state, the record for the permanent device identifier including the state of the permanent device identifier.

[0008] In some example embodiments, the state indicating that the permanent device identifier is prohibited means that the permanent device identifier is blocked or restricted from use.

[0009] In some example embodiments, storing the information includes: storing an association between the second network function and the permanent device identifier based on the indication of the permanent device identifier, wherein the indication provided to the second network function and related to the state associated with the permanent device identifier is based on the association.

[0010] In some example embodiments, the indication related to the state associated with the permanent device identifier includes: a request for the second network function to deregister a subscriber associated with the permanent device identifier.

[0011] In some example embodiments, storing the information includes: storing a subscription for a change in the state associated with the permanent device identifier for the second network function based on the indication of the permanent device identifier, wherein the indication provided to the second network function and related to the state associated with the permanent device identifier is based on the subscription.

[0012] In some example embodiments, the indication related to the state associated with the permanent device identifier includes: an indication that the state associated with the permanent device identifier has changed, and an indication of the state associated with the permanent device identifier.

[0013] In some example embodiments, the indication of the permanent device identifier is received in a request for the state associated with the permanent device identifier.

[0014] In some example embodiments, the component is configured to: determine whether there is a record for the permanent device identifier based on the indication of the permanent device identifier; and based on the determination, provide to the second network function the state associated with the permanent device identifier from the record for the permanent device identifier.

[0015] In some example embodiments, the indication of the permanent device identifier is received in a request for subscribing to a notification related to the state associated with the permanent device identifier.

[0016] In some example embodiments, the component is further configured to: in response to receiving the request for subscribing to the state associated with the permanent device identifier, provide to the second network function one of the following: the state associated with the permanent device identifier from the record for the permanent device identifier, or an indication that no record available for the permanent device identifier is stored.

[0017] In some example embodiments, the indication of the state associated with the permanent device identifier is received from an operations management and maintenance service.

[0018] In some example embodiments, the component is further configured to: delete the information associated with the indication of the permanent device identifier received from the second network function, based on one of the following: a request received from the second network function to delete the information; or an indication of the permanent device identifier received from a third network function.

[0019] In some example embodiments, the apparatus is for a network function.

[0020] In some example embodiments, at least one of the following: the network function is a device identity register, the second network function is an access and mobility management function, the second network function is a mobility management entity, the third network function is another access and mobility management function, or the third network function is another mobility management entity.

[0021] According to one aspect, there is provided an apparatus, the apparatus including components for: providing an indication of a permanent device identifier to a network function; and receiving from the network function an indication related to a state associated with the permanent device identifier.

[0022] In some example embodiments, the indication received from the network function and related to the state associated with the permanent device identifier includes: a request for the second network function to deregister a subscriber associated with the permanent device identifier.

[0023] In some example embodiments, the indication received from the network function and related to the state associated with the permanent device identifier includes: an indication that the state associated with the permanent device identifier has changed, and an indication of the state associated with the permanent device identifier.

[0024] In some example embodiments, the indication received from the network function and related to the state associated with the permanent device identifier includes: an indication that the state has changed to an indication of a state where the permanent device identifier is prohibited.

[0025] In some example embodiments, providing an indication of a permanent device identifier to a network function includes: providing to the network function a request for subscribing to a notification related to the state associated with the permanent device identifier.

[0026] In some example embodiments, the request includes: an indication that the state of the currently stored permanent device identifier is to be provided.

[0027] In some example embodiments, the component is further configured to: based on the request, receive from the network function one of the following: the status associated with the permanent device identifier from a record for the permanent device identifier, or an indication that no record available for the permanent device identifier is stored.

[0028] In some example embodiments, the component is further configured to: provide to the network function a request to delete information stored at the network function related to the second network function and the permanent device identifier.

[0029] In some example embodiments, the apparatus is for a second network function.

[0030] In some example embodiments, at least one of the following: the network function is a device identity register, the second network function is an access and mobility management function, the second network function is a mobility management entity, the third network function is another access and mobility management function, or the third network function is another mobility management entity.

[0031] According to one aspect, there is provided a method, the method comprising: receiving an indication of a permanent device identifier from a second network function; storing information associated with the indication of the permanent device identifier received from the second network function; receiving an indication of a status associated with the permanent device identifier; and based on the information, providing to the second network function an indication related to the status associated with the permanent device identifier.

[0032] In some example embodiments, the indication of the status associated with the permanent device identifier is an indication that the status has changed to an indication that the permanent device identifier is prohibited.

[0033] In some example embodiments, the method comprises: based on the indication of the status that has been received, generating or updating a record associated with the permanent device identifier, the record for the permanent device identifier comprising the status of the permanent device identifier.

[0034] In some example embodiments, the status indicating that the permanent device identifier is prohibited means that the permanent device identifier is blocked or restricted from use.

[0035] In some example embodiments, storing the information comprises: based on the indication of the permanent device identifier, storing an association between the second network function and the permanent device identifier, wherein the indication provided to the second network function related to the status associated with the permanent device identifier is based on the association.

[0036] In some example embodiments, the indication related to the state associated with the permanent device identifier includes a request for the second network function to unsubscribe a subscriber associated with the permanent device identifier.

[0037] In some example embodiments, storing the information includes: storing, based on the indication of the permanent device identifier, a subscription for a change in the state associated with the permanent device identifier for the second network function, wherein the indication provided to the second network function and related to the state associated with the permanent device identifier is based on the subscription.

[0038] In some example embodiments, the indication related to the state associated with the permanent device identifier includes: an indication that the state associated with the permanent device identifier has changed, and an indication of the state associated with the permanent device identifier.

[0039] In some example embodiments, the indication of the permanent device identifier is received in a request for the state associated with the permanent device identifier.

[0040] In some example embodiments, the method includes: determining, based on the indication of the permanent device identifier, whether there is a record for the permanent device identifier; and based on the determination, providing to the second network function the state associated with the permanent device identifier from the record for the permanent device identifier.

[0041] In some example embodiments, the indication of the permanent device identifier is received in a request for subscribing to a notification related to the state associated with the permanent device identifier.

[0042] In some example embodiments, the method includes: in response to receiving the request for subscribing to the state associated with the permanent device identifier, providing to the second network function one of: the state associated with the permanent device identifier from the record for the permanent device identifier, or an indication that there is no record stored available for the permanent device identifier.

[0043] In some example embodiments, the indication of the state associated with the permanent device identifier is received from an operations management and maintenance service.

[0044] In some example embodiments, the method includes: deleting the information associated with the indication of the permanent device identifier received from the second network function, based on one of the following: a request for deleting the information received from the second network function; or an indication of the permanent device identifier received from a third network function.

[0045] In some example embodiments, the method is performed by a network function.

[0046] In some example embodiments, at least one of the following: the network function is a device identity register, the second network function is an access and mobility management function, the second network function is a mobility management entity, the third network function is another access and mobility management function, or the third network function is another mobility management entity.

[0047] According to one aspect, a method is provided, the method includes: providing an indication of a permanent device identifier to a network function; and receiving from the network function an indication related to the status associated with the permanent device identifier.

[0048] In some example embodiments, the indication received from the network function and related to the status associated with the permanent device identifier includes: a request for the second network function to deregister a subscriber associated with the permanent device identifier.

[0049] In some example embodiments, the indication received from the network function and related to the status associated with the permanent device identifier includes: an indication that the status associated with the permanent device identifier has changed, and an indication of the status associated with the permanent device identifier.

[0050] In some example embodiments, the indication received from the network function and related to the status associated with the permanent device identifier includes: an indication that the status has changed to an indication of a state in which the permanent device identifier is prohibited.

[0051] In some example embodiments, the providing an indication of a permanent device identifier to a network function includes: providing to the network function a request for subscribing to a notification related to the status associated with the permanent device identifier.

[0052] In some example embodiments, the request includes: an indication that the status of the currently stored permanent device identifier is to be provided.

[0053] In some example embodiments, the method includes: based on the request, receiving from the network function one of the following: the status associated with the permanent device identifier from a record for the permanent device identifier, or an indication that there is no stored record available for the permanent device identifier.

[0054] In some example embodiments, the method includes: providing to the network function a request to delete information stored at the network function that relates to the second network function and the permanent device identifier.

[0055] In some example embodiments, the method is performed by a second network function.

[0056] In some example embodiments, at least one of the following: the network function is a device identity register, the second network function is an access and mobility management function, the second network function is a mobility management entity, the third network function is another access and mobility management function, or the third network function is another mobility management entity.

[0057] According to a first aspect, there is provided an apparatus comprising: at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus to perform: receiving an indication of a permanent device identifier from a second network function; storing information associated with the indication of the permanent device identifier received from the second network function; receiving an indication of a status associated with the permanent device identifier; and based on the information, providing to the second network function an indication related to the status associated with the permanent device identifier.

[0058] In some example embodiments, the indication of the status associated with the permanent device identifier is an indication that the status has changed to indicate a state in which the permanent device identifier is prohibited.

[0059] In some example embodiments, the apparatus is caused to perform: based on the received indication of the status, generating or updating a record associated with the permanent device identifier, and the record for the permanent device identifier includes the status of the permanent device identifier.

[0060] In some example embodiments, the state indicating that the permanent device identifier is prohibited means that the use of the permanent device identifier is blocked or restricted.

[0061] In some example embodiments, storing the information includes: storing an association between the second network function and the permanent device identifier based on the indication of the permanent device identifier, wherein the indication provided to the second network function and related to the status associated with the permanent device identifier is based on the association.

[0062] In some example embodiments, the indication related to the status associated with the permanent device identifier includes a request for the second network function to de-register a subscriber associated with the permanent device identifier.

[0063] In some example embodiments, storing the information includes: storing a subscription for a change in the status associated with the permanent device identifier for the second network function based on the indication of the permanent device identifier, wherein the indication provided to the second network function and related to the status associated with the permanent device identifier is based on the subscription.

[0064] In some example embodiments, the indication related to the status associated with the permanent device identifier includes: an indication that the status associated with the permanent device identifier has changed, and an indication of the status associated with the permanent device identifier.

[0065] In some example embodiments, the indication of the permanent device identifier is received in a request for the status associated with the permanent device identifier.

[0066] In some example embodiments, the apparatus is caused to perform: determining, based on the indication of the permanent device identifier, whether there is a record for the permanent device identifier; and based on the determination, providing to the second network function the status associated with the permanent device identifier from the record for the permanent device identifier.

[0067] In some example embodiments, the indication of the permanent device identifier is received in a request for subscribing to a notification related to the status associated with the permanent device identifier.

[0068] In some example embodiments, the apparatus is caused to perform: in response to receiving the request for subscribing to the status associated with the permanent device identifier, providing to the second network function one of: the status associated with the permanent device identifier from the record for the permanent device identifier, or an indication that there is no record stored available for the permanent device identifier.

[0069] In some example embodiments, the indication of the status associated with the permanent device identifier is received from an operations management and maintenance service.

[0070] In some example embodiments, the apparatus is caused to perform: deleting the information associated with the indication of the permanent device identifier received from the second network function based on one of the following: a request received from the second network function to delete the information; or an indication of the permanent device identifier received from a third network function.

[0071] In some example embodiments, the apparatus is for a network function.

[0072] In some example embodiments, at least one of the following: the network function is a device identity register, the second network function is an access and mobility management function, the second network function is a mobility management entity, the third network function is another access and mobility management function, or the third network function is another mobility management entity.

[0073] According to one aspect, there is provided an apparatus comprising: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform: providing an indication of a permanent device identifier to a network function; and receiving from the network function an indication related to a status associated with the permanent device identifier.

[0074] In some example embodiments, the indication received from the network function and related to the status associated with the permanent device identifier includes: a request for the second network function to deregister a subscriber associated with the permanent device identifier.

[0075] In some example embodiments, the indication received from the network function and related to the status associated with the permanent device identifier includes: an indication that the status associated with the permanent device identifier has changed, and an indication of the status associated with the permanent device identifier.

[0076] In some example embodiments, the indication received from the network function and related to the status associated with the permanent device identifier includes: an indication that the status has changed to an indication of a state in which the permanent device identifier is prohibited.

[0077] In some example embodiments, the providing an indication of a permanent device identifier to a network function includes: providing to the network function a request to subscribe to notifications related to the status associated with the permanent device identifier.

[0078] In some example embodiments, the request includes: an indication that the status of the currently stored permanent device identifier is to be provided.

[0079] In some example embodiments, the apparatus is caused to perform: based on the request, receive from the network function one of the following: the status associated with the permanent device identifier from a record for the permanent device identifier, or an indication that there is no stored record available for the permanent device identifier.

[0080] In some example embodiments, the apparatus is caused to perform: provide to the network function a request to delete information stored at the network function that relates to the second network function and the permanent device identifier.

[0081] In some example embodiments, the apparatus is for a second network function.

[0082] In some example embodiments, at least one of the following: the network function is a device identification register, the second network function is an access and mobility management function, the second network function is a mobility management entity, the third network function is another access and mobility management function, or the third network function is another mobility management entity.

[0083] According to a first aspect, there is provided an apparatus, the apparatus comprising: circuitry configured to perform: receive an indication of a permanent device identifier from a second network function; circuitry configured to perform: store information associated with the indication of the permanent device identifier received from the second network function; circuitry configured to perform: receive an indication of a status associated with the permanent device identifier; and circuitry configured to perform: based on the information, provide to the second network function an indication related to the status associated with the permanent device identifier.

[0084] According to one aspect, there is provided an apparatus, the apparatus comprising: circuitry configured to perform: provide an indication of a permanent device identifier to a network function; and circuitry configured to perform: receive from the network function an indication related to a status associated with the permanent device identifier.

[0085] According to one aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following operations: receive an indication of a permanent device identifier from a second network function; store information associated with the indication of the permanent device identifier received from the second network function; receive an indication of a status associated with the permanent device identifier; and based on the information, provide to the second network function an indication related to the status associated with the permanent device identifier.

[0086] According to one aspect, there is provided a computer program comprising instructions which, when executed by a device, cause the device to perform at least the following operations: provide an indication of a permanent device identifier to a network function; and receive from the network function an indication related to a status associated with the permanent device identifier. A computer program stored on a medium may cause a device to perform the methods described herein.

[0087] A non-transitory computer-readable medium comprising program instructions which, when executed by a device, cause the device to perform the methods (or portions thereof) described herein.

[0088] An electronic device may comprise the device described herein.

[0089] Various other aspects and further example embodiments are also described in the following detailed description and the appended claims.

[0090] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. Any example embodiments that do not fall within the scope of the claims (if any) are to be construed as helpful in understanding the examples of the present disclosure.

[0091] List of Abbreviations:

[0092] AF: Application Function

[0093] AMF: Access and Mobility Management Function

[0094] AN: Access Network

[0095] BS: Base Station

[0096] CN: Core Network

[0097] DL: Downlink

[0098] EIR: Equipment Identity Register

[0099] eNB: eNodeB

[0100] gNB: gNodeB

[0101] HTTP: HyperText Transfer Protocol

[0102] IIoT: Industrial Internet of Things

[0103] LTE: Long-Term Evolution

[0104] NEF: Network Exposure Function

[0105] NG-RAN: Next Generation Radio Access Network

[0106] NF: Network Function

[0107] NR: New Radio

[0108] NRF: Network Repository Function

[0109] NW: Network

[0110] MME: Mobility Management Entity

[0111] MS: Mobile Station

[0112] PCF: Policy Control Function

[0113] PEI: Permanent Equipment Identifier

[0114] PLMN: Public Land Mobile Network

[0115] OAM: Operation, Administration and Maintenance

[0116] RAN: Radio Access Network

[0117] RF: Radio Frequency

[0118] SMF: Session Management Function

[0119] SUPI: Subscribed Permanent Identifier

[0120] UE: User Equipment

[0121] UDR: Unified Data Repository

[0122] UDSF: Unstructured Data Storage Function

[0123] UDM: Unified Data Management

[0124] UL: Uplink

[0125] UPF: User Plane Function

[0126] 3GPP: 3rd Generation Partnership Project

[0127] 5G: 5th Generation

[0128] 5GC: 5G Core Network

[0129] 5G-AN: 5G Radio Access Network

[0130] 5GS: 5G System Description of the Drawings

[0131] Some example embodiments will now be described with reference to the drawings, by way of illustration and non-limiting example only, wherein:

[0132] Figure 1 Shows a schematic diagram of a 5G communication system;

[0133] Figure 2 Shows a schematic diagram of a device for a Figure 1 5G communication system;

[0134] Figure 3 Shows a Figure 1 schematic diagram of a communication device for a 5G communication system;

[0135] Figure 4 Shows an example signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0136] Figure 5 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0137] Figure 6 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0138] Figure 7 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0139] Figure 8 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0140] Figure 9 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0141] Figure 10 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0142] Figure 11 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0143] Figure 12 Shows another exemplary signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure;

[0144] Figure 13 FIG. 0 shows an exemplary method flow diagram executed by a device in accordance with some example embodiments of the present disclosure;

[0145] Figure 14 FIG. 1 shows another exemplary method flow diagram executed by a device in accordance with some example embodiments of the present disclosure; and

[0146] Figure 15 FIG. 2 shows a schematic diagram of a non - volatile storage medium storing instructions that, when executed by a processor, allow the processor to execute Figures 13 to 14 one or more of the methods (or portions thereof) described above. DETAILED DESCRIPTION

[0147] In a 5G network, an Equipment Identity Register (EIR) is defined. The EIR is a core network function (NF) that supports the function of checking the status of a mobile device or user equipment using the permanent identifier of the device (e.g., checking whether it is not prohibited from use). The reference point N17 is used for the interaction between the EIR and the Access and Mobility Management Function (AMF), enabling the status of the Mobile Equipment (ME) identity to be checked.

[0148] During any process of establishing a signaling connection with a UE, the network can perform an ME identity check through the "N5g - eir_EquipmentIdentityCheck" service presented by the 5G - EIR via the EIR. The "N5g - eir_EquipmentIdentityCheck" service can be used to determine whether the ME / UE is blacklisted.

[0149] In this way, the EIR is a repository of device records representing devices (e.g., ME, UE) that may be designated as "permitted", "restricted", or "tracked". "Restricted" devices may be referred to as blacklisted devices. For example, if a network access device is reported as stolen, the record of that device can be added to the EIR, and the EIR marks the device as restricted (or blacklisted).

[0150] Whenever processing a request for a UE to register on the network, the AMF can check the records in the EIR. If the device has an EIR record and the status is set to restricted / blacklisted, the AMF can reject the registration request.

[0151] The records in the EIR are identified using the Permanent Equipment Identifier (PEI). The PEI is globally unique for a device. When attempting network registration, the device provides the PEI to the AMF. In 5G, the PEI is the means by which the network identifies the UE. For a device capable of accessing a 3GPP network, the PEI is the International Mobile Equipment Identity (IMEI).

[0152] When processing a network registration attempt, the AMF can query the EIR. If the communication device (e.g., ME, UE) attempting registration is recorded as restricted in the EIR, the AMF can reject the registration attempt. In this way, communication devices prohibited from accessing the network are subsequently prevented from registering. For example, after reporting a communication device stolen, access to the network can be prohibited for the communication device. In this context, it should be understood that the terms "restricted", "prohibited", "blacklisted", and "blocked" can be used interchangeably. These terms are used to describe communication devices prohibited from accessing the network.

[0153] When a communication device is to be recorded as restricted, a record of the communication device can be generated, added to, or updated in the EIR. Any subsequent attempt to register the communication device with the network can be blocked (assuming the Access and Mobility Management Function (AMF) checks the EIR).

[0154] However, there may be a lag (duration) between when the communication device is marked as restricted and when the communication device attempts to register again. During this period, the communication device is still able to obtain network services. Certain challenges arise in the following process of logging out the communication device once the record is updated to be restricted in the EIR. In principle, this can be achieved by the EIR initiating a logout at the AMF immediately when the record of the communication device is set to restricted.

[0155] The EIR that initiates the logout at the AMF can use the following Unified Data Management (UDM) mechanism: 1) The EIR sends a request to the UDM containing the PEI of the communication device to be logged out, 2) The UDM determines the subscriber currently associated with the PEI, 3) The UDM determines the AMF currently serving the subscriber, 4) The UDM sends a logout request to the AMF containing the subscriber ID, and 5) The AMF logs out the subscriber.

[0156] This mechanism involves the UDM looking up the subscriber currently associated with the PEI of the communication device to be logged out. This can be performed by requesting the Unified Data Repository (UDR) to search all subscriber context (registration) information to find the subscriber record containing the PEI. However, the UDR may not support searching for subscriber records based on the PEI. Additionally, requesting subscriber information based on the PEI is not supported on the UDR interface (Nudr). Furthermore, if there are multiple UDRs in the network, all UDRs are searched to find the PEI. Therefore, there are many issues associated with using this mechanism to log out communication devices.

[0157] Another way for the UDM to find the subscriber currently associated with the PEI of the communication device to be deregistered is to search an auxiliary data store for the association between the PEI and the subscriber and / or the AMF.

[0158] However, in order to use this method, an auxiliary data store maintaining the association between the device and the subscriber and / or the AMF must be maintained. This involves replication of data and associated problems (e.g., the PEI may already be associated with a subscriber in the UDR). In addition, this also means maintaining the auxiliary data store of the association and involves database updates every time the AMF performs a registration. There is no standardized mechanism for storing this association data. Therefore, there are many problems associated with using this mechanism to deregister a communication device.

[0159] Any of the various example embodiments of the present disclosure may solve one or more problems explicitly described herein or apparent to those skilled in the art from the present disclosure (at least in part).

[0160] In some example embodiments, there is provided an apparatus configured to (e.g., including components for performing the following operations and / or including at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform the following operations): receive an indication of a permanent device identifier from a second network function (e.g., an AMF or an MME), and store information associated with the indication of the permanent device identifier received from the second network function. The apparatus is also configured to receive an indication of a status associated with the permanent device identifier, and based on the information, provide an indication related to the status associated with the permanent device identifier to the second network function.

[0161] In this way, a deregistration request or an indication associated with deregistration is initiated by the EIR using the storage of information between the PEI and the subscriber and / or the AMF separated from the stored UDR subscriber data, without requiring additional signaling to maintain the data store whenever the AMF registers a subscriber.

[0162] In some example embodiments, an existing EIR service operation (i.e., CheckEquipmentIdentity) in the EIR for checking the status of a held device (e.g., restricted (or blacklisted), tracked (or grey-listed), allowed (or white-listed)) is also used to deregister a blacklisted communication device. This EIR service operation is performed by the AMF every time a communication device attempts to register on the network.

[0163] In some example embodiments, CheckEquipmentIdentity is used to store an association in the EIR, which the EIR will use to send a deregistration request to the AMF when the device is marked as blacklisted / blocked at a later time. The EIR behavior can be extended such that when a CheckEquipmentIdentity request is processed, the EIR stores the association between the PEI received in the request and the AMF that sent the request. In some example embodiments, the association also includes the identity of the subscriber (e.g., subscriber ID).

[0164] When the EIR is updated with a record that marks the device as blacklisted / blocked, the EIR searches for the association of the device. Upon finding the association, the EIR directly sends a deregistration request to the AMF indicated in the association. The AMF behavior and the association interface (with the EIR) can be extended to accept the deregistration request from the EIR and use the PEI sent by the EIR in the request to locate the device registration to remove it.

[0165] In some example embodiments, a new service operation is configured for the EIR that allows the AMF to subscribe to notifications regarding device identity records in the EIR. The subscription request creates a subscription to the notification, whereby the subscription serves as an association (to be stored in the EIR) between the PEI and the AMF. The subscription can be created based on the presence or absence of a device identity record for the PEI in the EIR. This allows notifications to be sent when a device identity record is created, as well as when it is updated or deleted.

[0166] In some example embodiments, the subscription operation can specify an "intermediate report" parameter to request the current status of the device identity record for the PEI. If this parameter is included, the EIR sends the content of the device identity record for the PEI in response to the subscription request. If no record currently exists, this can be indicated in response to the subscription request.

[0167] In some example embodiments, when the intermediate report parameter is used in the subscription request, the subscription request can serve as an alternative to the CheckEquipmentIdentity (check device identity) operation, as it achieves both subscription and retrieval of the current status in a single operation. In some example embodiments, both the CheckEquipmentIdentity operation and the subscription to the notification are used (individually).

[0168] In some example embodiments, the EIR behavior is extended such that when the EIR is updated with a record that marks the device as blocked (or changes the state of the communication device), the EIR (directly) sends a notification to the AMF that has subscribed to notifications regarding the communication device.

[0169] In some example embodiments, the AMF behavior and the interface to the EIR are extended to accept notifications of device state changes and use the PEI sent by the EIR in the notification to locate the communication device registration and remove it.

[0170] In explaining the various example embodiments in further detail, reference is made to Figures 1 to 3 to briefly explain certain general aspects of the wireless communication system and communication devices that can utilize the EIR service to assist in understanding the technology underlying the example embodiments. For example, the EIR and AMF of a 5G communication system capable of communicating with each other are described (as Figure 1 shown). Additionally, communication devices capable of being assigned a device state (e.g., running, prohibited, etc.) are described (as Figure 3 shown).

[0171] Figure 1 A schematic diagram of a 5G communication system 100 is shown. The wireless communication system 100 includes one or more communication devices 102, such as user equipment (UE) or terminals. The wireless communication system 100 includes a 5G system (5GS). The 5GS includes a 5G radio access network (5G-RAN) 106, a 5G core network (5GC) 104 including one or more network functions (NF), one or more application functions (AF) 108, and one or more data networks (DN) 110.

[0172] The 5G-RAN 106 may include one or more gNodeB (gNB) distributed unit (DU) functions connected to one or more gNodeB (gNB) centralized unit (CU) functions.

[0173] The 5GC 104 includes an access and mobility management function (AMF) 112, a session management function (SMF) 114, an authentication server function (AUSF) 116, a user data management (UDM) 118, a user plane function (UPF) 120, a network exposure function (NEF) 122, an EIR 124, and / or other NFs. Some of the various example embodiments as shown below (and described herein) may be applied to the 3GPP 5G standard. Additionally or alternatively, some of the various example embodiments may also be applied to 6G, advanced 5G, 4G, 3G, and other 3GPP standards.

[0174] In the wireless communication system 100 (e.g., Figure 1In the example shown in [FIGURE], the communication device 102, such as a terminal, user device, user equipment (UE), and / or machine type communication device, is provided with wireless access via at least a wireless transmitting and / or receiving node or point (such as a base station). The communication device 102 is provided with appropriate signal receiving and transmitting means for enabling (or otherwise facilitating) communication, such as enabling (or otherwise facilitating) access to a communication network or direct communication with other devices. The communication device 102 can access a carrier provided by a base station or access point and transmit and / or receive communication via the carrier.

[0175] Figure 2 An example of device 200 is shown. Device 200 can be used for Figure 1 a 5G communication system. Device 200 can be used to control the functions of one or more network entities and / or network functions, such as Figure 1 the entities of 5G-RAN or 5GC as shown. Device 200 includes at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. At least one processor 212, 213 is coupled to RAM 211a, ROM 211b. At least one processor 212, 213 can be configured to execute appropriate software code 215. The software code 215 can, for example, enable (or otherwise facilitate) the execution of any of the aspects described herein or various example embodiments of the present disclosure (including any part thereof). The software code 215 can be stored in ROM 211b. Device 200 can be interconnected with another device 200 that controls another entity / function of 5G-AN or 5GC. In some example embodiments, device 200 can be configured to execute one or more functions of 5G-AN or 5GC. For example, device 200 can be configured to execute at least some of the functions of a specific function of 5G-AN or 5GC. For example, device 200 can be configured to operate as a specific function of 5G-AN or 5GC. In an alternative example, device 200 can be configured to execute at least some of the functions of two or more functions of 5G-AN and / or 5GC. For example, device 200 can be configured to operate as two or more functions of 5G-AN and / or 5GC. Device 200 can include one or more circuits or circuitry (not shown) that can be configured to execute any aspect described herein or various example embodiments of the present disclosure (including any part thereof).

[0176] Figure 3 An example of communication device 300 is shown. Communication device 300 can be similar to Figure 1The communication device 102 shown in []. The communication device 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting and illustrative examples of the communication device 300 include a user equipment (UE), a terminal, a mobile station (MS), or a mobile device (such as a mobile phone or a so-called "smartphone"), a computer equipped with a wireless interface card or other wireless interface facilities (such as a USB adapter), a personal data assistant (PDA), or a tablet computer equipped with wireless communication capabilities, a machine type communication (MTC) device, a cellular Internet of Things (CIoT) device, or a land / sea / air vehicle (such as a car, a truck, a ship, an airplane, or a drone, or any combination of these or the like). The communication device 300 can provide, for example, data communication for carrying communications. The communication can be one or more of voice, email, text message, multimedia, data, machine data, etc.

[0177] The communication device 300 can receive signals via an air or radio interface 307 by appropriate means for reception, and can send signals by appropriate means for sending radio signals. In Figure 3 (the figure), the transceiver means is schematically designated by block 306. For example, the transceiver means 306 can be provided by a radio section and an associated antenna arrangement. The antenna arrangement can be disposed inside and / or outside the mobile device.

[0178] The communication device 300 can be equipped with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for software and hardware assisted execution of the tasks it is designed to perform, including controlling access to and communication with an access system and other communication devices. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 can be configured to execute appropriate software code 308. For example, the software code 308 can enable (or otherwise facilitate) the execution of any aspect described herein or various example embodiments of the present disclosure (including any part thereof). The software code 308 can be stored in the ROM 302a. The communication device 300 can include one or more circuits, or circuitry (not shown), which can be configured to execute any aspect described herein or various example embodiments of the present disclosure (including any part thereof).

[0179] The processor, storage device, and other associated control means can be provided on a suitable circuit board and / or chipset. This feature is denoted by the reference numeral 304.

[0180] A communication device 300 (e.g., a UE) may include a mobile device (ME) and a Universal Integrated Circuit Card (UICC) (not shown). The UICC may include one or more applications, such as a Universal Subscriber Identity Module (USIM). The USIM stores (e.g., securely) and processes sensitive data related to a subscriber and a home network (HN).

[0181] The communication device 300 may optionally have a user interface, such as a keyboard 305, a touch screen or a keyboard, a combination thereof, etc. Depending on the type of the device, one or more of a display, a speaker, and a microphone are optionally provided (e.g., equipped).

[0182] Figure 4 An example signaling and operation diagram between network functions associated with a device representation registration service according to some example embodiments of the present disclosure is shown.

[0183] In some example embodiments, there is communication between an AMF, an EIR, and Operations Management and Maintenance (OAM). The EIR may be referred to as an NF / First NF. The AMF may be referred to as another NF / Second NF. In other example embodiments, a Mobility Management Entity (MME) may replace the AMF. In other example embodiments, an NF or other network service may replace the OAM.

[0184] In S401, the AMF provides an indication of the PEI to the EIR. The indication may be a request for the device status of the PEI. For example, the AMF may provide to the EIR “GET… / equipment-status?pei={pei} (GET… / device-status?pei={pei})”. “GET… / equipment-status?pei={pei}” is a representation of an HTTP request of the method type GET (retrieve) including a URI of the target resource … / equipment-status?pei={pei}, although in some example embodiments, the first part of the URI has been replaced by ellipsis for clarity. The URI contains a query parameter (the part after “?”) and follows the format defined in RFC3986.

[0185] The EIR determines whether there is a record for the PEI that the EIR can access based on the PEI.

[0186] In S402a, when there is no record for the PEI, the EIR provides an indication that the PEI was not found to the AMF. For example, the EIR may provide to the AMF “404 Not found”.

[0187] At S402b, when there is a record for the PEI, the EIR accesses the record and determines the associated state (or device state) for the PEI. The EIR provides an indication of the state for the PEI to the AMF. In some example embodiments, the EIR provides an indication that the PEI is permitted. For example, the EIR provides to the AMF "OK EirResponseData(“WHITELISTED”)".

[0188] At S403, the EIR stores the information received from the AMF related to the PEI. The EIR may store the association between the AMF and the PEI. For example, the identity of the AMF (“AMF ID”) may be associated with the PEI and stored at a location accessible to the EIR.

[0189] At S404, the EIR receives an indication of the state for the PEI. The indication of the state for the PEI may be received from the OAM.

[0190] In some example embodiments, the received indication is that the device assigned the PEI has been blocked (e.g., prohibited from use). This may be because the communication device (which has the PEI) has been stolen. For example, the EIR receives “Block device(PEI={pei})”. In this context, it should be understood that “the PEI has been blocked” and “the device assigned the PEI has been blocked” have the same meaning.

[0191] In some example embodiments, the received indication of the state is that the communication device assigned to the PEI has been blocked (e.g., prohibited from use).

[0192] In some example embodiments, the received indication of the state is that the record of the communication device assigned to the PEI has been given a blocked state.

[0193] In example embodiments where the EIR has a record for the PEI (e.g., S402b), this received indication means that the state of the PEI has changed. The state for the PEI has changed from “permitted” to “prohibited”.

[0194] At S405, the EIR determines whether there is a stored association for the PEI that has been indicated as blocked. In this way, the EIR searches for the device-to-AMF association for the PEI.

[0195] At S406, the EIR provides an indication related to the state associated with the PEI to the AMF. The EIR may provide an indication for the AMF to deregister the subscriber for the PEI. For example, the EIR may provide to the AMF “POST DeregisterDevice({pei})”.

[0196] At S407, the AMF provides an acknowledgement of the indication (from S406) to the EIR. For example, the AMF may provide "204 No content" to the EIR.

[0197] This enables (or otherwise facilitates) the EIR to initiate a deregistration request for the correct AMF (e.g., the AMF currently associated with the PEI) without involving other core network entities such as the UDM and UDR.

[0198] Figure 5 Shows another example signaling and operation diagram between network functions associated with the device identity registration service according to some example embodiments of the present disclosure.

[0199] In some example embodiments, there is communication between the AMF, the EIR, and the OAM. The EIR may be referred to as the NF / First NF. The AMF may be referred to as the other NF / Second NF. In other example embodiments, the Mobility Management Entity (MME) may replace the AMF. In other example embodiments, an NF or other network service may replace the OAM.

[0200] At S501, the AMF provides an indication of the PEI to the EIR. The indication may be a request for the device status of the PEI. For example, the AMF may provide "GET… / equipment-status? pei={pei}" to the EIR.

[0201] The EIR determines whether there is a record of the PEI that the EIR can access based on the PEI.

[0202] At S502a, when there is no record of the PEI, the EIR provides an indication that the PEI was not found to the AMF. For example, the EIR may provide "404 Not found" to the AMF.

[0203] At S502b, when there is a record of the PEI, the EIR accesses the record and determines the association status (or device status) of the PEI. The EIR provides an indication of the status of the PEI to the AMF. In some example embodiments, the EIR provides an indication that the PEI is permitted. For example, the EIR may provide "OK EirResponseData ("WHITELISTED")" to the AMF.

[0204] In S503, the AMF provides an indication of the PEI to the EIR. The indication can be a subscription request for notifications of the PEI. For example, a subscription for notifications of any changes to the PEI, to the status (device status).

[0205] For example, the AMF provides to the EIR "POST… / equipment-status-subscriptionsEquipmentStatusSubscription(pei{pei})(POST… / device-status-subscriptionsDeviceStatusSubscription(pei{pei}))".

[0206] In S504, the EIR stores the information related to the PEI received from the AMF. For example, the EIR creates and stores a subscription for the AMF for changes to the status associated with the PEI. The creation of the subscription can be performed in response to receiving a subscription request from the AMF.

[0207] In S505, the EIR provides a confirmation of the indication (from S503) to the AMF. The confirmation can be interpreted by the AMF as a confirmation of the subscription for notifications of the PEI. For example, the EIR can provide to the AMF "204 No content".

[0208] In S506, the EIR receives an indication of the status of the PEI. The indication of the status of the PEI can be received from the OAM.

[0209] In some example embodiments, the received indication is that the device assigned the PEI has been blocked (e.g., prohibited from use). This can be because the communication device (PEI) has been stolen. For example, the EIR receives "Block device (PEI={pei})".

[0210] In some example embodiments, the received indication of the status is that the communication device assigned to the PEI has been blocked (e.g., prohibited from use).

[0211] In some example embodiments, the received indication of the status is that the record of the communication device assigned to the PEI has been given a blocked status.

[0212] In example embodiments where the EIR has a record of the PEI (e.g., S502b), the received indication means that the status of the PEI has changed. The status of the PEI has changed from "allowed" to "prohibited".

[0213] At S507, the EIR provides an indication related to the status associated with the PEI to the AMF. The EIR may provide a message / notification indicating the (current) status of the PEI. In some example embodiments, the status of the PEI has changed to prohibited. For example, the EIR may provide to the AMF "POST EquipmentStatusChangeNotif({pei}, "BLACKLISTED")".

[0214] At S508, the AMF provides an acknowledgement (of the message in S507) to the EIR. For example, the AMF may provide to the EIR "204 No content".

[0215] At Figure 5 in, the status of the PEI changes from "permitted" to "prohibited". When the EIR is updated with a record that marks the PEI (or the device assigned the PEI) as blocked or otherwise changes the status of the PEI (or the device assigned the PEI), if there is a subscription to notifications for the device, the EIR directly sends a notification to the AMF that has subscribed to notifications for that PEI.

[0216] In response to receiving an indication that the status is prohibited, the AMF may use the PEI sent in the notification to locate the device registration and initiate the deregistration of the device.

[0217] Therefore, this enables (or otherwise facilitates) the EIR to request the AMF to initiate a deregistration without involving other core network entities such as the UDM and UDR. This involves an additional request for a subscription notification from the AMF.

[0218] Figure 6 Shows another example signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure.

[0219] In some example embodiments, there is communication between the AMF, the EIR, and the OAM. The EIR may be referred to as the NF / First NF. The AMF may be referred to as another NF / Second NF. In other example embodiments, the Mobility Management Entity (MME) may replace the AMF. In other example embodiments, an NF or other network service may replace the OAM.

[0220] At S601, the AMF provides an indication of the PEI to the EIR. The indication may be a request for a notification for the PEI. For example, a subscription to notifications of any change in the status (device status) for the PEI.

[0221] The subscription request also includes an indication that the current state of the PEI is to be provided. For example, in a subscription request to the EIR, a parameter (such as the "immediateReport" parameter) can be marked as "TRUE".

[0222] For example, the AMF provides the EIR with "POST… / equipment-status-subscriptionsEquipmentStatusSubscription(pei{pei},immediateReport{true})(POST… / device-status-subscriptionsDeviceStatusSubscription(pei{pei}, immediateReport{true}))".

[0223] In S602, the EIR stores the information related to the PEI received from the AMF. For example, the EIR creates and stores a subscription for the AMF for changes in the status associated with the PEI. The creation of the subscription can be performed in response to receiving a subscription request from the AMF.

[0224] When the indication received from the AMF (in S601) includes an indication of the current state of the PEI, the EIR determines whether there is a record of the PEI.

[0225] In S603a, when there is a record for the PEI accessible to the EIR, the EIR provides the AMF with an indication of the status of the PEI. For example, when the PEI record is "PERMITTED", the EIR provides the AMF with "200 OK EirResponseData(immediateReport{"WHITELISTED"})(200 OK Eir response data(immediateReport{"WHITELISTED"}))".

[0226] In S603b, when there is no record for the PEI accessible to the EIR, the EIR provides the AMF with an indication that the status of the PEI is unknown. For example, the EIR provides the AMF with "200 OK EirResponseData(immediateReport{"UNKNOWN"})(200 OK Eir response data(immediateReport{"UNKNOWN"}))".

[0227] In S604, the EIR receives an indication of the status of the PEI. The indication of the status of the PEI can be received from the OAM.

[0228] In some example embodiments, the received indication is that the device assigned the PEI has been blocked (e.g., prohibited from use). This can be because the communication device (with the assigned PEI) has been stolen. For example, the EIR receives "Block device (PEI = {pei})".

[0229] In some example embodiments, the received indication of the status is that the communication device assigned to the PEI has been blocked (e.g., prohibited from use).

[0230] In some example embodiments, the received indication of the status is that the record of the communication device assigned to the PEI has been given a blocked status.

[0231] In an example embodiment where the EIR has a record for the PEI (e.g., S603b), this received indication means that the status for the PEI has changed. The status of the PEI has changed from "allowed" to "prohibited".

[0232] In S605, the EIR provides an indication related to the status associated with the PEI to the AMF. The EIR can provide a message / notification indicating the (current) status of the PEI. In some example embodiments, the status of the PEI has changed to prohibited. For example, the EIR can provide "POST EquipmentStatusChangeNotif({pei}, "BLACKLISTED")" to the AMF.

[0233] In S606, the AMF provides an acknowledgement (of the message in S605) to the EIR. For example, the AMF can provide "204 No content" to the EIR.

[0234] In Figure 6 When the status of the PEI changes from "allowed" to "prohibited", when the EIR is updated with a record that marks the PEI (or the device assigned the PEI) as blocked or otherwise changes the status of the PEI (or the device assigned the PEI), if there is a subscription to notifications for the device, the EIR (e.g., directly) sends a notification to the AMF that has subscribed to notifications for that PEI.

[0235] In response to receiving an indication that the status is prohibited, the AMF can use the PEI sent in the notification to locate the device registration and initiate the deregistration of the device.

[0236] This enables (or otherwise facilitates) the EIR to request the AMF to initiate a deregistration without involving other core network entities such as the UDM and UDR.

[0237] Figures 4 to 6 Example embodiments relate to storing data / information. There are several example options for EIR storage of the association between PEI and AMF ID, including: using an internal data store located within the EIR itself, using an external entity such as an Unstructured Data Store Function (UDSF). The implementation of such EIR storage may be at the discretion of the network operator.

[0238] Figure 7 Another example signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure is shown.

[0239] In some example embodiments, there is communication between the AMF and the EIR. The EIR may be referred to as NF / first NF. The AMF may be referred to as another NF / second NF. In other example embodiments, a mobility management entity (MME) may replace the AMF.

[0240] At S701, the AMF provides an indication of the PEI to the EIR. The indication may be a request for the equipment status for the PEI. For example, the AMF may provide "GET ... / equipment-status?pei={pei}" to the EIR.

[0241] The EIR determines, based on the PEI, whether there are records of the PEI to which the EIR has access.

[0242] At S702a, when there is no record for PEI, the EIR provides an indication to the AMF that the PEI is not found. For example, the EIR may provide a "404 Not found" to the AMF.

[0243] At S702b, when there is a record of PEI, the EIR accesses the record and determines the associated state (or device state) of the PEI. The EIR provides an indication of the state for the PEI to the AMF. In some example embodiments, the EIR provides an indication that the PEI is allowed. For example, the EIR may provide "OK EirResponseData("WHITELISTED") to the AMF.

[0244] At S703, the EIR stores the information related to the PEI received from the AMF. The EIR may store the association between the AMF and the PEI. For example, the AMF identifier (AMF ID) may be associated with the PEI and stored in a location accessible to the EIR.

[0245] At S704, the subscriber associated with the PEI deregisters from the network (eg, deregisters from the AMF). The AMF manages the deregistration of the subscriber.

[0246] At S705, the AMF provides a request to the EIR to delete the association between the AMF and the PEI. For example, the AMF provides to the EIR "DELETE… / equipment-status-associations / {pei} (DELETE (delete)… / device-status-associations / {pei})".

[0247] At S706, the EIR removes (or deletes) the association between the AMF and the PEI.

[0248] At S707, the EIR provides a confirmation to the AMF. The confirmation can indicate to the AMF that the association has been deleted.

[0249] Figure 8 Another example signaling and operation diagram between network functions associated with the device identity registration service according to some example embodiments of the present disclosure is shown.

[0250] In some example embodiments, there is communication between the AMF and the EIR. The EIR can be referred to as the NF / First NF. The AMF can be referred to as the other NF / Second NF. In other example embodiments, the Mobility Management Entity (MME) can replace the AMF.

[0251] At S801, the AMF provides an indication of the PEI to the EIR. The indication can be a subscription request for notifications for the PEI. For example, a subscription for notifications of any change in the status (device status) of the PEI.

[0252] The subscription request also includes an indication of the current status of the PEI to be provided. A parameter (such as the "immediateReport" parameter) in the subscription request to the EIR can be marked as "TRUE".

[0253] For example, the AMF provides to the EIR "POST… / equipment-status-subscriptionsEquipmentStatusSubscription(pei{pei},immediateReport{true}) (POST… / device-status-subscriptionsDeviceStatusSubscription(pei{pei}, immediateReport{true}))".

[0254] At S802, the EIR stores the information received from the AMF related to the PEI. For example, the EIR creates and stores a subscription for the AMF for changes in the status associated with the PEI. The creation of the subscription can be performed in response to receiving the subscription request from the AMF.

[0255] When the indication received from the AMF (at S801) includes an indication of the current state of the PEI, the EIR determines whether there is a record for the PEI.

[0256] At S803a, when there is a record for the PEI accessible to the EIR, the EIR provides an indication of the status for the PEI to the AMF. For example, when the PEI record is "Allowed", the EIR provides the AMF with "200OK EirResponseData(immediateReport{“WHITELISTED”})(200OK Eir response data (immediate report {"WHITELISTED"}))".

[0257] At S803b, when there is no record for the PEI accessible to the EIR, the EIR provides an indication that the status for the PEI is unknown to the AMF. For example, the EIR provides the AMF with "200OK EirResponseData(immediateReport{“UNKNOWN”})(200OK Eir response data (immediate report {"UNKNOWN"}))".

[0258] At S804, the subscriber associated with the PEI logs off from the network (e.g., logs off from the AMF). The AMF manages the logoff of the subscriber.

[0259] At S805, the AMF provides the EIR with a request to delete the subscription for notifications regarding the PEI for the AMF. The request may include an identifier of the subscription. In some example embodiments, the subscription has an identity (subscription ID). For example, the AMF may provide the EIR with "DELETE… / equipment-status-subscriptions / {subscriptionID}(DELETE… / device-status-subscriptions / {subscriptionId})".

[0260] At S806, the EIR removes (or deletes) the subscription for the AMF.

[0261] At S807, the EIR provides the AMF with an acknowledgement. The acknowledgement may indicate to the AMF that the subscription has been deleted.

[0262] Figure 9 Another example signaling and operation diagram between network functions associated with an equipment identity registration service according to some example embodiments of the present disclosure is shown.

[0263] In some example embodiments, there is communication between an AMF (“AMF1”), another AMF (“AMF2”), and an EIR. The EIR may be referred to as an NF / first NF. AMF1 may be referred to as another NF / second NF. AMF2 may be referred to as a third NF. In other example embodiments, a Mobility Management Entity (MME) may replace AMF1 or AMF2.

[0264] In S901, the AMF provides an indication of the PEI to the EIR. The indication may be a request for the device status for the PEI. For example, AMF1 may provide to the EIR “GET… / equipment-status?pei={pei} (GET… / device-status?pei={pei})”.

[0265] The EIR determines whether there is a record of the PEI that the EIR can access based on the PEI.

[0266] In S902a, when there is no record of the PEI, the EIR provides an indication to AMF1 that the PEI was not found. For example, the EIR may provide to the AMF “404 Not found (404 not found)”.

[0267] In S902b, when there is a record of the PEI, the EIR accesses the record and determines the associated status (or device status) for the PEI. The EIR provides an indication of the status for the PEI to AMF1. In some example embodiments, the EIR provides an indication that the PEI is permitted. For example, the EIR may provide to AMF1 “OK EirResponseData(“WHITELISTED”) (OK Eir response data (“whitelisted”))”.

[0268] In S903, the EIR stores the information related to the PEI received from AMF1. The EIR may store the association between AMF1 and the PEI. For example, the identifier of AMF1 (AMF ID) may be associated with the PEI and stored in a location accessible to the EIR.

[0269] In S904, the subscriber associated with the PEI registers with a new AMF (i.e., AMF2). In this way, the subscriber associated with the PEI moves from AMF1 to AMF2.

[0270] In S905, AMF2 provides an indication of the PEI to the EIR. The indication may be a request for the device status for the PEI. For example, AMF2 may provide to the EIR “GET… / equipment-status?pei={pei} (GET… / device-status?pei={pei})”.

[0271] At S906, the EIR stores the association between AMF2 and the PEI. The EIR deletes the association between AMF1 and the PEI. In this way, receiving the PEI from AMF2 causes the EIR to replace the stored association between AMF1 and the PEI with the "updated" association between AMF2 and the PEI.

[0272] At S907, the EIR provides an indication of the status of the PEI to AMF2. In some example embodiments, the EIR provides an indication that the PEI is permitted. For example, the EIR may provide "OK EirResponseData(“WHITELISTED”) " to AMF2.

[0273] Figure 10 Another example signaling and operation diagram between network functions associated with an equipment identity registration service according to some example embodiments of the present disclosure is shown.

[0274] In some example embodiments, there is communication between an AMF (AMF1), another AMF (AMF2), and the EIR. The EIR may be referred to as an NF / first NF. AMF1 may be referred to as another NF / second NF. AMF2 may be referred to as a third NF. In other example embodiments, a mobility management entity (MME) may replace AMF1 / AMF2.

[0275] At S1001, AMF1 provides an indication of the PEI to the EIR. The indication may be a subscription request for a notification regarding the PEI. For example, a subscription for any change in the status (such as device status) of the PEI.

[0276] The subscription request also includes an indication that the current status of the PEI is to be provided. For example, a parameter (such as an "immediateReport" parameter) in the subscription request to the EIR may be marked as "TRUE".

[0277] For example, AMF1 provides the EIR with "POST… / equipment-status-subscriptionsEquipmentStatusSubscription(pei{pei},immediateReport{true}) (POST… / device-status-subscriptionsDeviceStatusSubscription(pei{pei}, immediateReport{true}))".

[0278] At S1002, the EIR stores the information received from AMF1 regarding the PEI. For example, the EIR creates and stores a subscription for AMF1 for changes in the status associated with the PEI. The creation of the subscription may be performed in response to receiving the subscription request from AMF1.

[0279] When the indication received from AMF1 (at S1001) includes an indication of the current state of the PEI, the EIR determines whether there is a record for the PEI.

[0280] At S1003a, when there is a record for the PEI accessible to the EIR, the EIR provides an indication of the status of the PEI to AMF1. For example, when the PEI record is “PERMITTED”, the EIR provides “200OK EirResponseData(immediateReport{“WHITELISTED”})(200OK Eir response data (immediate report {“WHITELISTED”}))” to AMF1.

[0281] At S1003b, when there is no record of the PEI accessible to the EIR, the EIR provides an indication that the status of the PEI is unknown. For example, the EIR provides “200OK EirResponseData(immediateReport{“UNKNOWN”})(200OK Eir response data (immediate report {“UNKNOWN”}))” to AMF1.

[0282] At S1004, the subscriber associated with the PEI registers with the new AMF, i.e., AMF2. In this way, the subscriber associated with the PEI moves from AMF1 to AMF2.

[0283] At S1005, AMF2 provides an indication of the PEI to the EIR. The indication can be a subscription request for notifications of the PEI. For example, a subscription for notifications of any change in the status (device status) of the PEI.

[0284] The subscription request also includes an indication that the current state of the PEI is to be provided. For example, in the subscription request to the EIR, a parameter (such as the “immediateReport” parameter) can be marked as “TRUE”.

[0285] For example, AMF2 provides “POST… / equipment-status-subscriptionsEquipmentStatusSubscription(pei{pei},immediateReport{true})(POST… / device-status-subscriptionsDeviceStatusSubscription(pei{pei}, immediate report {true}))” to the EIR.

[0286] In S1006, the EIR creates and stores a subscription for the AMF2 for notifications regarding the status of the PEI. The EIR deletes the subscription for the AMF1 for notifications regarding the status of the PEI. In other example embodiments, the EIR updates (or changes) the subscription such that the AMF1 is updated to the AMF2 for notifications related to the status of the PEI.

[0287] In this way, the receipt of the subscription request from the AMF2 causes the EIR to replace the subscription for the AMF1 with an “updated” subscription for the AMF2.

[0288] In S1007, the EIR provides an indication of the status of the PEI to the AMF2. For example, when the PEI is recorded as “allowed”, the EIR provides “200OK EirResponseData(immediateReport{“WHITELISTED”})(200OK Eir response data (immediate report {“whitelisted”}))” to the AMF2.

[0289] Figure 11 An example signaling and operation diagram between network functions associated with a device identity registration service according to some example embodiments of the present disclosure is shown.

[0290] In some example embodiments, there is communication between the AMF, the EIR, and the Operations, Administration, and Maintenance (OAM). The EIR may be referred to as the NF / First NF. The AMF may be referred to as the other NF / Second NF. In other example embodiments, the Mobility Management Entity (MME) may replace the AMF. In other example embodiments, an NF or other network service may replace the OAM.

[0291] In S1101, the AMF provides an indication of the PEI to the EIR. The indication may be a request for the device status for the PEI. For example, the AMF may provide “GET… / equipment-status?pei={pei}(GET… / device-status?pei={pei})” to the EIR.

[0292] The EIR determines whether there is a record of the PEI that the EIR can access based on the PEI.

[0293] In S1102, when there is a record of the PEI, the EIR accesses the record and determines the associated status (or device status) for the PEI. The EIR provides an indication of the status of the PEI to the AMF. In some example embodiments, the EIR provides an indication that the PEI is allowed. For example, the EIR provides “OK EirResponseData(“WHITELISTED”)(OK Eir response data (“whitelisted”))” to the AMF.

[0294] At S1103, the EIR stores information related to the PEI received from the AMF. The EIR may store the association between the AMF and the PEI. For example, the identifier of the AMF ("AMF ID") may be associated with the PEI and stored at a location accessible to the EIR.

[0295] At S1104, the EIR receives a request from the OAM to remove the record of the PEI.

[0296] At S1105, the EIR provides an indication to the AMF that the record for the PEI has been deleted in the EIR.

[0297] At S1106, the EIR deletes the record for the PEI. The EIR maintains the association between the AMF and the PEI. In other words, the association between the AMF and the PEI is maintained in the storage device (after the record of the PEI has been deleted).

[0298] At S1107, the AMF provides an acknowledgement of the message received in S1105 to the EIR.

[0299] Figure 12 Another example signaling and operation diagram is shown among network functions associated with the device identity registration service according to some example embodiments of the present disclosure.

[0300] In some example embodiments, there is communication between the AMF, the EIR, and the OAM. The EIR may be referred to as the NF / First NF. The AMF may be referred to as another NF / Second NF. In other example embodiments, a Mobility Management Entity (MME) may replace the AMF. In other example embodiments, an NF or other network service may replace the OAM.

[0301] At S1201, the AMF provides an indication of the PEI to the EIR. The indication may be a subscription request for notifications of the PEI. For example, a subscription for notifications of any change in the status (device status) of the PEI.

[0302] The subscription request further includes an indication that the current status of the PEI is to be provided. For example, a parameter (such as the "immediateReport" parameter) in the subscription request to the EIR may be marked as "TRUE".

[0303] For example, the AMF provides to the EIR "POST… / equipment-status-subscriptionsEquipmentStatusSubscription(pei{pei},immediateReport{true})(POST… / device-status-subscriptionsDeviceStatusSubscription(pei{pei}, immediateReport{true}))".

[0304] At S1202, the EIR stores information related to the PEI received from the AMF. For example, the EIR creates and stores a subscription for the AMF for changes in the status associated with the PEI. The creation of the subscription can be performed in response to receiving a subscription request from the AMF.

[0305] When the indication received from the AMF (at S1201) includes an indication of the current status of the PEI, the EIR determines whether there is a record of the PEI.

[0306] At S1203a, when there is a record for the PEI accessible to the EIR, the EIR provides an indication of the status of the PEI to the AMF. The status of the PEI is stored as part of the record of the PEI. For example, when the PEI record is "allowed", the EIR provides the AMF with "200OK EirResponseData(immediateReport{“WHITELISTED”})(200OK Eir response data (immediate report {"WHITELISTED"}))".

[0307] At S1204, the EIR receives a request from the OAM to remove the record of the PEI.

[0308] The EIR deletes the record of the PEI.

[0309] At S1205, the EIR provides an indication related to the status associated with the PEI to the AMF. The EIR can provide a message / notification indicating the (current) status of the PEI. In some example embodiments, the record of the PEI has been deleted in the EIR. In this way, the status of the PEI is no longer known. For example, the EIR can provide the AMF with "POSTEquipmentStatusChangeNotif({pei},“UNKNOWN”)(POST device status change notification ({pei}, “unknown”))" or "POST EquipmentStatusChangeNotif({pei},“STATUS_DELETED”)(POST device status change notification ({pei}, “status_deleted”)".

[0310] At S1206, the EIR maintains a subscription for the AMF for notifications related to the status of the PEI. In other words, the subscription is maintained in the storage device (even if the record of the PEI has been deleted).

[0311] At S1207, the AMF provides an acknowledgement of the message received at S1205 to the EIR.

[0312] As Figures 9 to 12As shown, information related to the PEI (e.g., association or subscription) can be stored in the EIR and will continue to be stored even if the record has been deleted. In some example embodiments, the association or subscription stored in the EIR can utilize an expiration time (or timer) that enables the EIR to (or otherwise facilitates) remove an “expired” subscription. For example, each association or subscription has a timer, and when the timer expires, the association or subscription is deleted. Similar mechanisms are also used elsewhere in the 5GC to remove subscriptions to notifications.

[0313] It should be understood that in Figures 4 to 12 , in some other example embodiments, one or more of the described features can be removed or performed in a different order.

[0314] One or more of the example embodiments described above have the advantage that after a communication device (with an associated PEI) is marked as blocked, the communication device has a shorter duration of access to the network. For example, after the communication device has been marked as stolen. One or more of the example embodiments have the advantage that the EIR can determine the AMF associated with blocking / barring the communication device and provide an indication or notification of the updated status to the AMF (e.g., directly). The EIR can determine the associated AMF without communicating with the UDM / UDR. Utilizing both the UDM / UDR increases the time to determine the AMF associated with the communication device and uses more resources. Therefore. One or more of the example embodiments provide an enhanced (e.g., faster and more resource-efficient) way to notify the AMF of a blocked / barred device. The AMF can then take appropriate measures to remove access to the network for the blocked / barred device.

[0315] Figure 13 An example method flow performed by a device according to some example embodiments of the present disclosure is shown. The device can be for a network function. The device can provide a network function. The network function can be included in the device. The device can be a network function. In some example embodiments, the network function is an EIR.

[0316] In S1301, the method includes receiving an indication of a permanent device identifier from a second network function.

[0317] In S1303, the method includes storing information associated with the indication of the permanent device identifier received from the second network function.

[0318] In S1305, the method includes receiving an indication of a status associated with the permanent device identifier.

[0319] In S1307, the method includes providing, based on the information, an indication related to the status associated with the permanent device identifier to the second network function.

[0320] Figure 14 An example method flow executed by a device according to some example embodiments of the present disclosure is shown. The device may be for a second network function. The device may provide the second network function. The second network function may be included in the device. The device may be the second network function. In some example embodiments, the second network function is an AMF or an MME.

[0321] In S1401, the method includes providing an indication of a permanent device identifier to a network function.

[0322] In S1403, the method includes receiving from the network function an indication related to a status associated with the permanent device identifier.

[0323] Figure 15 A schematic diagram of non-volatile storage media 1500a (such as a Blu-ray Disc (BD), a computer disc (CD), or a Digital Versatile Disc (DVD)) and 1500b (such as a flash memory, a solid-state memory, a Universal Serial Bus (USB) memory stick) storing instructions and / or parameters 1502 is shown. The instructions and / or parameters 1502, when executed by a processor, allow the processor to execute Figures 13 to 14 one or more methods (or portions thereof).

[0324] It should be noted that although various example embodiments are described herein, various changes and modifications can be made to the disclosed solutions without departing from the scope of the present disclosure. For example, it should be understood that further example embodiments can be provided by any combination of two or more of the various example embodiments described herein.

[0325] Generally, some example embodiments can be implemented in hardware or a dedicated circuit, software, logic, or any combination thereof. For example, some aspects of the various example embodiments can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, a microprocessor, or other computing devices, but the embodiments are not limited thereto. Although the various example embodiments can be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, a dedicated circuit or logic, general hardware or a controller or other computing devices, or some combination thereof, as non-limiting and illustrative examples.

[0326] Example embodiments can be implemented by computer software stored in a memory and executable by at least one data processor of the entity involved, or by hardware, or by a combination of software and hardware. In this regard, it should be noted that any process can be represented by program steps, or interconnected logic circuits, blocks, and functions, or a combination of program steps and logic circuits, blocks, and functions. The software can be stored on a physical medium such as a memory chip or a memory block implemented within a processor, a magnetic medium such as a hard disk or a floppy disk, and an optical medium such as a DVD and its data variant CD.

[0327] As used herein, the term "non-transitory" is a limitation on the medium itself (e.g., tangible, rather than a signal), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0328] As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar phrasings, where the list of two or more elements is joined by "and" or "or", represent any and all combinations of the listed terms, including at least any one element, or at least any two or more elements, or at least all elements. As used herein, the expression "and / or" means any and all combinations of the listed terms, including any one element, or any two or more elements, or at least all elements.

[0329] As used herein, unless explicitly stated to the contrary, performing a step or function "in response to A" does not mean that the step or function is performed immediately after A occurs, as one or more intermediate steps may be included therebetween. Similarly, performing a step or function "based on A" does not mean that the step or function is performed only based on A, as the step or function may also be based on one or more additional conditions (e.g., "B") other than A. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and can include, as non-limiting examples, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a gate-level circuit, and a processor based on a multi-core processor architecture.

[0330] As used herein, the term "component for..." or "component configured to perform..." (or similar terms) can be any component suitable for performing that feature. A "component" can be configured to perform one or more of the functions and / or method steps described previously. For example, a "component" can include one or more of the following: at least one processor, at least one memory, transceiver circuitry, antenna circuitry, etc. It should be understood that these are provided as non-limiting examples.

[0331] Additionally or alternatively, some examples can be implemented using circuitry. The circuitry can be configured to perform one or more of the functions and / or method steps described previously. The circuitry can be provided in a base station and / or a communication device.

[0332] As used herein, the term "circuitry" can refer to one or more or all of the following example embodiments:

[0333] (a) A pure hardware circuit implementation (e.g., an implementation only in analog and / or digital circuitry);

[0334] (b) A combination of hardware circuitry and software, such as:

[0335] (i) A combination of analog and / or digital hardware circuitry and software / firmware, and

[0336] (ii) Any portion of a hardware processor (including a digital signal processor), software, and memory with the software that work together to cause a device such as a communication device or a base station to perform the various functions described previously; and

[0337] (c) Hardware circuitry and / or a processor that requires software (e.g., firmware) for operation, such as a microprocessor or a portion of a microprocessor, but the software may be absent when not required for operation.

[0338] This definition of circuitry applies to the use of the term "component" herein, including in any claim. As another example, as used herein, the term circuitry also encompasses an implementation of only hardware circuitry or a processor (or processors) or a portion of a hardware circuitry or a processor and its (or their) attendant software and / or firmware. The term circuitry also encompasses, for example, an integrated device. The term circuitry also encompasses, for example, if applicable to a particular claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0339] The foregoing description has provided a complete and informative description of various example embodiments of the present disclosure by way of illustrative and non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the foregoing description when read in conjunction with the accompanying drawings and the claims. Nevertheless, all such and similar modifications to the teachings will still fall within the scope defined in the present disclosure.

Claims

1. An apparatus, the apparatus comprising components for the following operations: Receiving an indication of a permanent device identifier from a second network function; Storing information associated with the indication of the permanent device identifier received from the second network function; Receiving an indication of a state associated with the permanent device identifier; And Based on the information, providing an indication related to the state associated with the permanent device identifier to the second network function.

2. The device according to claim 1, wherein The indication of the state associated with the permanent device identifier is an indication that the state has changed to an indication of a state in which the permanent device identifier is prohibited.

3. The device according to claim 1, wherein, The components are further configured to: Based on the received indication of the state, generate or update a record associated with the permanent device identifier, and the record for the permanent device identifier includes the state of the permanent device identifier.

4. The apparatus according to any one of claims 1 to 3, wherein Storing the information includes: Based on the indication of the permanent device identifier, storing an association between the second network function and the permanent device identifier, wherein the indication provided to the second network function and related to the state associated with the permanent device identifier is based on the association.

5. An apparatus, the apparatus comprising components for the following operations: Providing an indication of a permanent device identifier to a network function; and Receiving an indication related to a state associated with the permanent device identifier from the network function.

6. The device according to claim 5, wherein The indication received from the network function and related to the state associated with the permanent device identifier includes: a request for the second network function to deregister a subscriber associated with the permanent device identifier.

7. The apparatus according to claim 5 or 6, wherein The indication received from the network function and related to the state associated with the permanent device identifier includes: An indication that the state associated with the permanent device identifier has changed, and an indication of the state associated with the permanent device identifier.

8. A method, the method comprising: Receiving an indication of a permanent device identifier from a second network function; Storing information associated with the indication of the permanent device identifier received from the second network function; Receiving an indication of a state associated with the permanent device identifier; And Based on the information, providing an indication related to the state associated with the permanent device identifier to the second network function.

9. A method, the method comprising: Providing an indication of a permanent device identifier to a network function; And Receiving an indication related to a state associated with the permanent device identifier from the network function.

10. A computer program comprising instructions that, when executed by a device, cause the device to perform at least the following operations: Receiving an indication of a permanent device identifier from a second network function; Storing information associated with the indication of the permanent device identifier received from the second network function; Receiving an indication of a state associated with the permanent device identifier; And Based on the information, providing an indication related to the state associated with the permanent device identifier to the second network function.

11. A computer program comprising instructions which, when executed by a device, cause the device to perform at least the following operations: Provide an indication of a permanent device identifier to a network function; and Receive from the network function an indication related to a status associated with the permanent device identifier.

Images