Method and device for transmitting or receiving scheduling request in mobile communication system
US-2018092118-A1 · Mar 29, 2018 · US
US12520281B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12520281-B2 |
| Application number | US-202418641977-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 22, 2024 |
| Priority date | Apr 13, 2018 |
| Publication date | Jan 6, 2026 |
| Grant date | Jan 6, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are a communication technique for merging, with IOT technology, a 5G communication system for supporting a data transmission rate higher than that of a 4G system; and a system therefor. The present disclosure can be applied to intelligent services (for example, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, security, and safety-related services, and the like) based on 5G communication technology and IoT-related technology. An apparatus and a method performed by a first terminal in a sidelink communication system are provided. The method includes establishing a packet data convergence protocol (PDCP) entity for a radio bearer based on a first sidelink PDCP protocol data unit (PDU); and setting state variables of the PDCP entity to an initial value based on the first sidelink PDCP PDU, wherein the state variables include an RX_NEXT indicating a next PDCP PDU and an RX_DELIV indicating a PDCP PDU not delivered to an upper layer, wherein the initial value of a sequence number of the RX_NEXT is set based on a sequence number of the first sidelink PDCP PDU for sidelink communication, and wherein the initial value of a sequence number of the RX_DELIV is set based on the sequence number of the first sidelink PDCP PDU for the sidelink communication.
Opening claim text (preview).
What is claimed is: 1 . A method performed by a first terminal in a sidelink communication system, the method comprising: establishing a packet data convergence protocol (PDCP) entity for a radio bearer based on a first received sidelink PDCP protocol data unit (PDU); and setting state variables of the PDCP entity to an initial value based on the first received sidelink PDCP PDU, wherein the state variables include an RX_NEXT indicating a next PDCP PDU and an RX_DELIV indicating a PDCP PDU not delivered to an upper layer, wherein the initial value of a sequence number of the RX_NEXT is set based on a sequence number of the first received sidelink PDCP PDU for sidelink communication, and wherein the initial value of a sequence number of the RX_DELIV is set based on the sequence number of the first received sidelink PDCP PDU for the sidelink communication. 2 . The method of claim 1 , wherein the first received sidelink PDCP PDU is determined based on a source field and a destination field pair included in a sidelink medium access control (MAC) subheader. 3 . The method of claim 2 , wherein the sidelink MAC subheader includes a logical channel ID (LCID) field identifying a logical channel, a length field indicating a length of a sidelink MAC service data unit (SDU), and a format field indicating a size of the length field. 4 . The method of claim 3 , wherein a first value of the format field indicates 8 bits of the length field, and a second value of the format field indicates 16 bits of the length field. 5 . A first terminal in a sidelink communication system, the first terminal comprising: a transceiver; and a controller coupled with the transceiver and configured to: establish a packet data convergence protocol (PDCP) entity for a radio bearer based on a first received sidelink PDCP protocol data unit (PDU), and set state variables of the PDCP entity to an initial value based on the first received sidelink PDCP PDU, wherein the state variables include an RX_NEXT indicating a next PDCP PDU and an RX_DELIV indicating a PDCP PDU not delivered to an upper layer, wherein the initial value of a sequence number of the RX_NEXT is set based on a sequence number of the first received sidelink PDCP PDU for sidelink communication, and wherein the initial value of a sequence number of the RX_DELIV is set based on the sequence number of the first received sidelink PDCP PDU for the sidelink communication. 6 . The first terminal of claim 5 , wherein the first received sidelink PDCP PDU is determined based on a source field and a destination field pair included in a sidelink medium access control (MAC) subheader. 7 . The first terminal of claim 6 , wherein the sidelink MAC subheader includes a logical channel ID (LCID) field identifying a logical channel, a length field indicating a length of a sidelink MAC service data unit (SDU), and a format field indicating a size of the length field. 8 . The first terminal of claim 7 , wherein a first value of the format field indicates 8 bits of the length field, and a second value of the format field indicates 16 bits of the length field.
between access points and access point controllers · CPC title
Data link layer protocols · CPC title
Resources in frequency domain, e.g. a carrier in FDMA · CPC title
Resources in time domain, e.g. slots or frames · CPC title
for vehicles, e.g. vehicle-to-pedestrians [V2P] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.