CN110049503B

CN110049503B - Method and equipment for acquiring data

Info

Publication number: CN110049503B
Application number: CN201810036365.8A
Authority: CN
Inventors: 陈旭; 刘超; 孙滔
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2018-01-15
Filing date: 2018-01-15
Publication date: 2022-07-15
Anticipated expiration: 2038-01-15
Also published as: CN110049503A

Abstract

The invention discloses a method and equipment for acquiring data, which are used for solving the problem of higher overhead when an NF entity carries out addressing in the process of acquiring data in the prior art. In the embodiment of the invention, an NF entity sends a service request carrying a request number segment data indication mark to a unified data management functional entity; and after the NF entity receives the service response of the user number segment carrying the unified data management function entity returned by the unified data management function entity, establishing the corresponding relation between the user number segment of the unified data management function entity and the address of the unified data management function entity. The NF entity sends the service request and carries the indication mark of the request number segment, the unified data management function entity returns the service response and returns the user number segment, and establishes the corresponding relation between the user number segment and the unified data management function entity address.

Description

Method and equipment for acquiring data

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a method and a device for acquiring data.

Background

The 5G core Network adopts a Service architecture, interfaces among NF (Network Function) entities adopt SBI (Service Based Interface Service Interface), and communication mechanisms of Service call are adopted among the NF entities. The NF entity performs service registration with the NRF entity, ranking all services provided by itself. When the NF entity performs signaling addressing, a service discovery process needs to be considered, and the NF entity may find a specific service that needs to be invoked through a service discovery process provided by an NRF (Network Function discovery Function) entity.

When a specific service to be called is found in the service discovery process provided by the NRF entity, each user needs to inquire the NRF entity when addressing, and the expense of inquiring the NRF entity is related to the number of the network-wide users and the number of the service users, so that the service discovery process has larger expense.

In summary, in the prior art, in the process of acquiring data, when the NF entity addresses the unified data management function entity for each user, the NRF entity needs to be queried, which is relatively high in overhead.

Disclosure of Invention

The invention provides a method and equipment for acquiring data, which are used for solving the problems that in the process of acquiring data in the prior art, when an NF (NF) entity addresses a unified data management function entity for each user, an NRF (non return filter) entity needs to be inquired, and the cost is high.

In a first aspect, an embodiment of the present invention provides a method for acquiring data, where the method includes:

the NF entity sends a service request carrying a request number segment data indication mark to the unified data management functional entity;

and after the NF entity receives the service response of the user number segment carrying the unified data management function entity returned by the unified data management function entity, establishing the corresponding relation between the user number segment of the unified data management function entity and the address of the unified data management function entity.

In a second aspect, an embodiment of the present invention provides a method for acquiring data, where the method includes:

a unified data management functional entity receives a service request which is sent by an NF entity and contains a user code number;

if the service request containing the user number carries the request number segment data indication identification, the unified data management function entity returns the user number segment managed by the unified data management function entity to the NF entity in the service response, so that the NF entity updates the corresponding relation between the user number segment and the unified data management function entity address, and the NF entity determines the unified data management function entity address corresponding to the user number according to the corresponding relation before sending the service request to the unified data management function entity.

In a third aspect, an embodiment of the present invention provides a method for acquiring data, where the method includes:

the NF entity sends a service discovery request of a unified data management function entity to the NRF entity, and after receiving a redirection node address and a home region number section returned by the NRF entity, establishes a first corresponding relation between the redirection node address and the home region number section; and

and the NF entity sends a service request of a unified data management function entity to the redirection node, and establishes a second corresponding relation of the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node.

In a fourth aspect, an embodiment of the present invention provides a method for acquiring data, where the method includes:

the NRF entity receives a service discovery request of a unified data management function entity sent by the NF entity;

the NRF entity returns the home zone number segment and the corresponding redirection node address to the NF entity so that the NF entity can establish a first corresponding relation between the redirection node address and the home zone number segment and send a unified data management function entity service request to the redirection node corresponding to the redirection node address according to the first corresponding relation.

In a fifth aspect, an embodiment of the present invention provides a method for acquiring data, where the method includes:

a redirection node receives a service request of a unified data management function entity sent by an NF entity;

and the redirection node returns the user number segment and the corresponding unified data management function entity address to the NF entity so that the NF entity establishes a second corresponding relation between the user number segment and the unified data management function entity address.

In a sixth aspect, an embodiment of the present invention provides an apparatus for acquiring data, where the apparatus includes: a processor and a transceiver:

the processor is used for sending a service request carrying a request number segment data indication mark to the unified data management functional entity;

and after receiving a service response of the user number segment carrying the unified data management functional entity returned by the unified data management functional entity, establishing a corresponding relation between the user number segment of the unified data management functional entity and the address of the unified data management functional entity.

In a seventh aspect, an embodiment of the present invention provides an apparatus for acquiring data, where the apparatus includes: a processor and a transceiver:

the processor is used for receiving a service request which is sent by the NF entity and contains a user code number; if the service request containing the user number carries the request number segment data indication identification, returning the user number segment managed by the unified data management function entity to the NF entity in the service response, and enabling the NF entity to update the corresponding relation between the user number segment and the unified data management function entity address, so that the NF entity determines the unified data management function entity address corresponding to the user number according to the corresponding relation before sending the service request to the unified data management function entity subsequently.

In an eighth aspect, an embodiment of the present invention provides an apparatus for acquiring data, where the apparatus includes: the data processing system comprises at least one processing unit and at least one storage unit, wherein the storage unit stores program codes, and when the program codes are executed by the processing unit, the processing unit executes the steps of any one method of the NF entity in acquiring data or the steps of the method of the unified data management function entity in acquiring data.

In a ninth aspect, an embodiment of the present invention provides a storage medium readable by a computing device, including program code, when the program code runs on the computing device, for causing the computing device to execute the steps of any one of the methods of the NF entity in acquiring data or the methods of the unified data management function entity in acquiring data.

In a tenth aspect, an embodiment of the present invention provides an apparatus for acquiring data, where the apparatus includes: a processor and a transceiver:

the processor is used for sending a service discovery request of a unified data management function entity to an NRF entity and establishing a first corresponding relation between a redirection node address and an attribution area number segment after receiving the redirection node address and the attribution area number segment returned by the NRF entity; and sending a service request of a unified data management function entity to the redirection node, and establishing a second corresponding relation of the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node.

In an eleventh aspect, an embodiment of the present invention provides an apparatus for acquiring data, where the apparatus includes: a processor and a transceiver:

the processor is used for receiving a unified data management function entity service discovery request sent by the NF entity; and returning the home region number segment and the corresponding redirection node address to the NF entity so that the NF entity establishes a first corresponding relation between the redirection node address and the home region number segment, and sending a unified data management function entity service request to a redirection node corresponding to the redirection node address according to the first corresponding relation.

In a twelfth aspect, an embodiment of the present invention provides an apparatus for acquiring data, where the apparatus includes: a processor and a transceiver:

the processor is used for receiving a service request of a unified data management function entity sent by the NF entity; and returning the user number segment and the corresponding unified data management function entity address to the NF entity so that the NF entity establishes a second corresponding relation between the user number segment and the unified data management function entity address.

In a thirteenth aspect, an embodiment of the present invention provides an apparatus for acquiring data, where the apparatus includes: at least one processing unit and at least one memory unit, wherein said memory unit has stored program code which, when executed by said processing unit, causes said processing unit to perform the steps of any of said methods of said NF entity in acquiring data or any of said steps of said NRF entity in acquiring data or any of said steps of said redirection node in acquiring data.

In a fourteenth aspect, embodiments of the present invention provide a computing device-readable storage medium comprising program code for causing a computing device to perform the steps of causing the processing unit to perform any of the methods of the NF entity in acquiring data or any of the steps of the NRF entity in acquiring data or any of the steps of the redirecting node in acquiring data, when the program code is run on the computing device.

