Communication method and device

By setting network slicing policy parameters between core network equipment and access network equipment, the problem of network slicing service quality assurance is solved, differentiated processing is achieved, and the service quality of network slicing is improved.

CN113225206BActive Publication Date: 2024-11-26HUAWEI TECH CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202110363703.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-04-13
Publication Date
2024-11-26
Estimated Expiration
2038-04-13

AI Technical Summary

Technical Problem

Existing technologies lack effective network slicing protection schemes, making it impossible to ensure the differentiated network performance requirements of different communication services.

Method used

By setting network slicing policy parameters, including access control policies, scheduling control policies, and bandwidth control policies, between core network equipment and access network equipment, differentiated processing of network slices can be achieved to ensure service quality.

Benefits of technology

It improves the service quality of network slicing by controlling the number of access users, scheduling resources and bandwidth configuration through differentiated processing to meet the needs of different communication services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113225206B_ABST
    Figure CN113225206B_ABST
Patent Text Reader

Abstract

The present application provides a communication method and device, the method comprising: a core network device obtains a policy parameter of a network slice, the policy parameter of the network slice comprising at least one of the following parameters: an access control policy parameter, a scheduling control policy parameter, and a bandwidth control policy parameter; the core network device sends the policy parameter of the network slice to an access network device corresponding to the network slice, so that the access network device determines the relevant policy of the network slice according to the policy parameter of the network slice. The present application can guarantee the service quality of the network slice to a certain extent by setting the policy parameter of the network slice and determining the relevant policy of the network slice according to the policy parameter of the network slice.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention application with the application date of April 13, 2018, the Chinese application number 201810333894.4, and the application name “Communication Method and Device”. Technical Field

[0002] The present application relates to the field of communications, and in particular, to a communication method and device. Background Art

[0003] With the continuous emergence of various communication services, different communication services have significantly different requirements for network performance. The fifth generation mobile communication system (5G) introduces the concept of network slicing (NS) to cope with the differences in the requirements of different communication services for network performance.

[0004] A network slice is a collection of logical network function entities that support specific communication service requirements. It mainly uses software defined network (SDN) technology and network function virtualization (NFV) technology to realize customizable communication services. A network slice meets the connection communication service requirements of a certain class or use case. The entire network system is composed of a large number of network slices that meet different connection capabilities.

[0005] Network slicing is end-to-end, including wireless access networks, transmission networks, and core networks. The wireless access network, transmission network, and core network are all sliced, so multiple network slices are connected together to form a whole network slice that can provide users with a complete service. Different parts of the network slices are logically isolated, and the infrastructure network resources are shared. When the operator's business model shifts from selling connections to individual users to selling network slices to vertical industries, the original QoS guarantee based on users needs to be converted to slice-level guarantee based on service-level agreement (SLA) requirements. For example, how to ensure the service quality of network slices, how to ensure that network slices meet customer needs, and how to ensure the reasonable allocation of network resources between network slices.

[0006] Currently, there is no security solution for network slicing. Summary of the invention

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

[0008] In a first aspect, a communication method is provided, the method comprising: a core network device obtains policy parameters of a network slice, the policy parameters of the network slice comprising at least one of the following parameters: an access control policy parameter, a scheduling control policy parameter, and a bandwidth control policy parameter; the core network device sends the policy parameters of the network slice to an access network device corresponding to the network slice, so that the access network device determines relevant policies of the network slice according to the policy parameters of the network slice.

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

[0010] Optionally, the core network device obtains policy parameters of the network slice according to a predefined algorithm.

[0011] Specifically, the core network device sends a notification message to the access network device, and the notification message carries the policy parameters of the network slice and the slice identifier of the network slice. Correspondingly, the access network device receives the notification message from the core network device, and the access network device obtains the slice identifier of the network slice and the policy parameters of the network slice by parsing the notification message. The slice identifier of the network slice refers to information that can uniquely identify the network slice. The access network device can identify the network slice based on the slice identifier.

[0012] The embodiment of the present application can achieve differentiated processing of network slices by setting policy parameters of network slices and then processing network slices according to the policy parameters of network slices, which is beneficial to improving the service quality of network slices.

[0013] In combination with the first aspect, in a possible implementation of the first aspect, the priority of the network slice is an access category priority related to an access control policy, wherein a higher access category priority takes precedence over a lower access category priority in accessing the network.

[0014] Therefore, this embodiment sets the access category priority of the network slice, and then configures the access control policy of the network slice according to the access category priority of the network slice, so as to control the number of users allowed to access the network slice, and can ensure the service quality of the network slice to a certain extent.

[0015] In combination with the first aspect, in a possible implementation of the first aspect, the policy parameter of the network slice is an access category priority; the core network device obtains the policy parameter of the network slice, including: the core network device divides all network slices in the system into at least two access categories, and sets the access category priority according to the at least two access categories; the core network device obtains the policy parameter of the network slice, and the policy parameter of the network slice is the access category priority corresponding to the access category to which the network slice belongs.

[0016] In combination with the first aspect, in a possible implementation of the first aspect, the method also includes: the core network device notifies the terminal device of the access category of the network slice, and the terminal device is a terminal device that has established a contractual relationship with the network slice.

[0017] In combination with the first aspect, in a possible implementation of the first aspect, the policy parameter of the network slice is an access control parameter allowed or an access control parameter prohibited.

[0018] In combination with the first aspect, in a possible implementation of the first aspect, the method also includes: the core network device notifies the terminal device of the access category of the network slice, and the terminal device is a terminal device that has established a contractual relationship with the network slice.

[0019] Optionally, the policy parameter of the network slice is a scheduling control policy parameter. For example, the scheduling control policy parameter is a scheduling priority, wherein a higher scheduling priority is prioritized over a lower scheduling priority for resource scheduling.

[0020] This embodiment sets the scheduling control policy parameters of the network slice, and then controls the resource scheduling of the network slice according to the scheduling control policy parameters of the network slice, which can ensure the service quality of the network slice to a certain extent.

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

[0022] Therefore, this embodiment can flexibly configure the bandwidth size of the network slice by setting the bandwidth control policy parameters of the network slice, and can ensure the service quality of the network slice to a certain extent.

[0023] In combination with the first aspect, in a possible implementation of the first aspect, the core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, including: the core network device sends the policy parameters of the network slice to the access network device through the user plane or the control plane.

[0024] In combination with the first aspect, in a possible implementation of the first aspect, the core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, including: the core network device sends the policy parameters of the network slice to the access network device through the access and mobility management function AMF.

[0025] In combination with the first aspect, in a possible implementation of the first aspect, the core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, including: when the policy parameters of the network slice change, the core network device sends the changed policy parameters of the network slice to the access network device.

[0026] When the policy parameters of a network slice are determined for the first time or when the policy parameters of a network slice are changed, the embodiment of the present application will notify the access network device so that the access network device can be configured according to the policy parameters of the network slice to ensure the service quality of the network slice.

[0027] According to a second aspect, a communication method is provided, which includes: an access network device receives policy parameters of a network slice from a core network device, the policy parameters of the network slice including at least one of the following parameters: an access control policy parameter, a scheduling control policy parameter, and a bandwidth control policy parameter; and the access network device determines relevant policies of the network slice according to the policy parameters of the network slice.

[0028] In combination with the second aspect, in a possible implementation method of the second aspect, the policy parameters of the network slice are access control policy parameters; wherein, the access network device determines the relevant policies 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.

