# US 2019/0174576 A1 · Methods to indicate a version of packet data convergence protocol (pdcp) in dual connectivity arrangements > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0174576 A1 - Document ID: US20190174576A1 - Status: Published application - Kind: A1 - Application number: 16/273,728 - Filed: 2019-02-12 - Published: 2019-06-06 - Earliest claimed: 2018-02-15 - Assignees: Intel Corporation - Inventors: Sudeep K. Palat; Seau S. Lim; Yi Guo - Web page: https://patentgrep.com/patent/US20190174576A1 ## CPC - H04W 80/06: Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless {(transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16)} - H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals - H04W 48/12: using downlink control channel - H04W 48/16: Discovering, processing access restriction or access information - H04W 48/20: Selecting an access point - H04W 76/10: Connection setup - H04W 80/02: Data link layer protocols - H04W 80/08: Upper layer protocols {(network arrangements or communication protocols for networked applications H04L67/00)} - H04W 12/03: Protecting confidentiality, e.g. by encryption - H04W 12/10: Integrity - H04W 76/12: Setup of transport tunnels - H04W 76/22: Manipulation of transport tunnels - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Embodiments of a User Equipment (UE), Evolved Node-B (eNB) and methods of communication are generally described herein. The UE may receive a SystemInformationBlockType1 from an eNB. The UE may determine that the eNB supports Fifth Generation Core (5GC) operation if the SystemInformationBlockType1 message includes a plmn-Identity-5GC-r15 parameter. The UE may transmit a radio resource control (RRC) connection request message to establish an RRC connection. If it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation, the UE may encode the RRC connection request message in accordance with a default new radio packet data convergence protocol (NR PDCP) configuration; and may use NR PDCP for one or more subsequent messages. ## Claims ### Claim 1 An apparatus of a User Equipment (UE), the apparatus comprising: memory; and processing circuitry, configured to: decode a SystemInformationBlockType1 message that includes system information related to cell access and defines scheduling of other system information, wherein the SystemInformationBlockType1 message is received from an Evolved Node-B (eNB) either via broadcast or dedicated signaling; determine that the eNB supports Fifth Generation Core (5GC) operation if the SystemInformationBlockType1 message includes a plmn-Identity-5GC-r15 parameter; encode a radio resource control (RRC) connection request message to establish an RRC connection, wherein establishment of the RRC connection includes establishment of a signaling radio bearer 1 (SRB1); if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: use new radio packet data convergence protocol (NR PDCP) to decode one or more subsequent messages received on the SRB1; and use NR PDCP to encode one or more subsequent messages transmitted on the SRB1. ### Claim 2 (depends on 1) The apparatus according to claim 1, the processing circuitry configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: use NR PDCP for all subsequent messages received and sent on the SRB1. ### Claim 3 (depends on 2) The apparatus according to claim 2, the processing circuitry configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: use NR PDCP, in accordance with a default NR PDCP configuration, for all subsequent messages received and sent on the SRB1. ### Claim 4 (depends on 1) The apparatus according to claim 1, wherein the default NR PDCP configuration includes a t-reordering timer. ### Claim 5 (depends on 1) The apparatus according to claim 1, the processing circuitry configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: apply a default NR PDCP configuration to perform NR PDCP operations. ### Claim 6 (depends on 1) The apparatus according to claim 1, the processing circuitry further configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: perform integrity protection and ciphering, in accordance with NR PDCP, on all RRC messages that are encoded for transmission on the SIB1. ### Claim 7 (depends on 1) The apparatus according to claim 1, wherein the SRB1 is established for transmission of RRC messages and non-access stratum (NAS) messages. ### Claim 8 (depends on 1) The apparatus according to claim 1, the processing circuitry further configured to: attempt to receive the SystemInformationBlockType1 message in accordance with a fixed schedule with a periodicity of 80 milliseconds (msec) and repetitions made within 80 msec. ### Claim 9 (depends on 1) The apparatus according to claim 1, the processing circuitry further configured to: determine that the eNB does not support 5GC operation if the SystemInformationBlockType1 message does not include a plmn-Identity-5GC-r15 parameter; and if it is determined that the eNB does not support 5GC operation: encode one or more RRC c messages in accordance with a Long Term Evolution (LTE) PDCP configuration for the SRB1. ### Claim 10 (depends on 1) The apparatus according to claim 1, the processing circuitry further configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: set a ue-Identity in the RRC connection request message as: if upper layers provide a 5G-S-TMSI (temporary mobile subscriber identity), set the ue-Identity to ng-5G-S-TMSI-Part1, and else, select a random value in a predetermined range and set the ue-Identity to the random value; and set an establishmentCause in the RRC connection request message in accordance with information received from upper layers. ### Claim 11 (depends on 1) The apparatus according to claim 1, wherein the UE is configurable to support the 5GC operation and Long Term Evolution (LTE) operation in accordance with Evolved Universal Terrestrial Radio Access (E-UTRA) new radio (NR) dual connectivity (EN-DC). ### Claim 12 (depends on 1) The apparatus according to claim 1, the processing circuitry further configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: autonomously use NR PDCP for communication with the eNB on the SRB1. ### Claim 13 (depends on 1) The apparatus according to claim 1, the processing circuitry further configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: autonomously use NR PDCP for communication with the eNB on a data radio bearer (DRB), wherein the NR PDCP includes packet duplication for packets sent on the DRB. ### Claim 14 (depends on 1) The apparatus according to claim 1, the processing circuitry further configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: encode an RRC connection setup complete message that indicates that the UE supports 5GC operation. ### Claim 15 (depends on 1) The apparatus according to claim 1, wherein: the apparatus includes a transceiver to receive the SystemInformationBlockType1 message, the processing circuitry includes a baseband processor to decode the SystemInformationBlockType1 message, and the memory is configured to store information related to the SystemInformationBlockType1 message. ### Claim 16 A non-transitory computer-readable storage medium that stores instructions for execution by processing circuitry to perform operations for communication by an Evolved Node-B (eNB), the eNB configured to support Fifth Generation Core (5GC) operation, the operations to configure the processing circuitry to: encode a SystemInformationBlockType1 message to include a plmn-Identity-5GC-r15 parameter to indicate that the eNB supports 5GC operation, wherein the plmn-Identity-5GC-r15 parameter indicates an identifier of a public land mobile network (PLMN) for 5GC; decode, from a User Equipment (UE), a radio resource control (RRC) connection request message to establish an RRC connection, wherein establishment of the RRC connection includes establishment of a signaling radio bearer 1 (SRB1) between the eNB and the UE; decode, from the UE, an RRC connection setup complete message; determine that the UE supports 5GC operation based on an indicator in the RRC connection setup complete message; if it is determined that the UE supports 5GC operation: use new radio packet data convergence protocol (NR PDCP) to decode one or more subsequent messages received from the UE on the SRB1; and use NR PDCP to encode one or more subsequent messages transmitted to the UE on the SRB1. ### Claim 17 (depends on 16) The non-transitory computer-readable storage medium according to claim 16, the operations to further configure the processing circuitry to: encode the SystemInformationBlockType1 message for transmission via broadcast or dedicated signaling; and encode the SystemInformationBlockType1 message to include system information related to cell access and to define scheduling of other system information. ### Claim 18 (depends on 16) The non-transitory computer-readable storage medium according to claim 16, wherein the NR PDCP includes integrity protection and ciphering. ### Claim 19 (depends on 16) The non-transitory computer-readable storage medium according to claim 16, the operations to further configure the processing circuitry to: if it is determined that the UE supports 5GC operation: use NR PDCP for all subsequent messages received and sent on the SRB1; and perform integrity protection and ciphering, in accordance with the NR PDCP, on all RRC messages that are encoded for transmission on the SIB1. ### Claim 20 (depends on 16) The non-transitory computer-readable storage medium according to claim 16, the operations to further configure the processing circuitry to: encode the SystemInformationBlockType1 message for transmission in accordance with a fixed schedule with a periodicity of 80 milliseconds (msec) and repetitions made within 80 msec. ### Claim 21 (depends on 16) The non-transitory computer-readable storage medium according to claim 16, wherein the eNB is configurable to support the 5GC operation and Long Term Evolution (LTE) operation in accordance with Evolved Universal Terrestrial Radio Access (E-UTRA) new radio (NR) dual connectivity (EN-DC). ### Claim 22 An apparatus of a User Equipment (UE), the apparatus comprising: memory; and processing circuitry, configured to: decode a SystemInformationBlockType1 message received from an Evolved Node-B (eNB) via broadcast; determine that the eNB supports Fifth Generation Core (5GC) operation if the SystemInformationBlockType1 message includes a plmn-Identity-5GC-r15 parameter; encode a radio resource control (RRC) connection request message to establish an RRC connection, wherein establishment of the RRC connection includes establishment of a signaling radio bearer 1 (SRB1); if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: encode the RRC connection request message in accordance with a default new radio packet data convergence protocol (NR PDCP) configuration for the SRB1; and use new radio packet data convergence protocol (NR PDCP) for all subsequent messages received and sent on the SRB1. ### Claim 23 (depends on 22) The apparatus according to claim 22, the processing circuitry further configured to: if it is determined that the eNB supports 5GC operation, and if the UE supports 5GC operation: set a ue-Identity in the RRC connection request message as: if upper layers provide a 5G-S-TMSI (temporary mobile subscriber identity), set the ue-Identity to ng-5G-S-TMSI-Part1, and else, select a random value in a predetermined range and set the ue-Identity to the random value; and set an establishmentCause in the RRC connection request message in accordance with information received from upper layers.