A method and apparatus for registering user information

Abstract

The application provides a user information registration method and device to solve the problem of mutual coverage between registration information caused by multiple NWDAFs registering terminal device registration information to UDM. The method comprises: a network data analysis function (NWDAF) obtaining registration information of a terminal device; the NWDAF sending a registration request to a unified data management function (UDM); the registration request comprising the registration information and positioning information for identifying the storage path of the registration information in the UDM, the positioning information comprising the identifier of the NWDAF.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for registering user information. Background Technology

[0002] Currently, the traditional method of registering terminal device registration information is unique, meaning that one network element serves one terminal device and registers the terminal device's registration information in the database. When a terminal device is transferred between network elements, the old network element will pass the terminal device's registration information to the new network element, and the new network element will re-register or update the terminal device's registration information in the database.

[0003] Currently, when a Network Data Analytic Function (NWDAF) serves a specific terminal, it also needs to register the terminal device's registration information with the database. Since multiple NWDAFs can serve the same terminal device, the registration information of different NWDAFs may overlap when registering the terminal device's registration information with the database. Summary of the Invention

[0004] This application provides a user information registration method and apparatus to solve the problem of overlapping registration information caused by multiple NWDAFs registering registration information with UDM terminal devices.

[0005] In a first aspect, embodiments of this application provide a method for registering user information, including:

[0006] The Network Data Analysis Function (NWDAF) obtains the registration information of terminal devices;

[0007] The NWDAF sends a registration request to the Unified Data Management Function (UDM); the registration request includes the registration information and location information for identifying the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF.

[0008] Based on the above scheme, by adding the NWDAF identifier to the location information sent to the UDM, the registration information of different NWDAFs can be stored in different locations in the UDM, which can prevent the registration information of different NWDAFs from overwriting each other.

[0009] In some embodiments, the location information is a Resource Location Identifier (URI).

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

[0011] Based on the above scheme, an event analysis identifier is added to the location information, so that the data corresponding to different services provided by NWDAF to the terminal device can be stored in different locations, further preventing the registration information of different NWDAFs with the same event analysis identifier from overwriting each other.

[0012] In some embodiments, after the NWDAF sends a registration request to the UDM, the method further includes:

[0013] When the NWDAF determines that the registration information has been updated, it sends an update request to the UDM. The update request includes the updated registration information and the location information. 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.

[0014] In existing technologies, since multiple NWDAFs use the same location information for their registration, updating the registration information of one NWDAF may affect the registration information of other NWDAFs. However, this application allows for targeted updates to the registration information of a specific NWDAF based on the NWDAF identifier contained in the location information, without affecting the registration information of other NWDAFs and avoiding update errors.

[0015] In some embodiments, after the NWDAF sends a registration request to the UDM, the method further includes:

[0016] When the NWDAF determines that the registration information needs to be deleted, it 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.

[0017] In existing technologies, because the registration information of multiple NWDAFs is stored in the same storage path, when a UDM deletes registration information, it may delete the registration information of multiple NWDAFs in that storage path. However, this application, by adding the NWDAF identifier to the location information, allows the UDM to selectively delete the registration information of the NWDAF that sent the deletion request, without affecting the registration information of other NWDAFs, thus avoiding accidental deletion.

[0018] Secondly, embodiments of this application provide another method for registering user information, including:

[0019] The UDM receives a registration request from the NWDAF; the registration request includes registration information of the terminal device and location information for identifying the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF;

[0020] The UDM stores the registration information in the storage path indicated by the location information.

[0021] In some embodiments, after the UDM stores the registration information in the storage path indicated by the location information, the method further includes:

[0022] The UDM receives an update request from the NWDAF; the update request includes the updated registration information and the location information;

[0023] The UDM updates the registration information in the storage path indicated by the location information to the updated registration information according to the update request.

[0024] In some embodiments, after the UDM stores the registration information in the storage path indicated by the location information, the method further includes:

[0025] The UDM receives a deletion request from the NWDAF; the deletion request includes the location information;

[0026] The UDM deletes the registration information in the storage path indicated by the location information according to the deletion request.

[0027] In some embodiments, after the UDM stores the registration information in the storage path indicated by the location information, the method further includes:

[0028] The UDM receives a retrieval request from a network element consumer; the retrieval request includes the identifier of the first data included in the registration information and the location information;

[0029] The UDM sends the first data in the storage path indicated by the location information to the network element consumer.

[0030] Thirdly, embodiments of this application provide a method for registering user information, including:

[0031] The first NWDAF obtains the registration information of the terminal device;

[0032] The first NWDAF sends a registration request to the UDM; the registration request includes the registration information and location information for identifying the storage path of the registration information in the UDM;

[0033] The registration information includes second data, which 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 serving the terminal device.

[0034] Based on the above scheme, 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 in this application are different. So even if multiple NWDAFs store the second data in the UDM, since the shared storage identifiers associated with the second data stored by different NWDAFs are different, the situation of data overwriting can be avoided.

[0035] In some embodiments, the location information is a Resource Location Identifier (URI).

[0036] In some embodiments, the registration information may further include third data, which is not associated with the shared storage identifier, to indicate that the third data is stored in the storage path indicated by the location information.

[0037] In some embodiments, after the first NWDAF sends a registration request to the UDM, the method further includes:

[0038] When the first NWDAF determines that the second data has been updated, it sends an update request 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.

[0039] Based on the above scheme, since the first NWDAF carries the shared storage identifier associated with the second data in the update request sent to the UDM, it can be indicated that the second data to be updated is the second data stored in the first NWDAF. After receiving the update request, the UDM will update the second data previously stored in the first NWDAF, and will not update the second data stored in other NWDAFs serving the terminal device. This can avoid the occurrence of update errors.

