Method and apparatus for event opening of location reporting for a terminal device

Abstract

Methods and apparatuses for event disclosure are disclosed. According to one embodiment, a Network Exposure Function (NEF) entity receives a first request for event disclosure for subscribing to location reports for a terminal device from an Application Function (AF) entity. The first request indicates at least one location reporting accuracy for Fifth Generation (5G) Non-Third Generation Partnership Project (Non-3GPP) access for the terminal device. The NEF entity sends a second request for event disclosure for subscribing to location reports for the terminal device to a Unified Data Management (UDM) entity. The second request indicates the at least one location reporting accuracy. The NEF entity receives location information of the terminal device from an Access and Mobility Management Function (AMF) entity and sends the location information of the terminal device to the AF entity.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to communications, and more particularly to methods and apparatuses for event opening. Background Art

[0002] This section introduces aspects that can facilitate a better understanding of the present disclosure. Therefore, statements in this section should be read in this sense and should not be construed as admitting what is prior art or what is not prior art.

[0003] Figure 1 An architecture for a fifth generation (5G) system is shown. As shown, the 5G system includes a user equipment (UE), a (radio) access network ((R)AN), a user plane function (UPF), a data network (DN), an authentication server function (AUSF), an access and mobility management function (AMF), a session management function (SMF), a service communication proxy (SCP), a network slice selection function (NSSF), a network exposure function (NEF), a network repository function (NRF), a policy control function (PCF), a unified data management (UDM), and an application function (AF).

[0004] The 5G architecture is defined as service-based, and the interactions between network functions (NFs) are represented in two ways. One way is the service-based representation, where an NF within the control plane (e.g., the AMF) enables other authorized NFs to access its services. In necessary cases, this representation also includes point-to-point reference points. The other way is the reference point representation, which shows the interactions existing between NF services in the NFs described by point-to-point reference points (e.g., N11) between any two NFs (e.g., the AMF and the SMF).

[0005] The NEF supports the external exposure of the capabilities of NFs. The external exposure can be classified into monitoring capabilities, provisioning capabilities, policy / charging capabilities, and analysis reporting capabilities. The monitoring capabilities are used to monitor specific events of UEs in the 5G system and make such monitored event information available via the NEF for external exposure. The provisioning capabilities are used to allow an external party to provision information that can be used for UEs in the 5G system. The policy / charging capabilities are used to process service quality (QoS) and charging policies for UEs based on requests from an external party. The analysis reporting capabilities are used to allow an external party to obtain or subscribe / unsubscribe to analysis information generated by the 5G system. Summary of the Invention

[0006] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0007] One of the objectives of the present disclosure is to provide an improved solution for event opening.

[0008] According to a first aspect of the present disclosure, a method performed by a NEF entity is provided. The method may include receiving, from an AF entity, a first request for event opening for subscribing to location reports for a terminal device. The first request may indicate at least one location reporting accuracy for 5G non-Third Generation Partnership Project (non-3GPP) access for the terminal device. The method may further include sending, to a UDM entity, a second request for event opening for subscribing to location reports for the terminal device. The second request may indicate the at least one location reporting accuracy. The method may further include receiving, from an AMF entity, location information of the terminal device. The method may further include sending the location information of the terminal device to the AF entity.

[0009] In this way, the NEF entity can support location reporting for terminal devices from possible 5G non-3GPP accesses.

[0010] In an embodiment of the present disclosure, the at least one location reporting accuracy may include one or more of the following: a non-3GPP Interworking Function (N3IWF) used by the terminal device; a Trusted Non-3GPP Gateway Function (TNGF) used by the terminal device; an Internet Protocol (IP) address of the terminal device; a User Datagram Protocol (UDP) port used by the terminal device; a Wired Access Gateway Function (WAGF) used by the terminal device; a line identifier of an access point used by the terminal device; and a Hybrid Fiber-Coaxial (HFC) identifier of an access point used by the terminal device.

[0011] In an embodiment of the present disclosure, a list of accuracy attributes in an array form may be used in the first request to indicate the at least one location reporting accuracy.

[0012] In an embodiment of the present disclosure, a non-3GPP accuracy (n3gppAccuracy) attribute may be used in the first request to indicate the at least one location reporting accuracy.

[0013] In an embodiment of the present disclosure, a list of accuracy attributes in an array form may be used in the second request to indicate the at least one location reporting accuracy.

[0014] In an embodiment of the present disclosure, the n3gppAccuracy attribute may be used in the second request to indicate the at least one location reporting accuracy.

[0015] In an embodiment of the present disclosure, the location information of the terminal device may indicate one or more of the following: the N3IWF used by the terminal device; the TNGF used by the terminal device; the IP address of the terminal device; the UDP port used by the terminal device; the WAGF used by the terminal device; the line identifier of the access point used by the terminal device; and the HFC identifier of the access point used by the terminal device.

[0016] In an embodiment of the present disclosure, the location information of the terminal device may indicate one of the following: the initial location of the terminal device immediately after the second request is sent to the UDM entity; and the new location of the terminal device when a location change of the terminal device occurs.

[0017] According to a second aspect of the present disclosure, there is provided a method performed by a UDM entity. The method may include receiving, from an NEF entity, a first request for opening an event for subscribing to a location report for a terminal device. The first request may indicate at least one location report accuracy for non-3GPP access for the terminal device. The method may further include sending, to an AMF entity, a second request for opening an event for subscribing to a location report for the terminal device. The second request may indicate the at least one location report accuracy.

[0018] In this way, the UDM entity is enabled to support location reporting for terminal devices from possible non-3GPP accesses.

[0019] In an embodiment of the present disclosure, the at least one location report accuracy may include one or more of the following: the N3IWF used by the terminal device; the TNGF used by the terminal device; the IP address of the terminal device; the UDP port used by the terminal device; the WAGF used by the terminal device; the line identifier of the access point used by the terminal device; and the HFC identifier of the access point used by the terminal device.

[0020] In an embodiment of the present disclosure, an accuracy attribute list in an array form may be used in the first request to indicate the at least one location report accuracy.

[0021] In an embodiment of the present disclosure, the n3gppAccuracy attribute may be used in the first request to indicate the at least one location report accuracy.

[0022] In an embodiment of the present disclosure, the locationFilterList attribute of the AmfEvent data structure may be reused in the second request to indicate the at least one location report accuracy.

[0023] According to a third aspect of the present disclosure, a method performed by an AMF entity is provided. The method may include receiving, from a UDM entity, a request for opening an event for subscribing to location reports for a terminal device. The request may indicate at least one location reporting accuracy for non-3GPP access of the terminal device via TNGF and / or WAGF. The method may further include determining, based on the request, location information of the terminal device. The method may further include reporting the location information of the terminal device to an NEF entity.

[0024] In this way, the AMF entity is enabled to support location reporting for terminal devices from possible non-3GPP access via TNGF and / or WAGF.

[0025] In an embodiment of the present disclosure, the at least one location reporting accuracy may include one or more of the following: TNGF used by the terminal device; the IP address of the terminal device; the UDP port used by the terminal device; WAGF used by the terminal device; the line identifier of the access point used by the terminal device; and the HFC identifier of the access point used by the terminal device.

[0026] In an embodiment of the present disclosure, the locationFilterList attribute of the AmfEvent data structure may be reused in the request to indicate the at least one location reporting accuracy.

[0027] In an embodiment of the present disclosure, the location information of the terminal device may indicate one or more of the following: TNGF used by the terminal device; the IP address of the terminal device; the UDP port used by the terminal device; WAGF used by the terminal device; the line identifier of the access point used by the terminal device; and the HFC identifier of the access point used by the terminal device.

[0028] In an embodiment of the present disclosure, determining the location information of the terminal device may include determining information about an initial location of the terminal device immediately after the request is received from the UDM entity as the location information.

[0029] In an embodiment of the present disclosure, determining the location information of the terminal device may include monitoring whether a location change of the terminal device has occurred. Determining the location information of the terminal device may include, when a location change of the terminal device has occurred, determining information about a new location of the terminal device as the location information.

[0030] According to a fourth aspect of the present disclosure, a method performed by an AF entity is provided. The method may include sending a request to an NEF entity for opening an event for subscribing to location reports for a terminal device. The request may indicate at least one location reporting accuracy for 5G non-3GPP access for the terminal device. The method may further include receiving location information of the terminal device from the NEF entity.

[0031] In this way, the AF entity can support location reporting for terminal devices from possible 5G non-3GPP access.

[0032] In an embodiment of the present disclosure, the at least one location reporting accuracy may include one or more of the following: N3IWF used by the terminal device; TNGF used by the terminal device; IP address of the terminal device; UDP port used by the terminal device; WAGF used by the terminal device; line identifier of the access point used by the terminal device; and HFC identifier of the access point used by the terminal device.

[0033] In an embodiment of the present disclosure, a list of accuracy attributes in an array form may be used in the request to indicate the at least one location reporting accuracy.

[0034] In an embodiment of the present disclosure, the n3gppAccuracy attribute may be used in the request to indicate the at least one location reporting accuracy.

[0035] In an embodiment of the present disclosure, the location information of the terminal device may indicate one or more of the following: N3IWF used by the terminal device; TNGF used by the terminal device; IP address of the terminal device; UDP port used by the terminal device; WAGF used by the terminal device; line identifier of the access point used by the terminal device; and HFC identifier of the access point used by the terminal device.

[0036] In an embodiment of the present disclosure, the location information of the terminal device may indicate one of the following: the initial location of the terminal device immediately after the request is sent to the NEF entity; and the new location of the terminal device when a location change of the terminal device occurs.

[0037] According to a fifth aspect of the present disclosure, a NEF entity is provided. The NEF entity may include at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the NEF entity may be operable to receive, from an AF entity, a first request for opening an event for subscribing to location reports for a terminal device. The first request may indicate at least one location reporting accuracy for 5G non-3GPP access for the terminal device. The NEF entity may also be operable to send, to a UDM entity, a second request for opening an event for subscribing to location reports for the terminal device. The second request may indicate the at least one location reporting accuracy. The NEF entity may also be operable to receive the location information of the terminal device from an AMF entity. The NEF entity may also be operable to send the location information of the terminal device to the AF entity.

[0038] In an embodiment of the present disclosure, the NEF entity may be operable to execute the method according to the first aspect above.

[0039] According to a sixth aspect of the present disclosure, a UDM entity is provided. The UDM entity may include at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the UDM entity may be operable to receive, from a NEF entity, a first request for opening an event for subscribing to location reports for a terminal device. The first request may indicate at least one location reporting accuracy for non-3GPP access for the terminal device. The UDM entity may also be operable to send, to an AMF entity, a second request for opening an event for subscribing to location reports for the terminal device. The second request may indicate the at least one location reporting accuracy.

[0040] In an embodiment of the present disclosure, the UDM entity may be operable to execute the method according to the second aspect above.

[0041] According to a seventh aspect of the present disclosure, an AMF entity is provided. The AMF entity may include at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the AMF entity may be operable to receive, from a UDM entity, a request for opening an event for subscribing to location reports for a terminal device. The request may indicate at least one location reporting accuracy for non-3GPP access for the terminal device via TNGF and / or WAGF. The AMF entity may also be operable to determine the location information of the terminal device based on the request. The AMF entity may also be operable to report the location information of the terminal device to a NEF entity.

[0042] In an embodiment of the present disclosure, the AMF entity may be operable to execute the method according to the third aspect above.

[0043] According to an eighth aspect of the present disclosure, an AF entity is provided. The AF entity may include at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the AF entity may be operable to send a request for opening an event for subscribing to a location report for a terminal device to a NEF entity. The request may indicate at least one location report accuracy for 5G non-3GPP access of the terminal device. The AF entity may also be operable to receive location information of the terminal device from the NEF entity.

[0044] In an embodiment of the present disclosure, the AF entity may be operable to execute the method according to the fourth aspect above.

[0045] According to a ninth aspect of the present disclosure, a computer program product is provided. The computer program product may contain instructions that, when executed by at least one processor, cause the at least one processor to execute the method according to any one of the first to fourth aspects above.

[0046] According to a tenth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium may contain instructions that, when executed by at least one processor, cause the at least one processor to execute the method according to any one of the first to fourth aspects above.

[0047] According to an eleventh aspect of the present disclosure, a NEF entity is provided. The NEF entity may include a first receiving module for receiving a first request for opening an event for subscribing to a location report for a terminal device from an AF entity. The first request may indicate at least one location report accuracy for 5G non-3GPP access of the terminal device. The NEF entity may also include a first sending module for sending a second request for opening an event for subscribing to a location report for the terminal device to a UDM entity. The second request may indicate the at least one location report accuracy. The NEF entity may also include a second receiving module for receiving location information of the terminal device from an AMF entity. The NEF entity may also include a second sending module for sending the location information of the terminal device to the AF entity.

[0048] According to a twelfth aspect of the present disclosure, a UDM entity is provided. The UDM entity may include a receiving module configured to receive, from a NEF entity, a first request for opening an event for subscribing to location reports for a terminal device. The first request may indicate at least one location reporting accuracy for non-3GPP access of the terminal device. The UDM entity may further include a sending module configured to send, to an AMF entity, a second request for opening an event for subscribing to location reports for the terminal device. The second request may indicate the at least one location reporting accuracy.

[0049] According to a thirteenth aspect of the present disclosure, an AMF entity is provided. The AMF entity may include a receiving module configured to receive, from a UDM entity, a request for opening an event for subscribing to location reports for a terminal device. The request may indicate at least one location reporting accuracy for non-3GPP access of the terminal device via TNGF and / or WAGF. The AMF entity may further include a determining module configured to determine, based on the request, location information of the terminal device. The AMF entity may further include a reporting module configured to report the location information of the terminal device to a NEF entity.

[0050] According to a fourteenth aspect of the present disclosure, an AF entity is provided. The AF entity may include a sending module configured to send, to a NEF entity, a request for opening an event for subscribing to location reports for a terminal device. The request may indicate at least one location reporting accuracy for 5G non-3GPP access of the terminal device. The AF entity may further include a receiving module configured to receive, from the NEF entity, the location information of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] These and other objects, features, and advantages of the present disclosure will become apparent from the following detailed description of illustrative embodiments of the present disclosure, which is to be read in conjunction with the accompanying drawings.

[0052] Figure 1 is a diagram showing the architecture of a 5G system;

[0053] Figure 2 is a diagram showing the architecture of a 5G core network with untrusted non-3GPP access;

[0054] Figure 3 is a diagram showing the architecture of a 5G core network with trusted non-3GPP access;

[0055] Figure 4 is a diagram showing the architecture of a 5G core network for a 5G-RG with a wired 5G access network and an NG RAN;

[0056] Figure 5It is a diagram showing the architecture of a 5G core network for an FN-RG with a wired 5G access network and an NG RAN;

[0057] Figure 6 It is a flowchart showing a method implemented at a NEF entity according to an embodiment of the present disclosure;

[0058] Figure 7 It is a flowchart showing a method implemented at a UDM entity according to an embodiment of the present disclosure;

[0059] Figure 8 It is a flowchart showing a method implemented at an AMF entity according to an embodiment of the present disclosure;

[0060] Figure 9 It is for explaining Figure 8 a method;

[0061] Figure 10 It is a flowchart showing a method implemented at an AF entity according to an embodiment of the present disclosure;

[0062] Figure 11 It is a flowchart showing an exemplary process according to an embodiment of the present disclosure;

[0063] Figure 12 It is a flowchart showing another exemplary process according to an embodiment of the present disclosure;

[0064] Figure 13 It is a block diagram showing a device suitable for use in practicing some embodiments of the present disclosure;

[0065] Figure 14 It is a block diagram showing a NEF entity according to an embodiment of the present disclosure;

[0066] Figure 15 It is a block diagram showing a UDM entity according to an embodiment of the present disclosure;

[0067] Figure 16 It is a block diagram showing an AMF entity according to an embodiment of the present disclosure; and

[0068] Figure 17 It is a block diagram showing an AF entity according to an embodiment of the present disclosure. Detailed Description

[0069] For purposes of explanation, some details are set forth in the following description to provide a thorough understanding of the disclosed embodiments. However, it will be apparent to those skilled in the art that the embodiments may be practiced without these specific details or with equivalent configurations.

