Address service entity selection method and apparatus, electronic device, and readable storage medium

Abstract

This application discloses an address service entity selection method, apparatus, electronic device, and readable storage medium, relating to the field of communication technology. The method includes: obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of a terminal UE; and determining a target address service entity based on the service capability information of the candidate address service entities. The preset storage space includes local storage space located in the current functional entity or off-site storage space located in a functional entity other than the current functional entity. By using the service capability information of address service entities stored in the current functional entity or other functional entities, candidate address service entities matching the UE's address requirement information are determined, and the target address service entity is further selected from the matched candidate address service entities to obtain a target address service entity that better meets the user's needs, thereby improving the user's location service experience.

Description

Technical Field

[0001] This application relates to the field of communication technology, and specifically to an address service entity selection method, apparatus, electronic device, and readable storage medium. Background Technology

[0002] In communication networks such as 5G core networks, Location Management Function (LMF) entities and / or Gateway Mobile Location Centre (GMLC) entities are typically used to determine the location of terminals connected to the communication network. In existing technologies, LMF and / or GMLC providing location services are usually selected using the terminal's slice information. However, when selecting LMF and / or GMLC based on the terminal's slice information, there is a problem of selecting inappropriate LMF and / or GMLC. Summary of the Invention

[0003] This application provides a method, apparatus, electronic device, and readable storage medium for selecting an address service entity.

[0004] This application provides an address service entity selection method, which includes: obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of a terminal UE; and determining a target address service entity based on the service capability information of the candidate address service entities.

[0005] This application provides another method for selecting an address service entity. The method includes: sending service capability information of candidate address service entities in a preset storage space to a target functional entity, so that the target functional entity can determine a target address service entity based on the service capability information of the candidate address service entities; wherein the service capability information of the candidate address service entities is information obtained from the preset storage space based on the address requirement information of the terminal UE.

[0006] This application provides an address service entity selection device, including: an acquisition module configured to acquire service capability information of candidate address service entities from a preset storage space based on address requirement information of a terminal UE; and an entity determination module configured to determine a target address service entity based on the service capability information of the candidate address service entities.

[0007] This application provides another address service entity selection device, including: a sending module configured to send service capability information of candidate address service entities in a preset storage space to a target functional entity, so that the target functional entity can determine a target address service entity based on the service capability information of the candidate address service entities; wherein the service capability information of the candidate address service entities is information obtained from the preset storage space based on the address requirement information of the terminal UE.

[0008] This application provides an electronic device, including: one or more processors; and a memory storing one or more programs thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any of the address service entity selection methods in this application.

[0009] This application provides a readable storage medium storing a computer program that, when executed by a processor, implements any of the address service entity selection methods described in this application.

[0010] According to the address service entity selection method, apparatus, electronic device, and readable storage medium of this application, based on the address requirement information of the terminal UE, service capability information of candidate address service entities is obtained from a preset storage space, and a target address service entity is determined based on the service capability information of the candidate address service entities. The preset storage space includes local storage space located in the current functional entity or off-site storage space located in a functional entity other than the current functional entity. By using the service capability information of address service entities stored in the current functional entity or other functional entities, candidate address service entities matching the address requirement information of the terminal UE are determined, and a target address service entity is further selected from the matched candidate address service entities, thereby obtaining a target address service entity that better meets the user's needs. When providing location services to the terminal based on the target address service entity, the user's location service experience can be effectively improved.

[0011] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0012] Figure 1 This diagram illustrates the composition of the communication system network architecture in an embodiment of this application.

[0013] Figure 2 This diagram illustrates the composition of the location service network architecture in an embodiment of this application.

[0014] Figure 3 This is a flowchart illustrating an address service entity selection method according to an embodiment of this application.

[0015] Figure 4 This is a flowchart illustrating the address service entity selection method in another embodiment of this application.

[0016] Figure 5 This illustration shows a flowchart of a method for obtaining service capability information of alternative address service entities according to an embodiment of this application.

[0017] Figure 6 This is a flowchart illustrating another method for obtaining service capability information of alternative address service entities according to an embodiment of this application.

[0018] Figure 7 This illustration shows a flowchart of another method for obtaining service capability information of alternative address service entities according to an embodiment of this application.

[0019] Figure 8 This diagram illustrates a flowchart of an address service entity selection method according to another embodiment of the present application.

[0020] Figure 9 A flowchart illustrating an address service entity selection method according to another embodiment of this application is shown.

[0021] Figure 10 This diagram illustrates a flowchart of an address service entity registration method according to an embodiment of this application.

[0022] Figure 11 This diagram illustrates a flowchart of an address service entity registration and update method according to an embodiment of this application.

[0023] Figure 12 This diagram illustrates the structural composition of an address service entity selection device according to an embodiment of this application.

[0024] Figure 13 This diagram illustrates the structural composition of an address service entity selection device according to another embodiment of this application.

[0025] Figure 14 This diagram illustrates the structural composition of an address service entity selection device according to another embodiment of the present application.

[0026] Figure 15 This diagram illustrates the structural composition of an address service entity selection device according to another embodiment of this application.

[0027] Figure 16 This illustration shows a scenario diagram of an address selection service entity in an embodiment of this application.

[0028] Figure 17 This illustration shows another scenario of selecting an address service entity in an embodiment of this application.

[0029] Figure 18 This illustration shows another scenario diagram of an address selection service entity in an embodiment of this application.

[0030] Figure 19 A structural diagram of an exemplary hardware architecture of a computing device capable of implementing the address service entity selection method and apparatus according to embodiments of the present invention is shown. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be arbitrarily combined with each other.

[0032] Location Service (LCS) is a value-added service that has attracted much attention in the mobile communications field in recent years. It primarily obtains the terminal's location information through address service entities such as LMF and / or GMLC to provide location services. Furthermore, other services can be derived from the location information obtained through LCS, such as location-based navigation services.

[0033] In practical applications, LMF and / or GMLC can be deployed in various ways, such as centralized deployment, decentralized deployment, and independent deployment, to meet the different needs of different users for location services. However, in existing technologies, LMF and / or GMLC are usually selected based on terminal slice information without considering the actual deployment of LMF and / or GMLC, as well as the terminal's access location and / or access network information. Therefore, the selected LMF and / or GMLC may be unsuitable.

[0034] In view of this, embodiments of this application provide an address service entity selection method, apparatus, electronic device, and readable storage medium. By using the service capability information of address service entities stored in the current functional entity or other functional entities, alternative address service entities that match the address requirements of the terminal are determined, and a target address service entity is further selected from the matched alternative address service entities, thereby obtaining a target address service entity that better meets the user's needs. When providing location services to the terminal based on the target address service entity, the user's location service experience can be effectively improved.

[0035] To better understand this application, a brief introduction will first be given to the communication network and its functional entities involved in the embodiments of this application.

[0036] Figure 1 This diagram illustrates the composition of the communication system network architecture in an embodiment of this application. Figure 1As shown, the devices and functional entities in the network architecture of this communication system include: terminal 100, wireless access network 101, network function library functional entity 102, unified data management functional entity 103, policy control functional entity 104, capability opening functional entity 105, application functional entity 106, access and mobility management functional entity 107, session management functional entity 108, authentication server functional entity 109, network slice selection functional entity 110, and user plane functional entity 111.

[0037] Among them, the terminal (User Equipment, UE) 100 mainly accesses the 5G network and obtains services through the wireless air interface. Specifically, the terminal interacts with the base station through the air interface and interacts with the access and mobility management function (AMF) entity of the core network through the non-access stratum signaling (NAS).

[0038] The Radio Access Network (RAN) 101 is responsible for scheduling air interface resources for terminal access to the network and managing air interface connections.

[0039] The Network Function Repository Function (NRF) entity 102 belongs to the core network control plane entity and is responsible for the dynamic registration of network function service capabilities and network function discovery.

[0040] Unified Data Management (UDM) entity 103 belongs to the core network control plane entity, is owned by the user server, and permanently stores user subscription data.

[0041] The Policy Control Functionality (PCF) entity 104 belongs to the core network control plane entities and is responsible for access and mobility management policies, UE policies, session management policies, and charging rules. This entity mainly generates access and mobility management policies, UE routing policies, Quality of Service (QoS) rules for user data transmission, and charging rules based on service information, user subscription information, and operator configuration information.

[0042] The Network Exposure Function (NEF) entity 105 is a core network control plane entity responsible for exposing mobile network capabilities to the outside world.

[0043] Application Function (AF) entity 106 is an application entity responsible for providing specific services to users.

[0044] The Access and Mobility Management function (AMF) entity 107 belongs to the core network control plane entity and is mainly responsible for user mobility management, including registration and temporary identifier allocation; maintaining idle and connected states and state transitions; handover in the connected state; and triggering paging functions in the user's idle state.

[0045] The Session Management function (SMF) entity 108 belongs to the core network control plane entity. It is mainly responsible for maintaining Protocol Data Unit Sessions (PDU Sessions), allocating Internet Protocol (IP) addresses to users, and has QoS control and billing functions. When a user is in IDLE state, it receives downlink data packets, buffers them, and notifies the AMF to page the user.

[0046] The Authentication Server Function (AUSF) entity 109 belongs to the core network control plane entity and is mainly responsible for authenticating and authorizing users to ensure that users are legitimate users.

[0047] The Network Slice Selection Function (NSSF) entity 110 belongs to the core network control plane entity and is responsible for selecting the target network slice instance (NSI).

[0048] User plane function (UPF) entity 111 belongs to the core network user plane function entity. It is responsible for forwarding user data packets and also performs statistics on user data packets for billing and other functions.

[0049] Figure 2 This diagram illustrates the composition of the location service network architecture in an embodiment of this application. Figure 2As shown, the devices and functional entities in this location service network architecture include: terminal 200, wireless access network 201, network function library functional entity 202, address management functional entity 203, unified data management functional entity 204, access and mobility management functional entity 205, gateway mobile location center entity 206, and location service client 207.

[0050] Among them, the location management function entity 203 and the gateway mobile location center entity 206 are both address service entities used to provide location services for terminals; the location service client (LCS Client) 207 is responsible for deploying user location services.

