WO2019140872A1 - 数据复制的数据量的上报方法、用户设备及网络设备 - Google Patents
数据复制的数据量的上报方法、用户设备及网络设备 Download PDFInfo
- Publication number
- WO2019140872A1 WO2019140872A1 PCT/CN2018/095205 CN2018095205W WO2019140872A1 WO 2019140872 A1 WO2019140872 A1 WO 2019140872A1 CN 2018095205 W CN2018095205 W CN 2018095205W WO 2019140872 A1 WO2019140872 A1 WO 2019140872A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- information
- logical channel
- amount
- replicated
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
Definitions
- the present invention relates to the field of information processing technologies, and in particular, to a method for reporting data amount of data replication, a user equipment, a network device, and a computer storage medium.
- the data duplication scheme supports the PDCP replication data function (as shown in Figure 1), so that the replicated PDCP PDUs are transmitted to two RLC entities (two different). Logical channel), and finally ensure that the copied PDCP PDU can be transmitted on different physical layer aggregate carriers to achieve frequency diversity gain to improve data transmission reliability.
- an embodiment of the present invention provides a method for reporting data amount of data replication, a user equipment, a network device, and a computer storage medium.
- An embodiment of the present invention provides a method for reporting data volume of data replication, which is applied to a user equipment, where the method includes:
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- An embodiment of the present invention provides a method for reporting data volume of data replication, which is applied to a network device, where the method includes:
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- An embodiment of the present invention provides a user equipment, where the user equipment includes:
- the first communication unit transmits, to the network side, information that reports the amount of data of the copied data and the non-replicated data;
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- the embodiment of the invention provides a network device, where the network device includes:
- a second communication unit which receives information about the copy data sent by the user equipment and the data amount of the non-replicated data
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- a user equipment UE provided by an embodiment of the present invention includes: a processor and a memory for storing a computer program capable of running on the processor,
- processor is configured to perform the steps of the foregoing method when the computer program is run.
- a network device provided by an embodiment of the present invention includes: a processor and a memory for storing a computer program capable of running on a processor,
- processor is configured to perform the steps of the foregoing method when the computer program is run.
- a computer storage medium is provided by the embodiment of the present invention.
- the computer storage medium stores computer executable instructions, and the foregoing method steps are implemented when the computer executable instructions are executed.
- the technical solution of the embodiment of the present invention can use different logical channels, logical channel groups, target addresses, or target address identifiers to distinguish the data amount of the reported duplicate data and the non-replicated data to the network side, so that the network side can learn the UE side.
- the information transmission situation thus, the problem that the network side cannot know the amount of data transmitted by the UE in different transmission modes is solved.
- 1 is a schematic diagram of a dual connectivity network structure
- FIG. 2 is a schematic flowchart of a method for reporting data volume of data replication according to an embodiment of the present invention
- FIG. 3 is a schematic structural diagram of a user equipment according to an embodiment of the present invention.
- FIG. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention.
- FIG. 5 is a schematic diagram of a hardware architecture according to an embodiment of the present invention.
- An embodiment of the present invention provides a method for reporting data volume of data replication, which is applied to a user equipment, and the method includes:
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- the user equipment needs to report the amount of data for duplication and for non-duplication using at least one of the following: logical channel, logical channel group, target address, target address identifier.
- the manner in which the user reports includes:
- the radio resource control RRC information, and/or MAC CE transmits information of the reported data amount of the copied data and the non-replicated data to the network side.
- One way is to report different target addresses or different target address identifiers that distinguish the data volume of the duplicated data and the non-replicated data to the network side.
- the user reports the destination address for duplication and the destination address for non-duplication to the network.
- Another way is to report the replication data corresponding to the different target address or the target address identifier and the reliability requirement information of the non-replicated data to the network side.
- the user may send the reliability requirement information corresponding to different data to the network side; then, the corresponding copy data, the corresponding reliability requirement information, and the corresponding data amount are sent in different target addresses or destination address identifiers, and the data is also sent.
- the reliability requirement information includes at least one of the following: whether the data is associated with a reliability requirement; and a specific value of the reliability requirement information.
- whether the target data is related to the reliability requirement may be included in the reliability requirement information; in addition, specific data in the reliability requirement information may be included, for example, different in the data 1, 2, and 3
- the data may correspond to the reliability requirement A or B or C, or may correspond to only one of the specific values, and is not exhaustive here.
- the information for reporting the amount of data of the copied data and the non-replicated data to the network side includes:
- the information of the copy data and the data amount of the non-replicated data which are distinguished by the different target addresses or the identifiers of the different target addresses are reported to the network side.
- the network side may further control whether to allow data of a specific target address to use duplication.
- the method further sends information for reporting the amount of data of the copied data and the non-replicated data to the network side.
- the configuration information sent by the network side is received.
- the configuration information includes information about whether the network side allows the terminal device to perform data replication on the target address or the target address identifier.
- the user then uses different target addresses, and/or the destination address identifiers to report the amount of data used for duplication and for non-duplication.
- the method further includes: reporting, to the network side, priority information of the copied data.
- the priority information may be set according to actual conditions, and different duplicate data may correspond to different priorities.
- the method further includes: reporting, to the network side, the logical channel of the replicated data, or the logical channel group information.
- the two RLC entities corresponding to the duplicate data may be sent on different logical channels respectively, so the logical channel where the RLC entity that will send the two duplicate data is located is reported to the network side in advance; and further, the data is copied.
- the corresponding logical channel 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.
- configuration information includes the mapping relationship between the replication data and the non-replicated data configured by the network side and different logical channels or logical channel groups.
- Configuration information sent by the network side where the configuration information includes a correspondence between different logical channels configured by the network side, or logical channel groups, and data reliability requirement information.
- the duplicated data and the non-replicated data respectively correspond to different logical channels or logical channel groups, or respectively correspond to different logical channels or logical channel groups for different reliability requirements (for example, may be bit error rates). .
- the configuration information further includes: a logical channel or a logical channel group corresponding to the two RLC entities of the duplicate data. That is to say, the two RLC entities corresponding to the duplicate data may also correspond to different logical channels, or the logical channels where the two RLC entities are located respectively in different logical channel groups.
- the configuration information further includes: different logical channels, or priority information corresponding to different logical channel groups.
- the sending, to the network side, information for reporting the amount of data of the copied data and the non-replicated data includes: respectively, the data amount of the copied data and the data amount of the non-replicated data are respectively mapped to different logical channels, or different logics.
- the identifier of the channel group or the logical channel or the identifier of the different logical channel group is reported to the network side. It can be understood that the data amount of the corresponding two RLC entities of the copied data and the data amount of the non-replicated data respectively pass through the adopted logical channel, or different logical channel groups, or the identification of the logical channel, or adopt different The identification of the logical channel group is distinguished and then reported.
- the user respectively associates data for duplication and for non-duplication into different logical channels (groups); users use different logical channels (groups), and/or logical channel (group) identifiers. Reports the amount of data used for duplication and for non-duplication.
- the network side also controls whether data for a specific target address is allowed to use duplication; and control can be targeted to data of a particular priority.
- the configuration of the logical channel (group) can also be combined with the priority, that is, different logical channels (groups) not only correspond to whether it is used for duplication but also correspond to different priorities.
- the number corresponding to each RLC entity in the replicated data is also corresponding to the identifier of the logical channel, the logical channel, or the logical channel group, or the logical channel group identifier, and is reported to the network side.
- the corresponding relationship in the foregoing two scenarios is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different reliability requirements and logical channel or logical channel group correspondence may be configured, including whether the logical channel or the logical channel group corresponds to the reliability requirement. Or, the specific value of the reliability requirement information corresponding to the different target address or the target address identifier may be different.
- the information of the data amount of the reported copy data or the non-replicated data has the same priority
- the information of the reported copy data and the data amount of the non-replicated data is sent to the network side in a preset order
- the information of the reported copy data and the data amount of the non-replicated data is transmitted to the network side according to the priority.
- the comparison of the preset order may not be performed, and the report may be performed according to the priority; when the data of the data is copied or the data of the non-replicated data
- the information of the priority report is determined in the above manner.
- FIG. 2 the specific processing flow provided by this embodiment can be seen in FIG. 2, including:
- Step 101 Receive configuration information sent by the network side.
- Step 102 Send, to the network side, information that reports the amount of data of the copied data and the non-replicated data; wherein the information of the data amount of the copied data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group , target address, target address identifier.
- the configuration information may include at least part of the content in the configuration information described in the foregoing scenario.
- the embodiment of the invention provides a method for reporting data volume of data replication, which is applied to a network device, and the method includes:
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- the user equipment needs to report the amount of data for duplication and for non-duplication using at least one of the following: logical channel, logical channel group, target address, target address identifier.
- One way is to receive different target addresses or different target address identifiers reported by the user equipment for distinguishing the data amount of the copied data and the non-replicated data.
- the user reports the destination address for duplication and the destination address for non-duplication to the network.
- the other method is: receiving the replication data corresponding to the different target address or the target address and the reliability requirement information of the non-replicated data reported by the user equipment.
- the user may send the reliability requirement information corresponding to different data to the network side; then, the corresponding copy data, the corresponding reliability requirement information, and the corresponding data amount are sent in different target addresses or destination address identifiers, and the data is also sent.
- the reliability requirement information includes at least one of the following: whether the data is associated with a reliability requirement; and a specific value of the reliability requirement information. That is to say, whether the target data is related to the reliability requirement may be included in the reliability requirement information; in addition, specific data in the reliability requirement information may be included, for example, different in the data 1, 2, and 3
- the data may correspond to the reliability requirement A or B or C therein, or may only correspond to one of the specific values, and is not exhaustive here.
- the network side may further control whether the data of the specific target address is allowed to be used, specifically: sending configuration information to the user equipment, where the configuration information includes whether the terminal device is allowed to be allowed. Information for data copying of the target address or the target address identifier.
- the user then uses different target addresses, and/or the destination address identifiers to report the amount of data used for duplication and for non-duplication.
- the method further includes:
- the priority information may be set according to actual conditions, and different duplicate data may correspond to different priorities.
- a logical channel or logical channel group information of the duplicated data sent by the user equipment is also obtained.
- the two RLC entities corresponding to the duplicate data may be sent on different logical channels respectively, so the logical channel where the RLC entity that will send the two duplicate data is located is reported to the network side in advance; and further, the data is copied.
- the corresponding two logical channels can be in different logical channel groups. Therefore, the logical channel group corresponding to the replicated data can also be reported to the network side.
- the configuration information includes a mapping relationship between the replicated data and the non-replicated data configured on the network side, and different logical channels or logical channel groups.
- replicated data and the non-replicated data respectively correspond to different logical channels or different logical channel groups.
- the configuration information includes a correspondence between different logical channels configured on the network side, or logical channel groups, and data reliability requirement information.
- the duplicated data and the non-replicated data respectively correspond to different logical channels or logical channel groups, and respectively correspond to reliability requirement information (for example, may be a bit error rate).
- the configuration information further includes: a logical channel or a logical channel group corresponding to the two RLC entities of the duplicate data. That is to say, the two RLC entities corresponding to the duplicate data may also correspond to different logical channels, or the logical channels where the two RLC entities are located respectively in different logical channel groups.
- the configuration information further includes: different logical channels, or priority information corresponding to different logical channel groups.
- the data amount of the copy data corresponding to the different logical channels, or the different logical channel groups, or the identification of the logical channels, or the identification of the different logical channel groups, and the data amount of the non-replicated data are respectively received. It can be understood that the data amount of the corresponding two RLC entities of the copied data and the data amount of the non-replicated data respectively pass through the adopted logical channel, or different logical channel groups, or the identification of the logical channel, or adopt different The identification of the logical channel group is distinguished and then reported.
- the user respectively associates data for duplication and for non-duplication into different logical channels (groups); users use different logical channels (groups), and/or logical channel (group) identifiers. Reports the amount of data used for duplication and for non-duplication.
- the network side also controls whether data for a specific target address is allowed to use duplication; and control can be targeted to data of a particular priority.
- the configuration of the logical channel (group) can also be combined with the priority, that is, different logical channels (groups) not only correspond to whether it is used for duplication but also correspond to different priorities.
- the receiving of the duplicate data may be: a different logical channel corresponding to the data volume of the two RLC entities of the copied data, or an identifier of a different logical channel, or a different logical channel group, or a different logic.
- the identifier of the channel group the data amount of the two RLC entities of the copied data is obtained.
- the number corresponding to each RLC entity in the replicated data is also corresponding to the identifier of the logical channel, the logical channel, or the logical channel group, or the logical channel group identifier, and is reported to the network side.
- the corresponding relationship in the foregoing two scenarios is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different reliability requirements and logical channel or logical channel group correspondence may be configured, including whether the logical channel or the logical channel group corresponds to the reliability requirement. Or, the specific value of the reliability requirement information corresponding to the different target address or the target address identifier may be different.
- the user equipment determines to preferentially send information that reports the amount of data of the copied data or the non-replicated data to the network side.
- the information of the data amount of the reported copy data or the non-replicated data has the same priority, the information of the copy data sent by the user equipment in a preset order and the data amount of the non-replicated data are received;
- the receiving user equipment reports the data amount of the copy data and the non-replicated data according to the priority.
- the comparison may be performed in a preset order, and the reception may be performed according to the priority; when the data of the data is copied or the data is not copied.
- the network device determines which information the currently received information is in the above manner.
- An embodiment of the present invention provides a user equipment, as shown in FIG. 3, including:
- the first communication unit 31 transmits, to the network side, information that reports the amount of data of the copied data and the non-replicated data;
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- the user equipment needs to report the amount of data for duplication and for non-duplication using at least one of the following: logical channel, logical channel group, target address, target address identifier.
- the manner in which the user reports uses the radio resource control RRC information, and/or the MAC CE, to transmit information indicating the amount of data of the copied data and the non-replicated data to the network side.
- One way is that the first communication unit 31 reports to the network side a different target address that distinguishes the data amount of the duplicated data and the non-replicated data, or a different target address identifier.
- the user reports the destination address for duplication and the destination address for non-duplication to the network.
- the first communication unit 31 reports to the network side the replication request data corresponding to the different target address or the target address and the reliability requirement information of the non-replicated data.
- the user may send the reliability requirement information corresponding to different data to the network side; then, the corresponding copy data, the corresponding reliability requirement information, and the corresponding data amount are sent in different target addresses or destination address identifiers, and the data is also sent.
- the reliability requirement information includes at least one of the following: whether the data is associated with a reliability requirement; and a specific value of the reliability requirement information. That is to say, whether the target data is related to the reliability requirement may be included in the reliability requirement information; in addition, specific data in the reliability requirement information may be included, for example, different in the data 1, 2, and 3
- the data may correspond to the reliability requirement A or B or C therein, or may only correspond to one of the specific values, and is not exhaustive here.
- the information of the copy data and the data amount of the non-replicated data that are distinguished by the different target addresses or the identifiers of the different target addresses are reported to the network side.
- the network side may further control whether to allow data of a specific target address to use duplication.
- the user equipment further includes:
- the first processing unit 32 receives, by the first communication unit 31, configuration information sent by the network side, where the configuration information includes whether the network side allows the terminal device to identify the target address or the target address. Information for data replication.
- the user then uses different target addresses, and/or the destination address identifiers to report the amount of data used for duplication and for non-duplication.
- the first communication unit 31 can also report the priority information of the copied data to the network side.
- the priority information may be set according to actual conditions, and different duplicate data may correspond to different priorities.
- the logical channel of the duplicated data or the logical channel group information is also reported to the network side.
- the two RLC entities corresponding to the duplicate data may be sent on different logical channels respectively, so the logical channel where the RLC entity that will send the two duplicate data is located is reported to the network side in advance; and further, the data is copied.
- the corresponding logical channel 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.
- the first communication unit 31 receives the configuration information sent by the network side, where the configuration information includes the mapping relationship between the replication data and the non-replication data configured by the network side and different logical channels or logical channel groups.
- the first communication unit 31 receives configuration information sent by the network side, where the configuration information includes a correspondence between different logical channels configured by the network side, or logical channel groups, and data reliability requirement information.
- the duplicated data and the non-replicated data respectively correspond to different logical channels or logical channel groups
- the duplicated data and the non-replicated data respectively correspond to different logical channels or logical channel groups, or for different reliability requirements (
- the error rate may correspond to a different logical channel or logical channel group.
- the configuration information further includes: a logical channel or a logical channel group corresponding to the two RLC entities of the duplicate data. That is to say, the two RLC entities corresponding to the duplicate data may also correspond to different logical channels, or the logical channels where the two RLC entities are located respectively in different logical channel groups.
- the configuration information further includes: different logical channels, or priority information corresponding to different logical channel groups.
- the first processing unit 32 respectively maps the data amount of the copied data and the data amount of the non-replicated data to different logical channels, or different logical channel groups, or logical channel identifiers, or different logics.
- the identifier of the channel group is reported to the network side. It can be understood that the data amount of the corresponding two RLC entities of the copied data and the data amount of the non-replicated data respectively pass through the adopted logical channel, or different logical channel groups, or the identification of the logical channel, or adopt different The identification of the logical channel group is distinguished and then reported.
- the user respectively associates data for duplication and for non-duplication into different logical channels (groups); users use different logical channels (groups), and/or logical channel (group) identifiers. Reports the amount of data used for duplication and for non-duplication.
- the network side also controls whether data for a specific target address is allowed to use duplication; and control can be targeted to data of a particular priority.
- the configuration of the logical channel (group) can also be combined with the priority, that is, different logical channels (groups) not only correspond to whether it is used for duplication but also correspond to different priorities.
- the sending, to the network side, the information of the data amount of the reported data and the non-replicated data, wherein the sending of the copy data may be: the first processing unit 32, the data volume of the two RLC entities that will copy the data
- the identifiers of different logical channels, or different logical channels, or different logical channel groups, or different logical channel groups, are respectively reported to the network side by the first communication unit 31.
- the number corresponding to each RLC entity in the replicated data is also corresponding to the identifier of the logical channel, the logical channel, or the logical channel group, or the logical channel group identifier, and is reported to the network side.
- the corresponding relationship in the foregoing two scenarios is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different reliability requirements and logical channel or logical channel group correspondence may be configured, including whether the logical channel or the logical channel group corresponds to the reliability requirement. Or, the specific value of the reliability requirement information corresponding to the different target address or the target address identifier may be different.
- the first processing unit sends, by the first communication unit, the information of the reported data volume and the data amount of the non-replicated data to the network side in a preset order;
- the information of the data amount of the reported copy data or the non-replicated data has the same priority
- the information of the reported copy data and the data amount of the non-replicated data is sent to the network side by the first communication unit in a preset order.
- the first communication unit transmits the information of the reported data amount of the copy data and the non-replicated data to the network side according to the priority.
- the comparison of the preset order may not be performed, and the report may be performed according to the priority; when the data of the data is copied or the data of the non-replicated data
- the information of the priority report is determined in the above manner.
- An embodiment of the present invention provides a network device, as shown in FIG. 4, including:
- the second communication unit 41 receives the data of the copy data sent by the user equipment and the data amount of the non-replicated data
- the information of the data volume of the duplicated data and the non-replicated data is distinguished by using at least one of the following information: a logical channel, a logical channel group, a target address, and a target address identifier.
- the user equipment needs to report the amount of data for duplication and for non-duplication using at least one of the following: logical channel, logical channel group, target address, target address identifier.
- the second communication unit 41 receives the copy data sent by the user equipment and the data amount of the non-replicated data through the RRC information, and/or the MAC CE.
- the second communication unit 41 receives different target addresses or different target address identifiers reported by the user equipment for distinguishing the data amount of the copied data and the non-replicated data.
- the user reports the destination address for duplication and the destination address for non-duplication to the network.
- the second communication unit 41 receives the replication data corresponding to the different target address or the target address and the reliability requirement information of the non-replicated data reported by the user equipment.
- the user may send the reliability requirement information corresponding to different data to the network side; then, the corresponding copy data, the corresponding reliability requirement information, and the corresponding data amount are sent in different target addresses or destination address identifiers, and the data is also sent.
- the reliability requirement information includes at least one of the following: whether the data is associated with a reliability requirement; and a specific value of the reliability requirement information. That is to say, whether the target data is related to the reliability requirement may be included in the reliability requirement information; in addition, specific data in the reliability requirement information may be included, for example, different in the data 1, 2, and 3
- the data may correspond to the reliability requirement A or B or C therein, or may only correspond to one of the specific values, and is not exhaustive here.
- the second communication unit 41 sends configuration information to the user equipment, where the configuration information includes whether the terminal device is allowed to perform data replication on the target address or the target address identifier. information.
- the user then uses different target addresses, and/or the destination address identifiers to report the amount of data used for duplication and for non-duplication.
- the second communication unit 41 acquires priority information of the copied data sent by the user equipment.
- the priority information may be set according to actual conditions, and different duplicate data may correspond to different priorities.
- a logical channel or logical channel group information of the duplicated data sent by the user equipment is also obtained.
- the two RLC entities corresponding to the duplicate data may be sent on different logical channels respectively, so the logical channel where the RLC entity that will send the two duplicate data is located is reported to the network side in advance; and further, the data is copied.
- the corresponding logical channel 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.
- the second communication unit 41 sends configuration information to the user equipment
- the configuration information includes a mapping relationship between the replicated data and the non-replicated data configured on the network side, and different logical channels or logical channel groups.
- the second communication unit 41 sends configuration information to the user equipment
- the configuration information includes a correspondence between different logical channels configured on the network side, or logical channel groups, and data reliability requirement information.
- the duplicated data and the non-replicated data respectively correspond to different logical channels or logical channel groups, or respectively correspond to different logical channels or logical channel groups for different reliability requirements (for example, may be bit error rates). .
- the configuration information further includes: a logical channel or a logical channel group corresponding to the two RLC entities of the duplicate data. That is to say, the two RLC entities corresponding to the duplicate data may also correspond to different logical channels, or the logical channels where the two RLC entities are located respectively in different logical channel groups.
- the configuration information further includes: different logical channels, or priority information corresponding to different logical channel groups.
- the data amount of the copy data corresponding to the different logical channels, or the different logical channel groups, or the identification of the logical channels, or the identification of the different logical channel groups, and the data amount of the non-replicated data are respectively received. It can be understood that the data amount of the corresponding two RLC entities of the copied data and the data amount of the non-replicated data respectively pass through the adopted logical channel, or different logical channel groups, or the identification of the logical channel, or adopt different The identification of the logical channel group is distinguished and then reported.
- the user respectively associates data for duplication and for non-duplication into different logical channels (groups); users use different logical channels (groups), and/or logical channel (group) identifiers. Reports the amount of data used for duplication and for non-duplication.
- the network side also controls whether data for a specific target address is allowed to use duplication; and control can be targeted to data of a particular priority.
- the configuration of the logical channel (group) can also be combined with the priority, that is, different logical channels (groups) not only correspond to whether it is used for duplication but also correspond to different priorities.
- the network device may further include:
- the second processing unit 42 identifies different logical channels, or different logical channel identifiers, or different logical channel groups, or different logical channel groups, respectively, from the data amounts of the two RLC entities of the copied data. The amount of data of the two RLC entities that obtain the replicated data.
- the number corresponding to each RLC entity in the replicated data is also corresponding to the identifier of the logical channel, the logical channel, or the logical channel group, or the logical channel group identifier, and is reported to the network side.
- the corresponding relationship in the foregoing two scenarios is different for different target addresses or target address identifiers. That is, for different target addresses or different target address identifiers, different reliability requirements and logical channel or logical channel group correspondence may be configured, including whether the logical channel or the logical channel group corresponds to the reliability requirement. Or, the specific value of the reliability requirement information corresponding to the different target address or the target address identifier may be different.
- the second communication unit receives information of the copy data sent by the user equipment in a preset order and the data amount of the non-replicated data;
- the user equipment determines to preferentially send information that reports the amount of data of the copied data or the non-replicated data to the network side.
- the second communication unit receives the data of the duplicated data and the non-replicated data sent by the user equipment according to a preset order when the priority of the information of the data amount of the reported duplicate data or the non-replicated data is the same. Amount of information;
- the receiving user equipment reports the data amount of the copy data and the non-replicated data according to the priority.
- the comparison of the preset order may not be performed, and the report may be performed according to the priority; when the data of the data is copied or the data of the non-replicated data
- the information of the priority report is determined in the above manner.
- the embodiment of the present invention further provides a hardware component architecture of the user equipment or the receiver device.
- the method includes at least one processor 51, a memory 52, and at least one network interface 53.
- the various components are coupled together by a bus system 54.
- bus system 54 is used to implement connection communication between these components.
- the bus system 54 includes, in addition to the data bus, a power bus, a control bus, and a status signal bus.
- various buses are labeled as bus system 54 in FIG.
- 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.
- memory 52 stores elements, executable modules or data structures, or a subset thereof, or their extension set:
- the processor 51 is configured to be able to process the method steps of the foregoing first embodiment, and details are not described herein.
- the embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, and when the computer executable instructions are executed, the method steps of the foregoing first embodiment are implemented.
- Embodiments of the Invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
- a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
- the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
- embodiments of the invention are not limited to any specific combination of hardware and software.
- an embodiment of the present invention further provides a computer storage medium, wherein a computer program is configured, and the computer program is configured to execute a data scheduling method according to an embodiment of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (77)
- 一种数据复制的数据量的上报方法,应用于用户设备,所述方法包括:向网络侧发送上报复制数据以及非复制数据的数据量的信息;其中,所述复制数据以及非复制数据的数据量的信息采用以下至少信息之一进行区分:逻辑信道、逻辑信道组、目标地址、目标地址标识。
- 根据权利要求1所述的方法,其中,所述向网络侧发送上报复制数据以及非复制数据的数据量的信息,包括:采用无线资源控制RRC信息、和/或、MAC CE,向网络侧发送上报复制数据以及非复制数据的数据量的信息。
- 根据权利要求1所述的方法,其中,所述方法还包括:向网络侧上报区分复制数据以及非复制数据的数据量的不同的目标地址、或者不同的目标地址标识。
- 根据权利要求1所述的方法,其中,所述方法还包括:向网络侧上报对应与不同的目标地址或者目标地址标识的复制数据以及非复制数据的可靠性要求信息。
- 根据权利要求4所述的方法,其中,所述可靠性要求信息包括以下至少一项:数据是否与可靠性要求关联、可靠性要求信息的具体数值。
- 根据权利要求1所述的方法,其中,所述向网络侧发送上报复制数据以及非复制数据的数据量的信息,包括:将用不同的目标地址、或者用不同的目标地址的标识区分的复制数据以及非复制数据的数据量的信息上报至网络侧。
- 根据权利要求1所述的方法,其中,所述向网络侧发送上报复制数据以及非复制数据的数据量的信息之前,所述方法还包括:接收网络侧发来的配置信息;其中,所述配置信息中包括所述网络侧是否允许所述终端设备对所述目标地址或者目标地址标识进行数据复制的信息。
- 根据权利要求3-7任一项所述的方法,其中,所述方法还包括:向网络侧上报所述复制数据的优先级信息。
- 根据权利要求3-7任一项所述的方法,其中,所述方法还包括:向网络侧上报所述复制数据的逻辑信道,或者逻辑信道组信息。
- 根据权利要求1所述的方法,其中,所述方法还包括:接收网络侧发来的配置信息;其中,所述配置信息中包括有网络侧配置的复制数据和非复制数据和不同的逻辑信道、或者逻辑信道组的对应关系。
- 根据权利要求1所述的方法,其中,所述方法还包括:接收网络侧发来的配置信息;其中,所述配置信息中包括有网络侧配置的不同的逻辑信道、或者逻 辑信道组,和数据可靠性要求信息的对应关系。
- 根据权利要求10或11所述的方法,其中,所述对应关系针对不同的目标地址、或目标地址标识。
- 根据权利要求11所述的方法,其中,所述可靠性要求信息包括以下至少一项:逻辑信道、或者逻辑信道组是否与可靠性要求对应;与逻辑信道、或者逻辑信道组对应的可靠性要求信息的具体数值。
- 根据权利要求1所述的方法,其中,所述配置信息中,还包括:所述复制数据的两个RLC实体所分别对应的逻辑信道、或者逻辑信道组。
- 根据权利要求9-14任一项所述的方法,其中,所述配置信息中,还包括:不同的逻辑信道、或者不同的逻辑信道组所对应的优先级信息。
- 根据权利要求9-14任一项所述的方法,其中,所述向网络侧发送上报复制数据以及非复制数据的数据量的信息,包括:将复制数据的数据量以及非复制数据的数据量分别对应到不同的逻辑信道、或者不同的逻辑信道组、或者逻辑信道的标识、或者不同的逻辑信道组的标识中上报至所述网络侧。
- 根据权利要求9-14任一项所述的方法,其中,所述向网络侧发送上报复制数据以及非复制数据的数据量的信息,包括:将复制数据的两个RLC实体的数据量分别对应不同的逻辑信道、或者不同的逻辑信道的标识、或者不同的逻辑信道组、或者不同的逻辑信道组的标识,并上报至所述网络侧。
- 根据权利要求1-17任一项所述的方法,其中,所述向网络侧发送上报复制数据以及非复制数据的数据量的信息,包括:按照预设的次序向网络侧发送上报复制数据以及非复制数据的数据量的信息;其中,所述次序为以下之一:优先向网络侧发送上报复制数据的数据量的信息;优先向网络侧发送上报非复制数据的数据量的信息;自行决定优先向网络侧发送上报复制数据或非复制数据的数据量的信息。
- 根据权利要求18所述的方法,其中,所述按照预设的次序向网络侧发送上报复制数据以及非复制数据的数据量的信息,包括:当所述上报复制数据或非复制数据的数据量的信息的优先级相同时,按照预设的次序向网络侧发送上报复制数据以及非复制数据的数据量的信息;当所述上报复制数据或非复制数据的数据量的信息的优先级不同时,按照优先级向网络侧发送上报复制数据以及非复制数据的数据量的信息。
- 一种数据复制的数据量的上报方法,应用于网络设备,所述方法包括:接收用户设备发来的复制数据以及非复制数据的数据量的信息;其中,所述复制数据以及非复制数据的数据量的信息采用以下至少信息之一进行区分:逻辑信道、逻辑信道组、目标地址、目标地址标识。
- 根据权利要求20所述的方法,其中,所述接收用户设备发来的复制数据以及非复制数据的数据量的信息,包括:通过RRC信息、和/或、MAC CE,接收用户设备发来的复制数据以及非复制数据的数据量的信息。
- 根据权利要求20所述的方法,其中,所述方法还包括:接收所述用户设备上报的用于区分复制数据以及非复制数据的数据量的不同的目标地址、或者不同的目标地址标识。
- 根据权利要求20所述的方法,其中,所述方法还包括:接收所述用户设备上报的对应与不同的目标地址或者目标地址标识的复制数据以及非复制数据的可靠性要求信息。
- 根据权利要求23所述的方法,其中,所述可靠性要求信息包括以下至少一项:数据是否与可靠性要求关联、可靠性要求信息的具体数值。
- 根据权利要求20所述的方法,其中,所述方法还包括:向所述用户设备发送配置信息;其中,所述配置信息中包括是否允许所述终端设备对所述目标地址或者目标地址标识进行数据复制的信息。
- 根据权利要求20-25任一项所述的方法,其中,所述方法还包括:获取用户设备发来的所述复制数据的优先级信息。
- 根据权利要求20-25任一项所述的方法,其中,所述方法还包括:获取用户设备发来的所述复制数据的逻辑信道,或者逻辑信道组信息。
- 根据权利要求20所述的方法,其中,所述方法还包括:向用户设备发送配置信息;其中,所述配置信息中包括有网络侧配置的复制数据和非复制数据和不同的逻辑信道、或者逻辑信道组的对应关系。
- 根据权利要求20所述的方法,其中,所述方法还包括:向用户设备发送配置信息;其中,所述配置信息中包括有网络侧配置的不同的逻辑信道、或者逻辑信道组,和数据可靠性要求信息的对应关系。
- 根据权利要求28或29所述的方法,其中,所述对应关系针对不同的目标地址、或目标地址标识,各不相同。
- 根据权利要求29所述的方法,其中,所述可靠性要求信息包括以下至少一项:数据是否与可靠性要求关联;可靠性要求信息的具体数值。
- 根据权利要求20所述的方法,其中,所述配置信息中,还包括:所述复制数据的两个RLC实体所分别对应的逻辑信道、或者逻辑信道组。
- 根据权利要求28-32任一项所述的方法,其中,所述配置信息中,还包括:不同的逻辑信道、或者不同的逻辑信道组所对应的优先级信息。
- 根据权利要求28-32任一项所述的方法,其中,所述接收用户设备发来的复制数据以及非复制数据的数据量的信息,包括:接收分别对应到不同的逻辑信道、或者不同的逻辑信道组、或者逻辑信道的标识、或者不同的逻辑信道组的标识的复制数据的数据量以及非复制数据的数据量。
- 根据权利要求28-32任一项所述的方法,其中,所述接收用户设备发来的复制数据以及非复制数据的数据量的信息,包括:从所述复制数据的两个RLC实体的数据量分别对应的不同的逻辑信道、或者不同的逻辑信道的标识、或者不同的逻辑信道组、或者不同的逻辑信道组的标识中,获取所述复制数据的两个RLC实体的数据量。
- 根据权利要求20-35任一项所述的方法,其中,所述接收用户设备发来的复制数据以及非复制数据的数据量的信息,包括:接收用户设备按照预设的次序发来的复制数据以及非复制数据的数据量的信息;其中,所述次序为以下之一:优先发送上报复制数据的数据量的信息;优先发送上报非复制数据的数据量的信息;所述用户设备决定优先向网络侧发送上报复制数据或非复制数据的数据量的信息。
- 根据权利要求36所述的方法,其中,所述接收用户设备按照预设的次序发来的复制数据以及非复制数据的数据量的信息,包括:当所述上报复制数据或非复制数据的数据量的信息的优先级相同时,接收用户设备按照预设的次序发来的复制数据以及非复制数据的数据量的信息;当所述上报复制数据或非复制数据的数据量的信息的优先级不同时,接收用户设备按按照优先级上报复制数据以及非复制数据的数据量的信息。
- 一种用户设备,所述用户设备包括:第一通信单元,向网络侧发送上报复制数据以及非复制数据的数据量的信息;其中,所述复制数据以及非复制数据的数据量的信息采用以下至少信息之一进行区分:逻辑信道、逻辑信道组、目标地址、目标地址标识。
- 根据权利要求38所述的用户设备,其中,所述第一通信单元,采用无线资源控制RRC信息、和/或、MAC CE,向网络侧发送上报复制数据以及非复制数据的数据量的信息。
- 根据权利要求38所述的用户设备,其中,所述第一通信单元,向网络侧上报区分复制数据以及非复制数据的数据量的不同的目标地址、或者不同的目标地址标识。
- 根据权利要求38所述的用户设备,其中,所述第一通信单元,向网络侧上报对应与不同的目标地址或者目标地址标识的复制数据以及非复制数据的可靠性要求信息。
- 根据权利要求41所述的用户设备,其中,所述可靠性要求信息包括以下至少一项:数据是否与可靠性要求关联、可靠性要求信息的具体数值。
- 根据权利要求38所述的用户设备,其中,所述第一通信单元,将用不同的目标地址、或者用不同的目标地址的标识区分的复制数据以及非复制数据的数据量的信息上报至网络侧。
- 根据权利要求38所述的用户设备,其中,所述用户设备还包括:第一处理单元,通过所述第一通信单元接收网络侧发来的配置信息;其中,所述配置信息中包括所述网络侧是否允许所述终端设备对所述目标地址或者目标地址标识进行数据复制的信息。
- 根据权利要求38-44任一项所述的用户设备,其中,所述第一通信单元,向网络侧上报所述复制数据的优先级信息。
- 根据权利要求38-44任一项所述的用户设备,其中,所述第一通信单元,向网络侧上报所述复制数据的逻辑信道,或者逻辑信道组信息。
- 根据权利要求38所述的用户设备,其中,所述用户设备还包括:第一处理单元,通过所述第一通信单元接收网络侧发来的配置信息;其中,所述配置信息中包括有网络侧配置的复制数据和非复制数据和不同的逻辑信道、或者逻辑信道组的对应关系。
- 根据权利要求38所述的用户设备,其中,所述用户设备还包括:第一处理单元,通过所述第一通信单元接收网络侧发来的配置信息;其中,所述配置信息中包括有网络侧配置的不同的逻辑信道、或者逻辑信道组,和数据可靠性要求信息的对应关系。
- 根据权利要求47或48所述的用户设备,其中,所述对应关系针对不同的目标地址、或目标地址标识,各不相同。
- 根据权利要求47所述的用户设备,其中,所述可靠性要求信息包括以下至少一项:数据是否与可靠性要求关联;可靠性要求信息的具体数值。
- 根据权利要求38所述的用户设备,其中,所述配置信息中,还包括:所述复制数据的两个RLC实体所分别对应的逻辑信道、或者逻辑信道组。
- 根据权利要求47-51任一项所述的用户设备,其中,所述配置信息中,还包括:不同的逻辑信道、或者不同的逻辑信道组所对应的优先级信息。
- 根据权利要求47-51任一项所述的用户设备,其中,所述用户设备还包括:第一处理单元,将复制数据的数据量以及非复制数据的数据量分别对 应到不同的逻辑信道、或者不同的逻辑信道组、或者逻辑信道的标识、或者不同的逻辑信道组的标识中,通过所述第一通信单元上报至所述网络侧。
- 根据权利要求47-51任一项所述的用户设备,其中,所述第一处理单元,将复制数据的两个RLC实体的数据量分别对应不同的逻辑信道、或者不同的逻辑信道的标识、或者不同的逻辑信道组、或者不同的逻辑信道组的标识,并通过所述第一通信单元上报至所述网络侧。
- 根据权利要求38-54任一项所述的用户设备,其中,所述第一处理单元,按照预设的次序通过第一通信单元向网络侧发送上报复制数据以及非复制数据的数据量的信息;其中,所述次序为以下之一:优先向网络侧发送上报复制数据的数据量的信息;优先向网络侧发送上报非复制数据的数据量的信息;自行决定优先向网络侧发送上报复制数据或非复制数据的数据量的信息。
- 根据权利要求55所述的用户设备,其中,所述第一处理单元,当所述上报复制数据或非复制数据的数据量的信息的优先级相同时,通过第一通信单元按照预设的次序向网络侧发送上报复制数据以及非复制数据的数据量的信息;当所述上报复制数据或非复制数据的数据量的信息的优先级不同时,通过第一通信单元按照优先级向网络侧发送上报复制数据以及非复制数据的数据量的信息。
- 一种网络设备,所述网络设备包括:第二通信单元,接收用户设备发来的复制数据以及非复制数据的数据量的信息;其中,所述复制数据以及非复制数据的数据量的信息采用以下至少信息之一进行区分:逻辑信道、逻辑信道组、目标地址、目标地址标识。
- 根据权利要求57所述的网络设备,其中,所述第二通信单元,通过RRC信息、和/或、MAC CE,接收用户设备发来的复制数据以及非复制数据的数据量的信息。
- 根据权利要求57所述的网络设备,其中,所述第二通信单元,接收所述用户设备上报的用于区分复制数据以及非复制数据的数据量的不同的目标地址、或者不同的目标地址标识。
- 根据权利要求59所述的网络设备,其中,所述第二通信单元,接收所述用户设备上报的对应与不同的目标地址或者目标地址标识的复制数据以及非复制数据的可靠性要求信息。
- 根据权利要求60所述的网络设备,其中,所述可靠性要求信息包括以下至少一项:数据是否与可靠性要求关联、可靠性要求信息的具体数值。
- 根据权利要求60所述的网络设备,其中,所述第二通信单元,向所述用户设备发送配置信息;其中,所述配置信息中包括是否允许所述终端设备对所述目标地址或 者目标地址标识进行数据复制的信息。
- 根据权利要求60-62任一项所述的网络设备,其中,所述第二通信单元,获取用户设备发来的所述复制数据的优先级信息。
- 根据权利要求60-62任一项所述的网络设备,其中,所述第二通信单元,获取用户设备发来的所述复制数据的逻辑信道,或者逻辑信道组信息。
- 根据权利要求60所述的网络设备,其中,所述第二通信单元,向用户设备发送配置信息;其中,所述配置信息中包括有网络侧配置的复制数据和非复制数据和不同的逻辑信道、或者逻辑信道组的对应关系。
- 根据权利要求60所述的网络设备,其中,所述第二通信单元,向用户设备发送配置信息;其中,所述配置信息中包括有网络侧配置的不同的逻辑信道、或者逻辑信道组,和数据可靠性要求信息的对应关系。
- 根据权利要求65或66所述的网络设备,其中,所述对应关系针对不同的目标地址、或目标地址标识,各不相同。
- 根据权利要求67所述的网络设备,其中,所述可靠性要求信息包括以下至少一项:数据是否与可靠性要求关联;可靠性要求信息的具体数值。
- 根据权利要求60所述的网络设备,其中,所述配置信息中,还包括:所述复制数据的两个RLC实体所分别对应的逻辑信道、或者逻辑信道组。
- 根据权利要求65-69任一项所述的网络设备,其中,所述配置信息中,还包括:不同的逻辑信道、或者不同的逻辑信道组所对应的优先级信息。
- 根据权利要求65-69任一项所述的网络设备,其中,所述第二通信单元,接收分别对应到不同的逻辑信道、或者不同的逻辑信道组、或者逻辑信道的标识、或者不同的逻辑信道组的标识的复制数据的数据量以及非复制数据的数据量。
- 根据权利要求65-69任一项所述的网络设备,其中,所述网络设备还包括:第二处理单元,从所述复制数据的两个RLC实体的数据量分别对应的不同的逻辑信道、或者不同的逻辑信道的标识、或者不同的逻辑信道组、或者不同的逻辑信道组的标识中,获取所述复制数据的两个RLC实体的数据量。
- 根据权利要求57-72任一项所述的网络设备,其中,所述第二通信单元,接收用户设备按照预设的次序发来的复制数据以及非复制数据的数据量的信息;其中,所述次序为以下之一:优先发送上报复制数据的数据量的信息;优先发送上报非复制数据的数据量的信息;所述用户设备决定优先向网络侧发送上报复制数据或非复制数据的数据量的信息。
- 根据权利要求73所述的网络设备,其中,所述第二通信单元,当所述上报复制数据或非复制数据的数据量的信息的优先级相同时,接收用户设备按照预设的次序发来的复制数据以及非复制数据的数据量的信息;当所述上报复制数据或非复制数据的数据量的信息的优先级不同时,接收用户设备按按照优先级上报复制数据以及非复制数据的数据量的信息。
- 一种用户设备,包括:处理器和用于存储能够在处理器上运行的计算机程序的存储器,其中,所述处理器用于运行所述计算机程序时,执行权利要求1-19任一项所述方法的步骤。
- 一种网络设备,包括:处理器和用于存储能够在处理器上运行的计算机程序的存储器,其中,所述处理器用于运行所述计算机程序时,执行权利要求20-37任一项所述方法的步骤。
- 一种计算机存储介质,所述计算机存储介质存储有计算机可执行指令,所述计算机可执行指令被执行时实现权利要求1-37任一项所述方法的步骤。
Priority Applications (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201880065803.1A CN111201734A (zh) | 2018-01-16 | 2018-07-10 | 数据复制的数据量的上报方法、用户设备及网络设备 |
CA3091941A CA3091941A1 (en) | 2018-01-16 | 2018-07-10 | Method for reporting data volume of data duplication, user equipment, and network device |
KR1020207023321A KR102613813B1 (ko) | 2018-01-16 | 2018-07-10 | 데이터 복제의 데이터 양 리포팅 방법, 사용자 기기 및 네트워크 기기 |
BR112020014335-9A BR112020014335A2 (pt) | 2018-01-16 | 2018-07-10 | Método para relatar um volume de dados de duplicação de dados, aplicado ao equipamento de usuário, método para relatar um volume de dados de duplicação de dados aplicado a um dispositivo de rede, equipamento de usuário, dispositivo de rede e mídia de armazenamento de computador |
JP2020539031A JP7200255B2 (ja) | 2018-01-16 | 2018-07-10 | データ複製のデータ量を報告する方法、ユーザ装置及びネットワーク装置 |
EP18900912.9A EP3742635B1 (en) | 2018-01-16 | 2018-07-10 | Method for reporting data amount of data replication, user equipment and network device |
MX2020007579A MX2020007579A (es) | 2018-01-16 | 2018-07-10 | Metodo para informar volumen de datos de duplicacion de datos, equipo de usuario, y dispositivo de red. |
CN202010429708.4A CN111641478B (zh) | 2018-01-16 | 2018-07-10 | 数据复制的数据量的上报方法、用户设备及网络设备 |
AU2018403856A AU2018403856A1 (en) | 2018-01-16 | 2018-07-10 | Method for reporting data amount of data replication, user equipment and network device |
US16/922,785 US11452000B2 (en) | 2018-01-16 | 2020-07-07 | Method for reporting data volume of data duplication, user equipment, and network device |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNPCT/CN2018/072898 | 2018-01-16 | ||
PCT/CN2018/072898 WO2019140558A1 (zh) | 2018-01-16 | 2018-01-16 | 数据复制的数据量的上报方法、用户设备及网络设备 |
CNPCT/CN2018/084920 | 2018-04-27 | ||
PCT/CN2018/084920 WO2019140806A1 (zh) | 2018-01-16 | 2018-04-27 | 数据复制的数据量的上报方法、用户设备及网络设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/922,785 Continuation US11452000B2 (en) | 2018-01-16 | 2020-07-07 | Method for reporting data volume of data duplication, user equipment, and network device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019140872A1 true WO2019140872A1 (zh) | 2019-07-25 |
Family
ID=67301964
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/095205 WO2019140872A1 (zh) | 2018-01-16 | 2018-07-10 | 数据复制的数据量的上报方法、用户设备及网络设备 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2019140872A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101674617A (zh) * | 2009-09-16 | 2010-03-17 | 华为技术有限公司 | 基站及数据处理方法 |
CN103039109A (zh) * | 2010-02-12 | 2013-04-10 | 交互数字技术公司 | 多个站点间的数据分割 |
WO2014110800A1 (zh) * | 2013-01-18 | 2014-07-24 | 华为技术有限公司 | 数据传输方法、基站和用户设备 |
CN107241164A (zh) * | 2017-05-05 | 2017-10-10 | 电信科学技术研究院 | 一种无线承载重复传输的处理方法及装置 |
-
2018
- 2018-07-10 WO PCT/CN2018/095205 patent/WO2019140872A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101674617A (zh) * | 2009-09-16 | 2010-03-17 | 华为技术有限公司 | 基站及数据处理方法 |
CN103039109A (zh) * | 2010-02-12 | 2013-04-10 | 交互数字技术公司 | 多个站点间的数据分割 |
WO2014110800A1 (zh) * | 2013-01-18 | 2014-07-24 | 华为技术有限公司 | 数据传输方法、基站和用户设备 |
CN107241164A (zh) * | 2017-05-05 | 2017-10-10 | 电信科学技术研究院 | 一种无线承载重复传输的处理方法及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3742635A4 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3959835B1 (en) | Harq-ack reporting with pdsch grouping | |
EP3606014B1 (en) | Detecting hardware address conflicts in computer networks | |
CN103782569A (zh) | 数据处理装置和方法 | |
CN106105154A (zh) | 数据上载的方法、装置及*** | |
WO2019161547A1 (zh) | 动态配置方法、终端设备、网络设备及计算机存储介质 | |
WO2020063737A1 (zh) | 一种通信方法及设备 | |
WO2019140806A1 (zh) | 数据复制的数据量的上报方法、用户设备及网络设备 | |
WO2019062725A1 (zh) | 一种上行数据传输方法及装置 | |
WO2019140872A1 (zh) | 数据复制的数据量的上报方法、用户设备及网络设备 | |
CN103209394B (zh) | 群组语音数据处理方法、***及终端设备 | |
US20220385589A1 (en) | Data transmission method and apparatus | |
WO2019148655A1 (zh) | 通信***中控制用户设备进行复制传输的方法及其设备 | |
WO2019079997A1 (zh) | 数据传输模式的确定方法、网络设备及计算机存储介质 | |
CN111510263B (zh) | 一种重映射方法、终端和网络侧设备 | |
CN113015212A (zh) | 一种数据包重复传输的激活方法、设备及存储介质 | |
WO2019148369A1 (zh) | 一种终端设备触发数据停止传输的方法及终端设备 | |
US11751080B2 (en) | Wireless network access point and method for operation thereof | |
WO2019214554A1 (zh) | 一种mcs表格确定方法、终端和基站及可读存储介质 | |
WO2012024870A1 (zh) | 一种数据重传方法及*** | |
WO2020151002A1 (zh) | 数据修复方法和装置 | |
WO2019183956A1 (zh) | 一种常规bsr的触发方法、ue及计算机存储介质 | |
WO2019136710A1 (zh) | 资源分配方法、网络设备、终端设备及计算机存储介质 | |
CN111786747A (zh) | 接收状态反馈方法、状态反馈方法、通信单元及终端 | |
WO2019036843A1 (zh) | 传输数据的方法和设备 | |
WO2015013975A1 (zh) | 识别信道命令的方法、基站及用户设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18900912 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3091941 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2020539031 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20207023321 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2018900912 Country of ref document: EP Effective date: 20200817 |
|
ENP | Entry into the national phase |
Ref document number: 2018403856 Country of ref document: AU Date of ref document: 20180710 Kind code of ref document: A |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112020014335 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112020014335 Country of ref document: BR Kind code of ref document: A2 Effective date: 20200714 |