[0040] In some embodiments, after the first NWDAF sends a registration request to the UDM, the method further includes:

[0041] When the first NWDAF determines that the second data needs to be deleted, it 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 in the storage path indicated by the location information.

[0042] Based on the above scheme, since different NWDAFs use different shared storage identifiers, when the first NWDAF sends a deletion request to the UDM, the UDM will delete the data stored by the first NWDAF according to the shared storage identifier used by the first NWDAF, which can avoid accidental deletion.

[0043] Fourthly, embodiments of this application provide another method for registering user information, including:

[0044] The UDM receives a registration request from the first NWDAF; the registration request includes registration information of the terminal device and location information for identifying the storage path of the registration information in the UDM; the registration information is obtained by the NWDAF during the process of the terminal device registering to the core network;

[0045] The registration information includes second data, which 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 serving the terminal device.

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

[0047] In some embodiments, after the UDM stores the second data in the storage path indicated by the location information, the method further includes:

[0048] The UDM receives 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;

[0049] The UDM updates the second data in the storage path indicated by the location information to the updated second data.

[0050] In some embodiments, after the UDM stores the second data in the storage path indicated by the location information, the method further includes:

[0051] The UDM receives 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;

[0052] The UDM deletes the second data from the storage path indicated by the location information.

[0053] In some embodiments, after the UDM stores the registration information in the storage path indicated by the location information, the method further includes:

[0054] The UDM receives a retrieval request from a network element consumer; the retrieval request includes the identifier of the first data included in the registration information and the location information;

[0055] The UDM sends the first data in the storage path indicated by the location information to the network element consumer.

[0056] Fifthly, embodiments of this application provide a communication system, including:

[0057] NWDAF is used to obtain the registration information of the terminal device;

[0058] The NWDAF is also used to send a registration request to the UDM; the registration request includes the registration information and location information for identifying the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF;

[0059] The UDM is used to store the registration information in the storage path indicated by the location information.

[0060] In some embodiments, after the UDM stores the registration information in the storage path indicated by the location information,

[0061] The NWDAF is further configured to send an update request to the UDM when it is determined that the registration information has been updated; the update request includes the updated registration information and the location information.

[0062] The UDM is also used to update the registration information in the storage path indicated by the location information to the updated registration information.

[0063] In some embodiments, after the UDM stores the registration information in the storage path indicated by the location information,

[0064] The NWDAF is also used to send a deletion request to the UDM when it is determined that the registration information needs to be deleted; the deletion request includes the location information.

[0065] The UDM is also used to delete the registration information in the storage path indicated by the location information.

[0066] Sixthly, embodiments of this application provide another communication system, including:

[0067] The first NWDAF is used to obtain the registration information of the terminal device;

[0068] The first NWDAF is further configured to send a registration request to the UDM; the registration request includes the registration information and location information for identifying the 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; the first NWDAF is any one of at least one NWDAF serving the terminal device;

[0069] The UDM is used to store the second data in the storage path indicated by the location information.

[0070] In some embodiments, after the UDM stores the second data in the storage path indicated by the location information,

[0071] The first NWDAF is further configured to send an update request to the UDM when it is determined that the second data has been updated; the update request includes the updated second data, the shared storage identifier associated with the second data, and the location information;

[0072] The UDM is also used to update the second data in the storage path indicated by the location information to the updated second data.

[0073] In some embodiments, after the UDM stores the second data in the storage path indicated by the location information,

[0074] The first NWDAF is further configured to send a deletion request to the UDM when it is determined that the second data needs to be deleted; the deletion request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information;

[0075] The UDM is also used to delete the second data in the storage path indicated by the location information.

[0076] In some embodiments, the system further includes a network element consumer, which, after the UDM stores the second data into the storage path indicated by the location information,

[0077] The network element consumer is used to receive service requests from terminal devices, and the service requests are used to indicate the services required by the terminal devices.

[0078] 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 retrieval request to the UDM; the retrieval request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information;

[0079] The UDM is also used to send the second data in the storage path indicated by the location information to the network element consumer.

[0080] Seventhly, embodiments of this application provide a user information registration device, including:

[0081] The processing unit is used to obtain the registration information of the terminal device;

[0082] A communication unit is used to send a registration request to the UDM; the registration request includes the registration information and location information for identifying the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF.

[0083] In some embodiments, the location information is a Resource Location Identifier (URI).

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

[0085] In some embodiments, after sending a registration request to the UDM, the communication unit is further configured to:

[0086] When it is determined that the registration information has been updated, an 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.

[0087] In some embodiments, after sending a registration request to the UDM, the communication unit is further configured to:

[0088] When it is determined that the registration information needs to be deleted, a deletion request is sent 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.

[0089] Eighthly, embodiments of this application provide another user information registration device, including:

[0090] A communication unit is configured to receive a registration request sent from the NWDAF; the registration request includes registration information of the terminal device and location information for identifying the storage path of the registration information in the device, the location information including the identifier of the NWDAF;

[0091] The processing unit is used to store the registration information in the storage path indicated by the location information.

[0092] In some embodiments, after the processing unit stores the registration information into the storage path indicated by the location information,

[0093] The communication unit is also configured to receive an update request from the NWDAF; the update request includes the updated registration information and the location information;

[0094] 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 according to the update request.

[0095] In some embodiments, after the processing unit stores the registration information into the storage path indicated by the location information,

[0096] The communication unit is further configured to receive a deletion request from the NWDAF; the deletion request includes the location information.

[0097] The processing unit is further configured to delete the registration information in the storage path indicated by the location information according to the deletion request.

[0098] In some embodiments, after the processing unit stores the registration information into the storage path indicated by the location information,