[0051] Specifically, the Location Management Function (LMF) entity 203 belongs to the core network control plane entity and is responsible for collecting, calculating, and determining the relevant location information of the terminal 200. The Gateway Mobile Location Centre (GMLC) entity 206 belongs to the core network control plane entity and is responsible for interacting with the location service client 207 and the access and mobility management function entity 205, executing the location request of the location service client 207 and sending back the location result. The functions of the terminal 200, the radio access network 201, the network function library entity 202, the unified data management function entity 204, and the access and mobility management function entity 205 are described in the previous embodiment and will not be repeated here.

[0052] It should be noted that the number of location management function entities 203 and gateway mobile location center entities 206 can be one or more. According to existing technology, if the access and mobility management function entity 205 needs to select an address service entity, and selects the address service entity providing location services from multiple location management function entities 203 and / or gateway mobile location center entities 206 solely based on the terminal's slice information, the selection of such entities may be inappropriate because the terminal's location and access network information, as well as the service area and service network of the address service entity, are not considered. This can negatively impact the user's location service experience. Therefore, how to select a suitable address service entity to improve the user's location service experience has become an urgent problem to be solved.

[0053] Figure 3 This diagram illustrates a flowchart of an address service entity selection method according to an embodiment of this application. This address service entity selection method can be applied to functional entities that need to select an address service entity or need to determine whether to reselect an address service entity. Figure 3 As shown, the address service entity selection method in this application embodiment may include the following steps.

[0054] Step S301: Based on the address requirement information of the terminal UE, obtain the service capability information of the alternative address service entity from the preset storage space.

[0055] The address requirement information of the terminal UE includes the terminal UE's access location information and / or the terminal UE's access network information. The terminal's access location information can represent the terminal's current location. In some embodiments, the terminal's access location information includes any one or more of the following: the tracking area (TA), the access cell, and the access base station. For example, the terminal's access location information includes the TA the terminal is currently accessing, or the TA the terminal last accessed that the current functional entity can perceive. The terminal's access network information includes information about the networks the terminal accesses. In some embodiments, a Closed Access Group (CAG) identifier can be used to represent the terminal's access network information. For example, the terminal's access network information includes a list or subset of CAG identifiers supported by the cell the terminal is currently accessing, or a list or subset of CAG identifiers that the terminal is allowed to access.

[0056] Address service entities include Location Management Function (LMF) entities and / or Gateway Mobile Location Center (GMLC) entities. Candidate address service entities are one or more address service entities selected from the address service entities based on the terminal's address requirement information. The service capability information of a candidate address service entity includes its service area information and / or its service network information. The service area information indicates the area where the candidate address service entity can provide services. In some embodiments, the service area information includes one or a set of Location Area Controllers (TAs), indicating that the candidate address service entity can provide location services within the aforementioned TAs. The service network information indicates the network where the candidate address service entity can provide services. In some embodiments, the service network information includes one or a set of Location Controller (CAG) identifiers, indicating that the candidate address service entity can provide location services within the network corresponding to the aforementioned CAG identifier.

[0057] The preset storage space includes local storage space set in the current functional entity or off-site storage space set in functional entities other than the current functional entity. Furthermore, the preset storage space pre-stores the service capability information of address service entities, allowing the current functional entity to select the service capability information of alternative address service entities based on the terminal's address requirement information.

[0058] In some embodiments, the local storage space includes the storage space used by the current functional entity to store configuration information (e.g., Local_NF (local configuration functional entity)), wherein the configuration information includes the service capability information of the address service entity, and the current functional entity includes, but is not limited to, the access and mobility management functional entity; the off-site storage space includes the storage space set in the unified data management functional entity UDM or the storage space set in the network function library functional entity NRF.

[0059] In other words, based on the terminal's address requirement information, the current functional entity can obtain service capability information of alternative address service entities from local storage, from storage pre-set in the UDM, or from storage pre-set in the NRF. By setting preset storage spaces for multiple functional entities such as the current entity and others, the channels for the current functional entity to obtain service capability information of alternative address service entities are increased, allowing the current functional entity to obtain the required information from any of the aforementioned storage spaces, ensuring that the current functional entity can successfully obtain the service capability information of alternative address service entities.

[0060] In some embodiments, when the off-site storage space is a storage space located in the UDM, obtaining service capability information of candidate address service entities from a preset storage space based on the terminal's address requirement information includes: sending an address service entity subscription data acquisition request to the UDM; wherein the address service entity subscription data acquisition request includes the terminal's address requirement information; and receiving an address service entity subscription data feedback message returned by the UDM; wherein the address service entity subscription data feedback message includes service capability information of candidate address service entities, and the service capability information of candidate address service entities is information determined by the UDM based on the terminal's address requirement information and the service capability information of a first address service entity, the service capability information of the first address service entity being pre-stored in the UDM's storage space. In other words, the candidate address service entities in the address service entity subscription data feedback message are address service entities determined by the UDM that can meet the terminal's address requirement information.

[0061] By including the terminal's address requirement information in the address service entity's subscription data acquisition request, the UDM can filter candidate address service entities that meet the terminal's address requirements from the preset storage space, and feed back the service capability information of the candidate address service entities to the current functional entity. This allows the current functional entity to select a target address service entity that better meets the user's needs based on the service capability information of the candidate address service entities, thereby effectively improving the user's location service experience when providing location services to the terminal based on the target address service entity.

[0062] In some specific implementations, the service capability information of the first address service entity is obtained by the UDM based on the address service entity subscription request sent by the terminal; wherein, the address service entity subscription request includes the service capability information of the address service entity that has subscribed with the terminal. The UDM pre-stores the service capability information of the first address service entity, providing a corresponding data foundation for the current functional entity to select an address service entity.

[0063] In other embodiments, when the off-site storage space is a storage space set up in the NRF, the service capability information of candidate address service entities is obtained from a preset storage space according to the terminal's address requirement information. This includes: sending an address service entity discovery request to the NRF; wherein the address service entity discovery request includes the terminal's address requirement information; and receiving an address service entity discovery feedback message returned by the NRF; wherein the address service entity discovery feedback message includes the service capability information of candidate address service entities, and the service capability information of the candidate address service entities is information determined by the NRF based on the terminal's address requirement information and the service capability information of a second address service entity, the service capability information of the second address service entity being pre-stored in the NRF's storage space. In other words, the candidate address service entities in the address service entity discovery feedback message are address service entities determined by the NRF that can satisfy the terminal's address requirement information.

[0064] By including the terminal's address requirement information in the address service entity discovery request, the NRF can filter candidate address service entities that meet the terminal's address requirements from the preset storage space and feed back the service capability information of the candidate address service entities to the current functional entity. This allows the current functional entity to select a target address service entity that better meets the user's needs based on the service capability information of the candidate address service entities, thereby effectively improving the user's location service experience when providing location services to the terminal based on the target address service entity.

[0065] In some specific implementations, the service capability information of the second address service entity is obtained by the NRF based on the address service entity registration request and / or address service entity registration update request sent by the address service entity; wherein, the address service entity registration request and / or address service entity registration update request includes the service capability information of the address service entity to be registered and / or to be registered and updated. The NRF pre-stores the service capability information of the second address service entity, providing a corresponding data foundation for the current functional entity to select the address service entity.

[0066] In some other embodiments, when the preset storage space is the local storage space set in the current functional entity, the service capability information of the alternative address service entity is obtained from the preset storage space according to the address requirement information of the terminal, including: determining the alternative address service entity according to the address requirement information of the terminal and the service capability information of the third address service entity; wherein, the service capability information of the third address service entity is pre-stored in the storage space of the current functional entity; and obtaining the service capability information of the alternative address service entity.

[0067] Specifically, the current functional entity determines the alternative address service entity based on the terminal's address requirement information and the service capability information of the third address service entity, including: determining the alternative address service entity based on the terminal's access location information and the service area information of the third address service entity; or, determining the alternative address service entity based on the terminal's access network information and the service network information of the third address service entity; or, determining the alternative address service entity based on the terminal's access location information and access network information, as well as the service area information and service network information of the third address service entity.

[0068] In other words, when the current functional entity selects a candidate address service entity based on local storage space, it can do so based on the network information of the terminal and the address service entity, the location information of the terminal and the address service entity, or a combination of the service network and location information of the terminal and the address service entity. This allows the current functional entity to determine the corresponding candidate address service entity based on different types of information, thereby ensuring that the current functional entity can obtain the service capability information of the candidate address service entity in different information scenarios.

[0069] Step S302: Determine the target address service entity based on the service capability information of the candidate address service entities.

[0070] The number of candidate address service entities can be one or more. When there are multiple candidate address service entities, the current functional entity must select one of them as the target address service entity.

[0071] In some embodiments, determining the target address service entity based on the service capability information of the candidate address service entities includes: determining the service capability level of the candidate address service entities based on the service capability information of the candidate address service entities; and determining the target address service entity based on the service capability level of the candidate address service entities. The service capability level of the candidate address service entities is used to characterize the service capability level of the candidate address service entities.

[0072] For example, the candidate address service entities include a first candidate address service entity and a second candidate address service entity. The service area of ​​the first candidate address service entity is a first region, and the service area of ​​the second candidate address service entity is a second region. Furthermore, the first region is a subset of the second region (i.e., the first region is a part of the second region). Based on this, it is determined that the service capability level of the second candidate address service entity is higher than that of the first candidate address service entity. Therefore, the second candidate address service entity is selected as the target address service entity.

[0073] In this embodiment, when there are multiple candidate address service entities, the relatively optimal address service entity can be determined based on the service capability level of the candidate address service entities, and it can be used as the target address service entity, thereby further improving the user's location service experience.

[0074] In some other embodiments, the service capability information of the candidate address service entity also includes the service slice information of the candidate address service entity. Determining the target address service entity based on the service capability information of the candidate address service entity includes: determining the target address service entity based on the service slice information of the candidate address service entity; wherein the target address service entity is a candidate address service entity that matches the access slice of the terminal.

[0075] For example, the alternative address service entities include a first alternative address service entity, a second alternative address service entity, and a third alternative address service entity. The service slices of the first alternative address service entity are the first slice and the second slice, the service slice of the second alternative address service entity is the first slice, and the service slice of the third alternative address service entity is the third slice. Assuming the terminal's access slice is the third slice, based on this, the third alternative address service entity that matches the terminal's access slice is selected as the target address service entity.

[0076] It should be noted that the target address service entity can also be determined based on the service capability level and service slice information of the candidate address service entities. For example, when there are multiple candidate address service entities that match the terminal's access slice, the target address service entity can be further selected from them based on the service capability level of the matched candidate address service entities.

