CN110380887B

CN110380887B - Communication method and device

Info

Publication number: CN110380887B
Application number: CN201810333894.4A
Authority: CN
Inventors: 黄亚达; 武绍芸
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-04-13
Filing date: 2018-04-13
Publication date: 2021-04-09
Anticipated expiration: 2038-04-13
Also published as: CN110380887A; CN113225206A; WO2019196796A1

Abstract

The application provides a communication method and a device, and the method comprises the following steps: the method comprises the following steps that core network equipment obtains strategy parameters of a network slice, wherein the strategy parameters of the network slice comprise at least one of the following parameters: accessing a control strategy parameter, a scheduling control strategy parameter and a bandwidth control strategy parameter; the core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, so that the access network device determines the relevant policy of the network slice according to the policy parameters of the network slice. According to the method and the device, the strategy parameters of the network slices are set, and the related strategies of the network slices are determined according to the strategy parameters of the network slices, so that the service quality of the network slices can be guaranteed to a certain extent.

Description

Communication method and device

Technical Field

The present application relates to the field of communications, and in particular, to a communication method and apparatus.

Background

With the continuous emergence of various communication services, the requirements of different communication services on network performance are significantly different, and the fifth generation mobile communication system (5G) introduces the concept of Network Slice (NS) to cope with the difference of the requirements of different communication services on network performance.

The network slice refers to a set of logical network functional entities supporting a specific communication service requirement, and realizes a service that can be customized for a communication service mainly by means of a Software Defined Network (SDN) technology and a Network Function Virtualization (NFV) technology. One network slice meets the requirement of a certain type or one use case of connection communication service, and the whole network system consists of a large number of network slices meeting different connection capacities.

The network slice is end-to-end and includes a radio access network, a transport network, a core network, and the like. The radio access network, the transmission network and the core network are all processed by slicing, so that a plurality of partial network slices are connected together to form an integral network slice which can provide a complete service for users. The network slices of different parts are logically isolated, and the network resources of the infrastructure are shared. When the business model of an operator changes from selling connection to a single user to selling network slices in a vertical industry, the original guarantee requirement according to the QoS of the user is converted into the guarantee requirement according to the Service-Level Agreement (SLA) to carry out slice-Level guarantee, for example, how to guarantee the Service quality of the network slices, how to guarantee the network slices to meet the requirements of the clients, how to guarantee the network resources between the network slices to be reasonably configured, and the like.

At present, there is no guarantee scheme for network slicing.

Disclosure of Invention

The application provides a communication method and a communication device, which can ensure the service quality of network slices to a certain extent by setting priorities for the network slices.

In a first aspect, a communication method is provided, and the method includes: the method comprises the following steps that core network equipment obtains strategy parameters of a network slice, wherein the strategy parameters of the network slice comprise at least one of the following parameters: accessing a control strategy parameter, a scheduling control strategy parameter and a bandwidth control strategy parameter; the core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, so that the access network device determines the relevant policy of the network slice according to the policy parameters of the network slice.

Optionally, the core network device obtains the policy parameter of the network slice through NWDAF.

Optionally, the core network device obtains the policy parameter of the network slice according to a predefined algorithm.

Specifically, the core network device sends a notification message to the access network device, where the notification message carries the policy parameter of the network slice and the slice identifier of the network slice. Correspondingly, the access network device receives the notification message from the core network device, and the access network device obtains the slice identifier of the network slice and the policy parameter of the network slice by analyzing the notification message. The slice identification of the network slice refers to information capable of uniquely identifying the network slice. The access network device may identify the network slice based on the slice identification.

According to the embodiment of the application, the strategy parameters of the network slices are set, and then the network slices are processed according to the strategy parameters of the network slices, so that the differentiated processing of the network slices can be realized, and the improvement of the service quality of the network slices is facilitated.

With reference to the first aspect, in a possible implementation manner of the first aspect, the priority of the network slice is an access category priority related to an access control policy, where a higher access category priority prioritizes access to the network over a lower access category priority.

Therefore, in the embodiment, the number of users allowed to access by the network slice can be controlled by setting the access category priority of the network slice and then configuring the access control policy of the network slice according to the access category priority of the network slice, and the service quality of the network slice can be guaranteed to a certain extent.

With reference to the first aspect, in a possible implementation manner of the first aspect, the policy parameter of the network slice is an access category priority; the core network device obtaining the policy parameters of the network slice includes: the core network equipment divides all network slices in the system into at least two access categories and sets access category priority according to the at least two access categories; the core network device obtains the policy parameter of the network slice, and the policy parameter of the network slice is the access category priority corresponding to the access category to which the network slice belongs.

With reference to the first aspect, in a possible implementation manner of the first aspect, the method further includes: the core network device informs the terminal device of the access type of the network slice, and the terminal device is a terminal device which establishes a subscription relationship with the network slice.

With reference to the first aspect, in a possible implementation manner of the first aspect, the policy parameter of the network slice is an allowed access control parameter or a forbidden access control parameter.

Optionally, the policy parameter of the network slice is a scheduling control policy parameter. For example, the scheduling control policy parameter is a scheduling priority, wherein a higher scheduling priority prioritizes resource scheduling over a lower scheduling priority.

In this embodiment, the resource scheduling of the network slice is controlled according to the scheduling control policy parameter of the network slice, so that the service quality of the network slice can be guaranteed to a certain extent.

Optionally, the policy parameter of the network slice is a bandwidth control policy parameter.

Therefore, in this embodiment, by setting the bandwidth control policy parameter of the network slice, the bandwidth size of the network slice can be flexibly configured, and the service quality of the network slice can be guaranteed to a certain extent.

With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the core network device, the policy parameter of the network slice to an access network device corresponding to the network slice includes: the core network device sends the policy parameters of the network slice to the access network device through the user plane or the control plane.

With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the core network device, the policy parameter of the network slice to an access network device corresponding to the network slice includes: the core network device sends the policy parameters of the network slice to the access network device through an access and mobility management function (AMF).

With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the core network device, the policy parameter of the network slice to an access network device corresponding to the network slice includes: when the policy parameter of the network slice is changed, the core network device sends the policy parameter after the change of the network slice to the access network device.

According to the method and the device, when the strategy parameters of the network slice are determined for the first time or changed, the access network device is informed, so that the access network device can be conveniently configured according to the strategy parameters of the network slice, and the service quality of the network slice is guaranteed.

In a second aspect, a communication method is provided, the method comprising: the access network equipment receives the strategy parameters of the network slice from the core network equipment, wherein the strategy parameters of the network slice comprise at least one of the following parameters: accessing a control strategy parameter, a scheduling control strategy parameter and a bandwidth control strategy parameter; and the access network equipment determines the related strategy of the network slice according to the strategy parameter of the network slice.

With reference to the second aspect, in a possible implementation manner of the second aspect, the policy parameter of the network slice is an access control policy parameter; the access network device determines the relevant policy of the network slice according to the policy parameter of the network slice, and the method comprises the following steps: and the access network equipment determines the access control parameters of the network slice according to the access control strategy parameters of the network slice.

With reference to the second aspect, in a possible implementation manner of the second aspect, the policy parameter of the network slice is an allowed access control parameter or a forbidden access control parameter.

With reference to the second aspect, in a possible implementation manner of the second aspect, the method further includes: the access network equipment generates the access control parameters of the network slice according to the access control strategy parameters of the network slice; the access network equipment sends a broadcast message to the terminal equipment, the broadcast message carries the access control parameters of the network slice, and the terminal equipment and the network slice establish a subscription relationship.

With reference to the second aspect, in a possible implementation manner of the second aspect, the policy parameter of the network slice is a scheduling control policy parameter; the access network device determines the relevant policy of the network slice according to the policy parameter of the network slice, and the method comprises the following steps: and the access network equipment determines a strategy for scheduling resources for the terminal equipment accessed to the network slice according to the scheduling control strategy parameters of the network slice.

With reference to the second aspect, in a possible implementation manner of the second aspect, the policy parameter of the network slice is a bandwidth control policy parameter; the access network device determines the relevant policy of the network slice according to the policy parameter of the network slice, and the method comprises the following steps: and the access network equipment determines a strategy for allocating bandwidth for the terminal equipment accessed to the network slice according to the bandwidth control strategy parameters of the network slice.

With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the access network device, a policy parameter of a network slice from a core network device includes: the access network device receives the policy parameters of the network slice from the core network device through an access and mobility management function, AMF.

With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the access network device, a policy parameter of a network slice from a core network device includes: when the policy parameter of the network slice is changed, the access network device receives the policy parameter after the change of the network slice from the core network device.

With reference to the second aspect, in a possible implementation manner of the second aspect, the receiving, by the access network device, a policy parameter of a network slice from a core network device includes: the access network device receives a notification message from the core network device, where the notification message carries the policy parameter of the network slice and the slice identifier of the network slice.

In a third aspect, a communication method is provided, which includes: the terminal equipment receives the access type of the network slice sent by the core network equipment; the terminal equipment receives access control parameters sent by access network equipment, wherein the access control parameters comprise access control parameters of the network slice determined according to access control strategy parameters of the network slice sent by a core network; the terminal equipment determines the access control parameters of the network slice from the parameters received from the access network equipment according to the access type of the network slice; and the terminal equipment performs the access process of the network slice according to the access control parameters of the network slice.

With reference to the third aspect, in a possible implementation manner of the third aspect, the access control policy parameter of the network slice is an access category priority of the network slice.

With reference to the third aspect, in a possible implementation manner of the third aspect, the access control policy parameter of the network slice is an allowed access policy parameter or a forbidden access policy parameter.

In a fourth aspect, a communication device is provided, which is configured to perform the method of the first aspect or any possible implementation manner of the first aspect. In particular, the communication device may comprise means for performing the method of the first aspect or any possible implementation manner of the first aspect.

In a fifth aspect, a communication device is provided, which is configured to perform the method of the second aspect or any possible implementation manner of the second aspect. In particular, the communication device may comprise means for performing the method of the second aspect or any possible implementation of the second aspect.

A sixth aspect provides a communication device configured to perform the method of the third aspect or any of the possible implementation manners of the third aspect. In particular, the communication device may comprise means for performing the method of the third aspect or any possible implementation manner of the third aspect.

In a seventh aspect, a communication device is provided, which includes a memory for storing instructions and a processor for executing the instructions stored by the memory, and the execution of the instructions stored in the memory causes the processor to perform the first aspect or the method in any possible implementation manner of the first aspect.

In an eighth aspect, a communication device is provided, which comprises a memory for storing instructions and a processor for executing the instructions stored by the memory, and execution of the instructions stored in the memory causes the processor to perform the method of the second aspect or any possible implementation manner of the second aspect.

In a ninth aspect, there is provided a communication device comprising a memory for storing instructions and a processor for executing the instructions stored by the memory, and execution of the instructions stored in the memory causes the processor to perform the method of the third aspect or any possible implementation manner of the third aspect.

In a tenth aspect, a chip is provided, where the chip includes a processing module and a communication interface, the processing module is configured to control the communication interface to communicate with the outside, and the processing module is further configured to implement the method provided in the first aspect, the second aspect, or the third aspect.

In an eleventh aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a computer, causes the computer to carry out the method provided by the first or second or third aspect.

In a twelfth aspect, there is provided a computer program product comprising instructions which, when executed by a computer, cause the computer to carry out the method provided by the first aspect or the second aspect or the third aspect.

Drawings

Fig. 1 is a schematic diagram of a system architecture applied in the embodiment of the present application.

Fig. 2 is a schematic flowchart of a communication method according to an embodiment of the present application.

Fig. 3 is another schematic flow chart of a communication method according to an embodiment of the present application.

Fig. 4 is another schematic flow chart of a communication method provided in an embodiment of the present application.

Fig. 5 is another schematic flow chart of a communication method provided in an embodiment of the present application.

Fig. 6 is another schematic flow chart of a communication method provided in an embodiment of the present application.

Fig. 7 is another schematic flow chart of a communication method according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a communication device provided in an embodiment of the present application.

Fig. 9 is a schematic block diagram of another communication device provided in an embodiment of the present application.

Fig. 10 is a schematic block diagram of another communication device provided in an embodiment of the present application.

Fig. 11 is another schematic block diagram of another communication device provided in an embodiment of the present application.

Fig. 12 is a schematic block diagram of another communication device provided in an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a system architecture applied in the embodiment of the present application. The system architecture includes a terminal device (UE illustrated in fig. 1), an Access Network (RAN) device (RAN illustrated in fig. 1), and a Core Network (CN) device.

The terminal device may be a User Equipment (UE), a handheld terminal, a notebook computer, a subscriber unit (subscriber unit), a cellular phone (cellular phone), a smart phone (smart phone), a wireless data card, a Personal Digital Assistant (PDA) computer, a tablet computer, a wireless modem (modem), a handheld device (hand), a laptop computer (laptop computer), a cordless phone (cordless phone), a Wireless Local Loop (WLL) station, a Machine Type Communication (MTC) terminal, or other devices that can access a network. A terminal device (e.g., UE in fig. 1) and an access network device (RAN illustrated in fig. 1) communicate with each other by using some air interface technology.

The access network device (RAN) is mainly responsible for functions of radio resource management, quality of service (QoS) management, data compression, encryption, and the like on the air interface side. The access network equipment may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, etc. In systems using different radio access technologies, the names of devices with base station functionality may be different, for example, in a fifth generation (5G) system, referred to as a gNB; in an LTE system, referred to as an evolved node B (eNB or eNodeB); in the third generation (3G) system, the node b is called node b (node b).

As shown in fig. 1, the core Network device includes a Network Function (NF) as follows.

Access and mobility management function (AMF).

The AMF is mainly responsible for the signaling processing parts, such as: access control, mobility management, attach and detach, and gateway selection. When the AMF provides a service for a session in the terminal device, the AMF may provide a storage resource of a control plane for the session, store a session identifier, an SMF identifier associated with the session identifier, and the like.

Session Management Function (SMF).

SMF is responsible for the following functions: user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification, and release, and Quality of Service (QoS) control.

Policy Control Function (PCF).

The PCF mainly supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and being responsible for obtaining user subscription information related to policy decisions.

Network Data analysis Function (NWDAF).

The NWDAF mainly supports the collection and analysis of big data and provides analysis results for other related network elements.

As shown in fig. 1, the system architecture also includes a User Plane Function (UPF). The UPF is responsible for forwarding and receiving user data in the terminal equipment. The UPF can receive user data from a data network (namely a core network) and transmit the user data to the terminal equipment through the access network equipment; the UPF may also receive user data from the terminal device via the access network device and forward it to the data network. The transmission resources and scheduling functions in the UPF that provide services to the terminal device are managed and controlled by the SMF.

As shown in fig. 1, the various network functions in the core network are communicatively connected to each other. The AMF can also be respectively in communication connection with a terminal device (UE) and an access network device (RAN); the SMF may also be communicatively coupled to the UPF.

Although other Network functions in the core Network are also shown in fig. 1, such as a Network Slice Selection Function (NSSF), a Network open Function (NEF), an NF storage Function (NRF), a Unified Data Management (UDM), an Application Function (AF) and an Authentication Server Function (AUSF), and a Data Network (DN) is also shown in fig. 1, it is understood that these Network elements are not limited to the embodiment and are only illustrative.

Fig. 2 is a schematic flowchart of a communication method according to an embodiment of the present application. The method comprises the following steps.

S201, a core network device obtains a policy parameter of a network slice, wherein the policy parameter of the network slice comprises at least one of the following parameters: access control policy parameters, scheduling control policy parameters, and bandwidth control policy parameters.

The core network device obtains the policy parameter of the network slice, which may indicate that the core network device generates the policy parameter of the network slice, or may indicate that the core network device obtains the policy parameter of the network slice through other devices.

Specifically, the core network device subscribes to or requests the NWDAF to analyze the policy parameters of the network slice, and the core network device determines the policy parameters of the network slice according to the analysis result fed back by the NWDAF.

For example, the predefined algorithm is to determine the policy parameters of the network slice according to the type of the network slice, or determine the policy parameters of the network slice according to the SLA index requirements signed by the network slice, or determine the policy parameters of the network slice according to the slice parameters configured by the management network element for the network slice.

The policy parameters of the network slice include at least one of the following parameters: access control policy parameters, scheduling control policy parameters, and bandwidth control policy parameters. The access control strategy parameter represents a parameter for controlling the terminal equipment to access the network; the scheduling control policy parameter represents a parameter for scheduling resources for the terminal device accessing the network; the bandwidth control policy parameter denotes a parameter for allocating a bandwidth to a terminal device accessing the network. For example, if the bandwidth control policy parameter indicates the maximum bandwidth allocated to the network slice, the bandwidth allocated to the terminal device accessing the network slice is less than or equal to the maximum bandwidth allocated to the network slice.

The policy parameter of a network slice may be specifically the priority of the network slice. For example, the access control policy parameter of the network slice is the access category priority of the network slice; the scheduling control strategy parameter of the network slice is the scheduling priority of the network slice.

S202, the core network device sends the policy parameter of the network slice to the access network device corresponding to the network slice. Accordingly, the access network device receives the policy parameters for the network slice from the core network device.

S203, the access network device determines the relevant strategy of the network slice according to the strategy parameter of the network slice.

And when the strategy parameter of the network slice is the access control strategy parameter, the access network equipment generates the access control parameter of the network slice according to the access control strategy parameter of the network slice.

And when the strategy parameter of the network slice is the scheduling control strategy parameter, the access network equipment determines a strategy for scheduling transmission resources for the terminal equipment accessed to the network slice according to the scheduling control strategy parameter of the network slice.

And when the strategy parameter of the network slice is the bandwidth control strategy parameter, the access network equipment determines a strategy for distributing the network bandwidth for the terminal equipment accessed to the network slice according to the bandwidth control strategy parameter of the network slice.

For convenience of understanding and description, the present embodiment is described by taking one network slice as an example, but the present embodiment is not limited thereto, and all network slices in the network slice system can be processed by the method provided by the present embodiment.

It should be noted that the core network device in this embodiment may be a certain Network Function (NF) in the core network. Optionally, the core network device is NWDA, PCF, NSSF, or AMF in fig. 1. Alternatively, the core network device may be another network function besides the currently defined network function, for example, such a network function is called a Slice Control Function (SCF).

Optionally, when the core network device is a network function other than the AMF, S202 specifically includes: and the core network equipment sends the policy parameters of the network slice to the access network equipment through the AMF. Accordingly, the access network device receives the policy parameters of the network slice from the core network device through the AMF.

Optionally, in some embodiments, the policy parameter of the network slice is an access control policy parameter, in particular, an access class priority. Correspondingly, in S203, the access network device determines the access control parameter of the network slice according to the access category priority of the network slice. The access network device may send the access control parameter of the network slice to the terminal device through a broadcast message, so that the terminal device performs network access.

Specifically, the access control policy parameters include, but are not limited to: access is allowed, access is forbidden for a long time, access is forbidden for a certain probability, and the like. The access prohibition duration represents the duration from the access failure to the next access.

For example, the access category priority includes two levels, high and low, where high priority indicates access is allowed and low priority indicates access is forbidden. Assuming that the access class priority of the network slice indicates that access is allowed, the access control parameter determined by the access network device also indicates that the terminal device can access the network. When the access class priority of the network slice indicates access barring, the access control parameter determined by the access network device also indicates that the terminal device is barred from accessing the network.

As another example, the access category priority includes multiple levels, for example, including priority 1, priority 2, and priority 3, where priority 1 indicates that access is allowed, and the waiting time after access failure is T1; the priority 2 represents that the access is allowed, the waiting time after the access failure is T2, and T2 is more than T1; priority 3 indicates barring access. The priority order is: priority 1 > priority 2 > priority 3. Assuming that the access category priority of the network slice indicates that access is allowed, and the waiting time after access failure is T2, the access control parameter determined by the access network device also instructs the terminal device to access the access network according to the policy.

As an implementation manner, S201 specifically includes: the core network equipment divides all network slices in the system into at least two access categories and sets access category priority according to the at least two access categories; the core network device obtains the access category priority of the network slice, and the access category priority of the network slice is the access category priority corresponding to the access category to which the network slice belongs.

Optionally, the policy parameter of the network slice is an allowed access control parameter or a forbidden access control parameter.

If the number of the network slices in the system is large, all the network slices are divided into a plurality of access categories with small number, then the priority of the access categories is set according to the access categories, and the access control parameters are configured according to the priority of the access categories, so that the signaling overhead of issuing the access control parameters to the terminal equipment can be reduced.

It should be understood that the core network device may also set the access class priority in units of network slices. The embodiments of the present application do not limit this.

In this embodiment, the access network device generates the access control parameter according to the access category priority of the network slice. For example, the access class priority corresponds to the access control parameter one to one. The system message broadcasted by the access network device to the terminal device may include access control parameters of network slices of multiple access category priorities, and the terminal device needs to find the access control parameters of the corresponding network slices from the system message according to the access categories of the network slices. Therefore, when the access type priority of a network slice is set according to the access type of the network slice, it is necessary to notify the terminal device of the access type of the network slice in advance, and the terminal device and the network slice have a subscription relationship.

Optionally, the terminal device is made to know the access category of the network slice in a static configuration manner.

For example, when a user establishes a subscription relationship with a network slice, the access category of the network slice is statically saved. For example, the user stores the access category of the network slice in a memory space within the SIM card or the terminal device. The access category of the network slice is also stored in a user subscription database (e.g., UDM) corresponding to the network side.

The static configuration of the access category of the network slice is simple to operate and easy to deploy, and the signaling of the current network is not required to be modified.

Optionally, the terminal device is made to know the access category of the network slice in a dynamic configuration mode.

The core network device informs the terminal device of the access type of the network slice through the AMF, and the terminal device is the terminal device which establishes a subscription relationship with the network slice.

It should be understood that by setting the access category priority of the network slice and then configuring the access control policy of the network slice according to the access category priority of the network slice, differentiated access control of the network slice can be achieved.

For example, assuming that a network slice is less loaded, a higher access category priority may be set for the network slice, e.g., allowing the network slice to access more users. When the network slice is fully loaded or is approaching full load, the access category priority of the network slice is lowered, e.g., to reduce the number of users allowed to access the network slice or to prohibit access to the network slice. This may ensure the quality of service of the network slice.

Optionally, in some embodiments, the policy parameter of the network slice is a scheduling control policy parameter.

Specifically, the core network device determines a scheduling control policy parameter of the network slice according to the SLA index of the network slice or the type of the network slice.

Specifically, the scheduling control policy parameter is a scheduling priority. And the higher scheduling priority carries out resource scheduling preferentially relative to the lower scheduling priority.

For example, when the SLA index of a network slice is low, a higher scheduling priority may be set for the network slice, where the scheduling priority indicates that transmission resources are preferentially scheduled for users accessing the network slice, so as to improve the SLA index of the network slice.

In this embodiment, S202 specifically includes: the core network device sends the scheduling control strategy parameter of the network slice to the access network device through the user plane or the control plane. Accordingly, the access network device receives the scheduling control policy parameters of the network slice from the core network device through the user plane or the control plane.

In this embodiment, the scheduling priority of the network slice is set, and then the resource scheduling of the network slice is controlled according to the scheduling priority of the network slice, so that the service quality of the network slice can be guaranteed to a certain extent.

Optionally, in some embodiments, the policy parameter of the network slice is a bandwidth control policy parameter.

Specifically, the core network device determines a bandwidth control policy parameter of the network slice based on the maximum bandwidth of the network slice. For example, the maximum bandwidth of the network slice is used as the bandwidth control policy parameter of the network slice. After receiving the bandwidth control policy parameter of the network slice, the access network device needs to be less than or equal to the maximum bandwidth when allocating bandwidth to the terminal device accessing the network slice.

In this embodiment, S202 specifically includes: the core network device sends the bandwidth control strategy parameter of the network slice to the access network device through the user plane or the control plane.

The bandwidth control policy parameter for the network slice indicates the size of the bandwidth.

Optionally, the core network device notifies the access network device of the policy parameter of the network slice when determining the policy parameter of the network slice for the first time.

Optionally, when the policy parameter of the network slice is changed (or adjusted), the core network device notifies the access network device of the updated policy parameter of the network slice.

For example, when the access class priority of the network slice is degraded, the core network device notifies the access network device of the access class priority of the network slice after the degradation. For another example, when the access class priority of the network slice is upgraded, the core network device notifies the access network device of the access class priority of the network slice after the upgrade.

According to the method and the device, when the priority of the network slice is determined for the first time or the strategy parameters of the network slice are changed, the access network device is informed, so that the access network device can be conveniently configured according to the strategy parameters of the network slice, and the service quality of the network slice is guaranteed.

In the foregoing, the scheme provided by the embodiment of the present application may be applied to an access control scenario, and in this scenario, differentiated access of network slices may be implemented by the scheme of the present application. The scheme provided by the embodiment of the application can also be applied to a scene of resource scheduling control after the terminal equipment is accessed into the network, and under the scene, the scheme of the application can realize the differentiated scheduling of network slices and the differentiated bandwidth configuration.

For better understanding of the embodiments of the present application, specific implementations of the schemes provided by the embodiments of the present application in an access control scenario and a scheduling control scenario are specifically described below with reference to fig. 3 to fig. 7.

For convenience of understanding and description, in the following embodiments, an access control policy parameter is taken as an access category priority, and a scheduling control policy parameter is taken as a scheduling priority.

(1) And accessing a control scene.

The process of accessing the network by the terminal device is roughly as follows: the method comprises the steps that terminal equipment acquires access control parameters from access network equipment (RAN); then, the network is accessed according to the access control parameters.

For example, access control parameters include, but are not limited to: an access barring check indication, a boolean type parameter may be set to allow access or disallow access; it may also be an access barring factor (BarringFactor), a probability indicating access barring, and an access barring time (BarringTime), indicating an average barring time, etc.

In this scenario, the method provided in the embodiment of the present application includes the following steps:

1) the core network device determines an access category of the network slice.

Optionally, the core network device obtains the access category of the network slice through a predefined algorithm.

Specifically, the predefined algorithm determines an access category according to the type of the network slice, signs according to the SLA index requirements signed by the network slice, or sets the access category according to slice parameters configured by the management network element.

Optionally, the core network device obtains the access category of the network slice according to the analysis of the big data algorithm module.

For example, the core network device subscribes to or requests the NWDAF to analyze the access category of the network slice, and the core network device determines the access category of the network slice according to the analysis result fed back by the NWDAF.

2) And the core network equipment determines the access category priority of the network slice according to the access category of the network slice.

Optionally, the core network device determines the access category priority of the network slice through a predefined algorithm.

Specifically, the predefined algorithm determines the access class priority of the network slice according to at least one of the following factors: the type of the network slice, SLA index requirements signed by the network slice, and slice parameters configured by the management network element for the network slice.

Optionally, the core network device obtains the access category priority of the network slice according to the analysis of the big data algorithm module.

For example, the core network device subscribes to or requests the NWDAF to analyze the access category priority of the network slice, and the core network device determines the access category priority of the network slice according to the analysis result fed back by the NWDAF.

The access class priorities of the network slices of different access classes are not identical. For example, different access categories correspond to different access category priorities. As another example, two or more access categories correspond to the same priority.

The ease with which users of network slices of different access category priorities access the network varies. For example, a user accessing a network slice with a lower priority of the category prohibits access to the network slice, and a user accessing a network slice with a higher priority of the category grants access to the network slice. As another example, users of a network slice with a higher access category priority have priority access to the network slice over users of a network slice with a higher access category priority.

3) The core network device informs the access network device of the access class priority of the network slice.

4) And the access network equipment generates the access control parameters of the network slice according to the access category priority of the network slice.

The access network device broadcasts the access control parameter of the network slice to the terminal device, so that the terminal device can perform the process of accessing the network according to the access control parameter.

In this scenario, it is necessary to configure the access category of the network slice to the terminal device having the subscription relationship with the network slice in advance.

Optionally, the access class of the network slice is statically configured to the terminal device.

Optionally, the access class of the network slice is dynamically configured to the terminal device.

In particular, fig. 3 is a schematic diagram of dynamically configuring access types of network slices to a terminal device. In fig. 3, the core network device is denoted as SCF, the access network device is denoted as RAN, and the terminal device is denoted as UE. As shown in fig. 3, the method includes the following flow.

S301, the SCF determines the access category of the network slice.

Optionally, the SCF obtains the access category of the network slice by a predefined algorithm.

Optionally, the SCF obtains the access category of the network slice according to the analysis of the big data algorithm module.

As shown in fig. 3, the SCF subscribes to or requests to analyze the access category of the network slice from the NWDAF, and the SCF determines the access category of the network slice according to the analysis result fed back by the NWDAF.

For example, the NWDAF may directly feed back the access category of the specified slice, or feed back indication that the specified slice needs to increase or decrease the access priority.

S302, the SCF sends the access type of the network slice to the UE through the AMF.

Firstly, the AMF acquires the access type of the network slice from the SCF, and then the AMF sends the access type of the network slice to the UE which establishes a subscription relationship with the network slice.

Optionally, as an implementation, the AMF subscribes to a network slice access category (slice access category) configuration from the SCF. If the access type of a network slice is changed, the SCF informs the AMF of the new access type of the network slice.

In this implementation manner, the AMF may send the access category of the network slice acquired from the SCF to the UE in various manners.

For example, the AMF notifies the UE of the access category of the network slice through a configuration update (UE configuration update) procedure of the UE.

For another example, the AMF sends the access category of the network slice to the UE during the next registration (registration) or registration update (registration update) process of the UE. For example, after receiving a registration request message sent by the UE, the access category of the network slice is carried in a registration response message.

It should be understood that for an access category of a network slice, the AMF sends the access category of the network slice to the UE that has established a subscription relationship with the network slice. It should also be understood that, while the access category of the network slice is sent to the UE, the identity of the network slice, i.e., the information used in the system to uniquely identify the network slice, is also sent.

The first implementation described above is applicable to scenarios where the SCF is a newly defined network function, or the SCF is NSSF, NWDA, or.

Optionally, as a second implementation manner, the AMF does not actively acquire the access category of the network slice from the SCF, and in a process of registration (registration) or registration update (registration update) of the UE, when the AMF is to reply a registration response (registration accept) message to the UE, the AMF accesses the SCF first, and in a process of accessing the SCF, acquires an access category corresponding to the network slice that the UE is allowed to access, and then the AMF sends a registration response (registration accept) message to the UE, where the registration response (registration accept) message carries the access category of the network slice acquired from the SCF.

It should be understood that the second implementation is applicable to a scenario where the SCF is a PCF. Since the AMF would have to request the PCF for registration of the policy related to registration through Npcf _ ampolicocontrol get during registration (registration) or registration update (registration update) of the UE, in the second implementation, the access category of the network slice is carried in the registration policy that the PCF replies to the AMF.

Fig. 4 is a schematic flowchart of a communication method applied in an access control scenario according to an embodiment of the present application. In fig. 4, the core network device is denoted as an SCF, the access network device is denoted as an RAN, and the terminal device is denoted as a UE. The method comprises the following steps.

S401, the SCF determines an Access Category (AC) priority of the network slice.

First, the SCF determines the access class of the network slice. Specifically, the access category of the network slice is determined according to the method described above with reference to fig. 3, which is not described herein again.

And the SCF acquires the access category level of the network slice according to the access category of the network slice.

Alternatively, the SCF may obtain the access class priority of the network slice by a predefined algorithm.

For example, the predefined algorithm refers to determining access class priority for a network slice based on at least one of the following factors: the type of the network slice, SLA index requirements signed by the network slice, and slice parameters configured by the management network element for the network slice.

Optionally, the SCF may obtain the access category priority of the network slice from the analysis of the big data algorithm module.

As shown in fig. 4, the SCF subscribes to or requests from the NWDAF to analyze the access category priority of the network slice, and the SCF determines the access category priority of the network slice according to the analysis results provided by the NWDAF.

In particular, the SCF network may determine the access class priority of a network slice based on the real-time status of the network slice.

For example, when the load of a network slice is full or close to the full load, the SCF decreases the access category priority corresponding to the network slice, thereby causing the increase rate of the number of users accessing the network slice to decrease.

For another example, when a network slice has a temporary event in a certain geographic area, needs a large flow or faces a large number of users to access, the SCF may temporarily increase the priority of the access category corresponding to the network slice in the geographic area.

Optionally, in some embodiments, the access category priority of the network slice comprises two priorities: high priority and low priority, wherein high priority indicates access is allowed and low priority indicates access is forbidden.

Optionally, in some embodiments, the access category priorities of the network slices include N priorities, the priorities being in order of priority 1 > priority 2 > … > priority N-1 > priority N, N being a positive integer.

For example, a user accessing a network slice with a priority of 1 for the category of access may more easily access the network than a user accessing a network slice with a priority of 2 for the category of access. E.g., a smaller access barring factor, a shorter access barring time.

S402, the SCF sends the access category priority of the network slice to the AMF.

The SCF sends a configuration message to the AMF, where the configuration message is used to indicate the access category priority of the network slice determined in S401, and the configuration message includes the slice identifier of the network slice and the access category priority of the network slice.

For example, the slice of the network slice is identified as S-NSSAI or NSI.

Optionally, the configuration message may further include information related to configuration of an access category of the network slice, such as a priority of the access category, an access category ID, a slice identifier corresponding to the access category, a corresponding access request type, or a combination of one or more of the above parameters, such as a corresponding DN name, a QoS, an App ID, and the like.

Optionally, the configuration message may further include a Tracking Area list (TA list) corresponding to the Network slice, and a Public Land Mobile Network (PLMN) ID corresponding to the Network slice.

Optionally, in some embodiments, if the access category priority of one network slice X is changed, the SCF sends a configuration message to the AMF, where the configuration message indicates the access category priority of the network slice X after updating, and the configuration message carries a slice identifier (slice ID) of the network slice X and the access category priority of the network slice X.

For example, the slice of the network slice X is identified as S-NSSAI or NSI. Optionally, the configuration message may further include information related to the access category configuration of the network slice X. Optionally, the configuration message may further include a TA list corresponding to the network slice X and a PLMN ID corresponding to the network slice X.

Optionally, in some embodiments, the AMF may subscribe to a network slice access class priority (slice access priority) event with the SCF. In this way, the SCF will inform the AMF of the access class priority of the network slice in real time. For example, after determining the access category priority of a network slice for the first time, or after changing the access category priority of a network slice, the SCF sends the latest access category priority of the network slice to the AMF.

The AMF sends the access category priority of the network slice to the access network equipment (RAN) S403.

Specifically, the AMF sends the access category priority of the network slice to the RAN through an AMF configuration update (AMF configuration update) message, where the AMF configuration update message carries a slice identifier of the network slice and the access category priority of the network slice.

Optionally, the AMF configuration update message may also carry access type configuration related information, and may further include a TA list and a PLMN ID corresponding to the network slice.

Specifically, the AMF network selects a RAN for which an NG interface has been established according to the slice identifier of the network slice, and then sends the AMF configuration update message to the RAN.

The NG interface is an interface for communication between the access network equipment (RAN) and the AMF.

Optionally, in some embodiments, when the AMF intends to send the access category priority of the network slice to the RAN, the RAN has not established an NG interface yet, that is, the AMF cannot communicate with the RAN at this time, in this case, the AMF sends the access category priority of the network slice to the RAN in a subsequent process of establishing the NG interface with the RAN, for example, after receiving an NG setup request (NG setup request) message sent by the RAN, the AMF sends an NG setup response (NG setup response) message to the RAN, where the NG setup response message carries the access category priority of the network slice. Accordingly, the RAN may obtain the access category priority of the network slice by parsing the NG setup response message.

S404, the RAN sets the access control parameter of the network slice according to the access category priority of the network slice.

The RAN configures access control parameters for the network slice based on the access category of the network slice. Correspondingly, the terminal equipment selects a network slice to be accessed, determines the access control parameter of the network slice according to the access category of the network slice, and then accesses the network slice according to the access control parameter.

The RAN broadcasts the access control parameters via a broadcast message (system information). Accordingly, a terminal equipment (UE) receives a broadcast message sent by the RAN. When UE needs to initiate a connection request, according to the access category of the network slice with the established subscription relationship, searching the access control parameter corresponding to the access category from the received access control parameters, and then according to the access control parameter, determining whether to access the network slice and how to access. The process of accessing the network slice by the UE according to the access control parameter is the prior art, and is not described herein again.

Optionally, in some embodiments, the AMF may further reconfigure an access Policy of the UE, such as Network Slice Selection Policy (NSSP), according to an indication of the SCF, indicating that when the UE finds that a Network Slice that needs to be accessed is prohibited from being accessed, another Network Slice, such as a default Network Slice, may be selected for a corresponding application, so as to avoid that the UE is in a state in which the UE cannot perform a service.

It should be understood that, the conventional mobile network broadcasts an access control parameter (access barring configuration) over an air interface, and the terminal device performs access according to the configuration of the access control parameter after receiving the access control parameter. In the prior art, a network side may allow or deny a user access by configuring an access control parameter, so as to avoid network congestion.

According to the scheme provided by the application, the differentiation processing of the network slices can be realized besides the differentiation of the users. Assuming that the load of the network slice X1 is large and the load of the network slice X2 is small, the access category priority of the network slice X1 is set to be low priority, and the access category priority of the network slice X2 is set to be high priority, so that in the process that a terminal accesses a network, fewer users access to the network slice X1 and more users access to the network slice X2 are provided, and thus the service quality of the network slice can be effectively improved.

The network side can perform differentiated control on the number of different network slice access terminal devices by dynamically adjusting the priority corresponding to the access category of the network slice, namely the access category priority of the network slice.

Therefore, in the embodiment, differentiated access control is performed on different network slices, so that the number of users that can be accessed by different network slices is controlled, and the service quality of the network slices can be improved to a certain extent.

The foregoing describes a specific implementation of applying the communication method provided by the embodiment of the present application to a scenario of access control, and the following describes a specific implementation of applying the communication method provided by the embodiment of the present application to a scenario of scheduling control.

(2) And scheduling the control scenario.

The scheduling control scene refers to a scene that the network side schedules uplink and downlink resources for the terminal equipment after the terminal equipment is accessed into the network.

In this embodiment, different network slices are subjected to differentiated scheduling control, so as to influence resource scheduling of the UE currently in a connected state by the different network slices.

The core network equipment determines the scheduling priority of the network slice, and then notifies the access network equipment of the scheduling priority of the network slice in a user plane or control plane mode.

Fig. 5 is a schematic diagram of a method for performing differentiated scheduling control on network slices according to an embodiment of the present application. In fig. 5, the core network device is denoted as SCF, the access network device is denoted as RAN, and the terminal device is denoted as UE. In this embodiment, the core network device notifies the access network device of the scheduling priority of the network slice in a user plane manner. The method comprises the following steps.

S501, the SCF determines the scheduling priority of the network slice.

Optionally, the SCF obtains the scheduling priority between multiple network slices through a predefined algorithm.

Optionally, the SCF obtains scheduling priorities among the multiple network slices according to the analysis of the big data algorithm module.

As shown in fig. 5, the SCF subscribes to or requests to analyze the scheduling priority of the network slice from the NWDAF, and determines the scheduling priority of the network slice according to the analysis result fed back by the NWDAF.

For example, when a Service-Level Agreement (SLA) index of a network slice is low, the scheduling priority of the network slice should be increased, so that a user accessing the network slice can more easily obtain scheduling resources, thereby increasing the SLA of the network slice. And vice versa.

S502, the SCF sends the scheduling priority of the network slice to the SMF.

The SCF may inform the SMF of the scheduling priority of the network slice in two ways.

The first mode is as follows: the SCF informs the SMF network slice of the scheduling priority through the PCF.

For example, the PCF subscribes to a notification message of a scheduling priority change of a network slice on the SCF through a network slice priority subscription (slice priority subscription) interface of the SCF, where the subscription interface may provide an identification (slice ID) of the network slice. Optionally, the subscription interface may further include a TA list and a PLMN ID corresponding to the network slice.

For another example, when the scheduling priority of the network slice subscribed by the PCF needs to be adjusted, the SCF may send a notification message to the PCF, where the notification message carries the adjusted scheduling priority of the network slice and the identifier of the network slice. Optionally, the notification message may also carry a TA list corresponding to the network slice.

After receiving the notification message sent by the SCF, the PCF sends the notification message to the SMF through the Npcf _ SMPolicyControl interface. For example, the notification message notifies the SMF to adjust the priorities that need to be adjusted for sessions corresponding to one or more UEs under the specified TA, such as adjusting corresponding QoS parameters.

It should be understood that a tracking area (TrackingArea) is a concept newly set up by the LTE system for location management of the UE. When the UE is in the idle state, the core network can know the tracking area where the UE is located, and when the UE in the idle state needs to be paged, paging must be performed in all cells of the tracking area where the UE is registered. The TA is a configuration at a cell level, multiple cells may configure the same TA, and one cell may belong to only one TA.

The second mode is as follows: the SCF directly informs the SMF network slice of the scheduling priority.

For example, the SMF subscribes to a notification message of a scheduling priority change of a network slice on the SCF through a network slice priority subscription (slice priority) interface of the SCF, and may provide an identifier (slice ID) of the network slice in the subscription interface. Optionally, the subscription interface may further include a TA list and a PLMN ID corresponding to the network slice.

For another example, when the scheduling priority of the network slice subscribed by the SMF needs to be adjusted, the SCF may send a notification message to the SMF, where the notification message carries the adjusted scheduling priority of the network slice and the identifier of the network slice. Optionally, the notification message may also carry a TA list corresponding to the network slice.

Taking a network slice as an example, when the SCF determines the scheduling priority of the network slice for the first time, or when the SCF adjusts the scheduling priority of the network slice, the SCF sends the scheduling priority of the network slice to the SMF.

S503, the SMF sends a N4 session notification (N4 session modification) message to the UPF, wherein the N4 session modification message carries the scheduling priority of the network slice.

If the SMF directly obtains a notification message (slice priority notification) of the scheduling priority of the network slice from the SCF, it needs to select a designated session of the designated UE under the designated TA, notify the corresponding UPF through the N4 session modification message, and modify the priority of the corresponding session, for example, notify a new QoS parameter, or notify the UPF to improve the QoS. It should be understood that SMF is managed at session (session) granularity for the user. At this time, the session notification message N4 carries QoS parameters that are determined according to the scheduling priority of the network slice. The slice with high priority uses the QoS parameter with high priority.

If the SMF is a notification message for acquiring the scheduling priority of the network slice from the PCF, similar to the PCF triggering PDU session notification in the prior art, the scheduling priority of the network slice is notified to the UPF through N4 session modification according to the instruction.

S504, the UPF sends a message to the RAN, and the message carries the scheduling priority of the network slice.

And the UPF adjusts the scheduling priority of the corresponding session of the corresponding UE according to the N4 session modification message of the SMF.

For example, the downlink data may be notified to the RAN by a 5QI indication in the header of the data packet carrying a high priority QoS. For uplink data, the 5QI change of uplink may be indicated by the 5QI change of downlink according to the reflective QoS mechanism.

And S504, the RAN performs corresponding scheduling on an air interface according to the acquired scheduling priority of the network slice.

For example, the RAN may obtain the corresponding QoS parameter according to the 5QI indication in the data packet header, and perform corresponding scheduling on the air interface according to the corresponding QoS parameter.

Fig. 6 is another schematic diagram of a method for performing differentiated scheduling control on network slices according to an embodiment of the present application. In fig. 6, the core network device is denoted as SCF, the access network device is denoted as RAN, and the terminal device is denoted as UE. In this embodiment, the core network device notifies the access network device of the scheduling priority of the network slice in a control plane manner. The method comprises the following steps.

S601, SCF determines the scheduling priority of the network slice.

S601 is the same as S501, and the description in S501 is not repeated here.

S602, the SCF informs the AMF of the scheduling priority of the network slice.

The SCF may inform the AMF of the scheduling priority of the network slice in two ways.

The first mode is as follows: the SCF informs the AMF of the scheduling priority of the network slice through the PCF.

The PCF may subscribe the notification message of the change of the slice priority on the SCF through the slice priority subscribe interface of the SCF, and the subscribe interface may provide the slice ID, and optionally may further include the corresponding TA list and the corresponding PLMN ID.

When the scheduling priority of the subscribed network slice is adjusted, the SCF sends a notification message to the PCF, wherein the notification message carries the identifier of the network slice and the scheduling priority of the network slice.

Optionally, the notification message further includes a TA list corresponding to the network slice.

And the PCF sends a notification message to the AMF through an Npcf _ AMpolicy _ control interface, wherein the notification message carries the scheduling priority of the network slice. Optionally, the notification message may also carry a TA list corresponding to the network slice.

The second mode is as follows: the SCF directly informs the AMF of the scheduling priority of the network slice.

For example, the AMF subscribes to the Nscf _ AMpolicy _ control notification on the SCF. When the scheduling priority of the subscribed network slice is adjusted, the SCF sends a notification message to the PCF, wherein the notification message carries the identifier of the network slice and the scheduling priority of the network slice. Optionally, the notification message further includes a TA list corresponding to the network slice.

Taking a network slice as an example, after the SCF determines the scheduling priority of the network slice for the first time or adjusts the scheduling priority of the network slice, the SCF sends the scheduling priority for indicating the network slice to the PCF or the AMF.

S603, the AMF sends a message of scheduling priority to the RAN network element.

After receiving the notification message of the scheduling priority of the network slice, the AMF sends an AMF configuration update (AMF configuration update) message through an NG interface with the RAN, where the AMF configuration update message carries the scheduling priority of the network slice.

If slice ID received by AMF is NSI, it needs to be converted into S-NSSAI corresponding to slice. It should be understood that Slice ID has different identification means at different places, and can be represented by NSI or S-NSSAI within the CN, using S-NSSAI between the CN and the RAN.

S604, the RAN performs resource scheduling according to the AMF configuration update message received from the AMF.

The RAN acquires the scheduling priority of the network slice by analyzing the AMF configuration updating message, and then determines a resource scheduling strategy according to the scheduling priority of the network slice and a session (session) QoS parameter of the UE.

For example, when the session QoS parameters are the same, the UE of the network slice with higher scheduling priority is scheduled preferentially.

According to the method and the device, the scheduling priority of the network slice is set, and the scheduling resources are preferentially allocated to the users of the network slice with higher scheduling priority.

It should be understood that by setting the scheduling priority of the network slice, a differentiation process between network slices can be performed for UEs that have access to the network.

The CN may manage SLAs of different slices differently by controlling resource allocation of the RAN to different slices. The CN is not suitable for directly managing the radio spectrum allocation of the RAN, so indirect resource control can be performed by controlling slice-level bandwidth/rate limiting.

Fig. 7 is another schematic diagram of a method for performing differentiated scheduling control on network slices according to an embodiment of the present application. The method comprises the following steps.

S701, the SCF determines bandwidth control strategy parameters of the network slice.

Optionally, the SCF determines the bandwidth control policy parameters of the network slice by a predefined algorithm.

Optionally, the SCF obtains the bandwidth control policy parameters according to the analysis of the big data algorithm module.

As shown in fig. 7, the SCF subscribes to or requests to analyze the bandwidth control policy parameters of the network slice from the NWDAF, and the SCF determines the bandwidth control policy parameters of the network slice according to the analysis result fed back by the NWDAF.

For example, the bandwidth control policy parameters may be determined according to the following rules: when the SLA of network slice X is low, the network bandwidth of the network slice X may be increased, or the network bandwidth of other network slices may be limited. Such bandwidth control policy parameters can ensure that the network slice X can obtain network resources, so as to improve the SLA of the network slice X.

Specifically, the SCF or NWDAF may determine the bandwidth control policy parameters of the network slice through a bandwidth statistics report of the UPF or the network slice.

S702, SCF sends notification message to AMF, the notification message carries bandwidth control strategy parameter of network slice.

Specifically, the SCF may send the notification message to the AMF in the following two ways.

The first mode is as follows: the SCF sends the notification message to the AMF via the PCF.

The SCF sends the notification message to the PCF, which sends the notification message to the AMF.

The second mode is as follows: the SCF sends the notification message directly to the AMF.

Specifically, the SCF needs to select a corresponding AMF, and specifies a corresponding slice ID through a slice BW change interface notification of the AMF, and optionally may further include a corresponding TA list and a corresponding PLMN ID.

Taking a network slice as an example, after the SCF determines the bandwidth control policy parameter of the network slice for the first time or adjusts the bandwidth control policy parameter of the network slice, the SCF sends a notification message for indicating the bandwidth control policy parameter of the network slice to the PCF or the AMF.

S703, the AMF sends the bandwidth control policy parameters of the network slice to the RAN.

When receiving the message sent by the PCF or SCF, the AMF determines the corresponding RAN according to the slice ID carried in the message, optionally including the corresponding TA list, and then sends the bandwidth control policy parameter of the network slice to the RAN.

Optionally, the bandwidth control policy parameters of the network slice are sent to the RAN by an AMF configuration update (AMF configuration update) message.

Optionally, the bandwidth control policy parameters of the network slice are sent to the RAN by an over load message.

Specifically, the AMF configuration update message or over load message may carry the total bandwidth available for slice ID (S-NSSAI here), or may be a relative value, such as how much percent of the current bandwidth the bandwidth of slice can be (120% is increased bandwidth usage, 80% is decreased bandwidth usage)

And the RAN allocates bandwidth for the terminal equipment accessing the network slice according to the received bandwidth control strategy parameters of the network slice.

When the RAN allocates bandwidth to the terminal device accessing the network slice, it is ensured that the sum of the bandwidths allocated to all terminal devices under the network slice does not exceed the total bandwidth of the network slice.

The total bandwidth may also be a relative scale value between slices, e.g., expressed as a bandwidth ratio across the base station.

According to the embodiment of the application, the bandwidth control strategy parameters of the network slices are set, and then the network slices are processed according to the bandwidth control strategy parameters of the network slices, so that the differentiated processing of the network slices can be realized, and the improvement of the service quality of the network slices is facilitated.

The communication method provided by the embodiment of the present application is described above, and the communication device provided by the embodiment of the present application is described below.

Fig. 8 is a schematic block diagram of a communication device 800 according to an embodiment of the present application. The communication apparatus 800 includes the following elements.

A processing unit 810, configured to obtain policy parameters of a network slice, where the policy parameters of the network slice include at least one of the following parameters: accessing a control strategy parameter, a scheduling control strategy parameter and a bandwidth control strategy parameter;

a sending unit 820, configured to send the policy parameter of the network slice to the access network device corresponding to the network slice, so that the access network device determines the policy related to the network slice according to the policy parameter of the network slice.

Optionally, in some embodiments, the processing unit 810 is configured to divide all network slices in the system into at least two access categories, and set access category priorities according to the at least two access categories; and acquiring the strategy parameters of the network slice, wherein the strategy parameters of the network slice are the access category priority corresponding to the access category to which the network slice belongs.

Optionally, in some embodiments, the sending unit 820 is further configured to notify a terminal device of the access category of the network slice, where the terminal device is a terminal device that establishes a subscription relationship with the network slice.

Optionally, in some embodiments, the policy parameter of the network slice is an allowed access control parameter or a forbidden access control parameter.

Optionally, in some embodiments, the sending unit 820 is configured to send the policy parameters of the network slice to the access network device through an access and mobility management function AMF.

Optionally, in some embodiments, the sending unit 820 is configured to notify the access network device of the policy parameters after the network slice is changed when the policy parameters of the network slice are changed.

Optionally, in some embodiments, the processing unit 810 is configured to obtain the policy parameters of the network slice through a network data analysis function NWDAF.

Optionally, in some embodiments, the sending unit 820 is configured to send a notification message to the access network device, where the notification message carries the policy parameter of the network slice and the slice identifier of the network slice.

Optionally, the communication device 800 further comprises a receiving unit 830, for example for receiving the analysis result from the NWDAF.

It should be understood that the communication apparatus 800 provided according to the embodiment of the present application may correspond to the core network device in the foregoing method embodiment, and the foregoing and other operations and/or functions of each unit in the communication apparatus 800 are respectively for implementing corresponding flows of each method in fig. 2 to fig. 7, and are not described herein again for brevity.

Fig. 9 is a schematic block diagram of another communication device 900 provided in an embodiment of the present application. The communication device 900 comprises a processor 910, a memory 920 and a transceiver 930, wherein the memory 920 is used for storing instructions, the processor 910 is used for reading the instructions stored in the memory 920, and the execution of the instructions stored in the memory 920 causes the processor 910 to perform the actions performed by the processing unit 810 in the above embodiments, and the transceiver 930 is used for performing the actions performed by the transmitting unit 820 in the above embodiments.

Fig. 10 is a schematic block diagram of another communication device 1000 provided in an embodiment of the present application. The communication apparatus 1000 includes the following units.

A receiving unit 1010, configured to receive, from a core network device, policy parameters of a network slice, where the policy parameters of the network slice include at least one of the following parameters: accessing a control strategy parameter, a scheduling control strategy parameter and a bandwidth control strategy parameter;

a processing unit 1020 configured to determine a policy associated with the network slice according to the policy parameter of the network slice.

Optionally, in some embodiments, the policy parameter of the network slice is an access control policy parameter;

the processing unit 1020 is configured to determine the access control parameter of the network slice according to the access control policy parameter of the network slice.

Optionally, in some embodiments, the processing unit 1020 is configured to generate the access control parameter of the network slice according to the access control policy parameter of the network slice;

further comprising: a sending unit 1030, configured to send a broadcast message to a terminal device, where the broadcast message carries an access control parameter of the network slice, and the terminal device establishes a subscription relationship with the network slice.

Optionally, in some embodiments, the policy parameter of the network slice is a scheduling control policy parameter; the processing unit 1020 is configured to determine a policy for scheduling resources for the terminal device accessing the network slice according to the scheduling control policy parameter of the network slice.

Optionally, in some embodiments, the policy parameter of the network slice is the bandwidth control policy parameter; the processing unit 1020 is configured to determine a policy for allocating bandwidth to the terminal device accessing the network slice according to the bandwidth control policy parameter of the network slice.

Optionally, in some embodiments, the receiving unit 1010 is configured to receive the policy parameters of the network slice from the core network device through an access and mobility management function AMF.

Optionally, in some embodiments, the receiving unit 1010 is configured to receive, when the policy parameter of the network slice is changed, the policy parameter after the network slice is changed from the core network device.

Optionally, in some embodiments, the receiving unit 1010 is configured to receive a notification message from the core network device, where the notification message carries the policy parameter of the network slice and the slice identifier of the network slice.

It should be understood that the communication apparatus 1000 provided according to the embodiment of the present application may correspond to the access network device in the foregoing method embodiment, and the foregoing and other operations and/or functions of each unit in the communication apparatus 1000 are respectively for implementing corresponding flows of each method in fig. 2 to fig. 7, and are not described herein again for brevity.

Fig. 11 is a schematic block diagram of another communication device 1100 provided in an embodiment of the present application. The communication apparatus 1100 comprises a processor 1110, a memory 1120 and a transceiver 1130, wherein the memory 1120 is used for storing instructions, the processor 1110 is used for reading the instructions stored in the memory 1120, and the execution of the instructions stored in the memory 1120 causes the processor 1110 to perform the actions performed by the processing unit 1020 in the above embodiments, and causes the transceiver 1130 to perform the actions performed by the receiving unit 1010 and the sending unit 1030 in the above embodiments.

The embodiment of the application also provides a communication device, and the communication device can be terminal equipment or a chip. The communication device may be configured to perform the actions performed by the terminal device in the above-described method embodiments.

When the communication apparatus is a terminal device, fig. 12 shows a schematic structural diagram of a simplified terminal device. For easy understanding and convenience of illustration, in fig. 12, the terminal device is exemplified by a mobile phone. As shown in fig. 12, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used for processing communication protocols and communication data, controlling the terminal equipment, executing software programs, processing data of the software programs and the like. The memory is used primarily for storing software programs and data. The radio frequency circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are used primarily for receiving data input by a user and for outputting data to the user. It should be noted that some kinds of terminal devices may not have input/output devices.

When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs baseband signals to the radio frequency circuit, and the radio frequency circuit performs radio frequency processing on the baseband signals and sends the radio frequency signals to the outside in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data. For ease of illustration, only one memory and processor are shown in FIG. 12. In an actual end device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device, etc. The memory may be provided independently of the processor, or may be integrated with the processor, which is not limited in this embodiment.

In the embodiment of the present application, the antenna and the radio frequency circuit having the transceiving function may be regarded as a transceiving unit of the terminal device, and the processor having the processing function may be regarded as a processing unit of the terminal device. As shown in fig. 12, the terminal apparatus includes a transceiving unit 1201 and a processing unit 1202. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. A processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, or the like. Optionally, a device for implementing a receiving function in the transceiving unit 1201 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiving unit 1201 may be regarded as a transmitting unit, that is, the transceiving unit 1201 includes a receiving unit and a transmitting unit. A transceiver unit may also sometimes be referred to as a transceiver, transceiving circuitry, or the like. A receiving unit may also be referred to as a receiver, a receiving circuit, or the like. A transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

For example, in one implementation manner, the transceiving unit 1201 is configured to perform the receiving operation on the terminal device side in step 302 in fig. 3, and/or the transceiving unit 1201 is further configured to perform other transceiving steps on the terminal device side in the embodiment of the present application.

For another example, in another implementation manner, the transceiving unit 1201 is configured to perform a receiving operation on the terminal device side in S404 in fig. 4, and/or the transceiving unit 1201 is further configured to perform other transceiving steps on the terminal device side in the embodiment of the present application.

When the communication device is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input/output circuit and a communication interface; the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.