[0099] The communication unit is further configured to receive a retrieval request from a network element consumer; the retrieval request includes the identifier of the first data and the location information;

[0100] The processing unit is further configured to send the first data in the storage path indicated by the positioning information to the network element consumer.

[0101] Ninthly, embodiments of this application provide another method for registering user information, including:

[0102] The processing unit is used to obtain the registration information of the terminal device;

[0103] A communication unit is used to send a registration request to a UDM; the registration request includes the registration information and location information for identifying the 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, and the shared storage identifier is used to indicate that the second data belongs to the first NWDAF.

[0104] In some embodiments, the location information is a Resource Location Identifier (URI).

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

[0106] In some embodiments, after sending a registration request to the UDM, the communication unit is further configured to:

[0107] When it is determined that the second data has been 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, 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.

[0108] In some embodiments, after sending a registration request to the UDM, the communication unit is further configured to:

[0109] When it is determined that the second data needs to be deleted, a deletion request is sent 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, and the deletion request is used to instruct the UDM to delete the second data in the storage path indicated by the location information.

[0110] In a tenth aspect, embodiments of this application provide a user information registration device, comprising:

[0111] A communication unit is configured to receive a registration request from a first NWDAF; the registration request includes registration information of a terminal device and location information for identifying the storage path of the registration information in the device; the registration information is obtained by the NWDAF during the process of the terminal device registering to the core network; 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; the first NWDAF is any one of at least one NWDAF serving the terminal device;

[0112] A processing unit is configured to store the second data into the storage path indicated by the location information.

[0113] In some embodiments, after the processing unit stores the second data into the storage path indicated by the location information,

[0114] The communication unit is further configured to receive an update request from the first NWDAF; the update request includes updated second data, a shared storage identifier associated with the second data, and the location information;

[0115] 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.

[0116] In some embodiments, after the processing unit stores the second data into the storage path indicated by the location information,

[0117] The communication unit is further 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;

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

[0119] Eleventhly, embodiments of this application provide another user information registration device, including a memory and a processor;

[0120] Memory, used to store program instructions;

[0121] A processor is configured to invoke program instructions stored in the memory and execute the method in either the first or third aspect according to the obtained program.

[0122] In a twelfth aspect, embodiments of this application provide another user information registration apparatus, including a memory and a processor;

[0123] Memory, used to store program instructions;

[0124] A processor is configured to invoke program instructions stored in the memory and execute the method in either the second or fourth aspect according to the obtained program.

[0125] In a thirteenth aspect, embodiments of this application provide a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform the above-described method.

[0126] Furthermore, the technical effects of any of the implementation methods in the second, fourth to thirteenth aspects can be found in the technical effects of the different implementation methods in the first and third aspects, and will not be repeated here. Attached Figure Description

[0127] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0128] Figure 2 A flowchart illustrating a user information registration method provided in this application embodiment;

[0129] Figure 3A This is a schematic diagram of a user information update process provided in an embodiment of this application;

[0130] Figure 3B This is a schematic diagram of a user information deletion process provided in an embodiment of this application;

[0131] Figure 3C This application provides a schematic diagram of a user information retrieval process according to an embodiment of the present application.

[0132] Figure 4 A flowchart illustrating another user information registration method provided in this application embodiment;

[0133] Figure 5A This is a schematic diagram of another user information update process provided in an embodiment of this application;

[0134] Figure 5B This is a schematic diagram illustrating another user information deletion process provided in an embodiment of this application;

[0135] Figure 5C This is a schematic diagram of another user information retrieval process provided in an embodiment of this application;

[0136] Figure 6 This is a schematic diagram of the structure of a user information registration device 600 provided in an embodiment of this application;

[0137] Figure 7 This is a schematic diagram of the structure of a user information registration device 700 provided in an embodiment of this application. Detailed Implementation

[0138] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0139] The application scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application, and do not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will understand that with the emergence of new application scenarios, the technical solutions provided in this application are also applicable to similar technical problems. In the description of this application, unless otherwise stated, "multiple" means two or more.

[0140] Figure 1 This example illustrates a communication system architecture. It should be understood that the embodiments of this application are not limited to... Figure 1 In the system shown, in addition, Figure 1 The device in the document can be hardware, software defined by function, or a combination of both. For example... Figure 1 As shown, the system architecture provided in this application embodiment 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. This application embodiment does not limit the number of terminal devices, NWDAFs, SMFs, and AMFs included in the system. Figure 1 This example will only use one instance. Furthermore, it should be noted that a communication system can also include other network elements, such as access network equipment. Figure 1 It is not shown in the document.

[0141] Terminal device 101, also known as a terminal, mobile station (MS), mobile terminal (MT), etc., is a device that provides voice and / or data connectivity to users. Examples include handheld devices and in-vehicle devices with wireless connectivity. Currently, some examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes.

[0142] The SMF1021 is a functional unit in a service-based architecture for 5G communication systems. The SMF is primarily responsible for session management, such as session establishment, modification, and release. It is also used to implement functions such as allocating and managing IP addresses for terminal devices.

[0143] The AMF1022 is a functional unit in a 5G communication system. It is primarily responsible for implementing functions such as terminal device registration and access to the core network.

[0144] The NWDAF1023 collects information on user terminal device connection management, mobility management, session management, and accessed services. It uses reliable analysis and prediction models to evaluate and analyze different types of users, build user profiles, determine user movement trajectories and service usage habits, and predict user behavior. Based on the analysis and prediction data, it optimizes user mobility management parameters and radio resource management parameters.

[0145] UDM103 is an intelligent management platform for data services and data business operations. Its features include: simple deployment; robust user and data application security; tiered user management; comprehensive security measures; and robust data storage security.

[0146] Because network elements such as SMF or AMF provide unique services to terminal devices—that is, one SMF (or AMF) can only serve one terminal device—the network element currently serving a terminal device will register the terminal device's registration information in the UDM. Therefore, the registration information of that terminal device registered by the SMF stored in the UDM is unique. However, since multiple NWDAFs can serve the same UE, when different NWDAFs register the same terminal device's registration information with the UDM, there may be a situation where the information registered by the previous NWDAF is overwritten by the information registered by the subsequent NWDAF.

[0147] This application provides a user information registration method and apparatus. When an NWDAF registers user information, it adds an NWDAF identifier to the location information used to indicate the storage path in the registration request. This ensures that different NWDAFs registering registration information for the same terminal device will have different storage paths in the UDM, thus solving the problem of registration information being overwritten.

[0148] The following describes the user information registration method provided in the embodiments of this application. See also: Figure 2 This is a flowchart illustrating a user information registration method provided in an embodiment of this application. The method is executed by an NWDAF (Network Window Data Allocation Filter). Optionally, the NWDAF executing this process can be... Figure 1 The first NWDAF shown could also be a second NWDAF; this application does not specifically limit this. The method flow specifically includes:

[0149] 201. NWDAF obtains the registration information of the terminal device.

[0150] Optionally, the registration information may include one or more of the following:

[0151] The information includes the terminal device's ID or identifier, the NWDAF identifier, the event analysis identifier, the registration time, the UE context information, or the services that the NWDAF can provide to the terminal device. The NWDAF identifier can include the NWDAF instance ID or the NWDAF set ID. It should be noted that both the NWDAF instance ID and the NWDAF set ID can uniquely identify the NWDAF in the communication system. The NWDAF set ID is the ID of the NWDAF within a set of NWDAFs. For example, the NWDAF set ID consists of the ID of the NWDAF set to which the NWDAF belongs and the ID of the NWDAF within the NWDAF set. The event analysis identifier can be an event analysis ID (analytics ID), used to indicate the first service performed by the NWDAF for the terminal device. It should be noted that the registration information is generated by the NWDAF when providing 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.

[0152] As an optional approach, NWDAF obtaining the registration information of a terminal device may include: NWDAF receiving context information of the terminal device from a Network Data Analytic Function service consumer (NWDAF service consumer) or other network elements (e.g., AMF or SMF). Further, NWDAF can generate registration information for the terminal device based on the received context information. For example, after receiving the context information, NWDAF can generate information such as an NWDAF instance number, event analysis identifier, or registration time, and use the generated information and the received user context information together as the terminal device's registration information. Of course, the above method is merely an example; NWDAF can also obtain the terminal device's registration information through other methods, and this application does not specifically limit this approach.

[0153] 202. NWDAF sends a registration request to UDM, which includes registration information and location information.

[0154] 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, for example, it may include the instance number of the NWDAF or the set number of the NWDAF.

[0155] Optionally, the location information can be a Uniform Resource Identifier (URI). Taking the NWDAF instance number as an example, the location information could be:

[0156] The structure is ` / {ueId} / registrations / nwdaf-registration / nwdafInstanceId`, where `ueId` identifies the specific terminal device registering the information. `registrations` indicates that the registration request is a single registration request. `nwdaf-registration` indicates that the registration request was issued by NWDAF. `nwdafInstanceId` is the instance number of NWDAF.

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

[0158] Specifically, after receiving a registration request, 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 that storage path.

[0159] In one possible embodiment, after storing the registration information in the storage path indicated by the location information, the UDM can also return an indication message to the NWDAF to indicate successful registration. For example, this indication message could be "200 OK", "201 Created", or "204 Content". As another example, the UDM can also carry a successful registration identifier or registration information along with the indication message sent to the NWDAF. This allows the NWDAF to determine which registration information was successfully registered.

[0160] In another possible embodiment, if the UDM is unable to store the registration information for some reason, such as the UDM determining, based on the authorization information pre-provided by the terminal device, that the NWDAF that sent the registration request cannot provide services to the terminal device, the UDM can return an indication message indicating registration failure. This indication message may include a Hypertext Transfer Protocol (HTTP) status code indicating the current transmission status, such as "403 Forbidden" or "404 Not Found," to indicate that the registration information was not received or processed by the UDM. Optionally, the UDM may also carry error details along with the indication message indicating registration failure.

[0161] In some embodiments, the location information sent by the NWDAF to the UDM may further include an event analysis identifier. The event analysis identifier indicates a first service performed by the NWDAF for the terminal device, where the first service is one of the services that the NWDAF can provide to the terminal device. As an example, the event analysis identifier can be represented by an event analysis ID, and the location information can be represented as follows:

[0162] The structure is: / {ueId} / registrations / nwdaf-registration / nwdafInstanceId / {analyticsId}, where ueId, registrations, nwdaf-registration, and nwdafInstanceId represent the contents described above. Figure 2 The relevant details in step 202 will not be repeated here. The analytics ID is used to represent the event analysis number of the service performed by NWDAF for the terminal device.

[0163] The first user information registration scheme proposed in this application embodiment will be introduced below in conjunction with a specific scenario.

[0164] Scenario 1: Update the scene.

[0165] NWDAF determines when the registration information of a terminal device is updated. For example, when the service capabilities of NWDAF change, such as when a certain service is added, or when the terminal device no longer needs a certain service provided by NWDAF, its registration information will be updated.

[0166] In some embodiments, after confirming the registration information has been updated, the NWDAF may send an update request to the UDM, which includes the updated registration information and location information. Optionally, the location information can be found in the examples above and will not be repeated here. After receiving the update request, the UDM may delete the registration information from 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.