[0077] In this embodiment, based on the terminal's address requirement information, service capability information of candidate address service entities is obtained from a preset storage space. Then, based on this information, a target address service entity is determined. The preset storage space includes either local storage space within the current functional entity or off-site storage space within a functional entity other than the current functional entity. By using the service capability information of address service entities stored in the current functional entity or other functional entities, candidate address service entities matching the terminal's address requirement information are determined. The target address service entity is then further selected from the matched candidate address service entities, thereby obtaining a target address service entity that better meets the user's needs. When providing location services to the terminal based on the target address service entity, this effectively improves the user's location service experience.

[0078] Figure 4 This diagram illustrates a flowchart of an address service entity selection method according to another embodiment of this application. This address service entity selection method can be applied to functional entities that need to select an address service entity or need to determine whether to reselect an address service entity. For example... Figure 4 As shown, the address service entity selection method in this application embodiment may include the following steps.

[0079] Step S401: Determine the address service policy of the current functional entity.

[0080] The address service strategy is the strategy used by the current functional entity when selecting an address service entity.

[0081] In some embodiments, the address service policy includes any one of the following: a contracted address service policy, a remote address query service policy, and a locally configured address service policy.

[0082] In some specific implementations, when the current functional entity does not have the ability to communicate outwards or when the outward communication link is congested, the address service policy of the current functional entity can be set to a locally configured address service policy, so that the current functional entity can obtain the service capability information of the alternative address service entity based solely on the information pre-stored in the local storage space.

[0083] In some specific implementations, when the accuracy requirements of location services are high, it is necessary to obtain more accurate service capability information of candidate address service entities. Therefore, the address service strategy of the current functional entity can be set to the off-site query address service strategy, so as to determine the candidate address service entities based on more comprehensive and accurate data in the off-site storage space, and determine the better target address service entity based on the service capability information of the candidate address service entities, thereby improving the accuracy of location services.

[0084] In some specific implementations, when the latency requirements for location services are high, in order to simplify data processing and reduce latency, the address service policy of the current functional entity can be set to the subscribed address service policy, so as to directly select the target service entity based on the service capability information of the address service entity subscribed to by the terminal.

[0085] It should be noted that the above-mentioned address service strategies are merely illustrative examples, and other address service strategies not mentioned are also within the scope of protection of this application, which does not limit them.

[0086] Step S402: Determine the preset storage space based on the address service policy of the current functional entity.

[0087] When selecting an address service entity, the current functional entity can retrieve the service capability information of candidate address service entities from local storage, from storage pre-configured in the UDM, or from storage pre-configured in the NRF, based on the terminal's address requirement information. It then selects the target address service entity based on the service capability information of the candidate address service entities. The specific method and pre-configured storage space from which to retrieve the service capability information of the candidate address service entities can be determined according to the address service strategy set by the current functional entity.

[0088] In some embodiments, determining a preset storage space based on the address service policy of the current functional entity includes: determining the preset storage space as an off-site storage space set in the UDM when the address service policy of the current functional entity is a subscribed address service policy; determining the preset storage space as an off-site storage space set in the NRF when the address service policy of the current functional entity is an off-site query address service policy; and determining the preset storage space as a local storage space set in the current functional entity when the address service policy of the current functional entity is a locally configured address service policy.

[0089] By setting the correspondence between different address service policies and preset storage spaces, the current functional entity can quickly and accurately determine the corresponding preset storage space after determining the address service policy based on this correspondence.

[0090] It should be noted that the current functional entity may not have an address service policy set; in this case, the address service policy is in its default state. In this scenario, the current functional entity can prioritize selecting an address service entity based on the terminal's subscription information, thus ensuring that it can still select a suitable address service entity even without a set address service policy.

[0091] In some embodiments, when the address service policy of the current functional entity is in the default state, the current functional entity sends an address service entity subscription data acquisition request to the UDM; wherein, the address service entity subscription data acquisition request includes the terminal's address requirement information; and receives an address service entity subscription data feedback message returned by the UDM; wherein, the address service entity subscription data feedback message includes the service capability information of the candidate address service entity, and the candidate address service entity is information determined by the UDM based on the terminal's address requirement information and the service capability information of the first address service entity, and the service capability information of the first address service entity is pre-stored in the UDM's storage space.

[0092] Step S403: Based on the address requirement information of the terminal UE, obtain the service capability information of the alternative address service entity from the preset storage space.

[0093] Step S404: Determine the target address service entity based on the service capability information of the candidate address service entities.

[0094] It should be noted that steps S403 to S404 in this embodiment are the same as steps S301 to S302 in the previous embodiment, and will not be repeated here.

[0095] In this embodiment, the address service strategy of the current functional entity is first determined, then a preset storage space matching the address service strategy is determined, the service capability information of candidate address service entities is obtained from the matched preset storage space, and the target address service entity is determined based on the service capability information of the candidate address service entities. By pre-setting an address service strategy for the current functional entity according to the user's location service needs or actual application scenarios, and by obtaining the service capability information of candidate address service entities from the corresponding preset storage space based on the address service strategy, and selecting the target address service entity based on the obtained information, the system can flexibly meet user needs or application scenario requirements, thereby effectively improving the user's location service experience.

[0096] Figure 5 This diagram illustrates a flowchart of a method for obtaining service capability information of alternative address service entities according to an embodiment of this application. Figure 5 As shown, the method for obtaining service capability information of alternative address service entities may include the following steps.

[0097] Step S501: Send an address service entity subscription data acquisition request to the unified data management function entity UDM.

[0098] The address service entity's contract data acquisition request includes the terminal's address requirement information.

[0099] The terminal's address requirement information includes the terminal's access location information and / or the terminal's access network information. The terminal's access location information can represent the terminal's current location. In some embodiments, the terminal's access location information includes any one or more of the following: the TA (Transmission Area Code) the terminal is accessing, the access cell, and the access base station. For example, the terminal's access location information includes the TA the terminal is currently accessing, or the TA the terminal last accessed, which is perceptible to the current functional entity. The terminal's access network information includes information about the networks the terminal accesses. In some embodiments, CAG (Confirmation Agent Query) identifiers can be used to represent the terminal's access network information. For example, the terminal's access network information includes a list or subset of CAG identifiers supported by the cell the terminal is currently accessing, or a list or subset of CAG identifiers that the terminal is allowed to access.

[0100] Step S502: Receive the address service entity subscription data feedback message returned by UDM.

[0101] The address service entity subscription data feedback message includes the service capability information of the candidate address service entities. The service capability information of the candidate address service entities is determined by the UDM based on the terminal's address requirement information and the service capability information of the first address service entity. The service capability information of the first address service entity is pre-stored in the UDM's storage space.

[0102] The service capability information of the alternative address service entity includes the service area information and / or the service network information of the alternative address service entity. The service area information of the alternative address service entity indicates the area where the alternative address service entity can provide services. In some embodiments, the service area information of the alternative address service entity includes one or a set of Location Areas (TAs), indicating that the alternative address service entity can provide location services on the aforementioned TAs. The service network information of the alternative address service entity indicates the network information that the alternative address service entity can provide services on. In some embodiments, the service network information of the alternative address service entity includes one or a set of Location AG identifiers, indicating that the alternative address service entity can provide location services on the network corresponding to the aforementioned CAG identifier.

[0103] In this embodiment, the current functional entity obtains the service capability information of the candidate address service entities from the storage space preset in UDM. Specifically, the above information is obtained through the address service entity subscription data acquisition request and the address service entity subscription data feedback message. In order to select the target functional entity based on the obtained service capability information of the candidate address service entities, the matching degree of the selected address service entities can be improved, thereby enhancing the user's location service experience.

[0104] Figure 6This diagram illustrates a flowchart of yet another method for obtaining service capability information of alternative address service entities according to an embodiment of this application. Figure 6 As shown, the method for obtaining service capability information of alternative address service entities may include the following steps.

[0105] Step S601: Send an Address Service Entity Discovery Request to the Network Function Library Function Entity (NRF).

[0106] The address service entity discovery request includes the terminal's address requirement information.

[0107] The terminal's address requirement information includes the terminal's access location information and / or the terminal's access network information. The terminal's access location information can represent the terminal's current location. In some embodiments, the terminal's access location information includes any one or more of the following: the TA (Transmission Area Code) the terminal is accessing, the access cell, and the access base station. For example, the terminal's access location information includes the TA the terminal is currently accessing, or the TA the terminal last accessed, which is perceptible to the current functional entity. The terminal's access network information includes information about the networks the terminal accesses. In some embodiments, CAG (Confirmation Agent Query) identifiers can be used to represent the terminal's access network information. For example, the terminal's access network information includes a list or subset of CAG identifiers supported by the cell the terminal is currently accessing, or a list or subset of CAG identifiers that the terminal is allowed to access.

[0108] Step S602: Receive the address service entity discovery feedback message returned by NRF.

[0109] The address service entity discovery feedback message includes the service capability information of the candidate address service entity. The service capability information of the candidate address service entity is determined by the NRF based on the terminal's address requirement information and the service capability information of the second address service entity. The service capability information of the second address service entity is pre-stored in the NRF's storage space.

[0110] The service capability information of the alternative address service entity includes the service area information and / or the service network information of the alternative address service entity. The service area information of the alternative address service entity indicates the area where the alternative address service entity can provide services. In some embodiments, the service area information of the alternative address service entity includes one or a set of Location Areas (TAs), indicating that the alternative address service entity can provide location services on the aforementioned TAs. The service network information of the alternative address service entity indicates the network information that the alternative address service entity can provide services on. In some embodiments, the service network information of the alternative address service entity includes one or a set of Location AG identifiers, indicating that the alternative address service entity can provide location services on the network corresponding to the aforementioned CAG identifier.

[0111] In this embodiment, the current functional entity obtains the service capability information of the candidate address service entities from the storage space preset in the NRF. Specifically, the above information is obtained through the address service entity discovery request and the address service entity discovery feedback message. In order to select the target functional entity based on the obtained service capability information of the candidate address service entities, the matching degree of the selected address service entities can be improved, thereby enhancing the user's location service experience.

[0112] Figure 7 This diagram illustrates a flowchart of another method for obtaining service capability information of alternative address service entities according to an embodiment of this application. Figure 7 As shown, the method for obtaining service capability information of alternative address service entities may include the following steps.

