WO2022016512A1 - Method and apparatus for managing external subscription data - Google Patents

Method and apparatus for managing external subscription data Download PDF

Info

Publication number
WO2022016512A1
WO2022016512A1 PCT/CN2020/104468 CN2020104468W WO2022016512A1 WO 2022016512 A1 WO2022016512 A1 WO 2022016512A1 CN 2020104468 W CN2020104468 W CN 2020104468W WO 2022016512 A1 WO2022016512 A1 WO 2022016512A1
Authority
WO
WIPO (PCT)
Prior art keywords
external
external subscription
subscription data
data
subscription
Prior art date
Application number
PCT/CN2020/104468
Other languages
French (fr)
Inventor
Jianning Liu
Genadi Velev
Andreas Kunz
Tingfang Tang
Sheeba Backia MARY BASKARAN
Original Assignee
Lenovo (Beijing) Limited
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 Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2020/104468 priority Critical patent/WO2022016512A1/en
Publication of WO2022016512A1 publication Critical patent/WO2022016512A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • Embodiments of the present application generally relate to a wireless communication technology, and especially to a method and apparatus for managing external subscription data of a user equipment (UE) owned by a third party.
  • UE user equipment
  • a private 5G network is also termed a non-public network (NPN) .
  • NPN non-public network
  • the 5G private network provides 5G network services to a clearly defined user organization or group of user organizations.
  • the 5G private network is deployed on the organization’s defined premises, such as a campus or a factory.
  • 3GPP 3 rd generation partnership project
  • SNPN standalone non-public network
  • PLMN public land mobile network
  • SNPN public network integrated NPN
  • the SNPN is supposed to support a UE with external subscription data owned by a third party (3 rd party) entity (e.g., an authentication authorization accounting (AAA) server) , it is feasible to communicate between the SNPN and the 3 rd party entity for authentication and authorization for the UE.
  • a third party 3 rd party entity
  • AAA authentication authorization accounting
  • Embodiments of the present application provide a method and apparatus for managing the external subscription data.
  • An embodiment of the present application provides a method performed by a data management entity.
  • the method may include: receiving external subscription data for a user equipment (UE) from a home network of the UE; registering the UE with the received external subscription data; and generating and transmitting the external subscription registration result to the home network of the UE.
  • UE user equipment
  • receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from the home network of the UE, and transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration response including the identity of the UE and the external subscription registration result to the home network of the UE.
  • registering the UE with the received external subscription data further comprises: determining to register the UE with the received external subscription data based on a local policy of a non-public network after receiving the external subscription registration request.
  • receiving the external subscription data for the UE comprises: receiving an external subscription retrieve response including an identity of the UE and the external subscription data for the UE from the home network of the UE, and transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration notification including the identity of the UE and the external subscription registration result to the home network of the UE.
  • the method further comprises: before receiving the external subscription retrieve response, determining to retrieve the external subscription data for the UE from the home network of the UE based on a local policy of a non-public network; and transmitting an external subscription retrieve request including an identity of the UE and an identity of the non-public network to the home network of the UE.
  • receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from an access and mobility management function entity, and transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration response including the identity of the UE and the external subscription registration result to the access and mobility management function entity.
  • the external subscription data comprises: access and mobility related subscription data; and session management related subscription data.
  • the external subscription data further comprises at least one of: policy related subscription data; and slice related subscription data.
  • the method may include: receiving external subscription data for a user equipment (UE) from a home network of the UE; determining whether to register the external subscription data for the UE to a data management entity; and transmitting an external subscription registration request to the data management entity in response to determining to register the external subscription data for the UE to the data management entity.
  • UE user equipment
  • receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from the home network of the UE.
  • the method may further include: receiving an external subscription registration response including an identity of the UE and an external subscription registration result from the data management entity; and transmitting the external subscription registration response including the identity of the UE and the external subscription registration result to the home network of the UE.
  • the apparatus may include at least one non-transitory computer-readable medium having computer executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter.
  • the computer executable instructions are programmed to implement the above method with the at least one receiver, the at least one transmitter and the at least one processor.
  • Embodiments of the present application can manage the external subscription data of the UE in the UE's home network by the SNPN.
  • FIG. 1 is a flow chart illustrating a method for a SNPN to manage the external subscription data owned by a 3 rd party entity according to an embodiment of the present application
  • FIG. 2 is a flow chart illustrating a method for a SNPN to manage the external subscription data of a UE owned by a 3 rd party entity according to another embodiment of the present application;
  • FIG. 3 is a flow chart illustrating a method for a SNPN to manage the external subscription data owned by a 3 rd party entity according to yet another embodiment of the present application;
  • FIG. 4 illustrates an apparatus according to some embodiments of the present application.
  • FIG. 5 illustrates an apparatus according to some other embodiments of the present application.
  • the 3 rd party entity is deployed as 5G system, e.g., PLMN or SNPN.
  • the V-SNPN can retrieve the subscription data of the UE from a unified data management (UDM) in the 3 rd party entity via some direct interfaces.
  • UDM unified data management
  • this solution is only for the 3 rd party entity deployed as 5G system with a UDM and having the interface (s) to the SNPN.
  • the 3 rd party entity is an entity not deployed as 5G system or not deployed the UDM but only an AAA server.
  • IDs there are two identities (IDs) for a UE.
  • SI subscription ID
  • UDM unified data repository
  • the other is an identity of the UE (also called UE ID) allocated by the 3 rd party entity which is used for primary authentication and authorization between UE and the 3 rd party entity.
  • an access and mobility management function AMF has to maintain the mapping relationship between the two IDs.
  • the AMF in the SNPN has to firstly find the SI by mapping the UE ID, and then to finish the rest of the procedures. It is complicated and almost all of the procedures are impacted.
  • the 3 rd party entity is a home network of the UE
  • the AAA server in the 3 rd party entity is an example of an entity storing the subscription data of the UE in the home network of the UE. It should be understood that another entity storing the subscription data of the UE may replace the AAA server to perform its operations in the following embodiments of the present application.
  • FIG. 1 is a flow chart illustrating a method for a SNPN to manage the external subscription data owned by a 3 rd party entity according to an embodiment of the present application.
  • an AAA server in the 3 rd party entity triggers an external subscription registration of a UE by using a new interface between a UDM in the SNPN and the AAA server, when the UE accesses the SNPN (or called the serving SNPN) .
  • the AAA server in the 3 rd party entity stores the subscription data of the UE.
  • the SNPN includes an access network (AN) , an AMF, and a UDM.
  • the SNPN in FIG. 1 may also include a UDR for storing and retrieving the subscription data for the UDM.
  • the AN, the AMF, and the UDM being included in the SNPN are illustrated in FIG. 1 for concise, it should be understood that the SNPN may include other function entities.
  • the AN may be configured to provide a network access service for the UE.
  • AN entity may also be referred to as radio access network (RAN) entity, an access point, an access terminal, a base, a macro cell, a Node-B, an enhanced Node B (eNB) , a gNB, a home Node-B, a relay node, or any device described using other terminology used in the art.
  • RAN radio access network
  • the AMF, the UDM and the UDR are network function entities of a 5G core network.
  • the AMF is a network function entity used for receiving all the connection and session information from a UE or the AN and handling connection and mobility management tasks.
  • the UDM is a network function entity used for managing network user data in a single, centralized element.
  • the UDR is a converged repository of subscriber information and can be used to service a number of network functions. For example, in the embodiments of the present application, the UDM can use the UDR to store and retrieve subscription data of a UE.
  • the UE may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., television connected to the Internet) , a set-top box, a game console, a security system (including a security camera) , a vehicle on-board computer, a network device (e.g., a router, a switch, and a modem) , or the like.
  • a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., television connected to the Internet) , a set-top box, a game console, a security system (including a security camera) , a vehicle on-board computer, a network device (e.g., a router, a switch, and a modem) , or the like.
  • the UE may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, or the like.
  • the UE may be referred to as a subscriber unit, a mobile phone, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or any device described using other terminology used in the art.
  • step 101 the UE initiates a registration request including an identity of the UE (UE ID) in the 3 rd party to the serving SNPN, that is, the AN of the SNPN.
  • step 102 the AN transmits the registration request including the UE ID to the AMF.
  • step 103 an external authentication and authorization is successfully performed between the UE and the AAA server in the 3 rd party entity.
  • the AAA server determines to send an external subscription registration request for the UE to the UDM in the serving SNPN based on a 3 rd party policy or a service agreement with the serving SNPN via for example, the new interface between the UDM and the AAA server.
  • the external subscription registration request may include the UE ID and the external subscription data for the UE.
  • the external subscription data may include access and mobility related subscription data and session management related subscription data.
  • the external subscription data may further include policy related subscription data and/or slice related subscription data.
  • the 3 rd party entity since the 3 rd party entity has a service agreement with other networks (e.g., the serving SNPN) , the 3 rd party entity will create and maintain a set of subscription data of UE that is suitable for the serving network.
  • the serving SNPN the serving SNPN
  • the UDM After receiving the external subscription registration request, in step 105, the UDM determines whether the external subscription registration request with the received external subscription data from the 3 rd party entity is allowed based on a local policy of the SNPN and/or the agreement with the 3 rd party entity.
  • the UDM Upon determining the registration request is allowed and completing the registration successfully, in step 106, the UDM transmits an external subscription registration response to the AAA server.
  • the external subscription registration response may include the UE ID and an external subscription registration result. Since the UDM determines the registration request is allowed and completes the registration successfully, the UDM may generate the external subscription registration result as accepting; otherwise, the external subscription registration result is rejecting.
  • the AAA server may update the state of the subscription data of the UE related to the serving SNPN.
  • step 107 the UDM will wait to feedback the request from the AMF until the external subscription registration is completed when the UDM is performing the external subscription registration. More details regarding the step 107 are the same as the steps 14a-14c in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
  • step 108 the serving SNPN transmits a registration accept message including necessary parameters to the UE, and the UE transmits a registration complete message to the serving SNPN if needed, more details are the same as the steps 15-24 in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
  • FIG. 2 is a flow chart illustrating a method for a SNPN to manage the external subscription data of a UE owned by a 3 rd party entity according to another embodiment of the present application.
  • the UDM in the serving SNPN triggers an external subscription registration of a UE by using a new interface between the UDM in the SNPN and an AAA server in the 3 rd party entity, when the UE accesses the SNPN (the serving SNPN) .
  • the AAA server in the 3 rd party entity stores the subscription data of the UE.
  • the SNPN includes an AN, an AMF, and a UDM.
  • the SNPN in FIG. 2 may also include a UDR for storing and retrieving the subscription data for the UDM.
  • the AN, the AMF, and the UDM being included in the SNPN are illustrated in FIG. 2 for concise, it should be understood that the SNPN may include other function entities.
  • the UE initiates a registration request including an identity of the UE (UE ID) in the 3 rd party to the serving SNPN, that is, the AN of the SNPN.
  • the AN transmits the registration request including the UE ID to the AMF.
  • step 203 an external authentication and authorization is successfully performed between the UE and the AAA server in the 3 rd party entity.
  • step 204 the AMF transmits a Nudm_SDM_Get request including the UE ID to the UDM selected by the AMF so as to retrieve the subscription data of the UE from the UDM.
  • the UDM After receiving the Nudm_SDM_Get request including the UE ID, the UDM determines whether there is the subscription data of the UE corresponding to the UE ID included in the Nudm_SDM_Get request. In step 205, if there is no subscription data of the UE, the UDM determines to retrieve external subscription data of the UE from the AAA server in the 3 rd party entity based on a local policy of the SNPN and/or the agreement with the 3 rd party entity.
  • the UDM transmits an external subscription retrieve request to the AAA server in the 3 rd party entity via for example, the new interface between the UDM and the AAA server.
  • the external subscription retrieve request may include the UE ID and an identity of the SNPN (SNPN ID) .
  • the AAA server in the 3 rd party entity determines whether the request is allowed based on a local policy of the 3 rd party entity or a service agreement with the serving SNPN. If the request is allowed, in step 207, the AAA server transmits an external subscription retrieve response including the UE ID and the external subscription data of the UE to the UDM.
  • the external subscription data may include access and mobility related subscription data and session management related subscription data. Furthermore, the external subscription data may further include policy related subscription data and/or slice related subscription data.
  • the AAA server may transmit an external subscription retrieve response including the UE ID and a result indicating rejecting.
  • step 208 the UDM registers the UE with the received external subscription data of the UE.
  • the UDM transmits a Undm_SDM_Get response including the UE ID and the required subscription data of the UE to the AMF.
  • the UDM may transmit an external subscription registration notification including the UE ID and the registration result to the AAA server.
  • the UDM registers the UE with the external subscription data of the UE, thus the registration result is accepting; otherwise, the registration result is rejecting.
  • step 211 the serving SNPN transmits a registration accept message including necessary parameters to the UE, and the UE transmits a registration complete message to the serving SNPN if needed, more details are the same as the steps 15-24 in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
  • FIG. 3 is a flow chart illustrating a method for a SNPN to manage the external subscription data owned by a 3 rd party entity according to yet another embodiment of the present application.
  • an AAA server in the 3 rd party entity triggers an external subscription registration of a UE by using an AMF in the SNPN as a proxy, when the UE accesses the SNPN (the serving SNPN) .
  • the AAA server in the 3 rd party entity stores the subscription data of the UE.
  • the message between the AMF and the AAA server (for example, the messages communicated in steps 304 and 309 in FIG. 3) can be directly transferred via the new interface.
  • the message between the AMF and the AAA server can be indirectly transferred via other network function entities (such as, a network exposure function (NEF) entity, authentication server function (AUSF) entity, a proxy of AAA server) .
  • NEF network exposure function
  • AUSF authentication server function
  • the SNPN includes an AN, an AMF, and a UDM.
  • the SNPN in FIG. 3 may also include a UDR for storing and retrieving the subscription data for the UDM.
  • the AN, the AMF, and the UDM being included in the SNPN are illustrated in FIG. 3 for concise, it should be understood that the SNPN may include other function entities, for example, the NEF, the AUSF, and so on.
  • the UE initiates a registration request including an identity of the UE (UE ID) in the 3 rd party to the serving SNPN, that is, the AN of the SNPN.
  • the AN transmits the registration request including the UE ID to the AMF.
  • step 303 an external authentication and authorization is successfully performed between the UE and the AAA server in the 3 rd party entity via the AMF.
  • the AAA server determines to send an external subscription registration request for the UE to the AMF in the serving SNPN based on a 3 rd party policy or a service agreement with the serving SNPN via for example, the new interface between the AMF and the AAA server.
  • the external subscription registration request includes the UE ID and the external subscription data for the UE.
  • the external subscription data may include access and mobility related subscription data and session management related subscription data.
  • the external subscription data may further include policy related subscription data and/or slice related subscription data.
  • the 3 rd party entity since the 3 rd party entity has a service agreement with other networks (e.g., the serving SNPN) , the 3 rd party entity will create and maintain a set of subscription data of UE that is suitable for the serving network.
  • the serving SNPN the serving SNPN
  • the AMF determines the external subscription registration request is allowed based on a local policy of the SNPN and/or the agreement with the 3 rd party entity. In another embodiment, if the AMF determines the external subscription registration request is not allowed, for example, based on the local policy or there is no agreement with the 3 rd party entity, the AMF may transmit a rejecting message as a response to the request to the AAA server.
  • the AMF Upon determining the external subscription registration request is allowed, in step 306, the AMF transmits the external subscription registration request including the UE ID and the external subscription data for the UE to the UDM.
  • the UDM registers the UE with the UE ID and the received subscription data.
  • the UDM may store the received subscription data of the UE in the UDR.
  • the UDM After completing the registration successfully, in step 308, the UDM transmits an external subscription registration response to the AMF.
  • the external subscription registration response may include the UE ID and the external subscription registration result. Since the UDM completes the registration successfully, the external subscription registration result indicates accepting; otherwise, the external subscription registration result indicates rejecting.
  • the AMF After receiving the external subscription registration response, in step 309, the AMF transmits the external subscription registration response including the UE ID and the external subscription registration result to the AAA server, for example, via the new interface.
  • the AAA server may update the state of the subscription data of the UE related to the serving SNPN.
  • the AMF may transmit a registration accept message to the UE.
  • the serving SNPN transmits the registration accept message including necessary parameters to the UE, and the UE transmits a registration complete message to the serving SNPN if needed, more details are the same as the steps 15-24 in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
  • the SNPN to support the UE with external subscription data owned by a 3 rd party entity by registering the external subscription data from the 3 rd party entity to the UDM in the SNPN, so that the SNPN can manage the external UE as a native UE.
  • FIG. 4 illustrates an apparatus according to some embodiments of the present application.
  • the apparatus 400 may be the UDM illustrated in the above embodiments of the present application.
  • the apparatus 400 may include a receiver 401, a transmitter 403, a processer 405, and a non-transitory computer-readable medium 407.
  • the non-transitory computer-readable medium 407 has computer executable instructions stored therein.
  • the processer 405 is configured to be coupled to the non-transitory computer readable medium 407, the receiver 401, and the transmitter 403. It is contemplated that the apparatus 400 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements.
  • the receiver 401 and the transmitter 403 are integrated into a single device, such as a transceiver.
  • the apparatus 400 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 407 may have stored thereon computer-executable instructions to cause a processor to implement the processes performed by the UE in the above methods according to embodiments of the present application.
  • FIG. 5 illustrates an apparatus according to some other embodiments of the present application.
  • the apparatus 500 may be the AMF illustrated in the above embodiments of the present application.
  • the apparatus 500 may include a receiver 501, a transmitter 503, a processer 505, and a non-transitory computer-readable medium 507.
  • the non-transitory computer-readable medium 507 has computer executable instructions stored therein.
  • the processer 505 is configured to be coupled to the non-transitory computer readable medium 507, the receiver 501, and the transmitter 503. It is contemplated that the apparatus 500 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements.
  • the receiver 501 and the transmitter 503 are integrated into a single device, such as a transceiver.
  • the apparatus 500 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 507 may have stored thereon computer-executable instructions to cause a processor to implement the processes performed by the AMF in the above methods according to embodiments of the present application.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • the steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
  • the terms “comprises, “ “comprising, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
  • the term “another” is defined as at least a second or more.
  • the terms “including, “ “having, “ and the like, as used herein, are defined as “comprising. "

