Access control method and device for RedCap terminal supporting CAG

Abstract

The invention provides an access control method and device for a RedCap terminal supporting CAG, and relates to the field of communication, and the method comprises the steps: when the RedCap terminal starts a UAC process, determining whether the RedCap terminal satisfies a condition in access attempt forbidding information based on a received system information block message, if yes, forbidding the access attempt of the RedCap terminal, and if not, forbidding the access attempt of the RedCap terminal; and if not, allowing the access attempt of the RedCap terminal. Wherein the access attempt forbidding information is information which is configured in advance and is used for the RedCap terminal to determine whether the RedCap terminal can access the cell or not. According to the technical scheme, the access control of the RedCap terminal can be realized in a private network scene.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to an access control method and apparatus for a RedCap terminal supporting CAG. Background Art

[0002] With the continuous deployment and wide application of the 5th Generation Mobile Communication Technology (5G) system, in order to better meet the specific requirements of mid-end Internet of Things applications such as industrial wireless sensors, video surveillance, and wearable devices for device complexity, cost, size, and energy consumption, in the Rel-17 version, the 3rd Generation Partnership Project (3GPP) defined the Reduced Capability (RedCap) device type. For RedCap terminals, explicit or implicit indications in broadcast messages can be used to indicate whether a RedCap terminal can attach to a cell.

[0003] Currently, operators have further proposed the requirement of allowing restricted access for RedCap terminals in a private network scenario (supporting the Closed Access Group (CAG) function) if the system capacity is insufficient. However, there is currently no solution to meet the above requirements. Summary of the Invention

[0004] This application provides an access control method and apparatus for a RedCap terminal supporting CAG to implement access control for RedCap terminals in a private network scenario.

[0005] In a first aspect, an embodiment of this application provides an access control method for a RedCap terminal supporting CAG, including:

[0006] When a RedCap terminal starts the UAC process, determine whether the RedCap terminal meets the conditions in the prohibited access attempt information based on the system information block message received in advance, where the prohibited access attempt information is pre-configured information used by the RedCap terminal to determine whether it can access a cell;

[0007] If the RedCap terminal determines that it meets the conditions in the prohibited access attempt information, prohibit the access attempt of the RedCap terminal.

[0008] In a possible implementation, the method further includes:

[0009] If the RedCap terminal determines that it does not meet the conditions in the prohibited access attempt information, the access attempt of the RedCap terminal is allowed.

[0010] In a possible implementation, the conditions in the prohibited access attempt information include at least one of the following:

[0011] The system information block message contains a UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is a PLMN-identification index corresponding to the NPN identification information list used by the RedCap terminal in the UAC restricted PLMN entry;

[0012] Or,

[0013] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is no PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry, and the system information block message does not contain RedCap exclusive same-frequency reselection indication information;

[0014] Or,

[0015] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is no PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry, and the system information block message contains the RedCap exclusive same-frequency reselection indication information, and the system information block message contains a RedCap indication information related field, and the RedCap terminal meets the requirements for the RedCap terminal in the RedCap indication information related field;

[0016] Or,

[0017] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell does not contain a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal;

[0018] Or,

[0019] The system information block message does not contain the UAC restricted PLMN list cell.

[0020] In a possible implementation, the relevant fields of the RedCap indication information include at least one of the following:

[0021] The RedCap terminal residence field for cell restriction 1Rx, the RedCap terminal residence field for cell restriction 2Rx, the RedCap terminal residence field allowing half-duplex FDD.

[0022] In a possible implementation, if the relevant fields of the RedCap indication information include the RedCap terminal residence field for cell restriction 1Rx, the requirement for the RedCap terminal in the relevant fields of the RedCap indication information is that the number of receive antenna branches is equal to 1;

[0023] If the relevant fields of the RedCap indication information include the RedCap terminal residence field for cell restriction 2Rx, the requirement for the RedCap terminal in the relevant fields of the RedCap indication information is that the number of receive antenna branches is equal to 2;

[0024] If the relevant fields of the RedCap indication information include the RedCap terminal residence field allowing half-duplex FDD, the requirement for the RedCap terminal in the relevant fields of the RedCap indication information is to only support half-duplex FDD operation.

[0025] In a possible implementation, before the RedCap terminal starts the UAC process, the method further includes:

[0026] Receiving the system information block message;

[0027] If the cell access related information cell of the system information block message contains an entry corresponding to the PLMN selected by the RedCap terminal, and the RedCap terminal is allowed or instructed to access the PLMN selected by the RedCap terminal through a cell that has broadcast the CAG ID, it is determined that the RedCap terminal uses the information in the NPN identification information list containing the selected PLMN.

