CN113225206B

CN113225206B - Communication method and device

Info

Publication number: CN113225206B
Application number: CN202110363703.0A
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: 2024-11-26
Anticipated expiration: 2038-04-13
Also published as: CN110380887B; CN113225206A; CN110380887A; WO2019196796A1

Abstract

The application provides a communication method and a device, wherein the method comprises the following steps: the core network equipment acquires the strategy parameters of the network slice, wherein the strategy parameters of the network slice comprise at least one of the following parameters: access control policy parameters, scheduling control policy parameters, and bandwidth control policy parameters; 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 policies of the network slice according to the policy parameters of the network slice. The application can ensure the service quality of the network slice to a certain extent by setting the strategy parameters of the network slice and determining the related strategy of the network slice according to the strategy parameters of the network slice.

Description

Communication method and device

The application is a divisional application of the application application with the application date of 2018, 4, 13, china application number of 201810333894.4 and application name of 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, different communication services have significant differences in network performance requirements, and the fifth generation mobile communication system (the fifth generation, 5G) introduces the concept of Network Slice (NS) to cope with the difference in network performance requirements of different communication services.

Network slicing refers to a collection of logical network function entities supporting specific communication traffic requirements, and mainly implements services customizable by means of software defined network (software defined network, SDN) technology and network function virtualization (network function virtualization, NFV) technology. One network slice meets the connection communication service requirements of a certain class or use case, and the whole network system consists of a large number of network slices meeting different connection capacities.

Network slices are end-to-end, including radio access networks, transport networks, core networks, and the like. The radio access network, the transport network and the core network are all sliced, so that the network slices of the plurality of parts are connected together to form an integral network slice capable of providing a complete service for the user. The different portions of the network slices are logically isolated and the infrastructure network resources are shared. After the business mode of the operator changes from selling connection to a single user to selling network slices in the vertical industry, the original QoS guarantee needs according to the users are converted into the guarantee according to the Service level agreement (Service-LEVEL AGREEMENT, SLA) requirements for carrying out the slice level, for example, how to guarantee the Service quality of the network slices, how to guarantee the network slices to meet the requirements of clients, how to guarantee the network resources between the network slices to be reasonably configured, and the like.

Currently, 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 priority to the network slices.

In a first aspect, a communication method is provided, the method comprising: the core network equipment acquires the strategy parameters of the network slice, wherein the strategy parameters of the network slice comprise at least one of the following parameters: access control policy parameters, scheduling control policy parameters, and bandwidth control policy parameters; 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 policies of the network slice according to the policy parameters of the network slice.

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

Optionally, the core network device obtains policy parameters 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 a policy parameter of the network slice and a slice identifier of the network slice. Correspondingly, the access network equipment receives the notification message from the core network equipment, and the access network equipment acquires the slice identifier of the network slice and the policy parameters of the network slice by analyzing the notification message. Slice identification of the network slice refers to information that is 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 network slice is processed according to the strategy parameters of the network slice by setting the strategy parameters of the network slice, so that the differentiated processing of the network slice can be realized, and the service quality of the network slice is improved.

With reference to the first aspect, in one possible implementation manner of the first aspect, the priority of the network slice is an access class priority related to an access control policy, wherein a higher access class priority accesses the network with respect to a lower access class priority.

Therefore, in this embodiment, by setting the access class priority of the network slice, and then configuring the access control policy of the network slice according to the access class priority of the network slice, the number of users allowed to access by the network slice can be controlled, and the service quality of the network slice can be ensured 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 class priority; the core network device obtains policy parameters of the network slice, including: 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 equipment acquires the policy parameters of the network slice, wherein the policy parameters of the network slice are access category priorities corresponding to the access categories 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 category of the network slice, and the terminal device is the terminal device establishing a subscription relationship with the network slice.

With reference to the first aspect, in one 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, where a higher scheduling priority prioritizes resource scheduling relative to a lower scheduling priority.

According to the embodiment, the scheduling control strategy parameters of the network slice are set, and then the resource scheduling of the network slice is controlled according to the scheduling control strategy parameters 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, the bandwidth control policy parameters of the network slice are set, so that the bandwidth of the network slice can be flexibly configured, and the service quality of the network slice can be ensured 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, policy parameters of the network slice to an access network device corresponding to the network slice includes: the core network device sends policy parameters of the network slice to the access network device through a user plane or a control plane.

With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by the core network device, policy parameters of the network slice to an access network device corresponding to the network slice includes: the core network device sends 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, policy parameters of the network slice to an access network device corresponding to the network slice includes: when the policy parameters of the network slice are changed, the core network equipment sends the policy parameters after the network slice is changed to the access network equipment.

The embodiment of the application informs the access network equipment when determining the strategy parameters of the network slice for the first time or changing the strategy parameters of the network slice, so that the access network equipment can be conveniently configured according to the strategy parameters of the network slice, and the service quality of the network slice is ensured.