Landscapes

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

Abstract

A method and apparatus for managing external subscription data. A method performed by a data management entity is provided. The method may include: receiving external subscription data for a UE from a home network of the UE; registering the UE with the received external subscription data; and generating and transmitting the external subscription registration result to the home network of the UE.

Description

METHOD AND APPARATUS FOR MANAGING EXTERNAL SUBSCRIPTION DATA TECHNICAL FIELD
Embodiments of the present application generally relate to a wireless communication technology, and especially to a method and apparatus for managing external subscription data of a user equipment (UE) owned by a third party.
BACKGROUND
A private 5G network is also termed a non-public network (NPN) . In contrast to a network that offers mobile network services to the general public, the 5G private network provides 5G network services to a clearly defined user organization or group of user organizations. The 5G private network is deployed on the organization’s defined premises, such as a campus or a factory. According to 3 rd generation partnership project (3GPP) TS 23.501, there are two types of 5G private network: a standalone non-public network (SNPN) , which does not rely on a public land mobile network (PLMN) and is operated by a SNPN operator; and a public network integrated NPN, which is a nonpublic network deployed with the support of a PLMN network.
Currently, the SNPN is supposed to support a UE with external subscription data owned by a third party (3 rd party) entity (e.g., an authentication authorization accounting (AAA) server) , it is feasible to communicate between the SNPN and the 3 rd party entity for authentication and authorization for the UE.
However, there is no mechanism to exchange the UE’s subscription data between the SNPN and the 3 rd party entity so that the SNPN cannot retrieve UE’s subscription data from the 3 rd party entity to finish the necessary procedures, for example, a registration procedure, or a protocol packet unit (PDU) session establishment procedure and so on.
Therefore, a method for the SNPN to manage the external subscription data of the UE owned by a 3 rd party entity is needed.
SUMMARY OF THE APPLICATION
Embodiments of the present application provide a method and apparatus for managing the external subscription data.
An embodiment of the present application provides a method performed by a data management entity. The method may include: receiving external subscription data for a user equipment (UE) from a home network of the UE; registering the UE with the received external subscription data; and generating and transmitting the external subscription registration result to the home network of the UE.
In an embodiment of the present application, receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from the home network of the UE, and transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration response including the identity of the UE and the external subscription registration result to the home network of the UE.
In an embodiment of the present application, registering the UE with the received external subscription data further comprises: determining to register the UE with the received external subscription data based on a local policy of a non-public network after receiving the external subscription registration request.
In another embodiment of the present application, receiving the external subscription data for the UE comprises: receiving an external subscription retrieve response including an identity of the UE and the external subscription data for the UE from the home network of the UE, and transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration notification including the identity of the UE and the external subscription registration result to the home network of the UE. The method further  comprises: before receiving the external subscription retrieve response, determining to retrieve the external subscription data for the UE from the home network of the UE based on a local policy of a non-public network; and transmitting an external subscription retrieve request including an identity of the UE and an identity of the non-public network to the home network of the UE.
In another embodiment of the present application, receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from an access and mobility management function entity, and transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration response including the identity of the UE and the external subscription registration result to the access and mobility management function entity.
In an embodiment of the present application, the external subscription data comprises: access and mobility related subscription data; and session management related subscription data. The external subscription data further comprises at least one of: policy related subscription data; and slice related subscription data.
Another embodiment of the present application provides a method performed by an access and mobility management function entity. The method may include: receiving external subscription data for a user equipment (UE) from a home network of the UE; determining whether to register the external subscription data for the UE to a data management entity; and transmitting an external subscription registration request to the data management entity in response to determining to register the external subscription data for the UE to the data management entity.
In an embodiment of the present application, receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from the home network of the UE.
In an embodiment of the present application, the method may further include: receiving an external subscription registration response including an identity of the  UE and an external subscription registration result from the data management entity; and transmitting the external subscription registration response including the identity of the UE and the external subscription registration result to the home network of the UE.
Another embodiment of the present application provides an apparatus. The apparatus may include at least one non-transitory computer-readable medium having computer executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter. The computer executable instructions are programmed to implement the above method with the at least one receiver, the at least one transmitter and the at least one processor.
Embodiments of the present application can manage the external subscription data of the UE in the UE's home network by the SNPN.
BRIEF DESCRIPTION OF THE DRAWINGS
In order to describe the manner in which advantages and features of the application can be obtained, a description of the application is rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. These drawings depict only example embodiments of the application and are not therefore to be considered limiting of its scope.
FIG. 1 is a flow chart illustrating a method for a SNPN to manage the external subscription data owned by a 3 rd party entity according to an embodiment of the present application;
FIG. 2 is a flow chart illustrating a method for a SNPN to manage the external subscription data of a UE owned by a 3 rd party entity according to another embodiment of the present application;
FIG. 3 is a flow chart illustrating a method for a SNPN to manage the  external subscription data owned by a 3 rd party entity according to yet another embodiment of the present application;
FIG. 4 illustrates an apparatus according to some embodiments of the present application; and
FIG. 5 illustrates an apparatus according to some other embodiments of the present application.
DETAILED DESCRIPTION
The detailed description of the appended drawings is intended as a description of preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present application.
Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architecture and new service scenarios, such as 3GPP 5G. It is contemplated that along with developments of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems; and moreover, the terminologies recited in the present application may change, which should not affect the principle of the present application.
As discussed above, currently, it is feasible to communicate between the SNPN and the 3 rd party entity for authentication and authorization for the UE.
For example, in a solution, the 3 rd party entity is deployed as 5G system, e.g., PLMN or SNPN. When the UE is in a visited-SNPN (V-SNPN) , the V-SNPN can retrieve the subscription data of the UE from a unified data management (UDM) in the 3 rd party entity via some direct interfaces. However, this solution is only for the  3 rd party entity deployed as 5G system with a UDM and having the interface (s) to the SNPN. However, in the embodiments of the present application, it assumes that the 3 rd party entity is an entity not deployed as 5G system or not deployed the UDM but only an AAA server. Currently, there is no interface for exchanging the subscription data between the SNPN and the AAA server.
In another solution, there are two identities (IDs) for a UE. One is subscription ID (SI) created by the SNPN which is used for internal network operations towards UDM or a unified data repository (UDR) . The other is an identity of the UE (also called UE ID) allocated by the 3 rd party entity which is used for primary authentication and authorization between UE and the 3 rd party entity. In this solution, an access and mobility management function (AMF) has to maintain the mapping relationship between the two IDs. And during all the procedures, e.g., registration, PDU session establishment, the AMF in the SNPN has to firstly find the SI by mapping the UE ID, and then to finish the rest of the procedures. It is complicated and almost all of the procedures are impacted.
In the embodiments of the present application, some methods for a SNPN to manage external subscription data of a UE owned by a 3 rd party entity are described. In the embodiments of the present application, the 3 rd party entity is a home network of the UE, and the AAA server in the 3 rd party entity is an example of an entity storing the subscription data of the UE in the home network of the UE. It should be understood that another entity storing the subscription data of the UE may replace the AAA server to perform its operations in the following embodiments of the present application.
FIG. 1 is a flow chart illustrating a method for a SNPN to manage the external subscription data owned by a 3 rd party entity according to an embodiment of the present application.
In this embodiment, an AAA server in the 3 rd party entity triggers an external subscription registration of a UE by using a new interface between a UDM in the SNPN and the AAA server, when the UE accesses the SNPN (or called the serving SNPN) . The AAA server in the 3 rd party entity stores the subscription data of the UE.
As shown in FIG. 1, the SNPN includes an access network (AN) , an AMF, and a UDM. The SNPN in FIG. 1 may also include a UDR for storing and retrieving the subscription data for the UDM. Although the AN, the AMF, and the UDM being included in the SNPN are illustrated in FIG. 1 for concise, it should be understood that the SNPN may include other function entities.
The AN may be configured to provide a network access service for the UE. AN entity may also be referred to as radio access network (RAN) entity, an access point, an access terminal, a base, a macro cell, a Node-B, an enhanced Node B (eNB) , a gNB, a home Node-B, a relay node, or any device described using other terminology used in the art.
The AMF, the UDM and the UDR are network function entities of a 5G core network. In particular, the AMF is a network function entity used for receiving all the connection and session information from a UE or the AN and handling connection and mobility management tasks. The UDM is a network function entity used for managing network user data in a single, centralized element. The UDR is a converged repository of subscriber information and can be used to service a number of network functions. For example, in the embodiments of the present application, the UDM can use the UDR to store and retrieve subscription data of a UE.
The UE may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., television connected to the Internet) , a set-top box, a game console, a security system (including a security camera) , a vehicle on-board computer, a network device (e.g., a router, a switch, and a modem) , or the like. According to an embodiment of the present disclosure, the UE may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network. In some embodiments, the UE may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, or the like. Moreover, the UE may be referred to as a subscriber unit, a mobile phone, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a  subscriber station, a user terminal, or any device described using other terminology used in the art.
As shown in FIG. 1, in step 101, the UE initiates a registration request including an identity of the UE (UE ID) in the 3 rd party to the serving SNPN, that is, the AN of the SNPN. After receiving the registration request, in step 102, the AN transmits the registration request including the UE ID to the AMF.
In step 103, an external authentication and authorization is successfully performed between the UE and the AAA server in the 3 rd party entity.
Once the authentication and authorization is successful, in step 104, the AAA server determines to send an external subscription registration request for the UE to the UDM in the serving SNPN based on a 3 rd party policy or a service agreement with the serving SNPN via for example, the new interface between the UDM and the AAA server. The external subscription registration request may include the UE ID and the external subscription data for the UE. The external subscription data may include access and mobility related subscription data and session management related subscription data. Furthermore, the external subscription data may further include policy related subscription data and/or slice related subscription data.
In this embodiment, since the 3 rd party entity has a service agreement with other networks (e.g., the serving SNPN) , the 3 rd party entity will create and maintain a set of subscription data of UE that is suitable for the serving network.
After receiving the external subscription registration request, in step 105, the UDM determines whether the external subscription registration request with the received external subscription data from the 3 rd party entity is allowed based on a local policy of the SNPN and/or the agreement with the 3 rd party entity.
Upon determining the registration request is allowed and completing the registration successfully, in step 106, the UDM transmits an external subscription registration response to the AAA server. The external subscription registration response may include the UE ID and an external subscription registration result. Since the UDM determines the registration request is allowed and completes the  registration successfully, the UDM may generate the external subscription registration result as accepting; otherwise, the external subscription registration result is rejecting.
Upon receiving the external subscription registration response, the AAA server may update the state of the subscription data of the UE related to the serving SNPN.
In step 107, the UDM will wait to feedback the request from the AMF until the external subscription registration is completed when the UDM is performing the external subscription registration. More details regarding the step 107 are the same as the steps 14a-14c in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
In step 108, the serving SNPN transmits a registration accept message including necessary parameters to the UE, and the UE transmits a registration complete message to the serving SNPN if needed, more details are the same as the steps 15-24 in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
FIG. 2 is a flow chart illustrating a method for a SNPN to manage the external subscription data of a UE owned by a 3 rd party entity according to another embodiment of the present application.
In this embodiment, the UDM in the serving SNPN triggers an external subscription registration of a UE by using a new interface between the UDM in the SNPN and an AAA server in the 3 rd party entity, when the UE accesses the SNPN (the serving SNPN) . The AAA server in the 3 rd party entity stores the subscription data of the UE.
As shown in FIG. 2, the SNPN includes an AN, an AMF, and a UDM. The SNPN in FIG. 2 may also include a UDR for storing and retrieving the subscription data for the UDM. Although the AN, the AMF, and the UDM being included in the SNPN are illustrated in FIG. 2 for concise, it should be understood that the SNPN may include other function entities.
As shown in FIG. 2, in step 201, the UE initiates a registration request including an identity of the UE (UE ID) in the 3 rd party to the serving SNPN, that is, the AN of the SNPN. After receiving the registration request, in step 202, the AN transmits the registration request including the UE ID to the AMF.
In step 203, an external authentication and authorization is successfully performed between the UE and the AAA server in the 3 rd party entity.
In step 204, the AMF transmits a Nudm_SDM_Get request including the UE ID to the UDM selected by the AMF so as to retrieve the subscription data of the UE from the UDM.
After receiving the Nudm_SDM_Get request including the UE ID, the UDM determines whether there is the subscription data of the UE corresponding to the UE ID included in the Nudm_SDM_Get request. In step 205, if there is no subscription data of the UE, the UDM determines to retrieve external subscription data of the UE from the AAA server in the 3 rd party entity based on a local policy of the SNPN and/or the agreement with the 3 rd party entity.
In step 206, the UDM transmits an external subscription retrieve request to the AAA server in the 3 rd party entity via for example, the new interface between the UDM and the AAA server. The external subscription retrieve request may include the UE ID and an identity of the SNPN (SNPN ID) .
After receiving the external subscription retrieve request, the AAA server in the 3 rd party entity determines whether the request is allowed based on a local policy of the 3 rd party entity or a service agreement with the serving SNPN. If the request is allowed, in step 207, the AAA server transmits an external subscription retrieve response including the UE ID and the external subscription data of the UE to the UDM. The external subscription data may include access and mobility related subscription data and session management related subscription data. Furthermore, the external subscription data may further include policy related subscription data and/or slice related subscription data.
Otherwise, if the request is not allowed, the AAA server may transmit an  external subscription retrieve response including the UE ID and a result indicating rejecting.
In step 208, the UDM registers the UE with the received external subscription data of the UE.
And then in step 209, the UDM transmits a Undm_SDM_Get response including the UE ID and the required subscription data of the UE to the AMF.
Meanwhile, in step 210, the UDM may transmit an external subscription registration notification including the UE ID and the registration result to the AAA server. In this embodiment, the UDM registers the UE with the external subscription data of the UE, thus the registration result is accepting; otherwise, the registration result is rejecting.
In step 211, the serving SNPN transmits a registration accept message including necessary parameters to the UE, and the UE transmits a registration complete message to the serving SNPN if needed, more details are the same as the steps 15-24 in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
FIG. 3 is a flow chart illustrating a method for a SNPN to manage the external subscription data owned by a 3 rd party entity according to yet another embodiment of the present application.
In this embodiment, an AAA server in the 3 rd party entity triggers an external subscription registration of a UE by using an AMF in the SNPN as a proxy, when the UE accesses the SNPN (the serving SNPN) . The AAA server in the 3 rd party entity stores the subscription data of the UE. In this embodiment, there is a new interface between the AMF and the AAA server. The message between the AMF and the AAA server (for example, the messages communicated in  steps  304 and 309 in FIG. 3) can be directly transferred via the new interface. In another embodiment, the message between the AMF and the AAA server can be indirectly transferred via other network function entities (such as, a network exposure function (NEF) entity, authentication server function (AUSF) entity, a proxy of AAA server) .
As shown in FIG. 3, the SNPN includes an AN, an AMF, and a UDM. The SNPN in FIG. 3 may also include a UDR for storing and retrieving the subscription data for the UDM. Although the AN, the AMF, and the UDM being included in the SNPN are illustrated in FIG. 3 for concise, it should be understood that the SNPN may include other function entities, for example, the NEF, the AUSF, and so on.
As shown in FIG. 3, in step 301, the UE initiates a registration request including an identity of the UE (UE ID) in the 3 rd party to the serving SNPN, that is, the AN of the SNPN. After receiving the registration request, in step 302, the AN transmits the registration request including the UE ID to the AMF.
In step 303, an external authentication and authorization is successfully performed between the UE and the AAA server in the 3 rd party entity via the AMF.
Once the authentication and authorization is successful, in step 304, the AAA server determines to send an external subscription registration request for the UE to the AMF in the serving SNPN based on a 3 rd party policy or a service agreement with the serving SNPN via for example, the new interface between the AMF and the AAA server. The external subscription registration request includes the UE ID and the external subscription data for the UE. The external subscription data may include access and mobility related subscription data and session management related subscription data. Furthermore, the external subscription data may further include policy related subscription data and/or slice related subscription data.
In this embodiment, since the 3 rd party entity has a service agreement with other networks (e.g., the serving SNPN) , the 3 rd party entity will create and maintain a set of subscription data of UE that is suitable for the serving network.
After receiving the external subscription registration request, in step 305, the AMF determines the external subscription registration request is allowed based on a local policy of the SNPN and/or the agreement with the 3 rd party entity. In another embodiment, if the AMF determines the external subscription registration request is not allowed, for example, based on the local policy or there is no agreement with the 3 rd party entity, the AMF may transmit a rejecting message as a response to the request to the AAA server.
Upon determining the external subscription registration request is allowed, in step 306, the AMF transmits the external subscription registration request including the UE ID and the external subscription data for the UE to the UDM.
In step 307, the UDM registers the UE with the UE ID and the received subscription data. For example, the UDM may store the received subscription data of the UE in the UDR.
After completing the registration successfully, in step 308, the UDM transmits an external subscription registration response to the AMF. The external subscription registration response may include the UE ID and the external subscription registration result. Since the UDM completes the registration successfully, the external subscription registration result indicates accepting; otherwise, the external subscription registration result indicates rejecting.
After receiving the external subscription registration response, in step 309, the AMF transmits the external subscription registration response including the UE ID and the external subscription registration result to the AAA server, for example, via the new interface. The AAA server may update the state of the subscription data of the UE related to the serving SNPN.
And then in step 310, the AMF may transmit a registration accept message to the UE. In particular, the serving SNPN transmits the registration accept message including necessary parameters to the UE, and the UE transmits a registration complete message to the serving SNPN if needed, more details are the same as the steps 15-24 in Figure 4.2.2.2.2-1 (Registration procedure) in section 4.2.2.2.2 in 3GPP 23.502, which will not be described in detail here.
Therefore, through the above described embodiments of the present application, it is possible for the SNPN to support the UE with external subscription data owned by a 3 rd party entity by registering the external subscription data from the 3 rd party entity to the UDM in the SNPN, so that the SNPN can manage the external UE as a native UE.
FIG. 4 illustrates an apparatus according to some embodiments of the present  application. In some embodiments of the present disclosure, the apparatus 400 may be the UDM illustrated in the above embodiments of the present application.
As shown in FIG. 4, the apparatus 400 may include a receiver 401, a transmitter 403, a processer 405, and a non-transitory computer-readable medium 407. The non-transitory computer-readable medium 407 has computer executable instructions stored therein. The processer 405 is configured to be coupled to the non-transitory computer readable medium 407, the receiver 401, and the transmitter 403. It is contemplated that the apparatus 400 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements. In some embodiments of the present application, the receiver 401 and the transmitter 403 are integrated into a single device, such as a transceiver. In certain embodiments, the apparatus 400 may further include an input device, a memory, and/or other components.
In some embodiments of the present application, the non-transitory computer-readable medium 407 may have stored thereon computer-executable instructions to cause a processor to implement the processes performed by the UE in the above methods according to embodiments of the present application.
FIG. 5 illustrates an apparatus according to some other embodiments of the present application. In some embodiments of the present disclosure, the apparatus 500 may be the AMF illustrated in the above embodiments of the present application.
As shown in FIG. 5, the apparatus 500 may include a receiver 501, a transmitter 503, a processer 505, and a non-transitory computer-readable medium 507. The non-transitory computer-readable medium 507 has computer executable instructions stored therein. The processer 505 is configured to be coupled to the non-transitory computer readable medium 507, the receiver 501, and the transmitter 503. It is contemplated that the apparatus 500 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements. In some embodiments of the present application, the receiver 501 and the transmitter 503 are integrated into a single device, such as a transceiver. In certain embodiments, the apparatus 500 may further include an input device, a memory, and/or other components.
In some embodiments of the present application, the non-transitory computer-readable medium 507 may have stored thereon computer-executable instructions to cause a processor to implement the processes performed by the AMF in the above methods according to embodiments of the present application.
Persons skilled in the art should understand that as the technology develops and advances, the terminologies described in the present application may change, and should not affect or limit the principle and spirit of the present application.
Those having ordinary skill in the art would understand that the steps of a method described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
While this disclosure has been described with specific embodiments thereof, it is evident that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in the other embodiments. Also, all of the elements of each figure are not necessary for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the disclosure.
In this document, the terms "comprises, " "comprising, " or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "a, " "an, " or the  like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element. Also, the term "another" is defined as at least a second or more. The terms "including, " "having, " and the like, as used herein, are defined as "comprising. "

Claims (15)

  1. A method performed by a data management entity, comprising:
    receiving external subscription data for a user equipment (UE) from a home network of the UE;
    registering the UE with the received external subscription data; and
    generating and transmitting the external subscription registration result to the home network of the UE.
  2. The method of Claim 1, wherein receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from the home network of the UE, and
    wherein transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration response including the identity of the UE and the external subscription registration result to the home network of the UE.
  3. The method of Claim 2, wherein registering the UE with the received external subscription data further comprises: determining to register the UE with the received external subscription data based on a local policy of a non-public network after receiving the external subscription registration request.
  4. The method of Claim 1, wherein receiving the external subscription data for the UE comprises: receiving an external subscription retrieve response including an identity of the UE and the external subscription data for the UE from the home network of the UE, and
    wherein transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration  notification including the identity of the UE and the external subscription registration result to the home network of the UE.
  5. The method of Claim 4, wherein the method further comprises:
    before receiving the external subscription retrieve response, determining to retrieve the external subscription data for the UE from the home network of the UE based on a local policy of a non-public network; and
    transmitting an external subscription retrieve request including an identity of the UE and an identity of the non-public network to the home network of the UE.
  6. The method of Claim 1, wherein receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from an access and mobility management function entity, and
    wherein transmitting the external subscription registration result to the home network of the UE comprises: transmitting an external subscription registration response including the identity of the UE and the external subscription registration result to the access and mobility management function entity.
  7. The method of claim 1, wherein the external subscription data comprises:
    access and mobility related subscription data; and
    session management related subscription data.
  8. The method of claim 7, wherein the external subscription data further comprises at least one of:
    policy related subscription data; and
    slice related subscription data.
  9. A method performed by an access and mobility management function entity, comprising:
    receiving external subscription data for a user equipment (UE) from a home network of the UE;
    determining whether to register the external subscription data for the UE to a data management entity; and
    transmitting an external subscription registration request to the data management entity in response to determining to register the external subscription data for the UE to the data management entity.
  10. The method of claim 9, wherein receiving the external subscription data for the UE comprises: receiving an external subscription registration request including an identity of the UE and the external subscription data for the UE from the home network of the UE.
  11. The method of claim 9, further comprising:
    receiving an external subscription registration response including an identity of the UE and an external subscription registration result from the data management entity; and
    transmitting the external subscription registration response including the identity of the UE and the external subscription registration result to the home network of the UE.
  12. The method of claim 9, wherein the external subscription data comprises:
    access and mobility related subscription data; and
    session management related subscription data.
  13. The method of claim 12, wherein the external subscription data further comprises at least one of:
    policy related subscription data; and
    slice related subscription data.
  14. An apparatus, comprising:
    at least one non-transitory computer-readable medium having computer executable instructions stored therein;
    at least one receiver;
    at least one transmitter; and
    at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter;
    wherein the computer executable instructions are programmed to implement a method according to any one of Claims 1-8 with the at least one receiver, the at least one transmitter and the at least one processor.
  15. An apparatus, comprising:
    at least one non-transitory computer-readable medium having computer executable instructions stored therein;
    at least one receiver;
    at least one transmitter; and
    at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter;
    wherein the computer executable instructions are programmed to implement a method according to any one of Claims 9-13 with the at least one receiver, the at least one transmitter and the at least one processor.