In the embodiment of the invention, an NF entity sends a service request carrying a request number segment data indication mark to a unified data management functional entity; and after the NF entity receives the service response of the user number segment carrying the unified data management function entity returned by the unified data management function entity, establishing the corresponding relation between the user number segment of the unified data management function entity and the address of the unified data management function entity. The NF entity sends a service request to the uniform data management function entity firstly, and carries a request number section indicating identification in the service request, so that the uniform data management function entity returns a service response after receiving the service request carrying the request user indicating identification, and simultaneously returns the user number section of the uniform data management function entity, and at the moment, the corresponding relation between the user number section and the uniform data management function entity address is locally established.

Meanwhile, in the embodiment of the invention, the NF entity sends a service discovery request of a unified data management functional entity to the NRF entity, and after receiving the address of the redirection node and the number segment of the home zone returned by the NRF entity, establishes a first corresponding relation between the address of the redirection node and the number segment of the home zone; and the NF entity sends a service request of a unified data management function entity to the redirection node, and establishes a second corresponding relation of the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node. When the NF entity sends service request to the unified data management function entity, firstly sending a unified data management function entity service discovery request to the NRF entity, inquiring the address of the redirection node, determining the address of the redirection node and the home zone number segment corresponding to the address of the redirection node, then storing the corresponding relation of the address of the redirection node and the home zone number segment, sending a unified data management function entity service request to the redirection node corresponding to the address of the redirection node, obtaining the address of the unified data management function entity, receiving the user number segment corresponding to the address of the unified data management function entity while receiving the address of the unified data management function entity, storing the corresponding relation of the address of the unified data management function entity and the user number segment, and finally sending the service request to the obtained address of the unified data management function entity, in the prior art, when the NF entity sends the service request to the unified data management function entity, the NRF entity needs to inquire to obtain the address of the unified data management function entity, and the quantity of information stored by the NRF entity is large, so that the cost is high.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required to be used in the description of the embodiments will be briefly introduced below, and it is apparent that the drawings in the description below are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings may be obtained according to the drawings without inventive labor.

FIG. 1 is a diagram illustrating a first system for acquiring data according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of a first apparatus for acquiring data according to an embodiment of the present invention;

FIG. 3 is a diagram illustrating a second apparatus for acquiring data according to an embodiment of the present invention;

FIG. 4 is a diagram illustrating a third apparatus for acquiring data according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating a fourth apparatus for acquiring data according to an embodiment of the present invention;

FIG. 6 is a flowchart of a first method for obtaining data according to the embodiment of the present invention;

FIG. 7 is a flowchart of a second method for obtaining data according to the embodiment of the present invention;

FIG. 8 is a flowchart of an overall method for obtaining data according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of another system for acquiring data according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a fifth apparatus for acquiring data according to an embodiment of the present invention;

Fig. 11 is a schematic structural diagram of a sixth apparatus for acquiring data according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a seventh apparatus for acquiring data according to the embodiment of the present invention;

fig. 13 is a schematic structural diagram of an eighth apparatus for acquiring data according to the embodiment of the present invention;

fig. 14 is a schematic structural diagram of a ninth apparatus for acquiring data according to the embodiment of the present invention;

fig. 15 is a schematic structural diagram of a tenth apparatus for acquiring data according to an embodiment of the present invention;

FIG. 16 is a flowchart of a third method for obtaining data according to the present invention;

FIG. 17 is a flowchart illustrating a fourth method for acquiring data according to an embodiment of the present invention;

FIG. 18 is a flow chart of a fifth method for obtaining data according to an embodiment of the present invention;

FIG. 19 is a flow chart of another overall method for obtaining data according to an embodiment of the invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

As shown in fig. 1, a system for acquiring data according to an embodiment of the present invention includes:

the NF entity 100 is used for sending a service request carrying a request number segment data indication mark to the unified data management functional entity; and after receiving a service response of the user number segment carrying the unified data management functional entity returned by the unified data management functional entity, establishing a corresponding relation between the user number segment of the unified data management functional entity and the address of the unified data management functional entity.

The unified data management functional entity 101 is used for receiving a service request which is sent by the NF entity and contains a user code number; if the service request containing the user number carries the request number segment data indication identification, returning the user number segment managed by the unified data management function entity to the NF entity in the service response, so that the NF entity updates the corresponding relation between the user number segment and the unified data management function entity address, and the NF entity determines the unified data management function entity address corresponding to the user number according to the corresponding relation.

Wherein, the unified data management function entity includes but is not limited to the following part or all:

UDM (Unified Data Management), UDR (Unified Data Repository).

Specifically, one unified data management function entity address corresponds to at least one user code number, that is, one unified data management function entity address corresponds to one user number segment, for example, the user number segment is 13920001000-13920001100, and the unified data management function entity address corresponding to the user number segment is unified data management function entity 1.

The unified data management function entity address comprises a unified data management function entity ID and/or a unified data management function entity IP.

Wherein the service request includes, but is not limited to, some or all of the following:

user context management service, user subscription data management service, user authentication service, event subscription service and unified data management service.

Specifically, when the NF entity sends a service request to the unified data management function entity, part or all of the service request is sent, and when one or more of the service requests are sent to the unified data management function entity, a request number segment data identifier is carried in the service request.

Wherein, the request number segment indicator is mainly used for: when the unified data management function entity receives the service request, the user number section managed by the unified data management function entity is determined to be returned according to the user number section indication identification, so that the NF entity establishes the corresponding relation between the user number section and the unified data management function entity address according to the user number section managed by the NF entity returned by the unified data management function entity, and updates the corresponding relation between the locally stored user number section and the unified data management function entity address.

In implementation, when the NF entity sends a service request to the address of the unified data management function entity, the NF entity carries the request number segment indicator, the unified data management function entity returns the user number segment managed by the NF entity to the NF entity according to the user number segment data in the request number segment indicator, the NF entity updates the corresponding relationship between the local user number segment and the address of the unified data management function entity in response to receiving the user number segment returned by the unified data management function entity, that is, the received user number segment returned by the unified data management function entity and the corresponding address of the unified data management function entity are stored locally, so that when the NF entity sends a service request to the unified data management function entity in the subsequent period, the NF entity queries the local area and can directly obtain the address of the unified data management function entity corresponding to the user number when receiving the user number in the user number segment, and the address of the unified data management function entity is not required to be obtained through the query of the NRF entity, so that the expense is reduced.

The service response mainly comprises a response made according to one or more service requests, and when the request service is determined to carry a request number segment indication identifier, the service response also carries a user number segment of a unified data management function entity; and if the request service does not carry the request number segment indication identification in the service response, making a corresponding service response aiming at the service request.

In the invention, when the NF entity sends a service request to the unified data management function entity, whether a corresponding relation between a user number segment and a unified data management function entity address exists locally is firstly inquired, after the corresponding relation between the user number and the unified data management function entity address exists is determined, the address of the unified data management function entity is determined according to the corresponding relation, and then the service request is sent to the unified data management function entity corresponding to the unified data management function entity address; and if the corresponding relation between the user code number and the unified data management function entity address does not exist in the corresponding relation, the NF entity sends a query request to the NRF entity, and sends a service request to the unified data management function entity corresponding to the unified data management function entity address according to the unified data management function entity address returned by the NRF entity.

Optionally, before the NF entity sends a service request carrying a request number segment data indication identifier to a unified data management function entity, the NF entity does not have a unified data management function entity address corresponding to a user number in the correspondence, and sends a request for querying the unified data management function entity address corresponding to the user number to an NRF entity; the NF entity receives a unified data management function entity address returned by the NRF entity;

and when the NF entity sends a service request carrying a request number segment data indication mark to the unified data management function entity, the NF entity sends the service request carrying the request number segment data indication mark to the unified data management function entity according to the address of the unified data management function entity.

Specifically, before sending a service request to the unified data management function entity, the NF entity queries whether a corresponding relationship between the user number segment and a unified data management function entity address is locally stored, and after determining that there is no unified data management function entity address corresponding to a received user number in the corresponding relationship, sends a request for querying the unified data management function entity address to the NRF entity, where the sent request carries the user number; after the NRF entity receives an inquiry request containing a user code number, inquiring the corresponding relation between a user number segment stored in the NRF entity and the address of the unified data management function entity according to the user code number, determining the address of the unified data management function entity corresponding to the user code number, and returning the address to the NF entity; and after receiving the unified data management function entity address returned by the NRF entity, the NF entity sends the service request to a unified data management function entity corresponding to the unified data management function entity address, wherein the service request carries a request number segment data indication identifier.