[0070] Figure 1One of the nodes depicted is the access network (AN), which can be wireless-based or wire-based. A typical wireless access network is the radio access network (RAN) defined by 3GPP. The following types of non-3GPP access networks are defined: untrusted non-3GPP access network; trusted non-3GPP access network; and wire access network. The 5G core network supports the connectivity of the UE via non-3GPP access networks (e.g., wireless local area network (WLAN) access network).

[0071] The 5G core network supports as Figure 2 shown the untrusted non-3GPP access network and as Figure 3 shown the trusted non-3GPP access network (TNAN). The untrusted non-3GPP access network will be connected to the 5G core network via the non-3GPP interworking function (N3IWF), while the trusted non-3GPP access network will be connected to the 5G core network via the trusted non-3GPP gateway function (TNGF). Both the N3IWF and the TNGF are connected to the 5G core network control plane (CP) and user plane (UP) functions via the N2 and N3 interfaces respectively.

[0072] Figure 4 The architecture of the 5G core network is shown for a 5G residential gateway (5G-RG) with a wire 5G access network and a next generation (NG) RAN. As shown, the wire 5G access network will be connected to the 5G core network via the wire access gateway function (W-AGF). The W-AGF is connected to the 5G core network CP and UP functions via the N2 and N3 interfaces respectively. For the scenario of the 5G-RG connected via the NG RAN, the specifications for the UE can apply as defined for the UE connected to the 5G core (5GC) via the NG RAN, unless otherwise specified. When the 5G-RG is connected via the NG-RAN and via the wire 5G access network (W-5GAN), there will be multiple N1 instances for the 5G-RG, i.e., there will be one N1 instance on the NG-RAN and one N1 instance on the W-5GAN.

[0073] Figure 5 The architecture of the 5G core network is shown for a fixed network residential gateway (FN-RG) with a wire 5G access network and an NG RAN. As shown, for the scenario of the FN-RG that does not have 5G capabilities and is connected to the 5GC via the W-5GAN, the W-AGF provides the N1 interface to the AMF on behalf of the FN-RG.

[0074] A UE connected to a 5G-RG or an FN-RG can access the 5GC via the N3IWF or via the TNGF, where the combination of the 5G-RG / FN-RG, the W-5GAN, and the UPF serving the 5G-RG or FN-RG acts as an untrusted non-3GPP access network or as a trusted non-3GPP access network, respectively. For example, the UE connects to the 5G-RG via a WLAN radio access and connects to the 5GC via the N3IWF.

[0075] Regarding the NEF network event exposure, the monitoring capabilities consist of means to allow identification of 5G NFs suitable for configuring specific monitoring events, means to detect the monitoring events, and means to report the monitoring events to an authorized external party. The monitoring capabilities can be used to expose the UE mobility management context, such as UE location, reachability, roaming status, and connection loss. The AMF stores UE Reachability Request Parameter (URRP-AMF) information for the AMF in the mobility management (MM) context to determine the NFs authorized to receive direct notifications from the AMF. The UDM stores the URRP-AMF information locally to determine the authorized monitoring requests when forwarding indirect notifications.

[0076] of 3GPP Technical Specification (TS) 23.501 Vl6.1.0 Figure 4 .2.3-5 shows the architecture for the NEF. As shown in the figure, the monitoring event feature is intended to monitor specific events in the 3GPP system and enable such monitoring event information to be reported via the NEF. The monitoring event feature consists of means to allow NFs in the 5G System (5GS) to configure specific events, event detection, and event reporting to the requesting party.

[0077] To support the monitoring feature in the roaming scenario, a roaming agreement needs to be reached between the Home Public Land Mobile Network (HPLMN) and the Visited PLMN (VPLMN). An Intermediate NEF (I-NEF) can be deployed as defined. If the I-NEF is deployed, the AMF and SMF in the VPLMN provide the configuration for a given monitoring event at the I-NEF and enable the monitoring event to be reported via the I-NEF. The I-NEF knows the monitoring event and enables it to be reported via the NEF.

[0078] The set of capabilities required for monitoring will become accessible to NFs in the 5GS via the NEF. Monitoring events via the UDM, AMF, SMF, and Gateway Mobile Location Center (GMLC) enable the NEF to configure a given monitoring event at the UDM, AMF, SMF, or GMLC, and to report events via the UDM and / or AMF or GMLC. Depending on the specific monitoring event or information, it is the AMF, GMLC, or UDM that knows the monitoring event or information and causes it to be reported via the NEF. Table 4.15.3.1-1 of 3GPP TS 23.502 V16.1.1 shows the currently supported monitoring events.

[0079] As shown in Figure 4 .2.3-5 of 3GPP TS 23.501 V16.1.0, the NEF exposes application programming interfaces (APIs) to external AFs (Service Capability Servers / Application Servers (SCS / AS)) for subscribing to events defined in Table 4.15.3.1-1 of 3GPP TS 23.502 V16.1.1. The data structures defined for monitoring event subscriptions can be obtained from Table 5.3.2.1.2-1 of 3GPP TS 29.122 Vl6.2.0. The supported accuracy levels related to location reporting events can be obtained from Table 5.3.2.4.7-1 of 3GPP TS 29.122 Vl6.2.0.

[0080] Regarding UDM network event openings, the following monitoring events (not exhaustive) apply to monitoring event configuration via the UDM for a single UE or a group of UEs or any UE: connection loss, UE reachability, location reporting, change in the association of International Mobile Subscriber Identity - International Mobile Equipment Identity (IMSI-IMEI) (Software Version SV), roaming status, communication failure, and availability after Delivery Status Notification (DNN) failure.

[0081] For the Nudm_EventExposure service, the following service operations are defined: Subscribe; Unsubscribe; Notify; and Modify Subscription. The Nudm_EventExposure service is used by a consumer NF (e.g., NEF) to subscribe to notifications of event occurrences by subscribing to the service operations. For events that can be detected by the AMF, the UDM uses the appropriate AMF service operations to subscribe on behalf of the consumer NF (e.g., NEF). The Nudm_EventExposure service is also used by a consumer NF (e.g., NEF) that has previously subscribed to notifications to unsubscribe by using the Unsubscribe service operation. For events that can be detected by the AMF, the UDM uses the appropriate AMF service operations to unsubscribe on behalf of the consumer NF (e.g., NEF). The Nudm_EventExposure service is also used by a subscribed consumer NF (e.g., NEF) to be notified by the UDM when a subscribed event occurs at the UDM by using the Notify service operation. For a subscribed event that can occur at the AMF, the consumer NF (e.g., NEF) is directly notified by the AMF by using the corresponding AMF service operation without the involvement of the UDM. The Nudm_EventExposure service is also used by a subscribed consumer NF (e.g., NEF) to modify an existing subscription by using the Modify Subscription service operation.

[0082] of 3GPP TS 29.503 V16.0.0 Figure 5 .5.2.2.2-1 shows a scenario where an NF service consumer sends a request to the UDM to subscribe to notifications of event occurrences. The request contains a callback uniform resource identifier (URI), the type of the event being monitored, and additional information such as event filters and reporting options. More details can be obtained from clause 5.5.2.2.2 of 3GPP TS 29.503 V16.0.0. Tables 6.4.6.2.2-1, 6.4.6.2.3-1, 6.4.6.2.10-1, and 6.4.6.3.4-1 of 3GPP TS 29.503 V16.0.0 define the EeSubscription data structure and, in particular, the data structures related to location reporting.

[0083] Regarding the opening of AMF network events, of 3GPP TS 29.518 V16.0.0 Figure 5.3.2.2.2-1 shows subscribing to event notifications from the AMF. More details can be obtained from clause 5.3.2.2.2 of 3GPP TS 29.518 V16.0.0. Table 6.2.6.2.2-1 of 3GPP TS 29.518 V16.0.0 defines the data structure for subscribing to event subscriptions from the AMF. Table 6.2.6.2.3-1 and Table 6.2.6.3.5-1 of 3GPP TS 29.518 V16.0.0 show the configuration information for location reporting events. Table 6.2.6.2.5-1 of 3GPP TS 29.518 V16.0.0 and Table 5.4.4.10-1 of 3GPP TS 29.571 V16.0.0 show the data structure for location change reporting.

