Method and apparatus for registering user information

Abstract

The present invention provides a method and device for registering user information to solve the problem of registration information being overwritten by each other when multiple NWDAFs register registration information of terminal devices in UDM (Unified Data Management). The method includes a step of a network data analysis function (NWDAF) acquiring registration information of a terminal device, and a step of the NWDAF sending a registration request to Unified Data Management (UDM), the registration request including the registration information and location information for identifying a storage path of the registration information in the UDM, and the location information including an identifier of the NWDAF.

Description

Technical Field

[0001] Cross - reference to related applications This application claims priority based on a Chinese patent application filed with the Chinese Patent Office on July 30, 2021, with an application number of 202110869866.6 and an invention title of "Method and Apparatus for Registering User Information", and incorporates all of its disclosures herein.

[0002] The present invention relates to the field of wireless communication technologies, and particularly to a method and apparatus for registering user information.

Background Art

[0003] Currently, the conventional method for registering the registration information of a terminal device has uniqueness, that is, one network element provides services to one terminal device and registers the registration information of the terminal device in a database. When the terminal device moves between network elements, the old network element transfers the registration information of the terminal device to the new network element, and the new network element re - registers or updates the registration information of the terminal device in the database.

[0004] Currently, when a Network Data Analytic Function (NWDAF) provides services to a certain terminal, the NWDAF also needs to register the registration information of the terminal device in a database. Since multiple NWDAFs can provide services to the same terminal device, when multiple NWDAFs register the registration information of the terminal device in the database, the registration information between different NWDAFs may overwrite each other.

Summary of the Invention

Problems to be Solved by the Invention

[0005] Embodiments of the present invention provide a method and an apparatus for registering user information to solve the problem that registration information is overwritten with each other because a plurality of NWDAFs register the registration information of a terminal device with a UDM (Unified Data Management).

Means for Solving the Problem

[0006] In a first aspect, embodiments of the present invention provide a method for registering user information, and the method includes: a step in which a Network Data Analytics Function (NWDAF) acquires registration information of a terminal device; a step in which the NWDAF sends a registration request to a Unified Data Management (UDM); the registration request includes the registration information and position information for specifying a storage path of the registration information in the UDM, and the identifier of the NWDAF is included in the position information.

[0007] Based on the above solution, by adding the identifier of the NWDAF to the position information sent to the UDM, the information registered by different NWDAFs can be stored in different locations within the UDM, and the overwriting of the registration information between different NWDAFs can be prevented.

[0008] In some embodiments, the position information is a Uniform Resource Identifier (URI).

[0009] In some embodiments, the position information further includes an analysis identifier of an event, the analysis identifier of the event is used to indicate a first service executed by the NWDAF for the terminal device, and the registration information is generated when the NWDAF provides the first service for the terminal device.

[0010] Based on the above solutions, since the analysis identifier of the event is added to the location information, data corresponding to different services provided by the NWDAF to the terminal device can be stored at different locations, and the overwriting of registration information belonging to the same event analysis identifier between different NWDAFs can be prevented.

[0011] In some embodiments, after the NWDAF sends a registration request to the UDM, if the NWDAF determines that the registration information has been updated, the method further includes the step of sending an update request to the UDM, the update request includes the updated registration information and the location information, and the update request is used to instruct the UDM to update the registration information in the storage path indicated by the location information to the updated registration information.

[0012] In the prior art, since the registration information of multiple NWDAFs uses the same location information, the update of the registration information by one NWDAF may affect the registration information of other NWDAFs. However, in the present invention, in order to avoid the occurrence of update errors, the registration information of a specific NWDAF can be intentionally updated according to the identifier of the NWDAF included in the location information without affecting the registration information of other NWDAFs.

[0013] In some embodiments, after the NWDAF sends a registration request to the UDM, if the NWDAF determines that it is necessary to delete the registration information, the method further includes the step of the NWDAF sending a deletion request to the UDM, the deletion request includes the location information, and the deletion request is used to instruct the UDM to delete the registration information in the storage path indicated by the location information.

[0014] In the prior art, since the registration information of multiple NWDAFs is stored in the same storage path, when the UDM deletes the registration information, the UDM may delete the registration information of multiple NWDAFs in the storage path. In the present invention, by adding the identifier of the NWDAF to the location information, the UDM can intentionally delete the registration information of the NWDAF that sent the deletion request according to the location information, without affecting the registration information of other NWDAFs and avoiding the situation of accidental deletion.

[0015] In a second aspect, embodiments of the present invention provide another method for registering user information. The method includes: a step in which the UDM receives a registration request from the NWDAF; a step in which the UDM stores the registration information in a storage path indicated by the location information, wherein the registration request includes the registration information of the terminal device and the location information for specifying the storage path of the registration information in the UDM, and the identifier of the NWDAF is included in the location information.

[0016] In some embodiments, after the UDM stores the registration information in a storage path indicated by the location information, the method includes: a step in which the UDM receives an update request from the NWDAF; a step in which the UDM updates the registration information in the storage path indicated by the location information to the updated registration information based on the update request, wherein the update request includes the updated registration information and the location information.

[0017] In some embodiments, after the UDM stores the registration information in a storage path indicated by the location information, the method includes: a step in which the UDM receives a deletion request from the NWDAF; a step in which the UDM deletes the registration information in the storage path indicated by the location information based on the deletion request, The location information is included in the deletion request.

[0018] In some embodiments, after the UDM stores the registration information in a storage path indicated by the location information, the method further includes: the UDM receiving a search request for a consumer from a network element; the UDM sending first data within a storage path indicated by the location information to the network element consumer, wherein the search request includes an identifier of the first data included in the registration information and the location information.

[0019] In a third aspect, embodiments of the present invention provide a method for registering user information. The method includes: a first NWDAF obtaining registration information of a terminal device; the first NWDA sending a registration request to a UDM, wherein the registration request includes the registration information and location information for specifying a storage path of the registration information in the UDM, the registration information includes second data, the second data is associated with a shared storage identifier, the shared storage identifier is used to indicate that the second data belongs to the first NWDAF, and the first NWDAF is any one of at least one NWDAF that provides services to the terminal device.

[0020] Based on the above solution, the shared storage identifier associated with the second data is used to indicate that the second data was sent by the first NWDAF. Therefore, the shared storage identifiers used by different NWDAFs of the present invention are different. When multiple NWDAFs store second data in the UDM, since the shared storage identifiers associated with the second data stored by different NWDAFs are different, a situation where the data overwrites each other can be avoided.

[0021] In some embodiments, the location information is a uniform resource identifier (URI).

[0022] In some embodiments, the registration information further includes third data, and the third data is not associated with the shared storage identifier and indicates that the third data is stored in a storage path indicated by the location information.