In a second aspect, a communication method is provided, the method comprising: the access network device receives policy parameters of a network slice from the core network device, the policy parameters of the network slice comprising at least one of: access control policy parameters, scheduling control policy parameters, and bandwidth control policy parameters; the access network device determines the relevant strategy of the network slice according to the 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 access control policy parameter; wherein the access network device determines the relevant policy of the network slice according to the policy parameters of the network slice, including: the access network device determines the access control parameters of the network slice according to the access control policy 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 access control parameters of the network slice according to the access control policy parameters of the network slice; the access network device sends a broadcast message to the terminal device, wherein the broadcast message carries access control parameters of the network slice, and the terminal device establishes a subscription relationship with 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 scheduling control policy parameter; wherein the access network device determines the relevant policy of the network slice according to the policy parameters of the network slice, including: and the access network equipment determines a strategy for scheduling resources for the terminal equipment accessing 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, policy parameters and bandwidth control policy parameters of the network slice; wherein the access network device determines the relevant policy of the network slice according to the policy parameters of the network slice, including: the access network device determines a strategy for distributing bandwidth to the terminal device accessing the network slice according to the bandwidth control strategy parameter 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, policy parameters of a network slice from the core network device includes: the access network device receives policy parameters of the network slice from the core network device via 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, policy parameters of a network slice from the core network device includes: when the policy parameters of the network slice are changed, the access network equipment receives the changed policy parameters of the network slice from the core network equipment.

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

In a third aspect, a communication method is provided, the method comprising: the terminal equipment receives the access category of the network slice sent by the core network equipment; the terminal equipment receives access control parameters sent by the 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 the core network; the terminal equipment determines an access control parameter of the network slice from 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 class 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 for performing the method of the first aspect or any of the possible implementation manners of the first aspect. In particular, the communication device may comprise means for performing the method of the first aspect or any of the possible implementations of the first aspect.

In a fifth aspect, there is provided a communication device for performing the method of the second aspect or any of the possible implementations of the second aspect. In particular, the communication device may comprise means for performing the method of the second aspect or any of the possible implementations of the second aspect.

In a sixth aspect, a communication device is provided for performing the method of the third aspect or any of the possible implementations of the third aspect. In particular, the communication device may comprise means for performing the method of the third aspect or any possible implementation of the third aspect.

In a seventh aspect, a communications apparatus is provided, the communications apparatus comprising a memory configured to store instructions and a processor configured to execute the instructions stored in the memory, and execution of the instructions stored in the memory causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.

In an eighth aspect, there is provided a communications device comprising a memory for storing instructions and a processor for executing the instructions stored in the memory, and execution of the instructions stored in the memory causes the processor to perform the method of the second aspect or any one of the possible implementations of the second aspect.

In a ninth aspect, a communications apparatus is provided, the communications apparatus comprising a memory for storing instructions and a processor for executing the instructions stored in the memory, and execution of the instructions stored in the memory causes the processor to perform the method of the third aspect or any one of the possible implementations of the third aspect.

In a tenth aspect, a chip is provided, the chip including a processing module and a communication interface, the processing module being configured to control the communication interface to communicate with the outside, and the processing module being 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 implement the method provided in the first aspect or the second aspect or the 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 in the first aspect or the second aspect or the third aspect.

Drawings

Fig. 1 is a schematic diagram of a system architecture to which an embodiment of the present application is applied.

Fig. 2 is a schematic flow chart 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 according to an embodiment of the present application.

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

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

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

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

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

Fig. 10 is a schematic block diagram of another communication device according to 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 apparatus provided in an embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a system architecture to which an embodiment of the present application is applied. The system architecture includes a terminal device (UE illustrated in fig. 1), an access Network (Radio 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 (handheld), a laptop computer (laptop computer), a cordless phone (cordless phone), a wireless local loop (wireless local loop, WLL) station, a machine type communication (MACHINE TYPE communication, MTC) terminal, or other devices that can access a network. The terminal devices (e.g., UEs in fig. 1) communicate with the access network device (e.g., RAN as illustrated in fig. 1) using some air interface technology.

The access network device (RAN) is mainly responsible for radio resource management, quality of service (quality of service, qoS) management, data compression, encryption, and other functions on the air interface side. The access network device 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, and the like. In systems employing different radio access technologies, the names of base station-capable devices may vary, for example, in fifth generation (5th generation,5G) systems, referred to as gNB; in the LTE system, it is called evolved NodeB (eNB or eNodeB); in the third generation (3rd generation,3G) system, it is called Node B (Node B) or the like.

As shown in fig. 1, the core Network device includes the following Network Functions (NF).

Access and mobility management functions (ACCESS AND mobility management function, AMF).

The AMF is mainly responsible for the signaling processing part, for example: access control, mobility management, attach and detach, gateway selection, etc. In the case where 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 so on.

Session management functions (Session Management Function, SMF).

SMF is responsible for the following functions: user plane network element selection, user plane network element redirection, internet protocol (internet protocol, IP) address assignment, bearer establishment, modification and release, and quality of service (Quality of Service, qoS) control.

Policy control function (policy control function, PCF).

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

Network data analysis Function (Network DATA ANALYTICS Function, NWDAF).

NWDAF mainly support the collection and analysis of big data and provide analysis results for other relevant network elements.

As shown in fig. 1, the system architecture further includes a user plane function (User Plane Function, UPF). The UPF is responsible for forwarding and receiving user data in the terminal device. The UPF may receive user data from a data network (i.e. a core network) and transmit the user data to a terminal device through an access network device; the UPF may also receive user data from the terminal device via the access network device and forward the user data to the data network. The transmission resources and scheduling functions in the UPF that serve the terminal devices are managed and controlled by the SMF.

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

While other Network functions in the core Network are also shown in fig. 1, such as a Network slice selection function (Network Slice Selection Function, NSSF), a Network opening function (Network Exposure Function, NEF), an NF storage function (NF Repository Function, NRF), the same Data management (Unified DATA MANAGEMENT, UDM), an application function (Application Function, AF) and an authentication server function (Authentication Server Function, AUSF), a Data Network (DN) is also shown in fig. 1, it is to be understood that these Network elements are not limiting illustrations of the present embodiment and are merely illustrative.

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

S201, core network equipment acquires policy parameters of a network slice, wherein the policy parameters of the network slice comprise 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 parameters of the network slice, which may indicate that the core network device generates the policy parameters of the network slice, or may indicate that the core network device obtains the policy parameters of the network slice through other devices.

Specifically, the core network device subscribes to NWDAF or requests 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 NWDAF.

For example, the predefined algorithm is to determine policy parameters of the network slice according to the type of the network slice, or determine policy parameters of the network slice according to SLA index requirements signed by the network slice, or determine policy parameters of the network slice according to slice parameters configured by a 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. Wherein the access control policy parameter represents a parameter for controlling the terminal device to access the network; the scheduling control policy parameter represents a parameter for scheduling resources for a terminal device accessing the network; the bandwidth control policy parameter represents a parameter for allocating bandwidth to terminal devices of the access network. For example, the bandwidth control policy parameter indicates a maximum bandwidth allocated for the network slice, and the bandwidth allocated for the terminal device accessing the network slice is less than or equal to the maximum bandwidth allocated for the network slice.

The policy parameters of the 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 class priority of the network slice; the scheduling control policy parameter of the network slice is the scheduling priority of the network slice.

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

S203, the access network equipment determines the relevant strategy of the network slice according to the strategy parameters of the network slice.

When the policy parameter of the network slice is an access control policy parameter, the access network device generates the access control parameter of the network slice according to the access control policy parameter of the network slice.

When the policy parameter of the network slice is a scheduling control policy parameter, the access network device determines a policy for scheduling transmission resources for a terminal device accessing the network slice according to the scheduling control policy parameter of the network slice.

When the policy parameter of the network slice is a bandwidth control policy parameter, the access network device determines a policy for allocating network bandwidth to a terminal device accessing the network slice according to the bandwidth control policy parameter of the network slice.

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

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 than the currently defined network function, for example, such a network function is called a slice control function (slice control function, SCF).

Optionally, when the core network device is a network function other than AMF, S202 specifically includes: the core network device sends the policy parameters of the network slice to the access network device through the AMF. Accordingly, the access network device receives 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 an access control parameter of the network slice according to the access class priority of the network slice. The access network device can send the access control parameters of the network slice to the terminal device through the broadcast message, so that the terminal device can conveniently access the network.

Specifically, the access control policy parameters include, but are not limited to: allowed access, barred access duration, barred access probability, etc. The access prohibition time period indicates a time period from when the access fails to when the next access is performed.

For example, the access class priority includes a high and a low class, where a high priority indicates that access is allowed and a low priority indicates that access is barred. The access control parameters determined by the access network device also indicate that the terminal device can access the network, assuming that the access class priority of the network slice indicates that access is allowed. When the access class priority of the network slice indicates that access is prohibited, the access control parameter determined by the access network device also indicates that the terminal device prohibits access to the network.

As another example, the access class priority includes a plurality of levels, including, for example, priority 1, priority 2, and priority 3, where priority 1 indicates that access is allowed, and a waiting period after failure of access is T1; priority 2 indicates that access is allowed, and the waiting time after failure of access is T2, T2 > T1; priority 3 indicates that access is barred. The priority order is: priority 1 > priority 2 > priority 3. Assuming that the access class priority of the network slice indicates that access is allowed and the waiting time after the access failure is T2, the access control parameter determined by the access network device also indicates that the terminal device accesses the access network according to the policy.

As one implementation, 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, wherein 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 access control allowed parameter or an access control forbidden parameter.

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

It should be appreciated that the core network device may also set access class priorities in units of network slices. The embodiment of the present application is not limited thereto.

In this embodiment, the access network device generates the access control parameter according to the access class priority of the network slice. For example, the access class priorities are in one-to-one correspondence with the access control parameters. The system message broadcast by the access network device to the terminal device may include access control parameters of network slices with multiple access class 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 classes of the network slices. Therefore, in the case of setting the access class priority of the network slice according to the access class of the network slice, it is necessary to notify in advance the access class of the network slice to the terminal device with which the subscription relationship is established.

Optionally, the terminal device is enabled to learn the access category of the network slice in a static configuration mode.

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 operation of static configuration of the access category of the network slice is simpler, the deployment is easier, and the signaling of the current network is not required to be modified.

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

The core network device informs the access category of the network slice to the terminal device through the AMF, and the terminal device is the terminal device establishing a subscription relationship with the network slice.

It should be appreciated that differentiated access control of network slices may be achieved by setting access class priorities of the network slices, and then configuring access control policies of the network slices according to the access class priorities of the network slices.

For example, assuming that a network slice is less loaded, a higher access class priority may be set for the network slice, e.g., allowing the network slice to access more users. When the load of the network slice is full or has approached full load, then the access class priority of the network slice is reduced, e.g., the number of users allowed to access the network slice is reduced or access to the network slice is prohibited. This can guarantee 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 the scheduling control policy parameters 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. Wherein, the higher scheduling priority performs resource scheduling with respect 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 scheduled for users accessing the network slice preferentially, so as to promote the SLA index of the network slice.

In this embodiment, S202 specifically includes: the core network device sends the scheduling control policy parameters of the network slice to the access network device through a user plane or a 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.

According to the 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 for the network slice based on the maximum bandwidth of the network slice. For example, the maximum bandwidth of the network slice will be taken as the bandwidth control policy parameter for the network slice. After receiving the bandwidth control policy parameter of the network slice, the access network device is smaller 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 policy parameters of the network slice to the access network device through a user plane or a control plane.

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

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

Optionally, when changing (or adjusting) the policy parameters of the network slice, the core network device notifies the access network device of the updated policy parameters of the network slice.

For example, when the access class priority for the network slice is downgraded, the core network device informs the access network device of the reduced access class priority for the network slice. 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 network slice is upgraded.

The embodiment of the application informs the access network equipment when determining the priority of the network slice for the first time or changing the strategy parameters of the network slice, so that the access network equipment can be conveniently configured according to the strategy parameters of the network slice, and the service quality of the network slice is ensured.

As can be seen from 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 through 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 to the network, and under the scene, the differential scheduling of the network slices and the differential bandwidth configuration can be realized through the scheme of the application.

In order to better understand the embodiments of the present application, the implementation of the scheme provided by the embodiments of the present application in the access control scenario and the scheduling control scenario is specifically described below with reference to fig. 3 to 7.

For ease of understanding and description, in the following embodiments, access control policy parameters are taken as access class priorities, and scheduling control policy parameters are taken as scheduling priorities as examples.

(1) And accessing a control scene.

The process of accessing the terminal equipment into the network is approximately as follows: the terminal equipment acquires access control parameters from access network equipment (RAN); then, the network is accessed according to the access control parameter.

For example, access control parameters include, but are not limited to: an access barring check indicates that the boolean type parameter may be set to allow access or not allow access; or an access barring factor (barrenfactor), a probability indicating access barring, and an access barring time (barrettime), an average barring time, etc.

In this scenario, the method provided by the embodiment of the application comprises the following steps:

1) The core network device determines an access class 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 is to determine an access category according to the type of the network slice, sign according to the SLA index requirement signed by the network slice, or set 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 NWDAF or requests analysis of 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 NWDAF.

2) The core network device 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 class priority of the network slice by a predefined algorithm.

Specifically, the predefined algorithm is to determine 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 network element for the network slice are managed.

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 NWDAF or requests analysis of access class priorities of the network slices, and the core network device determines the access class priorities of the network slices according to the analysis result fed back by NWDAF.

The access class priorities of the network slices of different access classes are not exactly the same. 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 difficulty level of accessing the network by the users of the network slices with different access category priorities is different. For example, a user accessing a network slice with a lower priority access class may prohibit access to the network slice, and a user accessing a network slice with a higher priority access class may allow access to the network slice. For another example, users accessing network slices with higher access class priorities may access network slices preferentially over users accessing network slices with higher access class priorities.

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 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 parameters of the network slice to the terminal device so that the terminal device can access the network according to the access control parameters.

In this scenario, the access category of a network slice needs to be configured in advance to the terminal device with which the network slice has a subscription relationship.

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.

Specifically, fig. 3 is a schematic diagram of dynamically configuring access types of network slices to terminal devices. 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 procedure.

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

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

Optionally, the SCF obtains an 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 NWDAF or requests analysis of the access categories of the network slices, and determines the access categories of the network slices according to the analysis result fed back by NWDAF.

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

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

First, the AMF acquires an access category of a network slice from the SCF, and then the AMF transmits the access category of the network slice to a UE that 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 with the SCF. If the access type of a network slice changes, the SCF will inform the AMF of the new access class of the network slice.

