Abstract
Embodiments of the present disclosure describe techniques and configurations for transmitting small data payloads in a wireless communication network. An apparatus may include non-access stratum (NAS) circuitry configured to receive a trigger to send a data payload to a wireless communication network the data payload having a size that is less than a preconfigured threshold and generate a NAS message including the data payload and access stratum (AS) circuitry coupled with the NAS circuitry and configured to transmit the NAS message including the data payload to a node comprising a Mobility Management Entity (MME) or a Serving GPRS (General Packet Radio Service) Support Node (SGSN). Other embodiments may be described and/or claimed.
Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Number | ||||||
4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
|
No | Family Member | |||
4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member |
Specification Information
Specification Information
Technologies
Family Information
All Granted Patents In Patent Family : | ---- |
All Pending Patents In Patent Family : | ---- |
Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
---|---|---|---|---|---|---|---|---|---|---|
Declaration Date | Declaration Reference | Declaring Company | Specification Number | |||||||
US2013083653A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
Yes | Basis Patent | |||
US2013083653A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083653A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | Yes | Basis Patent | ||||
US2013083653A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
Yes | Basis Patent | |||
US8854960B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
Yes | Basis Patent | |||
US8854960B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8854960B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | Yes | Basis Patent | ||||
US8854960B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
Yes | Basis Patent | |||
CN104025475A | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP | No | Family Member | ||||
CN104025475A | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
CN104025475A | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
CN104025475A | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
EP2764641A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP | No | Family Member | ||||
EP2764641A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
EP2764641A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
EP2764641A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
EP2764641A4 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP | No | Family Member | ||||
EP2764641A4 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
EP2764641A4 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
EP2764641A4 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
JP2014530574A | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP | No | Family Member | ||||
JP2014530574A | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
JP2014530574A | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
JP2014530574A | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
JP5944004B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP | No | Family Member | ||||
JP5944004B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
JP5944004B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
JP5944004B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR101589393B1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR101589393B1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR101589393B1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
KR101589393B1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR20140080514A | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR20140080514A | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR20140080514A | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
KR20140080514A | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR20150079995A | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR20150079995A | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
KR20150079995A | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
KR20150079995A | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
RU2014117527A | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
RU2014117527A | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
RU2014117527A | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
RU2014117527A | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
RU2581622C2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
RU2581622C2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
RU2581622C2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
RU2581622C2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013084885A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013084885A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013084885A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2013084885A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8923891B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8923891B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8923891B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US8923891B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083726A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083726A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083726A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2013083726A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083783A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083783A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083783A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2013083783A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8817623B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8817623B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8817623B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US8817623B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083661A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083661A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013083661A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2013083661A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8824298B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8824298B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8824298B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US8824298B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013086653A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013086653A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013086653A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2013086653A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8839382B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8839382B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8839382B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US8839382B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013084894A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013084894A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2013084894A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2013084894A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8818426B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8818426B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US8818426B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US8818426B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2015036495A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2015036495A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
Yes | Family Member | |||
US2015036495A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2015036495A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9877139B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9877139B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
Yes | Family Member | |||
US9877139B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US9877139B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2014369201A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2014369201A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2014369201A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US2014369201A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9510133B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9510133B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9510133B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
US9510133B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2015029845A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2015029845A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2015029845A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | Yes | Family Member | ||||
US2015029845A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
Yes | Family Member | |||
US9215552B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9215552B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9215552B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | Yes | Family Member | ||||
US9215552B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
Yes | Family Member | |||
WO2013052163A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
WO2013052163A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
Yes | Basis Patent | |||
WO2013052163A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
WO2013052163A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2016337781A1 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2016337781A1 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US2016337781A1 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | Yes | Family Member | ||||
US2016337781A1 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
Yes | Family Member | |||
US9820080B2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9820080B2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
US9820080B2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | Yes | Family Member | ||||
US9820080B2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
Yes | Family Member | |||
BR112014007959A2 | 4G,3G,2G | 13/01/2016 | ISLD-201602-012 | INTEL CORP | No | Family Member | ||||
BR112014007959A2 | 4G | 20/03/2017 | ISLD-201703-007 | INTEL CORP |
S1
S2
|
No | Family Member | |||
BR112014007959A2 | 4G | 20/03/2017 | ISLD-201703-054 | INTEL CORP | No | Family Member | ||||
BR112014007959A2 | 4G,3G,2G | 20/03/2017 | ISLD-201703-054 | INTEL CORP |
S1
S2
|
No | Family Member | |||
EP2764641B1 | ----- | ----- | ----- | ----- | ----- | ----- | ----- | |||
CN104025475B | ----- | ----- | ----- | ----- | ----- | ----- | ----- |
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. An apparatus comprising:
non-access stratum (NAS) circuitry coupled with access stratum (AS) circuitry, the NAS circuitry to:
receive a trigger to send a data payload to a wireless communication network, the data payload having a size that is less than a preconfigured threshold;
generate a NAS message including the data payload; and
transmit, using the AS circuitry, the NAS message including the data payload to a node comprising a Mobility Management Entity (MME) or a Serving General Packet Radio Service Support Node (SGSN) upon establishment of a Radio Resource Control (RRC) connection,
wherein the NAS message is an attach request message for initiation of an attachment procedure with the node and the attach request message includes a communication type information element, and the communication type information element is an attach type information element that includes three bits to indicate an attach type value, wherein the attach type value is to indicate that a purpose of the attachment procedure with the node is for small data transmission.
2. The apparatus of claim 1, wherein the NAS message includes a small data container information element, the small data container information element including the data payload.
3. The apparatus of claim 2, wherein the small data container information element is included with the NAS message based on a determination that the communication type information element indicates that the apparatus is communicating with the wireless communication network to transmit the data payload.
4. The apparatus of claim 2, wherein the small data container information element includes information to identify the small data container information element and information to indicate a size of the data payload.
5. The apparatus of claim 1, wherein:
the attach type value indicates that the apparatus is communicating with the wireless communication network to transmit the small data payload if a first bit of the three bits has a value of 0, a second bit of the three bits has a value of 0, and a third bit of the three bits has a value of 1.
6. A method comprising:
receiving, by a node including a Mobility Management Entity (MME) or a Serving General Packet Radio Service Support Node (SGSN), a request to send a data payload to user equipment (UE) of a wireless communication network over a radio access network (RAN);
sending, by the node to the UE via the RAN, a paging message including a small data indicator information element that indicates that a data payload intended for transmission to the UE is located at the node, and wherein the data payload is smaller than a preconfigured threshold;
subsequent to sending the paging message, sending, by the node to the UE via the RAN, a non-access stratum (NAS) message that includes the data payload; and
receiving, by the node from the UE, an extended service request message to request a NAS attachment with the node and to indicate whether the UE has a small data payload to send to the wireless communication network, wherein:
the extended service request message is sent by the UE in response to the paging message and upon establishment of a Radio Resource Control (RRC) connection between the UE and the RAN;
the extended service request message includes a service type information element having a service type value that is to indicate that a purpose of the NAS attachment with the node is for small data transmission and whether the UE has a small data payload to send to the wireless communication network; and
the service type information element includes four bits to indicate the service type value.
7. The method of claim 6, wherein the NAS message is a NAS transport message that includes a NAS message container information element, the NAS message container information element including the data payload.
8. The method of claim 6, wherein:
the service type value indicates that the UE has no small data payload to send to the wireless communication network if a first bit of the four bits has a value of 0, a second bit of the four bits has a value of 0, a third bit of the four bits has a value of 1, and a fourth bit of the four bits has a value of 1; and
the service type value indicates that the UE has a small data payload to send to the wireless communication network in a small data container information element included with the service request message if the first bit has a value of 1, the second bit has a value of 0, the third bit has a value of 1, and the fourth bit has a value of 1.
9. A base station, comprising:
one or more non-transitory computer-readable media having instructions; and
one or more processors coupled with the one or more computer-readable media to execute the instructions to:
receive, from a node of a wireless communication network including a Mobility Management Entity (MME) or a Serving General Packet Radio Service Support Node (SGSN), a first paging message including a small data indicator information element that indicates transmission of a data payload from the node to a user equipment (UE) of the wireless communication network, wherein the data payload is a small data payload that is smaller than a preconfigured threshold; and
send a second paging message including the small data indicator information element to the UE, wherein:
the first paging message received by the base station includes the small data payload;
the second paging message sent by the base station does not include the small data payload;
the small data indicator information element in the second paging message indicates that the small data payload is intended for transmission to the UE and is located at the base station; and
the one or more processors are further to execute the instructions to
receive a radio resource control (RRC) connection request message from the UE, the RRC connection request message being sent by the UE in response to the paging message, and
receive, from the UE in response to the RRC connection request message, an RRC connection setup complete message and an extended service request message to request a NAS attachment with the node, wherein the extended service request message includes a service type information element having a service type value, and wherein the service type value indicates that a purpose of the NAS attachment with the node is for small data transmission and indicates whether the UE has a small data payload to send to the wireless communication network.
10. The base station of claim 9, wherein the one or more processors are further to execute the instructions to send an RRC connection setup message including the small data payload to the UE in response to the RRC connection request message.
11. An apparatus comprising:
non-access stratum (NAS) circuitry coupled with access stratum (AS) circuitry, the NAS circuitry to:
receive a trigger to send a data payload to a wireless communication network, the data payload having a size that is less than a preconfigured threshold;
generate a NAS message including the data payload; and
transmit, using the AS circuitry, the NAS message including the data payload to a node comprising a Mobility Management Entity (MME) or a Serving General Packet Radio Service Support Node (SGSN) upon establishment of a Radio Resource Control (RRC) connection,
wherein the NAS message is a routing area update request message for initiation of a routing area update procedure with the node and the routing area update request message includes a communication type information element, and the communication type information element is an update type information element that includes three bits to indicate an update type value, wherein the update type value is to indicate that a purpose of the routing area update procedure with the node is for periodic updating with small data transmission or for routing area updating with small data transmission.
12. The apparatus of claim 11, wherein:
the update type value indicates that the apparatus is communicating with the wireless communication network to transmit the small data payload as part of a periodic updating if a first bit of the three bits has a value of 0, a second bit of the three bits has a value of 0, and a third bit of the three bits has a value of 1; and
the update type value indicates that the apparatus is communicating with the wireless communication network to transmit the small data payload as part of routing area updating if a first bit of the three bits has a value of 1, a second bit of the three bits has a value of 0, and a third bit of the three bits has a value of 1.
13. An apparatus comprising:
non-access stratum (NAS) circuitry coupled with access stratum (AS) circuitry, the NAS circuitry to:
receive a trigger to send a data payload to a wireless communication network, the data payload having a size that is less than a preconfigured threshold;
generate a NAS message including the data payload; and
transmit the NAS message including the data payload to a node comprising a Mobility Management Entity (MME) or a Serving General Packet Radio Service Support Node (SGSN) upon establishment of a Radio Resource Control (RRC) connection,
wherein the NAS message is a tracking area update request message for initiation of a tracking area update procedure with the node and the tracking area update request message includes a communication type information element, and the communication type information element is an update type information element that includes three bits to indicate an update type value, wherein the update type value is to indicate that a purpose of the tracking area update procedure with the node is for periodic updating with small data transmission or for tracking area updating with small data transmission.
14. The apparatus of claim 13, wherein:
the update type value indicates that the apparatus is communicating with the wireless communication network to transmit the small data payload as part of tracking area updating if a first bit of the three bits has a value of 0, a second bit of the three bits has a value of 0, and a third bit of the three bits has a value of 1; and
the update type value indicates that the apparatus is communicating with the wireless communication network to transmit the small data payload as part of a periodic updating if a first bit of the three bits has a value of 1, a second bit of the three bits has a value of 0, and a third bit of the three bits has a value of 1.
Associated Portfolios
Claim Chart | Technology | Creation Date | Download |
---|---|---|---|
Claim charts will soon be available!
|
SUMMARY
ClaimChart-US9544709B2-STO
Patent number:US9544709B2
Claim Chart Type : SEP Claim Chart
Price: 200 €
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.