[0023] In some embodiments, after the first NWDAF sends a registration request to the UDM, the method further includes, when the first NWDAF determines that the second data has been updated, sending an update request to the UDM, where the update request includes the updated second data, the shared storage identifier associated with the second data, and the location information, and the update request is used to instruct the UDM to update the second data in the storage path indicated by the location information to the updated second data.

[0024] Based on the above solution, since the update request sent by the first NWDAF to the UDM may include the shared storage identifier associated with the second data, it can be indicated that the second data that needs to be updated is the second data stored by the first NWDAF. After receiving the update request, the UDM updates the second data previously stored by the first NWDAF and does not update the second data stored by other NWDAFs that provide services for the terminal device. Thereby, the occurrence of update errors can be avoided.

[0025] In some embodiments, after the first NWDAF sends a registration request to the UDM, the method further includes When the first NWDAF determines that it is necessary to delete the second data, the NWDAF sends a deletion request to the UDM. The deletion request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information. The deletion request is used to instruct the UDM to delete the second data within the storage path indicated by the location information.

[0026] Based on the above solution, since the shared storage identifiers used by different NWDAFs are different, when the first NWDAF sends a deletion request to the UDM, the UDM deletes the data stored by the first NWDAF according to the shared storage identifier used by the first NWDAF, thus avoiding the occurrence of incorrect deletions.

[0027] In a fourth aspect, embodiments of the present invention provide another method for registering user information. The method includes the UDM receiving a registration request from the first NWDAF, and the UDM storing the second data in the storage path indicated by the location information. The registration request includes the registration information of the terminal device and the location information for specifying the storage path of the registration information in the UDM. The registration information is obtained by the NWDAF during the flowchart of registering the terminal device to the core network. The registration information includes second data, the second data is associated with a shared storage identifier, and the shared storage identifier is used to indicate that the second data belongs to the first NWDAF. The first NWDAF is any one of at least one NWDAF that provides services to the terminal device.

[0028] In some embodiments, after the UDM stores the second data in the storage path indicated by the location information, the method further includes the UDM receiving an update request from the first NWDAF, and the updated second data in the update request The UDM includes the step of updating second data in a storage path indicated by the location information to the updated second data, and includes a shared storage identifier associated with the second data and the location information.

[0029] In some embodiments, after the UDM stores the second data in a storage path indicated by the location information, the method further includes the step of the UDM receiving a deletion request from the first NWDAF, and the step of the UDM deleting second data in a storage path indicated by the location information, wherein the deletion request includes an identifier of the second data, a shared storage identifier associated with the second data, and the location information.

[0030] In some embodiments, after the UDM stores the registration information in a storage path indicated by the location information, the method further includes the step of the UDM receiving a search request for a consumer from a network element, and the step of the UDM sending first data in a storage path indicated by the location information to the network element consumer, wherein the search request includes an identifier of the first data included in the registration information and the location information.

[0031] In a fifth aspect, an embodiment of the present invention provides a communication system, the communication system including an NWDAF configured to obtain registration information of a terminal device, wherein the NWDAF is further configured to send a registration request to a UDM, the registration request including the registration information and location information for specifying a storage path of the registration information in the UDM, and the identifier of the NWDAF is included in the location information, The UDM is configured to store the registration information in a storage path indicated by the location information.

[0032] In some embodiments, after the UDM stores the registration information in a storage path indicated by the location information, when the NWDAF further determines that the registration information has been updated, the NWDAF sends an update request to the UDM, and the update request includes the updated registration information and the location information, the UDM is further configured to update the registration information in the storage path indicated by the location information to the updated registration information.

[0033] In some embodiments, after the UDM stores the registration information in a storage path indicated by the location information, when the NWDAF further determines that the registration information needs to be deleted, the NWDAF is configured to send a deletion request to the UDM, and the deletion request includes the location information, the UDM is further configured to delete the registration information in the storage path indicated by the location information.

[0034] In a sixth aspect, an embodiment of the present invention provides another communication system, and the communication system includes an NWDAF configured to obtain registration information of a first terminal device, the first NWDAF is further configured to send a registration request to the UDM, and the registration request includes the registration information and location information for identifying a storage path of the registration information in the UDM. The registration information includes second data, the second data is associated with a shared storage identifier, the shared storage identifier is used to indicate that the second data belongs to the first NWDAF, and the first NWDAF is any one of at least one NWDAF that provides services to the terminal device, the UDM is configured to store the second data in a storage path indicated by the location information.

[0035] In some embodiments, after the UDM stores the second data in the storage path indicated by the location information, when the first NWDAF further determines that the second data is updated, the first NWDAF sends an update request to the UDM, and the update request includes the updated second data, the shared storage identifier associated with the second data, and the location information. The UDM is further configured to update the second data in the storage path indicated by the location information to the updated second data.

[0036] In some embodiments, after the UDM stores the second data in the storage path indicated by the location information, when the first NWDAF further determines that the second data needs to be deleted, the NWDAF sends a deletion request to the UDM, and the deletion request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information. The UDM is further configured to delete the second data in the storage path indicated by the location information.

[0037] In some embodiments, the system further includes a network element consumer. After the UDM stores the second data in the storage path indicated by the location information, the network element consumer is configured to receive a service request from a terminal device, and the service request is configured to indicate the service requested by the terminal device. The network element consumer is further configured to determine, based on the service request, that the second data needs to be obtained, and send a search request to the UDM. The search request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information. The UDM is further configured to send second data within the storage path indicated by the location information to the network element consumer.

[0038] In a seventh aspect, an embodiment of the present invention provides an apparatus for registering user information, the apparatus comprising: a processing unit configured to obtain registration information of a terminal device; and a communication unit configured to send a registration request to a UDM, wherein the registration request includes the registration information and location information for specifying a storage path of the registration information in the UDM, and the location information includes an identifier of the NWDAF.

[0039] In some embodiments, the location information is a uniform resource identifier (URI).

[0040] In some embodiments, the location information further includes an analysis identifier of an event, the analysis identifier of the event being used to indicate a first service executed by the NWDAF for the terminal device, and the registration information being generated when the NWDAF provides the first service for the terminal device.

[0041] In some embodiments, after sending the registration request to the UDM, the communication unit further: when it is determined that the registration information has been updated, sends an update request to the UDM, the update request including the updated registration information and the location information, and the update request being used to instruct the UDM to update the registration information within the storage path indicated by the location information to the updated registration information.

[0042] In some embodiments, after sending the registration request to the UDM, the communication unit further: When it is determined that the registration information needs to be deleted, the NWDAF sends a deletion request to the UDM. The deletion request includes the location information, and is used to instruct the UDM to delete the registration information within the storage path indicated by the location information.

[0043] In an eighth aspect, an embodiment of the present invention provides another device for registering user information, and the device includes: a communication unit configured to receive a registration request from the NWDAF; a processing unit configured to store the registration information in a storage path indicated by the location information, wherein the registration request includes registration information of a terminal device and location information for identifying a storage path of the registration information in the device, and the location information includes an identifier of the NWDAF.