In this implementation, the AMF may send the access class of the network slice acquired from the SCF to the UE in a number of ways.

For example, the AMF informs 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) of the UE. For example, after receiving a registration request message sent by the UE, the registration response message carries an access category of the network slice.

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

The first implementation described above applies to a scenario 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 obtain the access category of the network slice from the SCF, when the AMF is about to reply a registration response (registration accept) message to the UE in the process of registration (registration) or registration update (registration update) of the UE, accesses the SCF first, obtains the access category corresponding to the network slice that the UE is allowed to access in the process of accessing the SCF, 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 obtained from the SCF.

It should be appreciated that the second implementation is applicable to scenarios where the SCF is a PCF. Because the AMF is inherently required to request registration related policies from the PCF via Npcf _ AMPolicyControl get during registration (registration) or registration update (registration update) of the UE, in the second implementation, the access class of the network slice is carried in the registration policy of the PCF to reply to the AMF.

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

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

First, the SCF determines the access category of the network slice. Specifically, the access category of the network slice is determined according to the method described above in connection with fig. 3, which is not described here 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 through a predefined algorithm.

For example, the predefined algorithm refers to determining access class priority of 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 network element for the network slice are managed.

Alternatively, the SCF may obtain the access class priority of the network slice based on analysis by the big data algorithm module.

As shown in fig. 4, the SCF subscribes or requests from NWDAF to analyze the access class priority of the network slice, and determines the access class priority of the network slice based on the analysis result provided by 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 has approached full load, the SCF decreases the access class priority corresponding to the network slice, thereby decreasing the rate of increase in the number of users accessing the network slice.

For another example, when a network slice has a temporary event occurring in a geographic area, requiring a large amount of traffic or facing a large number of user accesses, the SCF may temporarily increase the access class priority corresponding to the network slice in the geographic area.

Optionally, in some embodiments, the access class priority of the network slice includes two priorities: high priority and low priority, where high priority indicates access is allowed and low priority indicates access is barred.

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

For example, a user accessing a network slice with a class of priority 1 may access the network more easily than a user accessing a network slice with a class of priority 2. Such as smaller access barring coefficients, shorter access barring times.

S402, the SCF sends the AMF an access class priority of the network slice.

The SCF sends a configuration message to the AMF, where the configuration message is used to indicate the access class priority of the network slice determined in S401, and the configuration message includes the slice identifier of the network slice and the access class 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 access category configuration of the network slice, such as priority of the access category, access category ID, slice identifier corresponding to the access category, corresponding access request type, or corresponding DN name, qoS, app ID, or a combination of one or more of the above parameters.

Optionally, the configuration message may further include a tracking area list (TRACKING AREA LIST, TA list) corresponding to the network slice, and a public land mobile network (Public Land Mobile Network, PLMN) ID corresponding to the network slice.

Optionally, in some embodiments, if the access class priority of a network slice X changes, the SCF sends a configuration message to the AMF, where the configuration message indicates the access class priority of the network slice X after updating, and the configuration message carries the slice identifier (slice ID) of the network slice X and the access class 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 about 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 network slice access class priority (SLICE ACCESS category priority) events 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 class priority of a network slice for the first time, or after changing the access class priority of a network slice, the SCF sends the last access class priority of the network slice to the AMF.

S403, the AMF sends the access class priority of the network slice to the access network equipment (RAN).

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

Optionally, the AMF configuration update message may further carry information related to access type configuration, 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 an access network device (RAN) and the AMF.

Optionally, in some embodiments, when the AMF wants to send the access class priority of the network slice to the RAN, the RAN does not yet establish an NG interface, i.e. at this time the AMF cannot communicate with the RAN, in which case the AMF sends the access class priority of the network slice to the RAN in the subsequent process of establishing the NG interface with the RAN, e.g. after receiving an NG interface establishment request (NG setup request) message sent by the RAN, the AMF sends an NG establishment response (NG setup response) message to the RAN, where the NG establishment response message carries the access class priority of the network slice. Accordingly, the RAN may obtain the access class priority of the network slice by parsing the NG setup response message.

S404, the RAN sets access control parameters 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 class of the network slice. Correspondingly, the terminal equipment selects a network slice to be accessed, determines an 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 device (UE) receives the broadcast message sent by the RAN. When the UE needs to initiate a connection request, according to the access category of the network slice with the subscription relation, searching the access control parameter corresponding to the access category from the received access control parameters, and then determining whether to access the network slice and how to access according to the access control parameter. The process of the UE accessing the network slice according to the access control parameter is the prior art, and will not be described in detail herein.

Optionally, in some embodiments, the AMF may reconfigure the access policy of the UE, such as Network Slice Selection Policy (NSSP), according to the indication of the SCF, to indicate that when the UE finds that the network slice requiring access is prohibited from being accessed, another network slice, such as a default network slice, may be selected for the corresponding application, avoiding that the UE is in a state where it is not able to perform service.

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

The scheme provided by the application not only can realize user differentiation, but also can realize differentiation processing of network slices. Assuming that the load of the network slice X1 is larger and the load of the network slice X2 is smaller, 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 fewer users access the network slice X1 and more users access the network slice X2 are enabled in the process of accessing the terminal to the network, and the service quality of the network slice can be effectively improved.

The network side can carry out differential 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, the embodiment controls the number of the users which can be accessed by different network slices by differentially controlling the access of the different network slices, so that the service quality of the network slices can be improved to a certain extent.

The specific implementation of the communication method provided by the embodiment of the present application in the scenario of access control is described above, and the specific implementation of the communication method provided by the embodiment of the present application in the scenario of scheduling control is described below.

(2) Scheduling a controlled scenario.

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

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

The core network device determines the scheduling priority of the network slice, and then notifies the scheduling priority of the network slice to the access network device by means of a user plane or a control plane.

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 informs the access network device of the scheduling priority of the network slice by means of the user plane. The method comprises the following flow.

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

Alternatively, the SCF obtains scheduling priorities among the plurality of network slices through a predefined algorithm.

Alternatively, the SCF obtains scheduling priorities among the plurality of network slices based on the analysis of the big data algorithm module.

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

For example, when a Service-level agreement (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 obtain scheduling resources more easily, thereby improving 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 the following two ways.

The first way is: the SCF informs the SMF network of the scheduling priority of the slice by the PCF.

For example, the PCF subscribes to notification messages of changes in the scheduling priority of the network slice on the SCF via a network slice priority subscription (slice priority subscribe) interface of the SCF, in which an identification (slice ID) of the network slice may be provided. 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 further 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 priority that the session corresponding to one or more UEs under the specified TA needs to be adjusted, such as adjusting the corresponding QoS parameter.

It should be understood that tracking area (tracking area) is a newly established concept of the LTE system for location management of UEs. When the UE is in an 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, a plurality of cells can configure the same TA, and one cell can belong to only one TA.

The second way is: the SCF directly informs the SMF network of the scheduling priority of the slice.

For example, the SMF subscribes to notification messages of changes in the scheduling priority of network slices on the SCF via a network slice priority subscription (slice priority subscribe) interface of the SCF, in which an identification (slice ID) of the network slice may be provided. 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 further 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 after the SCF adjusts the scheduling priority of the network slice, the scheduling priority of the network slice is sent to the SMF.

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

If the SMF is a notification message (slice priority notification) that directly obtains the scheduling priority of the network slice from the SCF, then the designated session of the designated UE under the designated TA needs to be selected, the corresponding UPF is notified via the N4 session modification message, the priority of the corresponding session is modified, for example, a new QoS parameter is notified, or the UPF is notified to promote QoS. It should be appreciated that SMF is managed at the user's session (session) granularity. In this case, the QoS parameter is carried in the N4 session notification message, and the QoS parameter is determined according to the scheduling priority of the network slice. The higher priority slice uses the higher priority QoS parameter.

If the SMF is a notification message that obtains the scheduling priority of the network slice from the PCF, the UPF is notified of the scheduling priority of the network slice by N4 session modification, as indicated by PCF trigger PDU session motification in the prior art.

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

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 inform the RAN by carrying a 5QI indication of the high priority QoS in the header. For uplink data, the uplink 5QI change may be indicated by the downlink 5QI change according to REFLECTIVE QOS mechanism.

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

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

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 SCF, the access network device is denoted RAN, and the terminal device is denoted UE. In this embodiment, the core network device informs the access network device of the scheduling priority of the network slice by means of a control plane. The method comprises the following flow.

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

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

S602, the SCF notifies 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 way is: the SCF informs the AMF of the scheduling priority of the network slice by the PCF.

The PCF may subscribe to the notification message of the change in the slice priority on the SCF through the slice priority subscribe interface of the SCF, and the subscription interface may provide the slice ID, and optionally may further include a corresponding TA list, and a 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 identification 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.

The PCF sends a notification message to the AMF over the Npcf _ AMpolicy _control interface, which carries the scheduling priority of the network slice. Optionally, the notification message may further carry a TA list corresponding to the network slice.

The second way is: the SCF directly informs the AMF of the scheduling priority of the network slice.

For example, the AMF subscribes to Nscf _ AMpolicy _control notifications 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 identification 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 a scheduling priority indicating the network slice to the PCF or 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 the slice ID received by the AMF is NSI, the slice ID needs to be converted into S-NSSAI corresponding to the slice. It should be appreciated that the Slice ID may be identified differently at different locations, and may be indicated within the CN by NSI or S-NSSAI, with S-NSSAI being used 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 update message, and then the RAN determines a resource scheduling strategy according to the scheduling priority of the network slice and the session (session) QoS parameter of the UE.

For example, in the case where session QoS parameters are the same, UEs scheduling network slices with higher priority are scheduled preferentially.

The embodiment of the application realizes that the user of the network slice with higher scheduling priority is preferentially allocated with the scheduling resource by setting the scheduling priority of the network slice.

It should be appreciated that by setting the scheduling priority of the network slices, the differentiation process between the network slices can be performed for UEs that have accessed 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 adapted to directly manage the radio spectrum allocation of the RAN, so indirect resource control can be done by controlling the 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 flow.

S701, the SCF determines bandwidth control policy 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 analysis by the big data algorithm module.

As shown in fig. 7, the SCF subscribes or requests from NWDAF to analyze the bandwidth control policy parameters of the network slice, and determines the bandwidth control policy parameters of the network slice according to the analysis result fed back by 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 that network slice X may be increased or the network bandwidth of other network slices may be limited. Such bandwidth control policy parameters may ensure that network resources are available to the network slice X to improve the SLA of the network slice X.

In particular, the SCF or NWDAF may determine the bandwidth control policy parameters of the network slice through UPF or bandwidth statistics reporting of the network slice.

S702, the SCF sends a notification message to the AMF, wherein the notification message carries the bandwidth control policy parameters of the network slice.

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

The first way is: 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 way is: the SCF sends the notification message directly to the AMF.

Specifically, the SCF needs to select a corresponding AMF, notify through a slice BW change interface of the AMF, specify a corresponding slice ID, 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 parameters of the network slice for the first time or adjusts the bandwidth control policy parameters of the network slice, the SCF sends a notification message to the PCF or AMF for indicating the bandwidth control policy parameters of the network slice.

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

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

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

Optionally, the network slice's bandwidth control policy parameters are sent to the RAN via an over load message.

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

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

The RAN, when allocating bandwidth for the terminal devices accessing the network slice, ensures that the sum of the allocated bandwidths for all the terminal devices under the network slice does not exceed the total bandwidth of the network slice.

The total bandwidth may also be a relative proportional value between slices, as represented by the bandwidth duty cycle across the base station.

According to the embodiment of the application, the network slice is processed according to the bandwidth control strategy parameters of the network slice, so that the differentiated processing of the network slice can be realized, and the service quality of the network slice is improved.

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 will be described below.

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

The processing unit 810 is 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: access control policy parameters, scheduling control policy parameters, and bandwidth control policy parameters;

And the sending unit 820 is configured to send 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 policies of the network slice according to the policy parameters 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 policy parameters of the network slice, wherein the policy parameters of the network slice are access category priorities corresponding to the access categories to which the network slice belongs.

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

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

Optionally, in some embodiments, the sending unit 820 is configured to send 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, when the policy parameter of the network slice is changed, the access network device of the policy parameter after the change of the network slice.

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

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 a policy parameter of the network slice and a 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 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 above method embodiment, and the above and other operations and/or functions of each unit in the communication apparatus 800 are respectively for implementing the corresponding flow of each method in fig. 2 to 7, which are not repeated herein for brevity.

Fig. 9 is a schematic block diagram of another communication apparatus 900 provided in an embodiment of the present application. The communication device 900 includes a processor 910, a memory 920 and a transceiver 930, where the memory 920 is configured to store instructions, the processor 910 is configured to read the instructions stored in the memory 920, and 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 embodiment, and causes the transceiver 930 to perform the actions performed by the transmitting unit 820 in the above embodiment.

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: access control policy parameters, scheduling control policy parameters, and bandwidth control policy parameters;

A processing unit 1020 for determining a relevant policy for the network slice according to the policy parameters 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 parameters of the network slice according to the access control policy parameters of the network slice.

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

further comprises: and the sending unit 1030 is 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 a terminal device accessing the network slice according to the scheduling control policy parameter of the network slice.

Optionally, in some embodiments, the policy parameters and bandwidth control policy parameters of the network slice; the processing unit 1020 is configured to determine a policy for allocating bandwidth to a 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, by way of an access and mobility management function AMF, policy parameters of the network slice from the core network device.

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 change of the network slice 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 above method embodiment, and the above and other operations and/or functions of each unit in the communication apparatus 1000 are respectively for implementing the corresponding flow of each method in fig. 2 to 7, which are not repeated herein for brevity.

Fig. 11 is a schematic block diagram of another communication device 1100 provided by an embodiment of the present application. The communication device 1100 comprises a processor 1110, a memory 1120 and a transceiver 1130, the memory 1120 is configured to store instructions, the processor 1110 is configured to read the instructions stored in the memory 1120, and 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 transmitting unit 1030 in the above embodiments.

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

When the communication apparatus 1200 is a terminal device, fig. 12 shows a simplified schematic structure of the terminal device. For easy understanding and convenient illustration, in fig. 12, a mobile phone is taken as an example of the terminal device. 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 mainly used for storing software programs and data. The radio frequency circuit is mainly used for converting a baseband signal and a radio frequency signal and processing the radio frequency signal. 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 mainly used for receiving data input by a user and outputting data to the user. It should be noted that some kinds of terminal apparatuses may not have an input/output device.

When data need to be sent, the processor carries out baseband processing on the data to be sent and then outputs a baseband signal to the radio frequency circuit, and the radio frequency circuit carries out radio frequency processing on the baseband signal and then sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal equipment, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data. For ease of illustration, only one memory and processor is 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 storage device, etc. The memory may be provided separately from the processor or may be integrated with the processor, as the embodiments of the application are not limited in this respect.

In the embodiment of the application, the antenna and the radio frequency circuit with the receiving and transmitting functions can be regarded as a receiving and transmitting unit of the terminal equipment, and the processor with the processing function can be regarded as a processing unit of the terminal equipment. As shown in fig. 12, the terminal device includes a transceiving unit 1201 and a processing unit 1202. The transceiver unit may also be referred to as a transceiver, transceiver device, etc. The processing unit may also be called a processor, a processing board, a processing module, a processing device, etc. Alternatively, a device for implementing a receiving function in the transceiver unit 1201 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiver unit 1201 may be regarded as a transmitting unit, i.e., the transceiver unit 1201 includes a receiving unit and a transmitting unit. The transceiver unit may also be referred to as a transceiver, transceiver circuitry, or the like. The receiving unit may also be referred to as a receiver, or receiving circuit, among others. The transmitting unit may also sometimes be referred to as a transmitter, or a transmitting circuit, etc.

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

For another implementation, the transceiver unit 1201 is configured to perform the receiving operation at the terminal device side in S404 in fig. 4, and/or the transceiver unit 1202 is also configured to perform other transceiver steps at the terminal device side in the embodiment of the present application.

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

The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, which when executed by a computer causes the computer to implement the method on the core network device side, the method on the access network device side, or the method on the terminal device side in the method embodiment.

The embodiment of the application also provides a computer program product containing instructions, which when executed by a computer, cause the computer to implement the method on the core network device side, the method on the access network device side, or the method on the terminal device side in the method embodiment.

Any explanation and beneficial effects of the related content in any of the communication devices provided above may refer to the corresponding method embodiments provided above, and are not described herein.

It should be appreciated that the Processor referred to in the embodiments of the present invention may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory referred to in embodiments of the present invention may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) is integrated into 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 solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

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

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in 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 this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within 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 related strategy of the network slice according to the strategy parameters of the network slice;

The relevant policies of the network slice include determining policies for scheduling transmission resources for terminal devices accessing the network slice and/or determining policies for allocating network bandwidth for terminal devices accessing the network slice;

Wherein the scheduling control policy parameter represents a parameter for scheduling resources for a terminal device accessing the network slice; the bandwidth control policy parameter represents a parameter for allocating bandwidth to a terminal device accessing the network slice.

2. The method of claim 1, wherein the policy parameters of the network slice further comprise access control policy parameters, the access control policy parameters being access class priorities;

The core network device obtains policy parameters of the network slice, including:

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 access category priority corresponding to the access category to which the network slice belongs.

3. The method according to claim 2, wherein the method further comprises:

the core network device informs the terminal device of the access category of the network slice, and the terminal device is the terminal device establishing a subscription relationship with the network slice.

4. The method of claim 1, wherein the policy parameters of the network slice further comprise access control policy parameters, the access control policy parameters being allowed access control parameters or forbidden access control parameters.

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

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.

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

When the policy parameters of the network slice are changed, the core network equipment informs the access network equipment of the policy parameters after the network slice is changed.

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

The core network device obtains the policy 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 core network device sending policy parameters of the network slice to an access network device corresponding to the network slice, comprises:

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 the 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 relevant strategy of the network slice according to the strategy parameters 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 access network device determines the relevant strategy of the network slice according to the strategy parameters 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 policy parameters of the network slice.

11. The method of claim 9, wherein the policy parameters of the network slice further comprise access control policy parameters, the access control policy parameters being allowed access control parameters or forbidden access control parameters.

12. The method according to claim 10, wherein the method further comprises:

the access network equipment generates access control parameters of the network slice according to the access control policy parameters of the network slice;

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

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

The access network device receives policy parameters of the network slice from the core network device through an access and mobility management function AMF.

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

when the policy parameters of the network slice are changed, the access network equipment receives the changed policy parameters of the network slice from the core network equipment.

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

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

16. A communication device comprising a processor; the processor is configured to read and run a program from a memory to implement the method of any of claims 1-8.

17. A communication device comprising a processor; the processor is configured to read and run a program from a memory to implement the method of any of claims 9-15.

18. A chip, characterized in that it comprises a processing module and a communication interface, the processing module being adapted to control the communication interface to communicate with the outside, the processing module being further adapted to implement the method of any of claims 1 to 15.

19. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a computer, causes the computer to implement the method of any of claims 1 to 15.

20. A computer program product comprising instructions which, when executed by a computer, cause the computer to carry out the method of any one of claims 1 to 15.