Communication method and apparatus, and access network device

Abstract

The present application provides a communication method and apparatus, and an access network device. The communication method comprises: acquiring a capability parameter of a user equipment, wherein the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than that of the second network; determining that the capability parameter does not correspond to the type of the user equipment, and acquiring a first release parameter; and on the basis of the first release parameter, ending the access of the user equipment to the first network.

Description

Communication method, device and access network equipment

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on March 18, 2024, with application number 202410308855.4 and invention name “A communication method, device and access network equipment”, the entire contents of which are cited in this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method, apparatus, and access network equipment. Background Art

[0003] 3GPP defined the RedCap (Reduced Capability) terminal device type in Rel-17 to meet the 5G IoT requirements for low-cost, low-power terminals. However, there is currently a lack of solutions for abnormal communication scenarios involving RedCap terminals. Summary of the Invention

[0004] This application provides the following technical solutions:

[0005] On one hand, the present application provides a communication method, including:

[0006] Obtaining capability parameters of a user equipment; the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network;

[0007] Determining that the capability parameter does not correspond to the type of the user equipment, and obtaining a first release parameter;

[0008] The access of the user equipment to the first network is terminated based on the first release parameter.

[0009] Get the first release parameters, including:

[0010] Obtaining a message of an initial context establishment failure, where the message of the initial context establishment failure carries a first cause value, where the first cause value is used to indicate that the capability parameter represents insufficient capability of the user equipment to access the first network;

[0011] A user equipment context release command is obtained, where the user equipment context release command carries a second cause value, where the second cause value is used to prompt that the capability parameter represents insufficient capability of the user equipment to access the first network.

[0012] The step of terminating the user equipment's access to the first network based on the first release parameter includes:

[0013] Sending a message indicating that the initial context establishment has failed to the access and mobility management function network element of the first network, so that the access and mobility management function network element ends establishing the context with the user equipment;

[0014] The user equipment context release command is sent to a distribution unit of an access network device, so that the distribution unit ends establishing the context with the user equipment.

[0015] The method further comprises:

[0016] Determining, based on the capability parameter, that the user equipment has the capability of accessing the second network, and acquiring a second release parameter;

[0017] The user equipment is enabled to access the second network based on the second release parameter.

[0018] Get the second release parameters, including:

[0019] Acquire RRC release connection information, where the RRC release connection information carries a redirection parameter, and the redirection parameter is used to assist the user equipment in accessing the second network.

[0020] The redirection parameters include:

[0021] Redirect frequency;

[0022] Or, the redirection frequency and the working parameters of the redirection frequency.

[0023] The method further comprises:

[0024] Determining, based on the capability parameter, that the user equipment does not have an ability to access the second network, and acquiring a third release parameter;

[0025] The user equipment is caused to enter a waiting state based on the third release parameter, and in the waiting state, the user equipment does not request to access the first network.

[0026] Get the third release parameter, including:

[0027] RRC release connection information is obtained, where the RRC release connection information carries a waiting instruction, and the waiting instruction is used to prompt the user equipment to enter a waiting state.

[0028] Another aspect of the present application provides a communication device, comprising:

[0029] a first acquisition module, configured to acquire a capability parameter of a user equipment; the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network;

[0030] a second acquisition module, configured to determine that the capability parameter does not correspond to the type of the user equipment, and acquire a first release parameter;

[0031] A first control module is configured to terminate the user equipment's access to the first network based on the first release parameter.

[0032] A third aspect of the present application provides an access network device, including:

[0033] at least one distribution unit;

[0034] Centralized unit for:

[0035] Obtaining capability parameters of a user equipment; the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network;

[0036] Determining that the capability parameter does not correspond to the type of the user equipment, and obtaining a first release parameter;

[0037] The access of the user equipment to the first network is terminated based on the first release parameter. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0039] FIG1 is a flow chart of a communication method provided in Example 1 of the present application;

[0040] FIG2 is a flow chart of a communication method provided in Example 2 of the present application;

[0041] FIG3 is a flow chart of a communication method provided in Example 4 of the present application;

[0042] FIG4 is a schematic diagram of a signaling processing flow provided by the present application;

[0043] FIG5 is a flow chart of a communication method provided in Example 4 of the present application;

[0044] FIG6 is a flow chart of a communication method provided in Example 5 of the present application;

[0045] FIG7 is a schematic diagram of another signaling processing flow provided by the present application;

[0046] FIG8 is a flow chart of a communication method provided in Example 7 of the present application;

[0047] FIG9 is a schematic diagram of another signaling processing flow provided by the present application;

[0048] FIG10 is a schematic diagram of an interaction provided by the present application;

[0049] FIG11 is a schematic structural diagram of a communication device provided in this application. DETAILED DESCRIPTION

[0050] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0051] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0052] 1 is a flow chart of a communication method provided in Example 1 of the present application. The method can be applied to an access network device, which can provide a random access function for a user equipment. The present application does not limit the product type of the access network device. As shown in FIG1 , the method may include but is not limited to the following steps:

[0053] Step S101: Acquire capability parameters of a user equipment; the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network.

[0054] In this embodiment, the access network device (such as a base station) identifies whether the user equipment type is RedCap as early as possible during the user equipment access phase. Specifically, a PRACH opportunity dedicated to RedCap type user equipment can be configured in the SIB1 message, and the access network device determines the RedCap type user equipment by detecting the dedicated PRACH opportunity where MSG1 / MSGA is located. During the process of random access to the first network, the RedCap type user equipment can send MGS3 / MSGA using a specific LCID to identify the CCCH, and the access network device determines the RedCap type user equipment by the LCID used by the user equipment.

[0055] The first network may include but is not limited to: 5G network (5G Network, fifth-generation mobile communication network), and the second network may include but is not limited to: 4G (fourth-generation mobile communication technology) network or 3G (third-generation mobile communication technology) network or 2G (second-generation mobile communication technology) network.

[0056] After determining that the user equipment is of the RedCap type, the access network device establishes an initial connection with the user equipment according to the RedCap type.

[0057] In this embodiment, obtaining the capability parameters of the user equipment may include but is not limited to:

[0058] After the user equipment establishes an initial connection with the access network device, the access network device may send a UE capability enquiry message to the user equipment. The UE capability enquiry message is used to query the UE's capabilities. After receiving the UE capability enquiry message, the user equipment reports the user equipment's capabilities to the access network device by including them in capability parameters.

[0059] In the case where the user equipment type is a reduced capability type, the user equipment's capability parameters may include RedCap feature support information, which is used to indicate the user equipment's RedCap feature support status. If the user equipment's capability parameters include RedCap feature support information, the access network device communicates with the user equipment according to the processing flow corresponding to the RedCap type. Specifically, the user equipment's capability parameters may include a RedCapParameters information element indicating the user equipment's RedCap feature support status.

[0060] Step S102: Determine that the capability parameter does not correspond to the type of the user equipment, and obtain a first release parameter.

[0061] It is understandable that if the capability parameters do not correspond to the type of user equipment, it will affect the subsequent communication between the user equipment and the access network equipment that establish the initial connection. For example, the access network equipment cannot normally handle the subsequent BWP, wireless bearer and other configuration processes of the user equipment.

[0062] If the capability parameter corresponds to the type of the user equipment, the access network device can complete the initial registration and subsequent session establishment according to the processing flow corresponding to the RedCap type specified in the communication protocol.

[0063] As described in step S101, the capability parameters of the user equipment of the reduced capability type should include the RedCap feature support information. If the capability parameters of the user equipment of the reduced capability type do not include the RedCap feature support information, it can be determined that the capability parameters do not correspond to the type of the user equipment. Of course, the implementation method of determining that the capability parameters do not correspond to the type of the user equipment is not limited to this.

[0064] In an abnormal communication scenario where the capability parameters do not correspond to the type of user equipment, the first release parameter may be, but is not limited to, a parameter defined in the communication protocol. For example, if the first network is a 5G network, one or more parameters defined in the 3GPP 5G protocol may be applied to an abnormal communication scenario where the capability parameters do not correspond to the type of user equipment. The first release parameter comes from one or more parameters defined in the 3GPP 5G protocol.

[0065] Step S103: End the user equipment's access to the first network based on the first release parameter.

[0066] In this embodiment, the capability parameters of the user device are obtained; the type of the user device is a reduced capability type, and an abnormal communication scenario in which the capability parameters do not correspond to the type of the user device is determined. For the abnormal communication scenario, a first release parameter is obtained, and the user device's access to the first network is terminated based on the first release parameter to optimize the processing flow of the access network device.

[0067] As another optional embodiment of the present application, refer to FIG. 2 , which is a flow chart of a communication method provided in Example 2 of the present application. This embodiment is mainly an implementation of step S102 in the above-mentioned Example 1. As shown in FIG. 2 , step S102 may include but is not limited to the following steps:

[0068] Step S1021: Determine that the capability parameter does not correspond to the type of the user equipment, and obtain a message indicating that the initial context establishment has failed and a user equipment context release command.

[0069] In this embodiment, the initial context setup failure message (INITIAL CONTEXT SETUP FAILURE) is a message defined in the communication protocol.

[0070] The message indicating that the initial context establishment has failed carries a first cause value (Insufficient UE Capabilities), where the first cause value is used to indicate that the capability parameter represents that the capability of the user equipment to access the first network is insufficient.

[0071] The message indicating that the initial context establishment failed corresponds to a core network device. For example, if the first network is a 5G network, the core network device may include an AMF (Access and Mobility Management Function) network element.

[0072] The message indicating that the initial context establishment has failed may be used to cause the core network device to terminate the context establishment with the user equipment.

[0073] In this embodiment, the UE Context Release Command is a message defined in the communication protocol.

[0074] The user equipment context release command (UE Context Release Command) carries a second cause value (Insufficient UE Capabilities), where the second cause value is used to indicate that the capability parameter represents that the capability of the user equipment to access the first network is insufficient.

[0075] The user equipment context release command corresponds to the access network device. For example, if the access network device is a base station, the user equipment context release command corresponds to a DU (distributed unit) in the base station.

[0076] The user equipment context release command may be used to enable the access network device to terminate the context establishment between the access network device and the user equipment.

[0077] Accordingly, step S103 in Example 1 may include but is not limited to:

[0078] Step S1031: End the user equipment's access to the first network based on the message indicating the failure of the initial context establishment and the user equipment context release command.

[0079] In this embodiment, by obtaining the capability parameters of the user device; the type of the user device is a reduced capability type, and an abnormal communication scenario in which the capability parameters do not correspond to the type of the user device is determined, for the abnormal communication scenario, a message of failure to establish an initial context and a user device context release command are obtained. The message of failure to establish an initial context and the user device context release command are messages and commands defined in the communication protocol. The user device's access to the first network is terminated through the defined messages and commands to optimize the processing flow of the access network device.

[0080] As another optional embodiment of the present application, referring to FIG. 3 , which is a flow chart of a communication method provided in Example 3 of the present application, this embodiment is mainly an implementation of step S1031 in the above-mentioned Example 2. As shown in FIG. 3 , step S1031 may include but is not limited to the following steps:

[0081] Step S10311: Send a message indicating that the initial context establishment has failed to the access and mobility management function network element of the first network, so that the access and mobility management function network element ends establishing the context with the user equipment.

[0082] A message about the failure of initial context establishment is sent to the access and mobility management function network element of the first network, that is, the access and mobility management function network element of the first network is notified that the user equipment has insufficient ability to access the first network. On this basis, the access and mobility management function network element can terminate the context establishment between the user equipment and the access and mobility management function network element.

[0083] Step S10312: Send a user equipment context release command to the distribution unit of the access network device, so that the distribution unit ends establishing the context with the user equipment.

[0084] Sending a user equipment context release command to the distribution unit of the access network device notifies the distribution unit of the access network device that the user equipment has insufficient capability to access the first network. Based on this, the distribution unit may terminate establishing the context with the user equipment.

[0085] After the access and mobility management function network element finishes establishing the context with the user equipment and the distribution unit finishes establishing the context with the user equipment, the user equipment's access to the first network ends and the user equipment cannot access the first network to perform corresponding data services.

[0086] In this embodiment, by obtaining the capability parameters of the user equipment; the type of the user equipment is a reduced capability type, and an abnormal communication scenario in which the capability parameters do not correspond to the type of the user equipment is determined, for the abnormal communication scenario, a message of failure in initial context establishment and a user equipment context release command are obtained, and the message of failure in initial context establishment and the user equipment context release command are messages and commands defined in the communication protocol. The message of failure in initial context establishment is sent to the access and mobility management function network element of the first network, so that the access and mobility management function network element ends establishing the context with the user equipment, and the user equipment context release command is sent to the distribution unit of the access network device, so that the distribution unit ends establishing the context with the user equipment, so as to optimize the processing flow of the access network device.

[0087] For example, if the access network device is a base station, and the base station includes a CU and a DU, the optimized signaling processing flow of the access network device can be referred to FIG4 . As shown in FIG4 , in the initial access process, if the CU determines that the UE (i.e., an implementation method of the user equipment) carries a RedCap terminal identifier in the UE access message, the UE RRC establishment process, NAS authentication, NAS security, RRC security process, and UE capability query process are normally completed;

[0088] The above-mentioned initial access process, UE RRC establishment process, completion of NAS authentication, NAS security, RRC security process, and UE capability query process can be referred to the initial access process, UE RRC establishment process, completion of NAS authentication, NAS security, RRC security process, and UE capability query process in the 3GPP 5G protocol in the prior art, and will not be repeated here.

[0089] After determining that the capability parameters do not correspond to the type of user equipment, the exception handling process is entered: the CU sends INITIAL CONTEXT SETUP FAILURE to the AMF, carrying the first cause value of "Insufficient UE Capabilities"; among them, INITIAL CONTEXT SETUP FAILURE comes from TS 38.413 in the 3GPP 5G protocol.

[0090] The CU sends a UE Context Release Command to the DU, carrying the second cause value of "Insufficient UE Capabilities". The UE Context Release Command comes from TS 38.473 in the 3GPP 5G protocol.

[0091] As another optional embodiment of the present application, referring to FIG. 5 , which is a flow chart of a communication method provided in Example 4 of the present application, as shown in FIG. 5 , the method may include but is not limited to the following steps:

[0092] Step S201: Acquire capability parameters of a user equipment; the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network.

[0093] Step S202: Determine that the capability parameter does not correspond to the type of the user equipment, and obtain a first release parameter.

[0094] Step S203: End the user equipment's access to the first network based on the first release parameter.

[0095] The detailed process of steps S201-S203 can be found in the relevant introduction of steps S101-S103 in Example 1, and will not be repeated here.

[0096] Step S204: Determine based on the capability parameter that the user equipment has the capability to access the second network, and obtain a second release parameter.

[0097] In an implementation where the first network is a 5G network and the second network is a 4G network, if the capability parameters of the user equipment include "Rat-Type: eutra" information, it can be determined that the user equipment has the ability to access the 4G network. The "Rat-Type: eutra" information is used to indicate that the user equipment supports eutra (which can be understood as the standard of the LTE network, which is the fourth generation mobile communication technology). Of course, the implementation method of determining whether the user equipment has the ability to access the second network based on the capability parameters is not limited to this.

[0098] In an abnormal communication scenario where the capability parameter does not correspond to the type of the user equipment, the second release parameter may be, but is not limited to, a parameter defined in the communication protocol.

[0099] Step S205: Enable the user equipment to access the second network based on the second release parameter.

[0100] In this embodiment, by obtaining the capability parameters of the user device; the type of the user device is a reduced capability type, an abnormal communication scenario in which the capability parameters do not correspond to the type of the user device is determined, and for the abnormal communication scenario, a first release parameter is obtained, and the user device's access to the first network is terminated based on the first release parameter. Furthermore, it can be determined based on the capability parameters that the user device has the ability to access the second network, and a second release parameter is obtained. Based on the second release parameter, the user device is enabled to access the second network to optimize the processing flow of the access network device.

[0101] As another optional embodiment of the present application, referring to FIG. 6 , which is a flow chart of a communication method provided in Example 5 of the present application, this embodiment is mainly an implementation of step S204 in the above-mentioned Example 4. As shown in FIG. 6 , step S204 may include but is not limited to the following steps:

[0102] Step S2041: Determine based on the capability parameter that the user equipment has the capability to access the second network, and obtain RRC release connection information, where the RRC release connection information carries a redirection parameter, which is used to assist the user equipment in accessing the second network.

[0103] Acquiring RRC release connection information is a specific implementation method of acquiring the second release parameter.

[0104] In this embodiment, the RRC connection release message (RRCRelease) is a message defined in the communication protocol. The redirection parameter carried in the RRC connection release message is also a parameter defined in the communication protocol.

[0105] The RRC release connection information corresponds to the user equipment.

[0106] Accordingly, step S205 may include but is not limited to:

[0107] Step S2051: Send RRC connection release information to the user equipment, so that the user equipment stops accessing the first network based on the RRC connection release information and accesses the second network based on the redirection parameter.

[0108] In this embodiment, by obtaining the capability parameters of the user equipment; the type of the user equipment is a reduced capability type, an abnormal communication scenario in which the capability parameters do not correspond to the type of the user equipment is determined, and for the abnormal communication scenario, a first release parameter is obtained, and the user equipment access to the first network is terminated based on the first release parameter. Furthermore, it can be determined based on the capability parameters that the user equipment has the ability to access the second network, and the RRC release connection information is sent to the user equipment, so that the user equipment stops accessing the first network based on the RRC release connection information, and accesses the second network based on the redirection parameter, which can effectively reduce the number and frequency of invalid accesses of the user equipment in the first network, and reduce the abnormal impact on the wireless KPI indicators.

[0109] For example, if the access network device is a base station, and the base station includes a CU and a DU, the signaling processing flow after optimization of the access network device can be referred to FIG7 . As shown in FIG7 , in the initial access process, if the CU determines that the UE (i.e., an implementation method of the user equipment) carries a RedCap terminal identifier in the UE access message, the UE RRC establishment process, NAS authentication, NAS security, RRC security process, and UE capability query process are normally completed;

[0110] The above-mentioned initial access process, UE RRC establishment process, completion of NAS authentication, NAS security, RRC security process, and UE capability query process can be referred to the initial access process, UE RRC establishment process, completion of NAS authentication, NAS security, RRC security process, and UE capability query process in the 3GPP 5G protocol in the prior art, and will not be repeated here.

[0111] After determining that the capability parameters do not correspond to the type of user equipment, the exception handling process is entered: the CU sends INITIAL CONTEXT SETUP FAILURE to the AMF, carrying the first cause value of "Insufficient UE Capabilities"; among them, INITIAL CONTEXT SETUP FAILURE comes from TS 38.413 in the 3GPP 5G protocol.

[0112] The CU sends a UE Context Release Command to the DU, carrying the second cause value of "Insufficient UE Capabilities". The UE Context Release Command comes from TS 38.473 in the 3GPP 5G protocol.

[0113] If it is determined based on the capability parameters that the user equipment has the "eutra" capability, the CU sends an RRCRelease message carrying "redirectionCarrierInfo" to the UE through the DU; among them, the "redirectionCarrierInfo" and RRCRelease message come from the TS 38.331 part of the 3GPP 5G protocol.

[0114] As another optional embodiment of the present application, a communication method is provided in Example 6 of the present application. This embodiment is mainly an implementation method of the redirection parameters in Example 5 above. The redirection parameters may include but are not limited to:

[0115] Redirect frequency.

[0116] The redirected frequency point is used to enable the user equipment to search for and access the second network.

[0117] Corresponding to the implementation method where the first network is a 5G network, the second network can be a 4G network, and the redirection frequency can be determined based on the Eutra frequency configured by the 5G base station and the frequency band information (Bandlist) supported by the user equipment.

[0118] Redirect parameters may also include but are not limited to:

[0119] Redirection frequency and its working parameters.

[0120] The working parameters of the redirected frequency can be used to select a target cell from at least one cell of the second network corresponding to the redirected frequency, and access the target cell of the second network based on the redirected frequency.

[0121] In this embodiment, by obtaining the capability parameters of the user equipment; the type of the user equipment is a reduced capability type, an abnormal communication scenario in which the capability parameters do not correspond to the type of the user equipment is determined, and for the abnormal communication scenario, a first release parameter is obtained, and the user equipment access to the first network is terminated based on the first release parameter. Furthermore, it can be determined based on the capability parameters that the user equipment has the ability to access the second network, and the RRC release connection information is obtained and sent to the user equipment, so that the user equipment stops accessing the first network based on the RRC release connection information, and accesses the second network based on the redirected frequency point, which can effectively reduce the number and frequency of invalid accesses of the user equipment in the first network, and reduce the abnormal impact on the wireless KPI indicators.

[0122] As another optional embodiment of the present application, referring to FIG8 , which is a flow chart of a communication method provided in Example 7 of the present application, as shown in FIG8 , the method may include but is not limited to the following steps:

[0123] Step S301: Acquire capability parameters of a user equipment; the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network.

[0124] Step S302: Determine that the capability parameter does not correspond to the type of the user equipment, and obtain a first release parameter.

[0125] Step S303: End the user equipment's access to the first network based on the first release parameter.

[0126] Step S304: Determine based on the capability parameter that the user equipment has the capability to access the second network, and obtain a second release parameter.

[0127] Step S305: Enable the user equipment to access the second network based on the second release parameter.

[0128] The detailed process of steps S301-S305 can be found in the relevant introduction of steps S201-S205 in Example 4, and will not be repeated here.

[0129] Step S306: Determine based on the capability parameter that the user equipment does not have the capability to access the second network, and obtain a third release parameter.

[0130] In an implementation where the first network is a 5G network and the second network is a 4G network, if the capability parameters of the user equipment do not include "Rat-Type: eutra" information, it can be determined that the user equipment does not have the ability to access the 4G network. Of course, the implementation of determining that the user equipment does not have the ability to access the second network based on the capability parameters is not limited to this.

[0131] In an abnormal communication scenario where the capability parameter does not correspond to the type of the user equipment, the third release parameter may be, but is not limited to, a parameter defined in the communication protocol.

[0132] Step S307: Based on the third release parameter, the user equipment enters a waiting state. In the waiting state, the user equipment does not request to access the first network.

[0133] In this embodiment, by obtaining the capability parameters of the user equipment; the type of the user equipment is a reduced capability type, an abnormal communication scenario in which the capability parameters do not correspond to the type of the user equipment is determined, and for the abnormal communication scenario, a first release parameter is obtained, and the user equipment access to the first network is terminated based on the first release parameter. Furthermore, it can be determined based on the capability parameters that the user equipment has the ability to access the second network, and the RRC release connection information is obtained and sent to the user equipment, so that the user equipment stops accessing the first network based on the RRC release connection information, and accesses the second network based on the redirected frequency point, which can effectively reduce the number and frequency of invalid accesses of the user equipment in the first network, and reduce the abnormal impact on the wireless KPI indicators.

[0134] Based on the capability parameter, it is determined that the user equipment does not have the ability to access the second network, a third release parameter is obtained, and based on the third release parameter, the user equipment enters a waiting state. In the waiting state, the user equipment does not request access to the first network. This can avoid frequent requests for access to the first network in abnormal communication scenarios where the capability parameter does not correspond to the type of the user equipment, thereby reducing signaling overhead.

[0135] As another optional embodiment of the present application, a communication method is provided in Example 8 of the present application. This embodiment is mainly an implementation method for obtaining the third release parameter in Example 7. Obtaining the third release parameter may include but is not limited to the following steps:

[0136] Step S3061: Acquire RRC connection release information, where the RRC connection release information carries a wait instruction, which is used to prompt the user equipment to enter a wait state.

[0137] In this embodiment, the RRC connection release information (RRCRelease) is a message defined in the communication protocol.

[0138] In this embodiment, the waiting instruction may be "waitTime" information defined in the communication protocol, and the "waitTime" information may indicate the waiting time.

[0139] The RRC release connection information corresponds to the user equipment.

[0140] Accordingly, step S307 may include but is not limited to:

[0141] Step S3071: Send RRC connection release information to the user equipment, so that the user equipment enters a waiting state based on the waiting instruction. In the waiting state, the user equipment does not request to access the first network.

[0142] In the implementation method where the corresponding waiting instruction is the "waitTime" information, when the duration of the user equipment in the waiting state reaches the waiting duration indicated by the "waitTime" information, the user equipment may end the waiting.

[0143] In this embodiment, it is determined based on the capability parameter that the user equipment does not have the ability to access the second network, and RRC release connection information is obtained. The RRC release connection information carries a waiting instruction. The RRC release connection information is information defined in the communication protocol. The RRC release connection information is sent to the user equipment, so that the user equipment enters a waiting state based on the waiting instruction. In the waiting state, the user equipment does not request access to the first network, which can avoid frequent requests for access to the first network in abnormal communication scenarios where the capability parameter does not correspond to the type of the user equipment, thereby reducing signaling overhead.

[0144] For example, if the access network device is a base station, and the base station includes a CU and a DU, the optimized signaling processing flow of the access network device can be referred to FIG9 . As shown in FIG9 , in the initial access process, if the CU determines that the UE (i.e., an implementation method of the user equipment) carries a RedCap terminal identifier in the UE access message, the UE RRC establishment process, NAS authentication, NAS security, RRC security process, and UE capability query process are normally completed;

[0145] The above-mentioned initial access process, UE RRC establishment process, completion of NAS authentication, NAS security, RRC security process, and UE capability query process can be referred to the initial access process, UE RRC establishment process, completion of NAS authentication, NAS security, RRC security process, and UE capability query process in the 3GPP 5G protocol in the prior art, and will not be repeated here.

[0146] After determining that the capability parameters do not correspond to the type of user equipment, the exception handling process is entered: the CU sends INITIAL CONTEXT SETUP FAILURE to the AMF, carrying the first cause value of "Insufficient UE Capabilities"; among them, INITIAL CONTEXT SETUP FAILURE comes from TS 38.413 in the 3GPP 5G protocol.

[0147] The CU sends a UE Context Release Command to the DU, carrying the second cause value of "Insufficient UE Capabilities". The UE Context Release Command comes from TS 38.473 in the 3GPP 5G protocol.

[0148] If it is determined based on the capability parameters that the user equipment has the "eutra" capability, the CU sends an RRCRelease message carrying "redirectionCarrierInfo" to the UE through the DU; among them, the "redirectionCarrierInfo" and RRCRelease message come from the TS 38.331 part of the 3GPP 5G protocol.

[0149] If it is determined based on the capability parameters that the user equipment does not have the "eutra" capability, the CU sends an RRCRelease message carrying "waitTime" to the UE through the DU; among them, the "waitTime" and RRCRelease message come from the TS 38.331 part of the 3GPP 5G protocol.

[0150] Among them, the interaction process between UE, CU, DU and AMF can be seen in Figure 10. As shown in Figure 10, DU determines whether the type of user equipment is RedCap through the dedicated PRACH opportunity where MSG1 / MSGA is located, or determines whether the type of user equipment is RedCap through the LCID used by the user equipment;

[0151] If the user device type is not RedCap, the CU can perform the normal device establishment process;

[0152] If the type of the user equipment is RedCap, the CU determines whether the UE capability supports RedCap. If so, the AMF and DU perform the corresponding RedCap registration establishment process; if not, the CU sends an INITIAL CONTEXT SETUP FAILURE to the AMF, carrying "Insufficient UE Capabilities"; the CU sends a UE Context Release Command to the DU, carrying "Insufficient UE Capabilities";

[0153] CU determines whether UE capabilities support ertra;

[0154] If ertra is supported, the CU selects the redirection frequency, the DU releases the UE Context, and sends an RRCRelease message carrying "redirectionCarrierInfo" to the UE;

[0155] The UE stops accessing the first network based on the RRCRelease message and accesses the second network based on the "redirectionCarrierInfo";

[0156] If ertra is not supported, the DU releases the UE Context and sends an RRCRelease message carrying "waitTime" to the UE;

[0157] The UE enters the waiting state based on the RRCRelease message carrying the "waitTime", and the user equipment does not request to access the first network in the waiting state.

[0158] Next, a communication device provided by the present application is introduced. The communication device introduced below and the communication method introduced above can refer to each other.

[0159] 11 , the communication device includes a first acquisition module 100 , a second acquisition module 200 and a first control module 300 .

[0160] A first acquisition module 100 is configured to acquire capability parameters of a user equipment; the type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network;

[0161] A second acquisition module 200 is configured to determine that the capability parameter does not correspond to the type of the user equipment and acquire a first release parameter;

[0162] The first control module 300 is configured to terminate the user equipment's access to the first network based on a first release parameter.

[0163] The process of the second acquiring module 200 acquiring the first release parameter may specifically include:

[0164] Obtaining a message of an initial context establishment failure, where the message of the initial context establishment failure carries a first cause value, where the first cause value is used to indicate that a capability parameter represents insufficient capability of the user equipment to access the first network;

[0165] A user equipment context release command is obtained, where the user equipment context release command carries a second cause value, where the second cause value is used to indicate that a capability parameter represents insufficient capability of the user equipment to access the first network.

[0166] The first control module 300 may be specifically configured to:

[0167] Sending a message indicating that the initial context establishment has failed to the access and mobility management function network element of the first network, so that the access and mobility management function network element ends establishing the context with the user equipment;

[0168] A user equipment context release command is sent to the distribution unit of the access network device, so that the distribution unit ends establishing the context with the user equipment.

[0169] In this embodiment, the communication device may further include:

[0170] a third acquisition module, configured to determine, based on the capability parameter, that the user equipment has the capability of accessing the second network, and acquire a second release parameter;

[0171] The second control module is configured to enable the user equipment to access the second network based on a second release parameter.

[0172] The process of the third acquiring module acquiring the second release parameter may specifically include:

[0173] RRC release connection information is obtained, where the RRC release connection information carries a redirection parameter, and the redirection parameter is used to assist the user equipment in accessing the second network.

[0174] Redirection parameters, which can include:

[0175] Redirect frequency;

[0176] Or, the redirection frequency and the working parameters of the redirection frequency.

[0177] The communication device may further include:

[0178] a fourth acquisition module, configured to determine, based on the capability parameter, that the user equipment does not have the capability to access the second network, and acquire a third release parameter;

[0179] The third control module is configured to enable the user equipment to enter a waiting state based on a third release parameter, wherein the user equipment does not request to access the first network in the waiting state.

[0180] The process of the fourth acquiring module acquiring the third release parameter may specifically include:

[0181] The RRC release connection information is obtained, where the RRC release connection information carries a waiting instruction, and the waiting instruction is used to prompt the user equipment to enter a waiting state.

[0182] Corresponding to the above-mentioned communication method embodiment provided by the present application, the present application also provides an access network device.

[0183] Access network equipment, including:

[0184] at least one distribution unit;

[0185] Centralized unit for:

[0186] Acquiring capability parameters of a user device; the type of the user device is a reduced capability type, the type of the user device allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network;

[0187] Determining that the capability parameter does not correspond to the type of the user equipment, and obtaining a first release parameter;

[0188] The access of the user equipment to the first network is terminated based on the first release parameter.

[0189] It should be noted that each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to in detail. For the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0190] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0191] For the convenience of description, the above devices are described as being divided into various modules according to their functions. Of course, when implementing this application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0192] Through the description of the above embodiments, it can be seen that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or an access network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of the present application.

[0193] The above is a detailed introduction to a communication method, device and access network equipment provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core ideas. At the same time, for general technical personnel in this field, based on the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A communication method, comprising: Obtain capability parameters of user equipment; The type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network; Determining that the capability parameter does not correspond to the type of the user equipment, and obtaining a first release parameter; The access of the user equipment to the first network is terminated based on the first release parameter.

2. The communication method according to claim 1, wherein obtaining the first release parameter comprises: Obtaining a message of an initial context establishment failure, where the message of the initial context establishment failure carries a first cause value, where the first cause value is used to indicate that the capability parameter represents insufficient capability of the user equipment to access the first network; A user equipment context release command is obtained, where the user equipment context release command carries a second cause value, where the second cause value is used to prompt that the capability parameter represents insufficient capability of the user equipment to access the first network.

3. The communication method according to claim 2, wherein terminating the user equipment's access to the first network based on the first release parameter comprises: Sending a message indicating that the initial context establishment has failed to the access and mobility management function network element of the first network, so that the access and mobility management function network element ends establishing the context with the user equipment; The user equipment context release command is sent to a distribution unit of an access network device, so that the distribution unit ends establishing the context with the user equipment.

4. The communication method according to claim 1, further comprising: Determining, based on the capability parameter, that the user equipment has the capability of accessing the second network, and acquiring a second release parameter; The user equipment is enabled to access the second network based on the second release parameter.

5. The communication method according to claim 4, wherein obtaining the second release parameter comprises: Acquire RRC release connection information, where the RRC release connection information carries a redirection parameter, and the redirection parameter is used to assist the user equipment in accessing the second network.

6. The communication method according to claim 5, wherein the redirection parameter comprises: Redirect frequency; Or, the redirection frequency and the working parameters of the redirection frequency.

7. The communication method according to claim 4, further comprising: Determining, based on the capability parameter, that the user equipment does not have an ability to access the second network, and acquiring a third release parameter; The user equipment is caused to enter a waiting state based on the third release parameter, and in the waiting state, the user equipment does not request to access the first network.

8. The communication method according to claim 7, wherein obtaining the third release parameter comprises: RRC release connection information is obtained, where the RRC release connection information carries a waiting instruction, and the waiting instruction is used to prompt the user equipment to enter a waiting state.

9. A communication device comprising: A first acquisition module, configured to acquire capability parameters of a user equipment; The type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network; a second acquisition module, configured to determine that the capability parameter does not correspond to the type of the user equipment, and acquire a first release parameter; A first control module is configured to terminate the user equipment's access to the first network based on the first release parameter.

10. An access network device, comprising: at least one distribution unit; Centralized unit for: Obtain capability parameters of user equipment; The type of the user equipment is a reduced capability type, the type of the user equipment allows access to a first network and a second network, and the network standard of the first network is higher than the network standard of the second network; Determining that the capability parameter does not correspond to the type of the user equipment, and obtaining a first release parameter; The access of the user equipment to the first network is terminated based on the first release parameter.

Images