Method for reporting data volume of data replication, user equipment and network equipment

Abstract

The application discloses a data volume reporting method of data duplication, user equipment, network equipment and computer storage medium, wherein the method comprises the following steps: sending information of reporting data volume of duplicated data and non-duplicated data to a network side; wherein the information of the data volume of the duplicated data and the non-duplicated data is distinguished by at least one of the following information: a logical channel, a logical channel group, a target address and a target address identifier.

Description

Technical Field

[0001] This invention relates to the field of information processing technology, and in particular to a method for reporting the amount of data copied, a user device, a network device, and a computer storage medium. Background Technology

[0002] For carrier aggregation (CA), schemes supporting data duplication utilize PDCP's data duplication function (e.g., Figure 1 As shown, the replicated PDCP PDU is transmitted to two RLC entities (two different logical channels) respectively, and ultimately the replicated PDCP PDU can be transmitted on aggregated carriers of different physical layers, thereby achieving frequency diversity gain to improve data transmission reliability.

[0003] However, when using the above architecture for data transmission, how to enable the network side to know the amount of data transmitted under different transmission modes of the user device is a problem that needs to be solved. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of the present invention provide a method for reporting the amount of data copied, a user device, a network device, and a computer storage medium.

[0005] This invention provides a method for reporting the amount of data copied, applied to user equipment, the method comprising:

[0006] Send information to the network side regarding the amount of replicated and non-replicated data;

[0007] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0008] This invention provides a method for reporting the amount of data copied, applied to network devices, the method comprising:

[0009] Receive information about the amount of copied and non-copied data sent from the user equipment;

[0010] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0011] This invention provides a user equipment, the user equipment comprising:

[0012] The first communication unit sends information to the network side regarding the amount of copied data and non-copied data.

[0013] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0014] This invention provides a network device, the network device comprising:

[0015] The second communication unit receives information about the amount of copied data and non-copied data sent by the user equipment.

[0016] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0017] An embodiment of the present invention provides a user equipment (UE) comprising: a processor and a memory for storing computer programs capable of running on the processor.

[0018] The processor is used to execute the steps of the aforementioned method when running the computer program.

[0019] An embodiment of the present invention provides a network device, comprising: a processor and a memory for storing computer programs capable of running on the processor.

[0020] The processor is used to execute the steps of the aforementioned method when running the computer program.

[0021] An embodiment of the present invention provides a computer storage medium storing computer-executable instructions, which, when executed, implement the aforementioned method steps.

[0022] The technical solution of this invention can use different logical channels, logical channel groups, target addresses, or target address identifiers to distinguish the amount of data reported as copied data and non-copied data to the network side, so that the network side can know the information transmission status of the UE side; thus, the problem that the network side cannot know the amount of data transmitted by the UE in different transmission modes is solved. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of a dual-connection network structure;

[0024] Figure 2 A schematic flowchart of a data replication reporting method provided in an embodiment of the present invention;

[0025] Figure 3This is a schematic diagram of the user equipment composition structure according to an embodiment of the present invention;

[0026] Figure 4 This is a schematic diagram of the network device composition structure according to an embodiment of the present invention;

[0027] Figure 5 This is a schematic diagram of a hardware architecture according to an embodiment of the present invention. Detailed Implementation

[0028] To gain a more detailed understanding of the features and technical content of the embodiments of the present invention, the implementation of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and illustration only and are not intended to limit the embodiments of the present invention.

[0029] Example 1

[0030] This invention provides a method for reporting the amount of data copied, applied to user equipment, the method comprising:

[0031] Send information to the network side regarding the amount of replicated and non-replicated data;

[0032] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0033] In other words, the user equipment needs to use at least one of the following to distinguish the amount of data used for duplication and the amount used for non-duplication: logical channel, logical channel group, destination address, and destination address identifier.

[0034] The user reporting method, namely, sending information about the amount of replicated and non-replicated data to the network side, includes:

[0035] The system uses Radio Resource Control (RRC) information and / or MAC CE to send information to the network side regarding the amount of copied and non-copied data.

[0036] The following will be explained separately, Scenario 1: When using a target address or target address identifier:

[0037] One approach is to report to the network side different target addresses or different target address identifiers for the data volumes that distinguish between replicated and non-replicated data.

[0038] In other words, users report to the network the target address used for duplication and the target address used for non-duplication.

[0039] Another approach is to report to the network side the reliability requirements of replicated data and non-replicated data corresponding to different target addresses or target address identifiers.

[0040] In other words,

[0041] Users can send different data and their corresponding reliability requirements to the network side; then send the corresponding replicated data, its corresponding reliability requirements, and the corresponding data volume to different target addresses or target address identifiers; and also send non-replicated data, its corresponding reliability requirements, and the corresponding data volume.

[0042] The reliability requirement information includes at least one of the following: whether the data is associated with the reliability requirement; and the specific value of the reliability requirement information.

[0043] In other words, whether the target data is related to the reliability requirements can be included in the reliability requirements information; in addition, it can also include the specific data in the reliability requirements information. For example, different data in data 1, 2, and 3 can correspond to reliability requirements A, B, or C, or they can only correspond to a specific value. This is not an exhaustive list.

[0044] Furthermore, information regarding the amount of replicated and non-replicated data reported is sent to the network side, including:

[0045] Information on the amount of replicated data and non-replicated data, distinguished by different destination addresses or identifiers of different destination addresses, will be reported to the network side.

[0046] Furthermore, before performing the aforementioned processing, the network side can also control whether data from a specific target address is allowed to use duplication. Specifically, before sending information to the network side regarding the amount of replicated and non-replicated data, the method further includes:

[0047] The device receives configuration information from the network side; wherein the configuration information includes information on whether the network side allows the terminal device to copy data from the target address or target address identifier.

[0048] Accordingly, if the configuration information is allowed, subsequent processing can be performed; otherwise, data copying will not be performed.

[0049] Then the user distinguishes between different target addresses and / or target address identifiers to report the amount of data used for duplication and the amount used for non-duplication.

[0050] Furthermore, the method also includes: reporting the priority information of the replicated data to the network side. The priority information can be set according to actual conditions, with different replicated data corresponding to different priorities.

