Method and apparatus for providing localized services subscription information in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method by the communication system comprises determining, a user equipment (UE), subscription data for the UE and UE location, filtering, a hosting network to be provided to the UE, based on the subscription data for the UE and the UE location, transmitting, to the second network entity, a request including at least one of a UE identifier, UE location information, or information on a localized service, and receiving, from the second network entity, information on the hosting network based on the request.

Description

METHOD AND APPARATUS FOR PROVIDING LOCALIZED SERVICES SUBSCRIPTION INFORMATION IN A WIRELESS COMMUNICATION SYSTEM

[0001] The disclosure relates to a wireless communication system. More particularly, the disclosure relates to an apparatus and method for providing localized services subscription information in a wireless communication system.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below.

[0009] Additional aspects will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the presented embodiments.

[0010] In accordance with an aspect of the disclosure, a method by a first network entity in a wireless communication, the method comprising: determining, a user equipment (UE), subscription data for the UE and UE location; filtering, a hosting network to be provided to the UE, based on the subscription data for the UE and the UE location; transmitting, to the second network entity, a request including at least one of a UE identifier, UE location information, or information on a localized service; and receiving, from the second network entity, information on the hosting network based on the request.

[0011] In an embodiment, further comprising: transmitting, to an access and mobility management function (AMF), the subscription data for the UE and the UE location; and receiving, from the AMF, location information for one or more UEs in the area of interest.

[0012] In an embodiment, further comprising: receiving, from a network exposure function (NEF), a message including at least one of the UE identifier, or the information on the localized service.

[0013] In an embodiment, wherein the information on the hosting network is generated based on the request, and wherein the information on the hosting network includes at least one of a list of hosting network identifier, credentials, or validity information.

[0014] In accordance with another aspect of the disclosure, a method by a second network entity in a wireless communication, the method comprising: receiving, from a first network entity, a request including at least one of a user equipment (UE) identifier, UE location information, or information on a localized service; and transmitting, to the first network entity, information on a hosting network based on the request, wherein the UE, subscription data for the UE and UE location are determined by the first network entity, and wherein the hosting network to be provided to the UE are filtered based on the subscription data for the UE and the UE location.

[0015] In accordance with another aspect of the disclosure, a first network entity in a wireless communication, the first network entity comprising: a transceiver; and a controller coupled with the transceiver and configured to: determine, a user equipment (UE), subscription data for the UE and UE location, filter, a hosting network to be provided to the UE, based on the subscription data for the UE and the UE location, transmit, to the second network entity, a request including at least one of a UE identifier, UE location information, or information on a localized service, and receive, from the second network entity, information on the hosting network based on the request.

[0016] In accordance with another aspect of the disclosure, a second network entity in a wireless communication, the second network entity comprising: a transceiver; and a controller coupled with the transceiver and configured to: receive, from a first network entity, a request including at least one of a user equipment (UE) identifier, UE location information, or information on a localized service, and transmit, to the first network entity, information on a hosting network based on the request, wherein the UE, subscription data for the UE and UE location are determined by the first network entity, and wherein the hosting network to be provided to the UE are filtered based on the subscription data for the UE and the UE location.

[0017] Advantageously, various embodiments of the disclosure minimize changes to the UE synchronization procedure.

[0018] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0019] According to an embodiment of the disclosure, terminal configuration information can be managed more efficiently in a wireless communication system.

[0020] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0021] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0022] Figure 1 is a diagram illustrating a typical scenario according to an embodiment of the disclosure;

[0023] Figure 2A is a procedure illustrating steering of roaming procedure;

[0024] Figure 2B is a procedure illustrating steering of roaming procedure;

[0025] Figure 3 is a diagram illustrating a solution 1 according to an embodiment of the disclosure;

[0026] Figure 4A is a procedure illustrating a solution 2 according to an embodiment of the disclosure;

[0027] Figure 4B is a procedure illustrating a solution 2 according to an embodiment of the disclosure;

[0028] Figure 5 is a procedure illustrating a solution 3 associated with a Solution 2 without NEF according to an embodiment of the disclosure;

[0029] Figure 6A is a procedure illustrating a solution 4 associated with the solution 1 with LSP-F interacting with UDR according to an embodiment of the disclosure;

[0030] Figure 6B is a procedure illustrating a solution 4 associated with the solution 1 with LSP-F interacting with UDR according to an embodiment of the disclosure;

[0031] Figure 7 shows a diagram illustrating a structure of a network entity according to an embodiment of the disclosure.

[0032] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.

[0033] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0034] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