[0028] In a second aspect, an access control device for a RedCap terminal supporting CAG provided by an embodiment of the present application includes:

[0029] A determination module, configured to determine whether the RedCap terminal meets the conditions in the prohibited access attempt information based on the pre-received system information block message when the lightweight RedCap terminal starts the UAC process, where the prohibited access attempt information is pre-configured information for the RedCap terminal to determine whether it can access the cell;

[0030] A prohibition module, configured to prohibit the access attempt of the RedCap terminal if the RedCap terminal determines that it meets the conditions in the prohibited access attempt information.

[0031] In a possible implementation manner, the access control device of the RedCap terminal supporting CAG further includes:

[0032] An allowance module, configured to allow the access attempt of the RedCap terminal if the RedCap terminal determines that it does not meet the conditions in the prohibited access attempt information.

[0033] In a possible implementation manner, the conditions in the prohibited access attempt information include at least one of the following:

[0034] The system information block message contains a UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identification information list, and there is a PLMN-identification index corresponding to the NPN identification information list used by the RedCap terminal in the UAC restricted PLMN entry;

[0035] Or,

[0036] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identification information list, and there is no PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry, and the system information block message does not contain RedCap exclusive same-frequency reselection indication information;

[0037] Or,

[0038] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains the UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identification information list, and there is no PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry, and the system information block message contains the RedCap exclusive same-frequency reselection indication information, and the system information block message contains the RedCap indication information related field, and the RedCap terminal meets the requirements for the RedCap terminal in the RedCap indication information related field;

[0039] Or,

[0040] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell does not contain the UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal;

[0041] Or,

[0042] The system information block message does not contain the UAC restricted PLMN list cell.

[0043] In a possible implementation, the RedCap indication information related field includes at least one of the following:

[0044] The RedCap terminal residence field with cell restriction 1Rx, the RedCap terminal residence field with cell restriction 2Rx, the RedCap terminal residence field allowing half-duplex FDD.

[0045] In a possible implementation, if the RedCap indication information related field includes the RedCap terminal residence field with cell restriction 1Rx, then the requirement for the RedCap terminal in the RedCap indication information related field is that the number of receive antenna branches is equal to 1;

[0046] If the RedCap indication information related field includes the RedCap terminal residence field with cell restriction 2Rx, then the requirement for the RedCap terminal in the RedCap indication information related field is that the number of receive antenna branches is equal to 2;

[0047] If the RedCap indication information related field includes the RedCap terminal residence field allowing half-duplex FDD, then the requirement for the RedCap terminal in the RedCap indication information related field is that it only supports half-duplex FDD operation.

[0048] In a possible implementation, before the RedCap terminal starts the UAC process, the access control device of the RedCap terminal supporting CAG further includes:

[0049] a receiving module, configured to receive the system information block message;

[0050] The determining module is further configured to determine that the RedCap terminal uses the information in the NPN identification information list including the selected PLMN if the cell access related information element of the system information block message includes an entry corresponding to the PLMN selected by the RedCap terminal, and the RedCap terminal is allowed or instructed to access the PLMN selected by the RedCap terminal through a cell broadcasting the CAG ID.

[0051] In a third aspect, an embodiment of the present application provides a RedCap terminal, including: a processor, a memory, and computer program instructions stored on the memory and executable on the processor, where the processor is configured to implement the methods provided by the first aspect and various possible designs when executing the computer program instructions.

[0052] In a fourth aspect, an embodiment of the present application may provide a computer-readable storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are configured to implement the methods provided by the first aspect and various possible designs when executed by a processor.

[0053] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, where the computer program is configured to implement the methods provided by the first aspect and various possible designs when executed by a processor.

[0054] For the access control method and device of the RedCap terminal supporting CAG provided by the embodiments of the present application, in this method, when the RedCap terminal starts the UAC process, it is determined whether the RedCap terminal meets the conditions in the prohibited access attempt information based on the received system information block message. If it meets the conditions, the access attempt of the RedCap terminal is prohibited; if it does not meet the conditions, the access attempt of the RedCap terminal is allowed. Among them, the prohibited access attempt information is pre-configured information used for the RedCap terminal to determine whether it can access a cell. In the embodiments of the present application, by determining whether the RedCap terminal itself meets the conditions in the prohibited access attempt information, the access control of the RedCap terminal is realized in the private network scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The accompanying drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0056] Figure 1 This is a schematic flowchart of the first embodiment of the access control method for a RedCap terminal supporting CAG provided by the embodiments of the present application;

[0057] Figure 2 This is a schematic flowchart of the second embodiment of the access control method for a RedCap terminal supporting CAG provided by the embodiments of the present application;

[0058] Figure 3 This is a schematic structural diagram of the access control device for a RedCap terminal supporting CAG provided by the embodiments of the present application;

[0059] Figure 4 This is a schematic structural diagram of the RedCap terminal provided by the embodiments of the present application.

[0060] Through the above-mentioned drawings, the specific embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Embodiments

[0061] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Apparently, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0062] Before introducing the embodiments of the present application, first, the application background of the embodiments of the present application will be explained:

[0063] The non-public network (NPN) technology proposed by 3GPP in the R16 standard is a 5G private network constructed using 5G technology and independent of the public land mobile network (PLMN) network that serves the public, and is used for enterprise services (such as enterprise production control, etc.).

[0064] The NPN includes two technical solutions: Stand-alone Non-Public Network (SNPN) and Public Network Integrated Non-Public Network (PNI-NPN). Among them, the PNI-NPN technology provides the NPN through a PLMN (for example, through a dedicated Data Network Name (DNN)), or through one or more PLMN network slice instances assigned to the NPN.

[0065] Since network slicing cannot restrict the terminal from attempting to access the network in its unauthorized network slice area, a Closed Access Group (CAG) can be used for access control. The CAG is used in the PNI-NPN network to prevent the UE from accessing the NPN by automatically selecting and accessing the associated cell.

[0066] For traditional UEs, there are two mechanisms that allow the operator to perform cell reselection or access restrictions: one mechanism uses cell state indication and specific reselection to control the cell selection (reselection) process; the second mechanism, Unified Access Control (UAC), allows the operator to prohibit the selected access type or access identifier from sending an initial access message for reasons such as load control.

[0067] However, for RedCap terminals in a private network scenario (supporting the CAG function), there is currently no solution to implement access control for RedCap terminals supporting the CAG function.

[0068] Based on this, the present application provides an access control method for RedCap terminals supporting CAG to implement access control for RedCap terminals supporting the CAG function. By pre-configuring information on prohibited access attempts, when the RedCap terminal starts the UAC process, it can be determined whether the RedCap terminal meets the conditions in the information on prohibited access attempts, so as to prohibit the access attempt of the RedCap terminal when the conditions are met and allow the access attempt of the RedCap terminal when the conditions are not met, thereby implementing access control for RedCap terminals supporting the CAG function.

[0069] Next, the technical solutions of the present application will be described in detail through specific embodiments.

[0070] It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0071] Figure 1This is a schematic flowchart of the first embodiment of the access control method for a RedCap terminal supporting CAG provided by an embodiment of the present application. As Figure 1 shown, the access control method for a RedCap terminal supporting CAG is applied to the RedCap terminal. The access control method for a RedCap terminal supporting CAG may include the following steps:

[0072] S11. When the RedCap terminal starts the UAC process, determine whether the RedCap terminal meets the conditions in the prohibited access attempt information based on the received system information block message.

[0073] In this step, the system information block message is the System Information Block Type 1 (SIB1) information, and the prohibited access attempt information is pre-configured information used by the RedCap terminal to determine whether it can access the cell.

[0074] It should be understood that the embodiment of the present application does not limit the device for configuring the prohibited access attempt information. Exemplarily, the network device may configure the prohibited access attempt information for the RedCap terminal.

[0075] It should be understood that the conditions included in the prohibited access attempt information will be described by way of example hereinafter and will not be elaborated here.

[0076] S12. If the RedCap terminal determines that it meets the conditions in the prohibited access attempt information, prohibit the access attempt of the RedCap terminal.

[0077] In this step, when the RedCap terminal determines that it meets the conditions in the prohibited access attempt information, it means that the vendor restricts the access of the RedCap terminal, so the access attempt of the RedCap terminal is prohibited.

[0078] S13. If the RedCap terminal determines that it does not meet the conditions in the prohibited access attempt information, allow the access attempt of the RedCap terminal.

[0079] In this step, when the RedCap terminal determines that it does not meet the conditions in the prohibited access attempt information, it means that the vendor allows the access of the RedCap terminal, so the access attempt of the RedCap terminal is allowed.

[0080] The access control method for a RedCap terminal supporting CAG provided by an embodiment of this application. When the RedCap terminal starts the UAC process, it determines whether the RedCap terminal meets the conditions in the access prohibition attempt information based on the received system information block message. If it meets the conditions, the access attempt of the RedCap terminal is prohibited; if it does not meet the conditions, the access attempt of the RedCap terminal is allowed. Among them, the access prohibition attempt information is pre-configured information used by the RedCap terminal to determine whether it can access the cell. In the embodiment of this application, by the RedCap terminal judging whether it meets the conditions in the access prohibition attempt information, the access control of the RedCap terminal is realized in the private network scenario.

[0081] Figure 2 It is a schematic flowchart of the second embodiment of the access control method for a RedCap terminal supporting CAG provided by an embodiment of this application. As Figure 2 shown, before S11, the access control method for the RedCap terminal supporting CAG may further include the following steps:

[0082] S21: Receive the system information block message.

[0083] S22: If the cell access related information cell in the system information block message contains an entry corresponding to the PLMN selected by the RedCap terminal, and the RedCap terminal is allowed or instructed to access the PLMN selected by the RedCap terminal through a cell that broadcasts the CAG ID, then determine that the RedCap terminal uses the information in the NPN identification information list containing the selected PLMN.

[0084] In this step, after the RedCap terminal receives the system information block message (SIB1 message), it retrieves whether the cell access related information cell (cellAccessRelatedInfo cell) in it contains an entry corresponding to the PLMN selected by the RedCap terminal, and the RedCap terminal is allowed or instructed to access the PLMN selected by the RedCap terminal through a cell that broadcasts the CAG ID. Then, in the subsequent process (such as the UAC process), it is determined that the RedCap terminal uses the entry from the NPN identification information (npn-IdentityInfoList) containing the selected PLMN.

[0085] Among them, the entries in the npn-IdentityInfoList of the PLMN selected by the RedCap terminal are the information of the received cell in the corresponding NPN-IdentityInfo in the npn-IdentityInfoList, including the NPN identity list (npn-IdentityList), the tracking area code (trackingAreaCode), and the cell identity (cellIdentity).

[0086] Based on the above embodiments, exemplarily, the conditions in the access attempt prohibition information may include at least one of the following:

[0087] Condition 1: The system information block message contains a UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identity information list, and there is a PLMN-identity index corresponding to the NPN identity information list used by the RedCap terminal in the UAC restricted PLMN entry.

[0088] In practical applications, Condition 1 can be implemented as that the SIB1 message contains a UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell), and the UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell) contains a UAC restricted PLMN entry (UAC-BarringPerPLMN entry) corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identity information list (npn-IdentityInfoList), and there is a PLMN-identity index (plmn-IdentityIndex) corresponding to the NPN identity information list (npn-IdentityInfoList) used by the RedCap terminal in the UAC restricted PLMN entry (UAC-BarringPerPLMN entry).

[0089] Among them, the above corresponding UAC-BarringPerPLMN entry is the entry corresponding to the plmn-IdentityIndex of the PLMN selected by the RedCap terminal in the UAC-BarringPerPLMN-List cell.

[0090] Optionally, when the RedCap terminal determines that Condition 1 is met, select the UAC-BarringPerPLMN entry according to the plmn-IdentityIndex corresponding to the npn-IdentityInfoList used by the RedCap terminal in the UAC-BarringPerPLMN entry, and prohibit the access attempt of the RedCap terminal.

[0091] Condition 2: The system information block message contains a UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identification information list, and there is no PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry, and the system information block message does not contain RedCap exclusive co-frequency reselection indication information.

[0092] In practical applications, Condition 2 can be implemented as follows: The SIB1 message contains a UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell), and the UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell) contains a UAC restricted PLMN entry (UAC-BarringPerPLMN entry) corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identification information list (npn-IdentityInfoList), and there is no PLMN-identification index (plmn-IdentityIndex) corresponding to the NPN identification information list (npn-IdentityInfoList) used by the RedCap terminal in the UAC restricted PLMN entry (UAC-BarringPerPLMN entry), and the system information block message does not contain RedCap exclusive co-frequency reselection indication information (intraFreqReselectionRedCap).

[0093] Condition 3: The system information block message contains a UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identity information list, and there is no PLMN-identity index corresponding to the NPN identity information list in the UAC restricted PLMN entry, and the system information block message contains RedCap-specific intra-frequency reselection indication information, and the system information block message contains fields related to RedCap indication information, and the RedCap terminal meets the requirements for the RedCap terminal in the fields related to RedCap indication information.

[0094] In practical applications, Condition 3 can be implemented as follows: The SIB1 message contains a UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell), and the UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell) contains a UAC restricted PLMN entry (UAC-BarringPerPLMN entry) corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses the information in the NPN identity information list (npn-IdentityInfoList), and there is no PLMN-identity index (plmn-IdentityIndex) corresponding to the NPN identity information list (npn-IdentityInfoList) used by the RedCap terminal in the UAC restricted PLMN entry (UAC-BarringPerPLMN entry), and the system information block message contains RedCap-specific intra-frequency reselection indication information (intraFreqReselectionRedCap), and the system information block message contains fields related to RedCap indication information, and the RedCap terminal meets the requirements for the RedCap terminal in the fields related to RedCap indication information.

[0095] Among them, the fields related to RedCap indication information include at least one of the following:

[0096] The RedCap terminal residence field for cell restriction 1 receive (Rx) (cellBarredRedCap1Rx), the RedCap terminal residence field for cell restriction 2 Rx (cellBarredRedCap2Rx), the RedCap terminal residence field allowing half-duplex Frequency Division Duplexing (FDD) (halfDuplexRedCapAllowed).

[0097] It should be understood that if the relevant fields of the RedCap indication information include the RedCap terminal residence field for cell restriction 1Rx, the requirement for the RedCap terminal in the relevant fields of the RedCap indication information is that the number of receive antenna branches is equal to 1.

[0098] If the relevant fields of the RedCap indication information include the RedCap terminal residence field for cell restriction 2Rx, the requirement for the RedCap terminal in the relevant fields of the RedCap indication information is that the number of receive antenna branches is equal to 2.

[0099] If the relevant fields of the RedCap indication information include the RedCap terminal residence field allowing half-duplex FDD, the requirement for the RedCap terminal in the relevant fields of the RedCap indication information is that it only supports half-duplex FDD operation.

[0100] That is to say, the system information block message contains the relevant fields of the RedCap indication information, and the realization that the RedCap terminal meets the requirements for the RedCap terminal in the relevant fields of the RedCap indication information can be:

[0101] When cellBarredRedCap1Rx is sent in the SIB1 message, and cellBarredRedCap1Rx is set to "forbidden", and the number of Rx branches of the RedCap terminal is equal to 1.

[0102] When cellBarredRedCap2Rx is sent in the SIB1 message, and cellBarredRedCap2Rx is set to "forbidden", and the number of Rx branches of the RedCap terminal is equal to 2.

[0103] When halfDuplexRedCapAllowed is sent in the SIB1 message, and the RedCap terminal only supports half-duplex FDD operation.

[0104] Condition 4: The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell does not contain the UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal.

[0105] In practical applications, Condition 4 can be implemented such that the SIB1 message contains a UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell), and the UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell) does not contain a UAC restricted PLMN entry (UAC-BarringPerPLMN entry) corresponding to the PLMN selected by the RedCap terminal.

[0106] Optionally, when the RedCap terminal determines that Condition 4 is met, it can also select a UAC-BarringPerPLMN entry through the plmn-IdentityIndex entry corresponding to the PLMN selected by the RedCap terminal and the PLMN identity information (PLMN-IdentityInfo).

[0107] Condition 5: The system information block message does not contain a UAC restricted PLMN list cell.

[0108] In practical applications, Condition 5 can be implemented such that the SIB1 message does not contain a UAC restricted PLMN list cell (UAC-BarringPerPLMN-List cell).

[0109] Optionally, when the RedCap terminal determines that Condition 5 is met, it can also select a UAC-BarringPerPLMN entry through the plmn-IdentityIndex entry corresponding to the PLMN selected by the RedCap terminal and the PLMN identity information (PLMN-IdentityInfo).

[0110] It should be understood that if any UAC-BarringPerPLMN entry is selected, then in the subsequent process, regardless of whether the SIB1 message contains UAC common restriction information (uac-BarringForCommon) (i.e., whether there is an access restriction parameter in this entry), the selected UAC-BarringPerPLMN entry will be used and the access attempt of the RedCap terminal will be prohibited.

[0111] Based on the access control method for a RedCap terminal supporting CAG shown in any of the above embodiments, the method will be explained through a specific example next.

[0112] Exemplarily, the access control method for the RedCap terminal supporting CAG can be implemented through the following steps:

[0113] Step 1: Store the obtained SIB1 message.

[0114] Step 2. Include the entry corresponding to the PLMN selected by the RedCap terminal in the cellAccessRelatedInfo of the SIB1 message. If the RedCap terminal is allowed or instructed to access the PLMN through a cell that broadcasts the CAG ID, then in the subsequent process, the RedCap terminal will use the information of the cell received from the entry (i.e., the corresponding NPN-IdentityInfo) in the npn-IdentityInfoList that contains the selected PLMN, including npn-IdentityList, trackingAreaCode, and cellIdentity.

[0115] Step 3. Determine whether the SIB1 message contains the cell UAC-BarringPerPLMN-List and whether it contains the UAC-BarringPerPLMN entry corresponding to the selected PLMN (i.e., the entry corresponding to the plmn-IdentityIndex of the selected PLMN).

[0116] If the SIB1 message contains the cell UAC-BarringPerPLMN-List and it contains the UAC-BarringPerPLMN entry corresponding to the selected PLMN, then execute Step 3.1; if the SIB1 message does not contain the cell UAC-BarringPerPLMN-List, then execute Step 3.2; if the SIB1 message contains the cell UAC-BarringPerPLMN-List and it does not contain the UAC-BarringPerPLMN entry corresponding to the selected PLMN, then execute Step 3.2.

[0117] Step 3.1. Determine whether the selected PLMN uses the information in the entry npn-IdentityInfoList.

[0118] If so, then execute Step 3.1.1; if not, then execute Step 3.1.2.

[0119] Step 3.1.1. If there is a plmn-IdentityIndex entry in the information of UAC-BarringPerPLMN that corresponds to the information in the used npn-IdentityInfoList, then select the UAC-BarringPerPLMN entry through the corresponding plmn-IdentityIndex entry and prohibit the access attempt of the RedCap terminal.

[0120] Step 3.1.2. Determine whether intraFreqReselectionRedCap is sent in the SIB1 message.

[0121] If so, execute step 3.1.2.1; if not, execute step 3.1.2.2.

[0122] Step 3.1.2.1: Consider that the cell prohibits the RedCap terminal from camping and prohibits access attempts by the RedCap terminal.

[0123] Step 3.1.2.2: If the SIB1 message contains fields related to RedCap indication information and the RedCap terminal meets the requirements for the RedCap terminal in the fields related to RedCap indication information, prohibit access attempts by the RedCap terminal.

[0124] Specifically, step 3.1.2.2 can be implemented in the following three ways:

[0125] Method 1: When cellBarredRedCap1Rx is sent in the SIB1 message and cellBarredRedCap1Rx is set to "barred". If the number of Rx branches of the RedCap terminal is equal to 1, prohibit access attempts by the RedCap terminal.

[0126] Method 2: When cellBarredRedCap2Rx is sent in the SIB1 message and cellBarredRedCap2Rx is set to "barred". If the number of Rx branches of the RedCap terminal is equal to 2, prohibit access attempts by the RedCap terminal.

[0127] Method 3: When halfDuplexRedCapAllowed is sent in the SIB1 message, if the RedCap terminal only supports half-duplex FDD operation, consider that the cell prohibits the RedCap terminal from camping and prohibits access attempts by the RedCap terminal.

[0128] Step 3.2: Select the UAC-BarringPerPLMN entry through the plmn-IdentityIndex entry corresponding to the selected PLMN and PLMN-IdentityInfo.

[0129] Step 4: Determine whether any UAC-BarringPerPLMN entry is selected correspondingly.

[0130] If so, execute step 4.1; if not, execute step 4.2.

[0131] Step 4.1: In the subsequent process, regardless of whether the SIB1 message contains uac-BarringForCommon (i.e., whether there is an access restriction parameter in this entry), the selected UAC-BarringPerPLMN entry will be used, and the access attempt of the RedCap terminal will be prohibited.

[0132] Step 4.2: Allow the access attempt of the RedCap terminal.

[0133] This application provides a UAC mechanism to implement access control for RedCap terminals supporting the CAG function, meeting the requirement of the operator to restrict the initial access attempt of RedCap terminals for reasons such as load control in the private network scenario.

[0134] The following is an embodiment of the device of this application, which can be used to execute the method embodiment of this application. For details not disclosed in the device embodiment of this application, please refer to the method embodiment of this application.

[0135] Figure 3 It is a schematic structural diagram of an access control device for a RedCap terminal supporting CAG provided by an embodiment of this application. As Figure 3 shown, the access control device 30 for the RedCap terminal supporting CAG includes:

[0136] A determination module 31, configured to determine whether the RedCap terminal meets the conditions in the prohibited access attempt information based on the system information block message received in advance when the lightweight RedCap terminal starts the UAC process, where the prohibited access attempt information is pre-configured information for the RedCap terminal to determine whether it can access the cell;

[0137] A prohibition module 32, configured to prohibit the access attempt of the RedCap terminal if the RedCap terminal determines that it meets the conditions in the prohibited access attempt information.

[0138] In a possible implementation manner, the access control device for the RedCap terminal supporting CAG further includes:

[0139] An allowance module, configured to allow the access attempt of the RedCap terminal if the RedCap terminal determines that it does not meet the conditions in the prohibited access attempt information.

[0140] In a possible implementation manner, the conditions in the prohibited access attempt information include at least one of the following:

[0141] The system information block message contains a UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is a PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry;

[0142] Or,

[0143] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is no PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry, and the system information block message does not contain RedCap exclusive co-frequency reselection indication information;

[0144] Or,

[0145] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is no PLMN-identification index corresponding to the NPN identification information list in the UAC restricted PLMN entry, and the system information block message contains the RedCap exclusive co-frequency reselection indication information, and the system information block message contains a field related to RedCap indication information, and the RedCap terminal meets the requirements for the RedCap terminal in the field related to RedCap indication information;

[0146] Or,

[0147] The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell does not contain a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal;

[0148] Or,

[0149] The system information block message does not contain the UAC restricted PLMN list cell.

[0150] In a possible implementation, the field related to RedCap indication information includes at least one of the following:

[0151] RedCap terminal residence fields restricted to 1Rx for the cell, RedCap terminal residence fields restricted to 2Rx for the cell, and RedCap terminal residence fields allowing half-duplex FDD.

[0152] In a possible implementation, if the RedCap indication information related field includes the RedCap terminal residence field restricted to 1Rx for the cell, the requirement for the RedCap terminal in the RedCap indication information related field is that the number of receive antenna branches is equal to 1;

[0153] If the RedCap indication information related field includes the RedCap terminal residence field restricted to 2Rx for the cell, the requirement for the RedCap terminal in the RedCap indication information related field is that the number of receive antenna branches is equal to 2;

[0154] If the RedCap indication information related field includes the RedCap terminal residence field allowing half-duplex FDD, the requirement for the RedCap terminal in the RedCap indication information related field is that it only supports half-duplex FDD operation.

[0155] In a possible implementation, the access control device 30 for the RedCap terminal supporting CAG further includes:

[0156] A receiving module, configured to receive the system information block message before the RedCap terminal starts the UAC process;

[0157] The determining module 31 is further configured to determine that the RedCap terminal uses the information in the NPN identification information list including the selected PLMN if the cell access related information element in the system information block message contains the entry corresponding to the PLMN selected by the RedCap terminal, and the RedCap terminal is allowed or indicated to access the PLMN selected by the RedCap terminal through the cell that has broadcast the CAGID.

[0158] The access control device for the RedCap terminal supporting CAG provided in the embodiments of the present application can be used to execute the access control method for the RedCap terminal supporting CAG in any of the above embodiments, and its implementation principle and technical effects are similar, and will not be elaborated here.

[0159] It should be noted that it should be understood that the division of each module of the above device is only a division of logical functions. In actual implementation, it can be fully or partially integrated into a physical entity, or physically separated. And these modules can all be implemented in the form of software called by a processing element; they can also all be implemented in the form of hardware; or some modules can be implemented in the form of software called by a processing element, and some modules can be implemented in the form of hardware. In addition, all or part of these modules can be integrated together or can be independently implemented. The processing element mentioned here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through the integrated logic circuit of the hardware in the processor element or the instruction in the form of software.

[0160] Figure 4 This is a schematic structural diagram of the RedCap terminal provided by the embodiment of the present application. As Figure 4 shown, the RedCap terminal 40 may include: a processor 41, a memory 42, and computer program instructions stored on the memory 42 and executable on the processor 41. When the processor 41 executes the computer program instructions, it implements the access control method of the RedCap terminal supporting CAG provided in any of the foregoing embodiments.

[0161] Optionally, the above-mentioned various components of the RedCap terminal 40 may be connected through a system bus.

[0162] The memory 42 may be a separate storage unit or may be an integrated storage unit in the processor. The number of processors is one or more.

[0163] Optionally, the RedCap terminal 40 may further include a transceiver for communicating with a network device.

[0164] It should be understood that the processor 41 may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0165] The system bus can be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The system bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity in illustration, only a thick line is used in the figure to represent it, but it does not mean that there is only one bus or one type of bus. The memory may include a Random Access Memory (RAM), and may also include a Non-Volatile Memory (NVM), such as at least one disk memory.

[0166] All or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a readable memory. When the program is executed, it performs the steps including the above method embodiments; and the foregoing memory (storage medium) includes: Read-Only Memory (ROM), RAM, flash memory, hard disk, solid state drive, magnetic tape, floppy disk, optical disc, and any combination thereof.

[0167] The RedCap terminal provided in the embodiments of this application can be used to execute the access control method for the RedCap terminal supporting CAG provided in any of the above method embodiments. The implementation principles and technical effects are similar and will not be elaborated here.

[0168] The embodiments of this application provide a computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When the computer-executable instructions run on a computer, the computer is caused to execute the above access control method for the RedCap terminal supporting CAG.

