WO2022000203A1 - 接入控制方法及装置、存储介质 - Google Patents

接入控制方法及装置、存储介质 Download PDF

Info

Publication number
WO2022000203A1
WO2022000203A1 PCT/CN2020/099027 CN2020099027W WO2022000203A1 WO 2022000203 A1 WO2022000203 A1 WO 2022000203A1 CN 2020099027 W CN2020099027 W CN 2020099027W WO 2022000203 A1 WO2022000203 A1 WO 2022000203A1
Authority
WO
WIPO (PCT)
Prior art keywords
application scenario
access
service application
access control
service
Prior art date
Application number
PCT/CN2020/099027
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/CN2020/099027 priority Critical patent/WO2022000203A1/zh
Priority to CN202080001391.2A priority patent/CN114208292B/zh
Publication of WO2022000203A1 publication Critical patent/WO2022000203A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery

Definitions

  • the embodiments of the present disclosure relate to the field of wireless communication, but are not limited to the field of wireless communication, and in particular, relate to an access control method and device, and a storage medium.
  • the working mechanism of AC (Access Control, Access Control) restriction is: according to the access level (Access Control) of the terminal Class) and the call initiated by the terminal to obtain the corresponding AC barring (AC barring) parameters, and perform AC barring check (AC barring check).
  • 3GPP 3rd Generation Partnership Project, 3rd Generation Partnership Project
  • existing services only consider the needs of wireless resources, which may not be enough to meet services such as AI (Artificial Intelligence, artificial intelligence) or ML (Machine Learning, machine learning). resource requirements.
  • AI Artificial Intelligence, artificial intelligence
  • ML Machine Learning, machine learning
  • the present disclosure provides an access control method and device, and a storage medium.
  • an access control method including:
  • a first access control parameter is delivered according to a first service application scenario, wherein the first access control parameter includes a first access type of the first service application scenario.
  • the method further includes:
  • the first access control parameter further includes: corresponding to the first access category the first access identifier.
  • the first service application scenario includes at least one of the following:
  • the first access control parameter further includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the method further includes:
  • a prohibit timer is configured for the first service application scenario according to the service type of the first service application scenario.
  • configuring a disable timer for the first service application scenario according to the service type of the first service application scenario includes:
  • the timing of whether to stop the prohibit timer is configured when a de-triggering event is detected.
  • different service types have different resource consumption attributes
  • the resource consumption attribute includes at least one of the following:
  • the deactivation trigger event includes at least one of the following:
  • configuring whether to stop the timing of the prohibit timer when a de-triggering event is detected includes:
  • configuring whether to stop the timing of the prohibit timer when a de-triggering event is detected includes:
  • the timing of whether to stop the prohibit timer is configured through dedicated signaling or public signaling or a communication protocol when a de-triggering event is detected.
  • an access control method including:
  • the first access control parameter further includes: the first access identifier corresponding to the first access category in the first service application scenario.
  • the first access control parameter further includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the method further includes:
  • the disable timer is started in response to the parameter of the disable timer.
  • the method further includes:
  • timing to stop or continue the inhibit timer is determined when a mitigation trigger time is detected.
  • the deactivation trigger event includes at least one of the following:
  • the determining, according to the parameter, the timing to stop or continue the inhibit timer when a mitigation trigger time is detected comprising:
  • the timing of the prohibit timer is continued according to the parameter.
  • the method further includes:
  • the AS In response to the first access control parameter, the AS (Access Stratum, access stratum) transmits a notification message for prohibiting access to the first service application scenario to the NAS (Non Access Stratum, non-access stratum);
  • the NAS stops the call of the first service application scenario according to the notification message.
  • the method further includes:
  • the AS transmits, to the NAS, the prohibition duration information for prohibiting access to the first service application scenario; wherein, the prohibition duration is used to re-initiate the NAS after the prohibition duration A call in a business application scenario.
  • an access control apparatus including:
  • the delivery module is configured to deliver a first access control parameter according to a first service application scenario, wherein the first access control parameter includes a first access type of the first service application scenario.
  • the apparatus further includes:
  • a first determining module configured to determine, in response to the existence of the first service application scenario, a first access identifier of the first service application scenario; wherein the first access control parameter further includes: and the first access control parameter the first access identifier corresponding to the first access category.
  • the first service application scenario includes at least one of the following:
  • the first access control parameter further includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the apparatus further includes:
  • a configuration module configured to configure a prohibit timer for the first service application scenario according to the service type of the first service application scenario.
  • the configuration module is configured to:
  • the timing of whether to stop the prohibit timer is configured when a de-triggering event is detected.
  • different service types have different resource consumption attributes
  • the resource consumption attribute includes at least one of the following:
  • the deactivation trigger event includes at least one of the following:
  • the configuration module includes:
  • the first configuration sub-module is configured to, in response to the service type of the first service application scenario being an AI-related service type, configure to continue the prohibit timer when an RRC connection establishment message corresponding to the release trigger event is received Timing;
  • the second configuration sub-module is configured to, in response to the service type of the first service application scenario being an AI-related service type, configure to continue the prohibit timer when an RRC connection recovery message corresponding to the release trigger event is received Timing.
  • the configuration module is configured to:
  • the timing of whether to stop the prohibit timer is configured through dedicated signaling or public signaling or a communication protocol when a de-triggering event is detected.
  • an access control apparatus including:
  • a receiving module configured to receive a first access control parameter, wherein the first access control parameter is used for access control in a first service application scenario, wherein the first access control parameter includes The first access category of the first service application scenario.
  • the first access control parameter further includes: the first access identifier corresponding to the first access category in the first service application scenario.
  • the first access control parameter further includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the apparatus further includes:
  • a start module configured to start the prohibit timer in response to the parameter of the prohibit timer.
  • the apparatus further includes:
  • the second determining module is configured to determine to stop or continue the timing of the disable timer when a de-triggering event is detected.
  • the deactivation trigger event includes at least one of the following:
  • the second determining module includes:
  • the first timing sub-module is configured to, in response to the service type of the first service application scenario being the service type associated with AI, when receiving the RRC connection establishment message corresponding to the release trigger event, continue according to the configuration information the timing of the prohibition timer;
  • the second timing sub-module is configured to, in response to that the service type of the first service application scenario is the AI-related service type, when receiving the RRC connection recovery message corresponding to the release trigger event, continue according to the configuration information Timing of the disable timer.
  • the apparatus further includes:
  • a transmission module configured to, in response to the first access control parameter, transmit, at the access stratum AS, a notification message for prohibiting access to the first service application scenario to the non-access stratum NAS;
  • a stopping module configured to stop the call of the first service application scenario at the NAS according to the notification message.
  • the apparatus further includes:
  • an initiating module configured to transmit the prohibition duration information of prohibiting access to the first service application scenario to the NAS when the AS; wherein, the prohibition duration is used for, after the prohibition duration, in the NAS Re-initiate the call of the first service application scenario.
  • a communication device including at least: a processor and a memory for storing executable instructions that can be executed on the processor, wherein:
  • the executable instructions execute the steps in any one of the above access control methods.
  • a non-transitory computer-readable storage medium where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, any of the above-mentioned Steps in an access control method.
  • the embodiments of the present disclosure may include the following beneficial effects: the embodiments of the present disclosure provide an implementation manner of access control, and according to the first service application scenario, the corresponding first access control parameters are issued in a targeted manner, Thus, it is convenient to realize the access control of the first service application scenario. In this way, compared with the related art, which uses a unified access control method for all service application scenarios, the technical solutions of the embodiments of the present disclosure can be distinguished from the access control of other service application scenarios according to the specific requirements of the first service application scenario. The method is convenient to meet the resource requirements such as bandwidth or processing capability of the first service application scenario.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment
  • FIG. 2 is a schematic flowchart 1 of an access control method according to an exemplary embodiment
  • FIG. 3 is a second schematic flowchart of an access control method according to an exemplary embodiment
  • Fig. 4 is a schematic flow chart 3 of an access control method according to an exemplary embodiment
  • FIG. 5 is a fourth schematic flowchart of an access control method according to an exemplary embodiment
  • FIG. 6 is a schematic flowchart 5 of an access control method according to an exemplary embodiment
  • FIG. 7 is a schematic structural diagram 1 of an access control apparatus according to an exemplary embodiment
  • FIG. 8 is a second schematic structural diagram of an access control apparatus according to an exemplary embodiment
  • FIG. 9 is a schematic structural diagram 1 of a communication device according to an exemplary embodiment.
  • FIG. 10 is a second schematic structural diagram of a communication device according to an exemplary embodiment.
  • first, second, third, etc. may be used in embodiments of the present disclosure to describe various pieces of information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • the words "if” and “if” as used herein can be interpreted as “at the time of” or “when” or “in response to determining”, depending on the context.
  • an embodiment of the present disclosure takes an application scenario of access control as an example for illustrative description.
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: several terminals 110 and several base stations 120 .
  • the terminal 110 may be a device that provides voice and/or data connectivity to a user.
  • the terminal 110 may communicate with one or more core networks via a Radio Access Network (RAN), and the terminal 110 may be an IoT terminal such as a sensor device, a mobile phone (or "cellular" phone) and a
  • the computer of the IoT terminal for example, may be a fixed, portable, pocket, hand-held, built-in computer or a vehicle-mounted device.
  • a station For example, a station (Station, STA), a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile station), a mobile station (mobile), a remote station (remote station), an access point, a remote terminal ( remote terminal), access terminal, user terminal, user agent, user device, or user equipment (terminal).
  • the terminal 110 may also be a device of an unmanned aerial vehicle.
  • the terminal 110 may also be a vehicle-mounted device, for example, a trip computer with a wireless communication function, or a wireless terminal connected to an external trip computer.
  • the terminal 110 may also be a roadside device, for example, a streetlight, a signal light, or other roadside device with a wireless communication function.
  • the base station 120 may be a network-side device in a wireless communication system.
  • the wireless communication system may be the 4th generation mobile communication (4G) system, also known as the Long Term Evolution (Long Term Evolution, LTE) system; or, the wireless communication system may also be a 5G system, Also known as new radio (NR) system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system may be called NG-RAN (New Generation-Radio Access Network, a new generation of radio access network).
  • the base station 120 may be an evolved base station (eNB) used in the 4G system, or a base station (gNB) using a centralized distributed architecture in the 5G system, or any type of base station of the next generation mobile communication network technology.
  • eNB evolved base station
  • gNB base station
  • the base station 120 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is provided with a protocol stack of a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control Protocol (Radio Link Control, RLC) layer, and a Media Access Control (Media Access Control, MAC) layer; distribution A physical (Physical, PHY) layer protocol stack is set in the unit, and the specific implementation manner of the base station 120 is not limited in this embodiment of the present disclosure.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control Protocol
  • MAC Media Access Control
  • distribution A physical (Physical, PHY) layer protocol stack is set in the unit, and the specific implementation manner of the base station 120 is not limited in this embodiment of the present disclosure.
  • a wireless connection can be established between the base station 120 and the terminal 110 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on a 5G next-generation mobile communication network technology standard.
  • an E2E (End to End, end-to-end) connection may also be established between the terminals 110 .
  • V2V vehicle to vehicle, vehicle-to-vehicle
  • V2I vehicle to Infrastructure, vehicle-to-roadside equipment
  • V2P vehicle to pedestrian, vehicle-to-person communication in vehicle-to-everything (V2X) communication etc. scene.
  • the above wireless communication system may further include a network management device 130 .
  • the network management device 130 may be a core network device in a wireless communication system.
  • the network management device 130 may be a mobility management entity (Mobility Management Entity) in an evolved packet core network (Evolved Packet Core, EPC). MME).
  • the network management device may also be other core network devices, such as a serving gateway (Serving GateWay, SGW), a public data network gateway (Public Data Network GateWay, PGW), a policy and charging rule functional unit (Policy and Charging Rules) Function, PCRF) or home subscriber server (Home Subscriber Server, HSS), etc.
  • the implementation form of the network management device 130 is not limited in this embodiment of the present disclosure.
  • the structure of the access control parameters (AC Barring parameters) of access control is for each PLMN (Public Land Mobile Network, public land mobile network), each access category and each access identified.
  • Table 1 below gives examples of access control parameters, wherein the maximum number of PLMNs is 6, the maximum number of access categories is 64, and the maximum number of access identities is 16.
  • Access categories are access categories. According to the provisions of 3GPP TS24 301, access categories include the following: “originating signaling (source signaling)”, “emergency calls (emergency calls)”, “originating MMTEL” (MultiMediaTelephony, multimedia telephony) voice (source multimedia voice call)”, “originating MMTEL video (source multimedia video call)”, “originating SMSoIP (Short Message Service over Internet Protocol, Internet Protocol-based SMS transmission)”, “ “originating SMS”, “terminating calls”, “originating calls” and “mobile originating CS fallback”.
  • originating signaling source signaling
  • emergency calls emergency calls
  • originating MMTEL MultiMediaTelephony, multimedia telephony voice
  • originating MMTEL video source multimedia video call
  • originating SMSoIP Short Message Service over Internet Protocol, Internet Protocol-based SMS transmission
  • Access identities refers to access identities. It can be understood as the attribute or level of UE (User Equipment, user equipment). For example, 0 to 9 are low-priority users, such as individual users, and 11 to 15 are high-priority users, such as those related to public safety and emergency services or PLMN management. user.
  • UE User Equipment
  • the definition of the access control parameters in the table may include the following ways: for low-priority users, it may be defined according to the random number and the barring effective duration; for high-priority users, it may be in the form of a bitmap.
  • the low-priority users include commercial users and high-priority users.
  • the basic access control detection (AC barring check) process is to obtain AC barring parameters according to the access type and access identifier, and perform access control detection.
  • the access control parameters usually use random numbers for low-priority users (0-9), and use bitmap form for high-priority users (11-15). Usually, this parameter will be defined in the system message. For the random number mode, if it is restricted, a timer needs to be started, and its time will be calculated from the AC barring time (AC-BarringTime). For example, the limit duration is 512 seconds.
  • AI and/or ML-based mobile applications have the development trend of intensive computing, large memory consumption and high power consumption.
  • end devices often have strict energy consumption, computing and memory cost constraints. Therefore, AI/ML needs to be decoupled on the device and the network. That is, offloading the compute-intensive, energy-intensive parts to the network endpoints, while leaving the privacy-sensitive and latency-sensitive parts on the end devices.
  • Devices execute operations or models to specific components or layers and send intermediate data to network endpoints. The network endpoint performs the rest and feeds the inference results back to the device.
  • the key to splitting AI and ML operations is to choose the best splitting mode and splitting point to keep the required resources below the upper limit of the resources available on mobile devices, and to optimize compute, storage or memory, power consumption, device and network side communication resources.
  • the resource requirements for uplink and downlink are very different.
  • the training mode requires a large amount of uplink bandwidth because it involves the upload of training data, while for the downlink, only the result of inference after training is returned, and the downlink bandwidth is relatively small.
  • the AC process is too rough, because its access categories are all "originating calls". It is initiated by the terminal, so the access identification is also the same. That is to say, the granularity of distinguishing access types and access identifiers is not fine enough, but in fact, different access types consume completely different resources, and the load on the network is also completely different. deal with.
  • the resources required for mobile applications of AI and ML include not only wireless resources, but also resources such as computing power.
  • the existing services of 3GPP only consider the requirements of wireless resources, so special processing needs to be carried out in the aspect of access control for the movement of AI and ML.
  • an embodiment of the present disclosure provides an access control method, including:
  • Step S101 delivering a first access control parameter according to a first service application scenario, wherein the first access control parameter includes a first access type of the first service application scenario.
  • the access control method can be applied to network devices such as base stations and core network devices.
  • the base station can configure different access control parameters for different service application scenarios, so that when the UE requests to access the corresponding service, it is convenient to determine whether to prohibit or allow the service according to the corresponding access control parameters. access.
  • the first access control parameter may be an identifier used to indicate the first access category of the first service application scenario, or may be the first access type used to imply the first service application scenario category. implying that the first access category of the first service application scenario means that the first access control parameter may be a length parameter of a signaling, so that the UE determines the first access control parameter according to the length of the signaling; and It may be a coding sequence, so that the UE determines the first access control parameter according to the sequence.
  • the first access control parameter may be one or more explicit bits to indicate the first access category of the first service application scenario, or may be determined according to a communication protocol or indicated by the base station for identifying Certain information of the first access category of the first service application scenario.
  • the first service application scenario can be distinguished by the above-mentioned first access category, and can be identified by a new access category different from the access category in the related art.
  • the first service application scenario may be a service application scenario with resource requirements of larger wireless resources or network computing processing capabilities.
  • the above-mentioned AI and ML related business scenarios By delivering the first access control parameter corresponding to the first service application scenario to the UE, independent control of the access request of the first service application scenario can be implemented, thereby facilitating the UE to access the first service when network resources permit. Businesses related to application scenarios.
  • the access category is the category of the communication connection established between the UE and the base station, indicating different reasons for the UE to establish the RRC connection. According to different access types, the base station can perform corresponding access control, provide different access rights, and prohibit access timing rules, etc. For example, if the reason why the UE establishes the RRC connection is an emergency call, the access category is "emergency calls", that is, the emergency call category. For another example, for the RRC connection request initiated by the UE as the calling end, that is, the call request initiated by the UE, the access type may be "originating calls", that is, the originating call.
  • Typical emergency calls include, but are not limited to, a SOS call, an alarm call, a fire call, or a medical call.
  • a corresponding access type different from other service application scenarios may be determined.
  • the AI service category may be determined as the access category corresponding to the first service application scenario.
  • the AI service category may be different from the above-mentioned "source signaling", “emergency call”, “source multimedia voice call”, “source multimedia video call”, “Internet Protocol-based short message” defined in the related art.
  • the special access categories such as “transmission”, “source short message”, “terminal call”, “source call” and “mobile source circuit domain fallback" are the specific access categories used to define the first service application scenario .
  • the first service application scenario related to AI and/or ML is distinguished from the access category of "source-end call" corresponding to other calls originated by the UE in the related art, so as to facilitate integration with other services
  • the calls of the application are subject to access control respectively.
  • service types other than the first service application scenario defined in the embodiments of the present disclosure such as other service application scenarios initiated by the UE, may include second service application scenarios and the like.
  • the second access control parameter corresponding to the second service application scenario may be the same as or different from the first access control parameter.
  • Different access control parameters are allocated for different service scenarios, thereby reducing the poor access control effect caused by the use of unified access control parameters, and different access control parameters are issued separately, making the access control of the two service scenarios more flexible .
  • the first access control parameter used for access control is determined according to the corresponding first service category, so as to perform targeted access. control.
  • the method further includes:
  • Step S102 In response to the existence of the first service application scenario, determine a first access identifier of the first service application scenario; wherein the first access control parameter further includes: The first access identifier corresponding to the category.
  • the access identifier is an identifier indicating the user level or user type corresponding to the UE, and can be set corresponding to the SIM card.
  • the access identifier of the individual user may be any one of 0 to 9.
  • the above-mentioned first access identifier can be set independently of the access identifier corresponding to the SIM card in the UE.
  • the access identifier corresponding to the user equipment is the access identifier of the low-priority user set corresponding to the SIM card, for example, 0-9.
  • the first access identifier corresponding to the first service application scenario may be different from the access identifier of the low-priority user and different from the access identifier of the high-priority user.
  • the access identifiers of low-priority users are 0-9
  • the access identifiers of high-priority users are 11-15
  • the access identifiers corresponding to the first service application scenario may be 16 and so on.
  • the first access identifier corresponding to the first service application scenario may also be defined as the above-mentioned first access identifier.
  • Reserved access ID For example, in an actual application, the access identifiers of low-priority users include 0-8, and 9 is a reserved access identifier, and the first access identifier of the above-mentioned first service application scenario is defined as reserved access identifier 9.
  • the access identifiers can be distinguished in more detail at the level of service application scenarios, thereby facilitating corresponding configuration of access control parameters.
  • the first service application scenario includes at least one of the following:
  • Service application scenarios that use AI services as the reason for call establishment refer to related services that use cloud and/or local data and models; service application scenarios that use the AI model to train locally in the UE
  • the business application scenarios in which the cloud training service is the cause of call establishment and the business application scenarios in which the AI model is jointly trained locally and in the cloud as the cause of call establishment refer to the establishment of the model and the related services of the training process.
  • the AI service may include: the UE requests the cloud for target recognition or target tracking based on the acquired images, such as monitoring images, etc., which requires the use of the database and/or AI model established in the cloud, so that the acquired images can be used as Enter data and use cloud databases and/or AI models for quick identification.
  • the AI model training service may include: the UE transmits the collected data to the cloud, so that the cloud can use the data as training data for training to determine and/or improve the AI model. For example, these data can be used as a training model to adjust the neural network parameters of the AI model, so as to obtain an AI model for use by the AI business.
  • AI business application scenarios require a large amount of data processing locally and/or in the cloud, for example: local applications use cloud models for data processing, downloaded data use local models for data processing, etc.; Training, such as local and/or cloud model training, also requires a large amount of data upload and download, and data processing. Therefore, AI-related services have high demands on network wireless resources, computing processing capabilities, and storage capabilities.
  • the service application scenario that takes the above-mentioned AI-related services (including AI service application and AI model training) as the reason for call establishment is defined as the above-mentioned first service application scenario, so as to facilitate the targeted application of AI service-related applications. Provides flexible access control to facilitate the access of AI services when the network status is appropriate.
  • AI-related services include but are not limited to any of the following situations: model training, ML, model adjustment, and model application.
  • the local training service and cloud training service of the AI model can be further subdivided to correspond to different access control parameters.
  • the AI model requires a large amount of downlink bandwidth for local training services of the UE, and the data processing operation requires high local capabilities. Therefore, it can be configured that the downlink is congested or the UE processing capability is lower than the threshold to prohibit access. access control parameters.
  • the business scenario in which the AI model is trained in the cloud requires a large amount of uplink bandwidth and requires the cloud to have high computing and processing capabilities. Therefore, it can be configured that the cloud network is busy or the uplink is congested or the cloud processing capability is lower than The access control parameter that prohibits access at the threshold.
  • the first access control parameter includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the first access category of the first service application scenario and the parameters of the barring timer may be sent to the UE through the same signaling or different signaling.
  • a prohibition timer may be configured for the service of the first service application scenario.
  • the parameters for prohibiting the timer include, but are not limited to, any one of the following: the duration of prohibiting the access of the call of the first service application scenario, and the condition for prohibiting the timer from interrupting the timing.
  • the parameter of the disable timer may be: whether to interrupt the operation of the disable timer based on an emergency call event or an incoming call event.
  • the access initiated by the service in the first service application scenario is the access request initiated by the UE.
  • the timing process of the prohibition timer it will not re-initiate the access request as the originator.
  • the UE end is the called end, it can determine whether to stop the timing of the prohibit timer according to the pre-configuration.
  • the base station sends the parameter of the barring timer to the UE through the aforementioned first access control parameter, so that the UE can determine the duration of the barring timer according to the parameter and delay initiating an access request.
  • the UE may initiate an access request to the base station according to the interval time determined by the parameter until the access is successful. In this way, the UE will not initiate an access request when the timer is prohibited, thereby reducing unnecessary repeated access requests and increasing the probability of successful access when re-initiating an access request.
  • the timing of the above barring timer can be started. In this way, the UE will not initiate an access request again during the timing process of the prohibit timer. Or, the UE starts the barring timer at any appropriate time; and the UE does not initiate an access request when the barring timer does not expire.
  • the method further includes:
  • Step S103 Configure a prohibit timer for the first service application scenario according to the service type of the first service application scenario.
  • this step 103 may be implemented in combination with the aforementioned steps 101 and 102, or may be implemented independently, which is not limited in this embodiment of the present disclosure; meanwhile, if step 103 is combined with the aforementioned step 101 When implemented in combination with 102 and 102, the execution order of the three steps is not limited to the execution order of steps 101 to 103, but may be any possible execution order.
  • the base station when receiving the access request of the first service application scenario initiated by the UE, can configure the corresponding prohibit timer according to the service type of the first service application scenario, and set the configured parameters to sent to UE. It is also possible to directly deliver the prohibit timer configuration parameter for the first service application scenario to the UE without receiving the access request initiated by the UE.
  • the base station configures a specific prohibition timer for a service type different from other service application scenarios, so that the UE can run the prohibition timer according to the requirements of the first service application scenario.
  • the other service application scenarios may be the second service application scenarios.
  • configuring a disable timer for the first service application scenario according to the service type of the first service application scenario includes:
  • the timing of whether to stop the prohibit timer is configured when a de-triggering event is detected.
  • the above-mentioned parameters of the disable timer may include a release trigger event and/or a duration of the disable timer to release the trigger event.
  • the release trigger event refers to the event that triggers the UE to release the access prohibition. According to whether the release trigger event is used to stop the prohibition timer timing, the UE can determine whether the access request can be initiated when the release trigger event occurs. For example, if the above-mentioned de-triggering event is detected in the process of inhibiting the timer timing, the timing of the inhibiting timer can be stopped, so that the UE can initiate an access request; that is, the de-triggering event can ignore whether the inhibiting timer is still running , directly initiate an access request.
  • Dismissal trigger events may include emergency call events, incoming call events, and the like.
  • the first service application scenario may have higher requirements for network resources, computing resources and storage resources, when the prohibit timer is suspended due to the de-triggering event, so that the UE re-initiates the access request, it may be due to network resources. If it is insufficient, it will be banned again, or it cannot meet the requirements of the first service application scenario after access.
  • the timing can be stopped when the de-triggering event is detected, and the UE can initiate an access request again, that is, for In the second service application scenario, the release trigger event may be configured to stop the timing of the prohibit timer corresponding to the access request of the second service application scenario.
  • the timing of the prohibition timer will not be stopped due to an emergency call or an incoming call event, etc., so that in the process of prohibiting the timer timing, the timing will not be interrupted. Initiate an access request when it is unnecessary or does not meet the application requirements.
  • the deactivation trigger event includes at least one of the following:
  • the called event is a communication connection request received by the UE. Since it is passively received, it can be used as a release trigger event, so that a communication connection can be successfully established with the UE when the opposite end initiates a connection request.
  • the emergency call event is to facilitate the UE itself to initiate a call in time, thereby improving the timeliness of the emergency call event.
  • the called event is a connection request generated when the UE is called by other UEs or network devices
  • the emergency call event refers to an access request for an emergency call or an alarm call based on a specific number
  • an emergency call event is received.
  • the incoming request is not limited to the provider type and the UE's own call charge or allowance limit.
  • the called event or the emergency call event may cause the timing stop of the prohibit timers corresponding to various service requests, so that the UE can re-initiate the call requests of various services.
  • the emergency call event can be used as a release trigger event.
  • the prohibition timer corresponding to the call request can be released, so that the UE can re-initiate the call request.
  • the first service application scenario in the embodiment of the present disclosure because it is a service type that may have relatively high demands on network communication resources, computing resources, and storage resources, and it is not necessary to quickly detect an emergency call event or a called event The business of establishing connections. Therefore, in order to improve the probability of successful access after the first service application scenario sends an access request, and reduce the probability that the UE is still banned after sending an access request, here, for the first service application scenario, even if a de-triggering event is detected , you can also continue to disable the timing of the timer according to the configuration.
  • different service types have different resource consumption attributes
  • the resource consumption attribute includes at least one of the following:
  • the resource consumption attribute is the demand and consumption of network resources of different service types after accessing the network.
  • the attributes of computing resource consumption include business requirements for cloud data processing capabilities, processing rates, and the amount of data to be calculated; the attributes of storage resource consumption include the requirements for the storage capacity of cloud data that the business needs to use; the attributes of network resource consumption include Business requirements for network bandwidth, transmission rate, and network stability.
  • the same access control parameters may not be able to meet different requirements, so that some services with large resource consumption cannot be used normally after access.
  • network resource consumption such as downlink bandwidth
  • cloud training service of AI models a large amount of data needs to be uploaded, and the cloud needs to have higher computing power processing capability to realize model training, so there is a high demand for network resource consumption such as uplink bandwidth, and a high demand for computing resource consumption on the network side
  • data can be stored through the cloud-stored models Therefore, there is a high demand for computing resource consumption attributes and storage resource consumption attributes on the network side.
  • the service type of the above-mentioned first service application scenario and the service types of other service application scenarios can be distinguished according to the difference of the above-mentioned resource consumption attribute.
  • configuring whether to stop the timing of the prohibit timer when a de-triggering event is detected includes:
  • the first service application scenario when the above-mentioned first service application scenario is an AI-related service type, it can be considered that the first service application scenario has a high demand for network capabilities.
  • the trigger event stops timing. In this way, repeated access failures in the first service application scenario can be reduced, and the situation that the service cannot be used normally due to the mismatch of network resources after the access is disabled due to the timer interruption timing can also be reduced. As far as possible, make the UE re-access when the network resources meet the demand.
  • the base station may configure the first service application scenario to continue the timing of the timer when receiving the RRC connection establishment message and the RRC connection recovery message corresponding to the de-triggering event, so that the UE does not re-initiate the access request.
  • configuring whether to stop the timing of the prohibit timer when a de-triggering event is detected includes:
  • the timing of continuing the prohibit timer is configured through dedicated signaling or public signaling or a communication protocol when a de-triggering event is detected.
  • a common signaling can be used to send it to the UE, or a special signaling dedicated to configuring the prohibit timer can be added. sent to UE.
  • the base station may load the relevant information of the configuration prohibit timer, including the above-mentioned configuration information on whether to stop the timing of the prohibit timer when the de-triggering event is detected, as the communication signaling in the channel of the public signaling to carry out the process. transmission.
  • the configuration information used to configure whether the release trigger event is used to stop the timing of the prohibition timer can also be transmitted as a dedicated signaling different from the public signaling, and is dedicated to configuring the prohibition corresponding to the above-mentioned first service application scenario. timer.
  • an access control method including:
  • Step S201 Receive a first access control parameter, where the first access control parameter is used for access control in a first service application scenario, wherein the first access control parameter includes the The first access category of the first service application scenario.
  • the first access control parameter may be an identifier used to indicate the first access category of the first service application scenario, or may be the first access type used to imply the first service application scenario category. implying that the first access category of the first service application scenario means that the first access control parameter may be a length parameter of a signaling, so that the UE determines the first access control parameter according to the length of the signaling; and It can be a coding sequence, so that the UE determines the first access control parameter according to the coding sequence.
  • the first access control parameter may be one or more explicit bits to indicate the first access category of the first service application scenario, or may be determined according to a communication protocol or indicated by the base station for identifying Certain information of the first access category of the first service application scenario.
  • the access control method can be applied to terminals, UEs, and the like.
  • the base station configures the first access control parameter for the first service application scenario and sends it to the UE
  • the UE receives the first access control parameter, so as to determine whether to initiate an access request for the first service application scenario, or can determine whether to initiate an access request for the first service application scenario according to the first access control parameter.
  • the access control parameter determines the access timing for initiating the first service application scenario, and so on.
  • the first access control parameter corresponds to the access control parameter of the first service application scenario
  • the first access control parameter does not affect the access control of other services of the UE. Therefore, when to initiate the access request can be determined according to the characteristics of the access category corresponding to the first service application scenario and whether the network meets the requirements of the first service application scenario.
  • the first access control parameter further includes: the first access identifier corresponding to the first access category in the first service application scenario.
  • the first access control parameter may further include a first access identifier corresponding to the first service application scenario.
  • the UE may determine information such as whether to initiate an access request or whether access is prohibited after initiating the access request according to the first access category and the first access control parameter corresponding to the first access identifier.
  • the first access control parameter includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the first access control parameter may include the first access category and/or the parameter of the barring timer of the first service application scenario.
  • the first access category of the first service application scenario and the parameters of the barring timer may be sent to the UE through the same signaling or different signaling.
  • the parameter of the prohibition timer may include the delay time for re-initiating the access request after the first service application scenario is prohibited from accessing, and may also include whether to stop the timer and allow re-initiation when an emergency call or an incoming call event is detected. Initiate access request and other provisions.
  • the UE can further determine the timing of initiating the access request according to the parameter of the prohibition timer, so as to reduce the situation of access failure.
  • the method further includes:
  • Step S202 in response to the parameter of the prohibition timer, start the prohibition timer.
  • the prohibition timer may be started according to the parameter of the prohibition timer to start timing. During the timing process, the UE does not re-initiate the access request until the timing of the prohibit timer stops, and then re-initiates the access request, thereby increasing the probability of successful access and reducing unnecessary access requests.
  • the timing of the above barring timer can be started. In this way, the UE will not initiate an access request again during the timing process of the prohibit timer. Or, the UE starts the barring timer at any appropriate time; and the UE does not initiate an access request when the barring timer does not expire.
  • the method further includes:
  • the above-mentioned parameter of the disable timer may include a deactivation trigger event.
  • the UE may detect whether there is a detriggering event in the process of disabling the timer timing according to the deactivation event specified in the parameter, and determine the timing of stopping or continuing the deactivation timer according to the specification of the parameter.
  • the timing of stopping or continuing the prohibition timer may be determined according to the communication standard or the configuration of the base station when a de-triggering event is detected.
  • the deactivation trigger event includes at least one of the following:
  • the determining to stop or continue the timing of the disable timer when a release trigger event is detected includes:
  • the timing of the prohibit timer is continued according to the parameter.
  • the first service application scenario when the above-mentioned first service application scenario is an AI-related service type, it can be considered that the first service application scenario has a high demand for network capabilities.
  • the trigger event stops timing. In this way, repeated access failures in the first service application scenario can be reduced, and the situation that the service cannot be used normally due to the mismatch of network resources after the access is disabled due to the timer interruption timing can also be reduced. As far as possible, make the UE re-access when the network resources meet the demand.
  • the UE can determine to continue the timing of the timer when receiving the RRC connection establishment message and the RRC connection recovery message corresponding to the de-triggering event, so that the process of disabling the timer timing is no longer necessary. Re-initiate the access request.
  • the method further includes:
  • the access stratum AS transmits a notification message for prohibiting access to the first service application scenario to the non-access stratum NAS;
  • the NAS stops the call of the first service application scenario according to the notification message.
  • the communication link between the UE and the network includes the protocol stacks of the access layer and the non-access layer, and realizes signaling transmission between the UE and the network.
  • the access layer establishes a signaling transmission path between the UE and the network, and the non-access layer can perform signaling transmission based on the access layer.
  • the UE when the UE determines, according to the first access control parameter of the first service application scenario, that the access request of the first service application scenario is prohibited, the UE may notify the non-access layer to prohibit access. At this time, the non-access layer may stop initiating the access request of the first service application scenario according to the notification message of prohibiting access, and further receive the notification message of allowing access, the notification message that the access prohibition is released, or After the access prohibition time period expires, the access request is re-initiated.
  • the method further includes:
  • the AS transmits, to the NAS, the prohibition duration information for prohibiting access to the first service application scenario; wherein, the prohibition duration is used to, after the prohibition duration, the NAS re-initiate the first service application scenario.
  • the access layer can also notify the non-access layer of the prohibition duration according to the parameter of the prohibition timer in the above-mentioned embodiment, so that the non-access layer can re-initiate the access request after the prohibition time expires.
  • a more refined access control can be realized by using an access control parameter for a newly added first service application scenario in the network.
  • a currently unused reserved access category can be used as an access category corresponding to the first service application scenario, and a currently undefined access category can also be added as an access category corresponding to the first service application scenario category.
  • the base station may perform access control on the corresponding access request according to the access category corresponding to the first service application scenario.
  • a currently unused reserved access identifier can be used as an access identifier corresponding to the first service application scenario, and a currently undefined access identifier can also be added as an access identifier corresponding to the first service application scenario logo.
  • the base station may perform access control on the corresponding access request according to the access category and/or access identifier corresponding to the first service application scenario.
  • the reasons for establishing a call in the first service application scenario include the following:
  • the reason for the call establishment is "AI business related"
  • the call establishment reason is "AI local training"
  • the reason for the call establishment is "joint training between the AI cloud and the local UE".
  • the access prohibition of the service type of the first service application scenario will not be released because the user equipment receives a terminal service (MT service), that is, a called service or an emergency call service. That is, the timer is prohibited, such as the T390 timer will continue to run.
  • MT service terminal service
  • the timer is prohibited, such as the T390 timer will continue to run.
  • the access prohibition of the service type of the first service application scenario will not be stopped due to the receipt of the RRC connection establishment message and the RRC connection recovery message, that is, the T390 timer continues to run.
  • whether the access prohibition of the service type of the first service application scenario can be released because the user equipment receives the terminal service (MT service), that is, the called service or the emergency call service, etc., can be determined according to the network configuration. or agreement.
  • the network side can notify the user equipment of configuration information through dedicated or public signaling.
  • the access layer can notify the non-access layer, and the current user equipment access request to the AI/ML model is prohibited state. Further, the non-access stratum can also be notified of the length of time that access is prohibited, that is, the length of time that the upper layer is notified that the lower layer is blocked, so that the upper layer can initiate an access request again at a suitable time.
  • an embodiment of the present disclosure further provides an access control apparatus 700, including:
  • the delivery module 701 is configured to deliver a first access control parameter according to a first service application scenario, where the first access control parameter includes a first access type of the first service application scenario.
  • the apparatus further includes:
  • a first determining module configured to determine, in response to the existence of the first service application scenario, a first access identifier of the first service application scenario; wherein the first access control parameter further includes: and the first access control parameter the first access identifier corresponding to the first access category.
  • the first service application scenario includes at least one of the following:
  • the first access control parameter further includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the apparatus further includes:
  • a configuration module configured to configure a prohibit timer for the first service application scenario according to the service type of the first service application scenario.
  • the configuration module is configured to:
  • the timing of whether to stop the prohibit timer is configured when a de-triggering event is detected.
  • different service types have different resource consumption attributes
  • the resource consumption attribute includes at least one of the following:
  • the deactivation trigger event includes at least one of the following:
  • the configuration module includes:
  • the first configuration sub-module is configured to, in response to the service type of the first service application scenario being an AI-related service type, configure to continue the prohibit timer when an RRC connection establishment message corresponding to the release trigger event is received Timing;
  • the second configuration sub-module is configured to, in response to the service type of the first service application scenario being an AI-related service type, configure to continue the prohibit timer when an RRC connection recovery message corresponding to the release trigger event is received Timing.
  • the configuration module is configured to:
  • the timing of whether to stop the prohibit timer is configured through dedicated signaling or public signaling or a communication protocol when a de-triggering event is detected.
  • an embodiment of the present disclosure further provides an access control apparatus 800, including:
  • the receiving module 801 is configured to receive a first access control parameter, wherein the first access control parameter is used for access control in a first service application scenario, wherein the first access control parameter Including the first access category of the first service application scenario.
  • the first access control parameter further includes: the first access identifier corresponding to the first access category in the first service application scenario.
  • the first access control parameter further includes: a parameter of a prohibition timer
  • the prohibition timer is used to prohibit the access initiated by the service of the first service application scenario.
  • the apparatus further includes:
  • a start module configured to start the prohibit timer in response to the parameter of the prohibit timer.
  • the apparatus further includes:
  • the second determining module is configured to determine to stop or continue the timing of the disable timer when a de-triggering event is detected.
  • the deactivation trigger event includes at least one of the following:
  • the second determining module includes:
  • the first timing sub-module is configured to, in response to the service type of the first service application scenario being the service type associated with AI, when receiving the RRC connection establishment message corresponding to the release trigger event, continue according to the configuration information the timing of the prohibition timer;
  • the second timing sub-module is configured to, in response to that the service type of the first service application scenario is the AI-related service type, when receiving the RRC connection recovery message corresponding to the release trigger event, continue according to the configuration information Timing of the disable timer.
  • the apparatus further includes:
  • a transmission module configured to, in response to the first access control parameter, transmit, at the access stratum AS, a notification message for prohibiting access to the first service application scenario to the non-access stratum NAS;
  • a stopping module configured to stop the call of the first service application scenario at the NAS according to the notification message.
  • the apparatus further includes:
  • an initiating module configured to transmit the prohibition duration information of prohibiting access to the first service application scenario to the NAS when the AS; wherein, the prohibition duration is used for, after the prohibition duration, in the NAS Re-initiate the call of the first service application scenario.
  • Embodiments of the present disclosure provide a communication device, including a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being run by the processor, wherein the processor executes the execution of any of the foregoing technical solutions when running the executable program. Access control method.
  • the communication device may be the aforementioned base station or UE.
  • the processor may include various types of storage media, which are non-transitory computer storage media that can continue to memorize and store information on the communication device after the power is turned off.
  • the communication device includes a base station or a user equipment.
  • the processor may be connected to the memory through a bus or the like, and is used to read the executable program stored on the memory.
  • Embodiments of the present disclosure provide a non-transitory computer-readable storage medium, where an executable program is stored in the computer storage medium; after the executable program is executed by a processor, any technology involved in the embodiments of the present disclosure can be implemented method shown in the scheme.
  • FIG. 9 is a block diagram of a communication device 900 according to an exemplary embodiment.
  • communication device 900 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.
  • a communication device 900 may include one or more of the following components: a processing component 901, a memory 902, a power supply component 903, a multimedia component 904, an audio component 905, an input/output (I/O) interface 906, a sensor component 907, and communication component 908.
  • a processing component 901 a memory 902
  • a power supply component 903 a multimedia component 904
  • an audio component 905 an input/output (I/O) interface 906, a sensor component 907, and communication component 908.
  • I/O input/output
  • the processing component 901 generally controls the overall operation of the communication device 900, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 901 may include one or more processors 910 to execute instructions to perform all or part of the steps of the methods described above.
  • the processing component 901 may also include one or more modules to facilitate interaction between the processing component 901 and other components.
  • processing component 901 may include a multimedia module to facilitate interaction between multimedia component 904 and processing component 901 .
  • Memory 910 is configured to store various types of data to support operation at communication device 900 .
  • Examples of such data include instructions for any application or method operating on the communication device 900, contact data, phonebook data, messages, pictures, videos, and the like.
  • Memory 902 may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic or Optical Disk Magnetic Memory
  • Power supply component 903 provides power to various components of communication device 900 .
  • Power supply components 903 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to communication device 900 .
  • Multimedia component 904 includes screens that provide an output interface between the communication device 900 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
  • the touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
  • the multimedia component 904 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front camera and/or rear camera can be a fixed optical lens system or have focal length and optical zoom capability.
  • Audio component 905 is configured to output and/or input audio signals.
  • audio component 905 includes a microphone (MIC) that is configured to receive external audio signals when communication device 900 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 910 or transmitted via communication component 908 .
  • audio component 905 also includes a speaker for outputting audio signals.
  • the I/O interface 906 provides an interface between the processing component 901 and a peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: home button, volume buttons, start button, and lock button.
  • Sensor assembly 907 includes one or more sensors for providing various aspects of status assessment for communication device 900 .
  • the sensor assembly 907 can detect the open/closed state of the communication device 900, the relative positioning of the components, such as the display and the keypad of the communication device 900, and the sensor assembly 907 can also detect the communication device 900 or the communication device 900.
  • the position of a component changes, the presence or absence of user contact with the communication device 900, the orientation or acceleration/deceleration of the communication device 900 and the temperature change of the communication device 900.
  • Sensor assembly 907 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact.
  • Sensor assembly 907 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 907 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 908 is configured to facilitate wired or wireless communication between communication device 900 and other devices.
  • Communication device 900 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 908 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 908 also includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module may be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology or other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • communication device 900 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A programmed gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A programmed gate array
  • controller microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • non-transitory computer readable storage medium including instructions, such as a memory 902 including instructions, executable by the processor 910 of the communication device 900 to perform the method described above.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • an embodiment of the present disclosure shows the structure of another communication device.
  • the communication device may be the base station involved in the embodiment of the present disclosure.
  • the communication device 1000 may be provided as a network device. 12
  • the communication device 1000 includes a processing component 1022, which further includes at least one processor, and a memory resource, represented by memory 1032, for storing instructions executable by the processing component 1022, such as an application program.
  • An application program stored in memory 1032 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 1022 is configured to execute instructions to perform any of the aforementioned methods applied to the communication device.
  • the communication device 1000 may also include a power supply assembly 1026 configured to perform power management of the communication device 1000, a wired or wireless network interface 1050 configured to connect the communication device 1000 to a network, and an input output (I/O) interface 1058 .
  • Communication device 1000 may operate based on an operating system stored in memory 1032, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

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