[0044] In some embodiments, after the processing unit stores the registration information in the storage path indicated by the location information, the communication unit is further configured to receive an update request from the NWDAF, the update request includes updated registration information and the location information, and the processing unit is further configured to update the registration information in the storage path indicated by the location information to the updated registration information based on the update request.

[0045] In some embodiments, after the processing unit stores the registration information in the storage path indicated by the location information, the communication unit is further configured to receive a deletion request from the NWDAF, the deletion request includes the location information, and the processing unit is configured to delete the registration information in the storage path indicated by the location information based on the deletion request.

[0046] In some embodiments, after the processing unit stores the registration information in the storage path indicated by the location information, the communication unit is further configured to receive a search request from a network element consumer, the search request including an identifier of the first data and the location information, the processing unit is configured to transmit the first data within the storage path indicated by the location information to the network element consumer.

[0047] In a ninth aspect, an embodiment of the present invention provides another device for registering user information, the device including a processing unit configured to obtain registration information of a terminal device, and a communication unit configured to send a registration request to a UDM, the registration request including the registration information and location information for specifying a storage path of the registration information in the UDM, the registration information including second data, the second data being associated with a shared storage identifier, the shared storage identifier being used to indicate that the second data belongs to the first NWDAF.

[0048] In some embodiments, the location information is a uniform resource identifier (URI).

[0049] In some embodiments, the registration information further includes third data, the third data not being associated with the shared storage identifier, and indicating that the third data is stored in the storage path indicated by the location information.

[0050] In some embodiments, after the communication unit sends a registration request to the UDM, it further When it is determined that the second data has been updated, an update request is sent to the UDM, and the update request includes the updated second data, the shared storage identifier associated with the second data, and the location information. The update request is used to instruct the UDM to update the second data in the storage path indicated by the location information to the updated second data.

[0051] In some embodiments, after the communication unit sends a registration request to the UDM, further, When it is determined that the second data needs to be deleted, the NWDAF sends a deletion request to the UDM, and the deletion request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information. The deletion request is used to instruct the UDM to delete the second data in the storage path indicated by the location information.

[0052] In a tenth aspect, an apparatus for registering user information provided by an embodiment of the present invention includes a communication unit configured to receive a registration request from a first NWDAF; a processing unit configured to store the second data in a storage path indicated by the location information, wherein the registration request includes registration information of a terminal device and location information for identifying a storage path of the registration information in the apparatus. The registration information is obtained by the NWDAF in a flowchart for registering the terminal device in a core network. The registration information includes second data, the second data is associated with a shared storage identifier, and the shared storage identifier is used to indicate that the second data belongs to the first NWDAF. The first NWDAF is any one of at least one NWDAF that provides services to the terminal device.

[0053] In some embodiments, after the processing unit stores the second data in the storage path indicated by the location information, the communication unit is further configured to receive an update request from the first NWDAF, the update request including the updated second data, a shared storage identifier associated with the second data, and the location information, and the processing unit is further configured to update the second data in the storage path indicated by the location information to the updated second data.

[0054] In some embodiments, after the processing unit stores the second data in the storage path indicated by the location information, the communication unit is further configured to receive a deletion request from the first NWDAF, the deletion request including an identifier of the second data, a shared storage identifier associated with the second data, and the location information, and the processing unit is configured to delete the second data in the storage path indicated by the location information.

[0055] In an eleventh aspect, an apparatus for registering another user information provided by an embodiment of the present invention includes a memory and a processor, the memory is configured to store program instructions, and the processor is configured to call the program instructions stored in the memory and execute the method in any implementation form of the first aspect or the third aspect according to the obtained program.

[0056] In a twelfth aspect, an apparatus for registering another user information provided by an embodiment of the present invention includes a memory and a processor, the memory is configured to store program instructions, The processor is configured to call program instructions stored in the memory and execute the method in an implementation form of either the second aspect or the fourth aspect according to the obtained program.

[0057] In a thirteenth aspect, an embodiment of the present invention provides a computer-readable storage medium, in which computer instructions are stored, and when the computer instructions are executed on a computer, the computer is caused to execute the above method.

[0058] Furthermore, regarding the technical effects brought about by any implementation of the second aspect and from the fourth aspect to the thirteenth aspect, reference can be made to the technical effects brought about by different implementations of the first aspect and the third aspect. Details will not be repeated here.

Brief Description of Drawings

[0059]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 3C

Figure 4

Figure 5A

Figure 5B

Figure 5C

Figure 6

Figure 7

Embodiments for Carrying Out the Invention

[0060] To make the object, technical solution, and advantages of the present invention clearer, the present invention will be described in more detail below with reference to the accompanying drawings. Apparently, the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments of the present invention. All other embodiments obtained by those skilled in the art without creative efforts based on the embodiments of the present invention belong to the protection scope of the present invention.

[0061] The application scenarios described in the embodiments of the present invention are for more clearly explaining the technical solutions of the embodiments of the present invention and do not limit the technical solutions provided by the embodiments of the present invention. Those skilled in the art know that with the emergence of new application scenarios, the technical solutions provided by the embodiments of the present invention can also be applied to similar technical problems. In the description of the present invention, "a plurality" means two or more unless otherwise specified.

[0062] FIG. 1 shows a communication system architecture. It should be understood that the embodiments of the present invention are not limited to the system shown in FIG. 1. Further, the devices in FIG. 1 may be hardware, functionally divided software, or a combination of both. As shown in FIG. 1, the system architecture provided by the embodiments of the present invention includes a terminal device 101, a Session Management Function (SMF) 1021, an Access and Mobility Management Function (AMF) 1022, an NWDAF 1023, a Network Function consumer (NF consumer) 1024, and a UDM 103. The embodiments of the present invention do not limit the number of terminal devices, NWDAFs, SMFs, and AMFs included in the system. In FIG. 1, only one is used as an example for introduction. Further, it should be noted that the communication system may also include other network elements. For example, the communication system may include an access network device not shown in FIG. 1.

[0063] The terminal device 101, also called a terminal, Mobile Station (MS), Mobile Terminal (MT), etc., is a device that provides users with voice and / or data connectivity, such as a handheld device with a wireless connection function, an in-vehicle device, etc. At present, examples of terminals include mobile phones, tablets, notebook computers, palm rests, Mobile Internet Devices (MIDs), wearable devices, Virtual Reality (VR) devices, Augmented Reality (AR) devices, wireless terminals for industrial control, wireless terminals for self-driving, wireless terminals for remote medical surgery, wireless terminals for smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0064] SMF1021 is a functional unit based on the service architecture in the 5G communication system. The SMF is mainly responsible for session management such as session establishment, modification, and release. It is also used to implement functions such as the allocation and management of the IP address of the terminal device.

[0065] AMF1022 is a functional unit in the 5G communication system and is mainly responsible for realizing functions such as the registration of the terminal device and access to the core network.

[0066] NWDAF1023 collects information such as connection management, mobility management, session management, and access services of the user's terminal device, analyzes and evaluates different types of users using reliable analysis and prediction models, constructs user portraits, determines the user's movement trajectory and service usage habits, and predicts the user's behavior. Based on the analysis and prediction data, it optimizes user mobility management parameters, radio resource management parameters, etc.

[0067] UDM103 is an intelligent management platform for data services and data service operations, characterized by easy introduction, hierarchical management of users for the security of users and data applications, and implementation of overall security guarantees to ensure the security of data storage.

[0068] Network elements such as SMF and AMF are specific when providing services to a terminal device. That is, one SMF (or AMF) can only provide services to one terminal device. Therefore, the network element currently providing services to a specific terminal device registers the registration information with the UDM. Thus, the registration information of the terminal device stored in the UDM registered by the SMF is unique. However, since multiple NWDAFs can serve the same UE, if different NWDAFs register the registration information of the same terminal device with the UDM, the information registered by the previous NWDAF may be overwritten by the information registered by the subsequent NWDAF.

[0069] Embodiments of the present invention provide a method and an apparatus for registering user information. When the NWDAF registers user information, the identifier of the NWDAF is added to the location information indicating the storage path included in the transmitted registration request. Therefore, when different NWDAFs register the registration information of the same terminal device, the situation where the registration information is overwritten can be solved due to different storage paths in the UDM.

[0070] Next, a method for registering user information provided by an embodiment of the present invention will be introduced. Referring to FIG. 2, FIG. 2 is a flowchart of a user information registration method provided by an embodiment of the present invention. This method is executed by the NWDAF, and the NWDAF that selectively executes this flowchart may be the first NWDAF shown in FIG. 1, or the second NWDAF, but is not particularly limited in the present invention. Specifically, the flowchart of the method includes the following.

[0071] 201. The NWDAF acquires the registration information of the terminal device.

[0072] Optionally, the registration information may include at least one of a terminal device number or identifier, an NWDAF identifier, an event analysis identifier, a registration time, UE context information of the terminal device, or a service that the NWDAF can provide to the terminal device. Here, the NWDAF identifier may include an NWDAF instance number (NWDAFInstance Id) or an NWDAF set number (NWDAFSet Id). Note that it should be noted that both the NWDAF instance number and the NWDAF set number can uniquely identify the NWDAF within the communication system. Here, the NWDAF set number is the number of the NWDAF within one NWDAF set. For example, the NWDAF set number is composed of the number of the NWDAF set including the NWDAF and the number of the NWDAF within the NWDAF set. The event analysis identifier can use an event analysis number (analytics Id) used to indicate the first service executed by the NWDAF for the terminal device. Note that the registration information is generated when the NWDAF provides the first service to the terminal device, and the first service is any one of the services that the NWDAF can provide to the terminal device.

[0073] As a selective means, the NWDAF can obtain the registration information of the terminal device. Specifically, the NWDAF can receive the context information of the terminal device from a network data analytic function service consumer (NWDAF service consumer) or other network elements (such as the AMF or SMF). Further, the NWDAF can generate the registration information of the terminal device based on the received context information of the terminal device. For example, after receiving the context information of the terminal device, the NWDAF generates information such as the instance number of the NWDAF, the analysis identifier of the event, or the registration time, and uses the generated information and the received user context information as the registration information of the terminal device. Of course, the above method is only an example, and the NWDAF can also obtain the registration information of the terminal device by other methods, which is not particularly limited in the present invention.

[0074] 202. The NWDA sends a registration request to the UDM, and the registration request includes registration information and location information.

[0075] Specifically, the location information is used to identify the storage path of the registration information in the UDM. The location information includes the identifier of the NWDAF and can include, for example, the instance number of the NWDAF or the set number of the NWDAF.

[0076] Optionally, the location information may be a Resource Location Identifier (Uniform Resource Identifier, URI). As an example, the instance number of the NWDAF is adopted as the identifier of the NWDAF. For example, the location information is / {ueId} / registrations / nwdaf-registration / nwdafInstanceId. Here, ueId is used to identify which terminal device's registration information it is. Registrations is used to indicate that the registration request is a registration request. nwdaf-registration is used to indicate that the registration request is a registration request from the NWDAF, and nwdafInstanceId is the instance number of the NWDAF.

[0077] 203. The UDM receives the registration request and stores the registration information in the storage path indicated by the location information.

[0078] Specifically, after receiving the registration request, the UDM can determine the storage path based on the location information in the registration request and store the registration information included in the registration request in the storage path.

[0079] In a possible embodiment, after storing the registration information in the storage path indicated by the location information, the UDM can also return indication information indicating the success of the registration to the NWDAF. For example, the indication information may be "200 OK", "201 Created", or "204 Content". As an example, the UDM can send the indication information indicating the success of the registration to the NWDAF and at the same time carry the identifier of the success of the registration or the registration information. Therefore, the NWDAF can know which registration information has been successfully registered.

[0080] In another possible embodiment, if the UDM cannot store the above registration information for some reason, for example, the UDM determines that the NWDAF that sends a registration request based on the permission information provided in advance by the terminal device cannot provide services to the terminal device. In this case, the UDM may return instruction information indicating a registration failure. For example, the instruction information may include the status code of the Hyper Text Transfer Protocol (HTTP) indicating the current transmission state. For example, "403 Forbidden" and "404 Not Found" indicate that the registration information has not been received or processed by the UDM. Optionally, while the UDM sends instruction information indicating a registration failure, it can also carry Problem Details.

[0081] In some embodiments, the location information sent to the NWDAF by the UDM can also include an analysis identifier of an event used to indicate a first service executed by the NWDAF for the terminal device. The first service is one of the services that the NWDAF can provide to the terminal device. As an example, the analysis identifier of the event can be represented by an analytics Id, and the location information can be represented as / {ueId} / registrations / nwdaf-registration / nwdafInstanceId / {analyticsId}. Here, the content represented by ueId, registrations, nwdaf-registration, and nwdafInstanceId can refer to the relevant descriptions in step 202 of FIG. 2 above. Here, the description thereof is omitted. The analytics Id is used to indicate the event analysis number of the service executed by the NWDAF for the terminal device.

[0082] In the following, a first method for registering user information provided in the embodiments of the present invention will be introduced in combination with specific scenarios.

[0083] Scenario 1: Update scenario.

[0084] The NWDAF determines that the registration information of the terminal device has been updated. For example, when the service capabilities of the NWDAF change, such as the addition of a specific service, or when the terminal device no longer requires the NWDAF to provide a specific service, the registration information of the terminal device is updated.

