US2019297641A1PendingUtilityA1

Apparatus and method for operating user plane protocol stack in connectionless communication system

Assignee: SAMSUNG ELECTRONICS CO LTDPriority: Jan 16, 2014Filed: Jun 12, 2019Published: Sep 26, 2019
Est. expiryJan 16, 2034(~7.5 yrs left)· nominal 20-yr term from priority
H04W 72/23H04W 76/14H04W 84/042H04W 72/1289H04W 92/18H04W 72/25H04W 28/065
64
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

ID.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method of an user equipment (UE), the method comprising:
 receiving, by the UE, a medium access control (MAC) protocol data unit (PDU) including a MAC header;   determining whether the MAC PDU is associated with a MAC layer entity of the UE based on an UE ID included in the MAC header;   identifying a packet data convergence protocol (PDCP) layer entity and a radio link control (RLC) layer entity for data reception, in respond to the MAC PDU being associated with the MAC layer entity;   generating a new PDCP layer entity and a new RLC layer entity for data reception corresponding to the UE ID, if there are no the identified PDCP layer entity and the identified RLC layer entity for data reception; and   releasing the identified PDCP layer entity and the identified RLC layer entity for data reception, and generating the new PDCP layer entity and the new RLC layer entity for data reception corresponding to the UE ID, if a UE ID which corresponds to the identified PDCP layer entity and the identified RLC layer entity for data reception is different from the UE ID included in the MAC header.   
     
     
         2 . The method of  claim 1 , further comprising:
 maintaining the new PDCP layer entity and the new RLC layer entity for data reception corresponding to the UE ID.   
     
     
         3 . The method of  claim 1 , wherein the UE ID included in the MAC header is used to identify another UE for device to device (D2D) data transmission. 
     
     
         4 . The method of  claim 1 , wherein the UE ID is provided by an upper layer entity of the UE which transmits the MAC PDU. 
     
     
         5 . The method of  claim 1 , wherein the UE ID included in the MAC header corresponds to a UE ID of a UE which transmits the MAC PDU. 
     
     
         6 . A method of an user equipment (UE), the method comprising:
 acquiring an UE ID provided from an upper layer entity of the UE;   identifying the PDCP layer entity and the RLC later entity for the data transmission, using the UE ID;   generating a source identifier field in a medium access control (MAC) header of a MAC protocol data unit (PDU), wherein the source identifier field is set to the UE ID;   transmitting the MAC PDU including the source identified field set to the UE ID in the MAC header.   
     
     
         7 . The method of  claim 6 , further comprising:
 maintaining the PDCP layer entity and the RLC layer entity for the data transmission corresponding to the UE ID.   
     
     
         8 . The method of  claim 6 , wherein the UE ID is used for identifying a destination of the data transmission. 
     
     
         9 . An user equipment (UE) in a D2D communication system, the UE comprising:
 a transceiver; and   a processor configured to:
 control the transceiver to receive a medium access control (MAC) protocol data unit (PDU) including a MAC header, 
 determine whether the MAC PDU is associated with a MAC layer entity of the UE based on an UE ID included in the MAC header, 
 identify a packet data convergence protocol (PDCP) layer entity and a radio link control (RLC) layer entity for data reception, in respond to the MAC PDU being associated with the MAC layer entity, 
 generate a new PDCP layer entity and a new RLC layer entity for data reception corresponding to the UE ID, if there are no the identified PDCP layer entity and the identified RLC layer entity for data reception, and 
 release the identified PDCP layer entity and the identified RLC layer entity for data reception, and generate the new PDCP layer entity and the new RLC layer entity for data reception corresponding to the UE ID, if a UE ID which corresponds to the identified PDCP layer entity and the identified RLC layer entity for data reception is different from the UE ID included in the MAC header. 
   
     
     
         10 . The UE of  claim 9 , wherein the processor is further configured to maintain the new PDCP layer entity and the new RLC layer entity for data reception corresponding to the UE ID. 
     
     
         11 . The UE of  claim 9 , wherein the UE ID included in the MAC header is used to identify another UE for device to device (D2D) data transmission. 
     
     
         12 . The UE of  claim 9 , wherein the UE ID is provided by an upper layer entity of the UE which transmits the MAC PDU. 
     
     
         13 . The UE of  claim 9 , wherein the UE ID included in the MAC header corresponds to a UE ID of a UE which transmits the MAC PDU. 
     
     
         14 . An user equipment (UE) in a D2D communication system, the UE comprising:
 a transceiver; and   a processor configured to:
 acquire an UE ID provided from an upper layer entity of the UE, 
 identify the PDCP layer entity and the RLC later entity for the data transmission, using the UE ID, 
 generate a source identifier field in a medium access control (MAC) header of a MAC protocol data unit (PDU), the source identifier field being set to the UE ID, and 
 control the transceiver to transmit the MAC PDU including the source identified field set to the UE ID in the MAC header. 
   
     
     
         15 . The UE of  claim 14 , wherein the processor is further configured to maintain the PDCP layer entity and the RLC layer entity for the data transmission corresponding to the UE ID. 
     
     
         16 . The UE of  claim 14 , wherein the UE ID is used for identifying a destination of the data transmission.

Join the waitlist — get patent alerts

Track US2019297641A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.