[0035] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0036] In the 3rdgeneration partnership project (3GPP) standards, 5G network system architectures and procedures are standardized. A mobile communication network operator may provide various services in a 5G network. In order to provide each service, the mobile communication network operator may have to satisfy different service requirements (e.g., latency, communication range, data rate, bandwidth, reliability, or the like). To this end, the mobile communication network operator may configure network slices, and may allocate an appropriate network resource for a particular service according to each of the network slices or according to a set of a network slice. The network resource may indicate a network function (NF), a logical resource provided by the NF, or radio resource allocation by a base station (BS).

[0037] For example, the mobile communication network operator may configure a network slice A to provide a mobile broadband service, may configure a network slice B to provide a vehicle communication service, and may configure a network slice C to provide an Internet of things (IoT) service. For example, in the 5G network, each service may be provided on a dedicated network slice according to features of each service. As a differentiator for differentiating network slices, single-network slice selection assistance information (S-NSSAI) defined in the 3GPP may be used.

[0038] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include computer-executable instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0039] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphical processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a wireless-fidelity (Wi-Fi) chip, a BluetoothTMchip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display drive integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0040] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth®chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display drive integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an integrated circuit (IC), or the like.

[0041] <Definitions and Abbreviations used in the disclosure>

[0042] - Localized service: A service which may be bounded in terms of time or location. These services can be in the form of connectivity (UE having connection to a specific Data Network).

[0043] - Hosting network: A network (usually a private network) which provides access to Localized services.

[0044] - LSP (Localized Service Provider): it may be the network operator, or a special service provider (e.g. streaming service such that hosting network provides access to special DNN for the particular streaming service) that has relationship with one or more Hosting networks to provide a particular Localized service.

[0045] - LSP-F (Localized Service Provider - Function): A Network Entity (which is controlled by Localized Service Provider) which provides functionality to provide UE's Home Network or UE's Serving Network the information related to UE's Subscription data related to Localized Services and Hosting Network that provides those Localized services.

[0046] - Steering of Roaming: A procedure through which a home network or Credentials Holder can provide UE the information regarding the preferred network to select to.

[0047] - SoR-AF: Steering of Roaming - Application Function

[0048] - Hosting Network selection: Network selection performed by UE to connect and register to a Hosting Network in order to avail localized services.

[0049] A UE can be subscribed to multiple Localized services. A UE can have a relationship with a particular Localized service provider, to access the localized services through particular Hosting networks that provide those Localized services.

[0050]

[0051] Figure 1 is a diagram illustrating a typical scenario according to an embodiment of the disclosure. A typical scenario is depicted in Figure 1. UE has a subscription with the home network A. There is an event in the stadium where Hosting network C provides good quality of service. Localized service provider has relationship with Hosting network C in the stadium in order to provide the viewers of the match the particular Localized service (getting access to Hosting network C and enjoying better QoS). The Home network may get into service agreement with the Localized service provider so as toto provide its UE(s) access to Hosting network C services.

[0052]

[0053] Figure 2A and Figure 2B are a procedure illustrating steering of roaming procedure. Referring to Figure 2A and Figure 2B, Steering of Roaming (SoR) in 5G is a mechanism that allows mobile network operators to influence the selection of a preferred roaming partner for their subscribers when they are outside their home network's coverage area. In the case for SNPN, they are configured and can be updated using SoR by the UE's home network to guide the UE's network selection area where SNPNs (to which UE is subscribed to) are available. Currently, in order to provide UE with the information related to selecting Hosting Networks for localized services, steering of roaming procedure is used as described Figure 2A and Figure 2B. The disadvantages of the procedure are:

[0054] 1. An external entity (for e.g. LSP-F) cannot provide network the dynamic information related to Localized services that is it cannot update information regarding UE's subscribed Localized services or UE's subscribed Hosting Networks

[0055] 2. When providing UE the information related to selected Hosting Networks, it does not take into account the UE's location. For e.g. UE need not be provided the information of those Hosting Networks that are not available in the area close to UE's location.

[0056]

[0057] <Scenario and Issue>

[0058] A UE has subscription to one or more Localized services. Those Localized services are provided by different Hosting Networks. Each LSP know which Hosting Networks provide which all localized services and at what locations and at what time they provide those services.

[0059] Now we assume that the LSP-F (controlled by some LSP) has relationship with the UE's Home network. We want that LSP-F can provide the home network information regarding Localized services (which includes the Hosting Network that provides that Localized services and the validity conditions corresponding to the Localized services).

[0060] Furthermore, UE should not be provided the information for all the Hosting Networks corresponding to the Localized services that UE has subscribed to. The Hosting Network information provided to the UE should take into account the current geographical location of the UE as well.

