WO2019029568A1 - 通信方法、终端设备和网络设备 - Google Patents

通信方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2019029568A1
WO2019029568A1 PCT/CN2018/099388 CN2018099388W WO2019029568A1 WO 2019029568 A1 WO2019029568 A1 WO 2019029568A1 CN 2018099388 W CN2018099388 W CN 2018099388W WO 2019029568 A1 WO2019029568 A1 WO 2019029568A1
Authority
WO
WIPO (PCT)
Prior art keywords
access
terminal device
classification identifier
qos parameter
access control
Prior art date
Application number
PCT/CN2018/099388
Other languages
English (en)
French (fr)
Inventor
韩锋
毕皓
谭巍
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019029568A1 publication Critical patent/WO2019029568A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • 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 present application relates to the field of wireless communications, and in particular, to a communication method, a terminal device, and a network device.
  • 5G defines a framework based on quality of service flow (QoS flow), which will support QoS flow that guarantees flow rate and QoS flow that does not guarantee flow rate.
  • QoS flow the base station establishes one or more Data Radio Bearers (DRBs) for each UE's PDU session, and the base station maps data packets belonging to different PDU sessions to different DRBs.
  • DRBs Data Radio Bearers
  • QoS flow is the minimum granularity at which a PDU session implements QoS differentiation.
  • the application provides a communication method, and the network device can perform unified access control on the terminal device to improve network performance, in response to a request for accessing the network triggered by the user plane of the terminal device.
  • the first aspect provides a method for controlling an access network, where the method includes: determining, by the terminal device, a first access classification identifier corresponding to the data packet according to a QoS parameter corresponding to the data packet; and determining, by the terminal device, the first access The classification identifier determines an access control parameter, wherein the access control parameter is used by the terminal device to determine whether the network can be accessed.
  • the method further includes: the terminal device receiving access control information from the network device, the access control information including at least one QoS parameter and at least one access a classification identifier, the at least one QoS parameter and the at least one access classification identifier have a corresponding relationship; and the terminal device determines, according to the QoS parameter corresponding to the data packet, the first access classification identifier corresponding to the data packet, including: the terminal The device determines the first access classification identifier according to the access control information and the QoS parameter corresponding to the data packet.
  • the network device may perform control of the access network on the terminal device based on the access classification identifier (Category ID).
  • Unified access control of terminal devices can be implemented under the framework of 5G QoS flow.
  • the at least one QoS parameter and the at least one access classification identifier have a corresponding relationship, including one-to-one correspondence or many-to-one.
  • each QoS parameter uniquely corresponds to an access classification identifier.
  • each access QoS parameter can uniquely identify an access classification identifier.
  • one QoS parameter may correspond to two or more access classification identifiers.
  • the terminal device may combine the QoS parameters corresponding to the data packet.
  • an access classification identifier is determined from the multiple or multiple access classification identifiers.
  • the method further includes: when the terminal device determines that the at least one QoS parameter does not include the QoS parameter corresponding to the data packet, the terminal device uses the default access classification identifier. As the access classification identifier corresponding to the data packet.
  • the terminal device receives the access control information from the network device, including: the terminal device receives the access control information sent by the core network device; or the terminal device receives the Access control information sent by the access network device.
  • the terminal device is in a connected state or an inactive state.
  • the method further includes: receiving, by the terminal device, information of a timer of the at least one QoS parameter sent by the network device; the terminal device in the at least one QoS When the timer of the first QoS parameter in the parameter times out, determining whether the network can access the network based on the access classification identifier corresponding to the first QoS parameter.
  • the terminal device is in a connected state or an inactive state.
  • An embodiment of the present application provides a method for performing access control based on a Category ID for a terminal device in an RRC-Connected state and an RRC-inactive state defined by a 5G system, so that the network device pair is in an RRC-Connected state and an RRC-inactive
  • the terminal device can also perform an access control procedure triggered by the user plane. It can achieve smaller granular access control for the system and improve network performance. For example, you can improve congestion control and management of your network.
  • the access control mechanism based on the control plane triggering for the idle state UE is defined in the 5G system, and is not described in detail herein.
  • the terminal device determines, according to the QoS parameter corresponding to the data packet, the first access classification identifier corresponding to the data packet, which is a non-access NAS layer of the terminal device. implemented.
  • the determining, by the terminal device, the access control parameter according to the first access classification identifier is performed by an access layer of the terminal device.
  • the access layer includes a Service Data Adaptation Protocol (SDAP) layer.
  • SDAP Service Data Adaptation Protocol
  • the access layer includes a radio resource control RRC layer.
  • the QoS parameters include a quality of service flow identification QFI and a 5G QoS indicator.
  • a second aspect provides a method for controlling an access network, the method comprising: receiving, by an access network device, at least one QoS parameter and at least one access classification identifier sent by a core network device, the at least one QoS parameter and At least one access classification identifier has a corresponding relationship; the access network device sends the access control information to the terminal device, where the access control information includes an access control parameter corresponding to each access classification identifier of the at least one access classification identifier. To perform access control on the terminal device.
  • the method further includes: the access network device sends the information of the timer of the at least one QoS parameter to the terminal device, where the timer of each QoS parameter is used by the terminal The device performs access control for the access classification identifier corresponding to the QoS parameter.
  • the third aspect provides a method for controlling an access network, where the core network device sends access control information to the access network device, where the access control information includes at least one QoS parameter and at least one access classification identifier, where The at least one QoS parameter and the at least one access classification identifier have a corresponding relationship; the core network device sends the access control information to the terminal device.
  • the QoS parameters include a quality of service flow identification QFI and a 5G QoS indicator.
  • a communication method includes: determining, by a terminal device, a first access classification identifier corresponding to the data packet according to a mapping identifier corresponding to the data packet; and determining, by the terminal device, access control according to the first access classification identifier a parameter, wherein the access control parameter is used by the terminal device to determine whether the network can be accessed.
  • the method further includes: the terminal device receiving the access control information from the access network device, where the access control information includes at least one mapping identifier and at least one access classification And the identifier, wherein the at least one mapping identifier and the at least one access classification identifier have a corresponding relationship; and the terminal device determines, according to the mapping identifier corresponding to the data packet, the first access classification identifier corresponding to the data packet, including: the terminal The device determines the first access classification identifier according to the access control information and the mapping identifier corresponding to the data packet.
  • the method further includes: when the terminal device determines that the at least one mapping identifier does not include the mapping identifier corresponding to the data packet, the terminal device uses the default access classification identifier as The access classification identifier corresponding to the data packet.
  • the mapping identity comprises a data radio bearer identity DRB ID and/or a logical channel identity.
  • the fifth aspect provides a communication method, where the method includes: the access network device sends, to the terminal device, at least one mapping identifier and at least one access classification identifier, where the at least one mapping identifier and the at least one access classification identifier have corresponding
  • the access network device sends an access control parameter corresponding to each access classification identifier of the at least one access classification identifier to the terminal device to perform access control on the terminal device.
  • a terminal device having the function of implementing the terminal device in the method design of the above first aspect or the fourth aspect.
  • These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a network device having the function of implementing the terminal device in the method design of the second aspect or the fifth aspect.
  • These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a network device having the function of implementing the terminal device in the method design of the above third aspect.
  • These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a terminal device including a transceiver, a processor, and a memory.
  • the processor is for controlling a transceiver transceiver signal for storing a computer program for calling and running the computer program from the memory such that the terminal device performs the method of the first aspect or the fourth aspect above.
  • a network device including a transceiver, a processor, and a memory.
  • the processor is for controlling transceiver transceiver signals for storing a computer program for calling and running the computer program from the memory such that the network device performs the method of the second aspect or the fifth aspect.
  • a network device including a transceiver, a processor, and a memory.
  • the processor is for controlling transceiver transceiver signals for storing a computer program for calling and running the computer program from memory such that the network device performs the method of the third aspect.
  • a communication device may be a terminal device in the above method design, or a chip disposed in the terminal device.
  • the communication device includes a memory for storing computer executable program code, a communication interface, and a processor coupled to the memory and the communication interface.
  • the program code stored in the memory includes instructions which, when executed by the processor, cause the communication device to perform the method performed by the terminal device in any of the possible aspects of the first aspect or the fourth aspect described above.
  • a communication device in a thirteenth aspect, may be a network device in the above method design, or a chip disposed in the network device.
  • the communication device includes a memory for storing computer executable program code, a communication interface, and a processor coupled to the memory and the communication interface.
  • the program code stored in the memory includes instructions which, when executed by the processor, cause the communication device to perform the method performed by the network device in any of the possible aspects of the second aspect or the fifth aspect above.
  • a communication device may be a network device in the above method design, or a chip disposed in the network device.
  • the communication device includes a memory for storing computer executable program code, a communication interface, and a processor coupled to the memory and the communication interface.
  • the program code stored in the memory includes instructions which, when executed by the processor, cause the communication device to perform the method performed by the network device in any of the possible designs of the third aspect above.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to perform the first to fifth aspects and any of the above The method in the possible implementation.
  • a computer readable medium storing program code for causing a computer to perform the first to fifth aspects described above and when the computer program code is run on a computer
  • the method in any possible implementation.
  • a chip comprising a processor and a memory, the memory being for storing a computer program, the processor for calling and running the computer program from the memory, the computer program for implementing the first aspect to the first Five aspects and methods in any of the possible implementations.
  • the terminal device may determine, according to the access classification table identifier, whether the network can be accessed according to the signaling of the user plane.
  • the network device can perform unified access control on the terminal device to improve network performance, in response to a request for accessing the network triggered by the user plane of the terminal device.
  • Figure 1 shows the QoS flow architecture at 5G.
  • FIG. 2 is a schematic flowchart of a communication method 100 according to an embodiment of the present application.
  • FIG. 3 is an example of a method for controlling access to a network according to an embodiment of the present application.
  • FIG. 4 is another example of a communication method of an embodiment of the present application.
  • FIG. 5 is an interaction diagram between protocol layers in which the UE performs access control.
  • FIG. 6 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a network device 600 according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a network device 700 according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a terminal device 800 according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network device 900 according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network device 1000 according to an embodiment of the present application.
  • 5G will support various types of network deployments and application types, including:
  • 5G defines a framework based on quality of service flow (QoS flow) that will support QoS flows that guarantee flow rates and QoS flows that do not guarantee flow rates.
  • QoS flow quality of service flow
  • Figure 1 shows the QoS flow architecture at 5G.
  • the base station establishes one or more DRBs for each PDU session of the UE.
  • the base station maps packets belonging to different PDU sessions to different DRBs.
  • QoS flow is the minimum granularity of QoS differentiation in a PDU session.
  • a QFI is used to indicate a QoS flow.
  • a service with QFI within a PDU session will receive the same scheduling policy, admission control, and the like.
  • the QFI will be carried on the encapsulation header.
  • the NG-RAN in Fig. 1 represents a next generation radio network controller.
  • the packet processing mechanism on the air interface is defined based on DRB under 5G.
  • a packet served by a DRB has the same packet processing mechanism on the air interface.
  • the base station can establish multiple DRBs to meet QoS flows with different packet processing requirements.
  • the base station maps the downlink packets belonging to the QoS flow to the DRB based on the QFI identifier on the NG-U (ie, the N3 interface) and the corresponding QoS profile.
  • the UE maps the uplink data packets belonging to the QoS flow to the DRB according to the QoS flow to DRB mapping or reflection mapping configured by the base station.
  • NR unified
  • the NR defines an access category table in which multiple categories are recorded, each with a unique Category ID. For each Category ID, there is a corresponding service type, signaling type, and slice information. Application layer ID, etc.
  • Table 1 is an example of an access classification table.
  • the S-NSSAI in Table 1 represents Single Network Slice Selection Assistance Information (S-NSSAI). Each PDU session can only belong to one network slice.
  • the symbol * in Table 1 indicates that it is not required.
  • * indicates that it can be any access level, that is, the access level is not required.
  • Application ID indicates that the application identifier can be arbitrarily applied.
  • * indicates that the call type can be unrestricted.
  • an idle state (RRC-Idle) UE defined in 5G accesses the network based on the above unified access mechanism. Specifically, when the idle state UE has an access network request, the NAS layer of the UE determines, according to the access classification table, the Category ID to which the access network request belongs, and sends the Category ID to the RRC layer of the UE. The RRC layer of the UE performs a corresponding access procedure according to the access control parameter corresponding to the Category ID broadcast by the base station.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE-A advanced long term evolution
  • UMTS universal mobile telecommunication system
  • LTE continuously evolved systems 4.5G or next generation communication systems (eg, fifth-generation (5G) systems), and the like.
  • 5G system can also be called a new generation new air (NR) system.
  • NR new generation new air
  • the access network device in the embodiment of the present application may be a base transceiver station (BTS) in Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA), or may be a wideband code division multiple access (WCDMA).
  • the base station (NodeB, NB) in the ) may also be an evolved base station (evolutional node B, eNB or eNodeB) in Long Term Evolution (LTE), or a relay station, an access point or a remote radio unit (RRU) ), or an in-vehicle device or a wearable device, or a wireless controller in a cloud radio access network (CRAN) scenario, and a network-side device in a future 5G system, such as a transmission point (transmission point, TP), transmission reception point (TRP), base station (gNodeB, gNB), small base station equipment, and the like.
  • TP transmission point
  • TRP transmission reception point
  • gNodeB, gNB small base station equipment, and the
  • the terminal device in the embodiment of the present application may also be referred to as a user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, Terminal, wireless communication device, user agent or user device.
  • UE User Equipment
  • the terminal device may be a station (station, ST) in a wireless local area network (WLAN), and may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, or a wireless local loop (wireless local Loop, WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and next-generation communication system Terminal equipment, etc.
  • WLAN wireless local area network
  • PDA personal digital assistant
  • the access network device and the terminal device can communicate via wireless communication technology.
  • the core network device is generally connected to the access network device through various interfaces, and performs mobility management and policy control on the terminal device.
  • FIG. 2 is a schematic flowchart of a communication method 100 according to an embodiment of the present application.
  • the method can be performed by a terminal device.
  • the terminal device may be a terminal device in a connected state or a terminal device in an inactive state.
  • the terminal device determines, according to the QoS parameter corresponding to the data packet, a first access classification identifier corresponding to the data packet.
  • the QoS parameters include QFI and/or 5QI.
  • a QFI is used to uniquely identify a QoS flow in a PDU session.
  • the core network notifies the terminal device of multiple QoS rules through the NAS message.
  • Each QoS rule includes a QoS rule ID, a QoS flow ID, and the like. According to the QoS rule, the terminal can know which QoS flow ID (ie, QFI) to map each uplink packet to be sent.
  • the QoS parameter corresponding to the data packet can also be said as the QoS parameter of the data packet mapping.
  • QFI or 5QI for packet mapping.
  • the QFI or the 5QI has a corresponding relationship with the access classification identifier. Therefore, the terminal device determines the data according to the QFI of the data packet mapping (hereinafter referred to as the first QFI) and the correspondence between the QFI and the access classification identifier.
  • the access classification identifier corresponding to the packet. 5QI is similar.
  • the method before determining, by the terminal device, the first access classification identifier corresponding to the data packet according to the QoS parameter corresponding to the data packet, the method further includes:
  • the terminal device receives the access control information sent by the network device, where the access control information includes at least one QoS parameter and at least one access classification identifier, where the at least one QoS parameter corresponds to the at least one access classification identifier.
  • the at least one QoS parameter corresponds to at least one access classification identifier, including one-to-one correspondence or many-to-one.
  • each QoS parameter uniquely corresponds to an access classification identifier.
  • each access QoS parameter can uniquely identify an access classification identifier.
  • one QoS parameter may correspond to two or more access classification identifiers.
  • the terminal device may combine the QoS parameters corresponding to the data packet. For other information, an access classification identifier is determined from the multiple or multiple access classification identifiers.
  • the network side may configure one or some QoS parameters to correspond to the default access classification identifier.
  • the network configures one or more default access classification identifiers. If the QoS parameter corresponding to a data packet cannot find the corresponding access classification identifier, the terminal device can directly access the default access classification identifier. control.
  • the network device can set the default access classification identifier in two ways. One way is to explicitly specify that a Category ID is the default access classification identifier. One way is implicit, that is, if all the elements corresponding to a Category ID are not required, the Category ID is the default access classification identifier.
  • Table 2 below gives an example of the implicit setting method.
  • the other elements of the row in Table 2 of Category ID 4 in Table 2 are “*”, that is, none of these elements are required.
  • Category ID 4 is an implicitly set default access. Classification identifier.
  • step 110 performing access control based on the access classification identifier (ie, Category ID) is triggered based on the terminal device having data to transmit.
  • the embodiments of the present application are not limited thereto.
  • the terminal device can also perform access control based on the Category ID.
  • the access control may be performed by the RRC layer or the SDAP layer of the terminal device, and the result of the access control is notified to the upper layer of the terminal device.
  • the network device sends the access control information to the terminal device, and the purpose is to send the at least one QoS parameter and the at least one access classification identifier and the corresponding relationship to the terminal device. Therefore, the specific form in which the network device sends the at least one QoS parameter and the at least one access classification identifier to the terminal device is not limited.
  • the network device may send the access control information to the terminal device, where the access control information carries the correspondence between the at least one QoS parameter and the at least one access classification identifier and the two.
  • the network device may also send an access classification table to the terminal device, where the access classification table includes the at least one QoS parameter and the at least one access classification identifier, and the at least one QoS parameter and the at least one The access classification identifiers have a corresponding relationship.
  • the following describes the process of performing access control on the terminal device by using the network device to send the at least one QoS parameter and the at least one access classification identifier with the corresponding relationship to the terminal device as an example.
  • step 110 when the terminal device determines the access classification identifier corresponding to the data packet according to the QoS parameter of the data packet, it may be determined based on the access classification table.
  • the access classification table records at least one QoS parameter and at least one access classification identifier, and the at least one QoS parameter and the at least one access classification identifier are in one-to-one correspondence.
  • the terminal device can find the access classification identifier corresponding to the QoS parameter of the data packet mapping by looking up the access classification table, that is, the first access classification identifier.
  • the QoS parameter recorded in the access classification table is QFI
  • the at least one QFI is supported by the terminal device. If the network side knows which QFIs a terminal device can support, the network side generally sends the QFI supported by the terminal device to the terminal device.
  • the access classification table may be sent by the network device to the terminal device.
  • the network device may send an access classification table to the terminal device when the terminal device has a request for accessing the network.
  • the network device may also send periodically or when the access classification table has modifications.
  • the terminal device may receive the access classification table sent by the network device every time the network is requested to be accessed, or may receive the information periodically, or the terminal device stores after receiving an access classification table. And in the network device notification access classification form has been modified to receive again.
  • the network device can configure a default access classification identifier for each QoS parameter or part of the QoS parameters. Therefore, if the terminal device does not find the access classification identifier corresponding to a certain QoS parameter in the access classification table, the terminal device may select the default access classification identifier configured on the network side.
  • At least one QoS parameter in the access classification table configured by the network device has a one-to-one correspondence with at least one access classification identifier (Category ID).
  • Category ID there may be a one-to-many or many-to-one correspondence between the QoS parameters in the access classification table and the Category ID.
  • the terminal device can determine a Category ID by combining other information in the access classification table.
  • the other information in the access classification table mentioned here includes type information of the terminal, slice information, application layer ID, communication type, and the like.
  • the QFI corresponding to one packet can also uniquely determine a Category ID.
  • the access classification table is sent by the network device to the terminal device.
  • the network device that sends the access classification table to the terminal device includes two cases.
  • the core network device sends an access classification table to the terminal device, where the access classification table is generated by the core network device.
  • the access classification table comes from the core network device.
  • the core network device After the core network device generates the access classification table, it is forwarded by the access network device and sent to the terminal device.
  • the table 2 herein is only an example of an access classification table that is sent to the terminal device as a core network device, which is not limited in this embodiment of the present application.
  • the access classification table may also include more or less information than the above information and the like.
  • the access classification table includes at least QFI.
  • the one-to-one corresponding to the access classification identifier may also be 5QI.
  • the 5QI identifies the 5G QoS indicator.
  • the 5QI may also indicate QoS parameters related to the QoS flow, such as priority, packet loss rate, packet delay, and the like.
  • the access classification table generated by the core network may include the QFI, and record the one-to-one correspondence between the QFI and the Category ID, so that the terminal device can find the corresponding Category ID according to a QFI.
  • the access classification table includes 5QI, and records a one-to-one correspondence between the 5QI and the Category ID.
  • the terminal device can determine the Category ID according to the 5QI.
  • the access classification table may also include both QFI and 5QI.
  • the access network device sends an access classification table to the terminal device, wherein the access classification table is generated by the access network device.
  • the access network device generates an access classification table and sends it to the terminal device. This process does not require the core network device to participate. Moreover, the access classification table generated by the access network device may be different from the access table generated by the core network device.
  • the access classification table generated by the access network device can be seen in Table 3 or Table 4.
  • the access classification identifier (ie, the Category ID) may be associated with the DRB ID or the Logical channel ID.
  • the terminal device may also determine the Category ID corresponding to the DRB ID or the Logical channel ID according to the DRB ID or the Logical channel ID of the data packet mapping.
  • the access classification table generated by the access network device can also be as shown in Table 4. That is, the access network device can establish a correspondence between the Category ID and the QFI/5QI.
  • the access classification table generated by the access network device may be different from the access classification table generated by the core network device.
  • the access classification table generated by the core network device may include more QoS parameters, such as the slice information, Application ID, and the like shown in Table 2.
  • the terminal device can uniquely determine a Category ID before the data transmission, and the Category ID is also the first access classification identifier mentioned above.
  • the terminal device determines an access control parameter corresponding to the first access classification identifier.
  • the access control parameter is used by the terminal device to determine whether the network can be accessed.
  • the access network device After the access network device sends the access classification table to the terminal device, a set of access control parameters corresponding to each Category ID is generated according to the core network or its own load status or other factors. Then, the access network device sends at least one set of access control parameters corresponding to the Category IDs to the terminal device.
  • the access network device may send the at least one set of access control parameters to the terminal device by using broadcast signaling or proprietary signaling.
  • the terminal device acquires a set of access control parameters corresponding to the first access classification identifier from the multiple access control parameters sent by the access network device.
  • the access control parameters may include a barring factor and a barring time.
  • the terminal device determines whether it can access the network according to the access control parameter.
  • the terminal device generates a random number between 0 and 1 according to the barring factor. If the random number is lower than the barring factor, it indicates that the network side permits the terminal device to access the network. Otherwise, access to the network is not permitted.
  • the terminal device can generate a random waiting time (referred to as T barring ) according to the following formula:
  • the terminal device After the random waiting time has elapsed, the terminal device regenerates the random number and attempts to access the network in the same way.
  • the terminal device may perform access based on the category ID.
  • FIG. 3 is an example of a method for controlling an access network according to an embodiment of the present application.
  • the embodiment of the present application does not limit the core network device in FIG. 3 .
  • it may be an access and mobility management function (AMF), a session management function (SMF), or the like.
  • AMF is responsible for mobility management, registration management, and connection management.
  • SMF is responsible for session management, IP address allocation, user plane function selection and control.
  • the core network device sends the access control information #1 to the UE by using NAS signaling.
  • the UE receives the access control information #1 sent by the core network device.
  • the access control information #1 may be an access classification table or other forms.
  • a plurality of event types such as an application ID, a service type, a Category ID, a QFI, and/or a 5QI, are defined in the access classification table. If the access classification table includes QFI, the Category ID has a correspondence with QFI. If the access classification table includes 5QI, the access classification table has a correspondence with the 5QI. As described above, the correspondence here may be one-to-one correspondence, one-to-many or many-to-one.
  • the NAS signaling may be delivered to the UE during a registration area update or an initial registration area.
  • the core network device sends the access control information #2 to the base station.
  • the base station receives the access control information #2 sent by the core network device.
  • control information #1 in step 201 and the access control information #2 in step 202 may be identical or different.
  • access control information #1 and the access control information #2 at least include the at least one QoS parameter and the at least one access classification identifier and their corresponding relationships.
  • the QoS parameter may be a QFI, a 5QI, a DRB ID, or a logical channel ID.
  • the access control information #1 and the access control information #2 as an example for accessing the classification table, and the following flow is explained.
  • the access classification table sent by the core network device to the base station may be carried in an initial context setup request or a PDU session establishment request or a PDU session establishment modification.
  • step 201 There is no order between step 201 and step 202.
  • the core network device sends the access classification table to the terminal device and the base station.
  • the specific form of sending is not limited.
  • the NAS layer of the UE provides the triggered access classification identifier to the user plane of the UE.
  • the access layer includes a user plane and an RRC layer. Therefore, the access layer of the UE is shown in FIG.
  • the NAS layer of the UE notifies the access layer of the UE to the triggered UE ID.
  • the access layer may be an SDAP layer or an RRC layer.
  • the RRC layer may perform an attempt to access the network according to the access control parameter corresponding to the triggered Category ID. or,
  • the SDAP layer performs an attempt to access the network based on the access control parameter corresponding to the triggered category ID notified by the RRC layer.
  • Step 203 can have multiple implementations.
  • the NAS layer may first determine the triggered Directory ID, and then provide the triggered Directory ID to the user plane of the UE.
  • the NAS layer of the UE directly sends the access classification table to the user plane of the UE.
  • the user layer of the UE's NAS layer providing the determined category ID to the UE may be as follows.
  • the NAS layer determines the triggered category ID and directly provides the determined category ID to the user plane of the UE.
  • the NAS layer provides the determined category ID to the RRC layer, and then the RRC layer forwards the category ID to the user plane of the UE.
  • the NAS layer of the UE sends the received access classification table to the user plane of the UE.
  • the user plane of the UE determines the triggered category ID.
  • the NAS layer of the UE sends the received access classification table to the RRC layer of the UE, and the RRC layer transparently transmits the access classification table to the user plane of the UE.
  • the user plane of the UE determines the triggered access classification identifier.
  • the user plane of the UE receives the access control parameter corresponding to all the category IDs of the base station, and determines the access control parameter corresponding to the triggered category ID.
  • the user plane of the UE receives the access control parameters corresponding to all the category IDs sent by the base station, determines the access control parameters corresponding to the triggered category ID, and performs access control based on the access control parameters.
  • the user plane of the UE performs access control based on an access control parameter corresponding to the triggered category ID.
  • the user of the UE returns the acceptance result to the NAS layer of the UE.
  • the embodiment may correspond to the foregoing case 1, that is, the core network device generates the access control information that carries the access classification table, and sends the access classification table to the terminal device through the access control information.
  • Network access equipment
  • FIG. 4 is another example of a communication method of an embodiment of the present application.
  • the base station defines an access classification table (or, also referred to as a Category list) for the air interface.
  • Each Category ID in the Category list corresponds to a data radio bearer (DRB) or a logical channel.
  • the access classification table generated by the base station includes a Category ID, a DRB ID, or a logical channel ID, and the Category ID has a correspondence relationship with the DRB ID or the logical channel ID.
  • the base station sends an access classification table to the UE.
  • the UE receives an access classification table sent by the base station.
  • the correspondence between the DRB ID and the Category ID and/or the correspondence between the logical channel ID and the Category ID are recorded in the access classification table.
  • the base station may send an access classification table to the UE by using RRC signaling.
  • the RRC signaling may be carried in the RRC reconnection configuration message.
  • the base station broadcasts access control parameters corresponding to all Category IDs.
  • the access control parameters corresponding to all the Category IDs broadcast by the base station may be determined according to the system load condition or the load condition of the own.
  • the above steps 301 and 302 may be a MAC layer or a PDCP layer directly sent by the base station to the UE. Alternatively, it may be forwarded by the RRC layer of the UE.
  • the UE determines an access control parameter corresponding to triggering the access network Category ID.
  • the UE When the UE has an initial transmission of data mapped to the DRB ID or the logical channel ID, the UE performs the correspondence between the DRB ID and the Category ID received in step 301, or the correspondence between the logical channel ID and the Category ID. Determine the Category ID corresponding to the DRB ID or logical channel ID of the packet mapping, that is, the Category ID that triggers the access network. Further, the UE determines an access control parameter corresponding to the Category ID that triggers the access network.
  • the UE performs access control based on the access control parameter.
  • step 304 if the data packet is mapped on the logical channel ID, access control is performed by the MAC layer of the UE. If the data packet is mapped on the DRB ID, access is performed by the PDCP layer or the MAC layer of the UE.
  • the corresponding steps in the foregoing steps 301-304 may be specifically performed by the MAC layer or the PDCP layer of the UE.
  • the PDCP layer or the MAC layer of the UE Taking the packet mapping on the DRB ID as an example, the PDCP layer or the MAC layer of the UE generates a random number between 0 and 1 according to the access control parameters broadcasted by the received base station. If the random number is lower than the barring factor in the access control parameter, the access to the network is permitted, otherwise the network is not accurately accessed. The UE waits for a random time and re-attempts the access without granting access to the network.
  • the method of calculating the random waiting time can be referred to the formula (1) above, and details are not described herein again.
  • This embodiment may correspond to the foregoing case 2, that is, an access classification table is generated by the access network device and sent to the terminal device. Moreover, the access network device also needs to send, to the terminal device, an access control parameter corresponding to each category ID in the access classification table. The terminal device can determine whether the network can be accessed according to the access control parameter corresponding to the category ID triggered by the terminal device.
  • the UE performs access control based on the Category ID for an initially transmitted data packet.
  • access control may also be performed based on the Category ID for subsequent data packets.
  • the base station can be implemented by defining a timer for each or part of the QoS flow, DRB or logical channel.
  • QoS flow describes QoS flow as an example.
  • the base station defines a timer for each QoS flow, and notifies the UE of the timing information of each QoS flow.
  • the access control is performed based on the Category ID for the subsequent data packet mapped to the QoS flow, thereby accessing the network.
  • the base station may restart the mechanism for controlling the access network based on the Category ID for subsequent data packets of the initial data packet.
  • the UE performs an access control mechanism based on user plane triggering.
  • the UE performing the access control mechanism may also be triggered based on the control plane.
  • the Category ID is provided to the RRC layer of the UE.
  • access control is performed by the RRC layer of the UE.
  • the specific signaling procedure can be seen in Figure 5.
  • FIG. 5 is an interaction diagram between protocol layers in which the UE performs access control.
  • the NAS layer of the UE determines the triggered Directory ID.
  • the NAS layer of the UE determines the Category ID (ie, the triggered Directory ID) of the requesting access network based on the access classification table.
  • the Category ID ie, the triggered Directory ID
  • the RRC layer of the UE queries the NAS layer of the UE to request the Category ID of the access network, and the NAS layer provides the determined Category ID to the RRC layer.
  • the UE's NAS sends the Category ID requesting access to the network to the RRC layer of the UE.
  • the RRC layer of the UE performs access control.
  • the RRC triggering signaling request needs to be sent, and the RRC signaling may be carried in the RAN notification area update message.
  • the RRC triggered signaling request is also required to be sent, and the RRC signaling may be carried in an RRC connection reestablishment message, a measurement report, or a proximity indication message.
  • the triggered Category ID is different from the name of the Category ID of the request access network, but is actually the same concept. That is, the access classification identifier corresponding to the data packet mentioned in the foregoing method 100, or the Category ID corresponding to the data packet.
  • the RRC layer of the UE may send an access failure message to the NAS layer in case of multiple attempts but fails to access.
  • the network side may configure a maximum access number N for the UE in advance. Once the network has not been successfully accessed for more than N times, the UE may send an access failure message to the network side, where N ⁇ 1 and is an integer. Subsequently, the network side may reconfigure the access control parameter corresponding to the Category ID triggered by the UE, so that the terminal device may have an opportunity to access the network.
  • the access control triggered by the RRC may also perform system admission based on the access mechanism of the Category ID.
  • the communication method of the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 5.
  • the terminal device and the network device according to the embodiment of the present application are described below with reference to FIG. 6 to FIG.
  • FIG. 6 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application.
  • the terminal device 500 includes a processing unit 510, configured to:
  • the access control parameter is determined according to the first access classification identifier, and the access control parameter is used by the terminal device to determine whether the network can be accessed.
  • the units in the terminal device 500 of the embodiment of the present application and the other operations or functions described above are respectively implemented in order to implement the corresponding processes performed by the terminal device in the foregoing embodiments. For the sake of brevity, it will not be repeated here.
  • FIG. 7 is a schematic block diagram of a network device 600 according to an embodiment of the present application. As shown in FIG. 4, the network device 600 includes:
  • the receiving unit 610 is configured to receive at least one QoS parameter and at least one access classification identifier sent by the core network device, where the at least one QoS parameter and the at least one access classification identifier are in one-to-one correspondence;
  • the sending unit 620 is configured to send, to the terminal device, an access control parameter corresponding to each of the at least one QoS parameter, to perform access control on the terminal device.
  • the units in the network device 600 of the embodiment of the present application and the other operations or functions described above are respectively implemented in order to implement the corresponding processes performed by the access network device (or base station) in the foregoing embodiments. For the sake of brevity, it will not be repeated here.
  • FIG. 8 is a schematic block diagram of a network device 700 according to an embodiment of the present application.
  • the network device 700 includes a processing unit 710 and a transmitting unit 720.
  • the processing unit 710 is configured to control the sending unit 720 to perform the following steps:
  • the units in the network device 700 of the embodiment of the present application and the other operations or functions described above are respectively implemented in order to implement the corresponding processes performed by the core network device in the foregoing embodiments. For the sake of brevity, it will not be repeated here.
  • FIG. 9 is a schematic structural diagram of a terminal device 800 according to an embodiment of the present application.
  • the terminal device 800 includes one or more processors 801, one or more memories 802, and one or more transceivers 803.
  • the processor 801 is configured to control the transceiver 803 to send and receive signals
  • the memory 802 is configured to store a computer program
  • the processor 801 is configured to call and run the computer program from the memory 802, so that the terminal device performs the communication method implementation of the present application.
  • FIG. 10 is a schematic structural diagram of a network device 900 according to an embodiment of the present application.
  • network device 900 includes one or more processors 901, one or more memories 902, and one or more transceivers 903.
  • the processor 901 is configured to control the transceiver 903 to send and receive signals
  • the memory 902 is configured to store a computer program
  • the processor 901 is configured to call and run the computer program from the memory 902, so that the network device performs the communication method implementation of the present application.
  • the corresponding processes and/or operations performed by the access network device in the example For the sake of brevity, it will not be repeated here.
  • FIG. 11 is a schematic structural diagram of a network device 1000 according to an embodiment of the present application.
  • network device 1000 includes one or more processors 1001, one or more memories 1002, and one or more transceivers 1003.
  • the processor 1001 is configured to control the transceiver 1003 to send and receive signals
  • the memory 1002 is configured to store a computer program
  • the processor 1001 is configured to call and run the computer program from the memory 1002, so that the network device performs the communication method implementation of the present application.
  • the corresponding processes and/or operations performed by the core network device in the example For the sake of brevity, it will not be repeated here.
  • the processor may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the program of the present application.
  • the processor can include a digital signal processor device, a microprocessor device, an analog to digital converter, a digital to analog converter, and the like.
  • the processor can distribute the control and signal processing functions of the mobile device among the devices according to their respective functions.
  • the processor can include functionality to operate one or more software programs, which can be stored in memory.
  • the functions of the processor may be implemented by hardware or by software executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the memory can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of information and instructions that can be stored. Dynamic storage device. It can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage (including a compact disc, a laser disc, a compact disc, a digital versatile disc, a Blu-ray disc, etc.), a disk storage medium or other magnetic storage device, or any other device that can be used to carry or store desired program code in the form of an instruction or data structure and accessible by a computer. Medium, but not limited to this.
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • disc storage including a compact disc, a laser disc, a compact disc, a digital versatile disc, a Blu-ray disc, etc.
  • the foregoing memory and the memory may be physically independent units, or the memory may be integrated with the processor.
  • the application further provides a communication system, including the foregoing terminal device, access network device, and core network device.
  • the application also provides a computer program product comprising computer program code for causing a computer to perform operations and/or processes performed by a terminal device in an embodiment of the method described above when the computer program code is run on a computer .
  • the application also provides a computer program product comprising computer program code, when the computer program code is run on a computer, causing the computer to perform the operations performed by the access network device in the above method embodiment and/ Or process.
  • the application also provides a computer program product comprising computer program code, when the computer program code is run on a computer, causing the computer to perform the operations performed by the core network device in the method embodiment described above and/or Process.
  • the application further provides a computer readable medium storing program code, when the computer program code is run on a computer, causing the computer to perform the operations performed by the terminal device in the above method embodiment and/ Or process.
  • the application further provides a computer readable medium storing program code, when the computer program code is run on a computer, causing the computer to perform operations performed by the access network device in the above method embodiment And / or process.
  • the present application also provides a computer readable medium storing program code, when the computer program code is run on a computer, causing the computer to perform operations performed by the core network device in the above method embodiment and / or process.
  • the present application also provides a chip, including a processor and a memory, the memory for storing a computer program, the processor for calling and running the computer program from the memory to perform execution by the terminal device in the above method embodiment Operation and / or process.
  • the present application also provides a chip, including a processor and a memory, the memory for storing a computer program, the processor for calling and running the computer program from the memory to perform the method of the above method by the access network device The actions and/or processes performed.
  • the present application also provides a chip, including a processor and a memory, the memory for storing a computer program, the processor for calling and running the computer program from the memory to perform execution by the core network device in the above method embodiment Operation and / or process.
  • the systems, devices, and methods disclosed in the embodiments provided herein may also be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请提供了控制接入网络的方法，能够对终端设备执行统一接入控制，提升网络性能。该方法包括：终端设备根据数据包对应的QoS参数，确定与数据包对应的第一接入分类标识；终端设备根据第一接入分类标识确定接入控制参数，其中，接入控制参数用于终端设备确定是否能够接入网络。

Description

通信方法、终端设备和网络设备
本申请要求于2017年8月11日提交中国专利局、申请号为201710687717.1、申请名称为“通信方法、终端设备和网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，更具体地，涉及一种通信方法、终端设备和网络设备。
背景技术
随着对下一代通信系统的研究不断深入，业界对于5G系统的具体特点达成了基本共识。例如，更高速率体验和更大带宽的接入能力、更低时延和更高可可靠性的信息交互、更大规模、更低成本的机器类型通信(machine type communication，MTC)设备的接入和管理等。
为了满足上述需求，5G定义了基于服务质量流(quality of service flow，QoS flow)的框架，其将支持保障流速率的QoS flow和不保障流速率的QoS flow。在QoS flow框架下，基站为每个UE的PDU会话建立一个或多个数据无线承载(Data Radio Bearer，DRB)，基站将属于不同PDU会话的数据包映射到不同的DRB中。QoS flow是PDU会话实现QoS区分的最小粒度。
因此，在QoS flow的框架下，网络侧如何对终端设备执行统一接入控制，以满足5G系统的上述需求，成为一个亟待解决的问题。
发明内容
本申请提供一种通信方法，网络设备可以针对终端设备的用户面触发的接入网络的请求，对终端设备执行统一接入控制，提升网络性能。
第一方面，提供了一种控制接入网络的方法，该方法包括：终端设备根据数据包对应的QoS参数，确定与该数据包对应的第一接入分类标识；终端设备根据第一接入分类标识确定接入控制参数，其中，所述接入控制参数用于终端设备确定是否能够接入网络。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：终端设备从网络设备接收接入控制信息，所述接入控制信息包括至少一种QoS参数和至少一种接入分类标识，该至少一种QoS参数和至少一种接入分类标识具有对应关系；以及，终端设备根据数据包对应的QoS参数，确定与该数据包对应的第一接入分类标识，包括：终端设备根据接入控制信息以及该数据包对应的QoS参数，确定第一接入分类标识。
本申请实施例提供的技术方案，网络设备可以基于接入分类标识(Category ID)对终端设备执行接入网络的控制。可以在5G QoS flow的框架下，实现对终端设备的统一接入控制。
这里，该至少一种QoS参数和至少一种接入分类标识具有对应关系，包括一一对应或者多对一的情况下。例如，在一一对应的情况下，每一种QoS参数与一个接入分类标识唯一对应。换句话说，每给定一种QoS参数，就能唯一确定一个接入分类标识。在多对一情况下，一个QoS参数可能对应两个或者多个接入分类标识，此时，终端设备在确定数据包对应的接入分类标识时，可以根据数据包对应的QoS参数，并结合其它信息，从该多个或者多个接入分类标识中确定一个接入分类标识。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：终端设备确定该至少一种QoS参数中不包括该数据包对应的QoS参数时，终端设备将默认接入分类标识作为该数据包对应的接入分类标识。
结合第一方面，在第一方面的某些实现方式中，终端设备从网络设备接收接入控制信息，包括：终端设备接收来自核心网设备发送的接入控制信息；或者终端设备接收来自所述接入网设备发送的接入控制信息。
结合第一方面，在第一方面的某些实现方式中，终端设备处于连接态或非激活态。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：终端设备接收所述网络设备发送的该至少一种QoS参数的定时器的信息；终端设备在该至少一种QoS参数中的第一QoS参数的定时器超时时，基于所述第一QoS参数对应的接入分类标识确定是否能够接入网络。
结合第一方面，在第一方面的某些实现方式中，终端设备处于连接态或非激活态。
本申请实施例，针对5G系统定义的RRC-Connected态和RRC-inactive态的终端设备，提供了一种基于Category ID进行接入控制的方法，使得网络设备对处于RRC-Connected态和RRC-inactive态的终端设备也可以执行由用户面触发的接入控制过程。可以对系统实现更小粒度的接入控制，提升网络性能。例如，可以提升网络的拥塞控制和管理。
需要说明的是，5G系统中定义了针对空闲态UE基于控制面触发的接入控制机制，这里不作详述。
结合第一方面，在第一方面的某些实现方式中，终端设备根据数据包对应的QoS参数，确定与该数据包对应的第一接入分类标识，是由终端设备的非接入NAS层执行的。
结合第一方面，在第一方面的某些实现方式中，终端设备根据第一接入分类标识确定接入控制参数，是由终端设备的接入层执行的。
结合第一方面，在第一方面的某些实现方式中，接入层包括业务数据适应协议SDAP层。
结合第一方面，在第一方面的某些实现方式中，接入层包括无线资源控制RRC层。
结合第一方面，在第一方面的某些实现方式中，所述QoS参数包括服务质量流标识QFI和5G QoS指示器。
第二方面，提供了一种控制接入网络的方法，该方法包括：接入网设备接收核心网设备发送的至少一种QoS参数和至少一种接入分类标识，该至少一种QoS参数和至少一种接入分类标识具有对应关系；接入网设备向终端设备发送接入控制信息，接入控制信息包括该至少一种接入分类标识中每种接入分类标识对应的接入控制参数，以对终端设备进行接入控制。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：接入网设备向终端设 备发送该至少一种QoS参数的定时器的信息，每种QoS参数的定时器用于终端设备针对以该QoS参数对应的接入分类标识的进行接入控制。
第三方面，提供了一种控制接入网络的方法，核心网设备向接入网设备发送接入控制信息，接入控制信息包括至少一种QoS参数和至少一种接入分类标识，其中，该至少一种QoS参数和至少一种接入分类标识具有对应关系；核心网设备向终端设备发送该接入控制信息。
在某些实现方式中，QoS参数包括服务质量流标识QFI和5G QoS指示器。
第四方面，提供一种通信方法，该方法包括：终端设备根据数据包对应的映射标识，确定该数据包对应的第一接入分类标识；终端设备根据第一接入分类标识确定接入控制参数，其中，接入控制参数用于终端设备确定是否能够接入网络。
结合第四方面，在第四方面的某些实现方式中，该方法还包括:终端设备从接入网设备接收接入控制信息，接入控制信息包括至少一个映射标识和至少一种接入分类标识，其中，该至少一个映射标识和至少一种接入分类标识具有对应关系；以及，终端设备根据数据包对应的映射标识，确定与该数据包对应的第一接入分类标识，包括：终端设备根据接入控制信息和该数据包对应的映射标识，确定第一接入分类标识。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：终端设备确定该至少一个映射标识中不包括该数据包对应的映射标识时，终端设备将默认接入分类标识作为该数据包对应的接入分类标识。
结合第四方面，在第四方面的某些实现方式中，映射标识包括数据无线承载标识DRB ID和/或逻辑通道标识。
第五方面，提供一种通信方法，该方法包括：接入网设备向终端设备发送至少一个映射标识和至少一个接入分类标识，该至少一个映射标识和该至少一种接入分类标识具有对应关系；接入网设备向终端设备发送该至少一种接入分类标识中的每种接入分类标识对应的接入控制参数，以对终端设备进行接入控制。
第六方面，提供了一种终端设备，所述终端设备具有实现上述第一方面或第四方面的方法设计中的终端设备的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
第七方面，提供了一种网络设备，所述网络设备具有实现上述第二方面或第五方面的方法设计中的终端设备的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
第八方面，提供了一种网络设备，所述网络设备具有实现上述第三方面的方法设计中的终端设备的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
第九方面，提供了一种终端设备，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该终端设备执行上述第一方面或第四方面中的方法。
第十方面，提供了一种网络设备，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该网络设备执行第二方面或第五方面中的方法。
第十一方面，提供了一种网络设备，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该网络设备执行第三方面中的方法。
第十二方面，提供一种通信装置。该通信装置可以为上述方法设计中的终端设备，或者为设置在终端设备中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；通信接口，以及处理器，处理器与存储器、通信接口耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第一方面或第四方面的任意一种可能的设计中终端设备所执行的方法。
第十三方面，提供一种通信装置。该通信装置可以为上述方法设计中的网络设备，或者为设置在网络设备中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；通信接口，以及处理器，处理器与存储器、通信接口耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第二方面或第五方面的任意一种可能的设计中网络设备所执行的方法。
第十四方面，提供一种通信装置。该通信装置可以为上述方法设计中的网络设备，或者为设置在网络设备中的芯片。该通信装置包括：存储器，用于存储计算机可执行程序代码；通信接口，以及处理器，处理器与存储器、通信接口耦合。其中存储器所存储的程序代码包括指令，当处理器执行所述指令时，使通信装置执行上述第三方面的任意一种可能的设计中网络设备所执行的方法。
第十五方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面至第五方面及其任意可能的实现方式中的方法。
第十六方面，提供了一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面至第五方面及其任意可能的实现方式中的方法。
第十七方面，提供一种芯片，包括处理器和存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，该计算机程序用于实现上述第一方面至第五方面及其任意可能的实现方式中的方法。
在本申请实施例中，终端设备可以基于用户面的信令，根据接入分类表标识确定是否可以接入网络。相对应地，网络设备可以针对终端设备的用户面触发的接入网络的请求，对终端设备执行统一接入控制，提升网络性能。
附图说明
图1是5G下的QoS flow架构。
图2为本申请实施例提供的通信方法100的示意性流程图。
图3是本申请实施例的控制接入网络的方法的一个示例。
图4是本申请实施例的通信方法的另一个示例。
图5是UE执行接入控制的协议层之间的交互图。
图6为本申请实施例提供的终端设备500的示意性框图。
图7为本申请实施例提供的网络设备600的示意性框图。
图8为本申请实施例提供的网络设备700的示意性框图。
图9为本申请实施例提供的终端设备800的示意性结构图。
图10为本申请实施例提供的网络设备900的示意性结构图。
图11为本申请实施例提供的网络设备1000的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
首先，对本申请实施例涉及的相关技术作简单介绍。
随着下一代通信系统研究不断深入，业界对5G研究的具体内容达成了基本共识。5G将支持各种类型的网络部署和应用类型，其中包括：
(1)更高速率体验和更大带宽的接入能力；
(2)更低时延和高可靠性的信息交互；
(3)更大规模、更低成本的MTC设备的接入和管理。
为满足上述需求，5G定义了基于服务质量流(quality of service flow，QoS flow)的框架，其将支持保障流速率的QoS flow和不保障流速率的QoS flow。
参见图1，图1是5G下的QoS flow架构。如图1所示，对于每个UE，基站为该UE的每个PDU会话建立一个或者多个DRB。基站将属于不同PDU会话的数据包映射到不同的DRB中。QoS flow是在PDU会话实现QoS区分的最小粒度。一个QFI用于指示一个QoS flow。在一个PDU会话内具有QFI的业务将会收到相同的调度策略、接纳控制等。在N3接口上(即，核心网与基站之间的接口)，QFI将在封装头上携带。图1中的NG-RAN表示下一代无线网络控制器(next generation radio network controller)。
5G下基于DRB定义了空口上的包处理机制。由一个DRB服务的包在空口上具有相同的包处理机制。基站可建立多个DRBs以满足具有不同包处理需求的QoS flows。
例如，对于下行链路，基站将基于NG-U(即，N3接口)上QFI标识和对应的QoS profile，将属于QoS flow的下行数据包映射到DRB上。对于上行链路，UE根据基站配置的QoS flow到DRB的映射或者反射映射，将属于QoS flow的上行数据包映射到DRB上。
不同于LTE针对不同场景下的接入控制机制，NR下将采用统一(“uniform”)的接入控制机制。在这个控制机制下，NR中定义了一个接入分类(access category)表格，在这个接入分类表格中，记录有多个Category，每个Category具有一个唯一的Category ID。针对每个Category ID，都有对应的业务类型、信令类型、切片信息。应用层ID等。
参见表1，表1是接入分类表格的一个示例。
表1
Figure PCTCN2018099388-appb-000001
Figure PCTCN2018099388-appb-000002
表1中的S-NSSAI表示单个网络切片选择辅助信息(Single Network Slice Selection Assistance Information,S-NSSAI)。其中，每个PDU会话只能归属于一个网络切片。表1中的符号*表示不作要求。例如，表1中“Access class”这一列中，*表示可以为任意的接入等级，即对接入等级不作要求。又例如，表1中的“Application ID”这一列中，*表示可以任意的应用标识。“Call type”这一列中，*表示可以对呼叫类型不作限定。
同时，在5G中定义了空闲态(RRC-Idle)UE基于上述统一接入机制接入网络。具体地，在空闲态UE有接入网络请求时，UE的NAS层根据上述接入分类表格，确定该接入网络请求所属于的Category ID，并将该Category ID发送给UE的RRC层。UE的RRC层，根据基站广播的Category ID所对应的接入控制参数，执行相应的接入流程。
下面对本申请实施例的通信方法进行详细说明。
本申请的技术方案可以应用于各种通信系统，例如：全球移动通信(global system of mobile communication，GSM)系统、码分多址(code division multiple access,CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(LTE)系统、先进的长期演进(LTE-A)系统、通用移动通信系统(universal mobile telecommunication system，UMTS)、LTE持续演进的系统、4.5G或下一代通信系统(例如，第五代通信(fifth-generation，5G)系统)等。其中，5G系统也可以称为新一代新空口技术(new radio,NR)系统。
本申请实施例中所说的接入网设备，可以是全球移动通信(GSM)或码分多址(CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(WCDMA)中的基站(NodeB，NB)，还可以是长期演进(LTE)中的演进型基站(evolutional node B，eNB或eNodeB)，或者中继站、接入点或射频拉远单元(remote radio unit，RRU)，或者车载设备、可穿戴设备，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，以及未来5G系统中的网络侧设备，如传输点(transmission point，TP)、发送接收点(transmission reception point，TRP)、基站(gNodeB，gNB)、小基站设备等。
本申请实施例中的终端设备，也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端(terminal)、无线通信设备、用户代理或用户装置。终端设备可以是无线局域网(wireless local area networks，WLAN)中的站点(station，ST)，可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统中的终端设备等。
接入网设备和终端设备可以通过无线通信技术进行通信。核心网设备一般通过各种接口与接入网设备连接，对终端设备进行移动性管理、策略控制等。
参见图2，图2为本申请实施例的通信方法100的示意性流程图。该方法可以由终端设备执行。其中，该终端设备可以为处于连接态的终端设备，或者处于非激活态的终端设备。
110、终端设备根据数据包对应的QoS参数，确定与该数据包对应的第一接入分类标识。
在本申请实施例中，QoS参数包括QFI和/或5QI。
根据上文对于QoS flow的框架介绍，我们已经知道，一个QFI用于在一个PDU会话中唯一地标识一个QoS flow。并且，终端设备在执行PDU会话建立、PDU会话修改或者业务请求的过程中，核心网会通过NAS消息告诉终端设备多个QoS规则(QoS rules)。每个QoS rule包括QoS rule ID、QoS flow ID等。终端根据QoS规则，可以知道将每一个待发送的上行数据包映射到哪个QoS flow ID(即，QFI)上。
步骤110中所说的，数据包对应的QoS参数，也可以说是这个数据包映射的QoS参数。例如，数据包映射的QFI或5QI。
而QFI或5QI与接入分类标识之间具有对应的关系，因此，终端设备根据数据包映射的QFI(以下记作第一QFI)以及QFI和接入分类标识之间的对应关系，确定该数据包对应的接入分类标识。5QI是类似的。
在本申请实施例中，终端设备根据数据包对应的QoS参数，确定该数据包对应的第一接入分类标识之前，该方法还包括：
终端设备接收到网络设备发送的接入控制信息，接入控制信息包括至少一种QoS参数和至少一种接入分类标识，该至少一种QoS参数和该至少一种接入分类标识对应。
这里，该至少一种QoS参数和至少一种接入分类标识对应，包括一一对应或者多对一的情况下。例如，在一一对应的情况下，每一种QoS参数与一个接入分类标识唯一对应。换句话说，每给定一种QoS参数，就能唯一确定一个接入分类标识。在多对一情况下，一个QoS参数可能对应两个或者多个接入分类标识，此时，终端设备在确定数据包对应的接入分类标识时，可以根据数据包对应的QoS参数，并结合其它信息，从该多个或者多个接入分类标识中确定一个接入分类标识。
可以理解的是，在多个QoS参数对应多个接入分类标识的情况下，也就意味着，这多个QoS参数可以选择同一个接入分类标识进行接入控制。
在一种可能的情况下，网络侧可以配置一个或一些QoS参数与默认接入分类标识相对应。
在另一个情况下，网络配置一个或多个默认接入分类标识，如果一个数据包对应的QoS参数无法找到对应的接入分类标识时，则终端设备可以直接使用默认接入分类标识进行接入控制。
网络设备可以通过两种方式设定默认接入分类标识。一种方式是显式，即明确指定某个Category ID为默认接入分类标识。一种方式是隐式，即，如果一个Category ID对应的所有元素都不作要求时，这个Category ID则是默认接入分类标识。
以下文的表2对隐式的设定方式进行举例说明。例如，表2中的Category ID 4在表2中所在的行的其它元素都为“*”，即对这些元素都不作要求，此时，Category ID 4即为一个隐式设定的默认接入分类标识。
另外，虽然步骤110中，基于接入分类标识(即，Category ID)执行接入控制是基于终端设备有数据需要发送而触发的。但是，本申请实施例并不限制于此。例如，在没有数据包产生的情况下，终端设备也可以基于Category ID执行接入控制。具体地，可以由终 端设备的RRC层或SDAP层执行接入控制，并向终端设备的高层告知接入控制的结果。
应理解，网络设备向终端设备发送接入控制信息，目的在于将该至少一种QoS参数与至少一个接入分类标识及其对应关系发送给终端设备。因此，网络设备向终端设备发送该至少一种QoS参数和至少一种接入分类标识的具体形式可以不作限定。例如，网络设备可以向终端设备发送接入控制信息，在该接入控制信息中携带该至少一种QoS参数和该至少一种接入分类标识及其两者的对应关系。或者，网络设备也可以向终端设备发送一个接入分类表格，该接入分类表格中包括有该至少一种QoS参数和至少一种接入分类标识，并且，该至少一种QoS参数和至少一种接入分类标识是具有对应关系的。
下文以网络设备通过接入分类表格向终端设备下发该具有对应关系的至少一种QoS参数和至少一种接入分类标识作为示例，对终端设备进行接入控制的过程进行说明。
在步骤110中，终端设备在根据数据包的QoS参数确定该数据包对应的接入分类标识时，可以是基于接入分类表格确定的。其中，接入分类表格中记录有至少一种QoS参数和至少一种接入分类标识，该至少一种QoS参数和该至少一种接入分类标识一一对应。
因此，终端设备可以通过查找接入分类表格，找到与数据包映射的QoS参数对应的接入分类标识即为第一接入分类标识。
可以理解的是，如果接入分类表格中记录的QoS参数是QFI，则该至少一个QFI都是终端设备所支持的。网络侧如果知道一个终端设备能够支持哪些QFI，网络侧一般会向终端设备发送该终端设备支持的QFI。
另外，接入分类表格可以是由网络设备发送给终端设备。具体地，网络设备可以在终端设备有接入网络请求的时候，向该终端设备下发接入分类表格。或者，网络设备也可以周期性地发送，或者在接入分类表格有修改时进行发送。相对应地，终端设备可以在每次请求接入网络时去接收网络设备下发的接入分类表格，或者也可以周期性地接收，再或者，终端设备接收到一个接入分类表格后进行存储，并在网络设备通知接入分类表格有修改再次接收。
这里还有一种可能，网络设备可以为每个QoS参数或部分QoS参数配置一个默认的接入分类标识。因此，如果终端设备在接入分类表格中没有找到某个QoS参数对应的接入分类标识的情况下，终端设备可以选择网络侧配置的默认接入分类标识。
通常情况下，网络设备配置的接入分类表格中的至少一个QoS参数与至少一个接入分类标识(Category ID)之间具有一一对应关系。但是，在一些情况下，接入分类表格中的QoS参数与Category ID之间也可能存在一对多或多对一的对应关系。例如，以QoS参数为QFI为例，接入分类表格中的某个QFI对应至少两个Category ID，此时，终端设备可以结合接入分类表格中的其它信息，来确定一个Category ID。这里所说的接入分类表格中的其它信息包括终端的类型信息、切片信息、应用层ID、通信类型等。而对于多个QFI对应一个Category ID的情况，一个数据包对应的QFI也可以唯一地确定一个Category ID。
上面已经提到，接入分类表格是由网络设备发送给终端设备的。而在本申请实施例中，向终端设备发送接入分类表格的网络设备包括两种情况。
情况1
核心网设备向终端设备发送接入分类表格，其中，接入分类表格是由核心网设备生成的。换句话说，接入分类表格来自核心网设备。
核心网设备生成接入分类表格后，经过接入网设备的转发，发送给终端设备。
接入网络设备生成的接入分类表格的具体形式可以参见表2。
表2
Figure PCTCN2018099388-appb-000003
应理解，这里的表2仅是作为核心网设备发送给终端设备的接入分类表格的一个示例，本申请实施例对此不作限定。例如，接入分类表格还可以包括以上信息之外的更多或更少的信息等。但是，接入分类表格中至少包括了QFI。
在本申请实施例中，与接入分类标识一一对应的也可以是5QI。5QI标识5G QoS指示器。5QI除了可以在一个PDU会话中唯一地标识一个QoS flow之外，还可以指示与该QoS flow相关的QoS参数，例如优先级、丢包率、包延时等。换句话说，核心网生成的接入分类表格中可以包括QFI，并且记录QFI与Category ID的一一对应关系，可以保证终端设备根据一个QFI，可以找到对应的Category ID即可。或者，接入分类表格中包括5QI，并且记录5QI与Category ID的一一对应关系。同样地，终端设备根据5QI也可以确定出Category ID即可。或者，接入分类表格中也可以同时包括QFI和5QI。
情况2
接入网设备向终端设备发送接入分类表格，其中，接入分类表格是由接入网设备生成的。
在情况2中，接入网设备生成接入分类表格，并将其发送给终端设备，这个过程是不需要核心网设备参与的。并且，接入网设备生成的接入分类表格可以和核心网设备生成的接入表格有所不同。
例如，接入网设备生成的接入分类表格可以参见表3或表4所示。
表3
Figure PCTCN2018099388-appb-000004
参见表3，接入网设备生成的接入分类表格中，可以将接入分类标识(即，Category ID)与DRB ID或者Logical channel ID建立对应关系。此时，终端设备根据数据包映射的DRB ID或者Logical channel ID，也可以确定这个DRB ID或者Logical channel ID对应的Category ID。
表4
Category ID QoS flow ID/5QI
1  
2  
3  
接入网设备生成的接入分类表格还可以如表4所示。即，接入网设备可以建立Category ID和QFI/5QI的对应关系。
这里需要说明的是，接入网设备生成的接入分类表格与核心网设备生成的接入分类表格可以不同。核心网设备生成的接入分类表格中可以包括更多的QoS参数，例如表2中所示的切片信息、Application ID等。
综上，终端设备在进行数据传输之前，可以唯一地确定一个Category ID，这个Category ID也就是上文所说的第一接入分类标识。
120、终端设备确定与第一接入分类标识对应的接入控制参数。
其中，接入控制参数用于终端设备确定是否可以接入网络。
接入网设备向终端设备下发接入分类表格之后，会根据核心网或者自身的负载状况或者更多的其它因素，生成与每一个Category ID对应的一组接入控制参数。之后，接入网设备将这些Category ID对应的至少一组接入控制参数发送给终端设备。
可选地，接入网设备可以通过广播信令或专有信令向该终端设备发送该至少一组接入控制参数。
终端设备从接入网设备发送的多组接入控制参数中，获取与第一接入分类标识对应的一组接入控制参数。这里，接入控制参数可以包括barring factor和barring Time。
后续，终端设备根据接入控制参数，确定是否能够接入网络。
具体地，终端设备根据barring factor，生成一个0至1之间的随机数。若该随机数低于barring factor，则表明网络侧准许该终端设备接入网络。否则，不准许接入网络。
在不准许终端设备接入网络的情况下，终端设备可以根据下式生成随机等待时间(记作T barring)：
T barring＝(0.7+0.6·rand)·ac-barring time          (1)
终端设备在经过随机等待时间之后，重新生成随机数，采用同样的方法尝试接入网络。
在本申请实施例中，终端设备可以基于category ID进行接入。
下面对本申请实施例提供的通信方法，进行举例说明。
参见图3，图3是本申请实施例的控制接入网络的方法的一个示例。
其中，本申请实施例对于图3中的核心网设备不作限定。例如，可以为接入和移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)等。其中AMF负责移动性管理，注册管理、连接管理等。SMF负责会话管理，IP地址分配，用户面功能选择和控制等。
201、核心网设备通过NAS信令向UE发送接入控制信息#1。UE接收核心网设备发送的接入控制信息#1。
其中，接入控制信息#1可以为一个接入分类表格，或者其它形式。在接入控制信息#1为接入分类表格的情况下，该接入分类表格中定义了多个事件类型，例如，应用ID、业务类型、Category ID、QFI和/或5QI。如果接入分类表格中包括QFI，则Category ID与QFI具有对应关系。如果接入分类表格中包括5QI，则接入分类表格与5QI具有对应关 系。如前文所述，这里的对应关系可以是一一对应、一对多或多对一。
具体地，该NAS信令可以在注册区更新(registration area update)或初始注册区(initial registration area)过程中传递给UE。
202、核心网设备向基站发送接入控制信息#2。基站接收核心网设备发送的接入控制信息#2。
应理解，步骤201中的控制信息#1与步骤202中的接入控制信息#2的内容可以完全相同或不同。但需要注意的是，接入控制信息#1与接入控制信息#2至少都包含了上文所说的至少一种QoS参数与至少一种接入分类标识及其对应关系。其中，QoS参数可以为QFI、5QI、DRB ID或logical channel ID。
为了描述上的方便，我们以接入控制信息#1和接入控制信息#2具体为接入分类表格为例，对下面的流程进行说明。
核心网设备发送给基站的接入分类表格可以承载在初始上下文建立消息(initial context setup request)或者PDU会话建立请求或者PDU会话建立修改中。
步骤201和步骤202之间没有先后顺序。实际上，核心网设备将接入分类表格发送给终端设备和基站。发送的具体形式不作限定。
203、UE的NAS层向UE的用户面提供触发的接入分类标识。
应理解，接入层包括用户面和RRC层。因此，图3中所示为UE的接入层。
可选地，UE的NAS层将触发的Category ID通知给UE的接入层。
这里，该接入层可以为SDAP层或者RRC层。
在接入层为RRC层的情况下，可以由RRC层根据触发的Category ID对应的接入控制参数执行接入网络的尝试。或者，
在接入层为SDAP层的情况下，由SDAP层基于RRC层告知的该触发的category ID对应的接入控制参数执行接入网络的尝试。
步骤203可以有多种实现。例如，NAS层可以先确定触发的Category ID，再将该触发的Category ID提供给UE的用户面。或者，UE的NAS层直接将接入分类表格发送给UE的用户面。
这里，UE的NAS层将确定的category ID提供给UE的用户面可以通过如下方式。
方式1
NAS层确定触发的category ID，并直接将确定的category ID提供给UE的用户面。
方式2
NAS层将确定的category ID提供给RRC层，再由RRC层将category ID转发给UE的用户面。
可选地，UE的NAS层将接收到的接入分类表格发送至UE的用户面。
此种情况下，UE的用户面在接收到接入分类表格之后，自己确定触发的category ID。
可选地，UE的NAS层将接收到的接入分类表格发送至UE的RRC层，由RRC层将接入分类表格透传给UE的用户面。
同样地，这种情况下，UE的用户面接收到接入分类表格之后，自己确定触发的接入分类标识。
204、UE的用户面接收基站发送所有category ID对应的接入控制参数，并确定触发 的category ID对应的接入控制参数。
UE的用户面接收基站发送的所有category ID对应的接入控制参数，确定与触发的category ID对应的接入控制参数，并基于该接入控制参数执行接入控制。
其中，终端设备根据接入控制参数确定是否可以接入网络的过程可参见前文所作的说明，这里不再详述。
205、UE的用户面基于与触发的category ID对应的接入控制参数，执行接入控制。
206、UE的用户面向UE的NAS层返回接纳结果。
接纳结果，也即是否成功接入网络的结果。
可以理解的是，本实施例可以对应上文情况1，即，核心网设备生成携带接入分类表格的接入控制信息，并通过接入控制信息将该接入分类表格发送给终端设备和接入网设备。
参见图4，图4是本申请实施例的通信方法的另一个示例。在该实施例中，基站定义了空口的接入分类表格(或者，也称作Category列表)。Category列表中的每个Category ID对应一个数据无线承载(data radio bearer，DRB)或者逻辑信道(logical channel)。换句话说，基站生成的接入分类表格中包括Category ID、DRB ID或logical channel ID，并且，Category ID与DRB ID或logical channel ID具有对应关系。
301、基站向UE发送接入分类表格。UE接收基站发送的接入分类表格。
其中，接入分类表格中记录有DRB ID和Category ID之间的对应关系，和/或logical channel ID与Category ID之间的对应关系。
其中，基站可以通过RRC信令向UE发送接入分类表格。RRC信令可以携带在RRC重连接配置消息中。
302、基站广播所有Category ID对应的接入控制参数。
在步骤302中，基站广播的所有Category ID对应的接入控制参数，可以是根据系统负载情况、或者自身的负载情况确定的。
上述步骤301和302可以是基站直接发送给UE的MAC层或PDCP层。或者，也可以由UE的RRC层进行转发。
303、UE确定触发接入网络Category ID对应的接入控制参数。
当UE有映射到DRB ID或logical channel ID上的数据的初始传输时，UE根据步骤301中接收到的DRB ID和Category ID之间的对应关系，或者logical channel ID与Category ID之间的对应关系，确定数据包映射的DRB ID或logical channel ID对应的Category ID，也即触发接入网络的Category ID。进一步地，UE确定触发接入网络的Category ID对应的接入控制参数。
304、UE基于接入控制参数执行接入控制。
在步骤304中，若数据包映射在logical channel ID上，则由UE的MAC层执行接入控制。若数据包映射在DRB ID上，则由UE的PDCP层或MAC层执行接入。
图4中，具体可以由UE的MAC层或PDCP层执行上述步骤301-304中的相应步骤。
以数据包映射在DRB ID上为例，UE的PDCP层或MAC层根据接收到的基站广播的接入控制参数，产生0至1之间的随机数。如果随机数低于接入控制参数中的barring factor，则准许接入网络，否则不准确接入网络。在不准许接入网络的情况下，UE等待随机时间 之后重新尝试接入。这里，计算随机等待时间的方法可以参见上文的公式(1)，这里不再赘述。
本实施例可以对应上文情况2，即由接入网设备生成接入分类表格，并发送给终端设备。并且，接入网设备还需要向终端设备发送接入分类表格中的每一种Category ID对应的接入控制参数。终端设备根据自己触发的Category ID对应的接入控制参数，可以确定是否可以接入网络。
在以上的实施例中，UE针对一个初始传输的数据包，基于Category ID执行接入控制。在本申请实施例中，对于后续的数据包也可以基于Category ID执行接入控制。
基站可以通过为每个或部分QoS flow、DRB或logical channel定义一个定时器实现。以下以QoS flow为例进行说明。
(1)基站为每个QoS flow定义一个定时器，并将每个QoS flow的定时信息通知UE。
(2)当终端设备确定某个QoS flow的定时器超时时，对于映射到该QoS flow上的后续的数据包基于Category ID执行接入控制，从而接入网络。
在本实施例中，基站可以对初传数据包的后续数据包，重新启动基于Category ID进行接入网络控制的机制。
在上述实施例中，UE执行接入控制机制是基于用户面触发的。可选地，在本申请实施例中，UE执行接入控制机制还可以是基于控制面触发的。
具体地，UE的NAS层确定了数据包映射在哪个Category ID上之后，将该Category ID提供给UE的RRC层。接下来，由UE的RRC层执行接入控制。具体的信令流程可以参见图5。
图5是UE执行接入控制的协议层之间的交互图。
401、UE的NAS层确定触发的Category ID。
在步骤401中，UE的NAS层基于接入分类表格确定请求接入网络的Category ID(即，触发的Category ID)，具体过程可以参见前述实施例。这里不再详述。
402、UE的RRC层向UE的NAS层询问请求接入网络的Category ID，NAS层将确定的Category ID提供给RRC层。
换句话说，由UE的NAS将请求接入网络的Category ID发送给UE的RRC层。
403、UE的RRC层执行接入控制。
在基于控制面触发的接入控制中，对于非激活态的UE，需要发送RRC触发的信令请求，RRC信令可以携带在RAN通知区域更新(RAN notification area update)消息中。对于连接态的UE，也需要发送RRC触发的信令请求，RRC信令可以在RRC连接重建(RRC connection reestablishment)消息、测量报告(measurement report)或接近指示(proximity indication)消息中携带。
另外，在本申请实施例中，触发的Category ID与请求接入网的Category ID的叫法不同，但实际上是相同的概念。也就是前文方法100中所说的数据包对应的接入分类标识，或者说，数据包对应的Category ID。
以上是对终端设备基于Category ID进行接入控制的流程所作的说明。如果一个UE基于Category ID请求接入网络，在多次尝试而未能接入的情况下，该UE的RRC层可以向NAS层发送接入失败消息。例如，网络侧可以预先为UE配置一个最大接入次数N， 一旦连续超过N次还未能成功接入网络，UE则可以向网络侧发送接入失败消息，N≥1且为整数。后续，网络侧可以对该UE触发的Category ID对应的接入控制参数进行重配置，使得该终端设备可以有机会接入网络。
本实施例中提出，通过增加UE的RRC层与NAS层之间的交互，使得由RRC触发的接入控制，也可以基于Category ID的接入机制执行系统准入。
以上结合图1至图5，对本申请实施例的通信方法作了详细说明。下面结合图6至图11，对本申请实施例涉及的终端设备和网络设备进行说明。
图6为本申请实施例提供的终端设备500的示意性框图。如图3所示，终端设备500包括处理单元510，用于：
根据数据包对应的QoS参数，确定与所述数据包对应的第一接入分类标识；
根据第一接入分类标识确定接入控制参数，接入控制参数用于终端设备确定是否能够接入网络。
本申请实施例的终端设备500中的各单元和上述其它操作或功能分别为了实现上述实施例中由终端设备执行的相应流程。为了简洁，此处不再赘述。
图7为本申请实施例提供的网络设备600的示意性框图。如图4所示，网络设备600包括：
接收单元610，用于接收核心网设备发送的至少一种QoS参数和至少一种接入分类标识，所述至少一种QoS参数和至少一种接入分类标识一一对应；
发送单元620，用于向终端设备发送所述至少一种QoS参数中的每种QoS参数对应的接入控制参数，以对所述终端设备进行接入控制。
本申请实施例的网络设备600中的各单元和上述其它操作或功能分别为了实现上述各实施例中由接入网设备(或，基站)执行的相应流程。为了简洁，此处不再赘述。
图8为本申请实施例提供的网络设备700的示意性框图。如图8所示，网络设备700包括处理单元710和发送单元720。其中，处理单元710用于控制发送单元720执行如下步骤：
向终端设备和接入网设备发送至少一种QoS参数和至少一种接入分类标识，其中，所述至少一种QoS参数和至少一种接入分类标识一一对应。
本申请实施例的网络设备700中的各单元和上述其它操作或功能分别为了实现上述各实施例中由核心网设备执行的相应流程。为了简洁，此处不再赘述。
图9为本申请实施例提供的终端设备800的示意性结构图。如图9所示，终端设备800包括：一个或多个处理器801，一个或多个存储器802，一个或多个收发器803。该处理器801用于控制收发器803收发信号，该存储器802用于存储计算机程序，该处理器801用于从存储器802中调用并运行该计算机程序，使得该终端设备执行本申请的通信方法实施例中由终端设备执行的相应流程和/或操作。为了简洁，此处不再赘述。
图10为本申请实施例提供的网络设备900的示意性结构图。如图9所示，网络设备900包括：一个或多个处理器901，一个或多个存储器902，一个或多个收发器903。该处理器901用于控制收发器903收发信号，该存储器902用于存储计算机程序，该处理器901用于从存储器902中调用并运行该计算机程序，使得该网络设备执行本申请的通信方法实施例中由接入网设备执行的相应流程和/或操作。为了简洁，此处不再赘述。
图11为本申请实施例提供的网络设备1000的示意性结构图。如图11所示，网络设备1000包括：一个或多个处理器1001，一个或多个存储器1002，一个或多个收发器1003。该处理器1001用于控制收发器1003收发信号，该存储器1002用于存储计算机程序，该处理器1001用于从存储器1002中调用并运行该计算机程序，使得该网络设备执行本申请的通信方法实施例中由核心网设备执行的相应流程和/或操作。为了简洁，此处不再赘述。
以上实施例中，处理器可以为中央处理器(central processing unit，CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路等。例如，处理器可以包括数字信号处理器设备、微处理器设备、模数转换器、数模转换器等。处理器可以根据这些设备各自的功能而在这些设备之间分配移动设备的控制和信号处理的功能。此外，处理器可以包括操作一个或多个软件程序的功能，软件程序可以存储在存储器中。
处理器的所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
存储器可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备。也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
可选的，上述的存储器与存储器可以是物理上相互独立的单元，或者，存储器也可以和处理器集成在一起。
本申请还提供一种通信系统，包括上述终端设备、接入网设备和核心网设备。
本申请还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法实施例中由终端设备执行的操作和/或流程。
本申请还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法实施例中由接入网设备执行的操作和/或流程。
本申请还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法实施例中由核心网设备执行的操作和/或流程。
本申请还提供一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法实施例中由终端设备执行的操作和/或流程。
本申请还提供一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法实施例中由接入网设备执行的操作和/或流程。
本申请还提供一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法实施例中由核心网设备执行的操作和/或流程。
本申请还提供一种芯片，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于从存储器中调用并运行该计算机程序，以执行上述方法实施例中由终端设备执行的操作和/或流程。
本申请还提供一种芯片，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于从存储器中调用并运行该计算机程序，以执行上述方法实施例中由接入网设备执行的操作和/或流程。
本申请还提供一种芯片，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于从存储器中调用并运行该计算机程序，以执行上述方法实施例中由核心网设备执行的操作和/或流程。
本领域普通技术人员可以意识到，本申请中公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能。
所属领域的技术人员可以清楚地了解到，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本申请提供的实施例中所揭露的系统、装置和方法，还可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的范围之内。本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种通信的方法，其特征在于，包括：
    终端设备根据数据包对应的QoS参数，确定与所述数据包对应的第一接入分类标识；
    所述终端设备根据所述第一接入分类标识确定接入控制参数，其中，所述接入控制参数用于所述终端设备确定是否能够接入网络。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备从网络设备接收接入控制信息，所述接入控制信息包括至少一种QoS参数和至少一种接入分类标识，所述至少一种QoS参数和至少一种接入分类标识具有对应关系；
    以及，所述终端设备根据数据包对应的QoS参数，确定与所述数据包对应的第一接入分类标识，包括：
    所述终端设备根据所述接入控制信息和所述数据对应的QoS参数，确定所述第一接入分类标识。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    所述终端设备确定所述至少一种QoS参数中不包括所述数据包对应的QoS参数时，所述终端设备将默认接入分类标识作为所述数据包对应的接入分类标识。
  4. 根据权利要求2或3所述的方法，其特征在于，所述终端设备从网络设备接收所述接入控制信息，包括：
    所述终端设备接收来自核心网设备的所述接入控制信息；或者
    所述终端设备接收来自所述接入网设备的所述接入控制信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述终端设备处于连接态或非激活态。
  6. 根据权利要求2至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述网络设备发送的所述至少一种QoS参数的定时器的信息；
    所述终端设备在所述至少一种QoS参数中的第一QoS参数的定时器超时时，基于所述第一QoS参数对应的接入分类标识确定是否能够接入网络。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述终端设备根据数据包对应的QoS参数，确定与所述数据包对应的第一接入分类标识，是由所述终端设备的非接入NAS层执行的。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述终端设备根据所述第一接入分类标识确定接入控制参数后，由所述终端设备的接入层执行接入网络的尝试。
  9. 根据权利要求8所述的方法，其特征在于，所述接入层包括业务数据适应协议SDAP层或无线资源控制RRC层。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述QoS参数包括服务质量流标识QFI和/或5G QoS指示器。
  11. 一种通信的方法，其特征在于，包括:
    接入网设备接收核心网设备发送的至少一种QoS参数和至少一种接入分类标识，所 述至少一种QoS参数和至少一种接入分类标识具有对应关系；
    所述接入网设备向终端设备发送接入控制信息，所述接入控制信息包括所述至少一种接入分类标识中的每种接入分类标识对应的接入控制参数，以对所述终端设备进行接入控制。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述接入网设备向所述终端设备发送所述至少一种QoS参数的定时器的信息，每种QoS参数的定时器用于终端设备针对以所述QoS参数对应的接入分类标识的进行接入控制。
  13. 根据权利要求11或12所述的方法，其特征在于，所述QoS参数包括服务质量流标识QFI和/或5G QoS指示器。
  14. 一种通信的方法，其特征在于，包括:
    核心网设备向接入网设备发送接入控制信息，所述接入控制信息包括至少一种QoS参数和至少一种接入分类标识，其中，所述至少一种QoS参数和至少一种接入分类标识具有对应关系；
    所述核心网设备向终端设备发送所述接入控制信息。
  15. 根据权利要求14所述的方法，其特征在于，所述QoS参数包括服务质量流标识QFI和/或5G QoS指示器。
  16. 一种终端设备，其特征在于，包括：
    处理单元，用于根据数据包对应的QoS参数，确定与所述数据包对应的第一接入分类标识；
    所述处理单元，还用于根据所述第一接入分类标识确定接入控制参数，其中，所述接入控制参数用于所述终端设备确定是否能够接入网络。
  17. 根据权利要求16所述的终端设备，其特征在于，所述终端设备还包括：
    接收单元，用于从网络设备接收接入控制信息，所述接入控制信息包括至少一种QoS参数和至少一种接入分类标识，所述至少一种QoS参数和至少一种接入分类标识具有对应关系；
    以及，所述处理单元具体用于：
    根据所述接入控制信息和所述数据包对应的QoS参数，确定所述第一接入分类标识。
  18. 根据权利要求17所述的终端设备，其特征在于，所述处理单元还用于：
    确定所述至少一种QoS参数中不包括所述数据包对应的QoS参数时，所述终端设备将默认接入分类标识作为所述数据包对应的接入分类标识。
  19. 根据权利要求17或18所述的终端设备，其特征在于，所述接收单元具体用于:
    接收来自核心网设备的所述接入控制信息；或者
    接收来自接入网设备的所述接入控制信息。
  20. 根据权利要求16至19中任一项所述的终端设备，其特征在于，所述终端设备处于连接态或非激活态。
  21. 根据权利要求17至20中任一项所述的终端设备，其特征在于，所述接收单元还用于从所述网络设备接收所述至少一种QoS参数的定时器的信息；
    以及，所述处理单元具体用于在所述至少一种QoS参数中的第一QoS参数的定时器 超时时，基于所述第一QoS参数对应的接入分类标识确定是否能够接入网络。
  22. 根据权利要求16至21中任一项所述的终端设备，其特征在于，所述处理单元用于根据所述数据包对应的QoS参数，确定所述数据包对应的接入分类标识时，所述处理单元具体位于所述终端设备的非接入NAS层。
  23. 根据权利要求16至22中任一项所述的终端设备，其特征在于，所述处理单元用于根据所述数据包的接入分类标识确定接入控制参数后，所述处理单元具体位于所述终端设备的接入层。
  24. 根据权利要求23所述的终端设备，其特征在于，所述接入层包括业务数据适应协议SDAP层或无线资源控制RRC层。
  25. 根据权利要求16至24中任一项所述的终端设备，其特征在于，所述QoS参数包括服务质量流标识QFI和/或5G QoS指示器。
  26. 一种网络设备，其特征在于，包括：
    接收单元，用于从核心网设备接收至少一种QoS参数和至少一种接入分类标识，所述至少一种QoS参数和至少一种接入分类标识具有对应关系；
    发送单元，用于向终端设备发送接入控制信息，所述接入控制信息包括所述至少一种接入分类标识中的每种接入分类标识对应的接入控制参数，以对所述终端设备进行接入控制。
  27. 根据权利要求26所述的网络设备，其特征在于，所述发送单元还用于向所述终端设备发送所述至少一种QoS参数的定时器的信息，每种QoS参数的定时器用于终端设备针对以所述QoS参数对应的接入分类标识的进行接入控制。
  28. 根据权利要求26或27所述的网络设备，其特征在于，所述QoS参数包括服务质量流标识QFI和/或5G QoS指示器。
  29. 一种网络设备，其特征在于，包括：
    发送单元，用于向接入网设备发送接入控制信息，所述接入控制信息包括至少一种QoS参数和至少一种接入分类标识，其中，所述至少一种QoS参数和至少一种接入分类标识具有对应关系；
    所述发送单元还用于向终端设备发送所述接入控制信息。
  30. 根据权利要求29所述的网络设备，其特征在于，所述QoS参数包括服务质量流标识QFI和/或5G QoS指示器。
PCT/CN2018/099388 2017-08-11 2018-08-08 通信方法、终端设备和网络设备 WO2019029568A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710687717.1 2017-08-11
CN201710687717.1A CN109548077A (zh) 2017-08-11 2017-08-11 通信方法、终端设备和网络设备

Publications (1)

Publication Number Publication Date
WO2019029568A1 true WO2019029568A1 (zh) 2019-02-14

Family

ID=65273177

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099388 WO2019029568A1 (zh) 2017-08-11 2018-08-08 通信方法、终端设备和网络设备

Country Status (2)

Country Link
CN (1) CN109548077A (zh)
WO (1) WO2019029568A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113424639B (zh) * 2019-06-27 2023-06-23 Oppo广东移动通信有限公司 一种接入控制方法及装置、终端
CN110351202B (zh) * 2019-07-09 2023-01-20 北京锐安科技有限公司 5g核心网流量分组方法、装置、设备和计算机存储介质
CN115474259A (zh) * 2020-04-09 2022-12-13 中兴通讯股份有限公司 在无线通信中配置接入控制参数
WO2021217654A1 (zh) * 2020-04-30 2021-11-04 Oppo广东移动通信有限公司 网络接入控制方法、装置、设备及存储介质
CN113469829B (zh) * 2021-06-16 2024-04-09 深圳市中金岭南有色金属股份有限公司凡口铅锌矿 视频培训方法、装置、终端设备及介质
CN116614862B (zh) * 2023-07-14 2023-10-20 上海建工七建集团有限公司 一种基于位置区域和收发设备的基站准入控制方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102685710A (zh) * 2011-03-11 2012-09-19 华为技术有限公司 属性信息传递方法和业务发起方法及相关设备和系统
CN102740493A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 终端接入控制调整方法及系统
CN102740397A (zh) * 2011-04-07 2012-10-17 华为技术有限公司 一种多个终端接入的控制方法、控制设备、终端及系统
CN104717693A (zh) * 2013-12-12 2015-06-17 电信科学技术研究院 一种业务接入控制、处理方法及设备
CN106105278A (zh) * 2014-03-14 2016-11-09 高通股份有限公司 基于分组过滤器的接入控制

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207914B (zh) * 2006-12-21 2010-09-22 华为技术有限公司 进行无线资源控制连接的方法、装置及系统
CN101478828B (zh) * 2008-01-04 2011-12-21 电信科学技术研究院 下行调度消息的发送方法、通信系统及基站
US9392462B2 (en) * 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
CN103929826B (zh) * 2014-05-05 2015-11-18 盐城工学院 一种机器类通信终端自适应随机接入方法及系统
WO2017100578A1 (en) * 2015-12-10 2017-06-15 Affirmed Networks, Inc. Data driven automated provisioning of telecommunication applications

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102685710A (zh) * 2011-03-11 2012-09-19 华为技术有限公司 属性信息传递方法和业务发起方法及相关设备和系统
CN102740493A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 终端接入控制调整方法及系统
CN102740397A (zh) * 2011-04-07 2012-10-17 华为技术有限公司 一种多个终端接入的控制方法、控制设备、终端及系统
CN104717693A (zh) * 2013-12-12 2015-06-17 电信科学技术研究院 一种业务接入控制、处理方法及设备
CN106105278A (zh) * 2014-03-14 2016-11-09 高通股份有限公司 基于分组过滤器的接入控制

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"5G Access Control Mechanism", 3GPP TSG RAN WG2 ADHOC MEETING R2-1707046, 29 June 2017 (2017-06-29), XP051301542 *
"Pseudo-CR on Unified Access Control", 3GPP TSG-CT WGI MEETING #104 C1-172601, 19 May 2017 (2017-05-19), XP051270721 *
"Unified Access Control in Different RRC Modes", 3GPP TSG-RAN2 MEETING #98 R2-1705739, 19 May 2017 (2017-05-19), XP051276040 *
"Unified Access Control in Different RRC Modes", 3GPP TSG-RAN2 MEETING NR AD HOC #2 R2-1706890, 29 June 2017 (2017-06-29), XP051301387 *

Also Published As

Publication number Publication date
CN109548077A (zh) 2019-03-29

Similar Documents

Publication Publication Date Title
JP7433488B2 (ja) 無線アクセスネットワーク通知エリア（ｒｎａ）更新の拒否時の構成を処理するための方法および装置
US20200221538A1 (en) Data transmission method, terminal device, and network device
KR102245654B1 (ko) 데이터 통신에서의 경량 ota 시그널링 메카니즘을 위한 시스템, 장치, 및 방법
TWI559790B (zh) 在無線通訊網路中用於壅塞控制的設備及方法
JP2023015354A (ja) 非アクティブ状態におけるデュアルコネクティビティの運用
WO2019029568A1 (zh) 通信方法、终端设备和网络设备
US20200374973A1 (en) Communication Method and Wireless Communications Apparatus
JP7095942B2 (ja) 通信方法、通信装置、及び通信システム
EP4274356A2 (en) Method, terminal device and network device for time advance adjustment
JP2021520742A (ja) 却下時の周期的な無線アクセスネットワーク通知エリア（ｒｎａ）アップデート構成をハンドリングするための方法
US20240023200A1 (en) Communication method and apparatus
US11202338B2 (en) Session establishment method and apparatus
JP2021029055A (ja) 無線端末及び基地局並びにこれらの方法
WO2019242756A1 (zh) 通信方法及装置
WO2021138807A1 (zh) 服务质量QoS参数配置方法及相关装置
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2021057864A1 (zh) 一种消息传输方法和装置
WO2019228185A1 (zh) 一种无线资源控制连接方法及设备、计算机存储介质
US11337112B2 (en) Methods and devices for load balancing across band-width parts
WO2022206007A1 (zh) 中继通信方法及装置、存储介质、中继设备
WO2018028636A1 (zh) Rrc连接控制方法及装置、系统
WO2021259358A1 (zh) 一种部分带宽切换方法及装置
WO2015103780A1 (zh) 一种承载电路语音业务的方法及装置
WO2016149875A1 (zh) 一种载波配置方法及设备
WO2018145292A1 (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: 18844499

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: 18844499

Country of ref document: EP

Kind code of ref document: A1