CN117835335A - Method and device for determining network slice and network equipment - Google Patents

Method and device for determining network slice and network equipment Download PDF

Info

Publication number
CN117835335A
CN117835335A CN202211197482.5A CN202211197482A CN117835335A CN 117835335 A CN117835335 A CN 117835335A CN 202211197482 A CN202211197482 A CN 202211197482A CN 117835335 A CN117835335 A CN 117835335A
Authority
CN
China
Prior art keywords
target
network
slice
identifier
address
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.)
Pending
Application number
CN202211197482.5A
Other languages
Chinese (zh)
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.)
China Mobile Communications Group Co Ltd
China Mobile IoT Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile IoT 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 China Mobile Communications Group Co Ltd, China Mobile IoT Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to CN202211197482.5A priority Critical patent/CN117835335A/en
Publication of CN117835335A publication Critical patent/CN117835335A/en
Pending legal-status Critical Current

Links

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses a method, a device and network equipment for determining a network slice, and relates to the technical field of communication, wherein the method for determining the network slice comprises the following steps: receiving message information sent by a terminal, wherein the message information comprises a target IP address, a target slice identifier and a target function identifier; acquiring a target reserved resource according to the target IP address and the target slice identifier; acquiring a target service function of the target reserved resource according to the target function identifier; the method comprises the steps that network slice information is sent to the terminal, the network slice information comprises the target reserved resources and the target service function, the service function is used as a minimum logic unit of the network slice, the effect of low coupling and high cohesion is achieved, and the risk of multi-service concurrency of the network slice based on the two-dimensional address can be effectively avoided.

Description

Method and device for determining network slice and network equipment
Technical Field
The present disclosure relates to the field of internet of things, and in particular, to a method and an apparatus for determining a network slice, and a network device.
Background
In the prior art, a two-dimensional address-based network slice usually performs resource reservation according to service requirements, but in the current background of the popularization of the fifth Generation mobile communication protocol (5 th-Generation, 5G), the two-dimensional address-based network slice has a risk of multi-service concurrency.
Disclosure of Invention
The invention aims to provide a method, a device and network equipment for determining a network slice, so as to solve the problem of multi-service concurrency risk of the network slice based on a two-dimensional address in the prior art.
In order to achieve the above object, the present application provides a method for determining a network slice, which is applied to a network device, and includes:
receiving message information sent by a terminal, wherein the message information comprises a target IP address, a target slice identifier and a target function identifier;
acquiring a target reserved resource according to the target IP address and the target slice identifier;
acquiring a target service function of the target reserved resource according to the target function identifier;
and sending network slice information to the terminal, wherein the network slice information comprises the target reserved resource and the target service function.
Optionally, the acquiring the target reserved resource according to the destination IP address and the target slice identifier includes:
acquiring a destination network output interface related to the destination IP address;
and under the destination network output interface, acquiring the target reserved resource corresponding to the target slice identifier by inquiring the slice identifier and the reserved resource mapping table.
Optionally, the obtaining a destination network output interface related to the destination IP address includes:
and inquiring the destination network output interface corresponding to the destination IP address in a prestored IP inquiry routing table.
Optionally, the obtaining a destination network output interface related to the destination IP address includes:
under the condition that the destination IP address is not queried in a pre-stored IP query routing table, creating a routing mapping table item related to the destination IP address in the IP query routing table;
and acquiring the destination network output interface according to the created route mapping table item.
Optionally, the target reserved resource includes: subinterfaces, channels, or slices.
Optionally, the obtaining, according to the target function identifier, the target service function of the target reserved resource includes:
and under the target reserved resource, acquiring the target service function corresponding to the target function identifier by traversing a function identifier and service function mapping table.
Optionally, the method further comprises:
performing functional division on reserved resources corresponding to each slice identifier by using a channelized sub-interface reservation technology or a flexible sub-channel reservation technology;
and creating the function identification and service function mapping table according to the division result.
In order to achieve the above object, an embodiment of the present application further provides a network slice determining apparatus, which is applied to a network device, including:
the receiving module is used for receiving message information sent by the terminal, wherein the message information comprises a target IP address, a target slice identifier and a target function identifier;
the first acquisition module is used for acquiring a target reserved resource according to the target IP address and the target slice identifier;
the second acquisition module is used for acquiring the target service function of the target reserved resource according to the target function identifier;
and the sending module is used for sending network slice information to the terminal, wherein the network slice information comprises the target reserved resource and the target service function.
In order to achieve the above object, an embodiment of the present application further provides a network device, including: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the method of determining network slices as described in the first aspect.
In order to achieve the above object, an embodiment of the present application further provides a readable storage medium, where a program is stored, the program being executed by a processor to implement the method for determining a network slice according to the first aspect.
The technical scheme of the application has at least the following beneficial effects:
firstly, receiving message information sent by a terminal, wherein the message information comprises a target IP address, a target slice identifier and a target function identifier; secondly, acquiring a target reserved resource according to the target IP address and the target slice identifier; thirdly, acquiring a target service function of the target reserved resource according to the target function identifier; therefore, the service function is used as the minimum logic unit of the network slice, the effect of low coupling and high cohesion is achieved, the risk of multi-service concurrency can be effectively avoided, and the difficulty of challenges to network element deployment caused by the differentiated requirements of the service on the network architecture is reduced; and finally, sending network slice information to the terminal, wherein the network slice information comprises the target reserved resource and the target service function. Therefore, the transmission of message data by the terminal based on the exclusive network slice determined by the network slice information can be realized.
Drawings
FIG. 1 is a diagram of a network slice system architecture associated with a method of determining network slices according to an embodiment of the application;
fig. 2 is one of flow diagrams of a method for determining a network slice according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a three-dimensional address-based network slice address model in an embodiment of the present application;
FIG. 4 is a schematic diagram of a three-dimensional address-based network slice in an embodiment of the present application;
FIG. 5 is a schematic diagram of a resource partitioning strategy based on three-dimensional addresses in an embodiment of the present application;
FIG. 6 is a second flow chart of a method for determining network slices according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a determining device for network slice according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
Before explaining the method for determining the network slice in the embodiment of the present application, the related overall architecture is explained:
as shown in fig. 1, the 5G network slices include radio access network slices, mobile core network slices, and protocol (Internet Protocol, IP) bearer network slices for interconnections between networks. The method for determining the network slice in the embodiment of the application is mainly realized based on the IP bearing network.
The main functions of the IP bearer network slice are to provide customized network topology connections between network elements and services in the network slices of the radio access network and the core network, and differentiated service level agreement (Service Level Agreement, SLA) guarantees for the traffic of the different network slices. In addition, in order to implement end-to-end network slice collaborative management with the radio access network and the core network slice, and provide the network slice as a new service to vertical industry tenants, the carrier network also needs to provide an open network slice management interface for the outside for lifecycle management of the network slice.
The IP-bearer network slice architecture can be divided into three levels as a whole: a network slice forwarding layer, a network slice control layer and a network slice management layer.
1) Network slice management layer
The network slice management layer provides a life cycle management function of the network slice, and the network slice divides one physical network into a plurality of logic slice networks to meet the requirements of various different services, so that the management complexity of the slice networks is increased, and therefore, the automation and intelligent management of the slice networks is important, and the network slice management layer specifically comprises four stages of planning, deployment, maintenance and optimization of the network slice.
2) Network slice control layer
The network slice control layer is used for generating different logic network slice examples in the physical network, providing logic topology connection customized according to the requirement, and integrating the logic topology of the slice with network resources allocated for the slice to form the network slice meeting the specific service requirement. The control layer can be subdivided into a control plane and a data plane, wherein the control plane is mainly responsible for distributing, collecting and calculating the network fragmentation information, and the data plane is responsible for identifying and forwarding the network fragmentation resources.
3) Network slice forwarding layer
The network slice forwarding layer needs to have flexible and fine resource reservation capability, supports the division of forwarding resources in a physical network into a plurality of mutually isolated parts, and provides the mutually isolated parts for different network slices.
The method, the device and the network equipment for determining the network slice provided by the embodiment of the application are described in detail below through specific embodiments and application scenes thereof with reference to the accompanying drawings.
As shown in fig. 1, one of the flow diagrams of a method for determining a network slice according to an embodiment of the present application is shown, where the method is applied to a network device, and the method includes:
step 201, receiving message information sent by a terminal, wherein the message information comprises a destination IP address, a target slice identifier and a target function identifier;
in this step, the destination IP address is the IP address of the destination network device (e.g., destination server); the target slice identifier is an identifier of a network slice used for transmitting message data, wherein in the embodiment of the application, a physical network is previously sliced and each network slice is identified; the target function identifier is an identifier of various service functions, for example, the service functions comprise a voice function, a positioning function, a video function and the like;
step 202, obtaining a target reserved resource according to the target IP address and the target slice identifier;
step 203, obtaining a target service function of the target reserved resource according to the target function identifier; that is, when determining a network slice for transmitting message data for a terminal, the service function module is the minimum logic unit of the network slice; thus, the mutual independence of the business functions is realized.
And step 204, sending network slice information to the terminal, wherein the network slice information comprises the target reserved resource and the target service function.
Specifically, the network slicing method in the embodiment of the application is a network slicing scheme based on a three-dimensional address (IP address, slice identifier (Slice ID), function identifier (Function ID)), and aims to refine the logic nodes under the existing two-dimensional address, that is, to propose specific functions in each service scene one by one, so that each functional module becomes the minimum logic unit of the network slicing. Wherein a three-dimensional address-based network slice address model is shown in fig. 3.
Firstly, receiving message information sent by a terminal, wherein the message information comprises a target IP address, a target slice identifier and a target function identifier; secondly, acquiring a target reserved resource according to the target IP address and the target slice identifier, and acquiring a target service function of the target reserved resource according to the target function identifier; therefore, the service function module is used as the minimum logic unit of the network slice, so that the effect of low coupling and high cohesion can be achieved, the risk of multi-service concurrency is effectively avoided, and the difficulty of challenges to network element deployment caused by the differentiated requirements of services on the network architecture is reduced; and finally, sending network slice information to the terminal, wherein the network slice information comprises the target reserved resource and the target service function, so that the terminal transmits message data based on the exclusive network slice determined by the network slice information.
Here, it should also be noted that low coupling brings advantages to network slicing: the method is easy to change and reuse, so that the networking compatibility of different factories can be greatly improved, the problem that 5G network slices possibly face to mutual operation of different factories in actual deployment is solved, the problem that the contribution of network resources or slicing functions exists when equipment is networking due to the differentiation of equipment of different factories is solved, and greater value is brought to operators, various industries and various users.
In addition, in the embodiment of the application, the target function identifier is added in the message information, so that when the network slice is determined for the terminal, the service function module is used as the minimum logic unit of the network slice, and in the process of converting the network slice, the independence of the IP session and the user state function can be realized, and the connectivity of the IP session and the maintenance of the user state are ensured; that is, the method for determining the network slice in the embodiment of the present application can solve the problem that the home network slice cannot support the user to access the network in the roaming scenario, resulting in interruption of the user network, and thus, the connectivity of the IP session is maintained in the process of transferring the user to the default slice.
As an optional implementation manner, step 202, obtaining the target reserved resource according to the destination IP address and the target slice identifier, includes:
acquiring a destination network output interface related to the destination IP address; in this step, the destination network output interface is a network output interface of each network device on a path between a network device (source network device) executing the method for determining a network slice in the embodiment of the present application and a destination network device corresponding to a destination IP address;
specifically, when the destination network device corresponding to the destination IP address and the network device in the embodiment of the present application belong to the same local area network, the source network device in the embodiment of the present application has a path directly connected to the destination network device corresponding to the destination IP address, so that the destination network device can be directly obtained based on the destination IP address, thereby further obtaining a destination network output interface, where the destination network output interface is a network output interface of the destination network device.
And under the destination network output interface, acquiring the target reserved resource corresponding to the target slice identifier by inquiring the slice identifier and the reserved resource mapping table.
In this alternative implementation manner, the slice identifier and the reserved resource mapping table are pre-created correspondence tables, that is, after the physical network is subjected to network slicing, each network slice is identified, so that the mapping relationship between the slice identifier and the reserved resource is constructed according to the network slice identifier and the network resource allocated to the network slice, and specifically, a schematic diagram of the network slice based on the three-dimensional address is shown in fig. 4.
Here, it should be noted that, the network slicing of the physical network may specifically be based on a flexible ethernet (Flexible Ethernet, flexE) interface resource reservation technique or a channelized sub-interface resource reservation technique or a flexible sub-channel (Flex-channel) resource reservation technique to perform resource division, so as to implement network slicing.
As a specific implementation manner, the obtaining a destination network output interface related to the destination IP address includes:
and inquiring the destination network output interface corresponding to the destination IP address in a prestored IP inquiry routing table.
Here, it should be noted that, the specific implementation manner is applicable to a scenario that the destination network device corresponding to the destination IP address and the source network device are located in different local area networks; that is, when the two belong to different local area networks, the route between the source network device and the destination network device can be obtained by inquiring the IP inquiry routing table, so that the destination network output interface is obtained.
As another specific implementation manner, the obtaining the destination network output interface corresponding to the destination IP address includes:
under the condition that the destination IP address is not queried in a pre-stored IP query routing table, creating a routing mapping table item related to the destination IP address in the IP query routing table;
and acquiring the destination network output interface according to the created route mapping table item.
That is, when there is no path between the source network device and the destination network device in the IP routing lookup table, a path between the source network device and the destination network device may be newly established by learning, thereby further obtaining the destination network output interface.
Specifically, the target reserved resource includes: subinterfaces, channels, or slices. That is, the target reserved resource in the embodiment of the present application may be referred to as a subinterface, or as a channel, or as a slice.
As an optional implementation manner, step 203, according to the target function identifier, obtains a target service function of the target reserved resource, including:
and under the target reserved resource, acquiring the target service function corresponding to the target function identifier by traversing a function identifier and service function mapping table.
In the alternative implementation manner, by traversing the function identifier and service function mapping table to be a mapping table which is created in advance under the target reserved resource, specific service implementation under the target reserved resource can be obtained, for example, a monitoring service function and a voice service function under an intelligent port service scene; video business functions in smart medical business scenarios, and the like.
Further, as an alternative implementation, the method further includes:
performing functional division on reserved resources corresponding to each slice identifier by using a channelized sub-interface reservation technology or a flexible sub-channel (Flex-channel) reservation technology;
in the step, after the reserved resources are functionally divided, each functional module is identified to obtain the functional identification of each functional module; i.e. the function identity is obtained by resource partitioning of the network slice using the relevant resource reservation technique (channelisation sub-interface resource reservation technique or Flex-channel resource reservation technique).
And creating the function identification and service function mapping table according to the division result.
Here, it should be noted that, in the embodiment of the present application, the function identifier is created based on the slice identifier, but the function identifier may be applied to different slice identifiers, that is, the function identifier may be autonomously adapted based on the difference of the slice identifiers, so as to complete function modularization in each service scenario, thereby simplifying complexity of network slice deployment. A schematic diagram of the resource partitioning strategy based on the three-dimensional address is shown in fig. 5.
According to the method for determining the network slice, the service function module is used as the minimum logic unit of the network slice, on one hand, the IP session and the user state function are independent, and in the process of converting the network slice, the influence on the IP session and the user state is reduced as much as possible; on the other hand, compared with the existing two-dimensional address-based network slicing, the service scene is used as a basic unit of the network slicing to easily generate the risk of multi-service concurrency, and the embodiment of the application realizes the maximum decoupling of service functions and avoids the multiplexing risk caused by hardware differentiation; on the other hand, the problems that in the prior art, the problems that in actual deployment, the mutual operation of slices of different factories is possibly faced, and the sharing of network resources or slice functions exists risk due to the differentiation among equipment of different factories when the equipment is networked are solved.
The implementation procedure of the network slice determination method according to the embodiment of the present application is described below with reference to fig. 6:
step 601, the device sends a network message; in this step, the device may be the aforementioned terminal, such as a camera, a smart meter, etc.; namely, the user equipment which needs to transmit message data with the network; the network message is the message information and comprises a target IP address, a target slice identifier and a target function identifier;
step 602, a server in a network receives a network message; in this step, the server in the network is the network device executing the method for determining the network slice in the embodiment of the present application, where the server in the network and the device may belong to the same local area network or different local area networks;
step 603, inquiring a routing table according to the destination IP in the message to obtain a network output interface; the method specifically comprises the steps that a server in a network queries a pre-established IP query routing table according to a destination IP address in a network message to obtain a network output interface of each hop server on a path between the server in the network and the destination server;
step 604, determining a resource reservation sub-interface or channel under the network output interface according to the Slice ID mapping table of the Slice interface queried by the Slice ID; the method specifically comprises the following steps: a server in a network queries a slice identifier and a reserved resource mapping table under a network output interface to obtain a sub-interface or a channel reserved under the network output interface;
step 605, traversing the Function ID sub-resources in the sub-interface table according to the Function ID to acquire a service specific implementation scheme under the reserved resources; the method specifically comprises the following steps: traversing a mapping table of Function ID and service functions according to the obtained sub-interfaces/channels/slices, and determining specific service implementation under the sub-interfaces/channels/slices;
step 606, the server forwards the message according to the resource channels after one-to-one correspondence;
in step 607, the device obtains the corresponding network slice resource.
As shown in fig. 7, an embodiment of the present application further provides a network slice determining apparatus, which is applied to a network device, including:
a receiving module 701, configured to receive message information sent by a terminal, where the message information includes a destination IP address, a target slice identifier, and a target function identifier;
a first obtaining module 702, configured to obtain a target reserved resource according to the destination IP address and the target slice identifier;
a second obtaining module 703, configured to obtain, according to the target function identifier, a target service function of the target reserved resource;
and a sending module 704, configured to send network slice information to the terminal, where the network slice information includes the target reserved resource and the target service function.
Optionally, the first obtaining module 702 includes:
the first acquisition sub-module is used for acquiring a destination network output interface related to the destination IP address;
and the second acquisition sub-module is used for acquiring the target reserved resource corresponding to the target slice identifier by inquiring the slice identifier and the reserved resource mapping table under the destination network output interface.
Optionally, the first obtaining submodule is configured to: and inquiring the destination network output interface corresponding to the destination IP address in a prestored IP inquiry routing table.
Optionally, the first obtaining submodule includes:
a creating unit, configured to create a route mapping table item related to the destination IP address in the IP lookup routing table, in a case where the destination IP address is not queried in a pre-stored IP lookup routing table;
and the acquisition unit is used for acquiring the destination network output interface according to the created route mapping table item.
Optionally, the target reserved resource includes: subinterfaces, channels, or slices.
Optionally, the second obtaining module 703 is specifically configured to: and under the target reserved resource, acquiring the target service function corresponding to the target function identifier by traversing a function identifier and service function mapping table.
Optionally, the apparatus further comprises:
the function division module is used for carrying out function division on reserved resources corresponding to each slice identifier by utilizing a channelized sub-interface reservation technology or a flexible sub-channel reservation technology;
and the creating module is used for creating the function identification and service function mapping table according to the division result.
It should be noted that, the determining device for network slice provided in this embodiment of the present application can implement all the method steps implemented in the determining method embodiment for network slice described in fig. 2, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.
As shown in fig. 8, the embodiment of the present application further provides a network device, including a transceiver 810, a memory 820, a processor 800, and a computer program stored in the memory 820 and running on the processor 800, where when the processor 800 executes the computer program, the processes of the embodiment of the method for determining a network slice described above are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no redundant description is given here.
The transceiver 810 is configured to receive and transmit data under the control of the processor 800.
Wherein in fig. 8, a bus architecture may comprise any number of interconnected buses and bridges, and in particular, one or more processors represented by processor 800 and various circuits of memory represented by memory 820, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 810 may be a plurality of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 800 in performing operations.
The embodiment of the present application further provides a readable storage medium, where a program is stored, where the program, when executed by a processor, implements each process of the network slice determination method embodiment described above, and the same technical effect can be achieved, so that repetition is avoided, and no further description is given here. Wherein the readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
While the foregoing is directed to the preferred embodiments of the present application, it should be noted that modifications and adaptations to those embodiments may occur to one skilled in the art and that such modifications and adaptations are intended to be comprehended within the scope of the present application without departing from the principles set forth herein.

Claims (10)

1. A method for determining a network slice, applied to a network device, comprising:
receiving message information sent by a terminal, wherein the message information comprises a target IP address, a target slice identifier and a target function identifier;
acquiring a target reserved resource according to the target IP address and the target slice identifier;
acquiring a target service function of the target reserved resource according to the target function identifier;
and sending network slice information to the terminal, wherein the network slice information comprises the target reserved resource and the target service function.
2. The method of claim 1, wherein the obtaining a target reserved resource according to the destination IP address and the target slice identifier comprises:
acquiring a destination network output interface related to the destination IP address;
and under the destination network output interface, acquiring the target reserved resource corresponding to the target slice identifier by inquiring the slice identifier and the reserved resource mapping table.
3. The method of claim 2, wherein the obtaining a destination network out interface associated with the destination IP address comprises:
and inquiring the destination network output interface corresponding to the destination IP address in a prestored IP inquiry routing table.
4. The method of claim 2, wherein the obtaining a destination network out interface associated with the destination IP address comprises:
under the condition that the destination IP address is not queried in a pre-stored IP query routing table, creating a routing mapping table item related to the destination IP address in the IP query routing table;
and acquiring the destination network output interface according to the created route mapping table item.
5. The method of claim 2, wherein the target reserved resource comprises: subinterfaces, channels, or slices.
6. The method according to claim 1, wherein the obtaining the target service function of the target reserved resource according to the target function identifier includes:
and under the target reserved resource, acquiring the target service function corresponding to the target function identifier by traversing a function identifier and service function mapping table.
7. The method of claim 6, wherein the method further comprises:
performing functional division on reserved resources corresponding to each slice identifier by using a channelized sub-interface reservation technology or a flexible sub-channel reservation technology;
and creating the function identification and service function mapping table according to the division result.
8. A network slice determination apparatus, applied to a network device, comprising:
the receiving module is used for receiving message information sent by the terminal, wherein the message information comprises a target IP address, a target slice identifier and a target function identifier;
the first acquisition module is used for acquiring a target reserved resource according to the target IP address and the target slice identifier;
the second acquisition module is used for acquiring the target service function of the target reserved resource according to the target function identifier;
and the sending module is used for sending network slice information to the terminal, wherein the network slice information comprises the target reserved resource and the target service function.
9. A network device, comprising: a processor, a memory and a program stored on the memory and executable on the processor, which when executed by the processor implements the method of determining network slices as claimed in any one of claims 1 to 7.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a program, which when executed by a processor, implements the network slice determination method according to any one of claims 1 to 7.
CN202211197482.5A 2022-09-29 2022-09-29 Method and device for determining network slice and network equipment Pending CN117835335A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211197482.5A CN117835335A (en) 2022-09-29 2022-09-29 Method and device for determining network slice and network equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211197482.5A CN117835335A (en) 2022-09-29 2022-09-29 Method and device for determining network slice and network equipment

Publications (1)

Publication Number Publication Date
CN117835335A true CN117835335A (en) 2024-04-05

Family

ID=90504948

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211197482.5A Pending CN117835335A (en) 2022-09-29 2022-09-29 Method and device for determining network slice and network equipment

Country Status (1)

Country Link
CN (1) CN117835335A (en)

Similar Documents

Publication Publication Date Title
CN110326345B (en) Method, device and system for configuring network slice
US8295204B2 (en) Method and system for dynamic assignment of network addresses in a communications network
CN102577257B (en) Virtual local area network identity transformation method and apparatus
CN107404512B (en) Resource subscription method, resource subscription device and resource subscription system
CN106941437B (en) Information transmission method and device
CN107342925B (en) Message transmission method and device
CN103944826A (en) Entry aggregation method in SPBM (shortest path bridging MAC mode) network and equipment
CN104283722A (en) SDN link state information collecting method and device
CN102185766A (en) Unicast forwarding method and forwarding equipment for responding messages by DHCP (Dynamic host configuration protocol) server
CN101345657B (en) Method and system for cluster management of multiple network elements based on simple network management protocol
CN101766007B (en) Methods and systems for providing RACF configuration information
CN112887117A (en) Method, device and medium for accessing and configuring network slice
CN101437297A (en) Method, apparatus and system for processing business
WO2018045949A1 (en) Message transmission method, device and network system
CN105050028A (en) Method and device for controlling household appliances
CN114513447A (en) SD-WAN (secure digital-to-Wide area network) service issuing system, method, device and network equipment
CN109548056B (en) Communication method and system based on ROS master-slave node manager
CN117835335A (en) Method and device for determining network slice and network equipment
CN112910959B (en) SDN-based network interconnection method for multiple Kubernetes clusters
CN110474781B (en) Method and device for forwarding multicast data
CN115242713A (en) IPV 6-based segmented routing message forwarding method, configuration method and equipment
CN102801618A (en) Method and device for determining three-layered data path in Ethernet ring network
CN105072150A (en) Service call method, and service call method and device through proxy gateway
WO2017198088A1 (en) Resource subscription method, resource subscription device, and resource subscription system
CN109587064A (en) A kind of IPv4/IPv6 address management system and method

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