[0085] In some embodiments, after determining that the registration information has been updated, the NWDAF can send an update request to the UDM. The update request includes the updated registration information and location information. Optionally, the location information can be found in the above example and will not be repeated here. After receiving the update request, the UDM can delete the registration information within the storage path indicated by the location information included in the update request and store the updated registration information included in the update request in the storage path indicated by the location information.

[0086] In some other embodiments, the NWDAF can also update only one or some of the data within the registration information. Hereinafter, the change of data A in the registration information will be taken as an example for introduction. Optionally, after determining that data A has been updated, the NWDAF can also send an update request to the UDM. The update request may include the updated data A, the identifier of data A, and location information. After receiving the update request, the UDM can determine that it is necessary to update the data A stored in the storage path indicated by the location information based on the identifier of data A. Further, the UDM may delete the data A on the storage path indicated by the location information and store the updated data A in the storage path indicated by the location information.

[0087] In one possible case, when the update is successful, that is, when the UDM successfully updates the data (which may be the registration information or the data included in the registration information) included in the update request to the storage path indicated by the location information. Thereafter, the UDM may return indication information to the NWDAF to indicate that the update was successful. For example, the indication information may be "204 No Content" or the like. Optionally, the UDM may send the data that was successfully updated, the identifier that was successfully updated, or the data that was successfully updated and the identifier that was successfully updated to the NWDAF together with the indication information.

[0088] Also, when the update fails, such as when the storage path indicated by the location information received by the UDM does not exist or when the data that needs to be updated does not exist, it is also possible that the UDM cannot update the data. The UDM can return indication information indicating an update failure, such as "404 Not Found", to the NWDAF. Optionally, the UDM can also return error information to the NWDAF together with the indication information. Here, the error information is used to indicate the reason for the update failure.

[0089] Optionally, a specific update flow can refer to the flow shown in Figure 3A. The flow shown in Figure 3A is described by an example where the entire registration information is updated and the update is successful, and specifically includes the following steps.

[0090] 301A. The NWDAF determines that the registration information has been updated and obtains the updated registration information.

[0091] 302A. The NWDAF sends an update request including the updated registration information and location information to the UDM.

[0092] Optionally, the location information can refer to the description in the above embodiments, but will not be repeated here.

[0093] 303A. The UDM receives the update request and updates the registration information.

[0094] Specifically, the registration information in the storage path indicated by the location information may be replaced with the updated registration information.

[0095] 304A. The UDM returns indication information indicating that the update was successful to the NWDAF.

[0096] Scenario 2: Deletion scenario.

[0097] The NWDAF determines that it is necessary to delete the registration information of the terminal device. For example, when the service provided by the NWDAF to the terminal device ends or the terminal device goes out of the service range of the NWDAF, the NWDAF determines that it is necessary to delete the registration information of the terminal device. Optionally, after the NWDAF determines that it is necessary to delete the registration information, the NWDAF can send a deletion request including location information to the UDM. Optionally, the location information can refer to the description in the foregoing embodiments, but will not be repeated here. In a conceivable case, after receiving the deletion request, the UDM may delete the registration information on the storage path indicated by the location information included in the deletion request and return indication information indicating that the deletion was successful to the NWDAF. Optionally, when the UDM sends indication information for indicating the success of the deletion, the indication information can also carry an identifier of the success of the deletion. As another possible case, if the UDM fails to delete the registration information in the storage path indicated by the location information, the UDM can return indication information for indicating the failure of the deletion to the NWDAF, and at the same time, the indication information can also carry error information indicating the reason for the deletion failure at the time of the NWDAF.

[0098] As an example, for a specific deletion flow, reference can also be made to the flowchart shown in FIG. 10. Note that the flowchart shown in FIG. 3B is introduced as an example where the deletion was successful, and specifically includes the following.

[0099] 301B. The NWDAF determines that it is necessary to delete the registration information.

[0100] 302B. The NWDAF sends a deletion request containing location information to the UDM.

[0101] 303B. The UDM receives the deletion request and deletes the registration information on the storage path indicated by the location information.

[0102] 304B. The UDM returns indication information indicating that the deletion was successful to the NWDAF.

[0103] Scenario 3: Search scenario.

[0104] The Network Function consumer (NF consumer) can first determine whether it is necessary to obtain registration information or one or more data included in the registration information. For example, when a terminal device sends a service request to a Network Function consumer (which may be, for example, an AMF, or of course, other network functions within the communication system), the Network Function consumer can send a search request to the UDM according to the service request from the terminal device. The search request is used to request the NWDAF that provides services to the terminal device and the registration information registered by the NWDAF in the UDM or the data included in the registration information. As an example, the case where the Network Function consumer needs to obtain the first data, which is any data included in the registration information, will be described. After determining that it is necessary to obtain the first data, the Network Function consumer can send a search request including the identifier and location information of the first data to the UDM. In some cases, the UDM can obtain the first data from the storage path indicated by the location information based on the search request. Furthermore, the UDM can return to the Network Function consumer instruction information indicating that the search was successful, such as "200 OK", and the instruction information carries the obtained first data. In another case, if the UDM does not have the first data in the storage path indicated by the location information, the UDM can return to the NF consumer instruction information indicating a search failure, such as "404 Not Found", and the instruction information includes error information.

[0105] As an example of a specific search flow, the flowchart shown in Figure 3C can be cited. Note that the flowchart shown in Figure 3C is introduced as an example of a successful search, and specifically, it is as follows.

[0106] 301C, the NF consumer determines that it is necessary to obtain the first data included in the registration information.

[0107] 302C. The NF consumer sends a search request containing the identifier and location information of the first data to the UDM.

[0108] 303C. The UDM receives the search request and obtains the first data from the storage path indicated by the location information.

[0109] 304C. The UDM returns the indication information indicating successful search and the first data to the NF consumer.

[0110] Since multiple NWDAFs can provide services to the same terminal device simultaneously, and multiple NWDAFs need to register the registration information of the terminal device with the UDM, the registration information may be overwritten by each other.

[0111] Referring to FIG. 4, FIG. 4 is a flowchart of another method for registering user information provided according to an embodiment of the present invention. This method is executed by the first NWDAF, and the first NWDAF is any one of a plurality of NWDAFs that provide services to the terminal device. Specifically, the flowchart of the method includes the following.

[0112] 401. The first NWDAF obtains the registration information of the terminal device.

[0113] Optionally, the registration information of the terminal device can refer to the relevant description in step 201 of FIG. 2, which will not be repeated here.

[0114] 402. The first NWDA sends a registration request to the UDM, and the registration request includes the registration information and location information.

[0115] Here, the registration information includes the second data, the second data is associated with the shared storage identifier, and the shared storage identifier indicates that the second data belongs to the first NWDAF.

[0116] In some embodiments, the location information is a uniform resource identifier (URI). Optionally, the location information can be expressed as / {ueId} / registrations / nwdaf-registration, and the content represented by each item can be referred to the description of step 202 in FIG. 2, which will be omitted here.

[0117] Optionally, the location information can also include an event analysis identifier used to indicate a first service executed by a first NWDAF for a terminal device. As an example, the event analysis identifier adopts an event analysis number, and the location information can be expressed as / {ueId} / registrations / nwdaf-registration / {analyticsId}. The content represented by each item can refer to the above. Since the above embodiments are the same, they will not be repeated here.

[0118] 403. The UDM stores the second data in the storage path indicated by the location information.

[0119] In some cases, the UDM can store all the received registration information in the storage path indicated by the location information, associating the second data included in the registration information with the shared data identifier. In some embodiments, the registration information can also include other data not associated with the shared data identifier. As another possible case, the UDM can also establish a sub-path under the storage path indicated by the location information, and the sub-path can be used as a path shared by at least one NWDAF that provides services to the terminal device. Hereinafter, for convenience of description, the sub-path is referred to as a shared path. When the UDM receives the second data including the shared data identifier, the UDM can store the second data in the shared path. In the following description, an example of the UDM storing the second data in the shared path will be introduced.

[0120] Optionally, the UDM can also store other data not associated with the shared storage identifier, except for the second data of the registration information, in the storage path indicated by the location information. Taking the third data as an example, if the third data included in the registration information is not associated with the shared storage identifier, the UDM stores the third data in the storage path indicated by the location information.

[0121] In a possible case, if the UDM successfully stores the data, the UDM can return instruction information for indicating the success of the registration to the first NWDAF. For the relevant instruction information, reference can be made to the description of the foregoing embodiments, which will not be repeated here. In another possible case, if the UDM fails to normally store the data, the UDM can return instruction information for indicating the failure of the registration to the first NWDAF, and the instruction information simultaneously carries error information indicating the reason for the registration failure.

[0122] Based on the above solutions, it can be seen that the shared storage identifiers used by different NWDAFs in the present invention are different. Therefore, even if different NWDAFs store the same data in the shared path, since it is shared, the data will not overwrite each other. The storage identifiers associated with the data stored by different NWDAFs are different.

[0123] Next, a second method for registering user information provided by the present invention will be introduced in combination with specific scenarios.

[0124] Scenario 4: Update scenario.

[0125] In some embodiments, after the first NWDAF determines that the second data included in the registration information of the terminal device has been updated, the first NWDAF sends an update request to the UDM. The update request includes the updated second data, a shared storage identifier associated with the second data, and location information. Optionally, the location information can refer to the example in step 402 of FIG. 4. This will not be repeated here. After receiving the update request, the UDM can determine that it is necessary to store the updated second data included in the update request in the shared path included in the storage path indicated by the location information based on the shared storage identifier associated with the second data included in the update request. The UDM can delete the second data in the shared path, store the updated second data in the shared path, and complete the update of the second data. In a conceivable case, if the update is successful, that is, if the UDM successfully replaces the original second data in the shared path with the updated second data, the UDM may return instruction information to indicate that the update is successful to the first NWDAF. In another possible case, if the update fails, the UDM can return instruction information to indicate the failure of the update to the first NWDAF. For specific instruction information and the reason for the update failure, reference can be made to the description of Scenario 1, so this will not be repeated here.

[0126] As an example, the specific update process can refer to the flow shown in FIG. 5A. It is assumed that the flow shown in FIG. 5A executes the following processing. The content of FIG. 5A is introduced by taking the case where the update of the second data is successful as an example, and specifically includes the following content.

[0127] 501A. The first NWDAF determines that the second data included in the registration information has been updated and obtains the updated second data.

[0128] 502A. The first NWDAF sends an update request to the UDM, and the update request includes the updated second data, a shared storage identifier associated with the second data, and location information.

[0129] 503A. The UDM receives an update request and updates the second data.

[0130] Specifically, the UDM needs to determine that it is necessary to update the second data within the shared path in the storage path indicated by the location information based on the location information and the shared storage identifier associated with the second data. Also, the UDM may delete the second data stored in the shared path and store the updated second data included in the update request in the shared path.

[0131] 504A. The UDM returns indication information indicating that the update was successful to the first NWDAF.

[0132] Scenario 5: Deletion scenario.

[0133] When the first NWDAF determines that it is necessary to delete the second data in the registration information, the first NWDAF can send a deletion request to the UDM. In this case, the deletion request includes the identifier of the second data and the shared storage identifier associated with the second data. Here, for the method of determining that it is necessary to delete the second data and the location information, reference can be made to the description of Scenario 2 above, and the details will not be repeated here. In a possible case, after receiving the deletion request, the UDM deletes the second data under the shared path in the storage path indicated by the location information based on the deletion request and returns indication information indicating that the deletion was successful to the first NWDAF. The indication information also includes an identifier for successful deletion. In another possible case, if the UDM fails to normally delete the second data in the shared path, the UDM can return indication information for indicating the failure of deletion to the first NWDAF, and the indication information can also carry error information at the same time.

[0134] As an example of a specific deletion flow, reference can also be made to the flowchart shown in Figure 5B. Note that the flowchart shown in Figure 5B is introduced by taking the case where the deletion is successful as an example, and specifically includes the following content.

[0135] 501B. The first NWDAF determines that it is necessary to delete the second data included in the registration information.

[0136] 502B. The first NWDAF sends a deletion request including the identifier of the second data, the shared storage identifier associated with the second data, and the location information to the UDM.

[0137] 503B. The UDM receives the deletion request and deletes the second data on the shared path.

[0138] Specifically, the UDM determines that it is necessary to delete the second data on the shared path under the storage path indicated by the location information in response to the deletion request, and executes the deletion operation.

[0139] 504B. The UDM returns indication information indicating that the deletion was successful to the first NWDAF.

[0140] Scenario 6: Search scenario.

[0141] The NF consumer determines that it is necessary to first obtain the registration information or the data included in the registration information. For details, refer to the description of Scenario 3, which will not be repeated here. After the determination, the NF consumer can send a search request including the identifier of the data to be obtained, the shared storage identifier associated with the data, and the location information to the UDM. As an example, the case where the network element consumer needs to obtain the second data included in the registration information will be described. When the network element consumer determines that it is necessary to obtain the second data included in the registration information, the network element consumer can send a search request to the UDM, and this search request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information. In some cases, the UDM can obtain the second data from the storage path indicated by the location information based on the search request. Next, the UDM can return the obtained second data to the network element consumer, and the obtained second data can carry the indication information for indicating the success of the acquisition. In another case, when the UDM fails to obtain the second data from the shared data, the UDM can return the indication information indicating the failure of the acquisition to the network element consumer, and the indication information can also carry the error information.