Abstract

本公开实施例提供了一种接入控制方法及装置、通信设备和存储介质。本公开实施例所提供的接入控制方法包括：根据第一业务应用场景，下发第一接入控制参数，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。

Description

接入控制方法及装置、存储介质 技术领域
本公开实施例涉及无线通信领域但不限于无线通信领域，尤其涉及一种接入控制方法及装置、存储介质。
背景技术
在LTE(Long Term Evolution，长期演进)通信系统以及5G的NR(New Radio，新空口)通信系统中，AC(Access Control，接入控制)限制的工作机制是：根据终端的接入等级(Access Class)以及终端发起的呼叫来获取相应的AC barring(AC限制)参数，进行AC限制判决(AC barring check)。
然而，不同的业务类型可能具有不同的资源需求，例如无线资源、计算能力资源以及存储资源等等。3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)现有的业务仅考虑到了无线资源的需求，可能不足以满足如AI(Artificial Intelligence，人工智能)或ML(Machine Learning,机器学习)等业务的资源需求。
发明内容
本公开提供一种接入控制方法及装置、存储介质。
根据本公开实施例的第一方面，提供一种接入控制方法，包括：
根据第一业务应用场景，下发第一接入控制参数，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在一些实施例中，所述方法还包括：
响应于存在所述第一业务应用场景，确定所述第一业务应用场景的第一接入标识；其中，所述第一接入控制参数，还包含：与所述第一接 入类别对应的所述第一接入标识。
在一些实施例中，所述第一业务应用场景包括以下至少之一：
以AI业务为呼叫建立原因的业务应用场景；
以AI模型在终端本地训练业务为呼叫建立原因的业务应用场景；
以AI模型在云端训练业务为呼叫建立原因的业务应用场景；
以AI模型在本地和云端共同训练业务为呼叫建立原因的业务应用场景。
在一些实施例中，所述第一接入控制参数，还包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在一些实施例中，所述方法还包括：
根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器。
在一些实施例中，所述根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器，包括：
响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
在一些实施例中，不同所述业务类型的资源消耗属性不同；
其中，所述资源消耗属性包含以下至少之一：
指示计算资源消耗的属性；
指示存储资源消耗的属性；
指示网络资源消耗的属性。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
在一些实施例中，所述响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时，包括：
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC(Radio Resource Control，无线资源控制)连接建立消息时继续所述禁止定时器的定时；
和/或，
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接恢复消息时继续所述禁止定时器的定时。
在一些实施例中，所述响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时，包括：
响应于所述第一业务应用场景的业务类型，通过专用信令或公共信令或通信协议配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
根据本公开实施例的第二方面，提供一种接入控制方法，包括：
接收第一接入控制参数，其中，所述第一接入控制参数，用于对在在第一业务应用场景的接入控制，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在一些实施例中，所述第一接入控制参数，还包括：在所述第一业务应用场景与所述第一接入类别对应的所述第一接入标识。
在一些实施例中，所述第一接入控制参数，还包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在一些实施例中，所述方法还包括：
响应于所述禁止定时器的参数，启动所述禁止定时器。
在一些实施例中，所述方法还包括：
根据所述参数，确定在检测到缓解触发时间时停止或继续所述禁止定时器的定时。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
在一些实施例中，所述根据所述参数，确定在检测到缓解触发时间时停止或继续所述禁止定时器的定时，包括：
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接建立消息时，根据所述参数继续所述禁止定时器的定时；
和/或，
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接恢复消息时，根据所述参数继续所述禁止定时器的定时。
在一些实施例中，所述方法还包括：
响应于所述第一接入控制参数，在AS(Access Stratum，接入层)将禁止接入所述第一业务应用场景的通知消息传输至NAS(Non Access Stratum，非接入层)；
在所述NAS根据所述通知消息停止所述第一业务应用场景的呼叫。
在一些实施例中，所述方法还包括：
在所述AS将禁止接入所述第一业务应用场景的禁止时长信息传输至所述NAS；其中，所述禁止时长用于，在所述禁止时长后，在所述NAS 重新发起所述第一业务应用场景的呼叫。
根据本公开实施例的第三方面，提供一种接入控制装置，包括：
下发模块，配置为根据第一业务应用场景，下发第一接入控制参数，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在一些实施例中，所述装置还包括：
第一确定模块，配置为响应于存在所述第一业务应用场景，确定所述第一业务应用场景的第一接入标识；其中，所述第一接入控制参数，还包含：与所述第一接入类别对应的所述第一接入标识。
在一些实施例中，所述第一业务应用场景包括以下至少之一：
以AI业务为呼叫建立原因的业务应用场景；
以AI模型在终端本地训练业务为呼叫建立原因的业务应用场景；
以AI模型在云端训练业务为呼叫建立原因的业务应用场景；
以AI模型在本地和云端共同训练业务为呼叫建立原因的业务应用场景。
在一些实施例中，所述第一接入控制参数，还包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在一些实施例中，所述装置还包括：
配置模块，配置为根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器。
在一些实施例中，所述配置模块，配置为：
响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
在一些实施例中，不同所述业务类型的资源消耗属性不同；
其中，所述资源消耗属性包含以下至少之一：
指示计算资源消耗的属性；
指示存储资源消耗的属性；
指示网络资源消耗的属性。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
在一些实施例中，所述配置模块，包括：
第一配置子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接建立消息时继续所述禁止定时器的定时；
和/或，
第二配置子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接恢复消息时继续所述禁止定时器的定时。
在一些实施例中，所述配置模块，配置为：
响应于所述第一业务应用场景的业务类型，通过专用信令或公共信令或通信协议配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
根据本公开实施例的第四方面，提供一种接入控制装置，包括：
接收模块，配置为接收第一接入控制参数，其中，所述第一接入控制参数，用于对在在第一业务应用场景的接入控制，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在一些实施例中，所述第一接入控制参数，还包括：在所述第一业 务应用场景与所述第一接入类别对应的所述第一接入标识。
在一些实施例中，所述第一接入控制参数，还包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在一些实施例中，所述装置还包括：
启动模块，配置为响应于所述禁止定时器的参数，启动所述禁止定时器。
在一些实施例中，所述装置还包括：
第二确定模块，配置为在检测到解除触发事件时，确定停止或继续所述禁止定时器的定时。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
在一些实施例中，所述第二确定模块，包括：
第一定时子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接建立消息时，根据所述配置信息继续所述禁止定时器的定时；
和/或，
第二定时子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接恢复消息时，根据所述配置信息继续所述禁止定时器的定时。
在一些实施例中，所述装置还包括：
传输模块，配置为响应于所述第一接入控制参数，在接入层AS将禁止接入所述第一业务应用场景的通知消息传输至非接入层NAS；
停止模块，配置为在所述NAS根据所述通知消息停止所述第一业务应用场景的呼叫。
在一些实施例中，所述装置还包括：
发起模块，配置为在所述AS将禁止接入所述第一业务应用场景的禁止时长信息传输至所述NAS；其中，所述禁止时长用于，在所述禁止时长后，在所述NAS重新发起所述第一业务应用场景的呼叫。
根据本公开实施例的第五方面，提供一种通信设备，所述通信设备至少包括：处理器和用于存储能够在所述处理器上运行的可执行指令的存储器，其中：
处理器用于运行所述可执行指令时，所述可执行指令执行上述任一项接入控制方法中的步骤。
根据本公开实施例的第六方面，提供一种非临时性计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，该计算机可执行指令被处理器执行时实现上述任一项接入控制方法中的步骤。
本公开的实施例提供的技术方案可以包括以下有益效果：本公开实施例提供了一种接入控制的实现方式，根据第一业务应用场景，针对性地下发相应的第一接入控制参数，从而便于实现该第一业务应用场景的接入控制。如此，相对于相关技术中，对所有的业务应用场景使用统一的接入控制方法，本公开实施例的技术方案，可以根据第一业务应用场景的特定需求区别于其他业务应用场景的接入控制方法，从而便于满足第一业务应用场景对于带宽或者处理能力等资源的需求。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明实施例，并与说明书一起用于解释本发明实施例的原理。
图1是根据一示例性实施例示出的一种无线通信系统的结构示意图；
图2是根据一示例性实施例示出的一种接入控制方法的流程示意图一；
图3是根据一示例性实施例示出的一种接入控制方法的流程示意图二；
图4是根据一示例性实施例示出的一种接入控制方法的流程示意图三；
图5是根据一示例性实施例示出的一种接入控制方法的流程示意图四；
图6是根据一示例性实施例示出的一种接入控制方法的流程示意图五；
图7是根据一示例性实施例示出的一种接入控制装置的结构示意图一；
图8是根据一示例性实施例示出的一种接入控制装置的结构示意图二；
图9是根据一示例性实施例示出的通信设备的结构示意图一；
图10是根据一示例性实施例示出的通信设备的结构示意图二。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”及“若”可以被解释成为“在…… 时”或“当……时”或“响应于确定”。
为了更好地描述本公开任一实施例，本公开一实施例以一个接入控制的应用场景为例进行示例性说明。
请参考图1，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1所示，无线通信系统是基于蜂窝移动通信技术的通信系统，该无线通信系统可以包括：若干个终端110以及若干个基站120。
其中，终端110可以是指向用户提供语音和/或数据连通性的设备。终端110可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，终端110可以是物联网终端，如传感器设备、移动电话(或称为“蜂窝”电话)和具有物联网终端的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程终端(remote terminal)、接入终端(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户终端(user equipment，终端)。或者，终端110也可以是无人飞行器的设备。或者，终端110也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线终端。或者，终端110也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
基站120可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(Long Term Evolution，LTE)系统；或者，该无线通信系统也可以是5G系统，又称新空口(new radio，NR)系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为NG-RAN(New Generation-Radio Access Network， 新一代无线接入网)。
其中，基站120可以是4G系统中采用的演进型基站(eNB)，或5G系统中采用集中分布式架构的基站(gNB)，或更下一代移动通信网络技术的任何类型的基站。当基站120采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对基站120的具体实现方式不加以限定。
基站120和终端110之间可以通过无线空口建立无线连接。在不同的实施方式中，该无线空口是基于第四代移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，终端110之间还可以建立E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的V2V(vehicle to vehicle，车对车)通信、V2I(vehicle to Infrastructure，车对路边设备)通信和V2P(vehicle to pedestrian，车对人)通信等场景。
在一些实施例中，上述无线通信系统还可以包含网络管理设备130。
若干个基站120分别与网络管理设备130相连。其中，网络管理设备130可以是无线通信系统中的核心网设备，比如，该网络管理设备130可以是演进的数据分组核心网(Evolved Packet Core，EPC)中的移动性管理实体(Mobility Management Entity，MME)。或者，该网络管理设备也可以是其它的核心网设备，比如服务网关(Serving GateWay，SGW)、公用数据网网关(Public Data Network GateWay，PGW)、策略与计费规则功能单元 (Policy and Charging Rules Function，PCRF)或者归属签约用户服务器(Home Subscriber Server，HSS)等。对于网络管理设备130的实现形态，本公开实施例不做限定。
根据5G系统NR接入控制的结论，接入控制的接入控制参数(AC Barring参数)的结构是针对每个PLMN(Public Land Mobile Network，公共陆地移动网)、各接入类别以及各接入标识确定的。下表1给出了接入控制参数的示例，其中，PLMN的最大数目为6，接入类别的最大数目为64，接入标识的最大数目为16。
表1
Figure PCTCN2020099027-appb-000001
上表1中，Access categories即接入类别，根据3GPP TS24 301的规定，接入类别包括如下几种：“originating signalling(源端信令)”，“emergency calls(紧急呼叫)”，“originating MMTEL(MultiMediaTelephony，多媒体电话)voice(源端多媒体语音通话)”，“originating MMTEL video(源端多媒体视频通话)”，“originating SMSoIP(Short Message Service over Internet Protocol，基于网际协议的短信传输)”，“originating SMS(源端短信息)”， “terminating calls(终端呼叫)”，“originating calls(源端呼叫)”以及“mobile originating CS fallback(移动源端电路域回落)”。
上表1中，Access identities即接入标识。可以理解为UE(User Equipment，用户设备)的属性或等级比如0至9为低优先级用户，如个人用户，11至15为高优先级用户，如涉及公共安全及紧急业务或者PLMN管理相关的用户。
表格中接入控制参数的定义可包括如下方式：针对低优先级用户可根据随机数和barring生效时长来定义；针对高优先级用户则可采用位图(bitmap)形式。其中，低优先级用户包括商用用户，高优先级用户。
所以基本的接入控制检测(AC barring check)的过程就是根据接入类别以及接入标识，得到AC barring参数，进行接入控制检测。接入控制参数对于低优先级用户(0-9)通常采用随机数，而对于高优先级用户(11-15)，则采用bitmap形式。通常该参数将在系统消息中定义，对于随机数方式，若是被限制，则需要启动一个定时器，其时间将通过AC限制时长(AC-BarringTime)计算得到。例如，限制时长为512秒。
在本公开实施例中，基于AI和/或ML的移动应用计算密集、内存消耗和功耗大的发展趋势。同时，终端设备通常具有严格的能耗、计算和内存成本限制。因此，需要将AI/ML在设备和网络上进行分离。即将计算密集型、能源密集型部分卸载到网络端点，而将隐私敏感和延迟敏感部分留在终端设备上。设备将操作或模型执行到特定的部件或层，并将中间数据发送到网络端点。网络端点执行剩余的部分，并将推理结果反馈给设备。拆分AI及ML操作的关键是选择最佳的拆分模式和拆分点，以保证所需资源低于移动设备上可用资源的上限，并优化计算、存储或内存、功耗，设备和网络侧的通信资源。对于不同的拆分模式来说，对于上下行的资源需求是差异非常大的。比如对于AI和/或ML操作在本地的训练模式，因为涉及 到AI及ML模型的下载，需要大量的下行带宽，反而对于上行的带宽是比较小的；而对于AI和/或ML操作在云端的训练模式，因为涉及到训练数据的上传，需要大量的上行带宽，而对于下行仅仅返回训练之后推理的结果，对于下行的带宽是比较小的。而对于本地训练和云端训练同时进行的用户，则上下行都需要大带宽。因此当用户发起一个模型训练的应用，从AS层看，根据现有的流程，AC的流程过于粗糙，因为其接入类别都是“源端呼叫(originating calls)”，此外，由于是同一个终端发起的，因此接入标识也是相同的。也就是说，对于接入类别及接入标识的区分粒度不够精细，但是事实上不同接入类别需要耗费的资源是完全不同的，对于网络造成的负荷也是完全不同，因此需要更加精细的粒度进行处理。另外，AI及ML的移动应用所需要的资源不仅仅是包括无线资源，还包括计算能力等资源。而3GPP现有的业务仅仅考虑了无线资源的需求，因此对于AI及ML的移动在接入控制方面需要进行特殊处理。
如图2所示，本公开实施例提供一种接入控制方法，包括：
步骤S101、根据第一业务应用场景，下发第一接入控制参数，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在本公开实施例中，该接入控制方法可应用于基站、核心网设备等网络设备。下面以基站为例，基站可为不同的业务应用场景配置不同的接入控制参数，从而便于在UE请求接入相应的业务时，根据对应的接入控制参数确定是否需要禁止或允许该业务的接入。
在本公开的所有实施例中，第一接入控制参数可以为用于指示第一业务应用场景的第一接入类别的标识，也可以为用于暗示第一业务应用场景的第一接入类别。暗示第一业务应用场景的第一接入类别是指，该第一接入控制参数可以为一信令的长度参数，以使UE根据该信令的长度确定出第一接入控制参数；还可以为编码序列，以使UE根据该序列确定 出第一接入控制参数。当然，这些都只是举例说明，而非对本公开实施例保护范围的限定。该第一接入控制参数既可以是明确的一个或多个比特位以指示第一业务应用场景的第一接入类别，也可以为根据通信协议确定的或是由基站指示的用于识别出第一业务应用场景的第一接入类别的某一信息。
在本公开实施例中，第一业务应用场景可通过上述第一接入类别来区分，可采用不同于相关技术中的接入类别的新的接入类别来标识。不同于UE的通话或数据通信的接入请求，第一业务应用场景可以为具有较大无线资源或网络计算处理能力的资源需求的业务应用场景。例如上述AI及ML的相关业务场景。通过向UE下发第一业务应用场景对应的第一接入控制参数，可以实现对第一业务应用场景的接入请求的独立控制，从而便于UE在网络资源允许的情况下接入第一业务应用场景的相关业务。
接入类别为UE与基站之间建立通信连接的类别，表明了UE建立RRC连接的不同原因。基站根据不同的接入类别，可进行对应的接入控制，提供不同的接入权限以及禁止接入的定时规则等等。例如，UE建立RRC连接的原因为紧急呼叫，则接入类别为“emergency calls”，即紧急呼叫类别。又如，UE作为主叫端发起的RRC连接请求，即UE始发的呼叫请求，接入类别可为“originating calls”即源端呼叫。
典型的紧急呼叫包括但不限于：求救呼叫、报警呼叫、消防呼叫或求医呼叫。
在本公开实施例中，对于第一业务应用场景，可确定对应的不同于其他业务应用场景的接入类别。例如，第一业务应用场景是对于网络带宽资源、运算资源以及存储资源有较高需求的AI和/或ML业务场景，则可对应确定AI业务类别作为与第一业务应用场景对应的接入类别。这里， AI业务类别可为不同于相关技术中已定义的上述“源端信令”，“紧急呼叫”，“源端多媒体语音通话”，“源端多媒体视频通话”，“基于网际协议的短信传输”，“源端短信息”，“终端呼叫”，“源端呼叫”以及“移动源端电路域回落”等的专用接入类别，是用于定义第一业务应用场景的特定接入类别。
在本公开实施例中，将例如AI和/或ML相关的第一业务应用场景区别于相关技术中UE始发的其他呼叫所对应的“源端呼叫”的接入类别，从而便于与其他业务应用的呼叫分别进行接入控制。
可以理解的是，对于本公开实施例中定义的第一业务应用场景以外的业务类型，如UE发起的其他业务应用场景，可包括第二业务应用场景等。并且，对应于第二业务应用场景的第二接入控制参数，可以与第一接入控制参数相同或不相同。
不同业务场景分配不同的接入控制参数，从而减少采用统一接入控制参数的导致的接入控制效果差，且分别下发不同的接入控制参数，使得两类业务场景的接入控制更加灵活。
如此，便于在UE向基站发起第一业务应用场景的接入请求时，根据对应的第一业务类别，来确定用于接入控制的第一接入控制参数，从而进行有针对性的接入控制。
在一些实施例中，如图3所示，所述方法还包括：
步骤S102、响应于存在所述第一业务应用场景，确定所述第一业务应用场景的第一接入标识；其中，所述第一接入控制参数，还包含：与所述第一接入类别对应的所述第一接入标识。
接入标识为表明UE对应的用户级别或者用户类型的标识，可与SIM卡对应设置。例如，个人用户的接入标识可为0至9中的任一个。
在本公开实施例中，上述第一接入标识可独立于UE中SIM卡对应 的接入标识单独设置，例如，UE在使用其他业务应用场景，如通话场景或网页数据传输场景等场景时，用户设备对应的接入标识为与SIM卡对应设置的低优先级用户的接入标识，例如0-9。而第一业务应用场景对应的第一接入标识可不同于上述低优先级用户的接入标识且不同于高优先级用户的接入标识。例如，低优先级用户的接入标识为0-9，高优先级用户的接入标识为11-15，而对应于第一业务应用场景的接入标识可为16等。
当然，在实际应用中，如果低优先级用户的接入标识0-9中存在未被使用的预留接入标识，则也可以将第一业务应用场景对应的第一接入标识定义为上述预留接入标识。例如，实际应用中，低优先级用户的接入标识包括0-8，9为预留接入标识，则将上述第一业务应用场景的第一接入标识定义为预留接入标识9。
如此，可以在业务应用场景的层面对接入标识进行更加细化的区分，从而便于对应配置接入控制参数。
在一些实施例中，所述第一业务应用场景包括以下至少之一：
以AI业务为呼叫建立原因的业务应用场景；
以AI模型在UE本地训练业务为呼叫建立原因的业务应用场景；
以AI模型在云端训练业务为呼叫建立原因的业务应用场景；
以AI模型在本地和云端共同训练业务为呼叫建立原因的业务应用场景。
以AI业务为呼叫建立原因的业务应用场景，是指以使用云端和/或本地的数据及模型的相关业务；以AI模型在UE本地训练业务为呼叫建立原因的业务应用场景、以AI模型在云端训练业务为呼叫建立原因的业务应用场景以及以AI模型在本地和云端共同训练业务为呼叫建立原因的业务应用场景则是指：模型的建立以及训练过程的相关业务。
例如，AI业务可包括：UE基于获取的图像，如监控图像等，向云端请求目标识别或者目标跟踪的业务请求，需要使用云端已建立的数据库和/或AI模型，从而能够将获取的图像作为输入数据，并使用云端数据库和/或AI模型实现快速识别。AI模型的训练业务可包括：UE将采集的数据传输至云端，以使云端能够利用这些数据作为训练数据进行训练以确定和/或改进AI模型。例如，能够根据这些数据作为训练模型以调整AI模型的神经网络参数等，从而得到供AI业务使用的AI模型。
考虑到AI业务的特殊性：AI业务应用场景，需要本地和/或云端的大量数据处理，例如：本地应用使用云端的模型进行数据处理，下载数据使用本地模型进行数据处理，等；AI模型的训练，例如：本地和/或云端的模型训练，同样需要大量的数据上传和下载，并进行数据的运算处理。因此，AI相关业务对网络的无线资源及计算处理能力以及存储能力等具有较高的需求。这里，将以上述AI相关的业务(包括AI业务的应用以及AI模型的训练)为呼叫建立原因的业务应用场景，定义为上述第一业务应用场景，从而便于对AI业务的相关应用进行有针对性的接入控制，便于AI业务在网络状态合适的情况下进行接入。
可以理解的是，上述AI相关的业务包括但不限于以下任意一种情况：模型训练、ML、模型调整、模型应用。
此外，对于AI模型的本地训练业务与云端训练业务还可进一步细分对应不同的接入控制参数。在一些实施例中，AI模型在UE本地训练业务需要大量的下行带宽，而数据的处理运算则对本地能力要求较高，因此可配置下行链路拥堵或UE处理能力低于阈值时禁止接入的接入控制参数。在一些实施例中，AI模型在云端训练的业务场景，则需要大量的上行带宽，并且需要云端具有较高的运算处理能力，因此可配置云端网络繁忙或上行链路拥堵或云端处理能力低于阈值时禁止接入的接入控制 参数。
如此，可根据呼叫建立原因来确定UE发起的呼叫是否属于第一业务应用场景，进而根据上述第一接入类别及第一接入标识来配置对应的第一接入控制参数。
在一些实施例中，所述第一接入控制参数，包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在本公开的所有实施例中，所述第一业务应用场景的第一接入类别和禁止定时器的参数，可以通过相同的信令或不同的信令发送到UE。
当第一接入控制参数对应的接入控制结果为禁止接入时，可为该第一业务应用场景的业务配置禁止定时器。禁止定时器的参数包括但不限于以下的任意一种：禁止该第一业务应用场景的呼叫被接入的时长，禁止定时器中断定时的条件。在一些实施例中，该禁止定时器的参数可以为：是否基于紧急呼叫事件或者呼入事件等中断禁止定时器的运行。
在本公开实施例中，以第一业务应用场景的业务始发的接入为UE端主动发起的接入请求，响应于UE端首次作为始发端发起的接入请求被禁止，UE可在禁止定时器的定时过程中不再重新作为始发端发起接入请求。当然，如果UE端作为被叫端，则可根据预先的配置确定是否停止禁止定时器的定时。
基站将禁止定时器的参数通过前述的第一接入控制参数发送到UE，以使UE能够根据参数确定所述禁止定时器的时长，延迟发起接入请求。或者，UE在需要发起第一业务应用场景的接入请求时，可根据参数的确定的间隔时长向基站发起接入请求，直至成功接入。这样，UE在禁止定时器计时的过程中，不会发起接入请求，从而减少不必要的重复发起的 接入请求，并且提升了再次发起接入请求时成功接入的概率。
可以理解的是，如果UE在首次发起接入请求时被禁止，则可启动上述禁止定时器的定时。这样，UE在禁止定时器的定时过程中不会再次发起接入请求。或是，UE在任何恰当的时间点启动该禁止定时器；且UE在禁止定时器未到时的时候不发起接入请求。
在本公开的一些实施例中，所述方法还包括：
步骤S103、根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器。
示例性的，如图4所示，该步骤103可以与前述的步骤101、102结合实施，也可以单独实施，本公开实施例并不对此做出限定；同时，如果步骤103与前述的步骤101、102结合实施时，该三个步骤的执行顺序并不限定于步骤101至103的执行顺序，而可以为任何可能的执行顺序。
在本公开实施例中，基站可在接收到UE发起的第一业务应用场景的接入请求时，根据第一业务应用场景的业务类型，配置对应的禁止定时器，并将配置好的参数下发至UE。也可在未接收到UE发起的接入请求的情况下，直接将针对第一业务应用场景的禁止定时器配置参数并下发至UE。
如此，基站为区别于其他业务应用场景的业务类型配置特定的禁止定时器，从而便于UE根据第一业务应用场景的需求来运行禁止定时器。
其他业务应用场景可以为第二业务应用场景。
在一些实施例中，所述根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器，包括：
响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
上述禁止定时器的参数可以包括解除触发事件和/或禁止定时器的时 长解除触发事件。解除触发事件是指触发UE解除禁止接入的事件，根据配置解除触发事件是否用于停止禁止定时器的定时，可使UE在解除触发事件发生时确定是否可以发起接入请求。例如，如果在禁止定时器定时的过程中，检测到上述解除触发事件，则可停止禁止定时器的定时，使得UE可以发起接入请求；即，解除触发事件能够无视禁止定时器是否仍然在运行，直接发起接入请求。
解除触发事件可包括紧急呼叫事件、呼入事件等等。然而，由于第一业务应用场景可能具有较高的网络资源、计算资源以及存储资源的需求，当禁止定时器由于解除触发事件被暂停定时，使得UE重新发起接入请求，则可能由于网络资源的不足而重新被禁止，或者接入后无法满足第一业务应用场景的需求。
因此，在本公开实施例中，也可根据第一业务应用场景的业务类型，配置在检测到解除触发事件时不停止定时，使得第一业务应用场景的接入请求继续被延迟，直至定时结束。当然，对于其他业务类型的业务应用场景(如不同于第一业务应用场景的第二业务应用场景)，则可在检测到解除触发事件时停止定时，UE可再次发起接入请求，也就是针对第二业务应用场景，可配置解除触发事件用于停止第二业务应用场景接入请求对应的禁止定时器的定时。
如此，对于第一业务应用场景的接入请求，不会因为紧急呼叫、或者呼入事件等等而停止禁止定时器的定时，从而在禁止定时器定时的过程中，不会中断定时并进而在不必要或者不符合应用需求的情况下发起接入请求。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
上述实施例中，被叫事件为UE接收到的通信连接请求，由于是被动接收的，因此可以作为解除触发事件，便于对端发起连接请求时能够成功与UE建立通信连接。而紧急呼叫事件则是便于UE自身能够及时发起呼叫，提升紧急呼叫事件的及时性。
本公开的一些实施例中，被叫事件是UE被其他UE或者网络设备呼叫时产生的连接请求，紧急呼叫事件是指基于特定号码的紧急求救或报警电话的接入请求，紧急呼叫事件的接入请求不限于供应商类型以及UE自身的话费或者余量限制。在本公开的一些实施例中，被叫事件或者紧急呼叫事件都可引起各种业务请求对应的禁止定时器的定时停止，便于UE能够重新发起各业务的呼叫请求。由于检测到紧急呼叫事件时，用户可能需要能够快速发出通信业务等的接入请求，因此，紧急呼叫事件可作为解除触发事件。例如：通话请求被禁止的时段内，如果检测到紧急呼叫事件，可能用户急需与亲友通话，因此，可以解除通话请求对应的禁止定时器，以便UE重新发起通话请求。
而对于本公开实施例中的第一业务应用场景，由于是对于网络通信资源、计算资源以及存储资源可能具有较高需求的业务类型，且并非在检测到紧急呼叫事件或者被叫事件时需要快速建立连接的业务。因此，为了提升第一业务应用场景发出接入请求后成功接入的概率，以及减少UE发出接入请求后，仍被禁止的概率，这里，针对第一业务应用场景，即使检测到了解除触发事件，也可根据配置继续禁止定时器的定时。
在一些实施例中，不同所述业务类型的资源消耗属性不同；
其中，所述资源消耗属性包含以下至少之一：
指示计算资源消耗的属性；
指示存储资源消耗的属性；
指示网络资源消耗的属性。
资源消耗属性是不同业务类型在接入网络后对于网络资源的需求及消耗量等。计算资源消耗的属性包括业务对于云端数据处理的能力，处理速率以及运算的数据量等等的需求；存储资源消耗的属性包括业务需要使用的云端数据的存储量的需求；网络资源消耗的属性包括业务对于网络带宽、传输速率以及网络稳定性等的需求。
由于不同的资源消耗属性，对于接入网络的要求不同，采用相同的接入控制参数可能无法满足不同的需求，使得资源消耗大的部分业务接入后无法正常使用。例如，对于AI模型的本地训练业务，需要下载大量数据，因此对于下行带宽等网络资源消耗具有较高需求；对于AI模型的云端训练业务，需要大量数据的上传，同时需要云端具有较高的运算处理能力，以便实现模型训练，因此对于上行带宽等网络资源消耗具有较高需求，同时对于网络端的计算资源消耗具有较高的需求；对于AI业务的应用场景，可通过云端存储的模型进行数据的处理，因此，对于网络端的计算资源消耗属性以及存储资源消耗属性具有较高的需求。
因此，上述第一业务应用场景的业务类型，与其他业务应用场景的业务类型可根据上述资源消耗属性的不同来进行区分。
如此，根据不同的资源消耗属性来区分不同的业务类型，进而对不同的业务应用场景定义不同的接入控制参数，便于针对不同的场景实现满足各自场景的网络需求的接入控制。减少由于业务接入而网络资源不足带来的用户体验的降低。
在一些实施例中，所述响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时，包括：
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接建立消息时继续所述禁止定时器的定时；
和/或，
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接恢复消息时继续所述禁止定时器的定时。
在本公开实施例中，上述第一业务应用场景为AI关联的业务类型时，可认为第一业务应用场景对于网络能力的需求较高，因此，在禁止定时器定时的过程中，无需因解除触发事件停止定时。这样，可以减少第一业务应用场景重复的接入失败，也可以减少由于禁止定时器中断定时而接入后，网络资源不匹配而造成的业务无法正常使用的情况。尽可能使得UE在网络资源满足需求时再接入。
因此，基站可为第一业务应用场景配置在接收到解除触发事件对应的RRC连接建立消息以及RRC连接恢复消息时，继续定时器的定时，从而使UE不重新发起接入请求。
在一些实施例中，所述响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时，包括：
响应于所述第一业务应用场景的业务类型，通过专用信令或公共信令或通信协议配置在检测到解除触发事件时停止所述禁止定时器的定时，
或
响应于所述第一业务应用场景的业务类型，通过专用信令或公共信令或通信协议配置在检测到解除触发事件时继续所述禁止定时器的定时。
在本公开实施例中，对于上述检测到解除触发事件时是否停止禁止定时器的定时的配置，可利用公共信令来下发至UE，也可增加专用于配置禁止定时器的专用信令下发至UE。
公共信令即系统消息。在本公开实施例中，基站可将配置禁止定时器的相关信息，包括上述检测到解除触发事件时是否停止禁止定时器的定时的配置信息，作为通信信令加载在公共信令的通道来进行传输。此外，也可以将用于配置解除触发事件是否用于停止禁止定时器的定时的配置信息，作为通过不同于公共信令的专用信令来传输，专用于配置上述第一业务应用场景对应的禁止定时器。
如图5所示，提供一种接入控制方法，包括：
步骤S201、接收第一接入控制参数，其中，所述第一接入控制参数，用于对在在第一业务应用场景的接入控制，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在本公开的所有实施例中，第一接入控制参数可以为用于指示第一业务应用场景的第一接入类别的标识，也可以为用于暗示第一业务应用场景的第一接入类别。暗示第一业务应用场景的第一接入类别是指，该第一接入控制参数可以为一信令的长度参数，以使UE根据该信令的长度确定出第一接入控制参数；还可以为编码序列，以使UE根据该编码序列确定出第一接入控制参数。当然，这些都只是举例说明，而非对本公开实施例保护范围的限定。该第一接入控制参数既可以是明确的一个或多个比特位以指示第一业务应用场景的第一接入类别，也可以为根据通信协议确定的或是由基站指示的用于识别出第一业务应用场景的第一接入类别的某一信息。
在本公开实施例中，该接入控制方法可应用于终端、UE等。在基站为第一业务应用场景配置第一接入控制参数下发至UE后，UE接收第一接入控制参数，从而确定是否发起第一业务应用场景的接入请求，或者可根据第一接入控制参数确定发起第一业务应用场景的接入时机等等。
由于第一接入控制参数时对应于第一业务应用场景的接入控制参 数，因此，第一接入控制参数不影响UE其他业务的接入控制。从而可以根据第一业务应用场景对应的接入类别的特点和网络是否满足第一业务应用场景的需求来确定何时发起接入请求。
在一些实施例中，所述第一接入控制参数，还包括：在所述第一业务应用场景与所述第一接入类别对应的所述第一接入标识。
这里，第一接入控制参数还可包括对应于第一业务应用场景的第一接入标识。UE可根据第一接入类别以及第一接入标识所对应的第一接入控制参数，确定是否发起接入请求或者发起接入请求后被是否被禁止接入等信息。
在一些实施例中，所述第一接入控制参数，包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在本公开的所有实施例中，第一接入控制参数可以包括所述第一业务应用场景的第一接入类别和/或禁止定时器的参数。
在本公开的所有实施例中，所述第一业务应用场景的第一接入类别和禁止定时器的参数，可以通过相同的信令或不同的信令发送到UE。
这里，禁止定时器的参数可包括在第一业务应用场景被禁止接入后，重新发起接入请求的延迟时长，还可包括在检测到紧急呼叫以及呼入事件等情况时是否停止定时允许重新发起接入请求等规定。
UE可根据禁止定时器的参数，进一步确定发起接入请求的时机，减少接入失败的情况。
在一些实施例中，如图5所示，所述方法还包括：
步骤S202、响应于所述禁止定时器的参数，启动所述禁止定时器。
在UE发起第一业务应用场景的接入请求时，如果被禁止接入，则可 根据禁止定时器的参数启动禁止定时器，开始定时。在定时的过程中，UE不再重新发起接入请求，直至禁止定时器的定时停止后再重新发起接入请求，从而提升接入成功的概率，减少不必要的接入请求。
可以理解的是，如果UE在首次发起接入请求时被禁止，则可启动上述禁止定时器的定时。这样，UE在禁止定时器的定时过程中不会再次发起接入请求。或是，UE在任何恰当的时间点启动该禁止定时器；且UE在禁止定时器未到时的时候不发起接入请求。
在一些实施例中，所述方法还包括：
在检测到解除触发事件时，确定停止或继续所述禁止定时器的定时。
在一些实施例中，上述禁止定时器的参数，可以包括解除触发事件。
UE可根据参数中规定的解除触发事件，在禁止定时器定时的过程中，检测是否存在解除触发事件，并根据参数的规定，确定停止或继续禁止定时器的定时。
在本公开的所有实施例中，可以根据通信标准或基站的配置，来确定在检测到解除触发事件时，停止或继续所述禁止定时器的定时。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
在基站侧的实施例中，对于上述第一接入控制参数的各类型和/或解除触发事件都进行了详细的解释，这里不再赘述。
在一些实施例中，所述在检测到解除触发事件时，确定停止或继续所述禁止定时器的定时，包括：
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接建立消息时，根据所述参数继续所述禁止定时器的定时；
和/或，
响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接恢复消息时，根据所述参数继续所述禁止定时器的定时。
在本公开实施例中，上述第一业务应用场景为AI关联的业务类型时，可认为第一业务应用场景对于网络能力的需求较高，因此，在禁止定时器定时的过程中，无需因解除触发事件停止定时。这样，可以减少第一业务应用场景重复的接入失败，也可以减少由于禁止定时器中断定时而接入后，网络资源不匹配而造成的业务无法正常使用的情况。尽可能使得UE在网络资源满足需求时再接入。
因此，UE可以根据基站配置的禁止定时器的参数，确定在接收到解除触发事件对应的RRC连接建立消息以及RRC连接恢复消息时，继续定时器的定时，从而无需再禁止定时器定时的过程中重新发起接入请求。
在一些实施例中，所述方法还包括：
响应于所述第一接入控制参数，在接入层AS将禁止接入所述第一业务应用场景的通知消息传输至非接入层NAS；
在所述NAS根据所述通知消息停止所述第一业务应用场景的呼叫。
UE与网络端之间的通信链路包括接入层与非接入层的协议栈，实现UE与网络端之间的信令传输。接入层在UE与网络端之间建立了信令传输的通路，非接入层则可基于接入层进行信令传输。
因此，在本公开实施例中，UE根据第一业务应用场景的第一接入控制参数确定第一业务应用场景的接入请求被禁止时，可通知非接入层禁止接入。这时，非接入层根据禁止接入的通知消息，可以停止发起第一业务应用场景的接入请求，并在进一步接收到允许接入的通知消息、禁止接入被解除的通知消息，或者禁止接入的定时时长结束后，再重新发 起接入请求。
在一些实施例中，所述方法还包括：
在所述AS将禁止接入所述第一业务应用场景的禁止时长信息传输至所述NAS；其中，所述禁止时长用于，在所述禁止时长后，在所述NAS重新发起所述第一业务应用场景的呼叫。
在本公开实施例中，接入层还可根据上述实施例中的禁止定时器的参数，向非接入层通知禁止时长，便于非接入层在禁止时长结束后，重新发起接入请求。
在本公开实施例中，可根据上述方法对网络中新增加的第一业务应用场景，通过接入控制参数，实现更加精细的接入控制。
在本公开实施例中，可将目前未使用的预留接入类别作为第一业务应用场景对应的接入类别，还可增加目前未定义的接入类别作为第一业务应用场景对应的接入类别。基站可根据第一业务应用场景对应的接入类别对相应的接入请求实施接入控制。
在本公开实施例中，可将目前未使用的预留接入标识作为第一业务应用场景对应的接入标识，还可增加目前未定义的接入标识作为第一业务应用场景对应的接入标识。基站可根据第一业务应用场景对应的接入类别以和/或接入标识对相应的接入请求实施接入控制。
在本公开实施例中，第一业务应用场景的呼叫建立原因包括如下几种：
第一、呼叫建立原因为“AI业务相关”；
第二、呼叫建立原因为“AI本地训练”；
第三、呼叫建立原因为“AI云端训练”；
第四、呼叫建立原因为“AI云端及UE本地的共同训练”。
在本公开实施例中，第一业务应用场景的业务类型的禁止接入，不会因用户设备接收到终端业务(MT业务)，即被叫业务或者紧急呼叫业务等 而解除。即禁止定时器，如T390定时器会继续运行。
例如，第一业务应用场景的业务类型的禁止接入，不会因收到RRC连接建立消息以及RRC连接恢复消息而停止，即T390定时器继续运行。
在本公开实施例中，第一业务应用场景的业务类型的禁止接入，是否能够因用户设备接收到终端业务(MT业务)，即被叫业务或者紧急呼叫业务等而解除，可根据网络配置或者协议来约定。并且，网络端可通过专用或公共信令通知用户设备被配置的信息。
在本公开实施例中，如果用户设备经过接入控制的检测，确定当前不允许接入，则可由接入层通知非接入层，当前的用户设备对于AI/ML模型的接入请求为禁止状态。进一步地，还可通知非接入层禁止接入的时长，即通知高层底层被阻塞的时长，以便高层在合适的时间再次发起接入请求。
如图7所示，本公开实施例还提供一种接入控制装置700，包括：
下发模块701，配置为根据第一业务应用场景，下发第一接入控制参数，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在一些实施例中，所述装置还包括：
第一确定模块，配置为响应于存在所述第一业务应用场景，确定所述第一业务应用场景的第一接入标识；其中，所述第一接入控制参数，还包含：与所述第一接入类别对应的所述第一接入标识。
在一些实施例中，所述第一业务应用场景包括以下至少之一：
以AI业务为呼叫建立原因的业务应用场景；
以AI模型在终端本地训练业务为呼叫建立原因的业务应用场景；
以AI模型在云端训练业务为呼叫建立原因的业务应用场景；
以AI模型在本地和云端共同训练业务为呼叫建立原因的业务应用场景。
在一些实施例中，所述第一接入控制参数，还包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在一些实施例中，所述装置还包括：
配置模块，配置为根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器。
在一些实施例中，所述配置模块，配置为：
响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
在一些实施例中，不同所述业务类型的资源消耗属性不同；
其中，所述资源消耗属性包含以下至少之一：
指示计算资源消耗的属性；
指示存储资源消耗的属性；
指示网络资源消耗的属性。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
在一些实施例中，所述配置模块，包括：
第一配置子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接建立消息时继续所述禁止定时器的定时；
和/或，
第二配置子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC 连接恢复消息时继续所述禁止定时器的定时。
在一些实施例中，所述配置模块，配置为：
响应于所述第一业务应用场景的业务类型，通过专用信令或公共信令或通信协议配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
如图8所示，本公开实施例还提供一种接入控制装置800，包括：
接收模块801，配置为接收第一接入控制参数，其中，所述第一接入控制参数，用于对在在第一业务应用场景的接入控制，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
在一些实施例中，所述第一接入控制参数，还包括：在所述第一业务应用场景与所述第一接入类别对应的所述第一接入标识。
在一些实施例中，所述第一接入控制参数，还包括：禁止定时器的参数；
其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
在一些实施例中，所述装置还包括：
启动模块，配置为响应于所述禁止定时器的参数，启动所述禁止定时器。
在一些实施例中，所述装置还包括：
第二确定模块，配置为在检测到解除触发事件时，确定停止或继续所述禁止定时器的定时。
在一些实施例中，所述解除触发事件包括以下至少之一：
被叫事件；
紧急呼叫事件。
在一些实施例中，所述第二确定模块，包括：
第一定时子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接建立消息时，根据所述配置信息继续所述禁止定时器的定时；
和/或，
第二定时子模块，配置为响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接恢复消息时，根据所述配置信息继续所述禁止定时器的定时。
在一些实施例中，所述装置还包括：
传输模块，配置为响应于所述第一接入控制参数，在接入层AS将禁止接入所述第一业务应用场景的通知消息传输至非接入层NAS；
停止模块，配置为在所述NAS根据所述通知消息停止所述第一业务应用场景的呼叫。
在一些实施例中，所述装置还包括：
发起模块，配置为在所述AS将禁止接入所述第一业务应用场景的禁止时长信息传输至所述NAS；其中，所述禁止时长用于，在所述禁止时长后，在所述NAS重新发起所述第一业务应用场景的呼叫。
本公开实施例提供一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够有处理器运行的可执行程序，其中，处理器运行可执行程序时执行前述任意技术方案提供的接入控制方法。
该通信设备可为前述的基站或者UE。
其中，处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在通信设备掉电之后能够继续记忆存储其上的信息。这里，所述通信设备包括基站或用户设备。
所述处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序。
本公开实施例提供一种非临时性计算机可读存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现本公开实施例中所涉及的任意技术方案所示的方法。
图9是根据一示例性实施例示出的一种通信设备900的框图。例如，通信设备900可以是移动电话、计算机、数字广播终端、消息收发设备、游戏控制台、平板设备、医疗设备、健身设备、个人数字助理等。
参照图9，通信设备900可以包括以下一个或多个组件：处理组件901，存储器902，电源组件903，多媒体组件904，音频组件905，输入/输出(I/O)接口906，传感器组件907，以及通信组件908。
处理组件901通常控制通信设备900的整体操作，诸如与显示、电话呼叫、数据通信、相机操作和记录操作相关联的操作。处理组件901可以包括一个或多个处理器910来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件901还可以包括一个或多个模块，便于处理组件901和其他组件之间的交互。例如，处理组件901可以包括多媒体模块，以方便多媒体组件904和处理组件901之间的交互。
存储器910被配置为存储各种类型的数据以支持在通信设备900的操作。这些数据的示例包括用于在通信设备900上操作的任何应用程序或方法的指令、联系人数据、电话簿数据、消息、图片、视频等。存储器902可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)、电可擦除可编程只读存储器(EEPROM)、可擦除可编程只读存储器(EPROM)、可编程只读存储器(PROM)、只读存储器(ROM)、磁存储器、快闪存储器、磁盘或光盘。
电源组件903为通信设备900的各种组件提供电力。电源组件903可以包括：电源管理系统，一个或多个电源，及其他与为通信设备900生成、管理和分配电力相关联的组件。
多媒体组件904包括在所述通信设备900和用户之间提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件904包括一个前置摄像头和/或后置摄像头。当通信设备900处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和/或后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件905被配置为输出和/或输入音频信号。例如，音频组件905包括一个麦克风(MIC)，当通信设备900处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器910或经由通信组件908发送。在一些实施例中，音频组件905还包括一个扬声器，用于输出音频信号。
I/O接口906为处理组件901和外围接口模块之间提供接口，上述外围接口模块可以是键盘、点击轮、按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件907包括一个或多个传感器，用于为通信设备900提供各个方面的状态评估。例如，传感器组件907可以检测到通信设备900的打开/关闭状态、组件的相对定位，例如所述组件为通信设备900的显示器和小键盘，传感器组件907还可以检测通信设备900或通信设备900的一个组件的位置改变，用户与通信设备900接触的存在或不存在，通信设备900方位或加速/减速和通信设备900的温度变化。传感器组件907可以包括接近传感器，被配置为在没有任何的物理接触时检测附近物体的存在。传感 器组件907还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件907还可以包括加速度传感器、陀螺仪传感器、磁传感器、压力传感器或温度传感器。
通信组件908被配置为便于通信设备900和其他设备之间有线或无线方式的通信。通信设备900可以接入基于通信标准的无线网络，如WiFi、2G或3G，或它们的组合。在一个示例性实施例中，通信组件908经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件908还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术、红外数据协会(IrDA)技术、超宽带(UWB)技术、蓝牙(BT)技术或其他技术来实现。
在示例性实施例中，通信设备900可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器902，上述指令可由通信设备900的处理器910执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图10所示，本公开一实施例示出另一种通信设备的结构。该通信设备可为本公开实施例所涉及的基站。例如，通信设备1000可以被提供为一网络设备。参照图12，通信设备1000包括处理组件1022，其进一步包括至少一个处理器，以及由存储器1032所代表的存储器资源，用于存储可由处理组件1022的执行的指令，例如应用程序。存储器1032中存储的应用 程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件1022被配置为执行指令，以执行上述方法前述应用在所述通信设备的任意方法。
通信设备1000还可以包括一个电源组件1026被配置为执行通信设备1000的电源管理，一个有线或无线网络接口1050被配置为将通信设备1000连接到网络，和一个输入输出(I/O)接口1058。通信设备1000可以操作基于存储在存储器1032的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (23)

  1. 一种接入控制方法，其中，包括：
    根据第一业务应用场景，下发第一接入控制参数，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    响应于存在所述第一业务应用场景，确定所述第一业务应用场景的第一接入标识；其中，所述第一接入控制参数，还包含：与所述第一接入类别对应的所述第一接入标识。
  3. 根据权利要求2所述的方法，其中，所述第一业务应用场景包括以下至少之一：
    以人工智能AI业务为呼叫建立原因的业务应用场景；
    以AI模型在终端本地训练业务为呼叫建立原因的业务应用场景；
    以AI模型在云端训练业务为呼叫建立原因的业务应用场景；
    以AI模型在本地和云端共同训练业务为呼叫建立原因的业务应用场景。
  4. 根据权利要求1至3任一项所述的方法，其中，所述第一接入控制参数，还包括：禁止定时器的参数；
    其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
  5. 根据权利要求4所述的方法，其中，所述方法还包括：
    根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器。
  6. 根据权利要求5所述的方法，其中，所述根据所述第一业务应用场景的业务类型，为所述第一业务应用场景配置禁止定时器，包括：
    响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
  7. 根据权利要求6所述的方法，其中，不同所述业务类型的资源消耗属性不同；
    其中，所述资源消耗属性包含以下至少之一：
    指示计算资源消耗的属性；
    指示存储资源消耗的属性；
    指示网络资源消耗的属性。
  8. 根据权利要求6或7所述的方法，其中，所述解除触发事件包括以下至少之一：
    被叫事件；
    紧急呼叫事件。
  9. 根据权利要求8所述的方法，其中，所述响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时，包括：
    响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接建立消息时继续所述禁止定时器的定时；
    和/或，
    响应于所述第一业务应用场景的业务类型为AI关联的业务类型，配置在接收到与所述解除触发事件对应的RRC连接恢复消息时继续所述禁止定时器的定时。
  10. 根据权利要求6所述的方法，其中，所述响应于所述第一业务应用场景的业务类型，配置在检测到解除触发事件时是否停止所述禁止定时器的定时，包括：
    响应于所述第一业务应用场景的业务类型，通过专用信令或公共信令或通信协议配置在检测到解除触发事件时是否停止所述禁止定时器的定时。
  11. 一种接入控制方法，其中，包括：
    接收第一接入控制参数，其中，所述第一接入控制参数，用于对在在第一业务应用场景的接入控制，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
  12. 根据权利要求11所述的方法，其中，所述第一接入控制参数，还包括：在所述第一业务应用场景与所述第一接入类别对应的所述第一接入标识。
  13. 根据权利要求11或12所述的方法，其中，所述第一接入控制参数，还包括：禁止定时器的参数；
    其中，所述禁止定时器，用于禁止以所述第一业务应用场景的业务始发的接入。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：
    响应于所述禁止定时器的参数，启动所述禁止定时器。
  15. 根据权利要求14所述的方法，其中，所述方法还包括：
    根据所述参数，确定在检测到解除触发时间时停止或继续所述禁止定时器的定时。
  16. 根据权利要求15所述的方法，其中，所述解除触发事件包括以下至少之一：
    被叫事件；
    紧急呼叫事件。
  17. 根据权利要求15所述的方法，其中，所述根据所述参数，确定在检测到解除触发时间时停止或继续所述禁止定时器的定时，包括：
    响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接建立消息时，根据所述参数继续所述禁止定时器的定时；
    和/或，
    响应于所述第一业务应用场景的业务类型为AI关联的业务类型，在接收到与所述解除触发事件对应的RRC连接恢复消息时，根据所述参数继续所述禁止定时器的定时。
  18. 根据权利要求11至17任一所述的方法，其中，所述方法还包括：
    响应于所述第一接入控制参数，在接入层AS将禁止接入所述第一业务应用场景的通知消息传输至非接入层NAS；
    在所述NAS根据所述通知消息停止所述第一业务应用场景的呼叫。
  19. 根据权利要求18所述的方法，其中，所述方法还包括：
    在所述AS将禁止接入所述第一业务应用场景的禁止时长信息传输至所述NAS；其中，所述禁止时长用于，在所述禁止时长后，在所述NAS重新发起所述第一业务应用场景的呼叫。
  20. 一种接入控制装置，其中，包括：
    下发模块，配置为根据第一业务应用场景，下发第一接入控制参数，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
  21. 一种接入控制装置，其中，包括：
    接收模块，配置为接收第一接入控制参数，其中，所述第一接入控制参数，用于对在在第一业务应用场景的接入控制，其中，所述第一接入控制参数包括所述第一业务应用场景的第一接入类别。
  22. 一种通信设备，其中，所述通信设备至少包括：处理器和用于存 储能够在所述处理器上运行的可执行指令的存储器，其中：
    处理器用于运行所述可执行指令时，所述可执行指令执行上述权利要求1至10或11至19任一项提供的接入控制方法中的步骤。
  23. 一种非临时性计算机可读存储介质，其中，所述计算机可读存储介质中存储有计算机可执行指令，该计算机可执行指令被处理器执行时实现上述权利要求1至10或11至19任一项提供的接入控制方法中的步骤。
