A method, apparatus and system for data manipulation

Abstract

The application discloses a method, device and system for data operation, to improve the database capability of UDR. The method comprises: an NF sends a data operation request to a UDR through a set API, the API being an interface specially designed for accessing a set storage domain in the UDR; the set storage domain being capable of storing data in other formats except the UDR specification protocol format; and the NF receiving a response message returned by the UDR through the API, the response message being generated by the UDR after completing corresponding operation on the target data in the set storage domain according to the data operation request. According to the method, the NF can store data in a non-standard protocol format into the UDR through a set API, and the NF can read or modify the data in a non-standard protocol format stored in the UDR through a set API, thereby providing the database capability of the UDR.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus and system for data operation. Background Technology

[0002] According to the 3GPP protocol, during data exchange between network functions (NFs) and the unified data repository (UDR), each NF can only access the protocol-defined data in the UDR. The metadata and index data of various service data defined by the protocol in the UDR need to be negotiated between the UDR and the NF during the service deployment phase and upgraded together during the delivery and deployment phase. Service data mainly refers to the business data accessed by database service users. Metadata mainly refers to data used by database service users to describe the user's data structure, typically referring to the database service user's definition of business data tables, including the table's field composition, field types, and data table partitioning methods. Index data consists of access indexes created by the database service user for business data tables to improve the access performance and reliability of the business data tables.

[0003] However, each equipment vendor's implementation of NFs will have its own independent business data, and this business data in non-standard protocols may require the deployment of their own databases. Existing UDRs cannot provide flexible and universal business data operation capabilities. Summary of the Invention

[0004] This application provides a method, apparatus, and system for data manipulation to improve the database capabilities of a UDR.

[0005] Firstly, this application provides a method for data manipulation, the method comprising:

[0006] The Functional Network Element (NF) sends a data operation request to the Unified Data Repository (UDR) through a designated Application Programming Interface (API). The data operation request is used to request read, write, or modify operations on target data in a designated storage domain within the UDR. The API is an interface specifically designed for accessing the designated storage domain in the UDR. The designated storage domain can store data in formats other than those specified in the UDR protocol. The NF receives a response message returned by the UDR through the API. The response message is generated by the UDR after performing the corresponding operation on the target data in the designated storage domain according to the data operation request.

[0007] Based on the above scheme, in this embodiment of the application, the NF can use a set API to manage its own business-related data in the UDR. For example, the NF can use the set API to store its own non-standard protocol format data in the UDR, and the NF can use the set API to read or modify the non-standard protocol format data stored in the UDR, thus providing the database capability of the UDR.

[0008] As one possible implementation, before the NF sends a data operation request to the UDR through the set API, the NF sends a creation request to the UDR according to the API. The creation request is used to create a business data model corresponding to the target data in the UDR. The NF receives a response message after the UDR completes the creation of the business data model according to the creation request.

[0009] Based on the above scheme, in this embodiment of the application, NF can add new data types to UDR through the set API, thereby dynamically managing its own business-related metadata and index data in UDR, and updating the data tables and fields of UDR through the set API.

[0010] As one possible implementation method, when the type of the business data model to be created is a business data table, the creation request includes the table name, field names, and field types of the business data table to be created; when the type of the business data model to be created is a business data table index, the creation request includes the index name, index field names, and index types of the business data table index to be created.

[0011] Based on the above scheme, this application provides two types of business data model creation methods. For example, when the type of business data model to be created is a business data table, the creation request includes the table name, field name, and field type of the business data table to be created, so that the UDR creates the business data table according to the creation request. As another example, when the type of business data model to be created is a business data table index, the creation request includes the index name, index field name, and index type of the business data table index to be created, so that the UDR creates the business data table index according to the creation request.

[0012] As one possible implementation method, the NF determines the type of the business data model corresponding to the target data; the NF determines the API corresponding to the target data according to the correspondence between the type of the business data model and the API; the NF sends a data operation request to the UDR through the API corresponding to the target data.

[0013] Based on the above solution, this application embodiment provides a method for setting the API, for example, the set API is determined according to the correspondence between business data model and API.

[0014] Secondly, this application provides a data manipulation method, the method comprising:

[0015] The Unified Data Repository (UDR) receives data operation requests from Functional Network Elements (NFs) through a designated Application Programming Interface (API). These requests request reading or modifying of target data in a designated storage domain within the UDR. The API is an interface specifically designed for accessing the designated storage domain within the UDR. This designated storage domain can store data in formats other than those specified in the UDR's protocol. After performing the corresponding operation on the target data in the designated storage domain according to the data operation request, the UDR sends a response message back to the NF via the API.