[0061]

[0062] Figure 3 is a diagram illustrating a solution 1 according to an embodiment of the disclosure. Referring to Figure 3, a solution 1 is associated with a procedure "LSP-F and UDM (Unified Data Management) interaction, UDM and Hosting Network sponsor interaction".

[0063] The overall procedure is to provide the UE's Home Network, the information relates to a UE's subscribed Localized services.

[0064] An LSP-F provide the information related to localized services for example the Hosting Networks that provide the Localized services and the validity conditions for the localized services to the UDM.

[0065] Note that the information provided by the Localized service provider may or may not include a UE identifier, that is LSP-AF can just provide the information related to Localized services, and the Home Network policies decides which UEs will be able to avail those localized services or not.

[0066] Multiple LSP-F may request to store the information for the same UE in the UDM. These LSP-F(s) may provide the information for different Localized Services (identified by different Localized Service IDs).

[0067] After the information is provided to the UDM it may use the UE's location and take help of the entity Hosting Network Sponsor to generate the appropriate Hosting Network information that need to be finally delivered to the UE.

[0068] Hosting Network sponsor can be an operator controlled entity. It can consider the UE location and the UE's subscribed Hosting network (UE's subscribed Hosting network based on UE'sit's subscribed Localized services) and perform prioritization (according to operator policies) and generate a final list of Hosting networks that need to be delivered to the UE.

[0069] In this procedure UDM stores any mapping between the UE identifier used within the UE's serving network and the identifier used for UE identification between UDM and the LSP-F

[0070] First of all, Step 300. UE is registered to the network where an access and mobility management function (AMF) in the procedure resides.

[0071] Step 301. LSP-F to a network exposure function (NEF): Nnef_ParameterProvision_Create; The LSP-F provides the Localized service information to the NEF, so as to provide the Network, information related to a particular Localized service(s) where localized service may be identified by a Localized Service ID. The request may include a UE identifier in which case Network would determine the information is for a particular UE. Alternatively, the information provided by LSP-F can be without a UE identifier also, in which case the Home Network of the UE itself will determine which UEs are subscribed to the particular Localized services.

[0072] Step 302. NEF to UDM: Nudm_ParameterProvision _Create; Based on the received request from the LSP-F, NEF may find the corresponding UE identifier used internally in the network for which the information provided in Step 301 is targeted to and then proceed to send the information to the appropriate UDM.

[0073] Step 303. UDM operation; UDM determines the UEs based on the information received in Step 302, and updates the subscription data for the UEs corresponding to the Localized services subscribed by a UE.

[0074] Based on the validity conditions of the Localized services provided to the UDM in step 302 or configured in UDM, UDM subscribed for UE location via the UE's serving AMF.

[0075] Alternatively, UDM may contact a particular AMF to receive the information of all the UEs which are in a particular area, where that area is determined by the Location validity in Localized Service information.

[0076] Step 304. UDM to AMF; UDM subscribes the AMF for UE's (or UEs') location.

[0077] Step 305. UE moves to the area of interest and / or selects a SNPN and performs registration to it. When a UE moves in the particular area of interest or otherwise, UE or RAN shall communicate with the AMF regarding the location of the UE.

[0078] Step 306. UE / RAN towards the AMF, AMF is notified about UE's location.

[0079] Step 307. AMF to UDM; Based on the subscription in Step 304 or otherwise, AMF notifies the location information for one or more UEs in the area of interest.

[0080] Step 308. UDM operation; UDM based on UE location and the subscription information received in Step 302, filter the Hosting Networks that are to be provided to the UE and sends the information on Hosting Network Sponsor in Step 309.

[0081] Step 309. UDM to Hosting Network Sponsor: HostingNetworkList_get request; UDM requests the Hosting Network information from the Hosting Network sponsor by providing UE identifier, and / or UE location information and / or list of UE's subscribed Hosting network and their corresponding validity information.

[0082] Step 310. Hosting Network Sponsor operation; Based on the stored configuration and obtained information in Step 309, Hosting Network Sponsor generated Hosting Newark information to be transmitted to the requesting Network. It may take into account the UE location and / or the operator policies to prioritize particular Hosting Networks.

[0083] Step 311. Hosting Network Sponsor to UDM; Based on the operation in Step 310, Hosting Network sponsor sends UDM the corresponding Hosting Network Information.

[0084] Step 312. UDM to AMF; UDM forwards the list received in Step 311 towards AMF.

[0085] Step 313. AMF to UE Non-Access-Stratum (NAS) message; AMF forwards the information received in Step. 12 from UDM towards UE.

[0086] Further details regarding operation of UDM and Hosting Network sponsor are following:

[0087] Specifically, UDM operation with reference to Figure 3.

[0088] The below described UDM operation may be realized via other Network entities also and in scenarios / procedure other than those described in Figure 3.

[0089] Furthermore, the entities interacting with UDM (namely AMF / Hosting Network Sponsor / NEF) may be some other entities than those described below.

[0090] UDM in Step 302, receives from NEF, the message Nudm_ParameterProvision_Create Request with one or more parameters of: "Type: Localized service information", Localized Service Identifier, List of Hosting Network(s) that provides Localized services with validity condition, where validity condition may include Location validity info (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0091] UDM in Step 303, based on the message received in Step 302, determines the UEs and updates the subscription data for the UEs corresponding to the Localized services subscribed by a UE.

[0092] Based on the validity conditions of the Localized services provided to the UDM in step 302 or already configured in UDM, UDM subscribes for UE location via the UE's serving AMF (in Step 304) or notification for UE Registration.

[0093] Alternatively, UDM may contact a particular AMF to receive the information of all the UEs which are in a particular area, where that area is determined by the Location validity in Localized Service information.

[0094] UDM in Step 304, Based on the UDM operation in Step 303, sends to AMF the request including one or more parameters one or more of: Subscription Permanent Identifier (SUPI), Location information in order to trigger the AMF to notify the location of ta particular UE and / or receive the notification of UEs (along with their IDs) entering a particular area.

[0095] UDM in Step 307 may receive from AMF, as a response to Step 304 or otherwise, a message including: Either information of UE denoted by SUPI and UE's location information, or information of UE and indicating that it entered an area of interest, or, list of UEs (denoted by list of SUPIs) present in the Area of Interest.

[0096] Based on the UDM operation in Step 303 and received message in Step 307,

[0097] UDM in Step 308, filters the information that need to be provided to the Hosting Network Sponsor in order for the Hosting Network sponsor to provide UE with the appropriate Hosting Network List.

[0098] Alternatively, UDM in step 308 instead of performing any filtering just decides to request Hosting Network Sponsor for UE information regarding Hosting Network, based on the UE location, UDM may perform filtering of the Localized services and / or Hosting networks that need to be provided to the UE currently (for e.g. currently only those UEs).

[0099] UDM in Step 309, based on UDM operation in Step 308, sends Hosting Network Sponsor the message HostingNetworkList_Get request which includes one or more parameters of : SUPI, UE location information, Localized service information consisting of list of Localized service ID(s), Hosting Network(s) (identified by Public Land Mobile Network (PLMN) ID and / or NID) corresponding to Localized service ID, validity information corresponding to Localized Services, where validity condition may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0100] With TAI being Tracking Area Identity, comprising of MCC, MNC with Tracking Area Code (TAC).

[0101] As a response to the message UDM sent in Step 309, or otherwise:

[0102] UDM in Step 311, receives from Hosting Network Sponsor, the message HostingNetworkList_Get Response with one or more parameters of : a list of Hosting network ID(s) (PLMN ID and optionally NID), Credentials for the particular Hosting Network (may include SUPI or any identifiers that can be used by the UE in the particular Hosting network), validity information for corresponding Hosting Networks, where validity information may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0103] Based on the message received by UDM in Step 311,

[0104] UDM in Step 310, can transmit towards UE, (or transmit towards the Serving Network (AMF) of the UE), the message Nudm_SDM_Notification request, which includes one or more parameters of : SUPI, a list of Hosting network ID(s) (PLMN ID and optionally NID), Credentials for the particular Hosting Network (may include SUPI or any identifiers that can be used by the UE in the particular Hosting network), validity information for corresponding Hosting Networks, where validity information may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0105] Also, Hosting Network Sponsor operation with reference to Figure 3.

[0106] The below described Hosting Network Sponsor operation may be realized via other Network entities (such as SoR-AF) also and in scenarios / procedure other than those described in Figure 3.

[0107] Furthermore, the entities interacting with Hosting Network Sponsor (namely NEF / UDM / AUSF) may be some other entities than those described below.

[0108] Hosting Network Sponsor in Step 309, can receive from UDM, the message HostingNetworkList_Get request which includes one or more parameters of : SUPI, UE location information, Localized service information consisting of list of Localized service ID(s), Hosting Network(s) (identified by PLMN ID and / or NID) corresponding to Localized service ID, validity information corresponding to Localized Services, where validity condition may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0109] Based on the received information in Step 309, or otherwise,

[0110] Hosting network Sponsor in Step 310 consider the configured information for the UE (identified by SUPI or other identifier received in Step 309), and consider the information received in Step 309 to generate the Hosting Network Information relevant for UE.

[0111] Hosting Network Information may consist a list of Hosting network ID(s) (PLMN ID and optionally NID), Credentials for the particular Hosting Network (may include SUPI or any identifiers that can be used by the UE in the particular Hosting network), validity information for the corresponding Hosting Networks, where validity information may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information)

[0112] A particular Hosting network may provide multiple localized services, so based on operator's preferences for the Localized services and operator's preferences for the Hosting network's and also taking into account the validity information for different Localized services that are being offered by a particular Hosting network, Hosting Network sponsor creates Hosting network information.

[0113] Based on the Hosting Network sponsor operation in Step 310,

[0114] Hosting Network sponsor in Step 311, transmit towards UDM or towards the UE's Serving Network or towards UE the message including one or more of the parameters of : a list of Hosting network ID(s) (PLMN ID and optionally NID), Credentials for the particular Hosting Network (may include SUPI or any identifiers that can be used by the UE in the particular Hosting network), validity information for corresponding Hosting Networks, where validity information may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0115]

[0116] Figure 4A and Figure 4B are a diagram illustrating a solution 2 according to an embodiment of the disclosure. Referring to Figure 4A and Figure 4B, a solution 2 is associated with a procedure "LSP-F and Hosting Network Sponsor interaction".

[0117] In this procedure, the LSP-F instead of contacting the UDM (as in Figure 3) with the information related to Localized services, provide that information to the Hosting Network sponsor.

[0118] An LSP-F provide the information related to localized services for example the Hosting Networks that provide the Localized services and the validity conditions for the localized services to the Hosting Network Sponsor.

[0119] Hosting Network sponsor then based on request from UDM / AUSF provides the corresponding information received from LSP-F.

[0120] In case when NEF is not deployed LSP-F will directly contact the Hosting Network Sponsor. (Figure 5 and corresponding message flow between LSP-F and Hosting Network sponsor will happen without NEF).

[0121] Furthermore, this procedure can be used to communicate Subscription information other than Localized Service Subscription information as well, that is instead of Localized Service Subscription information, the container may contain some other kind of Subscription information to provide the UDM or the serving network of the UE, UE's Subscription information via Hosting Network sponsor.

[0122] This is useful for scenario when UE's subscription information is available at some entity (taking the role of LSP-F) and the Current serving network of the UE wants to request UE's subscription information but there is no relationship between UE's Serving network and the entity holding UE's current subscription.

[0123] Step 401a. LSP-F to NEF: Sending the information regarding the Localized Service Subscription Information.

[0124] Step 401b. NEF to Hosting Network Sponsor: NEF receives the request from LSP-F converts it to appropriate format, finds the appropriate entity to forwards to, and forward the request to it.

[0125] Step 402a. Hosting Network Sponsor to NEF: acknowledges the Request received in Step 401b.

[0126] Step 402b. NEF to LSP-F: Acknowledging the request that was received in Step. 1a. based on received response in Step 402a.

[0127] Step 403. Hosting Network Sponsor to UDM: Subscription for UE location whenever UDM requests for Hosting Network Information.

[0128] Step 404. UDM to AMF: UDM subscribes to AMF for UE location e.g. whenever UE goes into a particular area or the list of UEs that are in a particular area.

[0129] Step 405. UE performs registration to the network.

[0130] Step 406. NAS message UE to AMF: notifying the Network about the UE location and UE's intent to perform registration.

[0131] Step 407. AMF notifies the AUSF / UDM about UE registration and optionally UE location.

[0132] Step 408. AUSF / UDM receives the message from the AMF and decides to ask Hosting Network sponsor for UE's Hosting Network Information.

[0133] Step 409. AUSF / UDM to Hosting Network Sponsor: sending the request containing UE ID, UE location information so that Hosting Network Sponsor can provide the UE's subscription information related to Hosting Network Information.

[0134] Step 410. Hosting network service operation: Converts the UE Identifier received in Step 409 to the one which is used by LSP-F. Then it either directly sends the information for the UE as was received in Step 401b. or it may request to the LSP-F again for the updated UE's Localized Service Subscription Information

[0135] Step 411a. Hosting Network sponsor to NEF: Sends the request to NEF regarding request for UE's LS subscription.

[0136] Step 411b. NEF to LSP-F: NEF receives the request from Hosting Network sponsor converts it to appropriate format, finds the appropriate entity to forwards to, and forward the request to it.

[0137] Step 412a. LSP-F to NEF: Based on the request received in Step 411b. LSP-F send the appropriate Localized Service information corresponding to the UE identifier and / or Localized Service ID.

[0138] Step 412b. NEF to Hosting Network Sponsor: NEF receives the request from LSP-F converts it to appropriate format, finds the appropriate entity to forwards to, and forward the request to it.

[0139] Step 413. Hosting Network sponsor to AUSF / UDM.

[0140] Step 414. AUSF / UDM to AMF.

[0141] Step 415. AMF to UE NAS message containing Hosting network information including Hosting Network IDs, Validity information, along with credentials to use in particular Hosting Network).

[0142] UE is then able to utilize the Hosting Network Information to connect to the Hosting Networks for availing localized services.

[0143] Further details regarding operation of Hosting Network sponsor are following:

[0144] Hosting Network sponsor operation based on UE Figure 4A and Figure 4B

[0145] The below described Hosting Network Sponsor operation may be realized via other Network entities (such as SoR-AF) also and in scenarios / procedure other than those described in Figure 4A and Figure 4B.

[0146] Furthermore, the entities interacting with Hosting Network Sponsor (namely NEF / UDM / AUSF) may be some other entities than those described below.

[0147] Hosting Network sponsor in Step 401b, receives from NEF, the message Hosting Network_Association_Create Request with one or more parameters of: UE identifier, Localized Service Identifier, Hosting Network Information which includes, List of Hosting networks (identified by PLMN ID and or SNPN ID) that provides the Localized service, validity conditions for Localized Services, where validity condition may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information), other subscription related information for the UE identifier.

[0148] Alternatively, Hosting Network sponsor in Step 401b can receive a message with one or more parameters of: UE identifier, Localized Service Identifier, Hosting Network Information which includes, List of Hosting networks (identified by PLMN ID and or SNPN ID) that provides the Localized service, validity conditions for Localized Services, where validity condition may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0149] Based on the Message received in Step 401b, Hosting Network Sponsor updates it's configuration and stores the information related to UE and UE'sit's Subscription data related to Localized services and Hosting Networks.

[0150] Hosting Network Sponsor in Step 402a, as a response to message received in Step 401b, sends NEF the message HostingNetwork_CreateAssociation response as confirmation for receiving the information in Step 402a.

[0151] Based on the received information in Step 401b,

[0152] Hosting Network Sponsor in Step. 403, may send the message HostingNetworkUELocationNotification having one or more parameters of SUPI, Location information.

[0153] This message is for UDM of to provide or notify with UE location whenever requesting or Hosting Network information form the Hosting Network Sponsor.

[0154] Based on the subscription to UE location in Step 403, or otherwise when UE performs registration and UDM / AUSF decides to ask Hosting network Sponsor for UE subscription information related to Hosting Network information, and, Hosting Network Sponsor in Step 409, receives from the AUSF or UDM of the UE's serving network, the message HostingNetworkList_Get request, including one or more parameters of: UE SUPI or UE Subscription Concealed Identifier　(SUCI), UE location information.

[0155] Alternatively, Hosting Network Sponsor in Step 409, receives a message including one or more parameters of: "Indication for receiving UE subscription", UE SUPI or UE SUCI, UE location information.

[0156] Alternatively, Hosting Network Sponsor in Step 409, receives a message including one or more parameters of: UE SUPI or UE SUCI, UE location information.

[0157] Based on the received message in Step 409,

[0158] Hosting network sponsor in Step 410, generates the appropriate Hosting Network related information for the requested UE (identified by SUPI or SUCI) in the message received in Step. 9, the related information for the UE may be stored in the Hosting Network Sponsor as provided by LSP-F in Step 401a.

[0159] When receiving SUCI in Step 409, Hosting Network Sponsor may convert it to SUPI.

[0160] Furthermore, the identification of UE may be done by a different identifiers between AUSF / UDM (or UE's serving network) and the Hosting Network Sponsor, and between Hosting Network Sponsor and the LSP-F (or the entity where UE's (Localized) service subscription is stored).

[0161] Hosting Network sponsormay store a mapping between (as in table 1)the different UE identifiers which are used between Hosting Network Sponsor and Authentication Server Function　(AUSF) / UDM and in between the Hosting Network Sponsor and the LSP-F.

[0162] [Table 1]

[0163]

[0164] The UE identifiers used in the table 1 (A-UE ID1, A-UE ID 2, B-UE ID 1,...) may be realized via SUPI / Generic Public Subscription Identifier (GPSI) etc.

[0165] Hosting Network Sponsor may convert the UE id received in Step 409 to the one which is used between to Hosting Network Sponsor and the LSP-F to identify the same UE.

[0166] In addition, based on the configuration of Hosting Network sponsor, after converting the UE id provided in Step 409, Hosting Network Sponsor may send the response to the requesting entity (i.e. the entity requesting Step 409) based on the stored information for the UE, which was provided to the Hosting Network sponsor in Step 401b. In this case Hosting network sponsor will directly send the corresponding Hosting Network Information for the requested UE to the entity using the Step. 413, and Step 411a to Step 412b will be skipped.

[0167] Or it may proceed to request the LSP-F the UE's subscribed Localized service information (e.g. for getting updated information for a UE). In this case, Hosting network sponsor will convert the UE identifier received in Step 409 to the UE identifier which is used in between Hosting Network sponsor and the LSP-F and then proceed to request for UE's Localized Service subscription information in Step. 411a.

[0168] Based on the Hosting Network operation in Step 410,

[0169] Hosting Network Sponsor in Step 411a. sends to LSP-F (via NEF) the message, HostingNetwork_Association_Notification request containing one or more parameters of: UE identifier, Localized Service ID.

[0170] The UE identifier sent in the Step 411a, may be determined by Hosting NEtwrok sponsor in Step 410, using mapping information stored in Hosting network sponsor between the UE ID (SUPI / SUCI) received in Step 409 and UE ID to be transmitted to LSP-F.

[0171] Alternatively, Hosting Network Sponsor in Step 411a. sends a message, containing one or more parameters of: "Indication for receiving UE subscription", UE identifier, Localized Service ID.

[0172] Alternatively, Hosting Network Sponsor in Step 411a. sends a message, containing one or more parameters of: UE identifier, Localized Service ID.

[0173] Hosting Network sponsor in Step 412b, based on the message sent in Step 411a. receives the response from the LSP-F (via NEF) with the message HostingNetworkUpdateAssociation request including one or more parameters of: UE identifier, Localized Service Identifier, Hosting Network Information which includes, List of Hosting networks (identified by PLMN ID and or SNPN ID) that provides the Localized service, validity conditions for Localized Services, where validity condition may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information), other subscription related information for the UE identifier.

[0174] Alternatively, Hosting Network Sponsor in Step 412b, receives the message including one or more of the parameters: SUPI, container for subscription data.

[0175] Based on the operation in Step 410 and / or the received information in Step 412b,

[0176] Hosting Network sponsor in Step. 413, transmit towards UDM / AUSF or towards the UE's Serving Network or towards UE the message including one or more of the parameters of: SUPI, a list of Hosting network ID(s) (PLMN ID and optionally NID), Credentials for the particular Hosting Network (may include SUPI or any identifiers that can be used by the UE in the particular Hosting network), validity information for corresponding Hosting Networks, where validity information may include Location validity information (list of TAIs, geographical coordinates etc.), and / or time validity information (frequency of the event, start time / date information, ending time / date information).

[0177] Alternatively, Hosting Network Sponsor in Step 413, transmit towards UDM or AUSF or towards UE's serving network, the message including one or more of the parameters: SUPI, container for subscription data.

[0178]

[0179] Figure 5 is a procedure illustrating a solution 3 associated with a solution 2 without NEF according to an embodiment of the disclosure. Referring to Figure 5, a solution 3 is associated with a Procedure "Solution 2 without NEF".

[0180] The procedure described in Figure 5 is similar to the one described on Figure 4A and Figure 4B, without NEF. That is Steps 401a and 401b, Steps 402a and 402b, Steps 411a and 411b, and Step 412a and 412b will be merged together.

[0181] This procedure can also be used in scenarios where the Hosting network sponsor is outside the authority of UE's serving network, while there is a relationship between UE's serving network (or the operator controlling AUSF / UDM) and the Hosting Network Sponsor, and there is a relationship between Hosting network sponsor and the LSP-F. LSP-F can be any generic entity which holds the subscription for the UE and not just limited to holding information regarding Localized services related information.

[0182]

[0183] Figure 6A and Figure 6B are a procedure illustrating a solution 4 associated with the solution 1 with LSP-F interacting with Unified. Data Repository (UDR)according to an embodiment of the disclosure. Referring to Figure 6A and Figure 6B. a solution 4 is associated with a Procedure "Solution 1 with LSP-F interacting with UDR". The procedure depicted in Step 605 is similar to solution 1, but with LSP-F first provisioning the Localized Services information in the UDR (instead of UDM).

[0184]

[0185] Figure 7 is a diagram illustrating a structure of a network entity according to an embodiment of the disclosure.