[0051] Furthermore, the method also includes: reporting the logical channel or logical channel group information of the replicated data to the network side. The two RLC entities corresponding to the replicated data can be transmitted on different logical channels, so the logical channels of the RLC entities about to transmit the two replicated data are reported to the network side in advance. Furthermore, the logical channels corresponding to the replicated data can be in a specific logical channel group; therefore, the logical channel group corresponding to the replicated data can also be reported to the network side.

[0052] Scenario 2: When using logical channels or logical channel groups for differentiation:

[0053] Receive configuration information sent from the network side; wherein, the configuration information includes the correspondence between the replicated data and non-replicated data configured by the network side and different logical channels or logical channel groups.

[0054] or,

[0055] Receive configuration information sent from the network side; wherein, the configuration information includes the correspondence between different logical channels or logical channel groups configured by the network side and data reliability requirement information.

[0056] In other words, different logical channels or logical channel groups correspond to replicated data and non-replicated data, or different logical channels or logical channel groups correspond to different reliability requirements (e.g., bit error rate).

[0057] It should also be noted that the configuration information includes: the logical channels or logical channel groups corresponding to the two RLC entities of the replicated data. That is, the two RLC entities in the replicated data can also correspond to different logical channels, or the logical channels of the two RLC entities can be in different logical channel groups.

[0058] Furthermore, the configuration information also includes priority information corresponding to different logical channels or different logical channel groups.

[0059] Specifically, sending information about the amount of replicated and non-replicated data to the network side includes: mapping the amount of replicated data and the amount of non-replicated data to different logical channels, different logical channel groups, logical channel identifiers, or identifiers of different logical channel groups, and then reporting them to the network side. This can be understood as the amount of data corresponding to the two RLC entities of replicated data and the amount of non-replicated data being distinguished by different logical channels, different logical channel groups, logical channel identifiers, or identifiers of different logical channel groups, and then reported. For example, according to this configuration, the user maps data used for duplication and data used for non-duplication to different logical channels (groups); the user reports the amount of data used for duplication and data used for non-duplication using different logical channels (groups) and / or logical channel (group) identifiers.

[0060] In addition, similar to scenario 1, the network side will also control whether data from a specific target address is allowed to use duplication; and control the data that can be targeted for a specific priority.

[0061] The configuration of this logical channel (group) can also be combined with priority, that is, different logical channels (groups) not only correspond to whether they are used for duplication, but also to different priorities.

[0062] The information on the amount of replicated data and non-replicated data sent to the network side can be specifically as follows: the amount of data of the two RLC entities of the replicated data can be respectively assigned to different logical channels, or different logical channel identifiers, or different logical channel groups, or different logical channel group identifiers, and then reported to the network side.

[0063] In other words, the number of each RLC entity in the replicated data will also be corresponding to different logical channel identifiers, logical channels, or logical channel groups, or logical channel group identifiers, and will be reported to the network side.

[0064] It should be further noted that the correspondence described in the two scenarios above is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different correspondences between reliability requirements and logical channels or logical channel groups can be configured. This includes whether the logical channel or logical channel group corresponds to the reliability requirements; or, the specific values ​​of the reliability requirement information corresponding to different target addresses or target address identifiers can be different.

[0065] It should also be noted that, in this embodiment, when sending information about the amount of replicated data and non-replicated data to the network side, if the information includes two sets of data with the same priority (replicated data and non-replicated data), it will be processed as follows:

[0066] The system sends information about the amount of replicated and non-replicated data to the network side in a preset order.

[0067] The order is one of the following:

[0068] Prioritize sending information about the amount of data being copied to the network side;

[0069] Prioritize sending information about the amount of non-replicated data to the network side;

[0070] The system can decide on its own priority to send information about the amount of data reported as copied or non-copied data to the network side.

[0071] Specifically, when the information on the amount of reported copied data or non-copied data has the same priority, the information on the amount of reported copied data and non-copied data is sent to the network side in a preset order.

[0072] When the priority of the information on the amount of reported copied data or non-copied data is different, the information on the amount of reported copied data and non-copied data is sent to the network side according to the priority.

[0073] In other words, when the priority of information about the amount of copied data and non-copied data is different, there is no need to compare them in a preset order; they can be reported according to their priority. When the priority of information about the amount of copied data and non-copied data is the same, the information to be reported first should be determined in the manner described above.

[0074] For the specific processing flow provided in this embodiment, in light of the two scenarios described above, please refer to [link / reference]. Figure 2 ,include:

[0075] Step 101: Receive configuration information sent from the network side;

[0076] Step 102: Send information on the amount of replicated data and non-replicated data to the network side; wherein, the information on the amount of replicated data and non-replicated data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0077] The configuration information may include at least a portion of the content in the configuration information described in the aforementioned scenario.

[0078] As can be seen, by adopting the above scheme, different logical channels, logical channel groups, target addresses, or target address identifiers can be used to distinguish the amount of data reported as copied data and non-copied data to the network side, so that the network side can know the information transmission status of the UE side; thus, the problem that the network side cannot know the amount of data transmitted by the UE in different transmission modes is solved.

[0079] Example 2

[0080] This invention provides a method for reporting the amount of data copied, applied to network devices, the method comprising:

[0081] Receive information about the amount of copied and non-copied data sent from the user equipment;

[0082] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0083] In other words, the user equipment needs to use at least one of the following to distinguish the amount of data used for duplication and the amount used for non-duplication: logical channel, logical channel group, destination address, and destination address identifier.

[0084] The information on the amount of copied and non-copied data received from the user equipment includes: receiving the information on the amount of copied and non-copied data received from the user equipment via RRC information and / or MAC CE.

[0085] The following will be explained separately, Scenario 1: When using a target address or target address identifier:

[0086] One approach is to receive different target addresses or different target address identifiers reported by the user equipment to distinguish between the amount of copied data and non-copied data.

[0087] In other words, users report to the network the target address used for duplication and the target address used for non-duplication.

[0088] Another approach is to receive reliability requirement information for replicated data and non-replicated data reported by the user equipment, which correspond to different target addresses or target address identifiers.

[0089] In other words,