In the implementation, after determining the corresponding relation between the user number segment without the user number corresponding to the local user number and the unified data management function entity address, sending a request for inquiring the address of the unified data management function entity corresponding to the user code number to the NRF entity, the NRF entity determines the unified data management function entity address corresponding to the user code number according to the corresponding relation between the user number segment stored in the NRF entity and the unified data management function entity address, and then sends the determined unified data management function entity address corresponding to the user code number to the NF entity, after the NF entity receives the address of the unified data management function entity returned by the NRF entity, and sending the service request to a unified data management function entity corresponding to the unified data management function entity address, so as to ensure that the NF entity can smoothly send the service request containing the user code number to the unified data management function entity.

Optionally, the NF entity has a user number segment corresponding to the user number and a unified data management function entity address in the corresponding relationship, and sends the service request including the user number to the unified data management function entity of the unified data management function entity address corresponding to the user number.

Specifically, before sending a service request to the unified data management function entity, the NF entity queries whether a corresponding relationship between the user number segment and a unified data management function entity address is stored locally, and after determining that the corresponding relationship has the unified data management function entity address corresponding to the user number, directly sends the service request to the unified data management function entity corresponding to the unified data management function entity address.

In implementation, when the NF entity sends a service request to the address of the unified data management function entity, the query local may directly obtain the address of the unified data management function entity corresponding to the user number, and send the service request to the entity of the unified data management function entity corresponding to the address of the unified data management function entity, without querying through the NRF entity to obtain the address of the unified data management function entity, which reduces overhead.

Optionally, when the NF entity sends the service request including the user code number to the unified data management function entity of the unified data management function entity address corresponding to the user code number, the NF entity does not carry the request number segment data indication identifier in the service request sent to the unified data management function entity of the unified data management function entity address corresponding to the user code number.

Specifically, when the NF entity determines that the unified data management function entity address is a locally stored unified data management function entity address, and when the NF entity sends a service request to a unified data management function entity corresponding to the unified data management function entity address, the service request does not carry a request number segment data indication identifier.

In implementation, when a unified data management function entity address corresponding to a user number is determined to be in the local, a service request is directly sent to the unified data management function entity address, and the service request does not carry a request number segment data indication identifier, so that when the unified data management function entity returns a response, a corresponding service response is returned only for the service request, and a user number segment does not need to be carried, thereby reducing the overhead and saving transmission resources.

As shown in fig. 2, an embodiment of the present invention provides an apparatus for acquiring data, which includes a processor 200 and a transceiver 201;

the processor 200 is configured to send a service request carrying a request number segment data indication identifier to a unified data management function entity; and after receiving a service response of the user number segment carrying the unified data management functional entity returned by the unified data management functional entity, establishing a corresponding relation between the user number segment of the unified data management functional entity and the address of the unified data management functional entity.

Optionally, the processor 200 is further configured to:

after the corresponding relation has no user number segment corresponding to the user number and no unified data management function entity address, sending a request for inquiring the unified data management function entity address corresponding to the user number to the NRF entity; receiving a unified data management function entity address returned by the NRF entity;

the processor 200 is specifically configured to:

and sending a service request carrying a request number segment data indication mark to a unified data management function entity according to the unified data management function entity address.

Optionally, there are a user number segment corresponding to the user number and a unified data management function entity address in the corresponding relationship, and the service request including the user number is sent to the unified data management function entity of the unified data management function entity address corresponding to the user number.

Optionally, the processor 200 is specifically configured to:

and the service request sent to the unified data management function entity of the unified data management function entity address corresponding to the user code number does not carry the request number segment data indication identification.

Optionally, the service request includes part or all of the following:

As shown in fig. 3, an apparatus for acquiring data according to an embodiment of the present invention includes: at least one processing unit 300 and at least one storage unit 301, wherein the storage unit 301 stores program code that, when executed by the processing unit 300, causes the processing unit 300 to perform the steps of any of the methods of the NF entity in acquiring data.

As shown in fig. 4, an apparatus for acquiring data according to an embodiment of the present invention includes: processor 400 and transceiver 401:

the processor 400 is configured to receive a service request including a user code number sent by an NF entity; and if the service request containing the user number carries the request number segment data indication identification, returning the user number segment managed by the unified data management function entity to the NF entity in the service response, so that the NF entity updates the corresponding relation between the user number segment and the unified data management function entity address, and the NF entity determines the unified data management function entity address corresponding to the user number according to the corresponding relation before sending the service request to the unified data management function entity subsequently.

As shown in fig. 5, an apparatus for acquiring data according to an embodiment of the present invention includes: at least one processing unit 500 and at least one storage unit 501, wherein the storage unit 501 stores program code, which when executed by the processing unit 500, causes the processing unit 500 to perform the steps of the method when the unified data management function entity acquires data.

In some possible embodiments, various aspects of acquiring data provided by the embodiments of the present invention may also be implemented in the form of a program product, which includes program code for causing a computer device to perform the steps in the method for processing a terminal path according to various exemplary embodiments of the present invention described in this specification, when the program code runs on the computer device.

The program product may employ any combination of one or more readable media. The 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 electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A program product for data forwarding control according to an embodiment of the present invention may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a server device. However, the program product of the present invention is not limited in this regard and, in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an information delivery, apparatus, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with a periodic network action system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to external computing devices.

The embodiment of the invention also provides a readable storage medium of the computing equipment aiming at the method for acquiring data by the NF entity, namely, the content is not lost after the power is cut off. The storage medium stores therein a software program comprising program code which, when executed on a computing device, when read and executed by one or more processors, implements any of the above aspects of embodiments of the present invention when acquiring data.

The embodiment of the invention also provides a readable storage medium of the computing equipment aiming at the method for acquiring the data by the unified data management functional entity, namely, the content is not lost after the power failure. The storage medium stores therein a software program comprising program code which, when executed on a computing device, when read and executed by one or more processors, implements any of the above aspects of the unified data management function entity as an approach for data acquisition in accordance with embodiments of the present invention.

Based on the same inventive concept, the embodiment of the present invention further provides a method for acquiring data, and since the method corresponds to the method for acquiring data in the embodiment of the present invention, and the principle of the method for solving the problem is similar to that of the device, the method can be implemented with reference to the device, and the repeated parts are not described again.

As shown in fig. 6, a method for acquiring data according to an embodiment of the present invention specifically includes the following steps:

step 600, the NF entity sends a service request carrying a request number segment data indication mark to the unified data management functional entity;

601, after the NF entity receives a service response carrying the user number segment of the unified data management function entity returned by the unified data management function entity, establishing a corresponding relationship between the user number segment of the unified data management function entity and the address of the unified data management function entity.

Optionally, before the NF entity sends a service request carrying a request number segment data indication identifier to a unified data management function entity, the NF entity does not have a user number segment corresponding to a user number and a unified data management function entity address in the corresponding relationship, and sends a request for querying a unified data management function entity address corresponding to the user number to an NRF entity; the NF entity receives a unified data management function entity address returned by the NRF entity;

Optionally, the service request includes part or all of the following:

As shown in fig. 7, another method for acquiring data according to an embodiment of the present invention specifically includes the following steps:

step 700, the unified data management functional entity receives a service request containing a user code number, which is sent by an NF entity;

step 701, if the service request including the user number carries a request number segment data indication identifier, the unified data management function entity returns the user number segment managed by the unified data management function entity to the NF entity in a service response, so that the NF entity updates the corresponding relationship between the user number segment and the unified data management function entity address, so that the NF entity determines the unified data management function entity address corresponding to the user number according to the corresponding relationship before sending the service request to the unified data management function entity subsequently.

As shown in fig. 8, the complete method for acquiring data according to the embodiment of the present invention specifically includes the following steps:

step 800, the NF entity needs to access the unified data management function entity and sends a service request of the unified data management function entity containing the user code number A;

step 801, the NF entity queries whether a local user number segment and a unified data management function entity address contain a unified data management function entity address corresponding to the user number a, if the NF entity determines that there is no corresponding relationship between the user number segment where the user number a is located and the unified data management function entity address locally, then step 802 is executed;

step 802, the NF entity sends a request for inquiring the address of the unified data management function entity corresponding to the user code A to an NRF entity;

step 803, the NRF entity returns the address a of the unified data management function entity corresponding to the user code number according to the user code number a;

step 804, the NF entity sends a service request carrying a request number segment data indication identifier to the unified data management function entity a;

step 805, the unified data management functional entity A returns a service response and a managed user number segment;

806, the NF entity locally stores the corresponding relation between the unified data management functional entity A and the corresponding user number segment;

step 807, the NF entity needs to access the unified data management function entity and sends a service request of the unified data management function entity containing the user code number B;

step 808, the NF entity queries whether a unified data management function entity address corresponding to the user code number B exists in the local user number segment and the unified data management function entity address; if the NF entity determines that the unified data management function entity address corresponding to the user number segment where the user number B is located locally exists is a unified data management function entity address A;

step 809, the NF entity sends a service request of the unified data management function entity including the user number B to the unified data management function entity corresponding to the unified data management function entity address a, and the service request does not carry the request number segment indication identifier;

step 810, the address A of the unified data management function entity returns a service response;

step 811, the NF stores a unified data management function entity address a;

step 812, the NF entity needs to access the unified data management function entity and sends a unified data management function entity service request containing the user code number C;

Step 813, the NF entity queries whether a unified data management function entity address corresponding to the user code number C exists in the local user number segment and the unified data management function entity address, if the NF entity determines that there is no corresponding relationship between the user number segment where the user code number C exists and the unified data management function entity address locally, then step 814 is executed;

step 814, the NF entity sends a request for querying the address of the unified data management function entity corresponding to the user code number C to the NRF entity;

step 815, the NRF entity returns the address C of the unified data management function entity corresponding to the user code number according to the user code number C;

step 816, the NF entity sends a service request carrying a request number segment data indication identifier to the unified data management function entity C;

step 817, the unified data management functional entity C returns a service response and the managed user number segment;

step 818, the NF entity locally stores the corresponding relationship between the unified data management function entity C and the corresponding user number segment.

In the embodiment of the present invention, there is another system for acquiring data, which is described in detail below.

Specifically, as shown in fig. 9, another system for acquiring data according to an embodiment of the present invention includes:

The NF entity 900 is used for sending a service discovery request of a unified data management functional entity to the NRF entity and establishing a first corresponding relation between a redirection node address and an attribution area number segment after receiving the redirection node address and the attribution area number segment returned by the NRF entity; and sending a service request of a unified data management function entity to the redirection node, and establishing a second corresponding relation of the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node.

The NRF entity 901 is configured to receive a service discovery request of a unified data management function entity sent by the NF entity; and returning the home zone number segment and the corresponding redirection node address to the NF entity so that the NF entity establishes a first corresponding relation between the redirection node address and the home zone number segment and sends a unified data management function entity service request to the redirection node corresponding to the redirection node address according to the first corresponding relation.

The redirection node 902 is configured to receive a service request of a unified data management function entity sent by an NF entity; and returning the user number segment and the corresponding unified data management function entity address to the NF entity so that the NF entity establishes a second corresponding relationship between the user number segment and the unified data management function entity address.

In the embodiment of the invention, an NF entity sends a service discovery request of a unified data management functional entity to an NRF entity, and after receiving a redirection node address and an attribution area number section returned by the NRF entity, establishes a first corresponding relation between the redirection node address and the attribution area number section; and the NF entity sends a service request of a unified data management function entity to the redirection node, and establishes a second corresponding relation of the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node.

When the NF entity sends service request to the unified data management function entity, firstly sending a unified data management function entity service discovery request to the NRF entity, inquiring the address of the redirection node, determining the address of the redirection node and the home zone number segment corresponding to the address of the redirection node, then storing the corresponding relation of the address of the redirection node and the home zone number segment, sending a unified data management function entity service request to the redirection node corresponding to the address of the redirection node, obtaining the address of the unified data management function entity, receiving the user number segment corresponding to the address of the unified data management function entity while receiving the address of the unified data management function entity, storing the corresponding relation of the address of the unified data management function entity and the user number segment, and finally sending the service request to the obtained address of the unified data management function entity, in the prior art, when the NF entity sends the service request to the unified data management function entity, the NRF entity needs to inquire to obtain the address of the unified data management function entity, and the quantity of information stored by the NRF entity is large, so that the cost is high.

Specifically, when the NF entity sends a service discovery request of the unified data management function entity to the NRF entity, the service discovery request of the unified data management function entity is only one of the requests sent by the NF entity to the NRF entity, and any other request that enables the NRF entity to return the first corresponding relationship between the redirection node address and the home domain number segment is applicable to the embodiment of the present invention;

similarly, when the NF entity sends the service request of the unified data management function entity to the unified data management function entity, the service request of the unified data management function entity is only one of the requests sent by the NF entity to the unified data management function entity, and any other request which can enable the unified data management function entity to return the service response is applicable to the embodiment of the present invention.

The NRF entity is configured with a corresponding relation between a home area number segment and a corresponding redirection node address; and the redirection node is configured with the corresponding relation between all the unified data management function entity addresses and the user number segments in the area. In the embodiment of the invention, a redirection node at least comprises a corresponding relation between a unified data management function entity address and a user number segment.

In implementation, before sending a service request of the unified data management function entity to the unified data management function entity, the NF entity firstly queries whether a second corresponding relationship between a user number segment corresponding to a received user number and an address of the unified data management function entity and/or a first corresponding relationship between a number segment of a home area to which the user number belongs and an address of a redirection node exist locally, after the first corresponding relation is determined to exist, the address of the redirection node is determined according to the first corresponding relation, a service request of a unified data management function entity is sent to the redirection node corresponding to the address of the redirection node, after receiving the service request of the unified data management function entity, the redirection node forwards the service request of the unified data management function entity to a unified data management function entity corresponding to the corresponding unified data management function entity address; after the existence of the second corresponding relation is determined, the unified data management function entity address is directly determined according to the second corresponding relation, and a unified data management function entity service request is sent to the unified data management function entity address; after determining that a first corresponding relation and a second corresponding relation corresponding to a local existing user code number exist, sending the service request of the unified data management function entity to the unified data management function entity corresponding to the unified data management function entity address determined according to the second corresponding relation; and when determining that a first corresponding relation and a second corresponding relation corresponding to the user code number do not exist locally, namely the first corresponding relation and the second corresponding relation do not have the user code number, the NF entity sends a unified data management function entity service discovery request to the NRF entity. The following description is made for the above case.

The first condition is as follows: and the first corresponding relation and the second corresponding relation have no user code number.

In implementation, when the NF entity sends a unified data management function entity service discovery request to the NRF entity and sends a unified data management function entity service request to the redirection node, a corresponding introduction is made according to whether the unified data management function entity service discovery request and the unified data management function entity service request specifically include a user code number.

The method I comprises the following steps: the unified data management function entity service discovery request and the unified data management function entity service request both comprise user code numbers.

Optionally, when the NF entity sends a service discovery request of the unified data management function entity to the NRF entity, before the NF entity sends a service request of the unified data management function entity to the unified data management function entity in the subsequent step, if there is no user number segment corresponding to the user number in the first corresponding relationship and the second corresponding relationship, the NF entity sends a service discovery request of the unified data management function entity to the NRF entity.

Specifically, before sending a service request of the unified data management function entity to the unified data management function entity, the NF entity firstly queries whether a unified data management function entity address or a redirection node address corresponding to the user connection number exists locally; when the second corresponding relation of the user number segment and the unified data management function entity address in the local and the first corresponding relation of the redirection node and the home zone number segment are determined to have no user code number, the NF entity sends a unified data management function entity service discovery request to the NRF entity at the moment, and sets the user code number in the first service request, namely, the NF entity places the user code number in the unified data management function entity service discovery request.

Correspondingly, when the NRF entity returns the home region number segment and the corresponding redirection node address to the NF entity, the NRF entity returns the home region number segment to which the user number belongs in the service discovery request of the unified data management function entity and the corresponding redirection node address to the NF entity.

Specifically, the NRF entity receives a service discovery request of a unified data management function entity, which carries the user number, and at this time, the NRF entity queries a home area number segment configured by the NRF entity and a corresponding redirect node address according to the user number, determines the home area number segment to which the user number belongs and the redirect node address, and returns the home area number segment to which the user number belongs and the redirect node address to the NF entity.

Based on the above content, after the NF entity receives the home area number segment to which the user number belongs and the redirect node address returned by the NRF entity, the NF entity sends a unified data management function entity service request to the redirect node corresponding to the redirect node address, and the unified data management function entity service request carries the user number, that is, the NF entity places the user number in the unified data management function entity service request.

Correspondingly, the redirection node receives a unified data management function entity service request sent by the NF entity, and determines that the unified data management function entity service request comprises a user code number; and after the redirection node returns the user number segment to which the user number belongs and the corresponding unified data management function entity address to the NF entity, the redirection node forwards a unified data management function entity service request sent by the NF entity to the unified data management function entity according to the unified data management function entity address corresponding to the user number segment to which the user number belongs.

Specifically, after receiving the service request including the user number, the redirection node queries the configured unified data management function entity address and the user number segment according to the user number, determines the user number segment corresponding to the user number and the corresponding unified data management function entity address, returns the user number segment and the corresponding unified data management function entity address to the NF entity, and forwards the unified data management function entity service request to the unified data management function entity according to the unified data management function entity address determined by the redirection node.

The second method comprises the following steps: the service discovery request of the unified data management functional entity does not comprise a user code number, but the service request of the unified data management functional entity comprises the user code number.

Optionally, when the NF entity sends a service discovery request of the unified data management function entity to the NRF entity, before the NF entity sends a service request of the unified data management function entity to the unified data management function entity in the subsequent step, if there is no user code number in the first corresponding relationship and the second corresponding relationship, the NF entity sends a service discovery request of the unified data management function entity to the NRF entity, and the service discovery request of the unified data management function entity does not include a user code number.

Specifically, before sending a service request of the unified data management function entity to the unified data management function entity, the NF entity firstly queries whether a unified data management function entity address or a redirection node address corresponding to a user code number exists locally; and when the second corresponding relation of the user number segment and the unified data management function entity address in the local and the first corresponding relation of the redirection node and the home region number segment are determined to have no user number, the NF entity sends a unified data management function entity service discovery request to the NRF entity.

Correspondingly, when the NRF entity returns the home area number segment and the corresponding redirection node address to the NF entity, the NRF entity returns all the redirection node addresses and the corresponding home area number segment to the NF entity.

Specifically, because the service discovery request of the unified data management function entity received by the NRF entity does not have a user number, the NRF entity returns all home area number segments configured in the NRF entity and corresponding redirection node addresses to the NF entity according to the service discovery request of the unified data management function entity.

Based on the above content, after receiving the home area number segment to which all the user numbers belong and the redirection node address returned by the NRF entity, the NF entity determines, according to the user number, the redirection node address corresponding to the home area number segment to which the user number belongs, and sends a unified data management function entity service request to the redirection node corresponding to the redirection node address, where the unified data management function entity service request carries the user number, that is, the NF entity places the user number in the unified data management function entity service request.

The third method comprises the following steps: the service discovery request of the unified data management functional entity comprises a user code number, but the service request of the unified data management functional entity does not comprise the user code number.

Optionally, when the NF entity sends a service discovery request of the unified data management function entity to the NRF entity, before the NF entity sends a service request of the unified data management function entity to the unified data management function entity in the subsequent step, if there is no user code number in the first corresponding relationship and the second corresponding relationship, the NF entity sends a service discovery request of the unified data management function entity to the NRF entity, and the service discovery request of the unified data management function entity includes a user code number.

Specifically, before sending a service request of the unified data management function entity to the unified data management function entity, the NF entity firstly queries whether a unified data management function entity address or a redirection node address corresponding to a user code number exists locally; when the second corresponding relation of the user number section and the unified data management function entity address in the local and the first corresponding relation of the redirection node and the attribution area number section are determined to have no user code number, the NF entity sends a unified data management function entity service discovery request to the NRF entity at the moment, and sets a user receiving code number in the unified data management function entity service discovery request, namely, the NF entity places the user code number in the unified data management function entity service discovery request.

Specifically, the NRF entity receives a service discovery request carrying the user number from a unified data management function entity, and at this time, the NRF entity queries a home area number segment configured by the NRF entity and a corresponding redirection node address according to the user number, determines the home area number segment to which the user number belongs and the redirection node address, and returns the home area number segment to which the user number belongs and the redirection node address to the NF entity.

Based on the above content, after receiving the home area number segment to which all the user numbers belong and the redirection node address returned by the NRF entity, the NF entity determines, according to the user number, the redirection node address corresponding to the home area number segment to which the user number belongs, and sends a unified data management function entity service request to the redirection node corresponding to the redirection node address, where the unified data management function entity service request does not have the user number.

Correspondingly, the redirection node receives a unified data management function entity service request sent by the NF entity, the redirection node returns all user number segments configured in the redirection node and second corresponding relations of corresponding unified data management function entity addresses to the NF entity, the NF entity queries all second corresponding relations returned by the redirection node according to the user number, determines the unified data management function entity address corresponding to the user number segment where the user number is located, and the NF entity sends the unified data management function entity service request to the unified data management function entity corresponding to the unified data management function entity address.

The method four comprises the following steps: the unified data management function entity service discovery request does not include a user code number, and the unified data management function entity service request does not include the user code number.

Specifically, because the service discovery request of the unified data management function entity received by the NRF entity does not have a user code number, the NRF entity returns all home area number segments configured in the NRF entity and corresponding redirection node addresses to the NF entity according to the service discovery request of the unified data management function entity.

Based on the above content, after receiving the home area number segment to which all the user numbers belong and the redirection node address returned by the NRF entity, the NF entity determines, according to the user number, the redirection node address corresponding to the home area number segment to which the user number belongs, and sends a unified data management function entity service request to the redirection node corresponding to the redirection node address, where the unified data management function entity service request does not include the user number.

In the implementation, whether a first corresponding relationship and a second corresponding relationship corresponding to a user code number exist in a local category is firstly inquired, after the first corresponding relationship and the second corresponding relationship are determined to have no user code number, inquiry is initiated to the NRF entity, the unified data management functional entity service request is sent according to the inquiry result, and the unified data management functional entity service request can be guaranteed to be smoothly sent to the corresponding unified data management functional entity.

In implementation, the NF entity updates the first corresponding relationship and the second corresponding relationship stored locally according to the first corresponding relationship between the home domain number segment to which the NRF entity returns the user number and the corresponding redirection node address, and the second corresponding relationship between the user number segment to which the user number returned by the redirection node is located and the corresponding unified data management function entity address, that is, the received home domain number segment, the corresponding redirection node address, the user number segment, and the corresponding unified data management function entity address are stored locally, when the NF entity sends a unified data management function entity service request to the unified data management function entity, the local can directly obtain the unified data management function entity address or the redirection node address corresponding to the user number without obtaining the unified data management function entity address through the NRF entity, less overhead is incurred.

And a second condition: the first corresponding relation has a user number but the second corresponding relation has no user number.

Optionally, when the NF entity sends the service request of the unified data management function entity to the redirection node, the NF entity sends the service request of the unified data management function entity to the redirection node according to the redirection node address corresponding to the user code number after the NF entity has the redirection node address corresponding to the user code number in the first corresponding relationship and the second corresponding relationship does not have the address of the unified data management function entity corresponding to the user code number.

Specifically, before requesting a service request of the unified data management function entity from the NF entity, first, whether a unified data management function entity address or a redirection node address corresponding to a user connection number exists locally is queried; the NF entity determines the address of the redirection node corresponding to the number section of the attribution area to which the user number belongs according to the first corresponding relation, and sends a service request of the unified data management function entity to the redirection node corresponding to the address of the redirection node, wherein the service request of the unified data management function entity carries the user number, namely the NF entity places the user number in the service request of the unified data management function entity.

Correspondingly, the service request of the unified data management functional entity comprises a user code number; and after the redirection node returns the user number segment to which the user number belongs and the corresponding unified data management function entity address to the NF entity, the redirection node forwards a unified data management function entity service discovery request sent by the NF entity to the unified data management function entity according to the unified data management function entity address corresponding to the user number segment to which the user number belongs.

