Communication configuration, communication configuration methods, devices, terminals, base stations and communication systems

Abstract

This invention provides a communication configuration, method, apparatus, terminal, base station, and communication system. The base station configures service QoS characteristic parameters for the terminal, allowing the terminal to determine whether it can enter the RRC (Restricted Routing Control) connection state. Based on the service QoS characteristic parameters configured by the base station, the terminal can implement access control, ensuring that it enters the RRC connection state and acquires the corresponding communication resources when requirements are met, thereby enabling communication. If the terminal's own service QoS characteristic parameters do not meet the requirements, it temporarily does not enter the RRC connection state, which facilitates the utilization of communication resources and achieves optimized configuration of communication resources.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a communication configuration, a communication configuration method, a device, a terminal, a base station, and a communication system. Background Art

[0002] With the development of communication technologies and the enrichment of requirements, and the increasingly complete formulation of the fifth-generation communication technology standards, the application scenarios of wireless communication have gradually penetrated into vertical industries, and the application scenario of the Internet of Vehicles is relatively typical. Currently, the vehicle networking standard based on eLTE (Enhanced LTE) of Release 15 has been specified, and the vehicle networking technology (V2X, vehicle to everything) based on NR of Release 16 has been announced for research. The vehicle networking technology based on NR not only meets the existing basic safety-related services, but also adds support for many advanced services, such as remote driving and platooning.

[0003] For V2X terminals, how to perform access control and how to determine whether a terminal enters the RRC (Radio Resource Control) connection state are issues that need to be considered urgently at present. Summary of the Invention

[0004] A communication configuration, a communication configuration method, a device, a terminal, a base station, and a communication system provided by an embodiment of the present invention mainly solve the technical problem of how to control whether a terminal enters the RRC connection state for communication.

[0005] To solve the above technical problem, an embodiment of the present invention further provides a communication method, including:

[0006] Determining whether to enter the radio resource control RRC connection state through service QoS (Quality of Service) characteristic parameters.

[0007] An embodiment of the present invention provides a communication configuration method, including:

[0008] Configuring service QoS characteristic parameters for a terminal, and the service QoS characteristic parameters are used for the terminal to determine whether to enter the RRC connection state.

[0009] An embodiment of the present invention further provides a communication device, including:

[0010] A connection module, configured to determine whether to enter the RRC connection state through service QoS characteristic parameters.

[0011] An embodiment of the present invention further provides a communication configuration device, including:

[0012] The configuration module is used to configure the QoS (Quality of Service) characteristic parameters for the terminal. These QoS characteristic parameters are used by the terminal to determine whether it can enter the RRC (Relational Rate Control) connection state.

[0013] This invention also provides a terminal, which includes a second processor, a second memory, and a second communication bus;

[0014] The second communication bus is used to realize the connection and communication between the second processor and the second memory;

[0015] The second processor is used to execute one or more programs stored in the second memory to implement the steps of the above-described communication method.

[0016] This invention also provides a base station, which includes a first processor, a first memory, and a first communication bus;

[0017] The first communication bus is used to realize the connection and communication between the first processor and the first memory;

[0018] The first processor is used to execute one or more programs stored in the first memory to implement the steps of the above-described communication configuration method.

[0019] This invention also provides a communication system, including the aforementioned base station and at least one of the aforementioned terminals.

[0020] This invention also provides a computer storage medium storing at least a communication configuration program and / or a communication program, wherein the communication configuration program can be executed by one or more processors to implement the steps of the above-described communication configuration method; and the communication program can be executed by one or more processors to implement the steps of the above-described communication method.

[0021] The beneficial effects of this invention are:

[0022] The communication configuration, method, apparatus, terminal, base station, and communication system provided in this invention configure service QoS characteristic parameters for the terminal through the base station. The terminal can determine whether it can enter the RRC connection state through these service QoS characteristic parameters. Based on the service QoS characteristic parameters configured by the base station for the terminal, the terminal can implement access control, ensuring that it enters the RRC connection state and obtains the corresponding communication resources when the requirements are met, thereby realizing communication. When the terminal's own service QoS characteristic parameters do not meet the requirements, it temporarily does not enter the RRC connection state, which is beneficial for the utilization of communication resources and achieves optimized configuration of communication resources.

[0023] Other features and corresponding beneficial effects of the present invention will be described in the latter part of the specification, and it should be understood that at least some of the beneficial effects will become obvious from the description in the specification. Attached Figure Description

[0024] Figure 1 This is an interaction diagram between a base station and a terminal in the communication scheme provided in Embodiment 1 of the present invention;

[0025] Figure 2 This is a flowchart of a terminal determining whether it can enter the RRC connection state, as provided in Embodiment 1 of the present invention;

[0026] Figure 3 This is a schematic diagram of a V2X cellular network architecture provided in Embodiment 2 of the present invention;

[0027] Figure 4 This is an interaction diagram between a base station and a terminal in the communication scheme provided in Embodiment 2 of the present invention;

[0028] Figure 5 This is a schematic diagram of a communication configuration device provided in Embodiment 3 of the present invention;

[0029] Figure 6 This is a schematic diagram of a communication device provided in Embodiment 3 of the present invention;

[0030] Figure 7 This is a schematic diagram of a hardware structure of a base station provided in Embodiment 4 of the present invention;

[0031] Figure 8 This is a schematic diagram of a hardware structure of a terminal provided in Embodiment 4 of the present invention;

[0032] Figure 9 This is a schematic diagram of a communication system provided in Embodiment 4 of the present invention;

[0033] Figure 10 This is a flowchart illustrating how a terminal can access the network, as shown in Example 5 of Embodiment 5 of the present invention. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this invention clearer, the embodiments of this invention will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0035] Example 1:

[0036] To achieve access control of V2X terminals and ensure optimal allocation of communication resources, this embodiment provides a communication scheme. This scheme includes a communication configuration method implemented on the base station side and a communication method implemented on the terminal side. Please refer to [link to relevant documentation]. Figure 1 The diagram shown illustrates the interaction between the base station and the terminal:

[0037] S102: The base station configures service QoS characteristic parameters for the terminal.

[0038] The service QoS characteristic parameter is used to allow the terminal to determine whether it can currently enter the RRC connection state. In this embodiment, the service QoS characteristic parameter may include at least one of a class classification indicator and an access type. Those skilled in the art will understand that, in addition to including the class classification indicator and / or the access type corresponding to the service, the service QoS characteristic parameter may further include the terminal's access identifier. For example, the base station can configure an access identifier for the terminal, and terminals that agree with the terminal that their access identifier is a predetermined identifier can directly enter the RRC connection state. Therefore, for the terminal, it can determine whether it can enter the RRC connection state by judging whether its access identifier is a predetermined identifier. Typically, the base station configures an access identifier for ordinary communication terminals; in this embodiment, the base station can additionally configure an access identifier for V2X terminals.

[0039] The classification indicator enables the terminal to determine which service attribute characteristics are high-level and which are low-level. The service attribute characteristics referred to here include any one of the following:

[0040] QoS level;

[0041] QoS index;

[0042] The default priority level (DPL) for data packets.

[0043] In 5G communication systems, the QoS index can be a 5G QoS index, also known as 5QI. Of course, those skilled in the art will understand that in other communication systems besides 5G, the QoS index can also be other types of indication information.

[0044] "QoS level" can characterize the level of QoS requirement to a certain extent. For example, "QoS hierarchy1 (QoS level 1)", "QoS hierarchy2 (QoS level 2)", etc., where QoS level 1 represents the highest QoS requirement, QoS level 2 represents the next highest, and so on. The larger the QoS level value, the lower the QoS requirement corresponding to the QoS level, and vice versa. This mapping relationship can reflect the correspondence between QoS level and first parameter, with one QoS level corresponding to at least one first parameter. Furthermore, in the mapping relationship of this embodiment, at least one QoS level corresponds to at least two first parameters simultaneously. Of course, in the mapping relationships configured in some example base stations, each QoS level corresponds to two or more first parameters simultaneously.

[0045] The first parameter mentioned above can refer to any parameter in the mapping relationship between the QoS index and the QoS parameter group. For example, the first parameter can be either the QoS index or the default priority level of the data packet in the QoS parameter group. That is, the mapping relationship configured by the base station can be a mapping relationship between the QoS level and the QoS index, or a mapping relationship between the QoS level and the default priority of the data packet.

[0046] In one example of this embodiment, the classification indication configured by the base station for the terminal may include at least one of the following:

[0047] First business attribute feature list;

[0048] Second business attribute feature list;

[0049] First-level threshold;

[0050] Second-level threshold.

[0051] The first service attribute feature list includes low-level service attribute features specified by the base station. Of course, those skilled in the art will understand that service attribute features not included in the first service attribute feature list naturally belong to high-level service attribute features.

[0052] The second service attribute feature list includes various high-level service attribute features specified by the base station. If the terminal determines that a certain service attribute feature does not exist in the second service attribute feature list, it means that the service attribute feature is a high-level service attribute feature.

[0053] Those skilled in the art will understand that the classification indicator may include only the first business attribute feature list or the second business attribute feature list, or it may include both the first business attribute feature list and the second business attribute feature list.

[0054] In some examples of this embodiment, the level classification indicator can be a first level threshold, which is used to indicate that business attribute features with a level lower than the first level threshold are low-level business attribute features.

[0055] In other examples of this embodiment, the level classification indicator can be a second level threshold, which is used to indicate that business attribute features with a level higher than the second level threshold are high-level business attribute features.

[0056] It is understandable that the first-level threshold and the second-level threshold can be the same or different: if the first-level threshold and the second-level threshold are the same, then business attribute features with a level lower than the threshold are low-level business attribute features, and business attribute features with a level higher than the threshold are high-level business attribute features.

[0057] It should be understood that for the two service attribute characteristics, QoS level and default packet priority level, the larger the level value, the lower the corresponding level, and the smaller the level value, the higher the corresponding level. Taking the default packet priority as an example: a value of "1" has a higher priority than a value of "2". Therefore, for the two service attribute characteristics of QoS level and default packet priority level, service attribute characteristics with a level below the first level threshold actually refer to service attribute characteristics with a level value greater than the first level threshold; service attribute characteristics with a level above the second level threshold actually refer to service attribute characteristics with a level value less than the first level threshold.

[0058] In some examples of this embodiment, the base station can send a class classification indication to the terminal via a system broadcast message. In some examples of this embodiment, the class classification indication is indicated by a QoS index. Of course, the base station can also send the class classification indication to the terminal via signaling messages, etc. When the base station sends a class classification indication via a system broadcast message, the terminal will also obtain the class classification indication via the system broadcast message.

[0059] S104: The terminal determines whether it can enter the RRC connection state by using the service QoS characteristic parameters.

[0060] After determining the service QoS characteristic parameters configured for it by the base station, the terminal can determine whether it can enter the RRC connection state based on these service QoS characteristic parameters.

[0061] Assuming the service QoS characteristic parameters configured on the base station are level classification indicators, the terminal can refer to... Figure 2 The flowchart shown is used to determine whether to enter the RRC connection state:

[0062] S202: The terminal determines the low-level service attribute characteristics and high-level service attribute characteristics according to the level classification instruction;

[0063] S204: The terminal determines whether it can enter the RRC connection state to obtain dedicated resources based on the service characteristics of the current service.

[0064] The terminal first determines whether its current service belongs to a high-level service attribute or a low-level service attribute based on the level classification instruction, and then determines whether it can enter the RRC connection state based on the current service attribute characteristics.

[0065] In one example of this embodiment, if the terminal determines that the service attributes of all its current services belong to low-level service attribute characteristics, it cannot enter the RRC connection state to obtain dedicated resources. If the terminal's current service attributes of at least one service belong to high-level service attribute characteristics, it determines that it can enter the RRC connection state to obtain dedicated resources.

[0066] It is understood that in other examples of this embodiment, the terminal may also determine whether to enter the RRC connection state based on other judgment principles. For example, the terminal may determine whether to enter the RRC connection state only when it determines that all of its current services have high-level service attribute characteristics; if the terminal determines that at least one of its current services has low-level service attribute characteristics, it may determine that it cannot enter the RRC connection state temporarily.

[0067] The above explanation clarifies that the service QoS characteristic parameters configured by the base station are level classification indicators. In other examples of this embodiment, the service QoS characteristic parameters configured by the base station are the access types corresponding to the services, and the access types configured by the base station for the terminals correspond to the service QoS characteristics. For this situation, this embodiment provides the following two solutions:

[0068] Option 1 involves the base station configuring access types corresponding to the QoS characteristics of various services for the terminal, and configuring corresponding feature factors for each access type. These feature factors can limit the access probability corresponding to the access type to a certain extent. The terminal can then determine whether it can enter the RRC connection state based on the feature factors corresponding to the access type of its current service.

[0069] In this embodiment, the size of the feature factor corresponding to the access type can be configured by the base station according to the QoS characteristics (i.e., the QoS requirements of the service) corresponding to the access type. For example, for services with high QoS requirements, the feature factor value corresponding to the access type is smaller, and conversely, for services with low QoS requirements, the feature factor value corresponding to the access type is larger. In this embodiment, the feature factor takes the value (0,1).

[0070] For a terminal, after determining the access type and feature factor configured by the base station for each service, it can generate a random number. If the generated random number is greater than or equal to the feature factor corresponding to the current service access type, it indicates that it is currently allowed to enter the RRC connection state; if the generated random number is less than the feature factor corresponding to the current service access type, it indicates that it is currently temporarily unable to enter the RRC connection state.

[0071] Understandably, when configuring service QoS feature parameters, base stations configure the feature factors corresponding to access types based on the principle that QoS requirements and feature factor values ​​are negatively correlated. Therefore, access types corresponding to services with low QoS requirements have higher feature factor values, while access types corresponding to services with high QoS requirements have lower feature factor values. In this case, when determining whether a terminal can enter the RRC connection state, it can only be allowed to enter the RRC connection state if the random number is greater than or equal to the feature factor corresponding to the current service access type; otherwise, it cannot enter the RRC connection state. This is because only in this way can services with high QoS requirements have a higher probability of access, while services with low QoS requirements have a relatively lower probability of access.

[0072] In other examples of this embodiment, when the base station configures feature factor values ​​for service access types, the feature factor value corresponding to the access type is larger for services with higher QoS requirements, and conversely, the feature factor value corresponding to the access type is smaller for services with lower QoS requirements.

[0073] For a terminal, after determining the access type and feature factor configured by the base station for each service, it can generate a random number. If the generated random number is less than or equal to the feature factor corresponding to the current service access type, it indicates that it is currently allowed to enter the RRC connection state; if the generated random number is greater than the feature factor corresponding to the current service access type, it indicates that it is currently temporarily not allowed to enter the RRC connection state.

[0074] Understandably, when configuring service QoS feature parameters, base stations configure the feature factors corresponding to access types based on the principle that QoS requirements are positively correlated with feature factor values. Therefore, access types corresponding to services with low QoS requirements have smaller feature factor values, while access types corresponding to services with high QoS requirements have larger feature factor values. In this situation, when determining whether a terminal can enter the RRC connection state, it can only be allowed to enter the RRC connection state if the random number is less than the feature factor corresponding to the current service access type; otherwise, it cannot enter the RRC connection state. This is because only in this way can services with high QoS requirements have a higher access probability, while services with low QoS requirements have a relatively lower access probability.

[0075] Option 2: The base station can configure corresponding access types for each service and indicate the QoS level corresponding to each access type to the terminal. After determining the QoS level corresponding to the current service, the terminal can determine whether it can enter the RRC connection state based on the QoS level of the current service.

[0076] In this embodiment, services with higher QoS requirements have smaller QoS level values, while services with lower QoS requirements have larger QoS level values. To ensure a high probability of access when the terminal processes services with high QoS requirements, in this embodiment, when determining whether the terminal can enter the RRC connection state, it can first generate a random number. If the generated random number is less than or equal to the reciprocal of the QoS level, that is, less than or equal to 1 / QoS level, then it is determined that the terminal can enter the RRC connection state; otherwise, it is determined that the terminal cannot enter the RRC connection state.

[0077] In some examples of this embodiment, if the service QoS feature parameters configured by the base station include access type and feature factor or QoS level corresponding to access type, the base station will also configure the blocking duration corresponding to access type for the terminal. The blocking duration is used by the terminal to determine the total blocking duration when it determines that it cannot enter the RRC connection state.

[0078] In one example of this embodiment, when the terminal determines that it cannot enter the RRC connection state, it can determine the total blocking duration according to the following formula:

[0079] T = (0.7 + 0.6 * a) * T0

[0080] Where T is the total blocking duration, T0 is the blocking duration configured by the base station for the current access type of the service, and a is a feature factor, or the reciprocal of the QoS level (i.e., 1 / QoS level).

[0081] In some examples of this embodiment, when the terminal determines that it cannot enter the RRC connection state, it can also determine the total blocking duration according to the following formula:

[0082] T = (0.7 + 0.6 * random number * a) * T0

[0083] Here, 'a' can also be a feature factor, or the reciprocal of the QoS level (i.e., 1 / QoS level).

[0084] After determining the total blocking duration T, the terminal starts timing according to T. Until the timing is complete, it cannot enter the RRC connection state. Typically, the terminal does not need to re-determine whether it can enter the RRC connection state before the timing is complete. After the timing is complete, the terminal can re-determine whether it can enter the RRC connection state.

[0085] The terminal in this embodiment can be a V2X (vehicle to X, i.e., vehicle to everything, Internet of Vehicles) terminal, or other types of terminals. That is, the communication configuration method and communication method provided in this embodiment can be applied not only to the Internet of Vehicles field, but also to other fields.

[0086] The communication configuration method and communication method provided in this embodiment enable the terminal to perform access control based on the service QoS feature parameters configured by the base station. This ensures that when the service QoS feature parameters meet the requirements, the terminal controls itself to enter the RRC connection state to obtain the corresponding communication resources, thereby realizing communication. When the service QoS feature parameters do not meet the requirements, the terminal temporarily does not enter the RRC connection state, thereby achieving full utilization and optimized configuration of communication resources.

[0087] Example 2:

[0088] With the continuous improvement of industry standards for fifth-generation communication technology, the R15 version of the vehicle-to-everything (V2X) standard based on eLTE has been finalized, and the R16 version of the V2X standard based on NR has been announced for research and development.

[0089] The term "vehicle-to-everything (V2X)" refers to the ability of vehicles to participate in wireless communication. Please refer to [link to relevant documentation]. Figure 3The illustrated V2X cellular network architecture utilizes wireless cellular communication technology to enable real-time information exchange between vehicles, between vehicles and roadside units, and between vehicles and pedestrians. This includes sharing current status (vehicle location, speed, and route) and road environment information (such as traffic congestion and sudden traffic accidents). This collaborative sensing and interaction provides various early warning messages to reduce traffic accidents. Building upon these existing basic safety services, fifth-generation communication technology also supports many advanced services, such as remote driving and platooning. For example, a vehicle can lead the platoon to save fuel.

[0090] It is understandable that different services have different QoS requirements. For services with high QoS requirements, the terminal should prioritize sending and ensure the quality of service transmission (e.g., reliability, rate, maximum latency requirements, etc.).

[0091] V2X terminals operate in two modes: base station-controlled mode (mode 1) and self-resource scheduling mode (mode 2). In base station-controlled mode, whenever a terminal needs to communicate, it requests resources from the base station, reporting the service type of the data packet to be transmitted, the required frequency, the data packet priority, and the data packet buffer size. The base station allocates appropriate resources to the terminal based on this information for data transmission. In self-resource scheduling mode, the terminal can sense the resource pool, determine its congestion level, and select appropriate resources for data transmission.

[0092] In LTE V2X technology, when a terminal performs carrier selection in self-resource scheduling mode, each carrier's resource pool has a corresponding resource pool busy / idle indicator (CBR). For each terminal, different PPPP (Packet Priority Package) priorities are configured with different PPPP-CBR threshold values. Therefore, the terminal compares the current resource pool's busy / idle status with the PPPP-CBR threshold values ​​corresponding to different packet priorities to determine whether the current packet can be transmitted using this resource pool. If not, the terminal needs to perform carrier reselection.

[0093] The NR (New Radio) Uu (Universal Mobile Communications System Air Interface) interface introduces 5QI (5G QoS Indicator). 5QI quantitatively describes the characteristics of 5G QoS. One 5QI value corresponds to a set of 5G QoS parameters, and each parameter in the 5G QoS parameter set represents the communication quality requirements for the corresponding 5QI value. The 5G QoS parameter set may include default priority level, packet delay budget (PDB), packet error rate (PER), default maximum data burst volume (MDBV), and default average transmission window. The base station can configure the mapping relationship between 5QI and the 5G QoS parameter set (hereinafter referred to as "5QI-5G QoS mapping relationship") for the terminal and indicate the communication resources corresponding to each 5QI. Thus, when the terminal has a data packet to send, it can determine which communication resources to use to send the data packet based on the corresponding 5QI value. The 5QI-5G QoS mapping relationship configured for the base station can be seen in Table 1:

[0094] Table 1

[0095]

[0096]

[0097]

[0098] As can be seen from the "5QI Value" column in Table 1 above, the 5QI values ​​in the 5QI-5G QoS mapping relationship are not continuous, and the magnitude of the 5QI value is unrelated to the QoS requirements represented by the parameters in the 5G QoS parameter group. There is no discernible pattern, which means that when the base station indicates the communication resources corresponding to the 5QI value to the terminal, it can only specify them on a single 5QI value basis, resulting in high signaling overhead. Similarly, in other communication systems, the mapping relationship between the QoS index and the QoS parameter group (hereinafter referred to as the "first mapping relationship") also exhibits situations where the QoS index values ​​are inconsistent and unrelated to the QoS levels represented by the QoS parameter group. This leads to the base station having to indicate communication resources for each QoS index, resulting in high signaling overhead and resource consumption. To solve this problem, this embodiment first provides a solution, please refer to... Figure 4 :

[0099] S402: The base station configures the mapping relationship between the QoS level and the first parameter for the terminal.

[0100] "QoS levels" can characterize the level of QoS requirements to a certain extent. For example, "QoS hierarchy 1 (QoS level 1)", "QoS hierarchy 2 (QoS level 2)", etc., where QoS level 1 represents the highest QoS requirement, QoS level 2 represents the next highest, and so on. The larger the QoS level value, the lower the QoS requirement corresponding to the QoS level, and vice versa. In this embodiment, the base station configures a mapping relationship between QoS levels and first parameters for the terminal (to distinguish it from the aforementioned first mapping relationship, the mapping relationship between QoS levels and first parameters will be referred to as the "second mapping relationship" in the following description). It can be understood that this second mapping relationship can reflect the correspondence between QoS levels and first parameters, with one QoS level corresponding to at least one first parameter. Furthermore, in the second mapping relationship of this embodiment, there is at least one QoS level that simultaneously corresponds to at least two first parameters. Of course, in the second mapping relationships configured in some example base stations, each QoS level simultaneously corresponds to two or more first parameters.

[0101] In this embodiment, the first parameter refers to one of the parameters in the mapping relationship between the QoS index and the QoS parameter group. For example, the first parameter can be the QoS index or the default priority in the QoS parameter group. Of course, those skilled in the art will understand that the first parameter can also be other parameters in the QoS parameter group, such as any one of packet delay estimation, packet error rate, maximum data capacity, and default average transmission window. The following description uses the QoS index (5QI) as the first parameter as an example. Please refer to Table 2 for a second mapping relationship:

[0102]

[0103] It is understandable that the first parameter, QoS index, actually refers to the second mapping relationship configured by the base station, which is the mapping relationship between QoS levels and QoS indexes. As can be seen from Table 2, each QoS level corresponds to multiple 5QI values. For example, the four QoS indices 5QI1, 5QI3, 5QI7, and 5QI10 belong to QoS level 1; while the three QoS indices 5QI2, 5QI4, and 5QI12 belong to QoS level 2... QoS level 4 corresponds to three QoS indices: 5QI9, 5QI11, and 5QI13. In this embodiment, the base station classifies 5QI1, 5QI3, 5QI7, and 5QI10 into QoS level 1 because the QoS requirements corresponding to these 5QIs are relatively high, as can be seen from the QoS requirements of each 5QI in Table 1. Similarly, the classification of the other 5QIs in Table 1 is also based on the QoS requirements of each 5QI.

[0104] Since data corresponding to the 5QIs with high QoS requirements needs to use high-QoS communication resources during transmission, while data corresponding to the 5QIs with low QoS requirements can use low-QoS communication resources, the base station classifies the 5QIs in Table 1 into corresponding QoS levels based on their respective QoS requirements. By indicating communication resources based on these QoS levels, the base station can still ensure that data corresponding to the 5QIs with high QoS requirements can use high-QoS communication resources during transmission, and data corresponding to the 5QIs with low QoS requirements can use low-QoS communication resources.

[0105] Meanwhile, because base stations indicate communication resources in units of QoS levels, once a base station indicates communication resources for a specific QoS level, the terminal can determine the communication resources corresponding to multiple 5QIs under that QoS level. For example, if the base station specifies that the communication resource corresponding to QoS level 3 is A, the terminal can determine that the data corresponding to the three QoS indices 5QI5, 5QI6, and 5QI8 should all be transmitted using communication resource A. This avoids the problem of the base station needing to indicate the communication resource corresponding to each 5QI to the terminal when indicating communication resources, thus avoiding the problem of excessive signaling interaction and communication resource consumption caused by the base station.

[0106] Although the first parameter in Table 2 is 5QI, and Table 2 is applied to 5G communication systems, it is undeniable that the first parameter can also be a QoS index applicable to other communication systems, such as the QoS index in a future communication system. Therefore, in some other examples of this embodiment, the mapping relationship between the QoS level configured by the base station and the first parameter can also be applied to other communication systems.

[0107] The following explanation uses the first parameter as the default priority as an example. Please refer to Table 3 for another second mapping relationship of base station configuration:

[0108]

[0109] Generally, the higher the default priority of the data to be transmitted, the higher the QoS of the communication resources used to transmit that data. Conversely, if the default priority of the data to be transmitted is low, lower QoS communication resources can be used for its transmission. Therefore, in Table 2, the base station maps higher default priorities (i.e., lower default priorities) to higher QoS levels (i.e., lower QoS levels), and lower default priorities (i.e., higher default priorities) to lower QoS levels (i.e., higher QoS levels). This way, when allocating resources, only higher QoS communication resources need to be allocated to higher QoS levels to ensure that data with higher default priorities can be transmitted using high QoS communication resources; and only lower QoS communication resources need to be allocated to lower QoS levels to ensure that data with lower default priorities can be transmitted using low QoS communication resources, thus ensuring optimal resource allocation.

[0110] Meanwhile, because the base station divides the default priority into intervals and establishes a mapping relationship between each interval and the QoS level, when the base station specifies communication resources to the terminal according to the QoS level, the terminal can determine the communication resources corresponding to multiple default priorities after the base station specifies the communication resources corresponding to one QoS level. This can also significantly reduce the signaling interaction of the base station to indicate communication resources.

[0111] Tables 2 and 3 illustrate the second mapping relationship configured by the base station, taking the first parameter as the QoS index and the default priority as examples, respectively. Those skilled in the art will understand that the base station can also create other second mapping relationships between the first parameter and the QoS level by referring to the foregoing description.

[0112] S404: The base station sends a resource indication message to the terminal.

[0113] After the base station configures the second mapping relationship between QoS levels and the first parameter for the terminal, the base station can send a resource indication message to the terminal. This resource indication message indicates communication resources to the terminal in units of QoS levels. That is, after receiving the resource indication message, the terminal can at least determine the communication resources corresponding to a certain QoS level. It is understood that in some examples of this embodiment, the base station can specify communication resources corresponding to two or more QoS levels to the terminal through a single resource indication message. For example, in one example of this embodiment, the base station can specify communication resources corresponding to all QoS levels to the terminal simultaneously by sending a single communication resource indication message.

[0114] After receiving the resource indication message, the terminal can determine the communication resource corresponding to the first parameter by combining the resource indication message and the second mapping relationship, thereby determining which communication resource should be used to send the data corresponding to the first parameter. Optionally, the terminal first determines the mapping relationship between the QoS level and the first parameter.

[0115] The terminal determines the mapping relationship between the QoS level and the first parameter, i.e., the second mapping relationship. This mapping relationship can be configured by the base station to the terminal via signaling, or it can be configured by default at both the base station and the terminal. In some examples of this embodiment, after configuring the second mapping relationship between the QoS level and the first parameter, the base station can send it to the terminal through a relationship indication message. After receiving the relationship indication message, the terminal parses the message to determine the mapping relationship configured by the base station and stores the mapping relationship for later use.

[0116] After determining the mapping relationship between the QoS level and the first parameter, the terminal receives the resource indication message sent by the base station.

[0117] After determining the mapping relationship between the QoS level and the first parameter, i.e., the second mapping relationship, the terminal can receive the resource indication message sent by the base station. Based on this resource indication message, the terminal can determine the communication resources corresponding to at least one QoS level, because in the second mapping relationship, one QoS level corresponds to two or even more first parameters simultaneously.

[0118] Finally, the terminal determines the resource based on the resource indication message and communicates.

[0119] The base station configures a mapping relationship between the Quality of Service (QoS) level and a first parameter for the terminal, and indicates communication resources to the terminal in units of QoS level when indicating communication resources. The first parameter refers to one of the parameters in the mapping relationship between the QoS index and the QoS parameter group. Since the mapping relationship configured by the base station contains at least one QoS level corresponding to at least two first parameters, that is, when indicating communication resources to the terminal in terms of QoS level, one communication resource simultaneously corresponds to at least two first parameters. The base station can indicate communication resources corresponding to at least two first parameters to the terminal through a single resource indication message. This significantly reduces signaling interaction in resource indication and lowers the base station's signaling overhead, compared to the situation in related technologies where a message can only indicate communication resources corresponding to one first parameter.

[0120] Example 3:

[0121] This embodiment provides a communication configuration device; please refer to [link / reference]. Figure 5 The communication configuration device 50 can be deployed on the base station side, and includes a configuration module 502. The configuration module 502 is used to configure the service quality (QoS) characteristic parameters for the terminal. The QoS characteristic parameters are used by the terminal to determine whether it can enter the RRC connection state.

[0122] This embodiment also provides a communication device. Figure 6 A schematic diagram of the communication device is shown. The communication device 60 includes a connection module 602, which is used to determine whether it can enter the RRC connection state through service QoS characteristic parameters.

[0123] The service QoS characteristic parameter is used by the connection module 602 to determine whether it can currently enter the RRC connection state. In this embodiment, the service QoS characteristic parameter may include at least one of a class classification indicator and the access type corresponding to the service. Those skilled in the art will understand that, in addition to including the class classification indicator and / or the access type corresponding to the service, the service QoS characteristic parameter may further include the terminal's access identifier. For example, the configuration module 502 can configure an access identifier for the terminal, and agree with the connection module 602 that terminals with a predetermined access identifier can directly enter the RRC connection state. Therefore, the connection module 602 can determine whether it can enter the RRC connection state by judging whether the terminal's access identifier is a predetermined identifier. Typically, the configuration module 502 configures access identifiers for ordinary communication terminals; in this embodiment, the configuration module 502 can add an access identifier for the V2X terminal.

[0124] The level classification indicator enables the connection module 602 to determine which service attribute characteristics are high-level service attribute characteristics and which are low-level service attribute characteristics. The service attribute characteristics referred to here include any one of the following:

[0125] QoS level;

[0126] QoS index;

[0127] The default priority level for data packets.

[0128] In 5G communication systems, the QoS index can be a 5G QoS index, also known as 5QI. Of course, those skilled in the art will understand that in other communication systems besides 5G, the QoS index can also be other types of indication information.

[0129] "QoS levels" can characterize the level of QoS requirements to a certain extent. For example, "QoS hierarchy 1", "QoS hierarchy 2", etc., where QoS level 1 represents the highest QoS requirement, QoS level 2 represents the next highest, and so on. The larger the QoS level value, the lower the corresponding QoS requirement, and vice versa. This mapping relationship reflects the correspondence between QoS levels and first parameters, with one QoS level corresponding to at least one first parameter. Furthermore, in the mapping relationship of this embodiment, at least one QoS level corresponds to at least two first parameters simultaneously. Of course, in the mapping relationships configured by configuration module 502 in some examples, each QoS level corresponds to two or more first parameters simultaneously.

[0130] The first parameter mentioned above can refer to one of the parameters in the mapping relationship between the QoS index and the QoS parameter group. For example, the first parameter can be the QoS index or the default priority level of the data packet in the QoS parameter group. That is, the mapping relationship configured by the configuration module 502 can be a mapping relationship between the QoS level and the QoS index, or a mapping relationship between the QoS level and the default priority of the data packet.

[0131] In one example of this embodiment, the level classification indication configured by the configuration module 502 for the terminal may include at least one of the following:

[0132] First business attribute feature list;

[0133] Second business attribute feature list;

[0134] First-level threshold;

[0135] Second-level threshold.

[0136] The first business attribute feature list includes low-level business attribute features specified by the configuration module 502. Of course, those skilled in the art will understand that business attribute features not included in the first business attribute feature list naturally belong to high-level business attribute features.

[0137] The second business attribute feature list includes each high-level business attribute feature specified by the configuration module 502. If the connection module 602 determines that a certain business attribute feature does not exist in the second business attribute feature list, it means that the business attribute feature is a high-level business attribute feature.

[0138] Those skilled in the art will understand that the classification indicator may include only the first business attribute feature list or the second business attribute feature list, or it may include both the first business attribute feature list and the second business attribute feature list.

[0139] In some examples of this embodiment, the level classification indicator can be a first level threshold, which is used to indicate that business attribute features with a level lower than the first level threshold are low-level business attribute features.

[0140] In other examples of this embodiment, the level classification indicator can be a second level threshold, which is used to indicate that business attribute features with a level higher than the second level threshold are high-level business attribute features.

[0141] It is understandable that the first-level threshold and the second-level threshold can be the same or different: if the first-level threshold and the second-level threshold are the same, then business attribute features with a level lower than the threshold are low-level business attribute features, and business attribute features with a level higher than the threshold are high-level business attribute features.

[0142] It should be understood that for the two service attribute characteristics, QoS level and default packet priority level, the larger the level value, the lower the corresponding level, and the smaller the level value, the higher the corresponding level. Taking the default packet priority as an example: a value of "1" has a higher priority than a value of "2". Therefore, for the two service attribute characteristics of QoS level and default packet priority level, service attribute characteristics with a level below the first level threshold actually refer to service attribute characteristics with a level value greater than the first level threshold; service attribute characteristics with a level above the second level threshold actually refer to service attribute characteristics with a level value less than the first level threshold.

[0143] In some examples of this embodiment, the configuration module 502 can send a rank classification indication to the connection module 602 via a system broadcast message. In some examples of this embodiment, the rank classification indication is indicated by a QoS index. Of course, the configuration module 502 can also send the rank classification indication to the connection module 602 via signaling messages, etc. When the configuration module 502 sends the rank classification indication via a system broadcast message, the connection module 602 will also obtain the rank classification indication via a system broadcast message.

[0144] After determining the service QoS characteristic parameters configured by the configuration module 502, the connection module 602 can determine whether it can enter the RRC connection state based on the service QoS characteristic parameters.

[0145] Assuming that the service QoS characteristic parameter configured by the configuration module 502 is a level division indicator, the connection module 602 can first determine the low-level service attribute characteristics and high-level service attribute characteristics according to the level division indicator, and then determine whether it can enter the RRC connection state to obtain dedicated resources according to the service characteristic attributes of the current service.

[0146] The connection module 602 first determines whether the service attribute of the terminal's current service belongs to a high-level service attribute feature or a low-level service attribute feature based on the level classification indication, and then determines whether it can enter the RRC connection state based on the service attribute feature of the current service.

[0147] In one example of this embodiment, if the connection module 602 determines that the service attributes of all services currently used by the terminal belong to low-level service attribute characteristics, then the terminal cannot enter the RRC connection state to obtain dedicated resources. If the service attributes of at least one service currently used by the terminal belong to high-level service attribute characteristics, then the connection module 602 determines that the terminal can enter the RRC connection state to obtain dedicated resources.

[0148] It is understood that in other examples of this embodiment, the connection module 602 may also determine whether to enter the RRC connection state based on other judgment principles. For example, the connection module 602 determines that it can enter the RRC connection state only when it determines that the service attributes of all current services of the terminal belong to the high-level service attribute characteristics; if the connection module 602 determines that at least one of the current services of the terminal has the low-level service attribute characteristics, it determines that it cannot enter the RRC connection state temporarily.

[0149] The above explanation clarifies that the service QoS feature parameters configured by configuration module 502 are level classification indicators. In other examples of this embodiment, the service QoS feature parameters configured by configuration module 502 are the access types corresponding to the services, and the access types configured by configuration module 502 correspond to the service QoS characteristics. For this situation, this embodiment provides the following two solutions:

[0150] In Option 1, the configuration module 502 configures the access type corresponding to the QoS characteristics of each service for the terminal, and configures the corresponding feature factor for each access type. This feature factor can limit the access probability corresponding to the access type to a certain extent. The connection module 602 can then determine whether it can enter the RRC connection state based on the feature factor corresponding to the access type of its current service.

[0151] In this embodiment, the size of the feature factor corresponding to the access type can be configured by the configuration module 502 according to the QoS characteristics (i.e., the QoS requirements of the service) corresponding to the access type. For example, for services with high QoS requirements, the feature factor value corresponding to the access type is smaller, and conversely, for services with low QoS requirements, the feature factor value corresponding to the access type is larger.

[0152] For the connection module 602, after determining the access type and feature factor configured by the configuration module 502 for each service, it can generate a random number. If the generated random number is greater than or equal to the feature factor corresponding to the current service access type, it indicates that entering the RRC connection state is allowed. If the generated random number is less than the feature factor corresponding to the current service access type, it indicates that entering the RRC connection state is temporarily not allowed.

[0153] Understandably, when configuring service QoS feature parameters, the configuration module 502 configures the feature factors corresponding to the access type based on the principle that QoS requirements and feature factor values ​​are negatively correlated. Therefore, access types corresponding to services with low QoS requirements have higher feature factor values, while access types corresponding to services with high QoS requirements have lower feature factor values. In this case, when determining whether to enter the RRC connection state, the connection module 602 can only allow entry if the random number is greater than or equal to the feature factor corresponding to the current service access type; otherwise, it cannot enter the RRC connection state. This is because only in this way can services with high QoS requirements have a higher access probability, while services with low QoS requirements have a relatively lower access probability.

[0154] In some other examples of this embodiment, when configuring feature factor values ​​for service access types, the configuration module 502 sets the feature factor value corresponding to the access type to be larger for services with higher QoS requirements, and vice versa for services with lower QoS requirements.

[0155] For the connection module 602, after determining the access type and feature factor configured by the configuration module 502 for each service, it can generate a random number. If the generated random number is less than or equal to the feature factor corresponding to the current service access type, it indicates that entering the RRC connection state is allowed. If the generated random number is greater than the feature factor corresponding to the current service access type, it indicates that entering the RRC connection state is temporarily not allowed.

[0156] Understandably, when configuring service QoS feature parameters, the configuration module 502 configures the feature factors corresponding to the access type based on the principle that QoS requirements are positively correlated with feature factor values. Therefore, access types corresponding to services with low QoS requirements have smaller feature factor values, while access types corresponding to services with high QoS requirements have larger feature factor values. In this case, when determining whether to enter the RRC connection state, the connection module 602 can only allow entry if the random number is less than the feature factor corresponding to the current service access type; otherwise, it cannot enter the RRC connection state. This is because only in this way can services with high QoS requirements have a higher access probability, while services with low QoS requirements have a relatively lower access probability.

[0157] Option 2: Configuration module 502 can configure the corresponding access type for each service and indicate the QoS level corresponding to each access type to connection module 602. After determining the QoS level corresponding to the current service, connection module 602 can determine whether it can enter the RRC connection state based on the QoS level of the current service.

[0158] In this embodiment, services with higher QoS requirements have smaller QoS level values, while services with lower QoS requirements have larger QoS level values. To ensure a high probability of access when the terminal processes services with high QoS requirements, in this embodiment, the connection module 602 can generate a random number when determining whether it can enter the RRC connection state. If the generated random number is less than or equal to the reciprocal of the QoS level (i.e., less than or equal to 1 / QoS level), it is determined that it can enter the RRC connection state; otherwise, it is determined that it cannot enter the RRC connection state.

[0159] In some examples of this embodiment, if the service QoS feature parameters configured by the configuration module 502 include access type and feature factor or QoS level corresponding to access type, the configuration module 502 will also configure the blocking duration corresponding to access type for the terminal. The blocking duration is used by the connection module 602 to determine the total blocking duration when it determines that it cannot enter the RRC connection state.

[0160] In one example of this embodiment, when the connection module 602 determines that it cannot enter the RRC connection state, it can determine the total blocking duration according to the following formula:

[0161] T = (0.7 + 0.6 * a) * T0

[0162] Where T is the total blocking duration, T0 is the blocking duration configured by configuration module 502 for the current service access type, and a is a feature factor, or the reciprocal of the QoS level (i.e., 1 / QoS level).

[0163] In some examples of this embodiment, when the connection module 602 determines that it cannot enter the RRC connection state, it can also determine the total blocking duration according to the following formula:

[0164] T = (0.7 + 0.6 * random number * a) * T0

[0165] Here, 'a' can also be a feature factor, or the reciprocal of the QoS level (i.e., 1 / QoS level).

[0166] After determining the total blocking duration T, the connection module 602 starts timing according to T. Before the timing is complete, it cannot enter the RRC connection state. Normally, before the timing is complete, the connection module 602 does not need to re-determine whether it can enter the RRC connection state. After the timing is complete, the connection module 602 can re-determine whether it can enter the RRC connection state.

[0167] The terminal in this embodiment can be a V2X terminal or other types of terminals. That is, the communication configuration method and communication method provided in this embodiment can be applied not only to the field of vehicle networking but also to other fields.

[0168] In this embodiment, the communication configuration device 50 can be deployed on the base station side, while the communication device 60 can be deployed on the terminal side. The function of the configuration module 502 can be jointly implemented by the processor of the base station and the communication unit, and the function of the connection module 602 can be implemented by the processor of the terminal.

[0169] The communication configuration device and communication device provided in this embodiment enable the terminal to perform access control based on the service QoS feature parameters configured by the base station. This ensures that when the service QoS feature parameters meet the requirements, the terminal controls itself to enter the RRC connection state to obtain the corresponding communication resources, thereby realizing communication. When the service QoS feature parameters do not meet the requirements, the terminal temporarily does not enter the RRC connection state, thereby achieving full utilization and optimized configuration of communication resources.

[0170] Example 4:

[0171] This embodiment provides a storage medium that can store one or more computer programs that can be read, compiled, and executed by one or more processors. In this embodiment, the storage medium can store one of a communication configuration program and a communication program. The communication configuration program can be executed by one or more processors to implement any of the communication configuration methods described in the foregoing embodiments. The communication program can be executed by one or more processors to implement any of the communication methods described in the foregoing embodiments.

[0172] This embodiment also provides a base station, such as Figure 7 As shown, base station 70 includes a first processor 71, a first memory 72, and a first communication bus 73 for connecting the first processor 71 and the first memory 72. The first memory 72 can be the aforementioned storage medium storing a communication configuration program. The first processor 71 can read the communication configuration program, compile it, and execute the steps implementing the communication configuration method described in the foregoing embodiments. Details of how base station 70 implements the communication configuration method can be found in the description of the foregoing embodiments, and will not be repeated here.

[0173] This embodiment also provides a terminal, such as Figure 8 As shown, terminal 80 includes a second processor 81, a second memory 82, and a second communication bus 83 for connecting the second processor 81 and the second memory 82. The second memory 82 can be the aforementioned storage medium storing the communication program. The second processor 81 can read the communication program, compile it, and execute the steps to implement the communication method described in the foregoing embodiments. Details of how terminal 80 implements the communication method can be found in the description of the foregoing embodiments, and will not be repeated here.

[0174] This embodiment also provides a communication system; please refer to [link / reference]. Figure 9 The communication system 9 includes a base station 70 and terminals 80. In some examples, the communication system 9 includes one base station 70 and multiple terminals 80. In other examples of this embodiment, the communication system 9 may not include more than one base station 70.

[0175] The communication system provided in this embodiment configures service QoS characteristic parameters for terminals via a base station. Terminals can use these parameters to determine whether they can enter the RRC connection state. Based on the service QoS characteristic parameters configured by the base station, terminals can implement access control, ensuring they enter the RRC connection state and acquire corresponding communication resources when requirements are met, thereby enabling communication. Conversely, if the terminal's service QoS characteristic parameters do not meet the requirements, it temporarily does not enter the RRC connection state, thus facilitating the utilization and optimized allocation of communication resources.

[0176] Example 5:

[0177] To enable those skilled in the art to better understand the advantages and details of the aforementioned communication scheme, this embodiment will further illustrate the communication configuration method and communication method provided in the foregoing embodiments with some examples:

[0178] Example 1:

[0179] The base station configures a second-level threshold for QoS levels. This second-level threshold indicates that QoS levels higher than this threshold are considered high QoS levels. As mentioned above, since the numerical value of the QoS level is negatively correlated with the level of the QoS level, a QoS level higher than the second-level threshold actually means that the numerical value of the QoS level is lower than the second-level threshold.

[0180] For example, assuming the base station is configured with a second-level threshold of "2", that is, when the QoS hierarchy level value in the UE's current service is less than or equal to 2, the UE can determine that it can enter the RRC connection state to obtain dedicated resources.

[0181] Example 2:

[0182] The base station configures a first-level threshold for QoS levels. This first-level threshold indicates that QoS levels below this threshold are considered low QoS levels. As mentioned above, since the numerical value of the QoS level is negatively correlated with the level of the QoS level, a QoS level below the first-level threshold actually means that the numerical value of the QoS level is greater than the first-level threshold.

[0183] For example, if the first-level threshold configured by the base station is "4", then if the QoS hierarchy of all services currently used by the UE is greater than or equal to 4, such as when the QoS levels of the two services currently used by the terminal are QoS hierarchy4 and QoS hierarchy5 respectively, then the UE cannot temporarily enter the RRC connected state to obtain dedicated resources.

[0184] Example 3:

[0185] The base station assigns feature factors of 0.6 and 0.7 to access category 1 and access category 2, respectively. UE1's service characteristics belong to access category 1, and UE2's service characteristics belong to access category 2. In this embodiment, when the base station configures corresponding feature factors for each access type, the higher the QoS requirement of the service corresponding to the access type, the smaller the feature factor value; conversely, the lower the QoS requirement of the service corresponding to the access type, the larger the feature factor value.

[0186] During access control, UE1 generates a random number of 0.7, and UE2 generates a random number of 0.6. The random number generated by UE1 is greater than the feature factor of 0.6 corresponding to access category 1, so UE1 can access the network; the random number generated by UE2 is less than the feature factor corresponding to access category 2, so UE2 cannot access the network.

[0187] Base stations can configure the size of feature factors according to the QoS requirements of services. The higher the QoS requirements, the smaller the feature factor value, and the greater the probability of UE access. This ensures that services with high QoS requirements have a higher access probability.

[0188] Example 4:

[0189] Assume the base station configures a feature factor of 0.6 for access category 1. UE1's current service belongs to access category 1. During access control, UE1 generates a random number of 0.7. Because this random number is greater than the feature factor corresponding to access category 1, UE1 cannot access the service. Furthermore, the base station configures a blocking duration of 3 time units for access category 1. Therefore, the total blocking duration for UE1 is calculated as follows:

[0190] T390 = (0.7 + 0.6 * 0.6) * 3 time units

[0191] = 3.18 time units

[0192] In Example 4, the base station configures the feature factors and blocking durations corresponding to each access type for the terminal. When configuring the feature factors, the base station can configure the size of the feature factors according to the QoS requirements of the service. The higher the QoS requirements, the smaller the feature factor value, and the shorter the total blocking duration of the UE will be. That is, the higher the QoS requirements of the service, the shorter the total blocking duration.

[0193] Example 5:

[0194] In this example, the base station can add an access identifier, the access type corresponding to the service, the characteristic factor corresponding to the access type, and the blocking duration T0 for the V2X terminal. When configuring the characteristic factor for the access type, the base station follows the principle that the higher the service QoS requirement, the smaller the characteristic factor. The V2X terminal can refer to this when making access decisions. Figure 10 The flowchart shown is as follows:

[0195] S1002: The V2X terminal determines whether its own access identifier is a specific access identifier pre-configured by the base station.

[0196] If the result is negative, proceed to S1004; otherwise, proceed to S1012.

[0197] S1004: V2X terminal generates random numbers.

[0198] S1006: The V2X terminal determines whether the random number is greater than the feature factor corresponding to the current service access type.

[0199] If the judgment result is negative, proceed to S1008; otherwise, proceed to S1012.

[0200] S1008: The V2X terminal calculates the total blocking time based on the blocking time corresponding to the current service access type.

[0201] S1010: The V2X terminal starts timing according to the calculated total blocking duration.

[0202] After the timeout period ends, the access determination is performed again, i.e., it enters S1002. It is understandable that for a V2X terminal, its access identifier is usually fixed, so the terminal can also enter S1004 for determination after the timeout period ends.

[0203] S1012: The V2X terminal enters RRC connection state.

[0204] Those skilled in the art should understand that the communication configuration methods, communication methods, devices, terminals and base stations, communication systems and storage media provided in the various embodiments of the present invention can be applied not only to existing communication systems and currently deployed 5G communication systems, but also to any future communication system.

[0205] In this application, the technical features of the various embodiments can be combined and used in one embodiment without conflict.

[0206] It will be apparent to those skilled in the art that all or some of the steps, systems, or devices disclosed above, and their functional modules / units, can be implemented as software (which can be implemented using computer device executable program code), firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, executed by a computing device, and in some cases, the steps shown or described may be performed in a different order than those presented herein. The computer-readable medium may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium. Therefore, this invention is not limited to any particular hardware and software combination.

[0207] The above description, in conjunction with specific implementation methods, provides a further detailed explanation of the embodiments of the present invention. It should not be construed that the specific implementation of the present invention is limited to these descriptions. For those skilled in the art, various simple deductions or substitutions can be made without departing from the concept of the present invention, and all such modifications and substitutions should be considered within the scope of protection of the present invention.

Claims

1. A communication method, comprising: determining whether to enter a radio resource control (RRC) connected state according to a service quality of service (QoS) characteristic parameter, wherein the service QoS characteristic parameter comprises an access identifier of a terminal, and the access identifier is used to determine whether the terminal directly enters the RRC connected state; and the access identifier is an identifier of a terminal that is pre-agreed with a base station to directly enter the RRC connected state; the communication method further comprises: determining whether the access identifier of the terminal is a specific access identifier pre-configured by the base station, and if the determination result is no, generating a random number, otherwise, entering the RRC connected state; determining whether the random number is greater than a characteristic factor corresponding to a current service access type, and if the determination result is no, calculating a total blocking time according to a blocking time corresponding to the current service access type, otherwise, entering the RRC connected state; calculating the total blocking time according to the blocking time corresponding to the current service access type, timing according to the calculated total blocking time, and after the timing ends, re-determining whether to enter the RRC connected state.

2. The communication method of claim 1, wherein, The service QoS characteristic parameter is at least one of a grade division indication and an access type, the grade division indication is used to determine a low-grade service attribute characteristic and a high-grade service attribute characteristic, and the access type corresponds to a service QoS characteristic.

3. The communication method of claim 2, wherein, If the service QoS characteristic parameter is the grade division indication, the determining whether to enter the RRC connected state according to the service QoS characteristic parameter comprises: determining the low-grade service attribute characteristic and the high-grade service attribute characteristic according to the grade division indication; determining whether to enter the RRC connected state to obtain a dedicated resource according to a service attribute of a current service.

4. The communication method of claim 3, wherein, The determining whether to enter the RRC connected state to obtain the dedicated resource according to the service attribute of the current service comprises: if the service attribute of each current service belongs to the low-grade service attribute characteristic, determining that the current service cannot enter the RRC connected state to obtain the dedicated resource; and if the service attribute of at least one current service belongs to the high-grade service attribute characteristic, determining that the current service can enter the RRC connected state to obtain the dedicated resource.

5. The communication method of claim 2, wherein, The grade division indication comprises at least one of the following information: a first service attribute characteristic list, the first service attribute characteristic list comprising a low-grade service attribute characteristic; a second service attribute characteristic list, the second service attribute characteristic list comprising a high-grade service attribute characteristic; a first grade threshold, the first grade threshold being used to indicate that a service attribute characteristic with a grade lower than the first grade threshold is a low-grade service attribute characteristic; and a second grade threshold, the second grade threshold being used to indicate that a service attribute characteristic with a grade higher than the second grade threshold is a high-grade service attribute characteristic.

6. The communication method of claim 2, wherein, If the service QoS characteristic parameter is the grade division indication, the method further comprises, before the determining whether to enter the RRC connected state according to the service QoS characteristic parameter: receiving the grade division indication sent by the base station through a system broadcast message, and the grade division indication is indicated by a QoS index.

7. The communication method of claim 2, wherein, The service attribute characteristic is any one of a QoS grade, a QoS index, and a data packet default priority.

8. The communication method of claim 7, wherein, If the grade division indication is indication information for determining a low-grade QoS grade and a high-grade QoS grade, the communication method further comprises: determining a first mapping relationship between the QoS grade and a first parameter, the first parameter being a QoS index or a data packet default priority grade.

9. The communication method of claim 8, wherein, There are at least one QoS grade corresponding to at least two first parameters in the first mapping relationship.

10. The communication method of claim 2, wherein, If the service QoS characteristic parameter is an access type corresponding to the service, the determination of whether the terminal can enter the RRC connected state through the service QoS characteristic parameter comprises: determining the access type configured by the base station and the characteristic factor corresponding to each access type, and determining whether the terminal can enter the RRC connected state based on the characteristic factor corresponding to the access type of the current service; or, determining the QoS grade corresponding to the current service, and determining whether the terminal can enter the RRC connected state based on the QoS grade corresponding to the current service.

11. The communication method of claim 10, wherein, The communication method further comprises: when it is determined that the terminal cannot enter the RRC connected state, determining the total blocking time according to any one of the following two formulas: Formula one: T=(0.7+0.6*a)*T0 Formula two: T=(0.7+0.6*random number*a)*T0 The T is the total blocking time, the T0 is the blocking time configured by the base station for the access type to which the current service belongs, and the a is the characteristic factor or the reciprocal of the QoS grade.

12. The communication method of claim 10, wherein, The communication method further comprises: determining the access identifier configured by the base station for the terminal; determining whether the terminal can enter the RRC connected state according to the access identifier.

13. A communication configuration method, comprising: configuring a service QoS characteristic parameter for a terminal, the service QoS characteristic parameter being used by the terminal to determine whether the terminal can enter an RRC connected state, so that the terminal determines whether the terminal can enter an RRC connected state through the service QoS characteristic parameter; wherein the service QoS characteristic parameter comprises an access identifier of the terminal, the access identifier being used to determine whether the terminal directly enters the RRC connected state; the access identifier being an identifier of a terminal that can directly enter the RRC connected state and being pre-agreed between the terminal and the base station; the terminal determining whether the terminal can enter the RRC connected state through the service QoS characteristic parameter comprises: determining whether the access identifier of the terminal is a specific access identifier pre-configured by the base station, if the determination result is no, generating a random number, otherwise, entering the RRC connected state; determining whether the random number is greater than a characteristic factor corresponding to the access type of the current service, if the determination result is no, calculating the total blocking time according to the blocking time corresponding to the access type of the current service, otherwise, entering the RRC connected state; calculating the total blocking time according to the blocking time corresponding to the access type of the current service, timing according to the calculated total blocking time, and re-determining whether the terminal can enter the RRC connected state after the timing is over.

14. The communication configuration method of claim 13, wherein, The service QoS characteristic parameter comprises at least one of a grade division indication and an access type, the grade division indication being used by the terminal to determine a low-grade service attribute characteristic and a high-grade service attribute characteristic; and the access type corresponding to the service QoS characteristic.

15. The communication configuration method of claim 14, wherein, The grade division indication comprises at least one of the following information: A first service attribute feature list, wherein the first service attribute feature list comprises low-grade service attribute features; A second service attribute feature list, wherein the second service attribute feature list comprises high-grade service attribute features; A first grade threshold, wherein the first grade threshold is used to indicate that a service attribute feature with a grade lower than the first grade threshold is a low-grade service attribute feature; A second grade threshold, wherein the second grade threshold is used to indicate that a service attribute feature with a grade higher than the second grade threshold is a high-grade service attribute feature.

16. The communication configuration method of claim 14, wherein, If the service QoS feature parameter is a grade division indication, the method for configuring a terminal with a service quality service QoS feature parameter comprises: Sending a grade division indication to the terminal through a system broadcast message, wherein the grade division indication is indicated by a QoS index.

17. The communication configuration method of claim 14, wherein, The service attribute feature is any one of a QoS grade, a QoS index, and a data packet default priority grade.

18. The communication configuration method of claim 17, wherein, If the grade division indication is indication information used by the terminal to determine a low-grade QoS grade and a high-grade QoS grade, the communication configuration method further comprises: Configuring the terminal with a first mapping relationship between a QoS grade and a first parameter, wherein the first parameter is a QoS index or a data packet default priority grade.

19. The communication configuration method of claim 18, wherein, There are at least two first parameters corresponding to at least one QoS grade in the first mapping relationship.

20. The communication configuration method of claim 14, wherein, If the service QoS feature parameter is an access type corresponding to a service, the method for configuring a terminal with a service quality service QoS feature parameter comprises: Configuring the terminal with an access type corresponding to each service and a feature factor corresponding to each access type, wherein the feature factor is used by the terminal to determine whether the terminal can access a network based on an access type to which a current service belongs; Or, Configuring the terminal with an access type corresponding to each service and indicating a QoS grade corresponding to each access type to the terminal.

21. The communication configuration method of claim 20, wherein, The communication configuration method further comprises: Indicating a blocking time length corresponding to each access type to the terminal, wherein the blocking time length is used by the terminal to determine a total blocking time length when the terminal determines that the terminal cannot enter an RRC connected state based on the feature factor or the QoS grade.

22. The method of claim 13-21, wherein, The terminal is a vehicle-to-everything (V2X) terminal.

23. A communication device, comprising: A connection module configured to determine whether the terminal can enter an RRC connected state based on a service QoS feature parameter, wherein the service QoS feature parameter comprises an access identifier of the terminal, and the access identifier is used to determine whether the terminal directly enters the RRC connected state; and the access identifier is an identifier of a terminal that can directly enter the RRC connected state and is pre-agreed between the terminal and a base station; The communication device further comprises: Determining whether the access identifier of the terminal is a specific access identifier pre-configured by the base station, and if the determination result is no, generating a random number, otherwise, entering the RRC connected state; Determining whether the random number is greater than a feature factor corresponding to a current service access type, and if the determination result is no, calculating a total blocking time length according to a blocking time length corresponding to the current service access type, otherwise, entering the RRC connected state. The total blocking time is calculated according to the blocking time corresponding to the current service access type, timing is performed according to the calculated total blocking time, and after the timing ends, access judgment is performed again. 24.A communication configuration apparatus, comprising: A configuration module configured to configure a terminal with a quality of service (QoS) characteristic parameter, wherein the QoS characteristic parameter is used by the terminal to determine whether the terminal can enter a radio resource control (RRC) connected state, and the terminal determines whether the terminal can enter the RRC connected state through the QoS characteristic parameter; wherein the QoS characteristic parameter comprises an access identifier of the terminal, and the access identifier is used to determine whether the terminal directly enters the RRC connected state; and the access identifier is an identifier of a terminal that can directly enter the RRC connected state and is pre-agreed between the terminal and a base station. The terminal determines whether the terminal can enter the RRC connected state through the QoS characteristic parameter, comprising: determining whether the access identifier of the terminal is a specific access identifier pre-configured by the base station, and if the determination result is no, generating a random number, otherwise, entering the RRC connected state; determining whether the random number is greater than a characteristic factor corresponding to a current service access type, and if the determination result is no, calculating a total blocking time according to a blocking time corresponding to the current service access type, otherwise, entering the RRC connected state; calculating the total blocking time according to the blocking time corresponding to the current service access type, performing timing according to the calculated total blocking time, and after the timing ends, performing access judgment again. 25.A terminal, comprising a second processor, a second memory and a second communication bus; The second communication bus is configured to realize connection communication between the second processor and the second memory; The second processor is configured to execute one or more programs stored in the second memory to realize the steps of the communication method according to any one of claims 1 to 12.

26. The terminal of claim 25, wherein, The terminal is a V2X terminal. 27.A base station, comprising a first processor, a first memory and a first communication bus; The first communication bus is configured to realize connection communication between the first processor and the first memory; The first processor is configured to execute one or more programs stored in the first memory to realize the steps of the communication configuration method according to any one of claims 13 to 22. 28.A communication system, comprising the base station according to claim 27 and at least one terminal according to claim 25 or 26. 29.A storage medium, comprising at least a communication configuration program and / or a communication program, wherein the communication configuration program is executable by one or more processors to realize the steps of the communication configuration method according to any one of claims 13 to 22; and the communication program is executable by one or more processors to realize the steps of the communication method according to any one of claims 1 to 12.

Images