[0029] In combination with the second aspect, in a possible implementation of the second aspect, the policy parameter of the network slice is an access control parameter allowed or an access control parameter prohibited.

[0030] In combination with the second aspect, in a possible implementation manner of the second aspect, the method also includes: the access network device generates an access control parameter 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, the broadcast message carries the access control parameter of the network slice, and the terminal device establishes a contractual relationship with the network slice.

[0031] In combination with the second aspect, in a possible implementation method of the second aspect, the policy parameters of the network slice are scheduling control policy parameters; wherein, the access network device determines the relevant policies of the network slice according to the policy parameters of the network slice, including: the access network device determines the strategy for scheduling resources for terminal devices accessing the network slice according to the scheduling control policy parameters of the network slice.

[0032] In combination with the second aspect, in a possible implementation method of the second aspect, the policy parameters of the network slice and the bandwidth control policy parameters; wherein, the access network device determines the relevant policies of the network slice according to the policy parameters of the network slice, including: the access network device determines the strategy for allocating bandwidth to the terminal device accessing the network slice according to the bandwidth control policy parameters of the network slice.

[0033] In combination with the second aspect, in a possible implementation of the second aspect, the access network device receives the policy parameters of the network slice from the core network device, including: the access network device receives the policy parameters of the network slice from the core network device through the access and mobility management function AMF.

[0034] In combination with the second aspect, in a possible implementation of the second aspect, the access network device receives the policy parameters of the network slice from the core network device, including: when the policy parameters of the network slice change, the access network device receives the changed policy parameters of the network slice from the core network device.

[0035] In combination with the second aspect, in a possible implementation of the second aspect, the access network device receives policy parameters of a network slice from a core network device, including: the access network device receives a notification message from the core network device, and the notification message carries the policy parameters of the network slice and a slice identifier of the network slice.

[0036] According to a third aspect, a communication method is provided, which includes: a terminal device receiving an access category of a network slice sent by a core network device; a terminal device receiving an access control parameter sent by an access network device, the access control parameter including an access control parameter of the network slice determined according to an access control policy parameter of the network slice sent by the core network; the terminal device determines the access control parameter of the network slice from the parameters received from the access network device according to the access type of the network slice; and the terminal device performs an access process of the network slice according to the access control parameter of the network slice.

[0037] In combination with the third aspect, in a possible implementation of the third aspect, the access control policy parameter of the network slice is the access category priority of the network slice.

[0038] In combination with the third aspect, in a possible implementation of the third aspect, the access control policy parameters of the network slice are access permission policy parameters or access prohibition policy parameters.

[0039] In a fourth aspect, a communication device is provided, which is used to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the communication device may include a module for executing the method in the first aspect or any possible implementation of the first aspect.

[0040] In a fifth aspect, a communication device is provided, which is used to execute the method in the second aspect or any possible implementation of the second aspect. Specifically, the communication device may include a module for executing the method in the second aspect or any possible implementation of the second aspect.

[0041] In a sixth aspect, a communication device is provided, the communication device being used to execute the method in the third aspect or any possible implementation of the third aspect. Specifically, the communication device may include a module for executing the method in the third aspect or any possible implementation of the third aspect.

[0042] In the seventh aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory causes the processor to execute the method in the first aspect or any possible implementation of the first aspect.

[0043] In an eighth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory causes the processor to execute the method in the second aspect or any possible implementation of the second aspect.

[0044] In a ninth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, and the execution of the instructions stored in the memory causes the processor to execute the method in the third aspect or any possible implementation of the third aspect.

[0045] In the tenth aspect, a chip is provided, comprising a processing module and a communication interface, wherein the processing module is used to control the communication interface to communicate with the outside, and the processing module is also used to implement the method provided in the first aspect, the second aspect or the third aspect.

[0046] In the eleventh aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a computer, the computer implements the method provided in the first aspect, the second aspect, or the third aspect.

[0047] In a twelfth aspect, a computer program product comprising instructions is provided, and when the instructions are executed by a computer, the computer implements the method provided in the first aspect, the second aspect, or the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 A schematic diagram of the system architecture used in the embodiments of the present application.

[0049] Figure 2 A schematic flowchart of a communication method provided in an embodiment of the present application.

[0050] Figure 3Another schematic flowchart of the communication method provided in an embodiment of the present application.

[0051] Figure 4 Another schematic flowchart of the communication method provided in an embodiment of the present application.

[0052] Figure 5 Another schematic flowchart of the communication method provided in an embodiment of the present application.

[0053] Figure 6 Another schematic flowchart of the communication method provided in an embodiment of the present application.

[0054] Figure 7 Another schematic flowchart of the communication method provided in an embodiment of the present application.

[0055] Figure 8 A schematic block diagram of a communication device provided in an embodiment of the present application.

[0056] Fig. 9 A schematic block diagram of another communication device provided in an embodiment of the present application.

[0057] Fig.10 A schematic block diagram of another communication device provided in an embodiment of the present application.

[0058] Fig.11 Another schematic block diagram of another communication device provided in an embodiment of the present application.

[0059] Fig.12 A schematic block diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0061] Figure 1 Schematic diagram of the system architecture used in the embodiment of the present application. The system architecture includes a terminal device ( Figure 1 UE shown in the figure), access network (Radio Access Network, RAN) equipment ( Figure 1 RAN) and core network (CoreNetwork, CN) equipment shown in the figure.