[0169] For the above computer-readable storage medium, the above-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory, Electrically Erasable Programmable Read-Only Memory, Erasable Programmable Read-Only Memory, Programmable Read-Only Memory, Read-Only Memory, magnetic memory, flash memory, magnetic disk, or optical disc. The readable storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0170] Optionally, a readable storage medium is coupled to the processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an Application Specific Integrated Circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in a device.

[0171] An embodiment of this application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, the access control method for the RedCap terminal supporting CAG described above can be implemented.

[0172] It should be understood that this application is not limited to the exact structure already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is only limited by the appended claims.

Claims

1. An access control method for a RedCap terminal supporting CAG, characterized in that, it includes: When the lightweight RedCap terminal starts the unified access control (UAC) process, determine whether the RedCap terminal meets the conditions in the prohibited access attempt information based on the pre-received system information block message, where the prohibited access attempt information is pre-configured information used by the RedCap terminal to determine whether it can access the cell; If the RedCap terminal determines that it meets the conditions in the prohibited access attempt information, prohibit the access attempt of the RedCap terminal.

2. The method according to claim 1, characterized in that, the method further includes: If the RedCap terminal determines that it does not meet the conditions in the prohibited access attempt information, allow the access attempt of the RedCap terminal.

3. The method according to claim 1 or 2, characterized in that, the conditions in the prohibited access attempt information include at least one of the following: The system information block message contains a UAC restricted public land mobile network (PLMN) list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the non-public network (NPN) identification information list, and there is a PLMN-identification index in the UAC restricted PLMN entry corresponding to the NPN identification information list used by the RedCap terminal; Or, The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is no PLMN-identification index in the UAC restricted PLMN entry corresponding to the NPN identification information list, and the system information block message does not contain RedCap exclusive same-frequency reselection indication information; Or, The system information block message contains the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell contains a UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal, and the selected PLMN uses information in the NPN identification information list, and there is no PLMN-identification index in the UAC restricted PLMN entry corresponding to the NPN identification information list, and the system information block message contains the RedCap exclusive same-frequency reselection indication information, and the system information block message contains a RedCap indication information related field, and the RedCap terminal meets the requirements for the RedCap terminal in the RedCap indication information related field; Or, The system information block message includes the UAC restricted PLMN list cell, and the UAC restricted PLMN list cell does not include the UAC restricted PLMN entry corresponding to the PLMN selected by the RedCap terminal; Or, The system information block message does not include the UAC restricted PLMN list cell.

4. The method according to claim 3, wherein, The RedCap indication information related field includes at least one of the following: RedCap terminal residence field restricted to 1Rx in the cell, RedCap terminal residence field restricted to 2Rx in the cell, RedCap terminal residence field allowing half-duplex frequency division duplex (FDD).

5. The method according to claim 4, wherein, If the RedCap indication information related field includes the RedCap terminal residence field restricted to 1Rx in the cell, the requirement for the RedCap terminal in the RedCap indication information related field is that the number of receive antenna branches is equal to 1; If the RedCap indication information related field includes the RedCap terminal residence field restricted to 2Rx in the cell, the requirement for the RedCap terminal in the RedCap indication information related field is that the number of receive antenna branches is equal to 2; If the RedCap indication information related field includes the RedCap terminal residence field allowing half-duplex FDD, the requirement for the RedCap terminal in the RedCap indication information related field is that it only supports half-duplex FDD operation.

6. The method according to claim 3, wherein, Before the RedCap terminal starts the UAC process, the method further includes: Receiving the system information block message; If the cell access related information cell in the system information block message includes the entry corresponding to the PLMN selected by the RedCap terminal, and the RedCap terminal is allowed or indicated to access the PLMN selected by the RedCap terminal through a cell broadcasting a closed access group (CAG) ID, determining that the RedCap terminal uses the information in the NPN identification information list including the selected PLMN.

7. An access control device for a RedCap terminal supporting CAG, wherein, It includes: A determination module, configured to determine whether the RedCap terminal meets the conditions in the prohibited access attempt information based on a pre-received system information block message when the lightweight RedCap terminal starts the unified access control (UAC) process, where the prohibited access attempt information is pre-configured and used for the RedCap terminal to determine whether it can access the cell; A prohibition module, configured to prohibit the access attempt of the RedCap terminal if the RedCap terminal determines that it meets the conditions in the prohibited access attempt information.

8. A RedCap terminal, including: A processor, a memory, and computer program instructions stored on the memory and executable on the processor, wherein the processor, when executing the computer program instructions, is configured to implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, wherein, computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are configured to implement the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, wherein, when the computer program is executed by a processor, it is configured to implement the method according to any one of claims 1 to 6.

Images