CN111165025A

CN111165025A - Collaborative terminal slicing and network slicing functions

Info

Publication number: CN111165025A
Application number: CN201780095219.6A
Authority: CN
Inventors: 邓宇; 马春燕; 杨明; 姚松平; 李锋
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-10-16
Filing date: 2017-11-23
Publication date: 2020-05-15
Anticipated expiration: 2037-11-23
Also published as: WO2019075848A1; CN111165025B

Abstract

The method for coordinating the terminal slicing function and the network slicing function relates to the technical field of communication, and can be used for applying terminal slicing resources corresponding to slicing information through a terminal, so that the terminal slicing function and the network slicing function work cooperatively, the communication service quality is favorably improved, and the user experience is improved. The specific scheme comprises the following steps: the terminal sends a request message to the network equipment to obtain the slice information corresponding to the application identifier, and then applies for terminal slice resources and activates network slice resources according to the slice information.

Description

Collaborative terminal slicing and network slicing functions

The present application claims priority from a chinese patent application filed by the chinese patent office on 16/10/2017 under application number 201710963862.8 entitled "a method and apparatus for providing end-to-end terminal slices and network slices," the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, a terminal, and a system for coordinating a terminal slicing function and a network slicing function.

Background

With the development of communication technology, aiming at the upcoming rich and diverse application scenarios and differentiated service requirements, the Next Generation Mobile Network (NGMN) alliance proposes a solution to construct diverse Network Slices (NS) according to different requirements of different application scenarios so as to improve Network service quality. However, the specific implementation of this solution is yet to be further refined.

Disclosure of Invention

The application provides a method for coordinating a terminal slicing function and a network slicing function, so that the terminal slicing function and the network slicing function can work cooperatively, the communication service quality is favorably improved, and the user experience is improved.

In a first aspect, the present application provides a method for coordinating a terminal slicing function and a network slicing function, where the method specifically includes: the terminal sends a request message to the network equipment, wherein the request message contains an application identifier; the terminal receives a response message sent by the network equipment, wherein the response message contains slice information corresponding to the application identifier; and the terminal applies for terminal slice resources according to the slice information.

Wherein the slice information includes at least one of a slice type and slice differentiation information. The slice type includes at least one of enhanced mobile broadband, high-reliability low-delay connection, and large-scale internet of things. The slice differentiation information includes at least one of delay first, bandwidth first, consideration delay and bandwidth. Optionally, the slicing information may further include a category based on a type of a third-party application, such as a game, a video, music, or the like, or a feature of a vertical industry or other features, and the content of the slicing information is not limited in this embodiment of the application.

Illustratively, the terminal activating the terminal slice corresponding to the slice information includes: and the terminal activates the SST and/or the terminal Slice corresponding to the SD according to the Slice/Service type (SST) and/or the Slice differentiation information (SD) carried in the Slice information. In this way, the terminal prepares dedicated terminal slice resources for using the application, including but not limited to network resources, storage resources, computing resources, security isolation, etc. of the terminal.

Specifically, the network device queries, according to the application identifier carried in the request message, slice information of a network slice corresponding to the application identifier from a local network, or from a Business & Operation Support System (BOSS), or from a Policy Control Function (PCF), or from another network device, so that the communication System prepares a dedicated network slice resource for the terminal to use the application according to the slice information. And the network equipment sends the inquired slice information to the terminal in a mode of sending a response message to the terminal, so that the terminal can prepare a special terminal slice resource for the application according to the slice information.

Therefore, in the method provided by the embodiment of the application, the terminal acquires the slice information corresponding to the application identifier carried in the request message by sending the request message to the network device, and applies for the terminal slice resource according to the slice information. Therefore, the terminal slicing function and the network slicing function work cooperatively, the communication service quality is favorably improved, and the user experience is improved.

In one possible design, the network device includes a slice management server to manage network slice resources. The network device may also be another server responsible for managing the network slicing function, and the embodiment of the present application is not limited.

In one possible design, the response message further includes a slice application identifier SAID, and the SAID is generated by the network device according to the terminal identifier and the application identifier.

The SAID can be used for identifying a terminal identity and an application identity needing slicing, can be used for completing slicing requests to an operator network in an OTT network, and can also be used for billing of network slicing services. Therefore, the bookkeeping and the terminal identification are decoupled, the user is prevented from inputting the terminal identification, and the user information safety is protected.

In one possible design, after the terminal receives the response message sent by the network device, the terminal sends an indication to the network device to activate the network slice resource.

In a possible design, after the terminal sends an indication of activating a network slice resource to the network device, the terminal sends a first query message to the network device, where the first query message is used to indicate the network device to send an activation result of the network slice resource corresponding to the SAID; and the terminal receives the activation result sent by the network equipment.

In one possible design, after the terminal receives the activation result sent by the network device, the terminal sends the activation result to the application server.

It should be noted that the time period for using the network slice resource is the time for paying for the operator network, i.e. the charging time of the operator network. The activation time determined based on the activation result may be a starting time point of the payment time.

In one possible design, before the terminal sends the request message to the network device, the terminal sends an authorization request to the application server to obtain authorization authentication of the application server.

In a second aspect, the present application provides a method for coordinating a terminal slicing function and a network slicing function, where the method specifically includes: the terminal detects the operation of exiting the application of the user; and responding to the operation, and releasing the terminal slice resources by the terminal.

It should be noted that, in the release process of the slice function, the operator network may also initiate a release instruction, and the embodiment of the present application is not limited.

In one possible design, after the terminal detects the user's operation to exit the application, the terminal sends an indication to the network device to release the network slice resources.

In a possible design, after the terminal sends an instruction to the network device to release the network slice resources, the terminal sends a second query message to the network device, where the second query message is used to instruct the network device to send a release result of the network slice resources corresponding to the SAID; and the terminal receives the release result sent by the network equipment. And determining the time of releasing the network slice resources according to the release result, wherein the time is used as the termination time point of the charging time.

In a third aspect, the present application provides a method for coordinating a terminal slicing function and a network slicing function, including: the network equipment receives a request message sent by a terminal, wherein the request message contains an application identifier; based on the request message, the network device sends a response message to the terminal, wherein the response message contains the slice information corresponding to the application identifier.

In one possible design, the network device includes a slice management server to manage network slice resources.

In one possible design, the slice information includes at least one of a slice type and slice differentiation information.

In one possible design, the slice type includes at least one of enhanced mobile broadband, high-reliability low-delay connection, large-scale internet of things.

In one possible design, the slice differentiation information includes at least one of delay first, bandwidth first, compromise delay and bandwidth.

In one possible design, the request message further includes a terminal identifier, and before the network device sends the response message to the terminal, the network device generates a slice application identifier SAID according to the terminal identifier and the application identifier.

In one possible design, after the network device sends a response message to the terminal, the network device receives an indication of activating the network slice resource sent by the terminal, where the indication of activating the network slice resource includes an application identifier; based on the received indication of activating the network slice resource, the network device activates the application to identify the corresponding network slice resource.

In one possible design, after the network device receives an indication of activating a network slice resource sent by a terminal, the network device receives a first query message sent by the terminal, where the first query message is used to indicate the network device to send an activation result of the network slice resource corresponding to an SAID; the network device sends the activation result to the terminal.

In a fourth aspect, the present application provides a method for coordinating a terminal slicing function and a network slicing function, including: the network equipment receives an indication for releasing the network slice resource sent by a terminal, wherein the indication for releasing the network slice resource comprises an SAID; and based on the indication of releasing the network slice resources, the network equipment releases the network slice resources corresponding to the SAID.

In one possible design, after the network device receives an instruction for releasing the network slice resource sent by the terminal, the network device receives a second query message sent by the terminal, where the second query message is used to instruct the network device to send a release result of the network slice resource corresponding to the SAID: and the network equipment sends the release result to the terminal.

In a fifth aspect, a terminal is provided, including a receiving unit, a sending unit, and a processing unit, where the sending unit is configured to send a request message to a network device, where the request message includes an application identifier; the receiving unit is used for receiving a response message sent by the network equipment, wherein the response message contains slice information corresponding to the application identifier; and the processing unit is used for applying for the terminal slice resources according to the slice information.