Specifically, after receiving the service request of the unified data management function entity sent by the NF entity, determining that the unified data management function entity service request comprises a user number, querying a second corresponding relation between a unified data management function entity address and a user number section configured in a redirection node according to the user number by the redirection node, determining the unified data management function entity address corresponding to the user number section where the user number is positioned, the redirection node returns the user number segment to which the user number belongs and the corresponding unified data management function entity address to the NF entity, and simultaneously, the redirection node forwards a service discovery request of the unified data management function entity sent by the NF entity to the unified data management function entity according to the address of the unified data management function entity corresponding to the user number segment to which the user number belongs.

In the embodiment of the present invention, if the NF entity sends a unified data management function entity service request to the redirection node without including a user code number, the redirection node returns all user number segments configured in the redirection node and a second corresponding relationship of a corresponding unified data management function entity address to the NF entity, and the NF entity queries, in all received second corresponding relationships, a unified data management function entity address corresponding to the user code number according to the user code number, and after determining the unified data management function entity address, sends a unified data management function entity service to the corresponding unified data management function entity.

In implementation, when the NF entity sends a service request of the unified data management function entity to the unified data management function entity, it will first query whether there is a second corresponding relationship between a user number segment where a user number is located and an address of the unified data management function entity, if there is no second corresponding relationship; the NF entity queries whether there is a first corresponding relationship between the home area number segment to which the user number belongs and the redirection node address, the first corresponding relationship exists, the redirection node address is determined according to the first corresponding relationship, a unified data management function entity service request is sent to the redirection node corresponding to the redirection node address, after receiving the unified data management function entity service request, the redirection node forwards the unified data management function entity service request to a unified data management function entity corresponding to the user number, and the NRF entity does not need to be queried to obtain the unified data management function entity address, thereby reducing overhead.

And a third situation: the second corresponding relation has a user code number.

Optionally, after the NF entity has the unified data management function entity address corresponding to the user code number in the second corresponding relationship, a unified data management function entity service request is sent to a unified data management function entity according to the unified data management function entity address.

Specifically, when sending a unified data management function entity service request to the unified data management function entity, the NF entity firstly queries whether there is a second corresponding relationship between a user number segment corresponding to a user number and a unified data management function entity address locally, determines a unified data management function entity address corresponding to the number segment where the user number is located according to the second corresponding relationship after determining that there is the second corresponding relationship corresponding to the user number locally, and sends the unified data management function entity service request to the unified data management function entity corresponding to the unified data management function entity address.

For example, when the user number is 13920001001, the user number segment corresponding to the user number is 13920001000-13920001100, the unified data management function entity address corresponding to the user number segment is the unified data management function entity 10, the unified data management function entity address corresponding to the user number segment 13920001101-13920001200 stored locally is the unified data management function entity 1, the unified data management function entity address corresponding to 13920001300-13920001400 is the unified data management function entity 2, and the unified data management function entity address corresponding to the user number segment 13920001000-13920001100 is the corresponding relationship of the unified data management function entity 10, it is determined that the user number segment 13920001000-13920001100 corresponding to the user number 13920001001 is local, that is, the unified data management function entity address of the user number segment where the user number is located in the second corresponding relationship between the user number segment in local and the unified data management function entity address, at this time, the NF entity determines that the address of the unified data management function entity corresponding to the user number segment 13920001000-13920001100 where the user number is 13920001001 is the unified data management function entity 10, and the NF entity sends a unified data management function entity service request to the unified data management function entity 10.

In implementation, the NF entity firstly queries whether a second corresponding relationship exists between a user number segment where a user number is located and a unified data management function entity address, and if the second corresponding relationship exists, determines the unified data management function entity address corresponding to the user number according to the second corresponding relationship, and then sends a unified data management function entity service request to the unified data management function entity address corresponding to the user number; instead of inquiring the NRF entity to obtain the address of the unified data management function entity corresponding to the user code number, the expense is reduced.

In the embodiment of the present invention, when the service discovery request of the unified data management function entity is sent to the NRF entity and/or the service request of the unified data management function entity is sent to the redirection node, if the service discovery request of the unified data management function entity includes the user code number, all information in the configuration may also be returned during the return.

As shown in fig. 10, an apparatus for acquiring data according to an embodiment of the present invention includes a processor 1000 and a transceiver 1001;

the processor 1000 is configured to send a service discovery request of a unified data management function entity to an NRF entity, and after receiving a redirection node address and a home domain number segment returned by the NRF entity, establish a first correspondence between the redirection node address and the home domain number segment; and sending a service request of a unified data management function entity to the redirection node, and establishing a second corresponding relation of the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node.

Optionally, the processor 1000 is further configured to:

before sending a unified data management function entity service request to a unified data management function entity in the following, if the first corresponding relation and the second corresponding relation have no user code number, sending a unified data management function entity service discovery request containing the user code number to an NRF entity.

Optionally, the processor 1000 is further configured to: and placing the user code number in the service discovery request of the unified data management functional entity.

The processor 1000 is further configured to:

and after the first corresponding relation has the redirection node address corresponding to the user code number and the second corresponding relation has no unified data management function entity address corresponding to the user code number, sending a unified data management function entity service request to the redirection node according to the redirection node address corresponding to the user code number.

Optionally, the processor 1000 is further configured to: and placing the user code number in the service request of the unified data management functional entity.

Optionally, the processor 1000 is further configured to:

and after the second corresponding relation has the unified data management function entity address corresponding to the user code number, sending a unified data management function entity service request to a unified data management function entity according to the unified data management function entity address.

As shown in fig. 11, an apparatus for acquiring data according to an embodiment of the present invention includes: at least one processing unit 1100 and at least one storage unit 1101, wherein the storage unit 1101 stores program code that, when executed by the processing unit 1100, causes the processing unit 1100 to perform the steps of any of the methods of the NF entity in acquiring data.

As shown in fig. 12, an apparatus for acquiring data according to an embodiment of the present invention includes: processor 1200 and transceiver 1201:

the processor 1200 is configured to receive a service discovery request of a unified data management function entity sent by an NF entity; and returning the home zone number segment and the corresponding redirection node address to the NF entity so that the NF entity establishes a first corresponding relation between the redirection node address and the home zone number segment and sends a unified data management function entity service request to the redirection node corresponding to the redirection node address according to the first corresponding relation.

Optionally, the processor 1200 is specifically configured to:

all redirection node addresses and corresponding home region number segments are returned to the NF entity; or if the unified data management functional entity service discovery request comprises the user number, returning the number section of the home area to which the user number belongs and the corresponding redirection node address in the unified data management functional entity service discovery request to the NF entity.

As shown in fig. 13, an apparatus for acquiring data according to an embodiment of the present invention includes: at least one processing unit 1300 and at least one storage unit 1301, wherein the storage unit 1301 stores a program code, which when executed by the processing unit 1300, causes the processing unit 1300 to execute the steps of any of the methods of the NRF entity in acquiring data.

As shown in fig. 14, an apparatus for acquiring data according to an embodiment of the present invention includes: processor 1400 and transceiver 1401:

the processor 1400 is configured to receive a unified data management function entity service request sent by an NF entity; and returning the user number segment and the corresponding unified data management function entity address to the NF entity so that the NF entity establishes a second corresponding relationship between the user number segment and the unified data management function entity address.

Optionally, the service request of the unified data management function entity includes a user code number;

the processor 1400 is further configured to:

and forwarding a service discovery request of the unified data management function entity sent by the NF entity to the unified data management function entity according to the address of the unified data management function entity corresponding to the user number segment to which the user number belongs.

As shown in fig. 15, an apparatus for acquiring data according to an embodiment of the present invention includes: at least one processing unit 1500 and at least one storage unit 1501, wherein the storage unit 1501 stores program code that, when executed by the processing unit 1500, causes the processing unit 1500 to perform the steps of the method of the redirection node in acquiring data.

The program product may employ any combination of one or more readable media. The 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 electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The embodiment of the invention also provides a storage medium readable by computing equipment aiming at a method for acquiring data by an NRF entity, namely, the content is not lost after power failure. The storage medium stores therein a software program comprising program code which, when executed on a computing device, when read and executed by one or more processors, implements the aspects of any of the above NRF entities of embodiments of the present invention in obtaining data.