PCT/CN2020/104468 2020-07-24 2020-07-24 Method and apparatus for managing external subscription data WO2022016512A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/104468 WO2022016512A1 (en) 2020-07-24 2020-07-24 Method and apparatus for managing external subscription data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/104468 WO2022016512A1 (en) 2020-07-24 2020-07-24 Method and apparatus for managing external subscription data

Publications (1)

Publication Number Publication Date
WO2022016512A1 true WO2022016512A1 (en) 2022-01-27

Family

ID=79729724

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/104468 WO2022016512A1 (en) 2020-07-24 2020-07-24 Method and apparatus for managing external subscription data

Country Status (1)

Country Link
WO (1) WO2022016512A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018138656A1 (en) * 2017-01-24 2018-08-02 Tata Communications (Uk) Limited Accessing a privately hosted application from a device connected to a wireless network
CN109429214A (en) * 2017-07-17 2019-03-05 华为技术有限公司 Service conversation method for building up, equipment and system
WO2020003576A1 (en) * 2018-06-25 2020-01-02 Nec Corporation A method and system of indicating sms subscription to the ue upon change in the sms subscription in a network
WO2020036401A1 (en) * 2018-08-13 2020-02-20 삼성전자 주식회사 Apparatus and method for registration on network in wireless communication system
US20200112841A1 (en) * 2018-10-05 2020-04-09 Samsung Electronics Co., Ltd. Method and apparatus for providing information for vehicle communication services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018138656A1 (en) * 2017-01-24 2018-08-02 Tata Communications (Uk) Limited Accessing a privately hosted application from a device connected to a wireless network
CN109429214A (en) * 2017-07-17 2019-03-05 华为技术有限公司 Service conversation method for building up, equipment and system
WO2020003576A1 (en) * 2018-06-25 2020-01-02 Nec Corporation A method and system of indicating sms subscription to the ue upon change in the sms subscription in a network
WO2020036401A1 (en) * 2018-08-13 2020-02-20 삼성전자 주식회사 Apparatus and method for registration on network in wireless communication system
US20200112841A1 (en) * 2018-10-05 2020-04-09 Samsung Electronics Co., Ltd. Method and apparatus for providing information for vehicle communication services

