Abstract
Methods, network server, and mobile communication devices for reporting an MDT log are provided. The method, adopted by a network server, requesting a Minimization of Drive Test (MDT) log from a mobile communication device is disclosed, including: transmitting a first request message for the MDT log to the mobile communication device; in response to the first request message, receiving a first response message comprising a part of the MDT log from the mobile communication device, wherein the first response message indicates whether the MDT log reporting is finished or whether at least one more part of the MDT log is available; and transmitting a second request message for the MDT log to the mobile communication device when the first response message indicates that the MDT log reporting is not finished or at least one more part of the MDT log is available.
Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Information | ||||||
3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member |
Specification Information
Specification Information
Technologies
Family Information
All Granted Patents In Patent Family : | ---- |
Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
---|---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Information | |||||||
US2011306345A1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
Yes | Basis Patent | |||
US2011306345A1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Basis Patent | |||
US2011306345A1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Basis Patent | ||||
US8594657B2 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
Yes | Basis Patent | |||
US8594657B2 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Basis Patent | |||
US8594657B2 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Basis Patent | ||||
CN102291756A | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
CN102291756A | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
EP2398270A2 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
EP2398270A2 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
EP2398270A2 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
EP2398270A3 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
EP2398270A3 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
EP2398270A3 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
EP2398270B1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
EP2398270B1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
EP2398270B1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
JP2012005123A | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
JP2012005123A | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
JP2012005123A | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
JP5563526B2 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
JP5563526B2 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
JP5563526B2 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
KR101297032B1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
KR101297032B1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
KR101297032B1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
KR20110136757A | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
KR20110136757A | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
KR20110136757A | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
EP2555556A1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
EP2555556A1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
EP2555556A1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
EP2555556B1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
EP2555556B1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
EP2555556B1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
TW201204079A | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
TW201204079A | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
TW201204079A | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
TWI433562B | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
TWI433562B | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
TWI433562B | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
KR101352281B1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
KR101352281B1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
KR101352281B1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
KR20130023293A | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
KR20130023293A | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
KR20130023293A | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
EP2941042A1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
EP2941042A1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
EP2941042A1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
EP2941042B1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
EP2941042B1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
EP2941042B1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
JP2014053937A | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
JP2014053937A | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
JP2014053937A | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
JP5735609B2 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
JP5735609B2 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
JP5735609B2 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
US2014016566A1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
US2014016566A1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
US2014016566A1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
US9226187B2 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
US9226187B2 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
US9226187B2 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member | ||||
US2016066206A1 | 3G | 22/03/2012 | ISLD-201203-016 | HTC CORPORATION |
S1
S2
|
No | Family Member | |||
US2016066206A1 | 4G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION |
S1
S2
|
Yes | Family Member | |||
US2016066206A1 | 5G | 13/07/2022 | ISLD-202207-007 | HTC CORPORATION | Yes | Family Member |
Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | Status | National Phase Entries | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Information | |||||||||
----- | ----- | ----- | ----- | ----- |
S1
|
----- | ----- | ----- | ----- |
Technologies
Product
Use Cases
Services
Claim
1. A method of reporting a Minimization of Drive Test (MDT) log for a mobile communication device in a service network, comprising:
receiving, by the mobile communication device, a first request message for the MDT log from the service network; and
in response to the first request message, transmitting, by the mobile communication device, a first response message comprising a part of the MDT log to the service network; wherein the first response message indicates at least one more part of the MDT log is available; and
wherein the first request message is an UEInformationRequest message and the first response message is an UEInformationResponse message.
2. The method of claim 1, further comprising receiving, by the mobile communication device, a second request message for the MDT log from the service network when the first response message indicates that at least one more part of the MDT log is available.
3. The mobile communication device of claim 1, wherein the first response message comprises an indicator for indicating whether at least one more part of the MDT log is available.
4. The mobile communication device of claim 1, wherein when the part of the MDT log included in the first response message is not a last part of the MDT log, the first response message comprises an indicator for indicating that at least one more part of the MDT log is available.
5. The mobile communication device of claim 4, wherein when the part of the MDT log included in the first response message is a last part of the MDT log, the first response message indicates that no more part of the MDT log is available by not comprising the indicator.
6. A mobile communication device, providing a MDT log to a network server, comprising:
a transceiver, configured to receive a first request message for the MDT log from the network server; and in response to the first request message, transmit a first response message comprising a part of the MDT log to the network server, wherein the first response message indicates whether at least one more part of the MDT log is available; and
wherein the first request message is an UEInformationRequest message and the first response message is an UEInformationResponse message.
7. The mobile communication device of claim 6, wherein the transceiver is further configured to receive a second request message for the MDT log from the network server when the first response message indicates that at least one more part of the MDT log is available.
8. The mobile communication device of claim 6, wherein the first response message comprises an indicator for indicating whether at least one more part of the MDT log is available.
9. The mobile communication device of claim 6, wherein when the part of the MDT log included in the first response message is not a last part of the MDT log, the first response message comprises an indicator for indicating that at least one more part of the MDT log is available.
10. The mobile communication device of claim 9, wherein when the part of the MDT log included in the first response message is a last part of the MDT log, the first response message indicates that no more part of the MDT log is available by not comprising the indicator.
11. The mobile communication device of claim 6, wherein the first response message indicates at least one more part of the MDT log is available just by comprising the part of the MDT log.
12. The mobile communication device of claim 11, wherein:
in response to the second request message, the transceiver is further configured to transmit a second response message to the network server; and
when the part of the MDT log included in the first response message is not a last part of the MDT log, the second response message comprises another part of the MDT log.
13. The mobile communication device of claim 6, further comprising:
a controller, configured to remove or invalidate the part of the MDT log after the first response message is transmitted.
14. A network server, requesting a Minimization of Drive Test (MDT) log from a mobile communication device, comprising:
a transceiver, configured to transmit a first request message for the MDT log to the mobile communication device; and in response to the first request message, receive a first response message comprising a part of the MDT log from the mobile communication device, wherein the first response message indicates whether at least one more part of the MDT log is available; and
wherein the first request message is an UEInformationRequest message and the first response message is an UEInformationResponse message.
15. The network server of claim 14, wherein the transceiver is further configured to transmit a second request message for the MDT log to the mobile communication device when the first response message indicates that at least one more part of the MDT log is available.
16. The network server of claim 14, wherein the first response message comprises an indicator for indicating whether at least one more part of the MDT log is available.
17. The network server of claim 14, wherein when the part of the MDT log included in the first response message is not a last part of the MDT log, the first response message comprises an indicator for indicating that at least one more part of the MDT log is available.
18. The network server of claim 14, wherein when the part of the MDT log included in the first response message is a last part of the MDT log, the first response message indicates that no more part of the MDT log is available by not comprising the indicator.
19. The network server of claim 14, wherein the first response message indicates at least one more part of the MDT log is available just by comprising the part of the MDT log.
20. The network server of claim 19 wherein:
in response to the second request message, the transceiver is further configured to receive a second response message from the mobile communication device; and
when the part of the MDT log included in the first response message is not a last part of the MDT log, the second response message comprises another part of the MDT log.
Associated Portfolios
Claim Chart | Technology | Creation Date | Download |
---|---|---|---|
Claim charts will soon be available!
|
To view claim charts you must become a Gold or Platinum Member.
Upgrade your subscriptionYou have reached the maximum number of patents which can be associated to your account per your subscription. If you wish to associate more patents
Please upgrade your subscription.Note:
The information in blue was extracted from the third parties (Standard Setting Organisation, Espacenet)
The information in grey was provided by the patent holder
The information in purple was extracted from the FrandAvenue
Explicitly disclosed patent:openly and comprehensibly describes all details of the invention in the patent document.
Implicitly disclosed patent:does not explicitly state certain aspects of the invention, but still allows for these to be inferred from the information provided.
Basis patent:The core patent in a family, outlining the fundamental invention from which related patents or applications originate.
Family member:related patents or applications that share a common priority or original filing.