[0084] Based on the above, for location reporting events opened by the NEF / UDM / AMF, location reporting for all possible 5G non-3GPP accesses is not well supported. As a first problem, according to Table 5.3.2.4.7-1 of 3GPP TS 29.122 V16.2.0, for the location accuracy supported by the NEF / Service Capability Exposure Function (SCEF), only the Trusted WLAN Access Network (TWAN) is related to the fourth generation (4G) non-3GPP access, but the location accuracy of other 5G non-3GPP accesses (such as untrusted non-3GPP access and wired non-3GPP access) is not supported. Therefore, the problem is that the AF (SCS / AS) cannot subscribe to location change event notifications for UEs from all possible 5G non-3GPP accesses.

[0085] As a second problem, according to Table 6.4.6.3.4-1 of 3GPP TS 29.503 V16.0.0, for the location accuracy supported by the UDM, even worse, only CELL_LEVEL (cell level) or Tracking Area Level (TA_LEVEL) is supported for location accuracy, which is only applicable to 3GPP access. This implicitly limits the location reporting events to only 5G 3GPP access. Therefore, it is impossible for the UDM to open location change reporting to allow external service consumers (such as AF) to subscribe to location change event notifications for UEs from all possible 5G non-3GPP accesses through the NEF.

[0086] As a third issue, according to Table 6.2.6.3.5-1 of 3GPP TS 29.518 V16.0.0, for the location filters supported by the AMF, only the N3IWF level of accuracy is supported for non-3GPP access, but other 5G non-3GPP access location accuracies (such as trusted 5G non-3GPP access and wired 5G non-3GPP access) are not supported. Therefore, it is not possible for the AMF to open location change reports to allow external service consumers (such as the AF) to subscribe to location change event notifications for UEs from all possible 5G non-3GPP accesses through the NEF and UDM.

[0087] Based on the above three issues, it is obvious that there is the following overall problem: from the perspective of end-to-end usage scenarios, for location change events, when it comes to UEs from all possible 5G non-3GPP accesses, the network event opening of location change events does not work.

[0088] The present disclosure proposes an improved solution for event opening. As an exemplary example, this solution can be applied to Figure 1 the communication system shown. Figure 1 The functional descriptions of the entities shown in [reference] are specified in Clause 6 of 3GPP TS 23.501, and the entire content is incorporated herein by reference.

[0089] It should be noted that in the context of the present disclosure, the term terminal device (or UE) used herein may also be referred to as, for example, an access terminal, a mobile station, a mobile unit, a user station, etc. It can refer to any (stationary or mobile) end device capable of accessing a wireless communication network and receiving services therefrom. By way of example and not limitation, a UE may include a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a tablet computer, a wearable device, a personal digital assistant (PDA), an integrated or embedded wireless network card, an externally plugged-in wireless network card, and so on.

[0090] In the Internet of Things (IoT) scenario, a terminal device (or UE) may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another terminal device (or UE) and / or a network device. In this case, the terminal device (or UE) may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. Specific examples of such machines or devices may include sensors, metering devices such as power meters, industrial machinery, bicycles, vehicles, or household or personal appliances (e.g., refrigerators, televisions), personal wearable devices (such as watches), and so on.

[0091] As used herein, the term "communication system" refers to a system that complies with any suitable communication standard (such as the first generation (1G), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols), and / or any other protocol known currently or developed in the future. Additionally, the communication between the terminal device and the network node (or network entity) in the communication system can be conducted according to any suitable generation of communication protocol (including but not limited to the 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols), and / or any other protocol known currently or developed in the future. Further, the specific terms used herein do not limit the present disclosure to the communication systems related to the specific terms, but these specific terms can also be more generally applicable to other communication systems.

[0092] Figure 6 is a flowchart showing a method implemented at the NEF entity according to an embodiment of the present disclosure. At block 602, the NEF entity receives a first request from the AF entity for subscribing to an event opening for location reporting for a terminal device. The first request indicates at least one location reporting accuracy for the 5G non-3GPP access of the terminal device. The at least one location reporting accuracy can include any one or any combination of the following: the N3IWF used by the terminal device; the TNGF used by the terminal device; the Internet Protocol (IP) address of the terminal device; the User Datagram Protocol (UDP) port used by the terminal device; the WAGF used by the terminal device; the line identifier of the access point used by the terminal device; and the Hybrid Fiber Coaxial (HFC) identifier of the access point used by the terminal device. As an option, a list of accuracy attributes in the form of an array can be used in the first request to indicate the at least one location reporting accuracy. As another option, the non-3GPP accuracy (n3gppAccuracy) attribute can be used in the first request to indicate the at least one location reporting accuracy. It should be noted that the at least one location reporting accuracy can be indicated in the first request by any other suitable means. As an exemplary example, the first request can be an Nnef_EventExposure_Subscribe request.

[0093] At block 604, the NEF entity sends a second request to the UDM entity for opening an event for subscribing to location reports for the terminal device. The second request indicates the at least one location report accuracy indicated by the first request. As an option, a list of accuracy attributes in the form of an array can be used in the second request to indicate the at least one location report accuracy. As another option, the n3gppAccuracy attribute can be used in the second request to indicate the at least one location report accuracy. It should be noted that the at least one location report accuracy can be indicated in the second request by any other suitable means. As an exemplary example, the second request can be a Nudm_EventExposure_Subscribe request.

[0094] At block 606, the NEF entity receives the location information of the terminal device from the AMF entity. The operations performed by the AMF entity will be described later. Since the second request indicates the at least one location report accuracy for the 5G non-3GPP access of the terminal device, the location information of the terminal device can indicate any one or any combination of the following: the N3IWF used by the terminal device; the TNGF used by the terminal device; the IP address of the terminal device; the UDP port used by the terminal device; the WAGF used by the terminal device; the line identifier of the access point used by the terminal device; and the HFC identifier of the access point used by the terminal device. If immediate reporting is configured in the first request and the second request, the location information of the terminal device can indicate the initial location of the terminal device immediately after the second request is sent to the UDM entity. If continuous reporting is configured in the first request and the second request, the location information of the terminal device can indicate the new location of the terminal device when a location change of the terminal device occurs. Therefore, either the initial location or the new location can be represented by any one or any combination of the following: the identifier of the N3IWF used by the terminal device; the identifier of the TNGF used by the terminal device; the IP address of the terminal device; the UDP port used by the terminal device; the identifier of the WAGF used by the terminal device; the line identifier of the access point used by the terminal device; and the HFC identifier of the access point used by the terminal device. As an exemplary example, the location information of the terminal device can be received from the AMF entity in a Namf_EventExposure_Notify message.

[0095] At block 608, the NEF entity sends the location information of the terminal device to the AF entity. As an exemplary example, the location information of the terminal device can be sent to the AF entity in a Nnef_EventExposure_Notify message. With Figure 6A method enables the NEF entity to support location reporting for terminal devices from possible 5G non-3GPP access.

[0096] Figure 7 is a flowchart showing a method implemented at a UDM entity according to an embodiment of the present disclosure. At block 702, the UDM entity receives a first request from the NEF entity for opening an event for subscribing to location reporting for a terminal device. The first request indicates at least one location reporting accuracy for non-3GPP access of the terminal device. The at least one location reporting accuracy may include any one or any combination of the following: N3IWF used by the terminal device; TNGF used by the terminal device; IP address of the terminal device; UDP port used by the terminal device; WAGF used by the terminal device; line identifier of the access point used by the terminal device; and HFC identifier of the access point used by the terminal device. As an option, a list of accuracy attributes in the form of an array may be used in the first request to indicate the at least one location reporting accuracy. As another option, the n3gppAccuracy attribute may be used in the first request to indicate the at least one location reporting accuracy. It should be noted that the at least one location reporting accuracy may be indicated in the first request in any other suitable manner. As an exemplary example, the first request may be a Nudm_EventExposure_Subscribe request.

[0097] At block 704, the UDM entity sends a second request to the AMF entity for opening an event for subscribing to location reporting for the terminal device. The second request indicates the at least one location reporting accuracy indicated by the first request. For example, the locationFilterList attribute of the AmfEvent data structure may be reused in the second request to indicate the at least one location reporting accuracy. It should be noted that the at least one location reporting accuracy may be indicated in the second request in any other suitable manner. As an exemplary example, the second request may be a Namf_EventExposure_Subscribe request. Using Figure 7 A method enables the UDM entity to support location reporting for terminal devices from possible non-3GPP access.

[0098] Figure 8It is a flowchart showing a method implemented at an AMF entity according to an embodiment of the present disclosure. At block 802, the AMF entity receives a request from a UDM entity for opening an event for subscribing to location reports for a terminal device. The request indicates at least one location reporting accuracy for non-3GPP access of the terminal device via TNGF and / or WAGF. The at least one location reporting accuracy may include any one or any combination of the following: TNGF used by the terminal device; IP address of the terminal device; UDP port used by the terminal device; WAGF used by the terminal device; line identifier of the access point used by the terminal device; and HFC identifier of the access point used by the terminal device. For example, the locationFilterList attribute of the AmfEvent data structure may be reused in the request to indicate the at least one location reporting accuracy. It should be noted that the at least one location reporting accuracy may be indicated in the request by any other suitable means. As an exemplary example, the request may be a Namf_EventExposure_Subscribe request.

[0099] At block 804, the AMF entity determines the location information of the terminal device based on the request. Since at least one location reporting accuracy for non-3GPP access of the terminal device via TNGF and / or WAGF is indicated in the request, the location information of the terminal device may indicate any one or any combination of the following: TNGF used by the terminal device; IP address of the terminal device; UDP port used by the terminal device; WAGF used by the terminal device; line identifier of the access point used by the terminal device; and HFC identifier of the access point used by the terminal device. For example, block 804 may be implemented as Figure 9 block 804-1 or blocks 804-2 to 804-3 shown in. If immediate reporting is configured in the request, block 804-1 may be executed. At block 804-1, the AMF entity determines information about the initial location of the terminal device immediately after the request is received from the UDM entity as the location information.

[0100] If continuous reporting is configured in the request, execution boxes 804-2 and 804-3 are performed. At box 804-2, the AMF entity monitors whether a location change of the terminal device has occurred. When a location change of the terminal device has occurred, the AMF entity determines, at box 804-3, information about the new location of the terminal device as the location information. In the case where the terminal device accesses the network via TNGF or WAGF, since this access is directed towards the AMF entity, the AMF entity knows which TNGF or WAGF is used by the terminal device and whether it has been changed. This also holds true for the corresponding IP address / UDP port or the corresponding line identifier / HFC identifier. Therefore, the initial location or the new location can be determined at box 804-1 or boxes 804-2 to 804-3.

[0101] At box 806, the AMF entity reports the location information of the terminal device to the NEF entity. As an exemplary example, the location information of the terminal device is sent to the NEF entity in the Namf_EventExposure_Notify message. Using Figure 8 the method, the AMF entity is enabled to support location reporting for terminal devices from possible non-3GPP accesses via TNGF and / or WAGF.

[0102] Figure 10 is a flowchart showing a method implemented at the AF entity according to an embodiment of the present disclosure. At box 1002, the AF entity sends a request for event exposure for subscribing to location reporting for a terminal device to the NEF entity. The request indicates at least one location reporting accuracy for 5G non-3GPP access for the terminal device. Box 1002 corresponds to box 602, and its details are omitted here. At box 1004, the AF entity receives the location information of the terminal device from the NEF entity. Box 1004 corresponds to box 608, and its details are omitted here. Using Figure 10 the method, the AF entity is enabled to support location reporting for terminal devices from possible 5G non-3GPP accesses.

[0103] Figure 11It is a flowchart showing an exemplary process according to an embodiment of the present disclosure. As shown, the exemplary process relates to location change event subscription / notification for 5G 3GPP access and untrusted 5G non-3GPP access. The term N3AN refers to a non-3GPP access network. At step 1, the UE registers to the 5G core network. This may include the UE being authenticated by the network and registered to the 5G core network (including UDM). The UE can access the 5G network from different access networks: access the AMF from a new radio (NR)-based 5G 3GPP access network through a next-generation node B (gNB), or access the AMF from an untrusted 5G non-3GPP access network through an N3IWF, or access the AMF from a trusted 5G non-3GPP access network through a TNGF, or access the AMF from a wired 5G non-3GPP access network through a W-AGF.

[0104] At step 2, the AF operates an Nnef_EventExposure_Subscribe request through the NEF open API to subscribe to location change events for the UE. In the request body, more information about event subscription such as the following is provided:

[0105] MonitoringType (Monitoring type): LOCATION_REPORTING (Location_Report)

[0106] Msisdn: xxxxxxxxxxx

[0107] notificationDestination (Notification destination): http: / / example.af.com / notif

[0108] accuracy (3GPP) (Accuracy (3GPP)): CGI_ECGI

[0109] n3gppAccuracy (Non-3GPP accuracy): N3IWF, UE_IP, UE_PORT Here, the event notification subscription example is for the AF, which is interested in location granularity including any one of N3IWF, UE_IP, UE_PORT.

[0110] As described above, the NEF still cannot support such UE location change events. Therefore, enhancements need to be added to the NEF here to open location change events for UEs from all possible 5G non-3GPP accesses. An example of an enhancement to the 3GPP protocol is shown below, where the added content is underlined.

[0111] Table 1: Enumeration accuracy (changes compared to Table 5.3.2.4.7-1 of 3GPP TS 29.122 V16.2.0 are underlined)