[0113] Step S701: Determine the alternative address service entity based on the address requirement information of the terminal UE and the service capability information of the third address service entity.

[0114] The terminal's address requirement information includes the terminal's access location information and / or the terminal's access network information. The terminal's access location information can represent the terminal's current location. In some embodiments, the terminal's access location information includes any one or more of the following: the TA (Telematics Access Provider), the access cell, and the access base station. For example, the terminal's access location information includes the TA the terminal is currently accessing, or the TA the terminal last accessed, which is perceptible to the current functional entity. The terminal's access network information includes information about the network the terminal accesses. In some embodiments, a CAG (Confirmation Agent Grading) identifier can be used to represent the terminal's access network information. For example, the terminal's access network information includes a list or subset of CAG identifiers supported by the cell the terminal is currently accessing, or a list or subset of CAG identifiers that the terminal is allowed to access.

[0115] The service capability information of the third address service entity is pre-stored in the storage space of the current functional entity. In some embodiments, the service capability information of the third address service entity may be the configuration information of the current functional entity, which is used to select a candidate address service entity based on the local configuration information when the current functional entity cannot obtain the service capability information of the candidate address service functional entity from other functional entities, and then determine the target address service entity.

[0116] In some embodiments, determining a candidate address service entity based on the terminal's address requirement information and the service capability information of the third address service entity includes: determining a candidate address service entity based on the terminal's access location information and the service area information of the third address service entity; or, determining a candidate address service entity based on the terminal's access network information and the service network information of the third address service entity; or, determining a candidate address service entity based on the terminal's access location information and access network information, as well as the service area information and service network information of the third address service entity.

[0117] Step S702: Obtain the service capability information of the alternative address service entity.

[0118] The service capability information of the candidate address service entity includes the service area information and / or service network information of the candidate address service entity. The service area information of the candidate address service entity indicates the area where the candidate address service entity can provide services. In some embodiments, the service area information of the candidate address service entity includes one or a group of Location Areas (TAs), indicating that the candidate address service entity can provide location services within the aforementioned TAs. The service network information of the candidate address service entity indicates the network information where the candidate address service entity can provide services. In some embodiments, the service network information of the candidate address service entity includes one or a group of Location AG identifiers, indicating that the candidate address service entity can provide location services within the network corresponding to the aforementioned CAG identifier.

[0119] In this embodiment, the current functional entity can obtain the service capability information of the candidate address service entities from the local storage space, so as to select the target functional entity based on the obtained service capability information of the candidate address service entities. This does not depend on the communication capability of the current functional entity, and can also improve the matching degree of the selected address service entities, thereby improving the user's location service experience.

[0120] Figure 8 This diagram illustrates a flowchart of an address service entity selection method according to another embodiment of the present application. This address service entity selection method can be applied to functional entities that set preset storage spaces. For example... Figure 8 As shown, the address service entity selection method in this application embodiment may include the following steps.

[0121] Step S801: Send the service capability information of the candidate address service entities of the preset storage space to the target functional entity so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities.

[0122] Among them, the service capability information of the alternative address service entity is obtained from the preset storage space based on the address requirement information of the terminal.

[0123] The terminal's address requirement information includes the terminal's access location information and / or the terminal's access network information. The terminal's access location information can represent the terminal's current location. In some embodiments, the terminal's access location information includes any one or more of the following: the TA (Transmission Area Code) the terminal is accessing, the access cell, and the access base station. For example, the terminal's access location information includes the TA the terminal is currently accessing, or the TA the terminal last accessed, which is perceptible to the current functional entity. The terminal's access network information includes information about the networks the terminal accesses. In some embodiments, CAG (Confirmation Agent Query) identifiers can be used to represent the terminal's access network information. For example, the terminal's access network information includes a list or subset of CAG identifiers supported by the cell the terminal is currently accessing, or a list or subset of CAG identifiers that the terminal is allowed to access.

[0124] Address service entities include LMFs and / or GMLCs. Candidate address service entities are one or more address service entities selected from the address service entities based on the terminal's address requirement information. The service capability information of a candidate address service entity includes its service area information and / or its service network information. The service area information indicates the area where the candidate address service entity can provide services. In some embodiments, the service area information includes one or a set of TAs, indicating that the candidate address service entity can provide location services within the aforementioned TAs. The service network information indicates the network information that the candidate address service entity can provide services within. In some embodiments, the service network information includes one or a set of CAG identifiers, indicating that the candidate address service entity can provide location services within the network corresponding to the aforementioned CAG identifier.

[0125] In some embodiments, the current functional entity includes a UDM or an NRF. Accordingly, the preset storage space includes the storage space set in the UDM or the storage space set in the NRF.

[0126] When the current functional entity is UDM, the service capability information of candidate address service entities in the preset storage space is sent to the target functional entity. This includes: responding to the address service entity subscription data acquisition request sent by the target functional entity, returning an address service entity subscription data feedback message to the target functional entity, so that the target functional entity can obtain the service capability information of the candidate address service entities based on the address service entity subscription data feedback message, and determine the target address service entity based on the service capability information of the candidate address service entities; wherein, the address service entity subscription data acquisition request includes the terminal's address requirement information, and the address service entity subscription data feedback message includes the service capability information of the candidate address service entities. In other words, the candidate address service entities in the address service entity subscription data feedback message are the address service entities determined by UDM that can meet the terminal's address requirement information.

[0127] When the current functional entity is an NRF, the service capability information of candidate address service entities in the preset storage space is sent to the target functional entity. This includes: responding to the address service entity discovery request sent by the target functional entity, returning an address service entity discovery feedback message to the target functional entity, so that the target functional entity can obtain the service capability information of the candidate address service entities based on the address service entity discovery feedback message, and determine the target address service entity based on the service capability information of the candidate address service entities; wherein, the address service entity discovery request includes the terminal's address requirement information, and the address service entity discovery feedback message includes the service capability information of the candidate address service entities. In other words, the candidate address service entities in the address service entity discovery feedback message are the address service entities determined by the NRF that can meet the terminal's address requirement information.

[0128] In this embodiment, the service capability information of candidate address service entities in the preset storage space is sent to the target functional entity, so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities. This allows the functional entity with location service needs to determine the candidate address service entities that match the terminal's address needs based on the service capability information of the address service entities in the preset storage space, and further select the target address service entity from the matched candidate address service entities, thereby obtaining a target address service entity that better meets the user's needs. When providing location services to the terminal based on the target address service entity, the user's location service experience can be effectively improved.

[0129] Figure 9 A flowchart illustrating an address service entity selection method according to another embodiment of this application is shown. This address service entity selection method can be applied to functional entities that set preset storage spaces. Figure 9 As shown, the address service entity selection method in this application embodiment may include the following steps.

[0130] Step S901: Based on the address requirement information of the terminal UE, obtain the service capability information of the alternative address service entity from the preset storage space.

[0131] The system pre-stores the service capability information of multiple address service entities in the preset storage space. Based on the terminal's address requirements, address service entities that cannot meet the terminal's address requirements are first excluded, thereby filtering out address service entities that can meet the terminal's address requirements. These address service entities that can meet the terminal's address requirements are then used as candidate address service entities. This narrows down the range of target address service entities for other functional entities (i.e., functional entities that need to select address service entities or need to determine whether to reselect address service entities), reducing the difficulty for other functional entities to select target address service entities.

[0132] In some embodiments, when the current functional entity is a UDM, service capability information of candidate address service entities is obtained from a preset storage space based on the terminal's address requirement information. This includes: determining candidate address service entities based on the terminal's access location information and the service area information of the first address service entity; or, determining candidate address service entities based on the terminal's access network information and the service network information of the first address service entity; or, determining candidate address service entities based on the terminal's access location information, access network information, and the service area and service network information of the first address service entity. The service capability information of the first address service entity is stored in the UDM's storage space.

[0133] It should be noted that, in this embodiment, when determining the candidate address service entity, the UDM can do so based on the network information of the terminal and the address service entity, the location information of the terminal and the address service entity, or a combination of the network and location information of the terminal and the address service entity. This allows the UDM to determine the corresponding candidate address service entity based on different types of information, thereby ensuring that the UDM can obtain the service capability information of the candidate address service entity in different information scenarios.

[0134] In some specific implementations, before step S901, the method further includes: the UDM receiving an address service entity subscription request sent by the terminal; wherein the address service entity subscription request includes service capability information of the address service entity that has subscribed with the terminal; and returning an address service entity subscription feedback message to the terminal. Furthermore, based on the address service entity subscription request, the UDM obtains the service capability information of the first address service entity and stores the service capability information of the first address service entity in a preset storage space; wherein the first address service entity is the address service entity that has subscribed with the terminal.

[0135] It should be noted that the UDM pre-stores the service capability information of the first address service entity, providing a corresponding data foundation for other functional entities to select the address service entity.

[0136] In other embodiments, when the current functional entity is an NRF, service capability information of candidate address service entities is obtained from a preset storage space based on the terminal's address requirement information. This includes: determining candidate address service entities based on the terminal's access location information and the service area information of the second address service entity; or, determining candidate address service entities based on the terminal's access network information and the service network information of the second address service entity; or, determining candidate address service entities based on the terminal's access location information and access network information, as well as the service area information and service network information of the second address service entity. The service capability information of the second address service entity is stored in the NRF's storage space.

[0137] It should be noted that, in this embodiment, when determining the candidate address service entity, the NRF can rely on the network information of the terminal and the address service entity, the location information of the terminal and the address service entity, or a combination of the network and location information of the terminal and the address service entity. This allows the NRF to determine the corresponding candidate address service entity based on different types of information, thereby ensuring that the NRF can obtain the service capability information of the candidate address service entity in different information scenarios.

[0138] In some specific implementations, before step S901, the method further includes: the NRF receiving an address service entity registration request and / or address service entity registration update request sent by the address service entity; wherein the address service entity registration request and / or address service entity registration update request includes service capability information of the address service entity to be registered and / or to be registered and updated; and returning an address service entity registration response message and / or address service entity registration update response message to the address service entity. Furthermore, based on the address service entity registration request and / or address service entity registration update request, the NRF obtains the service capability information of the second address service entity and stores the service capability information of the second address service entity in a preset storage space; wherein the second address service entity is the address service entity to be registered and / or to be registered and updated.

[0139] It should be noted that the NRF pre-stores the service capability information of the second address service entity, providing a corresponding data foundation for other functional entities to select the address service entity.

