Cross-agency communication through an ad-hoc network slice
US-2022030407-A1 · Jan 27, 2022 · US
US12532255B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12532255-B2 |
| Application number | US-202318480605-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 4, 2023 |
| Priority date | Oct 4, 2023 |
| Publication date | Jan 20, 2026 |
| Grant date | Jan 20, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods enable dynamic network function management, including obtaining user input data identifying network slice provisioning parameters for a creation of a network slice in a network; sending a request for a network repository function (NRF) instance for the network slice, to an orchestrator; receiving, from the NRF instance, a verification message of the creation of the network slice; sending, to the orchestrator, a request for a creation of multiple network function (NF) instances according to the network slice provisioning parameters; receiving, from the orchestrator, a verification message of the creation of the NF instances for the network slice; receiving, from the NRF, a confirmation message of a registration of the NF instances for the network slice; sending slice-specific subscriber provisioning data to a user data instance provisioned for the network slice; and generating a network slice creation confirmation message identifying the network slice.
Opening claim text (preview).
What is claimed is: 1 . A network device comprising: one or more processors configured to: obtain user input data identifying network slice provisioning parameters for a creation of a network slice in a network; send a request for a network repository function (NRF) instance for the network slice, to an orchestrator in the network; receive, from the NRF instance, a verification message of the creation of the network slice; send, to the orchestrator, a request for a creation of multiple network function (NF) instances according to the network slice provisioning parameters; receive, from the orchestrator, a verification message of the creation of the multiple NF instances for the network slice; receive, from the NRF, a confirmation message of a registration of the multiple NF instances for the network slice; send slice-specific subscriber provisioning data to a user data instance provisioned for the network slice; and generate a network slice creation confirmation message identifying the network slice implemented in the network. 2 . The network device of claim 1 , wherein the network slice provisioning parameters include at least one of Network Slice Selection Assistance Information (S-NSSAI), user equipment route selection policies (URSPs), or an access point name (APN). 3 . The network device of claim 1 , wherein the network slice provisioning parameters include at least one of a type of the multiple NF instances, a forecasted number of subscribers, a dimension of the network slice, or a lifespan of the network slice. 4 . The network device of claim 1 , wherein the one or more processors are further configured to determine at least one of: an NF type of the multiple NF instances, a number of the multiple NF instances, or a size and geographic service location of the multiple NF instances per NF type. 5 . The network device of claim 1 , wherein the one or more processors are further configured to compare the verification message against the request for an NRF instance. 6 . The network device of claim 1 , wherein, when sending slice-specific subscriber provisioning data, the one or more processors are further configured to send the user input data. 7 . The network device of claim 1 , wherein the multiple NF instances include at least one of a unified data repository (UDR) device, a unified data management (UDM) device, a user plane function (UPF), an access and management mobility function (AMF), a session management function (SMF), a network slice selection function (NSSF), or a policy control function (PCF). 8 . A method comprising: obtaining user input data identifying network slice provisioning parameters for a creation of a network slice in a network; sending a request for a network repository function (NRF) instance for the network slice, to an orchestrator in the network; receiving, from the NRF instance, a verification message of the creation of the network slice; sending, to the orchestrator, a request for a creation of multiple network function (NF) instances according to the network slice provisioning parameters; receiving, from the orchestrator, a verification message of the creation of the multiple NF instances for the network slice; receiving, from the NRF, a confirmation message of a registration of the multiple NF instances for the network slice; sending slice-specific subscriber provisioning data to a user data instance provisioned for the network slice; and generating a network slice creation confirmation message identifying the network slice implemented in the network. 9 . The method of claim 8 , wherein the network slice provisioning parameters include at least one of Network Slice Selection Assistance Information (S-NSSAI), user equipment route selection policies (URSPs), or an access point name (APN). 10 . The method of claim 8 , wherein the network slice provisioning parameters include at least one of a type of the multiple NF instances, a forecasted number of subscribers, a dimension of the network slice, or a lifespan of the network slice. 11 . The method of claim 8 , further comprising determining at least one of: an NF type of the multiple NF instances, a number of the multiple NF instances, or a size and geographic service location of the multiple NF instances per NF type. 12 . The method of claim 8 , further comprising comparing the verification message against the request for an NRF instance. 13 . The method of claim 8 , wherein, when sending slice-specific subscriber provisioning data, the method further comprising sending the user input data. 14 . The method of claim 8 , wherein the multiple NF instances include at least one of a unified data repository (UDR) device, a unified data management (UDM) device, a user plane function (UPF), an access and management mobility function (AMF), a session management function (SMF), a network slice selection function (NSSF), or a policy control function (PCF). 15 . A non-transitory, computer-readable storage media storing instructions, which, when executed by one or more processors of a network device, cause the network device to: obtain user input data identifying network slice provisioning parameters for a creation of a network slice in a network; send a request for a network repository function (NRF) instance for the network slice, to an orchestrator in the network; receive, from the NRF instance, a verification message of the creation of the network slice; send, to the orchestrator, a request for a creation of multiple network function (NF) instances according to the network slice provisioning parameters; receive, from the orchestrator, a verification message of the creation of the multiple NF instances for the network slice; receive, from the NRF, a confirmation message of a registration of the multiple NF instances for the network slice; send slice-specific subscriber provisioning data to a user data instance provisioned for the network slice; and generate a network slice creation confirmation message identifying the network slice implemented in the network. 16 . The non-transitory, computer-readable storage media of claim 15 , wherein the network slice provisioning parameters include at least one of Network Slice Selection Assistance Information (S-NSSAI), user equipment route selection policies (URSPs), an access point name (APN), a type of the multiple NF instances, a forecasted number of subscribers, a dimension of the network slice, or a lifespan of the network slice. 17 . The non-transitory, computer-readable storage media of claim 15 , wherein the instructions further cause the network device to determine at least one of: an NF type of the multiple NF instances, a number of the multiple NF instances, or a size and geographic service location of the multiple NF instances per NF type. 18 . The non-transitory, computer-readable storage media of claim 15 , wherein the instructions further cause the network device to compare the verification message against the request for an NRF instance. 19 . The non-transitory, computer-readable storage media of claim 15 , wherein, to send slice-specific subscriber provisioning data, the instructions further cause the network device to send the user input data. 20 . The non-transitory, computer-readable storage media of claim 15 , wherein the multiple NF instances include at least one of a unified data repository (UDR) device, a unified data management (UDM) device, a user plane function (UPF), an access and management mo
Related publications grouped by family.
Answers are generated from the same data shown on this page.