[0167] In other embodiments, the NWDAF may update only one or several data items in the registration information. The following example illustrates this with a change in data A within the registration information. Optionally, after determining that data A has been updated, the NWDAF may send an update request to the UDM. This update request may include the updated data A, the identifier of data A, and location information. Upon receiving the update request, the UDM can determine, based on the identifier of data A, that data A stored in the storage path indicated by the location information needs to be updated. Further, the UDM may delete data A from the storage path indicated by the location information and store the updated data A in the storage path indicated by the location information.

[0168] In one possible scenario, if the UDM successfully updates the data included in the update request (which could be registration information or data included in the registration information) to the storage path indicated by the location information, it can return an indication message to the NWDAF indicating a successful update, such as "204 No Content". Optionally, the UDM can also return the successfully updated data, a successful update identifier, or both the successfully updated data and the successful update identifier along with the indication message to the NWDAF.

[0169] In another possible scenario, if the UDM fails to update the data—for example, if the storage path indicated by the location information received by the UDM does not exist, or if the data to be updated does not exist—the UDM will be unable to update the data. In this case, the UDM can return an indication message to the NWDAF indicating the update failure, such as "404 Not Found". Optionally, the UDM can also return an error message along with the indication message to the NWDAF. The error message indicates the reason for the update failure.

[0170] Alternatively, you can refer to the detailed update process. Figure 3A The process is shown below. It should be noted that... Figure 3A The process shown is based on updating the entire registration information successfully. Specifically, it includes:

[0171] 301A, NWDAF determines that the registration information has been updated and retrieves the updated registration information.

[0172] 302A, NWDAF sends an update request to UDM, which includes updated registration and location information.

[0173] Optionally, the location information can be found in the description in the above embodiments, and will not be repeated here.

[0174] 303A, UDM receives an update request and updates the registration information.

[0175] Specifically, UDM can replace the registration information in the storage path indicated by the location information with the updated registration information.

[0176] 304A, UDM returns an indication message to NWDAF to indicate that the update was successful.

[0177] Scenario 2: Delete the scenario.

[0178] The NWDAF confirms the need to delete the registration information of a terminal device. For example, this might happen when the service provided by the NWDAF to the terminal device has been completed, or when the terminal device has left the NWDAF's service area. Optionally, after determining the need to delete the registration information, the NWDAF can send a deletion request to the UDM, which includes location information. Optionally, the location information can be found in the description in the above embodiments and will not be repeated here. In one possible scenario, after receiving the deletion request, the UDM can delete the registration information in the storage path indicated by the location information included in the deletion request and can return an indication message to the NWDAF indicating successful deletion. Optionally, the UDM can also carry a deletion success identifier when sending the indication message. In another possible scenario, if the UDM fails to successfully delete the registration information in the storage path indicated by the location information, it can return an indication message to the NWDAF indicating deletion failure, and can also carry error information indicating the reason for the deletion failure.

[0179] As an example, the specific deletion process can also be found in [link to documentation]. Figure 3B The flowchart shown is provided. It should be noted that... Figure 3B The flowchart shown illustrates the process using a successful deletion as an example. Specifically, it includes:

[0180] 301B, NWDAF has determined that the registration information needs to be deleted.

[0181] 302B, NWDAF sends a deletion request to UDM, which includes location information.

[0182] 303B, UDM receives the deletion request and deletes the registration information from the storage path indicated by the location information.

[0183] 304B, UDM returns an indication message to NWDAF to indicate that the deletion was successful.

[0184] Scenario 3: Search Scenario.

[0185] A network function consumer (NF consumer) can first determine that it needs to obtain registration information or one or more data items included in the registration information. For example, when a terminal device sends a service request to an NF consumer (such as an AMF, or other network elements in the communication system), the NF consumer can send a retrieval request to the UDM based on the service request from the terminal device. The retrieval request is used to request the NWDAF that provides services to the terminal device and the registration information registered by the NWDAF with the UDM, or the data included in the registration information. As an example, the following describes how the NF consumer needs to obtain the first data included in the registration information. The first data is any one of the data included in the registration information. After determining that it needs to obtain the first data, the NF consumer can send a retrieval request to the UDM, which includes the identifier and location information of the first data. In one case, the UDM can obtain the first data from the storage path indicated by the location information based on the retrieval request. Further, the UDM can return an indication message to the NF consumer to indicate successful retrieval, such as "200 OK", along with the obtained first data. In another scenario, if the UDM does not find the first data in the storage path indicated by the location information, the UDM will return an indication message to the NFconsumer indicating the retrieval failure, such as "404 Not Found", and may also include error information.

[0186] As an example, the specific search process can be found in [link to relevant documentation]. Figure 3C The flowchart shown is provided. It should be noted that... Figure 3C The flowchart shown illustrates the process using a successful search as an example. Specifically, it includes:

[0187] 301C, NF consumer determines that it needs to obtain the first data including registration information.

[0188] 302C, the NF consumer sends a retrieval request to the UDM, which includes the identifier and location information of the first data.

[0189] 303C, UDM receives a retrieval request and retrieves the first data from the storage path indicated by the location information.

[0190] 304C, UDM returns an indication message and initial data to the NF consumer to indicate a successful retrieval.

[0191] Since multiple NWDAFs can serve the same terminal device simultaneously, and multiple NWDAFs need to register the terminal device's registration information with the UDM, it may lead to situations where registration information overlaps with each other.

[0192] See Figure 4 This is a flowchart of another user information registration method provided in an embodiment of this application. The method is executed by a first NWDAF, which is any one of a plurality of NWDAFs serving a terminal device. The specific steps of the method include:

