CN114553701B

CN114553701B - Slice identifier management method, device, equipment and medium

Info

Publication number: CN114553701B
Application number: CN202210149431.9A
Authority: CN
Inventors: 孙颖; 罗光峰; 方宇; 王晓韵; 王飞飞; 曹亚平
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2022-02-18
Filing date: 2022-02-18
Publication date: 2024-05-24
Anticipated expiration: 2042-02-18
Also published as: CN114553701A

Abstract

The disclosure provides a slice identifier management method, device, equipment and medium, and relates to the technical field of communication. The method comprises the following steps: receiving a session connection request sent by a terminal, wherein the session connection request comprises an application ID of a terminal service; searching a target slice ID matched with the application ID according to a preset application slice identification table; and determining a target slice ID according to the relation between the target slice ID and the default slice ID subscribed by the terminal, so that the terminal service is carried in a transmission channel corresponding to the target slice ID. The present disclosure provides a slice identifier management method, device, equipment and medium, which adds a slice identifier management module based on a 5G application service to a 5G core network, so as to realize that a terminal is carried in different slice transmission channels according to different services, and finally realize the SLA differentiation of the services.

Description

Slice identifier management method, device, equipment and medium

Technical Field

The disclosure relates to the technical field of communication, and in particular relates to a slice identifier management method, a slice identifier management device, electronic equipment and a computer readable storage medium.

Background

The dependency of modern information society on the internet is gradually deepened, and the requirements on the reliability and the usability of the network are also higher and higher, for example, the fields of security, finance, data centers and the like. The network is built by related devices and transmission lines, and as the degree of IP (Internet Protocol, protocol of interconnection between networks, i.e. internet protocol) of the network increases, the usage proportion of data network devices in the network (including fixed networks and mobile networks) also increases gradually, so that the requirements on the reliability and availability of the data network devices are also higher and higher.

With the continuous diversification of the services of the fifth generation mobile communication system 5G, a network slicing (Network Slicing, NS) technology is introduced into the 5G, and the network slicing technology allows the network (the core network and the radio access network) to be divided into a plurality of slices (slices), so that different services are transmitted in different transmission channels and do not interfere with each other.

As the differentiated requirements of the service level agreements (SERVICE LEVEL AGREEMENT, SLA) are increasingly prominent, the network resource environments required by different performance indexes are different, and operators divide slice resources aiming at different scenes and industry requirements in the 5G network according to the different performance index requirements. Then, there may be different 5G services for the same terminal to be carried in different slicing channels, and how to correctly and flexibly match to different slicing resources according to different 5G services is an urgent problem to be solved.

In the related art, the network slice identifier S-NSSAI is used to identify the end-to-end logically or physically isolated 5G network resource, however, there are some problems in this manner that one end user can only use one slice identifier, i.e., one end user can only use one slice under the condition that subscription information is unchanged, and cannot flexibly switch slice channels. Since vendor slicing technology is still immature, although signing up for multiple slices can be supported, since the terminal routing policy (UE Route Selection Policy, URSP) is immature, only one slice can be actually used finally, and switching cannot be flexibly performed according to customer services.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The disclosure provides a slice identifier management method, device, equipment and medium, which at least overcome the problem that different services cannot switch slice channels when subscription information provided in the related technology is unchanged to a certain extent.

Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.

According to one aspect of the present disclosure, there is provided a slice identifier management method applied to a core network side, the method including:

Receiving a session connection request sent by a terminal, wherein the session connection request comprises an application ID of a terminal service;

searching a target slice ID matched with the application ID according to a preset application slice identification table;

And determining a target slice ID according to the relation between the target slice ID and the default slice ID subscribed by the terminal, so that the terminal service is carried in a transmission channel corresponding to the target slice ID.

In one embodiment of the present disclosure, the application slice identifier table is preset in a slice identifier management module of the core network, and a mapping relationship between an application ID and a slice ID of the terminal service is stored in the application slice identifier table.

In one embodiment of the present disclosure, the determining the destination slice ID according to the relationship between the target slice ID and the default slice ID, so that the terminal service is carried in the transmission channel corresponding to the destination slice ID includes:

