# US 12,192,064 B2 · Method and system for hybrid network slicing > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,192,064 B2 - Document ID: US12192064B2 - Status: Granted - Kind: B2 - Application number: 18/393,886 - Filed: 2023-12-22 - Published: 2024-04-18 - Granted: 2025-01-07 - Earliest claimed: 2022-09-30 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Kalyani Bogineni; Sudhakar Reddy Patil; Matthew W. Nelson; Hans Raj Nahata - Web page: https://patentgrep.com/patent/US12192064B2 ## CPC - H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV] - H04W 76/10: Connection setup - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements - H04L 41/145: {involving simulating, designing, planning or modelling of a network} - H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities - H04L 41/5048: {Automatic or semi-automatic definitions, e.g. definition templates} - H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components - H04L 43/55: Testing of service level quality, e.g. simulating service usage - H04W 16/10: Dynamic resource partitioning - H04W 24/02: Arrangements for optimising operational condition - H04L 41/14: Network analysis or design - H04L 43/50: Testing arrangements - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method, a network device, and a non-transitory computer-readable storage medium are described in relation to a hybrid network slicing service. The hybrid network slicing service may enable the initial configuration of a network slice according to network slice requests that may include customized and user-specified network performance criteria. The hybrid network slicing service may enable network slice requests to specify selection of network resources and use/availability based on entity-based criteria including end device and/or application specific associations. The hybrid network slicing service may optimize network slice configurations and generate network slice templates. ## Claims ### Claim 1 A method comprising: receiving, by a network device, a request, which includes an identifier that identifies a domain including radio and core network resources associated with multiple entities, for a proposed network slice in a network; receiving, by the network device, current network analytics information pertaining to the network; and provisioning, by the network device, the proposed network slice according to a network slice configuration that is based on the current network analytics information and the request. ### Claim 2 (depends on 1) The method of claim 1, wherein the proposed network slice has not been previously available in the network. ### Claim 3 (depends on 1) The method of claim 1, wherein the request includes expected network performance parameters and values for the proposed network slice. ### Claim 4 (depends on 1) The method of claim 1, wherein the domain includes application layer network resources associated with the multiple entities. ### Claim 5 (depends on 1) The method of claim 1, wherein the proposed network slice pertains to an end device application or service development. ### Claim 6 (depends on 1) The method of claim 1, further comprising: generating, by the network device, a network slice template of the proposed network slice. ### Claim 7 (depends on 1) The method of claim 1, wherein the radio and core network resources of the domain are reserved. ### Claim 8 (depends on 1) The method of claim 1, further comprising: invoking, by the network device, transmission of test traffic data via the proposed network slice. ### Claim 9 A network device comprising: a processor that is configured to: receive a request, which includes an identifier that identifies a domain including radio and core network resources associated with multiple entities, for a proposed network slice in a network; receive current network analytics information pertaining to the network; and provision the proposed network slice according to a network slice configuration that is based on the current network analytics information and the request. ### Claim 10 (depends on 9) The network device of claim 9, wherein the proposed network slice has not been previously available in the network. ### Claim 11 (depends on 9) The network device of claim 9, wherein the request includes expected network performance parameters and values pertaining to the proposed network slice. ### Claim 12 (depends on 9) The network device of claim 9, wherein the domain includes application layer network resources associated with the multiple entities. ### Claim 13 (depends on 9) The network device of claim 9, wherein the proposed network slice pertains to an end device application or service development. ### Claim 14 (depends on 9) The network device of claim 9, wherein the processor is further configured to: generate a network slice template of the proposed network slice. ### Claim 15 (depends on 9) The network device of claim 9, wherein the radio and core network resources of the domain are reserved. ### Claim 16 (depends on 9) The network device of claim 9, wherein the processor is further configured to: invoke transmission of test traffic data via the proposed network slice. ### Claim 17 A non-transitory computer-readable storage medium storing instructions executable by a processor of a network device, wherein the instructions are configured to: receive a request, which includes an identifier that identifies a domain including radio and core network resources associated with multiple entities, for a proposed network slice in a network; receive current network analytics information pertaining to the network; and provision the proposed network slice according to a network slice configuration that is based on the current network analytics information and the request. ### Claim 18 (depends on 17) The non-transitory computer-readable storage medium of claim 17, wherein the proposed network slice has not been previously available in the network. ### Claim 19 (depends on 17) The non-transitory computer-readable storage medium of claim 17, wherein the radio and core network resources of the domain are reserved. ### Claim 20 (depends on 17) The non-transitory computer-readable storage medium of claim 17, wherein the instructions are further configured to: generate a network slice template of the proposed network slice.