In a possible design, the sending unit is further configured to send, to the network device, an indication to activate the network slice resource after the receiving unit receives the response message sent by the network device.

In one possible design, the sending unit is further configured to send, after the sending unit sends an indication of activating a network slice resource to the network device, a first query message to the network device, where the first query message is used to indicate the network device to send an activation result of the network slice resource corresponding to the SAID; and the receiving unit is also used for receiving the activation result sent by the network equipment.

In a possible design, the sending unit is further configured to send the activation result to the application server after the receiving unit receives the activation result sent by the network device.

In a possible design, the sending unit is further configured to send an authorization request to the application server before the sending unit sends the request message to the network device, so as to obtain authorization authentication of the application server.

In one possible design, the processing unit is further configured to detect an operation of exiting the application by the user after the processing unit applies for the terminal slice resource according to the slice information; and responding to the operation, and releasing the terminal slice resources.

In a possible design, the sending unit is further configured to send, to the network device, an indication to release the network slice resource after the processing unit detects that the user exits the application.

In one possible design, after the sending unit sends the indication of releasing the network slice resource to the network device, the sending unit sends a second query message to the network device, where the second query message is used to indicate the network device to send a release result of the network slice resource corresponding to the SAID; and the receiving unit is also used for receiving the release result sent by the network equipment.

A sixth aspect provides a network device, including a receiving unit, a sending unit, and a processing unit, where the receiving unit is configured to receive a request message sent by a terminal, and the request message includes an application identifier; and the sending unit is used for sending a response message to the terminal based on the request message, wherein the response message contains the slice information corresponding to the application identifier.

In a possible design, the request message further includes a terminal identifier, and the processing unit is configured to generate a slice application identifier SAID according to the terminal identifier and the application identifier before the sending unit sends the response message to the terminal.

In one possible design, the receiving unit is further configured to receive, after the sending unit sends the response message to the terminal, an indication of activating the network slice resource, which is sent by the terminal, where the indication of activating the network slice resource includes an application identifier; and the sending unit is further used for activating the network slice resource corresponding to the application identifier based on the received indication for activating the network slice resource.

In one possible design, the receiving unit is further configured to receive a first query message sent by the terminal after the receiving unit receives an indication of activating a network slice resource sent by the terminal, where the first query message is used to indicate the sending unit to send an activation result of a network slice resource corresponding to the SAID; and the sending unit is also used for sending the activation result to the terminal.

In one possible design, the receiving unit is further configured to receive, after the processing unit activates the network slice resource corresponding to the application identifier, an indication sent by the terminal to release the network slice resource, where the indication to release the network slice resource includes an SAID; and the processing unit is further used for releasing the network slice resources corresponding to the SAID based on the indication of releasing the network slice resources.

In a possible design, the receiving unit is further configured to receive, after the receiving unit receives an instruction sent by the terminal to release the network slice resource, a second query message sent by the terminal, where the second query message is used to instruct the sending unit to send a release result of the network slice resource corresponding to the SAID: and the sending unit is also used for sending the release result to the terminal.

In a seventh aspect, a terminal includes: a processor, a memory, and a communication interface, the memory and the communication interface coupled with the processor, the communication interface for communicating with a network device, the memory for storing computer program code, the computer program code comprising computer instructions that, when executed by the processor, cause the processor to send a request message to the network device via the communication interface, the request message including an application identification; the processor receives a response message sent by the network equipment through the communication interface, wherein the response message contains slice information corresponding to the application identifier; and the processor is used for applying for the terminal slice resources according to the slice information.

In one possible design, the processor is further configured to send, to the network device through the communication interface, an indication to activate the network slice resource after the processor receives a response message sent by the network device through the communication interface.

In one possible design, the processor is further configured to send, after the processor sends an indication of activating a network slice resource to the network device through the communication interface, a first query message to the network device through the communication interface, where the first query message is used to indicate the network device to send an activation result of the network slice resource corresponding to the SAID; and the processor is also used for receiving the activation result sent by the network equipment through the communication interface.

In one possible design, the processor is further configured to send the activation result to the application server through the communication interface after the processor receives the activation result sent by the network device through the communication interface.

In one possible design, the processor is further configured to send an authorization request to the application server through the communication interface before the processor sends the request message to the network device through the communication interface, so as to obtain authorization authentication of the application server.

In one possible design, the processor is further configured to detect an operation of exiting the application by the user after the processor applies for the terminal slice resource according to the slice information; and responding to the operation, and releasing the terminal slice resources.

In one possible design, after the processor detects an exit of the application by the user, the processor sends an indication to the network device to release the network slice resources through the communication interface.

In one possible design, after the processor sends an instruction to the network device through the communication interface to release the network slice resources, the processor sends a second query message to the network device through the communication interface, where the second query message is used to instruct the network device to send a release result of the network slice resources corresponding to the SAID; the processor receives the release result sent by the network equipment through the communication interface.

An eighth aspect is a network device, comprising: a processor, a memory and a communication interface, the memory and the communication interface being coupled to the processor, the communication interface being for communicating with the terminal, the memory being for storing computer program code, the computer program code comprising computer instructions, which, when executed by the processor, cause the processor to receive a request message sent by the terminal via the communication interface, the request message comprising an application identification; and the processor is further used for sending a response message to the terminal through the communication interface based on the request message, wherein the response message contains the slice information corresponding to the application identifier.

In one possible design, the request message further includes a terminal identifier, and the processor is further configured to generate a slice application identifier SAID according to the terminal identifier and the application identifier.

In one possible design, the processor is further configured to receive, through the communication interface, an indication of activating the network slice resource sent by the terminal after the processor sends the response message to the terminal through the communication interface, where the indication of activating the network slice resource includes the application identifier; based on the received indication to activate the network slice resource, the activation application identifies the corresponding network slice resource.

In one possible design, the processor is further configured to receive, through the communication interface, a first query message sent by the terminal after the processor receives, through the communication interface, an indication of activating a network slice resource sent by the terminal, where the first query message is used to indicate the network device to send an activation result of a network slice resource corresponding to the SAID; and sending the activation result to the terminal through the communication interface.

In one possible design, the processor is further configured to receive, through the communication interface, an indication to release the network slice resource, where the indication to release the network slice resource includes an SAID, after the processor activates the network slice resource corresponding to the application identifier; and releasing the network slice resources corresponding to the SAID based on the indication of releasing the network slice resources.

In one possible design, the processor is further configured to receive, through the communication interface, a second query message sent by the terminal after the processor receives, through the communication interface, an indication that the network slice resource is released and sent by the terminal, where the second query message is used to instruct the network device to send a release result of the network slice resource corresponding to the SAID: and sending the release result to the terminal through the communication interface.

A ninth aspect is a computer storage medium comprising computer instructions which, when run on a terminal, cause the terminal to perform a method of coordinating terminal slicing functions and network slicing functions as described in any one of the implementations of the first and second aspects.

A tenth aspect is a computer storage medium comprising computer instructions, which, when run on a terminal, cause the network device to perform a method of coordinating terminal slicing functions and network slicing functions as described in any of the implementations of the third and fourth aspects.

In an eleventh aspect, a computer program product is configured to, when run on a computer, cause the computer to perform the method for coordinating a terminal slicing function and a network slicing function as described in any one of the implementations of the first and second aspects.

Twelfth aspect, a computer program product, when running on a computer, causes the computer to perform a method of coordinating terminal slicing functions and network slicing functions as described in any one of the implementations of the third and fourth aspects.

Drawings

Fig. 1 is a first network topology diagram of a communication system provided in the present application;

fig. 2 is a schematic hardware structure diagram of a terminal and a network device provided in the present application;

fig. 3 is a first flowchart illustrating a method for coordinating a terminal slicing function and a network slicing function according to the present application;

fig. 4 is a schematic flowchart illustrating a second method for coordinating a terminal slicing function and a network slicing function according to the present application;

fig. 5 is a third schematic flowchart of a method for coordinating a terminal slicing function and a network slicing function according to the present application;

fig. 6 is a fourth flowchart illustrating a method for coordinating a terminal slicing function and a network slicing function according to the present application;

fig. 7 is a network topology diagram ii of a communication system according to the present application;