[0062] The terminal device may be a user equipment (UE), a handheld terminal, a laptop computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA), a tablet computer, a wireless modem, a handheld device, a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal or other device that can access the network. Figure 1 UE in the network) and access network equipment ( Figure 1 The RANs (shown in the figure) communicate with each other using a certain air interface technology.

[0063] The access network equipment (RAN) is mainly responsible for the wireless resource management, quality of service (QoS) management, data compression and encryption functions on the air interface side. The access network equipment may include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, access points, etc. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in the fifth generation (5G) system, it is called gNB; in the LTE system, it is called evolved NodeB (eNB or eNodeB); in the third generation (3G) system, it is called NodeB, etc.

[0064] like Figure 1 As shown, the core network equipment includes the following network functions (NF).

[0065] Access and mobility management function (AMF).

[0066] AMF is mainly responsible for signaling processing, such as access control, mobility management, attachment and detachment, and gateway selection. When AMF provides services for a session in a terminal device, AMF will provide control plane storage resources for the session, store the session identifier, and the SMF identifier associated with the session identifier.

[0067] Session Management Function (SMF).

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

[0069] Policy control function (PCF).

[0070] PCF mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is responsible for obtaining user contract information related to policy decisions.

[0071] Network Data Analytics Function (NWDAF).

[0072] NWDAF mainly supports the collection and analysis of big data and provides analysis results to other related network elements.

[0073] like Figure 1 As shown in the figure, the system architecture also includes a user plane function (UPF). UPF is responsible for forwarding and receiving user data in terminal devices. UPF can receive user data from the data network (i.e., core network) and transmit it to the terminal device through the access network device; UPF can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions in UPF that provide services to terminal devices are managed and controlled by SMF.

[0074] like Figure 1 As shown, the various network functions in the core network are connected to each other. Among them, AMF can also be connected to the terminal equipment (UE) and the access network equipment (RAN) respectively; SMF can also be connected to the UPF.

[0075] Although Figure 1Other network functions in the core network are also shown, such as Network Slice Selection Function (NSSF), Network Exposure Function (NEF), NF Repository Function (NRF), Unified Data Management (UDM), Application Function (AF) and Authentication Server Function (AUSF). Figure 1 A data network (DN) is also shown, but it can be understood that these network elements do not constitute a restrictive description of this embodiment and are only illustrative.

[0076] Figure 2 A schematic flow chart of a communication method provided in an embodiment of the present application. The method includes the following process.

[0077] S201, the core network device obtains the policy parameters of the network slice, and 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.

[0078] The core network device obtains the policy parameters of the network slice, which can mean that the core network device generates the policy parameters of the network slice, or it can mean that the core network device obtains the policy parameters of the network slice through other devices.

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

[0080] Specifically, the core network device subscribes to or requests NWDAF to analyze the policy parameters of the network slice, and the core network device determines the policy parameters of the network slice based on the analysis results fed back by NWDAF.

[0081] Optionally, the core network device obtains policy parameters of the network slice according to a predefined algorithm.

[0082] For example, the predefined algorithm determines the policy parameters of the network slice according to the type of network slice, or determines the policy parameters of the network slice according to the SLA indicator requirements signed by the network slice, or determines the policy parameters of the network slice according to the slice parameters configured by the management network element for the network slice.

[0083] 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. Among them, the access control policy parameters represent parameters used to control the access of terminal devices to the network; the scheduling control policy parameters represent parameters used to schedule resources for terminal devices accessing the network; and the bandwidth control policy parameters represent parameters used to allocate bandwidth to terminal devices accessing the network. For example, if the bandwidth control policy parameter indicates the maximum bandwidth allocated to the network slice, the bandwidth allocated to the terminal device accessing the network slice must be less than or equal to the maximum bandwidth allocated by the network slice.

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

[0085] S202, the core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice. Correspondingly, the access network device receives the policy parameters of the network slice from the core network device.

[0086] Specifically, the core network device sends a notification message to the access network device, and the notification message carries the policy parameters of the network slice and the slice identifier of the network slice. Correspondingly, the access network device receives the notification message from the core network device, and the access network device obtains the slice identifier of the network slice and the policy parameters of the network slice by parsing the notification message. The slice identifier of the network slice refers to information that can uniquely identify the network slice. The access network device can identify the network slice based on the slice identifier.

[0087] S203, the access network device determines the relevant strategy of the network slice according to the policy parameters of the network slice.

[0088] When the policy parameters of the network slice are access control policy parameters, the access network device generates the access control parameters of the network slice according to the access control policy parameters of the network slice.

[0089] When the policy parameters of the network slice are scheduling control policy parameters, the access network device determines the strategy for scheduling transmission resources for the terminal device accessing the network slice according to the scheduling control policy parameters of the network slice.

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

[0091] For ease of understanding and description, this embodiment is described using a network slice as an example, but the embodiments of the present application are not limited to this. All network slices in the network slicing system can be processed by the method provided in the embodiments of the present application.

[0092] The embodiment of the present application can achieve differentiated processing of network slices by setting policy parameters of network slices and then processing network slices according to the policy parameters of network slices, which is beneficial to improving the service quality of network slices.

[0093] It should be noted that the core network device in this embodiment may be a network function (NF) in the core network. Figure 1 NWDA, PCF, NSSF or AMF in the core network. Optionally, the core network device may also be another network function other than the currently defined network functions, for example, such a network function is called a slice control function (SCF).

[0094] 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 AMF. Correspondingly, the access network device receives the policy parameters of the network slice from the core network device through AMF.

[0095] Optionally, in some embodiments, the policy parameter of the network slice is an access control policy parameter, specifically, an access category priority. Correspondingly, in S203, the access network device determines the access control parameter of the network slice according to the access category priority of the network slice. The access network device may send the access control parameter of the network slice to the terminal device via a broadcast message to facilitate the terminal device to access the network.

[0096] Specifically, the access control policy parameters include but are not limited to: allow access, deny access, deny access duration, deny access probability, etc. The deny access duration indicates the duration from access failure to next access.

[0097] For example, the access category priority includes two levels, high and low, where the high priority indicates that access is allowed and the low priority indicates that access is prohibited. Assuming that the access category priority of the network slice indicates that access is allowed, the access control parameters determined by the access network device also indicate that the terminal device can access the network. When the access category priority of the network slice indicates that access is prohibited, the access control parameters determined by the access network device also indicate that the terminal device is prohibited from accessing the network.

[0098] For another example, the access category priority includes multiple levels, for example, priority 1, priority 2, and priority 3, where priority 1 indicates that access is allowed, and the waiting time after access failure is T1; priority 2 indicates that access is allowed, and the waiting time after access failure is T2, T2>T1; priority 3 indicates that access is prohibited. The priority order is: priority 1>priority 2>priority 3. Assuming that the access category priority of the network slice indicates that access is allowed, and the waiting time after access failure is T2, the access control parameters determined by the access network device also instruct the terminal device to access the access network according to this strategy.

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

[0100] Optionally, the policy parameters of the network slice are access control parameters that allow access control parameters or access control parameters that prohibit access control parameters.

[0101] If there are a large number of network slices in the system, divide all network slices into a smaller number of access categories, and then set the access category priority according to the access category, and configure the access control parameters according to the access category priority. This can reduce the signaling overhead of sending access control parameters to terminal devices.

[0102] It should be understood that the core network device can also set the access category priority in units of network slices. This embodiment of the present application does not limit this.

[0103] In this embodiment, the access network device generates access control parameters according to the access category priority of the network slice. For example, the access category priority corresponds to the access control parameter one by one. The system message broadcast by the access network device to the terminal device may include access control parameters of network slices with multiple access category priorities. The terminal device needs to find the access control parameters of the corresponding network slice from the system message according to the access category of the network slice. Therefore, when setting the access category priority of the network slice according to the access category of the network slice, it is necessary to notify the terminal device of the access category of the network slice in advance, and the terminal device has a contractual relationship with the network slice.

[0104] Optionally, the terminal device is informed of the access category of the network slice through static configuration.

[0105] For example, when a user establishes a contract 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 the storage space of a SIM card or a terminal device. The access category of the network slice is also saved in the corresponding user contract database (such as UDM) on the network side.

[0106] The static configuration of the access category of the network slice is relatively simple and easy to deploy without modifying the signaling of the current network.

[0107] Optionally, the terminal device is informed of the access category of the network slice through dynamic configuration.

[0108] The core network device notifies the terminal device of the access category of the network slice through AMF, and the terminal device is a terminal device that has established a contractual relationship with the network slice.

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

[0110] For example, assuming that a network slice has a small load, a higher access category priority can be set for the network slice, for example, allowing the network slice to access more users. When the network slice is fully loaded or close to fully loaded, the access category priority of the network slice is lowered, for example, the number of users allowed to access the network slice is reduced, or access to the network slice is prohibited. This can ensure the service quality of the network slice.

[0111] Therefore, this embodiment sets the access category priority of the network slice, and then configures the access control policy of the network slice according to the access category priority of the network slice, so as to control the number of users allowed to access the network slice, and can ensure the service quality of the network slice to a certain extent.

[0112] Optionally, in some embodiments, the policy parameters of the network slice are scheduling control policy parameters.

[0113] Specifically, the core network device determines the scheduling control strategy parameters of the network slice based on the SLA indicators of the network slice or the type of the network slice.

[0114] Specifically, the scheduling control strategy parameter is a scheduling priority, wherein a higher scheduling priority is prioritized over a lower scheduling priority in resource scheduling.

[0115] For example, when the SLA indicator of a network slice is low, a higher scheduling priority can be set for it. The scheduling priority indicates that transmission resources are scheduled first for users accessing the network slice, thereby improving the SLA indicator of the network slice.

[0116] 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 the user plane or the control plane. Correspondingly, 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.

[0117] This embodiment sets the scheduling priority of the network slice and then controls the resource scheduling of the network slice according to the scheduling priority of the network slice, which can ensure the service quality of the network slice to a certain extent.

[0118] Optionally, in some embodiments, the policy parameters of the network slice are bandwidth control policy parameters.

[0119] Specifically, the core network device determines the bandwidth control policy parameters of the network slice based on the maximum bandwidth of the network slice. For example, the maximum bandwidth of the network slice is used as the bandwidth control policy parameter of the network slice. After the access network device receives the bandwidth control policy parameter of the network slice, when allocating bandwidth to the terminal device accessing the network slice, it must be less than or equal to the maximum bandwidth.

[0120] 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 the user plane or the control plane.

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

[0122] Therefore, this embodiment can flexibly configure the bandwidth size of the network slice by setting the bandwidth control policy parameters of the network slice, and can ensure the service quality of the network slice to a certain extent.

[0123] Optionally, when the core network device first determines the policy parameters of the network slice, it notifies the access network device of the policy parameters of the network slice.

[0124] Optionally, when the core network device changes (or adjusts) the policy parameters of the network slice, it notifies the access network device of the updated policy parameters of the network slice.

[0125] For example, when the access category priority of the network slice is downgraded, the core network device notifies the access network device of the lowered access category priority of the network slice. For another example, when the access category priority of the network slice is upgraded, the core network device notifies the access network device of the lowered access category priority of the network slice.

[0126] When the priority of a network slice is determined for the first time or the policy parameters of a network slice are changed, the embodiment of the present application will notify the access network device so that the access network device can be configured according to the policy parameters of the network slice to ensure the service quality of the network slice.

[0127] As can be seen from the above, the solution provided by the embodiment of the present application can be applied to the access control scenario. In this scenario, the differentiated access of network slices can be achieved through the solution of the present application. The solution provided by the embodiment of the present application can also be applied to the scenario of resource scheduling control after the terminal device accesses the network. In this scenario, the differentiated scheduling of network slices can be achieved through the solution of the present application, and differentiated bandwidth configuration can also be achieved.

[0128] In order to better understand the embodiments of the present application, Figures 3 to 7 The specific implementation of the solution provided in the embodiments of the present application in the access control scenario and the scheduling control scenario is specifically described.

[0129] For ease of understanding and description, in the following embodiments, the access control policy parameter is taken as an access category priority and the scheduling control policy parameter is taken as an example for description.

[0130] (1) Access control scenario

[0131] The process of a terminal device accessing a network is roughly as follows: the terminal device obtains access control parameters from an access network device (RAN); and then accesses the network according to the access control parameters.

[0132] For example, access control parameters include but are not limited to: access barring check indication, a Boolean type parameter that can be set to allow access or not allow access; it can also be an access barring coefficient (BarringFactor), indicating the probability of access barring, and access barring time (BarringTime), indicating the average barring time, etc.

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

[0134] 1) The core network device determines the access category of the network slice.

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

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

[0137] Optionally, the core network device obtains the access category of the network slice based on the analysis of the big data algorithm module.

[0138] For example, the core network device subscribes to or requests NWDAF to analyze the access category of the network slice, and the core network device determines the access category of the network slice based on the analysis results fed back by NWDAF.

[0139] 2) The core network device determines the access category priority of the network slice according to the access category of the network slice.

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

[0141] Specifically, the predefined algorithm determines the access category priority of the network slice based on at least one of the following factors: the type of network slice, the SLA indicator requirements signed by the network slice, and the slice parameters configured by the management network element for the network slice.

[0142] Optionally, the core network device obtains the access category priority of the network slice based on the analysis of the big data algorithm module.

[0143] For example, the core network device subscribes to or requests NWDAF to analyze the access category priority of the network slice, and the core network device determines the access category priority of the network slice based on the analysis results fed back by NWDAF.

[0144] The access category priorities of network slices of different access categories are not completely the same. For example, different access categories correspond to different access category priorities. For another example, two or more access categories correspond to the same priority.

[0145] Users of network slices with different access category priorities have different degrees of difficulty in accessing the network. For example, users of network slices with lower access category priorities are prohibited from accessing the network slice, while users of network slices with higher access category priorities are allowed to access the network slice. For another example, users of network slices with higher access category priorities have priority in accessing the network slice over users of network slices with higher access category priorities.

[0146] 3) The core network device notifies the access network device of the access category priority of the network slice.

[0147] 4) The access network device generates access control parameters for the network slice based on the access category priority of the network slice.

[0148] The access network device broadcasts the access control parameters of the network slice to the terminal device to facilitate the terminal device to access the network according to the access control parameters.

[0149] In this scenario, the access category of the network slice needs to be pre-configured on the terminal device that has a contractual relationship with the network slice.

[0150] Optionally, the access category of the network slice is statically configured on the terminal device.

[0151] For example, when a user establishes a contract 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 the storage space of a SIM card or a terminal device. The access category of the network slice is also saved in the corresponding user contract database (such as UDM) on the network side.

[0152] The static configuration of the access category of the network slice is relatively simple and easy to deploy without modifying the signaling of the current network.

[0153] Optionally, the access category of the network slice is dynamically configured on the terminal device.

[0154] Specifically, Figure 3 Schematic diagram for dynamically configuring the access type of network slices on terminal devices. Figure 3 In the figure, the core network equipment is denoted as SCF, the access network equipment is denoted as RAN, and the terminal equipment is denoted as UE. Figure 3 As shown, the method includes the following process.

[0155] S301, SCF determines the access category of the network slice.

[0156] Optionally, the SCF obtains the access category of the network slice through a predefined algorithm.

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

[0158] Optionally, the SCF obtains the access category of the network slice based on the analysis of the big data algorithm module.

[0159] like Figure 3 As shown, SCF subscribes to or requests NWDAF to analyze the access category of the network slice, and SCF determines the access category of the network slice based on the analysis results fed back by NWDAF.

[0160] For example, NWDAF can directly feedback the access category of the specified slice, or feedback indication information that the access priority of the specified slice needs to be increased or decreased.

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

[0162] First, AMF obtains the access category of the network slice from SCF, and then AMF sends the access category of the network slice to the UE that has established a contract relationship with the network slice.

[0163] Optionally, as an implementation method, AMF subscribes to the network slice access category configuration from SCF. If the access type of a network slice changes, SCF will notify AMF of the new access category of the network slice.

[0164] In this implementation, the AMF can send the access category of the network slice obtained from the SCF to the UE in a variety of ways.

[0165] For example, AMF notifies the UE of the access category of the network slice through the UE configuration update process.

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

[0167] It should be understood 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 contractual relationship with the network slice. It should also be understood that when the access category of the network slice is sent to the UE, the identifier of the network slice is also sent, that is, the information used to uniquely identify the network slice in the system.

[0168] The first implementation method described above is applicable to the scenario where the SCF is a newly defined network function, or the SCF is NSSF, NWDA, or .

[0169] Optionally, as a second implementation method, AMF does not actively obtain the access category of the network slice from SCF. During the UE registration (registration) or registration update (registration update) process, when AMF is about to reply a registration response (registration accept) message to the UE, it first accesses the SCF. In the process of accessing the SCF, it obtains the access category corresponding to the network slice allowed to access by the UE, and then AMF sends a registration response (registration accept) message to the UE. The registration response (registration accept) message carries the access category of the network slice obtained from the SCF.