PCT/CN2020/099027 2020-06-29 2020-06-29 接入控制方法及装置、存储介质 WO2022000203A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/099027 WO2022000203A1 (zh) 2020-06-29 2020-06-29 接入控制方法及装置、存储介质
CN202080001391.2A CN114208292B (zh) 2020-06-29 2020-06-29 接入控制方法及装置、存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/099027 WO2022000203A1 (zh) 2020-06-29 2020-06-29 接入控制方法及装置、存储介质

Publications (1)

Publication Number Publication Date
WO2022000203A1 true WO2022000203A1 (zh) 2022-01-06

Family

ID=79315070

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/099027 WO2022000203A1 (zh) 2020-06-29 2020-06-29 接入控制方法及装置、存储介质

Country Status (2)

Country Link
CN (1) CN114208292B (zh)
WO (1) WO2022000203A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117692892A (zh) * 2022-08-29 2024-03-12 华为技术有限公司 一种无线通信方法及通信装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102761933A (zh) * 2011-04-29 2012-10-31 中兴通讯股份有限公司 Eab处理方法及装置、接入处理方法、装置及系统
WO2014176863A1 (zh) * 2013-05-03 2014-11-06 华为技术有限公司 接入控制方法及装置
US20190045577A1 (en) * 2017-08-03 2019-02-07 Samsung Electronics Co., Ltd. Method and apparatus for controlling access in next generation mobile communication system
CN109451838A (zh) * 2018-04-27 2019-03-08 北京小米移动软件有限公司 获取接入控制参数的方法、装置及存储介质
CN110035474A (zh) * 2018-01-11 2019-07-19 惠州Tcl移动通信有限公司 接入控制方法、用户设备、基站及具有存储功能的装置
WO2020032702A1 (en) * 2018-08-09 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for configuring network connection in mobile communication system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103379659B (zh) * 2012-04-17 2016-08-03 电信科学技术研究院 一种多优先级场景下接入请求实现方法及装置
CN110351872B (zh) * 2018-04-02 2024-04-30 夏普株式会社 接入控制方法及用户设备
US11096232B2 (en) * 2018-09-07 2021-08-17 Apple Inc. Enhancements to connection rejection procedures
CN111278111B (zh) * 2018-12-05 2023-04-28 中国移动通信集团浙江有限公司 一种基于业务场景的网络资源差异化调度方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102761933A (zh) * 2011-04-29 2012-10-31 中兴通讯股份有限公司 Eab处理方法及装置、接入处理方法、装置及系统
WO2014176863A1 (zh) * 2013-05-03 2014-11-06 华为技术有限公司 接入控制方法及装置
US20190045577A1 (en) * 2017-08-03 2019-02-07 Samsung Electronics Co., Ltd. Method and apparatus for controlling access in next generation mobile communication system
CN110035474A (zh) * 2018-01-11 2019-07-19 惠州Tcl移动通信有限公司 接入控制方法、用户设备、基站及具有存储功能的装置
CN109451838A (zh) * 2018-04-27 2019-03-08 北京小米移动软件有限公司 获取接入控制参数的方法、装置及存储介质
WO2020032702A1 (en) * 2018-08-09 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for configuring network connection in mobile communication system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT: "Access control for MTC", 3GPP DRAFT; R2-105388, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Xi'an; 20101011, 3 October 2010 (2010-10-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050452420 *
QUALCOMM CDMA TECHNOLOGIES: "Addition of NR5G UAC TC 11.3.8", 3GPP DRAFT; R5-202670, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG5, no. Electronic Meeting; 20200518 - 20200529, 2 June 2020 (2020-06-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051892605 *
SPREADTRUM COMMUNICATIONS: "Barring information signalling for 5G unified access control", 3GPP DRAFT; R2-1804476_UAC_BARRING_CHECK_INFO_SIGNALLING_REVISION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sanya, China; 20180416 - 20180420, 14 April 2018 (2018-04-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051428212 *

Also Published As

Publication number Publication date
CN114208292B (zh) 2024-01-30
CN114208292A (zh) 2022-03-18

Similar Documents

Publication Publication Date Title
WO2022120544A1 (zh) 通信方法及装置、无线接入网、终端及存储介质
WO2022016474A1 (zh) 接入控制方法及装置、存储介质
WO2021217571A1 (zh) 终端状态切换处理、控制方法及装置、通信设备及介质
CN110495196B (zh) 能力参数处理方法及装置、通信设备及存储介质
WO2022077372A1 (zh) 接入控制信息处理方法及装置、通信设备及存储介质
WO2022047799A1 (zh) 接入控制方法及装置、及通信设备及存储介质
WO2022000203A1 (zh) 接入控制方法及装置、存储介质
WO2022016471A1 (zh) 定时器的控制方法、装置、通信设备及存储介质
WO2022077232A1 (zh) 无线通信方法及装置、通信设备及存储介质
WO2022205362A1 (zh) 寻呼处理方法及装置、通信设备及存储介质
WO2022032581A1 (zh) 上行传输的发送、接收方法及装置、通信设备及介质
WO2022032693A1 (zh) 接入控制方法及装置、通信设备和存储介质
WO2023245448A1 (zh) 一种信息传输方法、装置、通信设备及存储介质
WO2023245457A1 (zh) 一种信息传输方法、装置、通信设备及存储介质
WO2022041016A1 (zh) 寻呼消息的处理方法及装置、通信设备和存储介质
WO2022000514A1 (zh) 接入控制的方法、装置、通信设备及存储介质
WO2022077400A1 (zh) 业务参与确定的方法及装置、网元设备、用户设备及存储介质
WO2023283809A1 (zh) 接入控制处理方法、装置、通信设备及存储介质
WO2022213330A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2024113189A1 (zh) 小数据传输sdt方法、装置、通信设备及存储介质
WO2024000518A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2022077401A1 (zh) 业务参与确定的方法及装置、网元设备、用户设备及存储介质
WO2024020755A1 (zh) 无线通信方法、装置、通信设备及存储介质
WO2023010348A1 (zh) 寻呼方法、装置、通信设备及存储介质
WO2022032541A1 (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: 20942518

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20942518

Country of ref document: EP

Kind code of ref document: A1