[0140] Step S902: Send the service capability information of the candidate address service entities of the preset storage space to the target functional entity so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities.

[0141] It should be noted that step S902 in this embodiment is the same as step S801 in the previous embodiment, and will not be described again here.

[0142] Figure 10 This diagram illustrates a flowchart of an address service entity registration method according to an embodiment of this application. This address service entity registration method can be applied to NRF (Network Request Forwarding). Figure 10 As shown, the address service entity registration method may include the following steps.

[0143] Step S1001: Receive the address service entity registration request sent by the address service entity.

[0144] The address service entity registration request includes the service capability information of the address service entity to be registered.

[0145] In some embodiments, the service capability information of an address service entity includes the service area information and / or the service network information of the address service entity. The service area information of the address service entity indicates the area in which the address service entity can provide services. In some embodiments, the service area information of the address service entity includes one or a set of Location Areas (TAs), indicating that the address service entity can provide address services within the aforementioned TAs. The service network information of the address service entity indicates the network information in which the address service entity can provide services. In some embodiments, the service network information of the address service entity includes one or a set of Coded Entities (CAGs), indicating that the address service entity can provide address services to the network corresponding to the aforementioned CAG.

[0146] Step S1002: Return an address service entity registration response message to the address service entity.

[0147] It should be noted that in the prior art, when an address service entity registers with the NRF, the address service entity registration request does not carry the service capability information of the address service entity to be registered. Therefore, the network function library entity cannot provide the service capability information of alternative address service entities to other functional entities (e.g., AMF).

[0148] In some embodiments, after step S1002, the method further includes: obtaining service capability information of a second address service entity based on the address service entity registration request; wherein the service capability information of the second address service entity is stored in the NRF's storage space.

[0149] In other words, after receiving an address service entity registration request, the NRF stores the service capability information of the address service entity to be registered carried in the address service entity registration request in the local storage space, so as to provide other functional entities (e.g., AMF) with the service capability information of alternative address service entities. This allows other functional entities to obtain a target address service entity that better meets the user's needs based on the service capability information of the alternative address service entities, and effectively improve the user's location service experience when providing location services to the terminal based on the target address service entity.

[0150] Figure 11 This diagram illustrates a flowchart of an address service entity registration and update method according to an embodiment of this application. This address service entity registration method can be applied to NRF. Figure 11 As shown, the address service entity registration update method may include the following steps.

[0151] Step S1101: Receive the address service entity registration update request sent by the address service entity.

[0152] The address service entity registration update request includes the service capability information of the address service entity to be registered and updated.

[0153] In some embodiments, the service capability information of an address service entity includes the service area information and / or the service network information of the address service entity. The service area information of the address service entity indicates the area in which the address service entity can provide services. In some embodiments, the service area information of the address service entity includes one or a set of Location Areas (TAs), indicating that the address service entity can provide address services within the aforementioned TAs. The service network information of the address service entity indicates the network information in which the address service entity can provide services. In some embodiments, the service network information of the address service entity includes one or a set of Coded Entities (CAGs), indicating that the address service entity can provide address services to the network corresponding to the aforementioned CAG.

[0154] In some embodiments, if the service capability information of a registered address service entity changes, the registered address service entity sends an address service entity registration update request to the NRF, and carries the updated service capability information of the registered address service entity in the address service entity registration update request.

[0155] Step S1102: Return an address service entity registration update response message to the address service entity.

[0156] In some embodiments, after step S1102, the method further includes: obtaining service capability information of a second address service entity based on the address service entity registration update request; wherein the service capability information of the second address service entity is stored in the NRF's storage space.

[0157] In other words, after receiving an address service entity registration update request, the NRF learns that the service capability information of the registered address service entity has changed, and stores the updated service capability information carried in the address service entity registration update request to overwrite the original service capability information in the local storage space, so as to obtain the latest and most accurate service capability information corresponding to the address service entity.

[0158] It should be noted that if the service area information of the address service entity is omitted in the address service entity registration request and / or address service entity registration update request sent by the address service entity to the NRF, it means that the address service entity does not restrict the service area; in other words, the address service entity can provide location services to terminals in all areas. Similarly, if the service network information of the address service entity is omitted in the address service entity registration request and / or address service entity registration update request sent by the address service entity to the NRF, it means that the address service entity does not restrict the service network; in other words, the address service entity can provide location services to access terminals in all networks.

[0159] Figure 12 This diagram illustrates the structural composition of an address service entity selection device according to an embodiment of this application. This address service entity selection device can be configured in functional entities that require selection of an address service entity or require determining whether to reselect an address service entity. Figure 12 As shown, the address service entity selection device 1200 includes the following modules:

[0160] The acquisition module 1201 is configured to acquire service capability information of alternative address service entities from a preset storage space based on the address requirement information of the terminal UE.

[0161] The terminal's address requirement information includes the terminal's access location information and / or the terminal's access network information. The terminal's access location information can represent the terminal's current location. In some embodiments, the terminal's access location information includes any one or more of the following: the TA (Transmission Area Code) the terminal is accessing, the access cell, and the access base station. For example, the terminal's access location information includes the TA the terminal is currently accessing, or the TA the terminal last accessed, which is perceptible to the current functional entity. The terminal's access network information includes information about the networks the terminal accesses. In some embodiments, CAG (Confirmation Agent Query) identifiers can be used to represent the terminal's access network information. For example, the terminal's access network information includes a list or subset of CAG identifiers supported by the cell the terminal is currently accessing, or a list or subset of CAG identifiers that the terminal is allowed to access.

[0162] Address service entities include LMFs and / or GMLCs. Candidate address service entities are one or more address service entities selected from the address service entities based on the terminal's address requirement information. The service capability information of a candidate address service entity includes its service area information and / or its service network information. The service area information indicates the area where the candidate address service entity can provide services. In some embodiments, the service area information includes one or a set of TAs, indicating that the candidate address service entity can provide location services within the aforementioned TAs. The service network information indicates the network information that the candidate address service entity can provide services within. In some embodiments, the service network information includes one or a set of CAG identifiers, indicating that the candidate address service entity can provide location services within the network corresponding to the aforementioned CAG identifier.

[0163] The preset storage space includes local storage space set in the current functional entity or off-site storage space set in functional entities other than the current functional entity. Furthermore, the preset storage space pre-stores the service capability information of address service entities, allowing the current functional entity to select the service capability information of alternative address service entities based on the terminal's address requirement information.

[0164] In some embodiments, the local storage space includes the storage space used by the current functional entity to store configuration information, wherein the configuration information includes the service capability information of the address service entity, and the current functional entity includes, but is not limited to, the access and mobility management functional entity; the off-site storage space includes the storage space set in the UDM or the storage space set in the NRF.

[0165] In other words, the acquisition module 1201 can obtain the service capability information of the alternative address service entity from the local storage space, the storage space preset in UDM, or the storage space preset in NRF, based on the address requirement information of the terminal.

[0166] In some embodiments, when the off-site storage space is a storage space located in the UDM, the acquisition module 1201 includes a first sending unit and a first receiving unit. The first sending unit is configured to send an address service entity subscription data acquisition request to the UDM, and the address service entity subscription data acquisition request includes the terminal's address requirement information. The first receiving unit is configured to receive an address service entity subscription data feedback message returned by the UDM, the address service entity subscription data feedback message including service capability information of candidate address service entities, and the service capability information of the candidate address service entities is information determined by the UDM based on the terminal's address requirement information and the service capability information of the first address service entity, which is pre-stored in the UDM's storage space. In other words, the candidate address service entities in the address service entity subscription data feedback message are address service entities determined by the UDM that can meet the terminal's address requirement information.

[0167] In some specific implementations, the service capability information of the first address service entity is information obtained by the UDM based on the address service entity subscription request sent by the terminal; wherein, the address service entity subscription request includes the service capability information of the address service entity that has subscribed with the terminal.

[0168] In some other embodiments, when the off-site storage space is a storage space located within the NRF, the acquisition module 1201 includes a second sending unit and a second receiving unit. The second sending unit is configured to send an address service entity discovery request to the NRF, and the address service entity discovery request includes the terminal's address requirement information. The second receiving unit is configured to receive an address service entity discovery feedback message returned by the NRF, the address service entity discovery feedback message including service capability information of candidate address service entities. This service capability information of the candidate address service entities is determined by the NRF based on the terminal's address requirement information and the service capability information of the second address service entity, and the service capability information of the second address service entity is pre-stored in the NRF's storage space. In other words, the candidate address service entities in the address service entity discovery feedback message are address service entities determined by the NRF that can satisfy the terminal's address requirement information.

[0169] In some specific implementations, the service capability information of the second address service entity is information obtained by the NRF based on the address service entity registration request and / or address service entity registration update request sent by the address service entity; wherein, the address service entity registration request and / or address service entity registration update request includes the service capability information of the address service entity to be registered and / or to be registered and updated.

[0170] In some other embodiments, when the preset storage space is the local storage space of the current functional entity, the acquisition module 1201 includes a selection unit and an acquisition unit based on the terminal's address requirement information. The selection unit is configured to determine candidate address service entities based on the terminal's address requirement information and the service capability information of a third address service entity, wherein the service capability information of the third address service entity is pre-stored in the storage space of the current functional entity; the acquisition unit is configured to acquire the service capability information of the candidate address service entities.

[0171] The selection unit determines the candidate address service entity based on the terminal's address requirement information and the service capability information of the third address service entity, including: determining the candidate address service entity based on the terminal's access location information and the service area information of the third address service entity; or, determining the candidate address service entity based on the terminal's access network information and the service network information of the third address service entity; or, determining the candidate address service entity based on the terminal's access location information and access network information, as well as the service area information and service network information of the third address service entity.

[0172] The entity determination module 1202 is configured to determine the target address service entity based on the service capability information of the candidate address service entities.

[0173] The number of candidate address service entities can be one or more. When there are multiple candidate address service entities, the current functional entity must select one of them as the target address service entity.

[0174] In some embodiments, the entity determination module 1202 includes a level determination unit and a target entity determination unit. The level determination unit is configured to determine the service capability level of a candidate address service entity based on the service capability information of the candidate address service entity; the target entity determination unit is configured to determine the target address service entity based on the service capability level of the candidate address service entity. The service capability level of the candidate address service entity is used to characterize the service capability level of the candidate address service entity.

[0175] In some other embodiments, the service capability information of the candidate address service entity also includes the service slice information of the candidate address service entity. The entity determination module 1202 determines the target address service entity based on the service capability information of the candidate address service entity, including: determining the target address service entity based on the service slice information of the candidate address service entity; wherein, the target address service entity is a candidate address service entity that matches the access slice of the terminal.

[0176] It should be noted that the entity determination module 1202 can also jointly determine the target address service entity based on the service capability level and service slice information of the candidate address service entities. For example, when there are multiple candidate address service entities that match the terminal's access slice, the target address service entity can be further selected from them based on the service capability level of the matched candidate address service entities.

[0177] In this embodiment, the acquisition module obtains service capability information of candidate address service entities from a preset storage space based on the terminal's address requirement information. The entity determination module then determines the target address service entity based on this service capability information. The preset storage space includes local storage space of the current functional entity or off-site storage space of a functional entity other than the current functional entity. By using the service capability information of address service entities stored in the current functional entity or other functional entities, candidate address service entities matching the terminal's address requirement information are determined. The target address service entity is then further selected from the matched candidate address service entities, thereby obtaining a target address service entity that better meets the user's needs. When providing location services to the terminal based on the target address service entity, this effectively improves the user's location service experience.

[0178] Figure 13 This diagram illustrates the structural composition of an address service entity selection device according to another embodiment of this application. This address service entity selection device can be configured in a functional entity that requires selection of an address service entity or needs to determine whether to reselect an address service entity. Figure 13 As shown, the address service entity selection device 1300 includes the following modules:

[0179] The policy determination module 1301 is configured to determine the address service policy of the current functional entity.

[0180] The address service strategy is the strategy used by the current functional entity when selecting an address service entity.

[0181] In some embodiments, the address service policy includes any one of a subscribed address service policy, a remote query address service policy, and a locally configured address service policy. The address service policy of the current functional entity can be determined by the policy determination module 1301.

[0182] It should be noted that the above-mentioned address service strategies are merely illustrative examples, and other address service strategies not mentioned are also within the scope of protection of this application, which does not limit them.

[0183] The storage space determination module 1302 is configured to determine the preset storage space based on the address service policy of the current functional entity.

[0184] In some embodiments, the storage space determination module 1302 determines a preset storage space based on the address service policy of the current functional entity, including: if the address service policy of the current functional entity is a subscribed address service policy, determining the preset storage space as an off-site storage space set in the UDM; if the address service policy of the current functional entity is an off-site query address service policy, determining the preset storage space as an off-site storage space set in the NRF; and if the address service policy of the current functional entity is a local configuration address service policy, determining the preset storage space as a local storage space set in the current functional entity.

[0185] It should be noted that the current functional entity may not have an address service policy set; in this case, the address service policy is in its default state. In this scenario, the current functional entity can prioritize selecting the address service entity based on the terminal's subscription information.

[0186] In some embodiments, when the address service policy of the current functional entity is in the default state, the current functional entity sends an address service entity subscription data acquisition request to the UDM; wherein, the address service entity subscription data acquisition request includes the terminal's address requirement information; and receives an address service entity subscription data feedback message returned by the UDM; wherein, the address service entity subscription data feedback message includes the service capability information of the candidate address service entity, and the candidate address service entity is information determined by the UDM based on the terminal's address requirement information and the service capability information of the first address service entity, and the service capability information of the first address service entity is pre-stored in the UDM's storage space.

[0187] The acquisition module 1303 is configured to acquire service capability information of alternative address service entities from a preset storage space based on the address requirement information of the terminal UE.

[0188] The entity determination module 1304 is configured to determine the target address service entity based on the service capability information of the candidate address service entities.

[0189] It should be noted that the acquisition module 1303 and entity determination module 1304 in this embodiment are the same as the acquisition module 1201 and entity determination module 1202 in the previous embodiment, and will not be described again here.

[0190] In this embodiment, the policy determination module first determines the address service policy of the current functional entity, then the storage space determination module determines a preset storage space that matches the address service policy, the acquisition module obtains the service capability information of candidate address service entities from the matched preset storage space, and the entity determination module determines the target address service entity based on the service capability information of the candidate address service entities. By pre-setting an address service policy for the current functional entity according to the user's location service needs or actual application scenarios, and by obtaining the service capability information of candidate address service entities from the corresponding preset storage space based on the address service policy, and selecting the target address service entity based on the obtained information, the system can flexibly meet user needs or application scenario requirements, thereby effectively improving the user's location service experience.

[0191] Figure 14 This diagram illustrates the structural composition of an address service entity selection device according to another embodiment of the present application. This address service entity selection device can be configured within a functional entity that includes a preset storage space. For example... Figure 14 As shown, the address service entity selection device 1400 includes the following modules:

[0192] The sending module 1401 is configured to send the service capability information of the candidate address service entities in the preset storage space to the target functional entity, so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities.

[0193] Among them, the service capability information of the alternative address service entity is obtained from the preset storage space based on the address requirement information of the terminal.

[0194] The terminal's address requirement information includes the terminal's access location information and / or the terminal's access network information. The terminal's access location information can represent the terminal's current location. In some embodiments, the terminal's access location information includes any one or more of the following: the TA (Transmission Area Code) the terminal is accessing, the access cell, and the access base station. For example, the terminal's access location information includes the TA the terminal is currently accessing, or the TA the terminal last accessed, which is perceptible to the current functional entity. The terminal's access network information includes information about the networks the terminal accesses. In some embodiments, CAG (Confirmation Agent Query) identifiers can be used to represent the terminal's access network information. For example, the terminal's access network information includes a list or subset of CAG identifiers supported by the cell the terminal is currently accessing, or a list or subset of CAG identifiers that the terminal is allowed to access.

[0195] Address service entities include LMFs and / or GMLCs. Candidate address service entities are one or more address service entities selected from the address service entities based on the terminal's address requirement information. The service capability information of a candidate address service entity includes its service area information and / or its service network information. The service area information indicates the area where the candidate address service entity can provide services. In some embodiments, the service area information includes one or a set of TAs, indicating that the candidate address service entity can provide location services within the aforementioned TAs. The service network information indicates the network information that the candidate address service entity can provide services within. In some embodiments, the service network information includes one or a set of CAG identifiers, indicating that the candidate address service entity can provide location services within the network corresponding to the aforementioned CAG identifier.

[0196] In some embodiments, the current functional entity includes a UDM or an NRF. Accordingly, the preset storage space includes the storage space set in the UDM or the storage space set in the NRF.

[0197] When the current functional entity is UDM, the sending module 1401 includes a third sending unit. The third sending unit is configured to respond to the address service entity subscription data acquisition request sent by the target functional entity, and return an address service entity subscription data feedback message to the target functional entity. This allows the target functional entity to obtain the service capability information of the candidate address service entities based on the address service entity subscription data feedback message, and to determine the target address service entity based on the service capability information of the candidate address service entities. The address service entity subscription data acquisition request includes the terminal's address requirement information, and the address service entity subscription data feedback message includes the service capability information of the candidate address service entities.

[0198] When the current functional entity is NRF, the sending module 1401 includes a fourth sending unit. The fourth sending unit is configured to respond to the address service entity discovery request sent by the target functional entity, and return an address service entity discovery feedback message to the target functional entity, so that the target functional entity can obtain the service capability information of the candidate address service entities based on the address service entity discovery feedback message, and determine the target address service entity based on the service capability information of the candidate address service entities; wherein, the address service entity discovery request includes the terminal's address requirement information, and the address service entity discovery feedback message includes the service capability information of the candidate address service entities.

[0199] In this embodiment, the sending module sends the service capability information of candidate address service entities in the preset storage space to the target functional entity, so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities. This allows functional entities with location service needs to determine candidate address service entities that match the terminal's address needs based on the service capability information of the address service entities in the preset storage space, and further select the target address service entity from the matched candidate address service entities, thereby obtaining a target address service entity that better meets the user's needs. When providing location services to the terminal based on the target address service entity, this can effectively improve the user's location service experience.

[0200] Figure 15 This diagram illustrates the structural composition of an address service entity selection device according to another embodiment of this application. This address service entity selection device can be configured within a functional entity that includes a preset storage space. For example... Figure 15 As shown, the address service entity selection device 1500 includes the following modules:

[0201] The information acquisition module 1501 is configured to acquire service capability information of alternative address service entities from a preset storage space based on the address requirement information of the terminal UE.

[0202] In some embodiments, when the current functional entity is a UDM, the information acquisition module 1501 comprises a first information acquisition unit, a second information acquisition unit, and a third information acquisition unit. The first information acquisition unit is configured to determine a candidate address service entity based on the terminal's access location information and the service area information of the first address service entity; the second information acquisition unit is configured to determine a candidate address service entity based on the terminal's access network information and the service network information of the first address service entity; and the third information acquisition unit is configured to determine a candidate address service entity based on the terminal's access location information, access network information, and the service area and service network information of the first address service entity. The service capability information of the first address service entity is stored in the UDM's storage space.

[0203] In some specific implementations, the UDM further includes a first receiving module, a first sending module, and a first storage module. The first receiving module is configured to receive an address service entity subscription request sent by the terminal; the address service entity subscription request includes service capability information of the address service entity that has subscribed with the terminal; the first sending module is configured to return an address service entity subscription feedback message to the terminal. Furthermore, based on the address service entity subscription request, the UDM obtains the service capability information of the first address service entity and stores the service capability information of the first address service entity in a preset storage space through the first storage module; the first address service entity is the address service entity that has subscribed with the terminal.

[0204] In some other embodiments, when the current functional entity is an NRF, the information acquisition module 1501 includes a fourth information acquisition unit, a fifth information acquisition unit, and a sixth information acquisition unit. The fourth information acquisition unit is configured to determine a candidate address service entity based on the terminal's access location information and the service area information of the second address service entity; the fifth information acquisition unit is configured to determine a candidate address service entity based on the terminal's access network information and the second address service entity's service network information; and the sixth information acquisition unit is configured to determine a candidate address service entity based on the terminal's access location information and access network information, as well as the second address service entity's service area information and service network information. The service capability information of the second address service entity is stored in the NRF's storage space.

[0205] In some specific implementations, the NRF also includes a second receiving module, a second sending module, and a second storage module. The second receiving module is configured to receive address service entity registration requests and / or address service entity registration update requests sent by address service entities; wherein the address service entity registration requests and / or address service entity registration update requests include service capability information of the address service entity to be registered and / or to be registered and updated; the second sending module is configured to return address service entity registration response messages and / or address service entity registration update response messages to the address service entities. Furthermore, based on the address service entity registration requests and / or address service entity registration update requests, the NRF obtains the service capability information of the second address service entity and stores the service capability information of the second address service entity in a preset storage space through the second storage module; wherein the second address service entity is the address service entity to be registered and / or to be registered and updated.

[0206] The sending module 1502 is configured to send the service capability information of the candidate address service entities in the preset storage space to the target functional entity, so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities.

[0207] It should be noted that the sending module 1502 in this embodiment is the same as the sending module 1401 in the previous embodiment, and will not be described again here.

[0208] Figure 16 This illustration shows a scenario diagram of selecting an address service entity according to an embodiment of this application. For example... Figure 16 As shown, in this scenario, different address management function entities and gateway mobile location center entities are deployed for different regions.

[0209] Specifically, the first address management function entity 1611 and the first gateway mobile location center entity 1612 are deployed to provide location services for the first service area, and the second address management function entity 1621 and the second gateway mobile location center entity 1622 are deployed to provide location services for the second service area.

[0210] When the access location of the first terminal 1613 is located in the first service area, the access location of the first terminal 1613 matches the first service area. According to the address service entity selection method provided in the embodiments of this application, the first terminal 1613 can use the location services of the first address management function entity 1611 and / or the first gateway mobile location center entity 1612 corresponding to the first service area.

[0211] Similarly, when the access location of the second terminal 1623 is located in the second service area, the access location of the second terminal 1623 matches the second service area. According to the address service entity selection method provided in the embodiments of this application, the second terminal 1623 can use the location service of the second address management function entity 1621 and / or the second gateway mobile location center entity 1622 corresponding to the second service area.

[0212] Figure 17 This illustration shows another scenario diagram of an address selection service entity in an embodiment of this application. For example... Figure 17 As shown, in this scenario, different address management function entities and gateway mobile location center entities are deployed for different networks.

[0213] Specifically, the first address management function entity 1711 and the first gateway mobile location center entity 1712 are independently deployed to provide location services for the first network, and the second address management function entity 1721 and the second gateway mobile location center entity 1722 are independently deployed to provide location services for the second network.

[0214] When the first terminal 1713 enters the signal coverage area of ​​the first network and accesses the first network, the access network of the first terminal 1713 is consistent with the first network. According to the address service entity selection method provided in the embodiments of this application, the first terminal 1713 can use the location services of the first address management function entity 1711 and / or the first gateway mobile location center entity 1712 corresponding to the first network.

[0215] Similarly, when the second terminal 1723 enters the signal coverage area of ​​the second network and accesses the second network, the access network of the second terminal 1723 is consistent with the second network. According to the address service entity selection method provided in the embodiments of this application, the second terminal 1723 can use the location services of the second address management function entity 1721 and / or the second gateway mobile location center entity 1722 corresponding to the second network.

[0216] Figure 18 This illustration shows another scenario diagram of an address selection service entity according to an embodiment of this application. For example... Figure 18 As shown, in this scenario, different address management function entities and gateway mobile location center entities are deployed for different regions and networks.

[0217] Specifically, the first address management function entity 1811 and the first gateway mobile location center entity 1812 are independently deployed to provide location services for the first network, the second address management function entity 1821 and the second gateway mobile location center entity 1822 are independently deployed to provide location services for the second network, and the third address management function entity 1831 and the third gateway mobile location center entity 1832 are centrally deployed to provide location services for terminals that can access any network in all areas.

[0218] Based on this, when the first terminal 1813 enters the signal coverage area of ​​the first network and accesses the first network, the access location of the first terminal 1813 matches the service area of ​​the first network, and the access network is also consistent with the first network. At the same time, the access location and access network of the first terminal 1813 also match the deployment of the third address management function entity 1831 and the third gateway mobile location center entity 1832. According to the address service entity selection method provided in the embodiments of this application, the first terminal 1813 can use the location services of the first address management function entity 1811 and / or the first gateway mobile location center entity 1812 corresponding to the first network, or it can use the location services of the third address management function entity 1831 and / or the third gateway mobile location center entity 1832.

[0219] Similarly, when the second terminal 1823 enters the signal coverage area of ​​the second network and accesses the second network, the access location of the second terminal 1823 matches the service area of ​​the second network, and the access network is also consistent with the second network. At the same time, the access location and access network of the second terminal 1823 also match the deployment of the third address management function entity 1831 and the third gateway mobile location center entity 1832. According to the address service entity selection method provided in the embodiments of this application, the second terminal 1823 can use the location services of the second address management function entity 1811 and / or the second gateway mobile location center entity 1812 corresponding to the second network, or it can use the location services of the third address management function entity 1831 and / or the third gateway mobile location center entity 1832.

[0220] It should be noted that in this embodiment, an address management function entity and a gateway mobile location center entity are deployed for the first network / second network. This is only an illustrative example of the deployment of address service entities in the network and does not imply a limitation on the number of address service entities in the network.

[0221] Figure 19 A structural diagram of an exemplary hardware architecture of a computing device capable of implementing the address service entity selection method and apparatus according to embodiments of the present invention is shown.

[0222] like Figure 19 As shown, the computing device 1900 includes an input device 1901, an input interface 1902, a central processing unit 1903, a memory 1904, an output interface 1905, and an output device 1906. The input interface 1902, central processing unit 1903, memory 1904, and output interface 1905 are interconnected via a bus 1907. The input device 1901 and output device 1906 are connected to the bus 1907 via the input interface 1902 and output interface 1905, respectively, and are thus connected to other components of the computing device 1900.

[0223] Specifically, input device 1901 receives input information from the outside and transmits the input information to central processing unit 1903 through input interface 1902; central processing unit 1903 processes the input information based on computer-executable instructions stored in memory 1904 to generate output information, temporarily or permanently stores the output information in memory 1904, and then transmits the output information to output device 1906 through output interface 1905; output device 1906 outputs the output information to the outside of computing device 1900 for user use.

[0224] In one embodiment, Figure 19 The computing device shown can be implemented as an electronic device, which may include: a memory configured to store a program; and a processor configured to run the program stored in the memory to perform the address service entity selection method described in the above embodiments.

[0225] In one embodiment, Figure 19 The computing device shown can be implemented as an address service entity selection system, which may include: a memory configured to store a program; and a processor configured to run the program stored in the memory to perform the address service entity selection method described in the above embodiments.

[0226] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application. Generally, various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0227] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0228] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (FGPAs), and processors based on multi-core processor architectures.

[0229] A detailed description of exemplary embodiments of this application has been provided above through exemplary and non-limiting examples. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, without departing from the scope of the invention. Therefore, the proper scope of the invention will be determined by the claims.

Claims

1. A method of address service entity selection, characterized by, The method includes: Based on the address requirement information of the terminal UE, the service capability information of the alternative address service entity is obtained from the preset storage space; The target address service entity is determined based on the service capability information of the candidate address service entities. The address service entity includes the location management function entity LMF and / or the gateway mobile location center entity GMLC; the service capability information of the alternative address service entity includes the service area information of the alternative address service entity and / or the service network information of the alternative address service entity; the address requirement information of the UE includes the access location information of the UE and / or the access network information of the UE. The preset storage space includes off-site storage space set in functional entities other than the current functional entity, and the off-site storage space includes storage space set in the unified data management functional entity UDM. The step of obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of the terminal UE includes: Send an address service entity subscription data acquisition request to the UDM; wherein, the address service entity subscription data acquisition request includes the address requirement information of the UE; Receive the address service entity subscription data feedback message returned by the UDM; wherein the address service entity subscription data feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is the information determined by the UDM based on the address requirement information of the UE and the service capability information of the first address service entity, and the service capability information of the first address service entity is pre-stored in the storage space of the UDM. Alternatively, the off-site storage space may include storage space located in the Network Function Library (NRF) functional entity; The step of obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of the terminal UE includes: Send an address service entity discovery request to the NRF; wherein the address service entity discovery request includes the address requirement information of the UE; The system receives an address service entity discovery feedback message returned by the NRF; wherein the address service entity discovery feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is determined by the NRF based on the address requirement information of the UE and the service capability information of the second address service entity, and the service capability information of the second address service entity is pre-stored in the storage space of the NRF.

2. The method of claim 1, wherein, The service capability information of the first address service entity is information obtained by the UDM based on the address service entity subscription request sent by the UE; wherein, the address service entity subscription request includes the service capability information of the address service entity that has subscribed with the UE.

3. The method of claim 1, wherein, The service capability information of the second address service entity is information obtained by the NRF based on the address service entity registration request and / or address service entity registration update request sent by the address service entity; wherein, the address service entity registration request and / or address service entity registration update request includes the service capability information of the address service entity to be registered and / or to be registered and updated.

4. The method of claim 1, wherein, The preset storage space is the local storage space set in the current functional entity; The step of obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of the terminal UE includes: The alternative address service entity is determined based on the address requirement information of the UE and the service capability information of the third address service entity; wherein, the service capability information of the third address service entity is pre-stored in the storage space of the current functional entity; Obtain the service capability information of the candidate address service entity.

5. The method of claim 4, wherein, The step of determining the candidate address service entity based on the UE's address requirement information and the service capability information of the third address service entity includes: The candidate address service entity is determined based on the UE's access location information and the service area information of the third address service entity; or, The candidate address service entity is determined based on the UE's access network information and the service network information of the third address service entity; or, The alternative address service entity is determined based on the UE's access location information and access network information, as well as the service area information and service network information of the third address service entity.

6. The method of claim 1, wherein, Before obtaining the service capability information of the alternative address service entity from the preset storage space based on the address requirement information of the terminal UE, the method further includes: Determine the address service policy for the current functional entity; The preset storage space is determined based on the address service policy of the current functional entity.

7. The method of claim 6, wherein, The address service strategy includes either the contracted address service strategy or the off-site query address service strategy. The step of determining the preset storage space based on the address service policy of the current functional entity includes: When the address service policy of the current functional entity is the contracted address service policy, the preset storage space is determined to be an off-site storage space set in UDM. If the address service strategy of the current functional entity is the off-site query address service strategy, the preset storage space is determined to be an off-site storage space set in the NRF.

8. The method of claim 6, wherein, After determining the address service policy of the current functional entity, the method further includes: When the address service policy of the current functional entity is in the default state, a request to obtain the address service entity subscription data is sent to the UDM; wherein, the request to obtain the address service entity subscription data includes the address requirement information of the UE; The address service entity subscription data feedback message returned by the UDM is received; wherein the address service entity subscription data feedback message includes the service capability information of the candidate address service entity, and the candidate address service entity is the information determined by the UDM based on the address requirement information of the UE and the service capability information of the first address service entity, and the service capability information of the first address service entity is pre-stored in the storage space of the UDM.

9. The method of claim 1, wherein, The step of determining the target address service entity based on the service capability information of the candidate address service entities includes: The service capability level of the candidate address service entity is determined based on the service capability information of the candidate address service entity. The target address service entity is determined based on the service capability level of the candidate address service entities.

10. The method of claim 1, wherein, The service capability information of the alternative address service entity also includes the service slice information of the alternative address service entity; The step of determining the target address service entity based on the service capability information of the candidate address service entities includes: The target address service entity is determined based on the service slice information of the candidate address service entity; wherein the target address service entity is a candidate address service entity that matches the access slice of the UE.

11. A method of address service entity selection, c h a r a c t e r i s e d by, The method includes: The service capability information of the candidate address service entities in the preset storage space is sent to the target functional entity so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities; wherein, the service capability information of the candidate address service entities is information obtained from the preset storage space based on the address requirement information of the terminal UE; The address service entity includes a location management function entity (LMF) and / or a gateway mobile location center entity (GMLC); the service capability information of the alternative address service entity includes the service area information of the alternative address service entity and / or the service network information of the alternative address service entity; the address requirement information of the UE includes the access location information of the UE and / or the access network information of the UE. The preset storage space includes off-site storage space set in functional entities other than the current functional entity, and the off-site storage space includes storage space set in the unified data management functional entity UDM. The step of obtaining the service capability information of the alternative address service entity from the preset storage space based on the address requirement information of the UE includes: Send an address service entity subscription data acquisition request to the UDM; wherein, the address service entity subscription data acquisition request includes the address requirement information of the UE; Receive the address service entity subscription data feedback message returned by the UDM; wherein the address service entity subscription data feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is the information determined by the UDM based on the address requirement information of the UE and the service capability information of the first address service entity, and the service capability information of the first address service entity is pre-stored in the storage space of the UDM. Alternatively, the off-site storage space may include storage space located in the Network Function Library (NRF) functional entity; The step of obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of the terminal UE includes: Send an address service entity discovery request to the NRF; wherein the address service entity discovery request includes the address requirement information of the UE; The system receives an address service entity discovery feedback message returned by the NRF; wherein the address service entity discovery feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is determined by the NRF based on the address requirement information of the UE and the service capability information of the second address service entity, and the service capability information of the second address service entity is pre-stored in the storage space of the NRF.

12. The method of claim 11, wherein, The current functional entity is the Unified Data Management Functional Entity (UDM). Before obtaining the service capability information of the alternative address service entity from the preset storage space based on the address requirement information of the UE, the method further includes: Receive an address service entity subscription request sent by the UE; wherein, the address service entity subscription request includes service capability information of the address service entity that has subscribed with the UE; The UE is returned a subscription feedback message to the address service entity.

13. The method of claim 12, wherein, After receiving the address service entity subscription request sent by the UE, the method further includes: Based on the subscription request of the address service entity, the service capability information of the first address service entity is obtained; wherein, the service capability information of the first address service entity is stored in the storage space of the UDM.

14. The method of claim 13, wherein, The step of obtaining the service capability information of the candidate address service entity from the preset storage space based on the address requirement information of the UE includes: The candidate address service entity is determined based on the UE's access location information and the service area information of the first address service entity; or, The candidate address service entity is determined based on the UE's access network information and the service network information of the first address service entity; or, The candidate address service entity is determined based on the UE's access location information and access network information, as well as the service area information and service network information of the first address service entity.

15. The method of claim 14, wherein, The step of sending the service capability information of the candidate address service entities in the preset storage space to the target functional entity, so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities, includes: In response to the address service entity subscription data acquisition request sent by the target functional entity, an address service entity subscription data feedback message is returned to the target functional entity, so that the target functional entity can obtain the service capability information of the candidate address service entities based on the address service entity subscription data feedback message, and determine the target address service entity based on the service capability information of the candidate address service entities; wherein, the address service entity subscription data acquisition request includes the address requirement information of the UE, and the address service entity subscription data feedback message includes the service capability information of the candidate address service entities.

16. The method of claim 11, wherein, The current functional entity is the Network Function Library (NRF) functional entity; Before obtaining the service capability information of the alternative address service entity from the preset storage space based on the address requirement information of the UE, the method further includes: Receive an address service entity registration request and / or address service entity registration update request sent by an address service entity; wherein, the address service entity registration request and / or address service entity registration update request includes the service capability information of the address service entity to be registered and / or to be registered and updated; Return an address service entity registration response message and / or an address service entity registration update response message to the address service entity.

17. The method of claim 16, wherein, After receiving the address service entity registration request and / or address service entity registration update request sent by the address service entity, the method further includes: Based on the address service entity registration request and / or address service entity registration update request, the service capability information of the second address service entity is obtained; wherein, the service capability information of the second address service entity is stored in the storage space of the NRF.

18. The method of claim 17, wherein, The step of obtaining the service capability information of the candidate address service entity from the preset storage space based on the address requirement information of the UE includes: The candidate address service entity is determined based on the UE's access location information and the service area information of the second address service entity; or, The candidate address service entity is determined based on the UE's access network information and the service network information of the second address service entity; or, The alternative address service entity is determined based on the UE's access location information and access network information, as well as the service area information and service network information of the second address service entity.

19. The method of claim 18, wherein, The step of sending the service capability information of the candidate address service entities in the preset storage space to the target functional entity, so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities, includes: In response to the address service entity discovery request sent by the target functional entity, an address service entity discovery feedback message is returned to the target functional entity, so that the target functional entity can obtain the service capability information of the candidate address service entities based on the address service entity discovery feedback message, and determine the target address service entity based on the service capability information of the candidate address service entities; wherein, the address service entity discovery request includes the address requirement information of the UE, and the address service entity discovery feedback message includes the service capability information of the candidate address service entities.

20. An address service entity selection apparatus, characterized by The device includes: The acquisition module is configured to acquire service capability information of alternative address service entities from a preset storage space based on the address requirement information of the terminal UE. The preset storage space includes off-site storage space set in functional entities other than the current functional entity. The entity determination module is configured to determine the target address service entity based on the service capability information of the candidate address service entities; The address service entity includes the location management function entity LMF and / or the gateway mobile location center entity GMLC; the service capability information of the alternative address service entity includes the service area information of the alternative address service entity and / or the service network information of the alternative address service entity; the address requirement information of the UE includes the access location information of the UE and / or the access network information of the UE. The off-site storage space includes the storage space set up in the unified data management functional entity UDM; The step of obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of the terminal UE includes: Send an address service entity subscription data acquisition request to the UDM; wherein, the address service entity subscription data acquisition request includes the address requirement information of the UE; Receive the address service entity subscription data feedback message returned by the UDM; wherein the address service entity subscription data feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is the information determined by the UDM based on the address requirement information of the UE and the service capability information of the first address service entity, and the service capability information of the first address service entity is pre-stored in the storage space of the UDM. Alternatively, the off-site storage space may include storage space located in the Network Function Library (NRF) functional entity; The step of obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of the terminal UE includes: Send an address service entity discovery request to the NRF; wherein the address service entity discovery request includes the address requirement information of the UE; The system receives an address service entity discovery feedback message returned by the NRF; wherein the address service entity discovery feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is determined by the NRF based on the address requirement information of the UE and the service capability information of the second address service entity, and the service capability information of the second address service entity is pre-stored in the storage space of the NRF.

21. An address service entity selection apparatus, characterized by The device includes: The acquisition module is configured to retrieve service capability information of alternative address service entities from a preset storage space based on the address requirement information of the terminal UE. The sending module is configured to send the service capability information of the candidate address service entities in the preset storage space to the target functional entity, so that the target functional entity can determine the target address service entity based on the service capability information of the candidate address service entities; wherein, the service capability information of the candidate address service entities is information obtained from the preset storage space based on the address requirement information of the terminal UE; The address service entity includes a location management function entity (LMF) and / or a gateway mobile location center entity (GMLC); the service capability information of the alternative address service entity includes the service area information of the alternative address service entity and / or the service network information of the alternative address service entity; the address requirement information of the UE includes the access location information of the UE and / or the access network information of the UE. The preset storage space includes off-site storage space set in functional entities other than the current functional entity, and the off-site storage space includes storage space set in the unified data management functional entity UDM. The step of obtaining the service capability information of the alternative address service entity from the preset storage space based on the address requirement information of the UE includes: Send an address service entity subscription data acquisition request to the UDM; wherein, the address service entity subscription data acquisition request includes the address requirement information of the UE; Receive the address service entity subscription data feedback message returned by the UDM; wherein the address service entity subscription data feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is the information determined by the UDM based on the address requirement information of the UE and the service capability information of the first address service entity, and the service capability information of the first address service entity is pre-stored in the storage space of the UDM. Alternatively, the off-site storage space may include storage space located in the Network Function Library (NRF) functional entity; The step of obtaining service capability information of candidate address service entities from a preset storage space based on the address requirement information of the terminal UE includes: Send an address service entity discovery request to the NRF; wherein the address service entity discovery request includes the address requirement information of the UE; The system receives an address service entity discovery feedback message returned by the NRF; wherein the address service entity discovery feedback message includes the service capability information of the candidate address service entity, and the service capability information of the candidate address service entity is determined by the NRF based on the address requirement information of the UE and the service capability information of the second address service entity, and the service capability information of the second address service entity is pre-stored in the storage space of the NRF.

22. An electronic device, comprising: include: One or more processors; A memory having stored one or more programs that, when executed by one or more processors, cause the one or more processors to implement the address service entity selection method as described in any one of claims 1-10 or 11-19.

23. A readable storage medium characterized by, The readable storage medium stores a computer program that, when executed by a processor, implements the address service entity selection method as described in any one of claims 1-10 or 11-19.

Images