Similar Documents

Publication Publication Date Title
US11388661B2 (en) Network slice configuration update
US20220110023A1 (en) Method, Apparatus, and System for Managing Background Data Transfer Policy
CN113709830A (en) Enhancements for processing network slice quotas
EP3758404A1 (en) Configuration information acquisition method, apparatus and device, and storage medium and system
US12034621B2 (en) Communication method, and communication apparatus and system
US20220225095A1 (en) External Authentication Method, Communication Apparatus, and Communication System
US20230239938A1 (en) Determining a default network slice
US20230048066A1 (en) Slice authentication method and apparatus
WO2021161193A1 (en) Registered ue count in slice service area
WO2018076553A1 (en) Method and device for accessing network
WO2022153256A1 (en) Redirection and retry of registration
US20230156457A1 (en) Method and apparatus for providing onboarding and provisioning services
CN115299168A (en) Method and apparatus for handover
WO2021088007A1 (en) Wireless communication method, terminal device, and network device
WO2021028193A1 (en) Slice selection subscription data enhancement
WO2022016512A1 (en) Method and apparatus for managing external subscription data
US20240323708A1 (en) Network slice quotas in the presence of interworking
WO2022021139A1 (en) Method and apparatus for subscribing and provisioning
CN114080000B (en) Network slice determination method and device, core network equipment and terminal
WO2021201729A1 (en) Faster release or resume for ue in inactive state
WO2022021155A1 (en) Method and apparatus for managing access control information
RU2816700C1 (en) Method and device of network connection in real time
WO2023151420A1 (en) Communication method and communication apparatus
US20240107287A1 (en) Support of non-subscribed temporary local slices while roaming for local ims service
US20230179597A1 (en) Access control method, access control apparatus, and communications device

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: 20946413

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 16/05/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20946413

Country of ref document: EP

Kind code of ref document: A1