[0193] 401, the first NWDAF obtains the registration information of the terminal device.

[0194] Optionally, the registration information of the terminal device can be found at [link to relevant documentation]. Figure 2 The relevant information in step 201 will not be repeated here.

[0195] 402. The first NWDAF sends a registration request to the UDM, which includes registration information and location information.

[0196] The registration information includes second data, which is associated with a shared storage identifier, indicating that the second data belongs to the first NWDAF.

[0197] In some embodiments, the location information is a resource location identifier (URI). Optionally, the location information can be represented as:

[0198] The information for each item in ` / {ueId} / registrations / nwdaf-registration` can be found in [link to relevant documentation]. Figure 2 The details of step 202 will not be repeated here.

[0199] Optionally, the location information may also include an event analysis identifier, used to indicate the first service performed by the first NWDAF for the terminal device. Taking the event analysis identifier as an example, the location information can be represented as follows:

[0200] The contents of / {ueId} / registrations / nwdaf-registration / {analyticsId} can be found in the above embodiments and will not be repeated here.

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

[0202] In one possible scenario, the UDM can store all received registration information in the storage path indicated by the location information, where the second data included in the registration information is associated with a shared data identifier. In some embodiments, the registration information may also include other data not associated with a shared data identifier. In another possible scenario, the UDM can also establish a sub-path under the storage path indicated by the location information. This sub-path can serve as a shared path for at least one NWDAF serving the terminal device; for ease of description, this sub-path will be referred to as the shared path below. When the UDM receives second data with a shared data identifier, it can store the second data in the shared path. In the following description, the UDM storing the second data in the shared path will be used as an example.

[0203] Optionally, the UDM may also store other data in the registration information that is not associated with a shared storage identifier besides the second data 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 a shared storage identifier, then the UDM will store the third data in the storage path indicated by the location information.

[0204] In one possible scenario, if the UDM successfully stores the data, it can return an indication message to the first NWDAF indicating successful registration. This indication message can be found in the description of the above embodiments and will not be repeated here. In another possible scenario, if the UDM fails to successfully store the data, it can return an indication message to the first NWDAF indicating registration failure, and may also carry error information indicating the reason for the registration failure.

[0205] Based on the above scheme, it can be seen that the shared storage identifiers used by different NWDAFs in this application are different. Therefore, even if different NWDAFs store the same data in the shared path, since the shared storage identifiers associated with the data stored by different NWDAFs are different, there will be no situation where the data is overwritten.

[0206] The second user information registration scheme proposed in this application will be introduced below in a specific scenario.

[0207] Scenario 4: Update the scene.

[0208] In some embodiments, after the first NWDAF determines that the second data included in the registration information of the terminal device has been updated, it can send an update request to the UDM. The update request includes the updated second data, the shared storage identifier associated with the second data, and location information. Optionally, the location information may refer to... Figure 4The example in step 402 will not be repeated here. After receiving the update request, the UDM can determine, based on the shared storage identifier associated with the second data included in the update request, that the updated second data included in the update request needs to be stored in the shared path included in the storage path indicated by the location information. The UDM can delete the second data in the shared path and store the updated second data in the shared path, completing the update of the second data. In one possible case, if the UDM update is successful, that is, if the original second data in the shared path is successfully replaced with the updated second data, it can return an indication message indicating successful update to the first NWDAF. In another possible case, if the UDM update fails, it can return an indication message indicating update failure to the first NWDAF. The specific indication message and the reason for update failure can be found in the description in Scenario 1, and will not be repeated here.

[0209] For example, the specific update process can be found in [link to documentation]. Figure 5A The process is shown below. It should be noted that... Figure 5A The process shown uses the successful update of the second set of data as an example. Specifically, it includes:

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

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

[0212] 503A, UDM receives an update request and updates the second data.

[0213] Specifically, the UDM determines, based on the location information and the shared storage identifier associated with the second data, that the second data in the shared path within the storage path indicated by the location information needs to be updated. Further, the UDM can delete the second data stored in the shared path and store the updated second data, as included in the update request, in the shared path.

[0214] 504A, UDM returns an indication message to the first NWDAF to indicate that the update was successful.

[0215] Scenario 5: Delete the scene.

[0216] When the first NWDAF determines that the second data in the registration information needs to be deleted, it can send 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 location information. For an explanation of how to determine the need to delete the second data and the location information, please refer to the description in Scenario 2 above; it will not be repeated here. In one possible scenario, after receiving the deletion request, the UDM can delete the second data in the shared path within the storage path indicated by the location information, and can return an indication message to the first NWDAF indicating successful deletion, which may also include a successful deletion identifier. In another possible scenario, if the UDM fails to successfully delete the second data in the shared path, it can return an indication message to the first NWDAF indicating deletion failure, which may also include an error message.

[0217] As an example, the specific deletion process can also be found in [link to documentation]. Figure 5B The flowchart shown is provided. It should be noted that... Figure 5B The flowchart shown illustrates the process using a successful deletion as an example. Specifically, it includes:

[0218] 501B, the first NWDAF determines that the second data, including the registration information, needs to be deleted.

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

[0220] 503B, UDM receives the deletion request and deletes the second data in the shared path.

[0221] Specifically, UDM determines, based on the deletion request, that the second data in the shared path under the storage path indicated by the location information needs to be deleted, and performs the deletion operation.

[0222] 504B, UDM returns an indication message to the first NWDAF to indicate that the deletion was successful.

[0223] Scenario 6: Search Scenario.

[0224] The NF consumer first determines whether it needs to retrieve registration information or data included in the registration information, as described in Scenario 3, and will not be repeated here. After determining this, the NF consumer can send a retrieval request to the UDM. The retrieval request includes the identifier of the data to be retrieved, the shared storage identifier associated with that data, and location information. As an example, the following describes how the NF consumer needs to retrieve the second data included in the registration information. When the NF consumer determines that it needs to retrieve the second data included in the registration information, it can send a retrieval request to the UDM. The retrieval request includes the identifier of the second data, the shared storage identifier associated with the second data, and location information. In one case, the UDM can retrieve the second data from the storage path indicated by the location information according to the retrieval request. The UDM can then return the retrieved second data to the NF consumer, possibly carrying an indication of successful retrieval. In another case, if the UDM does not find the second data in the shared data, it can return an indication of retrieval failure to the NF consumer, and may also carry error information.

[0225] Based on the above scheme, when the NF consumer needs to retrieve the second data stored in the first NWDAF, it will carry the shared storage identifier used by the first NWDAF associated with the second data in the retrieval request sent to the UDM. Therefore, the NF consumer can accurately obtain the second data stored in the first NWDAF, thus improving the retrieval efficiency.

[0226] As an example, the specific search process can be found in [link to relevant documentation]. Figure 5C The flowchart shown is provided. It should be noted that... Figure 5C The flowchart shown illustrates the process using a successful search as an example. Specifically, it includes:

[0227] 501C, NF consumer determines that it needs to obtain the second data, including the registration information.

[0228] 502C, the NF consumer sends a retrieval request to the UDM, which includes the identifier of the second data, the identifier of the shared storage associated with the second data, and location information.

[0229] 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.

[0230] 503C, UDM receives a retrieval request and retrieves second data from the storage path indicated by the location information.

[0231] 504C, UDM returns indication information and second data to the NF consumer to indicate successful retrieval.

[0232] Based on the same concept as the method described above, see [link to relevant documentation]. Figure 6 This application provides an apparatus 600 for implementing user information registration. The apparatus 600 is capable of performing the steps of the above-described method; to avoid repetition, these steps will not be described in detail here. The apparatus 600 includes: a processing unit 601 and a communication unit 602.

[0233] In one possible scenario:

[0234] Processing unit 601 is used to obtain registration information of terminal device;

[0235] The communication unit 602 is used to send a registration request to the UDM; the registration request includes the registration information and location information for identifying the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF.

[0236] In some embodiments, the location information is a Resource Location Identifier (URI).

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

[0238] In some embodiments, after sending a registration request to the UDM, the communication unit 602 is further configured to:

[0239] When it is determined that the registration information has been updated, an 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.

[0240] In some embodiments, after sending a registration request to the UDM, the communication unit 602 is further configured to:

[0241] When it is determined that the registration information needs to be deleted, a deletion request is sent 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.

[0242] In another possible scenario:

[0243] Processing unit 601 is used to obtain registration information of terminal device;

[0244] Communication unit 602 is used to send a registration request to UDM; the registration request includes the registration information and location information for identifying the storage path of the registration information in UDM; 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.

[0245] In some embodiments, the location information is a Resource Location Identifier (URI).

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

[0247] In some embodiments, after sending a registration request to the UDM, the communication unit 602 is further configured to:

[0248] When it is determined that the second data has been 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, 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.

[0249] In some embodiments, after sending a registration request to the UDM, the communication unit 602 is further configured to:

[0250] When it is determined that the second data needs to be deleted, a deletion request is sent 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, and the deletion request is used to instruct the UDM to delete the second data in the storage path indicated by the location information.

[0251] In another possible scenario:

[0252] The communication unit 602 is configured to receive a registration request sent from the NWDAF; the registration request includes registration information of the terminal device and location information for identifying the storage path of the registration information in the device, the location information including the identifier of the NWDAF;

[0253] The processing unit 601 is used to store the registration information in the storage path indicated by the location information.

[0254] In some embodiments, the location information is a Resource Location Identifier (URI).

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

[0256] In some embodiments, after the processing unit 601 stores the registration information into the storage path indicated by the location information,

[0257] The communication unit 602 is further configured to receive an update request from the NWDAF; the update request includes the updated registration information and the location information;

[0258] 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 according to the update request.

[0259] In some embodiments, after the processing unit 601 stores the registration information into the storage path indicated by the location information,

[0260] The communication unit 602 is further configured to receive a deletion request from the NWDAF; the deletion request includes the location information.

[0261] The processing unit 601 is further configured to delete the registration information in the storage path indicated by the location information according to the deletion request.

[0262] In some embodiments, after the processing unit 601 stores the registration information into the storage path indicated by the location information,

[0263] The communication unit 602 is further configured to receive a retrieval request from a network element consumer; the retrieval request includes the identifier of the first data and the location information;

[0264] The processing unit 601 is further configured to send the first data in the storage path indicated by the positioning information to the network element consumer.

[0265] In another possible scenario:

[0266] Communication unit 602 is configured to receive a registration request from a first NWDAF; the registration request includes registration information of a terminal device and location information for identifying the storage path of the registration information in the device; the registration information is obtained by the NWDAF during the process of the terminal device registering to the core network; 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; the first NWDAF is any one of at least one NWDAF serving the terminal device;

[0267] The processing unit 601 is used to store the second data into the storage path indicated by the location information.

[0268] In some embodiments, the location information is a Resource Location Identifier (URI).

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

[0270] In some embodiments, after the processing unit 601 stores the second data into the storage path indicated by the location information,

[0271] The communication unit 602 is further configured to receive an update request from the first NWDAF; the update request includes updated second data, a shared storage identifier associated with the second data, and the location information;

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

[0273] In some embodiments, after the processing unit 601 stores the second data into the storage path indicated by the location information,

[0274] The communication unit 602 is further 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;

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