[0090] Users can send different data and their corresponding reliability requirements to the network side; then send the corresponding replicated data, its corresponding reliability requirements, and the corresponding data volume to different target addresses or target address identifiers; and also send non-replicated data, its corresponding reliability requirements, and the corresponding data volume.

[0091] The reliability requirement information includes at least one of the following: whether the data is associated with a reliability requirement; and the specific value of the reliability requirement information. That is, whether the target data is associated with a reliability requirement can be included in the reliability requirement information; additionally, it can also include the specific data in the reliability requirement information. For example, different data in data 1, 2, and 3 can correspond to reliability requirements A, B, or C, or they can correspond to only one specific value. This is not an exhaustive list.

[0092] Furthermore, before performing the aforementioned processing, the network side can also control whether data duplication is allowed for a specific target address. Specifically, this involves sending configuration information to the user equipment; wherein the configuration information includes information on whether the terminal device is allowed to copy data from the target address or the target address identifier.

[0093] Accordingly, if the configuration information is allowed, subsequent processing can be performed; otherwise, data copying will not be performed.

[0094] Then the user distinguishes between different target addresses and / or target address identifiers to report the amount of data used for duplication and the amount used for non-duplication.

[0095] Furthermore, the method also includes:

[0096] Obtain priority information for the copied data sent by the user equipment. This priority information can be set according to actual conditions, with different copied data corresponding to different priorities.

[0097] In addition, the logical channel or logical channel group information of the replicated data sent by the user equipment will also be obtained. The two RLC entities corresponding to the replicated data can be transmitted on different logical channels, so the logical channels of the RLC entities about to transmit the two replicated data will be reported to the network side in advance. Furthermore, the two logical channels corresponding to the replicated data can be in different logical channel groups, so the logical channel group corresponding to the replicated data can also be reported to the network side.

[0098] Scenario 2: When using logical channels or logical channel groups for differentiation:

[0099] Send configuration information to the user equipment;

[0100] The configuration information includes the correspondence between replicated and non-replicated data configured on the network side and different logical channels or logical channel groups.

[0101] It should be noted that replicated data and non-replicated data correspond to different logical channels or different groups of logical channels, respectively.

[0102] or,

[0103] Send configuration information to the user equipment;

[0104] The configuration information includes the correspondence between different logical channels or logical channel groups configured on the network side and data reliability requirements.

[0105] In other words, replicated data and non-replicated data correspond to different logical channels or logical channel groups, and each corresponds to reliability requirements (e.g., bit error rate).

[0106] It should also be noted that the configuration information includes: the logical channels or logical channel groups corresponding to the two RLC entities of the replicated data. That is, the two RLC entities in the replicated data can also correspond to different logical channels, or the logical channels of the two RLC entities can be in different logical channel groups.

[0107] Furthermore, the configuration information also includes priority information corresponding to different logical channels or different logical channel groups.

[0108] Specifically, this involves receiving the data volume of replicated data and the data volume of non-replicated data, each corresponding to a different logical channel, a different logical channel group, a logical channel identifier, or a different logical channel group identifier. This can be understood as the data volume of the two RLC entities corresponding to the replicated data and the data volume of non-replicated data being distinguished by different logical channels, different logical channel groups, logical channel identifiers, or different logical channel group identifiers, and then reported. For example, based on this configuration, the user may map data used for duplication and data used for non-duplication to different logical channels (groups); the user may then report the data volume used for duplication and data used for non-duplication using different logical channels (groups) and / or logical channel (group) identifiers.

[0109] In addition, similar to scenario 1, the network side will also control whether data from a specific target address is allowed to use duplication; and control the data that can be targeted for a specific priority.

[0110] The configuration of this logical channel (group) can also be combined with priority, that is, different logical channels (groups) not only correspond to whether they are used for duplication, but also to different priorities.

[0111] Regarding the reception of replicated data, specifically, the data volume of the two RLC entities of the replicated data can be obtained from the different logical channels, or the identifiers of different logical channels, or the different logical channel groups, or the identifiers of different logical channel groups corresponding to the data volume of the two RLC entities of the replicated data.

[0112] In other words, the number of each RLC entity in the replicated data will also be corresponding to different logical channel identifiers, logical channels, or logical channel groups, or logical channel group identifiers, and will be reported to the network side.

[0113] It should be further noted that the correspondence described in the two scenarios above is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different correspondences between reliability requirements and logical channels or logical channel groups can be configured. This includes whether the logical channel or logical channel group corresponds to the reliability requirements; or, the specific values ​​of the reliability requirement information corresponding to different target addresses or target address identifiers can be different.

[0114] It should also be noted that, in this embodiment, when receiving information on the amount of replicated data and non-replicated data reported by the user equipment, if the information includes two sets of data with the same priority (replicated data and non-replicated data), it will be processed as follows:

[0115] Receive information on the amount of copied data and non-copied data sent by user equipment in a preset order;

[0116] The order is one of the following:

[0117] Prioritize sending information about the amount of data being copied;

[0118] Prioritize sending information about the amount of non-replicated data to be reported;

[0119] The user equipment decides to prioritize sending information to the network side regarding the amount of data reported as either copied or non-copied data.

[0120] Specifically, when the information on the amount of copied data or non-copied data reported has the same priority, the system receives the information on the amount of copied data and non-copied data sent by the user equipment in a preset order.

[0121] When the priority of the information on the amount of copied data or non-copied data reported is different, the information on the amount of copied data and non-copied data reported by the user equipment is received according to the priority.

[0122] In other words, when the priority of information about the amount of copied data and non-copied data is different, the comparison can be performed without a preset order, and the data can be received according to the priority. When the priority of information about the amount of copied data and non-copied data is the same, the network device determines which type of information is being received in the manner described above.

[0123] As can be seen, by adopting the above scheme, different logical channels, logical channel groups, target addresses, or target address identifiers can be used to distinguish the amount of data reported as copied data and non-copied data to the network side, so that the network side can know the information transmission status of the UE side; thus, the problem that the network side cannot know the amount of data transmitted by the UE in different transmission modes is solved.

[0124] Example 3

[0125] This invention provides a user equipment, such as... Figure 3 As shown, it includes:

[0126] The first communication unit 31 sends information to the network side regarding the amount of copied data and non-copied data.

[0127] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0128] In other words, the user equipment needs to use at least one of the following to distinguish the amount of data used for duplication and the amount used for non-duplication: logical channel, logical channel group, destination address, and destination address identifier.

[0129] The user reporting method, namely the first communication unit 31, uses Radio Resource Control (RRC) information and / or MAC CE to send information on the amount of copied data and non-copied data to the network side.

[0130] The following will be explained separately, Scenario 1: When using a target address or target address identifier:

[0131] One approach is that the first communication unit 31 reports to the network side different target addresses or different target address identifiers that distinguish between copied data and non-copied data.

[0132] In other words, users report to the network the target address used for duplication and the target address used for non-duplication.

[0133] Another approach is that the first communication unit 31 reports to the network side the reliability requirements information of the copied data and non-copied data corresponding to different target addresses or target address identifiers.

[0134] In other words,

[0135] Users can send different data and their corresponding reliability requirements to the network side; then send the corresponding replicated data, its corresponding reliability requirements, and the corresponding data volume to different target addresses or target address identifiers; and also send non-replicated data, its corresponding reliability requirements, and the corresponding data volume.

[0136] The reliability requirement information includes at least one of the following: whether the data is associated with a reliability requirement; and the specific value of the reliability requirement information. That is, whether the target data is associated with a reliability requirement can be included in the reliability requirement information; additionally, it can also include the specific data in the reliability requirement information. For example, different data in data 1, 2, and 3 can correspond to reliability requirements A, B, or C, or they can correspond to only one specific value. This is not an exhaustive list.

[0137] Furthermore, information on the amount of replicated data and non-replicated data, distinguished by different target addresses or different target address identifiers, will be reported to the network side.

[0138] Furthermore, before performing the aforementioned processing, the network side can also control whether data from a specific target address is allowed to use duplication. Specifically, the user equipment further includes:

[0139] The first processing unit 32 receives configuration information sent from the network side through the first communication unit 31; wherein, the configuration information includes information on whether the network side allows the terminal device to copy data of the target address or target address identifier.

[0140] Accordingly, if the configuration information is allowed, subsequent processing can be performed; otherwise, data copying will not be performed.

[0141] Then the user distinguishes between different target addresses and / or target address identifiers to report the amount of data used for duplication and the amount used for non-duplication.

[0142] The first communication unit 31 can also report the priority information of the copied data to the network side. This priority information can be set according to actual conditions, with different copied data corresponding to different priorities.

[0143] In addition, the logical channel or logical channel group information of the replicated data will be reported to the network side. The two RLC entities corresponding to the replicated data can be transmitted on different logical channels, so the logical channels of the RLC entities about to transmit the two replicated data will be reported to the network side in advance. Furthermore, the logical channels corresponding to the replicated data can be in a specific logical channel group; therefore, the logical channel group corresponding to the replicated data can also be reported to the network side.

[0144] Scenario 2: When using logical channels or logical channel groups for differentiation:

[0145] The first communication unit 31 receives configuration information sent from the network side; wherein, the configuration information includes the correspondence between the replicated data and non-replicated data configured by the network side and different logical channels or logical channel groups.

[0146] or,

[0147] The first communication unit 31 receives configuration information sent from the network side; wherein, the configuration information includes the correspondence between different logical channels or logical channel groups configured by the network side and data reliability requirement information.

[0148] In other words, different logical channels or logical channel groups are assigned to replicated data and non-replicated data respectively, or different logical channels or logical channel groups are assigned to different reliability requirements (e.g., bit error rate).

[0149] It should also be noted that the configuration information includes: the logical channels or logical channel groups corresponding to the two RLC entities of the replicated data. That is, the two RLC entities in the replicated data can also correspond to different logical channels, or the logical channels of the two RLC entities can be in different logical channel groups.

[0150] Furthermore, the configuration information also includes priority information corresponding to different logical channels or different logical channel groups.

[0151] Specifically, the first processing unit 32 reports the data volume of the copied data and the data volume of the non-copied data to the network side, respectively, by mapping them to different logical channels, different logical channel groups, logical channel identifiers, or different logical channel group identifiers. This can be understood as the data volume of the two RLC entities corresponding to the copied data and the data volume of the non-copied data being distinguished by different logical channels, different logical channel groups, logical channel identifiers, or different logical channel group identifiers, and then reported. For example, according to this configuration, the user maps the data used for duplication and the data used for non-duplication to different logical channels (groups); the user reports the data volume used for duplication and the data used for non-duplication using different logical channels (groups) and / or logical channel (group) identifiers.

[0152] In addition, similar to scenario 1, the network side will also control whether data from a specific target address is allowed to use duplication; and control the data that can be targeted for a specific priority.

[0153] The configuration of this logical channel (group) can also be combined with priority, that is, different logical channels (groups) not only correspond to whether they are used for duplication, but also to different priorities.

[0154] The information on the amount of copied data and non-copied data sent to the network side can be as follows: the first processing unit 32 can correspond the data amounts of the two RLC entities of the copied data to different logical channels, or different logical channel identifiers, or different logical channel groups, or different logical channel group identifiers, and report them to the network side through the first communication unit 31.

[0155] In other words, the number of each RLC entity in the replicated data will also be corresponding to different logical channel identifiers, logical channels, or logical channel groups, or logical channel group identifiers, and will be reported to the network side.

[0156] It should be further noted that the correspondence described in the two scenarios above is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different correspondences between reliability requirements and logical channels or logical channel groups can be configured. This includes whether the logical channel or logical channel group corresponds to the reliability requirements; or, the specific values ​​of the reliability requirement information corresponding to different target addresses or target address identifiers can be different.

[0157] It should also be noted that, in this embodiment, when sending information about the amount of replicated data and non-replicated data to the network side, if the information includes two sets of data with the same priority (replicated data and non-replicated data), it will be processed as follows:

[0158] The first processing unit sends information about the amount of copied data and non-copied data to the network side through the first communication unit in a preset order.

[0159] The order is one of the following:

[0160] Prioritize sending information about the amount of data being copied to the network side;

[0161] Prioritize sending information about the amount of non-replicated data to the network side;

[0162] The system can decide on its own priority to send information about the amount of data reported as copied or non-copied data to the network side.

[0163] Specifically, when the information on the amount of reported copied data or non-copied data has the same priority, the information on the amount of reported copied data and non-copied data is sent to the network side through the first communication unit in a preset order.

[0164] When the priority of the information on the amount of reported copied data or non-copied data is different, the information on the amount of reported copied data and non-copied data is sent to the network side through the first communication unit according to the priority.

[0165] In other words, when the priority of information about the amount of copied data and non-copied data is different, there is no need to compare them in a preset order; they can be reported according to their priority. When the priority of information about the amount of copied data and non-copied data is the same, the information to be reported first should be determined in the manner described above.

[0166] As can be seen, by adopting the above scheme, different logical channels, logical channel groups, target addresses, or target address identifiers can be used to distinguish the amount of data reported as copied data and non-copied data to the network side, so that the network side can know the information transmission status of the UE side; thus, the problem that the network side cannot know the amount of data transmitted by the UE in different transmission modes is solved.

[0167] Example 4

[0168] This invention provides a network device, such as... Figure 4 As shown, it includes:

[0169] The second communication unit 41 receives information about the amount of copied data and non-copied data sent by the user equipment.

[0170] The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier.

[0171] In other words, the user equipment needs to use at least one of the following to distinguish the amount of data used for duplication and the amount used for non-duplication: logical channel, logical channel group, destination address, and destination address identifier.

[0172] The second communication unit 41 receives information about the amount of copied data and non-copied data sent by the user equipment through RRC information and / or MAC CE.

[0173] The following will be explained separately, Scenario 1: When using a target address or target address identifier:

[0174] One approach is that the second communication unit 41 receives different target addresses or different target address identifiers reported by the user equipment to distinguish between the amount of copied data and non-copied data.

[0175] In other words, users report to the network the target address used for duplication and the target address used for non-duplication.

[0176] Another approach is that the second communication unit 41 receives the reliability requirement information of the copied data and non-copied data reported by the user equipment, which correspond to different target addresses or target address identifiers.

[0177] In other words,

[0178] Users can send different data and their corresponding reliability requirements to the network side; then send the corresponding replicated data, its corresponding reliability requirements, and the corresponding data volume to different target addresses or target address identifiers; and also send non-replicated data, its corresponding reliability requirements, and the corresponding data volume.

[0179] The reliability requirement information includes at least one of the following: whether the data is associated with a reliability requirement; and the specific value of the reliability requirement information. That is, whether the target data is associated with a reliability requirement can be included in the reliability requirement information; additionally, it can also include the specific data in the reliability requirement information. For example, different data in data 1, 2, and 3 can correspond to reliability requirements A, B, or C, or they can correspond to only one specific value. This is not an exhaustive list.

[0180] Furthermore, before performing the aforementioned processing, the second communication unit 41 sends configuration information to the user equipment; wherein, the configuration information includes information on whether the terminal device is allowed to copy data to the target address or target address identifier.

[0181] Accordingly, if the configuration information is allowed, subsequent processing can be performed; otherwise, data copying will not be performed.

[0182] Then the user distinguishes between different target addresses and / or target address identifiers to report the amount of data used for duplication and the amount used for non-duplication.

[0183] Furthermore, the second communication unit 41 acquires the priority information of the copied data sent by the user equipment. This priority information can be set according to actual conditions, with different copied data corresponding to different priorities.

[0184] In addition, the logical channel or logical channel group information of the replicated data sent by the user equipment will also be obtained. The two RLC entities corresponding to the replicated data can be transmitted on different logical channels, so the logical channels of the RLC entities about to transmit the two replicated data will be reported to the network side in advance. Furthermore, the logical channels corresponding to the replicated data can be in a specific logical channel group; therefore, the logical channel group corresponding to the replicated data can also be reported to the network side.

[0185] Scenario 2: When using logical channels or logical channel groups for differentiation:

[0186] The second communication unit 41 sends configuration information to the user equipment;

[0187] The configuration information includes the correspondence between replicated and non-replicated data configured on the network side and different logical channels or logical channel groups.

[0188] or,

[0189] The second communication unit 41 sends configuration information to the user equipment;

[0190] The configuration information includes the correspondence between different logical channels or logical channel groups configured on the network side and data reliability requirements.

[0191] In other words, different logical channels or logical channel groups correspond to replicated data and non-replicated data, or different logical channels or logical channel groups correspond to different reliability requirements (e.g., bit error rate).

[0192] It should also be noted that the configuration information includes: the logical channels or logical channel groups corresponding to the two RLC entities of the replicated data. That is, the two RLC entities in the replicated data can also correspond to different logical channels, or the logical channels of the two RLC entities can be in different logical channel groups.

[0193] Furthermore, the configuration information also includes priority information corresponding to different logical channels or different logical channel groups.

[0194] Specifically, this involves receiving the data volume of replicated data and the data volume of non-replicated data, each corresponding to a different logical channel, a different logical channel group, a logical channel identifier, or a different logical channel group identifier. This can be understood as the data volume of the two RLC entities corresponding to the replicated data and the data volume of non-replicated data being distinguished by different logical channels, different logical channel groups, logical channel identifiers, or different logical channel group identifiers, and then reported. For example, based on this configuration, the user may map data used for duplication and data used for non-duplication to different logical channels (groups); the user may then report the data volume used for duplication and data used for non-duplication using different logical channels (groups) and / or logical channel (group) identifiers.

[0195] In addition, similar to scenario 1, the network side will also control whether data from a specific target address is allowed to use duplication; and control the data that can be targeted for a specific priority.

[0196] The configuration of this logical channel (group) can also be combined with priority, that is, different logical channels (groups) not only correspond to whether they are used for duplication, but also to different priorities.

[0197] Regarding the reception of copied data, specifically: the network device further includes:

[0198] The second processing unit 42 obtains the data volume of the two RLC entities of the copied data from the different logical channels, or the identifiers of different logical channels, or the different logical channel groups, or the identifiers of different logical channel groups corresponding to the data volume of the two RLC entities of the copied data.