fig. 8 is a fifth flowchart illustrating a method for coordinating a terminal slicing function and a network slicing function according to the present application;

FIG. 9 is a schematic interface diagram of OTT purchasing network slice provided by the present application;

fig. 10 is a sixth flowchart illustrating a method for coordinating a terminal slicing function and a network slicing function according to the present application;

fig. 11 is a first schematic structural component diagram of a terminal provided in the present application;

fig. 12 is a schematic structural composition diagram of a terminal according to the present application;

fig. 13 is a first schematic structural component diagram of a network device provided in the present application;

fig. 14 is a schematic structural diagram of a network device according to the present application.

Detailed Description

The following describes a method for coordinating a terminal slicing function and a network slicing function according to the present application in detail with reference to the accompanying drawings.

With the development of communication technology, a variety of application scenarios with different network requirements will appear in the future. Different application scenarios have very different requirements in the aspects of network function, system performance, safety, user experience and the like, if the same network is still used for providing services, the network is complex and heavy, the requirement of the ultimate performance required by each application scenario cannot be met, the operation and maintenance of the network become quite complex, and the cost of network operation is increased.

Therefore, the NGMN alliance proposes a concept of Network slicing, that is, on one physical infrastructure, different NS are constructed as required by using technologies such as Software Defined Networking (SDN) and Network Function Virtualization (NFV), and the different NS correspond to different application scenarios. And logical isolation is realized among the NS, and the congestion, overload and configuration adjustment of any one NS do not affect other NS. Network functions (Network functions) in different NS can share the same software and hardware platform at the same position, and NS can dynamically extend and delete. Therefore, the efficiency of the network service is greatly improved, the network performance required by the application scene can be ensured, the operation and maintenance of the network become simple, and the investment and the operation and maintenance cost can be reduced.

On the other side, the terminal can construct the terminal resources of the terminal into a plurality of logically independent terminal slice resources according to different requirements of application scenes, so that the operation efficiency of the terminal is improved. These terminal resources include, but are not limited to, network resources, storage resources, computing resources, security isolation, and the like.

By way of example, Over The Top (OTT) includes third party services that are not associated with the carrier's communication network, and delivers a wide variety of content to users through applications. OTT typically uses carrier communication networks to provide services and applications to its users. OTT may directly access OTT content through platforms connected to carrier communication networks, such as personal computers, laptops, tablets, smart phones, and other web service enabled devices. Some examples of OTTs are web phones and instant messaging applications such as Skype, Google voice, and Viber. Such OTT applications provide voice call, messaging, and/or video services to users.

Providers of such OTT applications can purchase network-sliced services from operators, and service requirements of the network slices include, but are not limited to, OTT application identification, usage area, usage duration, number of concurrent users, and service requirements. The operator determines from this information to create and store different types of network slices, i.e. slice information, for these OTT application identities for which network slice services have been purchased. When the user uses the OTT application, the user needs to purchase a service of the network slice, including a use area, a use duration, and the like, from the OTT application service provider. For example: and opening a VIP member, purchasing a service acceleration package and the like. Or the provider of the OTT application may directly authorize all or part of users to use the network slice, which is not limited in the embodiment of the present application. After the provider of the OTT application authorizes the user, the user can use the service of the network slice of the operator, thereby improving the quality of the OTT service.

It should be noted that, when a user uses an OTT application, if the operator network accesses a dedicated network slice for the OTT application, the terminal does not invoke the dedicated terminal slice in time. This may also affect the quality of service of the network and affect the user experience. Therefore, the method for coordinating the terminal slicing function and the network slicing function provided by the embodiment of the application can be adopted, so that the service quality of the network is improved, and the user experience is improved.

As shown in fig. 1, a communication system 10 is provided for the embodiment of the present application, and includes a network device 20 and a terminal 30.

The network device 20 may be, for example, a network server, which is located at the edge of the mobile communication network of the operator, and is responsible for access authentication and management of the terminal 30 and providing services of mobile communication network slicing, which is not specifically limited in this embodiment of the present application.

The terminal 30 provides voice and/or data connectivity services to a user and may be, for example, User Equipment (UE), access terminal equipment, terminal equipment unit, terminal equipment station, mobile station, remote terminal equipment, mobile device, wireless communication device, terminal equipment agent, or terminal equipment device, etc. The access terminal device may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like, which is not particularly limited in this embodiment of the present application.

In the embodiment of the present application, the terminal 30 may also perform a terminal slicing function and the like.

Fig. 2 is a schematic diagram of a hardware structure of the network device 20 and the terminal 30 according to an embodiment of the present disclosure.

The terminal 30 comprises at least one processor 301, at least one memory 302, at least one transceiver 303. Optionally, the terminal 30 may also include an output device 304 and an input device 305.

The processor 301, the memory 302 and the transceiver 303 are connected by a bus. The processor 301 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application-Specific Integrated Circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present invention. The processor 301 may also include multiple CPUs, and the processor 301 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, or processing cores that process data (e.g., computer program instructions).

The Memory 302 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 302 may be a separate device and connected to the processor 301 through a bus. The memory 302 may also be integrated with the processor 301. The memory 302 is used for storing application program codes for executing the scheme of the application, and the processor 301 controls the execution. The processor 301 is configured to execute the computer program code stored in the memory 302, thereby implementing the method for data transmission described in the embodiments of the present application.

The transceiver 303 may use any transceiver or other communication Network for communicating with other devices or communication Networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc. The transceiver 303 includes a transmitter Tx and a receiver Rx.

The output device 304 is in communication with the processor 301 and may display information in a variety of ways. For example, the output device 304 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) Display device, a Cathode Ray Tube (CRT) Display device, a projector (projector), or the like. The input device 305 is in communication with the processor 301 and may receive user input in a variety of ways. For example, the input device 305 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

The network device 20 includes at least one processor 201, at least one memory 202, at least one transceiver 203, and at least one network interface 204. The processor 201, memory 202, transceiver 203 and network interface 204 are connected by a bus. The network interface 204 is configured to connect with a core network device through a link (e.g., an S1 interface), or connect with a network interface of another access network device through a wired or wireless link (not shown in the figure), which is not specifically limited in this embodiment of the application. In addition, the description of the processor 201, the memory 202 and the transceiver 203 may refer to the description of the processor 301, the memory 302 and the transceiver 303 in the terminal 30, and will not be repeated herein.

As shown in fig. 3, a flowchart of a method for coordinating a terminal slicing function and a network slicing function provided in an embodiment of the present application is shown, where the method specifically includes:

s101, the terminal sends a request message to the network equipment.

The network device is used for managing network slice resources, and may be a dedicated Slice Management (SM) server or other servers responsible for managing network slice functions, which is not limited in the embodiment of the present application.

The request message contains an application identifier, and is used for inquiring the slice information corresponding to the application identifier. The application identifier is a mark used for other applications, and may be, for example, a group of numbers, letters, symbols, or a character string combined by these, and the embodiments of the present application are not limited thereto. The Slice information includes a Slice requirement corresponding to the application identifier, and specifically includes unique Network Slice Selection Assistance information (S-NSSAI). The S-NSSAI is used to identify a type of a network Slice, including at least one of a Slice/Service type (SST) and Slice differentiation information (SD). The slice/service type is used for describing features of the network slice, and specifically includes: enhanced Mobile Broadband (eMBB), high-reliable low latency communications (URLLC), and large-scale internet of things (MIoT). The details are shown in table one.

TABLE SST values and description

Where SD can be used to distinguish a subclass of a slice/service type, as shown in table two.

Values and descriptions of Table two SD

SD value	Description of the invention
1	Delay first (delay first)
2	Bandwidth first
3	Compromise between delay and bandwidth
4	Retention

It should be noted that the terminal may determine what type of terminal slice is specifically prepared for the application based on SST and/or SD.

Optionally, the slicing information may further include a category based on a type of a third-party application, such as a game, a video, music, or the like, or a feature of a vertical industry or other features, and the content of the slicing information is not limited in this embodiment of the application.

S102, the terminal receives a response message sent by the network equipment.

Wherein, the response message contains slice information corresponding to the application identifier.

S103, the terminal applies for terminal slice resources based on the slice information.

The application for the terminal slice resource may also be understood as activating a terminal slice function, activating a terminal slice resource, or preparing a terminal slice resource, and the like, which is not limited in the embodiment of the present application.

Specifically, the terminal activates the terminal slice corresponding to the slice information. For example, the terminal activates a terminal slice corresponding to the SST and/or SD according to the SST and/or SD carried in the slice information. In this way, the terminal prepares dedicated terminal slice resources for using the application, including but not limited to network resources, storage resources, computing resources, security isolation, etc. of the terminal.

For example, if the slice information of an application is of a delay priority type, when the terminal prepares a terminal slice resource, the policy of the access layer may be configured as follows: the access allocation policy may be configured as a dual-path access policy, and/or the radio frequency management policy may be configured as a frequency band exclusive policy, and the like. The policy of the transport stack layer may be configured such that: configuring a differentiated congestion policy into a preemptive policy, and/or configuring a real-time multiplexing policy into a multiplexing policy, and/or configuring dynamic bandwidth diversity into a dynamic diversity policy, etc. These policies may ensure that the delay of the application meets the traffic demand. The operating system layer may be configured such that: the method comprises the steps of configuring a memory management strategy into a continuous memory, and/or configuring a multi-core scheduling strategy into a multi-core cooperation strategy, and/or configuring a task priority strategy into a high priority strategy, and the like. Thus, the terminal slice resource can be guaranteed to guarantee the delay requirement of the application.

In some embodiments, after step S103, step S104 is further included.

S104, the terminal sends an indication for activating the network slice resources to the network equipment.

The activating of the network slice resource may also be understood as activating a network slice function, or preparing a network slice resource, and the like, and the embodiment of the present application is not limited.

Specifically, the indication for activating the network slice resource carries an application identifier and an application server list. Wherein, the application server list includes the identifier of the application server. And the network equipment prepares a proprietary network slice resource for the application according to the application identifier and the application server list, so that the terminal and the application servers can use the proprietary network slice for data transmission. It should be noted that the application identifier here may be any other identifier capable of identifying the application, and the embodiments of the present application are not limited.

Step S104 may be executed before, after, or simultaneously with step S103, and the present application does not limit the order relationship between S104 and S103.

Therefore, in the method for coordinating the terminal slicing function and the network slicing function provided by the embodiment of the application, the terminal acquires the slicing information corresponding to the application identifier carried in the request message by sending the request message to the network device, and applies for the terminal slicing resource according to the slicing information. Therefore, the terminal slicing function and the network slicing function work cooperatively, the communication service quality is favorably improved, and the user experience is improved.

As shown in fig. 4, a flowchart of a method for coordinating a terminal slicing function and a network slicing function provided in an embodiment of the present application is shown, where the method specifically includes:

s201, the network equipment receives a request message sent by the terminal.

The request message includes an Application Identifier (APP ID) for querying slice information corresponding to the APP ID. The explanation and content of the slice information may refer to the description in step S101, and are not repeated.

S202, the network equipment acquires the slice information corresponding to the application identifier and sends a response message to the terminal.

The response message includes the slice information corresponding to the application identifier acquired by the network device.

In some embodiments, after step S202, steps S203-S204 are also included.

S203, the network equipment receives the indication of activating the network slice resource sent by the terminal.

The indication for activating the network slice resource carries an application identifier and an application server list. Wherein, the application server list includes the identifier of the application server. And the network equipment prepares a proprietary network slice resource for the application according to the application identifier and the application server list, so that the terminal and the application servers can use the proprietary network slice for data transmission. Wherein the preparation work includes, but is not limited to, creation of network slices, monitoring, alerting, and the like.

S204, based on the received indication of activating the network slice resources, the network device activates the network slice resources corresponding to the application identifier.

Specifically, the network device prepares a corresponding network slice resource for the terminal to use the application.

As shown in fig. 5, a flowchart of a method for coordinating a terminal slicing function and a network slicing function provided in an embodiment of the present application is shown, where the method specifically includes:

s301, the network equipment sends the slice information to the terminal.

Optionally, the terminal sends a request message to the network device, and requests to send the slice information of the network slice corresponding to the terminal using a certain application. Or the network device may actively send slice information of a network slice corresponding to an application that can be used by the terminal to the terminal.

And S302, the terminal applies for a terminal slicing function according to the slicing information.

The slice information comprises information such as the type of the network slice, and the terminal drives the terminal to prepare the terminal slice resource with the same type as the network slice resource according to the slice information. For example: if the slice information corresponding to an application is inquired by the network equipment to be delay-first, the network equipment activates network slice resources which are used for ensuring time delay for the application, and the data transmission efficiency of the application is improved. Then the terminal also prepares delay-prioritized terminal slice resources for the application. Therefore, the whole communication system reserves the resource with priority delay for the application, thereby being beneficial to improving the data transmission efficiency of the application and improving the user experience.

S303, the terminal sends an indication for activating the network slice resource to the network equipment.

Wherein the indication to activate the network slice resource comprises an application identification.

Step S303 may be executed before, after, or simultaneously with step S302, and the order relationship between S303 and S302 is not limited in the present application.

S304, based on the received indication of activating the network slice resources, the network device activates the network slice resources corresponding to the application identifier.

Specifically, the network device prepares a corresponding network slice resource for the terminal to use the application. The preparation involves the lifecycle of the network slicing service, for example: creation of network slices, allocation of network slice resources, reservation and allocation management, and the like. Table three shows one example of network device managing network slices. The following were used:

management table for table three network slices

Wherein, the slice 1 is an identifier of a network slice allocated to the application by the network device. The available nodes include node identifications that can be used, i.e., information including the server 1, the switch 1, and the like, and the amounts of resources (memory occupancy, CPU occupancy, and the like) allocated in the respective nodes. The capability of mobility control indicates whether the available nodes are capable of mobility control. The access area refers to information of an accessible area based on the location of an available node. The service usage time indicates providable service time information of the available node. The available bandwidth indicates the maximum bandwidth information that can be provided in the available nodes. The minimum delay time indicates a minimum delay time based on available nodes. The minimum packet loss rate identifies a minimum packet loss rate based on available resources. The resource utilization represents the resource utilization allocated by the current node.

As shown in fig. 6, a flowchart of a method for coordinating a terminal slicing function and a network slicing function provided in an embodiment of the present application is shown, where the method specifically includes:

s401, the terminal sends a request message to the network equipment for inquiring the slice information of the network slice.

The network device may be a dedicated Slicing Management (SM) server or other servers responsible for managing network Slicing functions, which is not limited in this embodiment of the present application.

The request message carries a terminal identifier, which may be an International Subscriber Directory Number (MSISDN) of the Mobile Station, or an International Mobile Subscriber identity Number (IMSI), and the embodiment of the present invention is not limited thereto.

In one implementation, the request message carries an application identifier. The application corresponding to the application identifier is an application to be used by the user on the terminal, and may be various application services provided to the terminal through the internet, such as micro blogging, network games, and the like. The request message is used to query the slice information of the network slice allocated by the communication system for the terminal to run the application.

In another implementation, the request message does not carry an application identifier. Then, the request message may be used to query slice information of network slices corresponding to all applications on the terminal.

S402, the network equipment acquires slice information corresponding to the application identification.

Specifically, the network device queries the slice information of the network slice corresponding to the application identifier from the local, or BOSS, or PCF, or other network device according to the application identifier, so that the network device requests to prepare a dedicated network slice resource for the terminal to use the application according to the slice information.

S403, the network device obtains a Slice Application Identification (SAID).

In one possible implementation, the network device generates the SAID according to the MISISDN and the application identity of the terminal, for example: the MISISDN, the application identifier, the application time, and the like are encrypted by using an Advanced Encryption Standard (AES), and the embodiment of the present application does not limit a specific algorithm.

It should be noted that, if the terminal identifier included in the request for querying the network slice information sent by the terminal in S101 is the IMSI, the network device further needs to query the MISISDN corresponding to the terminal according to the IMSI.

In another possible implementation manner, the PCF device, or the BOSS device, or another device generates an SAID according to the application identifier and the terminal identifier, and sends the SAID to the network device. For example: the SAID may be carried in a dedicated message, or may be carried in other messages, which is not limited in this embodiment.

S404, the network equipment sends a first response message to the terminal.

Specifically, if the query is successful, the first response message includes the slice information and the SAID corresponding to the application identifier. If the query fails, the first response message may carry information of the query failure, for example: the application identifier corresponds to a service for which the application does not open the network slicing function, or a service for which the communication system does not have the network slicing function, or a service for which the network slicing function is not opened in the area, and the like.

S405, after receiving a first response message sent by the network equipment, the terminal applies and activates terminal slice resources according to the slice information.

S406, the terminal sends an activation instruction to the network equipment, wherein the activation instruction is used for instructing to activate the network slice resource.

Wherein, the activation indication carries the SAID and the application server list. Wherein, the application server list includes the identifier of the application server. And the network equipment allocates a special network slice for the SAID according to the SAID and the application server list, so that the terminal and the application servers can use the special network slice for data transmission.

Optionally, the activation indication may also carry an application identifier, which may be used to verify the SAID, so as to ensure that the network slice corresponding to the application of the terminal is activated.

Step S406 may be executed before, after, or simultaneously with step S405, and the present application does not limit the order relationship between S405 and S406.

S407, after receiving the activation instruction, the network device sends a second response message to the terminal.

Wherein the second response message is used to notify the terminal that the network device has received the indication to activate the network slice resource.

And S408, after receiving the activation instruction, the network equipment activates the network slice resource and stores the activation result.

Specifically, according to the application identifier carried in the activation instruction, the network device is triggered to prepare the network slice resource corresponding to the application identifier, including but not limited to creation, monitoring, and alarm of the network slice.

And the network equipment stores the activation result of the network slice resource corresponding to the application identifier. Wherein the activation result comprises activation success and activation failure. If the activation fails, the activation result may also carry information of the activation failure, for example: the application identifier corresponds to a service for which the application does not open the network slicing function, or a service for which the communication system does not have the network slicing function, or a service for which the network slicing function is not opened in the area, and the like.

It should be noted that this step may be performed after, before, or simultaneously with S407, and the embodiment of the present application is not limited.

And S409, the network equipment sends the activation result to the terminal.

Optionally, step S409 may be replaced by S410-S411 as follows:

s410, the terminal sends a query message to the network equipment for querying the activation result of the network slice resource.

The request message carries an SAID, and is used for inquiring an activation result of a network slice function corresponding to the SAID.

Optionally, in step S405, after receiving the query response message from the network device, or while activating the terminal slicing function, or after activating the terminal slicing function, the terminal may send the query message after a preset time period.

S411, the network equipment sends the activation result to the terminal.

The following describes a method for coordinating a terminal slicing function and a network slicing function provided in the embodiment of the present application, with reference to a specific application scenario and an OTT application as an example.

As shown in fig. 7, a communication system 400 provided for the embodiment of the present application includes a terminal 401, at least one OTT server 402, an SM server 403, and an operator network 405. The communication system 400 may also include a web server 404.

The terminal 401 may be the terminal 30 shown in fig. 1 or fig. 2, and in this embodiment, the terminal 401 may further perform a terminal slicing function. Specifically, according to the role played in executing the slicing function of the terminal, the terminal may further include an OTT application module, a slice management Software Development Kit (SDK) module, and a slicing function module.

The OTT application module completes service package subscription, cancellation, query, and the like to the OTT server 402 through a communication Interface (IF), for example, IF 2. The OTT application module performs a security authentication procedure with the slice management SDK module through the communication interface IF1, and sends a slice activation instruction and a slice release instruction.

The slice management SDK module interacts with the carrier network 405 through the communication interface IF15, including applying for SAID, sending an activation indication and a deactivation indication of a network slice function, sending an activation indication and a deactivation indication of a terminal slice function, and receiving data sent by the carrier network. The slice function module receives an instruction for activating or deactivating the terminal slice function, which is sent by the slice management SDK module, through the communication interface IF7, and executes the terminal slice function, etc. The specific functions of the modules will be explained below.

The OTT server 402 applies for a token (token) from the slice management server 403 through the communication interface IF4, authorizes the slice management SDK module to complete application of the SAID, and provides service content of the OTT application.

The SM server 403 is connected to the operator network 405, and performs access authentication and management of the terminal 401, and provides a service for network slicing, and the like.

The web server 404 is used to provide web browsing services, and provide functions of creating, querying, monitoring, and reporting the slice type to the slice management server 405 through the communication interface IF 3.

The carrier network 405 is used to provide slicing service capabilities of the carrier network.

A method for coordinating a terminal slicing function and a network slicing function according to an embodiment of the present application is described with reference to a communication system 400 shown in fig. 7 as an example.

As shown in fig. 8, a flowchart of a method for coordinating a terminal slicing function and a network slicing function according to an embodiment of the present application is provided, where the method specifically includes:

s501, responding to the operation that the user starts the OTT application, the OTT application module obtains signing authorization from the OTT server.

Specifically, the identifier of the OTT application server carried in the request for subscription authorization is obtained, and the obtained identifier is used for subscribing the network slice capability to the OTT application servers, that is, the operator network can be applied to allocate the network slice for the terminal to use the OTT application. For example: the terminal may purchase an OTT service packet, such as a service acceleration packet, a service security packet, etc., from the OTT application server, so that the terminal may use the network slice when using the OTT application.

It should be noted that, the OTT service provider should purchase, in advance, the capability of the network slice from the operator, where the capability of the network slice includes, but is not limited to, the OTT application identifier, the usage area, the usage duration, the number of concurrent users, and the service requirement. The operator determines from this information to create and store different types of network slices, i.e. slice information, for these OTT application identities for which network slice capabilities have been purchased. FIG. 9 shows an interface diagram of an OTT service order network slice.

S502, the OTT server returns an authorization response message to the OTT application module.

And S503, the OTT application module and the slice management SDK module perform a security authentication process.

Specifically, the OTT application module sends an authentication request to the slice management SDK module, where the authentication request carries an application identifier. And the slice management SDK module determines whether the OTT application has the authority of using the slice according to the application identification. If yes, the authentication is successful, otherwise, the authentication fails.

If the terminal uses the application for the first time, the application further includes a registration process, specifically including S503a and S503b, as follows:

s503a, the OTT application module sends an application registration request to the slice management SDK module.

Specifically, the OTT application module performs registration authentication with the slice management SDK module to determine that the OTT application has the right to use the network slice. The authentication may be performed, for example, by adding a preset signature to the application identifier, and then the content of the application identifier plus the preset signature is carried in the application registration request.

The embodiments of the present application do not limit the specific form of authentication.

S503b, the slice SDK module sends a registration response message to the OTT application module.

Wherein, the registration response message carries the authentication result.

Specifically, the slice SDK module compares whether the signature carried in the application registration request is legal, and if so, the authentication is successful and the following steps are performed. If not, the authentication fails, and the process is ended.

S504, the OTT application module sends an indication of activating the slicing function to the slicing management SDK module.

The indication for activating the slicing function carries an application identifier, so that the slice management SDK module can activate the terminal slicing function corresponding to the application identifier and subsequently activate the network slicing function corresponding to the application identifier.

S505, the slice management SDK module sends a request message to the SM server. The request message includes an application identifier, and is used for querying slice information corresponding to the application identifier. The content and the effect of the slice information can refer to the explanation in step S101, and are not repeated.

The request message further includes a terminal identifier, which may be an MSISDN or an IMSI. If the terminal identifier is the IMSI, the SM server needs to query the MSISDN corresponding to the IMSI to the BOSS. If the terminal identity is an MSISDN, no query is required.

S506, the SM server obtains slice information of the network slice corresponding to the application identification from the BOSS.

S507, the SM server generates SAID according to MSISDN and slice information, and sends a query response message to the slice management SDK module.

The method for generating the SAID may refer to the description in step S403, and is not repeated.

S508, the slice management SDK module sends an instruction for activating the terminal slice function to the slice function module.

The slice information of the network slice inquired is included in the indication of the terminal slice function, so that the slice function module can activate the terminal slice function corresponding to the slice information according to the slice information, and thus, the terminal slice function and the network slice function are activated based on the same slice information, the terminal slice function and the network slice function can be cooperated, the network service quality is improved, and the user experience is improved.

And S509, after the slicing function module activates the terminal slicing function, sending an activation response to the slicing management SDK module.

Wherein the activation response is used to notify the slice management SDK module that the slice function module has successfully activated the terminal slice function.

S510, the slicing function SDK module sends an indication for activating the network slicing function to the SM server.

The indication for activating the network slicing function carries an SAID and an OTT server list, and this step may refer to S406 and is not repeated.

Optionally, the slicing function SDK module may be executed before, after, or simultaneously with S508, and this embodiment does not limit the sequential relationship between S510 and S508.

S511, the SM server sends a response message to the slice function SDK.

Wherein the response message is used to inform the slicing function SDK module that the SM server has received an indication to activate the network slicing function.

Optionally, the response message carries the timing duration of the timer T1. The timing duration is the estimated duration of the SM server activating the network slicing function. Thus, the slice management SDK module starts a timer T1, shown as S511a, after receiving the response message.

S512, the SM server sends an instruction for activating the network slicing function to the PCF.

The PCF may be a network element having a 5th Generation (5G) mobile communication function alone, a network element having a 4G mobile communication function alone, or a network element combining 4G and 5G functions.

It should be noted that, at present, the network slicing Function can only be applied to a 5G mobile communication network, and when a terminal requests a network slicing service, the terminal needs to apply for the network slicing Function from a PCF through an Access and Mobility Management Function (AMF). However, in the embodiment of the present application, the terminal is directly connected to the PCF through the SM server, and the network slicing function may be directly deactivated through the SM server. Therefore, the network slicing function of the embodiment of the application can be suitable for more communication networks, and the compatibility of the networks is improved.

S513, the PCF activates the network slice function.

S514, the PCF sends the activation result of the network slicing function to the SM server.

S515, the SM server caches the activation result of the network slice.

S516, the slice management SDK module sends a request for inquiring the activation result of the network slice to the SM server.

Optionally, after the timing duration of the timer T1 reaches the preset time, the slice management SDK module sends a request for querying an activation result of the network slice.

S517, the SM server feeds back the activation result of the network slice to the slice management SDK module.

And S518, the slice management SDK module sends the activation results of the terminal slices and the network slices to the OTT application module.

And S519, the OTT application module sends a slice function activation notification to the OTT server.

And S520, the OTT server records the slice activation time corresponding to the SAID according to the slice activation notification.

Specifically, the time period between the slice activation time and the slice deactivation time is the time that needs to be paid for the operator network, i.e., the charging time of the operator network. The activation time may be used as a starting point in time for the payment time.

Further, the method provided by the embodiment of the present application further includes a deactivation process. The process of deactivation may also be referred to as a process of releasing resources, etc. As shown in fig. 10, a flowchart of a method for coordinating a terminal slicing function and a network slicing function provided in the embodiment of the present application is provided, where the method specifically includes:

s601, responding to the operation that the user exits the OTT application module, the OTT application module sends an instruction for releasing the slice resources to the slice management SDK module.

The slice resource release may also be understood as deactivating a slice resource, releasing a slice function, deactivating a slice function, or the like, which is not limited in the embodiment of the present application. The SAID is carried in the indication for deactivating the slicing function, so that the operator network releases the network slicing resources corresponding to the SAID, and the terminal releases the terminal slicing resources corresponding to the SAID.

Optionally, the indication of releasing slice resources may also carry an application identifier, which may be used to verify the SAID.

It should be noted that, in the process of deactivating the slice function, it may also be that the operator network initiates the indication of releasing the slice resource, then step S601 may be replaced by S601a, as follows:

s601a, the SM server sends an instruction to release the slice resources to the slice management SDK module.

The terminal slice deactivation function may also be understood as terminal slice resource deactivation, terminal slice release function, or terminal slice resource release, and the like, which is not limited in the embodiment of the present application.

Specifically, when the SM server determines that the network slicing capability corresponding to the SAID changes, for example, the network slicing service time expires, or the terminal moves to a position outside the network slicing service area, the SM server sends an instruction for deactivating the terminal slicing function to the slicing management SDK module. The SAID is carried in the indication and used for indicating the terminal to release the terminal slice corresponding to the SAID.

S602, the slice management SDK module sends an instruction for releasing terminal slice resources to the slice function module.

Specifically, after receiving an instruction to release terminal slice resources, the slice function module releases the terminal slice corresponding to the SAID carried in the instruction.

S603, the slice management SDK module sends an indication of releasing the network slice resources to the SM server.

The releasing of the network slice resource may also be referred to as deactivating the network slice resource, releasing the network slice function, or deactivating the network slice function, and the like, which is not limited in the embodiment of the present application. The indication for deactivating the network slicing function carries the SAID and the list of the OTT server corresponding to the SAID, and may also carry an application identifier.

It should be noted that S603 may be executed before, after, or simultaneously with S602, and the execution order of S603 and S602 is not limited in this embodiment of the application.

S604, the SM server sends a response message to the slice management SDK module.

Wherein the response message is used to notify the slice management SDK module that the SM server has received an indication to deactivate the network slice function.

Optionally, the response message carries a timing duration of the timer T2, where the timing duration may be an estimated duration required by the SM server to deactivate the network slicing function. Thus, the slice management SDK module starts a timer T2, shown as S604a, upon receiving the response message.

S605, the SM server sends an instruction of releasing the network slice resource to the PCF.

Specifically, the PCF releases the network slice resource corresponding to the SAID after receiving the indication of releasing the network slice resource sent by the SM server.

S606, PCF sends the releasing result of the network slice resource to SM server.

S607, SM server receives and caches the release result of network slice resource sent by PCF.

S608, the slice management SDK module sends a request for inquiring the release result of the network slice resource to the SM server.

Optionally, the slice management SDK module sends a request for querying a release result of the network slice function when the time duration timed by the timer T2 reaches a preset time. Wherein, the request message carries SAID.

S609, the SM server feeds back the release result of the network slice resources to the slice management SDK module.

S610, the slice management SDK module sends the release result of the network slice resources to the OTT application module.

S611, the OTT application module sends a slice resource release notification to the OTT server.

And S612, the OTT server records the time of the slice resource release.

Specifically, the OTT server may record the time of the release of the slice resource according to the received slice resource release notification. The charging time of the operator network can be determined subsequently according to the time of the release of the slice resource. Specifically, the time period between the slice resource activation time and the slice resource release time is the time that needs to be paid for the operator network, i.e., the charging time of the operator network. Then, the time of slice deactivation may be used as the termination time point of the billing time.

It is to be understood that the above-mentioned terminal and the like include hardware structures and/or software modules corresponding to the respective functions for realizing the above-mentioned functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

In the embodiment of the present application, the terminal and the like may be divided into functional modules according to the method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

Fig. 11 shows a possible structure diagram of the terminal involved in the above embodiment in the case of dividing each functional module by corresponding functions. As shown in fig. 11, the terminal 1100 includes: transmitting section 1101, receiving section 1102, and processing section 1103.

Among other things, the sending unit 1101 is configured to support the terminal to perform S101 and S104 in fig. 3, S303 in fig. 5, S401, S406, S410 in fig. 6, S501, S505, S510, S516, and S519 in fig. 8, S603, S608, and S611 in fig. 10, and/or other processes for the techniques described herein. The receiving unit 1102 is configured to support the terminal to perform S102 in fig. 3, S502 in fig. 8, and/or other processes for the techniques described herein. The processing unit 1103 is configured to support the terminal to perform S103 in fig. 3, S302 in fig. 5, S405 in fig. 6, S503a, S503b, S504, S508-S509, S511a, and S518 in fig. 8, S601-S602, S604a, and S610 in fig. 10, and/or other processes for the techniques described herein.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Of course, the terminal 1100 may further include a storage unit for storing program codes, data, and the like. Moreover, the functions that can be specifically realized by the above-mentioned functional units also include, but are not limited to, the functions corresponding to the method steps described in the above examples, and the detailed description of the corresponding method steps may be referred to for the detailed description of other units of the terminal 1100, which is not described herein again in this embodiment of the present application.