[0016] Based on the above solution, in this embodiment of the application, when the NF adds a new data type, it can use a set API. It can dynamically manage its own business-related metadata and index data in the UDR through the set API, update the data tables and fields of the UDR, without relying on UDR development, without requiring the UDR to provide metadata definitions, and the UDR can be upgraded without upgrades, which reduces the operator's demand customization of UDR and network element upgrade costs.

[0017] As one possible implementation, before the UDR receives a data operation request sent by the NF through a set API, the UDR receives a creation request sent by the NF through a set API. The creation request is used to create a business data model corresponding to the target data in the UDR. The UDR creates the business data model on the set storage domain according to the creation request.

[0018] Based on the above scheme, in this embodiment of the application, NF can add new data types to UDR through the set API, thereby dynamically managing its own business-related metadata and index data in UDR, and updating the data tables and fields of UDR through the set API.

[0019] As one possible implementation method, when the type of the business data model to be created is a business data table, the creation request includes the table name, field names, and field types of the business data table to be created; when the type of the business data model to be created is a business data table index, the creation request includes the index name, index field names, and index types of the business data table index to be created.

[0020] Based on the above scheme, this application provides two types of business data model creation methods. For example, when the type of business data model to be created is a business data table, the creation request includes the table name, field name, and field type of the business data table to be created, so that the UDR creates the business data table according to the creation request. As another example, when the type of business data model to be created is a business data table index, the creation request includes the index name, index field name, and index type of the business data table index to be created, so that the UDR creates the business data table index according to the creation request.

[0021] Thirdly, embodiments of this application provide a data manipulation apparatus, which may be an NF (Network Functions) or a chip for NF. The apparatus has any method for implementing any possible implementation of the first or second aspect described above. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0022] Fourthly, embodiments of this application provide a data manipulation apparatus, including a processor and a memory; the memory is used to store computer execution instructions, and when the apparatus is running, the processor executes the computer execution instructions stored in the memory to cause the apparatus to perform any method in any possible implementation of the first or second aspect described above.

[0023] Fifthly, embodiments of this application also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause a processor to perform any method of any possible implementation of the first or second aspect described above.

[0024] Sixthly, embodiments of this application also provide a computer program product, which includes a computer program that, when executed, causes a processor to perform any method in any possible implementation of the first or second aspect described above.

[0025] In a seventh aspect, embodiments of this application also provide a chip system, including a processor and a memory. The memory is used to store a computer program; the processor is used to call and run the computer program from the memory, causing a device equipped with the chip system to perform any of the methods in any possible implementation of the first or second aspect described above. Attached Figure Description

[0026] Figure 1 A schematic diagram of a data operation system provided in this application;

[0027] Figure 2A schematic diagram of the data model for the first type of data operation provided in this application;

[0028] Figure 3 A flowchart illustrating a data manipulation method provided in this application;

[0029] Figure 4 A flowchart illustrating the process of creating a business data table provided in this application;

[0030] Figure 5 A flowchart illustrating the process of deleting a business data table provided in this application;

[0031] Figure 6 A flowchart illustrating the process of creating a business data table for the modifications provided in this application;

[0032] Figure 7 A flowchart illustrating the process of creating a business data table index provided in this application;

[0033] Figure 8 A schematic diagram of a data manipulation device provided in this application;

[0034] Figure 9 A schematic diagram of another data manipulation apparatus provided in this application. Detailed Implementation

[0035] To provide a clearer and more complete description of the technical solution of this application, the embodiments of this application will be described below in conjunction with the accompanying drawings.

[0036] like Figure 1 As shown, the data operating system of this application embodiment mainly includes at least one network function (NF) 100 and a unified data repository (UDR) 110. In this application embodiment, the data operating system can flexibly read or modify data in non-standard protocol formats between the NF and the UDR.

[0037] The NF can be a Network Exposure Function (NEF) network element, a Policy Control Function (PCF) network element, a Unified Data Management (UDM) network element, or a Network Repository Function (NRF) network element.