[0199] In other words, the number of each RLC entity in the replicated data will also be corresponding to different logical channel identifiers, logical channels, or logical channel groups, or logical channel group identifiers, and will be reported to the network side.

[0200] It should be further noted that the correspondence described in the two scenarios above is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different correspondences between reliability requirements and logical channels or logical channel groups can be configured. This includes whether the logical channel or logical channel group corresponds to the reliability requirements; or, the specific values ​​of the reliability requirement information corresponding to different target addresses or target address identifiers can be different.

[0201] It should also be noted that, in this embodiment, when sending information about the amount of replicated data and non-replicated data to the network side, if the information includes two sets of data with the same priority (replicated data and non-replicated data), it will be processed as follows:

[0202] The second communication unit receives information about the amount of copied data and non-copied data sent by the user equipment in a preset order;

[0203] The order is one of the following:

[0204] Prioritize sending information about the amount of data being copied;

[0205] Prioritize sending information about the amount of non-replicated data to be reported;

[0206] The user equipment decides to prioritize sending information to the network side regarding the amount of data reported as either copied or non-copied data.

[0207] Specifically, the second communication unit receives information on the amount of copied data and non-copied data sent by the user equipment in a preset order when the priority of the information on the amount of data of the reported copied data and non-copied data is the same.

[0208] When the priority of the information on the amount of copied data or non-copied data reported is different, the information on the amount of copied data and non-copied data reported by the user equipment is received according to the priority.

[0209] In other words, when the priority of information about the amount of copied data and non-copied data is different, there is no need to compare them in a preset order; they can be reported according to their priority. When the priority of information about the amount of copied data and non-copied data is the same, the information to be reported first should be determined in the manner described above.

[0210] As can be seen, by adopting the above scheme, different logical channels, logical channel groups, target addresses, or target address identifiers can be used to distinguish the amount of data reported as copied data and non-copied data to the network side, so that the network side can know the information transmission status of the UE side; thus, the problem that the network side cannot know the amount of data transmitted by the UE in different transmission modes is solved.

[0211] This invention also provides a hardware architecture for a user device or a receiving device, such as... Figure 5 As shown, it includes: at least one processor 51, memory 52, and at least one network interface 53. The various components are coupled together via a bus system 54. It is understood that the bus system 54 is used to implement communication between these components. In addition to a data bus, the bus system 54 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 5 The general labeled all buses as Bus System 54.

[0212] It is understood that the memory 52 in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.

[0213] In some implementations, memory 52 stores executable modules or data structures, or subsets thereof, or extended sets thereof:

[0214] Operating system 521 and application 522.

[0215] The processor 51 is configured to process the method steps of the aforementioned embodiment 1, which will not be described in detail here.

[0216] An embodiment of the present invention provides a computer storage medium storing computer-executable instructions, which, when executed, implement the method steps of the aforementioned embodiment one.

[0217] If the aforementioned apparatus of this invention is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, this invention is not limited to any specific hardware and software combination.

[0218] Accordingly, embodiments of the present invention also provide a computer storage medium storing a computer program configured to execute the data scheduling method of the embodiments of the present invention.

[0219] Although preferred embodiments of the invention have been disclosed for illustrative purposes, those skilled in the art will recognize that various modifications, additions, and substitutions are possible, and therefore the scope of the invention should not be limited to the embodiments described above.

Claims

1. A method for reporting the amount of data copied, applied to a user equipment, the method comprising: Send information to the network side regarding the amount of replicated and non-replicated data; The information regarding the amount of copied data and non-copied data is distinguished using at least one of the following: logical channel, logical channel group, target address, and target address identifier. The method further includes: Receive configuration information sent from the network side; The configuration information includes the correspondence between different logical channels or logical channel groups configured on the network side and data reliability requirements. The reliability requirements information includes at least one of the following: Whether the logical channel or group of logical channels corresponds to the reliability requirements; The specific numerical values ​​of the reliability requirements information corresponding to the logical channel or logical channel group.

2. The method of claim 1, wherein, The information on the amount of replicated and non-replicated data sent to the network side includes: The Radio Resource Control (RRC) information and / or Media Access Control (MAC) control particles (CEs) are used to send information to the network side regarding the amount of replicated and non-replicated data.

3. The method of claim 1, wherein, The method further includes: Report to the network side the different target addresses or different target address identifiers that distinguish between replicated and non-replicated data.

4. The method according to claim 1, wherein, The method further includes: Report to the network side the reliability requirements of replicated data and non-replicated data corresponding to different target addresses or target address identifiers.

5. The method of claim 4, wherein, The reliability requirements information includes at least one of the following: Whether the data is related to reliability requirements, and the specific numerical values ​​of the reliability requirement information.

6. The method of claim 1, wherein, The information on the amount of replicated and non-replicated data sent to the network side includes: Information on the amount of replicated data and non-replicated data, distinguished by different destination addresses or identifiers of different destination addresses, will be reported to the network side.

7. The method of claim 1, wherein, The configuration information includes whether the network side allows the user equipment to copy data from the target address or target address identifier.

8. The method according to any one of claims 1 to 7, wherein, The method further includes: The priority information of the copied data is reported to the network side.

9. The method according to any one of claims 1-7, wherein, The method further includes: The logical channel or logical channel group information of the replicated data is reported to the network side.

10. The method of claim 1, wherein, The configuration information includes the correspondence between replicated and non-replicated data configured on the network side and different logical channels or logical channel groups.

11. The method according to claim 1, wherein, The correspondence is for different target addresses or target address identifiers.

12. The method of claim 1, wherein, The configuration information also includes: The two Radio Link Control (RLC) entities that replicate the data correspond to the logical channels or logical channel groups, respectively.

13. The method according to any one of claims 10-12, wherein, The configuration information also includes: Priority information corresponding to different logical channels or different groups of logical channels.

14. The method according to any one of claims 10-12, wherein, The information on the amount of replicated and non-replicated data sent to the network side includes: The data volume of the copied data and the data volume of the non-copied data are respectively mapped to different logical channels, different logical channel groups, or logical channel identifiers, or different logical channel group identifiers and reported to the network side.