[0170] It should be understood that the second implementation is applicable to the scenario where the SCF is the PCF. Because during the UE registration or registration update process, the AMF needs to register the relevant policies to the PCF through the Npcf_AMPolicyControl get request. In the second implementation, the access category of the network slice is carried in the registration policy that the PCF replies to the AMF.

[0171] Figure 4 A schematic flow chart of the communication method provided in the embodiment of the present application applied to the access control scenario. Figure 4 In the method, the core network device is recorded as SCF, the access network device is recorded as RAN, and the terminal device is recorded as UE. The method includes the following process.

[0172] S401, SCF determines the access category (AC) priority of the network slice.

[0173] First, the SCF determines the access category of the network slice. Specifically, according to the above Figure 3 The described method determines the access category of the network slice and will not be repeated here.

[0174] SCF obtains the access category level of the network slice according to the access category of the network slice.

[0175] Optionally, the SCF can obtain the access category priority of the network slice through a predefined algorithm.

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

[0177] Optionally, the SCF can obtain the access category priority of the network slice based on the analysis of the big data algorithm module.

[0178] like Figure 4 As shown, SCF subscribes to or requests analysis of the access category priority of the network slice from NWDAF, and SCF determines the access category priority of the network slice based on the analysis results provided by NWDAF.

[0179] Specifically, the SCF network can determine the access category priority of a network slice based on the real-time status of the network slice.

[0180] For example, when a network slice is fully loaded or close to fully loaded, the SCF lowers the access category priority corresponding to the network slice, thereby reducing the growth rate of the number of users accessing the network slice.

[0181] For another example, when a network slice has a temporary event in a certain geographical area, requiring large traffic or facing a large number of user access, the SCF can temporarily increase the access category priority corresponding to the network slice in the geographical area.

[0182] Optionally, in some embodiments, the access category priority of the network slice includes two priorities: high priority and low priority, wherein the high priority indicates that access is allowed and the low priority indicates that access is prohibited.

[0183] Optionally, in some embodiments, the access category priority of the network slice includes N priorities, and the order of priority is priority 1>priority 2>…>priority N-1>priority N, where N is a positive integer.

[0184] For example, users of a network slice with an access category priority of priority 1 can more easily access the network than users of a network slice with an access category priority of priority 2. For example, a smaller access prohibition coefficient and a shorter access prohibition time.

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

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

[0187] For example, the slice identifier of the network slice is S-NSSAI or NSI.

[0188] Optionally, the configuration message may also include access category configuration-related information of the network slice, such as the priority of the access category, the access category ID, the slice identifier corresponding to the access category, the corresponding access request type, or the corresponding DN name, QoS, App ID, and one or more combinations of the above parameters.

[0189] Optionally, the configuration message may also include a tracking area list (TA list) corresponding to the network slice and a public land mobile network (PLMN) ID corresponding to the network slice.

[0190] Optionally, in some embodiments, if the access category priority of a network slice X changes, the SCF sends a configuration message to the AMF, which indicates the updated access category priority of the network slice X, and the configuration message carries the slice ID of the network slice X and the access category priority of the network slice X.

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

[0192] Optionally, in some embodiments, AMF can subscribe to the network slice access category priority event with SCF. In this way, SCF will notify AMF of the access category priority of the network slice in real time. For example, after the access category priority of a network slice is determined for the first time, or after the access category priority of a network slice changes, SCF sends the latest access category priority of the network slice to AMF.

[0193] S403, AMF sends the access category priority of the network slice to the access network equipment (RAN).

[0194] Specifically, AMF sends the access category priority of the network slice to RAN through an AMF configuration update message. The AMF configuration update message carries the slice identifier of the network slice and the access category priority of the network slice.

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

[0196] Specifically, the AMF network selects the RAN that has established the NG interface according to the slice identifier of the network slice, and then sends the AMF configuration update message to the RAN.

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

[0198] Optionally, in some embodiments, when the AMF wants to send the access category priority of the network slice to the RAN, the RAN has not yet established the NG interface, that is, the AMF cannot communicate with the RAN at this time. In this case, the AMF sends the access category priority of the network slice to the RAN in the subsequent process of establishing the NG interface with the RAN. For example, after receiving the NG interface establishment request (NG setup request) message sent by the RAN, the AMF sends an NG setup response (NG setup response) message to the RAN, and the NG setup response message carries the access category priority of the network slice. Accordingly, the RAN can obtain the access category priority of the network slice by parsing the NG setup response message.

[0199] S404, RAN sets the access control parameters of the network slice according to the access category priority of the network slice.

[0200] RAN configures the access control parameters of the network slice based on the access category of the network slice. Accordingly, the terminal device selects a network slice to access, determines the access control parameters of the network slice according to the access category of the network slice, and then accesses the network slice according to the access control parameters.

[0201] RAN broadcasts the access control parameter through a broadcast message (system information). Accordingly, the terminal device (UE) receives the broadcast message sent by the RAN. When the UE needs to initiate a connection request, it searches for the access control parameter corresponding to the access category from the received access control parameters according to the access category of the network slice for which a contract has been established, and then decides whether to access the network slice and how to access it according to the access control parameter. The process of UE accessing the network slice according to the access control parameter is a prior art and will not be described in detail in this article.

[0202] Optionally, in some embodiments, the AMF may also reconfigure the UE's access policy, such as the Network Slice Selection Policy (NSSP), according to the instructions of the SCF, to indicate that when the UE finds that the network slice it needs to access is prohibited from access, it can select another network slice for the corresponding application, such as the default network slice, to avoid the UE being in a state where it cannot provide service.

[0203] It should be understood that the traditional mobile network broadcasts access control parameters (access barring config) through the air interface, and the terminal device receives and accesses according to the configuration of the access control parameters. In the prior art, the network side can allow or deny user access by configuring the access control parameters to avoid network congestion.

[0204] The solution provided by this application can not only achieve user differentiation, but also achieve differentiated processing of network slices. Assuming that the load of network slice X1 is large and the load of network slice X2 is small, the access category priority of network slice X1 is set to low priority, and the access category priority of network slice X2 is set to high priority, so that during the process of terminal access to the network, fewer users access network slice X1 and more users access network slice X2, which can effectively improve the service quality of network slices.

[0205] The network side can perform differentiated control on the number of terminal devices accessing different network slices by dynamically adjusting the priority corresponding to the access category of the network slice, that is, the access category priority of the network slice.

[0206] Therefore, this embodiment performs differentiated access control on different network slices, thereby controlling the number of users that can access different network slices, thereby improving the service quality of the network slices to a certain extent.

[0207] The above describes the specific implementation of applying the communication method provided in the embodiment of the present application to the scenario of access control. The following describes the specific implementation of applying the communication method provided in the embodiment of the present application to the scenario of scheduling control.

[0208] (2) Scheduling control scenarios.

[0209] The scheduling control scenario refers to the scenario in which the network side schedules uplink and downlink resources for the terminal device after the terminal device accesses the network.

[0210] This embodiment performs differentiated scheduling control on different network slices to influence resource scheduling of the UE currently in a connected state by different network slices.

[0211] The core network device determines the scheduling priority of the network slice, and then notifies the access network device of the scheduling priority of the network slice through the user plane or control plane.

[0212] Figure 5 A schematic diagram of a method for performing differentiated scheduling control on network slices provided in an embodiment of the present application. Figure 5 In the embodiment, the core network device is recorded as SCF, the access network device is recorded as RAN, and the terminal device is recorded as UE. In this embodiment, the core network device notifies the access network device of the scheduling priority of the network slice through the user plane. The method includes the following process.

[0213] S501, SCF determines the scheduling priority of the network slice.

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

[0215] Optionally, the SCF obtains the scheduling priority between multiple network slices based on the analysis of the big data algorithm module.

[0216] like Figure 5 As shown, SCF subscribes to or requests NWDAF to analyze the scheduling priority of the network slice, and SCF determines the scheduling priority of the network slice based on the analysis results fed back by NWDAF.

[0217] For example, when the service-level agreement (SLA) indicator of a network slice is low, the scheduling priority of the network slice should be increased so that users accessing the network slice can more easily obtain scheduling resources, thereby improving the SLA of the network slice. And vice versa.

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

[0219] SCF can notify SMF of the scheduling priority of the network slice in the following two ways.

[0220] The first method: SCF notifies SMF of the scheduling priority of the network slice through PCF.

[0221] For example, PCF subscribes to the notification message of the scheduling priority change of the network slice on SCF through the network slice priority subscription interface of SCF, and the network slice identifier (slice ID) can be provided in the subscription interface. Optionally, the subscription interface can also include the TA list and PLMN ID corresponding to the network slice.

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

[0223] 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 of the session corresponding to one or more UEs under the specified TA, such as adjusting the corresponding QoS parameters.

[0224] It should be understood that Tracking Area is a new concept established by the LTE system for UE location management. When the UE is in idle state, the core network can know the tracking area where the UE is located. At the same time, when the UE in idle state needs to be paged, it must be paged in all cells of the tracking area where the UE is registered. TA is a cell-level configuration. Multiple cells can be configured with the same TA, and a cell can only belong to one TA.

[0225] The second method: SCF directly notifies SMF of the scheduling priority of the network slice.

[0226] For example, SMF subscribes to the notification message of the scheduling priority change of the network slice on SCF through the network slice priority subscription interface of SCF, and the network slice identifier (slice ID) can be provided in the subscription interface. Optionally, the subscription interface can also include the TA list and PLMN ID corresponding to the network slice.

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

[0228] Taking a network slice as an example, when the SCF determines the scheduling priority of the network slice for the first time, or when the SCF adjusts the scheduling priority of the network slice, it will send the scheduling priority of the network slice to the SMF.

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

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

[0231] If SMF obtains the notification message of the scheduling priority of the network slice from PCF, similar to the PCF triggering PDU session motification in the prior art, according to its instructions, the scheduling priority of the network slice is notified to UPF through N4 session modification.

[0232] S504, UPF sends a message to RAN, which carries the scheduling priority of the network slice.

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

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

[0235] S504: RAN performs corresponding scheduling on the air interface according to the obtained scheduling priority of the network slice.

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

[0237] Figure 6 Another schematic diagram of a method for performing differentiated scheduling control on network slices provided in an embodiment of the present application. Figure 6 In the embodiment, the core network device is recorded as SCF, the access network device is recorded as RAN, and the terminal device is recorded as UE. In this embodiment, the core network device notifies the access network device of the scheduling priority of the network slice through the control plane. The method includes the following process.

[0238] S601, SCF determines the scheduling priority of the network slice.

[0239] S601 is the same as S501, and the specific description of S501 will not be repeated here.

[0240] S602, SCF notifies AMF of the scheduling priority of the network slice.

[0241] SCF can notify AMF of the scheduling priority of network slices in the following two ways.

[0242] The first method: SCF notifies AMF of the scheduling priority of the network slice through PCF.

[0243] PCF can subscribe to the notification message of slice priority change on SCF through the slice priority subscribe interface of SCF. The subscription interface can provide the slice ID, and optionally also include the corresponding TA list and the corresponding PLMN ID.

[0244] When the scheduling priority of the subscribed network slice is adjusted, the SCF will send a notification message to the PCF, which carries the identifier of the network slice and the scheduling priority of the network slice.

[0245] Optionally, the notification message also includes the TA list corresponding to the network slice.

[0246] PCF sends a notification message to AMF through the Npcf_AMpolicy_control interface, which carries the scheduling priority of the network slice. Optionally, the notification message may also carry the TA list corresponding to the network slice.

[0247] The second method: SCF directly notifies AMF of the scheduling priority of the network slice.

[0248] For example, AMF subscribes to Nscf_AMpolicy_control notification on SCF. When the scheduling priority of the subscribed network slice is adjusted, SCF sends a notification message to PCF, which carries the identifier of the network slice and the scheduling priority of the network slice. Optionally, the notification message also includes the TA list corresponding to the network slice.

[0249] Taking a network slice as an example, when the SCF determines the scheduling priority of the network slice for the first time, or after adjusting the scheduling priority of the network slice, the SCF sends a message to the PCF or AMF to indicate the scheduling priority of the network slice.

[0250] S603, AMF sends a scheduling priority message to the RAN network element.

[0251] After receiving the notification message of the scheduling priority of the network slice, the AMF sends an AMF configuration update message through the NG interface between the AMF and the RAN. The AMF configuration update message carries the scheduling priority of the network slice.

[0252] If the slice ID received by AMF is NSI, it needs to be converted into S-NSSAI corresponding to the slice. It should be understood that Slice ID has different identification methods in different places. It can be represented by NSI or S-NSSAI in CN, and S-NSSAI is used between CN and RAN.

[0253] S604: RAN performs resource scheduling according to the AMF configuration update message received from AMF.

[0254] RAN obtains the scheduling priority of the network slice by parsing the AMF configuration update message. Then, RAN determines the resource scheduling strategy based on the scheduling priority of the network slice and the UE's session QoS parameters.

[0255] For example, when the session QoS parameters are the same, UEs in network slices with higher scheduling priorities are scheduled preferentially.

[0256] The embodiment of the present application sets the scheduling priority of the network slice so that users of the network slice with higher scheduling priority are preferentially allocated scheduling resources.

[0257] It should be understood that by setting the scheduling priority of the network slice, differentiated processing between network slices can be performed for UEs that have accessed the network.

[0258] CN can manage SLAs of different slices differently by controlling RAN resource allocation to different slices. CN is not suitable for directly managing RAN wireless spectrum allocation, so it can perform indirect resource control by controlling slice-level bandwidth / rate limits.

[0259] Figure 7 Another schematic diagram of a method for performing differentiated scheduling control on network slices provided in an embodiment of the present application. The method includes the following process.

[0260] S701, SCF determines the bandwidth control policy parameters of the network slice.

[0261] Optionally, the SCF determines the bandwidth control policy parameters of the network slice through a predefined algorithm.

[0262] Optionally, the SCF obtains bandwidth control policy parameters based on analysis of the big data algorithm module.

[0263] like Figure 7 As shown in , SCF subscribes to or requests analysis of the bandwidth control policy parameters of the network slice from NWDAF, and SCF determines the bandwidth control policy parameters of the network slice based on the analysis results fed back by NWDAF.

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

[0265] Specifically, SCF or NWDAF can determine the bandwidth control policy parameters of the network slice through the bandwidth statistics report of UPF or network slice.

[0266] S702, SCF sends a notification message to AMF, which carries the bandwidth control policy parameters of the network slice.

[0267] Specifically, the SCF can send the notification message to the AMF in the following two ways.