[0038] The data stored in the UDR typically consists of three parts: business data, metadata, and index data. Business data primarily refers to the business data accessed by database service users. Metadata mainly refers to data used by database service users to describe the user's data structure, typically the definition of business data tables by the database service user, including the table's field composition, field types, and data table partitioning methods. Index data consists of access indexes created by the database service user for the business data tables to improve the access performance and reliability of the data tables.

[0039] Furthermore, the communication system described in this application embodiment can be used in the fifth-generation (5G) network architecture. Of course, it can also be used in future network architectures, such as the sixth-generation (6G) network architecture, etc. This application does not limit it.

[0040] The data manipulation method provided in this application can be applied to any communication transmission scenario. For example, it can be used in Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WIMAX), 5th Generation (5G), or New Radio (NR), or applied to future communication systems or other similar communication systems.

[0041] It should be noted that the term "network element" in the embodiments of this application can also be referred to as an entity, device, apparatus, or module, etc., and this application does not specifically limit it. Furthermore, in this application, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, NEF element is abbreviated as NEF. In this case, "NEF network element" should be understood as NEF network element or NEF entity. The following omits descriptions of the same or similar situations. It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, or by multiple devices, or it can be a functional module within a device. This application embodiment does not specifically limit this. Network elements with the same or similar functions can be jointly configured.

[0042] It should be understood that the network architecture described above in this application is merely an example of a network architecture described from the perspective of a service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0043] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. It should be understood that... Figure 1 This is a simplified diagram for ease of understanding only. Other devices (network elements) may also be included in this network architecture. Figure 1 It was not drawn in the middle.

[0044] The following explanations will further clarify some of the terms used in the embodiments of this application to facilitate understanding.

[0045] 1) Policy control network elements include user subscription data management functions, policy control functions, charging policy control functions, and quality of service (QoS) control. In 4G communication systems, the policy control network element can be the policy control and charging function (PCRF). In 5G communication systems, the policy control network element can be the policy control function (PCF).

[0046] 2) The unified data management network element is responsible for managing the subscription information of terminal devices. In 4G communication systems, the unified data management network element can belong to the home subscriber server (HSS). In 5G communication systems, the unified data management network element can be the unified data management (UDM).

[0047] 3) Network capability open elements are mainly used to open up the capabilities of the communication system to third parties, application service functions, etc., and to transmit information between third parties, application servers, and the communication system. In 4G communication systems, network capability open elements can be service capability exposure functions (SCEF). In 5G communication systems, network capability open elements can be network exposure functions (NEF).

[0048] In addition, the terms "system" and "network" in the embodiments of this application can be used interchangeably. "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0049] Unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects. Furthermore, the terms "comprising" and "having" in the embodiments, claims, and drawings of this application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules and may also include steps or modules not listed.

[0050] To address the current issue that UDRs cannot provide flexible and universal business data operation capabilities, this application provides a flexible and open application programming interface (API) for data management between NFs and UDR network elements. This allows NFs to dynamically create their own business data tables in the UDR and dynamically maintain their own business data tables and indexes in the UDR.

[0051] Furthermore, in the data manipulation method provided in this application embodiment, the main applications are as follows: Figure 2 The data model is shown below. The UDR provides the NF with a defined API, which is an interface specifically designed to access a defined storage domain within the UDR. This allows the NF to dynamically create its own business data tables within the UDR and dynamically maintain its relevant business data tables and indexes within the UDR, based on the API provided by the UDR.

[0052] Specifically, such as Figure 3 As shown in the figure, the steps of a data manipulation method provided in this application embodiment are as follows:

[0053] S300 and NF send data operation requests to UDR through a set API. The data operation requests are used to request read, write or modify operations on target data in a set storage domain in UDR. The API is an interface designed specifically for accessing the set storage domain in UDR. The set storage domain can store data in formats other than the UDR specification protocol format.

[0054] In this embodiment of the application, before the NF sends a data operation request to the UDR through the set API, the NF needs to create a business data model corresponding to the target data in the UDR in advance through the preset API, so that the NF can perform data addition, deletion, modification or query operations based on the business data model.

[0055] Specifically, before the NF sends a data operation request to the UDR through the set API, the NF sends a creation request to the UDR according to the API. The creation request is used to create a business data model corresponding to the target data in the UDR. The NF receives a response message after the UDR completes the creation of the business data model according to the creation request.

[0056] Furthermore, this application provides various types of business data models, which can be structured data or unstructured data, and are not limited to the following:

[0057] Data tables, metadata, indexes, and table fields.