15. The method of any one of claims 10-12, wherein, The information on the amount of replicated and non-replicated data sent to the network side includes: The data volumes of the two RLC entities that replicate the data are respectively associated with different logical channels, or different logical channel identifiers, or different logical channel groups, or different logical channel group identifiers, and reported to the network side.

16. The method according to any one of claims 1-7 or 10-12, wherein, The information on the amount of replicated and non-replicated data sent to the network side includes: The system sends information about the amount of replicated and non-replicated data to the network side in a preset order. The order is one of the following: Prioritize sending information about the amount of data being copied to the network side; Prioritize sending information about the amount of non-replicated data to the network side; The system can decide on its own priority to send information about the amount of data reported as copied or non-copied data to the network side.

17. The method according to claim 16, wherein, The step of sending information about the amount of replicated and non-replicated data to the network side in a preset order includes: When the information on the amount of reported copied data or non-copied data has the same priority, the information on the amount of reported copied data and non-copied data is sent to the network side in a preset order. When the priority of the information on the amount of reported copied data or non-copied data is different, the information on the amount of reported copied data and non-copied data is sent to the network side according to the priority.

18. A method for reporting the amount of data replicated, applied to a network device, the method comprising: Receive information about the amount of copied and non-copied data sent from the user equipment; The information on the amount of copied data and non-copied data is distinguished by at least one of the following: logical channel, logical channel group, target address, and target address identifier; The method further includes: sending configuration information to the user equipment; The configuration information includes the correspondence between different logical channels or logical channel groups configured on the network side and data reliability requirements. The reliability requirements information includes at least one of the following: Whether the logical channel or group of logical channels corresponds to the reliability requirements; The specific numerical values ​​of the reliability requirements information corresponding to the logical channel or logical channel group.

19. The method according to claim 18, wherein, The information regarding the amount of copied and non-copied data received from the user equipment includes: Receive information about the amount of copied and non-copied data from the user equipment via RRC messages and / or MAC CE.

20. The method according to claim 18, wherein, The method further includes: Receive different target addresses or different target address identifiers reported by the user equipment to distinguish between the amount of copied data and non-copied data.

21. The method of claim 18, wherein, The method further includes: Receive reliability requirement information for replicated data and non-replicated data reported by the user equipment, which correspond to different target addresses or target address identifiers.

22. The method of claim 21, wherein, The reliability requirements information includes at least one of the following: Whether the data is related to reliability requirements, and the specific numerical values ​​of the reliability requirement information.

23. The method according to claim 18, wherein, The configuration information includes whether the user equipment is allowed to copy data from the target address or target address identifier.

24. The method according to any one of claims 18-23, wherein, The method further includes: Obtain priority information of the copied data sent by the user equipment.

25. The method according to any one of claims 18-23, wherein, The method further includes: Obtain the logical channel or logical channel group information of the copied data sent by the user equipment.

26. The method according to claim 18, wherein, The configuration information includes the correspondence between replicated and non-replicated data configured on the network side and different logical channels or logical channel groups.

27. The method according to claim 18, wherein, The correspondence is different for different target addresses or target address identifiers.

28. The method according to claim 18, wherein, The configuration information also includes: The two RLC entities of the replicated data correspond to the logical channels or logical channel groups, respectively.

29. The method according to any one of claims 26-28, wherein, The configuration information also includes: Priority information corresponding to different logical channels or different groups of logical channels.

30. The method according to any one of claims 26-28, wherein, The information regarding the amount of copied and non-copied data received from the user equipment includes: The amount of replicated data and the amount of non-replicated data received, each corresponding to a different logical channel, a different logical channel group, a logical channel identifier, or a different logical channel group identifier.

31. The method according to any one of claims 26-28, wherein, The information regarding the amount of copied and non-copied data received from the user equipment includes: The data volume of the two RLC entities of the replicated data is obtained from the different logical channels, or the identifiers of different logical channels, or the different logical channel groups, or the identifiers of different logical channel groups corresponding to the data volume of the two RLC entities of the replicated data.

32. The method according to any one of claims 18-23 or 26-28, wherein, The information regarding the amount of copied and non-copied data received from the user equipment includes: Receive information on the amount of copied data and non-copied data sent by user equipment in a preset order; The order is one of the following: Prioritize sending information about the amount of data being copied; Prioritize sending information about the amount of non-replicated data to be reported; The user equipment decides to prioritize sending information to the network side regarding the amount of data reported as either copied or non-copied data.

33. The method according to claim 32, wherein, The information regarding the amount of copied and non-copied data sent by the user equipment in a preset order includes: When the priority of the reported data volume information of copied data or non-copied data is the same, the system receives the data volume information of copied data and non-copied data sent by the user equipment in a preset order. When the priority of the information on the amount of copied data or non-copied data reported is different, the information on the amount of copied data and non-copied data reported by the user equipment according to the priority is received.

34. A user equipment, the user equipment comprising: The first communication unit sends information to the network side regarding the amount of copied data and non-copied data. The information regarding the amount of copied data and non-copied data is distinguished using at least one of the following: logical channel, logical channel group, target address, and target address identifier. The user equipment further includes: The first processing unit receives configuration information sent from the network side through the first communication unit; The configuration information includes the correspondence between different logical channels or logical channel groups configured on the network side and data reliability requirements. The reliability requirements information includes at least one of the following: Whether the logical channel or group of logical channels corresponds to the reliability requirements; The specific numerical values ​​of the reliability requirements information corresponding to the logical channel or logical channel group.

35. The user equipment according to claim 34, wherein, The first communication unit uses Radio Resource Control (RRC) information and / or MAC CE to send information to the network side regarding the amount of copied data and non-copied data.

36. The user equipment according to claim 34, wherein, The first communication unit reports to the network side different target addresses or different target address identifiers that distinguish between copied data and non-copied data.

37. The user equipment according to claim 34, wherein, The first communication unit reports to the network side the reliability requirements information of the copied data and non-copied data corresponding to different target addresses or target address identifiers.

38. The user equipment according to claim 37, wherein, The reliability requirements information includes at least one of the following: Whether the data is related to reliability requirements, and the specific numerical values ​​of the reliability requirement information.

39. The user equipment according to claim 34, wherein, The first communication unit reports information about the amount of copied data and non-copied data that are distinguished by different target addresses or by different target address identifiers to the network side.

40. The user equipment of claim 34, wherein, The configuration information includes whether the network side allows the user equipment to copy data from the target address or target address identifier.

41. The user equipment of any of claims 34-40, wherein, The first communication unit reports the priority information of the copied data to the network side.

42. The user equipment of any of claims 34-40, wherein, The first communication unit reports the logical channel or logical channel group information of the copied data to the network side.

43. The user equipment of claim 34, wherein, The configuration information includes the correspondence between replicated and non-replicated data configured on the network side and different logical channels or logical channel groups.

44. The user equipment according to claim 34, wherein, The correspondence is different for different target addresses or target address identifiers.

45. The user equipment of claim 34, wherein, The configuration information also includes: The two RLC entities of the replicated data correspond to the logical channels or logical channel groups, respectively.

46. The user equipment of any of claims 43-45, wherein, The configuration information also includes: Priority information corresponding to different logical channels or different groups of logical channels.

47. The user equipment of any of claims 43-45, wherein, The user equipment also includes: The first processing unit maps the amount of copied data and the amount of non-copied data to different logical channels, different logical channel groups, logical channel identifiers, or identifiers of different logical channel groups, and reports them to the network side through the first communication unit.

48. The user equipment according to any one of claims 43-45, wherein, The first processing unit assigns the data volumes of the two RLC entities that are copying the data to different logical channels, or different logical channel identifiers, or different logical channel groups, or different logical channel group identifiers, and reports them to the network side through the first communication unit.

49. The user equipment of any of claims 34-40 or 43-45, wherein, The first processing unit sends information about the amount of copied data and non-copied data to the network side through the first communication unit in a preset order. The order is one of the following: Prioritize sending information about the amount of data being copied to the network side; Prioritize sending information about the amount of non-replicated data to the network side; The system can decide on its own priority to send information about the amount of data reported as copied or non-copied data to the network side.

50. The user equipment of claim 49, wherein, The first processing unit, when the priority of the information on the amount of reported copied data or non-copied data is the same, sends the information on the amount of reported copied data and non-copied data to the network side in a preset order through the first communication unit. When the priority of the information on the amount of reported copied data or non-copied data is different, the information on the amount of reported copied data and non-copied data is sent to the network side through the first communication unit according to the priority.

51. A network device, the network device comprising: The second communication unit receives information about the amount of copied data and non-copied data sent by the user equipment, and sends configuration information to the user equipment. The information regarding the amount of copied data and non-copied data is distinguished using at least one of the following: logical channel, logical channel group, target address, and target address identifier. The configuration information includes the correspondence between different logical channels or logical channel groups configured on the network side and data reliability requirements. The reliability requirements information includes at least one of the following: Whether the logical channel or group of logical channels corresponds to the reliability requirements; The specific numerical values ​​of the reliability requirements information corresponding to the logical channel or logical channel group.

52. The network device of claim 51, wherein, The second communication unit receives information about the amount of copied data and non-copied data sent by the user equipment via RRC information and / or MAC CE.

53. The network device of claim 51, wherein, The second communication unit receives different target addresses or different target address identifiers reported by the user equipment to distinguish between copied data and non-copied data.

54. The network device of claim 53, wherein, The second communication unit receives reliability requirement information for copied data and non-copied data reported by the user equipment, which correspond to different target addresses or target address identifiers.

55. The network device of claim 54, wherein, The reliability requirements information includes at least one of the following: Whether the data is related to reliability requirements, and the specific numerical values ​​of the reliability requirement information.

56. The network device of claim 54, wherein, The configuration information includes whether the user equipment is allowed to copy data from the target address or target address identifier.

57. The network device of any of claims 54-56, wherein, The second communication unit acquires the priority information of the copied data sent by the user equipment.

58. The network device of any of claims 54-56, wherein, The second communication unit acquires the logical channel or logical channel group information of the copied data sent by the user equipment.

59. The network device of claim 54, wherein, The configuration information includes the correspondence between replicated and non-replicated data configured on the network side and different logical channels or logical channel groups.

60. The network device according to claim 54, wherein, The correspondence is different for different target addresses or target address identifiers.

61. The network device of claim 54, wherein, The configuration information also includes: The two RLC entities of the replicated data correspond to the logical channels or logical channel groups, respectively.

62. The network device of any of claims 59-61, wherein, The configuration information also includes: Priority information corresponding to different logical channels or different groups of logical channels.

63. The network device of any of claims 59-61, wherein, The second communication unit receives the amount of copied data and the amount of non-copied data corresponding to different logical channels, different logical channel groups, logical channel identifiers, or identifiers of different logical channel groups.

64. The network device of any of claims 59-61, wherein, The network device also includes: The second processing unit obtains the data volume of the two RLC entities of the copied data from the different logical channels, or the identifiers of different logical channels, or the different logical channel groups, or the identifiers of different logical channel groups corresponding to the data volume of the two RLC entities of the copied data.

65. The network device of any of claims 51-56 or 59-61, wherein, The second communication unit receives information about the amount of copied data and non-copied data sent by the user equipment in a preset order; The order is one of the following: Prioritize sending information about the amount of data being copied; Prioritize sending information about the amount of non-replicated data to be reported; The user equipment decides to prioritize sending information to the network side regarding the amount of data reported as either copied or non-copied data.

66. The network device of claim 65, wherein, The second communication unit receives information on the amount of copied data and non-copied data sent by the user equipment in a preset order when the priority of the information on the amount of copied data or non-copied data is the same. When the priority of the information on the amount of copied data or non-copied data reported is different, the information on the amount of copied data and non-copied data reported by the user equipment is received according to the priority.

67. A user equipment comprising: The processor and the memory used to store computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 1-17.

68. A network device comprising: The processor and the memory used to store computer programs that can run on the processor. When the processor is used to run the computer program, it performs the steps of the method according to any one of claims 18-33.

69. A computer storage medium storing computer-executable instructions that, when executed, perform the steps of the method according to any one of claims 1-33.

Images