And when the target slice ID and the default slice ID are different, issuing the target slice ID to the terminal as a target slice ID so that the terminal reinitiates a session connection request carrying the target slice ID.

And when the target slice ID is the same as the default slice ID, issuing a terminal IP to the terminal, and establishing a transmission channel between a base station and a user plane function UPF of a core network so that the user data message is transmitted through the transmission channel.

When the target slice ID matched with the application ID is not queried, taking the default slice ID as a target slice ID, and updating the application slice identification table;

and issuing a terminal IP to the terminal, and establishing a transmission channel between the base station and the UPF of the core network so as to transmit the user data message through the transmission channel.

According to another aspect of the present disclosure, there is provided a slice identifier management apparatus applied to a core network side, the apparatus including:

the first receiving module is used for receiving a session connection request sent by the terminal, wherein the session connection request comprises an application ID of the terminal service;

The matching module is used for searching a target slice ID matched with the application ID according to a preset application slice identification table;

And the determining module is used for determining a target slice ID according to the relation between the target slice ID and the default slice ID subscribed by the terminal so as to enable the terminal service to be borne in a transmission channel corresponding to the target slice ID.

According to another aspect of the present disclosure, there is provided a slice identifier management method applied to a terminal side, the method including:

Sending a session connection request to a core network, wherein the session connection request comprises an application ID of a terminal service;

And when receiving the destination slice ID issued by the core network, resending a session connection request carrying the destination slice ID to the core network so as to enable terminal service to be borne in a transmission channel corresponding to the destination slice ID.

According to another aspect of the present disclosure, there is provided a slice identifier management apparatus applied to a terminal side, the apparatus including:

a request sending module, configured to send a session connection request to a core network, where the session connection request includes an application ID of a terminal service;

the second receiving module is used for receiving the target slice ID issued by the core network in real time;

And the request sending module is further used for resending a session connection request carrying the target slice ID to the core network when the second receiving module receives the target slice ID issued by the core network, so that the terminal service is carried in a transmission channel corresponding to the target slice ID.

According to another aspect of the present disclosure, there is provided an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the slice identification management method described above via execution of the executable instructions.

According to another aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the disaster recovery method described above.

According to the slice identifier management method, device, equipment and medium provided by the embodiment of the disclosure, by adding the slice identifier management module based on the 5G application service to the 5G core network, the terminal is carried in different slice transmission channels according to different services, so that different services are carried in different network resource environments, and finally differentiation of service level agreements SLAs of the services is realized; the service level slice identification is switched through the 5G control plane signaling interaction mode, a terminal side is not required to be modified, the problem that slicing technologies of terminal manufacturers URSP and the like are not mature is solved, the association relation of the terminal applied to slices is flexibly designed, different slices can be selected by a terminal user according to requirements of reliability, time delay and the like of different services, the effective utilization rate of network resources is greatly improved, and the use value of an operator network is effectively improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.

FIG. 1 illustrates a system architecture diagram of a communication system in an embodiment of the present disclosure;

Fig. 2 shows a system architecture diagram of a communication system in a further embodiment of the present disclosure;

Fig. 3 is a flowchart illustrating a slice identifier management method applied to a core network side in an embodiment of the present disclosure;

fig. 4 illustrates a network element interaction diagram for slice identifier management and updating in an embodiment of the disclosure;

Fig. 5 is a flowchart illustrating a slice identifier management method applied to a core network side according to still another embodiment of the present disclosure;

fig. 6 shows a signaling flow diagram of a slice identifier management method applied to a core network side in an embodiment of the present disclosure;

fig. 7 is a flowchart of a slice identifier management method applied to a core network side in another embodiment of the present disclosure;

fig. 8 is a schematic diagram of a slice identifier management apparatus applied to a core network side in an embodiment of the disclosure;

Fig. 9 shows a flowchart of a slice identifier management method applied to a terminal side in an embodiment of the present disclosure;

Fig. 10 shows a schematic diagram of a slice identifier management apparatus applied to a terminal side in an embodiment of the present disclosure;

Fig. 11 shows a block diagram of an electronic device in an embodiment of the disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.

Fig. 1 illustrates a system architecture diagram of an exemplary communication system that may be applied to a slice identity management method or slice identity management apparatus of an embodiment of the present disclosure.

