WO2019232757A1 - 一种发送业务请求的方法、装置及系统 - Google Patents

一种发送业务请求的方法、装置及系统 Download PDF

Info

Publication number
WO2019232757A1
WO2019232757A1 PCT/CN2018/090309 CN2018090309W WO2019232757A1 WO 2019232757 A1 WO2019232757 A1 WO 2019232757A1 CN 2018090309 W CN2018090309 W CN 2018090309W WO 2019232757 A1 WO2019232757 A1 WO 2019232757A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
access control
service request
sending
control information
Prior art date
Application number
PCT/CN2018/090309
Other languages
English (en)
French (fr)
Inventor
王宏
唐珣
张戬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2018/090309 priority Critical patent/WO2019232757A1/zh
Priority to CN201880094073.8A priority patent/CN112262595A/zh
Priority to EP18921903.3A priority patent/EP3806545A4/en
Publication of WO2019232757A1 publication Critical patent/WO2019232757A1/zh
Priority to US17/111,523 priority patent/US20210092669A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • H04W48/06Access restriction performed under specific conditions based on traffic conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/18Selecting a network or a communication service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/25Maintenance of established connections

Definitions

  • the present application relates to the field of communications, and in particular, to a method, a device, and a system for sending a service request.
  • a user equipment (UE) in an idle state initiates a service, it first sends a connection establishment request to a network-side base station, establishes a wireless link connection with the base station, and enters a connected state. data transmission.
  • the base station controls the access of some communication services. For example, some communication service types are allowed to access through broadcast messages, some communication service types are not allowed to access, or some communication service types are generated according to the UE. The random number determines whether access is allowed. In this way, when the UE requests connection establishment, the UE checks whether the type of communication service that triggers its request to establish a connection is allowed by the base station according to the content broadcast by the base station. If the type of service initiated by the UE is not allowed by the base station, the UE does not send a connection establishment request; otherwise, it sends a connection establishment request.
  • the connected state UE will also initiate some communication services, for example, making a phone call while downloading a file, and a call coming in while browsing a web page.
  • some communication services for example, making a phone call while downloading a file, and a call coming in while browsing a web page.
  • the UE since the UE is already in the connected state, the UE does not need to check whether the newly initiated service is allowed or prohibited by the eNB. If a large number of UEs are currently performing emergency communication with the base station and the base station load is acceptable, if a connected UE initiates a new service at this time, it will impact the network and cause the base station to be overloaded. interrupt.
  • the embodiments of the present application provide a method, a device, and a system for sending a service request, so as to implement access control of a new service of a connected terminal device, thereby controlling the load of a network-side device.
  • a method for sending a service request includes: a terminal device receiving first access control information from a first network device; and in a connected state, if the first access control information indicates that the first service is prohibited from accessing , The terminal device stops sending the service request of the first service to the first network device.
  • the first service is prohibited from being accessed, and the terminal device stops sending the first service to the first network device when the terminal device is connected.
  • the service request of the terminal controls the access of new services when the terminal device is in the connected state, thereby controlling the load of the first network device, and preventing the overload from affecting the network service quality.
  • the new service is another service initiated by the terminal device in a connected state. For example, when the terminal device is performing a voice call service, the terminal device newly initiates a web browsing service.
  • This application does not specifically limit the type of new services.
  • the initiating service described refers to the process by which a terminal device implements a type of service communication.
  • a message sent by a terminal device may be referred to as a service request or service signaling of the service sent by the terminal device.
  • service request or service signaling of the service sent by the terminal device.
  • service signaling of the service sent by the terminal device.
  • the terminal device may be a UE or other user-side device, and the terminal device may also be some functional units or chips in the user-side device.
  • the type of the terminal device is not specifically limited in this application.
  • the first network device may be part or all of the base station; when the first network device is part of the base station, the first network device may be a functional unit or at least one chip in the base station.
  • the base station is an access network device in the wireless network, and is responsible for connecting the terminal device to the core network to implement communication between the terminal device and the core network.
  • the base station may be an evolved base station (evolved nodeB, eNB) in a 4th generation (4G) network, or the base station may be an ENodeB in a 5th generation (5G) network
  • NR, NodeB, gNB next generation radio access base station
  • this application does not limit the type of the base station.
  • the base station may have different types.
  • the second network device may be a mobile management network element.
  • a mobility management network element is a network element that is responsible for mobility management in the network.
  • the mobility management network element may be a mobility management entity (MME) in a 4G network, or the mobility management network element may be an access and mobility management function (Access and Mobility Management Function in a 5G network). (AMF) entity, this application does not limit the type of the mobile management network element.
  • MME mobility management entity
  • AMF Access and Mobility Management Function
  • the mobile management network element may have different types. It should be noted that when the first network device is a mobility management network element, the terminal device receives the first access control information from the first network device through the base station.
  • the first network device may also be another type of network device, and the type of the first network device is not specifically limited in this application.
  • the method for sending a service request provided in this application may further include: in the connected state, if the first service is not prohibited from being accessed, the terminal device sends the first network device Business request for first business. According to the indication that the first access control information received from the first network device indicates that the first service is not prohibited from being accessed, the terminal device sends a service request of the first service to the first network device when the terminal device is connected, and controls the terminal device in the connected state. Time service access, which in turn controls the load of the first network device and prevents the overload from affecting network service quality.
  • the foregoing service request may include a public data network (Public Data Network, PDN) connection request, or a bearer resource modification request ( bearer (resource, modification, request), or service request (service request).
  • PDN Public Data Network
  • bearer resource modification request bearer (resource, modification, request)
  • service request service request
  • the type of the service request is not limited to this, and the service request may also be another service request supported by the terminal device.
  • the service request may be a service request for browsing a webpage, or a service request for making a phone call, or the like, which is not described in detail in this application.
  • the first service is any service of the terminal equipment, and does not specifically refer to a certain service.
  • the terminal device receiving the first access control information from the first network device may specifically include: the terminal device from the first network device Receive a system message, where the system message includes first access control information.
  • the system message is sent by the first network device in a broadcast form.
  • system message may include System Information Block 2 (System Information Block 2) (SIB 2).
  • SIB 2 System Information Block 2
  • the system message may be a message configured to send the first access control information. This application does not specifically limit the type of the system message.
  • the terminal device receiving the first access control information from the first network device may specifically include: the terminal device from the first network device Receive dedicated signaling, which includes first access control information.
  • the dedicated signaling may include an RRC connection reconfiguration message.
  • the dedicated signaling may be a message configured to send the first access control information. This application does not specifically limit the type of the dedicated signaling.
  • the terminal device when receiving the first access control information from the first network device, the terminal device may be in an idle state (RRC_IDLE) or a connected state (RRC_CONNECTED), which is not specifically limited in this application.
  • the terminal device may determine whether the first access control information indicates that the first service is forbidden to access in the connected state, or may determine the first access control in the idle state.
  • the information indicates whether access to the first service is prohibited, and this application does not specifically limit this.
  • the first access control information may include at least one of the following information: enabling indication information, and a type of service allowed to be initiated , The type of the service that is prohibited from initiating, the type of terminal equipment that is allowed to initiate the service, the type of terminal equipment that is prohibited from initiating the service, and instructions for enabling the access control policy.
  • the enabling instruction information is used to indicate whether the terminal device needs to determine whether the first service is forbidden to access according to the first access control information. It should be noted that, in this implementation manner, only the possible content of the first access control information is listed, and the content of the first access control information is not specifically limited. In practical applications, the content of the first access control information may be configured according to actual requirements.
  • the access control policy may include at least one of the following: an access class barring (ACB) policy; or, Service-Specific Access Control (SSAC) policies for specific services; or, ACB Skip policies; or Extended Access Barring (EAB) policies; or, for specific applications in data communications Congestion control (Application Specific Control, Data Communication, ACDC) strategy.
  • ACDC Access Specific Control
  • ACDC Application Specific Control, Data Communication
  • the terminal device may include an access (Access Stratum, AS) layer and a non-access (Non Access Stratum, NAS) layer.
  • the terminal device receiving the first access control information from the first network device may be specifically implemented as follows: the AS layer receives the first access control information from the first network device.
  • the NAS layer is the upper layer and the AS layer is the lower layer.
  • the AS layer receives information or messages from other devices, and the NAS layer sends information or messages to other devices through the AS layer.
  • an operation performed by the NAS layer described in this article can be replaced by the upper layer to perform the operation; an operation performed by the AS layer described in this article can be replaced by the lower layer to perform the operation.
  • the method for sending a service request provided in this application may further include: the AS layer sending first access control information to the NAS layer;
  • the NAS layer determines whether the first service is forbidden to access according to the first access control information.
  • the terminal device stopping sending the service request of the first service to the first network device includes: the NAS layer stops sending the service request signaling of the first service to the AS layer.
  • the NAS layer determines whether to send a service request, and the AS layer only forwards the received first access control information.
  • the method for sending a service request may further include: the AS layer extracting the first of the first access control information For the instruction information, the AS layer sends the first instruction information to the NAS layer; the NAS layer judges whether the first service is forbidden to access according to the first instruction information.
  • the terminal device stopping sending the service request of the first service to the first network device includes: the NAS layer stops sending the service request signaling of the first service to the AS layer.
  • the NAS layer determines whether to send a service request, and the AS layer parses the received first access control information and extracts internal upper-layer NAS information and forwards it to the NAS layer.
  • the NAS layer determines whether the first service is forbidden to access according to the first access control information, which may be performed when the first service is initiated in the connected state, or may be performed before the first service is initiated in the connected state, or It is performed in an idle state, which is not specifically limited in this application.
  • the method for sending a service request provided in this application may further include: the NAS layer sends the first service to the AS layer in a connected state. Service request signaling.
  • the AS layer determines whether the first service is forbidden to access according to the first access control information and the service request signaling of the first service.
  • the terminal device stopping sending the service request of the first service to the first network device includes: the AS layer stops sending the service request signaling of the first service to the first network device.
  • the AS layer decides whether to send a service request to the network side, the AS layer receives the service request signaling of the first service sent by the NAS layer, and the AS layer decides whether to send the service request to the first access control information received.
  • the network side sends service request signaling for the first service.
  • the method for sending a service request provided in this application may further include: the NAS layer sends the first service to the AS layer in a connected state. Service request signaling and access control policy instruction information.
  • the AS layer refers to the access control policy indicated by the access control policy instruction information, and determines whether the first service is based on the first access control information and the first service request signaling. Access is blocked.
  • the AS layer determines whether the first service is prohibited from being connected according to the first access control information and the service request signaling of the first service.
  • Incoming includes: the AS layer analyzes the service request signaling of the first service to obtain the service type of the first service; the AS layer determines whether the first service is forbidden to access according to the first access control information and the service type of the first service.
  • the method for sending a service request provided in this application may further include: the NAS layer sends the first service to the AS layer in a connected state.
  • the service type of the first service is also sent to the AS layer.
  • the AS layer determines whether the first service is forbidden to access according to the first access control information and the service request signaling of the first service, including: the AS layer determines according to the first access control information and the service type of the first service Whether the first service is forbidden to access.
  • the method for sending a service request provided in this application may further include: The AS layer sends response information to the NAS layer, which indicates that the first service is prohibited from accessing.
  • the method for sending a service request provided in this application may further include: when the AS layer sends response information to the NAS layer, it sends the response information to the NAS layer. Send the reason why the first service is forbidden to access.
  • the method for sending a service request provided by the first aspect or any possible implementation manner of the first aspect may be executed by a terminal device, and may also be executed by a functional unit or chip in the terminal device. This is not specifically limited.
  • the present application provides another method for sending a service request, including: determining first access control information, where the first access control message is used to control a service request of a terminal device connection state; and sending the first access control information .
  • the first access control information is used to control the service request of the terminal device in the connected state, which controls the service access of the terminal device in the connected state, thereby controlling the load on the network side to avoid overload Affect network service quality.
  • the determination of the first access control information may be performed periodically, or may be performed when the network load meets a preset condition, and the application does not specifically limit the timing of performing the determination of the first access control information.
  • the foregoing service request may include: a PDN connection request, or a bearer resource modification request, or a service request.
  • a PDN connection request or a bearer resource modification request
  • a service request may also be another service request supported by the terminal device.
  • sending the first access control information may include: broadcasting a system message, where the system message includes the first access control information;
  • dedicated signaling is sent, and the dedicated signaling includes first access control information.
  • the system message may include a SIB2 message.
  • the system message may be a message configured to send the first access control information.
  • the dedicated signaling may include an RRC connection reconfiguration message.
  • the dedicated signaling may be a message configured to send the first access control information. This application does not specifically limit the type of the dedicated signaling.
  • the first access control information includes at least one of the following information: enabling indication information, a type of service allowed to be initiated, Types of services that are prohibited from initiating, types of terminal devices that are allowed to initiate services, types of terminal devices that are prohibited from initiating services, and instruction information for enabling access control policies, where the enabling instruction information is used to indicate whether the terminal device needs to be accessed based on the first access The control information determines whether access to the first service is prohibited.
  • the access control policy may include at least one of the following: an ACB policy; or an SSAC policy; or an ACB skip policy; or , EAB strategy; or ACDC strategy in data communication. It should be noted that, in this implementation manner, only the possible content of the access control policy is listed, and the content of the access control policy is not specifically limited. In practical applications, the content of the access control strategy can be configured according to actual needs.
  • the method for sending a service request provided in the second aspect of the present application may further include: determining the first access control information, which may specifically The implementation is: determining and determining the first access control information according to its own load condition.
  • a device that executes the method for sending a service request provided in the second aspect actively determines the first access control information according to its own load, saving system transmission resources.
  • the method for determining the first access control information according to the load condition may be configured according to actual requirements, which is not specifically limited in this application.
  • a preset correspondence relationship is configured in advance, and the preset correspondence relationship includes different load conditions and contents of the corresponding first access control information, which can be obtained by querying the preset correspondence relationship when determining the first access control information.
  • a model of the load condition and the content of the first access control information is established in advance, and the content of the first access control information is determined according to the model and the load condition.
  • the method for sending a service request provided in the second aspect of the present application may further include: receiving a second access from a second network device Control information, and the second access control information is used to control a service request of a terminal device in a connected state.
  • determining the first access control information may be specifically implemented as: determining the first access control information according to the second access control information.
  • the method for determining the first access control information according to the second access control information may be configured according to actual requirements, which is not specifically limited in this application.
  • the content of the second access control information may be directly the content of the first access control information.
  • a preset correspondence relationship is configured in advance, and the preset correspondence relationship includes content of different second access control information and corresponding content of the first access control information. Set the corresponding relationship to get it.
  • the method for sending a service request provided in this application may further include: sending a load for indicating a load condition to a second network device Instructions.
  • the second network device determines the second access control information according to the load indication information.
  • the method for sending a service request provided by the second aspect or any possible implementation manner of the second aspect may be executed by a first network device, and may also be executed by a functional unit or a chip in the first network device. This application does not specifically limit this.
  • the first network device has been described in detail in the above-mentioned first aspect, and is not repeated here.
  • another method for sending a service request including: determining second access control information, where the second access control information is used to control a service request of a terminal device connection state; and sending the first network device or the terminal device Second access control information.
  • the service request of the terminal device in the connected state is controlled by the second access control information, which controls the service access of the terminal device in the connected state, thereby controlling the load on the network side and avoiding overload Affect network service quality.
  • the method for sending a service request provided in this application may further include: receiving, from a first network device, load indication information used to indicate a load status of the first network device.
  • determining the second access control information may be specifically implemented as follows: determining the second access control information according to the load indication information.
  • the method for determining the second access control information according to the load indication information may be configured according to actual requirements, which is not specifically limited in this application.
  • a preset correspondence relationship is configured in advance, and the preset correspondence relationship includes different load conditions and contents of the corresponding second access control information, which can be obtained by querying the preset correspondence relationship when determining the second access control information.
  • a model of the load condition and the content of the second access control information is established in advance, and the content of the second access control information is determined according to the model and the load condition.
  • the method for sending a service request provided by the third aspect or any possible implementation manner of the third aspect may be executed by a second network device, and may also be executed by a functional unit or a chip in the second network device. This application does not specifically limit this.
  • the second network device has been described in detail in the above first aspect, and is not repeated here.
  • an embodiment of the present application provides a terminal device that can implement the functions of the terminal device in the foregoing method examples, and the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the foregoing functions.
  • the structure of the terminal device includes a processor and a transceiver, and the processor is configured to support the terminal device to perform a corresponding function in the foregoing method.
  • the transceiver is used to support communication between the terminal device and other devices.
  • the terminal device may further include a memory, which is used for coupling with the processor, and stores program instructions and data necessary for the terminal device.
  • an embodiment of the present application provides a first network device.
  • the first network device may implement functions of the first network device in the foregoing method example, and the functions may be implemented by hardware or may execute corresponding functions by hardware.
  • the hardware or software includes one or more modules corresponding to the foregoing functions.
  • the structure of the first network device includes a processor and a transceiver, and the processor is configured to support the first network device to perform a corresponding function in the foregoing method.
  • the transceiver is used to support communication between the first network device and other devices.
  • the first network device may further include a memory, which is configured to be coupled to the processor and stores program instructions and data necessary for the first network device.
  • an embodiment of the present application provides a second network device.
  • the second network device may implement the functions of the second network device in the foregoing method example, and the functions may be implemented by hardware or may execute corresponding functions by hardware.
  • the hardware or software includes one or more modules corresponding to the foregoing functions.
  • the structure of the second network device includes a processor and a transceiver, and the processor is configured to support the second network device to perform a corresponding function in the foregoing method.
  • the transceiver is used to support communication between the second network device and other devices.
  • the second network device may further include a memory, which is configured to be coupled to the processor and stores program instructions and data necessary for the second network device.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the foregoing terminal device, which includes a program designed to execute the foregoing first aspect.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the first network device, which includes a program designed to execute the second aspect.
  • an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the second network device, which includes a program designed to execute the third aspect.
  • an embodiment of the present application provides a communication system, including the terminal device and the first network device described in any one of the foregoing aspects or any possible implementation manner.
  • the communication system may further include a second network device described in any one of the foregoing aspects or any possible implementation manner.
  • an embodiment of the present application provides another communication system, including a terminal device and a second network device described in any one of the foregoing aspects or any possible implementation manner.
  • the solutions provided by the fourth aspect to the eleventh aspect are used to implement the method for sending a service request provided by the first aspect or the second aspect or the third aspect, and thus may be the same as the first aspect or the second aspect or the third aspect Achieving the same beneficial effects will not be repeated here.
  • FIG. 1 is a schematic architecture diagram of a communication system provided in the prior art
  • FIG. 2 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a first network device according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a second network device according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for sending a service request according to an embodiment of the present application
  • FIG. 6 is a schematic flowchart of another method for sending a service request according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an apparatus for sending a service request according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another apparatus for sending a service request according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of still another apparatus for sending a service request according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another apparatus for sending a service request according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of another apparatus for sending a service request according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of another apparatus for sending a service request according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another apparatus for sending a service request according to an embodiment of the present application.
  • this application proposes a method for sending a new service transmission request for controlling a terminal device to initiate a service in a connected state.
  • the basic principle is that the terminal device initiates a service in a connected state according to an indication of the first access control information. At this time, if the first access control information indicates that the service is prohibited from being accessed, the service is stopped from being initiated. Therefore, as long as the first access control information is configured according to the requirements, the initiated service of the connected terminal can be controlled, and then the load on the network side can be controlled to ensure the network service quality.
  • the terminal device described in this application may be part or all of a mobile communication device used by a user.
  • the terminal device may be a UE or other.
  • mobile communication devices can be mobile phones, tablets, laptops, Ultra-mobile Personal Computer (UMPC), netbooks, Personal Digital Assistants (PDAs), e-books, mobile TVs, and wearable devices , Personal Computer (PC), and so on.
  • UMPC Ultra-mobile Personal Computer
  • PDAs Personal Digital Assistants
  • e-books mobile TVs
  • wearable devices Personal Computer (PC), and so on.
  • PC Personal Computer
  • the embodiment of the present application does not specifically limit the type of the terminal device.
  • the first network device described in this application may be part or all of a base station; when the first network device is part of a base station, the first network device may be a functional unit or at least one chip in the base station.
  • a base station is a network-side device that provides communication services for terminal devices in a wireless communication system. In wireless communication systems of different standards, base stations may have different names, but they can all be understood as the base stations described in this application. The embodiment of the present application does not specifically limit the type of the base station. For example, base stations in the Universal Mobile Telecommunications System (UMTS) are called base stations (BS); base stations in the LTE system are called eNBs, and so on, which are not listed here one by one. Any network-side device that provides communication services for a terminal device in a wireless communication system can be understood as the base station described in this application.
  • UMTS Universal Mobile Telecommunications System
  • eNBs base stations in the LTE system
  • the second network device described in this application may be part or all of a mobility management network element; when the second network device is part of a mobility management network element, the second network device may be a functional unit in the mobility management network element or at least A chip.
  • a mobility management network element is a network element that is responsible for mobility management in the network. In communication systems of different standards, the mobile management network element may be called differently, but all of them can be understood as the mobile management network element described in this application.
  • the embodiment of the present application does not specifically limit the type of the mobile management network element.
  • the mobility management network element may be an MME in a 4G network, or the mobility management network element may be an AMF entity in a 5G network.
  • the communication system architecture includes a base station 101, a terminal device 102, and a mobility management network element 103.
  • the terminal device 102 communicates with the base station 101 and accesses the core network to which the mobile management network element 103 belongs.
  • FIG. 1 is only a schematic diagram of the communication system architecture by way of example.
  • the number and types of the base stations 101, terminal devices 102, and mobile management network elements 103 included in the communication system architecture can be configured according to actual needs, and FIG. 1 is not a specific limitation on this content.
  • the base station 101 illustrated in FIG. 1 represents the first network device described in this application
  • the mobility management network element 103 illustrated in FIG. 1 represents the second network device described in this application, which can directly replace the application.
  • the wireless communication system architecture shown in FIG. 1 may be an LTE network, a UMTS network, or another network.
  • the type of the network to which the solution of the present application is applied is not specifically limited in this embodiment of the present application.
  • the access control information refers to information used to control the service access of the terminal device, and according to its content, it can be determined whether the service is forbidden to access.
  • This application relates to the first access control information and the second access control information according to different execution subjects of the determination information.
  • the first access control information is information received by the terminal device from the network device, and is used to indicate whether the service is forbidden to access.
  • the second access control information is information exchanged between network devices and is used to determine the first access control information.
  • An access control policy is a preset rule for controlling access.
  • the access control policy may be an ACB policy; or, an SSAC policy; or an ACB skip policy; or an EAB policy; or an ACDC policy in data communication.
  • first and second in the specification and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of the objects.
  • first network device and the second network device are used to distinguish different network devices, rather than to describe a specific order of the devices.
  • words such as “exemplary” or “for example” are used as examples, illustrations or illustrations. Any embodiment or design described as “exemplary” or “for example” in the embodiments of the present application should not be construed as more preferred or more advantageous than other embodiments or designs. Rather, the use of the words “exemplary” or “such as” is intended to present the relevant concepts in a concrete manner to facilitate understanding.
  • FIG. 2 shows a terminal device 20 related to the embodiments of the present application.
  • the terminal device 20 may be the terminal device 102 in the communication system architecture shown in FIG. 1.
  • the terminal device 20 may include: a processor 201, a memory 202, and a transceiver 203.
  • Each component of the terminal device 20 is specifically described below with reference to FIG. 2:
  • the memory 202 may be a volatile memory (for example, random-access memory (RAM); or a non-volatile memory (for example, read-only memory) , ROM), flash memory (flash memory), hard disk (HDD) or solid state drive (SSD); or a combination of the above types of memory, used to store the program that can implement the method of the present application Code, and configuration files.
  • RAM random-access memory
  • non-volatile memory for example, read-only memory
  • ROM read-only memory
  • flash memory flash memory
  • HDD hard disk
  • SSD solid state drive
  • the processor 201 is the control center of the terminal device 20, and may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or configured to implement the embodiments of the present application.
  • One or more integrated circuits such as: one or more microprocessors (digital signal processors, DSPs), or one or more field programmable gate arrays (Field Programmable Gate Arrays, FPGAs).
  • the processor 201 may execute various functions of the terminal device 20 by running or executing software programs and / or modules stored in the memory 202 and calling data stored in the memory 202.
  • the transceiver 203 is used for the terminal device 20 to interact with other units.
  • the transceiver 203 may be a transceiver antenna or a transceiver function unit of the terminal device 20.
  • the processor 201 executes the following functions by running or executing software programs and / or modules stored in the memory 202 and calling data stored in the memory 202:
  • FIG. 3 shows a first network device 30 related to the embodiments of the present application.
  • the first network device 30 may be the first network device 101 in the communication system architecture shown in FIG. 1.
  • the first network device 30 may include: a processor 301, a memory 302, and a transceiver 303.
  • Each component of the first network device 30 is specifically described below with reference to FIG. 3:
  • the memory 302 may be a volatile memory, such as a RAM; or a non-volatile memory, such as a ROM, a flash memory, an HDD, or an SSD; or a combination of the foregoing types of memory, for storing program code that can implement the method of the present application, and Configuration file.
  • a volatile memory such as a RAM
  • a non-volatile memory such as a ROM, a flash memory, an HDD, or an SSD
  • program code that can implement the method of the present application, and Configuration file.
  • the processor 301 is a control center of the first network device 30, and may be a CPU, an ASIC, or one or more integrated circuits configured to implement the embodiments of the present application, for example, one or more DSPs, or , One or more FPGAs.
  • the processor 301 may perform various functions of the first network device 30 by running or executing software programs and / or modules stored in the memory 302 and calling data stored in the memory 302.
  • the transceiver 303 is used for the first network device 30 to interact with other units.
  • the transceiver 303 may be a transceiver antenna, a transceiver circuit, or a transceiver device of the first network device 30.
  • the processor 301 executes the following functions by running or executing software programs and / or modules stored in the memory 302 and calling data stored in the memory 302:
  • the first access control information is determined, and the first access control message is used to control the service request of the connection state of the terminal device; the first access control information is sent through the transceiver 303.
  • FIG. 4 shows a second network device 40 related to the embodiments of the present application.
  • the first network device 40 may be the second network device 103 in the communication system architecture shown in FIG. 1.
  • the second network device 40 may include a processor 401, a memory 402, and a transceiver 403.
  • the memory 402 may be a volatile memory, such as a RAM; or a non-volatile memory, such as a ROM, a flash memory, an HDD, or an SSD; or a combination of the foregoing types of memory, for storing program code that can implement the method of the present application, and Configuration file.
  • a volatile memory such as a RAM
  • a non-volatile memory such as a ROM, a flash memory, an HDD, or an SSD
  • program code that can implement the method of the present application, and Configuration file.
  • the processor 401 is a control center of the second network device 40, and may be a CPU, an ASIC, or one or more integrated circuits configured to implement the embodiments of the present application, for example, one or more DSPs, or , One or more FPGAs.
  • the processor 401 may perform various functions of the second network device 40 by running or executing software programs and / or modules stored in the memory 402, and calling data stored in the memory 402.
  • the transceiver 403 is used for the second network device 40 to interact with other units.
  • the transceiver 403 may be a transceiver antenna, a transceiver circuit, or a transceiver device of the second network device 40.
  • the processor 401 executes the following functions by running or executing software programs and / or modules stored in the memory 402 and calling data stored in the memory 402:
  • an embodiment of the present application provides a method for sending a service request, which is applied to an interaction process between a terminal device and a first network device.
  • the method for sending a service request provided in this embodiment of the present application may be executed by a terminal device and / or a first network device, and may also be executed by a functional unit or a chip in the terminal device and / or the first network device. This is not specifically limited.
  • the terminal device and / or the first network device described in the following embodiments perform an action, which may be replaced by a terminal unit and / or a functional unit or chip of the first network device to perform the action, which will not be described one by one.
  • the functional unit or chip in the terminal device and / or the first network device that executes the method for sending a service request provided in this application may be referred to as a device for sending a service request.
  • the method for sending a service request may include:
  • the first network device determines first access control information.
  • the first access control message is used to control a service request of a terminal device in a connected state.
  • the first network device may be part or all of the base station; when the first network device is part of the base station, the first network device may be a functional unit or at least one chip in the base station.
  • the base station is an access network device in the wireless network, and is responsible for connecting the terminal device to the core network to implement communication between the terminal device and the core network.
  • the base station may be an eNB in a 4G network, or the base station may be a gNB in a 5G network. This application does not limit the type of the base station. In different types of networks, the base station may have different types.
  • the first access control information is used to control the service access of the connected terminal device.
  • the content of the first access control information indicates which services of the connected terminal device are prohibited by the network side and which services are blocked by the network side. allow. It should be noted that being prohibited or allowed by the network side may be prohibited or allowed by the first network device, or may be prohibited or allowed by other network devices, which are not specifically limited in the embodiment of the present application.
  • the prohibition refers to prohibiting a terminal device in a connected state from initiating certain services, that is, prohibiting certain services of the terminal device from accessing the network.
  • the first access control information indicates that service A of the connected terminal device prohibits access to the network.
  • the service of service A is considered to be a service according to the indication of the first access control information.
  • the request is forbidden, that is, the service request of service A is not sent to the network device.
  • the permission refers to allowing the connected terminal device to initiate certain services, that is, allowing certain services of the terminal device to access the network.
  • the first access control information indicates that service B of the connected terminal device is allowed to access the network.
  • the terminal device sends a service request of service B the service of service B is considered according to the indication of the first access control information.
  • the request is allowed, that is, a service request for service B is sent to the network device.
  • not prohibition has the same meaning as permitted, and prohibition has the same meaning as disallowed.
  • the terminal device is in a connected state.
  • the first access control information may include at least one of the following information: enabling indication information, types of services permitted to be initiated, types of services prohibited to be initiated, types of terminal devices permitted to initiate services, and terminals prohibited to initiate services Device type and instructions for enabling access control policies.
  • the enabling instruction information is used to indicate whether the terminal device needs to determine whether the first service is forbidden to access based on the first access control information, even if the mechanism for connecting and controlling the terminal device to send a service request can be enabled or disabled. For example, when the enabling instruction information indicates that the mechanism is enabled, the terminal device judges whether the sending of service requests is disabled according to the access control information sent by the network device. When the enabling instruction information indicates that the mechanism is disabled, then The terminal device does not need to judge whether the sending of the service request is prohibited according to the access control information, but directly sends the service request according to the current technology.
  • the enabling indication information may be displayed indication information, for example, ConnectionAccessEnable is Enable or Enable indicates enabling, where ConnectionAccessEnable may be interpreted as connection state access enabling instruction information, that is, the above enabling instruction information, or ConnectionAccessEnable is False Or Disable means disable.
  • the enabling instruction information may also be implicit instruction information. For example, when the network device sends information related to the connection state access control, it indicates that the above connection state access control mechanism is enabled. When the information about the connection state access control is used, it means that the above connection state access control mechanism is disabled.
  • the content of the first access control information is only listed here, and the content of the first access control information is not specifically limited. In practical applications, the content of the first access control information may be configured according to actual requirements.
  • the type of service allowed to be initiated refers to the type of service allowed by the network device to initiate the connection state of the terminal device.
  • the type of service allowed to be initiated may include one or more of the following combinations: called service (Mobile terminating call), emergency Call service (Emergency call), calling service (Mobile origination call), signaling service (Signalling), circuit domain fallback (CS fallback), multimedia telephone service (Multi-Media Telephony (MMTEL), voice service (Voice), Video service (Video), short message service (SMS), delay tolerance service (Delay tolerance service), etc. It should be noted that the above examples of the types of services allowed to be initiated are not limited.
  • the types of services that are prohibited from initiating refer to the types of services that are prohibited by the network device from being initiated by the connected terminal device.
  • the types of services that are prohibited from being initiated may include one or more of the following combinations: called service (Mobile terminating call), emergency Call service (Emergency call), calling service (Mobile origination call), signaling service (Signalling), circuit domain fallback (CS fallback), multimedia telephone service (Multi-Media Telephony (MMTEL), voice service (Voice), Video service (Video), short message service (SMS), delay tolerance service (Delay tolerance service), etc.
  • called service Mobile terminating call
  • Emergency Call service Emergency call
  • calling service Mobile origination call
  • signaling service Simalling
  • circuit domain fallback CS fallback
  • multimedia telephone service Multi-Media Telephony (MMTEL), voice service (Voice), Video service (Video), short message service (SMS), delay tolerance service (Delay tolerance service), etc.
  • the types of terminal devices that are allowed to initiate services can be Machine Type Communication (MTC) terminal devices or Narrowband Internet of Things (NB-IoT) terminal devices or water meters or electricity meters or wearable devices Wait. It should be noted that the foregoing examples of the types of terminal devices allowed to initiate services are not limited.
  • MTC Machine Type Communication
  • NB-IoT Narrowband Internet of Things
  • the type of terminal device prohibited to initiate a service may be a Machine Type Communication (MTC) terminal device or a Narrowband Internet of Things (NB-IoT) terminal device or a water meter or electricity meter or a wearable device Wait. It should be noted that the foregoing examples of the types of terminal devices that are prohibited from initiating a service are not limited.
  • MTC Machine Type Communication
  • NB-IoT Narrowband Internet of Things
  • the instruction information for enabling the access control policy refers to the network device instructing the terminal device to determine whether to initiate a service when the connection state is determined according to the specified access control policy.
  • the access control policy is an access control criterion pre-configured or present in 3GPP TS 36.331.
  • the access control policy may include at least one of the following: ACB policy; or SSAC policy; or ACB skip policy; or EAB policy; or ACDC policy in data communication.
  • the content of the access control policy can be configured according to the actual needs.
  • the content of the access control policy is only exemplified, and it is not a specific limitation on this.
  • the ACB policy is an access control policy proposed in Release 8 of 3GPP.
  • the terminal device uses a random number and a timer to perform access control based on the type of access.
  • the SSAC strategy (Scheme / Mechanism) is the access control strategy proposed in Release 9 of 3GPP.
  • the network broadcasts the barring factor and random timer.
  • the actual decision is in the UE's IMS layer, which is applicable to the connected state and idle State, which is used to solve the network overload problem caused by the simultaneous access of a large number of terminal devices.
  • the ACB Skip policy is a method introduced in Release 12 of 3GPP to control IMS voice and video users to ignore the ACB policy.
  • the EAB policy is an access control policy proposed in Release 11 of 3GPP, in which the network is allowed to prohibit low priority UEs. This method is based on a bitmap. Each class in 0-9 can be disabled or allowed.
  • the ACDC policy in data communication is the access control policy proposed in Release 13 of 3GPP.
  • This policy services that prohibit specific applications are permitted, applications are classified based on global application identification, and the network broadcasts prohibition parameters (prohibition factors and Timer).
  • the instruction for enabling the access control policy is AccessControlStrategy.
  • One method is to indicate only one policy, that is, use an enumeration type definition, such as AccessControlStrategy is ENUMERATED ⁇ ACB, SSAC, ACBskip, EAB, ACDC, ... ⁇ , when When the AccessControlStratey value is ACB, the terminal device uses the current ACB policy to check the service request that the terminal device intends to send in the connected state according to the instruction information, and checks whether the access control conforms to the ACB policy. Incoming, the terminal device sends the service request, otherwise it does not send the service request.
  • the network device indicates one or more policies, which can be defined using AccessControlStrategyList, where AccessControlStrategyList is defined by SEQUENCE (SIZE (0..maxValue)) OF AccessControlStrategy, maxValue is the maximum number of policies allowed by the network, AccessControlStrategy The definition is as before.
  • the network device indicates that one or more policies can also be defined using a bitmap. For example, assuming a total of five policies, which are ACB, SSAC, ACBskip, EAB, and ACDC, the bitmap AccessControlStrategyBitmap can be defined as BIT. STRING (5), which is a total of 5 bits. Each bit indicates the above 5 policies in sequence.
  • the first network device may periodically determine the first access control information, or may determine the first access control information when its load condition meets a preset condition.
  • the timing of S501 is not specifically limited and can be configured according to actual needs.
  • the specific interval of the period can be configured according to actual requirements; the content of the preset conditions can also be configured according to actual requirements; this embodiment of the present application does not specifically limit this.
  • the first network device determining the first access control information may be implemented by any of the following schemes:
  • Solution 1 The first network device determines first access control information according to a load condition of the first network device.
  • a preset correspondence relationship between the load status and the content of the first access control information may be pre-configured, and when S501 is performed, the preset correspondence relationship may be queried.
  • the content of the preset correspondence relationship can be configured according to actual experience, and the application does not limit the configuration process.
  • Table 1 the content of a preset correspondence relationship is illustrated.
  • the load status is 15%
  • the first access control information taking the first access control information including the type of service forbidden to initiate as an example, then
  • the types of services that are prohibited from being initiated can be type A services and type B services.
  • Table 1 is only an exemplary description of the preset correspondence relationship, and is not a limitation on the content and form of the preset correspondence relationship.
  • a model of the load condition and the first access control information may be established in advance through learning, and when S501 is performed, the load condition is input into the model to obtain the first access control information.
  • the first network device receives the second access control information sent by the second network device, and determines the first access control information according to the second access control information.
  • the second access control information is determined by the second network device according to a load condition of the first network device.
  • the method for sending a service request provided in this embodiment of the present application may further include S501a to S501e.
  • the first network device sends load instruction information indicating a load status to the second network device.
  • the load indication information is used to indicate the load status of the first network device, and the load indication information may be in any form such as a character string or a code, which is not specifically limited in this embodiment of the present application. It should be noted that the correspondence between the load indication information and the load condition may be configured according to actual requirements, which is not specifically limited in the embodiment of the present application.
  • the load indication information may be represented by a binary character string, and the correspondence between the load indication information and the load status may be embodied in the form of a correspondence relationship.
  • S501a the correspondence relationship is obtained to obtain the load indication information and send it.
  • the second network device receives load indication information from the first network device.
  • the second network device determines second access control information.
  • the second network device determines the second access control information according to the load instruction information received in S501b.
  • the second network device may directly determine the second access control information according to the load indication information.
  • the second network device may directly determine the second access control information according to the load indication information.
  • reference may be made to the implementation manner of the first network device to determine the first access control information according to the load condition in Scheme 1, and details are not described herein again.
  • the second network device determines the load status according to the load indication information, and then determines the second access control information according to the load status, and the second network device determines the implementation of the second access control information according to the load status.
  • the method refer to the implementation manner that the first network device determines the first access control information according to the load condition in Solution 1, and details are not described herein again.
  • the content of the second access control information may be exactly the same as the content of the first access control information, or the content of the second access control information may correspond to the content of the first access control information.
  • This application The embodiment does not specifically limit this.
  • the second network device sends second access control information to the first network device.
  • the second network device transmits the second access control information through its communication interface with the first network device.
  • the first network device receives second access control information from the second network device.
  • Solution 3 The first network device receives the second access control information sent by the second network device, and determines the first access control information according to the second access control information.
  • the second access control information is determined by the load condition of the second network device.
  • Scenario 3 can be implemented.
  • An implementation manner is that the second network device determines the second access control information according to its own load condition.
  • the second access control information may be displayed similar to the first access control information or the second access control information.
  • the first network device determines the first access control information according to the load status of the second network device indicated by the second access control information.
  • S501 may include, but is not limited to, implementation 1 and implementation 2 described below.
  • the second access control information is the same as the first access control information, and the first network device can determine the first access control information after receiving the second access control information.
  • the first network device directly receives the first access control information after receiving the second access control information determined by the second network device.
  • the second access control information may be directly sent to the terminal device through the first network device, that is, the second access control information is encapsulated in the first access control information and sent to the terminal device.
  • the second access control information corresponds to the first access control information.
  • the first network device determines the first access control information according to the corresponding relationship. For example, the first network device determines the first access control information according to the second access control information and the communication protocol between the first network device and the terminal device. At this time, the first access control information and the second access control information are only The difference in the data transmission format has the same substantial meaning, that is, the first network device repackages the second access control information into the first access control information and sends it to the terminal device.
  • the first access control information is determined according to the load status of the first network device described in S501. In actual applications, the first access control information may also be determined according to the load status of other network devices. The same is not repeated here.
  • the first network device sends first access control information.
  • the first network device sends the first access control information, which can be implemented by, but not limited to, the following two implementations:
  • a first implementation manner a system message (system information), where the system message includes first access control information.
  • the system message may include SIB1 and SIB2 messages.
  • the system message may be a message dedicated to sending the first access control information.
  • the application does not specifically limit the type of the system message.
  • a second implementation manner dedicated signaling (Dedicated signaling), where the dedicated signaling includes first access control information.
  • the dedicated signaling may include an RRC connection reconfiguration message.
  • the dedicated signaling may be a message dedicated to sending the first access control information. This application does not specifically limit the type of dedicated signaling.
  • the terminal device receives first access control information from the first network device.
  • the terminal device receiving the first access control information from the first network device in S503 can also pass through but is not limited to the following two implementations:
  • Implementation manner A The terminal device receives a system message from the first network device, and the system message includes first access control information.
  • Implementation manner B The terminal device receives dedicated signaling from the first network device, where the dedicated signaling includes first access control information.
  • the terminal device when the terminal device receives the first access control information in S503, it may be in an idle (IDLE) state or a connected state.
  • IDLE idle
  • the terminal device may be in an idle (IDLE) state or a connected state.
  • the terminal device may include an AS layer and a NAS layer.
  • the terminal device receives the first access control information from the first network device, which is specifically implemented as follows: the AS layer receives the first access control information from the first network device.
  • the AS layer receives / sends information or messages from / to other devices, and the NAS layer receives / sends information or messages from / to other devices through the AS layer.
  • the method for sending a service request provided in the embodiment of the present application may further include S503a.
  • S503a The terminal device determines whether access to the first service is prohibited according to the first access control information.
  • the terminal device may execute S503a when receiving the first access control information in S503, or may execute S503a when initiating the first service in the connected state, which is not specifically limited in this embodiment of the present application.
  • the terminal device may receive the first access control information in the IDLE state or the connected state, and then the terminal device may also determine whether the first service is prohibited from being connected according to the first access control information in the IDLE state or the connected state. Into.
  • the terminal device includes an AS layer and a NAS layer
  • the AS layer receives the first access control information from the first network device, and the AS layer sends the first access control information to the NAS layer; the NAS layer judges the first based on the first access control information. Whether the service is forbidden to access.
  • the first service is any service initiated by the terminal service, and is not specifically referred to.
  • the AS layer receives the first access control information from the first network device, the AS layer extracts the first indication information in the first access control information, and the AS layer sends the first to the NAS layer. Indication information; the NAS layer determines whether the first service is prohibited from accessing according to the first indication information, and the first indication information includes information related to access control.
  • the AS layer receives the first access control information from the first network device and saves it.
  • the NAS layer sends the service request signaling of the first service to the AS layer in the connected state.
  • An access control information and a service request signaling of the first service determine whether the first service is barred from accessing.
  • the service request may include: a PDN connection request, or a bearer resource modification request, or a service request.
  • a PDN connection request or a bearer resource modification request
  • a service request may include: a PDN connection request, or a bearer resource modification request, or a service request.
  • this application does not specifically limit the type of the service request.
  • the service request may be a service request for browsing a webpage, or a service request for making a phone call, or the like, which is not described in detail in this application.
  • the AS layer receives the first access control information from the first network device and saves it.
  • the NAS layer sends the service request signaling and access control of the first service to the AS layer in the connected state.
  • the policy instruction information, the AS layer refers to the access control policy indicated by the access control policy instruction information, and determines whether the first service is forbidden to access according to the first access control information and the signaling of the first service request.
  • the access control policy indicated by the access control policy instruction information is an access control policy configured inside the terminal device, which is combined with the first access control information to control the access of the service initiated by the terminal device.
  • the access control policy indicated by the access control policy instruction information described here is the same as the access control policy described previously. The access control policy has been described in detail previously, and will not be repeated here.
  • the AS layer checks whether the ACB policy allows the MO service request to be initiated for the MO service request.
  • the AS layer determines whether the first service is forbidden to access according to the first access control information and the service request signaling of the first service, which may specifically include: the AS layer parses the service request letter of the first service Order to obtain the service type of the first service; the AS layer determines whether the first service is forbidden to access according to the first access control information and the service type of the first service.
  • the NAS layer when the NAS layer sends the service request signaling of the first service to the AS layer in the connected state, it also sends the service type of the first service to the AS layer.
  • the AS layer determines whether the first service is forbidden to access according to the first access control information and the service request signaling of the first service, including: the AS layer determines the first service according to the first access control information and the service type of the first service Whether access is prohibited.
  • the process of determining whether the first service is forbidden is a comparison process. Let's repeat them one by one.
  • the terminal device stops sending a service request for the first service to the first network device.
  • the terminal device includes an AS layer and a NAS layer
  • AS layer and a NAS layer
  • S504 there may be multiple specific implementations of S504, which are described below one by one.
  • the NAS layer determines that the first service is forbidden to access in the connected state according to the first access control information, and the terminal device stops sending the service request of the first service to the first network device, which may be specifically implemented as : The NAS layer stops sending the service request signaling of the first service to the AS layer.
  • the NAS layer sends the service request signaling of the first service to the AS layer in the connected state, and the AS layer determines that the first service is forbidden to access in the connected state according to the first access control information.
  • the terminal device stopping sending the service request of the first service to the first network device may be specifically implemented as: the AS layer stops sending the service request signaling of the first service to the first network device.
  • the method for sending a service request provided in this application may further include: the AS layer sends response information to the NAS layer, and the response The information indicates that access to the first service is prohibited.
  • the method for sending a service request provided in this application may further include: when the AS layer sends a response message to the NAS layer, sending the reason why the first service is forbidden to access to the NAS layer
  • the reason may include that the inspection result of policies such as ACB or ACDC is forbidden.
  • the first service is prohibited from being accessed, and the terminal device stops sending the first service to the first network device when the terminal device is connected.
  • the service request of the terminal controls the service access of the terminal device in the connected state, thereby controlling the load of the first network device, and preventing the overload from affecting the network service quality.
  • the method for sending a service request provided in this application may further include S505.
  • the terminal device In the connected state, if the first service is not prohibited from being accessed, the terminal device sends a service request for the first service to the first network device.
  • the terminal device includes an AS layer and a NAS layer
  • the NAS layer determines that the first service is not prohibited from being accessed in the connected state according to the first access control information, and the terminal device sends a service request for the first service to the first network device, which may be specifically implemented as :
  • the NAS layer sends the service request signaling of the first service to the AS layer, and the AS layer sends the service request signaling of the first service to the first network device.
  • the NAS layer sends the service request signaling of the first service to the AS layer in the connected state, and the AS layer determines that the first service is not forbidden to access in the connected state according to the first access control information.
  • the terminal device sending the service request for the first service to the first network device may be specifically implemented as follows: the AS layer sends the service request signaling for the first service to the first network device.
  • the terminal device and the first network device include a hardware structure and / or a software module corresponding to each function.
  • this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • the functional part of the terminal device and the first network device that executes the method for sending a service request provided in this application is called a device for sending a service request.
  • the device for sending a service request may be a terminal device or Part or all of the first network device, in other words, the device sending the service request may be equivalent to the terminal device or the first network device, or the device sending the service request may also be deployed in the terminal device or the first network device to support The terminal device or the first network executes the method for sending a service request provided in this application.
  • the functional modules of the terminal device and the first network device may be divided according to the foregoing method example.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module in.
  • the above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • dividing the function module of the terminal device or the first network device is equivalent to dividing the function module of the device sending the service request; or
  • dividing the function module of the device sending the service request is equivalent to dividing the function module of the terminal device or the first network device.
  • FIG. 7 illustrates a possible structural diagram of a device for sending a service request in the terminal device involved in the foregoing embodiment.
  • the apparatus 70 for sending a service request may include: a receiving unit 701, a sending unit 702, and a processing unit 703.
  • the receiving unit 701 is configured to execute the process S503 in FIG. 5 or FIG. 6;
  • the sending unit 702 is configured to send a service request to the first network device;
  • the processing unit 703 is configured to execute the processes S503a, S504, S505.
  • all relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.
  • FIG. 8 shows a possible structural diagram of a device for sending a service request in the terminal device involved in the foregoing embodiment.
  • the apparatus 80 for sending a service request may include a processing module 801 and a communication module 802.
  • the processing module 801 is configured to control and manage operations of the apparatus 80 for sending a service request.
  • the processing module 801 is configured to support the device 80 for sending a service request to perform the processes S503, S503a, S504, and S505 in FIG. 5 or FIG.
  • the device 80 for sending a service request may further include a storage module 803 for storing program code and data of the device 80 for sending a service request.
  • the processing module 801 may be the processor 201 in the physical structure of the terminal device 20 shown in FIG. 2, and may be a processor or a controller.
  • it can be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor 801 may also be a combination that realizes a computing function, for example, it includes a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 802 may be the transceiver 203 in the physical structure of the terminal device 20 shown in FIG. 2.
  • the communication module 802 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface. Alternatively, the communication interface may implement communication with other devices through the component having a transmitting and receiving function.
  • the above-mentioned component with a transmitting and receiving function may be implemented by an antenna and / or a radio frequency device.
  • the storage module 803 may be the memory 202 in the physical structure of the terminal device 20 shown in FIG. 1.
  • the apparatus 80 for sending a service request according to FIG. 8 in the embodiment of the present application may be part of the terminal device 20 shown in FIG. 2 or All.
  • the apparatus 70 for sending a service request or the apparatus 80 for sending a service request provided in the embodiments of the present application may be used to implement the functions of the terminal device in the methods implemented in the foregoing embodiments of the present application.
  • the apparatus 70 for sending a service request or the apparatus 80 for sending a service request provided in the embodiments of the present application may be used to implement the functions of the terminal device in the methods implemented in the foregoing embodiments of the present application.
  • FIG. 9 shows a possible structural diagram of a data transmission apparatus in a first network device involved in the foregoing embodiment.
  • the apparatus 90 for sending a service request may include: a determining unit 901 and a sending unit 902.
  • the determining unit 901 is configured to execute the process S501 in FIG. 5 or FIG. 6;
  • the sending unit 902 is configured to execute the processes S502 and S501a in FIG. 5 or FIG. 6.
  • all relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.
  • the apparatus 90 for sending a service request may further include a receiving unit 903.
  • the receiving unit 903 is configured to execute the process S501e in FIG. 6.
  • FIG. 11 illustrates a possible structural diagram of an apparatus for sending a service request in the first network device involved in the foregoing embodiment.
  • the apparatus 110 for sending a service request may include a processing module 1101 and a communication module 1102.
  • the processing module 1101 is configured to control and manage actions.
  • the communication module 1102 is used for communication with other network entities.
  • the processing module 1101 is configured to execute the process S501 in FIG. 5 or FIG. 6; the processing module 1101 is configured to execute the processes S502, S501a, and S501e in FIG. 5 or 6 through the communication module 1102.
  • the apparatus 110 for sending a service request may further include a storage module 1103 for storing program code and data.
  • the processing module 1101 may be the processor 301 in the physical structure of the first network device 30 shown in FIG. 3, and may be a processor or a controller.
  • it can be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor 1101 may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 1102 may be a transceiver 303 in the physical structure of the first network device 30 shown in FIG. 3.
  • the communication module 1102 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface.
  • the communication interface may implement communication with other devices through the component having a transmitting and receiving function.
  • the above-mentioned component with a transmitting and receiving function may be implemented by an antenna and / or a radio frequency device.
  • the storage module 1103 may be the memory 302 in the physical structure of the first network device 30 shown in FIG. 3.
  • the apparatus 110 for sending a service request according to FIG. 11 in the embodiment of the present application may be the first network device 30 shown in FIG. 3. Partial or full.
  • the device for sending a service request 90 or the device for sending a service request 110 provided in the embodiments of the present application may be used to implement the functions of the first network device in the methods implemented by the embodiments of the present application.
  • the parts related to the embodiments of the present application if specific technical details are not disclosed, please refer to the embodiments of the present application.
  • FIG. 12 illustrates a possible structural diagram of a data transmission apparatus in a second network device involved in the foregoing embodiment.
  • the apparatus 120 for sending a service request may include a receiving unit 1201, a determining unit 1202, and a sending unit 1203.
  • the receiving unit 1201 is configured to execute the process S501b in FIG. 6;
  • the determining unit 1202 is configured to execute the process S501c in FIG. 6;
  • the sending unit 1203 is configured to execute the process S501d in FIG.
  • all relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here.
  • FIG. 13 shows a possible structural diagram of an apparatus for sending a service request in the second network device involved in the foregoing embodiment.
  • the apparatus 130 for sending a service request may include a processing module 1301 and a communication module 1302.
  • the processing module 1301 is configured to control and manage actions.
  • the communication module 1302 is configured to communicate with other network entities.
  • the processing module 1301 is configured to execute the process S501c in FIG. 6; the processing module 1301 is configured to execute the processes S501b and S501d in FIG. 6 through the communication module 1302.
  • the apparatus 130 for sending a service request may further include a storage module 1303, configured to store program code and data.
  • the processing module 1301 may be the processor 401 in the physical structure of the second network device 40 shown in FIG. 4, and may be a processor or a controller.
  • it can be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor 1301 may also be a combination that realizes a computing function, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the communication module 1302 may be a transceiver 403 in the physical structure of the second network device 40 shown in FIG. 4.
  • the communication module 1302 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface.
  • the communication interface may implement communication with other devices through the component having a transmitting and receiving function.
  • the above-mentioned component with a transmitting and receiving function may be implemented by an antenna and / or a radio frequency device.
  • the storage module 1303 may be the memory 402 in the physical structure of the second network device 40 shown in FIG. 4.
  • the apparatus 130 for sending a service request according to FIG. 13 in this embodiment of the present application may be the second network device 40 shown in FIG. 4. Partial or full.
  • the apparatus 120 for sending a service request or the apparatus 130 for sending a service request provided in the embodiments of the present application may be used to implement the functions of the second network device in the methods implemented by the embodiments of the present application.
  • the parts related to the embodiments of the present application if specific technical details are not disclosed, please refer to the embodiments of the present application.
  • an embodiment of the present application provides a communication system including a terminal device described in any one of the foregoing embodiments, and a first network device described in any one of the foregoing embodiments.
  • an embodiment of the present application provides a communication system including a terminal device described in any one of the foregoing embodiments, a first network device described in any one of the foregoing embodiments, and a second network device described in any one of the foregoing embodiments.
  • the steps of the method or algorithm described in combination with the disclosure of this application may be implemented in a hardware manner, or may be implemented in a manner that a processor executes software instructions.
  • Software instructions can consist of corresponding software modules.
  • Software modules can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EPROM, EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC can be located in a core network interface device.
  • the processor and the storage medium can also exist as discrete components in the core network interface device.
  • the memory may be coupled to the processor, for example, the memory may exist independently and be connected to the processor through a bus.
  • the memory can also be integrated with the processor.
  • the memory may be used to store application program code that executes the technical solutions provided by the embodiments of the present application, and is controlled and executed by a processor.
  • the processor is configured to execute application program code stored in the memory, so as to implement the technical solution provided in the embodiment of the present application.
  • An embodiment of the present application further provides a chip system.
  • the chip system includes a processor, and is configured to implement the technical method of the embodiment of the present invention.
  • the chip system further includes a memory for storing program instructions and / or data necessary for the communication device in the embodiment of the present invention.
  • the chip system further includes a memory for the processor to call the application program code stored in the memory.
  • the chip system may be composed of one or more chips, and may also include chips and other discrete devices, which are not specifically limited in the embodiments of the present application.
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, the indirect coupling or communication connection of the device or unit, and may be electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may be separately physically included, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.
  • the above integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium.
  • the above software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute some steps of the method described in the embodiments of the present application.
  • the foregoing storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例提供一种发送业务请求的方法、装置及系统,涉及通信领域,实现对连接态终端设备新业务的接入控制,进而控制网络侧设备的负载。具体包括:终端设备从第一网络设备接收第一接入控制信息;在连接态时,若第一接入控制信息指示第一业务被禁止接入,终端设备停止向第一网络设备发送第一业务的业务请求。本申请用于发送业务请求。

Description

一种发送业务请求的方法、装置及系统 技术领域
本申请涉及通信领域,尤其涉及一种发送业务请求的方法、装置及系统。
背景技术
在移动通信中,空闲态的用户设备(User Equipment,UE)在业务发起时,先向网络侧的基站发送连接建立请求,与基站建立无线链路连接进入连接态,UE在连接态与基站进行数据传输。现有技术中,基站会控制一些通信业务的接入,例如通过广播消息控制一些通信业务类型是允许接入的,一些通信业务类型是不允许接入的,或一些通信业务类型是根据UE生成的随机数确定是否允许接入。这样,当UE请求连接建立时,UE根据基站广播的内容检查触发其请求建立连接的通信业务类型是否是基站所允许的。如果UE发起的业务类型是基站不允许的,则UE不发送连接建立请求,否则,发送连接建立请求。
但是,除了空闲态UE向基站发起通信业务之外,连接态的UE也会发起一些通信业务,例如,下载文件时向外打电话,浏览网页时有电话打进来。这时,由于UE已经在连接态,UE不需要再检查新发起的业务是否是eNB允许或禁止的。若大量UE当前与基站正在进行紧急通信,已经达到了基站负载的可接受程度,若此时连接态的UE发起新的业务,则会冲击到网络,导致基站过载,使得正在进行的紧急通信被打断。
发明内容
本申请实施例提供一种发送业务请求的方法、设备及系统,实现对连接态终端设备新业务的接入控制,进而控制网络侧设备的负载。
为达到上述目的,本申请的实施例采用如下技术方案:
第一方面,提供一种发送业务请求的方法,包括:终端设备从第一网络设备接收第一接入控制信息;在连接态时,若第一接入控制信息指示第一业务被禁止接入,终端设备停止向第一网络设备发送第一业务的业务请求。
通过本申请提供的发送业务请求的方法,根据从第一网络设备接收的第一接入控制信息的指示第一业务被禁止接入,终端设备连接态时停止向第一网络设备发送第一业务的业务请求,控制了终端设备在连接态时的新业务接入,进而控制了第一网络设备的负载,避免过载影响网络服务质量。
其中,所述新业务为终端设备在连接态时发起的又一业务。例如,当终端设备在进行语音通话业务时,终端设备又新发起网页浏览业务。本申请对于新业务的类型不进行具体限定。
需要说明的是,在本文中,描述的发起业务,是指终端设备实现一种业务通信的过程。在发起业务时,终端设备发送的消息,可以称之为终端设备发送的该业务的业务请求或者业务信令,当然,也可以有其他称呼,本申请对此不进行具体限定。
可选的,终端设备可以为UE或者其他用户侧的设备,终端设备还可以为用户侧 的设备中的部分功能单元或者芯片,本申请对于终端设备的类型不进行具体限定。
可选的,第一网络设备可以为基站的部分或全部;当第一网络设备为基站的部分时,第一网络设备可以为基站中的功能单元或者至少一个芯片。基站为无线网络中的接入网设备,负责将终端设备接入核心网,实现终端设备与核心网的通信。示例性的,基站可以为第四代移动通信(4th generation,4G)网络中的演进型基站(evolved nodeB,eNB),或者,基站可以为第五代移动通信(5th generation,5G)网络中的下一代无线接入基站(NR NodeB,gNB),本申请对于基站的类型不进行限定,在不同类型的网络中,基站可以有不同的类型。
可选的,第二网络设备可以为移动管理网元。移动管理网元为与网络中负责移动性管理的网元。示例性的,移动管理网元可以为4G网络中的移动管理实体(mobility management entity,MME),或者,移动管理网元可以为5G网络中的接入和移动性管理功能(Access and Mobility Management Function,AMF)实体,本申请对于移动管理网元的类型不进行限定,在不同类型的网络中,移动管理网元可以有不同的类型。需要说明的是,当第一网络设备为移动管理网元时,终端设备通过基站从第一网络设备接收第一接入控制信息。
当然,第一网络设备还可以为其他类型的网络设备,本申请对于第一网络设备的类型不进行具体限定。
结合第一方面,在一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:在连接态时,若第一业务未被禁止接入,终端设备向第一网络设备发送第一业务的业务请求。根据从第一网络设备接收的第一接入控制信息的指示第一业务未被禁止接入,终端设备连接态时向第一网络设备发送第一业务的业务请求,控制了终端设备在连接态时的业务接入,进而控制了第一网络设备的负载,避免过载影响网络服务质量。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,上述业务请求可以包括:公用数据网(Public Data Network,PDN)连接请求,或者,承载资源修改请求(bearer resource modification request),或者,服务请求(service request)。当然,业务请求的类型并不局限于此,业务请求还可以为终端设备支持的其他服务请求。
示例性的,服务请求可以为浏览网页的服务请求,或者,拨打电话的服务请求,或者其他,本申请对此不进行赘述。
需要说明的是,第一业务为终端设备的任一业务,并不是特指某一业务。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,终端设备从第一网络设备接收第一接入控制信息,具体可以包括:终端设备从第一网络设备接收系统消息,该系统消息包括第一接入控制信息。其中,系统消息由第一网络设备通过广播的形式发送。
可选的,上述系统消息可以包括系统信息块2(System Information Block Type2,SIB2)。或者,上述系统消息可以为配置的专用于发送第一接入控制信息的消息。本申请对于上述系统消息的类型不进行具体限定。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,终端 设备从第一网络设备接收第一接入控制信息,具体可以包括:终端设备从第一网络设备接收专用信令,该专用信令包括第一接入控制信息。
可选的,上述专用信令可以包括RRC连接重配置消息。或者,上述专用信令可以为配置的专用于发送第一接入控制信息的消息。本申请对于上述专用信令的类型不进行具体限定。
需要说明的是,终端设备从第一网络设备接收第一接入控制信息时,可以在空闲态(RRC_IDLE),也可以在连接态(RRC_CONNECTED),本申请对此不进行具体限定。
可选的,终端设备接收到第一接入控制信息后,可以在连接态判断第一接入控制信息指示第一业务是否被禁止接入,或者,也可以在空闲态判断第一接入控制信息指示第一业务是否被禁止接入,本申请对此不进行具体限定。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,第一接入控制信息可以包括下述信息中至少一项:使能指示信息、允许发起的业务类型、禁止发起的业务类型、允许发起业务的终端设备类型、禁止发起业务的终端设备类型、使能接入控制策略的指示信息。其中,使能指示信息用于指示终端设备是否需要根据第一接入控制信息确定第一业务是否被禁止接入。需要说明的是,在本实现方式中,只是列举了第一接入控制信息可能的内容,并不是对第一接入控制信息内容的具体限定。在实际应用中,可以根据实际需求配置第一接入控制信息的内容。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,接入控制策略可以包括以下至少一项:接入类型禁止(Access Class Barring,ACB)策略;或者,特定服务的接入控制(Service Specific Access Control,SSAC)策略;或者,ACB忽略(ACB skip)策略;或者,扩展接入限制(Extended Access Barring,EAB)策略;或者,数据通信中的特定应用的拥塞控制(Application specific Congestion control for Data Communication,ACDC)策略。需要说明的是,在本实现方式中,只是列举了接入控制策略可能的内容,并不是对接入控制策略内容的具体限定。在实际应用中,可以根据实际需求配置接入控制策略的内容。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,终端设备可以包括接入(Access Stratum,AS)层和非接入(Non Access Stratum,NAS)层。终端设备从第一网络设备接收第一接入控制信息,具体可以实现为:AS层从第一网络设备接收第一接入控制信息。NAS层为上层,AS层为下层,AS层从其他设备接收信息或消息,NAS层通过AS层向其他设备发送信息或消息。
需要说明的是,本文中描述的NAS层执行的某个操作,可以替换为上层执行该操作;本文中描述的AS层执行的某操作,可以替换为下层执行该操作。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:AS层向NAS层发送第一接入控制信息;NAS层根据第一接入控制信息判断第一业务是否被禁止接入。相应的,终端设备停止向第一网络设备发送第一业务的业务请求,包括:NAS层停止向AS层发送第一业务的业务请求信令。在该实现方式中,由NAS层决定是否发送业务请求,AS层仅转发接收到的第一接入控制信息。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:AS层提取第一接入控制信息中的第一指示信息,AS层向NAS层发送第一指示信息;NAS层根据第一指示信息判断第一业务是否被禁止接入。相应的,终端设备停止向第一网络设备发送第一业务的业务请求,包括:NAS层停止向AS层发送第一业务的业务请求信令。在该实现方式中,由NAS层决定是否发送业务请求,AS层解析接收到的第一接入控制信息并提取内部的上层NAS信息转发给NAS层。
其中,NAS层根据第一接入控制信息判断第一业务是否被禁止接入,可以在连接态发起第一业务时进行,或者,也可以在连接态发起第一业务之前进行,或者,也可以在空闲态进行,本申请对此不进行具体限定。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:NAS层在连接态向AS层发送第一业务的业务请求信令,AS层根据第一接入控制信息和第一业务的业务请求信令判断所述第一业务是否被禁止接入。相应的,终端设备停止向第一网络设备发送第一业务的业务请求,包括:AS层停止向第一网络设备发送第一业务的业务请求信令。在该实现方式中,由AS层决定是否向网络侧发送业务请求,AS层接收到NAS层发送的第一业务的业务请求信令,AS层根据接收到的第一接入控制信息决定是否向网络侧发送第一业务的业务请求信令。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:NAS层在连接态向AS层发送第一业务的业务请求的信令及接入控制策略指示信息,AS层参照接入控制策略指示信息所指示的接入控制策略,根据第一接入控制信息和第一业务请求的信令判断第一业务是否被禁止接入。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,AS层根据第一接入控制信息和第一业务的业务请求信令判断第一业务是否被禁止接入,包括:AS层解析第一业务的业务请求信令,获取第一业务的业务类型;AS层根据第一接入控制信息和第一业务的业务类型判断第一业务是否被禁止接入。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:NAS层在连接态向AS层发送第一业务的业务请求信令时,还向AS层发送第一业务的业务类型。相应的,AS层根据第一接入控制信息和第一业务的业务请求信令判断第一业务是否被禁止接入,包括:AS层根据第一接入控制信息和第一业务的业务类型判断第一业务是否被禁止接入。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,当AS层判断第一业务被禁止接入时,本申请提供的发送业务请求的方法还可以包括:AS层向NAS层发送响应信息,该响应信息指示第一业务被禁止接入。
结合第一方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:AS层向NAS层发送响应信息时,向NAS层发送第一业务被禁止接入的原因。
需要说明的是,第一方面或第一方面中任一种可能的实现方式提供的发送业务请 求的方法,可以由终端设备执行,也可以由终端设备中的功能单元或者芯片执行,本申请对此不进行具体限定。
第二方面,本申请提供另一种发送业务请求的方法,包括:确定第一接入控制信息,第一接入控制消息用于控制终端设备连接态的业务请求;发送第一接入控制信息。
通过本申请提供的发送业务请求的方法,通过第一接入控制信息控制终端设备连接态的业务请求,控制了终端设备在连接态时的业务接入,进而控制了网络侧的负载,避免过载影响网络服务质量。
需要说明的是,确定第一接入控制信息可以周期性的执行,也可以在网络负载满足预设条件的时候执行,本申请对于执行确定第一接入控制信息的时机不进行具体限定。
结合第二方面,在一种可能的实现方式中,上述业务请求可以包括:PDN连接请求,或者,承载资源修改请求,或者,服务请求。当然,业务请求的类型并不局限于此,业务请求还可以为终端设备支持的其他服务请求。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,发送第一接入控制信息,可以包括:广播系统消息,该系统消息包括第一接入控制信息;或者,发送专用信令,专用信令包括第一接入控制信息。
可选的,上述系统消息可以包括SIB2消息。或者,上述系统消息可以为配置的专用于发送第一接入控制信息的消息。本申请对于上述系统消息的类型不进行具体限定。可选的,上述专用信令可以包括RRC连接重配置消息。或者,上述专用信令可以为配置的专用于发送第一接入控制信息的消息。本申请对于上述专用信令的类型不进行具体限定。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,第一接入控制信息包括下述信息中至少一项:使能指示信息、允许发起的业务类型、禁止发起的业务类型、允许发起业务的终端设备类型、禁止发起业务的终端设备类型、使能接入控制策略的指示信息;其中,使能指示信息用于指示终端设备是否需要根据第一接入控制信息确定第一业务是否被禁止接入。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,接入控制策略可以包括以下至少一项:ACB策略;或者,SSAC策略;或者,ACB skip策略;或者,EAB策略;或者,数据通信中的ACDC策略。需要说明的是,在本实现方式中,只是列举了接入控制策略可能的内容,并不是对接入控制策略内容的具体限定。在实际应用中,可以根据实际需求配置接入控制策略的内容。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请第二方面提供的发送业务请求的方法还可以包括:确定第一接入控制信息,具体可以实现为:根据自身的负载状况,确定确定第一接入控制信息。在该实现方式中,执行第二方面提供的发送业务请求的方法的设备根据自己负载主动确定第一接入控制信息,节约了系统传输资源。
其中,根据负载状况确定第一接入控制信息的方式,可以根据实际需求配置,本申请对此不进行具体限定。例如,预先配置预设对应关系,该预设对应关系中包括不同的负载状况以及其对应的第一接入控制信息的内容,确定第一接入控制信息时查询 预设对应关系即可得到。再例如,预先建立负载状况与第一接入控制信息内容的模型,根据该模型及负载状况,确定第一接入控制信息的内容。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请第二方面提供的发送业务请求的方法还可以包括:从第二网络设备接收第二接入控制信息,第二接入控制信息用于控制终端设备连接态的业务请求。相应的,确定第一接入控制信息,具体可以实现为:根据第二接入控制信息,确定第一接入控制信息。
其中,根据第二接入控制信息确定第一接入控制信息的方式,可以根据实际需求配置,本申请对此不进行具体限定。例如,第二接入控制信息的内容可以直接是第一接入控制信息的内容。再例如,预先配置预设对应关系,该预设对应关系中包括不同的第二接入控制信息的内容以及其对应的第一接入控制信息的内容,确定第一接入控制信息时查询预设对应关系即可得到。
结合第二方面或上述任一种可能的实现方式,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:向第二网络设备发送用于指示负载状况的负载指示信息。这样一来,第二网络设备根据负载指示信息确定第二接入控制信息。
需要说明的是,第二方面或第二方面中任一种可能的实现方式提供的发送业务请求的方法,可以由第一网络设备执行,也可以由第一网络设备中的功能单元或者芯片执行,本申请对此不进行具体限定。对于第一网络设备已经在上述第一方面中进行了详细描述,此处不再进行赘述。
第三方面,提供另一种发送业务请求的方法,包括:确定第二接入控制信息,第二接入控制信息用于控制终端设备连接态的业务请求;向第一网络设备或终端设备发送第二接入控制信息。
通过本申请提供的发送业务请求的方法,通过第二接入控制信息控制终端设备连接态的业务请求,控制了终端设备在连接态时的业务接入,进而控制了网络侧的负载,避免过载影响网络服务质量。
结合第三方面,在一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:从第一网络设备接收用于指示第一网络设备的负载状况的负载指示信息。相应的,确定第二接入控制信息,具体可以实现为:根据负载指示信息确定第二接入控制信息。
其中,根据负载指示信息确定第二接入控制信息的方式,可以根据实际需求配置,本申请对此不进行具体限定。例如,预先配置预设对应关系,该预设对应关系中包括不同的负载状况以及其对应的第二接入控制信息的内容,确定第二接入控制信息时查询预设对应关系即可得到。再例如,预先建立负载状况与第二接入控制信息内容的模型,根据该模型及负载状况,确定第二接入控制信息的内容。
需要说明的是,第三方面或第三方面中任一种可能的实现方式提供的发送业务请求的方法,可以由第二网络设备执行,也可以由第二网络设备中的功能单元或者芯片执行,本申请对此不进行具体限定。对于第二网络设备已经在上述第一方面中进行了详细描述,此处不再进行赘述。
第四方面,本申请实施例提供了一种终端设备,该终端设备可以实现上述方法示例中的终端设备的功能,所述功能可以通过硬件实现,也可以通过硬件执行相应的软 件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
结合第四方面,在一种可能的实现方式中,该终端设备的结构中包括处理器和收发器,该处理器被配置为支持该终端设备执行上述方法中相应的功能。该收发器用于支持该终端设备与其他设备之间的通信。该终端设备还可以包括存储器,该存储器用于与处理器耦合,其保存该终端设备必要的程序指令和数据。
第五方面,本申请实施例提供了一种第一网络设备,该第一网络设备可以实现上述方法示例中的第一网络设备的功能,所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
结合第五方面,在一种可能的实现方式中,该第一网络设备的结构中包括处理器和收发器,该处理器被配置为支持该第一网络设备执行上述方法中相应的功能。该收发器用于支持该第一网络设备与其他设备之间的通信。该第一网络设备还可以包括存储器,该存储器用于与处理器耦合,其保存该第一网络设备必要的程序指令和数据。
第六方面,本申请实施例提供了一种第二网络设备,该第二网络设备可以实现上述方法示例中的第二网络设备的功能,所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
结合第六方面,在一种可能的实现方式中,该第二网络设备的结构中包括处理器和收发器,该处理器被配置为支持该第二网络设备执行上述方法中相应的功能。该收发器用于支持该第二网络设备与其他设备之间的通信。该第二网络设备还可以包括存储器,该存储器用于与处理器耦合,其保存该第二网络设备必要的程序指令和数据。
第七方面,本申请实施例提供了一种计算机存储介质,用于储存为上述终端设备所用的计算机软件指令,其包含用于执行上述第一方面所设计的程序。
第八方面,本申请实施例提供了一种计算机存储介质,用于储存为上述第一网络设备所用的计算机软件指令,其包含用于执行上述第二方面所设计的程序。
第九方面,本申请实施例提供了一种计算机存储介质,用于储存为上述第二网络设备所用的计算机软件指令,其包含用于执行上述第三方面所设计的程序。
第十方面,本申请实施例提供了一种通信系统,包括上述任一方面或任一可能的实现方式描述的终端设备及第一网络设备。
结合第十方面,在一种可能的实现方式中,该通信系统还可以包括上述任一方面或任一可能的实现方式描述的第二网络设备。
第十一方面,本申请实施例提供了另一种通信系统,包括上述任一方面或任一可能的实现方式描述的终端设备及第二网络设备。
上述第四方面至第十一方面提供的方案,用于实现上述第一方面或第二方面或第三方面提供的发送业务请求的方法,因此可以与第一方面或第二方面或第三方面达到相同的有益效果,此处不再进行赘述。
附图说明
图1为现有技术提供的一种通信系统的架构示意图;
图2为本申请实施例提供的一种终端设备的结构示意图;
图3为本申请实施例提供的一种第一网络设备的结构示意图;
图4为本申请实施例提供的一种第二网络设备的结构示意图;
图5为本申请实施例提供的一种发送业务请求的方法的流程示意图;
图6为本申请实施例提供的另一种发送业务请求的方法的流程示意图;
图7为本申请实施例提供的一种发送业务请求的装置的结构示意图;
图8为本申请实施例提供的另一种发送业务请求的装置的结构示意图;
图9为本申请实施例提供的再一种发送业务请求的装置的结构示意图;
图10为本申请实施例提供的又一种发送业务请求的装置的结构示意图;
图11为本申请实施例提供的又一种发送业务请求的装置的结构示意图;
图12为本申请实施例提供的又一种发送业务请求的装置的结构示意图;
图13为本申请实施例提供的又一种发送业务请求的装置的结构示意图。
具体实施方式
基于此,本申请提出一种发送新的业务传输请求的方法,用于控制终端设备在连接态发起业务,其基本原理是:终端设备根据第一接入控制信息的指示,在连接态发起业务时,若第一接入控制信息指示该业务被禁止接入,则停止发起该业务。因此,只要根据需求配置第一接入控制信息,即可对连接态终端发起业务进行控制,进而控制网络侧的负载,保证网络服务质量。
本申请中描述的终端设备,可以为用户使用的移动通信设备的部分或全部。例如终端设备可以为UE或者其他。其中,移动通信设备可以为手机、平板电脑、笔记本电脑、超级移动个人计算机(Ultra-mobile Personal Computer,UMPC)、上网本、个人数字助理(Personal Digital Assistant,PDA)、电子书、移动电视、穿戴设备、个人电脑(Personal Computer,PC)等等。在不同制式的通信系统中,终端设备可以有不同的称呼。本申请实施例对于终端设备的类型也不进行具体限定。
本申请中描述的第一网络设备可以为基站的部分或全部;当第一网络设备为基站的部分时,第一网络设备可以为基站中的功能单元或者至少一个芯片。基站,即无线通信系统中为终端设备提供通信服务的网络侧设备。在不同制式的无线通信系统中,基站可以有不同的称呼,但均可以理解为本申请中描述的基站。本申请实施例对于基站的类型也不进行具体限定。例如,通用移动通信系统(Universal Mobile Telecommunications System,UMTS)中的基站称之为基站(Base Station,BS);LTE系统中的基站称之为eNB等等,此处不再一一列举。凡是无线通信系统中为终端设备提供通信服务的网络侧设备,均可以理解为本申请描述的基站。
本申请中描述的第二网络设备可以为移动管理网元的部分或全部;当第二网络设备为移动管理网元的部分时,第二网络设备可以为移动管理网元中的功能单元或者至少一个芯片。移动管理网元为与网络中负责移动性管理的网元。在不同制式的通信系统中,移动管理网元可以有不同的称呼,但均可以理解为本申请中描述的移动管理网元。本申请实施例对于移动管理网元的类型也不进行具体限定。示例性的,移动管理网元可以为4G网络中的MME,或者,移动管理网元可以为5G网络中的AMF实体。
本申请提供的发送业务请求的方法,应用于如图1所示的通信系统架构中。如图1所示,该通信系统架构中包括基站101、终端设备102及移动管理网元103。终端设备102与基站101进行通信,接入移动管理网元103所属的核心网。
需要说明的是,图1仅仅是通过举例对通信系统架构的示意。对于通信系统架构 中包括的基站101、终端设备102及移动管理网元103的数量、类型,均可以根据实际需求配置,图1并不是对此内容的具体限定。为了描述清晰,图1中示意的基站101代表了本申请描述的第一网络设备,图1中示意的移动管理网元103代表了本申请描述的第二网络设备,可以直接替换应用,此处不再进行赘述。
其中,图1示出的无线通信系统架构,可以为LTE网络、或者UMTS网络,或者其他网络。对于本申请的方案所应用的网络的类型,本申请实施例对此并不进行具体限定。
在描述本申请实施例之前,此处对本申请实施例中涉及的名词进行解释。
接入控制信息,是指用于控制终端设备业务接入的信息,根据其内容可以确定出业务是否被禁止接入。本申请根据确定信息的执行主体不同,涉及第一接入控制信息、第二接入控制信息。
第一接入控制信息,是终端设备从网络设备接收到的信息,用于指示业务是否被禁止接入。
第二接入控制信息,是网络设备间交互的信息,用于确定第一接入控制信息。
接入控制策略,是预先设定的用于控制接入的规则。当前通信系统中已有的公知的接入控制策略。例如接入控制策略可以为ACB策略;或者,SSAC策略;或者,ACB skip策略;或者,EAB策略;或者,数据通信中的ACDC策略。
本申请实施例的说明书和权利要求书中的术语“第一”和“第二”等是用于区别不同的对象,而不是用于描述对象的特定顺序。例如,第一网络设备和第二网络设备等是用于区别不同的网络设备,而不是用于描述设备的特定顺序。
在本申请实施例中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念,便于理解。
下面结合附图,对本申请的实施例进行具体阐述。
一方面,本申请实施例提供一种终端设备。图2示出的是与本申请各实施例相关的一种终端设备20。终端设备20可以为图1所示的通信系统架构中的终端设备102。如图2所示,终端设备20可以包括:处理器201、存储器202、收发器203。
下面结合图2对终端设备20的各个构成部件进行具体的介绍:
存储器202,可以是易失性存储器(volatile memory),例如随机存取存储器(random-access memory,RAM);或者非易失性存储器(non-volatile memory),例如只读存储器(read-only memory,ROM),快闪存储器(flash memory),硬盘(hard disk drive,HDD)或固态硬盘(solid-state drive,SSD);或者上述种类的存储器的组合,用于存储可实现本申请方法的程序代码、以及配置文件。
处理器201是终端设备20的控制中心,可以是一个中央处理器(central processing unit,CPU),也可以是特定集成电路(Application Specific Integrated Circuit,ASIC),或者是被配置成实施本申请实施例的一个或多个集成电路,例如:一个或多个微处理器(digital signal processor,DSP),或,一个或者多个现场可编程门阵列(Field Programmable Gate Array,FPGA)。处理器201可以通过运行或执行存储在存储器202 内的软件程序和/或模块,以及调用存储在存储器202内的数据,执行终端设备20的各种功能。
收发器203用于终端设备20与其他单元进行交互。示例性的,收发器203可以为终端设备20的收发天线或者收发功能单元。
具体的,处理器201通过运行或执行存储在存储器202内的软件程序和/或模块,以及调用存储在存储器202内的数据,执行如下功能:
通过收发器203从第一网络设备接收第一接入控制信息;在连接态时,若第一接入控制信息指示第一业务被禁止接入,则终端设备停止向第一网络设备发送第一业务的业务请求。
另一方面,本申请实施例提供一种第一网络设备。图3示出的是与本申请各实施例相关的一种第一网络设备30。第一网络设备30可以为图1所示的通信系统架构中的第一网络设备101。如图3所示,第一网络设备30可以包括:处理器301、存储器302、收发器303。
下面结合图3对第一网络设备30的各个构成部件进行具体的介绍:
存储器302,可以是易失性存储器,例如RAM;或者non-volatile memory,例如ROM,flash memory,HDD或SSD;或者上述种类的存储器的组合,用于存储可实现本申请方法的程序代码、以及配置文件。
处理器301是第一网络设备30的控制中心,可以是一个CPU,也可以是ASIC,或者是被配置成实施本申请实施例的一个或多个集成电路,例如:一个或多个DSP,或,一个或者多个FPGA。处理器301可以通过运行或执行存储在存储器302内的软件程序和/或模块,以及调用存储在存储器302内的数据,执行第一网络设备30的各种功能。
收发器303用于第一网络设备30与其他单元进行交互。示例性的,收发器303可以为第一网络设备30的收发天线或者收发电路或者收发装置。
具体的,处理器301通过运行或执行存储在存储器302内的软件程序和/或模块,以及调用存储在存储器302内的数据,执行如下功能:
确定第一接入控制信息,第一接入控制消息用于控制终端设备连接态的业务请求;通过收发器303发送第一接入控制信息。
另一方面,本申请实施例提供一种第二网络设备。图4示出的是与本申请各实施例相关的一种第二网络设备40。第一网络设备40可以为图1所示的通信系统架构中的第二网络设备103。如图4所示,第二网络设备40可以包括:处理器401、存储器402、收发器403。
下面结合图4对第二网络设备40的各个构成部件进行具体的介绍:
存储器402,可以是易失性存储器,例如RAM;或者non-volatile memory,例如ROM,flash memory,HDD或SSD;或者上述种类的存储器的组合,用于存储可实现本申请方法的程序代码、以及配置文件。
处理器401是第二网络设备40的控制中心,可以是一个CPU,也可以是ASIC,或者是被配置成实施本申请实施例的一个或多个集成电路,例如:一个或多个DSP,或,一个或者多个FPGA。处理器401可以通过运行或执行存储在存储器402内的软 件程序和/或模块,以及调用存储在存储器402内的数据,执行第二网络设备40的各种功能。
收发器403用于第二网络设备40与其他单元进行交互。示例性的,收发器403可以为第二网络设备40的收发天线或者收发电路或者收发装置。
具体的,处理器401通过运行或执行存储在存储器402内的软件程序和/或模块,以及调用存储在存储器402内的数据,执行如下功能:
确定第二接入控制信息,第二接入控制信息用于控制终端设备连接态的业务请求;通过收发器403向第一网络设备或终端设备发送第二接入控制信息。
再一方面,本申请实施例提供一种发送业务请求的方法,应用于终端设备与第一网络设备的交互过程中。本申请实施例提供的发送业务请求的方法,可以是终端设备和/或第一网络设备执行,也可以是终端设备和/或第一网络设备中的功能单元或者芯片执行,本申请实施例对此不进行具体限定。在下面实施例的描述的终端设备和/或第一网络设备执行某动作,可以替换为终端设备和/或第一网络设备的功能单元或者芯片执行该动作,不再一一赘述。终端设备和/或第一网络设备内执行本申请提供的发送业务请求的方法的功能单元或者芯片可以称之为发送业务请求的装置。
如图5所示,本申请实施例提供的发送业务请求的方法可以包括:
S501、第一网络设备确定第一接入控制信息。
其中,第一接入控制消息用于控制终端设备连接态的业务请求。
可选的,第一网络设备可以为基站的部分或全部;当第一网络设备为基站的部分时,第一网络设备可以为基站中的功能单元或者至少一个芯片。基站为无线网络中的接入网设备,负责将终端设备接入核心网,实现终端设备与核心网的通信。示例性的,基站可以为4G网络中的eNB,或者,基站可以为5G网络中的gNB,本申请对于基站的类型不进行限定,在不同类型的网络中,基站可以有不同的类型。
其中,第一接入控制信息用于控制连接态终端设备的业务接入,第一接入控制信息的内容指示了处于连接态的终端设备的哪些业务被网络侧所禁止,哪些业务被网络侧允许。需要说明的是,被网络侧禁止或允许,可以是第一网络设备禁止或允许,也可以是其他网络设备禁止或允许,本申请实施例对此不进行具体限定。所述禁止指的是禁止连接态的终端设备发起某些业务,即禁止终端设备的某些业务接入到网络。例如,第一接入控制信息指示连接态的终端设备的业务A禁止接入网络,则当终端设备在发起业务A的业务请求时,根据第一接入控制信息的指示,认为业务A的业务请求是禁止的,即不向网络设备发送业务A的业务请求。同样的,所述允许指的是允许连接态的终端设备发起某些业务,即允许终端设备的某些业务接入到网络。例如,第一接入控制信息指示连接态的终端设备的业务B允许接入网络,则当终端设备在发送业务B的业务请求时,根据第一接入控制信息的指示,认为业务B的业务请求是允许的,即向网络设备发送业务B的业务请求。本文中,不禁止与允许意义相同,禁止与不允许意义相同。本文中,若无特别说明,终端设备处于连接态。
可选的,第一接入控制信息可以包括下述信息中至少一项:使能指示信息、允许发起的业务类型、禁止发起的业务类型、允许发起业务的终端设备类型、禁止发起业务的终端设备类型、使能接入控制策略的指示信息。
其中,使能指示信息用于指示终端设备是否需要根据第一接入控制信息确定第一业务是否被禁止接入,即使能或去使能连控制连接态终端设备发送业务请求的机制。例如,当该使能指示信息指示使能该机制时,终端设备根据网络设备发送的接入控制信息判断其发送业务请求是否被禁止,当该使能指示信息指示去使能该机制时,则终端设备不需要根据接入控制信息判断其发送业务请求是否被禁止,而是根据现在技术直接发送业务请求。进一步地,该使能指示信息可以是显示的指示信息,如ConnectionAccessEnable为Ture或Enable表示使能,其中ConnectionAccessEnable可以解释为连接态接入使能指示信息,即上述使能指示信息,或者ConnectionAccessEnable为False或Disable表示去使能。或者,该使能指示信息还可以是隐式的指示信息,如网络设备发送了与连接态接入控制相关的信息时,表示使能了上述连接态接入控制机制,若网络设备没有发送与连接态接入控制相关的信息时,则表示去使能上述连接态接入控制机制。需要说明的是,此处只是列举了第一接入控制信息可能的内容,并不是对第一接入控制信息内容的具体限定。在实际应用中,可以根据实际需求配置第一接入控制信息的内容。
允许发起的业务类型指的是网络设备允许连接态终端设备发起的业务的业务类型,例如,允许发起的业务类型可以包括以下一种或多种的组合,被叫业务(Mobile terminating call)、紧急呼叫业务(Emergency call)、主叫业务(Mobile originating call)、信令业务(Signalling)、电路域回退(CS fallback)、多媒体电话业务(Multi-Media Telephony,MMTEL)、语音业务(Voice)、视频业务(Video)、短信业务(Short Message Service,SMS)、时延容忍业务(Delay tolerance service)等。需要说明的是,上述对允许发起的业务类型的示例,并不构成限定。
禁止发起的业务类型指的是网络设备禁止连接态终端设备发起的业务的业务类型,例如,禁止发起的业务类型可以包括以下一种或多种的组合,被叫业务(Mobile terminating call)、紧急呼叫业务(Emergency call)、主叫业务(Mobile originating call)、信令业务(Signalling)、电路域回退(CS fallback)、多媒体电话业务(Multi-Media Telephony,MMTEL)、语音业务(Voice)、视频业务(Video)、短信业务(Short Message Service,SMS)、时延容忍业务(Delay tolerance service)等。需要说明的是,上述对禁止发起的业务类型的示例,并不构成限定。
示例性的,允许发起业务的终端设备类型可以是机器类型通信(Machine Type Communication,MTC)终端设备或窄带物联网(Narrow Band Internet of Thing,NB-IoT)终端设备或水表或电表或可穿戴设备等。需要说明的是,上述对允许发起业务的终端设备类型的示例,并不构成限定。
示例性的,禁止发起业务的终端设备类型可以是机器类型通信(Machine Type Communication,MTC)终端设备或窄带物联网(Narrow Band Internet of Thing,NB-IoT)终端设备或水表或电表或可穿戴设备等。需要说明的是,上述对禁止发起业务的终端设备类型的示例,并不构成限定。
使能接入控制策略的指示信息指的是网络设备指示终端设备根据指定的接入控制策略确定连接态时能否发起业务。其中,接入控制策略是预先配置或现在3GPP TS36.331中的接入控制准则。
示例性的,接入控制策略可以包括以下至少一项:ACB策略;或者,SSAC策略;或者,ACB skip策略;或者,EAB策略;或者,数据通信中的ACDC策略。
当然,在实际应用中,可以根据实际需求配置接入控制策略的内容,此处只是对接入控制策略的内容举例说明,并不是对此的具体限定。
其中,ACB策略是3GPP的Release8中提出的接入控制策略,终端设备使用一个随机数和一个定时器,基于接入的类型进行接入控制。
SSAC策略(Scheme/Mechanism)为3GPP的Release9中提出的接入控制策略,在该策略中,网络广播禁入因子和随机定时器,实际决策是在UE的IMS层,其适用于连接态和空闲态,用于解决因大量终端设备同时接入所引起的网络过载问题。
ACB skip策略为3GPP的Release12引入的用于控制IMS语音和视频用户忽略ACB策略的方法。
EAB策略为3GPP的Release11中提出的接入控制策略,在该策略中,准许网络禁止低优先级UE。该方法基于一个bitmap,0-9中的每个class可以被禁止或被准许。
数据通信中的ACDC策略为3GPP的Release13中提出的接入控制策略,在该策略中,准许禁止特定应用的业务,基于全球应用标识将应用分类,网络针对每类应用广播禁止参数(禁止因子和定时器)。
例如,使能接入控制策略的指示信息为AccessControlStrategy,一种方法是只指示一种策略,即使用枚举类型定义,如AccessControlStrategy为ENUMERATED{ACB,SSAC,ACBskip,EAB,ACDC,…},当AccessControlStratey值为ACB时,终端设备根据该指示信息,使用现在技术中的ACB策略对终端设备在连接态打算发送的业务请求进行检查,检查是否符合ACB策略的接入控制,若检查结果为允许接入,则终端设备发送该业务请求,否则不发送该业务请求。另一种方法是网络设备指示一种或多种策略,可以使用AccessControlStrategyList来定义,其中AccessControlStrategyList由SEQUENCE(SIZE(0..maxValue))OF AccessControlStrategy定义,maxValue为网络允许的最大的策略个数,AccessControlStrategy的定义如前一种方法。或者,网络设备指示一种或多种策略还可以使用比特图(Bitmap)来定义,例如,假设一共5种策略,依次为ACB,SSAC,ACBskip,EAB,ACDC,则可以定义比特图AccessControlStrategyBitmap为BIT STRING(5),即共5个比特,每个比特依次表示上述5种策略,某比特位为“1”时表示使能该策略,则终端设备需要根据该策略检查是否允许发送业务请求,某比特为“0”时表示去使能该策略,则终端设备不需要根据该策略检查是否允许发起业务。其中“1”和“0”的意义可以互换。例如,AccessControlStrategyBitmap为00110,则表示使能ACBskip,EAB策略,去使能其他策略。
可选的,在S501中,第一网络设备可以周期性的确定第一接入控制信息,也可以在其负载状况满足预设条件的时候确定第一接入控制信息,本申请实施例对于执行S501的时机不进行具体限定,可以根据实际需求配置。
其中,周期性确定第一接入控制信息时,周期的具体间隔可以根据实际需求配置;预设条件的内容也可以根据实际需求配置;本申请实施例对此均不进行具体限定。
可选的,在S501中,第一网络设备确定第一接入控制信息可以通过下述方案中任 一种实现:
方案1、第一网络设备根据自身负载状况确定第一接入控制信息。
可选的,在方案1中,可以预先配置负载状况与第一接入控制信息的内容的预设对应关系,在执行S501时,查询该预设对应关系即可。该预设对应关系的内容,可以根据实际经验配置,本申请对于配置过程不进行限定。
示例性的,如表1所示,示意了一种预设对应关系的内容。如表1所示,假设第一网络设备执行S501时,负载状态为15%,则确定第一接入控制信息的内容时,以第一接入控制信息包含禁止发起的业务类型为例,则禁止发起的业务类型可以为A类型业务、B类型业务。
表1
Figure PCTCN2018090309-appb-000001
需要说明的是,表1只是对预设对应关系的示例性说明,并不是对预设对应关系内容及形式的限定。
可选的,在方案1中,可以预先通过学习建立负载状况与第一接入控制信息的模型,当执行S501时,将负载状况输入模型中得到第一接入控制信息。
需要说明的是,对于根据负载状况确定第一接入控制信息的过程,还可以采用其他方式,本申请实施例对此不进行具体限定。
方案2、第一网络设备接收第二网络设备发送的第二接入控制信息,根据第二接入控制信息确定第一接入控制信息。其中,第二接入控制信息由第二网络设备根据第一网络设备的负载状况确定。
可选的,在方案2中,如图6所示,在S501之前,本申请实施例提供的发送业务请求的方法还可以包括S501a至S501e。
S501a、第一网络设备向第二网络设备发送指示负载状况的负载指示信息。
其中,负载指示信息用于指示第一网络设备的负载状况,负载指示信息可以为字符串、代码等任何形式,本申请实施例对此不进行具体限定。需要说明的是,负载指示信息与负载状况的对应关系,可以根据实际需求配置,本申请实施例对此不进行具体限定。
示例性的,负载指示信息可以用二进制字符串表示,负载指示信息与负载状况的对应关系可以用对应关系的形式体现,执行S501a时查询对应关系获取负载指示信息并发送。
S501b、第二网络设备从第一网络设备接收负载指示信息。
S501c、第二网络设备确定第二接入控制信息。
其中,第二网络设备根据S501b中接收的负载指示信息,确定第二接入控制信息。
在一种可能的实现方式中,第二网络设备可以根据负载指示信息直接确定第二接 入控制信息。第二网络设备根据负载指示信息确定第二接入控制信息的实现方式,可以参考方案1中第一网络设备根据负载状况确定第一接入控制信息的实现方式,此处不再进行赘述。
在另一种可能的实现方式中,第二网络设备根据负载指示信息确定负载状况,再根据负载状况确定第二接入控制信息,第二网络设备根据负载状况确定第二接入控制信息的实现方式,可以参考方案1中第一网络设备根据负载状况确定第一接入控制信息的实现方式,此处不再进行赘述。
需要说明的是,第二接入控制信息的内容可以和第一接入控制信息的内容完全相同,或者,第二接入控制信息的内容可以与第一接入控制信息的内容对应,本申请实施例对此不进行具体限定。
S501d、第二网络设备向第一网络设备发送第二接入控制信息。
第二网络设备通过其与第一网络设备的通信接口,传输第二接入控制信息。
S501e、第一网络设备从第二网络设备接收第二接入控制信息。
方案3:第一网络设备接收第二网络设备发送的第二接入控制信息,根据第二接入控制信息确定第一接入控制信息。其中,第二接入控制信息由第二网络设备的自身的负载状况确定。
具体的,将方案2中的S501a至S5-1e替换为S501c、S502d、S501e,即可实现方案3。
一种实现方式是,第二网络设备根据自身的负载状况确定第二接入控制信息,第二接入控制信息可以是显示的类似于第一接入控制信息,或是第二接入控制信息用于指示第二网络设备的负载状况,第一网络设备根据第二接入控制信息指示的第二网络设备的负载状况确定第一接入控制信息。
需要说明的是,本文中,所有网络设备“根据A确定B”中的“根据A”都是可选内容,即网络设备也可以根据其他信息来确定。
在方案2或者方案3中,S501的具体实现可以包括但不限于下述实现1和实现2。
实现1:第二接入控制信息与第一接入控制信息相同,第一网络设备接收到第二接入控制信息即可确定出第一接入控制信息。在实现1中,第一网络设备接收到第二网络设备确定的第二接入控制信息,直接得到第一接入控制信息。此时,第二接入控制信息可以直接通过第一网络设备发送到终端设备,即将第二接入控制信息封装进第一接入控制信息发送至终端设备。
实现2、第二接入控制信息与第一接入控制信息相对应,第一网络设备接收到第二接入控制信息后,根据对应关系确定出第一接入控制信息。例如,第一网络设备根据第二接入控制信息及第一网络设备与终端设备之间的通信协议确定第一接入控制信息,此时第一接入控制信息与第二接入控制信息只有数据传输格式上的区别,其实质意义相同,即第一网络设备将第二接入控制信息重新封装成第一接入控制信息发送至终端设备。
需要说明的是,在S501中描述的根据第一网络设备的负载状况确定第一接入控制信息,在实际应用中,也可以根据其他网络设备的负载状况确定第一接入控制信息,具体实现相同,此处不再进行赘述。
S502、第一网络设备发送第一接入控制信息。
具体的,在S502中第一网络设备发送第一接入控制信息,可以通过但不限于下述两种实现方式:
第一种实现方式:系统消息(system information),该系统消息包括第一接入控制信息。
可选的,上述系统消息可以包括SIB1、SIB2消息。或者,上述系统消息可以为专门用于发送第一接入控制信息的消息。本申请对于系统消息的类型不进行具体限定。
第二种实现方式:专用信令(Dedicated signalling),该专用信令包括第一接入控制信息。
可选的,上述专用信令可以包括RRC连接重配置消息。或者,上述专用信令可以为专门用于发送第一接入控制信息的消息。本申请对于专用信令的类型不进行具体限定。
S503、终端设备从第一网络设备接收第一接入控制信息。
对应于S502中的两种实现方式,S503中终端设备从第一网络设备接收第一接入控制信息也可以通过但不限于下述两种实现方式:
实现方式A:终端设备从第一网络设备接收系统消息,该系统消息包括第一接入控制信息。
实现方式B:终端设备从第一网络设备接收专用信令,该专用信令包括第一接入控制信息。
需要说明的是,S503中终端设备接收到第一接入控制信息时,可以处于空闲(IDLE)态,也可以处于连接态。
具体的,在终端设备内部,终端设备可以包括AS层和NAS层。在S503中,终端设备从第一网络设备接收第一接入控制信息,具体实现为:AS层从第一网络设备接收第一接入控制信息。AS层从/向其他设备接收/发送信息或消息,NAS层通过AS层从/向其他设备接收/发送信息或消息。
进一步,可选的,如图6所示,在S503之后,本申请实施例提供的发送业务请求的方法还可以包括S503a。
S503a、终端设备根据第一接入控制信息确定第一业务是否被禁止接入。
可选的,终端设备可以在S503中接收到第一接入控制信息时执行S503a,也可以在连接态发起第一业务时执行S503a,本申请实施例对此不进行具体限定。如前所述,终端设备可以在IDLE态或者连接态接收到第一接入控制信息,那么,终端设备也可以在IDLE态或者连接态根据第一接入控制信息确定第一业务是否被禁止接入。
进一步的,当终端设备包括AS层和NAS层时,S503a的具体实现可以有多种,下面一一描述。
一种可能的实现中,在S503中AS层从第一网络设备接收第一接入控制信息,AS层向NAS层发送第一接入控制信息;NAS层根据第一接入控制信息判断第一业务是否被禁止接入。其中,第一业务是终端业务发起的任一业务,并不是特指。
另一种可能的实现中,在S503中AS层从第一网络设备接收第一接入控制信息,AS层提取第一接入控制信息中的第一指示信息,AS层向NAS层发送第一指示信息; NAS层根据第一指示信息判断第一业务是否被禁止接入,第一指示信息包含与接入控制相关的信息。
另一种可能的实现中,在S503中AS层从第一网络设备接收第一接入控制信息并保存,NAS层在连接态向AS层发送第一业务的业务请求信令,AS层根据第一接入控制信息和第一业务的业务请求信令判断第一业务是否被禁止接入。
其中,业务请求可以包括:PDN连接请求,或者,承载资源修改请求,或者,服务请求。当然,本申请对于业务请求的类型不进行具体限定。
示例性的,服务请求可以为浏览网页的服务请求,或者,拨打电话的服务请求,或者其他,本申请对此不进行赘述。
另一种可能的实现中,在S503中AS层从第一网络设备接收第一接入控制信息并保存,NAS层在连接态向AS层发送第一业务的业务请求的信令及接入控制策略指示信息,AS层参照接入控制策略指示信息所指示的接入控制策略,根据第一接入控制信息和第一业务请求的信令判断第一业务是否被禁止接入。其中,接入控制策略指示信息所指示的接入控制策略为配置在终端设备内部的接入控制策略,其与第一接入控制信息结合起来对终端设备发起的业务的接入进行控制。此处描述的接入控制策略指示信息所指示的接入控制策略与前面描述的接入控制策略相同,前面已经对接入控制策略进行了详细描述,此处不再进行赘述。
例如,NAS层在连接态向AS层发送MO业务请求的信令及ACB策略指示信息,则AS层针对MO业务请求检查ACB策略是否允许MO业务请求的发起。
在一种可能的实现中,AS层根据第一接入控制信息和第一业务的业务请求信令判断第一业务是否被禁止接入,具体可以包括:AS层解析第一业务的业务请求信令,获取第一业务的业务类型;AS层根据第一接入控制信息和第一业务的业务类型判断第一业务是否被禁止接入。
在另一种可能的实现中,NAS层在连接态向AS层发送第一业务的业务请求信令时,还向AS层发送了第一业务的业务类型。AS层根据第一接入控制信息和第一业务的业务请求信令判断第一业务是否被禁止接入,包括:AS层根据第一接入控制信息和第一业务的业务类型判断第一业务是否被禁止接入。
需要说明的是,由于第一接入控制信息指示了哪些业务被禁止接入或者哪些业务未被禁止接入,因此确定第一业务是否被禁止接入的过程就是比对的过程,此处不再进行一一赘述。
S504、在连接态时,若第一接入控制信息指示第一业务被禁止接入,终端设备停止向第一网络设备发送第一业务的业务请求。
进一步的,当终端设备包括AS层和NAS层时,S504的具体实现可以有多种,下面一一描述。
在一种可能的实现中,由NAS层根据第一接入控制信息确定第一业务在连接态被禁止接入,终端设备停止向第一网络设备发送第一业务的业务请求,具体可以实现为:NAS层停止向AS层发送第一业务的业务请求信令。
在另一种可能的实现中,NAS层在连接态向AS层发送第一业务的业务请求的信令,由AS层根据第一接入控制信息确定第一业务在连接态被禁止接入,终端设备停 止向第一网络设备发送第一业务的业务请求,具体可以实现为:AS层停止向第一网络设备发送第一业务的业务请求信令。
可选的,在另一种可能的实现中,当AS层判断第一业务被禁止接入时,本申请提供的发送业务请求的方法还可以包括:AS层向NAS层发送响应信息,该响应信息指示第一业务被禁止接入。
可选的,在另一种可能的实现方式中,本申请提供的发送业务请求的方法还可以包括:AS层向NAS层发送响应信息时,向NAS层发送第一业务被禁止接入的原因,原因可以包括是因为ACB或ACDC等策略的检查结果为禁止。
通过本申请提供的发送业务请求的方法,根据从第一网络设备接收的第一接入控制信息的指示第一业务被禁止接入,终端设备连接态时停止向第一网络设备发送第一业务的业务请求,控制了终端设备在连接态时的业务接入,进而控制了第一网络设备的负载,避免过载影响网络服务质量。
进一步的,如图6所示,在S503a之后,本申请提供的发送业务请求的方法还可以包括S505。
S505、在连接态时,若第一业务未被禁止接入,终端设备向第一网络设备发送第一业务的业务请求。
进一步的,当终端设备包括AS层和NAS层时,S505的具体实现可以有多种,下面一一描述。
在一种可能的实现中,由NAS层根据第一接入控制信息确定第一业务在连接态未被禁止接入,终端设备向第一网络设备发送第一业务的业务请求,具体可以实现为:NAS层向AS层发送第一业务的业务请求信令,AS层向第一网络设备发送第一业务的业务请求信令。
在另一种可能的实现中,NAS层在连接态向AS层发送第一业务的业务请求的信令,由AS层根据第一接入控制信息确定第一业务在连接态未被禁止接入,终端设备向第一网络设备发送第一业务的业务请求,具体可以实现为:AS层向第一网络设备发送第一业务的业务请求信令。
上述主要从终端设备、第一网络设备的工作过程的角度对本申请实施例提供的方案进行了介绍。可以理解的是,终端设备、第一网络设备为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
需要说明的是,终端设备、第一网络设备中执行本申请提供的发送业务请求的方法的功能部分称之为发送业务请求的装置,可以理解的是,发送业务请求的装置可以为终端设备或者第一网络设备的部分或全部,换言之,发送业务请求的装置可以与终端设备或者第一网络设备等价,或者,发送业务请求的装置也可以部署在终端设备或者第一网络设备内,以支持终端设备或者第一网络执行本申请提供的发送业务请求的 方法。
本申请实施例可以根据上述方法示例对终端设备、第一网络设备进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。当发送业务请求的装置为终端设备或者第一网络设备的部分或全部时,对终端设备或者第一网络设备进行功能模块的划分,就相当于对发送业务请求的装置进行功能模块的划分;或者,当发送业务请求的装置为终端设备或者第一网络设备的部分或全部时,对发送业务请求的装置进行功能模块的划分,就相当于对终端设备或者第一网络设备进行功能模块的划分。
在采用对应各个功能划分各个功能模块的情况下,图7示出了上述实施例中所涉及的终端设备中的发送业务请求的装置的一种可能的结构示意图。发送业务请求的装置70可以包括:接收单元701,发送单元702、处理单元703。接收单元701用于执行图5或图6中的过程S503;发送单元702用于向所述第一网络设备发送业务请求;处理单元703用于执行图5或图6中的过程S503a、S504、S505。其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在采用集成的单元的情况下,图8示出了上述实施例中所涉及的终端设备中的发送业务请求的装置的一种可能的结构示意图。发送业务请求的装置80可以包括:处理模块801、通信模块802。处理模块801用于对发送业务请求的装置80的动作进行控制管理。例如,处理模块801用于支持发送业务请求的装置80执行图5或图6中的过程S503、S503a、S504、S505。发送业务请求的装置80还可以包括存储模块803,用于存储发送业务请求的装置80的程序代码和数据。
其中,当发送业务请求的装置80部署在终端设备内时,处理模块801可以为图2所示的终端设备20的实体结构中的处理器201,可以是处理器或控制器。例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器801也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块802可以为图2所示的终端设备20的实体结构中的收发器203,通信模块802可以是通信端口,或者可以是收发器、收发电路或通信接口等。或者,上述通信接口可以通过上述具有收发功能的元件,实现与其他设备的通信。上述具有收发功能的元件可以由天线和/或射频装置实现。存储模块803可以是图1所示的终端设备20的实体结构中的存储器202。
当处理模块801为处理器,通信模块802为收发器,存储模块803为存储器时,本申请实施例图8所涉及的发送业务请求的装置80可以为图2所示的终端设备20的部分或全部。
如前述,本申请实施例提供的发送业务请求的装置70或发送业务请求的装置80可以用于实施上述本申请各实施例实现的方法中终端设备的功能,为了便于说明,仅 示出了与本申请实施例相关的部分,具体技术细节未揭示的,请参照本申请各实施例。
在采用对应各个功能划分各个功能模块的情况下,图9示出了上述实施例中所涉及的第一网络设备中的传输数据的装置的一种可能的结构示意图。发送业务请求的装置90可以包括:确定单元901,发送单元902。确定单元901用于执行图5或图6中的过程S501;发送单元902用于执行图5或图6中的过程S502、S501a。其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
进一步的,如图10所示,发送业务请求的装置90还可以包括接收单元903。其中,接收单元903用于执行图6中的过程S501e。
在采用集成的单元的情况下,图11示出了上述实施例中所涉及的第一网络设备中的发送业务请求的装置的一种可能的结构示意图。发送业务请求的装置110可以包括:处理模块1101、通信模块1102。处理模块1101用于对动作进行控制管理。通信模块1102用于与其他网络实体的通信。例如,处理模块1101用于执行图5或图6中的过程S501;处理模块1101用于通过通信模块1102执行图5或图6中的过程S502、S501a、S501e。发送业务请求的装置110还可以包括存储模块1103,用于存储程序代码和数据。
其中,当发送业务请求的装置110部署在第一网络设备内时,处理模块1101可以为图3所示的第一网络设备30的实体结构中的处理器301,可以是处理器或控制器。例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器1101也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块1102可以为图3所示的第一网络设备30的实体结构中的收发器303,通信模块1102可以是通信端口,或者可以是收发器、收发电路或通信接口等。或者,上述通信接口可以通过上述具有收发功能的元件,实现与其他设备的通信。上述具有收发功能的元件可以由天线和/或射频装置实现。存储模块1103可以是图3所示的第一网络设备30的实体结构中的存储器302。
当处理模块1101为处理器,通信模块1102为收发器,存储模块1103为存储器时,本申请实施例图11所涉及的发送业务请求的装置110可以为图3所示的第一网络设备30的部分或全部。
如前述,本申请实施例提供的发送业务请求的装置90或发送业务请求的装置110可以用于实施上述本申请各实施例实现的方法中第一网络设备的功能,为了便于说明,仅示出了与本申请实施例相关的部分,具体技术细节未揭示的,请参照本申请各实施例。
在采用对应各个功能划分各个功能模块的情况下,图12示出了上述实施例中所涉及的第二网络设备中的传输数据的装置的一种可能的结构示意图。发送业务请求的装置120可以包括:接收单元1201、确定单元1202、发送单元1203。接收单元1201用于执行图6中的过程S501b;确定单元1202用于执行图6中的过程S501c;发送单元1203用于执行图6中的过程S501d。其中,上述方法实施例涉及的各步骤的所有相关 内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在采用集成的单元的情况下,图13示出了上述实施例中所涉及的第二网络设备中的发送业务请求的装置的一种可能的结构示意图。发送业务请求的装置130可以包括:处理模块1301、通信模块1302。处理模块1301用于对动作进行控制管理。通信模块1302用于与其他网络实体的通信。例如,处理模块1301用于执行图6中的过程S501c;处理模块1301用于通过通信模块1302执行图6中的过程S501b、S501d。发送业务请求的装置130还可以包括存储模块1303,用于存储程序代码和数据。
其中,当发送业务请求的装置130部署在第二网络设备内时,处理模块1301可以为图4所示的第二网络设备40的实体结构中的处理器401,可以是处理器或控制器。例如可以是CPU,通用处理器,DSP,ASIC,FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器1301也可以是实现计算功能的组合,例如包含一个或多个微处理器组合,DSP和微处理器的组合等等。通信模块1302可以为图4所示的第二网络设备40的实体结构中的收发器403,通信模块1302可以是通信端口,或者可以是收发器、收发电路或通信接口等。或者,上述通信接口可以通过上述具有收发功能的元件,实现与其他设备的通信。上述具有收发功能的元件可以由天线和/或射频装置实现。存储模块1303可以是图4所示的第二网络设备40的实体结构中的存储器402。
当处理模块1301为处理器,通信模块1302为收发器,存储模块1303为存储器时,本申请实施例图13所涉及的发送业务请求的装置130可以为图4所示的第二网络设备40的部分或全部。
如前述,本申请实施例提供的发送业务请求的装置120或发送业务请求的装置130可以用于实施上述本申请各实施例实现的方法中第二网络设备的功能,为了便于说明,仅示出了与本申请实施例相关的部分,具体技术细节未揭示的,请参照本申请各实施例。
再一方面,本申请实施例提供一种通信系统,包括上述任一实施例描述的终端设备,以及上述任一实施例描述的第一网络设备。
再一方面,本申请实施例提供一种通信系统,包括上述任一实施例描述的终端设备、上述任一实施例描述的第一网络设备,以及上述任一实施例描述的第二网络设备。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现,也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成,软件模块可以被存放于RAM、闪存、ROM、可擦除可编程只读存储器(Erasable Programmable ROM,EPROM)、电可擦可编程只读存储器(Electrically EPROM,EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息。当然,存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外,该ASIC可以位于核心网接口设备中。当然,处理器和存储介质也可以作为分立组件存在于核心网接口设备中。或者,存储器可以与处理器耦合,例如存储器可以是独立存在,通过总线与处理器相 连接。存储器也可以和处理器集成在一起。存储器可以用于存储执行本申请实施例提供的技术方案的应用程序代码,并由处理器来控制执行。处理器用于执行存储器中存储的应用程序代码,从而实现本申请实施例提供的技术方案。
本申请实施例再提供一种芯片系统,该芯片系统包括处理器,用于实现本发明实施例的技术方法。在一种可能的设计中,该芯片系统还包括存储器,用于保存本发明实施例通信设备必要的程序指令和/或数据。在一种可能的设计中,该芯片系统还包括存储器,用于处理器调用存储器中存储的应用程序代码。该芯片系统,可以由一个或多个芯片构成,也可以包含芯片和其他分立器件,本申请实施例对此不作具体限定。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
本领域技术人员应该可以意识到,在上述一个或多个示例中,本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时,可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质,其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理包括,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元,可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是:以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其 依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (47)

  1. 一种发送业务请求的方法,其特征在于,包括:
    终端设备从第一网络设备接收第一接入控制信息;
    在连接态时,若所述第一接入控制信息指示第一业务被禁止接入,所述终端设备停止向所述第一网络设备发送所述第一业务的业务请求。
  2. 根据权利要求1所述的发送业务请求的方法,其特征在于,还包括:
    在连接态时,若所述第一业务未被禁止接入,所述终端设备向所述第一网络设备发送所述第一业务的业务请求。
  3. 根据权利要求1所述的发送业务请求的方法,其特征在于,所述业务请求包括:
    公用数据网PDN连接请求,或者,承载资源修改请求,或者,服务请求。
  4. 根据权利要求1-3任一项所述的发送业务请求的方法,其特征在于,所述终端设备从所述第一网络设备接收所述第一接入控制信息,包括:
    所述终端设备从所述第一网络设备接收系统消息,所述系统消息包括所述第一接入控制信息;
    或者,
    所述终端设备从所述第一网络设备接收专用信令,所述专用信令包括所述第一接入控制信息。
  5. 根据权利要求1-4任一项所述的发送业务请求的方法,其特征在于,所述第一接入控制信息包括下述信息中至少一项:
    使能指示信息、允许发起的业务类型、禁止发起的业务类型、允许发起业务的终端设备类型、禁止发起业务的终端设备类型、使能接入控制策略的指示信息;
    其中,所述使能指示信息用于指示终端设备是否需要根据所述第一接入控制信息确定所述第一业务是否被禁止接入。
  6. 根据权利要求5所述的发送业务请求的方法,其特征在于,所述接入控制策略包括以下至少一项:
    接入类型禁止ACB(Access Class Barring)策略;或者,
    特定服务的接入控制SSAC(Service Specific Access Control)策略;或者,
    ACB忽略(ACB skip)策略;或者,
    扩展接入限制EAB(Extended Access Barring)策略;或者,
    数据通信中的特定应用的拥塞控制ACDC(Application specific Congestion control for Data Communication)策略。
  7. 根据权利要求1-6任一项所述的发送业务请求的方法,其特征在于,所述终端设备包括接入AS层和非接入NAS层;
    所述终端设备从所述第一网络设备接收所述第一接入控制信息,包括:所述AS层从所述第一网络设备接收所述第一接入控制信息;
    所述方法还包括:所述AS层向所述NAS层发送所述第一接入控制信息;所述NAS层根据所述第一接入控制信息判断所述第一业务是否被禁止接入;
    所述终端设备停止向所述第一网络设备发送所述第一业务的业务请求,包括:所述NAS层停止向所述AS层发送所述第一业务的业务请求信令。
  8. 根据权利要求1-6任一项所述的发送业务请求的方法,其特征在于,所述终端设备包括接入AS层和非接入NAS层;
    所述终端设备从所述第一网络设备接收所述第一接入控制信息,包括:所述AS层从所述第一网络设备接收所述第一接入控制信息;
    所述方法还包括:所述AS层提取所述第一接入控制信息中的第一指示信息,所述AS层向所述NAS层发送所述第一指示信息;所述NAS层根据所述第一指示信息判断所述第一业务是否被禁止接入;
    所述终端设备停止向所述第一网络设备发送所述第一业务的业务请求,包括:所述NAS层停止向所述AS层发送所述第一业务的业务请求信令。
  9. 根据权利要求1-6任一项所述的发送业务请求的方法,其特征在于,所述终端设备包括接入AS层和非接入NAS层;
    所述终端设备从所述第一网络设备接收所述第一接入控制信息,包括:所述AS层从所述第一网络设备接收所述第一接入控制信息;
    所述方法还包括:所述NAS层在连接态向所述AS层发送所述第一业务的业务请求信令,所述AS层根据所述第一接入控制信息和所述第一业务的业务请求信令判断所述第一业务是否被禁止接入;
    所述终端设备停止向所述第一网络设备发送所述第一业务的业务请求,包括:所述AS层停止向所述第一网络设备发送所述第一业务的业务请求信令。
  10. 根据权利要求1-6任一项所述的发送业务请求的方法,其特征在于,所述终端设备包括接入AS层和非接入NAS层;
    所述终端设备从所述第一网络设备接收所述第一接入控制信息,包括:所述AS层从所述第一网络设备接收所述第一接入控制信息;
    所述方法还包括:所述NAS层在连接态向所述AS层发送所述第一业务的业务请求的信令及接入控制策略指示信息,所述AS层参照所述接入控制策略指示信息所指示的接入控制策略,根据所述第一接入控制信息和所述第一业务请求的信令判断所述第一业务是否被禁止接入。
  11. 根据权利要求9或10所述的发送业务请求的方法,其特征在于,所述AS层根据所述第一接入控制信息和所述第一业务的业务请求信令判断所述第一业务是否被禁止接入,包括:
    所述AS层解析所述第一业务的业务请求信令,获取所述第一业务的业务类型;所述AS层根据所述第一接入控制信息和所述第一业务的业务类型判断所述第一业务是否被禁止接入。
  12. 根据权利要求9或10所述的发送业务请求的方法,其特征在于,
    所述方法还包括:所述NAS层在连接态向所述AS层发送所述第一业务的业务请求信令时,还向所述AS层发送所述第一业务的业务类型;
    所述AS层根据所述第一接入控制信息和所述第一业务的业务请求信令判断所述第一业务是否被禁止接入,包括:
    所述AS层根据所述第一接入控制信息和所述第一业务的业务类型判断所述第一业务是否被禁止接入。
  13. 一种发送业务请求的方法,其特征在于,包括:
    确定第一接入控制信息,所述第一接入控制消息用于控制终端设备连接态的业务请求;
    发送所述第一接入控制信息。
  14. 根据权利要求13所述的发送业务请求的方法,其特征在于,所述业务请求包括:
    公用数据网PDN连接请求,或者,承载资源修改请求,或者,服务请求。
  15. 根据权利要求13或14所述的发送业务请求的方法,其特征在于,所述发送所述第一接入控制信息,包括:
    广播系统消息,所述系统消息包括所述第一接入控制信息;
    或者,
    发送专用信令,所述专用信令包括所述第一接入控制信息。
  16. 根据权利要求13-15任一项所述的发送业务请求的方法,其特征在于,所述第一接入控制信息包括下述信息中至少一项:
    使能指示信息、允许发起的业务类型、禁止发起的业务类型、允许发起业务的终端设备类型、禁止发起业务的终端设备类型、使能接入控制策略的指示信息;
    其中,所述使能指示信息用于指示终端设备是否需要根据所述第一接入控制信息确定所述第一业务是否被禁止接入。
  17. 根据权利要求16所述的发送业务请求的方法,其特征在于,所述接入控制策略包括以下至少一项:
    接入类型禁止ACB(Access Class Barring)策略;或者,
    特定服务的接入控制SSAC(Service Specific Access Control)策略;或者,
    ACB忽略(ACB skip)策略;或者,
    扩展接入限制EAB(Extended Access Barring)策略;或者,
    数据通信中的特定应用的拥塞控制ACDC(Application specific Congestion control for Data Communication)策略。
  18. 根据权利要求13-17任一项所述的发送业务请求的方法,其特征在于,
    所述方法还包括:从第二网络设备接收第二接入控制信息,所述第二接入控制信息用于控制终端设备连接态的业务请求;
    所述确定所述第一接入控制信息,包括:根据所述第二接入控制信息,确定所述第一接入控制信息。
  19. 根据权利要求18所述的发送业务请求的方法,其特征在于,所述方法还包括:
    向所述第二网络设备发送用于指示负载状况的负载指示信息。
  20. 一种发送业务请求的装置,其特征在于,包括:
    接收单元,从第一网络设备接收第一接入控制信息;
    发送单元,用于向所述第一网络设备发送业务请求;
    处理单元,用于在连接态时,若所述第一接入控制信息指示第一业务被禁止接入,控制所述发送单元停止向所述第一网络设备发送所述第一业务的业务请求。
  21. 根据权利要求20所述的发送业务请求的装置,其特征在于,所述处理单元还 用于:
    在连接态时,若所述第一业务未被禁止接入,控制所述发送单元向所述第一网络设备发送所述第一业务的业务请求。
  22. 根据权利要求20所述的发送业务请求的装置,其特征在于,所述业务请求包括:
    公用数据网PDN连接请求,或者,承载资源修改请求,或者,服务请求。
  23. 根据权利要求20-22任一项所述的发送业务请求的装置,其特征在于,所述接收单元具体用于:
    从所述第一网络设备接收系统消息,所述系统消息包括所述第一接入控制信息;
    或者,
    从所述第一网络设备接收专用信令,所述专用信令包括所述第一接入控制信息。
  24. 根据权利要求20-23任一项所述的发送业务请求的装置,其特征在于,所述第一接入控制信息包括下述信息中至少一项:
    使能指示信息、允许发起的业务类型、禁止发起的业务类型、允许发起业务的终端设备类型、禁止发起业务的终端设备类型、使能接入控制策略的指示信息;
    其中,所述使能指示信息用于指示终端设备是否需要根据所述第一接入控制信息确定所述第一业务是否被禁止接入。
  25. 根据权利要求24所述的发送业务请求的装置,其特征在于,所述接入控制策略包括以下至少一项:
    接入类型禁止ACB(Access Class Barring)策略;或者,
    特定服务的接入控制SSAC(Service Specific Access Control)策略;或者,
    ACB忽略(ACB skip)策略;或者,
    扩展接入限制EAB(Extended Access Barring)策略;或者,
    数据通信中的特定应用的拥塞控制ACDC(Application specific Congestion control for Data Communication)策略。
  26. 根据权利要求20-25任一项所述的发送业务请求的装置,其特征在于,所述装置包括接入AS层和非接入NAS层;
    所述AS层用于从所述第一网络设备接收所述第一接入控制信息;所述AS层向所述NAS层发送所述第一接入控制信息;所述NAS层根据所述第一接入控制信息判断所述第一业务是否被禁止接入;
    在连接态时,若所述第一接入控制信息指示第一业务被禁止接入,所述NAS层停止向所述AS层发送所述第一业务的业务请求信令。
  27. 根据权利要求20-25任一项所述的发送业务请求的装置,其特征在于,所述装置包括接入AS层和非接入NAS层;
    所述AS层从所述第一网络设备接收所述第一接入控制信息;所述AS层提取所述第一接入控制信息中的第一指示信息,所述AS层向所述NAS层发送所述第一指示信息;所述NAS层根据所述第一指示信息判断所述第一业务是否被禁止接入;
    在连接态时,若所述第一接入控制信息指示第一业务被禁止接入,所述NAS层停止向所述AS层发送所述第一业务的业务请求信令。
  28. 根据权利要求20-25任一项所述的发送业务请求的装置,其特征在于,所述装置包括接入AS层和非接入NAS层;
    所述AS层从所述第一网络设备接收所述第一接入控制信息;所述NAS层在连接态向所述AS层发送所述第一业务的业务请求信令,所述AS层根据所述第一接入控制信息和所述第一业务的业务请求信令判断所述第一业务是否被禁止接入;
    在连接态时,若所述第一接入控制信息指示第一业务被禁止接入,所述AS层停止向所述第一网络设备发送所述第一业务的业务请求信令。
  29. 根据权利要求20-25任一项所述的发送业务请求的装置,其特征在于,所述装置包括接入AS层和非接入NAS层;
    所述AS层从所述第一网络设备接收所述第一接入控制信息;所述NAS层在连接态向所述AS层发送所述第一业务的业务请求的信令及接入控制策略指示信息,所述AS层参照所述接入控制策略指示信息所指示的接入控制策略,根据所述第一接入控制信息和所述第一业务请求的信令判断所述第一业务是否被禁止接入。
  30. 根据权利要求28或29所述的发送业务请求的装置,其特征在于,所述AS层根据所述第一接入控制信息和所述第一业务的业务请求信令判断所述第一业务是否被禁止接入,包括:
    所述AS层解析所述第一业务的业务请求信令,获取所述第一业务的业务类型;所述AS层根据所述第一接入控制信息和所述第一业务的业务类型判断所述第一业务是否被禁止接入。
  31. 根据权利要求28或29所述的发送业务请求的装置,其特征在于,
    所述NAS层在连接态向所述AS层发送所述第一业务的业务请求信令时,还向所述AS层发送所述第一业务的业务类型;
    所述AS层根据所述第一接入控制信息和所述第一业务的业务请求信令判断所述第一业务是否被禁止接入,包括:
    所述AS层根据所述第一接入控制信息和所述第一业务的业务类型判断所述第一业务是否被禁止接入。
  32. 一种发送业务请求的装置,其特征在于,包括:
    确定单元,用于确定第一接入控制信息,所述第一接入控制消息用于控制终端设备连接态的业务请求;
    发送单元,用于发送所述确定单元确定的所述第一接入控制信息。
  33. 根据权利要求32所述的发送业务请求的装置,其特征在于,所述业务请求包括:
    公用数据网PDN连接请求,或者,承载资源修改请求,或者,服务请求。
  34. 根据权利要求32或33所述的发送业务请求的装置,其特征在于,所述发送单元具体用于:
    广播系统消息,所述系统消息包括所述第一接入控制信息;
    或者,
    发送专用信令,所述专用信令包括所述第一接入控制信息。
  35. 根据权利要求32-34任一项所述的发送业务请求的装置,其特征在于,所述 第一接入控制信息包括下述信息中至少一项:
    使能指示信息、允许发起的业务类型、禁止发起的业务类型、允许发起业务的终端设备类型、禁止发起业务的终端设备类型、使能接入控制策略的指示信息;
    其中,所述使能指示信息用于指示终端设备是否需要根据所述第一接入控制信息确定所述第一业务是否被禁止接入。
  36. 根据权利要求35所述的发送业务请求的装置,其特征在于,所述接入控制策略包括以下至少一项:
    接入类型禁止ACB(Access Class Barring)策略;或者,
    特定服务的接入控制SSAC(Service Specific Access Control)策略;或者,
    ACB忽略(ACB skip)策略;或者,
    扩展接入限制EAB(Extended Access Barring)策略;或者,
    数据通信中的特定应用的拥塞控制ACDC(Application specific Congestion control for Data Communication)策略。
  37. 根据权利要求32-36任一项所述的发送业务请求的装置,其特征在于,所述装置还包括:
    接收单元,用于从第二网络设备接收第二接入控制信息,所述第二接入控制信息用于控制终端设备连接态的业务请求;
    所述确定单元具体用于:根据所述第二接入控制信息,确定所述第一接入控制信息。
  38. 根据权利要求37所述的发送业务请求的装置,其特征在于,所述发送单元还用于:
    向所述第二网络设备发送用于指示负载状况的负载指示信息。
  39. 一种发送业务请求的装置,其特征在于,所述装置包括处理器、存储器以及存储在存储器上并可在处理器上运行的指令,当所述指令被运行时,使得所述装置执行如权利要求1至12项任一项所述的发送业务请求的方法。
  40. 一种发送业务请求的装置,其特征在于,所述装置包括处理器、存储器以及存储在存储器上并可在处理器上运行的指令,当所述指令被运行时,使得所述发送业务请求的装置执行如权利要求13至19项任一项所述的发送业务请求的方法。
  41. 一种终端设备,其特征在于,包括如权利要求39所述的发送业务请求的装置。
  42. 一种网络设备,其特征在于,包括如权利要求40所述的发送业务请求的装置。
  43. 一种终端设备,其特征在于,所述终端设备包括处理器、存储器和收发器;所述存储器用于存储计算机执行指令,当所述终端设备运行时,处理器调用所述存储器存储的计算机执行指令,执行权利要求1-12任一项所述的发送业务请求的方法。
  44. 一种网络设备,其特征在于,所述网络设备包括处理器、存储器和收发器;所述存储器用于存储计算机执行指令,当所述网络设备运行时,处理器调用所述存储器存储的计算机执行指令,执行权利要求13-19任一项所述的发送业务请求的方法。
  45. 一种通信系统,其特征在于,包括:
    权利要求41或43所述的终端设备,及权利要求42或44所述的网络设备。
  46. 一种计算机可读存储介质,包括指令,当其在计算机上运行时,使得计算机 执行如权利要求1至19任一项所述的发送业务请求的方法。
  47. 一种计算机程序产品,当其在计算机上运行时,使得计算机执行权利要求1至19任一项所述的发送业务请求的方法。
PCT/CN2018/090309 2018-06-07 2018-06-07 一种发送业务请求的方法、装置及系统 WO2019232757A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2018/090309 WO2019232757A1 (zh) 2018-06-07 2018-06-07 一种发送业务请求的方法、装置及系统
CN201880094073.8A CN112262595A (zh) 2018-06-07 2018-06-07 一种发送业务请求的方法、装置及系统
EP18921903.3A EP3806545A4 (en) 2018-06-07 2018-06-07 METHOD, DEVICE, AND SYSTEM FOR SENDING A SERVICE REQUEST
US17/111,523 US20210092669A1 (en) 2018-06-07 2020-12-04 Method and apparatus for sending request of service, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/090309 WO2019232757A1 (zh) 2018-06-07 2018-06-07 一种发送业务请求的方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/111,523 Continuation US20210092669A1 (en) 2018-06-07 2020-12-04 Method and apparatus for sending request of service, and system

Publications (1)

Publication Number Publication Date
WO2019232757A1 true WO2019232757A1 (zh) 2019-12-12

Family

ID=68769700

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/090309 WO2019232757A1 (zh) 2018-06-07 2018-06-07 一种发送业务请求的方法、装置及系统

Country Status (4)

Country Link
US (1) US20210092669A1 (zh)
EP (1) EP3806545A4 (zh)
CN (1) CN112262595A (zh)
WO (1) WO2019232757A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022082364A1 (zh) * 2020-10-19 2022-04-28 Oppo广东移动通信有限公司 接入网络的方法、终端设备和网络设备
GB2607430A (en) * 2021-05-21 2022-12-07 Lenovo Beijing Ltd Service request processing method and device and electronic device

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110971641B (zh) * 2018-09-30 2022-04-19 维沃移动通信有限公司 一种网络服务控制方法及通信设备
CN113498146B (zh) * 2020-04-02 2022-08-30 大唐移动通信设备有限公司 一种接入方法、终端、节点、装置及介质
WO2022165679A1 (zh) * 2021-02-03 2022-08-11 华为技术有限公司 控制终端设备接入网络的方法、通信装置及系统
CN113420312B (zh) * 2021-07-08 2022-04-26 山东浪潮超高清视频产业有限公司 一种动态控制api接口访问的方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102595555A (zh) * 2011-01-12 2012-07-18 中兴通讯股份有限公司 控制终端发起业务的方法及系统
CN104427574A (zh) * 2013-09-11 2015-03-18 华为技术有限公司 一种接入控制的方法及装置
CN104717693A (zh) * 2013-12-12 2015-06-17 电信科学技术研究院 一种业务接入控制、处理方法及设备
CN106658745A (zh) * 2015-10-30 2017-05-10 北京信威通信技术股份有限公司 一种控制用户接入或上行数据发送的方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102892177B (zh) * 2011-07-20 2018-01-02 中兴通讯股份有限公司 一种终端接入控制处理方法及装置
CN104662966B (zh) * 2012-10-26 2019-02-19 华为技术有限公司 业务接入的控制方法及设备
EP3183911B1 (en) * 2014-08-21 2020-03-25 Telefonaktiebolaget LM Ericsson (publ) Access control for connected network user devices
US20160353356A1 (en) * 2015-06-01 2016-12-01 Qualcomm Incorporated Application-specific congestion control for data communication (acdc) in connected mode
WO2017017890A1 (ja) * 2015-07-28 2017-02-02 日本電気株式会社 無線端末、基地局、及びこれらの方法
EP3343981B1 (en) * 2015-09-29 2020-02-26 Huawei Technologies Co., Ltd. User equipment and network device implementing application specific congestion control for data communication (acdc)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102595555A (zh) * 2011-01-12 2012-07-18 中兴通讯股份有限公司 控制终端发起业务的方法及系统
CN104427574A (zh) * 2013-09-11 2015-03-18 华为技术有限公司 一种接入控制的方法及装置
CN104717693A (zh) * 2013-12-12 2015-06-17 电信科学技术研究院 一种业务接入控制、处理方法及设备
CN106658745A (zh) * 2015-10-30 2017-05-10 北京信威通信技术股份有限公司 一种控制用户接入或上行数据发送的方法

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022082364A1 (zh) * 2020-10-19 2022-04-28 Oppo广东移动通信有限公司 接入网络的方法、终端设备和网络设备
GB2607430A (en) * 2021-05-21 2022-12-07 Lenovo Beijing Ltd Service request processing method and device and electronic device

Also Published As

Publication number Publication date
EP3806545A4 (en) 2021-06-16
US20210092669A1 (en) 2021-03-25
EP3806545A1 (en) 2021-04-14
CN112262595A (zh) 2021-01-22

Similar Documents

Publication Publication Date Title
WO2019232757A1 (zh) 一种发送业务请求的方法、装置及系统
CN111586597B (zh) 用于处理优先级服务拥塞的系统和方法
EP2905990B1 (en) Method and device for controlling multipriority in wireless communication system
EP3122145B1 (en) Execution method and user equipment for service request procedure
CN104186012B (zh) 具有服务连续性保证的用于选择性接入控制的方法和装置
AU2021200924B2 (en) Access category handling for wireless communication systems
WO2014176863A1 (zh) 接入控制方法及装置
WO2016122830A1 (en) Methods, apparatus and system for application specific congestion control for data communication (acdc)
TW201404195A (zh) 於壅塞無線通訊網路中處理等候時間的技術
BR112021005249A2 (pt) método de comunicação, aparelho, meio de armazenamento legível por computador e sistema
KR20140116409A (ko) 무선 통신 시스템에서 다중 우선순위 제어 방법 및 장치
CN113170527B (zh) 方法、装置和计算机程序
US20220248314A1 (en) Method and apparatus for enforcement of maximum number of protocol data unit sessions per network slice in a communication system
JP6370993B2 (ja) サード・パーティー・サーバが問題に直面した場合のアプリケーションからのトラフィックのコントロール
EP3731545B1 (en) Communication method and devices
EP3531619B1 (en) Method, device and system for function scheduling
CN109327882B (zh) 接入控制方法、通信设备和具有存储功能的设备
WO2019112878A1 (en) Prioritization of mobile terminating radio resource control connections
WO2019024102A1 (zh) 无线通信中的会话处理方法及终端设备
TWI751265B (zh) 接入方法和終端
WO2022206007A1 (zh) 中继通信方法及装置、存储介质、中继设备
TW201931896A (zh) 執行存取控制的裝置及方法
WO2013149401A1 (zh) 无线通信系统的负荷方法和无线通信系统
US20220141763A1 (en) Managing mode of access to a compatible set of network slices
WO2021259358A1 (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: 18921903

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018921903

Country of ref document: EP

Effective date: 20210105