[0058] For example, when the type of business data model to be created is a business data table, the creation request may include the table name, field names, and field types of the business data table to be created.

[0059] When the type of business data model to be created is a business data table index, the creation request may include the index name, index field name, and index type of the business data table index to be created.

[0060] S301 and UDR receive data operation requests sent by NF through the configured API.

[0061] S302, the UDR performs the corresponding operation on the target data in the set storage domain according to the data operation request.

[0062] In this embodiment of the application, the UDR can determine the target data based on the information contained in the data operation request in order to perform the operation content on the target operation.

[0063] In one optional embodiment of this application, the data operation request may include the data table name, field name, and field type corresponding to the target data, as well as the operation content to be performed on the target data. The operation content includes adding target data, deleting, modifying, or querying the target data.

[0064] This allows the UDR to determine the location of the target data based on the data table ID, field ID, field type, etc. in the data operation request, and to perform relevant operations on the target data.

[0065] S303, The UDR sends a response message to the NF through the API.

[0066] S304. The NF receives the response message returned by the UDR through the API.

[0067] Furthermore, in one optional approach of this application embodiment, there are multiple configured APIs.

[0068] The NF described in this application embodiment can determine the API used for data operations with the UDR in various ways, and is not limited to the following:

[0069] Method 1: Determine the API for data operations based on the correspondence between the type of business data model and the API.

[0070] In this embodiment of the application, the NF can first determine the type of business data model to be created, and then determine the API used to create the business data model according to the correspondence between the type of business data model and the API.

[0071] Alternatively, the NF can first determine the type of business data model corresponding to the target data, and then, based on the correspondence between the type of business data model and the API, determine the API used to perform data operations on the target data.

[0072] For example, in the scenario of determination method 1, the API interfaces in this application embodiment are not limited to the following:

[0073] APIs for adding business data tables to UDR in NF and APIs for adding business data table indexes to UDR in NF.

[0074] Method 2: Determine the API to perform the data operation based on the correspondence between the data operation type and the API.

[0075] In this embodiment of the application, the NF can first determine the type of data operation to be performed on the target data, including data operation types such as add, delete, modify or query, and then determine the API used to perform data operations on the target data according to the correspondence between the data operation type and the API.

[0076] For example, in the scenario of determination method 2, the API interfaces in this application embodiment are not limited to the following:

[0077] APIs for adding business data in UDR using NF, deleting business data tables in UDR using NF, modifying business data in UDR using NF, and modifying business data table indexes in UDR using NF, etc.

[0078] Method 3: Determine the API for data operations based on the correspondence between the group where the NF is located and the API.

[0079] In this embodiment, multiple NFs can be grouped, and NFs in the same group correspond to the same API. That is, NFs in the same group can manage their own data in the UDR through the same API.

[0080] By providing an open and flexible data operation interface to the UDR through the embodiments of this application, the UDR is endowed with network database capabilities. Each NF network element does not need to have its own independent service database, but only needs to provide the NF's service logic processing capabilities, which effectively improves the UDR's service data operation capabilities.

[0081] It should be noted that the creation request described above in the embodiments of this application can also be regarded as a type of data operation request, and can be uniformly represented by data operation request.

[0082] The data manipulation methods provided in the embodiments of this application will be described in detail below based on different application scenarios.

[0083] Scenario 1: NF adds an API to the business data table provided by UDR to create a business data table.

[0084] like Figure 4 As shown, the process for creating a business data table using the data manipulation method provided in this application embodiment is as follows:

[0085] S400 and NF send data operation requests to UDR through the API used to add business data tables. The data operation requests are used to create business data tables.

[0086] In one optional embodiment of this application, the NF sends a PUT request to the UDR through the API, instructing the creation of a data table, and the resource identifier specifies the data-mode.

[0087] In one optional embodiment of this application, the data operation request includes the table name, field names, and field types of the business data table to be created.

[0088] S401, UDR receives the data operation request through the API.

[0089] S402, UDR creates a business data table based on the data operation request.

[0090] For example, the UDR creates a business data table in its own data tablespace according to the table name, field name, and field type specified in the data operation request, and records it in the metadata.

[0091] After S403 and UDR successfully create the business data table, they send a successful creation response to NF.

[0092] It should be noted that the scenario described in this application embodiment supports the creation of multiple business data tables at once.

[0093] Scenario 2: NF deletes the business data table using the business data table deletion API provided by UDR.

[0094] like Figure 5 As shown, the process of deleting a business data table using the data manipulation method provided in this application embodiment is as follows:

[0095] S500 and NF send a data operation request to UDR through an API used to delete business data tables. The data operation request is used to delete business data tables.

[0096] In one optional embodiment of this application, the NF sends a DELETE request to the UDR through the API, indicating that the data table should be deleted, and the resource identifier specifies the data-mode.

[0097] In one optional embodiment of this application, the data operation request includes the name of the business data table to be deleted. When the business data table is deleted, its related metadata and indexes are also deleted.

[0098] S501, UDR receives the data operation request through the API.

[0099] S502, UDR deletes the business data table according to the data operation request.

[0100] For example, after receiving a deletion request, the UDR will directly delete the table data, metadata, and index data of the specified business data table.

[0101] After S503 and UDR successfully delete the business data table, they send a successful deletion response to NF.

[0102] It should be noted that the second scenario described in this application embodiment supports deleting multiple business data tables at once.

[0103] Scenario 3: NF modifies the business data table through the business data table modification API provided by UDR.

[0104] like Figure 6 As shown, the process for modifying a business data table using the data manipulation method provided in this application embodiment is as follows:

[0105] S600 and NF send data operation requests to UDR through APIs used to modify business data tables. The data operation requests are used to modify business data tables.

[0106] In one optional embodiment of this application, the NF sends a PATCH request to the UDR through the API, indicating that the data table structure should be modified, and the resource identifier specifies the data-mode.

[0107] In one optional embodiment of this application, the data operation request includes the table name, field name, and field type of the business data table to be modified.

[0108] S601, UDR receives the data operation request through the API.

[0109] S602, UDR modifies the business data table according to the data operation request.

[0110] For example, after receiving a modification request, the UDR will modify the content of the specified business data table.

[0111] After S603 and UDR successfully modify the business data table, they send a successful modification response to NF.

[0112] It should be noted that the scenario described in this application embodiment supports modifying multiple business data tables at once.

[0113] Scenario 4: NF adds indexes to business data tables using the API provided by UDR for adding business data table indexes.

[0114] like Figure 7 As shown, the process for creating a business data table index using the data manipulation method provided in this application embodiment is as follows:

[0115] S700 and NF send data operation requests to UDR through the API used to add indexes to business data tables. The data operation requests are used to create indexes for business data tables.

[0116] In one optional embodiment of this application, the NF sends a PUT request to the UDR through the API, instructing the creation of an index for the data table, with the resource identifier specifying the data-index.

[0117] In one optional embodiment of this application, the data operation request includes the index name, index field name, and index type of the business data table to be created.

[0118] S701, UDR receives the data operation request through the API.

[0119] S702, UDR creates an index for the business data table based on the data operation request.

[0120] For example, the UDR creates an index for the business data table in its own data tablespace based on the index name, index field name, and index type of the table specified in the data operation request, and records it in the metadata.

[0121] After S703 and UDR successfully create the index of the business data table, they send a successful creation response to NF.

[0122] It should be noted that the fourth scenario described in this application embodiment supports index changes for multiple tables in a single operation.

[0123] Furthermore, in this embodiment of the application, NF can also perform operations such as adding, deleting, and modifying indexes of the business data table through the corresponding APIs provided by UDR. The specific content is similar to the types of operations performed by NF through the corresponding APIs provided by UDR on the business data table. For simplicity, NF can also perform operations such as adding, deleting, and modifying indexes of the business data table through the corresponding APIs provided by UDR. Please refer to the description below. Figure 7 The content, combined with the above Figures 4 to 6 The details of this will not be elaborated here.

[0124] The solution described in this application allows operators to dynamically change metadata description interfaces when adding new data types to NFs during 5G service development. This interface enables dynamic management of service-related metadata and index data within the UDR, updating UDR data tables and fields without relying on UDR development or requiring UDR metadata definitions. This eliminates the need for UDR upgrades and shortens the time to launch new services for operators, reducing the costs associated with customizing UDR requirements and upgrading network elements.

[0125] From the above description of the present application, it can be understood that the devices described above, in order to achieve the above functions, include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0126] Based on the above embodiments, such as Figure 8 As shown, this application discloses a data operation apparatus, which includes a processor 800, a memory 801, and a communication interface 802.

[0127] The processor 800 is responsible for managing the bus architecture and general processing, while the memory 801 stores the data used by the processor 800 during operation. The communication interface 802 is used for data communication between the processor 800 and the memory 801.

[0128] The processor 800 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 800 may further include a hardware chip. This hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The memory 1201 may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0129] The processor 800, the memory 801, and the communication interface 802 are interconnected. Optionally, the processor 800, the memory 801, and the communication interface 802 can be interconnected via a bus 803; the bus 803 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0130] Specifically, the processor 800 is used to read and execute the program in the memory 801:

[0131] When the data operation device is NF, the processor 800 is used to read the program in the memory 801 and execute it as follows: Figure 3 The method flow for NF execution described in S300 to S303 is shown; or the execution is as follows: Figure 4 The method flow for NF execution shown in S400 to S403; execution as follows Figure 5The method flow for NF execution shown in S500 to S503; execution as follows Figure 6 The method flow for NF execution shown in S600 to S603; execution as follows Figure 7 The method flow for NF execution shown in S700 to S703.

[0132] When the data operation device is a UDR, the processor 800 is used to read the program in the memory 801 and execute it as follows: Figure 3 The method flow for executing the UDR as shown in S300 to S304; or executing as follows Figure 4 The method flow for executing the UDR described in S400 to S403 is shown; execution is as follows: Figure 5 The method flow for executing the UDR described in S500 to S503 is shown; execution is as follows: Figure 6 The method flow for executing the UDR described in S600 to S603 is shown; execution is as follows: Figure 7 The method flow for executing the UDR shown in S700 to S703 is illustrated.

[0133] like Figure 9 As shown, the present invention provides a data manipulation apparatus, which includes at least one processing unit 900, at least one storage unit 901, and at least one communication unit 902, wherein the communication unit 902 is used to receive and send signaling and / or data under the control of the processing unit 900, and the storage unit 901 stores program code.

[0134] In one optional embodiment of this application, when the device is NF, when the program code is executed by the processing unit 900, the processing unit 900 performs the following process:

[0135] Identify the target data object that needs to be manipulated in the data repository UDR, the data object including a data table and / or a data table index; determine the API of the target data object based on the correspondence between the data object and the application programming interface (API); send a data operation request to the UDR through the API, the data operation request instructing the UDR to perform add, delete, or modify operations on the target data object; receive a response message from the UDR after it has completed the operation on the database according to the data operation request.

[0136] As one possible implementation, the processing unit 900 is further configured to:

[0137] According to the API, a creation request is sent to the UDR, which is used to create a business data model corresponding to the target data in the UDR; and a response message is received after the UDR completes the creation of the business data model according to the creation request.

[0138] As one possible implementation method, when the type of the business data model to be created is a business data table, the creation request includes the table name, field names, and field types of the business data table to be created; when the type of the business data model to be created is a business data table index, the creation request includes the index name, index field names, and index types of the business data table index to be created.

[0139] As one possible implementation, the processing unit 900 is specifically used for:

[0140] Determine the type of business data model corresponding to the target data; determine the API corresponding to the target data based on the correspondence between the type of business data model and the API; send a data operation request to the UDR through the API corresponding to the target data.

[0141] In another optional embodiment of this application, when the device is a UDR, when the program code is executed by the processing unit 900, the processing unit 900 performs the following process:

[0142] The system receives data operation requests from functional network elements (NFs) via a defined application programming interface (API). These requests request reading or modifying target data in a designated storage domain within the UDR. The API is specifically designed for accessing the designated storage domain in the UDR. This designated storage domain can store data in formats other than those specified in the UDR protocol. After performing the corresponding operation on the target data in the designated storage domain according to the data operation request, the system sends a response message back to the NF via the API.

[0143] As one possible implementation, the processing unit 900 is further configured to:

[0144] The system receives a creation request from the NF via a set API. The creation request is used to create a business data model corresponding to the target data in the UDR. The system then creates the business data model on the set storage domain according to the creation request.

[0145] The above Figure 9 The functions of the communication unit 902 and the processing unit 900 shown can be executed by the processor 800 running the program in the memory 801, or by the processor 800 alone.

[0146] Figure 9The data manipulation apparatus shown can be a NEF network element or a chip in the NEF network element in the above embodiments; or it can be a PCF network element or a chip in the PCF network element in the above embodiments; or it can be a UDM network element or a chip in the UDM network element in the above embodiments; or it can be an NRF network element or a chip in the NRF network element in the above embodiments.

[0147] In some possible implementations, various aspects of the data manipulation methods provided in the embodiments of the present invention can also be implemented as a program product comprising program code that, when run on a computer device, causes the computer device to perform the steps of the data manipulation methods according to various exemplary embodiments of the present invention as described in this specification.

[0148] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0149] According to embodiments of the present invention, a program product for performing data operations may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a server device. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an information transmission device or apparatus.

[0150] A readable signal medium may include data signals propagated in baseband or as part of a cell, carrying readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with a periodic network operating system, apparatus, or device.

[0151] The program code contained on the readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wired, optical fiber, RF, or any suitable combination thereof.

[0152] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network—including a local area network (LAN) or a wide area network (WAN)—or it can be connected to an external computing device.

[0153] The data manipulation method provided in this application also provides a computing device readable storage medium, meaning that the content is not lost after power failure. This storage medium stores software programs, including program code. When the program code runs on a computing device, the software program, when read and executed by one or more processors, can implement any of the data manipulation schemes described in the embodiments of this application.

[0154] The present application has been described above with reference to block diagrams and / or flowcharts illustrating methods, apparatus (systems), and / or computer program products according to embodiments of the present application. It should be understood that a block of a block diagram and / or flowchart, as well as combinations of blocks of block diagrams and / or flowcharts, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, and / or other programmable data processing means to produce a machine, such that the instructions, executable via the computer processor and / or other programmable data processing means, create methods for implementing the functions / actions specified in the blocks of the block diagrams and / or flowcharts.

[0155] Accordingly, this application can also be implemented using hardware and / or software (including firmware, resident software, microcode, etc.). Furthermore, this application can take the form of a computer program product on a computer-usable or computer-readable storage medium, having computer-usable or computer-readable program code implemented in the medium for use by or in conjunction with an instruction execution system. In the context of this application, a computer-usable or computer-readable medium can be any medium that can contain, store, communicate, transmit, or deliver a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0156] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A method for data manipulation, characterized in that, include: Functional network elements send data operation requests to the unified data repository through a designated application programming interface (API). These requests request read, write, or modify operations on target data in a designated storage domain within the unified data repository. The API is specifically designed for accessing the designated storage domain in the unified data repository and is used to maintain the data information within that domain. The data information includes some or all of the following: target data, business data tables, or indexes. The designated storage domain can store data in formats other than the unified data repository's specified protocol format. The functional network element receives a response message returned by the unified data repository through the application programming interface. The response message is generated by the unified data repository after it completes the corresponding operation on the target data in the set storage domain according to the data operation request. Before the functional network element sends a data operation request to the unified data repository through the configured application programming interface, the following steps are also included: The functional network element determines the application interface for performing data operations based on the correspondence between the type of business data model and the application interface. or, The functional network element determines the application interface to perform data operations based on the correspondence between the functional network element's group and the application interface.

2. The method as described in claim 1, characterized in that, Before the functional network element sends a data operation request to the unified data repository through the set application programming interface, it also includes: The functional network element sends a creation request to the unified data repository according to the application interface. The creation request is used to create a business data model corresponding to the target data in the unified data repository. The functional network element receives a response message from the unified data repository after the business data model has been created according to the creation request.

3. The method as described in claim 2, characterized in that, When the type of business data model to be created is a business data table, the creation request includes the table name, field names, and field types of the business data table to be created; When the type of business data model to be created is a business data table index, the creation request includes the index name, index field name, and index type of the business data table index to be created.

4. The method according to any one of claims 1 to 3, characterized in that, The functional network element determines the application programming interface (API) for data operations based on the correspondence between the type of business data model and the application programming interface (API), including: The functional network element determines the type of the business data model corresponding to the target data; The functional network element determines the application programming interface (API) corresponding to the target data based on the correspondence between the type of business data model and the application programming interface (API).

5. A method for data manipulation, characterized in that, include: The unified data repository receives data operation requests from functional network elements through a designated application programming interface (API). These requests request read or modify operations on target data in a designated storage domain within the unified data repository. The API is specifically designed for accessing the designated storage domain within the unified data repository and is used to maintain the data information within that domain. The data information includes some or all of the following: target data, business data tables, or indexes. The designated storage domain can store data in formats other than the unified data repository's specified protocol format. After the unified data repository completes the corresponding operation on the target data in the designated storage domain according to the data operation request, it sends a response message to the functional network element through the application programming interface. Wherein, the application programming interface (API) is determined by the functional network element based on the correspondence between the type of the business data model and the API; or, the API is determined by the functional network element based on the correspondence between the group to which the functional network element belongs and the API.

6. The method as described in claim 5, characterized in that, Before the unified data repository receives data operation requests from functional network elements through the defined application programming interface, it also includes: The unified data repository receives creation requests sent by functional network elements through a set application programming interface. The creation requests are used to create a business data model corresponding to the target data in the unified data repository. The unified data repository creates the business data model on the designated storage domain according to the creation request.

7. The method as described in claim 6, characterized in that, When the type of business data model to be created is a business data table, the creation request includes the table name, field names, and field types of the business data table to be created; When the type of business data model to be created is a business data table index, the creation request includes the index name, index field name, and index type of the business data table index to be created.

8. A data manipulation apparatus, characterized in that, include: One or more processors and memory; The memory stores computer program instructions; The one or more processors are configured to read program instructions from the memory and execute them: A data operation request is sent to the unified data repository through a defined application programming interface (API). The data operation request is used to request read, write, or modify operations on target data in a defined storage domain within the unified data repository. The API is an interface specifically designed for accessing the defined storage domain in the unified data repository and is used to maintain the data information in the defined storage domain. The data information includes some or all of the following: target data, business data tables, or indexes. The defined storage domain can store data in formats other than the unified data repository specification protocol format. Receive a response message returned by the unified data repository through the application interface. The response message is generated by the unified data repository after it has completed the corresponding operation on the target data in the set storage domain according to the data operation request. Before the processor sends a data operation request to the unified data repository through the configured application programming interface, it is also used to: Based on the correspondence between the type of business data model and the application programming interface (API), determine the API for performing data operations; or, Based on the correspondence between the functional network element's group and the application interface, the application interface for performing data operations is determined.

9. The apparatus as claimed in claim 8, characterized in that, The processor is also used for: According to the application interface, a creation request is sent to the unified data repository, and the creation request is used to create a business data model corresponding to the target data in the unified data repository; Receive the response message from the unified data repository after it has completed the creation of the business data model according to the creation request.

10. The apparatus as claimed in claim 9, characterized in that, When the type of business data model to be created is a business data table, the creation request includes the table name, field names, and field types of the business data table to be created; When the type of business data model to be created is a business data table index, the creation request includes the index name, index field name, and index type of the business data table index to be created.

11. The apparatus according to any one of claims 8 to 10, characterized in that, When the processor determines the application interface for data operations based on the correspondence between the type of business data model and the application interface, it is specifically used for: Determine the type of business data model corresponding to the target data; Based on the correspondence between the type of business data model and the application interface, determine the application interface corresponding to the target data.

12. A data manipulation apparatus, characterized in that, include: One or more processors and memory; The memory stores computer program instructions; The one or more processors are configured to read program instructions from the memory and execute them: The system receives data operation requests from functional network elements via a designated application programming interface (API). These requests are used to request reading or modification of target data in a designated storage domain within the unified data repository. The API is specifically designed for accessing the designated storage domain in the unified data repository and is used to maintain data information within that domain. The data information includes some or all of the following: target data, business data tables, or indexes. The designated storage domain can store data in formats other than the unified data repository specification protocol format. After performing the corresponding operation on the target data in the designated storage domain according to the data operation request, a response message is sent back to the functional network element through the application programming interface. Wherein, the application programming interface (API) is determined by the processor based on the correspondence between the type of the service data model and the API; or, the API is determined by the processor based on the correspondence between the group to which the functional network element is located and the API.

13. The apparatus as claimed in claim 12, characterized in that, The processor is also used for: The application programming interface is used to receive a creation request sent by a functional network element. The creation request is used to create a business data model corresponding to the target data in a unified data repository. The business data model is created on the designated storage domain according to the creation request.

14. The apparatus as claimed in claim 13, characterized in that, When the type of business data model to be created is a business data table, the creation request includes the table name, field names, and field types of the business data table to be created; When the type of business data model to be created is a business data table index, the creation request includes the index name, index field name, and index type of the business data table index to be created.

15. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on a data-operating apparatus, cause the data-operating apparatus to perform the method as described in any one of claims 1 to 4; or to perform the method as described in any one of claims 5 to 7.

16. A computer program product, characterized in that, Includes a computer program that, when the computer program is executed, causes a processor to perform the method as described in any one of claims 1 to 4; or to perform the method as described in any one of claims 5 to 7.

Images