[0186] Referring to Figure 7, the network entity may include a transceiver 710, a controller 720, and a storage unit 730. In the disclosure, the controller may be defined as a circuit, an application-specific integrated circuit, and at least one processor.

[0187] The transceiver 710 may transmit and receive a signal to / from another network entity.

[0188] The controller 720 may control general operations of the network entity according to embodiments proposed in the disclosure. For example, the controller 720 may control a signal flow between blocks to perform operations described with reference to the flowchart.

[0189] The storage 730 may store at least one of information transmitted and received through the transceiver 710 or information generated by the controller 720.

[0190]

[0191] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0192] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform a method of the disclosure.

[0193] Any such software may be stored in the form of volatile or non-volatile storage, such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory, such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium, such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0194] While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.

Claims

1.A method by a first network entity in a wireless communication, the method comprising:determining, a user equipment (UE), subscription data for the UE and UE location; filtering, a hosting network to be provided to the UE, based on the subscription data for the UE and the UE location;transmitting, to the second network entity, a request including at least one of a UE identifier, UE location information, or information on a localized service; andreceiving, from the second network entity, information on the hosting network based on the request.2.The method of claim 1, further comprising:transmitting, to an access and mobility management function (AMF), the subscription data for the UE and the UE location; andreceiving, from the AMF, location information for one or more UEs in the area of interest.3.The method of claim 1, further comprising:receiving, from a network exposure function (NEF), a message including at least one of the UE identifier, or the information on the localized service.4.The method of claim 1,wherein the information on the hosting network is generated based on the request, andwherein the information on the hosting network includes at least one of a list of hosting network identifier, credentials, or validity information.5.A method by a second network entity in a wireless communication, the method comprising:receiving, from a first network entity, a request including at least one of a user equipment (UE) identifier, UE location information, or information on a localized service; andtransmitting, to the first network entity, information on a hosting network based on the request,wherein the UE, subscription data for the UE and UE location are determined by the first network entity, andwherein the hosting network to be provided to the UE are filtered based on the subscription data for the UE and the UE location.6.The method of claim 5,wherein the subscription data for the UE and the UE location are transmitted from the first network entity to an access and mobility management function (AMF), andwherein location information for one or more UEs in the area of interest is transmitted from the AMF to the first network entity.7.The method of claim 5,wherein a message including at least one of the UE identifier, or the information on localized service is transmitted from a network exposure function (NEF) to the first network entity.8.The method of claim 5, further comprising:generating the information on the hosting network based on the request, andwherein the information on the hosting network includes at least one of a list of hosting network identifier, credentials, or validity information.9.A first network entity in a wireless communication, the first network entity comprising:a transceiver; anda controller coupled with the transceiver and configured to:determine, a user equipment (UE), subscription data for the UE and UE location,filter, a hosting network to be provided to the UE, based on the subscription data for the UE and the UE location,transmit, to the second network entity, a request including at least one of a UE identifier, UE location information, or information on a localized service, andreceive, from the second network entity, information on the hosting network based on the request.10.The first network entity of claim 9, wherein the controller further configured to:transmit, to an access and mobility management function (AMF), the subscription data for the UE and the UE location, andreceive, from the AMF, location information for one or more UEs in the area of interest.11.The first network entity of claim 9, wherein the controller further configured to:receive, from a network exposure function (NEF), a message including at least one of the UE identifier, or the information on the localized service.12.The first network entity of claim 9,wherein the information on the hosting network is generated based on the request, andwherein the information on the hosting network includes at least one of a list of hosting network identifier, credentials, or validity information.13.A second network entity in a wireless communication, the second network entity comprising:a transceiver; anda controller coupled with the transceiver and configured to:receive, from a first network entity, a request including at least one of a user equipment (UE) identifier, UE location information, or information on a localized service, andtransmit, to the first network entity, information on a hosting network based on the request,wherein the UE, subscription data for the UE and UE location are determined by the first network entity, andwherein the hosting network to be provided to the UE are filtered based on the subscription data for the UE and the UE location.14.The second network entity of claim 13,wherein a message including at least one of the UE identifier, or the information on localized service is transmitted from a network exposure function (NEF) to the first network entity,wherein the subscription data for the UE and the UE location are transmitted from the first network entity to an access and mobility management function (AMF), andwherein location information for one or more UEs in the area of interest is transmitted from the AMF to the first network entity.15.The second network entity of claim 13,wherein the controller further configured to generate the information on the hosting network based on the request, andwherein the information on the hosting network includes at least one of a list of hosting network identifier, credentials, or validity information.

Images