Method and apparatus for extended information element identifier
Patent Information
- Application Number
- PCT/EP2024/053632
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-01-30
- Filing Date
- 2024-02-13
- Publication Date
- 2024-11-28
Smart Images

Figure EP2024053632_28112024_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS FOR EXTENDED INFORMATION ELEMENT IDENTIFIERTECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more specifically to information elements (IES) of non-access stratum (NAS) messages.BACKGROUND
[0002] A wireless communications system or public land Mobile network (PLMN) may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as User Equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY
[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition Bwithout departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be constmed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
[0004] Some implementations of the method and apparatuses described herein may include a UE for wireless communication and comprising at least one memory and at least one processor coupled with the at least one memory. The processor is configured to cause the UE to transmit, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI, receive, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI, generate a NAS request message comprising at least one IE based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI, and transmit the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
[0005] In some implementations of the method and apparatuses described herein: a 5GMM capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI.
[0006] In some implementations of the method and apparatuses described herein: at least one bit of an octet of the 5GMM capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI.
[0007] In some implementations of the method and apparatuses described herein: a 5GS network feature support IE comprises the capability information of the network entity that indicates whether the network entity supports the extended IEI.
[0008] In some implementations of the method and apparatuses described herein: at least one bit of an octet of the 5GS network feature support IE comprises the capability information of the network entity that indicates whether the network entity supports the extended IEI
[0009] In some implementations of the method and apparatuses described herein: the extended IEI has a length of more than one octet.
[0010] In some implementations of the method and apparatuses described herein: the IE corresponds to a Type 1 IE of format TV; the extended IEI is encapsulated within a half octet of a first octet and one or more second octets; or a half octet of a first octet is empty and the extended IEI is encapsulated within one or more second octets.
[0011] In some implementations of the method and apparatuses described herein: the IE corresponds to a Type 2 IE of format T and the extended IEI is encapsulated within more than one octets.
[0012] In some implementations of the method and apparatuses described herein: the IE corresponds to a Type 3 IE of format TV; the extended IEI is encapsulated within more than one octet; and a value part is encapsulated within one or more octets.
[0013] In some implementations of the method and apparatuses described herein: the IE corresponds to a Type 4 IE of format TLV; the extended IEI is encapsulated within two or more octets; and a LI is encapsulated within one octet and precedes a value part which consists of zero, one, or up to 255 octets.
[0014] In some implementations of the method and apparatuses described herein: the IE corresponds to a Type 6 IE of format TLV-E; the extended IEI is encapsulated within at least two or more second octets; a LI is encapsulated within two octets; and a value part comprises zero, one, or up to 65,535 octets.
[0015] Some implementations of the method and apparatuses described herein may include a processor for wireless communication, comprising at least one controller coupled with at least one memory and configured to cause the processor to: transmit, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI; receive, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI; generate a NAS request message comprising at least one IE based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI; and transmit the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
[0016] Some implementations of the method and apparatuses described herein may include a method performed by a UE the method comprising: transmitting, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI; receiving, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI; generating a NAS request message comprising at least one IE based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI; and transmitting the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
[0017] Some implementations of the method and apparatuses described herein may include a Network Entity for wireless communication, comprising at least one memory and at least one processor coupled with the at least one memory. The processor is configured to cause the Network Entity to: receive, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI; transmit, via the NAS layer, a registration accept message comprising capability information of the Network Entity, wherein the capability information of the Network Entity indicates whether the Network Entity supports the extended IEI; and receive, via the NAS layer, a NAS request message comprising the at least one IE that includes the extended IEI.
[0018] In some implementations of the method and apparatuses described herein: a 5GMM capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI.
[0019] In some implementations of the method and apparatuses described herein: at least one bit of an octet of the 5GMM capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI.
[0020] In some implementations of the method and apparatuses described herein: a 5GS network feature support IE comprises the capability information of the network entity that indicates whether the network entity supports the extended IEI.
[0021] In some implementations of the method and apparatuses described herein: the capability of the network for an extended information element identifier is listed in a bit 4 of an octet of the 5GS network feature support information element.
[0022] In some implementations of the method and apparatuses described herein: the extended IEI has a length more than one octet.
[0023] In some implementations of the method and apparatuses described herein: the Network Entity being an AMF.BRIEF DESCRIPTION OF THE DRAWINGS
[0024] Figs la, lb and 1c illustrate various Type 1 standard IES of format V in accordance with aspects of the present disclosure.
[0025] Figure 2 illustrates a Type 2 standard IE of format T in accordance with aspects of the present disclosure.
[0026] Figs. 3a and 3b illustrate Type 3 standard IEs of format V and TV respectively in accordance with aspects of the present disclosure.
[0027] Figs. 4a and 4b illustrate Type 4 standard IEs of format LV and TLV respectively in accordance with aspects of the present disclosure.
[0028] Figs. 5a and 5b illustrate Type 6 standard IEs of format LV-E and TLV-E respectively in accordance with aspects of the present disclosure.
[0029] Figure 6 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
[0030] Figure 7 shows an example of a signaling diagram in accordance with aspects of the present disclosure.
[0031] Figure 8 shows an example 5GMM capability IE including indication of support by the UE for an extended IEI in accordance with aspects of the present disclosure.
[0032] Figure 9 shows an example 5GMM network feature support IE including indication of support by a Network Entity for an extended IEI in accordance with aspects of the present disclosure.
[0033] Figure 10 illustrates Type 1 standard IEs of format TV in accordance with aspects of the present disclosure.
[0034] Figure 11 illustrates a Type 2 standard IE of format T in accordance with aspects of the present disclosure .
[0035] Figure 12 illustrates a Type 3 standard IE of format TV in accordance with aspects of the present disclosure .
[0036] Figure 13 illustrates a Type 4 standard IE of format TLV in accordance with aspects of the present disclosure .
[0037] Figure 14 illustrates a Type 6 standard IE of format TLV-E in accordance with aspects of the present disclosure.
[0038] Figure 15 illustrates an example of a UE in accordance with aspects of the present disclosure.
[0039] Figure 16 illustrates an example of a processor in accordance with aspects of the present disclosure.
[0040] Figure 17 illustrates an example of a network equipment (NE) in accordance with aspects of the present disclosure.
[0041] Figure 18 is a flowchart of method performed by a UE in accordance with aspects of the present disclosure.
[0042] Figure 19 is a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION
[0043] A wireless communication system, which may include a public land mobile network (PLMN), may support NAS signalling (e.g., NAS messaging via a NAS layer). NAS signalling may use IES to indicate information. For example, a non-mandatory IE type may include an 8 bit binary number or octet, or two hexadecimal numbers (where the hexadecimal numbers are identified by respective 4-bit segments of the octet). An 8-bit range limits (to 256) numbers to uniquely identify non-mandatory IEs. This limitation may be problematic when it comes to introducing new non-mandatory IEs for new features as is likely with future 5G architectures.
[0044] For example, for services provided by the wireless communication system, routing functions of a 5G system (5GS) NAS pass standard layer-3 (L3) messages according to the protocol discriminator and protocol data unit (PDU) session identity towards the 5Gmobility management (5GMM) entities or towards the 5G session management (5GSM) entities of the various 5GS NAS service access points (SAPs). 3GPP TS 24.007 defines standard L3 messages as consisting of an “imperative part” which contains a header and an “non-imperative part”. The non-header of the imperative part and the non-imperative part are composed of successive parts, referred as standard IES, where each standard IE may have the following format:- an IE identifier (IEI);- a length indicator (LI); and- a value part.
[0045] A standard IE has one of the formats shown in Table 11.1 of 3GPP TS 24.007:Table 11.1: Formats of IEs
[0046] The IEI is of length half an octet if the IE is of type 1 IE of format TV and is one octet if the IE is of: type 2 IE of format T; type 3 IE of format TV; type 4 IE of format TLV; and type 6 IE of format TLV-E.The IEI is used for the non-mandatory standard IE, which may not be present. Formats with the IEI are T, TV, TLV or TLV-E.
[0047] If the format of the standard IE is LV or TLV, the length indicator (LI) of the standard IE is one octet. If the format of the standard IE is LV-E and TLV-E, the LI of thestandard IE is two octets where bit 8 of the first octet contains the most significant bit and bit 1 of the second octet contains the least significant bit.
[0048] The value part of a standard IE either consists of zero octet, a half octet, one octet, or multiple octets. The value part of a type 2 standard IE of format T does not consist of any value part, and as such it is always empty. If a standard IE is type 1 IE of format V or TV, the value part of the standard IE consists of a half octet, whilst a type 3 standard IE of format V or TV contains a value part of at least one octet. The value part of a type 4 standard IE of format LV or TLV consists of an integral number of octets, between 0 and 255 inclusive (as such it may be empty, i.e., consist of zero octets). For a standard IE of LV-E and TLV-E, the value part of a standard IE consists of an integral number of octets, between 0 and 65535 inclusive(and as such it may be empty, i.e., consist of zero octets).
[0049] According to clause 11.2.1.1.4 in 3GPP TS 24.007, five categories or types of standard IES are defined and each type adopts one or more of the formats listed above in Table 11.1. The types are as follows:
[0050] Type 11 - standard IEs of format V provide:The value in bit positions 8, 7, 6, 5 of an octet (Figure la); or the value in bit positions 4, 3, 2, 1 of an octet (Figure lb).2- or standard IEs of format TV have an IEI of a half octet length; they provide the IEI in bit positions 8, 7, 6, 5 of an octet and the value part in bit positions 4, 3, 2, 1 of the same octet (Figure 1c)
[0051] Type 2Standard IE has format T; its IEI consists of one octet, its value part is empty (Figure 2).
[0052] Type 31 - standard IEs of format V provide value part with at least one octet (Figure 3a): or 2- or standard IEs of format TV provide one octet IEI and an at least one octet value part (Figure 3 b).
[0053] Type 41- standard IE of format LV with LI having one octet and precedes the value part, which consists of zero, one, or up to 255 octets (Fig4a): or2- standard IE of format TLV with one octet IEI and LI having one octet and precedes the value part, which consists of zero, one, or up to 255 octets (Figure 4b).
[0054] Type 6 (No Type 4 is specified)1 - standard IE has format LV-E with LI having 2 octets and precedes the value part, which consists of zero, one or up to 65535 octets (Figure 5a): or2- standard IE has format TLV-E with one octet IEI and LI having 2 octets and precedes the value part, which consists of zero, one or up to 65535 octets (Figure 5b).
[0055] As will be apparent from the discussion below it is proposed here to introduce a mechanism that allows a User Equipment (UE) to inform a network of its support for an extended non-mandatory IEI at a time of registration of the UE with the network. This allows for the specification of lEIs of length greater than half an octet for type 1 IE of format TV or one octet for type 3 IE of format TV, type 4 IE of format TLV, and type 6 IE of format TLV- E.
[0056] Aspects of the present disclosure are described in the context of a wireless communications system.
[0057] Figure 6 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LIE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.
[0058] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0059] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
[0060] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
[0061] A UE 104 may be able to support wireless communication directly with other UEs104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to- everything (V2X) deployments, or cellular-V2X deployments, the communication link 114may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0062] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other directly or indirectly (e.g., via the CN 106). In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).
[0063] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
[0064] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).
[0065] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0066] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0067] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0068] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include anumber (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l, / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / i =0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0069] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0070] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHzsubcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.
[0071] The wireless communications system 100 may address the shortcomings of the current single (or half) octet length of an IEI, relevant to IES transmitted via a NAS layer (some IEs containing information IEI may be non-mandatory IEs). The wireless communications system 100 may allow a UE to inform a network of its support for an extended IEI at the time of registration of the UE with the network. A possible registration exchange is illustrated in Figure 7.
[0072] In the Register Request 150 the UE may insert a 5GS mobility management (5GMM) capability IE set defined in clause 9.11.3.1 of3GPP TS 24.501. The new capability may be indicated in the 5GMM capability IE specified in Figure 9.11.3.1.1 of 3GPP TS 24.501. This IE is illustrated in accompanying Figure 8 where, if ExtIEI is 0 then extended IE identifier is not supported while, if ExtIEI is 1 , then extended IE identifier is supported.
[0073] Similarly, the network may insert an indicator in the 5GS network feature support IE, Register accept 152, as defined in clause 9.11.3.5 of 3GPP TS 24.501, that the network supports or does not support the extended IE identifier. This IE is illustrated in accompanying Figure 9 where, if ExtIEI is 0 then extended IE identifier is not supported while, if ExtIEI is 1, then extended IE identifier is supported.
[0074] The register request 150 and the register accept 152 may use the current standard IE identifier as defined in clause 11.2.1.1.4 in 3GPP TS 24.007, i.e. the first registration request containing 5GMM capability information element with the new indicator and the registration accept containing 5GS network feature support information element with the indicator, use the conventional information element identifiers (lEIs) for the NAS messages [the UE and the network do not know that the other entity is using the new proposed information element indicators (lEIs)].
[0075] In matter of fact the network can send the NAS messages with the new lEIs while also sending its support for the new lEIs, since the network has already received indication from the UE that it supports the new lEIs.
[0076] Five categories or types of standard IES that include and IEI are defined below.Type l : standard IEs of format TV including an IEI of a half octet length; or an empty half an octet length, in bit positions 8, 7, 6, 5 of an octet followed by one or more octets as the extension of the IEI (Figure 10).Type l : standard IE has format T with the extended IEI containing one or more octets (Figure 11).Type 3 : standard IEs of format TV provide the extended IEI containing one or more octets, and in addition at least one octet value part (Figure 12).Type 4 : standard IE of format TLV with the extended IEI containing one or more octets, and LI having one octet and precedes the value part, which consists of zero, one, or up to 255 octets (Figure 13).Type 6 : standard IE has format TLV-E with the extended IEI containing one or more octets, and LI having 2 octets and precedes the value part, which consists of zero, one or up to 65535 octets (Figure 14).
[0077] Backward compatibility analysis shows, since the UE and the network inform each other about their support for the extended IEI, no backward compatibility issues arise.
[0078] Figure 15 illustrates an example of a UE 200 in accordance with aspects of the present disclosure. The UE 200 may include a processor 202, a memory 204, a controller 206, and a transceiver 208. The processor 202, the memory 204, the controller 206, or the transceiver 208, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0079] The processor 202, the memory 204, the controller 206, or the transceiver 208, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0080] The processor 202 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In someimplementations, the processor 202 may be configured to operate the memory 204. In some other implementations, the memory 204 may be integrated into the processor 202. The processor 202 may be configured to execute computer-readable instructions stored in the memory 204 to cause the UE 200 to perform various functions of the present disclosure.
[0081] The memory 204 may include volatile or non-volatile memory. The memory 204 may store computer-readable, computer-executable code including instructions when executed by the processor 202 cause the UE 200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 204 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.
[0082] In some implementations, the processor 202 and the memory 204 coupled with the processor 202 may be configured to cause the UE 200 to perform one or more of the functions described herein (e.g., executing, by the processor 202, instructions stored in the memory 204). For example, the processor 202 may support wireless communication at the UE 200 in accordance with examples as disclosed herein. The UE 200 may be configured to support a means for wireless communication and comprising at least one memory and at least one processor coupled with the at least one memory. The processor is configured to cause the UE to transmit, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI, receive, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI, generate a NAS request message comprising at least one IE based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI; and transmit the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
[0083] The controller 206 may manage input and output signals for the UE 200. The controller 206 may also manage peripherals not integrated into the UE 200. In someimplementations, the controller 206 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 206 may be implemented as part of the processor 202.
[0084] In some implementations, the UE 200 may include at least one transceiver 208. In some other implementations, the UE 200 may have more than one transceiver 208. The transceiver 208 may represent a wireless transceiver. The transceiver 208 may include one or more receiver chains 210, one or more transmitter chains 212, or a combination thereof.
[0085] A receiver chain 210 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 210 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 210 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 210 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 210 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0086] A transmitter chain 212 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 212 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 212 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0087] Figure 16 illustrates an example of a processor 300 in accordance with aspects of the present disclosure. The processor 300 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 300 may include a controller 302 configured to perform various operations in accordance with examples as described herein. The processor 300 may optionally include at least onememory 304, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 300 may optionally include one or more arithmetic-logic units (ALUs) 306. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0088] The processor 300 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 300) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).
[0089] The controller 302 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 300 to cause the processor 300 to support various operations in accordance with examples as described herein. For example, the controller 302 may operate as a control unit of the processor 300, generating control signals that manage the operation of various components of the processor 300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0090] The controller 302 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 304 and determine subsequent instruction(s) to be executed to cause the processor 300 to support various operations in accordance with examples as described herein. The controller 302 may be configured to track memory address of instructions associated with the memory 304. The controller 302 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 302 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 300 to cause the processor300 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 302 may be configured to manage flow of data within the processor 300. The controller 302 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 300.
[0091] The memory 304 may include one or more caches (e.g., memory local to or included in the processor 300 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 304 may reside within or on a processor chipset (e.g., local to the processor 300). In some other implementations, the memory 304 may reside external to the processor chipset (e.g., remote to the processor 300).
[0092] The memory 304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 300, cause the processor 300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 302 and / or the processor 300 may be configured to execute computer-readable instructions stored in the memory 304 to cause the processor 300 to perform various functions. For example, the processor 300 and / or the controller 302 may be coupled with or to the memory 304, the processor 300, the controller 302, and the memory 304 may be configured to perform various functions described herein. In some examples, the processor 300 may include multiple processors and the memory 304 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0093] The one or more ALUs 306 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 306 may reside within or on a processor chipset (e.g., the processor 300). In some other implementations, the one or more ALUs 306 may reside external to the processor chipset (e.g., the processor 300). One or more ALUs 306 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 306 may receive input operands and an operation code, whichdetermines an operation to be executed. One or more ALUs 306 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 306 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 306 to handle conditional operations, comparisons, and bitwise operations.
[0094] The processor 300 may support wireless communication in accordance with examples as disclosed herein. The processor 300 may be configured to or operable to support a means for wireless communication comprising at least one controller coupled with at least one memory and configured to cause the processor to transmit, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI; receive, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI; generate a NAS request message comprising at least one IE based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI; and transmit the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
[0095] Figure 17 illustrates an example of a NE 400 in accordance with aspects of the present disclosure. The NE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0096] The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or anycombination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0097] The processor 402 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 402 may be configured to operate the memory 404. In some other implementations, the memory 404 may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in the memory 404 to cause the NE 400 to perform various functions of the present disclosure.
[0098] The memory 404 may include volatile or non-volatile memory. The memory 404 may store computer-readable, computer-executable code including instructions when executed by the processor 402 cause the NE 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 404 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.
[0099] In some implementations, the processor 402 and the memory 404 coupled with the processor 402 may be configured to cause the NE 400 to perform one or more of the functions described herein (e.g., executing, by the processor 402, instructions stored in the memory 404). For example, the processor 402 may support wireless communication at the NE 400 in accordance with examples as disclosed herein. The NE 400 may be configured to support a means for wireless communication, comprising at least one memory and at least one processor coupled with the at least one memory and configured to cause the Network Entity to receive, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI; transmit, via the NAS layer, a registration accept message comprising capability information of the Network Entity, wherein the capability information of the Network Entity indicates whether the Network Entity supports the extended IEI; and receive, via the NAS layer, a NAS request message comprising the at least one IE that includes the extended IEI
[0100] The controller 406 may manage input and output signals for the NE 400. The controller 406 may also manage peripherals not integrated into the NE 400. In some implementations, the controller 406 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 406 may be implemented as part of the processor 402.
[0101] In some implementations, the NE 400 may include at least one transceiver 408. In some other implementations, the NE 400 may have more than one transceiver 408. The transceiver 408 may represent a wireless transceiver. The transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.
[0102] A receiver chain 410 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 410 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 410 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 410 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 410 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0103] A transmitter chain 412 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0104] Figure 18 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as describedherein. In some implementations, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions.
[0105] At 602, the method may include transmitting, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended IEI. The operations of 602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 602 may be performed by a UE as described with reference to Figure 15.
[0106] At 604, the method may include receiving, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI. The operations of 604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 604 may be performed by a UE as described with reference to Figure 15.
[0107] At 606, the method may include generating a NAS request message comprising at least one IE based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI. The operations of 606 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 606 may be performed by a UE as described with reference to Figure 15.
[0108] At 608, the method may include transmitting the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer. The operations of 608 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 608 may be performed by a UE as described with reference to Figure 15.
[0109] Figure 19 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
[0110] At 702, the method may include receiving, via a NAS layer, a registration request message comprising capability information of the UE, wherein the capability information ofthe UE indicates whether the UE supports an extended IEI The operations of 702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 702 may be performed by a NE as described with reference to Figure 17.
[0111] At 704, the method may include transmitting, via the NAS layer, a registration accept message comprising capability information of the Network Entity, wherein the capability information of the Network Entity indicates whether the Network Entity supports the extended IEI The operations of 704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 704 may be performed by a NE as described with reference to Figure 17.
[0112] At 706, the method may include receiving, via the NAS layer, a NAS request message comprising the at least one IE that includes the extended IEI The operations of 706 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 706 may be performed by a NE as described with reference to Figure 17.
[0113] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
What is claimed is:
1. A User Equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit, via a Non-Access Access Stratum (NAS) layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended Information Element Identifier (IEI); receive, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI; generate a NAS request message comprising at least one Information Element (IE) based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI; and transmit the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
2. The UE of claim 1, wherein a Fifth Generation 5G Mobility Management (5GMM) capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI.
3. The UE of claim 2, wherein at least one bit of an octet of the 5GMM capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI4. The UE of any of claims 1 to 3, wherein a 5G System (5GS) network feature support IE comprises the capability information of the network entity that indicates whether the network entity supports the extended IEI.
5. The UE of claim 4, wherein at least one bit of an octet of the 5GS network feature support IE comprises the capability information of the network entity that indicates whether the network entity supports the extended IEI.
6. The UE of any preceding claim, wherein the extended IEI has a length of more than one octet.
7. The UE of any preceding claim, wherein: the IE corresponds to a Type 1 IE of format TV; the extended IEI is encapsulated within a half octet of a first octet and one or more second octets; or a half octet of a first octet is empty and the extended IEI is encapsulated within one or more second octets.
8. The UE of any one of claims 1 to 6, wherein the IE corresponds to a Type 2 IE of format T and the extended IEI is encapsulated within more than one octets.
9. The UE of any of claims 1 to 6, wherein: the IE corresponds to a Type 3 IE of format TV; the extended IEI is encapsulated within more than one octet; and a value part is encapsulated within one or more octets.
10. The UE of any preceding claim, wherein: the IE corresponds to a Type 4 IE of format TLV; the extended IEI is encapsulated within two or more octets; and a Length Indicator (LI) is encapsulated within one octet and precedes a value part which consists of zero, one, or up to 255 octets.
11. The UE of any preceding claim, wherein: the IE corresponds to a Type 6 IE of format TLV-E;the extended IEI is encapsulated within at least two or more second octets; a Length Indicator (LI) is encapsulated within two octets; and a value part comprises zero, one, or up to 65,535 octets.
12. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: transmit, via a Non-Access Stratum (NAS) layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended Information Element Identifier (El); receive, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI; generate a NAS request message comprising at least one Information Element (IE) based at least in part on one or more of the capability information of the UE or the capability information of the network entity, wherein the at least one IE includes the extended IEI; and transmit the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
13. A method performed by a User Equipment (UE) the method comprising: transmitting, via a Non-Access Access Stratum (NAS) layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended Information Element Identifier (IEI); receiving, via the NAS layer, a registration accept message comprising capability information of a network entity, wherein the capability information of the network entity indicates whether the network entity supports the extended IEI; generating a NAS request message comprising at least one Information Element (IE) based at least in part on one or more of the capability information of theUE or the capability information of the network entity, wherein the at least one IE includes the extended IEI; and transmitting the NAS request message, comprising the at least one IE that includes the extended IEI, via the NAS layer.
14. A Network Entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the Network Entity to: receive, via a Non-Access Stratum (NAS) layer, a registration request message comprising capability information of the UE, wherein the capability information of the UE indicates whether the UE supports an extended Information Element Identifier (El); transmit, via the NAS layer, a registration accept message comprising capability information of the Network Entity, wherein the capability information of the Network Entity indicates whether the Network Entity supports the extended IEI; and receive, via the NAS layer, a NAS request message comprising the at least one IE that includes the extended IEI.
15. The Network Entity of claim 14, wherein a Fifth Generation 5G Mobility Management (5GMM) capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI.
16. The Network Entity of claim 15, wherein at least one bit of an octet of the 5GMM capability IE comprises the capability information of the UE that indicates whether the UE supports the extended IEI.
17. The Network Entity of any of claims 14 to 16, wherein a 5G System (5GS) network feature support IE comprises the capability information of the network entity that indicates whether the network entity supports the extended IEI.
18. The Network Entity of claim 17, wherein the capability of the network for an extended information element identifier is listed in a bit 4 of an octet of the 5GS network feature support information element.
19. The Network Entity of any of claims 14 to 18, wherein the extended IEI has a length more than one octet.
20. The Network Entity of any one of claims 14 to 19, the Network Entity being an Access and Mobility Management Function (AMF).
Citation Information
Patent Citations
Method and device for reducing data loss in mobile communication system
US20210297888A1
Communication method and communication apparatus
WO2024000412A1