[0268] The first method: SCF sends the notification message to AMF through PCF.

[0269] SCF sends the notification message to PCF, and PCF sends the notification message to AMF.

[0270] The second method: SCF sends the notification message directly to AMF.

[0271] Specifically, the SCF needs to select the corresponding AMF, notify through the slice BW change interface of the AMF, specify the corresponding slice ID, and optionally include the corresponding TA list and the corresponding PLMN ID.

[0272] Taking a network slice as an example, when the SCF determines the bandwidth control policy parameters of the network slice for the first time, or after adjusting the bandwidth control policy parameters of the network slice, the SCF sends a notification message to the PCF or AMF to indicate the bandwidth control policy parameters of the network slice.

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

[0274] When AMF receives a message sent by PCF or SCF, it determines the corresponding RAN based on the slice ID carried in the message, which may optionally include the corresponding TA list, and then sends the bandwidth control policy parameters of the network slice to the RAN.

[0275] Optionally, the bandwidth control policy parameters of the network slice are sent to the RAN via an AMF configuration update message.

[0276] Optionally, the bandwidth control policy parameters of the network slice are sent to the RAN via an over load message.

[0277] Specifically, the AMF configuration update message or overload message can carry the total bandwidth available for the slice ID (here S-NSSAI), or it can be a relative value, such as the bandwidth of the slice can be a percentage of the current bandwidth (120% is to increase bandwidth usage, 80% is to reduce bandwidth usage)

[0278] RAN allocates bandwidth to terminal devices accessing the network slice based on the bandwidth control policy parameters of the received network slice.

[0279] When RAN allocates bandwidth to terminal devices accessing the network slice, it ensures that the total bandwidth allocated to all terminal devices under the corresponding network slice does not exceed the total bandwidth of the network slice.

[0280] The total bandwidth may also be a relative ratio between slices, such as a bandwidth ratio of the entire base station.

[0281] The embodiment of the present application sets the bandwidth control policy parameters of the network slice and then processes the network slice according to the bandwidth control policy parameters of the network slice, so as to achieve differentiated processing of the network slice, which is beneficial to improving the service quality of the network slice.

[0282] The above describes the communication method provided by the embodiment of the present application, and the following describes the communication device provided by the embodiment of the present application.

[0283] Figure 8 This is a schematic block diagram of a communication device 800 provided in an embodiment of the present application. The communication device 800 includes the following units.

[0284] The processing unit 810 is used to obtain a policy parameter of a network slice, where the policy parameter of the network slice includes at least one of the following parameters: an access control policy parameter, a scheduling control policy parameter, and a bandwidth control policy parameter;

[0285] The sending unit 820 is used 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.

[0286] Optionally, in some embodiments, the processing unit 810 is used 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; obtain policy parameters of the network slice, which are access category priorities corresponding to the access category to which the network slice belongs.

[0287] Optionally, in some embodiments, the sending unit 820 is also used to notify the terminal device of the access category of the network slice, and the terminal device is a terminal device that has established a contractual relationship with the network slice.

[0288] Optionally, in some embodiments, the policy parameters of the network slice are access control parameters allowed or access control parameters prohibited.

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

[0290] Optionally, in some embodiments, the sending unit 820 is used to notify the access network device of the changed policy parameters of the network slice when the policy parameters of the network slice change.

[0291] Optionally, in some embodiments, the processing unit 810 is used to obtain policy parameters of the network slice through the network data analysis function NWDAF.

[0292] Optionally, in some embodiments, the sending unit 820 is used to send a notification message to the access network device, where the notification message carries the policy parameters of the network slice and the slice identifier of the network slice.

[0293] Optionally, the communication device 800 further includes a receiving unit 830, for example, for receiving an analysis result from the NWDAF.

[0294] It should be understood that the communication device 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 device 800 are respectively to implement Figures 2 to 7 For the sake of brevity, the corresponding processes of each method in are not repeated here.

[0295] Fig. 9 A schematic block diagram of another communication device 900 provided in an embodiment of the present application. The communication device 900 includes a processor 910, a memory 920 and a transceiver 930, the memory 920 is used to store instructions, the processor 910 is used to read the instructions stored in the memory 920, and the execution of the instructions stored in the memory 920 enables the processor 910 to perform the actions performed by the processing unit 810 in the above embodiment, and enables the transceiver 930 to perform the actions performed by the sending unit 820 in the above embodiment.

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

[0297] The receiving unit 1010 is configured to receive a policy parameter of a network slice from a core network device, where the policy parameter of the network slice includes at least one of the following parameters: an access control policy parameter, a scheduling control policy parameter, and a bandwidth control policy parameter;

[0298] Processing unit 1020 is used to determine the relevant strategy of the network slice according to the policy parameters of the network slice.

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

[0300] Processing unit 1020 is used to determine the access control parameters of the network slice according to the access control policy parameters of the network slice.

[0301] Optionally, in some embodiments, the policy parameters of the network slice are access control parameters allowed or access control parameters prohibited.

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

[0303] It also includes: a sending unit 1030, which is used to send a broadcast message to a terminal device, wherein the broadcast message carries the access control parameters of the network slice, and the terminal device has established a contractual relationship with the network slice.

[0304] Optionally, in some embodiments, the policy parameters of the network slice are scheduling control policy parameters; the processing unit 1020 is used to determine a strategy for scheduling resources for terminal devices accessing the network slice according to the scheduling control policy parameters of the network slice.

[0305] Optionally, in some embodiments, the policy parameters of the network slice and the bandwidth control policy parameters; the processing unit 1020 is used to determine the strategy for allocating bandwidth to the terminal device accessing the network slice according to the bandwidth control policy parameters of the network slice.

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

[0307] Optionally, in some embodiments, the receiving unit 1010 is used to receive the changed policy parameters of the network slice from the core network device when the policy parameters of the network slice change.

[0308] Optionally, in some embodiments, the receiving unit 1010 is used to receive a notification message from the core network device, where the notification message carries the policy parameters of the network slice and the slice identifier of the network slice.

[0309] It should be understood that the communication device 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 device 1000 are respectively to implement Figures 2 to 7 For the sake of brevity, the corresponding processes of each method in are not repeated here.

[0310] Fig.11 A schematic block diagram of another communication device 1100 provided in an embodiment of the present application. The communication device 1100 includes a processor 1110, a memory 1120, and a transceiver 1130. The memory 1120 is used to store instructions, and the processor 1110 is used to read the instructions stored in the memory 1120. The execution of the instructions stored in the memory 1120 enables the processor 1110 to perform the actions performed by the processing unit 1020 in the above embodiment, and enables the transceiver 1130 to perform the actions performed by the receiving unit 1010 and the sending unit 1030 in the above embodiment.

[0311] The embodiment of the present application further provides a communication device 1200, which can be a terminal device or a chip. The communication device 1200 can be used to execute the actions executed by the terminal device in the above method embodiment.

[0312] When the communication device 1200 is a terminal device, Fig.12 A simplified schematic diagram of the structure of a terminal device is shown. For ease of understanding and illustration, Fig.12 In this article, a mobile phone is used as an example of a terminal device. Fig.12 As shown, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input-output device. The processor is mainly used to process communication protocols and communication data, as well as to control the terminal device, execute software programs, process software program data, etc. The memory is mainly used to store software programs and data. The radio frequency circuit is mainly used for conversion between baseband signals and radio frequency signals and processing of radio frequency signals. The antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input-output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users. It should be noted that some types of terminal devices may not have input-output devices.