In case an integrated unit is used, the processing unit may be a processing module of the terminal. The transmitting unit 1101 and the receiving unit 1102 may be integrated into a communication module of the terminal, and the communication module may be an RF circuit, a WiFi module, or a bluetooth module of the terminal. The storage unit may be a storage module of the terminal.

Fig. 12 shows a schematic diagram of a possible structure of the terminal involved in the above embodiment. The terminal 1200 includes: a processing module 1201, a storage module 1202, and a communication module 1203. The processing module 1201 is configured to control and manage an action of the terminal. A storage module 1202 for storing program codes and data of the terminal. The communication module 1203 is used for communicating with other terminals. The Processing module 1201 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1203 may be a transceiver, transceiving circuitry, or a communication interface, etc. The storage module 1202 may be a memory.

The processing module 1201 is configured to send a request message to the network device through the communication module 1203, where the request message includes an application identifier; the application identifier sending module 1203 is further configured to receive a response message sent by the network device, where the response message includes slice information corresponding to the application identifier; and the terminal is also used for applying for terminal slice resources according to the slice information. The processing module 1201 is configured to enable the terminal to perform S103 in fig. 3, S302 in fig. 5, S405 in fig. 6, S503a, S503b, S504, S508-S509, S511a, and S518 in fig. 8, S601-S602, S604a, and S610 in fig. 10, and/or other processes for the techniques described herein.

A communication module 1203 configured to enable the terminal to perform S101 and S104 in fig. 3, S303 in fig. 5, S401, S406, S410 in fig. 6, S501, S502, S505, S510, S516, and S519 in fig. 8, S603, S608, and S611 in fig. 10, and/or other processes for the techniques described herein.

When the processing module 1201 is a processor (such as the processor 301 shown in fig. 2), the communication module 1203 is an RF transceiver circuit (such as the transceiver 303 shown in fig. 2), and the storage module 1202 is a memory (such as the memory 302 shown in fig. 2), the terminal provided in the embodiment of the present application may be the terminal 30 shown in fig. 1 or fig. 2. The communication module 1203 may include not only an RF circuit, but also a WiFi module and a bluetooth module. The communication modules such as the RF circuit, WiFi module, and bluetooth module may be collectively referred to as a communication interface. Wherein the processor, the communication interface, and the memory may be coupled together by a bus.

Fig. 13 shows a schematic diagram of a possible structure of the network device involved in the above embodiment. As shown in fig. 13, the network device 1300 includes: transmitting section 1301, receiving section 1302, and processing section 1303.

Among other things, the sending unit 1301 is used to support the network device to perform S202 in fig. 4, S301 in fig. 5, S404, S407, S409, S411 in fig. 6, S507, S511, S512, S517 in fig. 8, S601a, S604-S605, and S609 in fig. 10, and/or other processes for the techniques described herein. The receiving unit 1302 is configured to support the network device to perform S201, S203 in the method embodiment, 514 in fig. 8, S606 in fig. 10, and/or other processes for the technology described herein. Processing unit 1303 is to support network device in performing S204 in fig. 4, S402-S403, S408 in fig. 6, S506 and S515 in fig. 8, S607 in fig. 10, and/or other processes for the techniques described herein.

Of course, the network device 1300 includes, but is not limited to, the above listed unit modules, for example, the network device 1300 may further include a storage unit for storing program codes, data, and the like. Moreover, the functions that can be specifically implemented by the functional units also include, but are not limited to, the functions corresponding to the method steps described in the foregoing examples, and the detailed description of the corresponding method steps may be referred to for the detailed description of other units of the network device 1300, which is not described herein again in this embodiment of the present application.

In case an integrated unit is used, the processing unit may be a processing module of the network device. The transmitting unit 1301 and the receiving unit 1302 may be integrated into a communication module of the network device, and the communication module may be an RF circuit, a WiFi module, or a bluetooth module of the network device. The storage unit may be a storage module of the network device.

Fig. 14 shows a schematic diagram of a possible structure of the network device involved in the above embodiments. The network device 1400 includes: a processing module 1401, a storage module 1402 and a communication module 1403. The processing module 1401 is used for controlling and managing the actions of the network device. A storage module 1402 for storing program codes and data of the network device. The communication module 1403 is used for communicating with the terminal. The Processing module 1401 may be a Processor or a controller, such as a Central Processing Unit (CPU), a general purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module 1403 may be a transceiver, a transceiver circuit or a communication interface, etc. The storage module 1402 may be a memory.

The processing module 1401 is configured to receive a request message sent by a terminal through a communication module 1403, where the request message includes an application identifier; and is further configured to send a response message to the terminal through the communication module 1403 based on the request message, where the response message includes the slice information corresponding to the application identifier. Processing module 1401 to enable the network device to perform S204 in fig. 4, S402-S403, S408 in fig. 6, S506 and S515 in fig. 8, S607 in fig. 10, and/or other processes for the techniques described herein.

A communication module 1403 to support the network device to perform S201-S203 in fig. 4, S301 in fig. 5, S404, S407, S409, S411 in fig. 6, S507, S511, S512, S514, S517 in fig. 8, S601a, S604-S606, and S609 in fig. 10, and/or other processes for the techniques described herein.

When the processing module 1401 is a processor (such as the processor 201 shown in fig. 2), the communication module 1403 is an RF transceiver circuit (such as the transceiver 203 shown in fig. 2), and the storage module 1402 is a memory (such as the memory 202 shown in fig. 2), the network device provided in the embodiment of the present application may be the network device 20 shown in fig. 1 or fig. 2. The communication module 1403 may include not only an RF circuit, but also a WiFi module and a bluetooth module. The communication modules such as the RF circuit, WiFi module, and bluetooth module may be collectively referred to as a communication interface. The network device may also include a network interface for communicating with other network devices. Wherein the processor, the communication interface, the network interface, and the memory may be coupled together by a bus.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for coordinating a terminal slicing function and a network slicing function, comprising:

a terminal sends a request message to network equipment, wherein the request message contains an application identifier;

the terminal receives a response message sent by the network equipment, wherein the response message contains slice information corresponding to the application identifier;

and the terminal applies for terminal slice resources according to the slice information.
The method of claim 1, wherein the network device comprises a slice management server configured to manage network slice resources.
The method according to any one of claims 1 or 2, wherein the slice information comprises at least one of slice type and slice differentiation information.
The method of claim 3, wherein the slice type comprises at least one of enhanced mobile broadband, high-reliability low-latency connection, large-scale Internet of things.
The method of claim 3 or 4, wherein the slice-differentiation information comprises at least one of delay first, bandwidth first, compromise delay and bandwidth.
The method according to any of claims 1-5, wherein the response message further comprises a Slice Application Identity (SAID), the SAID being generated by the network device based on a terminal identity and the application identity.
The method according to any of claims 1-6, wherein after the terminal receives the response message sent by the network device, the method further comprises:

the terminal sends an indication to the network device to activate network slice resources.
The method of claim 7, wherein after the terminal sends the indication to the network device to activate network slice resources, the method further comprises:

the terminal sends a first query message to the network equipment, wherein the first query message is used for indicating the network equipment to send an activation result of the network slice resource corresponding to the SAID;

and the terminal receives the activation result sent by the network equipment.
The method according to claim 8, wherein after the terminal receives the activation result sent by the network device, the method further comprises:

and the terminal sends the activation result to an application server.
The method according to any of claims 1-9, wherein before the terminal sends the request message to the network device, the method further comprises:

and the terminal sends an authorization request to the application server for obtaining the authorization authentication of the application server.
The method according to any of claims 1-10, wherein after the terminal applies for terminal slice resources based on the slice information, the method further comprises:

the terminal detects the operation of exiting the application of the user;

and responding to the operation, and releasing the terminal slice resources by the terminal.
The method according to claim 11, wherein after the terminal detects an operation of exiting the application by the user, the method further comprises:

and the terminal sends an indication for releasing the network slice resources to the network equipment.
The method of claim 12, wherein after the terminal sends the network device an indication to release network slice resources, the method further comprises:

the terminal sends a second query message to the network equipment, wherein the second query message is used for indicating the network equipment to send a release result of the network slice resource corresponding to the SAID;

and the terminal receives the release result sent by the network equipment.
A method for coordinating a terminal slicing function and a network slicing function, comprising:

the method comprises the steps that network equipment receives a request message sent by a terminal, wherein the request message contains an application identifier;

based on the request message, the network device sends a response message to the terminal, wherein the response message contains the slice information corresponding to the application identifier.
The method of claim 14, wherein the network device comprises a slice management server configured to manage network slice resources.
The method according to any one of claims 14 or 15, wherein the slice information comprises at least one of slice type and slice differentiation information.
The method of claim 16, wherein the slice type comprises at least one of enhanced mobile broadband, high-reliability low-latency connection, and large-scale internet of things.
The method of any of claims 16 or 17, wherein the slice-differentiation information comprises at least one of delay first, bandwidth first, compromise delay and bandwidth.
The method according to any of claims 14-18, wherein the request message further comprises a terminal identification, and wherein before the network device sends a response message to the terminal, the method further comprises:

and the network equipment generates a slice application identifier SAID according to the terminal identifier and the application identifier.
The method according to any of claims 14-19, wherein after the network device sends a response message to the terminal, the method further comprises:

the network equipment receives an indication of activating the network slice resource sent by the terminal, wherein the indication of activating the network slice resource comprises the application identifier;

based on the received indication of activating the network slice resource, the network device activates the network slice resource corresponding to the application identifier.
The method of claim 20, wherein after the network device receives the indication of the activated network slice resources sent by the terminal, the method further comprises:

the network equipment receives a first query message sent by the terminal, wherein the first query message is used for indicating the network equipment to send an activation result of a network slice resource corresponding to the SAID;

and the network equipment sends the activation result to the terminal.
The method according to any of claims 20 or 21, wherein after the network device activates the network slice resource corresponding to the application identity, the method further comprises:

the network equipment receives an indication of releasing network slice resources sent by the terminal, wherein the indication of releasing network slice resources comprises the SAID;

based on the indication of releasing the network slice resources, the network device releases the network slice resources corresponding to the SAID.
The method according to claim 22, wherein after the network device receives the indication of releasing network slice resources sent by the terminal, the method further comprises:

the network device receives a second query message sent by the terminal, where the second query message is used to instruct the network device to send a release result of the network slice resource corresponding to the SAID:

and the network equipment sends the release result to the terminal.
A terminal, characterized in that the terminal comprises: a processor, a memory and a communication interface, the memory and the communication interface coupled with the processor, the communication interface for communicating with a network device, the memory for storing computer program code, the computer program code comprising computer instructions that, when executed by the processor,

the processor is configured to send a request message to the network device through the communication interface, where the request message includes an application identifier;

the processor is further configured to receive a response message sent by the network device through the communication interface, where the response message includes slice information corresponding to the application identifier;

the processor is further configured to apply for terminal slice resources according to the slice information.
The terminal of claim 24, wherein the network device comprises a slice management server configured to manage network slice resources.
The terminal according to any of claims 24 or 25, wherein the slice information comprises at least one of a slice type and slice differentiation information.
The terminal of claim 26, wherein the slice type comprises at least one of enhanced mobile broadband, high-reliability low-latency connection, and large-scale internet of things.
The terminal according to claim 26 or 27, wherein the slice differentiation information comprises at least one of delay first, bandwidth first, compromise delay and bandwidth.
The terminal according to any of claims 24-28, wherein SAID response message further comprises a slice application identity, SAID, generated by SAID network device based on a terminal identity and SAID application identity.
The terminal of claim 24, wherein the processor is further configured to send an indication of activating network slice resources to the network device through the communication interface after the processor receives a response message sent by the network device through the communication interface.
The terminal of claim 30, wherein the processor is further configured to send a first query message to the network device through the communication interface after the processor sends an indication of activating a network slice resource to the network device through the communication interface, and the first query message is used to instruct the network device to send an activation result of the network slice resource corresponding to the SAID;

the processor is further configured to receive the activation result sent by the network device through the communication interface.
The terminal according to claim 30 or 31, wherein the processor is further configured to send the activation result to an application server through the communication interface after the processor receives the activation result sent by the network device through the communication interface.
The terminal according to any of claims 24 to 32, wherein the processor is further configured to send an authorization request to the application server through the communication interface before the processor sends a request message to the network device through the communication interface, so as to obtain authorization authentication of the application server.
The terminal according to any of claims 24-33, wherein the processor is further configured to detect an exit operation of the user from the application after the processor applies for a terminal slice resource according to the slice information;

the processor is further configured to release terminal slice resources in response to the operation.
The terminal of claim 34, wherein the processor is further configured to send an indication to release network slice resources to the network device through the communication interface after the processor detects an operation of a user to exit an application.
The terminal according to claim 34 or 35, wherein the processor is further configured to send a second query message to the network device through the communication interface after the processor sends an indication of releasing network slice resources to the network device through the communication interface, where the second query message is used to instruct the network device to send a release result of network slice resources corresponding to the SAID;

the processor is further configured to receive the release result sent by the network device through the communication interface.
A network device, characterized in that the network device comprises: a processor, a memory and a communication interface, the memory and the communication interface coupled with the processor, the communication interface for communicating with a terminal, the memory for storing computer program code, the computer program code comprising computer instructions that, when executed by the processor,

the processor is configured to receive a request message sent by the terminal through the communication interface, where the request message includes an application identifier;

the processor is further configured to send a response message to the terminal through the communication interface based on the request message, where the response message includes slice information corresponding to the application identifier.
The network device of claim 37, wherein the network device comprises a slice management server configured to manage network slice resources.
The network device of any one of claims 37 or 38, wherein the slice information comprises at least one of a slice type and slice differentiation information.
The network device of claim 39, wherein the slice type comprises at least one of enhanced mobile broadband, high reliability low latency connection, and large-scale Internet of things.
The network device of any one of claims 39 or 40, wherein the slice differentiation information comprises at least one of latency first, bandwidth first, latency and bandwidth.
The network device of any of claims 37-41, wherein the request message further comprises a terminal identification,

the processor is further configured to generate a slice application identifier SAID according to the terminal identifier and the application identifier.
The network device according to any of claims 37-42, wherein the processor is further configured to receive, via the communication interface, an indication of an active network slice resource sent by the terminal after the processor sends a response message to the terminal via the communication interface, the indication of the active network slice resource containing the application identifier;

the processor is further configured to activate the network slice resource corresponding to the application identifier based on the received indication to activate the network slice resource.
The network device according to any one of claims 37 to 43, wherein the processor is further configured to receive, through the communication interface, a first query message sent by the terminal after the processor receives, through the communication interface, the indication that the network slice resource is activated, where the indication is sent by the terminal, and the first query message is used to instruct the network device to send an activation result of the network slice resource corresponding to the SAID;

the processor is further configured to send the activation result to the terminal through the communication interface.
The network device according to any one of claims 43 or 44, wherein the processor is further configured to receive, through the communication interface, an indication sent by the terminal to release network slice resources after the processor activates the network slice resources corresponding to the application identifier, where the indication to release network slice resources includes the SAID;

the processor is further configured to release the network slice resource corresponding to the SAID based on the indication to release the network slice resource.
The network device of claim 45, wherein the processor is further configured to receive, through the communication interface, a second query message sent by the terminal after the processor receives, through the communication interface, the indication that the network slice resource is released and sent by the terminal, where the second query message is used to instruct the network device to send a release result of the network slice resource corresponding to the SAID:

the processor is further configured to send the release result to the terminal through the communication interface.
A computer storage medium comprising computer instructions which, when run on a terminal, cause the terminal to perform a method of coordinating terminal slicing functions and network slicing functions according to any of claims 1-13.
A computer storage medium comprising computer instructions which, when run on a terminal, cause the network device to perform the method of coordinating terminal slicing functions and network slicing functions according to any of claims 14-23.
A computer program product, characterized in that it causes a computer to carry out the method of coordinating terminal slicing functions and network slicing functions according to any one of claims 1-13, when said computer program product is run on the computer.
A computer program product, characterized in that it causes a computer to carry out the method of coordinating terminal slicing functions and network slicing functions according to any one of claims 14-23, when said computer program product is run on the computer.