As shown in fig. 1, a communication system may include a terminal 10, a network 20, and a core network 30.

The network 20 may be a wired network or a wireless network, and is a medium used to provide a communication link between the terminal 10 and the core network 30.

Alternatively, the wireless network or wired network described above uses standard communication techniques and/or protocols. The network 20 is typically the Internet, but may be any network including, but not limited to, a local area network (Local Area Network, LAN), metropolitan area network (Metropolitan Area Network, MAN), wide area network (Wide Area Network, WAN), a mobile, wired or wireless network, a private network, or any combination of virtual private networks. In some embodiments, data exchanged over the network is represented using techniques and/or formats including HyperText Mark-up Language (HTML), extensible markup Language (Extensible MarkupLanguage, XML), and the like. All or some of the links may also be encrypted using conventional encryption techniques such as secure sockets layer (Secure Socket Layer, SSL), transport layer security (Transport Layer Security, TLS), virtual private network (Virtual Private Network, VPN), internet protocol security (Internet Protocol Security, IPsec), etc. In other embodiments, custom and/or dedicated data communication techniques may also be used in place of or in addition to the data communication techniques described above.

It will be appreciated that for a wireless communication system, it is a network that provides wireless communication functionality. The communication system may employ different communication techniques such as code division Multiple access (Code Division Multiple Access, CDMA), wideband code division Multiple access (Wideband Code Division Multiple Access, WCDMA), time division Multiple access (Time Division Multiple Access, TDMA), frequency division Multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division Multiple access (Orthogonal Frequency-division Multiple Access, OFDMA), single carrier frequency division Multiple access (SINGLE CARRIER FDMA, SC-FDMA), carrier sense Multiple access/collision avoidance (CARRIER SENSE Multiple ACCESS WITH Collision Avoidance). Networks may be classified into 2G (generation) networks, 3G networks, 4G networks, or future evolution networks, such as 5G networks, 5G networks simply referred to as networks or systems, according to factors such as capacity, rate, delay, etc. of different networks. In the present disclosure, the network 20 may include a radio access network (Radio Access Network, RAN), and the network 20 includes a network device, which may be, for example, a radio access network node; the core network 30 includes core network devices. Wherein the radio access network node may also become a base station. The network 20 may provide network services to the terminal through network devices, and different operators may provide different network services to the terminal 10, and may also be understood that different operators correspond to different operator networks.

Further, the network 20 may communicate with the core network through a bearer network, which includes: a Synchronous digital hierarchy system (Synchronous DIGITAL HIERARCHY, SDH), a packet transport network (Packet Transport Network, PTN), an optical transport network (Optical Transport Network, OTN), etc.; wherein, the 2G service is mainly carried on SDH, and the 3G service is mainly carried on PTN.

The network structure of SDH, PTN, OTN comprises a core layer, a converging ring and an access ring, wherein the core layer of SDH is mainly carried by bare optical fibers, the converging ring of SDH is generally carried by optical cables, the long-distance section is carried by OTN, and the access ring of SDH is carried by optical cables; the core layer of the PTN is borne by an OTN or a bare optical fiber, the convergence ring of the PTN is generally borne by the OTN or an optical cable, and the access ring of the PTN is borne by the optical cable; therefore SDH, PTN, OTN are relatively independent.

The terminal 10, which may be a user device, a mobile terminal, a terminal device, a mobile station, etc., is a device that provides voice and/or data connectivity to a user, and the terminal 10 may be a variety of electronic devices including, but not limited to, smart phones, tablet computers, laptop portable computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc.

Alternatively, the clients of the applications installed in different terminals 10 are the same or clients of the same type of application based on different operating systems. The specific form of the application client may also be different based on the different terminal platforms, for example, the application client may be a mobile phone client, a PC client, etc.

The slice identification management method provided by the embodiment of the disclosure is applied to a communication network which introduces a network slicing technology, wherein different services can be transmitted in different slices by applying the network slicing technology, and the different services are not mutually interfered. Fig. 2 shows a system architecture diagram of a further communication system in this embodiment, and as shown in fig. 2, a slice identifier management module is disposed in the 5G core network, where the slice identifier management module may be configured with a session management function (Session Management Function, SMF) network element, or may be deployed separately. The slice identifier management module stores a slice identifier corresponding relation between an application ID and a slice ID, the 5G core network inquires the slice ID matched with the application ID from the slice identifier management module according to the application ID carried in a session connection request initiated by the 5G terminal and transmits the slice ID to the 5G terminal, the 5G terminal carries a correct slice ID to resend the session connection request, and the wireless network, the bearing network and the 5G core network can sense the user slice ID and bear user services in a special slice channel, so that the 5G terminal can flexibly switch slice identifier information carried by the 5G terminal when using different applications, and the method can be applied to scenes of different grades of guarantee required by different services in the 5G network, scenes of shielding manufacturer terminals to directly realize flexible switching of slices, scenes of requiring flexible customization of slices and services under 5G scenes, and the like.

The present exemplary embodiment will be described in detail below with reference to the accompanying drawings and examples.

First, in the embodiments of the present disclosure, a slice identifier management method is provided, and the method may be executed by any system having computing processing capability.

Fig. 3 shows a flowchart of a slice identifier management method in an embodiment of the present disclosure, and as shown in fig. 3, the slice identifier management method provided in the embodiment of the present disclosure is applied to a core network side, and the method includes the following steps:

S302, receiving a session connection request sent by a terminal, wherein the session connection request comprises an application ID of a terminal service.

Specifically, when the user uses the 5G service, the terminal carries an application ID and a data network name (Data Network Name, DNN) of the 5G terminal service, where the DNN includes a network ID and an operator ID, which are used to identify an external data network, and the user can configure the DNN on the AR to access to the corresponding data network.

The session connection request in S302 may be a data communication request or a voice communication request, and the different types of requests are implemented by different applications and distinguished by the application ID of the terminal service.

S304, searching a target slice ID matched with the application ID according to a preset application slice identification table.

Specifically, a slice identifier management module is provided in the core network in this embodiment, and the slice identifier management module stores the application slice identifier table, where a mapping relationship between an application ID of a terminal service and a slice ID is stored in the application slice identifier table.

It should be noted that, after the SMF receives the session connection request of the terminal sent by the AMF, the SMF sends a query request to the slice identifier management module, where the query request carries information such as DNN, a default slice ID, and an application ID of the terminal service, and according to an application slice identifier table stored in the slice identifier management module, the SMF searches for a target slice ID corresponding to the application ID of the terminal service, and the slice identifier management module feeds back the queried target slice ID to the SMF.

In this embodiment, before the 5G service transmission, the method further includes: when a slice is newly added, the configuration information of each network element in the core network and the application slice identification table are updated to support the newly added slice information.

In a communication system, network elements of a core Network mainly include a Network storage function (NF Repository Function, NRF), a policy control function (Policy Control Function, PCF), a Unified Data management (Unified DATA MANAGEMENT, UDM), AN application function (Application Function, AF), AN authentication service function (Authentication Server Function, AUSF), AN Access and mobility management function (ACCESSAND MOBILITY MANAGEMENT FUNCTION, AMF), AN SMF, a User Equipment (UE), AN Access Network (R) AN, a User plane function (Userplane Function, UPF), a Data Network (Data Network, DN).

Fig. 4 shows a network element interaction diagram of slice identifier management and update in this embodiment, as shown in fig. 4, when a slice is newly added, supported slice identifier information is added in NSSF, and the AMF requests NSSF for the newly added slice information and configures the supported slice information; the AMF acquires a user slice signing policy from the UDM/AUSF, wherein the AMF performs user access authentication based on IMSI selection AUSF, adds slice selection auxiliary information (Network Slice Selection Assistant Information, NSSAI) of a network element in the UDM, and signs a slice; the AMF inquires SMF/PCF to NRF through the information of slice ID, DNN, etc., the AMF sends request access strategy to PCF, PCF increases the slice mark supported synchronously; the AMF sends the added supported slice identifier to the SMF, the SMF sends the added slice identifier to the slice identifier management module to store the newly added slice identifier, the SMF acquires the session policy from the PCF and inquires the PCF from the NRF, and the supported slice identifier is added in the PCF; the AMF communicates with the terminal, the terminal initiates a session connection request to the base station gNB carrying information such as a designated slice ID, DNN and the like, the designated slice ID is bound with a bearing network VLAN in the gNB, after the gNB selects the AMF corresponding to the designated slice ID, the AMF sends the session connection request to the SMF, the SMF issues session information and strategy information and informs the UPF of wireless allocation tunnel information according to the designated slice ID, supported slice identification is added in the UPF, the binding of the slice and a corresponding slice resource channel is added, and the UPF matches the received session information, strategy information and tunnel information with the corresponding DN, so that a transmission channel is established to complete the configuration of the network element.

S306, determining the target slice ID according to the relation between the target slice ID and the default slice ID subscribed by the terminal, so that the terminal service is carried in the transmission channel corresponding to the target slice ID.

When the terminal initiates a session connection request to the base station by carrying information such as application ID and DNN of the terminal service, the session connection request is sent to the core network through the base station, and the AMF in the core network receives the session connection request.

Specifically, after the AMF receives the session connection request, the AMF queries the UDM for a default slice ID subscribed by the user, each user subscribes to a default slice, and the UDM feeds back the query result to the AMF.

Further, after the AMF receives the query result of the UDM, the AMF sends a session connection request of the terminal to the SMF, carrying information such as DNN, default slice ID, and application ID of the terminal service.

In this embodiment, the SMF determines, according to the received relationship between the target slice ID and the default slice ID, the destination slice ID corresponding to the application ID of the terminal service, so that the terminal service is carried in the transmission channel corresponding to the destination slice ID, thereby achieving the purpose of selecting the slice transmission channel according to the service.

According to the slice identification management method provided by the embodiment of the disclosure, the slice identification management module based on the 5G application service is added to the 5G core network, so that the terminal is carried in different slice transmission channels according to different services, a user can enter different slice channels according to different application services, the differentiated guarantee of different services of the same terminal user in the 5G network can be realized, the diversified guarantee requirements of the user are met, different services are carried in different network resource environments, the differentiation of service level protocol SLA of the service is finally realized, the switching of service level slice identifications is realized through a 5G control plane signaling interaction mode, the terminal side is not required to be modified, and the problem that the slicing technology of terminal manufacturer URSP and the like is not mature is solved.

Fig. 5 shows a flowchart of a slice identifier management method applied to a core network side in yet another embodiment of the present disclosure. As shown in fig. 5, the step S308 determines the destination slice ID according to the relationship between the destination slice ID and the default slice ID, so that the terminal service is carried in the transmission channel corresponding to the destination slice ID, including:

S502, when the target slice ID and the default slice ID are different, the target slice ID is issued to the terminal as the target slice ID, so that the terminal reinitiates a session connection request carrying the target slice ID.

Fig. 6 shows a signaling flow chart of a slice identifier management method applied to a core network side in an embodiment of the disclosure, as shown in fig. 6, when a terminal UE sends a session connection request to a gNB, the gNB sends the session connection request to an AMF, the AMF queries a default slice ID subscribed by a user to a UDM and receives a feedback result of the UDM, the UDM sends the session connection request carrying the default slice ID to an SMF, the SMF requests a target slice ID corresponding to an application ID of a query terminal service to a slice identifier management module, and receives a query result fed back by the slice identifier management module.

When the SMF judges that the target slice ID and the default slice ID are different, the SMF issues the target slice ID to the AMF as a target slice ID, and the AMF issues the target slice ID through the gNB.

When the gNB receives the target slice ID issued by the core network, the gNB re-initiates a session connection request carrying information such as an application ID, a target slice ID, DNN and the like of the terminal service, at the moment, the application ID is matched with the target slice ID, namely a transmission channel is determined, so that the SMF initiates the session request to the UPF, the UPF issues the terminal IP to activate the session, a GPRS (Generic Protocol Radio System, GPRS) tunneling protocol (GPRS Tunnelling Protocol, GTP) transmission channel is established between the gNB and the UPF, and the user data message starts normal transmission through the GTP transmission channel.

According to the slice identification management method provided by the embodiment of the disclosure, when the target slice ID matched with the application ID is different from the default slice ID, the target slice ID is used as the target slice ID to issue the terminal, the terminal carries the target slice ID to initiate the session connection request again, different services are loaded in different network resource environments, SLA differentiation of the services is realized, and through designing the association relationship between the terminal application and the slice, the terminal user can select different slices to use according to the reliability, time delay and other requirements of different services, so that the effective utilization rate of network resources is greatly improved, and the use value of an operator network is improved.

In one embodiment of the present disclosure, the step S308 determines the destination slice ID according to the relationship between the target slice ID and the default slice ID, so that the terminal service is carried in the transmission channel corresponding to the destination slice ID, including:

And when the target slice ID is the same as the default slice ID, issuing a terminal IP to the terminal, and establishing a transmission channel between the base station and the UPF so that the user data message is transmitted through the transmission channel.

Specifically, when the target slice ID is the same as the default slice ID, the SMF initiates a session request to the UPF, and the UPF issues the terminal IP to activate the session, and a GTP transmission channel is established between the gNB and the UPF, so that the user data packet starts to be normally transmitted through the GTP transmission channel.

In one embodiment of the present disclosure, as shown in fig. 7, the determining, in step S308, the destination slice ID according to the relationship between the destination slice ID and the default slice ID, so that the terminal service is carried in the transmission channel corresponding to the destination slice ID includes:

S702, when the target slice ID matched with the application ID is not queried, taking the default slice ID as the target slice ID, and updating the application slice identification table;

S704, issuing a terminal IP to the terminal, and establishing a transmission channel between the base station and the UPF of the core network so that the user data message is transmitted through the transmission channel.

When the SMF receives the target slice ID matched with the application ID as a feedback result of the slice identification management module, the SMF takes the default slice ID as the target slice ID, and the slice identification management module stores the application ID and the default slice ID so as to finish updating the application slice identification table.

Further, the SMF sends a session connection request to the UPF carrying an application ID, a default slice ID, DNN, etc., after the UPF receives the session connection request, issues a terminal IP address to the SMF, and the SMF issues the terminal IP address to the terminal through the AMF and the gNB, and after the GTP transmission channel is established, service message transmission is performed between the terminal and the base station, and the service message data is normally transmitted through the GTP transmission channel.

According to the slice identification management method provided by the embodiment of the disclosure, when the target slice ID matched with the application ID is not queried, the target slice ID is used as the target slice ID, the application ID and the target slice ID are updated into the application slice identification table, and meanwhile, the terminal IP is issued to the terminal, so that different services are carried in different network resource environments, SLA differentiation of the services is realized, through designing the association relationship between the terminal application and the slice, the terminal user can select different slices to use according to the requirements of reliability, time delay and the like of the different services, the effective utilization rate of network resources is greatly improved, and the use value of an operator network is improved.

Based on the same inventive concept, the embodiment of the disclosure also provides a slice identifier management device, as described in the following embodiment. Since the principle of solving the problem of the embodiment of the device is similar to that of the embodiment of the method, the implementation of the embodiment of the device can be referred to the implementation of the embodiment of the method, and the repetition is omitted.

Fig. 8 is a schematic diagram of a slice identifier management apparatus according to an embodiment of the disclosure, as shown in fig. 8, applied to a core network side, where the apparatus includes:

a first receiving module 801, configured to receive a session connection request sent by a terminal, where the session connection request includes an application ID of a terminal service;

A matching module 802, configured to search a target slice ID matched with the application ID according to a preset application slice identifier table;

and the determining module 803 is configured to determine a destination slice ID according to a relationship between the destination slice ID and a default slice ID that the terminal has subscribed to, so that the terminal service is carried in a transmission channel corresponding to the destination slice ID.

It should be noted that the application slice identifier table is preset in the slice identifier management module of the core network, where the application slice identifier table stores a mapping relationship between an application ID and a slice ID of the terminal service.

In one embodiment of the present disclosure, the apparatus further comprises an update module and a transmission module, not shown in the drawings,

The updating module is specifically configured to update the configuration of the network element in the core network and apply the slice identifier table according to the target slice ID when the determining module determines that the target slice ID and the default slice ID are different;

And the sending module is used for sending the target slice ID to the terminal as the target slice ID so as to enable the terminal to reinitiate the session connection request carrying the target slice ID.

In an embodiment of the present disclosure, the sending module is further configured to send a terminal IP to the terminal when the determining module determines that the target slice ID is the same as the default slice ID, and establish a transmission channel between the base station and a user plane function UPF of the core network, so that the user datagram is transmitted through the transmission channel.

In one embodiment of the present disclosure, the updating module is further configured to, when the determining module does not query the target slice ID that matches the application ID, take the default slice ID as the target slice ID, and update the application slice identification table;

the sending module is further used for sending the terminal IP to the terminal, and establishing a transmission channel between the base station and a user plane function UPF of the core network so that the user data message is transmitted through the transmission channel.

Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the invention may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.

According to the slice identification management method and the slice identification management method provided by the embodiment of the disclosure, the slice identification management module based on the 5G application service is added to the 5G core network, so that the terminal is carried in different slice transmission channels according to different services, a user can enter different slice channels according to different application services, the differentiated guarantee of different services of the same terminal user in the 5G network can be realized, the diversified guarantee requirements of the user are met, different services are carried in different network resource environments, the differentiation of service level agreement SLA of the service is finally realized, the switching of service level slice identifications is realized through a 5G control plane signaling interaction mode, the terminal side is not required to be modified, and the problem that the slicing technology of terminal manufacturer URSP and the like is not mature is solved.

Fig. 9 shows a flowchart of a slice identifier management method in an embodiment of the present disclosure, and as shown in fig. 9, the slice identifier management method provided in the embodiment of the present disclosure is applied to a terminal side, and the method includes the following steps:

S902, a session connection request is sent to a core network, wherein the session connection request comprises an application ID of a terminal service;

Specifically, the user terminal sends a session connection request to the core network through the base station, where the session connection request includes information such as DNN, and an application ID of the terminal service.

S904, when receiving the destination slice ID issued by the core network, retransmitting a session connection request carrying the destination slice ID to the core network so that the terminal service is carried in a transmission channel corresponding to the destination slice ID.

In this embodiment, the core network queries the slice identifier management module according to the application ID to obtain a target slice ID matched with the application ID, and determines whether the core network issues the target slice ID by comparing the relationship between the target slice ID and the default slice ID that the terminal has subscribed.

When the target slice ID is different from the default slice ID, the core network transmits a target slice ID to the terminal through the base station, wherein the target slice ID is the target slice ID, the terminal receives the target slice ID transmitted by the core network and then transmits a session connection request to the core network again, and the retransmitted session connection request carries information such as the target slice ID, DNN, application ID of the terminal service and the like, so that the terminal service is borne in a GTP transmission channel corresponding to the target slice ID.

The slice identifier management method provided by the embodiment of the disclosure can select different slice channels according to terminal services, realize differentiated guarantee of different services of the same terminal user in a 5G network, meet the guarantee requirements of user diversification, and is low in technical difficulty and easy to realize.

Fig. 10 is a schematic diagram of a slice identifier management apparatus according to an embodiment of the present disclosure, as shown in fig. 10, applied to a terminal side, where the apparatus includes:

A request sending module 1001, configured to send a session connection request to a core network, where the session connection request includes an application ID of a terminal service;

A second receiving module 1002, configured to receive, in real time, a destination slice ID issued by the core network;

The request sending module is further configured to resend, when the second receiving module 1002 receives the destination slice ID issued by the core network, a session connection request carrying the destination slice ID to the core network, so that the terminal service is carried in a transmission channel corresponding to the destination slice ID.

The slice identifier management method and the slice identifier management device provided by the embodiment of the disclosure can select different slice channels according to terminal services, realize differentiated guarantee of different services of the same terminal user in a 5G network, meet the guarantee requirements of user diversification, have low technical difficulty and are easy to realize.

An electronic device 1100 according to this embodiment of the invention is described below with reference to fig. 11. The electronic device 1100 shown in fig. 11 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.

As shown in fig. 11, the electronic device 1100 is embodied in the form of a general purpose computing device. Components of electronic device 1100 may include, but are not limited to: the at least one processing unit 1110, the at least one memory unit 1120, a bus 1130 connecting the different system components, including the memory unit 1120 and the processing unit 1110.