[0142] Based on the above solution, when the NF consumer needs to obtain the second data stored by the first NWDAF, the search request sent to the UDM may include the shared storage identifier used by the first NWDAF and associated with the second data. Since the NF consumer can accurately obtain the second data stored by the first NWDAF, the search efficiency is improved.

[0143] As an example of a specific search flow, the flowchart shown in Figure 5C can be cited. Note that the flowchart shown in Figure 5C is introduced by taking the case where the search is successful as an example, and specifically includes the following content.

[0144] 501C. The network element consumer determines that it is necessary to obtain the second data included in the registration information.

[0145] 502C. The network element consumer sends a search request including the identifier of the second data, the shared storage identifier associated with the second data, and the location information to the UDM.

[0146] Here, the shared storage identifier associated with the second data is used to indicate that the second data is stored in the storage path indicated by the location information.

[0147] 503C. The UDM receives the search request and obtains the second data from the storage path indicated by the location information.

[0148] 504C. The UDM returns the indication information indicating that the search was successful and the second data to the network element consumer.

[0149] Based on the same concept as the above method, referring to FIG. 6, an embodiment of the present invention provides an apparatus 600 for registering user information. The apparatus 600 can execute each step of the above method, but the details will not be described again here to avoid repetition.

[0150] The apparatus 600 includes a processing unit 601 and a communication unit 602.

[0151] In a conceivable scenario, the processing unit 601 is configured to obtain the registration information of the terminal device.

[0152] The communication unit 602 is configured to send a registration request to the UDM. The registration request includes the registration information and the location information for specifying the storage path of the registration information in the UDM, and the location information includes the identifier of the NWDAF.

[0153] In some embodiments, the location information is a uniform resource identifier (URI).

[0154] In some embodiments, the location information further includes an analysis identifier of an event, and the analysis identifier of the event is used to indicate a first service executed by the NWDAF for the terminal device, and the registration information is generated when the NWDAF provides the first service for the terminal device.

[0155] In some embodiments, after sending a registration request to the UDM, the communication unit 602 is further configured as follows.

[0156] If it is determined that the registration information has been updated, a update request is sent to the UDM, the update request includes the updated registration information and the location information, and the update request is used to instruct the UDM to update the registration information in the storage path indicated by the location information to the updated registration information.

[0157] In some embodiments, after sending a registration request to the UDM, the communication unit 602 further If it is determined that the registration information needs to be deleted, the NWDAF sends a deletion request to the UDM, the deletion request includes the location information, and the deletion request is used to instruct the UDM to delete the registration information in the storage path indicated by the location information.

[0158] In another possible scenario, the processing unit 601 is configured to obtain the registration information of the terminal device.

[0159] The communication unit 602 is configured to send a registration request to the UDM. The registration request includes the registration information and location information for identifying a storage path of the registration information in the UDM. The registration information includes second data, and the second data is associated with a shared storage identifier, and the shared storage identifier is used to indicate that the second data belongs to the first NWDAF.

[0160] In some embodiments, the location information is a uniform resource identifier (URI).

[0161] In some embodiments, the registration information further includes third data, and the third data is not associated with the shared storage identifier, and the third data is stored in a storage path indicated by the location information.

[0162] In some embodiments, after the communication unit 602 sends a registration request to the UDM, further, when it is determined that the second data is updated, an update request is sent to the UDM. The update request includes the updated second data, the shared storage identifier associated with the second data, and the location information. The update request is used to instruct the UDM to update the second data in the storage path indicated by the location information to the updated second data.

[0163] In some embodiments, after the communication unit 602 sends a registration request to the UDM, further, when it is determined that the second data needs to be deleted, the NWDAF sends a deletion request to the UDM. The deletion request includes an identifier of the second data, the shared storage identifier associated with the second data, and the location information. The deletion request is used to instruct the UDM to delete the second data in the storage path indicated by the location information.

[0164] In another possible scenario, the communication unit 602 is configured to receive a registration request from the NWDAF. The registration request includes registration information of the terminal device and location information for identifying a storage path of the registration information in the device. The location information includes an identifier of the NWDAF, The processing unit 601 is configured to store the registration information in the storage path indicated by the location information.

[0165] In some embodiments, the location information is a uniform resource identifier (URI).

[0166] In some embodiments, the location information further includes an analysis identifier of an event, and the analysis identifier of the event is used to indicate a first service executed by the NWDAF for the terminal device. The registration information is generated when the NWDAF provides the first service for the terminal device.

[0167] In some embodiments, after the processing unit 601 stores the registration information in the storage path indicated by the location information, the communication unit 602 is further configured to receive an update request from the NWDAF. The update request includes updated registration information and the location information, The processing unit 601 is further configured to update the registration information in the storage path indicated by the location information to the updated registration information based on the update request.

[0168] In some embodiments, after the processing unit 601 stores the registration information in the storage path indicated by the location information, the communication unit 602 is further configured to receive a deletion request from the NWDAF. The deletion request includes the location information.

[0169] The processing unit 601 further deletes the registration information in the storage path indicated by the position information based on the deletion request.

[0170] In some embodiments, after the processing unit 601 stores the registration information in the storage path indicated by the position information, the communication unit 602 is further configured to receive a search request from a network element consumer. The search request includes the identifier of the first data and the position information.

[0171] The processing unit 601 further transmits the first data in the storage path indicated by the position information to the network element consumer.

[0172] In another possible scenario, the communication unit 602 is configured to receive a registration request from a first NWDAF. The registration request includes the registration information of the terminal device and the position information for identifying the storage path of the registration information in the device. The registration information is obtained by the NWDAF during the flowchart of registering the terminal device to the core network. The registration information includes second data, and the second data is associated with a shared storage identifier. The shared storage identifier is used to indicate that the second data belongs to the first NWDAF. The first NWDAF is any one of at least one NWDAF that provides services to the terminal device.

[0173] The processing unit 601 stores the second data in the storage path indicated by the position information.

[0174] In some embodiments, the position information is a uniform resource identifier (URI).

[0175] In some embodiments, the registration information further includes third data, and the third data is not associated with the shared storage identifier, indicating that the third data is stored in the storage path indicated by the location information.

[0176] In some embodiments, after the processing unit 601 stores the second data in the storage path indicated by the location information, the communication unit 602 is further configured to receive an update request from the first NWDAF. The update request includes the updated second data, the shared storage identifier associated with the second data, and the location information.

[0177] The processing unit 601 is further configured to update the second data in the storage path indicated by the location information to the updated second data.

[0178] In some embodiments, after the processing unit 601 stores the second data in the storage path indicated by the location information, the communication unit 602 is configured to receive a deletion request from the first NWDAF. The deletion request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information.

[0179] The processing unit 601 is further configured to delete the second data in the storage path indicated by the location information.

[0180] In some embodiments, after the processing unit 601 stores the second data in the storage path indicated by the location information, the communication unit 602 is further configured to request a search from a network element consumer. The search request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information.

[0181] The processing unit 601 is further configured to transmit second data within the storage path indicated by the position information to the network element consumer.

[0182] As shown in FIG. 7, an embodiment of the present invention also provides another device 700 for registering user information. The device 700 includes a communication interface 701, a memory 702, and a processor 703.

[0183] Here, the registration device 700 communicates with other devices via the communication interface 701, such as sending and receiving messages. The memory 702 is configured to store program instructions, and the processor 703 is configured to call the program instructions stored in the memory 702 and execute any method provided in the above embodiment based on the obtained program.

[0184] The embodiment of the present invention does not limit a specific connection medium among the communication interface 701, the memory 702, and the processor 703, such as a bus that can be divided into an address bus, a data bus, and a control bus.

[0185] In an embodiment of the present invention, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic device, a discrete gate, or transistor logic device, or a discrete gate, and can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied to be executed and completed by a hardware processor or by a combination of hardware and software modules within the processor.

[0186] In embodiments of the present invention, the memory may be a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), or may be a volatile memory such as a random-access memory (RAM). The memory can be configured to carry or store the desired program code in the form of instructions or data structures, and may be other media accessible by a computer, but is not limited thereto. The memory in embodiments of the present invention may be a circuit or other device capable of realizing a storage function for storing program instructions and / or data.

[0187] Embodiments of the present invention also provide a computer-readable storage medium containing program code. When the program code is executed on a computer, it causes the computer to execute the steps of the method provided in the above embodiments of the present invention.

[0188] Those skilled in the art should understand that embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can adopt the form of a computer program product implemented on a storage medium (including but not limited to disk memory, compact disc read-only memory (CD-ROM), optical memory, etc.) of one or more computers with available program code.

[0189] These computer program instructions may be loaded onto a computer or other programmable data processing apparatus, resulting in a series of operational steps being executed on the computer or other programmable apparatus to generate computer-implemented processing. The computer or other programmable device provides steps for performing the functions specified in one or more of the flows of the flowchart and / or one or more of the blocks of the block diagram.

[0190] Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional modifications and variations to these embodiments if they understand the basic creative concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments within the scope of the present invention and all modifications and variations.

[0191] Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from the scope of the present invention. Thus, if these modifications and variations of the present invention are included within the scope of the claims of the present invention and the scope of its equivalent technologies, the present invention shall also include these modifications and variations.

Explanation of Reference Numerals

[0192] 101 Terminal device 103 Unified Data Management (UDM) 600 Device 601 Processing unit 602 Communication unit 700 Device 701 Communication interface 702 Memory 703 Processor 1021 Session Management Function (SMF) 1022 Mobility Management Function (AMF) 1023 Network Data Analysis Function (NWDAF) 1024 Network Element Consumer

Claims

1. A method for registering user information, comprising: a step in which a network data analysis function (NWDAF) obtains registration information of a terminal device; a step in which the NWDAF sends a registration request to unified data management (UDM), wherein the registration request includes the registration information and position information for specifying a storage path of the registration information in the UDM, and the position information includes an identifier of the NWDAF. A method for registering user information, characterized by the above.

2. The method for registering user information according to claim 1, wherein the position information is a uniform resource identifier (URI).

3. The method for registering user information according to claim 1, wherein the position information further includes an analysis identifier of an event, the analysis identifier of the event is used to indicate a first service executed by the NWDAF for the terminal device, and the registration information is generated when the NWDAF provides the first service for the terminal device.

4. After the NWDAF sends a registration request to the UDM, the method further includes: a step of sending an update request to the UDM when the NWDAF determines that the registration information has been updated, wherein the update request includes the updated registration information and the position information, and the update request is used to instruct the UDM to update the registration information in the storage path indicated by the position information to the updated registration information. A method for registering user information according to any one of claims 1 to 3, characterized by the above.

5. After the NWDAF sends a registration request to the UDM, the method further includes: a step in which the NWDAF sends a deletion request to the UDM when the NWDAF determines that it is necessary to delete the registration information, wherein the deletion request includes the position information, and the deletion request is used to instruct the UDM to delete the registration information in the storage path indicated by the position information. A method for registering user information according to any one of claims 1 to 3, characterized by the above.

6. A method for registering user information, comprising: The step in which the UDM receives a registration request from the NWDAF, The step in which the UDM stores the registration information in a storage path indicated by location information, and The registration request includes the registration information of the terminal device and the location information for specifying the storage path of the registration information in the UDM, and the identifier of the NWDAF is included in the location information. A method for registering user information, characterized in that.

7. The method for registering user information according to claim 6, characterized in that the location information is a uniform resource identifier (URI).

8. The location information further includes an analysis identifier of an event, and the analysis identifier of the event is used to indicate a first service executed by the NWDAF for the terminal device, and the registration information is generated when the NWDAF provides the first service for the terminal device. A method for registering user information according to claim 6, characterized in that.

9. After the UDM stores the registration information in a storage path indicated by the location information, the method further includes: The step in which the UDM receives a search request from a network element consumer, and The step in which the UDM transmits first data in a storage path indicated by the location information to the network element consumer, and The search request includes an identifier of first data included in the registration information and the location information. A method for registering user information according to any one of claims 6 to 8, characterized in that.

10. An apparatus for registering user information, comprising: A processing unit configured to obtain registration information of a terminal device, and A communication unit configured to transmit a registration request to the UDM, and The registration request includes the registration information and location information for specifying a storage path of the registration information in the UDM, and an identifier of the NWDAF is included in the location information. An apparatus for registering user information, characterized in that.

11. The apparatus for registering user information according to claim 10, characterized in that the location information is a uniform resource identifier (URI).

12. The location information further includes an analysis identifier of an event, and the analysis identifier of the event is used to indicate a first service executed by the NWDAF for the terminal device, and the registration information is generated when the NWDAF provides the first service for the terminal device. The apparatus for registering user information according to claim 10, characterized in that.

13. An apparatus for registering user information, A communication unit configured to receive a registration request from the NWDAF, And a processing unit configured to store the registration information in a storage path indicated by the location information, The registration request includes the registration information of the terminal device and the location information for identifying the storage path of the registration information in the apparatus, and the location information includes an identifier of the NWDAF. The apparatus for registering user information, characterized in that.

14. The location information is a uniform resource identifier (URI). The apparatus for registering user information according to claim 13, characterized in that.

15. The location information further includes an analysis identifier of an event, and the analysis identifier of the event is used to indicate a first service executed by the NWDAF for the terminal device, and the registration information is generated when the NWDAF provides the first service for the terminal device. The apparatus for registering user information according to claim 13, characterized in that.

Images