[0276] In some embodiments, after the processing unit 601 stores the second data into the storage path indicated by the location information,

[0277] The communication unit 602 is further configured to receive a retrieval request from a network element consumer; the retrieval request includes the identifier of the second data, the shared storage identifier associated with the second data, and the location information;

[0278] The processing unit 601 is further configured to send the second data in the storage path indicated by the positioning information to the network element consumer.

[0279] This application embodiment also provides another user information registration device 700, see [link to documentation]. Figure 7 As shown, it includes:

[0280] Communication interface 701, memory 702, and processor 703;

[0281] The registration device 700 communicates with other devices through the communication interface 701, such as sending and receiving messages; the memory 702 is used to store program instructions; and the processor 703 is used to call the program instructions stored in the memory 702 and execute any of the methods proposed in the above embodiments according to the obtained program.

[0282] In this embodiment, the specific connection medium between the communication interface 701, the memory 702 and the processor 703 is not limited, such as a bus. A bus can be divided into an address bus, a data bus, a control bus, etc.

[0283] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0284] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory can also be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0285] This application also provides a computer-readable storage medium including program code. When the program code is run on a computer, the program code is used to cause the computer to perform the steps of the method provided in the above-described embodiments of this application.

[0286] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0287] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0288] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0289] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for registering user information, characterized in that, include: The Network Data Analysis Function (NWDAF) obtains the registration information of terminal devices; The NWDAF sends a registration request to the Unified Data Management Function (UDM); the registration request includes the registration information and location information used to identify the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF; the location information is a Resource Location Identifier (URI).

2. The method as described in claim 1, characterized in that, The location information also includes an event analysis identifier, which is used to indicate the first service performed by the NWDAF for the terminal device. The registration information is generated when the NWDAF provides the first service to the terminal device.

3. The method as described in claim 1 or 2, characterized in that, After the NWDAF sends a registration request to the UDM, the method further includes: When the NWDAF determines that the registration information has been updated, it sends an update request to the UDM. The update request includes the updated registration information and the location information. 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.

4. The method as described in claim 1 or 2, characterized in that, After the NWDAF sends a registration request to the UDM, the method further includes: When the NWDAF determines that the registration information needs to be deleted, it 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.

5. A method for registering user information, characterized in that, include: The UDM receives a registration request from the NWDAF; the registration request includes registration information of the terminal device and location information for identifying the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF; the location information is a Resource Location Identifier (URI); The UDM stores the registration information in the storage path indicated by the location information.

6. The method as described in claim 5, characterized in that, The location information also includes an event analysis identifier, which is used to indicate the first service performed by the NWDAF for the terminal device. The registration information is generated when the NWDAF provides the first service to the terminal device.

7. The method as described in claim 5 or 6, characterized in that, After the UDM stores the registration information in the storage path indicated by the location information, the method further includes: The UDM receives a retrieval request from a network element consumer; the retrieval request includes the identifier of the first data included in the registration information and the location information; The UDM sends the first data in the storage path indicated by the location information to the network element consumer.

8. A method for registering user information, characterized in that, include: The first NWDAF obtains the registration information of the terminal device; The first NWDAF sends a registration request to the UDM; the registration request includes the registration information and location information for identifying the 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; the first NWDAF is any one of at least one NWDAF serving the terminal device; the location information is a resource location identifier (URI).

9. The method as described in claim 8, characterized in that, The registration information also includes third data, which is not associated with the shared storage identifier, to indicate that the third data is stored in the storage path indicated by the location information.

10. A method for registering user information, characterized in that, include: The UDM receives a registration request from the first NWDAF; the registration request includes registration information of the terminal device and location information for identifying the storage path of the registration information in the UDM; the registration information is obtained by the NWDAF during the process of the terminal device registering to the core network; The registration information includes second data, which 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 serving the terminal device. The UDM stores the second data in the storage path indicated by the location information; the location information is a resource location identifier (URI).

11. The method as described in claim 10, characterized in that, The registration information also includes third data, which is not associated with the shared storage identifier, to indicate that the third data is stored in the storage path indicated by the location information.

12. A user information registration device, characterized in that, Applied to NWDAF, including: The processing unit is used to obtain the registration information of the terminal device; A communication unit is used to send a registration request to a UDM; the registration request includes the registration information and location information for identifying the storage path of the registration information in the UDM, the location information including the identifier of the NWDAF; the location information is a resource location identifier (URI).

13. A user information registration device, characterized in that, include: A communication unit is configured to receive a registration request sent from an NWDAF; the registration request includes registration information of a terminal device and location information for identifying the storage path of the registration information in the device, the location information including the identifier of the NWDAF; the location information is a Resource Location Identifier (URI). The processing unit is used to store the registration information in the storage path indicated by the location information.

14. A user information registration device, characterized in that, Applied to the first NWDAF, including: The processing unit is used to obtain the registration information of the terminal device; A communication unit is used to send a registration request to a UDM; the registration request includes the registration information and location information for identifying the 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; the location information is a resource location identifier (URI).

15. A user information registration device, characterized in that, include: A communication unit for receiving registration requests from the first NWDAF; The registration request includes registration information of the terminal device and location information for identifying the storage path of the registration information in the device; the registration information is obtained by the NWDAF during the process of the terminal device registering to the core network; 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; the first NWDAF is any one of at least one NWDAF serving the terminal device; the location information is a resource location identifier (URI). A processing unit is configured to store the second data into the storage path indicated by the location information.

16. A user information registration device, characterized in that, include: Memory and processor; Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the method described in any one of claims 1 to 7 according to the obtained program.

17. A user information registration device, characterized in that, include: Memory and processor; Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the method according to any one of claims 8 to 11.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 11.

Images