Wherein the storage unit stores program code that is executable by the processing unit 1110 such that the processing unit 1110 performs steps according to various exemplary embodiments of the present invention described in the above-described "exemplary methods" section of the present specification. For example, the processing unit 1110 may execute a session connection request sent by the receiving terminal as shown in fig. 3, where the session connection request includes an application ID of the terminal service; searching a target slice ID matched with the application ID according to a preset application slice identification table; and determining the target slice ID according to the relation between the target slice ID and the default slice ID subscribed by the terminal, so that the terminal service is carried in a transmission channel corresponding to the target slice ID.

It should be noted that, the processing unit 1110 may perform sending a session connection request to the core network as shown in fig. 9, where the session connection request includes an application ID of the terminal service; and when receiving the destination slice ID issued by the core network, retransmitting a session connection request carrying the destination slice ID to the core network so as to enable the terminal service to be borne in a transmission channel corresponding to the destination slice ID.

The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a Random Access Memory (RAM) 11201 and/or a cache memory 11202, and may further include a Read Only Memory (ROM) 11203.

Storage unit 1120 may also include a program/utility 11204 having a set (at least one) of program modules 11205, such program modules 11205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

The bus 1130 may be a local bus representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a bus using any of a variety of bus architectures.

The electronic device 1100 may also communicate with one or more external devices 1140 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the system 1100, and/or any devices (e.g., routers, modems, etc.) that enable the electronic device 1100 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1150. Also, system 1100 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, e.g., the Internet, through a network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 1100, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.

More specific examples of the computer readable storage medium in the present disclosure may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

In this disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Alternatively, the program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

In particular implementations, the program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.

From the description of the above embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A slice identifier management method applied to a core network side, the method comprising:

determining a target slice ID according to the relation between the target slice ID and a default slice ID signed by the terminal, so that terminal service is carried in a transmission channel corresponding to the target slice ID;

The determining the target slice ID according to the relation between the target slice ID and the default slice ID, so that the terminal service is carried in the transmission channel corresponding to the target slice ID, includes:

2. The slice identifier management method according to claim 1, wherein the application slice identifier table is preset in a slice identifier management module of the core network, and the application slice identifier table stores a mapping relationship between an application ID and a slice ID of the terminal service.

3. The slice identifier management method according to claim 1 or 2, wherein determining a destination slice ID according to a relationship between the target slice ID and a default slice ID, so that the terminal service is carried in a transmission channel corresponding to the destination slice ID, includes:

4. The slice identifier management method according to claim 1 or 2, wherein determining a destination slice ID according to a relationship between the target slice ID and a default slice ID, so that the terminal service is carried in a transmission channel corresponding to the destination slice ID, includes:

5. A slice identifier management apparatus applied to a core network side, the apparatus comprising:

The determining module is used for determining a target slice ID according to the relation between the target slice ID and the default slice ID signed by the terminal so as to enable the terminal service to be borne in a transmission channel corresponding to the target slice ID;

And the determining module is used for issuing the target slice ID to the terminal as a target slice ID when the target slice ID and the default slice ID are different, so that the terminal reinitiates a session connection request carrying the target slice ID.

6. A slice identifier management method applied to a terminal side, the method comprising:

And when receiving a target slice ID issued by the core network, retransmitting a session connection request carrying the target slice ID to the core network so that terminal service is borne in a transmission channel corresponding to the target slice ID, wherein the target slice ID is the target slice ID transmitted by the core network when the target slice ID is different from a default slice ID signed by the terminal, and the target slice ID is the target slice ID matched with the application ID obtained by searching according to a preset application slice identification table.

7. A slice identifier management apparatus applied to a terminal side, the apparatus comprising:

The second receiving module is used for receiving a target slice ID issued by the core network in real time, wherein the target slice ID is the target slice ID sent by the core network when the target slice ID is different from a default slice ID signed by the terminal, and the target slice ID is the target slice ID matched with the application ID and obtained by searching according to a preset application slice identification table;

8. An electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the slice identity management method of any one of claims 1-4 or the slice identity management method of claim 6 via execution of the executable instructions.

9. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the slice identity management method according to any one of claims 1 to 4, or implements the slice identity management method according to claim 6.