[0112] Enumeration value Description CGI_ECGI The SCS / AS request is notified with cell-level location accuracy. ENODEB The SCS / AS request is notified with eNodeB-level location accuracy. TA_RA The SCS / AS request is notified with TA / RA-level location accuracy. PLMN The SCS / AS request is notified with PLMN-level location accuracy. TWAN_ID The SCS / AS request is notified with TWAN identifier-level location accuracy. GEO_AREA The SCS / AS request is notified of geographical area accuracy. <![CDATA N3IWF > <![CDATA The SCS / AS request is notified with N3WIF-level location accuracy. <!-- 11 -->]]> <![CDATA TNGF > <![CDATA The SCS / AS request is notified with TNGF-level location accuracy. > <![CDATA UE_IP > <![CDATA The SCS / AS request is notified with UE IP-level location accuracy. > <![CDATA UE_PORT > <![CDATA The SCS / AS request is notified with UE PORT-level location accuracy. > <![CDATA WAGF > <![CDATA The SCS / AS request is notified with WAGF-level location accuracy. > <![CDATA LINE_ID > <![CDATA The SCS / AS request is notified with line identifier-level location accuracy. > <![CDATA HFC_ID > <![CDATA The SCS / AS request is notified with HFC identifier-level location accuracy. >

[0113] As shown in the above table, the N3IWF and TNGF granularities are added respectively for untrusted 5G non-3GPP access and trusted 5G non-3GPP access. The WAGF is added for wired 5G non-3GPP access. In addition, the UE_IP and UE_PORT are added for the IP connectivity level granularity of the UE connected via untrusted 5G non-3GPP access or trusted 5G non-3GPP access. For wired 5G non-3GPP access, the line identifier (LINE_ID) or HFC identifier (HFC_ID) level granularity is added. The formats of the line ID and HFC ID are defined in 3GPP TS 23.316, and the extracts are copied below for reference.

[0114] · The format of the line ID is generic, allowing different operators and access networks to use different encodings of the content. The line ID can have the following formats:

[0115] - DHCPv4 option 82 interchange (TR-101 Issue 2 [6] Appendix B, original specification 2006);

[0116] - PPPoE circuit and remote ID AVP insertion (TR-101 Issue 2 [6] Appendix A / 8.3,

[0117] original specification 2006);

[0118] - DHCPv6 use of option 18 via the LDRA function in the access node (BBF TR-177 Issue 1 Errata 1

[12] , original specification 2010);

[0119] - Use of the line ID option (LIO) in RS messaging (BBF TR-177 Issue 1 Errata 1

[12] , original specification 2010). It is also recorded in RFC 6788

[13] which is slightly different from the BBF encoding.

[0120] · The format of the HFC_Identifier is an octet string and can contain the cable modem MAC address or the overall HFC account identifier, as defined by CableLabs in DOCSIS MULPI [8].

[0121] In addition, to allow for the configuration of multiple accuracy levels on the subscribed location change events, it is proposed to update the NEF data structure for the subscribed events. Tables 2-1 and 2-2 show two alternatives for the changes compared to Table 5.3.2.1.2-1 of 3GPP TS 29.122 V16.2.0.

[0122] Table 2-1: Definition of type MonitoringEventSubscription

[0123] (Changes compared to Table 5.3.2.1.2-1 of 3GPP TS 29.122 V16.2.0 are underlined)

[0124]

[0125]

[0126]

[0127]

[0128] Table 2-2: Definition of type MonitoringEventSubscription

[0129] (Changes compared to Table 5.3.2.1.2-1 of 3GPP TS 29.122 V16.2.0 are underlined)

[0130]

[0131]

[0132]

[0133]

[0134] At step 3, the NEF subscribes to UE location change event notifications from the UDM via an API operation Nudm_EventExposure_Subscribe request. More information is included in the request Uniform Resource Locator (URL) or in the request body as follows:

[0135] ueldentity:msisdn-xxxxxxxxxxx

[0136] referenceId:nef01-0001

[0137] callbackReference:http: / / example.nef01.com / notif

[0138] EventType:LOCATION_REPORT

[0139] Accuracy(3GPP):CELL_LEVEL

[0140] n3gppAccuracy:N3IWF,UE_IP,UE_PORT

[0141] The UDM can perform an identity transformation to convert the Mobile Subscriber International ISDN Number (MSISDN) to a Subscription Permanent Identifier (SUPI) identity so that the SUPI can be used internally in relation to this UE location change event. The term ISDN refers to the Integrated Services Digital Network.

[0142] Following the previous example, the event notification subscription is for the NEF, which is interested in location granularity including any of N3IWF, UE_IP, UE_PORT. As mentioned above, the UDM still cannot support such UE location change events. Enhancements need to be added to the UDM here to open up location change events for UEs from all possible 5G non-3GPP accesses. An example of an enhancement to the 3GPP protocol is shown below, where the added content is underlined.

[0143] Table 3: Enumerated LocationAccuracy

[0144] (Changes compared to Table 6.4.6.3.4-1 of 3GPP TS 29.503 V16.0.0 are underlined)

[0145] Enumeration value Description "CELL_LEVEL" Changes in the cell should be reported. "TA_LEVEL" Changes in the TA should be reported. <![CDATA "N3IWF_LEVEL” > <![CDATA Changes in the N3IWF node for non-3GPP access should be reported. > <![CDATA "TNGF_LEVEL” > <![CDATA Changes in the TNGF node for non-3GPP access should be reported. > <![CDATA "UE_IP” > <![CDATA Changes in the UE IP address (for reaching the N3IWF) should be reported. > <![CDATA "UE_PORT” > <![CDATA Changes in the UE source port should be reported. > <![CDATA "WAGF_LEVEL” > <![CDATA Changes in the WAGF node for non-3GPP access should be reported. > <![CDATA "LINE_ID” > <![CDATA Changes in the line identifier of the access point should be reported. > <![CDATA "HFC_ID” > <![CDATA Changes in the HFC identifier of the access point should be reported. >

[0146] In addition, to allow for the configuration of multiple accuracy levels on the subscribed location change events, it is proposed to update the UDM data structure for the subscribed events. Tables 4-1 and 4-2 show two alternatives for the changes compared to Table 6.4.6.2.10-1 of 3GPP TS 29.503 V16.0.0.

[0147] Table 4-1: Definition of type LocationReportingConfiguration

[0148] (Changes compared to Table 6.4.6.2.10-1 of 3GPP TS 29.503 V16.0.0 are underlined)

[0149]

[0150] Table 4-2: Definition of type LocationReportingConfiguration

[0151] (Changes compared to Table 6.4.6.2.10-1 of 3GPP TS 29.503 V16.0.0 are underlined)

[0152]

[0153] At step 4, the UDM subscribes to UE location change event notifications by operating a Namf_EventExposure_Subscribe request through the API. More information is included in the request body as follows:

[0154] eventNotifyUri: http: / / example.nef01.com / notif

[0155] notifyCorrelationId: nef01-0001

[0156] subsChangeNotifyUri: http: / / example.udm.com / notif

[0157] subsChangeNotifyCorrelationId: udm01-0001

[0158] AmfEventType: LOCATION_REPORT

[0159] supi: imsi-xxxxxxxxxx

[0160] locationFilterList:

[0161] - 3GPP: CELL_ID,

[0162] - Non-3GPP: N3IWF, UE_IP, UDP_PORT

[0163] Although the current protocol can support event notification subscription for the UDM interested in untrusted 5G non-3GPP access, the AMF still cannot support UE location change events for trusted 5G non-3GPP access and wired 5G non-3GPP access, as described above. Enhancements need to be added to the AMF here to enable UE location change events for all possible 5G non-3GPP accesses. An example of an enhancement to the 3GPP protocol is as follows, where the added content is underlined.

[0164] Table 5: Enumerated LocationFilter

[0165] (Changes compared to Table 6.2.6.3.5-1 of 3GPP TS 29.518 V16.0.0 are underlined)

[0166] Enumeration value Description "TAI" Indicates that any changes in the TA used by the UE should be reported. "CELL_ID" Indicates that any changes in the cell used by the UE should be reported. "N3IWF" Indicates that any changes in the N3IWF node used by the UE should be reported. <![CDATA "TNGF” > <![CDATA Indicates that any changes in the TNGF node used by the UE should be reported. > "UE_IP" Indicates that any changes in the UE local IP address should be reported. "UDP_PORT" Indicates that any changes in the local UDP port used by the UE should be reported. <![CDATA "WAGF” > <![CDATA Indicates that any changes in the WAGF node used by the UE should be reported. > <![CDATA "LINE_ID” > <![CDATA Indicates that any changes in the line identifier should be reported. > <![CDATA "HFC_ID” > <![CDATA Indicates that any changes in the HFC identifier should be reported. >

[0167] In addition, for the final AMF event report, the current AMF protocol needs to be extended to support the reporting of UE location from trusted 5G non-3GPP access and wired 5G non-3GPP access, as shown in Table 6 below.

[0168] Table 6: Definition of type N3gaLocation

[0169] (Changes compared to Table 5.4.4.10-1 of 3GPP TS 29.571 V16.0.0 are underlined)

[0170]

[0171] At step 5, the AMF sends a Namf_EventExposure_Subscribe response to the UDM for UE location change event notification subscription. At step 6, the UDM sends a Nudm_EventExposure_Subscribe response to the NEF for UE location change event notification subscription. At step 7, the NEF sends a Nnef_EventExposure_Subscribe response to the AF for UE location change event notification subscription.

[0172] For immediate location reporting (which can be referred to as case #l), at step 8, if immediate reporting was requested in the previous UE location change event notification subscription (steps 2-7), depending on the access network to which the UE is attached, the AMF can report the current location to the NEF immediately after step 5, for example:

[0173] - Current CELL_ID for 5G 3GPP access

[0174] - N3IWF, UE_IP, and UE_PORT for untrusted 5G non-3GPP access.

[0175] At step 9, if immediate reporting was requested in the previous UE location change event notification subscription (steps 2-7), depending on the access network to which the UE is attached, once the AMF report has been received, the NEF can report the current location to the AF, for example:

[0176] - Current CELL_ID for 5G 3GPP access

[0177] - For the N3IWF, UE_IP, and UE_PORT for untrusted 5G non-3GPP access.

[0178] For a UE location change in 3GPP access (which can be referred to as case #2), at step 10, it is assumed that the UE location has changed in 3GPP access. For example, due to moving to a new cell and registration from the new cell, the cell id has changed. At step 11, the AMF notifies the NEF in a consecutive event report for the UE location change event as follows based on the previous event subscription configuration:

[0179] - The new CELL_ID in 5G 3GPP access.

[0180] At step 12, once the event report has been received from the AMF, the NEF can report the current UE location to the AF as follows:

[0181] - The new CELL_ID in 5G 3GPP access.

[0182] For a UE location change in untrusted 5G non-3GPP access with an N3IWF node change (which can be referred to as case #3), at step 13, it is assumed that the UE location has changed in untrusted 5G non-3GPP access. For example, due to moving to another area and registration from a new N3IWF, the UE_IP and UE_Port have also changed. At step 14, the AMF notifies the NEF in a consecutive event report for the UE location change event as follows based on the previous event subscription configuration:

[0183] - The new N3IWF ID, new UE_IP, and new UE_Port for untrusted 5G non-3GPP access.

[0184] At step 15, once the event report has been received from the AMF, the NEF can report the current UE location to the AF as follows:

[0185] - The new N3IWF ID, new UE_IP, and new UE_Port for untrusted 5G non-3GPP access.

[0186] For UE location change in untrusted 5G non-3GPP access with the same N3IWF Id but changing UE_IP and UE_PORT (which can be referred to as case #4), at step 16, it is assumed that the UE location changes in untrusted 5G non-3GPP access. For example, due to moving to another attachment point but still under the same N3IWF, the UE_IP and UP_PORT are reallocated. At step 17, the AMF notifies the NEF in consecutive event reports for UE location change events based on the previous event subscription configuration as follows:

[0187] - The N3IWF ID for untrusted 5G non-3GPP access and the changed UE_IP and UE_PORT.

[0188] At step 18, once the event report has been received from the AMF, the NEF can report the current UE location to the AF as follows:

[0189] - The N3IWF ID for untrusted 5G non-3GPP access and the changed UE_IP and UE_PORT.

[0190] Figure 12 is a flowchart showing another exemplary process according to an embodiment of the present disclosure. As shown, this exemplary process relates to UE location change event subscription / notification for 5G 3GPP access and wired 5G non-3GPP access. Based on the previously proposed enhancements, more and more cases can now be supported, such as to support UE location change reporting:

[0191] - 3GPP accuracy: TA_LEVEL

[0192] - Non-3GPP accuracy: WAGF_ID, LINE_ID, HFC_ID.

[0193] Step 1 is the same as step 1 for UE registration to the 5G core network in Figure 11 . Steps 2-7 are similar to steps 2-7 in Figure 11 , and the only difference is regarding the UE location granularity of interest:

[0194] - 3GPP accuracy: TA_LEVEL (tracking area level)

[0195] - Non-3GPP accuracy: WAGF_ID, LINE_ID, HFC_ID.

[0196] For case #l (instant location report), steps 8-9 are similar to steps 8-9 in Figure 11 , but this time for instant reporting of the UE location:

[0197] - TA ID for 3GPP access

[0198] - WAGF ID, LINE_ID, or HFC_ID for non-3GPP access.

[0199] For scenario #2 (UE location change (TAID change) in 5G 3GPP access), steps 10 - 12 are similar to those in Figure 11 , but the UE location change is due to UE movement and registration from the new TA. So the new TA_ID in 3GPP access is reported.

[0200] For scenario #3 (UE location change (WAGF ID and LINE_ID change) in 5G non-3GPP access), steps 13 - 15 are similar to those in Figure 11 , but the UE location change is due to UE movement, and attachment to the new LINE_ID and registration from the new WAGF. So the new WAGF_ID and new LINE_ID for 5G wired non-3GPP access are reported.

[0201] For scenario #4 (UE location change in non-3GPP access under the same WAGF, but attachment to the new HFC_ID), steps 16 - 18 are similar to those in Figure 11 , but the UE location change is due to UE movement and attachment to the new HFC_ID, but under the same WAGF. So the same WAGF and new HFC_ID for 5G wired non-3GPP access are reported. Using the processes shown in Figure 11 and 12 , location change events can be supported end-to-end for UEs from all possible 5G non-3GPP accesses. It should be noted that two consecutively shown boxes in the figures can actually be executed substantially in parallel, or they can sometimes also be executed in the reverse order, depending on the functions involved.

[0202] Figure 13 is a block diagram showing a device suitable for use in practicing some embodiments of the present disclosure. For example, any one of the above-mentioned NEF entity, UDM entity, AMF entity, and AF entity can be implemented by device 1300. As shown, device 1300 may include a processor 1310, a memory 1320 storing programs, and an optional communication interface 1330 for data communication with other external devices via wired and / or wireless communication.

[0203] The program includes program instructions that, when executed by the processor 1310, enable the device 1300 to operate in accordance with embodiments of the present disclosure, as discussed above. That is, embodiments of the present disclosure can be implemented at least in part by computer software executable by the processor 1310, or by hardware, or by a combination of software and hardware.

[0204] The memory 1320 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The processor 1310 can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0205] Figure 14 is a block diagram showing a NEF entity according to an embodiment of the present disclosure. As shown, the NEF entity 1400 includes a first receiving module 1402, a first sending module 1404, a second receiving module 1406, and a second sending module 1408. The first receiving module 1402 can be configured to receive, from an AF entity, a first request for opening an event for subscribing to a location report for a terminal device, as described above with respect to block 602. The first request indicates at least one location report accuracy for 5G non-3GPP access of the terminal device. The first sending module 1404 can be configured to send, to a UDM entity, a second request for opening an event for subscribing to a location report for the terminal device, as described above with respect to block 604. The second request indicates the at least one location report accuracy. The second receiving module 1406 can be configured to receive the location information of the terminal device from an AMF entity, as described above with respect to block 606. The second sending module 1408 can be configured to send the location information of the terminal device to the AF entity, as described above with respect to block 608.

[0206] Figure 15 is a block diagram showing a UDM entity according to an embodiment of the present disclosure. As shown, the UDM entity 1500 includes a receiving module 1502 and a sending module 1504. The receiving module 1502 can be configured to receive, from a NEF entity, a first request for opening an event for subscribing to a location report for a terminal device, as described above with respect to block 702. The first request indicates at least one location report accuracy for non-3GPP access of the terminal device. The sending module 1504 can be configured to send, to an AMF entity, a second request for opening an event for subscribing to a location report for the terminal device, as described above with respect to block 704. The second request indicates the at least one location report accuracy.

[0207] Figure 16 It is a block diagram showing an AMF entity according to an embodiment of the present disclosure. As shown in the figure, the AMF entity 1600 includes a receiving module 1602, a determining module 1604, and a reporting module 1606. The receiving module 1602 may be configured to receive, from a UDM entity, a request for opening an event for subscribing to a location report for a terminal device, as described above with respect to block 802. This request indicates at least one location reporting accuracy for non-3GPP access of the terminal device via TNGF and / or WAGF. The determining module 1604 may be configured to determine the location information of the terminal device based on this request, as described above with respect to block 804. The reporting module 1606 may be configured to report the location information of the terminal device to a NEF entity, as described above with respect to block 806.

[0208] Figure 17 It is a block diagram showing an AF entity according to an embodiment of the present disclosure. As shown in the figure, the AF entity 1700 includes a sending module 1702 and a receiving module 1704. The sending module 1702 may be configured to send, to a NEF entity, a request for opening an event for subscribing to a location report for a terminal device, as described above with respect to block 1002. This request indicates at least one location reporting accuracy for 5G non-3GPP access of the terminal device. The receiving module 1704 may be configured to receive the location information of the terminal device from the NEF entity, as described above with respect to block 1004. The modules described above may be implemented by hardware or software or a combination of both.

[0209] Generally, various exemplary embodiments may be implemented in hardware or a dedicated circuit, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, a microprocessor, or other computing device, although the present disclosure is not limited thereto. Although various aspects of the exemplary embodiments of the present disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be well understood that, by way of non-limiting example, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, a dedicated circuit or logic, general hardware or a controller, or other computing device, or some combination thereof.

[0210] Thus, it should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be practiced in various components such as integrated circuit chips and modules. Accordingly, it should be understood that the exemplary embodiments of the present disclosure can be implemented in a device embodied as an integrated circuit, where the integrated circuit can include circuitry (and possibly, firmware) for embodying at least one or more of a data processor, a digital signal processor, a baseband circuit, and a radio frequency circuit that can be configured to operate in accordance with the exemplary embodiments of the present disclosure.

[0211] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be embodied in computer-executable instructions executed by one or more computers or other devices, such as embodied in one or more program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., which perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. The computer-executable instructions can be stored on a computer-readable medium such as a hard disk, an optical disk, a removable storage medium, a solid-state memory, a RAM, etc. Those skilled in the art will understand that the functions of the program modules can be combined or distributed as needed in various embodiments. Additionally, the functions can be embodied wholly or partially in firmware or hardware equivalents such as integrated circuits, field-programmable gate arrays (FPGAs), etc.

[0212] References in the present disclosure to "an embodiment", "embodiments", etc. mean that the described embodiments may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is within the knowledge of those skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0213] It should be understood that although terms such as "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the present disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0214] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the terms "comprises", "comprising", and / or "having", when used herein, specify the presence of stated features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. The term "connected" as used herein covers both direct and / or indirect connections between two elements.

[0215] The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or in any of its generalizations. Various modifications and adaptations of the above-described exemplary embodiments of the present disclosure will become apparent to those skilled in the relevant art in view of the above description when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure.

Claims

1. A method performed by a Network Exposure Function (NEF) entity, comprising: Receiving (602) from an Application Function (AF) entity a first request for opening an event for subscribing to location reports for a terminal device, wherein the first request indicates at least one location report accuracy for 5G non-3GPP access of the terminal device, and wherein a non-3GPP accuracy n3gppAccuracy attribute is used in the first request to indicate the at least one location report accuracy; Sending (604) to a Unified Data Management (UDM) entity a second request for opening an event for subscribing to location reports for the terminal device, wherein the second request indicates the at least one location report accuracy, and wherein the n3gppAccuracy attribute is used in the second request to indicate the at least one location report accuracy; Receiving (606) location information of the terminal device from an Access and Mobility Management Function (AMF) entity; and Sending (608) the location information of the terminal device to the AF entity.

2. The method according to claim 1, wherein The at least one location report accuracy includes one or more of the following: Non-3GPP Interworking Function (N3IWF) information indicating a change of an N3IWF node used by the terminal device; A Trusted Non-3GPP Gateway Function (TNGF) used by the terminal device; Internet Protocol (IP) address information indicating a change of the IP of the terminal device; A User Datagram Protocol (UDP) port used by the terminal device; A Wired Access Gateway Function (WAGF) used by the terminal device; A line identifier of an access point used by the terminal device; And A Hybrid Fiber Coaxial (HFC) identifier of an access point used by the terminal device.

3. The method according to any one of claims 1 to 2, wherein An accuracy attribute list in an array form is used in the second request to indicate the at least one location report accuracy.

4. The method according to any one of claims 1 to 2, wherein, The location information of the terminal device indicates one or more of the following: The N3IWF used by the terminal device; The TNGF used by the terminal device; The IP address of the terminal device; The UDP port used by the terminal device; The WAGF used by the terminal device; The line identifier of the access point used by the terminal device; And The HFC identifier of the access point used by the terminal device.

5. The method according to any one of claims 1 to 2, wherein The location information of the terminal device indicates one of the following: The initial location of the terminal device immediately after the second request is sent to the UDM entity; and The new location of the terminal device when a location change of the terminal device occurs.

6. A method performed by a Unified Data Management (UDM) entity, comprising: Receive (702) a first request from a Network Exposure Function (NEF) entity for opening an event for subscribing to location reports for a terminal device, where the first request indicates at least one location reporting accuracy for 5G non-3GPP access of the terminal device, and where the non-3GPP accuracy n3gppAccuracy attribute is used in the first request to indicate the at least one location reporting accuracy; and Send (704) a second request for opening an event for subscribing to location reports for the terminal device to an Access and Mobility Management Function (AMF) entity, where the second request indicates the at least one location reporting accuracy.

7. The method according to claim 6, wherein The at least one location reporting accuracy includes one or more of the following: Non-3GPP Interworking Function (N3IWF) information, which indicates a change in the N3IWF node used by the terminal device; Trusted Non-3GPP Gateway Function (TNGF) used by the terminal device; Internet Protocol (IP) address information, which indicates a change in the IP of the terminal device; User Datagram Protocol (UDP) port used by the terminal device; Wired Access Gateway Function (WAGF) used by the terminal device; Line identifier of the access point used by the terminal device; And Hybrid Fiber Coaxial (HFC) identifier of the access point used by the terminal device.

8. The method according to any one of claims 6 to 7, wherein The locationFilterList attribute of the AmfEvent data structure is used in the second request to indicate the at least one location reporting accuracy.

9. A method performed by an Application Function (AF) entity, comprising: Send (1002) a request for opening an event for subscribing to location reports for a terminal device to a Network Exposure Function (NEF) entity, where the request indicates at least one location reporting accuracy for 5G non-3GPP access of the terminal device, and where the non-3GPP accuracy n3gppAccuracy attribute is used in the request to indicate the at least one location reporting accuracy; and Receive (1004) location information of the terminal device from the NEF entity.

10. The method according to claim 9, wherein, The at least one location reporting accuracy includes one or more of the following: Non-3GPP Interworking Function (N3IWF) used by the terminal device; Trusted Non-3GPP Gateway Function (TNGF) used by the terminal device; Internet Protocol (IP) address of the terminal device; User Datagram Protocol (UDP) port used by the terminal device; Wired Access Gateway Function (WAGF) used by the terminal device; Line identifier of the access point used by the terminal device; And Hybrid Fiber Coaxial (HFC) identifier of the access point used by the terminal device.

11. The method according to any one of claims 9 to 10, wherein The location information of the terminal device indicates one or more of the following: Non-3GPP Interworking Function (N3IWF) used by the terminal device; Trusted Non-3GPP Gateway Function (TNGF) used by the terminal device; IP address of the terminal device; User Datagram Protocol (UDP) port used by the terminal device; WAGF used by the terminal device; Line identifier of the access point used by the terminal device; and HFC identifier of the access point used by the terminal device.

12. The method according to any one of claims 9 to 10, wherein, The location information of the terminal device indicates one of the following: The initial location of the terminal device immediately after the request is sent to the NEF entity; and The new location of the terminal device when a location change of the terminal device occurs.

13. A Network Exposure Function (NEF) entity (1300) comprising: At least one processor (1310); and At least one memory (1320), the at least one memory (1320) containing instructions executable by the at least one processor (1310), whereby the NEF entity (1300) is operable to: Receive a first request from an Application Function (AF) entity for opening an event for subscribing to location reports for a terminal device, wherein the first request indicates at least one location report accuracy for 5G non-3rd Generation Partnership Project (non-3GPP) access for the terminal device, and wherein the n3gppAccuracy attribute is used in the first request to indicate the at least one location report accuracy; Send a second request to a Unified Data Management (UDM) entity for opening an event for subscribing to location reports for the terminal device, wherein the second request indicates the at least one location report accuracy, and wherein the n3gppAccuracy attribute is used in the second request to indicate the at least one location report accuracy; Receive the location information of the terminal device from an Access and Mobility Management Function (AMF) entity; and Send the location information of the terminal device to the AF entity.

14. The NEF entity (1300) according to claim 13, wherein, The NEF entity (1300) is operable to perform the method according to any one of claims 2 to 5.

15. A Unified Data Management (UDM) entity (1300) comprising: At least one processor (1310); and At least one memory (1320), the at least one memory (1320) containing instructions executable by the at least one processor (1310), whereby the UDM entity (1300) is operable to: Receive a first request from a Network Exposure Function (NEF) entity for opening an event for subscribing to location reports for a terminal device, wherein the first request indicates at least one location report accuracy for 5G non-3rd Generation Partnership Project (non-3GPP) access for the terminal device, and wherein the non-3GPP accuracy n3gppAccuracy attribute is used in the first request to indicate the at least one location report accuracy; and Send a second request to an Access and Mobility Management Function (AMF) entity for opening an event for subscribing to location reports for the terminal device, wherein the second request indicates the at least one location report accuracy.

16. The UDM entity (1300) according to claim 15, wherein, The UDM entity (1300) is operable to perform the method according to any one of claims 7 to 8.

17. An Application Function (AF) entity (1300) comprising: At least one processor (1310); and at least one memory (1320), the at least one memory (1320) containing instructions executable by the at least one processor (1310), whereby the AF entity (1300) is operable to: send a request for event exposure for subscribing to location reports for a terminal device to a Network Exposure Function NEF entity, wherein the request indicates at least one location reporting accuracy for fifth generation 5G non-Third Generation Partnership Project i.e. non-3GPP access for the terminal device; and receive location information of the terminal device from the NEF entity.

18. The AF entity (1300) according to claim 17, wherein, The AF entity (1300) is operable to perform the method according to any one of claims 10 to 12.

19. A computer-readable storage medium comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 12.

Images