An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a computer, causes the computer to implement the method at the core network device side, or the method at the access network device side, or the method at the terminal device side in the above method embodiments.

Embodiments of the present application further provide a computer program product containing instructions, where the instructions, when executed by a computer, cause the computer to implement the method at the core network device side, or the method at the access network device side, or the method at the terminal device side in the foregoing method embodiments.

For the explanation and beneficial effects of the related content in any of the communication apparatuses provided above, reference may be made to the corresponding method embodiments provided above, and details are not repeated here.

It should be understood that the Processor mentioned in the embodiments of the present invention may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory referred to in this embodiment of the invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

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

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

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising:

the method comprises the steps that core network equipment obtains strategy parameters of a network slice, wherein the strategy parameters of the network slice comprise scheduling control strategy parameters and/or bandwidth control strategy parameters;

the core network equipment sends the strategy parameters of the network slice to the access network equipment corresponding to the network slice, so that the access network equipment determines the relevant strategy of the network slice according to the strategy parameters of the network slice;

the network slice related policies include a policy for determining scheduling transmission resources for terminal devices accessing the network slice and/or a policy for allocating network bandwidth for terminal devices accessing the network slice.

2. The method of claim 1, wherein the policy parameters of the network slice further comprise an access control policy parameter, the access control policy parameter being an access category priority;

the core network device obtaining the policy parameters of the network slice includes:

the core network equipment divides all network slices in the system into at least two access categories and sets access category priority according to the at least two access categories;

and the core network equipment acquires the strategy parameters of the network slice, wherein the strategy parameters of the network slice are the access category priority corresponding to the access category to which the network slice belongs.

3. The method of claim 2, further comprising:

and the core network equipment informs terminal equipment of the access type of the network slice, wherein the terminal equipment establishes a subscription relationship with the network slice.

4. The method of claim 1, wherein the policy parameters of the network slice further comprise an access control policy parameter, and wherein the access control policy parameter is an allowed access control parameter or a forbidden access control parameter.

5. The method according to any one of claims 1 to 4, wherein the sending, by the core network device, the policy parameter of the network slice to the access network device corresponding to the network slice includes:

and the core network equipment sends the policy parameters of the network slice to the access network equipment through an access and mobility management function (AMF).

6. The method according to any one of claims 1 to 4, wherein the sending, by the core network device, the policy parameter of the network slice to the access network device corresponding to the network slice includes:

when the policy parameter of the network slice is changed, the core network device notifies the access network device of the policy parameter after the change of the network slice.

7. The method according to any one of claims 1 to 4, wherein the core network device obtains the policy parameters of the network slice, including:

and the core network equipment acquires the strategy parameters of the network slice through a network data analysis function NWDAF.

8. The method according to any one of claims 1 to 4, wherein the sending, by the core network device, the policy parameter of the network slice to the access network device corresponding to the network slice includes:

and the core network equipment sends a notification message to the access network equipment, wherein the notification message carries the strategy parameters of the network slice and the slice identifier of the network slice.

9. A method of communication, comprising:

the access network equipment receives strategy parameters of a network slice from core network equipment, wherein the strategy parameters of the network slice comprise scheduling control strategy parameters and/or bandwidth control strategy parameters;

the access network equipment determines the related strategy of the network slice according to the strategy parameter of the network slice;

10. The method of claim 9, wherein the policy parameters of the network slice further comprise access control policy parameters;

the determining, by the access network device, the relevant policy of the network slice according to the policy parameter of the network slice includes:

and the access network equipment determines the access control parameters of the network slice according to the access control strategy parameters of the network slice.

11. The method of claim 9, wherein the policy parameters of the network slice further comprise an access control policy parameter, and wherein the access control policy parameter is an allowed access control parameter or a forbidden access control parameter.

12. The method of claim 10, further comprising:

the access network equipment generates access control parameters of the network slices according to the access control strategy parameters of the network slices;

and the access network equipment sends a broadcast message to the terminal equipment, wherein the broadcast message carries the access control parameters of the network slice, and the terminal equipment and the network slice establish a subscription relationship.

13. The method of any of claims 9 to 12, wherein the access network device receives the network slice policy parameters from a core network device, comprising:

and the access network equipment receives the policy parameters of the network slice from the core network equipment through an access and mobility management function (AMF).

14. The method of any of claims 9 to 12, wherein the access network device receives the network slice policy parameters from a core network device, comprising:

and when the strategy parameters of the network slice are changed, the access network equipment receives the strategy parameters after the network slice is changed from the core network equipment.

15. The method of any of claims 9 to 12, wherein the access network device receives the network slice policy parameters from a core network device, comprising:

and the access network equipment receives a notification message from the core network equipment, wherein the notification message carries the strategy parameters of the network slice and the slice identifier of the network slice.

16. A communications apparatus comprising a memory to store instructions and a processor to execute the memory-stored instructions, and execution of the instructions stored in the memory causes the processor to:

acquiring strategy parameters of a network slice, wherein the strategy parameters of the network slice comprise scheduling control strategy parameters and/or bandwidth control strategy parameters;

sending the strategy parameters of the network slice to access network equipment corresponding to the network slice so that the access network equipment can determine the relevant strategy of the network slice according to the strategy parameters of the network slice;

17. The apparatus of claim 16, wherein the policy parameters of the network slice further comprise an access control policy parameter, the access control policy parameter being an access category priority;

the processor is specifically configured to: dividing all network slices in the system into at least two access categories, and setting access category priorities according to the at least two access categories; and acquiring the strategy parameters of the network slice, wherein the strategy parameters of the network slice are the access category priority corresponding to the access category to which the network slice belongs.

18. The apparatus of claim 17, wherein the processor is further configured to notify a terminal device of the access category of the network slice, and wherein the terminal device is a terminal device that establishes a subscription relationship with the network slice.

19. The apparatus of claim 16, wherein the policy parameters of the network slice further comprise an access control policy parameter, and wherein the access control policy parameter is an allowed access control parameter or a forbidden access control parameter.

20. The apparatus according to any of claims 16 to 19, wherein the processor is configured to send policy parameters of the network slice to the access network device through an access and mobility management function, AMF.

21. The apparatus of any of claims 16 to 19, wherein the processor is configured to notify the access network device of the policy parameters of the network slice changed when the policy parameters of the network slice are changed.

22. The apparatus of any one of claims 16 to 19, wherein the processor is configured to obtain the policy parameters of the network slice by a network data analysis function, NWDAF.

23. The apparatus of any one of claims 16 to 19, wherein the processor is configured to send a notification message to the access network device, and wherein the notification message carries the policy parameters of the network slice and the slice identifier of the network slice.

24. A communications apparatus comprising a memory to store instructions and a processor to execute the memory-stored instructions, and execution of the instructions stored in the memory causes the processor to:

receiving policy parameters of a network slice from core network equipment, wherein the policy parameters of the network slice comprise scheduling control policy parameters and/or bandwidth control policy parameters;

determining the related strategy of the network slice according to the strategy parameters of the network slice;

25. The apparatus of claim 24, wherein the policy parameters of the network slice further comprise access control policy parameters;

the processor is specifically configured to determine the access control parameter of the network slice according to the access control policy parameter of the network slice.

26. The apparatus of claim 24, wherein the policy parameters of the network slice further comprise an access control policy parameter, and wherein the access control policy parameter is an allowed access control parameter or a forbidden access control parameter.

27. The apparatus of claim 25, wherein the processor is further configured to:

generating access control parameters of the network slices according to the access control strategy parameters of the network slices;

and sending a broadcast message to a terminal device, wherein the broadcast message carries the access control parameters of the network slice, and the terminal device and the network slice establish a subscription relationship.

28. The apparatus according to any of claims 24 to 27, wherein the processor is configured to receive, from the core network device, policy parameters for the network slice via an access and mobility management function, AMF.

29. The apparatus according to any of claims 24 to 27, wherein the processor is configured to receive the network slice changed policy parameters from the core network device when the network slice policy parameters are changed.

30. The apparatus according to any one of claims 24 to 27, wherein the processor is configured to receive a notification message from the core network device, and the notification message carries the policy parameters of the network slice and the slice identifier of the network slice.

31. A computer storage medium, having stored thereon a computer program which, when executed by a computer, causes the computer to perform the method of any one of claims 1 to 8.

32. A computer storage medium, having stored thereon a computer program which, when executed by a computer, causes the computer to perform the method of any one of claims 9 to 15.