CN113225440B - Management method of cloud communication network slices, computer equipment and storage medium - Google Patents

Management method of cloud communication network slices, computer equipment and storage medium Download PDF

Info

Publication number
CN113225440B
CN113225440B CN202110436788.0A CN202110436788A CN113225440B CN 113225440 B CN113225440 B CN 113225440B CN 202110436788 A CN202110436788 A CN 202110436788A CN 113225440 B CN113225440 B CN 113225440B
Authority
CN
China
Prior art keywords
network slice
code number
network
management data
call request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110436788.0A
Other languages
Chinese (zh)
Other versions
CN113225440A (en
Inventor
覃飞剑
刘作
陈杨
黄梅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangxi Dongxin Yitong Technology Co ltd
Original Assignee
Guangxi Dongxin Yitong Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangxi Dongxin Yitong Technology Co ltd filed Critical Guangxi Dongxin Yitong Technology Co ltd
Priority to CN202110436788.0A priority Critical patent/CN113225440B/en
Publication of CN113225440A publication Critical patent/CN113225440A/en
Application granted granted Critical
Publication of CN113225440B publication Critical patent/CN113225440B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/54Arrangements for diverting calls for one subscriber to another predetermined subscriber
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0893Assignment of logical groups to network elements

Abstract

The invention provides a management method of a cloud communication network slice, which comprises the following steps: receiving a call request, wherein the call request comprises a target code number, and the target code number is a privacy number bound with a called number; redirecting the call request from the first network slice to a second network slice if the target code number is in a state of being migrated from the first network slice to the second network slice; and forwarding the call request to the called number through the second network slice. According to the invention, the code number is migrated among different network slices, the calling speech path is redirected to the second network slice aiming at the calling of the code number during migration, and the calling speech path is processed by the second network slice, so that the normal use of the code number migration process is realized, the code number utilization rate is improved, the calling interruption caused by the code number migration is avoided, the use process of a user is not perceived, and the use experience of the user is improved.

Description

Management method of cloud communication network slices, computer equipment and storage medium
Technical Field
The invention relates to the technical field of network function virtualization, in particular to a management method of a cloud communication network slice, computer equipment and a storage medium.
Background
Network Function Virtualization (NFV), a concept of Network architecture (Network architecture), which uses Virtualization technology to divide the Network node level function into several functional blocks, which are implemented in software respectively and are not limited to hardware architecture any more. At the heart of Network Function Virtualization (NFV) is a virtual network function. It provides Network functions that can only be found in hardware, including many applications such as routing, CPE (Customer Premise Equipment), mobile core, IMS (Management Information System), CDN (Content Delivery Network), accessories, security, policy, and so forth. The goal of network function virtualization technology is to provide network functions on standard servers, not on custom devices.
The privacy number communication technology is a technology for providing temporary numbers for clients in specific scenes and time periods to allow two parties in a conversation to contact with each other so as to achieve the purposes of hiding real numbers of the two parties and protecting privacy of the two parties. The technology is widely applied to internet services such as network car booking, take-out food ordering, renting and selling intermediaries and the like.
The prior art is able to combine privacy number technology with network function virtualization technology.
When the traffic volume is increased, a new network slice needs to be generated in an incremental mode, the code number in the first network slice is manually offline first, then the code number in the newly generated network slice is online, the code number needs to be suspended for use in the process of transferring among the network slices, the code number utilization rate is low, and the user experience is poor.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a cloud communication network slice management method. The method comprises the following steps:
receiving a call request, wherein the call request comprises a target code number, and the target code number is a privacy number bound with a called number;
redirecting the call request from the first network slice to a second network slice if the target code number is in a state of being migrated from the first network slice to the second network slice;
forwarding the call request to the called number through the second network slice.
In one embodiment, the specific step of redirecting the call request from the first network slice to the second network slice is:
acquiring IP addresses of the first network slice and the second network slice;
changing a target IP address of calling data from a first network slice IP address to a second network slice IP address, wherein the calling data is used for calling the target code number after receiving the calling request;
and sending the call data to a second network slice.
In one embodiment, the state migrated from the first network slice to the second network slice specifically includes:
a state in which the code number of the first network slice is re-registered in a second network slice or waits for registration.
In one embodiment, the step after redirecting the transmission target of the call request from the first network slice to the second network slice is:
updating the state information of the code number which is successfully migrated;
and discarding the registration information of the target code number which is migrated in the first network slice.
In one embodiment, the step before accepting the call request is:
acquiring network slice management data, wherein the network slice management data is used for deploying computing resources and network resources of a network slice;
acquiring code number management data, wherein the code number management data describes management information for controlling the migration of the code number;
and migrating the code number from the first network slice to a second network slice according to the code number management data and the slice management data.
In one embodiment, the second network slice is a network slice with unsaturated carrying capacity.
In one embodiment, the first network slice is a network slice which needs to be resource-recycled after all code number migration is completed according to network slice management data.
A management method of a cloud communication network slice comprises the following steps:
acquiring network slice management data, wherein the network slice management data is used for deploying computing resources and network resources of a network slice;
generating a second network slice according to the network slice management data deployment;
acquiring code number management data, wherein the code number management data describes management information for controlling the migration of the code number;
migrating the code number from a first network slice to a second network slice according to the code number management data; a call request for a code number in a migrated state, the call request handled by a second network slice.
A computer device comprising a memory and a processor, the memory having stored therein a computer program which, when executed by the processor, causes the processor to carry out the steps of the network slice management method described above.
A computer-readable storage medium, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of the network slice management method described above.
According to the management method, the computer equipment and the storage medium of the cloud communication network slice, the code numbers are migrated among different network slices, the calling of the code numbers in the migration is realized by redirecting the calling speech path to the second network slice and processing the calling speech path by the second network slice, so that the normal use of the code number migration process is realized, the utilization rate of the code numbers is improved, the calling interruption caused by the migration of the code numbers is avoided, the use process of a user is not perceived, and the use experience of the user is improved.
Drawings
Fig. 1 is an application environment diagram of a management method for a cloud communication network slice provided in one embodiment;
FIG. 2 is a flow diagram of a method for managing cloud communication network slices in one embodiment;
fig. 3 is a flowchart of a management method of a cloud communication network slice in another embodiment;
fig. 4 is a flowchart of a management method of a cloud communication network slice in another embodiment;
fig. 5 is a flowchart of a method for managing a cloud communication network slice in another embodiment;
FIG. 6 is an architectural diagram of a slice of a cloud communication network in one embodiment;
FIG. 7 is a flow diagram that illustrates a method for managing slices of a cloud communication network, under an embodiment;
FIG. 8 is a block diagram showing an internal configuration of a computer device according to one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
It will be understood that, as used herein, the terms "first," "second," and the like may be used herein to describe various elements, but these elements should not be limited by these terms unless otherwise specified. These terms are only used to distinguish one element from another. For example, a first xx script may be referred to as a second xx script, and similarly, a second xx script may be referred to as a first xx script, without departing from the scope of the present application.
Fig. 1 is a diagram of an application environment of a network slice management method provided in an embodiment, as shown in fig. 1, in the application environment, including a first terminal 111, a second terminal 112, and a computer device 120.
The computer device 120 may be an independent physical server or terminal having a communication function, may also be a server cluster formed by a plurality of physical servers, and may be a cloud server providing basic cloud computing services such as a cloud server, a cloud database, a cloud storage, and a CDN.
The first terminal 111 and the second terminal 112 may be devices capable of making a call or performing short message communication, such as a smart phone, a tablet computer, a smart watch, and a fixed phone, but are not limited thereto. The first terminal 111, the second terminal 112 and the computer device 120 may be connected through a network, which is not limited herein. A computer device 120 is connected to at least one terminal i 111 and terminal ii 112 to implement a communication service between the terminal i 111 and the terminal ii 112.
As shown in fig. 2, in an embodiment, a method for network slice management is provided, and this embodiment is mainly illustrated by applying the method to the server 120 in fig. 1. The method specifically comprises the following steps:
step S202, receiving a call request, wherein the call request comprises a target code number, and the target code number is a privacy number bound with a called number;
step S204, if the target code number is in a state of being migrated from the first network slice to the second network slice, redirecting the call request from the first network slice to the second network slice;
step S206, forwarding the call request to the called number through the second network slice.
In an embodiment of the present invention, a first terminal 111 and a second terminal 112 need to perform communication, such as telephone communication or short message communication, where one end is a calling party and the other end is a called party, in order to protect privacy of the called party, in one case, an intermediate number, also called a privacy number, is allocated to the called party without informing the calling party of a called party communication number, the intermediate number is bound with the called number, the intermediate number is called by the calling party, and then the intermediate number is switched to the calling number, so that communication between the calling party and the called party is achieved under the condition of protecting privacy of the called party. In the communication process, the terminal one 111 or the terminal two 112 directly calls the target code number, the server 120 receives a call request for the target code number, and the call request may be a call request, or may be a short message or multimedia message sending request, which is not specifically limited herein. In a period of time or after two terminal communication end, can retrieve the high-efficient utilization of code number to middle privacy number.
In one embodiment of the present invention, the target code number is assigned at the server in the NFV architecture, and the server in the NFV architecture assigns the code number to the server 120 in the present invention, that is, the privacy number technology is combined with the network function virtualization. The server 120 can decouple software and hardware and abstract functions, so that the functions of network equipment do not depend on special hardware any more, resources can be fully and flexibly shared, rapid development and deployment of new services are realized, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are carried out based on actual service requirements; and according to the actual service carrying capacity, hardware resources and software resources are distributed and deployed to form mutually independent network slices, and the network slices have corresponding network functions such as a conversation function and a short message service function. In one case, as the traffic volume increases or decreases, different network slices need to be merged or newly added, and the code number needs to be transferred between different network slices. When the code number is transferred, the code number needs to be registered in a target slice so that the network slice can process a call request aiming at the code number, the transfer of the code number among different network slices needs time, the code number cannot be used in an original slice in the transfer process, the code number is not registered in the target slice, when the target code number is judged to be in a state of being transferred from a first network slice to a second network slice, in order to enable the code number to be continuously used, the call request is redirected to the second network slice from the first network slice, a routing signaling of the call request can be directed to the target slice, at the moment, a speech path of the call request is processed by computing resources and network resources of the target slice, the code number can also be used when the code number is transferred among the network slices, and the code number utilization efficiency is improved.
In one embodiment of the invention, the call request is forwarded to the called number through the second network slice. A code number is registered in a network slice, when a call request related to the code number is accessed, the network slice where the code number is registered processes the call request, for the subsequent processing steps, a called number bound with the code number can be inquired by the network slice, the network slice receives returned called number information, then sends a call to the called number, and after the network slice is communicated with a called party, the network slice overlaps the telephone channel of the called party and a calling party, so that the communication between the called party and the calling party is realized. When the called number is bound with the code number, the calling party displays the called number as the code number to protect the privacy of the called party; the calling number can also be bound with the code number, and at the moment, the called party displays that the incoming number is also the code number, so that the privacy of both parties is protected.
In an embodiment of the present invention, after redirecting the call request from the first network slice to the second network slice, the second network slice processes the voice channel logic of the call request, and then directly communicates with the called number according to the binding relationship between the number and the called number, the specific binding relationship between the number and the called number may not be managed in the slice, and may be managed by a separate function module, and different network slices may all query the called number bound to the number in the internal part thereof, and the function module can return the called number information to the network slice after receiving the query request. The code number in migration can continue to be registered in the target slice at this time. For the second network slice, it may be any network slice that has the same network function and unsaturated traffic carrying capacity.
In the embodiment of the invention, for the calling of the code number which is migrated between the network slices, the calling session is redirected, the calling is accessed into the target slice, the calling session function is specifically realized by the target slice, the usability of the code number in the migration is realized, the utilization rate of the code number is not reduced, the calling is not interrupted due to the migration of the code number, no perception is generated in the using process of a user, the utilization rate of the code number is high, and the user experience is good.
As shown in fig. 3, in an embodiment of the present invention, the specific steps of redirecting the call request from the first network slice to the second network slice are:
s302, acquiring IP addresses of the first network slice and the second network slice;
s304, changing a target IP address of calling data from a first network slice IP address to a second network slice IP address, wherein the calling data is used for calling the target code number after receiving the calling request;
s306, the call data is sent to the second network slice.
In one embodiment of the present invention, the incoming call request is transmitted to the network slice with the registered code number through the IP address of the network slice, and when the code number is in the migration state, the server 120 obtains the IP address of the first network slice and the slice address of the target network, and changes the target IP address of the call data from the IP address of the first network slice to the IP address of the second network slice, so that the call data is processed by the second network slice. The call data is data for calling a target code number after the call request is accepted. And transmitting the call data to the second network slice according to the IP address of the second network slice.
In an embodiment of the present invention, the state migrated from the first network slice to the second network slice specifically includes:
a state in which the code number of the first network slice is re-registered in a second network slice.
In the embodiment of the invention, the network slices are relatively independent virtual functions, the code numbers can be migrated among different network slices, and the code numbers can be migrated only when being migrated to realize the same functions in the second network slice. And the code number has a binding relationship with the called number in the network slice, and the code number is registered in the network slice, so that the incoming call channel aiming at the code number can be used in the registered network slice. In one aspect of the present invention, when a code number migrates between slices, the code number to be migrated is re-registered in a target slice, and thus a state in which the code number migrates from a first network slice to a second network slice specifically refers to a state in which the code number of the first network slice is re-registered in the second network slice.
Referring to fig. 4, in an embodiment of the present invention, the steps after redirecting the transmission target of the call request from the first network slice to the second network slice are:
s402, updating the state information of the successfully migrated code number;
s404, discarding the registration information of the migrated target code number in the first network slice.
In an embodiment of the present invention, after the code number is registered in the second network slice, the code number is successfully migrated, and at this time, the call request for the code number can be directly routed to the second network slice registered by the code number for communication without passing through the first network slice or redirecting the routing signaling of the call request. Meanwhile, the registration information of the code number in the first network slice is abandoned, and the migration of the code number among different network slices is realized.
Referring to fig. 5, in an embodiment of the present invention, the steps before the call request is accepted are:
s502, acquiring network slice management data, wherein the network slice management data is used for deploying computing resources and network resources of a network slice;
s504, acquiring code number management data, wherein the code number management data describes management information for controlling the migration of the code number;
s506, migrating the code number from the first network slice to the second network slice according to the code number management data and the slice management data.
In an embodiment of the present invention, before receiving a call request, a network slice needs to be managed and arranged according to a current service carrying capacity to adapt to the current service carrying capacity, and calculation and network resources are reasonably utilized. For example, when the service carrying capacity is too large, the number of current network slices is not enough to support service processing, and hardware resources and software resources need to be arranged to generate new network slices to process more services. Similarly, when the service carrying capacity is reduced, the resource utilization rate of the current network slice is low, and the network slices with small service carrying capacity need to be merged, so that the resource recovery is performed, and the resource utilization rate is improved.
In an embodiment of the present invention, network slice management data is obtained, and the network slice management data is used to deploy computing resources, network resources, and storage resources of the network slice, so that the computing resources, the network resources, and the storage resources of the portion form a network slice with a set network function. Specifically, a part of hardware resources and software resources are arranged according to network functions and are deployed into a network slice instance according to the network functions, and the network slice instance can realize corresponding network functions.
In an embodiment of the present invention, code number management data is obtained, where the code number management data is management information describing control of code number migration, that is, a code number to be migrated and a called number bound to the code number to be migrated are specified, and a second network slice to be migrated of the code number to be migrated is also obtained. The code number management information may also include information describing the state of the code number to facilitate understanding of the state in which the code number is located. The code number management data may also be used to assign an intermediate code number to the called number, causing an association to be made between the called number and the code number.
In an embodiment of the present invention, after the code number management data and the network slice management data are obtained, the server 120 migrates the corresponding code number to the second network slice according to the indication of the obtained code number management data and the network slice management data, so as to implement reasonable allocation and deployment of internal computing resources and network resources.
In one embodiment of the present invention, the second network slice is a network slice whose carrying capacity is not saturated. As a situation of the present invention, when there is a large amount of traffic and a large amount of bearer, the first network slice may be a network slice whose bearer is saturated or is nearly saturated, a new network slice needs to share a part of traffic bearer, specifically, a new code number needs to be registered in the new network slice, or a part of code numbers in the first network slice may be migrated to the new network slice, and the new network slice implements a network function. The new network slice may be a network slice generated when traffic volume increases, such as a network slice generated after acquiring the network slice management data and before code number migration; or an existing but not saturated bearing capacity network slice; at this time, the several new network slices may be target slices for code number migration.
In an embodiment of the present invention, the first network slice is a network slice that needs to be resource-recycled after all code number migration is completed according to network slice management data. As a case of the present invention, when the traffic volume is small, there are multiple network slices processing the same type of service, and there are network slices with small carrying capacity, the resource utilization rate is low, and resource needs to be reconfigured as well, that is, multiple network slices processing the same type of service are merged, and when merging, data inside the network slices needs to be merged or migrated, that is, code numbers in different network slices are migrated to network slices with unsaturated carrying capacity, and the network slices with unsaturated carrying capacity are target slices. The first network slice is a network slice which needs resource recovery according to the network slice management data, and the time for resource recovery is that after all code numbers in the first network slice are migrated to the target slice, the code numbers in the first network slice can be migrated to the same second network slice, or can be migrated to different second network slices.
In the embodiment of the present invention, in one case, the network slice management data may manage to generate only a new second network slice when traffic increases, in one case, the network slice management data may manage to recover only the first network slice when traffic decreases, and in another case, when the slice is used for switching between different network functions, the second network slice may be a newly generated second network slice, and the first network slice may be a network slice that needs to be recovered.
As shown in fig. 6, for providing a specific example of a network slicing architecture for the present invention, the server 120 includes:
the NFV MANO (network function virtualization-management and virtualization orchestrator) is responsible for allocating basic hardware resources required by network slices, completing deployment of virtual network functions on virtualized basic hardware, and completing network connection between network function hardware, so as to implement dynamic deployment and deletion of network slices.
The VNFO (virtualized network function organizer) is responsible for unified configuration and management of cooperative work of network elements within and between network slices.
I-CSCF (interworking-Call Session Control Function, Interrogating Call Session Control Function).
The NFV MANO, VNFO, I-CSCF may each be connected to different network slices for managing network functions of the network slices.
Further included in the network slice is:
the P-CSCF (Proxy-Call Session Control Function) maintains registration and registration of code numbers to enable Call requests to be routed to network slices.
The MS (Media Server) is responsible for completing the functions of Media negotiation, encoding and decoding, playback, etc. during the call.
The SMS (Short Message Service) is responsible for completing the Short Message uplink and downlink processes in the call process.
NLM (number location management) manages and maintains the number state in the network slice.
And the AS (Application Server) is used for uniformly scheduling functions of the P-CSCF, the MS, the SMS and the NLM and is mainly responsible for incoming call and outgoing call control, butt joint with a service arrangement layer and sip signaling control and butt joint.
In an embodiment of the present invention, when the traffic volume increases, a new network slice is needed to carry the traffic, and the existing network slice calculates and allocates the code number to be migrated according to its own carrying capacity, that is, network slice management data and code number management data can be generated.
And according to the network slice management data, the NFV MANO deploys basic computing resources, storage resources and network resources to generate a newly deployed network slice.
According to the code number management data, the code numbers to be migrated and newly allocated from the existing network slices can be simultaneously registered in batches in the newly deployed network slices.
During registration, for the code number to be migrated, the VNFO controls the original slice P-CSCF to redirect the routing signaling to the newly deployed slice P-CSCF, i.e., the call request for the code number in migration is re-accessed to the newly deployed network slice P-CSCF, and the speech path is processed by the computing resources and network resources of the newly deployed network slice.
After the code number is successfully registered, updating the code number state to the NLM of the new network slice, and synchronously sending the code number state to the NFV MANO and the NLM of the existing network slice for synchronizing the consistency of the database states and updating the part of code number state data from the NLM of the existing network slice; the updating of the state of the registration success code number can be processed in parallel, and the calculation efficiency is improved.
And for the newly-incoming call and the short message service to be routed to a new network slice, the registration information of the first network slice is abandoned after being expired, and the user can not sense the whole process in the service migration process.
In an embodiment of the present invention, when traffic is reduced or a temporary scenario is eliminated, network slices need to be merged, and corresponding computing resources, storage resources, and network resources need to be recycled or reallocated, so that network slice management data and code number management data can also be generated.
And acquiring the network slices needing to be merged by the NFV MANO according to the network slice management data.
And managing data according to the code numbers, and performing batch registration on all the code numbers to be combined in the second network slice, namely performing a migration process.
In the process of registration migration, for an incoming call channel aiming at a code number to be migrated, the VNFO controls the P-CSCF of the first network slice to redirect a routing signaling to the P-CSCF of the second network slice, and the second network slice is a network slice with unsaturated service bearing capacity.
And after the code number is successfully registered, updating the code number states in the NLM and NFV MANO databases.
For the incoming call request, the new incoming call request is directly routed to the merged second network slice, and the code number registration information in the first network slice is abandoned after being naturally expired.
And initializing and recycling the network slice resource after observing that the call request speech path carried by the merged network slice returns to zero.
According to the embodiment of the invention, the network slice is elastically stretched according to different service bearing capacities, and meanwhile, when the code number in the network slice is migrated, the code number can be normally used in the migration process or the migration waiting process by redirecting the incoming call channel and processing the code number by the second network slice, so that the non-perception experience of a user is realized.
Referring to fig. 7, in an embodiment of the present invention, a network slice management method is provided, and this embodiment is mainly illustrated by applying the method to the server 120 in fig. 1. The method specifically comprises the following steps:
s702, acquiring network slice management data, wherein the network slice management data is used for deploying computing resources and network resources of a network slice;
s704, deploying and generating a second network slice according to the network slice management data;
s706, acquiring code number management data, wherein the code number management data describes management information for controlling the migration of the code number;
s708, migrating the code number from a first network slice to a second network slice according to the code number management data; a call request for a code number in a migrated state, the call request handled by a second network slice.
In an embodiment of the present invention, the network slice needs to be managed and arranged according to the current service carrying capacity to adapt to the current service carrying capacity, and the calculation and network resources are reasonably utilized. For example, when the service carrying capacity is too large, the number of current network slices is not enough to support service processing, and hardware resources and software resources need to be arranged to generate new network slices to process more services. Similarly, when the service carrying capacity is reduced, the resource utilization rate of the current network slice is low, and the network slices with small service carrying capacity need to be merged, so that the resource recovery is performed, and the resource utilization rate is improved.
In an embodiment of the present invention, network slice management data is obtained, and the network slice management data is used to deploy computing resources, network resources, and storage resources of the network slice, so that the computing resources, the network resources, and the storage resources of the portion form a network slice with a set network function. Specifically, a part of hardware resources and software resources are arranged according to network functions and are deployed into a network slice instance according to the network functions, and the network slice instance can realize corresponding network functions.
In an embodiment of the present invention, code number management data is obtained, where the code number management data is management information describing control of code number migration, that is, a code number to be migrated is specified, and a second network slice to which the code number to be migrated is yet to be migrated is obtained. The code number management information may also include information describing the state of the code number to facilitate understanding of the state in which the code number is located. The code number management data may also be used to assign an intermediate code number to the called number, causing an association to be made between the called number and the code number.
In an embodiment of the present invention, after the code number management data and the network slice management data are obtained, the server 120 migrates the corresponding code number to the second network slice according to the indication of the obtained code number management data and the network slice management data, so as to implement reasonable allocation and deployment of internal computing resources and network resources.
In an embodiment of the present invention, the second network slice is a newly deployed generated network slice. As a situation of the present invention, when there is a large amount of traffic and a large amount of bearer, the first network slice may be a network slice whose bearer is saturated or is nearly saturated, a new network slice needs to share a part of traffic bearer, specifically, a new code number needs to be registered in the new network slice, or a part of code numbers in the first network slice may be migrated to the new network slice, and the new network slice implements a network function. The new network slice may be a network slice generated as traffic grows, such as a network slice generated after acquiring network slice management data and before code number migration.
According to the embodiment of the invention, the network slice is newly deployed according to the increase of the service bearing capacity, and meanwhile, the code number in the network slice is processed by the second network slice through the redirection of the incoming call channel when the code number is migrated, so that the code number can be normally used in the migration process or the migration waiting process, and the non-perception experience of a user is realized.
FIG. 8 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the server 120 in fig. 1. The computer device comprises a processor, a memory, a network interface, an input device and a display screen which are connected through a system bus. The memory comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement a method of managing a cloud communication network slice. The internal memory may also store a computer program, and when the computer program is executed by the processor, the computer program may cause the processor to execute a method for managing a cloud communication network slice. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 8 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is proposed, the computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
step S202, receiving a call request, wherein the call request comprises a target code number, and the target code number is a privacy number bound with a called number;
step S204, if the target code number is in a state of being migrated from the first network slice to the second network slice, redirecting the call request from the first network slice to the second network slice;
step S206, forwarding the call request to the called number through the second network slice.
In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of:
step S202, receiving a call request, wherein the call request comprises a target number, and the target number is a privacy number bound with a called number;
step S204, if the target code number is in a state of being migrated from the first network slice to the second network slice, redirecting the call request from the first network slice to the second network slice;
step S206, forwarding the call request to the called number through the second network slice.
It should be understood that, although the steps in the flowcharts of the embodiments of the present invention are shown in sequence as indicated by the arrows, the steps are not necessarily performed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in various embodiments may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by a computer program, which may be stored in a non-volatile computer readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that various changes and modifications can be made by those skilled in the art without departing from the spirit of the invention, and these changes and modifications are all within the scope of the invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (8)

1. A method of managing a cloud communication network slice, the method comprising:
receiving a call request, wherein the call request comprises a target code number, and the target code number is a privacy number bound with a called number;
redirecting the call request from the first network slice to a second network slice if the target code number is in a state of being migrated from the first network slice to the second network slice;
forwarding the call request to the called number through the second network slice;
the specific steps of redirecting the call request from the first network slice to the second network slice are:
acquiring IP addresses of the first network slice and the second network slice;
changing a target IP address of calling data from a first network slice IP address to a second network slice IP address, wherein the calling data is used for calling the target code number after receiving the calling request;
sending the call data to a second network slice;
the state of the migration from the first network slice to the second network slice is specifically:
a state in which the code number of the first network slice is re-registered in a second network slice or waits for registration.
2. The method of claim 1, wherein the step of redirecting the transmission target of the call request from the first network slice to the second network slice is:
updating the state information of the code number which is successfully migrated;
discarding the registration information of the target code number that has been migrated in the first network slice.
3. The method for managing network slices according to claim 1, wherein the step of receiving the call request is:
acquiring network slice management data, wherein the network slice management data is used for deploying computing resources and network resources of a network slice;
acquiring code number management data, wherein the code number management data describes management information for controlling the migration of the code number;
and migrating the code number from the first network slice to a second network slice according to the code number management data and the slice management data.
4. The method for managing network slices of claim 3, wherein the second network slice is a network slice with unsaturated carrying capacity.
5. The method for managing network slices of claim 4, wherein the first network slice is a network slice that needs to be resource-recycled after all code number migrations are completed according to network slice management data.
6. The method for managing network slices of claim 1, further comprising:
acquiring network slice management data, wherein the network slice management data is used for deploying computing resources and network resources of a network slice;
generating a second network slice according to the network slice management data deployment;
acquiring code number management data, wherein the code number management data describes management information for controlling the migration of the code number;
migrating the code number from a first network slice to a second network slice according to the code number management data; a call request for a code number in a migrated state, the call request handled by a second network slice.
7. A computer device comprising a memory and a processor, the memory having stored therein a computer program which, when executed by the processor, causes the processor to carry out the steps of the method of managing network slices of any of claims 1 to 6.
8. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, causes the processor to carry out the steps of the method of managing network slices of any of claims 1 to 6.
CN202110436788.0A 2021-04-22 2021-04-22 Management method of cloud communication network slices, computer equipment and storage medium Active CN113225440B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110436788.0A CN113225440B (en) 2021-04-22 2021-04-22 Management method of cloud communication network slices, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110436788.0A CN113225440B (en) 2021-04-22 2021-04-22 Management method of cloud communication network slices, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113225440A CN113225440A (en) 2021-08-06
CN113225440B true CN113225440B (en) 2022-09-02

Family

ID=77088651

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110436788.0A Active CN113225440B (en) 2021-04-22 2021-04-22 Management method of cloud communication network slices, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113225440B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1277789A (en) * 1997-08-27 2000-12-20 利伯特尔网络有限公司 Method and system for processing calls for communication equipment with a subscriber number ported from a first operator to a second operator, especially for mobile communication
CN1893730A (en) * 2005-07-07 2007-01-10 株式会社东芝 Handover processing system in mobile communication system
CN101031146A (en) * 2007-03-23 2007-09-05 华为技术有限公司 Method, apparatus and system for switching network
CN106797591A (en) * 2014-03-07 2017-05-31 环球星公司 Honeycomb control tower feature with inserting of satellite to allow cellular devices to be roamed on satellite network
CN109819488A (en) * 2017-11-20 2019-05-28 华为技术有限公司 A kind of conversation switching method, equipment and system
CN112003855A (en) * 2020-08-20 2020-11-27 杭州诚智天扬科技有限公司 Privacy number service platform system based on IMS network and application method thereof
CN112004243A (en) * 2018-01-19 2020-11-27 Oppo广东移动通信有限公司 Method for configuring network slice identifier
CN112512100A (en) * 2020-12-10 2021-03-16 中国联合网络通信集团有限公司 Slice priority-based AMF (advanced metering framework) redirection method and newly-added management network element

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108924884B (en) * 2017-04-04 2021-02-23 华为技术有限公司 Communication method and communication device
CN117596632A (en) * 2017-10-13 2024-02-23 三星电子株式会社 Network entity and method for executing same
CN112636959B (en) * 2020-12-14 2022-06-21 广西东信易通科技有限公司 Network slice privacy number service guarantee system and method for distinguishing service types
CN112671864B (en) * 2020-12-15 2023-04-07 广西东信易通科技有限公司 Privacy number dynamic allocation system based on active request

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1277789A (en) * 1997-08-27 2000-12-20 利伯特尔网络有限公司 Method and system for processing calls for communication equipment with a subscriber number ported from a first operator to a second operator, especially for mobile communication
CN1893730A (en) * 2005-07-07 2007-01-10 株式会社东芝 Handover processing system in mobile communication system
CN101031146A (en) * 2007-03-23 2007-09-05 华为技术有限公司 Method, apparatus and system for switching network
CN106797591A (en) * 2014-03-07 2017-05-31 环球星公司 Honeycomb control tower feature with inserting of satellite to allow cellular devices to be roamed on satellite network
CN109819488A (en) * 2017-11-20 2019-05-28 华为技术有限公司 A kind of conversation switching method, equipment and system
CN112004243A (en) * 2018-01-19 2020-11-27 Oppo广东移动通信有限公司 Method for configuring network slice identifier
CN112003855A (en) * 2020-08-20 2020-11-27 杭州诚智天扬科技有限公司 Privacy number service platform system based on IMS network and application method thereof
CN112512100A (en) * 2020-12-10 2021-03-16 中国联合网络通信集团有限公司 Slice priority-based AMF (advanced metering framework) redirection method and newly-added management network element

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"S2-1812394 eNS KI1 Solution #1.7 evaluation";Samsung Electronics;《3GPP TSG-SA WG2 Meeting #129BIS S2-1812394》;20181120;全文 *

Also Published As

Publication number Publication date
CN113225440A (en) 2021-08-06

Similar Documents

Publication Publication Date Title
US11178062B2 (en) Orchestrating physical and virtual resources for delivering digital contents
CN110113498B (en) Bidirectional number protection method and device
CN113596191B (en) Data processing method, network element equipment and readable storage medium
MX2011006536A (en) Network node and method for controlling resources in a communication network.
WO2017036216A1 (en) Virtual number processing method and device
CN110225146B (en) Intranet and extranet mapping method and device, electronic equipment, medium and video conference system
CN112822061B (en) Method and system for exposing service to outside by edge node
CN111327668B (en) Network management method, device, equipment and storage medium
US11218536B2 (en) Processing data and operating a communications device
CN109358967B (en) ME platform APP instantiation migration method and server
WO2024002142A1 (en) Traffic forwarding method
CN104426968A (en) Data management method and device
CN113225440B (en) Management method of cloud communication network slices, computer equipment and storage medium
US8982902B1 (en) Backup server architecture in a VoIP system
CN111629031A (en) Cluster storage method, system, computer equipment and storage medium
CN113411363A (en) Uploading method of image file, related equipment and computer storage medium
CN111315037B (en) Communication link establishing method and device, computer equipment and storage medium
CN112616143B (en) Method and device for distributing communication numbers, electronic equipment and storage medium
US11616878B2 (en) System and method for dynamic redundant call recording
CN110213838B (en) Network connection method, device, computer equipment and storage medium
CN115915289A (en) Method, device, network element and medium for determining strategy or allocating resources of computing task
CN113093995A (en) Cloud disk data migration method and system
CN113515392A (en) RPC calling method, device, equipment and storage medium
US20240106792A1 (en) Data packet transmission method and apparatus, device, storage medium, and program product
CN110198360B (en) Number allocation method, device, storage medium and electronic device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant