WO2023016006A1 - 一种通信控制方法和通信设备 - Google Patents

一种通信控制方法和通信设备 Download PDF

Info

Publication number
WO2023016006A1
WO2023016006A1 PCT/CN2022/092582 CN2022092582W WO2023016006A1 WO 2023016006 A1 WO2023016006 A1 WO 2023016006A1 CN 2022092582 W CN2022092582 W CN 2022092582W WO 2023016006 A1 WO2023016006 A1 WO 2023016006A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
information
request information
terminal device
pdu session
Prior art date
Application number
PCT/CN2022/092582
Other languages
English (en)
French (fr)
Inventor
舒林
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023016006A1 publication Critical patent/WO2023016006A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier

Definitions

  • the present application relates to the technical field of communication, and more specifically, to a communication control method and a communication device.
  • the fifth generation (5th generation, 5G) network supports three typical application scenarios: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC) and ultra-reliable low-latency communication ( ultra-reliable and low latency communication, URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine-type communication
  • URLLC ultra-reliable low-latency communication
  • eMBB is aimed at traditional user terminals
  • mMTC and URLLC are aimed at vertical industry-oriented Internet of Things (IoT) terminals.
  • IoT Internet of Things
  • CoT Cellular Internet of Things
  • NB-IoT narrowband Internet of Things
  • IoT terminals In the initial stage of the 5G network, IoT terminals still access the 5G core network (core network, CN) through the traditional NB-IoT air interface access technology, and the new air interface (new radio, NR) does not support the access of IoT terminals.
  • core network core network, CN
  • new air interface new radio, NR
  • the third generation partnership project (3rd generation partnership project, 3GPP) established a special standard project in the protocol version 17 (release 17, Rel-17) stage to analyze and optimize the functional characteristics of existing 5G terminals and networks to realize 5G IoT terminals access the 5G core network through 5G NR.
  • 3GPP proposes NR devices with reduced capability (reduced capability, RedCap), that is, RedCap terminals.
  • RedCap reduced capability
  • terminal equipment with reduced capacity has the advantages of lower cost, lower complexity, more compact size, and high performance.
  • the present application provides a communication control method and communication equipment, which can be used to solve the problem of avoiding excessive consumption of network resources by terminals, and make them meet the business requirements of vertical industry scenarios to which they are applicable, thereby improving communication efficiency and network resource utilization Rate.
  • a communication control method including: a first network element receives request information from a terminal device with reduced capability; the first network element processes the request information based on a threshold; the first network element sends feedback information to the terminal device with reduced capability , the feedback information is used to indicate a processing result of the request information by the first network element, and the feedback information includes a cause value, where the cause value is used to indicate a reason for rejection or indicate that the threshold has been reached.
  • this application can avoid excessive consumption of network resources by the capacity-reducing terminal device, and make it suitable for the vertical industry to which it applies
  • the business requirements of the scenario can improve communication efficiency and network resource utilization.
  • the request information is registration request information or service request information
  • the threshold is the maximum number of terminal devices with reduced capabilities registered in the first location area, where the registration The request information includes information indicative of reduced capacity.
  • the first network element Through the UE sending the indication information of capacity reduction to the first network element during the registration process, the first network element performs control on the capacity reduction terminal device based on the maximum number of terminal devices, and provides the UE with a rejection reason value, this application can avoid the capacity reduction terminal
  • the excessive consumption of network resources by equipment can meet the business needs of typical vertical industry scenarios where terminal equipment is applicable, thereby improving communication efficiency and network resource utilization.
  • the processing result is that the first network element rejects the request information
  • the reason value is used to indicate that the maximum number of end devices has been reached.
  • the first location area includes any one of the following parameters: a tracking area, a registration area, and a service area of the first network element of the terminal device with reduced capabilities.
  • the request information is uplink non-access stratum NAS transmission information or PDU session establishment request information
  • the threshold is the maximum number of PDU sessions.
  • this application can avoid the excessive consumption of network resources by the capability-reduced terminal device and meet the typical vertical requirements applicable to the capability-reduced terminal device.
  • the business requirements of industry scenarios can improve communication efficiency and network resource utilization.
  • the PDU session establishment request information includes capability reduction indication information.
  • the processing result is that the first network element rejects the request information, and the cause value is used to indicate that the maximum number of PDU sessions is reached.
  • the request information is packet data unit PDU session modification request information
  • the threshold is the maximum value of the quality of service flow QoS flow quantity
  • the threshold is the maximum value of the QoS rate.
  • this application can avoid the excessive consumption of network resources by the terminal device with reduced capability and meet the requirement of capability Reduce the business requirements of typical vertical industry scenarios applicable to terminal equipment, thereby improving communication efficiency and network resource utilization.
  • the processing result when the number of QoS flows of the terminal equipment with reduced capability reaches a threshold value, the processing result is that the first network element rejects the request information, and the reason value is used to indicate that the maximum number of QoS flows is reached, Or, when the QoS flow quantity of the PDU session of the terminal device with reduced capability reaches the threshold value, the processing result is that the first network element rejects the request information, and the reason value is used to indicate that the maximum QoS flow quantity is reached.
  • the processing result is that the first network element accepts the request information , the cause value is used to indicate that the maximum number of QoS flows has been reached, or, when the number of QoS flows of the PDU session of the terminal device with reduced capabilities plus the number of QoS flows requested to be established by the terminal device with reduced capabilities reaches the threshold, the processing result is that the first network element accepts the request Information, the reason value is used to indicate that the maximum number of QoS flows has been reached.
  • the processing result when the number of QoS flows of the capability-reduced terminal device plus the number of QoS flows requested by the capability-reduced terminal device is greater than the threshold, the processing result is that the first network element rejects or accepts Request information, the cause value is used to indicate that the maximum number of QoS flows has been reached, or, when the number of QoS flows of the PDU session of the terminal device with reduced capabilities plus the number of QoS flows requested by the terminal device with reduced capabilities is greater than the threshold, the processing result is the first network element Reject or accept the request information, and the reason value is used to indicate that the maximum number of QoS flows has been reached.
  • the processing result is that the first network element rejects the request information, and the feedback information also includes the maximum value of the QoS flow quantity.
  • the processing result is that the first network element accepts the request information, and the cause value indicates that the maximum QoS rate is reached.
  • the processing result is that the first network element rejects or accepts the request information, and the cause value is used to indicate that the QoS is not accepted or Reach the maximum QoS rate.
  • the processing result is that the first network element rejects the request information, and the feedback information further includes the maximum value of the QoS rate.
  • the first network element determines that the terminal device is a terminal device with reduced capability according to the indication information of reduced capability.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication control method including: a capability-reduced terminal device sends request information to a first network element; a capability-reduced terminal device receives feedback information from the first network element, and the feedback information is used to indicate that the first network element
  • the feedback information includes a cause value, and the cause value is used to indicate a reason for rejection or to indicate that a threshold has been reached; the capability-reduced terminal device processes the feedback information according to the cause value.
  • the request information is any one of the following information: registration request information, service request information, uplink non-access stratum NAS transmission information, packet data unit PDU session establishment request information, and packet data unit PDU session modification request information, wherein the registration request information or the PDU session establishment request information includes capability reduction indication information.
  • the feedback information when the request information is registration request information, the feedback information is registration rejection information, or when the request information is service request information, the feedback information is service rejection information, or, When the request information is uplink NAS transmission information, the feedback information is downlink NAS transmission information, or, when the request information is PDU session establishment request information, the feedback information is PDU session establishment rejection information, or, when the request information is PDU session modification request information,
  • the feedback information is PDU session modification rejection information, or PDU session modification command information, wherein the PDU session modification rejection information also includes: the maximum value of the quality of service flow QoS flow quantity or the maximum value of the quality of service QoS rate.
  • the feedback information is registration rejection information, and the cause value is reaching the maximum number of terminal devices; or, the feedback information is service rejection information, and the cause value is reaching the maximum number of terminal devices; Or, the feedback information is downlink NAS transmission information, and the reason value is that the maximum number of PDU sessions is reached; or, the feedback information is PDU session establishment rejection information, and the reason value is that the maximum number of PDU sessions is reached; or, the feedback information is PDU session modification rejection information, The reason value is that the maximum number of QoS flows is reached, or that the maximum QoS rate is reached, or that QoS is not accepted.
  • the capability-reduced terminal device processes the feedback information according to the cause value, including: the cause value is that the maximum number of terminal devices is reached, and the capability-reduced terminal device no longer sends information to the first network.
  • the element sends registration request information; or, the reason value is that the maximum number of PDU sessions is reached, and the terminal device with reduced capability no longer sends PDU session establishment request information to the first network element; or, the reason value is that the maximum number of QoS flows is reached, and the terminal device with reduced capability
  • the PDU session modification request information is no longer sent to the first network element, and the PDU session modification request information is used to establish the QoS flow of the terminal device with reduced capability; or, the reason value is that the maximum QoS rate is reached or the QoS is not accepted, and the terminal device with reduced capability
  • the PDU session modification request information is no longer sent to the first network element, and the PDU session modification request information is used to request the ability to reduce the QoS rate of the terminal device.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication control method including: a first network element receives control plane user data from a terminal device with reduced capabilities; the first network element processes the control plane user data based on a threshold, and the threshold is the maximum value of the control plane user data value; the first network element sends feedback information to the terminal device with reduced capability, the feedback information is used to indicate the processing result of the user data on the control plane by the first network element, the feedback information includes a cause value, and the cause value is used to indicate the reason for rejection .
  • the processing result is that the first network element rejects the control plane user data, and the cause value is used to indicate that the threshold is reached or greater.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication control method including: a capability-reduced terminal device sends control plane user data to a first network element; a capability-reduced terminal device receives feedback information from the first network element, and the feedback information is used to indicate that the first network element A network element processes the user data on the control plane, the feedback information includes a cause value, and the cause value is used to indicate the reason for rejection; the capability-reduced terminal device processes the feedback information according to the cause value.
  • the processing result is that the first network element rejects the control plane user data, and the cause value is used to indicate that the threshold is reached or greater.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication control method including: a user plane functional network element receives user plane user data from a terminal device with reduced capability; the user plane functional network element processes the user plane user data based on a threshold, and the threshold is the user plane user data The maximum value of the size; the user plane function network element sends the packet forwarding control protocol PFCP session report request information to the session management function network element, and the PFCP session report request information is used to indicate that the threshold value is reached or exceeded.
  • a communication control method including: the session management function network element receives the packet forwarding control protocol PFCP session report request information from the user plane function network element, and the PFCP session report request information is used to indicate that the threshold value is reached or greater than the threshold , the threshold is the maximum value of user data on the user plane; the session management function network element releases the packet data unit PDU session corresponding to the user plane user data; the session management function network element sends PDU release command information to the terminal device with reduced capability, and the PDU release command information is used to indicate the release of the PDU session.
  • a communication control method including: a capability-reducing terminal device sends user-plane user data to a user-plane functional network element; a capability-reducing terminal device receives PDU release command information from a session management function network element, and the PDU release command The information is used to indicate the release of the PDU session; the terminal device with reduced capabilities processes the user data on the user plane according to the PDU release command information.
  • a communication device including: a transceiver unit, configured to receive request information from a terminal device with reduced capability; a processing unit, configured to process the request information based on a threshold; and a transceiver unit, configured to send the request information to the terminal device with reduced capability Send feedback information, where the feedback information is used to indicate the result of processing the request information by the first network element, where the feedback information includes a cause value, where the cause value is used to indicate a reason for rejection or to indicate that the threshold has been reached.
  • the request information is registration request information or service request information
  • the threshold is the maximum number of terminal devices with reduced capabilities registered in the first location area, where the registration The request information includes information indicative of reduced capacity.
  • the processing result is that the first network element rejects the request information
  • the reason value is used to indicate that the maximum number of end devices has been reached.
  • the first location area includes any one of the following parameters: a tracking area, a registration area, and a service area of the first network element of the terminal device with reduced capabilities.
  • the request information is uplink non-access stratum NAS transmission information or PDU session establishment request information
  • the threshold is the maximum number of PDU sessions.
  • the PDU session establishment request information includes capability reduction indication information.
  • the processing result is that the first network element rejects the request information, and the cause value is used to indicate that the maximum number of PDU sessions is reached.
  • the request information is packet data unit PDU session modification request information
  • the threshold is the maximum value of the quality of service flow QoS flow quantity
  • the threshold is the maximum value of the QoS rate.
  • the processing result when the number of QoS flows of the capability-reduced terminal device reaches a threshold, the processing result is that the first network element rejects the request information, and the reason value is used to indicate that the maximum number of QoS flows is reached, Or, when the QoS flow quantity of the PDU session of the terminal device with reduced capability reaches the threshold value, the processing result is that the first network element rejects the request information, and the reason value is used to indicate that the maximum QoS flow quantity is reached.
  • the processing result is that the first network element accepts the request information , the cause value is used to indicate that the maximum number of QoS flows has been reached, or, when the number of QoS flows of the PDU session of the terminal device with reduced capabilities plus the number of QoS flows requested to be established by the terminal device with reduced capabilities reaches the threshold, the processing result is that the first network element accepts the request Information, the reason value is used to indicate that the maximum number of QoS flows has been reached.
  • the processing result when the number of QoS flows of the capability-reduced terminal device plus the number of QoS flows requested by the capability-reduced terminal device is greater than the threshold, the processing result is that the first network element rejects or accepts Request information, the cause value is used to indicate that the maximum number of QoS flows has been reached, or, when the number of QoS flows of the PDU session of the terminal device with reduced capabilities plus the number of QoS flows requested by the terminal device with reduced capabilities is greater than the threshold, the processing result is the first network element Reject or accept the request information, and the reason value is used to indicate that the maximum number of QoS flows has been reached.
  • the processing result is that the first network element rejects the request information, and the feedback information also includes the maximum value of the QoS flow quantity.
  • the processing result is that the first network element accepts the request information, and the cause value indicates that the maximum QoS rate is reached.
  • the processing result is that the first network element rejects or accepts the request information, and the cause value is used to indicate that the QoS is not accepted or Reach the maximum QoS rate.
  • the processing result is that the first network element rejects the request information, and the feedback information further includes the maximum value of the QoS rate.
  • the first network element determines that the terminal device is a terminal device with reduced capability according to the indication information of reduced capability.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication device including: a transceiver unit, configured to send request information to a first network element; and a transceiver unit, further configured to receive feedback information from the first network element, where the feedback information is used to indicate that the first network element A processing result of the request information by a network element, the feedback information includes a cause value, and the cause value is used to indicate a reason for rejection or to indicate that a threshold has been reached; a processing unit is configured to process the feedback information according to the cause value.
  • the request information is any one of the following information: registration request information, service request information, uplink non-access stratum NAS transmission information, packet data unit PDU session establishment request information, and packet data unit PDU session modification request information, wherein the registration request information or the PDU session establishment request information includes capability reduction indication information.
  • the feedback information when the request information is registration request information, the feedback information is registration rejection information, or, when the request information is service request information, the feedback information is service rejection information, or, When the request information is uplink NAS transmission information, the feedback information is downlink NAS transmission information, or, when the request information is PDU session establishment request information, the feedback information is PDU session establishment rejection information, or, when the request information is PDU session modification request information,
  • the feedback information is PDU session modification rejection information, or PDU session modification command information, wherein the PDU session modification rejection information also includes: the maximum value of the quality of service flow QoS flow quantity or the maximum value of the quality of service QoS rate.
  • the feedback information is registration rejection information, and the cause value is reaching the maximum number of terminal devices; or, the feedback information is service rejection information, and the cause value is reaching the maximum number of terminal devices; Or, the feedback information is downlink NAS transmission information, and the reason value is that the maximum number of PDU sessions is reached; or, the feedback information is PDU session establishment rejection information, and the reason value is that the maximum number of PDU sessions is reached; or, the feedback information is PDU session modification rejection information, The reason value is that the maximum number of QoS flows is reached, or that the maximum QoS rate is reached, or that QoS is not accepted.
  • the cause value is that the maximum number of terminal devices is reached, and the transceiver unit is further configured to no longer send registration request information to the first network element; or, the cause value is to reach The maximum number of PDU sessions, the transceiver unit, is also used to no longer send PDU session establishment request information to the first network element; or, the reason value is that the maximum number of QoS flows is reached, and the transceiver unit is also used to no longer send PDU session establishment request information to the first network element.
  • the PDU session modification request information, the PDU session modification request information is used to establish the QoS flow of the terminal equipment with reduced capability; or, the cause value is that the maximum QoS rate is reached or the QoS is not accepted, and the transceiver unit is also used to no longer send the first network to the first network.
  • the unit sends PDU session modification request information, and the PDU session modification request information is used to request the ability to reduce the QoS rate of the terminal device.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication device including: a transceiver unit, configured to receive control plane user data from a terminal device with reduced capabilities; a processing unit, configured to process the control plane user data based on a threshold, where the threshold is the control plane user data The maximum value; the transceiver unit is also configured to send feedback information to the terminal device with reduced capabilities, the feedback information is used to indicate the processing result of the user data on the control plane by the first network element, the feedback information includes a cause value, and the cause value is used for Indicates the reason for the rejection.
  • the processing result is that the first network element rejects the control plane user data, and the cause value is used to indicate that the threshold is reached or greater.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication device including: a receiver unit, configured to send control plane user data to a first network element; the receiver unit, also configured to receive feedback information from the first network element, the feedback information is used to indicate the result of processing the user data on the control plane by the first network element, the feedback information includes a cause value, and the cause value is used to indicate a reason for rejection; the processing unit is configured to process the feedback information according to the cause value.
  • the processing result is that the first network element rejects the control plane user data, and the cause value is used to indicate that the threshold is reached or greater.
  • the first network element is a mobility management network element or a session management function network element.
  • a communication device including: a transceiver unit, configured to receive user plane user data from a terminal device with reduced capability; a processing unit, configured to process the user plane user data based on a threshold, where the threshold is the user plane user data The maximum value of the size; the transceiver unit is also used to send packet forwarding control protocol PFCP session report request information to the session management function network element, and the PFCP session report request information is used to indicate that the threshold value is reached or exceeded.
  • a communication device including: a transceiver unit, configured to receive packet forwarding control protocol PFCP session report request information from a user plane functional network element, where the PFCP session report request information is used to indicate that the threshold is reached or greater than , the threshold is the maximum value of the user data on the user plane; the processing unit is used to release the packet data unit PDU session corresponding to the user data on the user plane; Information is used to indicate the release of the PDU session.
  • PFCP session report request information is used to indicate that the threshold is reached or greater than , the threshold is the maximum value of the user data on the user plane
  • the processing unit is used to release the packet data unit PDU session corresponding to the user data on the user plane
  • Information is used to indicate the release of the PDU session.
  • a communication device including: a transceiver unit, configured to send user plane user data to a user plane functional network element; a transceiver unit, configured to receive PDU release command information from a session management functional network element, PDU The release command information is used to indicate the release of the PDU session; the processing unit is used to process user data on the user plane according to the PDU release command information.
  • a computer storage medium which stores instructions, and when the instructions are run on a computer, the computer executes the computer as described in the first aspect and any possible implementation manner of the first aspect.
  • a computer storage medium which stores instructions, and when the instructions are run on a computer, the computer executes the method as described in the second aspect and any possible implementation manner of the second aspect.
  • a computer program product When the computer program product runs on a computer, the computer performs the communication as described in the first aspect and any possible implementation manner of the first aspect.
  • the control method, or the communication control method as described in the third aspect and any possible implementation of the third aspect, or the communication as described in the fourth aspect and any possible implementation of the fourth aspect The control method, or, the communication control method as described in the fifth aspect and any possible implementation manner of the fifth aspect, or, the communication as described in the sixth aspect and any possible implementation manner of the sixth aspect Control Method.
  • a computer program product is provided.
  • the computer program product is run on a computer, the computer is made to perform the communication described in the second aspect and any possible implementation manner of the second aspect.
  • FIG. 1 is a schematic diagram of the architecture of a 5G system provided by this application.
  • Fig. 2 is a schematic flowchart of a communication control method provided by the present application.
  • Fig. 3 is a schematic flowchart of another communication control method provided by the present application.
  • Fig. 4 is a schematic flowchart of another communication control method provided by the present application.
  • Fig. 5 is a structural block diagram of a communication device provided by the present application.
  • Fig. 6 is a structural block diagram of another communication device provided by the present application.
  • the technical solution of the embodiment of the present application can be applied to various communication systems, such as: global system of mobile communication (global system of mobile communication, GSM) system, code division multiple access (code division multiple access, CDMA) system, broadband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE Time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunications system, UMTS), global interconnection microwave access (worldwide interoperability for microwave access, WiMAX) communication system, 5G network or NR, or future communication Network, such as the sixth generation (6th generation, 6G) network, etc.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • general packet radio service general packet radio service
  • GPRS general packet radio service
  • the terminal device in the embodiment of the present application may be called an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network device, user agent or user device .
  • the terminal can be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (PDA), a wireless communication function Handheld devices, computing devices or other devices connected to a wireless modem, in-vehicle devices, wearable devices or end devices in the Internet of Things, vehicular networks, home gateways (customer premise equipment, CPE) and any form of end devices in future networks wait.
  • user equipment user equipment
  • UE user equipment
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a base station (base transceiver station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, BTS) in a WCDMA system.
  • BTS base transceiver station
  • NodeB, BTS base station
  • NB can also be an evolved base station (evolutional NodeB, eNB or eNodeB) in the LTE system
  • evolutional NodeB, eNB or eNodeB in the LTE system
  • the network device can For relay stations, access points, vehicle-mounted devices, wearable devices, and network devices in 5G networks or future communication networks, etc.
  • FIG. 1 shows a schematic diagram of a 5G system architecture provided by this application.
  • the application scenario to which the communication method of the present application can be applied may include a UE101, a radio access network (radio access network, RAN) device 102, a user plane function (user plane function, UPF) network element 103, Access and mobility management function (access and mobility management function, AMF) 104, session management function (session management function, SMF) network element 105, policy control function (policy control function, PCF) network element 106, application function (application function, AF) network element 107, network slice selection authentication and authorization function (network slice specific authentication and authorization function, NSSAAF) network element 108, unified data management (unified data management, UDM) network element 109, authentication and authorization service function ( authentication server function (AUSF) network element 110, network slice selection function (network slice selection function, NSSF) network element 111 and data network (data network, DN) 112.
  • radio access network radio access network
  • UPF user plane function
  • a RAN device is a base station (base station, BS).
  • Base station also known as base station equipment, is a device that connects terminal equipment to a wireless network, including but not limited to: transmission reception point (transmission reception point, TRP), 5G node B (gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS) , home base station (for example, home evolved nodeB, or home node B, HNB), base band unit (base band unit, BBU), or Wifi access point (access point, AP), or small base station equipment (pico), etc.
  • TRP transmission reception point
  • gNB 5G node B
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • base station controller base station controller
  • base transceiver station base transceiver station
  • BTS home base station
  • home base station
  • the user plane function network element mainly includes the following functions: data packet routing and transmission, packet detection, service usage reporting, quality of service (QoS) processing, lawful interception, uplink packet detection, downlink data packet storage, etc. related functions.
  • QoS quality of service
  • AMF It can be understood as the naming of mobility management network elements in the 5G architecture.
  • the mobility management network element mainly includes the following functions: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management and other functions related to access and mobility.
  • SMF It can be understood as the naming of session management network elements in the 5G architecture. Among them, the session management network element mainly performs functions such as session management, execution of control policies issued by PCF, selection of UPF, and allocation of UE IP addresses.
  • PCF It can be understood as the naming of policy control function network elements in the 5G architecture. Among them, the policy control function network element is mainly responsible for policy control functions such as charging for sessions and service flow levels, QoS bandwidth guarantee, mobility management, and UE policy decision-making.
  • the PCFs connected by AMF and SMF are access and mobility control PCF (PCF for access and mobility control, AM PCF) and SM PCF respectively.
  • AM PCF and SM PCF may not be the same PCF entity.
  • UDM It can be understood as the naming of unified data management network elements in the 5G architecture.
  • the unified data management network element mainly includes the following functions: unified data management, support for authentication credential processing in the 3GPP authentication and key agreement mechanism, user identity processing, access authorization, registration and mobility management, subscription management, short message management etc.
  • AUSF It can be understood as the naming of authentication and authorization service function network elements in the 5G architecture. Among them, the authentication and authorization service function network element is responsible for authentication and authorization of terminal equipment access.
  • the DN Data network, used to identify the operator network access point name.
  • the DN may also include an authentication, authorization, and accounting (authentication, authorization, accounting, AAA) server function, which is responsible for performing secondary authentication on the user.
  • AAA authentication, authorization, accounting
  • the application function network element mainly transmits requirements from the application side to the network side, for example, quality of service (quality of service, QoS) requirements, and the like.
  • the AF network element may be a third-party functional entity, or an application service deployed by an operator, such as an IP multimedia subsystem (IP multimedia subsystem, IMS) voice call service.
  • IP multimedia subsystem IP multimedia subsystem, IMS
  • NSSAAF It can be understood as the naming of the authentication and authorization functions selected for network slicing in the 5G architecture. Among them, the authentication and authorization function of network slicing selection is mainly used to authenticate and authorize the network slicing service requested by the terminal device.
  • the above-mentioned network element or function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • N1 The interface between the AMF and the UE, which has nothing to do with access, and is used to deliver QoS control rules to the UE.
  • N2 The interface between the AMF and the RAN, used to transfer radio bearer control information from the core network side to the RAN.
  • N3 the interface between RAN and UPF, used to transfer user plane data between RAN and UPF.
  • N4 The interface between SMF and UPF, which is used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules, QoS control rules, and traffic statistics rules for the user plane, as well as the information reporting of the user plane.
  • N5 The interface between the AF and the PCF, used for delivering application service requests and reporting network events.
  • N6 The interface between UPF and DN connection, used to transfer user plane data between UPF and DN.
  • N7 The interface between PCF and SMF, which is used to deliver protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control policy.
  • protocol data unit protocol data unit
  • PDU protocol data unit
  • N8 The interface between AMF and UDM, which is used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register UE current mobility management related information with UDM.
  • N9 The interface between UPF and UPF, such as the interface between the visited-policy control function (V-PCF) and the home-policy control function (H-PCF), or the interface with The interface between the UPF connected to the DN and the UPF connected to the RAN is used to transfer user plane data between the UPFs.
  • V-PCF visited-policy control function
  • H-PCF home-policy control function
  • N10 The interface between SMF and UDM, which is used for SMF to obtain session management-related subscription data from UDM, and for SMF to register UE current session-related information with UDM.
  • N11 The interface between the SMF and the AMF, used to transfer the PDU session tunnel information between the RAN and the UPF, the control information sent to the UE, the radio resource control information sent to the RAN, etc.
  • N12 The interface between AMF and AUSF, used for identity authentication of terminal equipment.
  • N13 The interface between UDM and AUSF, used to transmit authentication parameters and authentication results.
  • N14 An interface between two AMFs, used to transfer user context to support cross-AMF movement.
  • N15 the interface between the PCF and the AMF, used to issue UE policies and access control related policies.
  • N22 the interface between AMF and NSSF, used for slice selection and acquisition of slice information allowed by the terminal.
  • N33 The interface between NEF and AF, used for third-party applications to obtain capability opening information from the mobile network and provide application information to the mobile network.
  • N58 Interface between AMF and NSSAAF to perform authentication and authorization for network slice selection.
  • N59 The interface between NSSAAF and UDM, used to obtain user subscription information for authentication and authorization of network slice selection.
  • each network element included in FIG. 1 is only a name, and the name does not limit the function of the network element itself.
  • the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terms in 5G, or may be named by other names, etc., which will be described in a unified manner here, and will not be described in detail below.
  • the present application is not limited to the system architecture shown in FIG. 1 .
  • the communication system to which the communication method of the present application can be applied may include more or less network elements or devices.
  • the devices or network elements in FIG. 1 may be hardware, or functionally divided software, or a combination of the above two.
  • the devices or network elements in Figure 1 may communicate with each other through other devices or network elements.
  • the capability-reduced terminal device is equivalent to the RedCap UE.
  • the embodiment of the present application uses the capability-reduced terminal device to describe the technical solution of the embodiment of the present application.
  • Industrial wireless sensor network diverse requirements; no mobility or low-speed mobility; support relay transmission; low power consumption; low cost and low complexity.
  • Uplink transmission is the mainstay, with large uplink bandwidth; 24-hour real-time online; no mobility; no need for power saving.
  • Personal wearable smart devices support voice and business continuity; support relay transmission; low power consumption; low cost and low complexity.
  • the capability reduction terminal device has lower equipment complexity, lower cost, more compact size and high performance.
  • the 5G network needs to identify the connected terminal device as a terminal device with reduced capabilities, that is, a terminal device that supports the RedCap capability.
  • the 5G network needs to control its access and optimize the resource utilization of the 5G network to meet the business requirements of the vertical industry scenarios it applies to, thereby improving communication efficiency and network efficiency. resource utilization.
  • the access control factors for network resources of NB-IoT terminals include the maximum number of PDU sessions (sessions) activated on the user plane (UP).
  • the access control factor for the network resource of the eMBB terminal is the maximum number of connections of the PDU session.
  • this application provides a communication control method and communication equipment, which can help to avoid excessive consumption of network resources by RedCap terminal equipment, and make it meet the business requirements of the vertical industry scenarios to which it is applicable, thereby improving Communication efficiency and network resource utilization.
  • Fig. 2 shows a schematic flowchart of a communication control method #200 provided by the present application. The specific content is shown in Figure 2. It should be understood that the execution bodies of the method #200 shown in FIG. 2 are the network element #A and the UE, and the UE is a capability-reduced terminal device.
  • network element #A receives the request information from the UE.
  • the request information may be registration request information, service request information, packet data unit PDU session establishment request information, PDU session modification request information, and uplink non-access stratum (non access stratum, NAS ) to transmit information, and so on.
  • the network element #A processes the request information based on the threshold.
  • the threshold corresponds to the request information sent by the capability-reducing terminal device, that is, the correspondence can be understood as: if the request information is registration request information, the threshold is the ability to register with the network element #A in a certain location area Reduce the maximum number of terminal devices; if the request information is service request information, the threshold is also the ability to register in the network element #A in a certain location area Reduce the maximum number of terminal devices; if the request information is uplink NAS transmission information Or PDU session establishment request information, the threshold value is the maximum value of the PDU session number of the terminal device with this ability; if the request information is PDU session modification request information, the threshold value is the maximum value of the QoS flow (flow) quantity of the terminal device with this capability reduction, Or it is the ability to reduce the maximum value of the QoS rate of the terminal device, which will be described in detail later.
  • the network element #A processes the request information based on the threshold corresponding to the request information, and determines a corresponding processing result.
  • the network element #A enables the UE to know the processing result of the request information by the network element #A, so that the UE can determine a corresponding action or behavior based on the processing result.
  • the network element #A processes the request information based on the threshold, a corresponding processing result is determined, and the processing result includes: accepting the request information or rejecting the request information.
  • the feedback information sent by the network element #A to the UE will include a cause value (cause value), which is used to indicate the reason for rejection or to indicate that the threshold has been reached.
  • the UE processes the feedback information according to the cause value.
  • the UE will process the feedback information based on the cause value, For example, the request information is no longer sent to network element #A.
  • the network element #A determines that the UE is a terminal device with reduced capabilities through the indication information of reduced capabilities included in the request information.
  • the present application can realize the control of the network on the terminal device with reduced capability, and then realize the avoidance of excessive consumption of network resources by the terminal device with reduced capability, thereby make it meet the business needs of the vertical industry scenarios it applies to, so as to improve communication efficiency and network resource utilization.
  • the request information is registration request information
  • network element #A is an AMF network element.
  • the UE sends registration request (registration request) information, where the registration request information is used to request the UE to register with the network.
  • the registration request information includes capability reduction indication information
  • the AMF network element determines that the UE is a capability reduction device based on the indication information.
  • the AMF network element processes the registration request information by reducing the maximum number of terminal devices based on the registered capability in the first location area.
  • the AMF network element determines that the UE is a terminal device with reduced capability based on the reduced capability indication information included in the registration request information, and stores it in the context of the UE.
  • the AMF network element checks whether the number of terminal devices with reduced capabilities registered in the first location area reaches the maximum number of terminal devices. If it is not reached, the AMF network element completes the registration process; if it is reached, the AMF network element rejects the registration request information of the UE.
  • the first location area may include:
  • the tracking area (tracking area, TA) where the UE is currently located.
  • the registration area (registration area) where the UE is currently located.
  • the registration area includes the TA where the UE is currently located and multiple surrounding TAs, forming a TA list.
  • the AMF network element sends registration rejection (registration reject) information to the UE, the registration rejection information includes a reason value, and the reason value is used to indicate that the maximum number of UEs reached has been reached.
  • the AMF network element When the AMF network element determines to reject the registration request information of the UE, it will send registration rejection information to the UE, and carry a cause value in the registration rejection information, which is used to indicate the reason for the rejection.
  • the UE enters the de-registration state according to the registration rejection information and the cause value.
  • the UE After the UE learns that the AMF network element rejects the UE's registration request information, it will choose not to send the registration request information to the AMF network element based on the registration rejection information and the reason value, and enter the de-registration state.
  • the AMF network element Through the UE sending the indication information of capacity reduction to the AMF network element in the registration process, the AMF network element performs control on the capacity reduction terminal device based on the maximum number of terminal devices, and provides the rejection reason value to the UE.
  • This application can prevent the capacity reduction terminal device from The excessive consumption of network resources can meet the business needs of typical vertical industry scenarios where terminal equipment is applicable, thereby improving communication efficiency and network resource utilization.
  • the request information is service request information
  • network element #A is an AMF network element.
  • the UE sends service request (service request) information, and the service request information is used to request the network to provide services, such as establishing air interface user plane resources.
  • service request service request
  • the service request information is used to request the network to provide services, such as establishing air interface user plane resources.
  • the UE After the UE successfully registers with the network, the UE sends a service request message to the AMF network element, that is, it requests the network to provide a certain service or service, for example, to establish an air interface user plane resource.
  • the UE after the UE successfully registers with the network, the UE does not need to carry the indication information of reduced capacity in the service request information, and the AMF network element can determine that the UE is Ability to reduce terminal equipment.
  • the AMF network element processes the service request information by reducing the maximum number of terminal devices based on the capabilities registered in the first location area.
  • the AMF network element checks whether the number of capacity-reducing terminal devices registered in the first location area reaches the maximum number of terminal devices. If it is not reached, the AMF network element will continue to provide the requested service for the UE; if it is reached, the AMF network element will reject the service request information of the UE, that is, refuse to provide the requested service for the UE.
  • the AMF network element sends service rejection (service reject) information to the UE, the service rejection information includes a cause value, and the cause value is used to indicate that the maximum number of UEs reached has been reached.
  • service rejection service reject
  • the AMF network element When the AMF network element determines to reject the service request information of the UE, it will send service rejection information to the UE, and carry a cause value in the service rejection information, which is used to indicate the reason for the rejection.
  • the UE enters the de-registration state according to the service rejection information and the cause value.
  • the UE learns that the AMF network element has rejected the UE's service request information, it will no longer send service request information to the AMF network element based on the service rejection information and the cause value, and enter the de-registration state.
  • the AMF network element checks whether the number of registered capacity reduction terminal devices in the first location area has reached the maximum number of terminal devices, and determines whether to send a de-registration request to the UE based on the check result ( de-registration request) information. If reached, the AMF network element sends a de-registration request message to the UE.
  • the de-registration request message includes a cause value, which is used to indicate that the maximum number of terminal devices has been reached.
  • the AMF network element Through the UE sending the indication information of capacity reduction to the AMF network element in the registration process, the AMF network element performs control on the capacity reduction terminal device based on the maximum number of terminal devices, and provides the rejection reason value to the UE.
  • This application can prevent the capacity reduction terminal device from The excessive consumption of network resources can meet the business needs of typical vertical industry scenarios where terminal equipment is applicable, thereby improving communication efficiency and network resource utilization.
  • the request information is uplink NAS transmission information
  • network element #A is an AMF network element.
  • the UE sends uplink NAS transmission information to the AMF network element, and the uplink NAS transmission information includes PDU session establishment request information.
  • the UE initiates PDU session establishment request information based on the request of the upper layer application, and the PDU session establishment request information is encapsulated in uplink NAS transmission information and sent to the AMF network element, and the PDU session establishment request information is used to request establishment of a new PDU session.
  • the AMF network element processes the uplink NAS transmission information and PDU session establishment request information based on the maximum number of PDU sessions.
  • the AMF network element checks whether the number of active PDU sessions of the UE reaches the maximum number of PDU sessions. If not, the AMF network element executes the PDU session establishment process and forwards the PDU session establishment request information to the SMF network element; if it is reached, the AMF network element does not forward the PDU session establishment request information to the SMF network element.
  • the AMF network element sends downlink NAS transmission information to the UE, and the downlink NAS transmission information includes the PDU session establishment request information received in S210#C.
  • the AMF network element When the AMF network element determines that the number of active PDU sessions of the UE reaches the maximum number of PDU sessions, it will send downlink NAS transmission information to the UE, and include the PDU session establishment request information received from the UE in the downlink NAS transmission information and send it back to the UE , and carries a cause value in the downlink NAS transmission information, which is used to indicate the reason for rejection, that is, the reason for sending back the PDU session establishment request information.
  • the above-mentioned downlink NAS transmission information includes a cause value, which is used to indicate that the maximum number of PDU sessions reached (maximum number of PDU sessions reached).
  • the UE no longer sends PDU session establishment request information according to the downlink NAS transmission information and the cause value.
  • the AMF network element determines that the UE is a terminal device with reduced capabilities through the indication information of reduced capabilities carried by the UE in the previous registration process.
  • this application can avoid the excessive consumption of network resources by the capacity reduction terminal device, and meet the typical vertical industries applicable to the capacity reduction terminal device
  • the business requirements of the scenario can improve communication efficiency and network resource utilization.
  • the request information is PDU session establishment request information
  • network element #A is an SMF network element.
  • the UE sends PDU session establishment request information to the SMF network element.
  • the UE initiates PDU session establishment request information based on the request of the upper layer application, and the PDU session establishment request information is encapsulated in the uplink NAS transmission information and sent to the AMF network element, and the AMF network element encapsulates the received PDU session establishment request information in the creation
  • the PDU session context request information is sent to the SMF network element, and the PDU session establishment request information is used to request the establishment of a new PDU session.
  • the SMF network element processes the PDU session establishment request information based on the maximum number of PDU sessions.
  • the SMF network element checks whether the number of active PDU sessions of the UE reaches the maximum number of PDU sessions. If it is not reached, the SMF network element accepts the PDU session establishment request information; if it is reached, the SMF network element rejects the PDU session establishment request information, and sends a PDU session rejection information to the UE.
  • the SMF network element sends PDU session establishment rejection information to the UE.
  • the SMF network element When the SMF network element determines to reject the PDU session establishment request information of the UE, it will send the PDU session establishment rejection information to the UE, and carry a reason value in the rejection information, which is used to indicate the reason for the rejection.
  • the SMF network element encapsulates the PDU session establishment rejection information in the N1 transmission information and sends it to the AMF network element, and the AMF network element encapsulates the PDU session establishment rejection information in the downlink NAS transmission information and forwards it to the UE.
  • PDU session establishment rejection information includes a cause value, which is used to indicate that the maximum number of PDU sessions reached (maximum number of PDU sessions reached).
  • the UE no longer sends PDU session establishment request information to the SMF network element according to the PDU session establishment rejection information and the cause value.
  • the SMF network element determines from the AMF network element that the UE is a terminal device with reduced capabilities, for example, when creating the first PDU session, or during the location update registration process triggered by inter-AMF network element (inter-AMF) movement,
  • the AMF network element sends the learned indication information of the UE's ability to support RedCap to the SMF network element, or the SMF network element obtains the indication information of the UE's ability to support the RedCap directly from the UE through the PDU session establishment request information.
  • this application can avoid the excessive consumption of network resources by the capacity reduction terminal device, and meet the typical vertical industries applicable to the capacity reduction terminal device
  • the business requirements of the scenario can improve communication efficiency and network resource utilization.
  • the request information is PDU session modification request information, which is used to request to create at least one QoS flow
  • network element #A is an SMF network element.
  • the UE sends PDU session modification request information to the SMF network element.
  • the UE initiates PDU session modification request information based on the request of the upper layer application, and is used to request to create at least one QoS flow, wherein the PDU session modification request information includes the newly created at least one QoS flow information.
  • the PDU session modification request information is encapsulated in the uplink NAS transmission information and sent to the AMF network element.
  • the AMF network element encapsulates the received PDU session modification request information into the update PDU session context request information and sends it to the SMF network element.
  • the SMF network element processes the PDU session modification request information based on the maximum number of QoS flows.
  • the SMF network element has two processing methods for the UE's PDU session modification request information based on the maximum number of QoS flows:
  • Method 1 The number of QoS flows established by the capability-reduced terminal device at the SMF network element has reached the maximum number of QoS flows, or the number of QoS flows established by the capability-reduced terminal device at the SMF network element has not reached the maximum QoS flow quantity, but adding If the number of newly requested QoS flows exceeds the maximum number of QoS flows, the SMF network element rejects the UE's PDU session modification request information.
  • Method 2 The number of QoS flows established by the terminal device at the SMF network element does not reach the maximum number of QoS flows, but the number of newly requested QoS flows reaches or exceeds the maximum number of QoS flows, and the SMF network element receives all or part of the request. QoS flow, the SMF network element accepts the PDU session modification request information of the UE.
  • the SMF network element sends PDU session modification rejection information or PDU session modification command information to the UE.
  • the feedback information sent by the SMF network element to the UE has two forms:
  • Form #1 The SMF network element rejects the UE's PDU session modification information, and the SMF network element rejects the PDU session modification information
  • the PDU session modification rejection information includes the reason value, which indicates that the maximum number of QoS flows reached per UE has been reached, or the maximum number of QoS flows reached per UE has been reached, or the maximum QoS flow of the PDU session has been reached Number (maximum number of QoS flows reached per PDU session).
  • the AMF network element encapsulates the received PDU session modification rejection information into the downlink NAS transmission information and forwards it to the UE.
  • Form #2 The SMF network element accepts the PDU session modification information, the SMF network element encapsulates the PDU session modification command (PDU session modification command) information in the N1 transmission information and sends it to the AMF network element, and the PDU session modification command information includes the cause value , which indicates that the maximum number of QoS flows reached per UE has been reached, or the maximum number of QoS flows reached per PDU session has been reached.
  • the AMF network element encapsulates the received PDU session modification command information into the downlink NAS transmission information and forwards it to the UE.
  • the SMF network element can carry the UE maximum QoS flow number or the PDU session maximum QoS flow number or the maximum QoS flow number in the PDU session modification rejection information or the PDU session modification command information.
  • the SMF network element is based on the processing threshold, that is, the maximum number of QoS flows corresponds to two processing granularities, and one processing granularity is based on the UE level to determine whether the maximum number of QoS flows is reached, that is, one The maximum number of QoS flows that the UE can establish, and the corresponding cause value indicates that the maximum number of QoS flows reached per UE has been reached.
  • Another processing granularity is to determine whether the maximum number of QoS flows is reached based on a PDU session level of the UE, that is, the maximum number of QoS flows that can be included in a PDU session of the UE, and the corresponding cause value indicates that the maximum number of QoS flows (maximum number of QoS flows reached per PDU session).
  • the SMF network element uniformly provides the same cause value, which is used to indicate that the maximum number of QoS flows reached (maximum number of QoS flows reached), and the UE, according to the policy agreed with the network, Understand the received reason value as reaching the maximum QoS flow number of UE or reaching the maximum QoS flow number of PDU session.
  • the UE no longer sends PDU session modification request information to the SMF network element.
  • the UE determines not to send the PDU session establishment request information to the AMF network element, so as to no longer request to create a new QoS flow.
  • the SMF network element determines from the AMF network element that the UE is a terminal device with reduced capabilities. For example, when creating the first PDU session, or in the location update registration process triggered by inter-AMF movement, the AMF will know the The indication information that the UE supports the RedCap capability is sent to the SMF network element, or the SMF network element obtains the indication information that the UE supports the RedCap capability and directly reports it from the UE through the PDU session establishment request information.
  • this application can avoid the excessive consumption of network resources by the terminal device with reduced capacity, and meet the typical requirements applicable to the terminal device with reduced capacity.
  • the business requirements of vertical industry scenarios can improve communication efficiency and network resource utilization.
  • the request information is the PDU session modification request information, which is used to request to modify the QoS rate of at least one QoS flow
  • the network element #A is an SMF network element.
  • the UE sends PDU session modification request information to the SMF network element.
  • the UE initiates a PDU session modification request message based on the request of the upper layer application to request modification of the QoS rate of at least one QoS flow.
  • the PDU session modification request information is encapsulated in the uplink NAS transmission information and sent to the AMF network element.
  • the AMF network element encapsulates the received PDU session modification request information into the update PDU session context request information and sends it to the SMF network element.
  • the SMF network element processes the PDU session modification request information based on the maximum QoS rate.
  • the SMF network element checks whether the QoS rate requested by the UE exceeds the maximum QoS rate limit of the network for terminal equipment with reduced capabilities. If the QoS rate requested by the UE exceeds the network's maximum QoS rate for terminal equipment with reduced capabilities, and the SMF network element rejects the UE's QoS rate request, the SMF network element rejects the UE's PDU session modification request, or if the QoS rate requested by the UE The network reaches or exceeds the maximum QoS rate for terminal equipment with reduced capabilities, but the SMF network element decides to allocate the maximum QoS rate for the UE, then the SMF network element accepts the UE's PDU session modification request.
  • the SMF network element sends PDU session modification rejection information or PDU session modification command information to the UE.
  • the feedback information sent by the SMF network element to the UE has two forms:
  • Form #3 If the SMF network element rejects the PDU session modification information of the UE, the SMF network element encapsulates the PDU session modification rejection information in the N1 transmission information and sends it to the AMF network element, and the information includes the cause value, which indicates that the maximum QoS is reached rate (maximum rate of QoS flows reached) or indicate QoS not accepted (QoS not accepted).
  • the AMF network element encapsulates the received PDU session modification rejection information into the downlink NAS transmission information and forwards it to the UE.
  • Form #4 If the SMF network element accepts the PDU session modification information of the UE, the SMF network element encapsulates the PDU session modification command (PDU session modification command) information in the N1 transmission information and sends it to the AMF network element, and the information includes the cause value, It indicates that the maximum rate of QoS flows reached (maximum rate of QoS flows reached) or indicates that QoS is not accepted (QoS not accepted).
  • the AMF network element encapsulates the received PDU session modification command information into the downlink NAS transmission information and forwards it to the UE.
  • the SMF network element may carry the maximum QoS rate in the PDU session modification rejection information or the PDU session modification command information.
  • the UE no longer sends PDU session modification request information to the SMF network element.
  • the UE no longer requests the SMF network element for a rate greater than the maximum QoS rate issued by the network.
  • the SMF network element determines from the AMF network element that the UE is a terminal device with reduced capabilities, for example, when creating the first PDU session, or during the location update registration process triggered by inter-AMF network element (inter-AMF) movement,
  • the AMF network element sends the learned indication information of the UE's ability to support RedCap to the SMF network element, or the SMF network element obtains the indication information of the UE's ability to support the RedCap directly from the UE through the PDU session establishment request information.
  • this application can avoid the excessive consumption of network resources by the terminal device with reduced capacity, and meet the typical vertical requirements applicable to the terminal device with reduced capacity.
  • the business requirements of industry scenarios can improve communication efficiency and network resource utilization.
  • Fig. 3 shows a schematic flowchart of a communication control method #300 provided by the present application. The specific content is shown in Figure 3. It should be understood that the execution bodies of the method #300 shown in FIG. 3 are the network element #A and the UE, and the UE is a capability-reduced terminal device.
  • the UE needs to send uplink control plane (control plane, CP) user data based on the request of the upper layer application.
  • control plane control plane
  • the UE encapsulates the CP user data in a container (such as a small data container or a payload container) of control plane service request information ;
  • the UE encapsulates the CP user data in a container (for example, a payload container) of uplink NAS transmission information.
  • network element #A receives CP user data from UE.
  • the network element #A processes the CP user data based on the threshold.
  • the network element #A checks whether the received CP user data size exceeds the maximum user data size limit of the network for the terminal equipment with reduced capabilities. If the size of the CP user data sent by the UE exceeds the maximum user data size limit of the network for the terminal equipment with reduced capabilities, then:
  • the network element #A rejects the CP service request information, and discards the received CP user data;
  • the network element #A If the network element #A receives the uplink NAS transmission information, the network element #A sends the CP user data back to the UE;
  • the network element #A If the network element #A directly receives the CP user data, the network element #A discards the received CP user data.
  • the network element #A sends feedback information to the UE, where the feedback information includes a cause value, where the cause value is used to indicate a reason for rejection or to indicate that a threshold is reached.
  • network element #A if network element #A receives CP service request information, network element #A sends service rejection information to UE, and carries reason value: maximum user data size reached (maximum user data size reached) or maximum information size (maximum information size reached) message size reached); or, if the network element #A receives the uplink NAS transmission information, the network element #A encapsulates the CP user data in the downlink NAS transmission information and sends it back to the UE, and carries the cause value in the downlink NAS transmission information: The maximum user data size reached (maximum user data size reached) or the maximum message size reached (maximum message size reached); or, if network element #A directly receives CP user data, network element #A sends PDU session release command information to UE , release the PDU session associated with the CP user data, and carry the cause value in the PDU session release command information: the maximum user data size reached (maximum user data size reached) or the maximum message size reached (maximum message size reached).
  • the network element #A provides the maximum user data size value to the UE in the feedback information.
  • the UE processes the feedback information according to the cause value.
  • the UE determines not to send CP user data exceeding the maximum user data size to network element #A, and will restrict subsequent transmission to network element #A based on the cause value or the maximum user data size value.
  • the size of CP user data sent by #A is not to send CP user data exceeding the maximum user data size to network element #A, and will restrict subsequent transmission to network element #A based on the cause value or the maximum user data size value. The size of CP user data sent by #A.
  • this application can avoid excessive consumption of network resources by the capacity-reducing terminal device and satisfy the capacity-reducing terminal device. Applicable business requirements of typical vertical industry scenarios, so as to improve communication efficiency and network resource utilization.
  • the method #300 shown in FIG. 3 will be further described below for two cases where the network element #A is an SMF network element or an AMF network element.
  • network element #A is an AMF network element.
  • the UE sends CP plane user data to the AMF network element.
  • the AMF network element processes the user data on the CP plane based on the maximum user data size.
  • the AMF network element checks whether the received CP user data size exceeds the maximum user data size limit of the network for the terminal equipment with reduced capabilities. If the size of the CP user data sent by the UE exceeds the maximum user data size limit of the network for the terminal equipment with reduced capabilities, then:
  • the AMF network element rejects the CP service request information, and discards the received CP user data;
  • the AMF network element If the AMF network element receives the uplink NAS transmission information, the AMF network element sends back the CP user data to the UE.
  • the AMF network element sends feedback information to the UE.
  • the AMF network element sends service rejection information to the UE, and carries the reason value: the maximum user data size reached (maximum user data size reached) or the maximum message size reached (maximum message size reached); or, if the AMF network element receives the uplink NAS transmission information, network element #A encapsulates the CP user data in the downlink NAS transmission information and sends it back to the UE, and carries the cause value in the downlink NAS transmission information: the maximum number of users is reached Data size (maximum user data size reached) or maximum message size reached (maximum message size reached).
  • the AMF network element provides the maximum user data size value to the UE in the service rejection information or downlink NAS transmission information.
  • the UE processes the feedback information according to the cause value.
  • the UE determines not to send CP user data exceeding the maximum user data size to the AMF network element, and will determine based on the cause value or the maximum user data size value Limit the size of the CP user data subsequently sent to the AMF network element.
  • the AMF network element learns or determines that the UE is a terminal device with reduced capability based on the indication information of reduced capability carried by the UE during the first registration process.
  • this application can avoid excessive consumption of network resources by the capacity-reducing terminal device and meet the requirements of the capacity-reducing terminal device. Applicable to the business requirements of typical vertical industry scenarios, so as to improve communication efficiency and network resource utilization.
  • network element #A is an SMF network element.
  • the UE sends CP plane user data to the SMF network element.
  • the UE needs to send uplink CP user data based on the request of the upper layer application.
  • the UE encapsulates the CP user data in a container of the CP service request information (for example: a small data container or a load container) and sends it to the AMF; if the UE is in the connected state, the UE sends the CP
  • the user data is encapsulated in a container (such as a payload container) of uplink NAS transmission information and sent to the AMF.
  • the AMF network element forwards the received CP user data to the SMF network element.
  • the SMF network element processes the user data on the CP plane based on the maximum user data size.
  • the SMF network element checks whether the received CP user data size of the UE exceeds the maximum user data size limit of the network for the terminal equipment with reduced capabilities. If the size of the CP user data sent by the UE exceeds the maximum user data size limit of the network for the terminal equipment with reduced capabilities, the SMF network element discards the received CP user data and releases the corresponding CP PDU session.
  • the SMF network element sends feedback information to the UE.
  • the SMF network element encapsulates the PDU session release command information in the N1 transmission information and sends it to the AMF network element, and carries the cause value in the PDU session release command information: the maximum user data size reached (maximum user data size reached) or reached Maximum message size reached.
  • the AMF network element encapsulates the received PDU session release command information into the downlink NAS transmission information and forwards it to the UE.
  • the SMF network element provides the maximum user data size value to the UE in the PDU session release command information.
  • the UE processes the feedback information according to the cause value.
  • the UE determines not to send CP user data exceeding the maximum user data size to the SMF network element, and will limit subsequent directions based on the cause value or the maximum user data size value.
  • the size of the CP user data sent by the SMF network element is not limited.
  • the SMF network element determines from the AMF network element that the UE is a terminal device with reduced capabilities, for example, when creating the first PDU session, or during the location update registration process triggered by inter-AMF network element (inter-AMF) movement,
  • the AMF network element sends the learned indication information of the UE's ability to support RedCap to the SMF network element; or, the SMF network element obtains the indication information of the UE's ability to support the RedCap directly from the UE through the PDU session establishment request information.
  • this application can avoid excessive consumption of network resources by the capability-reduced terminal device and meet the requirements of the capability-reduced terminal device. Applicable to the business requirements of typical vertical industry scenarios, so as to improve communication efficiency and network resource utilization.
  • Fig. 4 shows a schematic flowchart of a communication control method #400 provided by the present application. The specific content is shown in Figure 4. It should be understood that the execution bodies of the method #400 shown in FIG. 4 are the UPF network element, the SMF network element, and the UE, and the UE is a capability-reduced terminal device.
  • the UE sends user data on a user plane to a UPF network element.
  • the UPF network element receives user data on the user plane (user plane, UP) from the UE.
  • user plane user plane
  • the UE sends UP user data to the UPF network element based on the request of the upper layer application.
  • the UPF network element processes the UP user data based on the maximum user data size.
  • the UPF network element checks whether the size of the received UP user data exceeds the limit of the maximum user data size of the network for the terminal equipment with reduced capabilities. If the size of the user data sent by the UE exceeds the maximum user data size limit of the network for the terminal equipment with reduced capabilities, the UPF network element discards the received user data and reports the information that the maximum user data size has been reached to the SMF network element.
  • the UPF network element sends packet forwarding control protocol session report request information to the SMF network element.
  • the UPF network element determines that the UE's UP data size reaches the limit based on the maximum user data size, the UPF network element sends a packet forwarding control protocol (PFCP) session report request (session report request) to the SMF network element ) information, and carry in the request information: an indication that the maximum user data size limit has been reached.
  • PFCP packet forwarding control protocol
  • the SMF network element releases the PDU session corresponding to the UP user data.
  • the SMF network element decides to release the PDU session corresponding to the UP user data based on the indication information reported by the UPF network element that the maximum user data size limit is reached.
  • the SMF network element sends PDU release command information to the UE.
  • the SMF network element initiates the PDU session release process, that is, sends the PDU session release command information to the UE.
  • the SMF network element encapsulates the PDU session release command information in the N1 transmission information and sends it to the AMF network element.
  • the AMF network element encapsulates the received PDU session release command information into the downlink NAS transmission information and forwards it to the UE.
  • the PDU session release command information carries a cause value: the maximum user data size reached (maximum user data size reached) or the maximum message size reached (maximum message size reached).
  • the SMF network element provides the maximum user data size value to the UE in the PDU session release command information.
  • the UE processes the UP user data based on the cause value.
  • the UE will re-establish the PDU session as needed based on the cause value carried in the feedback information and send UP user data to the UPF network element according to the maximum user data size value provided by the network.
  • the UPF network element learns or determines from the SMF network element that the UE is a terminal device with reduced capabilities
  • the manner in which the SMF network element learns that the UE is a terminal device with reduced capabilities can refer to the foregoing description, and details are not repeated here.
  • this application can avoid the excessive consumption of network resources by the terminal device with reduced capacity, and meet the applicable requirements of the terminal device with reduced capacity.
  • the business requirements of typical vertical industry scenarios can improve communication efficiency and network resource utilization.
  • Fig. 5 is a schematic block diagram of a communication device 500 provided in this application.
  • the communication device 500 may include: a transceiver unit 510 and a processing unit 520 .
  • the communication device 500 may be the UE in the above method embodiment, or may be a chip configured to realize the functions of the UE in the above method embodiment.
  • the communication device 500 may correspond to the UE in the method embodiments of the present application, and the communication device 500 may include a unit for performing the method performed by the UE in the foregoing method embodiments.
  • each unit in the communication device 500 and the above-mentioned other operations and/or functions are respectively intended to implement the corresponding processes in FIG. 2 to FIG. 4 .
  • the communications device 500 can also implement other UE-related steps, actions, or methods in the above method embodiments, which will not be repeated here.
  • the communication device 500 may be the network device in the above method embodiments, for example, an AMF network element, an SMF network element, and a UPF network element, etc., or it may be a The chip of the function of the network device in the method embodiment.
  • the communication device 500 may correspond to the network device in the method embodiment of the present application, and the communication device 500 may include a unit for performing the method performed by the network device in the above method embodiment.
  • transceiver unit 510 in the communication device 500 may correspond to the transceiver 620 in the communication device 600 shown in FIG. 6
  • processing unit 520 in the communication device 500 may correspond to the communication Processor 610 in device 600 .
  • the chip when the communication device 500 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the transceiver unit 510 is used to realize the signal sending and receiving operation of the communication device 500
  • the processing unit 520 is used to realize the signal processing operation of the communication device 500 .
  • the communication device 500 further includes a storage unit 530, and the storage unit 530 is used for storing instructions.
  • Fig. 6 is a schematic block diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device 600 includes: at least one processor 610 and a transceiver 620 .
  • the processor 610 is coupled with the memory for executing instructions stored in the memory to control the transceiver 620 to send signals and/or receive signals.
  • the communications device 600 further includes a memory 630 for storing instructions.
  • processor 610 and the memory 630 may be combined into one processing device, and the processor 610 is configured to execute program codes stored in the memory 630 to implement the above functions.
  • the memory 630 may also be integrated in the processor 610 , or be independent of the processor 610 .
  • the transceiver 620 may include a receiver (or called a receiver) and a transmitter (or called a transmitter).
  • the transceiver 620 may further include antennas, and the number of antennas may be one or more.
  • the transceiver 620 may be a communication interface or an interface circuit.
  • the chip When the communication device 600 is a chip, the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the embodiment of the present application also provides a processing device, including a processor and an interface.
  • the processor may be used to execute the methods in the foregoing method embodiments.
  • the above processing device may be a chip.
  • the processing device may be a field programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC), or a system chip (system on chip, SoC). It can be a central processor unit (CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller unit) , MCU), can also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • microcontroller micro controller unit
  • PLD programmable logic device
  • each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, no detailed description is given here.
  • the embodiment of the present application further provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the network device in the above method embodiment are stored.
  • the computer program when executed by a computer, the computer can implement the method performed by the network device in the foregoing method embodiments.
  • the embodiment of the present application further provides a computer-readable storage medium, on which computer instructions for implementing the method executed by the UE in the foregoing method embodiments are stored.
  • the computer program when executed by a computer, the computer can implement the method performed by the UE in the foregoing method embodiments.
  • the embodiment of the present application also provides a computer program product including an instruction, and when the instruction is executed by a computer, the computer implements the method executed by the UE in the foregoing method embodiment.
  • the embodiment of the present application also provides a computer program product including instructions, and when the instructions are executed by a computer, the computer implements the method executed by the network device in the above method embodiments.
  • the embodiment of the present application also provides a chip system, a processor, which is used to call and run a computer program from the memory, so that the communication device installed with the chip system executes the method that should be executed by the UE, or executes the method that should be executed by the network device. method of execution.
  • the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as the program that records the code of the method provided in the embodiment of the present application can be executed according to the method provided in the embodiment of the present application Just communicate.
  • the subject of execution of the method provided by the embodiment of the present application may be a UE or a network device, or a functional module in the UE or a network device that can call a program and execute the program.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • Usable media may include, but are not limited to, magnetic media or magnetic storage devices (for example, floppy disks, hard disks (such as removable hard disks), magnetic tapes), optical media (for example, optical disks, compact discs, etc.) , CD), digital versatile disc (digital versatile disc, DVD, etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), card, stick or key drive, etc. ), or semiconductor media (such as solid state disk (SSD), U disk, read-only memory (ROM), random access memory (RAM), etc. can store programs The medium of the code.
  • SSD solid state disk
  • ROM read-only memory
  • RAM random access memory
  • Various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile memory and nonvolatile memory.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • RAM can be used as an external cache.
  • RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).
  • static random access memory static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous DRAM
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory
  • Direct memory bus random access memory direct rambus RAM, DR RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module may be integrated in the processor.
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • the disclosed devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the above units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or can be Integrate into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.
  • each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • a computer can be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer can be a personal computer, a server, or a network device, etc.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g. Coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • Coaxial cable, optical fiber, digital subscriber line or wireless (such as infrared, wireless, microwave, etc.)
  • a corresponds to B means that B is associated with A, and B can be determined according to A.
  • determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种通信控制方法和通信设备，该通信控制方法包括：第一网元接收来自能力降低终端设备的请求信息；第一网元基于阈值处理请求信息；第一网元向能力降低终端设备发送反馈信息，反馈信息用于指示第一网元对请求信息的处理结果，并且，该反馈信息包括原因值，这原因值是用于指示拒绝原因或者指示达到阈值。通过由第一网元对来自能力降低终端设备的请求信息进行处理并做出相应的反馈，本申请能够实现避免能力降低终端设备对网络资源的过度消耗，并使其满足其所适用的垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。

Description

一种通信控制方法和通信设备
本申请要求于2021年08月09提交国家知识产权局、申请号为202110908135.8、申请名称为“一种通信控制方法和通信设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，更具体地，涉及一种通信控制方法和通信设备。
背景技术
第五代(5th generation，5G)网络支持三种典型的应用场景：增强移动宽带(enhanced mobile broadband，eMBB)、海量机器类通信(massive machine-type communication，mMTC)和超可靠低时延通信(ultra-reliable and low latency communication，URLLC)。其中，eMBB针对的是传统的用户终端，mMTC和URLLC针对的是面向垂直行业的物联网(internet of things，IoT)终端。
蜂窝物联网(cellular internet of things，CIoT)是一种通过窄带物联网(narrowband internet of things，NB-IoT)接入技术实现物联网终端接入移动通信网络的物联网。在5G网络的初始阶段，物联网终端还是通过传统的NB-IoT空口接入技术接入5G核心网(core network，CN)，新空口(new radio，NR)不支持物联网终端的接入。
第三代合作伙伴项目(3rd generation partnership project，3GPP)在协议版本17(release 17，Rel-17)阶段成立了专门的标准项目来分析并优化现有的5G终端和网络的功能特性来实现5G物联网终端通过5G NR接入5G核心网。在这个标准项目中，3GPP提出了支持能力降低(reduced capability，RedCap)的NR设备，亦即RedCap终端。与传统的eMBB/URLLC设备相比，能力降低终端设备具有成本更低、复杂度低，尺寸更紧凑，性能够用等优势。
然而，如何避免能力降低终端设备对网络资源的过度消耗，并使其满足其所适用的垂直行业场景的业务需求是目前亟待解决的技术问题。
发明内容
本申请提供一种通信控制方法和通信设备，能够用于解决避免能力降低终端对网络资源的过度消耗，并使其满足其所适用的垂直行业场景的业务需求，从而提升通信效率和网络资源利用率。
第一方面，提供了一种通信控制方法，包括：第一网元接收来自能力降低终端设备的请求信息；第一网元基于阈值处理请求信息；第一网元向能力降低终端设备发送反馈信息，该反馈信息是用于指示第一网元对请求信息的处理结果，该反馈信息包括原因值，该原因值是用于指示拒绝原因或者指示达到该阈值。
通过由第一网元对来自能力降低终端设备的请求信息进行处理并做出相应的反馈，本 申请能够实现避免能力降低终端设备对网络资源的过度消耗，并使其满足其所适用的垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
结合第一方面，在第一方面的某些实现方式中，请求信息是注册请求信息或者服务请求信息，阈值是第一位置区域内注册的所述能力降低终端设备数量的最大值，其中，注册请求信息包括能力降低的指示信息。
通过UE在注册流程中向第一网元发送能力降低的指示信息，第一网元基于最大终端设备数量对能力降低终端设备执行控制，并向UE提供拒绝原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
结合第一方面，在第一方面的某些实现方式中，当第一位置区域内在第一网元注册的能力降低终端设备的数量达到该阈值，则该处理结果是第一网元拒绝请求信息，该原因值用于指示达到最大终端设备数量。
结合第一方面，在第一方面的某些实现方式中，第一位置区域包括以下参数的任意一项：能力降低终端设备的跟踪区域、注册区域以及第一网元的服务区域。
结合第一方面，在第一方面的某些实现方式中，请求信息是上行非接入层NAS传输信息或者分组数据单元PDU会话建立请求信息，阈值是PDU会话数量的最大值。
通过第一网元基于最大PDU会话数对能力降低终端设备执行控制，并向UE提供原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
结合第一方面，在第一方面的某些实现方式中，PDU会话建立请求信息包括能力降低的指示信息。
结合第一方面，在第一方面的某些实现方式中，当能力降低终端设备的PDU会话数量达到阈值，处理结果是第一网元拒绝请求信息，原因值用于指示达到最大PDU会话数量。
结合第一方面，在第一方面的某些实现方式中，请求信息是分组数据单元PDU会话修改请求信息，阈值是服务质量流QoS flow数量的最大值，或者，阈值是QoS速率的最大值。
通过由第一网元基于最大QoS flow数量或者QoS速率的最大值处理UE的PDU会话修改请求信息，并向UE提供原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
结合第一方面，在第一方面的某些实现方式中，当能力降低终端设备的QoS flow数量达到阈值，处理结果是第一网元拒绝请求信息，原因值用于指示达到最大QoS flow数量，或者，当能力降低终端设备的PDU会话的QoS flow数量达到阈值，处理结果是第一网元拒绝请求信息，原因值用于指示达到最大QoS flow数量。
结合第一方面，在第一方面的某些实现方式中，当能力降低终端设备的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量达到阈值，处理结果是第一网元接受请求信息，原因值用于指示达到最大QoS flow数量，或者，当能力降低终端设备的PDU会话的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量达到阈值，处理结 果是第一网元接受请求信息，原因值用于指示达到最大QoS flow数量。
结合第一方面，在第一方面的某些实现方式中，当能力降低终端设备的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量大于阈值，处理结果是第一网元拒绝或者接受请求信息，原因值用于指示达到最大QoS flow数量，或者，当能力降低终端设备的PDU会话的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量大于阈值，处理结果是第一网元拒绝或者接受请求信息，原因值用于指示达到最大QoS flow数量。
结合第一方面，在第一方面的某些实现方式中，处理结果是第一网元拒绝请求信息，反馈信息还包括QoS flow数量的最大值。
结合第一方面，在第一方面的某些实现方式中，当能力降低终端设备请求的QoS速率达到阈值，处理结果是第一网元接受请求信息，原因值指示达到最大QoS速率。
结合第一方面，在第一方面的某些实现方式中，当能力降低终端设备请求的QoS速率大于阈值，处理结果是第一网元拒绝或者接受请求信息，原因值用于指示QoS未接受或者达到最大QoS速率。
结合第一方面，在第一方面的某些实现方式中，处理结果是第一网元拒绝请求信息，反馈信息还包括QoS速率的最大值。
结合第一方面，在第一方面的某些实现方式中，第一网元根据能力降低的指示信息确定终端设备为能力降低终端设备。
结合第一方面，在第一方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第二方面，提供了一种通信控制方法，包括：能力降低终端设备向第一网元发送请求信息；能力降低终端设备接收第一网元的反馈信息，该反馈信息是用于指示第一网元对请求信息的处理结果，该反馈信息包括原因值，原因值是用于指示拒绝原因或者指示达到阈值；能力降低终端设备根据原因值处理该反馈信息。
结合第二方面，在第二方面的某些实现方式中，请求信息是以下信息的任意一项：注册请求信息、服务请求信息、上行非接入层NAS传输信息、分组数据单元PDU会话建立请求信息，以及分组数据单元PDU会话修改请求信息，其中，注册请求信息或者PDU会话建立请求信息包括能力降低的指示信息。
结合第二方面，在第二方面的某些实现方式中，请求信息是注册请求信息时，反馈信息是注册拒绝信息，或者，请求信息是服务请求信息时，反馈信息是服务拒绝信息，或者，请求信息是上行NAS传输信息时，反馈信息是下行NAS传输信息，或者，请求信息是PDU会话建立请求信息时，反馈信息是PDU会话建立拒绝信息，或者，请求信息是PDU会话修改请求信息时，反馈信息是PDU会话修改拒绝信息，或者，PDU会话修改命令信息，其中，PDU会话修改拒绝信息还包括：服务质量流QoS flow数量的最大值或者服务质量QoS速率的最大值。
结合第二方面，在第二方面的某些实现方式中，反馈信息是注册拒绝信息，原因值是达到最大终端设备数量；或者，反馈信息是服务拒绝信息，原因值是达到最大终端设备数量；或者，反馈信息是下行NAS传输信息，原因值是达到最大PDU会话数量；或者，反馈信息是PDU会话建立拒绝信息，原因值是达到最大PDU会话数量；或者，反馈信息是PDU会话修改拒绝信息，原因值是达到最大QoS flow数量，或者，达到最大QoS速率， 或者，QoS未接受。
结合第二方面，在第二方面的某些实现方式中，能力降低终端设备根据原因值处理所述反馈信息，包括：原因值是达到最大终端设备数量，能力降低终端设备不再向第一网元发送注册请求信息；或者，原因值是达到最大PDU会话数量，能力降低终端设备不再向第一网元发送PDU会话建立请求信息；或者，原因值是达到最大QoS flow数量，能力降低终端设备不再向第一网元发送所述PDU会话修改请求信息，PDU会话修改请求信息用于建立能力降低终端设备的QoS flow；或者，原因值是达到最大QoS速率或者QoS未接受，能力降低终端设备不再向第一网元发送PDU会话修改请求信息，PDU会话修改请求信息用于请求能力降低终端设备的QoS速率。
结合第二方面，在第二方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第三方面，提供了一种通信控制方法，包括：第一网元接收来自能力降低终端设备的控制面用户数据；第一网元基于阈值处理控制面用户数据，阈值是控制面用户数据的最大值；第一网元向能力降低终端设备发送反馈信息，反馈信息是用于指示第一网元对控制面用户数据的处理结果，该反馈信息包括原因值，该原因值是用于指示拒绝原因。
结合第三方面，在第三方面的某些实现方式中，处理结果是第一网元拒绝控制面用户数据，原因值是用于指示达到或者大于阈值。
结合第三方面，在第三方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第四方面，提供了一种通信控制方法，包括：能力降低终端设备向第一网元发送控制面用户数据；能力降低终端设备接受来自第一网元的反馈信息，反馈信息是用于指示第一网元对控制面用户数据的处理结果，该反馈信息包括原因值，该原因值是用于指示拒绝原因；能力降低终端设备根据原因值处理反馈信息。
结合第四方面，在第四方面的某些实现方式中，处理结果是第一网元拒绝控制面用户数据，原因值是用于指示达到或者大于阈值。
结合第四方面，在第四方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第五方面，提供了一种通信控制方法，包括：用户面功能网元接收来自能力降低终端设备的用户面用户数据；用户面功能网元基于阈值处理用户面用户数据，阈值是用户面用户数据大小的最大值；用户面功能网元向会话管理功能网元发送分组转发控制协议PFCP会话上报请求信息，PFCP会话上报请求信息是用于指示达到或者大于阈值。
第六方面，提供了一种通信控制方法，包括：会话管理功能网元接收来自用户面功能网元的分组转发控制协议PFCP会话上报请求信息，PFCP会话上报请求信息是用于指示达到或者大于阈值，阈值是用户面用户数据的最大值；会话管理功能网元释放与用户面用户数据对应的分组数据单元PDU会话；会话管理功能网元向能力降低终端设备发送PDU释放命令信息，PDU释放命令信息是用于指示释放PDU会话。
第七方面，提供了一种通信控制方法，包括：能力降低终端设备向用户面功能网元发送用户面用户数据；能力降低终端设备接收来自会话管理功能网元的PDU释放命令信息，PDU释放命令信息是用于指示释放PDU会话；能力降低终端设备根据PDU释放命令信 息处理用户面用户数据。
第八方面，提供了一种通信设备，包括：收发单元，用于接收来自能力降低终端设备的请求信息；处理单元，用于基于阈值处理请求信息；收发单元，还用于向能力降低终端设备发送反馈信息，该反馈信息是用于指示第一网元对请求信息的处理结果，该反馈信息包括原因值，该原因值是用于指示拒绝原因或者指示达到该阈值。
结合第八方面，在第八方面的某些实现方式中，请求信息是注册请求信息或者服务请求信息，阈值是第一位置区域内注册的所述能力降低终端设备数量的最大值，其中，注册请求信息包括能力降低的指示信息。
结合第八方面，在第八方面的某些实现方式中，当第一位置区域内在第一网元注册的能力降低终端设备的数量达到该阈值，则该处理结果是第一网元拒绝请求信息，该原因值用于指示达到最大终端设备数量。
结合第八方面，在第八方面的某些实现方式中，第一位置区域包括以下参数的任意一项：能力降低终端设备的跟踪区域、注册区域以及第一网元的服务区域。
结合第八方面，在第八方面的某些实现方式中，请求信息是上行非接入层NAS传输信息或者分组数据单元PDU会话建立请求信息，阈值是PDU会话数量的最大值。
结合第八方面，在第八方面的某些实现方式中，PDU会话建立请求信息包括能力降低的指示信息。
结合第八方面，在第八方面的某些实现方式中，当能力降低终端设备的PDU会话数量达到阈值，处理结果是第一网元拒绝请求信息，原因值用于指示达到最大PDU会话数量。
结合第八方面，在第八方面的某些实现方式中，请求信息是分组数据单元PDU会话修改请求信息，阈值是服务质量流QoS flow数量的最大值，或者，阈值是QoS速率的最大值。
结合第八方面，在第八方面的某些实现方式中，当能力降低终端设备的QoS flow数量达到阈值，处理结果是第一网元拒绝请求信息，原因值用于指示达到最大QoS flow数量，或者，当能力降低终端设备的PDU会话的QoS flow数量达到阈值，处理结果是第一网元拒绝请求信息，原因值用于指示达到最大QoS flow数量。
结合第八方面，在第八方面的某些实现方式中，当能力降低终端设备的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量达到阈值，处理结果是第一网元接受请求信息，原因值用于指示达到最大QoS flow数量，或者，当能力降低终端设备的PDU会话的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量达到阈值，处理结果是第一网元接受请求信息，原因值用于指示达到最大QoS flow数量。
结合第八方面，在第八方面的某些实现方式中，当能力降低终端设备的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量大于阈值，处理结果是第一网元拒绝或者接受请求信息，原因值用于指示达到最大QoS flow数量，或者，当能力降低终端设备的PDU会话的QoS flow数量加上能力降低终端设备请求建立的QoS flow数量大于阈值，处理结果是第一网元拒绝或者接受请求信息，原因值用于指示达到最大QoS flow数量。
结合第八方面，在第八方面的某些实现方式中，处理结果是第一网元拒绝请求信息，反馈信息还包括QoS flow数量的最大值。
结合第八方面，在第八方面的某些实现方式中，当能力降低终端设备请求的QoS速率达到阈值，处理结果是第一网元接受请求信息，原因值指示达到最大QoS速率。
结合第八方面，在第八方面的某些实现方式中，当能力降低终端设备请求的QoS速率大于阈值，处理结果是第一网元拒绝或者接受请求信息，原因值用于指示QoS未接受或者达到最大QoS速率。
结合第八方面，在第八方面的某些实现方式中，处理结果是第一网元拒绝请求信息，反馈信息还包括QoS速率的最大值。
结合第八方面，在第八方面的某些实现方式中，第一网元根据能力降低的指示信息确定终端设备为能力降低终端设备。
结合第八方面，在第八方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第九方面，提供了一种通信设备，包括：收发单元，用于向第一网元发送请求信息；收发单元，还用于接收第一网元的反馈信息，该反馈信息是用于指示第一网元对请求信息的处理结果，该反馈信息包括原因值，原因值是用于指示拒绝原因或者指示达到阈值；处理单元，用于根据原因值处理该反馈信息。
结合第九方面，在第九方面的某些实现方式中，请求信息是以下信息的任意一项：注册请求信息、服务请求信息、上行非接入层NAS传输信息、分组数据单元PDU会话建立请求信息，以及分组数据单元PDU会话修改请求信息，其中，注册请求信息或者PDU会话建立请求信息包括能力降低的指示信息。
结合第九方面，在第九方面的某些实现方式中，请求信息是注册请求信息时，反馈信息是注册拒绝信息，或者，请求信息是服务请求信息时，反馈信息是服务拒绝信息，或者，请求信息是上行NAS传输信息时，反馈信息是下行NAS传输信息，或者，请求信息是PDU会话建立请求信息时，反馈信息是PDU会话建立拒绝信息，或者，请求信息是PDU会话修改请求信息时，反馈信息是PDU会话修改拒绝信息，或者，PDU会话修改命令信息，其中，PDU会话修改拒绝信息还包括：服务质量流QoS flow数量的最大值或者服务质量QoS速率的最大值。
结合第九方面，在第九方面的某些实现方式中，反馈信息是注册拒绝信息，原因值是达到最大终端设备数量；或者，反馈信息是服务拒绝信息，原因值是达到最大终端设备数量；或者，反馈信息是下行NAS传输信息，原因值是达到最大PDU会话数量；或者，反馈信息是PDU会话建立拒绝信息，原因值是达到最大PDU会话数量；或者，反馈信息是PDU会话修改拒绝信息，原因值是达到最大QoS flow数量，或者，达到最大QoS速率，或者，QoS未接受。
结合第九方面，在第九方面的某些实现方式中，原因值是达到最大终端设备数量，该收发单元，还用于不再向第一网元发送注册请求信息；或者，原因值是达到最大PDU会话数量，收发单元，还用于不再向第一网元发送PDU会话建立请求信息；或者，原因值是达到最大QoS flow数量，收发单元，还用于不再向第一网元发送所述PDU会话修改请求信息，PDU会话修改请求信息用于建立能力降低终端设备的QoS flow；或者，原因值是达到最大QoS速率或者QoS未接受，收发单元，还用于不再向第一网元发送PDU会话修改请求信息，PDU会话修改请求信息用于请求能力降低终端设备的QoS速率。
结合第九方面，在第九方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第十方面，提供了一种通信设备，包括：收发单元，用于接收来自能力降低终端设备的控制面用户数据；处理单元，用于基于阈值处理控制面用户数据，阈值是控制面用户数据的最大值；收发单元，还用于向能力降低终端设备发送反馈信息，反馈信息是用于指示第一网元对控制面用户数据的处理结果，该反馈信息包括原因值，该原因值是用于指示拒绝原因。
结合第十方面，在第十方面的某些实现方式中，处理结果是第一网元拒绝控制面用户数据，原因值是用于指示达到或者大于阈值。
结合第十方面，在第十方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第十一方面，提供了一种通信设备，包括：收方单元，用于向第一网元发送控制面用户数据；收方单元，还用于接受来自第一网元的反馈信息，反馈信息是用于指示第一网元对控制面用户数据的处理结果，该反馈信息包括原因值，该原因值是用于指示拒绝原因；处理单元，用于根据原因值处理反馈信息。
结合第十一方面，在第十一方面的某些实现方式中，处理结果是第一网元拒绝控制面用户数据，原因值是用于指示达到或者大于阈值。
结合第十一方面，在第十一方面的某些实现方式中，第一网元是移动管理网元或者会话管理功能网元。
第十二方面，提供了一种通信设备，包括：收发单元，用于接收来自能力降低终端设备的用户面用户数据；处理单元，用于基于阈值处理用户面用户数据，阈值是用户面用户数据大小的最大值；收发单元，还用于向会话管理功能网元发送分组转发控制协议PFCP会话上报请求信息，PFCP会话上报请求信息是用于指示达到或者大于阈值。
第十三方面，提供了一种通信设备，包括：收发单元，用于接收来自用户面功能网元的分组转发控制协议PFCP会话上报请求信息，PFCP会话上报请求信息是用于指示达到或者大于阈值，阈值是用户面用户数据的最大值；处理单元，用于释放与用户面用户数据对应的分组数据单元PDU会话；收发单元，还用于向能力降低终端设备发送PDU释放命令信息，PDU释放命令信息是用于指示释放PDU会话。
第十四方面，提供了一种通信设备，包括：收发单元，用于向用户面功能网元发送用户面用户数据；收发单元，用于接收来自会话管理功能网元的PDU释放命令信息，PDU释放命令信息是用于指示释放PDU会话；处理单元，用于根据PDU释放命令信息处理用户面用户数据。
第十五方面，提供了一种计算机存储介质，存储有指令，当所述指令在计算机上运行时，使得所述计算机执行如第一方面以及第一方面的任一种可能实现方式中所述的通信控制方法，或者，如第三方面以及第三方面的任一种可能实现方式中所述的通信控制方法，或者，如第四方面以及第四方面的任一种可能实现方式中所述的通信控制方法，或者，如第五方面以及第五方面的任一种可能实现方式中所述的通信控制方法，或者，如第六方面以及第六方面的任一种可能实现方式中所述的通信控制方法。
第十六方面，提供了一种计算机存储介质，存储有指令，当所述指令在计算机上运行 时，使得所述计算机执行如第二方面以及第二方面的任一种可能实现方式中所述的通信控制方法，或者，如第七方面以及第七方面的任一种可能实现方式中所述的通信控制方法。
第十七方面，提供了一种计算机程序产品，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如第一方面以及第一方面的任一种可能实现方式中所述的通信控制方法，或者，如第三方面以及第三方面的任一种可能实现方式中所述的通信控制方法，或者，如第四方面以及第四方面的任一种可能实现方式中所述的通信控制方法，或者，如第五方面以及第五方面的任一种可能实现方式中所述的通信控制方法，或者，如第六方面以及第六方面的任一种可能实现方式中所述的通信控制方法。
第十八方面，提供了一种计算机程序产品，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如第二方面以及第二方面的任一种可能实现方式中所述的通信控制方法，或者，如第七方面以及第七方面的任一种可能实现方式中所述的通信控制方法。
附图说明
图1是本申请提供的一种5G系统的架构示意图。
图2是本申请提供的一种通信控制方法的示意流程图。
图3是本申请提供的又一种通信控制方法的示意流程图。
图4是本申请提供的另一种通信控制方法的示意流程图。
图5是本申请提供的一种通信设备的结构框图。
图6是本申请提供的又一种通信设备的结构框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、5G网络或NR，或者未来的通信网络，如第六代(6th generation，6G)网络等。
本申请实施例中的终端设备可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置。终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备或物联网、车辆网中的终端设备、家庭网关(customer premise equipment，CPE)以及未来网络中的任意形态的终端设备等。为便于描述，本申请实施例以用户设备(user equipment，UE)来代指终端设备。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备可以是 GSM系统或CDMA中的基站(base transceiver station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(evolutional NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络或者未来通信网络中的网络设备等等。
图1示出了本申请提供的一种5G系统架构的示意图。具体如图1所示，可以应用本申请的通信方法的应用场景中可以包括UE101、无线接入网(radio access network，RAN)设备102、用户面功能(user plane function，UPF)网元103、接入和移动性管理功能(access and mobility management function，AMF)104、会话管理功能(session management function，SMF)网元105、策略控制功能(policy control function，PCF)网元106、应用功能(application function，AF)网元107、网络切片选择的认证和授权功能(network slice specific authentication and authorization function，NSSAAF)网元108、统一数据管理(unified data management，UDM)网元109、认证授权业务功能(authentication server function，AUSF)网元110、网络切片选择功能(network slice selection function，NSSF)网元111和数据网络(data network，DN)112。
应理解，RAN设备的一种示例是基站(base station，BS)。
基站，也可称为基站设备，是一种将终端设备接入到无线网络的设备，包括但不限于：传输接收点(transmission reception point，TRP)、5G节点B(gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(base band unit，BBU)，或Wifi接入点(access point，AP)，或小基站设备(pico)等。
应理解，本申请对基站的具体类型不作限定。在采用不同无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同。为方便描述，在本申请中，上述为终端设备提供无线通信功能的装置统称为基站。
UPF：可以理解为用户面功能网元在5G架构中的命名。其中，用户面功能网元主要包括以下功能：数据包路由和传输、包检测、业务用量上报、服务质量(quality of service，QoS)处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
AMF：可以理解为移动性管理网元在5G架构中的命名。其中，移动性管理网元主要包括以下功能：连接管理、移动性管理、注册管理、接入认证和授权、可达性管理、安全上下文管理等接入和移动性相关的功能。
SMF：可以理解为会话管理网元在5G架构中的命名。其中，会话管理网元主要进行会话管理、PCF下发控制策略的执行、UPF的选择、UE IP地址分配等功能。
PCF：可以理解为策略控制功能网元在5G架构中的命名。其中，策略控制功能网元主要负责针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、UE策略决策等策略控制功能。该系统中，AMF与SMF所连接的PCF分别是接入和移动控制PCF(PCF for access and mobility control，AM PCF)和SM PCF，在实际部署中AM PCF和SM PCF可能不是同一个PCF实体。
UDM：可以理解为统一数据管理网元在5G架构中的命名。其中，统一数据管理网元 主要包括以下功能：统一数据管理，支持3GPP认证和密钥协商机制中的认证信任状处理，用户身份处理，接入授权，注册和移动性管理，签约管理，短信息管理等。
AUSF：可以理解为认证授权业务功能网元在5G架构中的命名。其中，认证授权业务功能网元负责对终端设备的接入进行认证授权。
DN：数据网络，用于标识运营商网络接入点名称。在本申请中，DN还可包括验证、授权和记账(authentication、authorization、accounting，AAA)服务器功能，负责对用户执行二次鉴权。
AF：可以理解为应用功能网元在5G架构中的命名。其中，应用功能网元主要传递应用侧对网络侧的需求，例如，服务质量(quality of service，QoS)需求等。AF网元可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP multimedia subsystem，IMS)语音呼叫业务。
NSSAAF：可以理解为网络切片选择的认证和授权功能在5G架构中的命名。其中，网络切片选择的认证和授权功能主要用于对终端设备请求的网络切片业务进行认证和授权。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
其中，各接口功能描述如下：
N1：AMF与UE之间的接口，接入无关，用于向UE传递QoS控制规则等。
N2：AMF与RAN之间的接口，用于传递核心网侧至RAN的无线承载控制信息等。
N3：RAN与UPF间的接口，用于在RAN与UPF间传递用户面数据。
N4：SMF与UPF之间的接口，用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
N5：AF与PCF之间的接口，用于应用业务请求下发以及网络事件上报。
N6：UPF与DN连接间的接口，用于在UPF与DN间传递用户面数据。
N7：PCF与SMF之间的接口，用于下发协议数据单元(protocol data unit，PDU)会话粒度以及业务数据流粒度控制策略。
N8：AMF与UDM间的接口，用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。
N9：UPF与UPF间的接口，如拜访地策略控制功能(visited-policy control function，V-PCF)与归属地策略控制功能(home-policy control function，H-PCF)间的接口，或是与DN相连的UPF与RAN相连的UPF间的接口，用于在UPF间传递用户面数据。
N10：SMF与UDM间的接口，用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。
N11：SMF与AMF之间的接口，用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给UE的控制信息、传递发送给RAN的无线资源控制信息等。
N12：AMF与AUSF之间的接口，用于对终端设备进行身份认证。
N13：UDM与AUSF之间的接口，用于传递认证参数以及传递认证结果。
N14：两个AMF之间的接口，用于传递用户上下文以便支持跨AMF的移动。
N15：PCF与AMF之间的接口，用于下发UE策略及接入控制相关策略。
N22：AMF与NSSF之间的接口，用于切片选择以及获取终端允许的切片信息。
N33：NEF与AF之间的接口，用于第三方应用从移动网络获取能力开放信息，以及向移动网络提供应用信息。
N58：AMF与NSSAAF之间的接口，用于执行网络切片选择的认证和授权。
N59：NSSAAF与UDM之间的接口，用于获取用于网络切片选择的认证和授权的用户签约信息。
需要说明的是，图1中包括的各个网元的命名仅是一个名字，名字对网元本身的功能不构成限定。在5G网络以及未来其它的网络中，上述各个网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能是其他命名，等等，在此进行统一说明，以下不再赘述。
应理解，本申请并不限于图1所示的系统架构。例如，可以应用本申请的通信方法的通信系统中可以包括更多或更少的网元或设备。图1中的设备或网元可以是硬件，也可以是从功能上划分的软件或者以上二者的结合。图1中的设备或网元之间可以通过其他设备或网元通信。
需要说明的是，在本申请实施例中，能力降低终端设备与RedCap UE是等同的，为便于描述，本申请实施例采用能力降低终端设备来描述本申请实施例的技术方案。
应理解，能力降低终端设备对于网络的需求是介于传统的NB-IoT/eMTC终端和eMBB/URLLC终端之间，其主要面向的应用场景包括：
1.工业无线传感线网络：需求多样化；无移动性或低速移动性；支持中继relay传输；低功耗；低成本、低复杂度。
2.智慧城市中的视频监控：上行传输为主，上行大带宽；24小时实时在线；无移动性；无省电需求。
3.个人可穿戴智能设备：支持语音、业务连续性；支持中继relay传输；低功耗；低成本、低复杂度。
基于上述应用场景，与传统的eMBB/URLLC终端相比，能力降低终端设备的设备复杂度更低、成本更低、尺寸更紧凑以及性能够用。同时，5G网络需要识别所接入的终端设备为能力降低终端设备，即支持RedCap能力的终端设备。为避免能力降低终端设备对网络资源的过度消耗，5G网络需要对其进行接入控制，并优化5G网络的资源利用，满足其所适用的垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
针对NB-IoT终端的网络资源的接入控制因素有最大用户面(user plane，UP)激活的PDU会话(session)个数。针对eMBB终端的网络资源的接入控制因素有最大PDU会话的连接数。
然而，对于能力降低终端设备而言，基于其所适用的工业无线传感网络和智慧城市中视频监控的业务需求，以及运营商对于网络资源优化的需求，上述方案无法有助于解决5G网络对能力降低终端设备对网络资源的过度消耗，并使其满足其所适用的垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
鉴于上述技术问题，本申请提供了一种通信控制方法和通信设备，能够帮助解决避免 RedCap终端设备对网络资源的过度消耗，并使其满足其所适用的垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
图2示出了本申请提供的一种通信控制方法#200的示意流程图。具体内容如图2所示。应理解，图2所示的方法#200的执行主体为网元#A和UE，UE即为能力降低终端设备。
S210，UE发送请求信息。
对应地，网元#A接收来自UE的请求信息。
应理解，在本申请实施例中，该请求信息可以是注册请求信息、服务请求信息、分组数据单元PDU会话建立请求信息、PDU会话修改请求信息，以及上行非接入层(non access stratum，NAS)传输信息，等等。
S220，网元#A基于阈值处理请求信息。
应理解，该阈值是与该能力降低终端设备发送的请求信息对应的，即该对应关系可以理解为：若请求信息是注册请求信息，阈值是某个位置区域内在该网元#A注册的能力降低终端设备的最大终端设备数量；若请求信息是服务请求信息，阈值亦是某个位置区域内在该网元#A注册的能力降低终端设备的最大终端设备数量；若请求信息是上行NAS传输信息或者PDU会话建立请求信息，阈值是该能力降低终端设备的PDU会话数量的最大值；若请求信息是PDU会话修改请求信息，阈值是该能力降低终端设备的QoS流(flow)数量的最大值，或者是该能力降低终端设备的QoS速率的最大值，后文将对其进行详细描述。
应理解，网元#A基于与请求信息对应的阈值对请求信息进行处理，并确定相应的处理结果。
S230，网元#A发送反馈信息。
应理解，网元#A通过向UE发送反馈信息，从而使UE能够获知网元#A对该请求信息的处理结果，便于UE基于该处理结果确定相应的动作或者行为。
应理解，网元#A基于阈值对请求信息进行处理后，确定了相应的处理结果，该处理结果包括：接受该请求信息或者拒绝该请求信息。
需要说明的是，网元#A发送给UE的反馈信息中会包括原因值(cause value)，这原因值是用于指示拒绝原因或者是用于指示达到阈值。
S240，UE根据原因值处理反馈信息。
示例性地，若网元#A向UE发送的反馈信息指示的是网元#A拒绝该请求信息，并通过所携带的原因值指示拒绝原因，UE会基于原因值对该反馈信息进行处理，例如，不再向网元#A发送该请求信息。
作为一种可能的实现方式，网元#A通过请求信息中包括的能力降低的指示信息确定UE是能力降低终端设备。
通过由网元#A对来自UE发送的请求信息进行处理并确定相应的反馈信息，本申请能够实现网络对能力降低终端设备的控制，继而实现避免能力降低终端设备对网络资源的过度消耗，从而使其满足其所适用的垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
下文将结合请求信息的具体类型对上述方法#200的技术方案做进一步的描述。
第一，请求信息是注册请求信息，网元#A是AMF网元。
S210#A，UE发送注册请求(registration request)信息，该注册请求信息用于请求UE注册到网络。
应理解，该注册请求信息包括能力降低的指示信息，AMF网元基于该指示信息确定UE是能力降低设备。
S220#A，AMF网元基于第一位置区域内注册的能力降低终端设备的最大终端设备数量处理注册请求信息。
AMF网元基于注册请求信息中包括的能力降低的指示信息确定UE是能力降低终端设备，并将其保存在UE的上下文中。
应理解，AMF网元检查在第一位置区域内已经注册的能力降低终端设备的数量是否达到最大终端设备数量。若未达到，AMF网元完成注册流程；若达到，AMF网元拒绝UE的注册请求信息。
该第一位置区域可以包括：
1)UE当前所在的跟踪区域(tracking area，TA)。
2)UE当前所在的注册区域(registration area)，该注册区域包括UE当前所在的TA以及周边的多个TA，形成一个TA列表。
3)AMF网元的整个服务区域(service area)。
S230#A，AMF网元向UE发送注册拒绝(registration reject)信息，该注册拒绝信息包括原因值，原因值是用于指示达到最大终端设备数(maximum number of UEs reached)。
AMF网元确定拒绝UE的注册请求信息时，其会向UE发送注册拒绝信息，并在注册拒绝信息中携带原因值，其用于指示拒绝原因。
S240#A，UE根据注册拒绝信息及原因值，进入去注册状态。
UE获知AMF网元拒绝了UE的注册请求信息之后，其会基于该注册拒绝信息以及原因值，选择不再向AMF网元发送注册请求信息，并进入去注册状态。
通过UE在注册流程中向AMF网元发送能力降低的指示信息，AMF网元基于最大终端设备数量对能力降低终端设备执行控制，并向UE提供拒绝原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
第二，请求信息是服务请求信息，网元#A是AMF网元。
S210#B，UE发送服务请求(service request)信息，该服务请求信息用于请求网络提供服务，比如建立空口用户面资源。
在UE成功注册到网络之后，UE向AMF网元发送服务请求信息，即请求网络提供某种业务或者服务，例如，建立空口用户面资源。
应理解，在UE成功注册到网络之后，UE不需要在服务请求信息中携带能力降低的指示信息，AMF网元能够基于UE在之前的注册请求信息中所携带的能力降低的指示信息确定UE为能力降低终端设备。
S220#B，AMF网元基于第一位置区域内注册的能力降低终端设备的最大终端设备数量处理服务请求信息。
AMF网元检查在第一位置区域内已经注册的能力降低终端设备的数量是否达到最大 终端设备数量。若未达到，AMF网元则继续为该UE提供其所请求的服务；若达到，AMF网元则拒绝UE的服务请求信息，即拒绝为该UE提供其所请求的服务。
关于第一位置区域的内容，可以参考前述内容，在此不再赘述。
S230#B，AMF网元向UE发送服务拒绝(service reject)信息，该服务拒绝信息包括原因值，该原因值是用于指示达到最大终端设备数(maximum number of UEs reached)。
AMF网元确定拒绝UE的服务请求信息时，其会向UE发送服务拒绝信息，并在服务拒绝信息中携带原因值，其用于指示拒绝原因。
S240#B，UE根据服务拒绝信息及原因值，进入去注册状态。
应理解，当UE获知AMF网元拒绝了UE的服务请求信息之后，其会基于该服务拒绝信息以及原因值，不再向AMF网元发送服务请求信息，并进入去注册状态。
作为一种可能的实现方式，AMF网元通过检查第一位置区域内已注册的能力降低终端设备的数量是否已达到最大终端设备数量，并基于该检查结果确定是否需要向UE发送去注册请求(de-registration request)信息。若达到，则AMF网元向UE发送去注册请求信息，该去注册请求信息中包括原因值，该原因值是用于指示达到最大终端设备数，当UE收到该去注册请求信息之后，其会基于该去注册请求信息以及原因值，不再向AMF网元发送注册请求信息，并进入去注册状态。
通过UE在注册流程中向AMF网元发送能力降低的指示信息，AMF网元基于最大终端设备数量对能力降低终端设备执行控制，并向UE提供拒绝原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
第三，请求信息是上行NAS传输信息，网元#A是AMF网元。
S210#C，UE向AMF网元发送上行NAS传输信息，该上行NAS传输信息中包括PDU会话建立请求信息。
具体地，UE基于上层应用的请求发起PDU会话建立请求信息，PDU会话建立请求信息被封装在上行NAS传输信息中发送给AMF网元，该PDU会话建立请求信息用于请求建立新的PDU会话。
S220#C，AMF网元基于最大PDU会话数量处理上行NAS传输信息与PDU会话建立请求信息。
具体而言，AMF网元检查UE的激活态PDU会话数量是否达到最大PDU会话数。若未达到，AMF网元则执行PDU会话建立流程，向SMF网元转发PDU会话建立请求信息；若达到，AMF网元则不向SMF网元转发PDU会话建立请求信息。
S230#C，AMF网元向UE发送下行NAS传输信息，该下行NAS传输信息包括S210#C中收到的PDU会话建立请求信息。
AMF网元确定UE的激活态PDU会话数量达到最大PDU会话数时，其会向UE发送下行NAS传输信息，将从UE收到的PDU会话建立请求信息包括在下行NAS传输信息中发回给UE，并在该下行NAS传输信息中携带原因值，其用于指示拒绝原因，也即发回PDU会话建立请求信息的原因。
应理解，上述的下行NAS传输信息包括原因值，其用于指示达到最大PDU会话数(maximum number of PDU sessions reached)。
S240#C，UE根据下行NAS传输信息及原因值，不再发送PDU会话建立请求信息。
应理解，当UE获知AMF网元发回了UE的PDU会话建立请求信息之后，其会基于下行NAS传输信息以及原因值，不再发送PDU会话建立请求信息。
需要说明的是，AMF网元通过UE在之前的注册流程中所携带的能力降低的指示信息确定UE为能力降低终端设备。
通过AMF网元基于最大PDU会话数对能力降低终端设备执行控制，并向UE提供原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
第四，请求信息是PDU会话建立请求信息，网元#A是SMF网元。
S210#D，UE向SMF网元发送PDU会话建立请求信息。
具体地，UE基于上层应用的请求发起PDU会话建立请求信息，PDU会话建立请求信息被封装在上行NAS传输信息中发送给AMF网元，AMF网元将收到的PDU会话建立请求信息封装在创建PDU session上下文请求信息中发送给SMF网元，该PDU会话建立请求信息用于请求建立新的PDU会话。
S220#D，SMF网元基于最大PDU会话数量处理PDU会话建立请求信息。
具体而言，SMF网元检查UE的激活态PDU会话数量是否达到最大PDU会话数。若未达到，SMF网元则接受PDU会话建立请求信息；若达到，SMF网元则拒绝PDU会话建立请求信息，并向UE发出PDU会话拒绝信息。
S230#D，SMF网元向UE发送PDU会话建立拒绝信息。
SMF网元确定拒绝UE的PDU会话建立请求信息时，其会向UE发送PDU会话建立拒绝信息，并在拒绝信息中携带原因值，其用于指示拒绝原因。
SMF网元将PDU会话建立拒绝信息封装在N1传输信息中发送给AMF网元，AMF网元将该PDU会话建立拒绝信息封装在下行NAS传输信息中转发给UE。
应理解，上述的PDU会话建立拒绝信息包括原因值，其用于指示达到最大PDU会话数(maximum number of PDU sessions reached)。
S240#D，UE根据PDU会话建立拒绝信息及原因值，不再向SMF网元发送PDU会话建立请求信息。
应理解，当UE获知SMF网元拒绝了UE的PDU会话建立请求信息之后，其会基于该PDU会话建立拒绝信息以及原因值，不再向SMF网元发送PDU会话建立请求信息。
应理解，SMF网元从AMF网元处确定UE是能力降低终端设备，例如，在新建第一个PDU会话时，或者在跨AMF网元(inter-AMF)移动触发的位置更新注册流程中，AMF网元将获知的UE支持RedCap能力的指示信息发送给SMF网元，或者，SMF网元获取UE支持RedCap能力的指示信息是从UE通过PDU会话建立请求信息中直接上报的。
通过SMF网元基于最大PDU会话数对能力降低终端设备执行控制，并向UE提供原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
第五，请求信息是PDU会话修改请求信息，用于请求新建至少一个QoS flow，网元#A是SMF网元。
S210#E，UE向SMF网元发送PDU会话修改请求信息。
具体地，UE基于上层应用的请求发起PDU会话修改请求信息，用于请求新建至少一个QoS flow，其中，PDU会话修改请求信息包括新建的至少一个QoS flow信息。PDU会话修改请求信息被封装在上行NAS传输信息中发送给AMF网元。AMF网元将收到的PDU会话修改请求信息封装在更新PDU session上下文请求信息中发送给SMF网元。
S220#E，SMF网元基于最大QoS flow数量处理PDU会话修改请求信息。
应理解，SMF网元基于最大QoS flow数量对UE的PDU会话修改请求信息有两种处理方式：
方式一：能力降低终端设备在SMF网元处建立的QoS flow数量已达到了最大QoS flow数量，或者，能力降低终端设备在SMF网元处建立的QoS flow数量未达到最大QoS flow数量，但是加上新请求的QoS flow数量则超过了最大QoS flow数量，则SMF网元拒绝UE的PDU会话修改请求信息。
方式二：能力降低终端设备在SMF网元处建立的QoS flow数量未达到最大QoS flow数量，但是加上新请求的QoS flow数量达到或者超过了最大QoS flow数量，SMF网元接收全部或部分请求的QoS flow，则SMF网元接受UE的PDU session修改请求信息。
S230#E，SMF网元向UE发送PDU会话修改拒绝信息或者PDU会话修改命令信息。
根据不同的处理方式，SMF网元向UE发送的反馈信息有两种形式：
形式#1：SMF网元拒绝UE的PDU会话修改信息，SMF网元将PDU会话修改拒绝信息
封装在N1传输信息中发送给AMF网元，且该PDU会话修改拒绝信息包括原因值，其指示达到UE最大QoS flow数(maximum number of QoS flows reached per UE)，或者，达到PDU session最大QoS flow数(maximum number of QoS flows reached per PDU session)。AMF网元将收到的PDU会话修改拒绝信息封装在下行NAS传输信息中并转发给UE。
形式#2：SMF网元接受PDU会话修改信息，SMF网元将PDU会话修改命令(PDU session modification command)信息封装在N1传输信息中发送给AMF网元，且该PDU会话修改命令信息包括原因值，其指示达到UE最大QoS flow数(maximum number of QoS flows reached per UE)，或者，达到PDU session最大QoS flow数(maximum number of QoS flows reached per PDU session)。AMF网元将收到的PDU会话修改命令信息封装在下行NAS传输信息中并转发给UE。
作为一种可能的实现方式，SMF网元可以在PDU会话修改拒绝信息或者PDU会话修改命令信息中携带UE最大QoS flow数或者PDU session最大QoS flow数或者最大QoS flow数。
应理解，在上述所述的场景中，SMF网元基于处理的阈值，即最大QoS flow数量对应于两个处理粒度，一个处理粒度是基于UE层面判断是否达到最大QoS flow数量的限制，即一个UE所能建立的最大QoS flow数量，对应的原因值指示达到UE最大QoS flow数(maximum number of QoS flows reached per UE)。另一个处理粒度是基于UE的一个PDU会话层面判断是否达到最大QoS flow数量，即UE的一个PDU会话所能包括的最大QoS flow数量，对应的原因值指示达到PDU session最大QoS flow数(maximum number of QoS flows reached per PDU session)。
作为一种可能的实现方式，对于两个处理粒度，SMF网元统一提供相同的原因值， 其用于指示达到最大QoS flow数(maximum number of QoS flows reached)，UE根据与网络约定的策略，将收到的原因值理解为达到UE最大QoS flow数或者达到PDU session最大QoS flow数。
S240#E，UE不再向SMF网元发送PDU会话修改请求信息。
UE基于PDU会话修改拒绝信息或者PDU会话修改命令信息中所包括的原因值，确定不再向AMF网元发送PDU会话建立请求信息，从而不再请求新建QoS flow。
需要说明的是，SMF网元从AMF网元处确定UE是能力降低终端设备，例如，在新建第一个PDU会话时，或者在inter-AMF移动触发的位置更新注册流程中，AMF将获知的UE支持RedCap能力的指示信息发送给SMF网元，或者，SMF网元获取UE支持RedCap能力的指示信息是从UE通过PDU会话建立请求信息中直接上报的。
通过由SMF网元基于最大QoS flow数量处理UE的PDU会话修改请求信息，并向UE提供原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
第六，请求信息是PDU会话修改请求信息，用于请求修改至少一个QoS flow的QoS速率，网元#A是SMF网元。
S210#F，UE向SMF网元发送PDU会话修改请求信息。
具体地，UE基于上层应用的请求发起PDU会话修改请求信息请求修改至少一个QoS flow的QoS速率。PDU会话修改请求信息被封装在上行NAS传输信息中发送给AMF网元。AMF网元将收到的PDU会话修改请求信息封装在更新PDU session上下文请求信息中发送给SMF网元。
S220#F，SMF网元基于最大QoS速率处理PDU会话修改请求信息。
SMF网元检查UE请求的QoS速率是否超过网络对于能力降低终端设备的最大QoS速率限制。若UE请求的QoS速率超过了网络对于能力降低终端设备的最大QoS速率，且SMF网元拒绝UE的QoS速率请求，则SMF网元拒绝UE的PDU会话修改请求，或者，若UE请求的QoS速率达到或者超过了网络对于能力降低终端设备的最大QoS速率，但是SMF网元决定为UE分配最大的QoS速率，则SMF网元接受UE的PDU会话修改请求。
S230#F，SMF网元向UE发送PDU会话修改拒绝信息或者PDU会话修改命令信息。
应理解，根据不同的处理方式，SMF网元向UE发送的反馈信息则有两种形式：
形式#3：若SMF网元拒绝UE的PDU会话修改信息，SMF网元则将PDU会话修改拒绝信息封装在N1传输信息中发送给AMF网元，且该信息包括原因值，其指示达到最大QoS速率(maximum rate of QoS flows reached)或者指示QoS未接受(QoS not accepted)。AMF网元将收到的PDU会话修改拒绝信息封装在下行NAS传输信息中并转发给UE。
形式#4：若SMF网元接受UE的PDU会话修改信息，SMF网元将PDU会话修改命令(PDU session modification command)信息封装在N1传输信息中发送给AMF网元，且该信息包括原因值，其指示达到最大QoS速率(maximum rate of QoS flows reached)或者指示QoS未接受(QoS not accepted)。AMF网元将收到的PDU会话修改命令信息封装在下行NAS传输信息中并转发给UE。
作为一种可能的实现方式，SMF网元可以在PDU会话修改拒绝信息或者PDU会话修改命令信息中携带最大QoS速率。
S240#F，UE不再向SMF网元发送PDU会话修改请求信息。
应理解，UE基于SMF网元发送的反馈信息以及原因值，不再向SMF网元请求大于网络下发的最大QoS速率的速率。
应理解，SMF网元从AMF网元处确定UE是能力降低终端设备，例如，在新建第一个PDU会话时，或者在跨AMF网元(inter-AMF)移动触发的位置更新注册流程中，AMF网元网元将获知的UE支持RedCap能力的指示信息发送给SMF网元，或者，SMF网元获取UE支持RedCap能力的指示信息是从UE通过PDU会话建立请求信息中直接上报的。
通过由SMF网元基于最大QoS速率处理UE的PDU会话修改请求信息，并向UE提供原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
图3示出了本申请提供的一种通信控制方法#300的示意流程图。具体内容如图3所示。应理解，图3所示的方法#300的执行主体为网元#A和UE，UE即为能力降低终端设备。
S310，UE向网元#A发送控制面用户数据。
具体地，UE基于上层应用的请求需要发送上行控制面(control plane，CP)用户数据。其中，若UE处于空闲态，则UE将CP用户数据封装在控制面业务请求(control plane service request)信息的一个容器(比如，小数据容器(small data container)或载荷容器(payload container))中；或者，若UE处于连接态，则UE将CP用户数据封装在上行NAS传输信息的一个容器(比如，载荷容器)中。
对应地，网元#A接收来自UE的CP用户数据。
S320，网元#A基于阈值处理CP用户数据。
具体地，网元#A检查所接收的CP用户数据大小是否超过了网络对于能力降低终端设备的最大用户数据大小限制。若UE发送的CP用户数据大小超过了网络对于能力降低终端设备的最大用户数据大小限制，则：
a)若网元#A收到CP业务请求信息，网元#A则拒绝该CP业务请求信息，并丢弃接收到的CP用户数据；
b)若网元#A收到上行NAS传输信息，网元#A则将CP用户数据发回给UE；
c)若网元#A直接收到CP用户数据，网元#A则丢弃接收到的CP用户数据。
S330，网元#A向UE发送反馈信息，该反馈信息包括原因值，该原因值用于指示拒绝原因或者用于指示达到阈值。
具体地，若网元#A收到CP业务请求信息，网元#A发送服务拒绝信息给UE，并携带原因值：达到最大用户数据大小(maximum user data size reached)或者达到最大信息大小(maximum message size reached)；或者，若网元#A收到上行NAS传输信息，网元#A将CP用户数据封装在下行NAS传输信息中发回给UE，并在下行NAS传输信息中携带原因值：达到最大用户数据大小(maximum user data size reached)或者达到最大信息大小(maximum message size reached)；或者，若网元#A直接收到CP用户数据，网元#A发送PDU会话释放命令信息给UE，释放该CP用户数据所关联的PDU会话，并在PDU会 话释放命令信息中携带原因值：达到最大用户数据大小(maximum user data size reached)或者达到最大信息大小(maximum message size reached)。
可选地，网元#A在反馈信息中提供最大用户数据大小值给UE。
S340，UE根据原因值处理反馈信息。
应理解，UE基于反馈信息中所包括的原因值，确定不再向网元#A发送超过最大用户数据大小的CP用户数据，并会基于原因值或最大用户数据大小值来限制后续向网元#A发送的CP用户数据的大小。
通过由网元#A基于最大CP面用户数据大小执行对能力降低终端设备的控制，并向UE提供原因值，本申请能够实现避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
下文将对网元#A为SMF网元或者AMF网元两种情况对图3所示的方法#300做进一步的描述。
第一，网元#A是AMF网元。
S310#A，UE向AMF网元发送CP面用户数据。
应理解，具体发送过程可以参考前述内容，在此不再赘述。
S320#A，AMF网元基于最大用户数据大小处理CP面用户数据。
具体地，AMF网元检查所接收的CP用户数据大小是否超过了网络对于能力降低终端设备的最大用户数据大小限制。若UE发送的CP用户数据大小超过了网络对于能力降低终端设备的最大用户数据大小限制，则：
a)若AMF网元收到CP业务请求信息，AMF网元拒绝该CP业务请求信息，并丢弃接收到的CP用户数据；
b)若AMF网元收到上行NAS传输信息，AMF网元将CP用户数据发回给UE。
S330#A，AMF网元向UE发送反馈信息。
具体地，若AMF网元收到CP业务请求信息，AMF网元向UE发送服务拒绝信息，并携带原因值：达到最大用户数据大小(maximum user data size reached)或者达到最大信息大小(maximum message size reached)；或者，若AMF网元收到上行NAS传输信息，网元#A将CP用户数据封装在下行NAS传输信息中发回给UE，并在下行NAS传输信息中携带原因值：达到最大用户数据大小(maximum user data size reached)或者达到最大信息大小(maximum message size reached)。
可选地，AMF网元在服务拒绝信息或者下行NAS传输信息中提供最大用户数据大小值给UE。
S340#A，UE根据原因值处理反馈信息。
应理解，UE基于服务拒绝信息或者下行NAS传输信息中所包括的原因值，确定不再向AMF网元发送超过最大用户数据大小的CP用户数据，并会基于原因值或最大用户数据大小值来限制后续向AMF网元发送的CP用户数据的大小。
需要说明的是，AMF网元获知或者确定UE为能力降低终端设备是基于UE在第一次注册过程中所携带的能力降低的指示信息而获知的。
通过由AMF网元基于最大CP面用户数据大小执行对能力降低终端设备的控制，并 向UE提供原因值，本申请能够实现避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
第二，网元#A是SMF网元。
S310#B，UE向SMF网元发送CP面用户数据。
应理解，UE基于上层应用的请求需要发送上行CP用户数据。示例性地，若UE处于空闲态，则UE将CP用户数据封装在CP业务请求信息的一个容器(比如：小数据容器或载荷容器)中发送给AMF；若UE处于连接态，则UE将CP用户数据封装在上行NAS传输信息的一个容器(比如：载荷容器)中发送给AMF。
AMF网元将接收到的CP用户数据转发给SMF网元。
S320#B，SMF网元基于最大用户数据大小处理CP面用户数据。
具体地，SMF网元检查所接收的UE的CP用户数据大小是否超过了网络对于能力降低终端设备的最大用户数据大小限制。若UE发送的CP用户数据大小超过了网络对于能力降低终端设备的最大用户数据大小限制，则SMF网元丢弃接收到的CP用户数据，并释放对应的CP PDU session。
S330#B，SMF网元向UE发送反馈信息。
具体地，SMF网元将PDU会话释放命令信息封装在N1传输信息中发送给AMF网元，并在PDU会话释放命令信息中携带原因值：达到最大用户数据大小(maximum user data size reached)或达到最大信息大小(maximum message size reached)。AMF网元将收到的PDU会话释放命令信息封装在下行NAS传输信息中转发给UE。
可选地，SMF网元在PDU会话释放命令信息中提供最大用户数据大小值给UE。
S340#B，UE根据原因值处理反馈信息。
应理解，UE基于PDU会话释放命令信息中所包括的原因值，确定不再向SMF网元发送超过最大用户数据大小的CP用户数据，并会基于原因值或最大用户数据大小值来限制后续向SMF网元发送的CP用户数据的大小。
应理解，SMF网元从AMF网元处确定UE是能力降低终端设备，例如，在新建第一个PDU会话时，或者在跨AMF网元(inter-AMF)移动触发的位置更新注册流程中，AMF网元将获知的UE支持RedCap能力的指示信息发送给SMF网元；或者，SMF网元获取UE支持RedCap能力的指示信息是从UE通过PDU会话建立请求信息中直接上报的。
通过由SMF网元基于最大CP面用户数据大小执行对能力降低终端设备的控制，并向UE提供原因值，本申请能够实现避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
图4示出了本申请提供的一种通信控制方法#400的示意流程图。具体内容如图4所示。应理解，图4所示的方法#400的执行主体为UPF网元、SMF网元和UE，UE即为能力降低终端设备。
S410，UE向UPF网元发送用户面用户数据。
对应地，UPF网元接收来自UE的用户面(user plane，UP)用户数据。
具体地，UE基于上层应用的请求向UPF网元发送UP用户数据。
S420，UPF网元基于最大用户数据大小处理UP用户数据。
具体地，UPF网元检查所接收的UP用户数据大小是否超过了网络对于能力降低终端设备的最大用户数据大小限制。若UE发送的用户数据大小超过了网络对于能力降低终端设备的最大用户数据大小限制，则UPF网元丢弃接收到的用户数据，并向SMF网元上报达到最大用户数据大小的信息。
S430，UPF网元向SMF网元发送分组转发控制协议会话上报请求信息。
应理解，若UPF网元基于最大用户数据大小确定UE的UP数据大小达到该限制，则UPF网元向SMF网元发送分组转发控制协议(packet forwarding control protocol，PFCP)会话上报请求(session report request)信息，并在该请求信息中携带：达到最大用户数据大小限制指示。
S440，SMF网元释放与UP用户数据对应的PDU会话。
应理解，SMF网元基于UPF网元上报的达到最大用户数据大小限制的指示信息，决定释放与UP用户数据对应的PDU会话。
S450，SMF网元向UE发送PDU释放命令信息。
具体地，SMF网元发起PDU session释放流程，也即向UE发送PDU会话释放命令信息。其中，SMF网元将PDU会话释放命令信息封装在N1传输信息中并发送给AMF网元。AMF网元将收到的PDU会话释放命令信息封装在下行NAS传输信息中转发给UE。其中，PDU会话释放命令信息中携带原因值：达到最大用户数据大小(maximum user data size reached)或者达到最大信息大小(maximum message size reached)。
可选地，SMF网元在PDU会话释放命令信息中向UE提供最大用户数据大小值。
S460，UE基于原因值处理UP用户数据。
应理解，UE将基于反馈信息中所携带的原因值按需重新建立PDU会话并按照网络提供的最大用户数据大小值向UPF网元发送UP用户数据。
应理解，UPF网元是从SMF网元处获知或者确定UE为能力降低终端设备，且SMF网元获知UE为能力降低终端设备的方式可以参考前述描述，在此不再赘述。
通过由UPF网元和SMF网元基于最大UP面用户数据大小对UE进行控制，并向UE提供原因值，本申请能够避免能力降低终端设备对于网络资源的过度消耗，满足能力降低终端设备所适用的典型垂直行业场景的业务需求，从而能够提升通信效率和网络资源利用率。
下面将结合附图，对本申请中的通信设备进行描述。
图5是本申请提供的通信设备500的示意性框图。如图所示，该通信设备500可以包括：收发单元510和处理单元520。
在一种可能的设计中，该通信设备500可以是上文方法实施例中的UE，也可以是用于实现上文方法实施例中UE的功能的芯片。
应理解，该通信设备500可对应于本申请方法实施例中的UE，该通信设备500可以包括用于执行前述方法实施例中UE执行的方法的单元。
应理解，该通信设备500中的各单元和上述其他操作和/或功能分别为了实现图2至图4中的相应流程。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为 了简洁，在此不再赘述。
应理解，上述内容仅作为示例性理解，该通信设备500还能够实现上述方法实施例中的其他与UE相关的步骤、动作或者方法，在此不再赘述。
在另一种可能的设计中，该通信设备500可以是上文方法实施例中的网络设备，例如，AMF网元、SMF网元和UPF网元，等等，也可以是用于实现上文方法实施例中网络设备的功能的芯片。
应理解，该通信设备500可对应于本申请方法实施例中的网络设备，该通信设备500可以包括用于执行上述方法实施例中由网络设备执行的方法的单元。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信设备500中的收发单元510可对应于图6中示出的通信设备600中的收发器620，该通信设备500中的处理单元520可对应于图6中示出的通信设备600中的处理器610。
还应理解，当该通信设备500为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
收发单元510用于实现通信设备500的信号的收发操作，处理单元520用于实现通信设备500的信号的处理操作。
可选地，该通信设备500还包括存储单元530，该存储单元530用于存储指令。
图6是本申请实施例提供的通信设备600的示意性框图。如图所示，该通信设备600包括：至少一个处理器610和收发器620。该处理器610与存储器耦合，用于执行存储器中存储的指令，以控制收发器620发送信号和/或接收信号。
可选地，该通信设备600还包括存储器630，用于存储指令。
应理解，上述处理器610和存储器630可以合成一个处理装置，处理器610用于执行存储器630中存储的程序代码来实现上述功能。具体实现时，该存储器630也可以集成在处理器610中，或者独立于处理器610。
还应理解，收发器620可以包括接收器(或者称，接收机)和发射器(或者称，发射机)。
收发器620还可以进一步包括天线，天线的数量可以为一个或多个。收发器620有可以是通信接口或者接口电路。
当该通信设备600为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供了一种处理装置，包括处理器和接口。所述处理器可用于执行上述方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated  circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由网络设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由UE执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由UE执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由UE执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由网络设备执行的方法。
本申请实施例还提供一种芯片系统，处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片系统的通信设备执行由UE应该执行的方法，或者，执行由网络设备应该执行的方法。
所属领域的技术人员可以清楚地了解到，为描述方便和简洁，上述提供的任一种通信装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构进行特别限定，只要能够通过运行记录有本申请实施例提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可。例如，本申请实施例提供的方法的执行主体可以是UE或网络设备，或者，是UE或网络设备中能够调用程序并执行程序的功能模块。
本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本文中使用的术语“制品”可以涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。
其中，计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质(或者说计算机可读介质)例如可以包括但不限于：磁性介质或磁存储器件(例如，软盘、硬盘(如移动硬盘)、磁带)、光介质(例如，光盘、压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)、智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable  read-only memory，EPROM)、卡、棒或钥匙驱动器等)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等、U盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)等各种可以存储程序代码的介质。
本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可以包括但不限于：无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM可以包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，上述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元实现本申请提供的方案。
另外，在本申请各个实施例中的各功能单元可以集成在一个单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。
当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，计算机可以是个人计算机，服务器，或者网络设备等。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向 另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。关于计算机可读存储介质，可以参考上文描述。
应理解，在本申请实施例中，编号“第一”、“第二”…仅仅为了区分不同的对象。比如，为了区分不同的网络设备，并不对本申请实施例的范围构成限制，本申请实施例并不限于此。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下网元会做出相应的处理，并非是限定时间，且也不要求网元实现时一定要有判断的动作，也不意味着存在其它限定。
还应理解，在本申请各实施例中，“A对应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (29)

  1. 一种通信控制方法，其特征在于，包括：
    第一网元接收来自能力降低终端设备的请求信息；
    所述第一网元基于阈值处理所述请求信息；
    所述第一网元向所述能力降低终端设备发送反馈信息，所述反馈信息指示所述第一网元对所述请求信息的处理结果，所述反馈信息包括原因值，所述原因值指示拒绝原因或者指示达到所述阈值。
  2. 根据权利要求1所述的方法，其特征在于，
    所述请求信息是注册请求信息或者服务请求信息，所述阈值是第一位置区域内注册的所述能力降低终端设备数量的最大值，
    其中，所述注册请求信息包括能力降低的指示信息。
  3. 根据权利要求2所述的方法，其特征在于，
    当所述第一位置区域内在所述第一网元注册的所述能力降低终端设备的数量达到所述阈值，所述处理结果是所述第一网元拒绝所述请求信息，所述原因值指示达到最大终端设备数量。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第一位置区域包括以下参数的任意一项：
    所述能力降低终端设备的跟踪区域、注册区域以及所述第一网元的服务区域。
  5. 根据权利要求1所述的方法，其特征在于，
    所述请求信息是上行非接入层NAS传输信息或者分组数据单元PDU会话建立请求信息，所述阈值是PDU会话数量的最大值。
  6. 根据权利要求5所述的方法，其特征在于，
    所述PDU会话建立请求信息包括能力降低的指示信息。
  7. 根据权利要求5或6所述的方法，其特征在于，
    当所述能力降低终端设备的PDU会话数量达到所述阈值，所述处理结果是所述第一网元拒绝所述请求信息，所述原因值指示达到最大PDU会话数量。
  8. 根据权利要求1所述的方法，其特征在于，
    所述请求信息是分组数据单元PDU会话修改请求信息，所述阈值是服务质量流QoS flow数量的最大值，或者，
    所述阈值是QoS速率的最大值。
  9. 根据权利要求8所述的方法，其特征在于，
    当所述能力降低终端设备的QoS flow数量达到所述阈值，所述处理结果是所述第一网元拒绝所述请求信息，所述原因值指示达到最大QoS flow数量，或者，
    当所述能力降低终端设备的PDU会话的QoS flow数量达到所述阈值，所述处理结果是所述第一网元拒绝所述请求信息，所述原因值指示达到最大QoS flow数量。
  10. 根据权利要求8所述的方法，其特征在于，
    当所述能力降低终端设备的QoS flow数量加上所述能力降低终端设备请求建立的 QoS flow数量达到所述阈值，所述处理结果是所述第一网元接受所述请求信息，所述原因值指示达到最大QoS flow数量，或者，
    当所述能力降低终端设备的PDU会话的QoS flow数量加上所述能力降低终端设备请求建立的QoS flow数量达到所述阈值，所述处理结果是所述第一网元接受所述请求信息，所述原因值指示达到最大QoS flow数量。
  11. 根据权利要求8所述的方法，其特征在于，
    当所述能力降低终端设备的QoS flow数量加上所述能力降低终端设备请求建立的QoS flow数量大于所述阈值，所述处理结果是所述第一网元拒绝或者接受所述请求信息，所述原因值指示达到最大QoS flow数量，或者，
    当所述能力降低终端设备的PDU会话的QoS flow数量加上所述能力降低终端设备请求建立的QoS flow数量大于所述阈值，所述处理结果是所述第一网元拒绝或者接受所述请求信息，所述原因值指示达到最大QoS flow数量。
  12. 根据权利要求9或11所述的方法，其特征在于，
    所述处理结果是所述第一网元拒绝所述请求信息，所述反馈信息还包括QoS flow数量的最大值。
  13. 根据权利要求8所述的方法，其特征在于，
    当所述能力降低终端设备请求的QoS速率达到所述阈值，所述处理结果是所述第一网元接受所述请求信息，所述原因值指示达到最大QoS速率。
  14. 根据权利要求8所述的方法，其特征在于，
    当所述能力降低终端设备请求的QoS速率大于所述阈值，所述处理结果是所述第一网元拒绝或者接受所述请求信息，所述原因值指示QoS未接受或者达到最大QoS速率。
  15. 根据权利要求14所述的方法，其特征在于，
    所述处理结果是所述第一网元拒绝所述请求信息，所述反馈信息还包括QoS速率的最大值。
  16. 根据权利要求2或6所述的方法，其特征在于，
    所述第一网元根据所述能力降低的指示信息确定终端设备为所述能力降低终端设备。
  17. 根据权利要求1至16任一项所述的方法，其特征在于，
    所述第一网元是移动管理网元或者会话管理网元。
  18. 一种通信控制方法，其特征在于，包括：
    能力降低终端设备向第一网元发送请求信息；
    所述能力降低终端设备接收所述第一网元的反馈信息，所述反馈信息指示所述第一网元对所述请求信息的处理结果，所述反馈信息包括原因值，所述原因值指示拒绝原因或者指示达到所述阈值；
    所述能力降低终端设备根据所述原因值处理所述反馈信息。
  19. 根据权利要求18所述的方法，其特征在于，所述请求信息是以下信息的任意一项：
    注册请求信息、服务请求信息、上行非接入层NAS传输信息、分组数据单元PDU会话建立请求信息，以及分组数据单元PDU会话修改请求信息，
    其中，所述注册请求信息或者所述PDU会话建立请求信息包括能力降低的指示信息。
  20. 根据权利要求19所述的方法，其特征在于，
    所述请求信息是所述注册请求信息时，所述反馈信息是注册拒绝信息，或者，
    所述请求信息是所述服务请求信息时，所述反馈信息是服务拒绝信息，或者，
    所述请求信息是所述上行NAS传输信息时，所述反馈信息是下行NAS传输信息，或者，
    所述请求信息是所述PDU会话建立请求信息时，所述反馈信息是PDU会话建立拒绝信息，或者，
    所述请求信息是所述PDU会话修改请求信息时，所述反馈信息是PDU会话修改拒绝信息，或者，PDU会话修改命令信息，
    其中，所述PDU会话修改拒绝信息还包括：服务质量流QoS flow数量的最大值或者服务质量QoS速率的最大值。
  21. 根据权利要求20所述的方法，其特征在于，
    所述反馈信息是注册拒绝信息，所述原因值是达到最大终端设备数量；或者，
    所述反馈信息是服务拒绝信息，所述原因值是达到最大终端设备数量；或者，
    所述反馈信息是下行NAS传输信息，所述原因值是达到最大PDU会话数量；或者，
    所述反馈信息是PDU会话建立拒绝信息，所述原因值是达到最大PDU会话数量；或者，
    所述反馈信息是PDU会话修改拒绝信息，所述原因值是达到最大QoS flow数量，或者，达到最大QoS速率，或者，QoS未接受。
  22. 根据权利要求21所述的方法，其特征在于，所述能力降低终端设备根据所述原因值处理所述反馈信息，包括：
    所述原因值是达到最大终端设备数量，所述能力降低终端设备不再向所述第一网元发送所述注册请求信息；或者，
    所述原因值是达到最大PDU会话数量，所述能力降低终端设备不再向所述第一网元发送所述PDU会话建立请求信息；或者，
    所述原因值是达到最大QoS flow数量，所述能力降低终端设备不再向所述第一网元发送所述PDU会话修改请求信息，所述PDU会话修改请求信息用于建立所述能力降低终端设备的QoS flow；或者，
    所述原因值是达到最大QoS速率或者QoS未接受，所述能力降低终端设备不再向所述第一网元发送所述PDU会话修改请求信息，所述PDU会话修改请求信息用于请求所述能力降低终端设备的QoS速率。
  23. 根据权利要求18至22任一项所述的方法，其特征在于，
    所述第一网元是移动管理网元或者会话管理网元。
  24. 一种通信设备，其特征在于，包括至少一个处理器，所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述通信设备执行如权利要求1至17中任一项所述的通信方法。
  25. 一种通信设备，其特征在于，包括至少一个处理器，所述至少一个处理器，用于执行存储器中存储的计算机程序，以使得所述通信设备执行如权利要求18至23中任一项所述的通信方法。
  26. 一种计算机存储介质，其特征在于，存储有指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1至17中任一项所述的通信方法。
  27. 一种计算机存储介质，其特征在于，存储有指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求18至23中任一项所述的通信方法。
  28. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求1至17中任一项所述的方法。
  29. 一种计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得所述计算机执行如权利要求18至23中任一项所述的方法。
PCT/CN2022/092582 2021-08-09 2022-05-13 一种通信控制方法和通信设备 WO2023016006A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110908135.8 2021-08-09
CN202110908135.8A CN113795019B (zh) 2021-08-09 2021-08-09 一种通信控制方法和通信设备

Publications (1)

Publication Number Publication Date
WO2023016006A1 true WO2023016006A1 (zh) 2023-02-16

Family

ID=79181558

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/092582 WO2023016006A1 (zh) 2021-08-09 2022-05-13 一种通信控制方法和通信设备

Country Status (2)

Country Link
CN (1) CN113795019B (zh)
WO (1) WO2023016006A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113795019B (zh) * 2021-08-09 2022-12-30 华为技术有限公司 一种通信控制方法和通信设备
CN114448946A (zh) * 2022-01-25 2022-05-06 重庆智铸华信科技有限公司 一种ims业务处理方法、装置、系统设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210235339A1 (en) * 2020-01-28 2021-07-29 Alireza Babaei Wireless Device and Wireless Network Processes Based on Wireless Device Type
CN113795019A (zh) * 2021-08-09 2021-12-14 华为技术有限公司 一种通信控制方法和通信设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102264118B (zh) * 2010-05-25 2016-06-08 中兴通讯股份有限公司 一种实现mtc终端接入的方法及系统
CN102448117B (zh) * 2010-09-30 2016-04-13 电信科学技术研究院 一种负荷控制的方法和设备
US10117279B2 (en) * 2014-10-17 2018-10-30 Mediatek Inc. Method for maintenance of maximum number of bearers when maximum number of bearers reached
KR102370267B1 (ko) * 2017-10-20 2022-03-03 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 데이터 전송 방법, 단말 기기 및 네트워크 기기
CN112369057A (zh) * 2018-05-18 2021-02-12 联想（新加坡）私人有限公司 5g系统中的ue无线电能力更新
KR102653811B1 (ko) * 2019-01-15 2024-04-03 삼성전자 주식회사 차세대 이동통신 시스템에서 단말의 단말 능력 보고 방법 및 장치
CN112771903B (zh) * 2019-01-31 2022-06-28 华为技术有限公司 用于会话建立的方法及终端设备
CN111586771B (zh) * 2019-02-19 2022-05-10 华为技术有限公司 网络节点选择方法及装置
CN111800889B (zh) * 2019-08-27 2022-05-20 维沃移动通信有限公司 一种处理协议数据单元会话的方法、终端设备和网络设备
CN110933709B (zh) * 2019-12-24 2023-02-28 展讯通信（上海）有限公司 协议数据单元会话管理方法及通信装置
CN111918359A (zh) * 2020-07-03 2020-11-10 中兴通讯股份有限公司 接入控制方法、第一网络节点、第二网络节点及存储介质

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210235339A1 (en) * 2020-01-28 2021-07-29 Alireza Babaei Wireless Device and Wireless Network Processes Based on Wireless Device Type
CN113795019A (zh) * 2021-08-09 2021-12-14 华为技术有限公司 一种通信控制方法和通信设备

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 24.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. V17.3.1, 2 July 2021 (2021-07-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 825, XP052030000 *
HUAWEI, HISILICON: "Scope of Rel-17 WI on support of reduced capability NR devices", 3GPP DRAFT; RP-202268, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Electronic Meeting; 20201207 - 20201211, 30 November 2020 (2020-11-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051962118 *
INTEL CORPORATION: "Summary of discussion [109][REDCAP] Reduced capability signalling framework (Intel)", 3GPP DRAFT; R2-2008191, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 1 September 2020 (2020-09-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051926212 *
ZTE: "Access control and identification for Reduced Capability NR devices", 3GPP DRAFT; R1-2007719, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 17 October 2020 (2020-10-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051939853 *

Also Published As

Publication number Publication date
CN113795019A (zh) 2021-12-14
CN113795019B (zh) 2022-12-30

Similar Documents

Publication Publication Date Title
JP7118237B2 (ja) 通信方法及び通信装置
US11178576B2 (en) Parameter conversions between an evolved packet system network and a 5G network
EP3852482B1 (en) Resource establishing method, and device
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
WO2023016006A1 (zh) 一种通信控制方法和通信设备
US20220338106A1 (en) Slice control method and apparatus
WO2020224622A1 (zh) 一种信息配置方法及装置
EP3771242A1 (en) Key generation method and relevant apparatus
US20210274340A1 (en) Method For Obtaining Capability Information Of Terminal, Apparatus, And System
US20230046157A1 (en) Communication method and apparatus
US20230164591A1 (en) Communication method and apparatus
WO2022001318A1 (zh) 通信方法和装置
US20230087407A1 (en) Authentication and authorization method and apparatus
US20220272577A1 (en) Communication method and communication apparatus
US20230388756A1 (en) Communication method and apparatus for multicast/broadcast service
US20220361286A1 (en) Session Processing Method and Communication Apparatus
US20220116798A1 (en) Data transmission method, apparatus, and device
US20170071003A1 (en) Method, network node and computer program
US20240155325A1 (en) Information obtaining method and apparatus, and system
WO2023213112A1 (zh) 通信方法和装置
WO2023015973A1 (zh) 一种网络切片准入控制方法和装置
WO2023083153A1 (zh) 获取安全分级结果的方法及通信装置
WO2024032244A1 (zh) 通信方法和通信装置
WO2022247537A1 (zh) 通信方法和通信装置
WO2023202503A1 (zh) 通信方法和装置

Legal Events

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

Ref document number: 22854994

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE