Communication control method, device, equipment, chip and medium

Abstract

The present disclosure proposes a communication control method, apparatus, device, chip and medium, wherein the communication control method comprises: receiving a first request, wherein the first request is used to request to send first status information of a target radio link control RLC entity; determining a second request according to the first request, wherein the second request is used to request to send target status information of the target RLC entity, and the target status information comprises: first status information; and sending target status information. The technical problem that the processing overhead of status information reporting request in the prior art is high and the processing efficiency is low, resulting in high data processing delay is solved.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication control method, device, equipment, chip and medium. Background Art

[0002] Radio link control layer (Radio link Control, RLC) refers to the control layer in the wireless communication system. The main function of RLC is to control the wireless link and provide a reliable link. RLC is located between the media access control layer (Media Access Control, MAC) and the packet data convergence protocol layer (Packet Data Convergence Protocol, PDCP), and supports sending and receiving data. Among them, when sending data, it supports segmentation and / or re-segmentation of data. When receiving data, it supports reorganization of fragmented data. Summary of the invention

[0003] The present disclosure aims to solve one of the technical problems in the related art at least to some extent.

[0004] To this end, the present disclosure proposes a communication control method, apparatus, communication equipment, chip and storage medium, which can effectively reduce the processing overhead of status information reporting requests and improve processing efficiency, thereby reducing data processing delay.

[0005] An embodiment of the first aspect of the present disclosure proposes a communication control method, including: receiving a first request, wherein the first request is used to request sending first status information of a target wireless link control RLC entity; determining a second request based on the first request, wherein the second request is used to request sending target status information of the target RLC entity, the target status information including: first status information; and sending target status information.

[0006] The second aspect embodiment of the present disclosure proposes a communication control device, including: a receiving module, used to receive a first request, wherein the first request is used to request to send first status information of a target wireless link control RLC entity; a determining module, used to determine a second request based on the first request, wherein the second request is used to request to send target status information of the target RLC entity, and the target status information includes: first status information; and a sending module, used to send the target status information.

[0007] The third aspect embodiment of the present disclosure proposes a communication device, including: a processor, and a memory connected to the processor in communication; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the communication control method proposed in the first aspect embodiment of the present disclosure.

[0008] The fourth aspect embodiment of the present disclosure proposes a chip, which includes a processing circuit and an interface circuit; wherein the interface circuit is used to read instructions, and the interface circuit sends the instructions to the processing circuit so that the processing circuit executes the communication control method proposed in the first aspect embodiment of the present disclosure.

[0009] The fifth aspect of the present disclosure provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the communication control method as described above.

[0010] The communication control method, apparatus, communication equipment, chip and storage medium provided by the present disclosure receive a first request, wherein the first request is used to request the first status information of the target radio link control RLC entity to be sent, and determine a second request based on the first request, wherein the second request is used to request the target status information of the target RLC entity to be sent, and the target status information includes: first status information; and sending target status information. Thus, after receiving the first request, the second request to be actually processed is determined based on the first request without processing each request, and the target status information reported based on the second request to be actually processed can include the first status information, ensuring that the status information of the target RLC entity in different scenarios can be effectively reported, thereby effectively reducing the processing overhead of the status information reporting request, and improving the processing efficiency, thereby reducing the data processing delay.

[0011] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above and / or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0013] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0014] Figure 2 A flow chart of a communication control method provided by an embodiment of the present disclosure;

[0015] Figure 3 A flow chart of another communication control method provided by an embodiment of the present disclosure;

[0016] Figure 4 is a schematic diagram of parallel processing of a data processing process and a status report processing process in an embodiment of the present disclosure;

[0017] Figure 5is a schematic diagram of the process of processing shard data in an embodiment of the present disclosure;

[0018] Figure 6 is a schematic diagram of the process of processing complete data in an embodiment of the present disclosure;

[0019] Figure 7 A flow chart of another communication control method provided by an embodiment of the present disclosure;

[0020] Figure 8 is a schematic diagram of the structure of the Status Report module in an embodiment of the present disclosure;

[0021] Fig. 9 is a schematic diagram of the processing flow of the Status Report module in an embodiment of the present disclosure;

[0022] Fig.10 is a schematic diagram of an application flow in an embodiment of the present disclosure;

[0023] Fig.11 is another application flow diagram in an embodiment of the present disclosure;

[0024] Fig.12 A schematic diagram of the structure of a communication control device provided by an embodiment of the present disclosure;

[0025] Fig.13 A block diagram of an exemplary communication device suitable for implementing the embodiments of the present disclosure is shown;

[0026] Fig.14 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure;

[0027] Fig.15 It is a schematic diagram of the structure of another chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0029] In the embodiments of the present disclosure, the communication device may be, for example, a terminal or a network device, which is not limited.

[0030] Figure 1 FIG. 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. Figure 1As shown, the communication system 100 may include a terminal 101 and a network device 102. The network device 102 may include at least one of an access network device and a core network device.

[0031] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city (smart city), and at least one of a wireless terminal in a smart home (smart home), but is not limited to these.

[0032] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (CloudRAN), a base station in other communication systems, and at least one of an access node in a WiFi system, but is not limited thereto.

[0033] In some embodiments, the technical solution of the present disclosure may be applicable to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure may become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

[0034] In some embodiments, the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be referred to as a control unit (control unit). The CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.

[0035] In some embodiments, the core network device may be a device including one or more network elements, or may be a plurality of devices or a group of devices, each including all or part of one or more network elements. The network element may be virtual or physical. The core network, for example, includes at least one of an Evolved Packet Core (EPC), a 5G Core Network (5G Core Network, 5G CN), and a Next Generation Core (NGC).

[0036] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. A person of ordinary skill in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0037] The following embodiments of the present disclosure can be applied to Figure 1 The communication system 100, or a portion thereof, is shown but is not limited thereto. Figure 1 The various entities shown are examples, and the communication system may include Figure 1 All or part of the subject, and may also include Figure 1 For entities other than the above, the number and form of each entity are arbitrary, and the connection relationship between the entities is an example. The entities may be connected or disconnected, and the connection may be in any manner, which may be direct or indirect, and may be wired or wireless.

[0038] Embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, next-generation systems based on them, etc. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A and 5G, etc.) for application.

[0039] In the related art, if status report processing is required during the processing of the previous data (segmented data and / or complete data), the corresponding status report work and subsequent processes must be completed before the subsequent data can be processed. Among them, the same RLC entity or multiple RLC entities may process requests from multiple different scenarios (the request is used to trigger the status report, and the request can also be called a "status information reporting request"). If the triggering frequency of the status information reporting request is high in multiple scenarios, it means that more status information reporting requests need to be processed.

[0040] In this way, each status information reporting request needs to be processed, resulting in the processing time overhead of each status information reporting request being interspersed between data processing, while the difference between the status information of the same RLC entity in different scenarios may be relatively small, resulting in: the processing overhead of the status information reporting request is high and the processing efficiency is low, resulting in high data processing delay.

[0041] In order to solve the above technical problems, the disclosed embodiment provides a communication control method, which receives a first request, wherein the first request is used to request the first status information of the target radio link control RLC entity to be sent, and determines a second request based on the first request, wherein the second request is used to request the target status information of the target RLC entity to be sent, and the target status information includes: the first status information; and the sending target status information. Thus, after receiving the first request, the second request to be actually processed is determined based on the first request without processing each request, and the target status information reported based on the second request to be actually processed can include the first status information, ensuring that the status information of the target RLC entity in different scenarios can be effectively reported. Therefore, the processing overhead of the status information reporting request can be effectively reduced, and the processing efficiency can be improved, thereby reducing the data processing delay.

[0042] The communication control method in the embodiment of the present disclosure may be applied in a communication device, and the communication device is, for example, the above-mentioned terminal or network device, without limitation.

[0043] Figure 2 A flow chart of a communication control method provided by an embodiment of the present disclosure.

[0044] like Figure 2 As shown, the communication control method includes:

[0045] Step S201: Receive a first request, where the first request is used to request sending first status information of a target RLC entity.

[0046] The target RLC entity refers to the RLC entity currently processing data (segmented data and / or complete data). In the process of processing data, the target RLC entity may trigger reporting of status information in different scenarios. The request for triggering reporting of status information may be referred to as a first request. Specifically, the first request refers to a request currently generated for triggering reporting of status information.

[0047] Optionally, in some embodiments, the first status information may be used to describe the status of the target RLC entity in a certain scenario during data processing. Different scenarios may correspond to different or the same modules, and the module refers to the module used in the data processing process. For example, the module may be, for example, a protocol data unit (PDU) check module (PDU Check), a reassembly process module (Reassemble Process), a maintenance module (WinMaintain), a reassembly timer maintenance module (t-Reassembly Maintain), and a status report (Status Report) module, wherein the PDU check module is used to check the received data, for example, to check whether it is complete data in an unacknowledged mode (Unacknowledged Mode, UM) mode, whether it is UM data considered for reassembly, whether it is data outside the acknowledgement mode (Acknowledge Mode, AM) receiving window, or whether it is duplicate data in the AM mode. The reassembly process module is used to reassemble the received fragmented data and form complete data. The maintenance module is used to maintain the UM reassembly window or the AM receiving window and update the state variables during the maintenance process. The reorganization timer maintenance module is used to maintain the reorganization timer based on the current data reception status, window and state variable position, for example: the reorganization timer is turned on, off or turned on again after being turned off. The status report module is used to process the status reports triggered in different scenarios during data processing.

[0048] Optionally, in some embodiments, the first request may be generated by at least one of the above-mentioned protocol data unit (PDU Check), reassemble process module (Reassemble Process), maintenance module (WinMaintain), and reassembly timer maintenance module (t-Reassembly Maintain), and is used to report status information during the stage when the corresponding module processes data. In the process of receiving the first request, the first request formed by the above-mentioned at least one module may be received, and there is no limitation on this.

[0049] Optionally, in some embodiments, the first request is used to request the transmission of the first status information of the target RLC entity. That is to say, in the process of processing the data of the target RLC entity, the various modules mentioned above can be used, and the first request formed by each module in the stage of processing the data of the target RLC entity can indicate the target entity information of the target RLC entity (for example, the entity number of the target RLC entity), and then it can be determined whether to use the received first request as the second request actually processed based on the content indicated by the first request, and there is no limitation on this.

[0050] Step S202: Determine a second request according to the first request, wherein the second request is used to request to send target state information of a target RLC entity, and the target state information includes: first state information.

[0051] The second request refers to a request that needs to be responded to and processed to actually report the status information, and the first request may be a received request for triggering the reporting of the status information. After receiving the first request, it may be determined whether to use the received first request as the second request to be actually processed based on the content indicated by the first request. That is, based on the content indicated by the first request, it is determined whether to respond to the first request to realize the merging of the number dimension of multiple requests for triggering the reporting of the status information of the target RLC entity.

[0052] Optionally, in some embodiments, the number of first requests may be one or more, and each time a first request is received, the communication control method provided in the embodiments of the present disclosure may be used to process the first request.

[0053] The second request is used to report target state information of the target RLC entity, and the target state information includes: first state information. The state information reported by the second request may be referred to as target state information.

[0054] Optionally, in some embodiments, in the process of determining the second request according to the first request, it can be determined whether the second request associated with the target RLC entity already exists based on the content indicated by the first request. If so, the second request associated with the target RLC entity is obtained, that is, there is no need to process the first request later, but the second request is processed, and the target status information reported by the second request can also include the first status information triggered by the first request, so as to realize the merging of the number dimension of the requests for reporting multiple triggered status information of the target RLC entity. If it does not exist, the first request is directly used as the second request associated with the target RLC entity, that is, it is necessary to respond to and process the second request associated with the target RLC entity later. If another first request is received again, the first request received again and the second request associated with the target RLC entity are merged in the number dimension, and there is no restriction on this.

[0055] Step S203: Send target status information.

[0056] In the above, based on the first request, the second request is determined, and a reporting opportunity may be waited for. When the reporting opportunity is met, the target status information may be sent, and there is no restriction on this.

[0057] Since the multiple trigger status information reporting requests of the target RLC entity are merged in the dimension of number of times, and the target status information reported in response to the second request may include the first status information, it is possible to use the same second request to report the status information generated in multiple scenarios, thereby effectively reducing the processing overhead of the status information reporting request, improving the processing efficiency, and thus reducing the data processing delay.

[0058] In this embodiment, by receiving a first request, wherein the first request is used to request the first status information of the target radio link control RLC entity to be sent, and according to the first request, determining a second request, wherein the second request is used to request the target status information of the target RLC entity to be sent, and the target status information includes: first status information; and sending target status information. Thus, after receiving the first request, the second request to be actually processed is determined based on the first request without processing each request, and the target status information reported based on the second request to be actually processed can include the first status information, ensuring that the status information of the target RLC entity in different scenarios can be effectively reported, thereby effectively reducing the processing overhead of the status information reporting request, and improving the processing efficiency, thereby reducing the data processing delay.

[0059] Figure 3 A flowchart of another communication control method provided by an embodiment of the present disclosure.

[0060] like Figure 3 As shown, the communication control method includes:

[0061] Step S301: receiving a first request during processing of fragmented data; and / or receiving a first request during processing of complete data, wherein the first request is used to request sending first status information of a target radio link control RLC entity.

[0062] That is to say, the processing of the first request in the embodiments of the present disclosure may be performed in parallel with the data processing process. Optionally, in some embodiments, the first request may be received during the processing of the sharded data; or during the processing of the completed data; or during the processing of the sharded data and the complete data, without limitation.

[0063] As a result, the time delay introduced by the processing of the status information reporting request to the data processing process can be reduced to a large extent, thereby improving data processing efficiency and ensuring communication performance.

[0064] Step S302: Determine target entity information of the target RLC entity according to the first request.

[0065] After receiving the first request, the target entity information of the target RLC entity may be determined based on the first request. The target entity information, such as the entity number of the target RLC entity, is not limited thereto.

[0066] Optionally, in some embodiments, the target entity information of the target RLC entity can be parsed from the first request; or the source of the first request can be determined, and the target entity information of the target RLC entity can be determined based on the "source"; or any other possible method can be used to determine the target entity information of the target RLC entity according to the first request, without limitation.

[0067] The target entity information of the target RLC entity obtained above may be used to determine the second request to be actually processed, as described below for details.

[0068] Step S303: Determine a second request according to the target entity information, wherein the second request is used to request to send target state information of the target RLC entity, and the target state information includes: first state information.

[0069] Optionally, in some embodiments, it can be determined based on the target entity information whether a second request associated with the target RLC entity already exists. If so, the existing second request associated with the target RLC entity is obtained, that is, there is no need to process the first request subsequently, but the second request is processed, and the target status information reported by the second request can also include the first status information triggered by the first request, so as to realize the merging of the number dimension of the requests for reporting multiple triggered status information of the target RLC entity. If it does not exist, the first request is directly used as the second request associated with the target RLC entity, that is, it is necessary to respond to and process the second request associated with the target RLC entity subsequently. If another first request is received again, the first request received again and the second request associated with the target RLC entity are merged in the number dimension, and there is no restriction on this.

[0070] Step S304: Send target status information.

[0071] In the above, based on the first request, the second request is determined, and a reporting opportunity may be waited for. When the reporting opportunity is met, the target status information may be sent, and there is no restriction on this.

[0072] The following are some examples:

[0073] The data processing process and the status report processing process can be processed in parallel, thereby reducing data processing latency and improving data processing efficiency. Figure 4 As shown, Figure 4It is a schematic diagram of the parallel processing of the data processing process and the status report processing process in the embodiment of the present disclosure. Assuming that a transport block (Transport Block, TB) contains data of three RLC entities (RLC0, RLC1, RLC2), the request for triggering status information reporting generated by RLC0 may include: REQ1 and REQ2, the request for triggering status information reporting generated by RLC1 may include: REQ3 and REQ4, and the request for triggering status information reporting generated by RLC2 may include: REQ5, REQ6, REQ7. Status Report Req FIFO represents a status report request sequence, which is used to store pending status information reporting requests of different RLC entities (an optional example of pending requests, and the pending request corresponding to the target RLC entity can be an optional example of the above-mentioned second request). The data processing process and the status report processing process are parallel, which avoids the waiting between data processing and status report processing and reduces the data processing delay. In addition, the original seven status information reporting requests were merged (i.e., two for RLC entity 1 were merged into one, and three for RLC entity 2 were merged into one), thereby reducing the number of status reports actually processed from seven to four, effectively reducing the processing overhead of status information reporting requests, and solving the technical problem that the differences between multiple status information reported by RLC entity 1 or RLC entity 2 are small, thereby greatly improving the efficiency of status information reporting.

[0074] In this embodiment, by receiving a first request, wherein the first request is used to request the first state information of the target radio link control RLC entity to be sent, and according to the first request, determining a second request, wherein the second request is used to request the target state information of the target RLC entity to be sent, and the target state information includes: first state information; and sending target state information. Thus, after receiving the first request, the second request to be actually processed is determined based on the first request, without processing each request, and the target state information reported based on the second request to be actually processed can include the first state information, ensuring that the state information of the target RLC entity in different scenarios can be effectively reported, therefore, the processing overhead of the state information reporting request can be effectively reduced, and the processing efficiency can be improved, thereby reducing the data processing delay. By receiving the first request in the process of processing the fragmented data; and / or receiving the first request in the process of processing the complete data, wherein the first request is used to request the first state information of the target radio link control RLC entity to be sent, so that the processing process of the first request and the data processing process are performed in parallel, thereby, the delay introduced by the processing of the state information reporting request to the data processing process can be greatly reduced, thereby improving the data processing efficiency and ensuring the communication performance.

[0075] Optionally, in some embodiments, the first request may be generated in the process of processing the shard data. Optionally, for example, a first request may be generated in a first scenario corresponding to the shard data to report the first status information in the first scenario. The first scenario corresponding to the shard data includes at least one of the following: the sequence number SN of the shard data has been completely received, and the shard data includes a reference field, wherein the reference field is used to trigger the reporting of status information; the SN of the shard data is outside the receiving window, and the shard data includes a reference field; the shard data is repeatedly received, and the shard data includes a reference field; the shard data is not discarded, and the shard data includes a reference field, and the trigger condition is met, wherein the trigger condition is used to trigger the reporting of status information. Thus, the processing process of the first request and the shard data processing process are carried out in parallel, thereby improving the processing efficiency of the shard data and ensuring the communication performance. And the status information reporting request in various possible scenarios during the shard data processing process can be optimized, thereby greatly reducing the processing overhead of the status information reporting request and greatly improving the processing efficiency.

[0076] The reference field may be, for example, a "Polling" field, which is used to trigger the peer end to report status information. The trigger condition may be agreed upon by the protocol or indicated by the network device. The trigger condition refers to a threshold condition used to trigger reporting status information.

[0077] like Figure 5 As shown, Figure 5 1 is a schematic diagram of the process of processing the slice data in the embodiment of the present disclosure. The Data PDUFIFO may contain a number of slice data to be processed. After processing each slice data, the RLC may report the processed data to the RLC Service Data Unit (RLC SDU). The "solid line" represents the slice data processing process, and the "dashed line" represents the status request reporting process.

[0078] Optionally, in some embodiments, the above-mentioned first request may be generated in the process of processing complete data. Optionally, for example, a first request may be generated in a second scenario corresponding to the complete data to report the first status information in the second scenario. Among them, the second scenario corresponding to the complete data includes at least one of the following: the complete data is outside the receiving window, and the complete data includes a reference field, wherein the reference field is used to trigger the reporting of status information; the complete data is repeatedly received, and the complete data includes a reference field; the complete data includes a reference field, and the trigger condition is satisfied, wherein the trigger condition is used to trigger the reporting of status information. Thus, the processing process of the first request and the complete data processing process are carried out in parallel, thereby improving the processing efficiency of the complete data and ensuring the communication performance. And the status information reporting request in various possible scenarios during the complete data processing process can be optimized, thereby greatly reducing the processing overhead of the status information reporting request and greatly improving the processing efficiency.

[0079] like Figure 6 As shown, Figure 6 1 is a schematic diagram of the process of processing complete data in an embodiment of the present disclosure. The Data PDUFIFO may contain a number of complete data to be processed. After processing each complete data, the RLC may report the processed data to the RLC SDU. The "solid line" represents the complete data processing process, and the "dotted line" represents the status request reporting process.

[0080] By the above Figure 5 and Figure 6 It can be seen that the Status Report module is no longer interspersed in the data processing process, but is independent of the data processing path and can run in parallel with the data processing path, receiving status information reporting requests generated during the data processing process and triggered by other modules, and merging and subsequently processing the requests.

[0081] Figure 7 A flowchart of another communication control method provided by an embodiment of the present disclosure.

[0082] like Figure 7 As shown, the communication control method includes:

[0083] Step S701: Receive a first request, where the first request is used to request to send first status information of a target radio link control RLC entity.

[0084] Step S702: Determine target entity information of the target RLC entity according to the first request.

[0085] For the description of S701 - S702 , please refer to the above embodiment, which will not be repeated here.

[0086] Step S703: Determine at least one request to be processed, wherein the request to be processed has corresponding candidate entity information.

[0087] Optionally, in some embodiments, one or more pending requests may be stored in the Status Report Req FIFO, and each pending request corresponds to a candidate entity information, wherein the candidate entity information corresponding to different pending requests is different, thereby ensuring that the Status Report Req FIFO only stores the pending requests of one RLC entity.

[0088] Optionally, in some embodiments, the candidate entity information may be the entity number of the candidate RLC entity to which the request to be processed belongs.

[0089] Step S704: Determine whether there is candidate entity information identical to the target entity information in at least one candidate entity information, and obtain a reference result.

[0090] After determining at least one pending request and the candidate entity information corresponding to each pending request, it is possible to determine whether there is candidate entity information that is the same as the target entity information in at least one candidate entity information, and obtain a reference result. The reference result can be used to determine the second request that is actually processed, without any restriction.

[0091] For example, the pending requests stored in the Status Report Req FIFO can be determined, each pending request is associated with a candidate entity information, that is, the pending request is used to request to report the status information of the RLC entity to which the associated candidate entity information belongs. After receiving a new first request, the target entity information can be determined based on the first request, and then, it is determined whether there is candidate entity information identical to the target entity information in one or more candidate entity information to obtain a reference result.

[0092] Step S705: Determine the second request according to the reference result.

[0093] Optionally, in some embodiments, when there is candidate entity information identical to the target entity information in at least one candidate entity information, the pending request corresponding to the identical candidate entity information is determined as the second request. For example, if it is determined that there is candidate entity information identical to the target entity information in one or more candidate entity information, it means that the pending request of the target RLC entity has been stored in the Status Report Req FIFO, and the pending request of the target RLC entity can be determined as the second request.

[0094] Optionally, in some embodiments, when there is no candidate entity information identical to the target entity information in at least one candidate entity information, the first request is determined as the second request. For example, if it is determined that there is no candidate entity information identical to the target entity information in one or more candidate entity information, it means that the pending request of the target RLC entity has not been stored in the Status Report Req FIFO, and the first request of the target RLC entity can be determined as the second request.

[0095] Optionally, in some embodiments, after determining the first request as the second request, the second request, the target entity information, and the corresponding relationship between the second request and the target entity information can be stored, thereby ensuring that after receiving a new first request, the second request actually processed can be determined quickly and efficiently, thereby further ensuring the efficiency of status information reporting.

[0096] Thus, by determining at least one pending request, wherein the pending request has corresponding candidate entity information, and determining whether there is candidate entity information identical to the target entity information in the at least one candidate entity information, obtaining a reference result, and determining the second request based on the reference result, it is possible to quickly and accurately determine the second request actually processed by the target RLC entity.

[0097] Step S706: Determine target status information.

[0098] Optionally, in some embodiments, in order to ensure the accuracy of the target state information reported by the second request actually processed, the method for determining the target state information may also be optimized. In the process of determining the target state information, a current variable interval corresponding to the target RLC entity may be determined, and state information corresponding to each sequence number SN in the current variable interval may be obtained, wherein the plurality of state information includes the first state information, and the target state information is generated according to the plurality of state information.

[0099] The current variable interval may be the latest variable interval at the current moment. The variable interval, for example, is the interval between the state variable RX_N (i.e., RX_Next) and the state variable RX_S (i.e., RX_Highest_Status). RX_Next stores the next sequence number (SN) value of the last RLC SDU received completely on demand. RX_Highest_Status stores the highest value that the ACK_SN field can be set to when a PDU needs to be generated.

[0100] Optionally, in some embodiments, state information corresponding to each sequence number SN in the current variable interval may be obtained to obtain multiple state information, including first state information, and then the multiple state information may be processed to obtain target state information.

[0101] Step S707: Send target status information.

[0102] In the above, based on the first request, the second request is determined, and a reporting opportunity may be waited for. When the reporting opportunity is met, the target status information may be sent, and there is no restriction on this.

[0103] The examples for the above embodiment are as follows:

[0104] like Figure 8 As shown, Figure 8 is a structural diagram of a Status Report module in an embodiment of the present disclosure, wherein the Status Report module may include: a Status Report Req FIFO and a status report request processing module (StatusReport Req Process), wherein the Status Report Req FIFO represents a status report request sequence, and is used to store pending status information reporting requests of different RLC entities (an optional example of a pending request, and the pending request corresponding to the target RLC entity may be an optional example of the above-mentioned second request), Figure 8 The numbers in the Status Report Req FIFO can represent candidate entity numbers (an optional example of candidate entity information). The status report request processing module (Status Report Req Process) is used to take out the status information reporting request (an optional example of the second request) of the corresponding RLC entity from the Status Report Req FIFO for processing. The processing flow of the Status Report module for the status information reporting request (an optional example of the first request) received from different RLC entities in different scenarios can be as follows: Fig. 9 As shown, Fig. 9 : is a schematic diagram of the processing flow of the Status Report module in the embodiment of the present disclosure. Among them, the received status information reporting request can be an optional example of the first request, and the "entity number to which the request belongs" can be an optional example of the target entity information. The Req to be processed by the entity is an optional example of the second request of the target RLC entity. The Req of the entity is an optional example of the first request.

[0105] Optionally, in some embodiments, Fig.10 As shown, Fig.10 It is a schematic diagram of an application flow in an embodiment of the present disclosure. Take the target RLC entity as entity 3 for example. The Status Report module receives a status information reporting request from entity 3 (an optional example of a first request). However, if there is already a pending REQ of entity 3 in the Status Report Req FIFO (an optional example of a second request of entity 3), the newly received REQ will not be put into the StatusReport Req FIFO, but will be merged with the pending REQ of entity 3 (merging in the number dimension).

[0106] Optionally, in some embodiments, Fig.11 As shown, Fig.11 It is another application flow diagram in the embodiment of the present disclosure. Take the target RLC entity as entity 4 for example. When the Status Report module receives a status information reporting request (an optional example of a first request) from entity 4, and there is no pending REQ of entity 4 in the Status Report Req FIFO (an optional example of a second request of entity 4), the newly received REQ is placed in the Status Report Req FIFO to wait for processing.

[0107] Optionally, in some embodiments, for a REQ added to the Status Report Req FIFO, when it is taken out and processed by the Status Report Req Process, the variable interval (an optional example of the current variable interval) for reporting the latest status information can be obtained, and then the reception status of each SN can be searched in the corresponding variable interval for reporting. In this way, when a REQ is processed, the latest status information (an optional example of the target status information) can be reported, and it can be ensured that the latest status information can contain the status information required by the merged REQs.

[0108] In this embodiment, by receiving a first request, wherein the first request is used to request to send the first state information of the target radio link control RLC entity, and according to the first request, determining a second request, wherein the second request is used to request to send the target state information of the target RLC entity, and the target state information includes: first state information; and sending target state information. Thus, after receiving the first request, the second request actually processed is determined based on the first request, without processing each request, and the target state information reported based on the actually processed second request can include the first state information, ensuring that the state information of the target RLC entity in different scenarios can be effectively reported, so that the processing overhead of the state information reporting request can be effectively reduced, and the processing efficiency can be improved, thereby reducing the data processing delay. By determining at least one request to be processed, wherein the request to be processed has corresponding candidate entity information, and determining whether there is candidate entity information identical to the target entity information in at least one candidate entity information, a reference result is obtained, and according to the reference result, the second request is determined. It is possible to quickly and accurately determine the second request actually processed by the target RLC entity. It is also possible to ensure the accuracy of the target state information reported by the actually processed second request.

[0109] In the disclosed embodiment, the Status Report module can be independent of the data processing path and processed in parallel with the data processing process. For the same RLC entity, there is only one status information reporting request to be processed in the Status Report ReqFIFO in the Status Report module.

[0110] The method provided in the embodiment of the present disclosure effectively reduces the processing overhead introduced when each status information reporting request is processed. At the same time, it effectively solves the technical problem that after multiple status information reporting requests are processed, the status information generated is the same or has little difference. The number of status information reporting requests actually processed is reduced, that is, the latest status information is reported with fewer status information reporting request processing times, thereby improving the efficiency of status reporting. By parallelizing the data processing process and the status information reporting process, the waiting time of the data processing process for the status information reporting process is greatly reduced, the data processing delay is reduced, and the data processing efficiency is improved.

[0111] Fig.12 A schematic diagram of the structure of a communication control device provided in an embodiment of the present disclosure.

[0112] like Fig.12 As shown, the communication control device 120 includes:

[0113] The receiving module 1201 is used to receive a first request, wherein the first request is used to request to send first status information of a target radio link control RLC entity.

[0114] The determination module 1202 is used to determine a second request according to the first request, wherein the second request is used to request to send target state information of a target RLC entity, and the target state information includes: first state information.

[0115] The sending module 1203 is used to send target status information.

[0116] It should be noted that the above explanation of the communication control method embodiment is also applicable to the communication control device of this embodiment, and will not be repeated here.

[0117] In this embodiment, by receiving a first request, wherein the first request is used to request the first status information of the target radio link control RLC entity to be sent, and according to the first request, determining a second request, wherein the second request is used to request the target status information of the target RLC entity to be sent, and the target status information includes: first status information; and sending target status information. Thus, after receiving the first request, the second request to be actually processed is determined based on the first request without processing each request, and the target status information reported based on the second request to be actually processed can include the first status information, ensuring that the status information of the target RLC entity in different scenarios can be effectively reported, thereby effectively reducing the processing overhead of the status information reporting request, and improving the processing efficiency, thereby reducing the data processing delay.

[0118] In order to implement the above embodiments, the present disclosure also proposes a communication device, including: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method provided by the above embodiments.

[0119] Fig.13 A block diagram of an exemplary communication device suitable for implementing embodiments of the present disclosure is shown. Fig.13 The communication device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure. The communication device may be, for example, a terminal, which is not limited.

[0120] like Fig.13 As shown, the communication device 12 is in the form of a general purpose computing device. Components of the communication device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 that connects various system components (including the memory 28 and the processing unit 16).

[0121] The bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnection (PCI) bus.

[0122] The communication device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the communication device 12, including volatile and non-volatile media, removable and non-removable media.

[0123] The memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache 32. The communication device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Fig.13 Not shown, often called a "hard drive").

[0124] although Fig.13 Not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (e.g., a compact disc read only memory (hereinafter referred to as: CD-ROM), a digital versatile disc read only memory (hereinafter referred to as: DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0125] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28, such program modules 42 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods of the embodiments described in the present disclosure.

[0126] The communication device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a human body to interact with the communication device 12, and / or any device that enables the communication device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 22. In addition, the communication device 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the communication device 12 through a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the communication device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0127] The processing unit 16 executes various functional applications and data processing by running the programs stored in the memory 28, such as implementing the methods mentioned in the above embodiments.

[0128] In order to implement the above embodiments, the present disclosure further proposes a chip, including: the chip includes a processing circuit, and the processing circuit is configured to execute the method provided by the above embodiments.

[0129] Fig.14 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. Fig.14 The structure of the chip 1400 is shown, but is not limited to this.

[0130] The chip 1400 includes a processing circuit 1401 and an interface circuit 1402. The interface circuit 1402 is used to read instructions. The interface circuit 1402 sends the instructions to the processing circuit 1401 so that the processing circuit 1401 executes the above method.

[0131] Alternatively, if Fig.15 As shown, Fig.15The chip 1400 may further include: a memory 1403 for storing instructions, and the interface circuit 1402 may be used to read the instructions stored in the memory 1403 .

[0132] Optionally, the interface circuit 1402 is connected to the memory 1403, and the interface circuit 1402 can be used to receive signals from the memory 1403 or other devices, and the interface circuit 1402 can be used to send signals to the memory 1403 or other devices. For example, the interface circuit 1402 can read the instructions stored in the memory 1403 and send the instructions to the processing circuit 1401.

[0133] Optionally, the number of the memory 1403 may be one or more. The number of the interface circuit 1402 may also be one or more.

[0134] In some embodiments, the interface circuit 1402 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processing circuit 1401 performs other steps.

[0135] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0136] Optionally, all or part of the memory 1403 may also be located outside the chip 1400 .

[0137] In order to implement the above embodiments, the present disclosure further proposes a non-transitory computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method proposed in the above embodiments of the present disclosure is implemented.

[0138] In order to implement the above embodiments, the present disclosure further proposes a computer program product. When instructions in the computer program product are executed by a processor, the method proposed in the above embodiments of the present disclosure is executed.

[0139] The collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in this disclosure shall comply with the relevant laws and regulations and shall not violate public order and good morals.

[0140] It should be noted that personal information from users should be collected for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. In addition, such collection / sharing should be carried out after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign the agreement / authorization including authorization of relevant user information before the user uses the function. In addition, any necessary steps should be taken to protect and safeguard access to such personal information data and ensure that others who have access to personal information data comply with its privacy policy and procedures.

[0141] The present disclosure anticipates providing implementation schemes for users to selectively block the use or access of personal information data. That is, the present disclosure anticipates providing hardware and / or software to prevent or block access to such personal information data. Once the personal information data is no longer needed, risks can be minimized by limiting data collection and deleting the data. In addition, when applicable, such personal information is de-identified to protect the privacy of the user.

[0142] In the description of the aforementioned embodiments, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are contradictory.

[0143] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of the present disclosure, "plurality" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0144] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present disclosure includes additional implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present disclosure belong.

[0145] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0146] It should be understood that the various parts of the present disclosure can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used to implement: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0147] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0148] In addition, each functional unit in each embodiment of the present disclosure may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0149] The storage medium mentioned above may be a read-only memory, a disk or an optical disk, etc. Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations of the present disclosure. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present disclosure.

Claims

1. A communication control method, characterized in that: include: receiving a first request, wherein the first request is used to request to send first status information of a target radio link control RLC entity; Determine a second request according to the first request, wherein the second request is used to request to send target state information of the target RLC entity, the target state information comprising: the first state information; and The target status information is sent.

2. The method according to claim 1, characterized in that The determining the second request according to the first request includes: determining target entity information of the target RLC entity according to the first request; The second request is determined according to the target entity information.

3. The method according to claim 2, characterized in that The determining the second request according to the target entity information includes: Determining at least one pending request, wherein the pending request has corresponding candidate entity information; Determine whether there is candidate entity information identical to the target entity information in at least one of the candidate entity information to obtain a reference result; The second request is determined according to the reference result.

4. The method according to claim 3, characterized in that The determining the second request according to the reference result includes: In a case where there is candidate entity information identical to the target entity information in at least one of the candidate entity information, determining a pending request corresponding to the identical candidate entity information as the second request; In a case where there is no candidate entity information identical to the target entity information in at least one of the candidate entity information, the first request is determined as the second request.

5. The method according to claim 4, characterized in that After determining the first request as the second request, the method further includes: The second request, the target entity information, and a corresponding relationship between the second request and the target entity information are stored.

6. The method according to claim 1, characterized in that Before sending the target state information, the method further includes: The target state information is determined.

7. The method according to claim 6, characterized in that The determining the target state information comprises: Determining a current variable interval corresponding to the target RLC entity; Acquire state information corresponding to each sequence number SN in the current variable interval, wherein the plurality of state information includes the first state information; The target state information is generated according to the plurality of state information.

8. The method according to claim 1, characterized in that The receiving the first request comprises: In the process of processing the shard data, receiving the first request; and / or During processing of the complete data, the first request is received.

9. The method according to claim 8, characterized in that The first state information has a corresponding scenario; wherein the scenario includes: a first scenario corresponding to the fragmented data, and / or a second scenario corresponding to the complete data.

10. The method according to claim 9, characterized in that The first scenario includes at least one of the following: The sequence number SN of the completely received fragmented data, and the fragmented data includes a reference field, wherein the reference field is used to trigger the reporting of status information; The SN of the sliced ​​data is outside the receiving window, and the sliced ​​data includes the reference field; The slice data is received repeatedly, and the slice data includes the reference field; The fragmented data is not discarded, and the fragmented data includes the reference field and satisfies a trigger condition, wherein the trigger condition is used to trigger reporting of status information.

11. The method according to claim 9, characterized in that The second scenario includes at least one of the following: The complete data is outside the receiving window, and the complete data includes a reference field, wherein the reference field is used to trigger reporting of status information; The complete data is received repeatedly, and the complete data includes the reference field; The complete data includes the reference field and satisfies a trigger condition, wherein the trigger condition is used to trigger reporting of status information.

12. A communication control device, characterized in that: include: A receiving module, configured to receive a first request, wherein the first request is used to request to send first status information of a target radio link control RLC entity; A determination module, configured to determine a second request according to the first request, wherein the second request is used to request to send target state information of the target RLC entity, and the target state information includes: the first state information; A sending module is used to send the target status information.

13. A communication device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 11 when executed by a processor.

15. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 11 when being executed by a processor.

16. A chip, characterized in that: The chip includes a processing circuit and an interface circuit; wherein the interface circuit is used to read instructions, and the interface circuit sends the instructions to the processing circuit so that the processing circuit executes the method according to any one of claims 1-11.

Images