The embodiment of the invention also provides a computer readable storage medium for the method for acquiring data by the redirection node, namely, the content is not lost after power failure. The storage medium stores therein a software program comprising program code which, when executed on a computing device, when read and executed by one or more processors, implements any of the above aspects of embodiments of the present invention in obtaining data.

As shown in fig. 16, a method for acquiring data according to an embodiment of the present invention specifically includes the following steps:

1600, the NF entity judges whether a first corresponding relation between the local user number segment and the redirection node address has a redirection node address corresponding to the user number;

step 1601, after determining that the first corresponding relationship has a redirection node address corresponding to the user code number, the NF entity sends a service request, which includes the user code number and corresponds to the user code number, to a redirection node of the redirection node address corresponding to the user code number;

step 1602, the NF entity sends the service request including the user code number to the unified data management function entity of the unified data management function entity address returned by the redirection node.

Optionally, before the NF entity determines whether there is a redirection node address corresponding to the user number in the first corresponding relationship between the local user number segment and the redirection node address, the NF entity determines that there is no unified data management function entity address corresponding to the user number in the second corresponding relationship between the local user number segment and the unified data management function entity address.

Optionally, when the NF entity sends a service request including a user code number corresponding to the user code number to a redirection node of a redirection node address corresponding to the user code number, the NF entity places an update identifier in the service request including the user code number and sends the update identifier to the redirection node of the redirection node address;

And after the NF entity sends a service request which corresponds to the user code and contains the user code to a redirection node of a redirection node address corresponding to the user code, the NF entity updates the local second corresponding relation according to the unified data management function entity address and the user number section returned by the redirection node.

Optionally, if there is a unified data management function entity address corresponding to the user code number in the second mapping relationship, the NF entity sends the service request including the user code number to the unified data management function entity of the unified data management function entity address corresponding to the user code number.

Optionally, after the NF entity determines whether there is a redirection node address corresponding to the user number in the first corresponding relationship between the local user number segment and the redirection node address, if there is no redirection node address corresponding to the user number in the first corresponding relationship, the NF entity sends a request for querying a unified data management function entity address corresponding to the user number to the NRF entity;

the NF entity determines a redirection node corresponding to the redirection node address according to a first corresponding relation between the redirection node address returned by the NRF entity and the user number segment;

The NF entity sends a service request containing a user code number to a redirection node corresponding to the redirection node address;

and the NF entity sends the service request containing the user code number to a unified data management function entity of the unified data management function entity address returned by the redirection node.

Optionally, when the NF entity sends a service request including a user code number corresponding to the user code number to a redirection node of a redirection node address corresponding to the user code number, the NF entity places an update identifier in the service request including the user code number and sends the update identifier to the NRF entity;

and after the NF entity sends a service request which corresponds to the user number and contains the user number to the NRF entity, the NF entity updates the local first corresponding relation according to the redirection node address and the user number section returned by the NRF entity.

As shown in fig. 17, a method for acquiring data according to an embodiment of the present invention specifically includes the following steps:

1700, an NRF entity receives a request for inquiring the address of a unified data management function entity, which is sent by an NF entity;

step 1701, the NRF entity returns the first corresponding relation between the redirection node address and the user number section to the NF entity, so that the NF entity sends the service request containing the user number to the redirection node corresponding to the redirection node address according to the first corresponding relation.

Optionally, when the NRF entity returns the first correspondence between the redirect node address and the user number segment to the NF entity, the NRF entity returns the first correspondence between all redirect node addresses and user number segments to the NF entity; or

And the NRF entity returns the user number segment to which the user number in the request belongs and the corresponding redirection node address to the NF entity in the first corresponding relation.

As shown in fig. 18, a method for acquiring data according to an embodiment of the present invention specifically includes the following steps:

1800, the redirection node receives a service request which is sent by an NF entity and contains a user code number;

step 1801, the redirection node determines a unified data management function entity address corresponding to the user number segment to which the user number belongs according to a second corresponding relationship between the unified data management function entity address and the user number segment;

step 1802, the redirecting node returns the determined unified data management function entity address to the NF entity, so that the NF entity sends a service request including a user code number to a unified data management function entity corresponding to the unified data management function entity address.

Optionally, when the redirection node returns the determined unified data management function entity address to the NF entity, the redirection node sends the user number segment to which the user number belongs and the unified data management function entity address to the NF entity.

As shown in fig. 19, another overall method for acquiring data according to an embodiment of the present invention specifically includes the following steps:

step 1900, the NF entity needs to access the unified data management function entity, and sends a service request of the unified data management function entity including the user code number;

Step 1901, the NF entity queries a first corresponding relationship between a local redirection node address and a home area number segment, and if there is a unified data management function entity address or a redirection node address corresponding to a user number in a second corresponding relationship between a unified data management function entity address and a user number segment, if the NF entity determines that there is no first corresponding relationship and no second corresponding relationship corresponding to the user number segment where the user number is located locally, then step 1902 is executed;

step 1902, the NF entity sends a unified data management function entity service discovery request to the NRF entity;

step 1903, the NRF entity returns the redirect node address and home zone number segment;

step 1904, the NF entity stores the corresponding relationship between the address of the return redirection node and the home domain number segment locally;

step 1905, the NF entity sends a unified data management function entity service request to the redirection node corresponding to the redirection node address;

step 1906, the redirection node returns the address of the unified data management function entity and the user number segment;

step 1907, the NF entity stores the corresponding relationship between the unified data management function entity address and the user number segment locally;

Step 1908, the NF entity sends a unified data management function entity service request to a unified data management function entity address;

step 1909, the unified data management functional entity returns a service response;

step 1910, the NF entity needs to access the unified data management function entity and sends a unified data management function entity service request containing a user code number B;

step 1911, the NF entity queries a first corresponding relationship between a local redirection node address and a home zone number segment, and if there is a unified data management function entity address or a redirection node address corresponding to a user number in a second corresponding relationship between a unified data management function entity address and a user number segment, if the NF entity determines that the first corresponding relationship corresponding to the user number segment where the user number is located exists locally but the second corresponding relationship does not exist, then step 1912 is executed;

step 1912, the NF entity sends a service request of the unified data management function entity to the redirection node corresponding to the redirection node address;

step 1913, the redirection node returns the unified data management function entity address and the user number segment;

step 1914, the NF entity stores the corresponding relationship between the unified data management function entity address and the user number segment locally;

Step 1915, the NF entity sends a unified data management function entity service request to a unified data management function entity address;

step 1916, the unified data management functional entity returns a service response;

step 1917, the NF entity needs to access the unified data management function entity, and sends a unified data management function entity service request including the user code number B;

step 1918, the NF entity queries a first corresponding relationship between a local redirection node address and a home area number segment, and if there is a unified data management function entity address or a redirection node address corresponding to a user number in a second corresponding relationship between a unified data management function entity address and a user number segment, if the NF entity determines that the second corresponding relationship corresponding to the user number segment where the user number is located exists locally, step 1919 is executed;

step 1919, the NF entity sends a unified data management function entity service request to a unified data management function entity address;

and 1920, returning a service response by the unified data management functional entity.

The present application is described above with reference to block diagrams and/or flowchart illustrations of methods, apparatus (systems) and/or computer program products according to embodiments of the application. It will be understood that one block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, and/or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.

Accordingly, the present application may also be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). Furthermore, the present application may 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 embodied in the medium for use by or in connection with an instruction execution system. In the context of this application, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method of acquiring data, the method comprising:

the network function NF entity sends a service request carrying a request number segment data indication mark to the unified data management function entity;

2. The method as claimed in claim 1, wherein before the NF entity sends the service request carrying the request number segment data indication identifier to the unified data management function entity, the method further includes:

after the NF entity determines that the corresponding relation does not have the user number section corresponding to the user number and the unified data management function entity address, a request for inquiring the unified data management function entity address corresponding to the user number is sent to a network function storage function NRF entity;

the NF entity receives a unified data management function entity address returned by the NRF entity;

the NF entity sends a service request carrying a request number segment data indication mark to a unified data management function entity, and the service request comprises the following steps:

and the NF entity sends a service request carrying a request number segment data indication mark to a unified data management function entity according to the unified data management function entity address.

3. The method of claim 1, further comprising:

and after the NF entity determines that the corresponding relation has a user number section corresponding to the user number and a unified data management function entity address, the NF entity sends a service request containing the user number to the unified data management function entity of the unified data management function entity address corresponding to the user number.

4. The method as claimed in claim 3, wherein the NF entity sends the service request including the user code number to the unified data management function entity of the unified data management function entity address corresponding to the user code number, and includes:

and the service request sent by the NF entity to the unified data management function entity of the unified data management function entity address corresponding to the user code number does not carry the request number segment data indication identification.

5. A method according to any of claims 1 to 4, wherein the service request comprises some or all of:

6. A method of acquiring data, the method comprising:

if the service request containing the user number carries the request number segment data indication identification, the unified data management functional entity returns the user number segment managed by the unified data management functional entity to the NF entity in the service response, so that the NF entity updates the corresponding relation between the user number segment and the unified data management functional entity address, and the NF entity determines the unified data management functional entity address corresponding to the user number according to the corresponding relation before sending the service request to the unified data management functional entity subsequently.

7. A method of acquiring data, the method comprising:

the NF entity sends a unified data management function entity service discovery request to the NRF entity, and after receiving the redirection node address and the home region number section returned by the NRF entity, establishes a first corresponding relation between the redirection node address and the home region number section; and

and the NF entity sends a service request of a unified data management function entity to the redirection node, and establishes a second corresponding relation between the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node.

8. The method of claim 7, wherein the NF entity sends a unified data management function entity service discovery request to the NRF entity, further comprising:

and before the NF entity sends a service request of the unified data management function entity to the unified data management function entity in the subsequent process, if no user number segment corresponding to the user number exists in the first corresponding relation and the second corresponding relation, sending a service discovery request of the unified data management function entity to the NRF entity.

9. The method of claim 8, wherein prior to the NF entity sending a unified data management function entity service discovery request to the NRF entity, further comprising:

and the NF entity places the user code number in the service discovery request of the unified data management functional entity.

10. The method of claim 7, wherein the NF entity sending a unified data management function entity service request to a redirection node comprises:

and the NF entity sends a service request of a unified data management function entity to the redirection node according to the redirection node address corresponding to the user number after the NF entity has the attribution area number section corresponding to the user number and the redirection node address in the first corresponding relation and the NF entity has no user number section corresponding to the user number and no unified data management function entity address in the second corresponding relation.

11. The method of claim 7, wherein prior to the NF entity sending a unified data management function entity service request to a redirection node, further comprising:

and the NF entity places the user code number in the service request of the unified data management functional entity.

12. The method of claim 7, further comprising:

and after the NF entity has the user number section corresponding to the user number and the unified data management function entity address in the second corresponding relation, the NF entity sends a service request to the unified data management function entity according to the unified data management function entity address.

13. A method of acquiring data, the method comprising:

14. The method of claim 13, wherein the NRF entity returning a home zone number segment and a corresponding redirect node address to the NF entity comprises:

the NRF entity returns all redirection node addresses and corresponding home region number segments to the NF entity; or

If the service discovery request of the unified data management functional entity comprises a user number, the NRF entity returns the number section of the home area to which the user number belongs and the corresponding redirection node address in the service discovery request of the unified data management functional entity to the NF entity.

15. A method of acquiring data, the method comprising:

16. The method of claim 15, wherein the unified data management function entity service request includes a user code number;

after the redirecting node returns the user number segment to which the user number belongs and the corresponding unified data management function entity address to the NF entity, the method further comprises the following steps:

And the redirection node forwards a unified data management function entity service request sent by the NF entity to a unified data management function entity according to the unified data management function entity address corresponding to the user number segment to which the user number belongs.

17. An apparatus for acquiring data, the apparatus comprising: a processor and a transceiver:

the processor is used for sending a service request carrying a request number segment data indication mark to the unified data management functional entity; and after receiving a service response of the user number segment carrying the unified data management functional entity returned by the unified data management functional entity, establishing a corresponding relation between the user number segment of the unified data management functional entity and the address of the unified data management functional entity.

18. The device of claim 17, wherein the processor is further configured to:

after determining that the corresponding relation does not have a user number segment corresponding to the user number and a unified data management function entity address, sending a request for inquiring the unified data management function entity address corresponding to the user number to the NRF entity; receiving a unified data management function entity address returned by the NRF entity;

The processor is specifically configured to:

19. The apparatus of claim 18, further comprising:

and after determining that the corresponding relation has the user number segment corresponding to the user number and the unified data management function entity address, sending the service request containing the user number to the unified data management function entity of the unified data management function entity address corresponding to the user number.

20. The device of claim 19, wherein the processor is specifically configured to:

21. The apparatus according to any of claims 17 to 20, wherein the service request comprises some or all of:

22. An apparatus for acquiring data, the apparatus comprising a processor and a transceiver:

23. An apparatus for acquiring data, the apparatus comprising: at least one processing unit and at least one memory unit, wherein the memory unit has stored a program code which, when being executed by the processing unit, causes the processing unit to carry out the steps of the method of any one of claims 1 to 5 or the steps of the method of claim 6.

24. A computing device readable storage medium comprising program code for causing a computing device to perform the steps of the method of any of claims 1 to 5 or the steps of the method of claim 6 when said program code is run on the computing device.

25. An apparatus for acquiring data, the apparatus comprising: a processor and a transceiver:

the processor is used for sending a unified data management function entity service discovery request to an NRF entity, and establishing a first corresponding relation between a redirection node address and an attribution area number segment after receiving the redirection node address and the attribution area number segment returned by the NRF entity; and sending a service request of a unified data management function entity to the redirection node, and establishing a second corresponding relation of the unified data management function entity address and the user number segment after receiving the unified data management function entity address and the user number segment returned by the redirection node.

26. The device of claim 25, wherein the processor is further configured to:

and before a subsequent unified data management function entity service request is sent to a unified data management function entity, if no user number segment corresponding to the user number exists in the first corresponding relation and the second corresponding relation, sending a unified data management function entity service discovery request to an NRF entity.

27. The device of claim 26, wherein the processor is further configured to: and placing the user code number in the service discovery request of the unified data management functional entity.

28. The device of claim 25, wherein the processor is further configured to:

and after the first corresponding relation comprises the home region number section corresponding to the user number and the address of the redirection node and the second corresponding relation does not comprise the user number section corresponding to the user number and the address of the unified data management function entity, sending a service request of the unified data management function entity to the redirection node according to the address of the redirection node corresponding to the user number.

29. The device of claim 25, wherein the processor is further configured to: and the user code number is placed in the service request of the unified data management functional entity.

30. The device of claim 25, wherein the processor is further configured to:

and after the second corresponding relation has a user number section corresponding to the user number and a unified data management function entity address, sending a unified data management function entity service request to a unified data management function entity according to the unified data management function entity address.

31. An apparatus for acquiring data, the apparatus comprising a processor and a transceiver:

32. The device of claim 31, wherein the processor is specifically configured to:

33. An apparatus for acquiring data, the apparatus comprising: a processor and a transceiver:

the processor is used for receiving a service request of a unified data management function entity sent by the NF entity; and returning the user number segment and the corresponding unified data management function entity address to the NF entity so that the NF entity establishes a second corresponding relationship between the user number segment and the unified data management function entity address.

34. The apparatus of claim 33, wherein the unified data management function entity service request includes a user code number;

the processor is further configured to:

and forwarding a unified data management function entity service request sent by the NF entity to a unified data management function entity according to the unified data management function entity address corresponding to the user number segment to which the user number belongs.

35. An apparatus for acquiring data, the apparatus comprising: at least one processing unit and at least one memory unit, wherein the memory unit has stored a program code which, when being executed by the processing unit, causes the processing unit to carry out the steps of the method according to any one of claims 7 to 12 or the steps of the method according to any one of claims 13 to 14 or the steps of the method according to any one of claims 15 to 16.

36. A computing device readable storage medium comprising program code means for causing a computing device to perform the steps of the method of any of claims 7 to 12 or the steps of the method of any of claims 13 to 14 or the steps of the method of any of claims 15 to 16 when said program code means is run on the computing device.