WO2022214504A1 - Procédé et appareil pour la traduction d'un identifiant - Google Patents

Procédé et appareil pour la traduction d'un identifiant Download PDF

Info

Publication number
WO2022214504A1
WO2022214504A1 PCT/EP2022/059039 EP2022059039W WO2022214504A1 WO 2022214504 A1 WO2022214504 A1 WO 2022214504A1 EP 2022059039 W EP2022059039 W EP 2022059039W WO 2022214504 A1 WO2022214504 A1 WO 2022214504A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
type
gpsi
requested
translation
Prior art date
Application number
PCT/EP2022/059039
Other languages
English (en)
Inventor
Hongxia LONG
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022214504A1 publication Critical patent/WO2022214504A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for identifier translation.
  • a user or a subscriber or a device may be configured with at least one identifier.
  • a user or a subscriber or a device may be configured with different identifiers.
  • the identifier may be used in various services.
  • the identifier may be used in application triggering service, MSISDN (mobile subscriber integrated services digital network number)-less MO (Mobile Originated) SMS (short message service) service, and a service for setting a policy for a future AF (application function) session.
  • MSISDN mobile subscriber integrated services digital network number
  • MO Mobile Originated
  • SMS short message service
  • the identifier may be used in device triggering service.
  • 3GPP TS 23.502 V17.0.0 defined below use cases (UC) for NEF (network exposure function) as service consumer of Nudm id-translation-result service.
  • UC network exposure function
  • UC 1 as described in step 4 of Figure 4.13.2.2-1 of 3GPP TS 23.502 V17.0.0, the NEF invokes Nudm_SDM_Get (Identifier Translation, GPSI and AF Identifier) to resolve the GPSI to SUPI when the AF is authorized to trigger the UE (user equipment).
  • GPSI denotes generic public subscription identifier.
  • AF denotes application function.
  • SUPI denotes Subscription Permanent Identifier.
  • mapping from GPSI (External Id) to GPSI (MSISDN) is also provided for legacy SMS infrastructure not supporting MSISDN-less SMS.
  • Id or ID denotes identifier.
  • UC 2 as described in step 3 of Figure 4.13.7.2-1 of 3GPP TS 23.502 V17.0.0, the NEF invokes Nudm_SDM_Get (Identifier Translation, IMSI, Application Port ID, AF Identifier) to resolve the IMSI and Application Port ID to a GPSI (External Id).
  • IMSI denotes International Mobile Subscriber Identity.
  • UC 3 as described in step 3 of Figure 4.15.6.8-1 of 3GPP TS 23.502 V17.0.0, the NEF invokes Nudm_SDM_Get (Identifier Translation, GPSI) to resolve the GPSI (External Identifier) to a SUPI.
  • Nudm_SDM_Get Identifier Translation, GPSI
  • Flowever current id-translation service (such as Nudm id-translation service) doesn’t define AF identifier (for example required in UC 1 and UC 2) as input query parameter for authorization.
  • the current id-translation service also doesn’t define the requested identifier type (such as a specific GPSI type), for example, an additional GPSI type for UC1, a requested GPSI type in UC2. So some relevant use cases can’t be fulfilled.
  • the embodiments of the present disclosure propose an improved solution for identifier translation.
  • a method performed by a network function.
  • the method comprises sending an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier to a data management entity.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • the method further comprises receiving an identifier translation response from the data management entity.
  • AF application function
  • the AF identifier indicates authorization based on AF identifier is required on the data management entity.
  • the requested identifier type indicates an identifier belonging to the requested identifier type is required.
  • the identifier translation response comprises a failure result.
  • the identifier translation response comprises the second identifier.
  • the identifier translation response further comprises an identifier belonging to the requested identifier type.
  • the second identifier belongs to the requested identifier type.
  • the first identifier belongs to a first generic public subscription identifier (GPSI) type.
  • the second identifier comprises a subscription permanent identifier (SUPI) or an international mobile subscriber identity (IMSI).
  • the requested identifier type comprises a second GPSI type.
  • the first identifier comprises a SUPI or IMSI.
  • the second identifier comprises a GPSI.
  • the requested identifier type comprises a specific GPSI type.
  • a GPSI type comprises at least one of a mobile subscriber integrated services digital network number (MSISDN) type or an external identity type.
  • MSISDN mobile subscriber integrated services digital network number
  • the data management entity comprises at least one of a unified data management (UDM), a home subscriber server (HSS), or a home location register (HLR).
  • the network function comprises at least one of Service Capability Exposure Function (SCEF), Network Exposure Function (NEF), SCEF combined with NEF.
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • the identifier translation request comprises a Nudm_SDM_Get request or a subscriber information request and the identifier translation response comprises Nudm_SDM_Get response or a subscriber information response.
  • a method performed by a data management entity.
  • the method comprises receiving an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier from a network function.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • the method further comprises sending an identifier translation response to the network function.
  • the method further comprises performing authorization based on the AF identifier.
  • a network function comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said network function is operative to send an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier to a data management entity.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type. Said network function is further operative to receive an identifier translation response from the data management entity.
  • AF application function
  • a data management entity comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said data management entity is operative to receive an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier from a network function.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type. Said data management entity is further operative to send an identifier translation response to the network function.
  • AF application function
  • a network function comprises a sending module and a receiving module.
  • the sending module may be configured to send an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier to a data management entity.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • the receiving module may be configured to receive an identifier translation response from the data management entity.
  • a data management entity comprises a receiving module and a sending module.
  • the receiving module may be configured to receive an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier from a network function.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • the sending module may be configured to send an identifier translation response to the network function.
  • the data management entity may further comprise a authorization module configured to perform authorization based on the AF identifier.
  • a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first and second aspects.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first and second aspects.
  • Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows.
  • the proposed solution can enable the data management entity to perform authorization based on AF identifier.
  • the proposed solution can enable the requested-identifier-type as optional query parameter to indicate the required specific identifier type.
  • the proposed solution can fulfil more use cases.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG.1 schematically shows a high level architecture in the fifth generation network according to an embodiment of the present disclosure
  • FIG.2 schematically shows system architecture in a 4G network according to an embodiment of the present disclosure
  • FIG.3 shows non-roaming architecture for Network Exposure Function in reference point representation
  • FIG.4 shows non-roaming Service Exposure Architecture for EPC-5GC Interworking
  • FIG.5 shows a flowchart of a device triggering procedure via Nnef
  • FIG.6 shows a flowchart of a procedure of MSISDN-less MO SMS Service
  • FIG.7 shows a flowchart of setting a policy for a future AF session
  • FIG.8 shows a flowchart of device triggering procedure over Tsp
  • FIG.9 shows a flowchart of identifier translation
  • FIG.10 shows a flowchart of a method according to an embodiment of the present disclosure
  • FIG.11 shows a flowchart of a method according to another embodiment of the present disclosure.
  • FIG.12 shows a flowchart of GPSI to SUPI translation according to an embodiment of the present disclosure
  • FIG.13 shows a flowchart of SUPI to GPSI translation according to an embodiment of the present disclosure
  • FIG.14 shows a use case of GPSI to SUPI translation according to another embodiment of the present disclosure
  • FIG.15 shows a use case of SUPI to GPSI translation according to another embodiment of the present disclosure
  • FIG.16 shows a use case of GPSI to SUPI translation according to another embodiment of the present disclosure
  • FIG.17 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • FIG.18 is a block diagram showing a network function according to an embodiment of the disclosure.
  • FIG.19 is a block diagram showing a data management entity according to an embodiment of the disclosure.
  • the term “network” refers to a network following any suitable communication standards such as new radio (NR), long term evolution (LTE), LTE-Advanced, wideband code division multiple access (WCDMA), high-speed packet access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Address (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single carrier frequency division multiple access (SC-FDMA) and other wireless networks.
  • NR new radio
  • LTE long term evolution
  • WCDMA wideband code division multiple access
  • HSPA high-speed packet access
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Address
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA Single carrier frequency division multiple access
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), etc.
  • UTRA includes WCDMA and other variants of CDMA.
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • WiMAX IEEE 802.16
  • Flash-OFDMA Ad-hoc network
  • wireless sensor network etc.
  • the terms “network” and “system” can be used interchangeably.
  • the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP.
  • the communication protocols may comprise the first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • network device or “network node” refers to any suitable network function (NF) which can be implemented in a network entity (physical or virtual) of a communication network.
  • NF network function
  • the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.
  • the 5G system may comprise a plurality of NFs such as AMF (Access and mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User plane Function) and NRF (Network Repository Function), RAN (radio access network), SCP (service communication proxy), NWDAF (network data analytics function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice-Specific Authentication and Authorization Function), etc.
  • AMF Access and mobility Function
  • SMF Session Management Function
  • AUSF Authentication Service Function
  • UDM Unified Data Management
  • PCF Policy Control Function
  • AF Application Function
  • NEF Network Exposure Function
  • UPF User plane Function
  • NRF Network Repository Function
  • RAN radio access network
  • SCP service communication proxy
  • NWDAF network data analytics function
  • NSSF Network Slice Selection Function
  • the 4G system may include MME (Mobile Management Entity), HSS (home subscriber server), Policy and Charging Rules Function (PCRF), Packet Data Network Gateway (PGW), PGW control plane (PGW-C), Serving gateway (SGW), SGW control plane (SGW-C), E-UTRAN Node B (eNB), etc.
  • the network function may comprise different types of NFs for example depending on a specific network.
  • terminal device refers to any end device that can access a communication network and receive services therefrom.
  • the terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices.
  • the UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT).
  • the terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like.
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited
  • a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP (3rd Generation Partnership Project), such as 3GPP’ LTE standard or NR standard.
  • 3GPP 3rd Generation Partnership Project
  • a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and/or operates the relevant device.
  • a terminal device may be configured to transmit and/or receive information without direct human interaction.
  • a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
  • a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or network equipment.
  • the terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT narrow band internet of things
  • a terminal device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • references in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the phrase “at least one of A and B” or “at least one of A or B” should be understood to mean “only A, only B, or both A and B.”
  • the phrase “A and/or B” should be understood to mean “only A, only B, or both A and B”.
  • a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device.
  • the communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and/or use of the services provided by, or via, the communication system.
  • FIG.1 schematically shows a high level architecture in the fifth generation network according to an embodiment of the present disclosure.
  • the fifth generation network may be 5GS.
  • the architecture of FIG.1 is same as Figure 4.2.3-1 as described in 3GPP TS 23.501 V17.0.0, the disclosure of which is incorporated by reference herein in its entirety.
  • the system architecture of FIG.1 may comprise some exemplary elements such as AUSF, AMF, DN (data network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (Service Communication Proxy), NSSAAF (Network Slice-Specific Authentication and Authorization Function), NSACF (Network Slice Admission Control Function), etc.
  • the UE can establish a signaling connection with the AMF over the reference point N1, as illustrated in FIG.1.
  • This signaling connection may enable NAS (Non-access stratum) signaling exchange between the UE and the core network, comprising a signaling connection between the UE and the (R)AN and the N2 connection for this UE between the (R)AN and the AMF.
  • the (R)AN can communicate with the UPF over the reference point N3.
  • the UE can establish a protocol data unit (PDU) session to the DN (data network, e.g. an operator network or Internet) through the UPF over the reference point N6.
  • PDU protocol data unit
  • the exemplary system architecture also contains the service-based interfaces such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf and Nsmf exhibited by NFs such as the NRF, the NEF, the AUSF, the UDM, the PCF, the AMF, the NSACF and the SMF.
  • FIG.1 also shows some reference points such as N1, N2, N3, N4, N6 and N9, which can support the interactions between NF services in the NFs.
  • these reference points may be realized through corresponding NF service-based interfaces and by specifying some NF service consumers and providers as well as their interactions in order to perform a particular system procedure.
  • Various NFs shown in FIG.1 may be responsible for functions such as session management, mobility management, authentication, security, etc.
  • the AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, NSACF may include the functionality for example as defined in clause 6.2 of 3GPP TS 23.501 V17.0.0 .
  • FIG.2 schematically shows system architecture in a 4G network according to an embodiment of the present disclosure, which is the same as Figure 4.2-1 a of 3GPP TS 23.682 V16.9.0, the disclosure of which is incorporated by reference herein in its entirety.
  • the system architecture of FIG.2 may comprise some exemplary elements such as Services Capability Server (SCS), Application Server (AS), SCEF (Service Capability Exposure Function), HSS, UE, RAN(Radio Access Network), SGSN (Serving GPRS(General Packet Radio Service) Support Node), MME, MSC(Mobile Switching Centre), S-GW(Serving Gateway), GGSN/P-GW(Gateway GPRS Support Node/PDN(Packet Data Network) Gateway), MTC-IWF(Machine Type Communications-lnterWorking Function) CDF/CGF(Charging Data Function/Charging Gateway Function), MTC-AAA(Machine Type Communications-authentication, authorization and accounting), SMS-SC/GMSC/IWMSC(Short Message Service-Service Centre/Gateway MSC/lnterWorking MSC) IP-SM-GW(lnternet protocol Short Message Gateway).
  • the network elements and interfaces as shown in FIG.2 may be same as the corresponding network elements and interfaces as described in
  • the system architecture shows the architecture for a UE used for MTC connecting to the 3GPP network (UTRAN (Universal Terrestrial Radio Access Network), E-UTRAN (Evolved UTRAN), GERAN (GSM EDGE (Enhanced Data rates for GSM Evolution) Radio Access Network), etc.) via the Um/Uu/LTE-Uu interfaces.
  • the system architecture also shows the 3GPP network service capability exposure to SCS and AS.
  • the exemplary system architecture also contains various reference points.
  • Tsms Reference point used by an entity outside the 3GPP network to communicate with UEs used for MTC via SMS (Short Message Service).
  • Tsp Reference point used by a SCS to communicate with the MTC-IWF related control plane signalling.
  • T4 Reference point used between MTC-IWF and the SMS-SC in the FIPLMN.
  • T6a Reference point used between SCEF and serving MME.
  • T6b Reference point used between SCEF and serving SGSN.
  • T8 Reference point used between the SCEF and the SCS/AS.
  • S6m Reference point used by MTC-IWF to interrogate HSS/HLR (Flome Location Register).
  • S6n Reference point used by MTC-AAA to interrogate HSS/HLR.
  • S6t Reference point used between SCEF and HSS.
  • SGs Reference point used between MSC and MME.
  • Gi/SGi Reference point used between GGSN/P-GW and application server and between GGSN/P-GW and SCS.
  • Rf/Ga Reference point used between MTC-IWF and CDF/CGF.
  • Gd Reference point used between SMS-SC/GMSC/IWMSC and SGSN.
  • SGd Reference point used between SMS-SC/GMSC/IWMSC and MME.
  • E Reference point used between SMS-SC/GMSC/IWMSC and MSC.
  • the end-to-end communications uses services provided by the 3GPP system, and optionally services provided by a Services Capability Server (SCS).
  • SCS Services Capability Server
  • the MTC Application in the external network is typically hosted by an Application Server (AS) and may make use of an SCS for additional value added services.
  • the 3GPP system provides transport, subscriber management and other communication services including various architectural enhancements motivated by, but not restricted to, MTC (e.g. control plane device triggering).
  • FIG.3 shows non-roaming architecture for Network Exposure Function in reference point representation, which is same as Figure 4.2.3-5 of 3GPP TS 23.501 V17.0.0.
  • 3GPP Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity.
  • N33 is a reference point between NEF and AF.
  • API denotes Application Programming Interface.
  • FIG.4 shows non-roaming Service Exposure Architecture for EPC (Evolved Packet Core)-5GC Interworking, which is same as Figure 4.3.5.1 1 of 3GPP TS 23.501 V17.0.0 . If the UE is capable of mobility between EPS and 5GS, the network is expected to associate the UE with an SCEF+NEF (SCEF combined with NEF) node for Service Capability Exposure.
  • EPC Evolved Packet Core-5GC Interworking
  • EPC Interface represents southbound interfaces between SCEF and EPC nodes e.g. the S6t interface between SCEF and HSS, the T6a interface between SCEF and MME, etc. All southbound interfaces from SCEF are defined in 3GPP TS 23.682 V16.9.0] and are not shown for the sake of simplicity.
  • 5GC Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity.
  • FIG.5 shows a flowchart of a device triggering procedure via Nnef.
  • FIG.5 is same as Figure 4.13.2.2-1 of 3GPP TS 23.502 V17.0.0.
  • Step 1 The AF determines the need to trigger the device. If the AF has no contact details for the NEF, it shall discover and select NEF services.
  • Step 2 The AF invokes the Nnef_Trigger_Delivery request service.
  • Step 3 The NEF checks that the AF is authorised to send trigger requests and that the AF has not exceeded its quota or rate of trigger submission over Nnef. If this check fails, the NEF sends an Nnef_Trigger_Delivery response with a cause value indicating the reason for the failure condition and the flow stops at the step 3. Otherwise, the flow continues with step 4 of FIG.5.
  • Step 4 The NEF invokes Nudm_SDM_Get (Identifier Translation, GPSI and AF Identifier) to resolve the GPSI to SUPI when the AF is authorized to trigger the UE.
  • Nudm_SDM_Get Identifier Translation, GPSI and AF Identifier
  • the UDM may invoke the Nudr_DM_Query service to retrieve a list of AF's that are allowed to trigger the UE and determines, based on UDM policy, which identifier (SUPI or MSISDN) should be used to trigger the UE.
  • the UDM provides a Nudm_SDM_Get response (SUPI, optionally MSISDN. If the AF is not allowed to send a trigger message to this UE, or there is no valid subscription information for this user, the NEF sends an Nnef_Trigger_Delivery response with a cause value indicating the reason for the failure condition and the flow stops at this step 5 of FIG.5. Otherwise this flow continues with step 6 of FIG.5.
  • Step 6 The NEF invokes Nudm_UECM_Get (GPSI, SMS) to retrieve the UE SMSF(Short Message Service Function) identities.
  • the UDM may invoke the Nudr_DM_Query service to retrieve the UE SMSF identities.
  • the UDM provides a Nudm_UECM_Get response with the corresponding UE SMSF identities.
  • UDM policy possibly dependent on the VPLMN (Visited Public Land Mobile Network) ID
  • VPLMN Vehicle Land Mobile Network
  • the NEF can cache serving node information for the UE. However, this can increase the probability of trigger delivery attempt failures when the cached serving node information is stale.
  • Step 8 The NEF selects a suitable SMS-SC based on configured information.
  • the NEF acts as an MTC-IWF and sends a Submit Trigger (GPSI, SUPI, AF Identifier, trigger reference number, validity period, priority, SMSF serving node ID(s) (if available, are obtained from UDM in step 7 of FIG.5), SMS Application port ID, trigger payload, Trigger Indication) message to the SMS-SC.
  • a Submit Trigger GPSI, SUPI, AF Identifier, trigger reference number, validity period, priority, SMSF serving node ID(s) (if available, are obtained from UDM in step 7 of FIG.5), SMS Application port ID, trigger payload, Trigger Indication
  • the SMS-SC should not submit the message, but store it directly and send Routing Information for SM to request the UDM to add the SMS-SC address to the Message Waiting List.
  • Step 9 The SMS-SC sends a Submit Trigger Confirm message to the NEF to confirm that the submission of the SMS has been accepted by the SMS-SC.
  • Step 10 The NEF sends a Nnef_Trigger_Delivery response to the AF to indicate if the Device Trigger Request has been accepted for delivery to the UE.
  • Step 11 The SMS_SC performs MT SMS delivery as defined in clause 4.13.3.
  • the SMS-SC may provide the routing information that it received in step 6 of FIG.5 to SMS-GMSC to avoid UDM interrogation.
  • the SMS-SC generates the necessary CDR (Charging Data Record) information and includes the AF Identifier.
  • the SMS Application port ID which is included in the SM User Data Header, and the Trigger Indication are included in the CDRs in order to enable differentiated charging.
  • the SMS-SC stores the trigger payload, without routing information. If the message delivery fails and is attempted to be delivered again, UDM interrogation will be performed.
  • the SMS-SC shall send a SM (Short Message) Message Delivery Status Report to request the UDM to add the SMS-SC address to the Message Waiting list.
  • SM Short Message
  • a new UDM interrogation will be performed by the SMS-GMSC using SUPI or MSISDN.
  • SUPI Serving Node identities
  • the UDM may include up to four serving node identities (MSC or MME, SGSN, IP-SM-GW, AMF) in the response to SMS-GMSC.
  • Step 12 If the message delivery fails (either directly or when validity period of the trigger message expires) or when the message delivery succeeds, the SMS-SC shall send a Message Delivery Report (cause code, trigger reference number, AF Identifier) to the NEF.
  • a Message Delivery Report (cause code, trigger reference number, AF Identifier)
  • Step 13 The NEF provides a Nnef_Trigger_DeliveryNotify message to the AF with a Delivery Report indicating the trigger delivery outcome (e.g. succeeded, unknown or failed and the reason for the failure).
  • the NEF generates the necessary CDR information including the GPSI and AF Identifier.
  • Step 14 In response to the received device trigger, the UE takes specific actions and may take into consideration the content of the trigger payload. This action typically involves initiation of immediate or later communication with the AF.
  • Figure 6 In response to the received device trigger, the UE takes specific actions and may take into consideration the content of the trigger payload. This action typically involves initiation of immediate or later communication with the AF.
  • FIG.6 shows a flowchart of a procedure of MSISDN-less MO SMS Service.
  • FIG.6 is same as Figure 4.13.7.2-1 of 3GPP TS 23.502 V17.0.0.
  • Step 1 The UE uses SMS over NAS (Non-Access-Stratum) procedures in clause 4.13.3 of 3GPP TS 23.502 V17.0.0 to send an SMS to the AF.
  • NAS Non-Access-Stratum
  • the service center address points to the SMS-SC which contains the function described in this procedure, the destination SME address is set to short/long code of the AF and the Application Port ID element of the TP (Third Party)-User-Data field is set to the appropriate value.
  • the dummy MSISDN is used. This MSISDN and the IMSI of the UE are sent to SMS-SC.
  • SMS-SC uses the destination SME (Short Message Entity) address (long/short code of the AF) to identify the corresponding NEF based on a pre-configured mapping table. SMS-SC extracts the SMS payload, Application port ID, and IMSI of the UE and delivers them to NEF along with the destination SME address (long/short code of the AF). The NEF acts as an MTC-IWF in this procedure.
  • SME Short Message Entity
  • Step 4 The UDM provides a Nudm_SDM_Get response (GPSI). If the UE is not allowed to send an SMS payload to this AF, or there is no valid subscription information for this user, the flow proceeds to step 6 of FIG.6. [00109] Step 5.
  • the NEF provides a Nnef_MSISDN-less_MO_SMSNotify (SMS payload, GPSI, and
  • the AF is identified with the destination SME address (long/short code of the AF) received from step 2 of FIG.6.
  • the payload is delivered directly to the AF, it is not processed by NEF.
  • Step 6 The NEF, acting as an MTC-IWF, returns a success or failure delivery indication to SMS-SC.
  • Step 7. SMS-SC indicates success/failure back to UE using existing SMS delivery report defined in 3GPP TS 23.040 V17.0.0.
  • FIG.7 shows a flowchart of setting a policy for a future AF session.
  • FIG.7 is same as Figure 4.15.6.8-1 of 3GPP TS 23.502 V17.0.0.
  • Step 1 The AF previously negotiated policy for background data transfer using the Procedure for future background data transfer as described in clause 4.16.7.2 of 3GPP TS 23.502 V17.0.0.
  • Step 2 The AF requests that the previously negotiated policy for background data transfer be applied to a group of UE(s) or any UE, by invoking the Nnef_ApplyPolicy_Create service operation (AF Identifier, External Identifier or External Group Identifier, Background Data Transfer Reference ID).
  • the Background Data Transfer Reference ID parameter identifies a previously negotiated transfer policy for background data transfer as defined in clause 4.16.7 of 3GPP TS 23.502 V17.0.0.
  • the NEF assigns a Transaction Reference ID to the Nnef_ApplyPolicy_Create request.
  • the NEF authorizes the AF request and stores the AF Identifier and the Transaction Reference ID.
  • Step 3 The NEF invokes Nudm_SDM_Get (Identifier Translation, GPSI) to resolve the GPSI (External Identifier) to a SUPI or the NEF requests to resolve the External Group Identifier into the Internal Group Identifier using Nudm_SDM_Get (Group Identifier Translation, External Group Identifier).
  • Nudm_SDM_Get Identifier Translation, GPSI
  • Step 4b The NEF responds to the Nnef_ApplyPolicy_Create Request (Transaction Reference ID).
  • Step 7. SMS-SC indicates success/failure back to UE using existing SMS delivery report defined in 3GPP TS 23.040 V17.0.0.
  • FIG.8 shows a flowchart of device triggering procedure over Tsp.
  • FIG.8 is same as Figure 5.2.1 -1 of 3GPP TS 23.682 V16.9.0.
  • Step 1 The SCS determines the need to trigger the device. If the SCS has no contact details for an MTC-IWF, it may determine the IP address(es)/port(s) of the MTC-IWF by performing a DNS (Directory Name Service) query using the External Identifier or using a locally configured MTC-IWF identifier.
  • DNS Directory Name Service
  • Step 2 The SCS sends the Device Trigger Request (External Identifier or MSISDN, SCS Identifier, trigger reference number, validity period, priority, Application Port ID and trigger payload) message to the MTC-IWF.
  • the SCS includes a trigger payload that contains the information destined for the MTC application, along with the information to route it to the MTC application.
  • the Application Port ID is set to address a triggering function within the UE.
  • Step 3 The MTC-IWF checks that the SCS is authorised to send trigger requests and that the SCS has not exceeded its quota or rate of trigger submission over Tsp. If this check fails the MTC-IWF sends a Device Trigger Confirm message with a cause value indicating the reason for the failure condition and the flow stops at this step 3 of FIG.8. Otherwise, the flow continues with step 4 of FIG.8. [00125] Step 4.
  • the MTC-IWF sends a Subscriber Information Request (External Identifier or MSISDN and SCS Identifier) message to the HSS/HLR to determine if SCS is authorized to trigger the UE, to resolve the External Identifier or MSISDN to IMSI and retrieve the related HSS stored "Routing information" including the identities of the UE's serving CN node(s).
  • a Subscriber Information Request External Identifier or MSISDN and SCS Identifier
  • the MTC-IWF may cache authorization and routing information for the UE. Flowever, this may increase the probability of trigger delivery attempt failures when the cached serving node information is stale.
  • the HSS/HLR sends the Subscriber Information Response (IMSI and/or MSISDN and related "Routing information" including the serving node(s) identities, cause) message.
  • HSS/HLR policy possibly dependent on the VPLMN ID
  • the MTC-IWF sends a Device Trigger Confirm message with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise this flow continues with step 6a of FIG.8.
  • Step 6 The MTC-IWF attempts T4 trigger delivery procedure according to clause 5.2.2.
  • MTC-IWF may deliver device trigger as DL user data to the UE via SCEF using mobile terminated NIDD procedure as defined in clause 5.13.3. Otherwise, this flow continues with step 7 of FIG.8.
  • Step 7 The MTC-IWF sends the Device Trigger Report (External Identifier or MSISDN and trigger reference number) message to the SCS with a cause value indicating the trigger delivery outcome (e.g. succeeded, unknown or failed and the reason for the failure).
  • the MTC-IWF generates the necessary CDR information including the External Identifier or MSISDN and SCS Identifier.
  • Step 8 In response to the received device trigger, the UE takes specific actions that take into consideration the content of the trigger payload. This response typically involves initiation of immediate or later communication with the SCS or an AS.
  • FIG.9 shows a flowchart of identifier translation.
  • FIG.9 is same as Figure 5.2.2.2.10-1 of 3GPP TS 29.503 V17.2.0, the disclosure of which is incorporated by reference herein in its entirety.
  • FIG.9 shows a scenario where the NF service consumer (e.g. NEF) sends a request to the UDM to receive the SUPI/GPSI that corresponds to the provided GPSI/SUPI (see also 3GPP TS 23.502 V17.0.0, clause 4.13.2.2 and clause 4.13.7.2).
  • the request contains the UE's identity (/ ⁇ ueld ⁇ ) which shall be a SUPI or GPSI and the type of the requested information (/id-translation-result).
  • Step 1 The NF Service Consumer (e.g. NEF) shall send a GET request to the resource representing the IdTranslationResult, with query parameters indicating the supported-features and/or app-port-id.
  • Step 2 The UDM shall respond with "200 OK" with the message body containing the UE's SUPI.
  • the appropriate HTTP (Hyper Text Transfer Protocol) status code indicating the error shall be returned and appropriate additional error information should be returned in the GET response body.
  • Resource URI ⁇ apiRoot ⁇ /nudm-sdm/ ⁇ apiVersion>/ ⁇ ueld ⁇ /id-translation-result
  • This resource shall support the resource URI (Uniform Resource Identifier) variables defined in table 1 which is same as table 6.1.3.12.2-1 of 3GPP TS 29.503 V17.2.0.
  • Table 2 URI query parameters supported by the GET method on this resource
  • This method shall support the request data structures specified in table 3 which is same as table 6.1.3.12.3.1-2 of 3GPP TS 29.503 V17.2.0 and the response data structures and response codes specified in table 4 which is same as table 6.1.3.12.3.1-3 of 3GPP TS 29.503 V17.2.0.
  • Table 5 is same as table 6.1.3.12.3.1-4 of 3GPP TS 29.503 V17.2.0.
  • Table 6 is same as table 6.1.3.12.3.1-5 of 3GPP TS 29.503 V17.2.0.
  • Table 3 Data structures supported by the GET Request Body on this resource
  • Table 4 Data structures supported by the GET Response Body on this resource _
  • Table 6 Headers supported by the 200 Response Code on this resource as table 6.1.6.2.18-1 of 3GPP TS 29.503 V17.2.0.
  • Table 7 Definition of type IdTranslationResult
  • FIG.10 shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a network function or communicatively coupled to the network function.
  • the apparatus may provide means or modules for accomplishing various parts of the method 1000 as well as means or modules for accomplishing other processes in conjunction with other components.
  • the network function may be any suitable network device or node or entity or function which needs to use identifier translation service.
  • the network function may be a consumer of identifier translation service, such as an exposure function.
  • the exposure function may provide a means to securely expose the services, events and capabilities provided by network interfaces.
  • the exposure function may provide a means for the discovery of the exposed services and capabilities.
  • the exposure function may provide access to network capabilities through homogenous network application programming interfaces (e.g. Network APIs).
  • the exposure function may abstract the services from the underlying network interfaces and protocols.
  • the network function may comprise at least one of Service Capability Exposure Function (SCEF), Network Exposure Function (NEF), SCEF combined with NEF.
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • the network function may send an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier to a data management entity.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • AF application function
  • the network function may send the identifier translation request to the data management entity for example when the identifier translation is required.
  • the network function such as NEF may send the identifier translation request (such as Nudm_SDM_Get request) to the data management entity (such as UDM) in a procedure of application triggering service, a procedure of MSISDN-less MO SMS service, or a procedure of setting a policy for a future AF session.
  • the network function such as MTC-IWF may send the identifier translation request (such as subscriber information request) to the data management entity (such as HSS/HLR) in a procedure of device triggering service.
  • the identifier translation request such as subscriber information request
  • the data management entity such as HSS/HLR
  • the data management entity may be any suitable network device or node or entity or function which provides identifier translation service.
  • the data management entity may be a provider of identifier translation service.
  • the data management entity may comprise at least one of a unified data management (UDM), a home subscriber server (HSS), or a home location register (HLR).
  • the identifier translation request may comprise a Nudm_SDM_Get request as described in 3GPP TS 23.502 V17.0.0 or a subscriber information request as described in 3GPP TS 23.682 V16.9.0.
  • the first identifier and the second identifier may be any suitable identifier which can uniquely identify a user or a subscriber or a device, such as user identifier or subscriber identifier or device identifier, etc.
  • a subscriber or a user or a device may be configured with at least one identifier in a network.
  • SUPI and MSISDN may be used to identify a subscriber in 5GS.
  • IMSI and MSISDN may be used to identify a subscriber in LTE.
  • GPSI may be used to identify a subscriber in a network outside the 3GPP network.
  • a GPSI type comprises at least one of a MSISDN type or an external identity type.
  • the first identifier comprises a SUPI or IMSI.
  • the second identifier comprises a GPSI.
  • the requested identifier type comprises a specific GPSI type.
  • the first identifier belongs to a first GPSI type
  • the second identifier comprises a SUPI or an IMSI
  • the requested identifier type comprises a second GPSI type.
  • the first GPSI type may be MSISDN type and the second GPSI type may be external identity type.
  • the first GPSI type may be external identity type and the second GPSI type may be MSISDN type.
  • the second identifier belongs to the requested identifier type.
  • the first identifier may be resolved to the second identifier with the requested identifier type.
  • the AF identifier indicates authorization based on AF identifier is required on the data management entity.
  • the data management entity may perform authorization based on AF identifier.
  • the requested identifier type indicates an identifier belonging to the requested identifier type is required.
  • the identifier belonging to the requested identifier type may be returned to the network function.
  • the first identifier may be resolved to the second identifier with the requested identifier type.
  • the first identifier may be resolved to the second identifier and another identifier with the requested identifier type.
  • the network function may receive an identifier translation response from the data management entity.
  • the identifier translation response may comprise a Nudm_SDM_Get response as described in 3GPP TS 23.502 V17.0.0 or a subscriber information response as described in 3GPP TS 23.682 V16.9.0.
  • the identifier translation response may comprise any suitable information such as an identifier translation result.
  • the identifier translation response comprises a failure result. For example, if authorization based on AF identifier on the data management entity is failed, or there is no valid subscription information for the first identifier, the data management entity may send an identifier translation response with a cause value indicating the reason for the failure condition.
  • the identifier translation response comprises the second identifier.
  • the identifier translation response may comprise the second identifier.
  • the data management entity may send an identifier translation response comprising the second identifier.
  • the identifier translation request further comprises the requested identifier type
  • the first identifier may be resolved to the second identifier with the requested identifier type.
  • the identifier translation response further comprises an identifier belonging to the requested identifier type. For example, when the identifier translation request further comprises the requested identifier type, the first identifier may be resolved to the second identifier and another identifier with the requested identifier type.
  • FIG.11 shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a data management entity or communicatively coupled to the data management entity.
  • the apparatus may provide means or modules for accomplishing various parts of the method 1100 as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.
  • the data management entity may receive an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier from a network function.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • the network function may send the identifier translation request to the data management entity at block 1002 of FIG.10, and then the data management entity may receive the identifier translation request from the network function.
  • AF application function
  • the data management entity may perform authorization based on the AF identifier.
  • the data management entity may send an identifier translation response to the network function.
  • the requested identifier type indicates an identifier belonging to the requested identifier type is required.
  • the identifier translation response may comprise an identifier belonging to the requested identifier type.
  • the identifier translation response comprises a failure result.
  • the identifier translation response comprises the second identifier.
  • the first identifier may be resolved to the second identifier.
  • the identifier translation response further comprises an identifier belonging to the requested identifier type.
  • the first identifier may be resolved to the second identifier and another identifier belonging to the requested identifier type.
  • the second identifier belongs to the requested identifier type.
  • the first identifier may be resolved to the second identifier with the requested identifier type.
  • the first identifier belongs to a first GPSI type
  • the second identifier comprises a SUPI or an IMSI
  • the requested identifier type comprises a second GPSI type.
  • the first identifier may be resolved to the SUPI or the IMSI and the identifier belonging to the second GPSI type.
  • the identifier translation response may comprise the SUPI or the IMSI and the identifier belonging to the second GPSI type.
  • the first identifier comprises a SUPI or IMSI
  • the second identifier comprises a GPSI
  • the requested identifier type comprises a specific GPSI type.
  • the first identifier may be resolved to the GPSI with a specific GPSI type.
  • the identifier translation response may comprise the GPSI with a specific GPSI type.
  • the AF identifier as optional query parameter may be used to indicate whether authorization based on the AF identifier is additional required.
  • the requested identifier type such as requested-GPSI-type as optional query parameter may be used to indicate the specific identifier type such as the specific GPSI type is required.
  • the data management entity such as UDM performs authorization based on the AF identifier.
  • the data management entity such as UDM provides the identifier with the corresponding type within the response.
  • FIG.12 shows a flowchart of GPSI to SUPI translation according to an embodiment of the present disclosure.
  • UDM may receive an Id translation request from an NF consumer such as NEF for translation of a GPSI into a SUPI.
  • the Id translation request comprises GPSI, an AF identifier and a requested-GPSI-type in the query parameters.
  • UDM may perform authorization based on the AF identifier in the query parameter. If the AF identifier is not contained in the query parameter, the authorization step 1202 is skipped.
  • UDM may query SUPI based on GPSI in the Id translation request.
  • UDM may query additional GPSI based on the requested-GPSI-type in the Id translation request. If GPSI in the request resource URI variable is of type external identity and the requested-GPSI-type is MSISDN, UDM may query the MSISDN for the external identity. If GPSI in the request resource URI variable is of type MSISDN and the requested-GPSI-type is external identity, UDM may query the external identity for the MSISDN. If GPSI in the request resource URI variable is of type external identity and the requested-GPSI-type is not presented in the query parameter, step 1204 may be skipped. If GPSI in the request resource URI variable is of type MSISDN and the requested-GPSI-type is not presented in the query parameter, step 1204 may be skipped.
  • UDM may send an Id translation result to the NF consumer such as NEF.
  • FIG.13 shows a flowchart of SUPI to GPSI translation according to an embodiment of the present disclosure.
  • UDM may receive an Id translation request from an NF consumer such as NEF for translation of SUPI into GPSI.
  • the Id translation request may comprise SUPI, an AF identifier and a requested-GPSI-type in the query parameter.
  • UDM may perform authorization based on the AF identifier in the query parameter. If the AF identifier is not contained in the query parameter, the authorization step 1302 is skipped.
  • UDM may query the GPSI based on the requested-GPSI-type. If the requested-GPSI-type is MSISDN, UDM may query MSISDN for the SUPI in the request resource URI variable. If the requested-GPSI-type is external identity, UDM may query external identity for the SUPI in the request resource URI variable.
  • UDM may send an Id translation result to the NF consumer such as NEF.
  • the current UDM identity translation service can only serve use case 3, but for use case 1 and use case 2, there may be problem to be solved. So, it is necessary to provide enhancements on the identity translation service. For example, a new query parameter af-id is added, which when used contains the AF identifier. A new query parameter requested-gpsi-type is added, which when used contains the requested GPSI type.
  • 3GPP TS 29.503 V17.2.0 may be amended as following.
  • This resource represents the SUPI or GPSI. It is queried by the NEF for GPSI to SUPI translation or SUPI to GPSI translation. See 3GPP TS 23.502 [3] clause 4.13.2.2, 4.13.7.2, 4.15.6.8.
  • Resource URI ⁇ apiRoot ⁇ /nudm-sdm/ ⁇ apiVersion>/ ⁇ ueId ⁇ /id-translation-result This resource shall support the resource URI variables defined in table 6.1.3.12.2-1. Table 6.1.3.12.2-1: Resource URI variables for this resource
  • This method shall support the request data structures specified in table 6.1.3.12.3.1 -2 and the response data structures and response codes specified in table 6.1.3.12.3.1-3.
  • Table 6.1.3.12.3.1-2 Data structures supported by the GET Request Body on this resource
  • Table 6.1.3.12.3.1-3 Data structures supported by the GET Response Body on this resource
  • Table 6.1.3.12.3.1-4 Headers supported by the GET method on this resource
  • Last-Modified description:Timestamp forlastmodificationofthe resource,asdescribedin RFC 7232,
  • FIG.14 shows a use case of GPSI to SUPI translation according to another embodiment of the present disclosure.
  • the GPSI of type MSISDN for SMS.
  • URL Uniform Resource Locator
  • UDM performs the authorization based on the af-id in the query parameter. As an example suppose it is authorized.
  • UDM queries GPSI of the type MSISDN as indicated in the query parameter, requested-gpsi-type MSISDN. This query may further include query from external database UDR when UDM is stateless.
  • UDM sends the result to NEF, including the result from step 1403 and step 1404 for SUPI and MSISDN.
  • FIG.15 shows a use case of SUPI to GPSI translation according to another embodiment of the present disclosure.
  • UDM performs the authorization based on the af-id from the query parameter. As example suppose it is authorized.
  • UDM queries GPSI of type EXTJD by the ueld contained in the URI resource variable, imsi-zzzzzz. This query may further include query from external database UDR when UDM is stateless.
  • UDM sends the result to NEF, including the SUPI and the external identifier.
  • NEF including the SUPI and the external identifier.
  • FIG.16 shows a use case of GPSI to SUPI translation according to another embodiment of the present disclosure.
  • the NF service consumer such as NEF wants to translate a GPSI of type external identifier as extid-xxxxxx into a SUPI, but authorization based on AF identifier is not required, so af-id query parameter is not contained. Also additional GPSI types is not required, so requested-gpsi-type query parameter is not contained either.
  • the NF service consumer such as NEF sends a request to UDM by invoking Nudm_SDM_Get service, with URL like: .../ ⁇ ueld ⁇ /id-translation-result, uelD is the GPSI of type external identifier, such as extid-xxxxxx.
  • UDM queries SUPI by the ueld contained in the URI resource variable, extid-xxxxxx. This query may further include query from external database UDR when UDM is stateless.
  • UDM sends the result to NEF, including the result from step 1602 for the SUPI.
  • the proposed solution can enable the data management entity to perform authorization based on AF identifier.
  • the proposed solution can enable the requested-identifier-type as optional query parameter to indicate the required specific identifier type.
  • the proposed solution can fulfil more use cases.
  • the embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.
  • FIG.17 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure.
  • any one of the network function or the data management entity described above may be implemented as or through the apparatus 1700.
  • the apparatus 1700 comprises at least one processor 1721, such as a digital processor (DP), and at least one memory (MEM) 1722 coupled to the processor 1721.
  • the apparatus 1700 may further comprise a transmitter TX and receiver RX 1723 coupled to the processor 1721.
  • the MEM 1722 stores a program (PROG) 1724.
  • the PROG 1724 may include instructions that, when executed on the associated processor 1721, enable the apparatus 1700 to operate in accordance with the embodiments of the present disclosure.
  • a combination of the at least one processor 1721 and the at least one MEM 1722 may form processing means 1725 adapted to implement various embodiments of the present disclosure.
  • Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 1721, software, firmware, hardware or in a combination thereof.
  • the MEM 1722 may be of any type suitable to the local technical environment and may 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 memories and removable memories, as non-limiting examples.
  • the processor 1721 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • general purpose computers special purpose computers
  • microprocessors microprocessors
  • DSPs digital signal processors
  • processors based on multicore processor architecture as non-limiting examples.
  • the memory 1722 contains instructions executable by the processor 1721, whereby the network function operates according to any of the methods related to the network function as described above.
  • the memory 1722 contains instructions executable by the processor 1721, whereby the data management entity operates according to any of the methods related to the data management entity as described above.
  • FIG.18 is a block diagram showing a network function according to an embodiment of the disclosure.
  • the network function 1800 comprises a sending module 1801 and a receiving module 1802.
  • the sending module 1801 may be configured to send an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier to a data management entity.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • the receiving module 1802 may be configured to receive an identifier translation response from the data management entity.
  • AF application function
  • FIG.19 is a block diagram showing a data management entity according to an embodiment of the disclosure.
  • the data management entity 1900 comprises a receiving module 1901 and a sending module 1902.
  • the receiving module 1901 may be configured to receive an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier from a network function.
  • the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type.
  • the sending module 1902 may be configured to send an identifier translation response to the network function.
  • AF application function
  • the data management entity 1900 may further comprise a authorization module 1903 configured to perform authorization based on the AF identifier.
  • the term unit or module may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • the network function or the data management entity may not need a fixed processor or memory, any computing resource and storage resource may be arranged from the network function or the data management entity in the communication system.
  • the introduction of virtualization technology and network computing technology may improve the usage efficiency of the network resources and the flexibility of the network.
  • a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.
  • the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • the computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory), a ROM (read only memory), Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.
  • a method (1000) performed by a network function comprising: sending (1002) an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier to a data management entity, wherein the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type; and receiving (1004) an identifier translation response from the data management entity.
  • AF application function
  • identifier translation response further comprises an identifier belonging to the requested identifier type.
  • the first identifier belongs to a first generic public subscription identifier (GPSI) type
  • the second identifier comprises a subscription permanent identifier (SUPI) or an international mobile subscriber identity (IMSI)
  • the requested identifier type comprises a second GPSI type
  • the first identifier comprises a SUPI or IMSI
  • the second identifier comprises a GPSI
  • the requested identifier type comprises a specific GPSI type
  • a GPSI type comprises at least one of: a mobile subscriber integrated services digital network number (MSISDN) type, or an external identity type.
  • MSISDN mobile subscriber integrated services digital network number
  • the data management entity comprises at least one of: a unified data management (UDM), a home subscriber server (HSS), or a home location register (HLR).
  • UDM unified data management
  • HSS home subscriber server
  • HLR home location register
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • the identifier translation request comprises a Nudm_SDM_Get request or a subscriber information request and the identifier translation response comprises Nudm_SDM_Get response or a subscriber information response.
  • a method (1100) performed by a data management entity comprising: receiving (1102) an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier from a network function, wherein the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type; and sending (1106) an identifier translation response to the network function.
  • AF application function
  • the method further comprises: performing (1104) authorization based on the AF identifier.
  • identifier translation response further comprises an identifier belonging to the requested identifier type.
  • the first identifier belongs to a first generic public subscription identifier (GPSI) type
  • the second identifier comprises a subscription permanent identifier (SUPI) or an international mobile subscriber identity (IMSI)
  • the requested identifier type comprises a second GPSI type
  • a GPSI type comprises at least one of: a mobile subscriber integrated services digital network number (MSISDN) type, or an external identity type.
  • MSISDN mobile subscriber integrated services digital network number
  • the data management entity comprises at least one of: a unified data management (UDM), a home subscriber server (HSS), or a home location register (HLR).
  • UDM unified data management
  • HSS home subscriber server
  • HLR home location register
  • SCEF Service Capability Exposure Function
  • NEF Network Exposure Function
  • the identifier translation request comprises a Nudm_SDM_Get request or a subscriber information request and the identifier translation response comprises Nudm_SDM_Get response or a subscriber information response.
  • a network function (1700) comprising: a processor (1721); and a memory (1722) coupled to the processor (1721), said memory (1722) containing instructions executable by said processor (1721), whereby said network function (1700) is operative to: send an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier to a data management entity, wherein the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type; and receive an identifier translation response from the data management entity.
  • AF application function
  • a data management entity (1700) comprising: a processor (1721); and a memory (1722) coupled to the processor (1721), said memory (1722) containing instructions executable by said processor (1721), whereby said data management entity (1700) is operative to: receive an identifier translation request comprising a first identifier for resolving the first identifier to a second identifier from a network function, wherein the identifier translation request further comprises an application function (AF) identifier and/or a requested identifier type; and send an identifier translation response to the network function.
  • AF application function
  • a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of embodiment 1 to 26.
  • a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of embodiment 1 to 26.
  • an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions.
  • these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof.
  • firmware or software implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent un procédé et un appareil pour la traduction d'un identifiant. Un procédé exécuté par une fonction réseau consiste à envoyer à une entité de gestion de données une demande de traduction d'identifiant comprenant un premier identifiant pour résoudre le premier identifiant en un second identifiant. La demande de traduction d'identifiant comprend en outre un identifiant de fonction application (AF) et/ou un type d'identifiant demandé. Le procédé consiste en outre à recevoir une réponse de traduction d'identifiant en provenance de l'entité de gestion de données.
PCT/EP2022/059039 2021-04-06 2022-04-05 Procédé et appareil pour la traduction d'un identifiant WO2022214504A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2021/085713 2021-04-06
CN2021085713 2021-04-06

Publications (1)

Publication Number Publication Date
WO2022214504A1 true WO2022214504A1 (fr) 2022-10-13

Family

ID=81580828

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/059039 WO2022214504A1 (fr) 2021-04-06 2022-04-05 Procédé et appareil pour la traduction d'un identifiant

Country Status (1)

Country Link
WO (1) WO2022214504A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020102795A1 (fr) * 2018-11-16 2020-05-22 Talebi Fard Peyman Déclenchement d'application pour un dispositif sans fil
CN111490842A (zh) * 2020-03-23 2020-08-04 腾讯科技（深圳）有限公司 时间同步方法、装置、计算机可读介质及电子设备
WO2020252337A1 (fr) * 2019-06-12 2020-12-17 Apple Inc. Mesures de performance associées à un déclenchement d'application et à un sms sur une strate nas
WO2020249201A1 (fr) * 2019-06-12 2020-12-17 Huawei Technologies Co., Ltd. Procédés et dispositifs pour l'établissement de session à pdu redondante

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020102795A1 (fr) * 2018-11-16 2020-05-22 Talebi Fard Peyman Déclenchement d'application pour un dispositif sans fil
WO2020252337A1 (fr) * 2019-06-12 2020-12-17 Apple Inc. Mesures de performance associées à un déclenchement d'application et à un sms sur une strate nas
WO2020249201A1 (fr) * 2019-06-12 2020-12-17 Huawei Technologies Co., Ltd. Procédés et dispositifs pour l'établissement de session à pdu redondante
CN111490842A (zh) * 2020-03-23 2020-08-04 腾讯科技（深圳）有限公司 时间同步方法、装置、计算机可读介质及电子设备
US20220174631A1 (en) * 2020-03-23 2022-06-02 Tencent Technology (Shenzhen) Company Limited Time synchronization method and apparatus, computer-readable medium, and electronic device

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.040
3GPP TS 23.501
3GPP TS 23.502
3GPP TS 23.682
3GPP TS 29.503
CONVIDA WIRELESS LLC: "Introduction of the MSISDN-less MO SMS Service", vol. SA WG2, no. Kochi, India; 20190121 - 20190125, 14 March 2019 (2019-03-14), XP051697160, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/TSG%5FSA/TSGS%5F83/Docs/SP%2D190166%2Ezip> [retrieved on 20190314] *

Similar Documents

Publication Publication Date Title
EP3711282B1 (fr) Procédé et appareil de mise à jour d&#39;inscription
WO2021189369A1 (fr) Procédé et appareil pour une exposition de capacité de réseau
WO2022007904A1 (fr) Procédé et appareil de service de localisation
WO2022033478A1 (fr) Procédé et appareil de communication de sécurité
EP4104412A1 (fr) Support de sous-système multimédia de protocole internet pour réseaux non publics autonomes
WO2022214504A1 (fr) Procédé et appareil pour la traduction d&#39;un identifiant
US20230232205A1 (en) Method and apparatus for group-based network management
WO2023274366A1 (fr) Procédé et appareil d&#39;établissement de session avec une qualité de service requise
WO2022152209A1 (fr) Procédé et appareil d&#39;extraction d&#39;informations de routage
WO2024083105A1 (fr) Procédé et appareil de sécurité de plan utilisateur d&#39;un groupe de réseaux virtuels
WO2023143385A1 (fr) Procédé et appareil de formation de groupe fondé sur la localisation
US20230075951A1 (en) Method and apparatus for registration data retrieval
US20240155334A1 (en) Method and Apparatus for Exposing User Equipment Address Information
WO2023125805A1 (fr) Procédé et appareil de gestion de session
CN113424560B (zh) 用于组内容传送的方法和装置
US12004053B2 (en) Method and apparatus for group content delivery
WO2024094049A2 (fr) Procédé et appareil de gestion d&#39;abonnement
US20240064494A1 (en) Systems and methods for device triggering for 5g devices
WO2023006061A1 (fr) Procédé et appareil de facturation
WO2021180170A1 (fr) Procédé et appareil de transfert intercellulaire
WO2023047388A1 (fr) Prise en charge de session de sous-système multimédia de protocole internet pour fonction d&#39;analyse de données de réseau
EP4295550A1 (fr) Support d&#39;un déploiement de dccf multiples

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22721278

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22721278

Country of ref document: EP

Kind code of ref document: A1