The present disclosure is related generally to wireless networks and, more particularly, to methods and systems for transmitting and/or obtaining a temporary identifier.
In many current wireless networks (e.g., those of the major wireless carriers), when a user equipment (“UE”) attempts to access a radio access network (“RAN”) (e.g., after the UE is powered on), one of the first tasks carried out by the UE is to engage in a random access procedure. At the end of the random access procedure, the UE establishes a radio resource control (“RRC”) connection with the RAN. In doing so, the UE may identify itself using a temporary UE ID, which allows the core network (“CN”) to know who the subscriber is without the necessity of the UE providing the international mobile subscriber identity (“IMSI”), which can compromise the security of the UE. The CN maintains a mapping between the temporary UE ID and the IMSI.
While the appended claims set forth the features of the present techniques with particularity, these techniques, together with their objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:
The disclosure is generally directed to a method and system for transmitting and receiving a temporary identifier. According to various embodiments, a temporary identifier of a UE is divided into two parts and transmitted from the UE to a node of a RAN via separate messages—one part of the UE temporary identifier in a first message and the other part in a second message.
According to various embodiments, a method for transmitting a temporary identifier involves a wireless communication device: transmitting a first portion of a temporary identifier of the wireless communication device to a radio access network in a first message; and transmitting a second portion of the temporary identifier to the radio access network in a second message.
In an embodiment, the method further includes the device receiving, from the radio access network, a contention resolution message containing the first portion.
One of the first and second messages may be a radio resource control connection request message and a radio resource control connection setup complete message
According to various embodiments, the first portion is a plurality of least significant bits of the temporary identifier and the second portion is a plurality of the most significant bits of the temporary identifier.
In an embodiment, the least significant bits include a temporary mobile subscriber identity and an access and mobility management function pointer.
According to an embodiment, the least significant bits include the least significant bits of an access and mobility management function set identifier and the most significant bits include the most significant bits of the access and mobility management function set identifier.
The second communication device 104 operates as a node of a RAN (such as a “Node B” of a fourth generation or fifth generation RAN) 108. The RAN 108 is communicatively linked to a CN 110. The CN 110 carries are many functions in support of the RAN 108 and has many components, including an Access and Mobility Management Function (“AMF”) 112. It is to be understood that the “function” carried out by the AMF 112 is, in fact, carried out by one or more actual computing devices (e.g., under the control of software). Thus, all references herein to an AMF are to be understood as being references to a piece of computer hardware (e.g., one or more computing devices).
The following description will sometimes refer to a node and a UE without specific reference to
The term “logic circuitry” as used herein means a circuit (a type of electronic hardware) designed to perform complex functions defined in terms of mathematical logic. Examples of logic circuitry include a microprocessor, a controller, or an application-specific integrated circuit. When the present disclosure refers to a device carrying out an action, it is to be understood that this can also mean that logic circuitry integrated with the device is, in fact, carrying out the action.
In many existing wireless networks, an RRC connection request is used to deliver the temporary UE ID to network node, which the network node uses for contention resolution. The RRC connection request is sent over signaling radio bearer 0 (“SRB0”) using the uplink (“UL”) common control channel (“CCCH”), i.e., random access message 3 (“MSG3”). Because SRB0 uses radio link control (“RLC”) transparent mode (“TM”) and hence lacks segmentation, the whole RRC protocol data unit (“PDU”) needs to be sent within a single transport block, which limits its size. The size of the transport block is determined by the number of bits that can be reliably delivered to a UE at the cell edge, and can be as low as 56 bits in some deployments. After removing the media access control (“MAC”), RLC, and the packet data convergence protocol (“PDCP”) overhead, only 48 bits remain for the actual RRC PDU.
It has been proposed to extend the temporary UE ID to 48 bits. With such an extension, the temporary UE ID will not fit within MSG3, particularly because other elements need to be transmitted in the RRC connection request (e.g., the establishment cause).
In some recent versions of long-term evolution (“LTE”) networks, the RRC “resume” process uses a truncated version of the Resume ID to fit into a 56-bit MSG3. The Truncated Resume ID impacts performance because it reduces the number of connections that can be suspended per the base station and the area in which a connection can be resumed.
In order to address this issue, in an embodiment, a temporary identifier for a wireless communication device (e.g., a UE) is divided into two parts. The wireless communication device (“device”) transmits the first part (“first portion”) via RRC Connection Request message. The device transmits the second part (“second portion”) via RRC Connection Setup Complete message. Although examples of particular sizes for the first and second portions have been set forth herein, it is to be understood that other sizes may also be used.
Turning to
In this embodiment, the temporary identifier (e.g., the 5G-S-TMSI) is divided into two parts: the 40 least significant bits (“LSB”) and the 8 most significant bits (“MSB”). The wireless communication device transmits the 40 LSB via an RRC Connection Request message. The 40 LSB transmitted in the RRC Connection Request message include:
For initial access, the 40 LSB can be used (e.g., by the RAN) for contention resolution.
The wireless communication device (e.g., UE) transmits the 8 MSB bits of the temporary identifier via an RRC Connection Setup Complete message. The 8 MSB transmitted in the RRC Connection Setup Complete message include:
Turning to
In this embodiment, the wireless communication device transmits the 40 LSB in the RRC Connection Request message. The 40 LSB include:
The wireless communication device transmits the 8 MSB of the temporary identifier via an RRC Connection Setup Complete message. The 8 MSB transmitted in RRC Connection Setup Complete message in this embodiment include:
As in the previously described embodiment, the 40 LSB of the temporary identifier can be used (e.g., by the RAN) for contention resolution.
Turning to
At 402, the wireless communication device 102 transmits a Random Access Preamble on a random access channel (“RACH”) in a UL transmission to the RAN 108 (e.g., via a node of the RAN 108, such as the wireless communication device 104).
At 404, the RAN 108 transmits a Random Access Response (e.g., transmitted via the MAC layer and on the downlink shared channel (“DL-SCH”)) to the wireless communication device 102.
At 406, the wireless communication device 102 transmits on the first scheduled UL transmission on the uplink shared channel (“UL-SCH”) to the RAN 108. The transmission includes the RRC Connection Request (e.g., generated by the wireless communication device 102 at the RRC layer and transmitted via the CCCH). The RRC Connection Request includes the 40 LSB of the temporary identifier (e.g., of the 5G-S-TMSI, including the 32-bit 5G-TMSI and the 8-bit AMF Pointer (if using the implementation of
At 408, the RAN 108 transmits a Contention Resolution to the wireless communication device 102 on the downlink (“DL”). It should be noted that a hybrid automatic repeat request (“HARQ”) feedback is only transmitted by the wireless communication device 102 (e.g., UE) if it detects its own identity (i.e., in the 40 LSB of the temporary identifier), as provided in the RRC Connection Request message, echoed in the Contention Resolution message.
At 410, the RAN 108 establishes signaling radio bearer 1 (“SRB1”) by transmitting an RRC Connection Setup message to the wireless communication device 102.
At 412 the wireless communication device 102 confirms the successful completion of the establishment of an RRC connection. The wireless communication device 102 does so by transmitting an RRC Connection Setup Complete message via a dedicated control channel (“DCCH”) to transfer the initial non-access stratum (“NAS”) dedicated information/message to the RAN 108. The RRC Connection Setup Complete message includes the 8 MSB of the temporary identifier (e.g., of the 5G-S-TMSI) (which include the AMF Set ID, if using the implementation of
After transmission of Connection Setup Complete message, the wireless communication device 102 transmits the entire temporary identifier to the RAN 108, providing an unambiguous identification of the wireless communication device and allowing the identification of the AMF (e.g., the AMF 112) and the network (e.g., the RAN 108). It can be used by the network and the wireless communication device to establish the identity of the device during signaling between them.
According to another embodiment, a wireless communication device (e.g., UE) provides a temporary identifier as follows: the device (a) transmits a random value (e.g., for contention resolution) to the RAN (e.g., via a CCCH message. such as an RRC Connection Request), and (b) subsequently transmits the entire temporary identifier (e.g., the 5G-S-TMSI) to the RAN (e.g., via a DCCH message, such as an RRC Connection Setup Complete message).
According to an embodiment, when the size of the temporary identifier (e.g., 5G-S-TMSI) is larger than 40 bits, the wireless communication device transmits a 40-bit random value via an RRC Connection Request message for contention resolution. Then, the wireless communication device transmits the entire temporary identifier (e.g., the 5G-S-TMSI) to the RAN via an RRC Connection Setup Complete message.
Regardless of the temporary identifier size, in various embodiments, the wireless communication device transmits a random value via an RRC Connection Request message for contention resolution. Then, the wireless communication device transmits the entire temporary identifier (e.g., the 5G-S-TMSI) to the RAN via an RRC Connection Setup Complete message.
Referring again to
At 402, the wireless communication device 102 transmits a Random Access Preamble on a RACH in a UL transmission to the RAN 108 (e.g., via a node of the RAN 108, such as the wireless communication device 104).
At 404, the RAN 108 transmits a Random Access Response (e.g., transmitted via the MAC layer and on the DL-SCH) to the wireless communication device 102.
At 406, the wireless communication device 102 transmits on the first scheduled UL transmission on the UL-SCH to the RAN 108. The transmission includes the RRC Connection Request (e.g., generated by the wireless communication device 102 at the RRC layer and transmitted via the CCCH). The RRC Connection Request includes a 40-bit random value and an establishment cause. The 40-bit random value will be used as an identifier for the wireless communication device 102 for contention resolution.
At 408, the RAN 108 transmits a Contention Resolution to the wireless communication device 102 on DL. It should be noted that a HARQ feedback is only transmitted by the wireless communication device 102 (e.g., UE) if it detects its own identity (i.e., in the 40-bit random value), as provided in the RRC Connection Request message, echoed in the Contention Resolution message.
At 410, the RAN 108 establishes signaling radio bearer 1 (“SRB1”) by transmitting an RRC Connection Setup message to the wireless communication device 102.
At 412 the wireless communication device 102 confirms the successful completion of the establishment of an RRC connection. The wireless communication device 102 does so by transmitting an RRC Connection Setup Complete message via the DCCH to transfer the initial NAS dedicated information/message to the RAN 108. The RRC Connection Setup Complete message includes the entire temporary identifier (e.g., the entire 5G-S-TMSI).
After transmission of Connection Setup Complete message, the wireless communication device 102 transmits the entire temporary identifier to the RAN 108, providing an unambiguous identification of the wireless communication device and allowing the identification of the AMF (e.g., the AMF 112) and the network (e.g., the RAN 108). It can be used by the network and the wireless communication device to establish the identity of the device during signaling between them.
Any and all of the methods described herein are carried out by or on one or more computing devices. Furthermore, instructions for carrying out any or all of the methods described herein may be stored on a non-transitory, computer-readable medium, such as any of the various types of memory described herein.
It should be understood that the exemplary embodiments described herein should be considered in a descriptive sense only and not for purposes of limitation. Descriptions of features or aspects within each embodiment should typically be considered as available for other similar features or aspects in other embodiments. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from their spirit and scope of as defined by the following claims. For example, the steps of the various methods can be reordered in ways that will be apparent to those of skill in the art.
This patent document is a continuation of U.S. patent application Ser. No. 16/940,849, filed on Jul. 28, 2020, which is a continuation of and claims benefit of priority to International Patent Application No. PCT/CN2018/080887, filed on Mar. 28, 2018. The entire contents of the before-mentioned patent applications are incorporated by reference as part of the disclosure of this application.
Number | Name | Date | Kind |
---|---|---|---|
8406180 | Park et al. | Mar 2013 | B2 |
10448290 | Takahashi et al. | Oct 2019 | B2 |
10524166 | Youn et al. | Dec 2019 | B2 |
11419160 | Wang et al. | Aug 2022 | B2 |
20090262681 | Park et al. | Oct 2009 | A1 |
20100067495 | Lee et al. | Mar 2010 | A1 |
20160295398 | Ketheesan et al. | Oct 2016 | A1 |
20190124561 | Faccin | Apr 2019 | A1 |
20190144576 | Lue et al. | May 2019 | A1 |
20190150218 | Futaki | May 2019 | A1 |
20190174449 | Shan et al. | Jun 2019 | A1 |
20190174576 | Palat et al. | Jun 2019 | A1 |
20200100088 | Kim | Mar 2020 | A1 |
20200120742 | Mildh et al. | Apr 2020 | A1 |
20200228987 | Ben Henda et al. | Jul 2020 | A1 |
20200267539 | Tamura et al. | Aug 2020 | A1 |
20200267634 | Kim | Aug 2020 | A1 |
20200351816 | Persson et al. | Nov 2020 | A1 |
20200367224 | Persson et al. | Nov 2020 | A1 |
20210014781 | Ianev et al. | Jan 2021 | A1 |
20210029776 | Tiwari et al. | Jan 2021 | A1 |
20220022121 | Eklöf et al. | Jan 2022 | A1 |
20220201550 | Tiwari et al. | Jun 2022 | A1 |
Number | Date | Country |
---|---|---|
107251642 | Aug 2020 | CN |
109802809 | Feb 2021 | CN |
109155949 | Jun 2021 | CN |
3432641 | Jan 2019 | EP |
3373692 | Mar 2020 | EP |
3697123 | Aug 2020 | EP |
3709551 | Sep 2020 | EP |
101384865 | Apr 2014 | KR |
2007148917 | Dec 2007 | WO |
2008084949 | Jul 2008 | WO |
2017077979 | May 2017 | WO |
Entry |
---|
Alcatel-Lucent, “Proposed way forward on Establishment cause values”, 3GPP TSG RAN WG2 #62, Kansas City, United States of America, R2-082692, 4 pages, May 2008. |
Ericsson, “Message 3.5 in LTE connected to 5GC”, 3GPP TSG-RAN WG2 #101, Athens, Greece, R2-1802632, 4 pages, Mar. 2, 2018. |
International Search Report and Written Opinion dated Jan. 2, 2019 for International Application No. PCT/CN2018/080887, filed on Mar. 28, 2018 (7 pages). |
Oppo, “Discussion UE Identifier Definition in RRC Signalling in eLTE”, 3GPP TSG-RAN WG2#101, Athens, Greece, R2-1801776, 4 pages, Mar. 2018. |
SA2, “LS on 5G-S-TMSI code space”, SA WG2 Meeting #S2-126, Montreal, Canada, S2-182964, 1 page, Mar. 2018. |
Supplementary European Search Report for EP Patent Application No. 18911922.5, dated Mar. 15, 2021, 6 pages. |
Huawei et al: “On potential issues for signalling Msg3 size”, 3GPP Draft; R2-1706464 on Potential Issues for Signalling MSG3 Size, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles ; F-06921 Sophia-Antipolis Cedex; FR vol. RAN WG2, no. Qingdao, China; Jun. 27, 2017-Jun. 29, 2017, Jun. 26, 2017 (Jun. 26, 2017), XP051300970, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/ [retrieved on Jun. 26, 2017] 5 pages. |
Ericsson, “Handling of Collision between UE Identifiers in LTE connected to 56C,” 3GPP TSG-RAN WG2 #101, 2-1802631, Athens, Greece, Feb. 26-Mar. 2, 2018, 6 pages. |
ZTE, “Consideration on extending the code space for 5G-S-TMSI,” 3GPP TSG-RAN WG2 Meeting#101bis, R2-1804461, Sanya, China, Apr. 16-20, 2018, 4 pages. |
European Search Report for EP Patent Application No. 22157752.1, dated Sep. 19, 2022, 10 pages. |
Ericsson, “5GS Temporary Identifiers and mapping—Requirements,” SA WG2 Temporary Document, SA WG2 Meeting #126, S2-181889, Feb. 26-Mar. 2, 2018, Montreal, Canada, revision of S2-18xxxx), 3 pages. |
ZTE et al., “23.501: Network Slicing clause 5.15.5—Early vs. Late Binding of UE with the associated NSI corresponding to Allowed S-NSSAI,” SA WG2 Temporary Document, SA WG2 Meeting #112bis, proposed S2-176633, Aug. 21-25, 2017, Sophia Antipolis, France, revision of S2-17xxxx, 10 pages. |
Huawei et al., “Discussion on network identifiers,” 3GPP TSG-RAN WG2 Meeting #101, R2-1802517, Athens, Greece, Feb. 26-Mar. 2, 2018, 2 pages. |
Huawei et al., “Discussion on 2-step RACH Procedure,” 3GPP TSG-RAN2 Meeting #96, R2-167588, Reno, USA, Nov. 14-18, 2016, 3 pages. |
Nokia et al., “Considerations on NR RACH procedures,” 3GPP TSG-RAN WG2 Meeting #96, R2-168013, Reno, USA, Nov. 14-18, 2016, 5 pages. |
Alcatel-Lucent, “Proposed way forward on Establishment cause values,” 3GPP TSG RAN WG2 #62, R2-082393, May 5-9, 2008, Kansas City, USA, 3 pages. |
Motorola, “Proposal for Establishment Cause Values,” TSG-RAN WG2 Meeting #62, R2-082608, Kansas City, USA, May 5-9, 2008, 4 pages. |
ZTE Corporation et al., “On 2-step RACH procedure in NR,” 3GPP TSG RAN WG1 Meeting #87, R1-1611274, Reno, USA, Nov. 14-18, 2016, 4 pages. |
3GPP TS 23.003 V15.3.0 (Mar. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 15), 118 pages. |
Intel Corporation, “5G network identifiers,” 3GPP TSG RAN WG2 Meeting #101, R2-1802944, Athens, Greece, Feb. 26-Mar. 2, 2018, 4 pages. |
3GPP TS 36.331 V14.5.1 (Jan. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 14), 764 pages. |
3GPP TS 38.321 V15.0.0 (Dec. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15), 55 pages. |
Number | Date | Country | |
---|---|---|---|
20230020819 A1 | Jan 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16940849 | Jul 2020 | US |
Child | 17945787 | US | |
Parent | PCT/CN2018/080887 | Mar 2018 | WO |
Child | 16940849 | US |