System and method for unified data repositories and application programming interfaces for avoiding segmentation synchronization
A system includes a Network Repository Function in a segment of a Fifth Generation (5G) network. The NRF is configured to receive a registration request from a Unified Data Repository (UDR). The request indicates that the UDR includes both UE-specific data and non-UE specific data. The NRF is further configured to: store registration information provided in the registration request; receive a request from a network function within the segment and send a response to the request based on the registration information.
1 . A network comprising a first network segment and a second network segment, configured to:
synchronize a first Unified Data Repository (UDR) in the first network segment to another UDR in the second network segment if the first UDR includes only non-User Equipment (UE)-specific data, and
not synchronize the first UDR to the other UDR if the first UDR includes both non-UE specific data and UE-specific data,
wherein the first network segment includes a first Network Repository Function (NRF), and the second network segment includes a second NRF, and
wherein the first network segment and the second network segment are part of a same wireless network.
2 . The network of claim 1 , wherein the first NRF is configured to:
receive a registration request from the first UDR, wherein the registration request indicates that the first UDR includes both non-UE-specific data and UE specific data; and
store registration information provided in the registration request.
3 . The network of claim 2 , wherein the first NRF is further configured to:
receive a discovery request to identify a UDR that includes at least one of application data, exposure data, policy data, or subscription data, and wherein the discovery request specifies a Subscription Permanent Identifier (SUPI).
4 . The network of claim 3 , wherein the first NRF is further configured to:
send a message in response to the discovery request, wherein the response includes a fully qualified domain name (FQDN) of the first UDR.
5 . The network of claim 2 , wherein the registration request specifies one or more enumeration values, wherein each of the enumeration values specifies one of:
SUBSCRIPTION;
POLICY;
EXPOSURE;
APPLICATION;
APPLICATION_PFDS; or
APPLICATION_BDT_POLICY, POLICY_BDT.
6 . The network of claim 5 , wherein APPLICATION_PFDS identifies, in the first UDR, a resource that corresponds to Packet Flow Descriptions.
7 . The network of claim 1 , wherein the first network segment includes a network function that queries the first NRF for accessing the first UDR, wherein the network function includes one of a Policy Control Function (PCF) or a Network Exposure Function (NEF).
8 . A method comprising:
determining whether a first Unified Data Repository (UDR) in a first network segment included in a network comprises only non-User Equipment (UE)-specific data or both non-UE-specific and UE specific data;
synchronizing the first UDR to another UDR in a second network segment included in the network if the first UDR comprises only non-UE specific data, and
not synchronizing the first UDR to the other UDR if the first UDR comprises both non-UE specific data and UE-specific data,
wherein the first network segment includes a first Network Repository Function (NRF), and the second network segment includes a second NRF, and
wherein the first network segment and the second network segment are part of a same wireless network.
9 . The method of claim 8 , further comprising:
receiving, by the first NRF included in the first network segment, a registration request from the first UDR, wherein the registration request indicates that the first UDR includes both non-UE-specific data and UE specific data; and
storing registration information provided in the registration request.
10 . The method of claim 9 , further comprising:
receiving, by the first NRF, a discovery request to identify a UDR that includes at least one of application data, exposure data, policy data or subscription data, and wherein the discovery request specifies a Subscription Permanent Identifier (SUPI).
11 . The method of claim 10 , further comprising:
sending, by the first NRF, a message in response to the discovery request, wherein the response includes a fully qualified domain name (FQDN) of the first UDR.
12 . The method of claim 9 , wherein the registration request specifies one or more enumeration values, wherein each of the enumeration values specifies one of:
SUBSCRIPTION;
POLICY;
EXPOSURE;
APPLICATION;
APPLICATION_PFDS; or
APPLICATION_BDT_POLICY, POLICY_BDT.
13 . The method of claim 12 , wherein APPLICATION_PFDS identifies, in the first UDR, a resource that corresponds to Packet Flow Descriptions.
14 . The method of claim 8 , wherein the first network segment includes a network function that queries the first NRF for accessing the first UDR, wherein the network function includes one of a Policy Control Function (PCF) or a Network Exposure Function (NEF).
15 . A non-transitory computer-readable medium comprising processor-executable instructions, which when executed by one or more processors in a first network segment included in a network, cause the one or more processors to:
synchronize the first Unified Data Repository (UDR) in the first network segment to another UDR in a second network segment in the network if the first UDR includes only non-User Equipment (UE)-specific data, and
not synchronize the first UDR to the other UDR if the first UDR includes both non-UE specific data and UE-specific data,
wherein the first network segment includes a first Network Repository Function (NRF), and the second network segment includes a second NRF, and
wherein the first network segment and the second network segment are part of a same wireless network.
16 . The non-transitory computer-readable medium of claim 15 , wherein the first NRF is configured to:
receive a registration request from the first UDR, wherein the registration request indicates that the first UDR includes both non-UE-specific data and UE specific data; and
store registration information provided in the registration request.
17 . The non-transitory computer-readable medium of claim 16 , wherein the first NRF is further configured to:
receive a discovery request to identify a UDR that includes at least one of application data, exposure data, policy data, or subscription data, and wherein the discovery request specifies a Subscription Permanent Identifier (SUPI).
18 . The non-transitory computer-readable medium of claim 17 , wherein the first NRF is further configured to:
send a message in response to the discovery request, wherein the response includes a fully qualified domain name (FQDN) of the first UDR.
19 . The non-transitory computer-readable medium of claim 16 , wherein the registration request specifies one or more enumeration values, wherein each of the enumeration values specifies one of:
SUBSCRIPTION;
POLICY;
EXPOSURE;
APPLICATION;
APPLICATION_PFDS; or
APPLICATION_BDT_POLICY, POLICY_BDT.
20 . The non-transitory computer-readable medium of claim 19 , wherein APPLICATION_PFDS identifies, in the first UDR, a resource that corresponds to Packet Flow Descriptions.