WO2017045530A1 - 一种通信控制方法和控制器、用户设备、功能实例 - Google Patents

一种通信控制方法和控制器、用户设备、功能实例 Download PDF

Info

Publication number
WO2017045530A1
WO2017045530A1 PCT/CN2016/097649 CN2016097649W WO2017045530A1 WO 2017045530 A1 WO2017045530 A1 WO 2017045530A1 CN 2016097649 W CN2016097649 W CN 2016097649W WO 2017045530 A1 WO2017045530 A1 WO 2017045530A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
identifier
slice
function instance
data packet
Prior art date
Application number
PCT/CN2016/097649
Other languages
English (en)
French (fr)
Inventor
张伟
张锦芳
彭程晖
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16845644.0A priority Critical patent/EP3343978B1/en
Publication of WO2017045530A1 publication Critical patent/WO2017045530A1/zh
Priority to US15/923,899 priority patent/US10595233B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a communication control method, a controller, a user equipment, and a function example.
  • the difference in the demand for QoS for different services can be large. Corresponding to the communication network for the processing of these business data, the difference will be great. For example, for some delay-sensitive services, data packets are transmitted from the base station to the core network and then transmitted to the application server, which generates a large amount of delay, so that some functions of the core network and the application layer can be moved down to the location of the base station. Therefore, these delays can be avoided to ensure the delay requirements of the service for packet transmission and processing.
  • network operators must provide different processing mechanisms for different services based on different service requirements and carrier cost considerations.
  • the embodiments of the present invention provide a communication control method, a controller, a user equipment, and a function instance, which can meet the requirements of services for different requirements.
  • an embodiment of the present invention provides a communication control method, including:
  • the controller acquires a first slice identifier corresponding to the first service
  • the controller sends, to the first user equipment UE and the first function instance, indication information for establishing a bearer, where the bearer is used to transmit a data packet corresponding to the first service of the first UE, where the bearer Corresponding to the first slice identifier, the indication information carries an identifier of the first UE and an identifier of the first function instance.
  • the method further includes:
  • the controller acquires a correspondence between a service and a network slice, where the network slice corresponds to a slice identifier.
  • the controller obtains a correspondence between the service and the network slice, including:
  • the controller receives the service information sent by the service providing server, where the service information includes: a service identifier corresponding to the service and a service quality requirement required by the service, or the service information includes: a service identifier corresponding to the service, and a service quality required by the service
  • the service information includes: a service identifier corresponding to the service, and a service quality required by the service
  • the controller deploys the function instance according to the service information, and establishes a correspondence between the function instance and the network slice of the service deployment;
  • the controller establishes a correspondence between the service and the network slice according to the function instance deployed for the service.
  • the method further includes:
  • the controller sends the correspondence between the service and the network slice to the service providing server.
  • the controller acquires a correspondence between a service and a network slice, including:
  • the controller acquires a correspondence between the service and a network slice from a network slice deployment device.
  • the controller Determining, according to the first slice identifier, a first function instance corresponding to the first slice identifier, including:
  • the controller receives the authentication request message sent by the first UE, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE;
  • the controller selects a home subscription subscriber server HSS according to the authentication request message
  • the controller receives an authentication result of identity verification and slice authentication of the first UE by the HSS sent by the HSS;
  • the controller determines the first function instance according to the first slice identifier.
  • the controller Obtaining a first slice identifier corresponding to the first service, including:
  • the controller receives an instance request message sent by the PCEF entity after receiving the policy and charging rule function PCRF entity, after the first UE passes the authentication result of the identity authentication and the slice authentication, the instance request
  • the message includes: the first slice identifier obtained by the PCEF entity from the authentication result;
  • Determining, by the controller, the first function instance corresponding to the first slice identifier according to the first slice identifier includes:
  • the controller After the controller receives the instance request message, the controller determines the first function instance according to the first slice identifier.
  • a seventh possible implementation of the first aspect in combination with the first possible or second possible or third possible or fourth possible or fifth possible or sixth possible possible implementation of the first aspect further includes:
  • the controller sends the correspondence between the service and the network slice to the HSS or PCRF entity.
  • an embodiment of the present invention further provides a communication control method, including:
  • the first user equipment UE receives the indication information of the bearer corresponding to the first slice identifier, where the indication information carries the identifier of the first UE and the identifier of the first function instance;
  • the method further includes:
  • the first UE sends an authentication request message to the controller, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE.
  • the method further includes:
  • the first UE sends a service request message to the policy and charging execution function PCEF entity, where the service request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE transmits the first by using the bearer Business data package, including:
  • the first UE sends an uplink data packet to the first function instance by using the bearer, and the first function instance uses the processing resource and/or the transmission resource corresponding to the first slice identifier to the uplink Packet processing; and/or,
  • the first UE receives, by using the bearer, a downlink data packet that is sent after the first function instance processes the downlink data packet by using processing resources and/or transmission resources corresponding to the first slice identifier.
  • the method further includes:
  • the first UE sends an uplink scheduling request to the first base station, where the uplink scheduling request includes: the first slice identifier or the first connection identifier corresponding to the data packet that the first UE needs to send;
  • the first UE receives the resource assignment information sent by the first base station, where the resource assignment information includes: the first slice identifier or the first connection identifier, and the first slice identifier Or the processing resource and/or transmission resource corresponding to the first connection identifier, where the processing resource and/or the transmission resource includes an air interface transmission resource.
  • an embodiment of the present invention further provides a communication control method, including:
  • the first function instance receives the indication information of the bearer corresponding to the first slice identifier, where the indication information carries the identifier of the first user equipment UE and the identifier of the first function instance;
  • the first function instance is established as a bearer between the first UE and the first function instance of the first service service of the first user equipment UE according to the indication information;
  • the first function instance processes a data packet of the first service transmitted on the bearer by using a processing resource and/or a transmission resource corresponding to the first slice identifier, where the data packet of the first service is processed. Corresponding to the first slice identifier.
  • the first function instance includes at least one of: a first gateway GW, or a first data plane function node, or a first base station.
  • the first function instance is the first base station
  • the first function instance is used The method further includes: before the processing, by the first slice identifier, the processing resource and/or the transmission resource, to process the data packet of the first service that is transmitted on the bearer, the method further includes:
  • the first base station receives the uplink scheduling request sent by the first UE, where the uplink scheduling request includes: the first slice identifier or the first connection identifier corresponding to the data packet that the UE needs to send;
  • the first base station allocates a processing resource and/or a transmission resource corresponding to the first slice identifier or the first connection identifier according to the uplink scheduling request, where the processing resource and/or the transmission resource includes an air interface transmission resource;
  • the first base station sends the resource assignment information to the first UE, where the resource assignment information includes: the first slice identifier or the first connection identifier, and the first slice identifier Or the processing resource and/or the transmission resource corresponding to the first connection identifier, where the processing resource and/or the transmission resource includes an air interface transmission resource.
  • the first function instance is used with the first slice And processing, by the processing resource and/or the transmission resource, the data packet of the first service that is transmitted on the bearer, including:
  • the first function instance uses the processing resource and/or the transmission resource corresponding to the first slice identifier to the uplink Packet processing; and/or,
  • the first function instance processes the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier, and then sends the downlink after the processing is completed to the first UE by using the bearer. data pack.
  • the data packet of the first service is Corresponding to the first slice identifier, including:
  • the Internet Protocol IP quintuple of the downlink data packet received by the first GW corresponds to the first slice identifier
  • the IP data quintuple of the uplink data packet or the downlink data packet transmitted by the first data plane function node At least one of a label and a bearer identifier corresponding to the first slice identifier; or
  • the first function instance includes the first base station, at least one of a physical time-frequency resource, a user identifier, and a connection identifier used by the uplink data packet received by the first base station corresponds to the first slice identifier.
  • the embodiment of the present invention further provides a controller, including: a sending unit and a processing unit, where
  • the processing unit is configured to acquire a first slice identifier corresponding to the first service identifier, and determine, according to the first slice identifier, a first function instance corresponding to the first slice identifier;
  • the sending unit is configured to separately send indication information for establishing a bearer to the first user equipment UE and the first function instance, where the bearer is used to transmit a data packet corresponding to the first service of the first UE, where The bearer is associated with the first slice identifier, and the indication information carries an identifier of the first UE and an identifier of the first function instance.
  • the processing unit is further configured to obtain a correspondence between a service and a network slice, where the network slice corresponds to a slice identifier.
  • the controller further includes: a first receiving unit, where
  • the first receiving unit is configured to receive the service information sent by the service providing server, where the service information includes: a service identifier corresponding to the service and a service quality requirement required by the service, or the service information includes: a service identifier corresponding to the service, The quality of service requirements required by the business and the regional scope of the business;
  • the processing unit is further configured to: deploy a function instance according to the service information, and establish a correspondence between the service instance and the network slice, and establish a correspondence between the service and the network slice according to the function instance deployed for the service.
  • the sending unit is further configured to send the corresponding relationship between the service and the network slice to the service Provide a server.
  • the processing unit is further configured to acquire, by the network slice deployment device, the correspondence between the service and the network slice .
  • the controller further comprising: a second receiving unit, wherein
  • the second receiving unit is configured to receive an authentication request message sent by the first UE, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE;
  • the processing unit is configured to select a home subscription subscriber server HSS according to the authentication request message;
  • the second receiving unit is further configured to receive an authentication result that the HSS sent by the HSS performs identity authentication and slice authentication on the first UE.
  • the processing unit is specifically configured to determine, according to the first slice identifier, the first function instance, if the authentication result is that the first UE passes identity authentication and slice authentication.
  • the controller further comprising: a third receiving unit, wherein
  • the third receiving unit is configured to receive an instance request message sent by the PCEF entity after receiving the policy and the charging rule function PCRF entity, after the first UE passes the authentication result of the identity authentication and the slice authentication.
  • the instance request message includes: the first slice identifier obtained by the PCEF entity from the authentication result;
  • the processing unit is configured to determine the first function instance according to the first slice identifier after receiving the instance request message.
  • the sending unit is further configured to send the correspondence between the service and the network slice to the HSS or PCRF entity.
  • the embodiment of the present invention further provides a user equipment UE, where the UE is specifically a first UE, and the first UE includes: a receiving unit and a processing unit, where
  • the receiving unit is configured to receive indication information for establishing a bearer corresponding to the first slice identifier, where the indication information carries an identifier of the first UE and an identifier of the first function instance;
  • the processing unit is configured to establish, according to the indication information, a bearer between the first UE and the first function instance that is the first service service of the first UE, where the first function instance and the Corresponding to the first slice identifier; the data packet that transmits the first service by the bearer, the data packet corresponding to the first slice identifier.
  • the first UE further includes: a first sending unit, where
  • the first sending unit is configured to send an authentication request message to the controller, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE further includes: a second sending unit, where
  • the second sending unit is configured to send a service request message to the policy and charging execution function PCEF entity, where the service request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE further includes: a third sending unit, among them,
  • the third sending unit is configured to send, by using the bearer, an uplink data packet to the first function instance, where the first function instance uses a processing resource and/or a transmission resource corresponding to the first slice identifier. Processing the uplink data packet; and/or,
  • the receiving unit is further configured to receive, by using the bearer, a downlink data packet that is sent after the first function instance processes the downlink data packet by using processing resources and/or transmission resources corresponding to the first slice identifier.
  • the first UE further includes: a fourth sending unit, wherein
  • the sending unit is configured to send, by the processing unit, an uplink scheduling request to the first base station by using the bearer to transmit the data packet of the first service, where the uplink scheduling request includes: The first slice identifier or the first connection identifier corresponding to the data packet that the UE needs to send;
  • the receiving unit is configured to receive the resource assignment information that is sent by the first base station, where the resource assignment information includes: the first slice identifier or the first connection identifier, and the first cut a slice identifier or a processing resource and/or a transmission resource corresponding to the first connection identifier, where the processing resource and/or the transmission resource include an air interface transmission resource.
  • an embodiment of the present invention provides a function example, where the function instance is specifically a first function instance, where the first function instance includes: a receiving unit and a processing unit, where
  • the receiving unit is configured to receive indication information for establishing a bearer corresponding to the first slice identifier, where the indication information carries an identifier of the first user equipment UE and an identifier of the first function instance;
  • the processing unit is configured to establish, according to the indication information, a bearer between the first UE and the first function instance that is a first service service of the first user equipment UE, and use the first slice And identifying, by the processing resource and/or the transmission resource, the data packet of the first service that is transmitted on the bearer, where the data packet of the first service corresponds to the first slice identifier.
  • the first function instance includes at least one of: a first gateway GW, or a first data plane function node, or a first base station.
  • the first base station further includes: a sending unit, wherein
  • the receiving unit is further configured to receive, before the processing unit processes, by using a processing resource and/or a transmission resource corresponding to the first slice identifier, a data packet of the first service transmitted on the bearer, The uplink scheduling request sent by the first UE, where the uplink scheduling request includes: the first slice identifier or the first connection identifier corresponding to the data packet that the UE needs to send;
  • the processing unit is further configured to allocate processing resources and/or transmission resources corresponding to the first slice identifier or the first connection identifier according to the uplink scheduling request, where the processing resource and/or the transmission resource includes air interface transmission Resource
  • the first sending unit is configured to send, to the first UE, resource assignment information, where the resource assignment information includes: the first slice identifier or the first connection identifier, and A slice identifier or a processing resource and/or a transmission resource corresponding to the first connection identifier, where the processing resource and/or the transmission resource include an air interface transmission resource.
  • the first function instance further includes: a second sending unit, where
  • the receiving unit is configured to receive, by using the bearer, an uplink data packet sent by the first UE;
  • the processing unit is specifically configured to process the uplink data packet by using processing resources and/or transmission resources corresponding to the first slice identifier; and/or,
  • the processing unit is specifically configured to process the downlink data packet by using processing resources and/or transmission resources corresponding to the first slice identifier;
  • the second sending unit is configured to send, by using the bearer, the downlink data packet after the processing is completed to the first UE.
  • the data packet of the first service is Corresponding to the first slice identifier, including:
  • the Internet Protocol IP quintuple of the downlink data packet received by the first GW corresponds to the first slice identifier
  • the IP data quintuple of the uplink data packet or the downlink data packet transmitted by the first data plane function node At least one of a label and a bearer identifier corresponding to the first slice identifier; or
  • the first function instance includes the first base station, at least one of a physical time-frequency resource, a user identifier, and a connection identifier used by the uplink data packet received by the first base station corresponds to the first slice identifier.
  • the controller first obtains a first slice identifier corresponding to the first service, and then the controller determines, according to the first slice identifier, a first function instance corresponding to the first slice identifier, where the controller And transmitting, according to the first slice identifier, indication information for establishing a bearer to the first UE and the first function instance, where the bearer is used to transmit a data packet corresponding to the first service of the first UE.
  • the controller can determine the first function instance corresponding to the first slice identifier according to the first slice identifier that is obtained by the controller, for example, the first UE requests the controller to allocate a function instance, where the first UE The corresponding slice identifier is the first slice identifier, or the slice identifier corresponding to the first service initiated by the first UE is the first slice identifier, and the controller may obtain the corresponding first function instance according to the first slice identifier, Different The functional instances may provide different processing functions using processing resources and/or transmission resources corresponding to different slice identifications.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and can be different user devices and different The business provides differentiated services.
  • FIG. 1 is a schematic structural diagram of a relationship between a controller, a service providing server, a user equipment, and a function instance according to an embodiment of the present invention
  • FIG. 2 is a schematic block diagram of a communication control method according to an embodiment of the present invention.
  • FIG. 3 is a schematic block diagram of another communication control method according to an embodiment of the present invention.
  • FIG. 4 is a schematic block diagram of another communication control method according to an embodiment of the present invention.
  • FIG. 5 is a schematic block diagram of another communication control method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic block diagram of another communication control method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic block diagram of another communication control method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic block diagram of another communication control method according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic block diagram of another communication control method according to an embodiment of the present invention.
  • FIG. 10 is a schematic block diagram of another communication control method according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic block diagram of another communication control method according to an embodiment of the present disclosure.
  • 12-a is a schematic diagram of a general flow in a processing flow of a data packet according to an embodiment of the present invention
  • 12-b is a schematic diagram of an implementation manner of network slice deployment according to an embodiment of the present invention.
  • 12-c is a schematic diagram of a process of association between a service and a network slice according to an embodiment of the present invention.
  • 12-d is a schematic diagram of a process of association between a service and a network slice according to an embodiment of the present invention.
  • 12-e is a schematic flowchart of processing a downlink data packet according to an embodiment of the present invention.
  • 12-f is a schematic flowchart of processing an uplink data packet according to an embodiment of the present invention.
  • 12-g is a schematic diagram of a process for allocating air interface transmission resources by a first UE and a first base station according to an embodiment of the present invention
  • 13-a is a schematic structural diagram of a controller according to an embodiment of the present invention.
  • 13-b is a schematic structural diagram of another controller according to an embodiment of the present invention.
  • 13-c is a schematic structural diagram of an acquisition module according to an embodiment of the present invention.
  • 13-d is a schematic structural diagram of another controller according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a first UE according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of another first UE according to an embodiment of the present disclosure.
  • FIG. 15-a is a schematic structural diagram of a first functional example according to an embodiment of the present disclosure.
  • FIG. 15-b is a schematic structural diagram of another first functional example according to an embodiment of the present disclosure.
  • 16-a is a schematic structural diagram of another controller according to an embodiment of the present invention.
  • 16-b is a schematic structural diagram of another controller according to an embodiment of the present invention.
  • 16-c is a schematic structural diagram of another controller according to an embodiment of the present invention.
  • 16-d is a schematic structural diagram of another controller according to an embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of another first UE according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of another first UE according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of another first UE according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of another first UE according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of another first UE according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of another first functional example according to an embodiment of the present disclosure.
  • FIG. 18-b is a schematic structural diagram of another first functional example according to an embodiment of the present disclosure.
  • FIG. 18-c is a schematic structural diagram of another first functional example according to an embodiment of the present invention.
  • the embodiments of the present invention provide a communication control method, a controller, a user equipment, and a function instance, which can meet the requirements of services for different requirements.
  • FIG. 1 it is a schematic diagram of the structure relationship between the controller, the service providing server, the user equipment, and the function instance in the embodiment of the present invention.
  • the controller may be deployed on the operator side, and the controller determines a function instance for the UE, and the function instance provides the UE with processing resources and/or transmission resources, and the service provider provides service support for the UE.
  • the communication control method provided by the embodiment of the present invention is applicable to a case where the service requirement is clear and the service requirement category is determined.
  • the service providing server is located above the operator (English name: operator) and is used to provide various application services to the user equipment. Operators are used to provide wireless network access, such as mobile, China Unicom, and telecommunications.
  • the executor of the embodiment of the present invention includes at least a controller, a function instance, and a UE, where the controller may be configured to determine a function instance according to a correspondence between the slice identifier and the function instance, and allocate, to the UE, a first slice identifier.
  • the first function instance, the triggering UE, and the selected first function instance establish a bearer.
  • the UE is configured to request the controller to allocate a function instance, establish a bearer under the trigger of the controller, and transmit the data packet by using the established bearer.
  • the first function instance is configured to establish a bearer under the trigger of the controller after being selected by the controller, and provide a processing function corresponding to the first function instance by using a processing resource and/or a transmission resource corresponding to the first slice identifier.
  • a network slice can be divided into the following links from requesting requirements to providing services for users' services.
  • the operator deploys a network slice that provides service support for the service according to the requirements of the service, and the network slice includes various functional instances required, and corresponding processing resources and/or transmission resources.
  • the deployment process of the network slice is independent of the user.
  • the controller determines the network slice corresponding to the service, and establishes a bearer for the service on the function instance corresponding to the network slice, and establishes a correspondence between the service and the network slice.
  • the function instance finds the corresponding network slice according to the correspondence between the data packet feature established by the bearer and the network slice, and provides data processing for the service data according to the slice information.
  • the user is provided with a differentiated authentication and authorization charging process in the authentication and authorization charging process that the user accesses, but the transmission of the service data of all the virtual operators is provided by the shared infrastructure operator. With infrastructure, this clearly does not meet the need for service differentiation for service differentiation.
  • the communication control method and the prior art provided by the embodiments of the present invention are applicable to different application scenarios, and adopt different technical means. Specifically, the present invention is different from the application scenario of the prior art. In the embodiment of the present invention, the difference authentication is not provided in the link of the user accessing the network, but in the processing link of the data packet. In addition, the present invention is different from the technical methods used in the prior art.
  • different network slices corresponding to different services are obtained according to different service requirements, and different network slices respectively correspond to different functional instances, and different The function instance provides different processing functions by using different processing resources and/or transmission resources, so that the specific service function and the specific service quality requirement and the specific experience quality requirement can be satisfied in the embodiment of the present invention, so that different users can be Differentiated packet processing services are provided for devices and different services.
  • the communication control method provided by the embodiment of the present invention is first introduced from the controller side.
  • the communication control method provided by an embodiment of the present invention may include the following steps:
  • the controller acquires a first slice identifier corresponding to the first service.
  • the controller determines, according to the first slice identifier, a first function instance corresponding to the first slice identifier.
  • the controller first obtains the first slice identifier corresponding to the first service of the first UE, and the controller associates the correspondence between the slice identifier and the function instance in advance, or the controller acquires the slice identifier from the network. Correspondence with function instances. After the controller obtains the first slice identifier, the controller first obtains the first function instance, where the first function instance may include one or more function instances, and different function instances provide different processing resources and/or transmission resources. Processing function. Specifically, the service identifier of the first service initiated by the first UE corresponds to the slice identifier, and the slice identifier corresponds to the instance identifier of the function instance.
  • the first service may be an actual service initiated by the first UE, and the first service may also be a pre-configured service directly associated with the first UE, and the specific implementation manner of the first service depends on the application scenario. It is intended to be illustrative only and not to limit the invention.
  • the controller separately sends, according to the first slice identifier, the first UE and the first function instance.
  • the bearer is configured to transmit a data packet corresponding to the first service of the first UE, and the bearer is associated with the first slice identifier, where the indication information carries the identifier of the first UE and the identifier of the first function instance.
  • the controller determines that the first function instance uses the processing resource and/or the transmission resource to provide the first UE with the processing function of the data packet, and controls The device controls the first UE and the first function instance to perform bearer establishment. Specifically, the controller sends, to the first UE and the first function instance, indication information for establishing a bearer, where the bearer is used to transmit a data packet corresponding to the first service of the first UE, where the bearer and the first slice identifier are The first network slice corresponds.
  • the controller indicates that the bearer established by the first UE and the first function instance is used to transmit the data packet corresponding to the first service of the first UE, and thus the foregoing bearer may be identified by the first slice identifier.
  • the first UE and the first function instance receive the indication information of the controller, the first UE and the first function instance respectively perform the establishment process of the bearer, and the specific establishment manner of the bearer may refer to the prior art, and details are not described herein again.
  • the controller may obtain a corresponding first function instance according to the first slice identifier, and different function instances may provide different processing resources and/or transmission resources corresponding to different slice identifiers.
  • Processing function In the embodiment of the present invention, a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and can be different user devices and different The business provides differentiated services.
  • the communication control method provided by an embodiment of the present invention may include the following steps:
  • the controller obtains a correspondence between the service and the network slice, where the network slice corresponds to the slice identifier.
  • the controller acquires a first slice identifier corresponding to the first service.
  • the controller determines, according to the first slice identifier, a first function instance corresponding to the first slice identifier.
  • the controller separately sends indication information for establishing a bearer to the first UE and the first function instance according to the first slice identifier.
  • the bearer is configured to transmit a data packet corresponding to the first service of the first UE, and the bearer is associated with the first slice identifier, where the indication information carries the identifier of the first UE and the identifier of the first function instance.
  • Step 302 is similar to the implementation of step 201 in the foregoing embodiment, and step 303 is similar to the implementation of step 202 in the foregoing embodiment, step 304 and the steps in the foregoing embodiment.
  • the implementation of 203 is similar and will not be described here.
  • step 301 will be described in detail.
  • the controller may be deployed by an operator, and the operator provides service support to the service provider.
  • the controller establishes a correspondence between the service and the network slice according to the service requirement, and the service and network slice described in step 301.
  • the corresponding relationship refers to the correspondence between all services and different network slices.
  • the network slice may refer to a function instance and a collection of transmission resources and processing resources involved in meeting specific service requirements. For different service requirements, the controller needs to establish different network slices.
  • Different network slices may have different protocol stack processing flows, and each network slice corresponds to one or more function instances, and different function instances may provide different processing functions using different processing resources and/or transmission resources. That is, each function instance corresponds to a processing resource, or corresponds to a transmission resource, or corresponds to a processing resource and a transmission resource, and one network slice corresponds to one or more function instances, so that the network slice can determine the network.
  • the processing resource and/or transmission resource used by the corresponding function instance of the slice is sliced.
  • Processing resources and transmission resources can provide specific processing functions for the service.
  • the processing resources can be corresponding to the central processing unit (English: Central Processing Unit: CPU), core and other computing resources, and the transmission resources can correspond to network bandwidth.
  • a resource for example, a function instance is specifically a base station, and the transmission resource may specifically refer to an air interface transmission resource.
  • the processing resources and/or transmission resources used by different function instances are different.
  • the function examples may include: a base station, a gateway (English name: Gateway, English abbreviation: GW), and a data plane function (English name: Data Plane) Function, English abbreviation: DPFn) node, when the function instance represents different entities, its corresponding processing resources and/or transmission resources may be different.
  • the network slice is established in a flexible manner, for example, different network slices may be set based on different speed, capacity, and coverage, and different network slices may satisfy each specific service.
  • Network slicing includes: connection services implemented by a number of customizable software-defined functions, for example, based on management geographic coverage, duration, capacity, speed, latency, robustness, security, and availability. One or some requirements to build a specific network slice.
  • a service requirement refers to a specific requirement of a service to process a resource and/or a transmission resource.
  • the specific service requirements are different.
  • the service requirements may be considered to be different.
  • the business can be specifically machine type communication (English full name: Machine Type Communication, English abbreviation: MTC) Massive meter reading business or somatosensory game, etc., different services determine its different requirements for processing resources and / or transmission resources.
  • the controller may obtain the correspondence between the multiple services and the network slice before the user equipment (English name: User Equipment, English abbreviation: UE) initiates the service.
  • the controller 301 obtains the corresponding relationship between the service and the network slice, and specifically includes the following steps:
  • the controller receives the service information sent by the service providing server, where the service information includes: a service identifier corresponding to the service and a service quality requirement required by the service, or the service information includes: a service identifier corresponding to the service, a service quality requirement required by the service, and The area of the business;
  • the controller deploys the function instance according to the service information, and establishes a correspondence between the function instance and the network slice of the service deployment.
  • the controller establishes a correspondence between the service and the network slice according to the function instance deployed for the service.
  • the controllers deployed in the operator are configured to establish a correspondence between the service and the network slice by using the service providing server deployed in the service provider in steps A1 to A3.
  • the service providing server deployed in the service provider sends the service information to the controller. If the service providing server has multiple different services, the service information sent by the service providing server to the controller may include service information of multiple different services.
  • Each service information includes a service identifier corresponding to the service and a service quality requirement required by the service.
  • the service information includes, in addition to the service corresponding identifier and the service quality requirement required by the service, the service information may also be a service area. Scope, where the geographic area of the business refers to the geographic area in which the business deployment takes effect.
  • the controller deploys function instances according to the service requirements of each service in the service information. Some of the service requirements only need to deploy one function instance. Some service requirements need to deploy two or more function instances.
  • the controller attributes the established function instance to the corresponding network slice, thereby establishing a correspondence between the function instance and the network slice, and finally, associating the service with the network slice according to the deployed function instance, thereby Complete the correspondence between the establishment of the service and the network slice.
  • the service information a in the service a includes the service identifier a' corresponding to the service a, the service quality requirement required by the service a, and the area range of the service a.
  • the service information b of the service b includes the service identification b' corresponding to the service b, the service quality requirement required by the service b, and the area range of the service b.
  • the service information c of the service c includes the service identifier c' corresponding to the service c, the service quality requirement required by the service c, and the area range of the service c.
  • the controller can separately deploy the function instance for the three services, and establish a corresponding relationship between the function instance and the network slice. For example, if the controller deploys the function instance 1 and the function instance 2 for the service a according to the service requirement of the service a, the function instance 1 for the service a deployment and the function instance 2 correspond to a network slice x, and the controller can establish the function instance 1 Correspondence between function instance 2 and network slice x.
  • the function instance 3 is deployed for the service b according to the service requirement of the service b, and the function instance 3 deployed for the service b corresponds to a network slice y.
  • the controller can establish a corresponding relationship between the function instance 3 and the network slice y.
  • the controller deploys the function instance 4, the function instance 5, and the function instance 6 for the service c according to the service requirement of the service c.
  • the function instance 5 and the function instance 6 correspond to one network slice z, and the controller can establish the correspondence relationship between the function instance 4, the function instance 5, the function instance 6, and the network slice z.
  • the controller establishes the correspondence between the service a and the network slice x.
  • the controller establishes the correspondence between the service b and the network slice y, and the controller establishes the correspondence between the service c and the network slice z.
  • a, b, c, 1, 2, x, y, z are used to identify a specific object to distinguish it from other objects.
  • the mapping between the function instance and the network slice of the service deployment can be as follows:
  • Table 1 lists the correspondence between services, function instances, and network slices:
  • the controller may separately deploy a function instance and establish a correspondence between different services and network slices according to the foregoing implementation manner. relationship.
  • the controller may also use other methods to establish a correspondence between the service and the network slice in the embodiment of the present invention. For example, the controller pre-configures a plurality of service information, and the controller divides all the function instances into a plurality of function instance groups in advance, and includes one or more function instances in each function instance group, and each function instance group Corresponds to a network slice. Then the controller matches the function instance group according to the specific business information, and can The successfully configured function instance group may be a network slice corresponding to the service, so that the controller can establish a correspondence between different services and different network slices.
  • the communication control method provided by the embodiment of the present invention may further include the following steps:
  • the controller sends the correspondence between the service and the network slice to the service providing server.
  • the service providing server deployed by the service provider can receive the correspondence between the service sent by the controller and the network slice.
  • the controller sends the corresponding relationship between the service and the network slice to the service providing server.
  • the controller may send the corresponding relationship between the service identifier of the service and the slice identifier of the network slice to the service providing server.
  • the service providing server obtains the slice identifier of the corresponding network slice for the service initiated by the user equipment according to the corresponding relationship between the service and the network slice when the user equipment initiates different services.
  • the service provider allocates a slice identifier to the service initiated by the service provider server, or when the user equipment signs the service with the service provider, the service provider sends the service provider through the service provider server.
  • the user equipment allocates a slice identifier.
  • the same user equipment may use the same slice identifier, and the same user equipment may use different slice identifiers according to different services of the same user equipment. Therefore, the service providing server assigns a slice identifier to a user equipment or multiple slice identifiers, which can be flexibly determined according to the needs of the application scenario.
  • the controller 301 obtains the correspondence between the service and the network slice, and specifically includes the following steps:
  • the controller obtains a correspondence between the service and the network slice from the network slice deployment device.
  • the network slice deployment device establishes a correspondence between the service and the network slice, including:
  • the network slice deployment device receives the service information sent by the service providing server, and the service information includes: a service identifier corresponding to the service and a service quality requirement required by the service, or the service information includes: a service identifier corresponding to the service, a service quality requirement required by the service, and a service geographic range;
  • the network segment deployment device deploys the function instance according to the service information, and establishes a correspondence relationship between the function instance and the network slice of the service deployment;
  • the network slice deployment device establishes a correspondence between the service and the network slice according to the function instance deployed for the service, and sends the correspondence between the service and the network slice to the controller.
  • the network slice deployment device may be built in the controller, and the network slice deployment device may be independent of the controller.
  • the network slice deployment device is a functional device dedicated to establishing network slices.
  • the network slicing device establishes an implementation scenario of the correspondence between the service and the network slice through the service information provided by the service providing server.
  • the service providing server sends the service information to the network slice deployment device. If the service providing server has multiple different services, the service information sent by the service providing server to the network slice deployment device may include service information of multiple different services.
  • Each service information includes a service identifier corresponding to the service and a service quality requirement required by the service.
  • the service information includes the service identifier and the service quality requirement required by the service, and the service information may also include the service. geographic range.
  • the regional scope of the service refers to the geographical area in which the service deployment takes effect.
  • the network slice deployment device deploys the function instance according to the business requirements of each service in the service information. Some of the business requirements only need to deploy one functional instance, and some business needs to deploy two or more functional instances.
  • the network slice deployment device After the network slice deployment device deployment function instance is completed, the network slice deployment device attributes the established function instance to the corresponding network slice, thereby establishing a correspondence between the function instance and the network slice, and finally, associating the service with the network slice according to the deployed function instance. Up, so that the correspondence between the establishment of the service and the network slice can be completed.
  • the network slice deployment device can facilitate the use of the controller, and the network slice deployment device can send a correspondence between the service and the network slice to the controller.
  • step 302 and step 303 are used to illustrate that, in the implementation scenario that the first user identifier is corresponding to the first user equipment, the slice identifier used by the first user equipment is the first slice identifier, and different user equipments are used. Different slice IDs can be used.
  • the first user equipment corresponds to the slice identifier x
  • the second user equipment corresponds to the slice identifier y
  • the controller selects the function instance 1 and the function instance 2 corresponding to the slice identifier x according to the slice identifier x
  • the controller identifies the slice identifier according to the slice identifier y Select function example 3 corresponding to slice identifier y.
  • the controller can provide differentiated services for multiple user equipments according to different slice identifiers used by different user equipments.
  • the first user identifier corresponds to the service initiated by the first user equipment
  • different services initiated by the first user equipment correspond to different slice identifiers
  • the controller Different service instances may be assigned to different services initiated by the first user equipment.
  • the first user equipment initiates two services (service a and service b respectively), the service a initiated by the first user equipment corresponds to the slice identifier x, and the service b initiated by the first user equipment corresponds to the slice identifier y.
  • the controller selects the function instance 1 and the function instance 2 corresponding to the slice identifier x according to the slice identifier x, and the controller according to the slice identifier The function instance 3 corresponding to the slice identifier y is selected. Therefore, in the embodiment of the present invention, the controller may implement different function instances for different user equipments, so that different user equipments may be provided with differentiated services. In addition, in the embodiment of the present invention, the controller may also be different for the same user equipment. The service configures different function instances to provide differentiated services for different services of the same user equipment.
  • the controller acquires the correspondence between the service and the network slice in advance, and saves the correspondence between the slice identifier of the network slice and the instance identifier of the function instance on the controller side.
  • the function instance of the service selection initiated by the controller for the first user equipment or the first user equipment is a first function instance, and the first function instance may be a function instance or a plurality of function instances, which is not limited herein.
  • the controller selects the first function instance according to the first slice identifier, it is equivalent to the controller determining that the processing resource and/or the transmission resource are used by the first function instance to provide a processing function for the first user equipment, and the controller selects After the first function instance, the controller notifies the first function instance to be ready to provide processing functions for the first user equipment.
  • the communication control method provided by an embodiment of the present invention may include the following steps:
  • the controller acquires a correspondence between the service and the network slice, where the network slice corresponds to the slice identifier.
  • the controller receives the authentication request message sent by the first UE, where the authentication request message includes: the first service identifier corresponding to the first service of the first UE.
  • the controller selects a home subscriber server (English full name: Home Subscriber Server, HSS for short) according to the authentication request message, and the HSS can be used for identity authentication and slice authentication of the first UE.
  • HSS Home Subscriber Server
  • the controller receives an authentication result of the identity authentication and the slice authentication of the first UE by the HSS sent by the HSS. If the authentication result is that the first UE passes the identity authentication and the slice authentication, the controller determines the first according to the first slice identifier. Function example.
  • the controller separately sends indication information about establishing a bearer to the first UE and the first function instance according to the first slice identifier.
  • the bearer is configured to transmit a data packet corresponding to the first service of the first UE, and the bearer is associated with the first slice identifier, where the indication information carries the identifier of the first UE and the identifier of the first function instance.
  • Step 401 is similar to the implementation of step 301 in the foregoing embodiment, and step 404 is similar to the implementation of step 202 in the foregoing embodiment.
  • Step 405 is similar to the implementation of step 203 in the foregoing embodiment. Explain one by one.
  • step 402 and step 403 are entered. Detailed description of the line.
  • the controller is configured to perform authentication and slice authentication on the first UE before the function instance is allocated to the first UE. Only the first UE performs the identity authentication and the slice authentication, and the controller in step 404 can determine the first function instance according to the first slice identifier. If the first UE does not pass the identity authentication and the slice authentication, the controller does not need to allocate the function instance to the first UE, so as to prevent the processing resource and/or the transmission resource from being used by the illegal user equipment.
  • the controller selects an HSS according to the authentication request message of the first UE, and performs identity authentication and slice authentication on the first UE by the HSS, where the first request is sent by the first UE.
  • the UE may carry the first slice identifier, so that the HSS can perform identity authentication and slice authentication on the first UE. Or the first UE that is sent by the first UE may not carry the first slice identifier.
  • the HSS After the HSS authenticates the identity of the first UE and the slice authentication is passed, the HSS sends the authentication result to the controller. a first slice identifier corresponding to the UE, or a first slice identifier corresponding to the service initiated by the first UE.
  • the communication control method provided by the embodiment of the present invention may further include the following steps:
  • the controller sends the correspondence between the service and the network slice to the HSS, so that the HSS performs slice authentication on the UE according to the correspondence between the service and the network slice.
  • the step D1 needs to be triggered to execute after the step 401 is performed.
  • the corresponding relationship between the service and the network slice sent by the controller to the HSS may be that the controller sends the corresponding relationship between the service identifier of the service and the slice identifier of the network slice to the HSS, and the HSS sends the HSS when the user equipment initiates different services.
  • the user equipment may be provided with identity authentication and slice authentication according to the correspondence between the service and the network slice to determine whether the identity of the user equipment is legal and whether the user equipment has the right to use the network slice.
  • the communication control method provided by an embodiment of the present invention may include the following steps:
  • the controller obtains a correspondence between the service and the network slice, where the network slice corresponds to the slice identifier.
  • the controller receives the policy and the charging execution function (English name: Policy and Charging Enforcement Function, English abbreviation: PCEF).
  • the entity receives the policy and charging rule function. (English full name: Policy and Charging Rules Function, English abbreviation: PCRF)
  • PCRF Policy and Charging Rules Function
  • the controller determines, according to the first slice identifier, a first function instance corresponding to the first slice identifier.
  • the controller separately sends indication information for establishing a bearer to the first UE and the first function instance according to the first slice identifier.
  • the bearer is configured to transmit a data packet corresponding to the first service of the first UE, and the bearer is associated with the first slice identifier, where the indication information carries the identifier of the first UE and the identifier of the first function instance.
  • Step 501 is similar to the implementation of step 301 in the foregoing embodiment, and step 503 is similar to the implementation of step 201 in the foregoing embodiment.
  • Step 504 is similar to the implementation of step 202 in the foregoing embodiment. Explain one by one. Next, step 502 and step 503 will be described in detail.
  • the controller supports the authentication of the user equipment and the authentication of the slice, and the controller needs to perform identity authentication and slice authentication on the first UE before assigning the function instance to the first UE, only the first UE.
  • Step 503 can be triggered by identity authentication and slice authentication. If the first UE does not pass the identity authentication and the slice authentication, the controller does not need to allocate the function instance to the first UE, so as to prevent the processing resource and/or the transmission resource from being used by the illegal user equipment.
  • the first UE sends a service request message to the PCEF entity, where the service request message includes the first slice identifier.
  • the PCRF entity is selected by the PCEF entity according to the service request message, and the first UE is authenticated and sliced by the PCRF entity. After the PCRF entity performs identity authentication and slice authentication on the first UE, the PCRF entity sends the authentication result to the PCEF entity. If the authentication result is that the first UE passes the identity authentication and the slice authentication, the PCEF entity sends an instance request to the controller. Message.
  • the instance request message includes: a first slice identifier obtained by the PCEF entity from the authentication result, and if the controller receives the instance request message sent by the PCEF entity after receiving the authentication result of the first UE by identity authentication and slice authentication, The controller triggers execution of step 503. If the first UE does not pass identity authentication and slice authentication, the PCEF entity does not send an instance request message to the controller.
  • the communication control method provided by the embodiment of the present invention may further include the following steps:
  • E1 The controller sends the correspondence between the service and the network slice to the PCRF entity.
  • the PCRF entity may be configured to perform slice authentication on the UE according to the correspondence between the service and the network slice.
  • step 501 the foregoing step E1 needs to be triggered.
  • the PCRF entity obtains the correspondence between the service and the network slice by using the controller, and the PCRF performs slice authentication on the UE according to the obtained corresponding relationship.
  • the controller sends the correspondence between the service and the network slice to the PCEF entity, and the PCEF entity sends the corresponding relationship to the PCRF entity.
  • the PCRF entity can provide identity authentication and slice authentication for the user equipment according to the correspondence between the service and the network slice, to determine whether the identity of the user equipment is legal and whether the user equipment has the use. Network slice permissions.
  • the correspondence between the service and the network slice obtained by the PCRF entity may also be sent by the controller.
  • the slice network deployment device sends the PCRF to the PCRF.
  • the entity sends a correspondence between the service and the network slice, and the PCRF entity obtains the correspondence between the service and the network slice by using the slice network deployment device.
  • the mapping network deployment device establishes the correspondence between the service and the network slice, the corresponding relationship is stored in an independent database, and the PCRF entity can also obtain the correspondence between the service and the network slice through active access to the database. .
  • the communication control method provided by the embodiment of the present invention is described in the foregoing embodiment from the controller side of the operator.
  • the communication control method provided by the embodiment of the present invention is introduced from the user equipment side. Please refer to FIG.
  • the communication control method provided by the embodiment may specifically include the following steps:
  • the first UE receives the indication information of the bearer corresponding to the first slice identifier, where the indication information carries the identifier of the first UE and the identifier of the first function instance.
  • the controller determines that the first function instance uses the processing resource and/or the transmission resource to provide the first UE with a processing function for the data packet, and the controller separately sends the setup bearer to the first UE and the first function instance.
  • the indication information that the controller sends the bearer to the first UE and the first function instance may be that the controller sends the indication information for establishing the bearer to the first UE and the first function instance by using the PCEF entity.
  • the first UE and the first function instance respectively perform a bearer setup process, where the bearer is a bearer serving the first service of the first UE, where the specific setup manner of the bearer may be referred to The prior art is not described here.
  • the first UE establishes, according to the indication information, a bearer between the first UE and the first function instance of the first service service of the first UE.
  • the bearer is associated with the first network slice, and the slice identifier of the first network slice is the first slice identifier, and the first slice identifier corresponds to the instance identifier of the first function instance.
  • the first UE by using a bearer, transmits a data packet of the first service, where the data packet corresponds to the first slice identifier.
  • the bearer may be used to transmit a data packet corresponding to the first service of the first UE.
  • the data packet corresponding to the first service of the first UE corresponds to the first network slice.
  • the data packet can determine on which bearer the data packet needs to be transmitted by carrying the correspondence with the first network slice.
  • a bearer established between the first UE and the first function instance may be used for transmission of a data packet corresponding to the first service of the first UE.
  • the process of processing the data packet by the first UE in the uplink transmission process and the downlink transmission process is different.
  • the processing process of the data packet by the first function instance in the uplink transmission process and the downlink transmission process is also different.
  • the step 603, by the first UE, by transmitting a data packet corresponding to the first service of the first UE may specifically include the following steps:
  • the first UE sends an uplink data packet to the first function instance by using the bearer, and the first function instance processes the uplink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier; and/or,
  • the first UE sends, by using a bearer, a downlink data packet that is sent after the downlink data packet is processed by using the processing resource and/or the transmission resource corresponding to the first slice identifier by the first function instance.
  • the first UE sends an uplink data packet to the first function instance by using the bearer between the first UE and the first function instance, and the processing resource corresponding to the first slice identifier is used by the first function instance. / or transmission resources to process upstream packets.
  • the specific implementation manner of the first function instance is different, and the processing process of the uplink data packet by the first function instance is also different.
  • the function instance may be a base station, and the first function instance includes a first base station, where the first base station is determined by the controller to provide service for the first UE, where the first base station corresponds to the first network slice, and the first base station may be configured according to the first base station.
  • the processing function provided by the first network slice processes the uplink data packet and transmits the uplink data packet according to the specified transmission function.
  • the first function instance processes the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier.
  • the specific implementation of the first function instance is different, and the processing process of the downlink data packet by the first function instance is also different.
  • the first function instance sends the downlink data packet to the first UE after processing the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier, where the first UE passes between the first UE and the first function instance.
  • the bearer receives the downlink data packet sent by the first function instance.
  • the data packet of the first service corresponds to the first slice identifier, and may specifically include one or more of the following multiple implementation scenarios:
  • the Internet Protocol (English full name: Internet Protocol, IP: quintuple) of the downlink data packet received by the first GW corresponds to the first slice identifier; or
  • the first function instance includes the first data plane function node, the IP data quintuple of the uplink data packet or the downlink data packet transmitted by the first data plane function node, and the virtual local area network identifier (English full name: Virtual Local Area Network Identity, English abbreviation) : (VLAN ID), multi-protocol label switching (English name: Multi-Protocol Label Switch, English abbreviation: MPLS) label, at least one of the bearer identifiers, corresponding to the first slice identifier; or
  • the first function instance includes the first base station, at least one of a physical time-frequency resource, a user identifier, and a connection identifier used by the uplink data packet received by the first base station corresponds to the first slice identifier.
  • the function instance may have multiple implementation manners.
  • the correspondence between the data packet corresponding to the first service of the first UE and the first slice identifier may be A variety.
  • the IP quintuple of the downlink data packet sent by the first GW corresponds to the first slice identifier
  • the downlink data packet sent by the first GW can be obtained through the correspondence between the IP quintuple and the first slice identifier.
  • the slice identifier to be used is the first slice identifier.
  • the IP quintuple, the VLAN ID, the MPLS label, and the bearer identifier of the uplink data packet or the downlink data packet transmitted by the first data plane function node correspond to the first slice identifier.
  • the first data plane function node needs to use the IP quintuple, the VLAN ID, the MPLS label, and the bearer identifier of the uplink data packet or the downlink data packet, and then the foregoing correspondence relationship can be obtained for the uplink data packet or
  • the slice identifier of the IP quintuple, VLAN ID, MPLS label, and bearer identifier of the downlink data packet is the first slice identifier.
  • the physical time-frequency resource, the user identifier, the connection identifier, and the first slice identifier used by the uplink data packet received by the first base station correspond to each other.
  • the first base station needs the physical time-frequency resource, the user identifier, and the connection identifier used by the uplink data packet, and the physical time-frequency resource, the user identifier, and the connection used for the uplink data packet can be obtained through the foregoing correspondence. Identifies the slice ID to be used. A slice identification.
  • the first UE establishes a bearer of the first service service of the first UE according to the indication information of the bearer that is sent by the controller to the first UE and the first function instance.
  • the first UE corresponds to the data packet corresponding to the first service of the first UE, and the data packet corresponding to the first service of the first UE corresponds to the first slice identifier.
  • the controller obtains the correspondence between the service and the network slice according to the first slice identifier, and the slice identifier of the network slice corresponds to the instance identifier of the function instance.
  • the controller may obtain different Slice identification.
  • the first UE requests the controller to allocate a function instance, and the slice identifier corresponding to the first UE is the first slice identifier, or the slice identifier corresponding to the first service initiated by the first UE is the first slice identifier.
  • the controller may obtain a corresponding first function instance according to the first slice identifier, and the first function instance configured by the controller may include one or more function instances. Different functional instances may provide different processing functions using different processing resources and/or transmission resources.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • the communication control method provided by an embodiment of the present invention may include the following steps:
  • the first UE sends an authentication request message to the controller, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE receives indication information that is used to establish a bearer corresponding to the first slice identifier.
  • the first UE establishes, according to the indication information, a bearer between the first UE and the first function instance of the first service service of the first UE.
  • the first UE by using a bearer, transmits a data packet corresponding to the first service of the first UE, where the data packet of the first service corresponds to the first slice identifier.
  • Steps 702 to 704 are similar to the implementations of steps 601 to 603 in the foregoing embodiment, and step 701 is described in detail next.
  • the controller needs to perform identity authentication and slice on the first UE before assigning the function instance to the first UE. Authentication. Only the first UE passes the identity authentication and the slice authentication, and the controller can determine the first function instance corresponding to the first slice identifier according to the obtained first slice identifier corresponding to the first service. If the first UE does not pass the identity authentication and the slice authentication, the controller does not need to allocate the function instance to the first UE, so as to prevent the processing resource and/or the transmission resource from being used by the illegal user equipment. The controller selects the HSS according to the authentication request message of the first UE, and performs the identity authentication and the slice authentication on the first UE by the HSS.
  • the first UE may carry the first slice identifier in the authentication request message sent by the first UE, which is convenient.
  • the HSS performs identity authentication and slice authentication on the first UE, or the first UE in the first UE does not carry the first slice identifier, and the HSS performs identity authentication and slice authentication on the first UE.
  • the first slice identifier corresponding to the first UE or the first slice identifier corresponding to the service initiated by the first UE is carried in the authentication result sent by the HSS to the controller.
  • the first UE After the first UE is authenticated, the first UE performs step 702, and the controller sends the indication information of the bearer to the first UE.
  • the communication control method provided by an embodiment of the present invention may include the following steps:
  • the first UE sends a service request message to the PCEF entity, where the service request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE receives indication information that establishes a bearer corresponding to the first slice identifier.
  • the first UE establishes, according to the indication information, a bearer between the first UE serving as the first service of the first UE and the first function instance.
  • the first UE sends a service request message to the PCEF entity, where the service request message includes: a first service identifier corresponding to the service initiated by the first UE.
  • the steps 802 to 804 are similar to the implementations of the steps 601 to 603 in the foregoing embodiment, and the step 801 is described in detail next.
  • the controller is configured to perform authentication and slice authentication on the first UE before the function instance is allocated to the first UE. If the first UE does not pass the identity authentication and the slice authentication, the controller does not need to allocate the function instance to the first UE, so as to prevent the processing resource and/or the transmission resource from being used by the illegal user equipment.
  • the first UE sends a service request message to the PCEF entity, where the service request message includes a first slice identifier, and the PCEF entity selects a PCRF entity according to the service request message, and the PCRF entity performs identity authentication and slice authentication on the first UE.
  • the PCRF entity After the PCRF entity performs identity authentication and slice authentication on the first UE, the PCRF entity sends the authentication result to the PCEF entity, if the authentication result is A UE passes the identity authentication and slice authentication, and the PCEF entity sends an instance request message to the controller.
  • the instance request message includes: a first slice identifier obtained by the PCEF entity from the authentication result, and the controller selects the first function instance for the first UE according to the received instance request message sent by the PCEF entity, and sends the first function instance to the first UE. Establish instructions for the bearer. If the first UE does not pass identity authentication and slice authentication, the PCEF entity does not send an instance request message to the controller, and the controller does not receive the instance request message sent by the PCEF entity, and the controller does not select a function for the first UE.
  • a first slice identifier obtained by the PCEF entity from the authentication result
  • the controller selects the first function instance for the first UE according to the received instance request message sent by the PCEF entity, and sends the first function instance to the first UE. Establish instructions for the bearer. If the first UE does not pass identity authentication and slice authentication, the PCEF entity does not send an instance request message to the controller, and the controller does not receive the instance request message sent by the PCEF entity, and the controller does not select
  • the foregoing embodiment describes the communication control method provided by the embodiment of the present invention from the controller side and the user equipment side.
  • the communication control method provided by the embodiment of the present invention is introduced from the function example side. Referring to FIG. 9, the present invention is shown in FIG.
  • the communication control method provided by the embodiment may specifically include the following steps:
  • the first function instance receives the indication information of the bearer corresponding to the first slice identifier, where the indication information carries the identifier of the first UE and the identifier of the first function instance.
  • the controller determines that the first function instance uses the processing resource and/or the transmission resource to provide the first UE with a processing function for the data packet, and the controller separately sends the setup bearer to the first UE and the first function instance.
  • the indication information that the controller sends the bearer to the first UE and the first function instance may be that the controller sends the indication information for establishing the bearer to the first UE and the first function instance by using the PCEF entity.
  • the first function instance After the first function instance receives the indication information of the controller, the first function instance and the first UE respectively perform a bearer setup process, where the bearer is a bearer serving the first service of the first UE, where the specific setup manner of the bearer may be Refer to the prior art and will not be described here.
  • the first function instance is established as a bearer between the first UE and the first function instance of the first service service of the first UE according to the indication information of the bearer.
  • the first function instance processes the data packet of the first service transmitted on the bearer by using the processing resource and/or the transmission resource corresponding to the first slice identifier, where the data packet of the first service corresponds to the first slice identifier.
  • the controller determines that the first function instance uses the processing resource and/or the transmission resource to provide the first UE with the processing function of the data packet, and controls And sending, to the first UE and the first function instance, indication information for establishing a bearer, respectively.
  • the indication information that the controller sends the bearer to the first UE and the first function instance may be that the controller sends the indication information for establishing the bearer to the first UE and the first function instance by using the PCEF entity.
  • the indication information of the bearer that is sent by the controller includes a first slice identifier, where the first slice identifier corresponds to the first UE, or corresponds to a service initiated by the first UE.
  • the slice identifier used by the first user equipment is the first slice identifier, and different user equipments may use different slice identifiers in the implementation scenario corresponding to the first user identifier.
  • the first user equipment corresponds to the slice identifier x
  • the second user equipment corresponds to the slice identifier y
  • the controller selects the function instance 1 and the function instance 2 corresponding to the slice identifier x according to the slice identifier x
  • the controller identifies the slice identifier according to the slice identifier y Select function example 3 corresponding to slice identifier y. That is to say, the controller can provide differentiated services for multiple user equipments according to different slice identifiers used by different user equipments.
  • the first user identifier corresponds to the service initiated by the first user equipment
  • different services initiated by the first user equipment correspond to different slice identifiers
  • the controller Different service instances may be assigned to different services initiated by the first user equipment. For example, the first user equipment initiates two services (service a and service b respectively), the service a initiated by the first user equipment corresponds to the slice identifier x, and the service b initiated by the first user equipment corresponds to the slice identifier y.
  • the controller selects the function instance 1 and the function instance 2 corresponding to the slice identifier x according to the slice identifier x, and the controller selects the function instance 3 corresponding to the slice identifier y according to the slice identifier y. Therefore, in the embodiment of the present invention, the controller may implement different function instances for different user equipments, so that different user equipments may be provided with differentiated services. In addition, in the embodiment of the present invention, the controller may also be different for the same user equipment. The service configures different function instances to provide differentiated services for different services of the same user equipment.
  • processing resources and/or transmission resources used by different function instances are different.
  • the function instance may be a base station, a GW, and a data plane function node, and the function examples represent different
  • the entity may have different processing resources and/or transmission resources when it is an entity.
  • the first function instance includes at least one of the following: a first GW, or a first data plane function node, or a first base station.
  • the bearer may be used to transmit a data packet corresponding to the first service of the first UE.
  • the data packet corresponding to the first service of the first UE corresponds to the first network slice.
  • the data packet can determine on which bearer the data packet needs to be transmitted by carrying the correspondence with the first network slice.
  • the bearer established between the first UE and the first function instance may be used for transmission of a data packet corresponding to the first service of the first UE, and the data packet is in the first UE and the first Transfer between a functional instance.
  • the process of processing the data packet by the first UE in the uplink transmission process and the downlink transmission process is different.
  • the logarithm of the first function instance in the uplink transmission process and the downlink transmission process According to the package processing process is not the same.
  • the first function instance of step 903 processes the data packet of the first service transmitted on the bearer by using the processing resource and/or the transmission resource corresponding to the first slice identifier, and may specifically include the following steps. :
  • the first function instance receives the uplink data packet sent by the first UE by using the bearer, and the first function instance processes the uplink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier; and/or,
  • the first function instance processes the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier, and then sends the processed downlink data packet to the first UE by using the bearer.
  • the first UE sends an uplink data packet to the first function instance by using the bearer between the first UE and the first function instance, and the processing resource corresponding to the first slice identifier is used by the first function instance. / or transmission resources to process upstream packets.
  • the specific implementation manner of the first function instance is different, and the processing process of the uplink data packet by the first function instance is also different.
  • the function instance may be a base station, and the first function instance includes a first base station, where the first base station is determined by the controller to provide service for the first UE, where the first base station corresponds to the first network slice, and the first base station may be configured according to the first base station.
  • the processing function provided by the first network slice processes the uplink data packet and transmits the uplink data packet according to the specified transmission function.
  • the first function instance processes the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier.
  • the specific implementation manner of the first function instance is different, and the processing process of the downlink data packet by the first function instance is also different.
  • the first function instance sends the downlink data packet to the first UE after processing the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier, where the first UE passes between the first UE and the first function instance.
  • the bearer receives the downlink data packet sent by the first function instance.
  • the data packet of the first service corresponds to the first slice identifier, and may specifically include one or more of the following multiple implementation scenarios:
  • the IP quintuple of the downlink data packet received by the first GW corresponds to the first slice identifier
  • the first function instance includes the first data plane function node, at least one of an IP quintuple, a VLAN ID, an MPLS label, and a bearer identifier of the uplink data packet or the downlink data packet transmitted by the first data plane function node, and the first Corresponding to a slice identifier; or,
  • the first function instance includes the first base station, at least one of a physical time-frequency resource, a user identifier, and a connection identifier used by the uplink data packet received by the first base station corresponds to the first slice identifier.
  • the function instance may have multiple implementation manners.
  • the correspondence between the data packet corresponding to the first service of the first UE and the first slice identifier may be A variety.
  • the IP quintuple of the downlink data packet sent by the first GW corresponds to the first slice identifier, and the downlink data packet sent by the first GW can be obtained through the correspondence between the IP quintuple and the first slice identifier.
  • the slice identifier to be used is the first slice identifier.
  • the at least one of the IP quintuple, the VLAN ID, the MPLS label, and the bearer identifier of the uplink data packet or the downlink data packet transmitted by the first data plane function node corresponds to the first slice identifier.
  • the first data plane function node needs to use the IP quintuple, the VLAN ID, the MPLS label, and the bearer identifier of the uplink data packet or the downlink data packet, and then the foregoing correspondence relationship can be obtained for the uplink data packet or
  • the slice identifier of the IP quintuple, VLAN ID, MPLS label, and bearer identifier of the downlink data packet is the first slice identifier.
  • the physical time-frequency resource, the user identifier, the connection identifier, and the first slice identifier used by the uplink data packet received by the first base station correspond to each other.
  • the first base station needs the physical time-frequency resource, the user identifier, and the connection identifier used by the uplink data packet, and the physical time-frequency resource, the user identifier, and the connection used for the uplink data packet can be obtained through the foregoing correspondence. Identifies the slice ID to be used as the first slice identifier.
  • the first function instance receives the indication information of the bearer that is sent by the controller to the first function instance and the first UE, and the first function instance is established as the first UE according to the indication information for establishing the bearer.
  • the bearer of the first service service, the bearer and the controller are corresponding to the first network slice selected corresponding to the data packet of the first service of the first UE, and the first function instance uses the processing resource corresponding to the first slice identifier and And the transmission resource processes the data packet corresponding to the first service of the first UE that is transmitted on the bearer, and the data packet corresponding to the first service of the first UE corresponds to the first slice identifier.
  • different service identifiers are used for different services, and different services have different service requirements.
  • different slice identifiers may be obtained.
  • the first UE requests allocation to the controller.
  • the function example is that the slice identifier corresponding to the first UE is the first slice identifier, or the slice identifier corresponding to the first service initiated by the first UE is the first slice identifier, and the controller can obtain the first slice identifier according to the first slice identifier.
  • the first function instance configured by the controller may include one or more function instances, and different function instances may be used.
  • the same processing resources and/or transmission resources provide different processing functions.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • the foregoing embodiment describes a communication control method provided by an embodiment of the present invention from a controller, a UE, and a function instance.
  • another communication control method provided by an embodiment of the present invention is introduced from the UE side, as shown in FIG. 10 .
  • the communication control method provided by the embodiment of the present invention may specifically include the following steps:
  • the first UE sends an uplink scheduling request to the first base station.
  • the uplink scheduling request includes: a first slice identifier or a first connection identifier corresponding to the data packet that the first UE needs to send.
  • the function instance selected by the controller for the first UE is the first base station, and the first UE needs to request the air interface transmission resource from the first base station.
  • the UE requests the air interface transmission resource from the base station, and the air interface transmission resource allocated by the base station to the UE is for the entire UE, and cannot be specific to a certain service for the UE.
  • the processing resources and transmission resources corresponding to different network slices are different.
  • the uplink scheduling request sent by the first UE includes the first slice identifier or the first connection identifier corresponding to the data packet that the first UE needs to send, that is, the air interface transmission resource requested by the first UE to the first base station corresponds to the UE.
  • the different data packets correspond to different slice identifiers or connection identifiers, and the base station allocates different slice identifiers or connection identifiers. Allocate different air interface transmission resources.
  • the uplink scheduling request includes the first slice identifier or the first connection identifier.
  • the uplink scheduling request includes: the first slice corresponding to the data packet that the first UE needs to send.
  • the identifier, or the uplink scheduling request includes: a first connection identifier corresponding to the data packet that the first UE needs to send.
  • the first slice identifier and the first connection identifier are associated with each other.
  • the first UE may carry the first slice identifier in the uplink scheduling request or The first connection identifier, the first base station may determine the first slice identifier by using the first connection identifier.
  • the communication control method provided by the embodiment of the present invention may further include the following steps:
  • the first UE establishes a bearer of the first service service of the first UE according to the indication information of the bearer that is sent by the first UE and the first base station.
  • the controller determines that the first base station uses the processing resource and/or the transmission resource to provide the first UE with a processing function for the data packet, and the controller
  • the first UE and the first base station respectively send indication information for establishing a bearer.
  • the indication information that the controller sends the establishing bearer to the first UE and the first base station may be that the controller sends the indication information for establishing the bearer to the first UE and the first base station by using the PCEF entity.
  • the first UE receives the indication information of the controller, the first UE and the first base station respectively perform a setup process of the bearer, where the bearer is a bearer serving the first service of the first UE.
  • the bearer is a bearer serving the first service of the first UE.
  • the first UE receives resource assignment information sent by the first base station.
  • the resource assignment information includes: a first slice identifier or a first connection identifier, and processing resources and/or transmission resources corresponding to the first slice identifier or the first connection identifier, the processing resource and/or the transmission resource. Includes air interface transmission resources.
  • the first base station may perform the first slice identifier or the first connection identifier.
  • the air interface transmission resource is allocated, and the first base station sends the resource assignment information to the first UE.
  • the resource allocation information includes an air interface transmission resource corresponding to the first slice identifier or the first connection identifier, and the allocated air interface transmission resource corresponds to the first slice identifier or the first connection identifier. Therefore, only the data packet corresponding to the first slice identifier or the first connection identifier in the first UE can use the foregoing air interface transmission resource allocated by the first base station.
  • the air interface transmission resource configured by the first base station to the first UE is an implementation manner of the transmission resource used by the function instance.
  • the communication control method provided by the embodiment of the present invention may further include the following steps:
  • the first UE transmits a data packet corresponding to the first service of the first UE on the air interface transmission resource.
  • the first UE after acquiring the air interface transmission resource allocated by the first base station, uses the air interface transmission resource to transmit a data packet corresponding to the first service of the first UE, where The data packet of the first service of the first UE corresponds to the first network slice.
  • the first UE sends an uplink scheduling request to the first base station.
  • the uplink scheduling request includes: a first slice identifier or a first connection identifier corresponding to the data packet that the first UE needs to send, the first UE receives the resource assignment information sent by the first base station, and the air interface transmission resource allocated by the first base station
  • a slice identifier or a first connection identifier is corresponding, so that the air interface transmission resource allocated by the first base station for different slice identifiers or connection identifiers can implement differentiated processing functions, and thus can meet specific service functions and specific service quality requirements and Specific quality of experience requirements, which can provide differentiated services for different user devices and different services.
  • the foregoing embodiment introduces another communication control method provided by the embodiment of the present invention from the user equipment side.
  • another communication control method provided by the embodiment of the present invention is introduced from the function instance side, and the function example is specifically a base station.
  • the function example selected by the controller according to the first slice identifier is the first base station, as shown in FIG. 11, the communication control method provided by the embodiment of the present invention, the communication control method shown in FIG. 11 and the communication control method shown in FIG.
  • the method corresponding to the communication control method may specifically include the following steps:
  • the first base station receives an uplink scheduling request sent by the first UE.
  • the uplink scheduling request includes: a first slice identifier or a first connection identifier corresponding to the data packet that the UE needs to send.
  • the function instance selected by the controller for the first UE is the first base station, and the first UE needs to request the air interface transmission resource from the first base station.
  • the UE requests the air interface transmission resource from the base station, and the air interface transmission resource allocated by the base station to the UE is for the entire UE, and cannot be specific to a certain service for the UE.
  • the uplink scheduling request sent by the first UE includes the first slice identifier or the first connection identifier corresponding to the data packet that the first UE needs to send.
  • the air interface transmission resource requested by the first UE to the first base station is a first slice identifier or a first connection identifier corresponding to the data packet that the UE needs to send. Therefore, when multiple services are configured in the first UE, the data packets that the UE needs to send are also different, and the different data packets correspond to different slice identifiers or connection identifiers.
  • the uplink scheduling request sent by the first UE includes the first slice identifier or the first connection identifier.
  • the uplink scheduling request includes: the data packet corresponding to the first UE needs to be sent.
  • the first slice identifier, or the uplink scheduling request includes: the first UE needs The first connection identifier corresponding to the sent data packet.
  • the first slice identifier and the first connection identifier are associated with each other.
  • the first UE may carry the first slice identifier in the uplink scheduling request or The first connection identifier, the first base station may determine the first slice identifier by using the first connection identifier.
  • the communication control method provided by the embodiment of the present invention may further include the following steps:
  • the first base station establishes, as the bearer of the first service service of the first UE, the indication information of the bearer that is sent by the first UE and the first base station.
  • the data packet corresponding to the first service of the first UE needs to carry the first slice identifier or the first connection identifier.
  • the controller determines that the first base station uses the processing resource and/or the transmission resource to provide the first UE with a processing function for the data packet.
  • the controller sends the indication information for establishing the bearer to the first UE and the first base station, where the controller sends the indication information for establishing the bearer to the first UE and the first base station, where the controller may be the first UE and the first UE through the PCEF entity.
  • the base station sends indication information for establishing a bearer.
  • the first UE and the first base station respectively perform a setup process of the bearer, where the bearer is a bearer serving the first service of the first UE.
  • the bearer is a bearer serving the first service of the first UE.
  • the first base station allocates processing resources and/or transmission resources corresponding to the first slice identifier or the first connection identifier according to the uplink scheduling request, where the processing resource and/or the transmission resource includes an air interface transmission resource.
  • the first base station acquires the first slice identifier or the first connection identifier from the uplink scheduling request, and then the first base station allocates the air interface transmission resource for the first slice identifier or the first connection identifier, and then allocates
  • the air interface transmission resource can only be used for the first slice identifier or the data packet corresponding to the first connection identifier.
  • the first base station is equipped with two types of network slices: network slice A and network slice B. Network slice A and network slice B respectively have independent air interface transmission resources.
  • the first base station If the two different services in the first base station correspond to the network slice A and the network slice B respectively, if the uplink scheduling request sent by the first UE includes the slice identifier of the network slice A, the first base station according to the slice of the network slice A The identifier allocates an air interface transmission resource. If the uplink scheduling request sent by the first UE includes the slice identifier of the network slice B, the first base station allocates another air interface transmission resource according to the slice identifier of the network slice B.
  • the first base station sends resource assignment information to the first UE, where the resource assignment information includes: a slice identifier or a first connection identifier, and a processing resource and/or a transmission resource corresponding to the first slice identifier or the first connection identifier, where the processing resource and/or the transmission resource includes an air interface transmission resource.
  • the first base station may allocate an air interface transmission resource for the first slice identifier or the first connection identifier, and the first base station sends the resource assignment information to the first UE.
  • the resource allocation information includes an air interface transmission resource corresponding to the first slice identifier or the first connection identifier that is allocated by the first base station, where the allocated air interface transmission resource corresponds to the first slice identifier or the first connection identifier, so Only the data packet corresponding to the first slice identifier or the first connection identifier in a UE can use the above-mentioned air interface transmission resource allocated by the first base station.
  • the communication control method provided by the embodiment of the present invention may further include the following steps:
  • the first base station transmits, on the air interface transmission resource, a data packet corresponding to the first service of the first UE.
  • the first UE may use the air interface transmission resource to transmit a data packet corresponding to the first service of the first UE, where the first base station may be used on the air interface resource.
  • the data packet corresponding to the first service of the first UE corresponds to the first network slice.
  • the first UE sends an uplink scheduling request to the first base station, where the uplink scheduling request includes: a first slice identifier or a first connection identifier corresponding to the data packet that the first UE needs to send, and the first The UE receives the resource assignment information sent by the first base station, and the air interface transmission resource allocated by the first base station corresponds to the first slice identifier or the first connection identifier, so that the first base station allocates the air interface transmission resource for different slice identifiers or connection identifiers.
  • Differentiated processing functions can be implemented. Therefore, it can meet specific business functions as well as specific quality of service requirements and specific quality of experience requirements, so that differentiated services can be provided for different user devices and different services.
  • FIG. 12-a a schematic diagram of a general flow in a process of processing a data packet according to an embodiment of the present invention includes the following three parts:
  • S01 When the service providing server provides the controller deployed by the operator to the requirement for a specific service support in a certain area.
  • the controller processes resources and/or transmission resources and/or function instances for service deployment on a device associated with the specified area to form a network slice.
  • resources and/or transmission resources and/or function instances for service deployment on a device associated with the specified area to form a network slice.
  • different network slices can have different protocol stack processing flows.
  • the specific service is a specific service of the foregoing service providing server in the specified area, and the operator needs to identify that the specific service of the user equipment belongs to a previously deployed one.
  • Network slicing which associates the specific service of the user equipment with a specific network slice.
  • the network side gateway node or the border router receives the downlink data packet of the user service, according to the association relationship established in the foregoing step, identifying that the data packet belongs to the foregoing
  • the network slice is processed based on the corresponding customized processing of the network slice using the resources of the network slice.
  • Figure 12-b is a schematic diagram of an implementation manner of network slice deployment according to an embodiment of the present invention, where the specific process includes:
  • the controller deployed by the operator receives the service request of the service providing server.
  • the controller deployed by the operator receives the service message sent by the service providing server, and the content of the service message includes: meeting a certain service quality/user experience quality requirement for a specific service in a specified geographic area.
  • the service information includes: range information, service identifier, and corresponding service quality/service experience requirements.
  • the service identifier here can correspond to a specific type of service, such as meter reading service, somatosensory game, etc., and can also correspond to a type of user, such as a gold medal user or a silver medal user waiting. This process can be implemented through the northbound open interface of the operator controller.
  • the controller deployed by the operator allocates a slice identifier, and deploys a related function instance to the infrastructure within the scope of the corresponding device in the foregoing scope, and associates the function instance with the slice identifier on the device.
  • a type of function instance only processes the data of the corresponding slice identifier. Among them, a function instance can process only one slice identification data, and can also process multiple slice identification data.
  • the function instance involved and the collection of transmission resources and processing resources are referred to as a network slice.
  • the message sent by the controller to the function instance includes: establishing an instance indication, a function instance type, and a slice identifier. The controller saves the function instance corresponding to the network slice.
  • the controller sends a correspondence between the service and the network slice, and the HSS or the PCRF entity acquires the slice identifier corresponding to the specific service.
  • the controller sends a service response to the service providing server, where the slice identifier is included.
  • FIG. 12 is a schematic diagram of a process of associating a service with a network slice according to an embodiment of the present invention.
  • the specific process includes:
  • the first UE initiates an access authentication request process.
  • the first UE sends an authentication request message to the controller, where the first slice identifier is carried.
  • the first slice identifier of the first UE may be obtained when the user subscribes to the service provider, and the authentication request message may be transmitted through a device such as a base station.
  • the controller receives the authentication request message sent by the first UE, and the controller may perform the HSS selection according to the first slice identifier carried in the authentication request.
  • the HSS authenticates the user and at the same time authorizes whether the user is authorized to utilize a network slice.
  • the HSS has two parts for authentication and authorization of the first UE. One part is the confirmation of the identity of the user equipment, and the second part is to determine whether the first UE can use the first network slice corresponding to the first slice identifier.
  • the HSS After the authentication and the authorization succeed, the HSS returns an authentication result to the controller, where the first slice identifier passed by the first UE authentication and authorization is carried.
  • the controller selects a first function instance serving the first UE according to the received first slice identifier and a correspondence between the network slice saved in the slice deployment phase and the function instance.
  • the first function instance that is selected is sent to the first UE to perform the bearer setup process, and the first slice identifier is carried in the indication for establishing the bearer.
  • the first function instance After receiving the indication for establishing the bearer, the first function instance establishes a bearer serving the first service of the first UE, and establishes a correspondence between the bearer or the data on the bearer and the first network slice.
  • the corresponding relationship may include the following situations: the correspondence between the IP packet quintuple of the GW and the slice identifier, and the IP quintuple/VLAN ID/MPLS label/bearer identifier of the uplink and downlink data packets of the data plane function node. At least one of the corresponding relationship with the slice identifier, the physical time-frequency resource used by the uplink data packet sent by the base station, at least one of the user identifier and the connection identifier, and the correspondence relationship with the slice identifier.
  • the first UE establishes a bearer, and establishes a correspondence between the bearer and the slice identifier, where the correspondence may be: a correspondence between the user identifier and/or the connection identifier and the slice identifier.
  • FIG. 12 is a schematic diagram of a process of associating a service with a network slice according to an embodiment of the present invention.
  • the first UE itself does not have a slice feature, but a specific service that can be initiated belongs to a network slice. .
  • the specific processing procedure is as follows.
  • the first UE initiates a service request process, and sends a service request message to the PCEF entity, where the first slice identifier is carried.
  • the first slice identifier of the first UE may be obtained when the user subscribes to the service provider, and the service request message may be transmitted through a device such as a base station.
  • the PCEF entity performs a service authorization process, and performs a PCRF entity selection according to the first slice identifier carried in the service request message.
  • the PCRF entity authorizes the service of the first UE, while authorizing whether the first UE has the right to use the network slice.
  • the PCRF entity After the authorization succeeds, the PCRF entity returns an authentication result to the PCEF entity, where the first slice identifier passed by the first UE authentication and authorization is carried.
  • the PCEF entity After receiving the first slice identifier, the PCEF entity interacts with the controller, and sends an instance request message carrying the first slice identifier to the controller, where the controller saves according to the first slice identifier and during the slice deployment phase.
  • the function instance selected for the first UE is the first function instance, and the controller returns an instance response to the PCEF entity, where the instance identifier of the first function instance is carried.
  • the PCEF entity notifies the selected first function instance and the first UE to perform a bearer setup process, and carries the first slice identifier in the indication for establishing the bearer. And establishing a correspondence between the downlink data packet and the first network slice.
  • the first function instance After receiving the indication of establishing a bearer, the first function instance establishes a bearer serving the first service of the first UE, and establishes a correspondence between the bearer or the data packet on the bearer and the first network slice.
  • the correspondence The following may be included: the correspondence between the IP packet quintuple of the GW and the slice identifier of the GW, and at least one of the IP quintuple/VLAN ID/MPLS label/bearer identifier of the uplink and downlink data packets of the data plane function node.
  • Corresponding relationship with the slice identifier the physical time-frequency resource used by the uplink data packet sent by the base station, at least one of the user identifier and the connection identifier, and the correspondence relationship with the slice identifier.
  • FIG. 12-e the processing flow of the downlink data packet provided by the embodiment of the present invention is provided.
  • FIG. 12-f is a schematic flowchart of processing an uplink data packet according to an embodiment of the present invention.
  • Figure 12-e shows the downlink process: at the ingress gateway, according to the data characteristics such as the IP quintuple, the network slice to which the downlink data packet belongs is identified, and the data packet is used by using the function instance used by the network slice. Processing and using the transmission resource transmission strategy associated with the network slice for data transmission.
  • the network slice is identified according to the IP quintuple or the bearer used according to the downlink data packet, and the downlink data packet is directed to a specific network slice for processing.
  • the network slice corresponding to the downlink data packet is obtained according to the correspondence between the downlink data packet and the network slice, where the network slice 1, the network slice 2, and the network slice 3 need to perform different processing.
  • the network slice 1 implements a video optimization function for downlink data packets
  • the network slice 2 implements a split function for downlink data packets
  • the network slice 3 implements another split function for downlink data packets
  • the downlink data packets are sliced through the network. 1.
  • the base station After the downlink data packet arrives at the base station, according to different processing functions corresponding to the network slice 1, the network slice 2, and the network slice 3, the base station performs different processing processes, for example, the base station uses the downlink data packet.
  • the shared transmission resource is transmitted, or the downlink data packet is transmitted using a separate transmission resource.
  • a series of function instances have been deployed for the network slice, and a series of function instances are also different in different scenarios.
  • the processing functions of the network layer and the data link layer and the core network and application layer processing functions of the downward movement For example, in the MTC scenario, the processing functions of the network layer and the data link layer, and aggregation processing.
  • the transmission policy used for the transmission resource refers to the VLAN ID/MPLS label assigned to the network slice.
  • the transmission network can provide service guarantee for the network slice according to the above label. If the network segment occupies an independent physical resource, the air interface scheduling will also select the corresponding physical resource to transmit the data packet.
  • the policy corresponding to the network slice also affects the processing behavior of the function instance. For example, it needs to be set according to the transmission policy.
  • the time is 1ms scheduling or 0.1ms scheduling.
  • the uplink process shown in Figure 12-f If the network slice occupies an independent air interface transmission resource, the base station directly identifies the network slice to which the data packet belongs according to the physical resource, and processes according to the previous deployment. If the slice uses a shared air interface to transmit resources, the base station needs to be based on the service access. Or the corresponding relationship established in the process of establishing the service, processing the data packet by using the processing function corresponding to the slice, and transmitting according to the specified transmission policy. As shown in Figure 12-f, the uplink data packet is sent by the first UE to the base station. After acquiring the uplink data packet, the base station identifies the network slice according to the physical resource or according to the bearer, and directs the uplink data packet to a specific network slice for processing.
  • the network slice corresponding to the uplink data packet is obtained according to the correspondence between the uplink data packet and the network slice.
  • the network slice 1 and the network slice 3 need to perform different processing.
  • the network slice 1 corresponds to the GW
  • the network slice 2 corresponds to the multimedia broadcast multicast service (English full name: Multimedia Broadcast Multicast Service, English abbreviation: MBMS) ) Coordinating entity
  • network slice 3 corresponds to another MBMS coordination entity.
  • After the uplink data packet is processed by the network slice 1, the network slice 2, and the network slice 3 using different processing resources it needs to be processed according to different transmission resources used by the network slice 1, the network slice 2, and the network slice 3, according to different transmissions. Path and transport policies are processed.
  • the uplink data packet arrives at different functional entities through different network slices, for example, network slice 1 corresponds to a video selection entity, network slice 2 corresponds to a convergence entity, and network slice 3 corresponds to another aggregation entity.
  • FIG. 12-e and FIG. 12-f the processing procedure of the downlink data packet and the uplink data packet is described.
  • the embodiment of the present invention is further described.
  • An air interface transmission resource request that needs to be performed is described.
  • FIG. 12-g a schematic diagram of a process for allocating air interface transmission resources by a first UE and a first base station according to an embodiment of the present invention includes the following steps:
  • the first UE sends an uplink scheduling request to the first base station.
  • the uplink scheduling request includes: a first slice identifier or a first connection identifier corresponding to the data packet that the first UE needs to send.
  • the first UE Before transmitting the uplink data packet, the first UE needs to send an uplink scheduling request to the first base station to request the first base station to allocate air interface transmission resources for it.
  • the UE's resource request is made for the terminal. That is, the air interface transmission resource allocated by the base station to the UE in the prior art is applicable to all the data packets of the UE, and in the embodiment of the present invention, the uplink scheduling request sent by the first UE carries the first slice identifier or the first The connection identifier, the air interface transmission resource allocated by the first base station is specific to a specific service flow in the first UE. In a scenario where a user terminal has multiple services belonging to different slice networks, the physical resources or scheduling policies corresponding to different network slices are different.
  • the two network slices are used independently.
  • the transmission resource if the first UE has two services corresponding to the A/B slice at the same time, according to the prior art, the terminal sends an uplink resource request. At this time, the base station will not be able to determine which part of the transmission resource is allocated to the terminal.
  • the solution provided by the embodiment of the present invention is as follows: in a scenario where a user equipment has multiple services belonging to different network slices, if the physical resources or scheduling policies corresponding to the different network slices are different, the user equipment is in an uplink scheduling request.
  • the tag identifier or the data connection identifier is required to be carried.
  • the connection identifier may be a logical channel identifier (English name: Logical Channel Identify, English abbreviation: LCID).
  • the uplink scheduling request sent by the first UE carries the first slice identifier or the first connection identifier, so that the first base station can allocate the air interface transmission resource for the uplink request in the correct slice.
  • the first base station sends an acknowledgement message to the first UE.
  • the first base station After receiving the uplink scheduling request sent by the first UE, the first base station returns an acknowledgement message, further.
  • the air interface transmission resource corresponding to the first slice identifier or the first connection identifier is found according to the slice identifier or the UE identifier plus the correspondence between the connection identifier and the network slice.
  • the first base station sends resource assignment information to the first UE.
  • the first base station allocates a transmission resource for the uplink scheduling request of the first UE in the air interface transmission resource, and returns the resource assignment information to the first UE, where the resource assignment information carries the first slice identifier/first connection identifier, And the air interface transmission resource, where the air interface transmission resource corresponds to specific time-frequency resource information.
  • the uplink resource request of the user equipment may not carry the foregoing first slice identifier or the first connection identifier, and only the user identifier is carried by the existing technology.
  • the uplink resource request of the user equipment may also carry the foregoing first slice identifier or the first connection identifier.
  • the base station receives the uplink scheduling request sent by the first UE, the base station searches for the air interface transmission resource corresponding to the scheduling request according to the correspondence between the user identifier and the network slice established in the bearer phase. After the corresponding air interface transmission resource is found, the base station allocates the air interface transmission resource to the first UE, and returns the resource assignment information to the first UE, where the corresponding air interface transmission resource is carried.
  • the embodiment of the present invention can quickly implement processing on data packets, and different user devices can use different function instances to provide different services for different user devices, and can also be used for the same user device. Different services are assigned to different service instances, and different services are implemented on the same user device through different function instances, so that operators can quickly meet different service requirements of service providers.
  • a controller 1300 may include: a function instance determining module 1301, and a sending module 1302, where
  • a function instance determining module 1301, configured to acquire a first slice identifier corresponding to the first service identifier, and determine a first function instance corresponding to the first slice identifier according to the first slice identifier;
  • the sending module 1302 is configured to send, according to the first slice identifier, indication information for establishing a bearer to the first user equipment UE and the first function instance, where the bearer is used to transmit the first service corresponding to the first UE And the indication information carries the identifier of the first UE and the identifier of the first function instance.
  • the controller 1300 further includes: an obtaining module 1303, configured, by the function instance determining module 1301 according to the first and second Before the first slice identifier corresponding to the service determines the first function instance corresponding to the first slice identifier, the corresponding relationship between the service and the network slice is obtained, where the network slice corresponds to the slice identifier.
  • the obtaining module 1303 includes: a first receiving submodule 13031, a function instance deploying submodule 13032, and a corresponding relationship configuration submodule 13033, where
  • the first receiving sub-module 13031 is configured to receive the service information sent by the service providing server, where the service information includes: a service identifier corresponding to the service and a service quality requirement required by the service, or the service information includes: a service corresponding to the service Identification, service quality requirements required by the business, and the regional scope of the business;
  • the function instance deployment sub-module 13032 is configured to deploy a function instance according to the service information, and establish a correspondence relationship between the function instance and the network slice of the service deployment;
  • the corresponding relationship configuration sub-module 13033 is configured to establish a correspondence between the service and the network slice according to the function instance deployed for the service.
  • the sending module 1302 is further configured to: after the acquiring module acquires the correspondence between the service and the network slice, send the corresponding relationship between the service and the network slice to The service providing server.
  • the obtaining module 1303 is specifically configured to obtain a correspondence between a service and a network slice from a network slice deployment device, where the network slice deployment device establishes a correspondence between a service and a network slice, including:
  • the network segment deployment device receives the service information sent by the service providing server, where the service information includes: a service identifier corresponding to the service and a service quality requirement required by the service, or the service information includes: a service identifier corresponding to the service, and a service required Quality of service requirements and the scope of the business;
  • the network segment deployment device deploys a function instance according to the service information, and establishes a correspondence between the function instance of the service deployment and the network slice;
  • the network slice deployment device establishes a correspondence between the service and the network slice according to the function instance deployed for the service, and sends the correspondence between the service and the network slice to the controller.
  • the function instance determining module 1301 includes: a second receiving submodule 13011, an authentication selecting submodule 13012, and a function instance determining submodule 13013, where
  • the second receiving sub-module 13011 is configured to receive an authentication request message sent by the first UE, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE;
  • the authentication selection sub-module 13012 is configured to select a home subscription user server HSS according to the authentication request message
  • the second receiving submodule 13011 is further configured to receive an authentication result that the HSS sent by the HSS performs identity authentication and slice authentication on the first UE.
  • the function instance determining sub-module 13013 is configured to determine, according to the first slice, the first function instance according to the first slice identifier, if the authentication result is that the first UE passes the identity authentication and the slice authentication.
  • the function instance determining module 1301 is specifically configured to receive a policy and a charging execution function.
  • the PCEF entity receives the policy and charging rule function.
  • the first UE passes the identity authentication and the slice sent by the PCRF entity.
  • An instance request message sent after the authentication result of the authentication, the instance request message includes: a first slice identifier obtained by the PCEF from the authentication result; after receiving the instance request message, according to the first A slice identification determines the first functional instance.
  • the sending module 1302 is further configured to send the correspondence between the service and the network slice to an HSS or PCRF entity.
  • the controller selects a first function instance corresponding to the first slice identifier according to the first slice identifier, where the first function instance includes: one or more corresponding to the first slice identifier.
  • the function example is that the controller sends the indication information for establishing the bearer to the first UE and the first function instance, where the bearer is used to transmit the data packet corresponding to the first service of the first UE, and the bearer has the first slice identifier.
  • the first network slice corresponds.
  • different service identifiers are used for different services, and different services have different service requirements.
  • the controller establishes a correspondence between the service and the network slice according to the service requirement, and the slice identifier of the network slice and the instance identifier of the function instance.
  • different slice identifiers may be obtained.
  • the first UE requests the controller to allocate a function instance, and the slice identifier corresponding to the first UE is the first slice identifier, or the first The slice identifier corresponding to the first service initiated by the UE is the first slice identifier, and the controller may obtain the corresponding first function instance according to the first slice identifier, where the first function instance configured by the controller may include one or more Functional examples, different functional instances can provide different processing functions using different processing resources and/or transmission resources.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • a controller provided by an embodiment of the present invention is introduced.
  • a UE provided by an embodiment of the present invention is introduced.
  • the method may include: a receiving module 1401, a bearer establishing module 1402, and a data packet transmitting module 1403, where
  • the receiving module 1401 is configured to receive indication information that is used to establish a bearer corresponding to the first slice identifier, where the indication information carries an identifier of the first UE and an identifier of the first function instance.
  • a bearer establishing module 1402 configured to establish, according to the indication information, a bearer between the first UE and the first function instance that is the first service service of the first UE, where the first function instance is Corresponding to the first slice identifier;
  • the data packet transmission module 1403 is configured to transmit, by using the bearer, the data packet of the first service, where the data packet corresponds to the first slice identifier.
  • the first UE 1400 further includes: a sending module 1404, where
  • the sending module 1404 is configured to send an authentication request message to the controller, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE further includes: a sending module 1404, where
  • the sending module 1404 is configured to send a service request message to the policy and charging execution function PCEF entity, where the service request message includes: a first service identifier corresponding to the first service of the first UE.
  • the data packet transmission module 1403 is specifically configured to send, by using the bearer, an uplink data packet to the first function instance, where the first function instance is used by the first slice identifier. Processing, by the corresponding processing resource and/or transmission resource, the uplink data packet; and/or receiving, by the bearer, the first function instance, using processing resource and/or transmission corresponding to the first slice identifier The downstream data packet sent by the resource after processing the downlink data packet.
  • the first UE 1400 further includes: a sending module 1404, where
  • the sending module 1404 is configured to send an uplink scheduling request to the first base station, where the uplink scheduling request includes: a first slice identifier or a first connection identifier corresponding to the data packet that the first UE needs to send;
  • the receiving module 1401 is further configured to receive the resource assignment information sent by the first base station, where the resource assignment information includes: the first slice identifier or the first connection identifier, and the first A slice identifier or an air interface transmission resource corresponding to the first connection identifier.
  • the first UE is established as the first service of the first UE according to the indication information of the bearer sent by the controller to the first UE and the first function instance.
  • the first UE transmits a data packet corresponding to the first service of the first UE by using a bearer, and the data packet corresponding to the first service of the first UE corresponds to the first network slice.
  • different service identifiers are used for different services, and different services have different service requirements.
  • the controller obtains the correspondence between the service and the network slice, and the slice identifier of the network slice corresponds to the instance identifier of the function instance. When the UE has different service identifiers, the same identifier may be obtained.
  • the first UE requests the controller to allocate a function instance
  • the slice identifier corresponding to the first UE is the first slice identifier, or is initiated by the first UE.
  • the slice identifier corresponding to the first service is the first slice identifier
  • the controller may obtain the corresponding first function instance according to the first slice identifier
  • the first function instance configured by the controller may include one or more function instances. Different functional instances may provide different processing functions using different processing resources and/or transmission resources.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • the foregoing embodiment describes a controller and a user equipment provided by the embodiment of the present invention.
  • a function example provided by the embodiment of the present invention is introduced. Referring to FIG. 15-a, a method provided by the embodiment of the present invention is provided.
  • the first function instance 1500 may include: a receiving module 1501, a bearer establishing module 1502, and a data packet processing module 1503, where
  • the receiving module 1501 is configured to receive the indication information of the bearer corresponding to the first slice identifier, where the indication information carries the identifier of the first user equipment UE and the identifier of the first function instance;
  • the bearer establishing module 1502 is configured to establish, according to the indication information of the bearer, a bearer between the first UE and the first function instance that is the first service service of the first user equipment UE;
  • a data packet processing module 1503 configured to process, by using a processing resource and/or a transmission resource corresponding to the first slice identifier, a data packet corresponding to the first service of the first UE that is transmitted on the bearer, where The data packet corresponding to the first service of the first UE corresponds to the first slice identifier.
  • the first function instance 1500 includes at least one of: a first gateway GW, or a first data plane function node, or a first base station.
  • the first function instance 1500 further includes: a resource allocation module 1504 and a sending module 1505, wherein
  • the receiving module 1501 is further configured to: before the data packet processing module 1503 processes the data packet of the first service transmitted on the bearer by using a processing resource and/or a transmission resource corresponding to the first slice identifier, And receiving, by the first UE, an uplink scheduling request, where the uplink scheduling request includes: the first slice identifier or the first connection identifier corresponding to the data packet that the UE needs to send;
  • the resource allocation module 1504 is configured to allocate, according to the uplink scheduling request, an air interface transmission resource corresponding to the first slice identifier or the first connection identifier;
  • the sending module 1505 is configured to send the resource assignment information to the first UE, where the resource assignment information includes: the first slice identifier or the first connection identifier, and the first cut The slice identifier or the air interface transmission resource corresponding to the first connection identifier.
  • the data packet processing module 1503 is configured to receive, by using the bearer, an uplink data packet sent by the first UE, where the first function instance uses a first slice identifier. And processing the uplink data packet by using the processing resource and/or the transmission resource; and/or processing the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier, and then The first UE sends a downlink data packet after the processing is completed.
  • the data packet corresponding to the first service of the first UE is corresponding to the first slice identifier, and includes:
  • the Internet Protocol IP quintuple of the downlink data packet received by the first GW corresponds to the first slice identifier
  • the IP data quintuple of the uplink data packet or the downlink data packet transmitted by the first data plane function node At least one of a label and a bearer identifier corresponding to the first slice identifier; or
  • the first function instance includes the first base station, at least one of a physical time-frequency resource, a user identifier, and a connection identifier used by the uplink data packet received by the first base station corresponds to the first slice identifier.
  • the first function instance receives the indication information of the bearer that is sent by the controller to the first function instance and the first UE, and the first function instance is established as the first UE according to the indication information for establishing the bearer.
  • the bearer of the first service service, the bearer and the controller are corresponding to the first network slice selected corresponding to the data packet of the first service of the first UE, and the first function instance uses the processing resource corresponding to the first slice identifier and And the transmission resource processes the data packet corresponding to the first service of the first UE that is transmitted on the bearer, and the data packet corresponding to the first service of the first UE corresponds to the first network slice.
  • the controller obtains the correspondence between the service and the network slice, and the slice identifier of the network slice corresponds to the instance identifier of the function instance.
  • the first UE may be configured to allocate a different function identifier. For example, the first UE requests the controller to allocate a function instance, and the slice identifier corresponding to the first UE is the first slice identifier, or the first UE initiates.
  • the slice identifier corresponding to the first service is the first slice identifier
  • the controller may obtain the corresponding first function instance according to the first slice identifier
  • the first function instance configured by the controller may include one or more function instances.
  • Different functional instances may provide different processing functions using different processing resources and/or transmission resources.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium stores a program, and the program executes some or all of the steps described in the foregoing method embodiments.
  • the controller 1600 includes: a sending unit 1601 and a processing unit 1602, where
  • the processing unit 1602 is configured to acquire a first slice identifier corresponding to the first service identifier, and determine, according to the first slice identifier, a first function instance corresponding to the first slice identifier;
  • the sending unit 10601 is configured to separately send the first user equipment UE and the first function instance Sending the indication information of the bearer, where the bearer is used to transmit a data packet corresponding to the first service of the first UE, where the bearer corresponds to the first slice identifier, and the indication information carries the first An identifier of a UE and an identification of the first function instance.
  • the processing unit 1602 is further configured to obtain a correspondence between a service and a network slice, where the network slice corresponds to a slice identifier.
  • the controller 1600 further includes: a first receiving unit 1603, where
  • the first receiving unit 1603 is configured to receive the service information sent by the service providing server, where the service information includes: a service identifier corresponding to the service and a service quality requirement required by the service, or the service information includes: a service identifier corresponding to the service , the quality of service requirements required by the business and the regional scope of the business;
  • the processing unit 1602 is further configured to: deploy a function instance according to the service information, and establish a correspondence between the function instance and the network slice of the service deployment; and establish a correspondence between the service and the network slice according to the function instance deployed for the service .
  • the sending unit 1601 is further configured to send a correspondence between the service and a network slice to the service providing server.
  • the processing unit 1602 is further configured to acquire a correspondence between the service and a network slice from a network slice deployment device.
  • the controller 1600 further includes: a second receiving unit 1604, where
  • the second receiving unit 1604 is configured to receive an authentication request message sent by the first UE, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE;
  • the processing unit 1602 is configured to select a home subscription subscriber server HSS according to the authentication request message;
  • the second receiving unit 1604 is further configured to receive an authentication result that the HSS sent by the HSS performs identity authentication and slice authentication on the first UE.
  • the processing unit 1602 is specifically configured to determine, according to the first slice, the first function instance, according to the first slice identifier, if the authentication result is that the first UE passes identity authentication and slice authentication.
  • the controller 1600 further includes: a third receiving unit 1605, where
  • the third receiving unit 1605 is configured to receive an instance request sent by the PCEF entity after receiving the authentication result of the first UE by the identity authentication and the slice authentication sent by the PCEF entity sent by the policy and charging rule function PCRF entity. a message that the instance request message includes: the first slice identifier obtained by the PCEF entity from the authentication result;
  • the processing unit 1602 is specifically configured to determine, according to the first slice identifier, the first function instance after receiving the instance request message.
  • the sending unit 1601 is further configured to send the correspondence between the service and the network slice to an HSS or PCRF entity.
  • the processing unit 1602 may be a processor, the sending unit 1601 may be a transmitter, and the receiving unit 1603 may specifically be a receiver.
  • the number of the processing units 1602 in the controller 1600 may be one or more, and one processing unit is taken as an example in FIG. 16-a, FIG. 16-b, FIG. 16-c, and FIG. 16-d.
  • the transmitting unit 1601, the receiving unit 1603, and the processing unit 1602 may be connected by a bus or other means.
  • the first receiving unit, the second receiving unit, and the third receiving unit in the foregoing multiple embodiments may be implemented by one receiving unit.
  • the receiving unit may be implemented by two receiving units and three receiving units. Is the receiver.
  • the controller first establishes a correspondence between the service and the network slice according to the service requirement, and then the controller selects the first function instance corresponding to the first slice identifier according to the first slice identifier.
  • the first function instance includes: one or more function instances corresponding to the first slice identifier, and finally the controller separately sends indication information for establishing a bearer to the first UE and the first function instance, where the bearer is used for transmission corresponding to the first a data packet of the first service of the UE, the bearer corresponding to the first network slice having the first slice identifier.
  • different service identifiers are used for different services, and different services have different service requirements.
  • the controller obtains the correspondence between the service and the network slice, and the slice identifier of the network slice corresponds to the instance identifier of the function instance.
  • the first UE may be configured to allocate a different function identifier. For example, the first UE requests the controller to allocate a function instance, and the slice identifier corresponding to the first UE is the first slice identifier, or the first UE initiates.
  • the slice identifier corresponding to the first service is the first slice identifier
  • the controller may obtain the corresponding first function instance according to the first slice identifier, and the first function instance configured by the controller may include one or more function instances. Different functional instances can be served differently using different processing resources and/or transmission resources Processing function.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • the first UE 1700 includes: a receiving unit 1701 and a processing unit 1702, where
  • the receiving unit 1701 is configured to receive indication information for establishing a bearer corresponding to the first slice identifier, where the indication information carries an identifier of the first UE and an identifier of the first function instance;
  • the processing unit 1702 is configured to establish, according to the indication information, a bearer between the first UE and the first function instance that is the first service service of the first UE, where the first function instance is The first slice identifier corresponds to the data packet that is transmitted by the bearer to the first service, where the data packet corresponds to the first slice identifier.
  • the first UE 1700 further includes: a first sending unit 1703, where
  • the first sending unit 1703 is configured to send an authentication request message to the controller, where the authentication request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE 1700 further includes: a second sending unit 1704, where
  • the second sending unit 1704 is configured to send a service request message to the policy and charging execution function PCEF entity, where the service request message includes: a first service identifier corresponding to the first service of the first UE.
  • the first UE 1700 further includes: a third sending unit 1705, where
  • the third sending unit 1705 is configured to send, by using the bearer, an uplink data packet to the first function instance, where the first function instance uses processing resources and/or transmissions corresponding to the first slice identifier.
  • the resource processes the uplink data packet; and/or,
  • the receiving unit 1701 is further configured to: receive, by using the bearer, a downlink data packet that is sent after the first function instance processes the downlink data packet by using processing resources and/or transmission resources corresponding to the first slice identifier. .
  • the first UE 1700 further includes: a fourth sending unit 1706, where
  • the fourth sending unit 1706 is configured to send, by the processing unit, an uplink scheduling request to the first base station by using the bearer to transmit the data packet of the first service, where the uplink scheduling request includes: the first The first slice identifier or the first connection identifier corresponding to the data packet that the UE needs to send;
  • the receiving unit 1701 is configured to receive the resource assignment information that is sent by the first base station, where the resource assignment information includes: the first slice identifier or the first connection identifier, and the first a slice identifier or a processing resource and/or a transmission resource corresponding to the first connection identifier, where the processing resource and/or the transmission resource include an air interface transmission resource.
  • the processing unit 1702 may specifically be a processor, the receiving unit 1701 may specifically be a receiver, and the sending unit 1703 may specifically be a transmitter.
  • the number of the processing units 1702 in the controller 1700 may be one or more, and one processing unit is taken as an example in FIGS. 17-a, 17-b, 17-c, 17-d, and 17-e.
  • the transmitting unit 1703, the receiving unit 1701, and the processing unit 1702 may be connected by a bus or other means.
  • the first sending unit, the second sending unit, the third sending unit, and the fourth sending unit in the foregoing multiple embodiments may be implemented by one sending unit. Of course, two sending units and three sending units may also be used. Four sending units are implemented.
  • the first UE establishes a bearer of the first service service of the first UE according to the indication information of the bearer that is sent by the controller to the first UE and the first function instance, and the first UE passes the And carrying a data packet corresponding to the first service of the first UE, and the data packet corresponding to the first service of the first UE corresponds to the first network slice.
  • different service identifiers are used for different services, and different services have different service requirements.
  • the controller obtains the correspondence between the service and the network slice, and the slice identifier of the network slice corresponds to the instance identifier of the function instance.
  • the first UE may be configured to allocate a different function identifier. For example, the first UE requests the controller to allocate a function instance, and the slice identifier corresponding to the first UE is the first slice identifier, or the first UE initiates.
  • the slice identifier corresponding to the first service is the first slice identifier, and the controller may obtain the corresponding first function instance according to the first slice identifier, and the first function instance configured by the controller may include one or more function instances.
  • Different function instances can use different processing resources and/or transmissions Resources provide different processing capabilities.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • the first function instance 1800 includes: a receiving unit 1801 and a processing unit 1802, where
  • the receiving unit 1801 is configured to receive indication information for establishing a bearer corresponding to the first slice identifier, where the indication information carries an identifier of the first user equipment UE and an identifier of the first function instance;
  • the processing unit 1802 is configured to establish, according to the indication information, a bearer between the first UE and the first function instance that is a first service service of the first user equipment UE, and use the first cut
  • the processing resource and/or the transmission resource corresponding to the slice identifier processes the data packet of the first service transmitted on the bearer, and the data packet of the first service corresponds to the first slice identifier.
  • the first function instance 1800 includes at least one of: a first gateway GW, or a first data plane function node, or a first base station.
  • the first base station further includes: a first sending unit 1803, where
  • the receiving unit 1801 is further configured to: before the processing unit 1802 processes the data packet of the first service transmitted on the bearer by using processing resources and/or transmission resources corresponding to the first slice identifier, And receiving, by the first UE, an uplink scheduling request, where the uplink scheduling request includes: the first slice identifier or the first connection identifier corresponding to the data packet that the UE needs to send;
  • the processing unit 1802 is further configured to allocate processing resources and/or transmission resources corresponding to the first slice identifier or the first connection identifier according to the uplink scheduling request, where the processing resource and/or the transmission resource includes an air interface.
  • Transmission resource
  • the first sending unit 1803 is configured to send, to the first UE, resource assignment information, where the resource assignment information includes: the first slice identifier or the first connection identifier, and The first slice identifier or the processing resource and/or the transmission resource corresponding to the first connection identifier, where the processing resource and/or the transmission resource includes an air interface transmission resource.
  • the first function instance 1800 further includes: a second sending unit 1804, where
  • the receiving unit 1801 is configured to receive, by using the bearer, an uplink data packet sent by the first UE.
  • the processing unit 1802 is specifically configured to process the uplink data packet by using processing resources and/or transmission resources corresponding to the first slice identifier; and/or,
  • the processing unit 1802 is specifically configured to process the downlink data packet by using the processing resource and/or the transmission resource corresponding to the first slice identifier;
  • the second sending unit 1804 is configured to send, by using the bearer, the downlink data packet after the processing is completed to the first UE.
  • the data packet of the first service corresponds to the first slice identifier, and includes:
  • the Internet Protocol IP quintuple of the downlink data packet received by the first GW corresponds to the first slice identifier
  • the IP data quintuple of the uplink data packet or the downlink data packet transmitted by the first data plane function node At least one of a label and a bearer identifier corresponding to the first slice identifier; or
  • the first function instance includes the first base station, at least one of a physical time-frequency resource, a user identifier, and a connection identifier used by the uplink data packet received by the first base station corresponds to the first slice identifier.
  • the processing unit 1802 may specifically be a processor, the sending unit 1803 may specifically be a transmitter, and the receiving unit 1801 may specifically be a receiver.
  • the number of the processing units 1802 in the controller 1800 may be one or more, and one processing unit is taken as an example in FIGS. 18-a, 18-b, and 18-c.
  • the transmitting unit 1803, the receiving unit 1801, and the processing unit 1802 may be connected by a bus or other means.
  • the first sending unit and the second sending unit in the above multiple embodiments may be implemented by one sending unit. Of course, it may also be implemented by two sending units.
  • the first function instance receives the indication information of the bearer that is sent by the controller to the first function instance and the first UE, and the first function instance is established as the first UE according to the indication information for establishing the bearer.
  • the bearer of the first service service, the bearer and the controller correspond to the first network slice selected corresponding to the data packet of the first service of the first UE, and the first function instance is used.
  • the processing resource and/or the transmission resource corresponding to the first slice identifier processes the data packet corresponding to the first service transmitted by the first UE, and the data packet corresponding to the first service of the first UE and the first The network slice corresponds.
  • the controller obtains the correspondence between the service and the network slice, and the slice identifier of the network slice corresponds to the instance identifier of the function instance.
  • the first UE may be configured to allocate a different function identifier. For example, the first UE requests the controller to allocate a function instance, and the slice identifier corresponding to the first UE is the first slice identifier, or the first UE initiates.
  • the slice identifier corresponding to the first service is the first slice identifier
  • the controller may obtain the corresponding first function instance according to the first slice identifier
  • the first function instance configured by the controller may include one or more function instances.
  • Different functional instances may provide different processing functions using different processing resources and/or transmission resources.
  • a corresponding function instance is selected by using a slice identifier, so that different function instances can provide different processing functions by using different processing resources and/or transmission resources according to service requirements, and thus can meet specific service functions and Specific quality of service requirements and specific quality of experience requirements, thus providing differentiated services for different user devices and different services.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be Physical units can be located in one place or distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the connection relationship between the modules indicates that there is a communication connection between them, and specifically, one or more communication buses or signal lines can be realized.
  • the present invention can be implemented by means of software plus necessary general hardware, and of course, dedicated hardware, dedicated CPU, dedicated memory, dedicated memory, Special components and so on.
  • functions performed by computer programs can be easily implemented with the corresponding hardware, and the specific hardware structure used to implement the same function can be various, such as analog circuits, digital circuits, or dedicated circuits. Circuits, etc.
  • software program implementation is a better implementation in more cases.
  • the technical solution of the present invention which is essential or contributes to the prior art, can be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
  • U disk mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM), diskette or optical disk, etc., including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform various embodiments of the present invention Said method.
  • a computer device which may be a personal computer, server, or network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种通信控制方法和控制器、用户设备、功能实例，能够满足不同需求的业务对服务质量的要求。其中，一种通信控制方法，包括：控制器获取与第一业务相对应的第一切片标识；所述控制器根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例；所述控制器向第一用户设备UE和所述第一功能实例分别发送建立承载的指示信息，所述承载用于传输对应于所述第一UE的第一业务的数据包，所述承载和所述第一切片标识对应，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识。

Description

一种通信控制方法和控制器、用户设备、功能实例
本申请要求于2015年9月17日提交中国专利局、申请号为201510593669.0、发明名称为“一种通信控制方法和控制器、用户设备、功能实例”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信领域，尤其涉及一种通信控制方法和控制器、用户设备、功能实例。
背景技术
伴随着信息技术和通讯技术的发展，各种各样的业务层出不穷的涌现出来，比如，以视频业务为代表的高吞吐量业务，以智能抄表、健康服务为代表的物联网海量链接业务，以无人驾驶、车联网为代表的时延敏感业务等等。这些业务的特征以及对于服务质量(英文全称：(Quality of Service，英文简称：QoS)的要求，差别非常巨大，对应到通信网络中相应业务数据的处理，差别也会很大。
不同的业务对于QoS的需求，差别可以很大。对应到通信网络对于这些业务数据的处理，差别也会很大。例如：对于一些时延敏感的业务，数据包从基站传输到核心网再传输到应用服务器，这其中会产生的大量时延，因此可以将核心网及应用层的一些功能下移到基站的位置，从而就可以避免这些时延，以保证业务对于数据包传输和处理的时延要求。
从现有技术来看，通信网络中对于业务数据的处理过程，是完全一致的，没有提供差异化的能力。而运营商也不可能为所有业务，在所有维度上同时提供大而全的最高级别的支持，比如同时为抄表、视频、无人驾驶提供高吞吐量、海量链接及极低时延的支持。因为，一方面这些冗余的特性不是业务所必须的，从而完整的提供这些支持并不能为运营商带来收益；另一方面，庞大的冗余的特性支持，会给运营商带来极大的成本开销。
在前述背景下，基于业务需求的不同以及运营商成本的考虑，网络运营商必须为不同的业务提供不同的处理机制。目前，尚未有通信控制方法和控制器、用户设备、功能实例，能够满足不同需求的业务对服务质量的要求。
发明内容
本发明实施例提供了一种通信控制方法和控制器、用户设备、功能实例，能够满足不同需求的业务对服务质量的要求。
第一方面，本发明实施例提供一种通信控制方法，包括：
控制器获取与第一业务相对应的第一切片标识；
所述控制器根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例；
所述控制器向第一用户设备UE和所述第一功能实例分别发送建立承载的指示信息，所述承载用于传输对应于所述第一UE的第一业务的数据包，所述承载和所述第一切片标识对应，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识。
结合第一方面，在第一方面的第一种可能的实现方式中，所述方法还包括：
所述控制器获取业务和网络切片的对应关系，所述网络切片与切片标识对应。
结合第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述控制器获取业务和网络切片的对应关系，包括：
所述控制器接收业务提供服务器发送的业务信息，所述业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或所述业务信息包括：业务对应的业务标识、业务需要的服务质量要求和业务的区域范围；
所述控制器根据所述业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；
所述控制器根据所述为业务部署的功能实例建立业务和网络切片的对应关系。
结合第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述方法还包括：
所述控制器将所述业务和网络切片的对应关系发送给所述业务提供服务器。
结合第一方面的第一种可能的实现方式，在第一方面的第四种可能的实现方式中，所述控制器获取业务和网络切片的对应关系，包括：
所述控制器从网络切片部署装置获取所述业务和网络切片的对应关系。
结合第一方面或第一方面的第一种可能或第二种可能或第三种可能或第四种可能的实现方式，在第一方面的第五种可能的实现方式中，所述控制器根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例，包括：
所述控制器接收所述第一UE发送的认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识；
所述控制器根据所述认证请求消息选择归属签约用户服务器HSS；
所述控制器接收所述HSS发送的所述HSS对所述第一UE进行身份认证和切片鉴权的认证结果；
若所述认证结果为所述第一UE通过身份认证和切片鉴权，所述控制器根据所述第一切片标识确定所述第一功能实例。
结合第一方面或第一方面的第一种可能或第二种可能或第三种可能或第四种可能的实现方式，在第一方面的第六种可能的实现方式中，所述控制器获取与第一业务相对应的第一切片标识，包括：
所述控制器接收策略及计费执行功能PCEF实体在接收到策略与计费规则功能PCRF实体发送的第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，所述实例请求消息包括：所述PCEF实体从所述认证结果中获取到的所述第一切片标识；
所述控制器根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例包括：
所述控制器接收到所述实例请求消息之后，所述控制器根据所述第一切片标识确定所述第一功能实例。
结合第一方面的第一种可能或第二种可能或第三种可能或第四种可能或第五种可能或第六种可能的实现方式，在第一方面的第七种可能的实现方式中，所述方法还包括：
所述控制器将所述业务和网络切片的对应关系发送给HSS或PCRF实体。
第二方面，本发明实施例还提供一种通信控制方法，包括：
第一用户设备UE接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识；
所述第一UE根据所述指示信息建立为所述第一UE的第一业务服务的所 述第一UE与所述第一功能实例之间的承载，所述第一功能实例与所述第一切片标识对应；
所述第一UE通过所述承载传输所述第一业务的数据包，所述数据包和所述第一切片标识对应。
结合第二方面，在第二方面的第一种可能的实现方式中，所述方法还包括：
所述第一UE向所述控制器发送认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识。
结合第二方面，在第二方面的第二种可能的实现方式中，所述方法还包括：
所述第一UE向策略及计费执行功能PCEF实体发送业务请求消息，所述业务请求消息包括：所述第一UE的第一业务对应的第一业务标识。
结合第二方面或第二方面的第一种可能或第二种可能的实现方式，在第二方面的第三种可能的实现方式中，所述第一UE通过所述承载传输所述第一业务的数据包，包括：
所述第一UE通过所述承载向所述第一功能实例发送上行数据包，由所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
所述第一UE通过所述承载接收所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后发送的下行数据包。
结合第二方面或第二方面的第一种可能或第二种可能或第三种可能的实现方式，在第二方面的第四种可能的实现方式中，所述方法还包括：
所述第一UE向第一基站发送上行调度请求，所述上行调度请求包括：所述第一UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
所述第一UE接收所述第一基站发送的资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和所述第一切片标识或者所述第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
第三方面，本发明实施例还提供一种通信控制方法，包括：
第一功能实例接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有第一用户设备UE的标识和所述第一功能实例的标识；
所述第一功能实例根据所述指示信息建立为第一用户设备UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载；
所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理，所述第一业务的数据包和所述第一切片标识对应。
结合第三方面，在第三方面的第一种可能的实现方式中，所述第一功能实例包括以下至少一个：第一网关GW，或第一数据面功能节点，或第一基站。
结合第三方面的第一种可能的实现方式，在第三方面的第二种可能的实现方式中，若所述第一功能实例为所述第一基站时，所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理之前，所述方法还包括：
所述第一基站接收所述第一UE发送的上行调度请求，所述上行调度请求包括：所述UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
所述第一基站根据所述上行调度请求分配与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源；
所述第一基站向所述第一UE发送资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
结合第三方面或第三方面的第一种可能或第二种可能的实现方式，在第三方面的第三种可能的实现方式中，所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理，包括：
所述第一功能实例通过所述承载接收所述第一UE发送的上行数据包，所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理，然后通过所述承载向所述第一UE发送处理完成后的所述下行数据包。
结合第三方面或第三方面的第一种可能或第二种可能或第三种可能的实现方式，在第三方面的第四种可能的实现方式中，所述第一业务的数据包和所述第一切片标识对应，包括：
当所述第一功能实例包括第一网关GW时，所述第一GW接收的下行数据包的互联网协议IP五元组，和所述第一切片标识对应；或，
当所述第一功能实例包括第一数据面功能节点时，所述第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、虚拟局域网标识VLAN ID、多协议标签交换MPLS标签、承载标识中的至少一个，和所述第一切片标识对应；或，
当所述第一功能实例包括第一基站时，所述第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识中的至少一个，和所述第一切片标识对应。
第四方面，本发明实施例还提供一种控制器，包括：发送单元和处理单元，其中，
所述处理单元，用于获取与第一业务相对应的第一切片标识；根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例；
所述发送单元，用于向第一用户设备UE和所述第一功能实例分别发送建立承载的指示信息，所述承载用于传输对应于所述第一UE的第一业务的数据包，所述承载和所述第一切片标识对应，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识。
结合第四方面，在第四方面的第一种可能的实现方式中，所述处理单元，还用于获取业务和网络切片的对应关系，所述网络切片与切片标识对应。
结合第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，所述控制器，还包括：第一接收单元，其中，
所述第一接收单元，用于接收业务提供服务器发送的业务信息，所述业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或所述业务信息包括：业务对应的业务标识、业务需要的服务质量要求和和业务的区域范围；
所述处理单元，还用于根据所述业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；根据所述为业务部署的功能实例建立业务和网络切片的对应关系。
结合第四方面的第二种可能的实现方式，在第四方面的第三种可能的实现方式中，所述发送单元，还用于将所述业务和网络切片的对应关系发送给所述业务提供服务器。
结合第四方面的第一种可能的实现方式，在第四方面的第四种可能的实现方式中，所述处理单元，还用于从网络切片部署装置获取所述业务和网络切片的对应关系。
结合第四方面或第四方面的第一种可能或第二种可能或第三种可能或第四种可能的实现方式，在第四方面的第五种可能的实现方式中，所述控制器，还包括：第二接收单元，其中，
所述第二接收单元，用于接收第一UE发送的认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识；
所述处理单元，用于根据所述认证请求消息选择归属签约用户服务器HSS；
所述第二接收单元，还用于接收所述HSS发送的所述HSS对所述第一UE进行身份认证和切片鉴权的认证结果；
所述处理单元，具体用于若所述认证结果为所述第一UE通过身份认证和切片鉴权，根据所述第一切片标识确定所述第一功能实例。
结合第四方面或第四方面的第一种可能或第二种可能或第三种可能或第四种可能的实现方式，在第四方面的第六种可能的实现方式中，所述控制器，还包括：第三接收单元，其中，
所述第三接收单元，用于接收策略及计费执行功能PCEF实体在接收到策略与计费规则功能PCRF实体发送的第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，所述实例请求消息包括：所述PCEF实体从所述认证结果中获取到的所述第一切片标识；
所述处理单元，具体用于接收到所述实例请求消息之后，根据所述第一切片标识确定所述第一功能实例。
结合第四方面的第一种可能或第二种可能或第三种可能或第四种可能或第五种可能或第六种可能的实现方式，在第四方面的第七种可能的实现方式中，所述发送单元，还用于将所述业务和网络切片的对应关系发送给HSS或PCRF实体。
第五方面，本发明实施例还提供一种用户设备UE，所述UE具体为第一UE，所述第一UE，包括：接收单元和处理单元，其中，
所述接收单元，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识；
所述处理单元，用于根据所述指示信息建立为所述第一UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载，所述第一功能实例与所述第一切片标识对应；通过所述承载传输所述第一业务的数据包，所述数据包和所述第一切片标识对应。
结合第五方面，在第五方面的第一种可能的实现方式中，所述第一UE，还包括：第一发送单元，其中，
所述第一发送单元，用于向所述控制器发送认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识。
结合第五方面，在第五方面的第二种可能的实现方式中，所述第一UE，还包括：第二发送单元，其中，
所述第二发送单元，用于向策略及计费执行功能PCEF实体发送业务请求消息，所述业务请求消息包括：所述第一UE的第一业务对应的第一业务标识。
结合第五方面或第五方面的第一种可能或第二种可能的实现方式，在第五方面的第三种可能的实现方式中，所述第一UE，还包括：第三发送单元，其中，
所述第三发送单元，用于通过所述承载向所述第一功能实例发送上行数据包，由所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
所述接收单元，还用于通过所述承载接收所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后发送的下行数据包。
结合第五方面或第五方面的第一种可能或第二种可能或第三种可能的实现方式，在第五方面的第四种可能的实现方式中，所述第一UE，还包括：第四发送单元，其中，
所述发送单元，用于所述处理单元通过所述承载传输所述第一业务的数据包之前，通过向第一基站发送上行调度请求，所述上行调度请求包括：所述第 一UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
所述接收单元，用于接收所述第一基站发送的资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和所述第一切片标识或者所述第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
第六方面，本发明实施例提供一种功能实例，所述功能实例具体为第一功能实例，所述第一功能实例，包括：接收单元和处理单元，其中，
所述接收单元，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有第一用户设备UE的标识和所述第一功能实例的标识；
所述处理单元，用于根据所述指示信息建立为第一用户设备UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载；使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理，所述第一业务的数据包和所述第一切片标识对应。
结合第六方面，在第六方面的第一种可能的实现方式中，所述第一功能实例包括以下至少一个：第一网关GW，或第一数据面功能节点，或第一基站。
结合第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中，若所述第一功能实例为第一基站时，所述第一基站，还包括：第一发送单元，其中，
所述接收单元，还用于所述处理单元使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理之前，接收所述第一UE发送的上行调度请求，所述上行调度请求包括：所述UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
所述处理单元，还用于根据所述上行调度请求分配与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源；
所述第一发送单元，用于向所述第一UE发送资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
结合第六方面或第六方面的第一种可能或第二种可能的实现方式，在第六 方面的第三种可能的实现方式中，所述第一功能实例，还包括：第二发送单元，其中，
所述接收单元，用于通过所述承载接收所述第一UE发送的上行数据包；
所述处理单元，具体用于使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
所述处理单元，具体用于使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理；
所述第二发送单元，用于通过所述承载向所述第一UE发送处理完成后的所述下行数据包。
结合第六方面或第六方面的第一种可能或第二种可能或第三种可能的实现方式，在第六方面的第四种可能的实现方式中，所述第一业务的数据包和所述第一切片标识对应，包括：
当所述第一功能实例包括第一网关GW时，所述第一GW接收的下行数据包的互联网协议IP五元组，和所述第一切片标识对应；或，
当所述第一功能实例包括第一数据面功能节点时，所述第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、虚拟局域网标识VLAN ID、多协议标签交换MPLS标签、承载标识中的至少一个，和所述第一切片标识对应；或，
当所述第一功能实例包括第一基站时，所述第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识中的至少一个，和所述第一切片标识对应。
从以上技术方案可以看出，本发明实施例具有以下优点：
本发明实施例中，首先控制器首先获取到与第一业务相对应的第一切片标识，然后控制器根据第一切片标识确定与第一切片标识对应的第一功能实例，控制器根据第一切片标识向第一UE和第一功能实例分别发送建立承载的指示信息，该承载用于传输对应于第一UE的第一业务的数据包。本发明实施例中控制器根据其获取到的第一切片标识能够确定出与第一切片标识对应的第一功能实例，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，不同 的功能实例可以使用与不同切片标识对应的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，可以为不同的用户设备以及不同的业务提供差异化服务。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域的技术人员来讲，还可以根据这些附图获得其他的附图。
图1为本发明实施例中控制器、业务提供服务器、用户设备、功能实例之间的结构关系示意图；
图2为本发明实施例提供的一种通信控制方法的流程方框示意图；
图3为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图4为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图5为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图6为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图7为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图8为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图9为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图10为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图11为本发明实施例提供的另一种通信控制方法的流程方框示意图；
图12-a为本发明实施例提供的数据包的处理流程中总流程示意图；
图12-b为本发明实施例提供的一种网络切片部署的一种实现方式示意图；
图12-c为本发明实施例提供的一种业务与网络切片的关联过程示意图；
图12-d为本发明实施例提供的一种业务与网络切片的关联过程示意图；
图12-e为本发明实施例提供的对下行数据包的处理流程示意图；
图12-f为本发明实施例提供的对上行数据包的处理流程示意图；
图12-g为本发明实施例中第一UE和第一基站实现空口传输资源的分配过程示意图；
图13-a为本发明实施例提供的一种控制器的组成结构示意图；
图13-b为本发明实施例提供的另一种控制器的组成结构示意图；
图13-c为本发明实施例提供的一种获取模块的组成结构示意图；
图13-d为本发明实施例提供的另一种控制器的组成结构示意图；
图14-a为本发明实施例提供的一种第一UE的组成结构示意图；
图14-b为本发明实施例提供的另一种第一UE的组成结构示意图；
图15-a为本发明实施例提供的一种第一功能实例的组成结构示意图；
图15-b为本发明实施例提供的另一种第一功能实例的组成结构示意图；
图16-a为本发明实施例提供的另一种控制器的组成结构示意图；
图16-b为本发明实施例提供的另一种控制器的组成结构示意图；
图16-c为本发明实施例提供的另一种控制器的组成结构示意图；
图16-d为本发明实施例提供的另一种控制器的组成结构示意图；
图17-a为本发明实施例提供的另一种第一UE的组成结构示意图；
图17-b为本发明实施例提供的另一种第一UE的组成结构示意图；
图17-c为本发明实施例提供的另一种第一UE的组成结构示意图；
图17-d为本发明实施例提供的另一种第一UE的组成结构示意图；
图17-e为本发明实施例提供的另一种第一UE的组成结构示意图；
图18-a为本发明实施例提供的另一种第一功能实例的组成结构示意图；
图18-b为本发明实施例提供的另一种第一功能实例的组成结构示意图；
图18-c为本发明实施例提供的另一种第一功能实例的组成结构示意图。
具体实施方式
本发明实施例提供了一种通信控制方法和控制器、用户设备、功能实例，能够满足不同需求的业务对服务质量的要求。
为使得本发明的发明目的、特征、优点能够更加的明显和易懂，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，下面所描述的实施例仅仅是本发明一部分实施例，而非全部实施例。基于本发明中的实施例，本领域的技术人员所获得的所有其他实施例，都属于本发明保护的范围。
本发明的说明书和权利要求书及上述附图中的术语“第一”等是用于区别 类似的对象，“第一”只是特指了某一个或某一类的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本发明的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
首先对本发明实施例提供的通信控制方法中各种方法执行主体进行说明，如图1所示，为本发明实施例中控制器、业务提供服务器、用户设备、功能实例之间的结构关系示意图。控制器可以部署在运营商一侧，控制器为UE确定功能实例，由功能实例为UE提供处理资源和/或传输资源，业务提供商为UE提供业务支持。其中，本发明实施例提供的通信控制方法适用于业务需求清晰，且业务需求类别确定的情况。业务提供服务器位于运营商(英文名称：operator)之上，用于向用户设备提供各种应用服务。运营商用于提供无线网络接入，例如移动、联通、电信等运营商。
本发明实施例涉及的执行主体至少包括：控制器、功能实例、UE，其中，控制器可以用于根据切片标识与功能实例的对应关系来确定功能实例、向UE分配与第一切片标识对应的第一功能实例、触发UE和被选中的第一功能实例建立承载。UE用于向控制器请求分配功能实例、在控制器的触发下建立承载、通过建立完成的承载传输数据包。第一功能实例用于被控制器选中之后在控制器的触发下建立承载、通过与第一切片标识对应的处理资源和/或传输资源提供与该第一功能实例对应的处理功能。
整体上来看，一个网络切片从提出需求到为用户的业务提供服务，可以分为以下几个环节。
首先，运营商根据业务的需求，在网络中部署为该业务提供业务支持的网络切片，网络切片包括需要的各种功能实例，以及相应的处理资源和/或传输资源。其中网络切片的部署过程是与用户无关的。
其次，在用户发起业务时，控制器确定出该业务所对应的网络切片，并在该网络切片所对应的功能实例上为业务建立承载，并建立业务与网络切片的对应关系。
最后，在用户的业务数据传输过程中，功能实例根据建立承载时建立的数据包特征与网络切片的对应关系，找到对应的网络切片，并依据切片信息为业务数据提供数据处理。
在虚拟运营商场景中，在用户接入的认证授权计费环节为用户提供了差异化的认证授权计费处理，但是所有虚拟运营商的业务数据的传输都是共享基础设施运营商提供的一套基础设施，这显然无法满足业务差异化对服务质量的需求。本发明实施例提供的通信控制方法与现有技术是适用于不同的应用场景，并且采用完成不同的技术手段。具体的，本发明与现有技术的应用场景不同，本发明实施例中不是在用户接入网络的环节提供差异认证，而是在数据包的处理环节。另外，本发明与现有技术采用的技术手段不同，本发明实施例中根据业务需求的不同，获取不同业务对应的不同的网络切片，而不同的网络切片分别对应于不同的功能实例，不同的功能实例使用不同的处理资源和/或传输资源提供不同的处理功能，从而使得本发明实施例中可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化的数据包处理服务。
接下来首先从控制器侧介绍本发明实施例提供的通信控制方法，请参阅图2所示，本发明一个实施例提供的通信控制方法，可以包括如下步骤：
201、控制器获取与第一业务相对应的第一切片标识。
202、控制器根据第一切片标识确定与第一切片标识对应的第一功能实例。
在本发明实施例中，控制器首先获取到第一UE的第一业务对应的第一切片标识，控制器中预先设置切片标识和功能实例的对应关系，或者控制器从网络上获取切片标识和功能实例的对应关系。控制器得到第一切片标识之后，控制器先获取到第一功能实例，该第一功能实例可以包括一个或多个功能实例，不同的功能实例使用不同的处理资源和/或传输资源提供不同的处理功能。具体的，第一UE发起的第一业务的业务标识与切片标识相对应，切片标识和功能实例的实例标识相对应。
需要说明的是，第一业务可以是第一UE发起的一个实际业务，第一业务也可以是预先配置的与第一UE直接关联的业务，第一业务的具体实现方式取决于应用场景，此处仅作说明，不作为对本发明的限定。
203、控制器根据第一切片标识向第一UE和第一功能实例分别发送建立 承载的指示信息。
其中，承载用于传输对应于第一UE的第一业务的数据包，承载和第一切片标识对应，指示信息携带有第一UE的标识和第一功能实例的标识。
在本发明实施例中，控制器为第一UE选择出第一功能实例之后，控制器确定由第一功能实例使用处理资源和/或传输资源为第一UE提供对数据包的处理功能，控制器控制第一UE和第一功能实例进行承载建立。具体的，控制器向第一UE和第一功能实例分别发送建立承载的指示信息，该承载用于传输对应于第一UE的第一业务的数据包，该承载和具有第一切片标识的第一网络切片对应。控制器指示第一UE和第一功能实例建立的承载用于传输对应于第一UE的第一业务的数据包，因此可以通过第一切片标识来识别上述承载。第一UE和第一功能实例接收到控制器的指示信息之后，第一UE和第一功能实例分别执行承载的建立过程，其中承载的具体建立方式可以参阅现有技术，此处不再赘述。
通过前述实施例对本发明的描述可知，控制器根据第一切片标识可以获取到对应的第一功能实例，不同的功能实例可以使用与不同切片标识对应的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，可以为不同的用户设备以及不同的业务提供差异化服务。
接下来从控制器侧介绍本发明实施例提供的另一种通信控制方法，请参阅图3所示，本发明一个实施例提供的通信控制方法，可以包括如下步骤：
301、控制器获取业务和网络切片的对应关系，网络切片与切片标识对应。
302、控制器获取与第一业务相对应的第一切片标识。
303、控制器根据第一切片标识确定与第一切片标识对应的第一功能实例。
304、控制器根据第一切片标识向第一UE和第一功能实例分别发送建立承载的指示信息。
其中，承载用于传输对应于第一UE的第一业务的数据包，承载和第一切片标识对应，指示信息携带有第一UE的标识和第一功能实例的标识。
其中，步骤302和前述实施例中步骤201的实现方式相类似，步骤303和前述实施例中步骤202的实现方式相类似，步骤304和前述实施例中步骤 203的实现方式相类似，此处不再描述。接下来对步骤301进行详细说明。
在本发明实施例中，控制器可以由运营商来部署，运营商向业务提供商提供业务支撑，控制器根据业务需求建立业务和网络切片的对应关系，步骤301中所述的业务和网络切片的对应关系是泛指所有的业务分别与不同的网络切片的对应关系。其中，网络切片可以指的是为满足特定业务需求所涉及到的功能实例以及传输资源、处理资源的集合，对于不同的业务需求，控制器需要建立不同的网络切片。
不同的网络切片可以有不同的协议栈处理流程，每个网络切片分别对应有一个或多个功能实例，不同的功能实例可以使用不同的处理资源和/或传输资源提供不同的处理功能。即，每个功能实例都对应有处理资源，或者对应有传输资源，或者对应有处理资源和传输资源，一个网络切片对应有一个或多个功能实例，因此通过网络切片就可以确定出与该网络切片对应的功能实例使用的处理资源和/或传输资源。
处理资源和传输资源可以为业务提供具体的处理功能，处理资源可以是对应到中央处理器(英文全称：Central Processing Unit，英文简称：CPU)、核等计算资源，传输资源可以对应到网络带宽等资源，例如功能实例具体为基站时，该传输资源具体可以指的是空口传输资源。其中，不同的功能实例使用的处理资源和/或传输资源是不同的，例如，功能实例可以包括：基站、网关(英文全称：Gateway，英文简称：GW)以及数据面功能(英文全称：Data Plane Function，英文简称：DPFn)节点，在功能实例表示不同的实体时其对应的处理资源和/或传输资源可以不同。
需要说明的是，在本发明实施例中，网络切片是以灵活的方式建立，例如可以基于速度，容量和覆盖率的不同来设置不同的网络切片，不同的网络切片可以满足每个具体业务的具体要求。网络切片包括：由多个可定制的软件定义的功能实现的连接服务，例如，可以根据管理地域覆盖范围，持续时间，容量，速度，延迟，鲁棒性，安全性和可用性这些业务要求中的一个或一些要求来建立具体的网络切片。
在本发明实施例中，业务需求是指业务对处理资源和/或传输资源的具体需求，当业务不同时其具体的业务需求是不相同的，业务需求不同时也可以认为业务是不相同的。例如，业务具体可以为机器类型通信(英文全称：Machine  Type Communication，英文简称:MTC)中的海量抄表业务或者体感游戏等，不同的业务就决定了其对处理资源和/或传输资源具有不同的需求。
本发明的一些实施例中，控制器在用户设备(英文全称：User Equipment，英文简称：UE)发起业务之前可以提前获取到多种业务分别与网络切片的对应关系。具体的，在本发明的一些实施例中，步骤301控制器获取业务和网络切片的对应关系，具体可以包括如下步骤：
A1、控制器接收业务提供服务器发送的业务信息，其中，业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或业务信息包括：业务对应的业务标识、业务需要的服务质量要求和业务的区域范围；
A2、控制器根据业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；
A3、控制器根据为业务部署的功能实例建立业务和网络切片的对应关系。
在本发明实施例中，步骤A1至步骤A3中描述了运营商中部署的控制器通过与业务提供商中部署的业务提供服务器建立业务和网络切片的对应关系。业务提供商中部署的业务提供服务器向控制器发送业务信息。若业务提供服务器中设置有多种不同的业务，业务提供服务器向控制器发送的业务信息中可以包括多种不同业务的业务信息。
其中，每个业务信息中都包括有业务对应的业务标识、业务需要的服务质量要求，另外，业务信息除了包括：业务对应的标识和业务需要的服务质量要求以外，业务信息还可以业务的区域范围，其中业务的区域范围指的是该业务部署生效的地理区域。控制器根据业务信息中每个业务的业务需求部署功能实例，其中有的业务需求只需要部署一个功能实例即可，有的业务需求就需要部署两个或者更多的功能实例。控制器部署功能实例完成之后，控制器将建立的功能实例归属到对应的网络切片，从而建立功能实例和网络切片的对应关系，最后再根据部署的功能实例将业务和网络切片关联起来，从而可以完成建立业务和网络切片的对应关系。
举例说明，业务提供服务器中设置有三种业务，分别为业务a、业务b、业务c。在业务a中的业务信息a中包括有业务a对应的业务标识a’、业务a需要的服务质量要求、业务a的区域范围。在业务b的业务信息b中包括有业务b对应的业务标识b’、业务b需要的服务质量要求、业务b的区域范围。在 业务c的业务信息c中包括有业务c对应的业务标识c’、业务c需要的服务质量要求、业务c的区域范围。控制器接收到业务提供服务器发送的三个业务的业务信息之后，控制器可以为这三个业务分别部署功能实例，并建立功能实例与网络切片的对应关系。例如，控制器根据业务a的业务需求为业务a部署了功能实例1、功能实例2，则为业务a部署的功能实例1、功能实例2对应于一个网络切片x，控制器可以建立功能实例1、功能实例2和网络切片x的对应关系。控制器根据业务b的业务需求为业务b部署了功能实例3，则为业务b部署的功能实例3对应于一个网络切片y。控制器可以建立功能实例3和网络切片y的对应关系，控制器根据业务c的业务需求为业务c部署了功能实例4、功能实例5、功能实例6，则为业务c部署的功能实例4、功能实例5和功能实例6对应于一个网络切片z，控制器可以建立功能实例4、功能实例5、功能实例6和网络切片z的对应关系。通过部署不同的功能实例，控制器建立了业务a和网络切片x的对应关系，控制器建立了业务b和网络切片y的对应关系，控制器建立了业务c和网络切片z的对应关系。其中，a、b、c、1、2、x、y、z均用于标识一个特定的对象以区别于其他对象。通过上述举例可知，控制器为业务部署的功能实例与网络切片的对应关系可以如下表1所示：
表1为业务、功能实例、网络切片之间的对应关系表：
Figure PCTCN2016097649-appb-000001
需要说明的是，在前述举例中以三个业务为例，在实际应用中可以按照前述举例的实现方式，控制器可以针对更多的业务来分别部署功能实例以及建立不同业务与网络切片的对应关系。另外，前述步骤A1至A3中描述的建立业务和网络切片的对应关系的一种应用场景。不限定的是，本发明实施例中控制器还可以采用其他的方式来建立业务和网络切片的对应关系。例如，控制器预先配置了多种业务信息，控制器将所有的功能实例提前进行划分成多个功能实例组，在每个功能实例组中包括有一个或多个功能实例，每个功能实例组对应于一个网络切片。然后控制器根据具体的业务信息来匹配功能实例组，能够匹 配成功的功能实例组就可以是与业务对应的网络切片，从而控制器可以建立不同业务与不同网络切片的对应关系。
在本发明实施例中执行前述步骤A1至A3的实现场景下，步骤301控制器获取业务和网络切片的对应关系之后，本发明实施例提供的通信控制方法还可以包括如下步骤：
B1、控制器将业务和网络切片的对应关系发送给业务提供服务器。
其中，业务提供商部署的业务提供服务器可以接收到控制器发送的业务和网络切片的对应关系。控制器向业务提供服务器发送业务和网络切片的对应关系具体可以是控制器将业务的业务标识与网络切片的切片标识相对应的对应关系发送给业务提供服务器。那么业务提供服务器在用户设备发起不同的业务时，业务提供服务器就可以根据业务和网络切片的对应关系为用户设备发起的业务获取到对应的网络切片的切片标识。
举例说明如下，在用户设备与业务提供商签约时业务提供商通过业务提供服务器向该用户设备发起的业务分配切片标识，或，在用户设备与业务提供商签约时业务提供商通过业务提供服务器向该用户设备分配切片标识。其中，本发明实施例中同一个用户设备可以使用同一个切片标识，同一个用户设备也可以根据同一个用户设备的不同业务使用不同的切片标识。因此业务提供服务器向一个用户设备分配一个切片标识还是多个切片标识具体可以根据应用场景的需要来灵活确定。
在本发明的另一些实施例中，步骤301控制器获取业务和网络切片的对应关系，具体可以包括如下步骤：
C1、控制器从网络切片部署装置获取业务和网络切片的对应关系。
其中，网络切片部署装置建立业务和网络切片的对应关系，包括：
网络切片部署装置接收业务提供服务器发送的业务信息，业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或业务信息包括：业务对应的业务标识、业务需要的服务质量要求和业务的区域范围；
网络切片部署装置根据业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；
网络切片部署装置根据为业务部署的功能实例建立业务和网络切片的对应关系，并将业务和网络切片的对应关系发送给控制器。
其中，网络切片部署装置可以是内置于控制器中，网络切片部署装置也可以独立于控制器之外。网络切片部署装置为一个专用于建立网络切片的功能装置。网络切片装置通过业务提供服务器提供的业务信息建立了业务和网络切片的对应关系的实现场景。业务提供服务器向网络切片部署装置发送业务信息，若业务提供服务器中设置有多种不同的业务，业务提供服务器向网络切片部署装置发送的业务信息中可以包括多种不同业务的业务信息。
其中，每个业务信息中都包括有业务对应的业务标识、业务需要的服务质量要求，另外，业务信息除了包括：业务对应的标识和业务需要的服务质量要求以外，业务信息还可以包括业务的区域范围。其中业务的区域范围指的是该业务部署生效的地理区域。网络切片部署装置根据业务信息中每个业务的业务需求部署功能实例。其中有的业务需求只需要部署一个功能实例即可，有的业务需求就需要部署两个或者更多的功能实例。网络切片部署装置部署功能实例完成之后，网络切片部署装置将建立的功能实例归属到对应的网络切片，从而建立功能实例和网络切片的对应关系，最后再根据部署的功能实例将业务和网络切片关联起来，从而可以完成建立业务和网络切片的对应关系。网络切片部署装置为便于控制器的使用，网络切片部署装置可以向控制器发送业务和网络切片的对应关系。
接下来对前述步骤302和步骤303进行举例说明，在第一切片标识和第一用户设备相对应的实现场景中，第一用户设备使用的切片标识是第一切片标识，不同的用户设备可以使用不同的切片标识。举例说明，第一用户设备对应于切片标识x，第二用户设备对应于切片标识y，则控制器根据切片标识x选择与切片标识x对应的功能实例1和功能实例2，控制器根据切片标识y选择与切片标识y对应的功能实例3。也就是说，控制器根据不同的用户设备使用的不同切片标识可以为多个用户设备提供差异化服务。在第一切片标识和第一用户设备发起的业务相对应的实现场景中，第一用户设备在发起有多种业务时，第一用户设备发起的不同业务对应有不同的切片标识，控制器为第一用户设备发起的不同业务可以分配不同的功能实例。举例说明，第一用户设备发起了两个业务(分别为业务a和业务b)，第一用户设备发起的业务a对应于切片标识x，第一用户设备发起的业务b对应于切片标识y，则控制器根据切片标识x选择与切片标识x对应的功能实例1和功能实例2，控制器根据切片标 识y选择与切片标识y对应的功能实例3。因此本发明实施例中控制器可以实现对不同的用户设备配置不同的功能实例，从而可以为不同的用户设备提供差异化服务，另外本发明实施例中控制器还可以对同一个用户设备的不同业务配置不同的功能实例，从而可以为同一个用户设备的不同业务提供差异化服务。
需要说明的是，在本发明实施例中，控制器提前获取到业务和网络切片的对应关系，在控制器侧保存有网络切片的切片标识和功能实例的实例标识的对应关系。控制器为第一用户设备或者第一用户设备发起的业务选择的功能实例为第一功能实例，该第一功能实例可以是一个功能实例，也可以是多个功能实例，此处不做限定。控制器根据第一切片标识选择了第一功能实例之后，就相当于控制器确定由第一功能实例来使用处理资源和/或传输资源为第一用户设备提供处理功能，控制器在选择出第一功能实例之后，控制器会通知第一功能实例做好为第一用户设备提供处理功能的准备。
接下来从控制器侧介绍本发明实施例提供的另一种通信控制方法，请参阅图4所示，本发明一个实施例提供的通信控制方法，可以包括如下步骤：
401、控制器获取业务和网络切片的对应关系，网络切片与切片标识对应。
402、控制器接收第一UE发送的认证请求消息，认证请求消息包括：第一UE的第一业务对应的第一业务标识。
403、控制器根据认证请求消息选择归属签约用户服务器(英文全称：Home Subscriber Server，英文简称：HSS)，HSS可用于对第一UE进行身份认证和切片鉴权。
404、控制器接收HSS发送的HSS对第一UE进行身份认证和切片鉴权的认证结果，若认证结果为第一UE通过身份认证和切片鉴权，控制器根据第一切片标识确定第一功能实例。
405、控制器根据第一切片标识向第一UE和第一功能实例分别发送建立承载的指示信息。
其中，承载用于传输对应于第一UE的第一业务的数据包，承载和第一切片标识对应，指示信息携带有第一UE的标识和第一功能实例的标识。
其中，步骤401和前述实施例中步骤301的实现方式相类似，步骤404和前述实施例中步骤202的实现方式相类似，步骤405和前述实施例中步骤203的实现方式相类似，此处不再逐一说明。接下来对步骤402和步骤403进 行详细说明。
在本发明实施例支持对用户设备进行认证以及切片鉴权的应用场景中，控制器在为第一UE分配功能实例之前需要先对该第一UE进行身份认证和切片鉴权。只有第一UE通过身份认证和切片鉴权，才能执行步骤404中的控制器根据第一切片标识确定第一功能实例。若第一UE没有通过身份认证和切片鉴权，控制器不需要为该第一UE分配功能实例，以避免处理资源和/或传输资源被不合法的用户设备使用。步骤402至步骤404的应用场景中，控制器根据第一UE的认证请求消息选择出HSS，由HSS对第一UE进行身份认证和切片鉴权，在第一UE发送的认证请求消息中第一UE可以携带第一切片标识，便于HSS对第一UE进行身份认证和切片鉴权。或者在第一UE发送的认证请求消息第一UE也可以不携带第一切片标识，HSS对第一UE进行身份认证和切片鉴权通过之后，HSS发送给控制器的认证结果中携带与第一UE对应的第一切片标识，或者与第一UE发起的业务对应的第一切片标识。
需要说明的是，在本发明的前述实施例中步骤401控制器获取业务和网络切片的对应关系之后，本发明实施例提供的通信控制方法还可以包括如下步骤：
D1、控制器将业务和网络切片的对应关系发送给HSS，以使HSS根据业务和网络切片的对应关系对UE进行切片鉴权。
在本发明实施例支持对用户设备进行认证以及切片鉴权的应用场景中，步骤401执行之后还需要触发上述步骤D1执行。控制器向HSS发送业务和网络切片的对应关系具体可以是控制器将业务的业务标识与网络切片的切片标识相对应的对应关系发送给HSS，那么HSS在用户设备发起不同的业务时，HSS就可以根据业务和网络切片的对应关系为用户设备提供身份认证和切片鉴权，以判断用户设备的身份是否合法以及该用户设备是否拥有使用网络切片的权限。
接下来从控制器侧介绍本发明实施例提供的另一种通信控制方法，请参阅图5所示，本发明一个实施例提供的通信控制方法，可以包括如下步骤：
501、控制器获取业务和网络切片的对应关系，网络切片与切片标识对应。
502、控制器接收策略及计费执行功能(英文全称：Policy and Charging Enforcement Function，英文简称：PCEF)实体在接收到策略与计费规则功能 (英文全称：Policy and Charging Rules Function，英文简称：PCRF)实体发送的第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，实例请求消息包括：PCEF实体从认证结果中获取到的第一切片标识。
503、控制器接收到实例请求消息之后，控制器根据第一切片标识确定与第一切片标识对应的第一功能实例。
504、控制器根据第一切片标识向第一UE和第一功能实例分别发送建立承载的指示信息。
其中，承载用于传输对应于第一UE的第一业务的数据包，承载和第一切片标识对应，指示信息携带有第一UE的标识和第一功能实例的标识。
其中，步骤501和前述实施例中步骤301的实现方式相类似，步骤503和前述实施例中步骤201的实现方式相类似，步骤504和前述实施例中步骤202的实现方式相类似，此处不再逐一说明。接下来对步骤502和步骤503进行详细说明。
在本发明实施例支持对用户设备进行认证以及切片鉴权的应用场景中，控制器在为第一UE分配功能实例之前需要先对该第一UE进行身份认证和切片鉴权，只有第一UE通过身份认证和切片鉴权，才能触发执行步骤503。若第一UE没有通过身份认证和切片鉴权，控制器不需要为该第一UE分配功能实例，以避免处理资源和/或传输资源被不合法的用户设备使用。步骤502至503的应用场景中，第一UE向PCEF实体发送业务请求消息，业务请求消息中包括有第一切片标识。由PCEF实体根据业务请求消息选择PCRF实体，由PCRF实体对第一UE进行身份认证和切片鉴权。PCRF实体对第一UE进行身份认证和切片鉴权通过之后，PCRF实体向PCEF实体发送给认证结果，若该认证结果为第一UE通过身份认证和切片鉴权，PCEF实体向控制器发送实例请求消息。实例请求消息包括：PCEF实体从认证结果中获取到的第一切片标识，若控制器接收到PCEF实体在接收到第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，控制器触发执行步骤503。若第一UE没有通过身份认证和切片鉴权，则PCEF实体不会向控制器发送实例请求消息。
需要说明的是，在本发明的前述实施例中步骤501控制器获取业务和网络切片的对应关系之后，本发明实施例提供的通信控制方法还可以包括如下步骤：
E1、控制器将业务和网络切片的对应关系发送给PCRF实体。
其中，PCRF实体可用于根据业务和网络切片的对应关系对UE进行切片鉴权。
在本发明实施例支持对用户设备进行认证以及切片鉴权的应用场景中，步骤501执行之后还需要触发上述步骤E1执行。PCRF实体通过控制器获取到业务和网络切片的对应关系，PCRF根据获取到的上述对应关系对UE进行切片鉴权。例如，控制器将业务和网络切片的对应关系发送给PCEF实体，由PCEF实体发送给PCRF实体。那么PCRF实体在用户设备发起不同的业务时，PCRF实体就可以根据业务和网络切片的对应关系为用户设备提供身份认证和切片鉴权，以判断用户设备的身份是否合法以及该用户设备是否拥有使用网络切片的权限。
在本发明的另一些支持对用户设备进行认证以及切片鉴权的应用场景中，PCRF实体获取到业务和网络切片的对应关系也可以不通过控制器来发送，例如，切片网络部署装置向该PCRF实体发送业务和网络切片的对应关系，PCRF实体通过切片网络部署装置来获取到业务和网络切片的对应关系。又如，切片网络部署装置在建立业务和网络切片的对应关系之后，将该对应关系存储到一个独立的数据库中，PCRF实体还可以通过对该数据库的主动访问获取到业务和网络切片的对应关系。
上述实施例从运营商部署的控制器侧介绍了本发明实施例提供的通信控制方法，接下来从用户设备侧介绍本发明实施例提供的通信控制方法，请参阅如图6所示，本发明实施例提供的通信控制方法，具体可以包括如下步骤：
601、第一UE接收建立与第一切片标识对应的承载的指示信息，指示信息携带有第一UE的标识和第一功能实例的标识。
在本发明实施例中，控制器确定由第一功能实例使用处理资源和/或传输资源为第一UE提供对数据包的处理功能，控制器向第一UE和第一功能实例分别发送建立承载的指示信息。其中，控制器向第一UE和第一功能实例发送建立承载的指示信息可以是控制器通过PCEF实体向第一UE和第一功能实例发送建立承载的指示信息。第一UE接收到控制器的指示信息之后，第一UE和第一功能实例分别执行承载的建立过程，该承载是为第一UE的第一业务服务的承载，其中承载的具体建立方式可以参阅现有技术，此处不再赘述。
602、第一UE根据指示信息建立为第一UE的第一业务服务的第一UE和第一功能实例之间的承载。
其中，该承载和第一网络切片对应，第一网络切片的切片标识为第一切片标识，第一切片标识和第一功能实例的实例标识相对应。
603、第一UE通过承载传输第一业务的数据包，数据包和第一切片标识对应。
在本发明实施例中，第一UE根据控制器发送的建立承载的指示信息建立承载完成之后，该承载可以用于传输对应于第一UE的第一业务的数据包。其中，对应于第一UE的第一业务的数据包和第一网络切片对应。数据包通过承载与第一网络切片的对应关系可以确定数据包需要可以在哪个承载上传输。
需要说明的是，在本发明实施例中，第一UE和第一功能实例之间建立的承载可用于对应于第一UE的第一业务的数据包的传输。在上行传输过程和下行传输过程中第一UE对数据包的处理过程是不相同的，同样的，在上行传输过程和下行传输过程中第一功能实例对数据包的处理过程也是不相同的。在本发明的一些实施例中，步骤603第一UE通过承载传输对应于第一UE的第一业务的数据包，具体可以包括如下步骤：
E1、第一UE通过承载向第一功能实例发送上行数据包，由第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对上行数据包进行处理；和/或，
E2、第一UE通过承载接收第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后发送的下行数据包。
其中，对于上行传输过程，第一UE通过第一UE和第一功能实例之间的承载向第一功能实例发送上行数据包，由第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对上行数据包进行处理。其中，对于第一功能实例的具体实现方式不同，第一功能实例对上行数据包的处理过程也不相同。例如功能实例具体可以为基站，则第一功能实例包括第一基站，该第一基站由控制器确定用于为第一UE提供服务，第一基站对应于第一网络切片，第一基站可以根据第一网络切片提供的处理功能对上行数据包进行处理，并按照指定的传输功能对上行数据包进行传输。对于下行传输过程，第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理。其中，对 于第一功能实例的具体实现方式不同，第一功能实例对下行数据包的处理过程也不相同。第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后向第一UE发送下行数据包，第一UE通过第一UE和第一功能实例之间的承载接收到第一功能实例发送的下行数据包。
在本发明的一些实施例中，第一业务的数据包和第一切片标识对应，具体可以包括如下多种实现场景中的一种或者多种：
当第一功能实例包括第一GW时，第一GW接收的下行数据包的互联网协议(英文全称：Internet Protocol，英文简称：IP)五元组，和第一切片标识对应；或，
当第一功能实例包括第一数据面功能节点时，第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、虚拟局域网标识(英文全称：Virtual Local Area Network Identity，英文简称：VLAN ID)、多协议标签交换(英文全称：Multi-Protocol Label Switch，英文简称：MPLS)标签、承载标识中的至少一个，和第一切片标识对应；或，
当第一功能实例包括第一基站时，第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识中的至少一个，和第一切片标识对应。
其中，在本发明实施例中，功能实例可以有多种实现方式，在不同的实现方式下，对应于第一UE的第一业务的数据包和第一切片标识具有的对应关系就可以有多种。例如，第一GW发送的下行数据包的IP五元组和第一切片标识对应，那么通过IP五元组和第一切片标识的对应关系可以获取到对于第一GW发送的下行数据包需要使用的切片标识为第一切片标识。第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、VLAN ID、MPLS标签、承载标识，和第一切片标识对应。在不同的实现场景下，第一数据面功能节点需要使用上行数据包或下行数据包的IP五元组、VLAN ID、MPLS标签、承载标识，那么通过上述对应关系可以获取到对于上行数据包或下行数据包的IP五元组、VLAN ID、MPLS标签、承载标识需要使用的切片标识为第一切片标识。第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识和第一切片标识对应。在不同的实现场景下，第一基站需要上行数据包使用的物理时频资源、用户标识、连接标识，那么通过上述对应关系可以获取到对于上行数据包使用的物理时频资源、用户标识、连接标识需要使用的切片标识为第 一切片标识。
通过前述实施例对本发明的描述可知，第一UE按照控制器对第一UE和第一功能实例分别发送的建立承载的指示信息建立为第一UE的第一业务服务的承载。第一UE通过承载传输对应于第一UE的第一业务的数据包，对应于第一UE的第一业务的数据包和第一切片标识对应。本发明实施例中控制器根据第一切片标识获取到业务和网络切片的对应关系，网络切片的切片标识和功能实例的实例标识相对应，当UE具有不同的业务标识时可以获取到不同的切片标识。例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识。控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例。不同的功能实例可以使用不同的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
接下来从用户设备侧介绍本发明实施例提供的另一种通信控制方法，请参阅图7所示，本发明一个实施例提供的通信控制方法，可以包括如下步骤：
701、第一UE向控制器发送认证请求消息，认证请求消息包括：第一UE的第一业务对应的第一业务标识。
702、第一UE接收建立与第一切片标识对应的承载的指示信息。
703、第一UE根据指示信息建立为第一UE的第一业务服务的第一UE和第一功能实例之间的承载。
704、第一UE通过承载传输对应于第一UE的第一业务的数据包，第一业务的数据包和第一切片标识对应。
其中，步骤702至704和前述实施例中步骤601至603的实现方式相类似，接下来对步骤701进行详细说明。
在本发明实施例支持对用户设备进行认证以及切片鉴权的应用场景中，控制器在为第一UE分配功能实例之前需要先对该第一UE进行身份认证和切片 鉴权。只有第一UE通过身份认证和切片鉴权，控制器才能根据其所获取到的与第一业务相对应的第一切片标识确定与第一切片标识对应的第一功能实例。若第一UE没有通过身份认证和切片鉴权，控制器不需要为该第一UE分配功能实例，以避免处理资源和/或传输资源被不合法的用户设备使用。控制器根据第一UE的认证请求消息选择出HSS，由HSS对第一UE进行身份认证和切片鉴权，在第一UE发送的认证请求消息中第一UE可以携带第一切片标识，便于HSS对第一UE进行身份认证和切片鉴权，或者在第一UE发送的认证请求消息第一UE也可以不携带第一切片标识，HSS对第一UE进行身份认证和切片鉴权通过之后，HSS发送给控制器的认证结果中携带与第一UE对应的第一切片标识，或者与第一UE发起的业务对应的第一切片标识。第一UE通过认证之后，第一UE执行步骤702，控制器向该第一UE发送承载的指示信息。
接下来从用户设备侧介绍本发明实施例提供的另一种通信控制方法，请参阅图8所示，本发明一个实施例提供的通信控制方法，可以包括如下步骤：
801、第一UE向PCEF实体发送业务请求消息，业务请求消息包括：第一UE的第一业务对应的第一业务标识。
802、第一UE接收建立与第一切片标识对应的承载的指示信息。
803、第一UE根据指示信息建立为第一UE的第一业务服务的第一UE和第一功能实例之间的承载。
804、第一UE向PCEF实体发送业务请求消息，业务请求消息包括：第一UE发起的业务对应的第一业务标识。
其中，步骤802至804和前述实施例中步骤601至603的实现方式相类似，接下来对步骤801进行详细说明。
在本发明实施例支持对用户设备进行认证以及切片鉴权的应用场景中，控制器在为第一UE分配功能实例之前需要先对该第一UE进行身份认证和切片鉴权。若第一UE没有通过身份认证和切片鉴权，控制器不需要为该第一UE分配功能实例，以避免处理资源和/或传输资源被不合法的用户设备使用。
第一UE向PCEF实体发送业务请求消息，业务请求消息中包括有第一切片标识，由PCEF实体根据业务请求消息选择PCRF实体，由PCRF实体对第一UE进行身份认证和切片鉴权。PCRF实体对第一UE进行身份认证和切片鉴权通过之后，PCRF实体向PCEF实体发送给认证结果，若该认证结果为第 一UE通过身份认证和切片鉴权，PCEF实体向控制器发送实例请求消息。实例请求消息包括：PCEF实体从认证结果中获取到的第一切片标识，控制器根据接收到的PCEF实体发送的实例请求消息为第一UE选择出第一功能实例，并向第一UE发送建立承载的指示信息。若第一UE没有通过身份认证和切片鉴权，则PCEF实体不会向控制器发送实例请求消息，控制器没有接收到PCEF实体发送的实例请求消息，控制器就不会为第一UE选择功能实例。
上述实施例从控制器侧和用户设备侧介绍了本发明实施例提供的通信控制方法，接下来从功能实例侧介绍本发明实施例提供的通信控制方法，请参阅如图9所示，本发明实施例提供的通信控制方法，具体可以包括如下步骤：
901、第一功能实例接收建立与第一切片标识对应的承载的指示信息，指示信息携带有第一UE的标识和第一功能实例的标识。
在本发明实施例中，控制器确定由第一功能实例使用处理资源和/或传输资源为第一UE提供对数据包的处理功能，控制器向第一UE和第一功能实例分别发送建立承载的指示信息。其中，控制器向第一UE和第一功能实例发送建立承载的指示信息可以是控制器通过PCEF实体向第一UE和第一功能实例发送建立承载的指示信息。第一功能实例接收到控制器的指示信息之后，第一功能实例和第一UE分别执行承载的建立过程，该承载是为第一UE的第一业务服务的承载，其中承载的具体建立方式可以参阅现有技术，此处不再赘述。
902、第一功能实例根据建立承载的指示信息建立为第一UE的第一业务服务的第一UE和第一功能实例之间的承载。
903、第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对承载上传输的第一业务的数据包进行处理，第一业务的数据包和第一切片标识对应。
在本发明实施例中，控制器为第一UE选择出第一功能实例之后，控制器确定由第一功能实例使用处理资源和/或传输资源为第一UE提供对数据包的处理功能，控制器向第一UE和第一功能实例分别发送建立承载的指示信息。其中，控制器向第一UE和第一功能实例发送建立承载的指示信息可以是控制器通过PCEF实体向第一UE和第一功能实例发送建立承载的指示信息。控制器发送的建立承载的指示信息中包括有第一切片标识，该第一切片标识对应于第一UE，或对应于第一UE发起的业务。
其中，在第一切片标识和第一用户设备相对应的实现场景中，第一用户设备使用的切片标识是第一切片标识，不同的用户设备可以使用不同的切片标识。举例说明，第一用户设备对应于切片标识x，第二用户设备对应于切片标识y，则控制器根据切片标识x选择与切片标识x对应的功能实例1和功能实例2，控制器根据切片标识y选择与切片标识y对应的功能实例3。也就是说，控制器根据不同的用户设备使用的不同切片标识可以为多个用户设备提供差异化服务。在第一切片标识和第一用户设备发起的业务相对应的实现场景中，第一用户设备在发起有多种业务时，第一用户设备发起的不同业务对应有不同的切片标识，控制器为第一用户设备发起的不同业务可以分配不同的功能实例。举例说明，第一用户设备发起了两个业务(分别为业务a和业务b)，第一用户设备发起的业务a对应于切片标识x，第一用户设备发起的业务b对应于切片标识y，则控制器根据切片标识x选择与切片标识x对应的功能实例1和功能实例2，控制器根据切片标识y选择与切片标识y对应的功能实例3。因此本发明实施例中控制器可以实现对不同的用户设备配置不同的功能实例，从而可以为不同的用户设备提供差异化服务，另外本发明实施例中控制器还可以对同一个用户设备的不同业务配置不同的功能实例，从而可以为同一个用户设备的不同业务提供差异化服务。
需要说明的是，在本发明实施例中，不同的功能实例使用的处理资源和/或传输资源是不同的，例如，功能实例可以是基站、GW以及数据面功能节点，在功能实例表示不同的实体时其对应的处理资源和/或传输资源可以不同。第一功能实例包括以下至少一个：第一GW，或第一数据面功能节点，或第一基站。
在本发明实施例中，第一功能实例根据控制器发送的建立承载的指示信息建立承载完成之后，该承载可以用于传输对应于第一UE的第一业务的数据包。其中，对应于第一UE的第一业务的数据包和第一网络切片对应。数据包通过承载与第一网络切片的对应关系可以确定数据包需要可以在哪个承载上传输。需要说明的是，在本发明实施例中，第一UE和第一功能实例之间建立的承载可用于对应于第一UE的第一业务的数据包的传输，数据包在第一UE和第一功能实例之间传输。在上行传输过程和下行传输过程中第一UE对数据包的处理过程不相同，同样的，在上行传输过程和下行传输过程中第一功能实例对数 据包的处理过程不相同。
在本发明的一些实施例中，步骤903第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对承载上传输的第一业务的数据包进行处理，具体可以包括如下步骤：
F1、第一功能实例通过承载接收第一UE发送的上行数据包，第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对上行数据包进行处理；和/或，
F2、第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理，然后通过承载向第一UE发送处理完成后的下行数据包。
其中，对于上行传输过程，第一UE通过第一UE和第一功能实例之间的承载向第一功能实例发送上行数据包，由第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对上行数据包进行处理。其中，对于第一功能实例的具体实现方式不同，第一功能实例对上行数据包的处理过程也不相同。例如功能实例具体可以为基站，则第一功能实例包括第一基站，该第一基站由控制器确定用于为第一UE提供服务，第一基站对应于第一网络切片，第一基站可以根据第一网络切片提供的处理功能对上行数据包进行处理，并按照指定的传输功能对上行数据包进行传输。
对于下行传输过程，第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理。其中，对于第一功能实例的具体实现方式不同，第一功能实例对下行数据包的处理过程也不相同。第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后向第一UE发送下行数据包，第一UE通过第一UE和第一功能实例之间的承载接收到第一功能实例发送的下行数据包。
在本发明的一些实施例中，第一业务的数据包和第一切片标识对应，具体可以包括如下多种实现场景中的一种或者多种：
当第一功能实例包括第一GW时，第一GW接收的下行数据包的IP五元组，和第一切片标识对应；或，
当第一功能实例包括第一数据面功能节点时，第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、VLAN ID、MPLS标签、承载标识中的至少一个，和第一切片标识对应；或，
当第一功能实例包括第一基站时，第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识中的至少一个，和第一切片标识对应。
其中，在本发明实施例中，功能实例可以有多种实现方式，在不同的实现方式下，对应于第一UE的第一业务的数据包和第一切片标识具有的对应关系就可以有多种。例如，第一GW发送的下行数据包的IP五元组和第一切片标识对应，那么通过IP五元组和第一切片标识的对应关系可以获取到对于第一GW发送的下行数据包需要使用的切片标识为第一切片标识。第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、VLAN ID、MPLS标签、承载标识中的至少一个，和第一切片标识对应。在不同的实现场景下，第一数据面功能节点需要使用上行数据包或下行数据包的IP五元组、VLAN ID、MPLS标签、承载标识，那么通过上述对应关系可以获取到对于上行数据包或下行数据包的IP五元组、VLAN ID、MPLS标签、承载标识需要使用的切片标识为第一切片标识。第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识和第一切片标识对应。在不同的实现场景下，第一基站需要上行数据包使用的物理时频资源、用户标识、连接标识，那么通过上述对应关系可以获取到对于上行数据包使用的物理时频资源、用户标识、连接标识需要使用的切片标识为第一切片标识。
通过前述实施例对本发明的描述可知，第一功能实例接收控制器对第一功能实例和第一UE分别发送的建立承载的指示信息，第一功能实例根据建立承载的指示信息建立为第一UE的第一业务服务的承载，该承载和控制器为对应于第一UE的第一业务的数据包选择的第一网络切片对应，第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对承载上传输的对应于第一UE的第一业务的数据包进行处理，对应于第一UE的第一业务的数据包和第一切片标识对应。本发明实施例中对于不同的业务具有不同的业务标识，不同的业务具有不同的业务需求，当UE具有不同的业务标识时可以获取到不同的切片标识，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例，不同的功能实例可以使用不 同的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
上述实施例从控制器、UE、功能实例侧介绍了本发明实施例提供的一种通信控制方法，接下来从UE侧介绍本发明实施例提供的另一种通信控制方法，请参阅如图10所示，本发明实施例提供的通信控制方法，具体可以包括如下步骤：
1001、第一UE向第一基站发送上行调度请求。
其中，上行调度请求包括：第一UE需要发送的数据包对应的第一切片标识或者第一连接标识。
在本发明实施例中，控制器为第一UE选择出的功能实例为第一基站，第一UE需要向第一基站请求空口传输资源。按照现有技术，UE向基站请求空口传输资源，基站分配给UE的空口传输资源是针对整个UE的，而无法具体到针对UE的某一个业务。而本发明实施例中，一个UE有多个业务对应有不同的网络切片时，不同的网络切片对应的处理资源和传输资源都是不同的。因此第一UE发送的上行调度请求中包括有第一UE需要发送的数据包对应的第一切片标识或者第一连接标识，即第一UE向第一基站请求的空口传输资源是对应于UE需要发送的数据包对应的第一切片标识或者第一连接标识。因此当第一UE中配置有多种业务时，UE需要发送的数据包也是不同的，这些不同的数据包对应有不同的切片标识或者连接标识，那么基站分配针对不同的切片标识或者连接标识来分配不同的空口传输资源。
需要说明的是，在本发明实施例中，上行调度请求中包括有第一切片标识或者第一连接标识，例如，上行调度请求包括：第一UE需要发送的数据包对应的第一切片标识，或者，上行调度请求包括：第一UE需要发送的数据包对应的第一连接标识。第一切片标识和第一连接标识之间具有关联关系，在第一UE向第一基站请求分配空口传输资源的应用场景中，第一UE在上行调度请求中可以携带第一切片标识或者第一连接标识，第一基站可以通过第一连接标识确定出第一切片标识。
在本发明的一些实施例中，步骤1001第一UE向第一基站发送上行调度请求之前，本发明实施例提供的通信控制方法，还可以包括如下步骤：
G1、第一UE按照控制器对第一UE和第一基站分别发送的建立承载的指示信息建立为第一UE的第一业务服务的承载。
在本发明实施例中，控制器为第一UE选择出第一基站之后，控制器确定由第一基站使用处理资源和/或传输资源为第一UE提供对数据包的处理功能，控制器向第一UE和第一基站分别发送建立承载的指示信息。其中，控制器向第一UE和第一基站发送建立承载的指示信息可以是控制器通过PCEF实体向第一UE和第一基站发送建立承载的指示信息。第一UE接收到控制器的指示信息之后，第一UE和第一基站分别执行承载的建立过程，该承载是为第一UE的第一业务服务的承载。其中承载的具体建立方式可以参阅现有技术，此处不再赘述。
1002、第一UE接收第一基站发送的资源指配信息。
其中，资源指配信息包括：第一切片标识或者第一连接标识，以及和第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
在本发明实施例中，第一基站接收到第一UE发送的携带第一切片标识或者第一连接标识的上行调度请求之后，第一基站可以针对第一切片标识或者第一连接标识进行分配空口传输资源，第一基站向第一UE发送资源指配信息。在资源指配信息中包括有第一基站分配的与第一切片标识或者第一连接标识对应的空口传输资源，分配的空口传输资源对应于第一切片标识或者第一连接标识。因此第一UE中只有与第一切片标识或者第一连接标识对应的数据包才能使用第一基站分配的上述空口传输资源。其中，当第一功能实例具体为第一基站时，第一基站配置给第一UE的空口传输资源是功能实例使用的传输资源的一种实现方式。
在本发明的一些实施例中，步骤1002第一UE接收第一基站发送的资源指配信息之后，本发明实施例提供的通信控制方法，还可以包括如下步骤：
H1、第一UE在空口传输资源上传输对应于第一UE的第一业务的数据包。
在本发明实施例中，第一UE获取到第一基站分配的空口传输资源之后，利用该空口传输资源传输对应于第一UE的第一业务的数据包，其中，对应于 第一UE的第一业务的数据包和第一网络切片对应。
通过前述实施例对本发明的描述可知，第一UE向第一基站发送上行调度请求。上行调度请求包括：第一UE需要发送的数据包对应的第一切片标识或者第一连接标识，第一UE接收第一基站发送的资源指配信息，第一基站分配的空口传输资源与第一切片标识或者第一连接标识对应，从而第一基站针对不同的切片标识或者连接标识分配的空口传输资源可以实现差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
上述实施例从用户设备侧介绍了本发明实施例提供的另一种通信控制方法，接下来从功能实例侧介绍本发明实施例提供的另一种通信控制方法，该功能实例具体为基站，则控制器根据第一切片标识选择出的功能实例为第一基站，请参阅如图11所示，本发明实施例提供的通信控制方法，图11所示的通信控制方法与图10所示的通信控制方法相对应的方法，该方法具体可以包括如下步骤：
1101、第一基站接收第一UE发送的上行调度请求。
其中，上行调度请求包括：UE需要发送的数据包对应的第一切片标识或者第一连接标识。
在本发明实施例中，控制器为第一UE选择出的功能实例为第一基站，第一UE需要向第一基站请求空口传输资源。按照现有技术，UE向基站请求空口传输资源，基站分配给UE的空口传输资源是针对整个UE的，而无法具体到针对UE的某一个业务。而本发明实施例中，一个UE有多个业务对应有不同的网络切片时，不同的网络切片对应的处理资源和传输资源都是不同的。因此第一UE发送的上行调度请求中包括有第一UE需要发送的数据包对应的第一切片标识或者第一连接标识。即第一UE向第一基站请求的空口传输资源是对应于UE需要发送的数据包对应的第一切片标识或者第一连接标识。因此当第一UE中配置有多种业务时，UE需要发送的数据包也是不同的，这些不同的数据包对应有不同的切片标识或者连接标识。
需要说明的是，在本发明实施例中，第一UE发送的上行调度请求中包括有第一切片标识或者第一连接标识，例如，上行调度请求包括：第一UE需要发送的数据包对应的第一切片标识，或者，上行调度请求包括：第一UE需要 发送的数据包对应的第一连接标识。第一切片标识和第一连接标识之间具有关联关系，在第一UE向第一基站请求分配空口传输资源的应用场景中，第一UE在上行调度请求中可以携带第一切片标识或者第一连接标识，第一基站可以通过第一连接标识确定出第一切片标识。
在本发明的一些实施例中，步骤1101第一基站接收第一UE发送的上行调度请求之前，本发明实施例提供的通信控制方法，还可以包括如下步骤：
I1、第一基站按照控制器对第一UE和第一基站分别发送的建立承载的指示信息建立为第一UE的第一业务服务的承载。其中，对应于第一UE的第一业务的数据包需要携带第一切片标识或第一连接标识。
在本发明实施例中，控制器为第一UE选择出第一基站之后，控制器确定由第一基站使用处理资源和/或传输资源为第一UE提供对数据包的处理功能。控制器向第一UE和第一基站分别发送建立承载的指示信息，其中，控制器向第一UE和第一基站发送建立承载的指示信息可以是控制器通过PCEF实体向第一UE和第一基站发送建立承载的指示信息。第一UE接收到控制器的指示信息之后，第一UE和第一基站分别执行承载的建立过程，该承载是为第一UE的第一业务服务的承载。其中承载的具体建立方式可以参阅现有技术，此处不再赘述。
1102、第一基站根据上行调度请求分配与第一切片标识或者第一连接标识对应的处理资源和/或传输资源，处理资源和/或传输资源包括空口传输资源。
在本发明实施例中，第一基站从上行调度请求获取到第一切片标识或者第一连接标识，然后第一基站针对该第一切片标识或者第一连接标识分配空口传输资源，则分配的空口传输资源只能用于第一切片标识或者第一连接标识对应的数据包。举例说明，第一基站中配有两种网络切片：网络切片A和网络切片B。网络切片A和网络切片B分别对应有独立的空口传输资源。若第一基站中有两种不同的业务分别对应于网络切片A和网络切片B，若第一UE发送的上行调度请求中包括网络切片A的切片标识，则第一基站根据网络切片A的切片标识分配一种空口传输资源。若第一UE发送的上行调度请求中包括网络切片B的切片标识，则第一基站根据网络切片B的切片标识分配另一种空口传输资源。
1103、第一基站向第一UE发送资源指配信息，资源指配信息包括：第一 切片标识或者第一连接标识，以及和第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
在本发明实施例中，第一基站可以针对第一切片标识或者第一连接标识进行分配空口传输资源，第一基站向第一UE发送资源指配信息。在资源指配信息中包括有第一基站分配的与第一切片标识或者第一连接标识对应的空口传输资源，分配的空口传输资源对应于第一切片标识或者第一连接标识，因此第一UE中只有与第一切片标识或者第一连接标识对应的数据包才能使用第一基站分配的上述空口传输资源。
在本发明的一些实施例中，步骤1103第一基站向第一UE发送资源指配信息之后，本发明实施例提供的通信控制方法，还可以包括如下步骤：
J1、第一基站在空口传输资源上传输对应于第一UE的第一业务的数据包。
在本发明实施例中，第一UE获取到第一基站分配的空口传输资源之后，利用该空口传输资源传输对应于第一UE的第一业务的数据包，第一基站可以在空口传世资源上接收对应于第一UE的第一业务的数据包。其中，对应于第一UE的第一业务的数据包和第一网络切片对应。
通过前述实施例对本发明的描述可知，第一UE向第一基站发送上行调度请求，上行调度请求包括：第一UE需要发送的数据包对应的第一切片标识或者第一连接标识，第一UE接收第一基站发送的资源指配信息，第一基站分配的空口传输资源与第一切片标识或者第一连接标识对应，从而第一基站针对不同的切片标识或者连接标识分配的空口传输资源可以实现差异化的处理功能。因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
为便于更好的理解和实施本发明实施例的上述方案，下面举例相应的应用场景来进行具体说明。
请参阅如图12-a所示，为本发明实施例提供的数据包的处理流程中总流程示意图，包括如下三个部分：
S01、当业务提供服务器向运营商部署的控制器提出对于在一定区域内对于某一特定业务支撑的需求。控制器在指定区域相关的设备上，为业务部署处理资源和/或传输资源和/或功能实例，从而构成一个网络切片。除了处理资源 和传输资源分配的不同之外，不同的网络切片可以有不同的协议栈处理流程。
S02、在网络切片部署完成之后，当用户使用特定业务时，这个特定业务就是前述业务提供服务器在指定区域内的特定业务，运营商需要识别到用户设备的特定业务属于前面已经部署好的某个网络切片，将用户设备的具体业务关联到具体的网络切片之上。
S03、当前述用户设备向基站发送业务的上行数据包，或者网络侧网关节点或边界路由器接收该用户业务的下行数据包时，根据在前述步骤中建立的关联关系，识别该数据包从属于前述的网络切片，而基于该网络切片的对应的定制处理过程，使用该网络切片的资源进行处理。
接下来在后续实施例中，将针对每一个部分给出详细实现场景。
首先描述网络切片的部署过程，请参阅如图12-b所示，为本发明实施例提供的一种网络切片部署的一种实现方式示意图，具体过程包括：
S11，运营商部署的控制器接收业务提供服务器的服务请求。例如，运营商部署的控制器接收业务提供服务器发送的业务消息，该业务消息的内容包括：在指定的地理区域内，为某一特定业务，满足一定的服务质量/用户体验质量要求。即业务信息包括：范围信息、业务标识、以及对应的服务质量/服务体验要求。此处的业务标识可以对应到一类特定的业务，比如抄表业务，体感游戏等等，也可以对应到一类用户，比如金牌用户、银牌用户等待。这个过程可以通过运营商控制器的北向开放接口实现。
S12，为了满足特定业务的需求，运营商部署的控制器分配切片标识，并在前述范围内对应的设备范围内，向基础设施部署相关的功能实例，并在设备上将功能实例与切片标识相关联，一种类型的功能实例只处理对应的切片标识的数据。其中，一个功能实例可以只处理一个切片标识的数据，也可以处理多个切片标识的数据。为满足前述业务提供服务器的特定业务需求，所涉及到的功能实例以及传输资源、处理资源的集合，称之为一个网络切片。控制器向功能实例发送的消息，内容包括：建立实例指示，功能实例类型，切片标识。控制器将该网络切片对应的功能实例保存起来。
S13，控制器发送业务和网络切片的对应关系，HSS或PCRF实体获取到特定业务所对应的切片标识。
S14，控制器向业务提供服务器发送服务响应，其中包括切片标识。
接下来描述在默认承载场景下业务的关联过程。在用户接入的过程中，如果UE属于一类特定应用，比如抄表MTC，那么在接入建立默认承载的过程中，网络就识别出UE的切片特征，并把默认承载建立在指定切片上，在GW和基站节点及中间数据面处理节点上建立上下行数据包与切片的对应关系。请参阅如图12-c所示，为本发明实施例提供的一种业务与网络切片的关联过程示意图，具体过程包括：
S21，第一UE发起接入认证请求过程。第一UE向控制器发送认证请求消息，其中携带第一切片标识。第一UE的第一切片标识可以是在用户与业务提供商签约时得到的，认证请求消息可以经过基站等设备传递。
S22，控制器接收第一UE发送的认证请求消息，控制器可以根据认证请求中携带的第一切片标识进行HSS的选择。HSS对用户进行认证，同时对于该用户是否有权利用某个网络切片进行授权。HSS对第一UE的认证和授权有两部分。一部分是对用户设备身份的确认，第二部分是判断该第一UE是否可以使用与第一切片标识对应的第一网络切片。
S23，在认证和授权成功后，HSS向控制器返回认证结果，其中携带第一UE认证授权通过的第一切片标识。
S24，控制器根据接收到的第一切片标识，以及在切片部署阶段保存起来的网络切片与功能实例的对应关系，选择为该第一UE服务的第一功能实例。同时，通知选择到的第一功能实例和第一UE进行承载建立过程，在建立承载的指示中携带第一切片标识。
S25，第一功能实例接收到建立承载的指示后，建立为该第一UE的第一业务服务的承载，并建立该承载或者该承载上的数据与第一网络切片的对应关系。该对应关系，可以包括如下几种情况：GW的下行数据包IP五元组与切片标识的对应关系，数据面功能节点的上下行数据包的IP五元组/VLAN ID/MPLS标签/承载标识中的至少一个，与切片标识的对应关系，基站发送的上行数据包所使用的物理时频资源，用户标识、连接标识中的至少一个，与切片标识的对应关系。
S26，第一UE建立承载，并建立承载与切片标识的对应关系，该对应关系可以是:用户标识和/或连接标识，与切片标识的对应关系。
前述步骤S21至S26描述了在默认承载场景下业务的关联过程。接下来举 例说明专用承载场景下业务的关联过程。请参阅如图12-d所示，为本发明实施例提供的一种业务与网络切片的关联过程示意图，第一UE本身不具有切片特征，而是其可以发起的特定业务属于某一个网络切片。其具体处理过程如下所述。
S31，第一UE发起业务请求过程，向PCEF实体发送业务请求消息，其中携带第一切片标识。第一UE的第一切片标识可以是在用户与业务提供商签约时得到的，业务请求消息可以经过基站等设备传递。
S32，PCEF实体进行业务授权过程，可以根据业务请求消息中携带的第一切片标识进行PCRF实体的选择。PCRF实体对第一UE的业务进行授权，同时对于第一UE是否有权利使用网络切片进行授权。
S33，PCRF实体在授权成功后，向PCEF实体返回认证结果，其中携带第一UE认证授权通过的第一切片标识。
S34，PCEF实体接收到第一切片标识之后，PCEF实体与控制器交互，向控制器发送携带第一切片标识的实例请求消息，由控制器根据第一切片标识以及在切片部署阶段保存起来的网络切片与功能实例的对应关系。选择为该第一UE服务的功能实例为第一功能实例，控制器向PCEF实体返回实例响应，其中携带第一功能实例的实例标识。
S35，PCEF实体通知选择到的第一功能实例和第一UE进行承载建立过程，在建立承载的指示中携带第一切片标识。并建立下行数据包与第一网络切片的对应关系。
S36，第一功能实例接收到建立承载的指示后，建立为该第一UE的第一业务服务的承载，并建立该承载或者该承载上的数据包，与第一网络切片的对应关系。该对应关系。可以包括如下几种情况：GW的下行数据包IP五元组与切片标识的对应关系，数据面功能节点的上下行数据包的IP五元组/VLAN ID/MPLS标签/承载标识中的至少一个，与切片标识的对应关系，基站发送的上行数据包所使用的物理时频资源，用户标识、连接标识中的至少一个，与切片标识的对应关系。
前述图12-c和图12-d所示的实施例中描述了业务和网络切片的关联过程，接下来介绍第一UE和第一功能实例之间建立完成承载之后对数据包的处理过程。请参阅如图12-e所示，为本发明实施例提供的对下行数据包的处理流程 示意图，如图12-f所示，为本发明实施例提供的对上行数据包的处理流程示意图。
图12-e所示的对于下行过程：在入口网关处，根据IP五元组等数据特征，识别出下行数据包所属的网络切片，并使用该网络切片所使用到的功能实例对数据包进行处理，并使用给网络切片相关的传输资源传输策略进行数据传输。如图12-e所示，下行数据包由PCEF实体或者网关获取到之后，根据IP五元组或者根据下行数据包使用的承载来识别网络切片，将下行数据包引导到特定的网络切片进行处理，根据下行数据包与网络切片的对应关系获取到下行数据包对应的网络切片，其中网络切片1、网络切片2、网络切片3需要执行不同的处理。例如，网络切片1实现对下行数据包的视频优化功能，网络切片2实现对下行数据包的拆分功能，网络切片3实现对下行数据包的另一种拆分功能，下行数据包经过网络切片1、网络切片2、网络切片3使用不同的处理资源进行处理之后，还需要根据网络切片1、网络切片2、网络切片3使用的不同传输资源进行处理。根据不同的传输路径和传输策略进行处理，下行数据包到达基站之后，根据网络切片1、网络切片2、网络切片3对应的不同处理功能，基站执行不同的处理过程，例如基站对下行数据包使用共享的传输资源进行传输，或者对下行数据包使用独立的传输资源进行传输。
需要说明的是，在前述的网络切片部署阶段，已经为网络切片部署了一系列功能实例，其中一系列的功能实例，在不同的场景下也有所不同。比如车车通信(英文全称：Car to Car，英文简称：C2C)场景下，网络层和数据链路层的处理功能以及下移的核心网及应用层处理功能。比如在MTC场景下，网络层和数据链路层的处理功能以及聚合处理等。
对于传输资源采用的传输策略，指为了网络切片分配的VLAN ID/MPLS标签等，传输网络根据上述标签可以为网络切片提供业务保障。如果网络切片占用了独立的物理资源，则空口调度也将选择对应的物理资源为数据包进行传输，同时网络切片对应的策略也会影响到功能实例的处理行为，例如需要根据传输策略中设置的时间进行1ms调度或者0.1ms调度。
图12-f所示的对于上行过程：如果网络切片占用独立的空口传输资源，则基站根据物理资源，直接识别出数据包所属于的网络切片，并根据前期的部署进行处理。如果切片使用共享的空口传输资源，则基站需要根据在业务接入 或者业务建立过程中建立的对应关系，使用切片对应的处理功能对数据包进行处理，并按照指定的传输策略进行传输。如图12-f所示，上行数据包由第一UE发送给基站，基站获取到上行数据包之后，根据物理资源或者根据承载来识别网络切片，将上行数据包引导到特定的网络切片进行处理，根据上行数据包与网络切片的对应关系获取到上行数据包对应的网络切片。其中网络切片1、网络切片2、网络切片3需要执行不同的处理，例如，网络切片1对应于GW，网络切片2对应于多媒体广播多播业务(英文全称：Multimedia Broadcast Multicast Service，英文简称：MBMS)协调实体，网络切片3对应于另一种MBMS协调实体。上行数据包经过网络切片1、网络切片2、网络切片3使用不同的处理资源进行处理之后，还需要根据网络切片1、网络切片2、网络切片3使用的不同传输资源进行处理，根据不同的传输路径和传输策略进行处理。上行数据包经过不同的网络切片到达不同的功能实体，例如网络切片1对应于视频选择实体，网络切片2对应于汇聚实体，网络切片3对应于另一种汇聚实体。
在本发明如图12-e和图12-f对下行数据包和上行数据包的处理过程进行了说明，接下来描述在对下行数据包和上行数据包的处理过程之前，本发明实施例还可以需要执行的空口传输资源请求进行说明。请参阅如图12-g所示，为本发明实施例中第一UE和第一基站实现空口传输资源的分配过程示意图，主要包括如下步骤：
S41、第一UE向第一基站发送上行调度请求。其中，上行调度请求包括：第一UE需要发送的数据包对应的第一切片标识或者第一连接标识。
第一UE在发送上行数据包之前，需要向第一基站发送上行调度请求，以请求第一基站为其分配空口传输资源。在当前的标准设计中，UE的资源请求是针对终端进行的。也就是说，现有技术中基站为UE分配的空口传输资源适用于UE的所有数据包，而本发明实施例中，第一UE发送的上行调度请求中携带有第一切片标识或者第一连接标识，第一基站分配的空口传输资源是针对第一UE中的具体一个业务流。在一个用户终端有多个业务属于不同切片网络的场景下，不同网络切片对应的物理资源或者调度策略不同，例如，第一基站下有两个网络切片A/B，这两个网络切片使用独立的传输资源，若第一UE同时有两个业务分别对应于A/B切片，按照现有技术，终端发送上行资源请求 时，基站将无法判断给所述终端分配哪一部分的传输资源。
本发明实施例提供的解决方案如下，在一个用户设备有多个业务属于不同网络切片的场景下，如果所述不同网络切片对应的物理资源或者调度策略不同，则用户设备在上行调度请求中，需要携带切片标识或者数据连接标识，该连接标识可以为逻辑信道标识(英文全称：Logical Channel Identify，英文简称：LCID)。例如，第一UE发送的上行调度请求携带第一切片标识或者第一连接标识，以使得第一基站可以在正确的切片内，为上行请求分配空口传输资源。
S42、第一基站向第一UE发送确认消息。
第一基站在接收到第一UE发送的上行调度请求后，返回确认消息，进一步的。根据切片标识或者UE标识加连接标识与网络切片的对应关系，找到对应于第一切片标识或者第一连接标识的空口传输资源。
S43、第一基站向第一UE发送资源指配信息。
第一基站在前述空口传输资源内为第一UE的上行调度请求分配传输资源，并向第一UE返回资源指配信息，该资源指配信息中携带第一切片标识/第一连接标识，以及空口传输资源，该空口传输资源对应有特定的时频资源信息。
需要说明的是，当一个用户设备上的业务只从属于一个网络切片时，用户设备的上行资源请求可以不携带前述的第一切片标识或者第一连接标识，沿用现有技术只携带用户标识，当然用户设备的上行资源请求也可以携带前述的第一切片标识或者第一连接标识。在基站接收到第一UE发送的上行调度请求时，根据建立承载阶段建立的用户标识与网络切片的对应关系，寻找对应于该调度请求的空口传输资源。找到对应的空口传输资源后，基站向第一UE分配空口传输资源，并向第一UE返回资源指配信息，其中携带对应的空口传输资源。
通过前述本发明的举例说明可知，本发明实施例可以快速实现对数据包的处理，并且对于不同的用户设备可以使用不同的功能实例为不同用户设备提供不同的服务，还可以对于同一个用户设备发起的不同业务分配不同的功能实例，通过不同的功能实例实现对同一个用户设备的不同服务，从而可以保证了运营商可以快速的满足业务提供商的不同业务需求。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述 的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
为便于更好的实施本发明实施例的上述方案，下面还提供用于实施上述方案的相关装置。
请参阅图13-a所示，本发明实施例提供的一种控制器1300，可以包括：功能实例确定模块1301、发送模块1302，其中，
功能实例确定模块1301，用于获取与第一业务相对应的第一切片标识；根据第一切片标识确定与所述第一切片标识对应的第一功能实例；
发送模块1302，用于根据所述第一切片标识向第一用户设备UE和第一功能实例分别发送建立承载的指示信息，所述承载用于传输对应于所述第一UE的第一业务的数据包，指示信息携带有所述第一UE的标识和所述第一功能实例的标识。
在本发明的一些实施例中，请参阅如图13-b所示，所述控制器1300，还包括：获取模块1303，用于所述功能实例确定模块1301根据其所获取到的与第一业务相对应的第一切片标识确定与所述第一切片标识对应的第一功能实例之前，获取业务和网络切片的对应关系，所述网络切片与切片标识对应。
在本发明的一些实施例中，请参阅如图13-c所示，所述获取模块1303，包括:第一接收子模块13031、功能实例部署子模块13032和对应关系配置子模块13033，其中，
所述第一接收子模块13031，用于接收业务提供服务器发送的业务信息，所述业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或所述业务信息包括：业务对应的业务标识、业务需要的服务质量要求和业务的区域范围；
所述功能实例部署子模块13032，用于根据所述业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；
所述对应关系配置子模块13033，用于根据为业务部署的功能实例建立业务和网络切片的对应关系。
在本发明的一些实施例中，所述发送模块1302，还用于所述获取模块获取业务和网络切片的对应关系之后，将所述业务和网络切片的对应关系发送给 所述业务提供服务器。
在本发明的一些实施例中，所述获取模块1303，具体用于从网络切片部署装置获取业务和网络切片的对应关系，所述网络切片部署装置建立业务和网络切片的对应关系，包括：
所述网络切片部署装置接收业务提供服务器发送的业务信息，所述业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或所述业务信息包括：业务对应的业务标识、业务需要的服务质量要求和业务的区域范围；
所述网络切片部署装置根据所述业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；
所述网络切片部署装置根据为业务部署的功能实例建立业务和网络切片的对应关系，并将所述业务和网络切片的对应关系发送给所述控制器。
在本发明的一些实施例中，请参阅如图13-d所示，功能实例确定模块1301包括：第二接收子模块13011、认证选择子模块13012和功能实例确定子模块13013，其中，
所述第二接收子模块13011，用于接收所述第一UE发送的认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识；
所述认证选择子模块13012，用于根据所述认证请求消息选择归属签约用户服务器HSS；
所述第二接收子模块13011，还用于接收所述HSS发送的所述HSS对所述第一UE进行身份认证和切片鉴权的认证结果；
所述功能实例确定子模块13013，用于若所述认证结果为所述第一UE通过身份认证和切片鉴权，根据所述第一切片标识确定第一功能实例。
在本发明的一些实施例中，所述功能实例确定模块1301，具体用于接收策略及计费执行功能PCEF实体在接收到策略与计费规则功能PCRF实体发送的第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，所述实例请求消息包括：所述PCEF从所述认证结果中获取到的第一切片标识；接收到所述实例请求消息之后，根据所述第一切片标识确定所述第一功能实例。
在本发明的一些实施例中，所述发送模块1302，还用于将所述业务和网络切片的对应关系发送给HSS或PCRF实体。
需要说明的是，上述装置各模块/单元之间的信息交互、执行过程等内容，由于与本发明方法实施例基于同一构思，其带来的技术效果与本发明方法实施例相同，具体内容可参见本发明前述所示的方法实施例中的叙述，此处不再赘述。
通过前述实施例对本发明的描述可知，控制器根据第一切片标识选择与第一切片标识对应的第一功能实例，第一功能实例包括：对应于第一切片标识的一个或多个功能实例，最后控制器向第一UE和第一功能实例分别发送建立承载的指示信息，该承载用于传输对应于第一UE的第一业务的数据包，该承载和具有第一切片标识的第一网络切片对应。本发明实施例中对于不同的业务具有不同的业务标识，不同的业务具有不同的业务需求，控制器根据业务需求建立了业务和网络切片的对应关系，网络切片的切片标识和功能实例的实例标识相对应，当UE具有不同的业务标识时可以获取到不同的切片标识，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例，不同的功能实例可以使用不同的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
前述实施例介绍了本发明实施例提供的一种控制器，接下来介绍本发明实施例提供的一种UE，请参阅图14-a所示，本发明实施例提供的一种第一UE1400，可以包括：接收模块1401、承载建立模块1402、数据包传输模块1403，其中，
接收模块1401，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识；
承载建立模块1402，用于根据所述指示信息建立为所述第一UE的第一业务服务的所述第一UE与所述第一功能实例之间的承载，第一功能实例与所述 第一切片标识对应；
数据包传输模块1403，用于通过所述承载传输所述第一业务的数据包，所述数据包和所述第一切片标识对应。
在本发明的一些实施例中，如图14-b所示，所述第一UE1400，还包括：发送模块1404，其中，
所述发送模块1404，用于向所述控制器发送认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识。
在本发明的一些实施例中，所述第一UE，还包括：发送模块1404，其中，
所述发送模块1404，用于向策略及计费执行功能PCEF实体发送业务请求消息，所述业务请求消息包括：所述第一UE的第一业务对应的第一业务标识。
在本发明的一些实施例中，所述数据包传输模块1403，具体用于通过所述承载向第一功能实例发送上行数据包，由所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，通过所述承载接收所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后发送的下行数据包。
在本发明的一些实施例中，如图14-b所示，所述第一UE1400，还包括：发送模块1404，其中，
所述发送模块1404，用于向第一基站发送上行调度请求，所述上行调度请求包括：所述第一UE需要发送的数据包对应的第一切片标识或者第一连接标识；
所述接收模块1401，还用于接收所述第一基站发送的资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和所述第一切片标识或者所述第一连接标识对应的空口传输资源。
需要说明的是，上述装置各模块/单元之间的信息交互、执行过程等内容，由于与本发明方法实施例基于同一构思，其带来的技术效果与本发明方法实施例相同，具体内容可参见本发明前述所示的方法实施例中的叙述，此处不再赘述。
通过前述实施例对本发明的描述可知，第一UE按照控制器对第一UE和第一功能实例分别发送的建立承载的指示信息建立为第一UE的第一业务服务的 承载，第一UE通过承载传输对应于第一UE的第一业务的数据包，对应于第一UE的第一业务的数据包和第一网络切片对应。本发明实施例中对于不同的业务具有不同的业务标识，不同的业务具有不同的业务需求，控制器获取业务和网络切片的对应关系，网络切片的切片标识和功能实例的实例标识相对应，当UE具有不同的业务标识时可以获取到不同的切片标识，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例，不同的功能实例可以使用不同的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
前述实施例介绍了本发明实施例提供的一种控制器和用户设备，接下来介绍本发明实施例提供的一种功能实例，请参阅图15-a所示，本发明实施例提供的一种第一功能实例1500，可以包括：接收模块1501、承载建立模块1502、数据包处理模块1503，其中，
接收模块1501，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有第一用户设备UE的标识和所述第一功能实例的标识；
承载建立模块1502，用于根据所述建立承载的指示信息建立为第一用户设备UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载；
数据包处理模块1503，用于使用与第一切片标识对应的处理资源和/或传输资源对所述承载上传输的对应于所述第一UE的第一业务的数据包进行处理，所述对应于所述第一UE的第一业务的数据包和所述第一切片标识对应。
在本发明的一些实施例中，所述第一功能实例1500包括如下至少一个：第一网关GW，或第一数据面功能节点，或第一基站。
在本发明的一些实施例中，请参阅如图15-b所示，若所述第一功能实例为所述第一基站时，所述第一功能实例1500，还包括：资源分配模块1504和 发送模块1505，其中，
所述接收模块1501，还用于所述数据包处理模块1503使用与第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理之前，接收所述第一UE发送的上行调度请求，所述上行调度请求包括：所述UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
所述资源分配模块1504，用于根据所述上行调度请求分配与第一切片标识或者第一连接标识对应的空口传输资源；
所述发送模块1505，用于向所述第一UE发送资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和所述第一切片标识或者第一连接标识对应的空口传输资源。
在本发明的一些实施例中，所述数据包处理模块1503，具体用于通过所述承载接收所述第一UE发送的上行数据包，所述第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，使用与第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理，然后通过所述承载向所述第一UE发送处理完成后的下行数据包。
在本发明的一些实施例中，所述对应于所述第一UE的第一业务的数据包和所述第一切片标识对应，包括：
当所述第一功能实例包括第一网关GW时，所述第一GW接收的下行数据包的互联网协议IP五元组，和所述第一切片标识对应；或，
当所述第一功能实例包括第一数据面功能节点时，所述第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、虚拟局域网标识VLAN ID、多协议标签交换MPLS标签、承载标识中的至少一个，和所述第一切片标识对应；或，
当所述第一功能实例包括第一基站时，所述第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识中的至少一个，和所述第一切片标识对应。
需要说明的是，上述装置各模块/单元之间的信息交互、执行过程等内容，由于与本发明方法实施例基于同一构思，其带来的技术效果与本发明方法实施例相同，具体内容可参见本发明前述所示的方法实施例中的叙述，此处不再赘述。
通过前述实施例对本发明的描述可知，第一功能实例接收控制器对第一功能实例和第一UE分别发送的建立承载的指示信息，第一功能实例根据建立承载的指示信息建立为第一UE的第一业务服务的承载，该承载和控制器为对应于第一UE的第一业务的数据包选择的第一网络切片对应，第一功能实例使用与第一切片标识对应的处理资源和/或传输资源对承载上传输的对应于第一UE的第一业务的数据包进行处理，对应于第一UE的第一业务的数据包和第一网络切片对应。本发明实施例中对于不同的业务具有不同的业务标识，不同的业务具有不同的业务需求，控制器获取到业务和网络切片的对应关系，网络切片的切片标识和功能实例的实例标识相对应，当UE具有不同的业务标识时可以获取到不同的切片标识，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例，不同的功能实例可以使用不同的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
需要说明的是，上述装置各模块/单元之间的信息交互、执行过程等内容，由于与本发明方法实施例基于同一构思，其带来的技术效果与本发明方法实施例相同，具体内容可参见本发明前述所示的方法实施例中的叙述，此处不再赘述。
本发明实施例还提供一种计算机存储介质，其中，该计算机存储介质存储有程序，该程序执行包括上述方法实施例中记载的部分或全部步骤。
接下来介绍本发明实施例提供的另一种控制器，请参阅图16-a所示，控制器1600包括：发送单元1601和处理单元1602，其中，
所述处理单元1602，用于获取与第一业务相对应的第一切片标识；根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例；
所述发送单元10601，用于向第一用户设备UE和所述第一功能实例分别 发送建立承载的指示信息，所述承载用于传输对应于所述第一UE的第一业务的数据包，所述承载和所述第一切片标识对应，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识。
在本发明的一些实施例中，所述处理单元1602，还用于获取业务和网络切片的对应关系，所述网络切片与切片标识对应。
在本发明的一些实施例中，如图16-b所示，所述控制器1600，还包括：第一接收单元1603，其中，
所述第一接收单元1603，用于接收业务提供服务器发送的业务信息，所述业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或所述业务信息包括：业务对应的业务标识、业务需要的服务质量要求和和业务的区域范围；
所述处理单元1602，还用于根据所述业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；根据所述为业务部署的功能实例建立业务和网络切片的对应关系。
在本发明的一些实施例中，所述发送单元1601，还用于将所述业务和网络切片的对应关系发送给所述业务提供服务器。
在本发明的一些实施例中，所述处理单元1602，还用于从网络切片部署装置获取所述业务和网络切片的对应关系。
在本发明的一些实施例中，如图16-c所示，所述控制器1600，还包括：第二接收单元1604，其中，
所述第二接收单元1604，用于接收第一UE发送的认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识；
所述处理单元1602，用于根据所述认证请求消息选择归属签约用户服务器HSS；
所述第二接收单元1604，还用于接收所述HSS发送的所述HSS对所述第一UE进行身份认证和切片鉴权的认证结果；
所述处理单元1602，具体用于若所述认证结果为所述第一UE通过身份认证和切片鉴权，根据所述第一切片标识确定所述第一功能实例。
在本发明的一些实施例中，如图16-d所示，所述控制器1600，还包括：第三接收单元1605，其中，
所述第三接收单元1605，用于接收策略及计费执行功能PCEF实体在接收到策略与计费规则功能PCRF实体发送的第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，所述实例请求消息包括：所述PCEF实体从所述认证结果中获取到的所述第一切片标识；
所述处理单元1602，具体用于接收到所述实例请求消息之后，根据所述第一切片标识确定所述第一功能实例。
在本发明的一些实施例中，所述发送单元1601，还用于将所述业务和网络切片的对应关系发送给HSS或PCRF实体。
需要说明的是，在本发明实施例中，处理单元1602具体可以为处理器，发送单元1601具体可以为发射器，接收单元1603具体可以为接收器。并且控制器1600中的处理单元1602的数量可以一个或多个，图16-a、图16-b、图16-c、图16-d中以一个处理单元为例。在本发明的一些实施例中，发送单元1601、接收单元1603、处理单元1602可通过总线或其它方式连接。其中，以上多个实施例中第一接收单元、第二接收单元、第三接收单元可以通过一个接收单元来实现，当然，也可以通过两个接收单元、三个接收单元来实现，接收单元可以是接收器。
通过前述实施例对本发明的描述可知，首先控制器根据业务需求建立业务和网络切片的对应关系，接下来控制器根据第一切片标识选择与第一切片标识对应的第一功能实例。第一功能实例包括：对应于第一切片标识的一个或多个功能实例，最后控制器向第一UE和第一功能实例分别发送建立承载的指示信息，该承载用于传输对应于第一UE的第一业务的数据包，该承载和具有第一切片标识的第一网络切片对应。本发明实施例中对于不同的业务具有不同的业务标识，不同的业务具有不同的业务需求，控制器获取到了业务和网络切片的对应关系，网络切片的切片标识和功能实例的实例标识相对应，当UE具有不同的业务标识时可以获取到不同的切片标识，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例，不同的功能实例可以使用不同的处理资源和/或传输资源提供不同 的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
接下来介绍本发明实施例提供的另一种第一UE，请参阅图17-a所示，第一UE1700包括：接收单元1701和处理单元1702，其中，
所述接收单元1701，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识；
所述处理单元1702，用于根据所述指示信息建立为所述第一UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载，所述第一功能实例与所述第一切片标识对应；通过所述承载传输所述第一业务的数据包，所述数据包和所述第一切片标识对应。
在本发明的一些实施例中，如图17-b所示，所述第一UE1700，还包括：第一发送单元1703，其中，
所述第一发送单元1703，用于向所述控制器发送认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识。
在本发明的一些实施例中，如图17-c所示，所述第一UE1700，还包括：第二发送单元1704，其中，
所述第二发送单元1704，用于向策略及计费执行功能PCEF实体发送业务请求消息，所述业务请求消息包括：所述第一UE的第一业务对应的第一业务标识。
在本发明的一些实施例中，如图17-d所示，所述第一UE1700，还包括：第三发送单元1705，其中，
所述第三发送单元1705，用于通过所述承载向所述第一功能实例发送上行数据包，由所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
所述接收单元1701，还用于通过所述承载接收所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后发送的下行数据包。
在本发明的一些实施例中，如图17-e所示，所述第一UE1700，还包括：第四发送单元1706，其中，
所述第四发送单元1706，用于所述处理单元通过所述承载传输所述第一业务的数据包之前，通过向第一基站发送上行调度请求，所述上行调度请求包括：所述第一UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
所述接收单元1701，用于接收所述第一基站发送的资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和所述第一切片标识或者所述第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
需要说明的是，在本发明实施例中，处理单元1702具体可以为处理器，接收单元1701具体可以为接收器，发送单元1703具体可以为发射器。并且控制器1700中的处理单元1702的数量可以一个或多个，图17-a、图17-b、图17-c、图17-d、图17-e中以一个处理单元为例。在本发明的一些实施例中，发送单元1703、接收单元1701、处理单元1702可通过总线或其它方式连接。其中，以上多个实施例中第一发送单元、第二发送单元、第三发送单元、第四发送单元可以通过一个发送单元来实现，当然，也可以通过两个发送单元、三个发送单元、四个发送单元来实现。
通过前述实施例对本发明的描述可知，第一UE按照控制器对第一UE和第一功能实例分别发送的建立承载的指示信息建立为第一UE的第一业务服务的承载，第一UE通过承载传输对应于第一UE的第一业务的数据包，对应于第一UE的第一业务的数据包和第一网络切片对应。本发明实施例中对于不同的业务具有不同的业务标识，不同的业务具有不同的业务需求，控制器获取到业务和网络切片的对应关系，网络切片的切片标识和功能实例的实例标识相对应，当UE具有不同的业务标识时可以获取到不同的切片标识，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例，不同的功能实例可以使用不同的处理资源和/或传输 资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
接下来介绍本发明实施例提供的另一种第一功能实例，请参阅图18-a所示，第一功能实例1800包括：接收单元1801和处理单元1802，其中，
所述接收单元1801，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有第一用户设备UE的标识和所述第一功能实例的标识；
所述处理单元1802，用于根据所述指示信息建立为第一用户设备UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载；使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理，所述第一业务的数据包和所述第一切片标识对应。
在本发明的一些实施例中，所述第一功能实例1800包括以下至少一个：第一网关GW，或第一数据面功能节点，或第一基站。
在本发明的一些实施例中，请参阅如图18-b所示，若所述第一功能实例为第一基站时，所述第一基站，还包括：第一发送单元1803，其中，
所述接收单元1801，还用于所述处理单元1802使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理之前，接收所述第一UE发送的上行调度请求，所述上行调度请求包括：所述UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
所述处理单元1802，还用于根据所述上行调度请求分配与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源；
所述第一发送单元1803，用于向所述第一UE发送资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
在本发明的一些实施例中，请参阅如图18-c所示，所述第一功能实例1800，还包括：第二发送单元1804，其中，
所述接收单元1801，用于通过所述承载接收所述第一UE发送的上行数据包；
所述处理单元1802，具体用于使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
所述处理单元1802，具体用于使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理；
所述第二发送单元1804，用于通过所述承载向所述第一UE发送处理完成后的所述下行数据包。
在本发明的一些实施例中个，所述第一业务的数据包和所述第一切片标识对应，包括：
当所述第一功能实例包括第一网关GW时，所述第一GW接收的下行数据包的互联网协议IP五元组，和所述第一切片标识对应；或，
当所述第一功能实例包括第一数据面功能节点时，所述第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、虚拟局域网标识VLAN ID、多协议标签交换MPLS标签、承载标识中的至少一个，和所述第一切片标识对应；或，
当所述第一功能实例包括第一基站时，所述第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识中的至少一个，和所述第一切片标识对应。
需要说明的是，在本发明实施例中，处理单元1802具体可以为处理器，发送单元1803具体可以为发射器，接收单元1801具体可以为接收器。并且控制器1800中的处理单元1802的数量可以一个或多个，图18-a、图18-b、图18-c中以一个处理单元为例。在本发明的一些实施例中，发送单元1803、接收单元1801、处理单元1802可通过总线或其它方式连接。其中，以上多个实施例中第一发送单元、第二发送单元可以通过一个发送单元来实现，当然，也可以通过两个发送单元来实现。
通过前述实施例对本发明的描述可知，第一功能实例接收控制器对第一功能实例和第一UE分别发送的建立承载的指示信息，第一功能实例根据建立承载的指示信息建立为第一UE的第一业务服务的承载，该承载和控制器为对应于第一UE的第一业务的数据包选择的第一网络切片对应，第一功能实例使用 与第一切片标识对应的处理资源和/或传输资源对承载上传输的对应于第一UE的第一业务的数据包进行处理，对应于第一UE的第一业务的数据包和第一网络切片对应。本发明实施例中对于不同的业务具有不同的业务标识，不同的业务具有不同的业务需求，控制器获取到了业务和网络切片的对应关系，网络切片的切片标识和功能实例的实例标识相对应，当UE具有不同的业务标识时可以获取到不同的切片标识，例如，第一UE向控制器请求分配功能实例，该第一UE对应的切片标识为第一切片标识，或者该第一UE发起的第一业务对应的切片标识为第一切片标识，控制器根据第一切片标识可以获取到对应的第一功能实例，控制器配置的该第一功能实例可以包括一个或多个功能实例，不同的功能实例可以使用不同的处理资源和/或传输资源提供不同的处理功能。本发明实施例中通过切片标识来选择对应的功能实例，从而使得不同的功能实例可以根据业务需求使用不同的处理资源和/或传输资源提供差异化的处理功能，因此可以满足特定的业务功能以及特定的服务质量需求以及特定的体验质量需求，从而可以为不同的用户设备以及不同的业务提供差异化服务。
另外需说明的是，以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本发明提供的装置实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可借助软件加必需的通用硬件的方式来实现，当然也可以通过专用硬件包括专用集成电路、专用CPU、专用存储器、专用元器件等来实现。一般情况下，凡由计算机程序完成的功能都可以很容易地用相应的硬件来实现，而且，用来实现同一功能的具体硬件结构也可以是多种多样的，例如模拟电路、数字电路或专用电路等。但是，对本发明而言更多情况下软件程序实现是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘、U盘、移动硬盘、只读存储器(ROM，Read-Only  Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
综上所述，以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照上述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对上述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (36)

  1. 一种通信控制方法，其特征在于，包括：
    控制器获取与第一业务相对应的第一切片标识；
    所述控制器根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例；
    所述控制器向第一用户设备UE和所述第一功能实例分别发送建立承载的指示信息，所述承载用于传输对应于所述第一UE的第一业务的数据包，所述承载和所述第一切片标识对应，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述控制器获取业务和网络切片的对应关系，所述网络切片与切片标识对应。
  3. 根据权利要求2所述的方法，其特征在于，所述控制器获取业务和网络切片的对应关系，包括：
    所述控制器接收业务提供服务器发送的业务信息，所述业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或所述业务信息包括：业务对应的业务标识、业务需要的服务质量要求和业务的区域范围；
    所述控制器根据所述业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；
    所述控制器根据所述为业务部署的功能实例建立业务和网络切片的对应关系。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述控制器将所述业务和网络切片的对应关系发送给所述业务提供服务器。
  5. 根据权利要求2所述的方法，其特征在于，所述控制器获取业务和网络切片的对应关系，包括：
    所述控制器从网络切片部署装置获取所述业务和网络切片的对应关系。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述控制器根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例，包括：
    所述控制器接收所述第一UE发送的认证请求消息，所述认证请求消息包 括：所述第一UE的第一业务对应的第一业务标识；
    所述控制器根据所述认证请求消息选择归属签约用户服务器HSS；
    所述控制器接收所述HSS发送的所述HSS对所述第一UE进行身份认证和切片鉴权的认证结果；
    若所述认证结果为所述第一UE通过身份认证和切片鉴权，所述控制器根据所述第一切片标识确定所述第一功能实例。
  7. 根据权利要求1至5中任一项所述的方法，其特征在于，所述控制器获取与第一业务相对应的第一切片标识，包括：
    所述控制器接收策略及计费执行功能PCEF实体在接收到策略与计费规则功能PCRF实体发送的第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，所述实例请求消息包括：所述PCEF实体从所述认证结果中获取到的所述第一切片标识；
    所述控制器根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例包括：
    所述控制器接收到所述实例请求消息之后，所述控制器根据所述第一切片标识确定所述第一功能实例。
  8. 根据权利要求2至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述控制器将所述业务和网络切片的对应关系发送给HSS或PCRF实体。
  9. 一种通信控制方法，其特征在于，包括：
    第一用户设备UE接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识；
    所述第一UE根据所述指示信息建立为所述第一UE的第一业务服务的所述第一UE与所述第一功能实例之间的承载，所述第一功能实例与所述第一切片标识对应；
    所述第一UE通过所述承载传输所述第一业务的数据包，所述数据包和所述第一切片标识对应。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述第一UE向所述控制器发送认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述第一UE向策略及计费执行功能PCEF实体发送业务请求消息，所述业务请求消息包括：所述第一UE的第一业务对应的第一业务标识。
  12. 根据权利要求9至11中任一项所述的方法，其特征在于，所述第一UE通过所述承载传输所述第一业务的数据包，包括：
    所述第一UE通过所述承载向所述第一功能实例发送上行数据包，由所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
    所述第一UE通过所述承载接收所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后发送的下行数据包。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一UE向第一基站发送上行调度请求，所述上行调度请求包括：所述第一UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
    所述第一UE接收所述第一基站发送的资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和所述第一切片标识或者所述第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
  14. 一种通信控制方法，其特征在于，包括：
    第一功能实例接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有第一用户设备UE的标识和所述第一功能实例的标识；
    所述第一功能实例根据所述指示信息建立为第一用户设备UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载；
    所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理，所述第一业务的数据包和所述第一切片标识对应。
  15. 根据权利要求14所述的方法，其特征在于，所述第一功能实例包括以下至少一个：第一网关GW，或第一数据面功能节点，或第一基站。
  16. 根据权利要求15所述的方法，其特征在于，若所述第一功能实例为 所述第一基站时，所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理之前，所述方法还包括：
    所述第一基站接收所述第一UE发送的上行调度请求，所述上行调度请求包括：所述UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
    所述第一基站根据所述上行调度请求分配与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源；
    所述第一基站向所述第一UE发送资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
  17. 根据权利要求14至16中任一项所述的方法，其特征在于，所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理，包括：
    所述第一功能实例通过所述承载接收所述第一UE发送的上行数据包，所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
    所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理，然后通过所述承载向所述第一UE发送处理完成后的所述下行数据包。
  18. 根据权利要求14至17中任一项所述的方法，其特征在于，所述第一业务的数据包和所述第一切片标识对应，包括：
    当所述第一功能实例包括第一网关GW时，所述第一GW接收的下行数据包的互联网协议IP五元组，和所述第一切片标识对应；或，
    当所述第一功能实例包括第一数据面功能节点时，所述第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、虚拟局域网标识VLAN ID、多协议标签交换MPLS标签、承载标识中的至少一个，和所述第一切片标识对应；或，
    当所述第一功能实例包括第一基站时，所述第一基站接收的上行数据包使 用的物理时频资源、用户标识、连接标识中的至少一个，和所述第一切片标识对应。
  19. 一种控制器，其特征在于，包括：发送单元和处理单元，其中，
    所述处理单元，用于获取与第一业务相对应的第一切片标识；根据所述第一切片标识确定与所述第一切片标识对应的第一功能实例；
    所述发送单元，用于向第一用户设备UE和所述第一功能实例分别发送建立承载的指示信息，所述承载用于传输对应于所述第一UE的第一业务的数据包，所述承载和所述第一切片标识对应，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识。
  20. 根据权利要求19所述的控制器，其特征在于，所述处理单元，还用于获取业务和网络切片的对应关系，所述网络切片与切片标识对应。
  21. 根据权利要求20所述的控制器，其特征在于，所述控制器，还包括：第一接收单元，其中，
    所述第一接收单元，用于接收业务提供服务器发送的业务信息，所述业务信息包括：业务对应的业务标识和业务需要的服务质量要求，或所述业务信息包括：业务对应的业务标识、业务需要的服务质量要求和和业务的区域范围；
    所述处理单元，还用于根据所述业务信息部署功能实例，并建立为业务部署的功能实例与网络切片的对应关系；根据所述为业务部署的功能实例建立业务和网络切片的对应关系。
  22. 根据权利要求21所述的控制器，其特征在于，所述发送单元，还用于将所述业务和网络切片的对应关系发送给所述业务提供服务器。
  23. 根据权利要求20所述的控制器，其特征在于，所述处理单元，还用于从网络切片部署装置获取所述业务和网络切片的对应关系。
  24. 根据权利要求19至23中任一项所述的控制器，其特征在于，所述控制器，还包括：第二接收单元，其中，
    所述第二接收单元，用于接收第一UE发送的认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识；
    所述处理单元，用于根据所述认证请求消息选择归属签约用户服务器HSS；
    所述第二接收单元，还用于接收所述HSS发送的所述HSS对所述第一 UE进行身份认证和切片鉴权的认证结果；
    所述处理单元，具体用于若所述认证结果为所述第一UE通过身份认证和切片鉴权，根据所述第一切片标识确定所述第一功能实例。
  25. 根据权利要求19至23中任一项所述的控制器，其特征在于，所述控制器，还包括：第三接收单元，其中，
    所述第三接收单元，用于接收策略及计费执行功能PCEF实体在接收到策略与计费规则功能PCRF实体发送的第一UE通过身份认证和切片鉴权的认证结果之后发送的实例请求消息，所述实例请求消息包括：所述PCEF实体从所述认证结果中获取到的所述第一切片标识；
    所述处理单元，具体用于接收到所述实例请求消息之后，根据所述第一切片标识确定所述第一功能实例。
  26. 根据权利要求20至25中任一项所述的控制器，其特征在于，所述发送单元，还用于将所述业务和网络切片的对应关系发送给HSS或PCRF实体。
  27. 一种用户设备UE，其特征在于，所述UE具体为第一UE，所述第一UE，包括：接收单元和处理单元，其中，
    所述接收单元，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有所述第一UE的标识和所述第一功能实例的标识；
    所述处理单元，用于根据所述指示信息建立为所述第一UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载，所述第一功能实例与所述第一切片标识对应；通过所述承载传输所述第一业务的数据包，所述数据包和所述第一切片标识对应。
  28. 根据权利要求27所述的用户设备，其特征在于，所述第一UE，还包括：第一发送单元，其中，
    所述第一发送单元，用于向所述控制器发送认证请求消息，所述认证请求消息包括：所述第一UE的第一业务对应的第一业务标识。
  29. 根据权利要求27所述的用户设备，其特征在于，所述第一UE，还包括：第二发送单元，其中，
    所述第二发送单元，用于向策略及计费执行功能PCEF实体发送业务请求消息，所述业务请求消息包括：所述第一UE的第一业务对应的第一业务标识。
  30. 根据权利要求27至29中任一项所述的用户设备，其特征在于，所述 第一UE，还包括：第三发送单元，其中，
    所述第三发送单元，用于通过所述承载向所述第一功能实例发送上行数据包，由所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
    所述接收单元，还用于通过所述承载接收所述第一功能实例使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理之后发送的下行数据包。
  31. 根据权利要求27至30中任一项所述的用户设备，其特征在于，所述第一UE，还包括：第四发送单元，其中，
    所述第四发送单元，用于所述处理单元通过所述承载传输所述第一业务的数据包之前，通过向第一基站发送上行调度请求，所述上行调度请求包括：所述第一UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
    所述接收单元，用于接收所述第一基站发送的资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和所述第一切片标识或者所述第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
  32. 一种功能实例，其特征在于，所述功能实例具体为第一功能实例，所述第一功能实例，包括：接收单元和处理单元，其中，
    所述接收单元，用于接收建立与第一切片标识对应的承载的指示信息，所述指示信息携带有第一用户设备UE的标识和所述第一功能实例的标识；
    所述处理单元，用于根据所述指示信息建立为第一用户设备UE的第一业务服务的所述第一UE和所述第一功能实例之间的承载；使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理，所述第一业务的数据包和所述第一切片标识对应。
  33. 根据权利要求32所述的功能实例，其特征在于，所述第一功能实例包括以下至少一个：第一网关GW，或第一数据面功能节点，或第一基站。
  34. 根据权利要求33所述的功能实例，其特征在于，若所述第一功能实例为第一基站时，所述第一基站，还包括：第一发送单元，其中，
    所述接收单元，还用于所述处理单元使用与所述第一切片标识对应的处理资源和/或传输资源对所述承载上传输的所述第一业务的数据包进行处理之 前，接收所述第一UE发送的上行调度请求，所述上行调度请求包括：所述UE需要发送的数据包对应的所述第一切片标识或者第一连接标识；
    所述处理单元，还用于根据所述上行调度请求分配与所述第一切片标识或者第一连接标识对应的空口传输资源；
    所述第一发送单元，用于向所述第一UE发送资源指配信息，所述资源指配信息包括：所述第一切片标识或者所述第一连接标识，以及和与所述第一切片标识或者第一连接标识对应的处理资源和/或传输资源，所述处理资源和/或传输资源包括空口传输资源。
  35. 根据权利要求32至34中任一项所述的功能实例，其特征在于，所述第一功能实例，还包括：第二发送单元，其中，
    所述接收单元，用于通过所述承载接收所述第一UE发送的上行数据包；
    所述处理单元，具体用于使用与所述第一切片标识对应的处理资源和/或传输资源对所述上行数据包进行处理；和/或，
    所述处理单元，具体用于使用与所述第一切片标识对应的处理资源和/或传输资源对下行数据包进行处理；
    所述第二发送单元，用于通过所述承载向所述第一UE发送处理完成后的所述下行数据包。
  36. 根据权利要求32至35中任一项所述的功能实例，其特征在于，所述第一业务的数据包和所述第一切片标识对应，包括：
    当所述第一功能实例包括第一网关GW时，所述第一GW接收的下行数据包的互联网协议IP五元组，和所述第一切片标识对应；或，
    当所述第一功能实例包括第一数据面功能节点时，所述第一数据面功能节点传输的上行数据包或下行数据包的IP五元组、虚拟局域网标识VLAN ID、多协议标签交换MPLS标签、承载标识中的至少一个，和所述第一切片标识对应；或，
    当所述第一功能实例包括第一基站时，所述第一基站接收的上行数据包使用的物理时频资源、用户标识、连接标识中的至少一个，和所述第一切片标识对应。
PCT/CN2016/097649 2015-09-17 2016-08-31 一种通信控制方法和控制器、用户设备、功能实例 WO2017045530A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16845644.0A EP3343978B1 (en) 2015-09-17 2016-08-31 Communication control method and controller, user equipment, and function instance
US15/923,899 US10595233B2 (en) 2015-09-17 2018-03-16 Communication control method, controller, user equipment, and function instance

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510593669.0A CN106550410B (zh) 2015-09-17 2015-09-17 一种通信控制方法和控制器、用户设备、相关装置
CN201510593669.0 2015-09-17

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/923,899 Continuation US10595233B2 (en) 2015-09-17 2018-03-16 Communication control method, controller, user equipment, and function instance

Publications (1)

Publication Number Publication Date
WO2017045530A1 true WO2017045530A1 (zh) 2017-03-23

Family

ID=58288621

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/097649 WO2017045530A1 (zh) 2015-09-17 2016-08-31 一种通信控制方法和控制器、用户设备、功能实例

Country Status (4)

Country Link
US (1) US10595233B2 (zh)
EP (1) EP3343978B1 (zh)
CN (1) CN106550410B (zh)
WO (1) WO2017045530A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3567896A4 (en) * 2017-07-17 2020-01-15 Huawei Technologies Co., Ltd. COMMUNICATIONS METHOD, DEVICE AND SYSTEM
EP3567877A4 (en) * 2017-09-23 2020-02-26 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE

Families Citing this family (57)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017063708A1 (en) * 2015-10-15 2017-04-20 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for attaching user equipment to a mobile communications network
US11006309B2 (en) * 2015-11-18 2021-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Network node, radio network node and methods performed therein
FR3048574A1 (fr) 2016-03-07 2017-09-08 Orange Selection d'une instanciation de tranche de reseau pour la transmission de paquets montants
JP7010215B2 (ja) * 2016-04-27 2022-01-26 日本電気株式会社 通信方法、認証サーバ及び認証サーバのための方法
JP6727087B2 (ja) * 2016-09-28 2020-07-22 Kddi株式会社 通信システム、通信装置、及びプログラム
WO2018059689A1 (en) 2016-09-29 2018-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Quality of service differentiation between network slices
CN108243106B (zh) * 2016-12-23 2020-09-04 华为技术有限公司 控制网络切片的方法、转发设备、控制设备和通信系统
EP3603238B1 (en) * 2017-03-20 2023-07-05 ZTE Corporation Network slicing serving function
EP3592033A4 (en) * 2017-03-21 2020-04-22 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
JP7004738B2 (ja) * 2017-03-31 2022-01-21 中▲興▼通▲訊▼股▲ふぇん▼有限公司 セッション管理機能選択のための方法および装置
CN108809671B (zh) * 2017-04-26 2020-10-09 华为技术有限公司 通信方法、网络设备和系统
KR102493348B1 (ko) * 2017-04-27 2023-01-31 삼성전자 주식회사 네트워크 슬라이스를 이용할 수 있는 지역에 대한 정보를 획득하는 방법
CN108810978B (zh) * 2017-05-04 2022-03-18 上海诺基亚贝尔软件有限公司 用于通信资源管理的方法和设备
PL3425963T3 (pl) 2017-05-09 2021-06-28 Huawei Technologies Co., Ltd. Urządzenie i sposób komunikacji oparty na wydzieleniach
CN108933682B (zh) * 2017-05-22 2020-09-25 华为技术有限公司 网络切片控制方法、设备及系统
CN108990068B (zh) * 2017-06-01 2021-02-05 华为技术有限公司 通信方法和网络设备
US10292073B2 (en) * 2017-06-13 2019-05-14 Nokia Solutions And Networks Oy Enhancement for X2/Xn to support RAN slicing
CN109104726A (zh) * 2017-06-20 2018-12-28 上海中兴软件有限责任公司 网络切片的认证方法及相应装置、系统和介质
CN110622573A (zh) * 2017-06-29 2019-12-27 诺基亚通信公司 基于计费规则的网络切片选择
CN113364686B (zh) 2017-06-30 2022-10-04 华为技术有限公司 一种生成转发表项的方法、控制器和网络设备
CN109429214B (zh) * 2017-07-17 2020-10-16 华为技术有限公司 业务会话建立方法、设备及系统
CN109391648B (zh) 2017-08-04 2020-12-22 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统
CN109391969A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 网络管理方法和系统
CN109428749B (zh) * 2017-08-28 2022-04-22 华为技术有限公司 网络管理方法及相关设备
CN109511115B (zh) * 2017-09-14 2020-09-29 华为技术有限公司 一种授权方法和网元
CN109560948B (zh) * 2017-09-25 2021-01-29 华为技术有限公司 一种网络切片的部署方法及相关设备
CN109560952B (zh) * 2017-09-27 2021-04-09 华为技术有限公司 一种网络切片管理方法及设备
CN109600769B (zh) * 2017-09-30 2022-01-11 华为技术有限公司 通信方法及装置
CN109600760B (zh) * 2017-09-30 2022-04-22 华为技术有限公司 网络管理方法、设备及系统
CN109660379B (zh) * 2017-10-12 2022-04-05 中兴通讯股份有限公司 一种网络方法和系统、及终端
JP6979520B2 (ja) 2017-10-13 2021-12-15 テレフオンアクチーボラゲット エルエム エリクソン（パブル） ネットワーク機能サービス発見のための方法および装置
CN109787849B (zh) * 2017-11-10 2020-08-07 中国信息通信研究院 一种olt逻辑网络测试方法
CN109787803B (zh) * 2017-11-15 2021-10-26 华为技术有限公司 管理共享网络功能的方法及装置
CN109803281B (zh) 2017-11-16 2021-11-19 华为技术有限公司 网络业务的管理方法、设备及系统
EP3503609B1 (en) * 2017-12-22 2020-02-05 Deutsche Telekom AG Radio access network slice
CN110621045B (zh) 2018-06-20 2022-05-13 华为云计算技术有限公司 一种物联网业务路由的方法
CN110912795B (zh) * 2018-09-14 2022-04-15 中兴通讯股份有限公司 一种传输控制方法、节点、网络系统及存储介质
CN110972193B (zh) 2018-09-28 2021-12-03 华为技术有限公司 一种切片信息处理方法及装置
CN111031538B (zh) * 2018-10-09 2021-12-03 华为技术有限公司 一种鉴权的方法及装置
CN111147436B (zh) * 2018-11-05 2022-03-11 华为技术有限公司 一种网络切片授权的方法及通信装置
US10841964B2 (en) * 2018-11-27 2020-11-17 Verizon Patent And Licensing Inc. Systems and methods for RAN slicing in a wireless access network
CN111263383A (zh) * 2018-12-03 2020-06-09 中兴通讯股份有限公司 接入网配置方法、装置、网管设备及存储介质
US11963094B2 (en) * 2019-04-11 2024-04-16 Nokia Technologies Oy Network slice selection in a network based on use case
CN112087780B (zh) * 2019-06-14 2022-08-30 中国电信股份有限公司 Ims服务提供方法、系统和网络侧服务提供系统
CN112104469B (zh) * 2019-06-17 2022-07-29 华为技术有限公司 数据处理方法及装置
CN112152899B (zh) * 2019-06-28 2023-04-07 中兴通讯股份有限公司 一种基于网络切片的数据处理方法及装置
CN112291784B (zh) * 2019-07-09 2022-04-05 华为技术有限公司 一种通信方法以及网元
US11675324B2 (en) * 2019-09-19 2023-06-13 Bao Tran Air transportation systems and methods
CN115052369A (zh) * 2019-10-29 2022-09-13 北京小米移动软件有限公司 连接建立方法及装置、基站、用户设备和核心网设备
CN116567736A (zh) 2019-11-14 2023-08-08 华为技术有限公司 一种资源分配方法、装置、系统及存储介质
CN112804687B (zh) 2019-11-14 2023-04-11 华为技术有限公司 一种资源分配方法、装置、系统及存储介质
EP3855787B1 (en) 2020-01-27 2023-10-11 Nokia Technologies Oy Network slice selection in cellular system
CN113301586B (zh) * 2020-02-24 2023-04-18 华为技术有限公司 网络选择方法及电子设备
CN113453284B (zh) * 2020-03-27 2023-05-26 大唐移动通信设备有限公司 一种服务质量Qos控制方法、设备及存储介质
CN113541989B (zh) * 2020-04-17 2023-05-09 中国移动通信有限公司研究院 一种网络切片检测方法、装置和存储介质
CN113517995B (zh) * 2021-03-05 2024-03-12 深圳艾灵网络有限公司 网络切片建立方法和设备
CN115442304A (zh) * 2021-06-04 2022-12-06 中国移动通信有限公司研究院 一种资源确定方法、转发设备、控制器、系统及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102821154A (zh) * 2012-08-13 2012-12-12 苏州阔地网络科技有限公司 一种多功能实例通信方法及系统
US20130155963A1 (en) * 2011-12-19 2013-06-20 International Business Machines Corporation Push based services in a mobile data network with data breakout at the edge
CN103327529A (zh) * 2013-05-27 2013-09-25 北京邮电大学 针对移动通信网络的OpenFlow协议架构及业务分片处理方法
CN104349400A (zh) * 2013-07-23 2015-02-11 华为技术有限公司 无线通信的方法、有线传输检测的方法及相关设备
CN104767677A (zh) * 2014-01-07 2015-07-08 上海贝尔股份有限公司 接入节点系统和用于该接入节点系统的计算资源池单元

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8825876B2 (en) * 2008-07-17 2014-09-02 Qualcomm Incorporated Apparatus and method for mobile virtual network operator (MVNO) hosting and pricing
US8948726B2 (en) * 2008-12-29 2015-02-03 Blackberry Limited Device-based network service provisioning
US9537730B2 (en) * 2009-09-18 2017-01-03 Nokia Solutions And Networks Gmbh & Co. Kg Virtual network controller
CN104081719B (zh) * 2012-01-26 2017-12-15 西门子公司 在物理网络上控制应用的通信服务的控制器和方法
KR20140144266A (ko) * 2012-04-05 2014-12-18 퀄컴 인코포레이티드 Lte 무선 액세스 네트워크 공유를 위한 방법 및 장치
JP2015524186A (ja) * 2012-05-09 2015-08-20 インターデイジタル パテント ホールディングス インコーポレイテッド フレキシブルなネットワーク共有
EP2901766A2 (en) * 2012-09-27 2015-08-05 Interdigital Patent Holdings, Inc. End-to-end architecture, api framework, discovery, and access in a virtualized network
US20160219076A1 (en) * 2015-01-26 2016-07-28 Sprint Communications Company L.P. Hardware trust for integrated network function virtualization (nfv) and software defined network (sdn) systems
CN106375987B (zh) * 2015-07-22 2021-08-20 中兴通讯股份有限公司 一种网络切片的选择方法及系统
US9775045B2 (en) * 2015-09-11 2017-09-26 Intel IP Corporation Slicing architecture for wireless communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130155963A1 (en) * 2011-12-19 2013-06-20 International Business Machines Corporation Push based services in a mobile data network with data breakout at the edge
CN102821154A (zh) * 2012-08-13 2012-12-12 苏州阔地网络科技有限公司 一种多功能实例通信方法及系统
CN103327529A (zh) * 2013-05-27 2013-09-25 北京邮电大学 针对移动通信网络的OpenFlow协议架构及业务分片处理方法
CN104349400A (zh) * 2013-07-23 2015-02-11 华为技术有限公司 无线通信的方法、有线传输检测的方法及相关设备
CN104767677A (zh) * 2014-01-07 2015-07-08 上海贝尔股份有限公司 接入节点系统和用于该接入节点系统的计算资源池单元

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3343978A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3567896A4 (en) * 2017-07-17 2020-01-15 Huawei Technologies Co., Ltd. COMMUNICATIONS METHOD, DEVICE AND SYSTEM
EP3567877A4 (en) * 2017-09-23 2020-02-26 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
JP2020511848A (ja) * 2017-09-23 2020-04-16 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． 通信方法および通信装置
US10939333B2 (en) 2017-09-23 2021-03-02 Huawei Technologies Co., Ltd. Communication method and communications apparatus to implement a network slice based service in a central unit (CU)-distributed unit (DU) architecture

Also Published As

Publication number Publication date
US10595233B2 (en) 2020-03-17
US20180206152A1 (en) 2018-07-19
EP3343978B1 (en) 2022-04-06
EP3343978A1 (en) 2018-07-04
CN106550410A (zh) 2017-03-29
EP3343978A4 (en) 2018-09-12
CN106550410B (zh) 2020-07-07

Similar Documents

Publication Publication Date Title
WO2017045530A1 (zh) 一种通信控制方法和控制器、用户设备、功能实例
US11683716B2 (en) Communication apparatus, system, method, allocation apparatus, and non-transitory recording medium
CN108810903B (zh) 一种数据传输配置及数据传输方法和装置
Sama et al. Reshaping the mobile core network via function decomposition and network slicing for the 5G Era
CN108713327B (zh) 用于实现通信网络中的通信的网络节点和在网络节点中执行的方法
US9173158B2 (en) Method and apparatus for improving LTE enhanced packet core architecture using openflow network controller
JP2022093339A (ja) ＱｏＳ制御方法およびデバイス
EP3226604A1 (en) Data multi streaming transmission method, apparatus, anchor point, and system
CN111684824A (zh) 增强的nef功能、mec和5g集成
CN109155904B (zh) 支持本地多媒体广播多播服务（mbms）分发的装置和方法
US10686723B2 (en) Providing quality of service based on bandwidth
CN103220650A (zh) 一种WiFi终端访问不同业务域的方法和装置
US10326669B2 (en) Data service policy control based on software defined network (SDN) key performance indicators (KPIS)
WO2022012352A1 (zh) 一种业务处理方法、装置、设备及系统
WO2017177753A1 (zh) 一种基于流的承载管理方法、数据传输方法及装置
US11723062B2 (en) System and method for determining priorities for handling data based on network slice identifiers
CN107005834A (zh) 数据处理的方法和设备
US10389601B2 (en) Dynamic adaptive network
WO2016095142A1 (zh) 软件定义网络sdn中数据转发的方法、设备和系统
US20160353459A1 (en) Apparatus and method for allocating base station resources based on virtualization
EP2487847B1 (en) QoS control method and system
Dao et al. A softwarized paradigm for mobile virtual networks: Overcoming a lack of access infrastructure
CN114845344A (zh) 一种多接入边缘计算网络、流量处理方法及相关设备
JP6180182B2 (ja) 複数の無線ベアラにアクセスする方法及び装置
CN118714089A (zh) 一种数据传输方法及其相关装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16845644

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016845644

Country of ref document: EP