[0313] When data needs to be sent, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, Fig.12 Only one memory and processor are shown. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device. The memory may be set independently of the processor or may be integrated with the processor, and the embodiments of the present application do not limit this.

[0314] In the embodiments of the present application, the antenna and the radio frequency circuit having transceiver functions may be regarded as the transceiver unit of the terminal device, and the processor having the processing function may be regarded as the processing unit of the terminal device. Fig.12 As shown, the terminal device includes a transceiver unit 1201 and a processing unit 1202. The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver device, etc. The processing unit may also be referred to as a processor, a processing board, a processing module, a processing device, etc. Optionally, the device used to implement the receiving function in the transceiver unit 1201 may be regarded as a receiving unit, and the device used to implement the sending function in the transceiver unit 1201 may be regarded as a sending unit, that is, the transceiver unit 1201 includes a receiving unit and a sending unit. The transceiver unit may also be sometimes referred to as a transceiver, a transceiver, or a transceiver circuit, etc. The receiving unit may also be sometimes referred to as a receiver, a receiver, or a receiving circuit, etc. The sending unit may also be sometimes referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0315] For example, in one implementation, the transceiver unit 1201 is used to execute Figure 3 The receiving operation on the terminal device side in step 302, and / or the transceiver unit 1201 is also used to perform other transceiver steps on the terminal device side in an embodiment of the present application.

[0316] For example, in another implementation, the transceiver unit 1201 is used to execute Figure 4 The receiving operation on the terminal device side in S404, and / or the transceiver unit 1202 is also used to execute other transceiver steps on the terminal device side in the embodiment of the present application.

[0317] When the communication device 1200 is a chip, the chip includes a transceiver unit and a processing unit, wherein the transceiver unit may be an input / output circuit or a communication interface; and the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.

[0318] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a computer, the computer implements the method on the core network device side, or the method on the access network device side, or the method on the terminal device side in the above method embodiment.

[0319] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method on the core network device side, or the method on the access network device side, or the method on the terminal device side in the above method embodiment.

[0320] The explanation of the relevant contents and beneficial effects in any of the communication devices provided above can refer to the corresponding method embodiments provided above, and will not be repeated here.

[0321] It should be understood that the processor mentioned in the embodiments of the present invention may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0322] It should also be understood that the memory mentioned in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus random access memory (Direct Rambus RAM, DR RAM).

[0323] 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 component, the memory (storage module) is integrated in the processor.

[0324] It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0325] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0326] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0327] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0328] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.

[0329] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0330] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0331] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: The core network device obtains policy parameters of the network slice, where the policy parameters of the network slice include scheduling control policy parameters and / or 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 policy of the network slice according to the policy parameters of the network slice; The relevant strategies of the network slice include determining a strategy for scheduling transmission resources for a terminal device accessing the network slice and / or determining a strategy for allocating network bandwidth for a terminal device accessing the network slice; Among them, the scheduling control strategy parameters represent parameters used to schedule resources for terminal devices accessing the network slice; the bandwidth control strategy parameters represent parameters used to allocate bandwidth for terminal devices accessing the network slice.

2. The method according to claim 1, characterized in that The policy parameters of the network slice also include access control policy parameters, and the access control policy parameters are access category priorities; The core network device obtains the policy parameters of the network slice, including: The core network device divides all network slices in the system into at least two access categories, and sets access category priorities according to the at least two access categories; The core network device obtains the access category priority corresponding to the access category to which the network slice belongs.

3. The method according to claim 2, characterized in that The method further comprises: The core network device notifies the terminal device of the access category of the network slice, and the terminal device is a terminal device that has established a contractual relationship with the network slice.

4. The method according to claim 1, characterized in that: The policy parameters of the network slice also include access control policy parameters, and the access control policy parameters are access control parameters that are allowed or access control parameters that are prohibited.

5. The method according to any one of claims 1 to 4, characterized in that The core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, including: The core network device sends the policy parameters of the network slice to the access network device through the access and mobility management function AMF.

6. The method according to any one of claims 1 to 4, characterized in that The core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, including: When the policy parameters of the network slice change, the core network device notifies the access network device of the changed policy parameters of the network slice.

7. The method according to any one of claims 1 to 4, characterized in that The core network device obtains policy parameters of the network slice, including: The core network device obtains the policy parameters of the network slice through the network data analysis function NWDAF.

8. The method according to any one of claims 1 to 4, characterized in that The core network device sends the policy parameters of the network slice to the access network device corresponding to the network slice, including: The core network device sends a notification message to the access network device, wherein the notification message carries the policy parameters of the network slice and the slice identifier of the network slice.

9. A communication method, characterized in that: include: The access network device receives the policy parameters of the network slice from the core network device, where the policy parameters of the network slice include scheduling control policy parameters and / or bandwidth control policy parameters; The access network device determines the relevant policy of the network slice according to the policy parameters of the network slice; The relevant strategies of the network slice include determining a strategy for scheduling transmission resources for a terminal device accessing the network slice and / or determining a strategy for allocating network bandwidth for a terminal device accessing the network slice; Among them, the scheduling control strategy parameters represent parameters used to schedule resources for terminal devices accessing the network slice; the bandwidth control strategy parameters represent parameters used to allocate bandwidth for terminal devices accessing the network slice.

10. The method according to claim 9, characterized in that The policy parameters of the network slice also include access control policy parameters; 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.

11. The method according to claim 9, characterized in that The policy parameters of the network slice also include access control policy parameters, and the access control policy parameters are access control parameters that are allowed or access control parameters that are prohibited.

12. The method according to claim 10, characterized in that The method further comprises: The access network device generates an access control parameter of the network slice according to the access control policy parameter of the network slice; The access network device sends a broadcast message to the terminal device, wherein the broadcast message carries the access control parameters of the network slice, and the terminal device establishes a contractual relationship with the network slice.

13. The method according to any one of claims 9 to 12, characterized in that The access network device receives a policy parameter of a network slice from a core network device, including: The access network device receives the policy parameters of the network slice from the core network device through the access and mobility management function AMF.

14. The method according to any one of claims 9 to 12, characterized in that The access network device receives a policy parameter of a network slice from a core network device, including: When the policy parameters of the network slice change, the access network device receives the changed policy parameters of the network slice from the core network device.

15. The method according to any one of claims 9 to 12, characterized in that The access network device receives a policy parameter of a network slice from a core network device, including: The access network device receives a notification message from the core network device, wherein the notification message carries the policy parameters of the network slice and the slice identifier of the network slice.

16. A communication device, characterized in that: The device comprises a processor; the processor is used to read and run a program from a memory to implement the method according to any one of claims 1 to 8.

17. A communication device, characterized in that: The device comprises a processor; the processor is used to read and run a program from a memory to implement the method as claimed in any one of claims 9 to 15.

18. A chip, characterized in that The chip includes a processing module and a communication interface, wherein the processing module is used to control the communication interface to communicate with the outside, and the processing module is also used to implement the method described in any one of claims 1 to 15.

19. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the computer implements the method described in any one of claims 1 to 15.

20. A computer program product, characterized in that The computer program product comprises instructions which, when executed by a computer, cause the computer to implement the method of any one of claims 1 to 15 .

Citation Information

Patent Citations

  • Network slice selection method, device and network architecture

    CN107580360A

  • Access control method and device for wireless network

    CN107734708A

  • Method and apparatus for communicating based on network slicing

    KR1020170119296A