MX2008009448A - Extended capability transfer between a user equipment and a wireless network - Google Patents

Abstract

Techniques for transferring new capability information in an efficient and backward compatible manner are described. A user equipment (UE) may send a new capability indicator to a wireless network to indicate that the UE has new capability information to send. This new capability indicator may be implemented with a spare bit in an information element included in an initial message sent to the network. The network may request for the information or indicate that it can receive the information. The UE may then send the new capability information to the network upon receiving the request or the indication. Alternatively, the network may convey that it supports transfer of new capability information, e.g., via a broadcast message or a unicast message. The UE may then send new capability information at any time to the network, without having to send the new capability indicator.

Description

TRANSFER OF EXTENDED CAPACITY BETWEEN A USER EQUIPMENT AND A WIRELESS NETWORK FIELD OF THE INVENTION The present disclosure generally refers to communication, and more specifically, to techniques for transferring capabilities between a user equipment (UE) and a wireless communication network.

BACKGROUND OF THE INVENTION A UE (for example, a cell phone) can establish communication with a wireless communication network in order to obtain various communication services such as voice, video, packet data, messaging, broadcasting, etc. The UE can register with the network, prior to obtaining any services. During registration, the UE can provide a list of its capabilities to the network, and the network can similarly provide a list of its capabilities to the UE. The UE and the network can also exchange lists of capabilities when the UE has access to the network before or after registration, for example, when the UE has access to a new base station. Each list of capabilities can allow a receiving entity (the UE or network) to know which capabilities the sending entity supports and, therefore, which capabilities and characteristics can be requested and used for various services. The network can transmit some or all of its capabilities. This can then allow the UE as well as other UEs to receive the network capabilities without having to exchange signaling with the network. The network can also send its capabilities in a point-to-point way to the UE. In this case, the UE should be registered (or in the act of registration) with the network and can interact explicitly with the network to obtain network capabilities. The UE can send its capabilities to the network in a point-to-point manner before, during or after registration. The UE can also send its capabilities in other cases, such as when entering an active state with the network in order to use a service in the network (for example, making an outgoing call), to respond to a location request from the network for a certain service invoked by the network (for example, receiving an incoming call), etc. The UE can send its capabilities in an information element (IE) to the network. The network can also send its capabilities in the same element of information or in an information element different from the UE. An information element can be a parameter that can be included in a message and can be defined with specific fields of specific lengths. Different capacities can be transmitted through different fields of the information element. The UE and the network can transfer capacity information using specific messages and information elements with the ability to transmit known capabilities at the time messages and information elements are defined. However, new capabilities can be added as wireless technology evolves, as the design of the UEs improves, etc. The ability to include information in new capabilities using existing messages and information elements can be restricted, for example, because messages and information elements can not be expanded to include new capacity information. New messages and / or new information elements can be defined to transmit information of new capacity. However, these new messages and / or information elements may cause compatibility problems for UEs and networks that do not support these new messages and / or information elements. In addition, these new messages and / or elements of Information may have development impacts on the network entities that transport them. Therefore, there is a need for techniques to transfer new capacity information in a compatible way backwards and / or with little or no development impact.

SUMMARY OF THE INVENTION Here we describe techniques for transferring new capacity information in an efficient and backward compatible manner. In one aspect, a UE can send a new capacity indicator to a wireless network to indicate that the UE has new capacity information to send and that the UE can send the information. This new capacity indicator can be executed with a reservation bit in an information element included in a message sent by the UE to the network. The new capacity information may comprise any information that is not transferable in the information element sent to the network. If the network supports the transfer of new capacity information and recognizes the new capacity indicator, then the network can request the information or indicate that it can receive the information. The EU can send the new capacity information to the network when receiving the request or indication from the network. In another aspect, the network can transmit that it supports the transfer of new capacity information, for example, through a broadcast message sent to all the UEs or a unicast message sent to the UE. The UE can then send the new capacity information at any time to the network, without having to send the new capacity indicator. In the following, various aspects and characteristics of the invention are described in greater detail.

BRIEF DESCRIPTION OF THE FIGURES Figure 1 shows a display that includes several wireless networks. Figure 2A shows an information element for the Mobile Station (MS) Class Mark 1. Figure 2B shows an information element for MS Class 2 Mark. Figure 2C shows an information element for MS Class 3 Mark. Figures 3 and 4 show message flows for two new information transfer designs capacity from a UE to a wireless network. Figures 5 and 6 show two processes for transferring new capacity information. Figure 7 shows a block diagram of a UE, a base station, and a network entity.

DETAILED DESCRIPTION OF THE INVENTION The techniques described herein can be used for several wireless communication networks such as Global System for Mobile Communications (GSM) networks, Universal Mobile Telecommunications System (UMTS) networks, Code Division Multiple Access (CDMA) networks, networks wireless local area (WLAN), etc. The terms "network" and "system" are often used interchangeably. A GSM network uses GSM radio technology. A UMTS network can use broadband CDMA or some other radio technology. A CDMA network can use CDMA2000 IX, CDMA2000 lxEV-DO, or some other cdma2000 radio technology. A WLAN can use a radio technology of IEEE 802.11, Hiperlan, etc. W-CDMA and GSM are described in the documents of an organization called "Third Generation Society Project" (3GPP). cdma2000 is described in the documents of an organization called "3rd Generation Society Project 2" (3GPP2). These documents are publicly available. Figure 1 shows the display 100 that includes a GSM network 110, a UMTS network 120, a CDMA 130 network, and a WLAN 140. For simplicity, only one case of some network entities is shown for each of the networks 110, 120, 130 and 140. The GSM network 110 includes Base Transceiver Stations (BTS) 112 that communicate with the UEs within the coverage area of the GSM network. A Base Station Controller (BSC) 114 is coupled to the BTS 112 and provides coordination and control for these BTS. A Mobile Switching Center / Serving GPRS Support Node (MSC / SGSN) 116 is coupled to the BSC 114 and a core network 118 and performs various functions such as data routing. The MSC 116 supports circuit switched services for the UEs that communicate with the GSM network 110. The SGSN 116 supports General Packet Radio Service (GPRS) and provides packet switched services for the UEs that communicate with the GSM network 110 The core network 118 includes several entities that support various services for the GSM network 110. The core network 118 can be coupled to a Public Switched Telephone Network (PSTN) and / or a data network (for example, the Internet) 148 .

The UMTS network 120 includes the Nodes B 122 that communicate with the UEs within the coverage area of the UMTS network. A Radio Network Controller (RNC) 124 couples the Nodes B 122 and provides coordination and control for these Nodes B. An MSC / SGSN 126 couples the RNC 124 and a core network 128 and executes routing and other functions. The core network 128 supports several services for the UMTS network 120 and can be coupled to the PSTN or data network 148. The CDMA network 130 includes the BTSs 132 which communicate with the network. the UEs within the coverage area of the CDMA network. A BSC and possibly a Packet Control Function (PCF) 134 is coupled to the BTS 132 and provides coordination and control for these BTSs. An MSC or Packet Data Service Node (PDSN) 136 is coupled to the BSC (+ PCF) 134 and a core network 138. The BSC 134 and MSC 136 support circuit switched services while the PCF 134 and PDSN 136 support package switched services. PCF 134 is present for PDSN 136. Core network 138 supports several services for CDMA network 130 and can be coupled to PSTN or data network 148. WLAN 140 includes access points 142 communicating with UEs within the area of WLAN coverage. A router 144 couples to access points 142 and routes data for these access points. Router 134 can also be coupled to other entities and / or networks. For example, router 134 may be coupled to a 3GPP LAN network, which may include a WLAN Access Door (WAG) and a Packet Data Door (PDG). The 3GPP WLAN network may be coupled to a 3GPP core network, for example, the core network 118 or 128. Alternatively or additionally, the router 134 may be coupled to a Packet Data Interworking Function (PDIF), which it can be coupled to a core network 3GPP2, for example, the core network 138. A UE 150 can have the ability to establish communication only with the GSM network 110, only with the UMTS 120 network, only with the CDMA 130 network, both with the GSM network 110 as with the UMTS 120 network, or some other network or combination of networks. The UE 150 may be stationary or mobile and may also be referred to as a mobile station, a terminal, a mobile equipment, a subscriber unit, a station, etc. The terms "UE", "mobile station", and "terminal" are synonyms and are used here interchangeably. The UE 150 may also be a cellular telephone, a personal digital assistant (PDA), a wireless communication device, a handheld device, a wireless modem, a portable computer, etc. UE 150 can establish communication with one or more base stations in a wireless network in the link descending and / or uplink at any given moment. The downlink (or forward link) refers to the communication link from the base stations to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base stations. A base station can correspond to a BTS, a Node B, an access point, etc. The techniques described here can be used for several wireless networks. For clarity, some aspects of the techniques are described for GSM and UMTS networks. The UE may send its capabilities to a wireless network (eg, GSM network 110 or UMTS network 120) during registration with the network and possibly at other times. For example, the UE can send its capabilities in an information element for the Mobile Station (MS) Mark of Class 1, 2 or 3 defined in the 3GPP version 6. The MS Mark of Class 1 provides the network with information regarding aspects High priority of the EU. MS Brand Class 2 provides the network with information regarding high and low priority aspects of the UE. The Class 3 MS Mark provides the network with information regarding aspects of the UE. The information in the MS Mark of Class 1, 2, or 3 may indicate general characteristics of the UE and may affect the way in which the network handles the operation of the UE.

Figure 2A shows MS Class 1 information element 210, which has two octets in length. The octet 1 includes an information element identifier (IEI) for the MS Mark of Class 1. The byte 2 includes a revision level field, a controlled Advance Class Mark (IS IND) sending option field, an A5 / 1 field of encryption algorithm, a radio frequency (RF) power capacity field, and a reserve bit (shown with shading in Figure 2A and always set to zero for 3GPP Version 6 and 3GPP Versions) previous). These fields are described in 3GPP TS 24.008, entitled "Mobile Radio Interface Layer 3 Specification; Core Network Protocols; Stage 3" which is publicly available. Figure 2B shows an MS information element 220 Class 2 Mark, which has five octets in length. The octet 1 includes an IEI for the MS Mark of Class 2. The octet 2 includes the length of the information element of MS Mark of Class 2. The octet 3 includes all the fields in octet 2 of the MS information element. Class 1. The octet 4 includes a pseudo-synchronization capability (PS) field, a supplementary service selection indicator (SS) field, a short message capability (SM) field, a Voice Broadcasting Service Notification Receiving Field (VBS), a group call service notification (VGCS) reception field, a frequency capability (FC) field, and a reserve bit set to zero. The octet 5 includes a Class 3 Mark field (CM3), a localized service area support field (SoLSA), a connection management service (CM) indicative field (CMSP), an A5 / algorithm field. 3, an A5 / 2 encryption algorithm field, and a reserve bit set to zero. These fields are described in 3GPP TS 24.008. Figure 2C shows an MS information element 230 Class 3 Mark, which may be up to 14 octets in length. This information element includes a number of fields that are coded according to the CSN.l rules described in 3GPP TS 24.007, entitled "Layer 3 mobile radio interface signaling; general aspects ", Annex B. Some fields are mandatory and have a fixed format, some fields are optional and can be included by setting a bit, and some fields have flexible formats that can be indicated by one or more header bits. , the Class 3 MS Mark information element includes a reservation bit set to zero at startup and may include one or more reserve bits set to zero at the end. Although not defined in 3GPP version 6, an extension bit can be added to the MS Class 3 Brand information element to indicate new capacity information, as shown in Figure 2C. As shown in Figures 2A to 2C, the information elements for Class 1, 2 and 3 Mark MSs can indicate various capabilities of the UE, such as the supported encryption algorithms, the RF power capacity, the capacity for be notified of a request for geographical location for the EU, etc. The UE may send its capabilities in one or more Classmark information elements in a CM Service Request message, a CM Reset Request message, a Location Update Request message, a Location Response message, etc. The UE may send the CM Service Request message to request the establishment of the switched circuit connection, the activation of supplementary services, the transfer of short messages, location services, etc. The UE can send the CM Reset Request message to request the restoration of a connection. The UE can send the Location Update Request message to request the update of its location file or to request the IMSI annex. He UE may send the Location Response message as a response to a Location Request message. These messages are described in 3GPP TS 24.008 and in 3GPP TS 44.018, entitled "Layer 3 Specification of Mobile Radio Interface; Radio Resource Control Protocol (RRC)", both are publicly available. The Class Mark information elements have fixed maximum lengths, and most of the bits in each Class Mark information element are currently used. In 3GPP Version 6, the information element of MS Mark of Class 1 has a single reservation bit, the information element of MS Mark of Class 2 has three bits of single reservation, and the information element of MS Mark of Class 3 It has some spare bits. The reserve bits can be used to transmit new UE capabilities. However, the limited number of reserve bits and the limitation on the maximum size of the information element in the case of MS Class 3 mark mean that only a few capabilities can be transmitted directly with these reserve bits. You can define a new information element to carry new capacity / additional information. In the present description, "new" capacity information and "additional" capacity information are synonyms and are used interchangeably. The new information element can be included in a message (for example, a CM Service Request message) initially sent by the UE to the network. This would then allow the network to obtain the new capacity information of the initial message sent by the UE. However, the size of the initial message may be limited due to the restrictions imposed during the transport of the message from the UE to the network. The limitation of the message size for some messages carrying information elements of MS Mark of Class 1, 2 and 3 is 20 octets in GSM, and some messages are already very close to this limit. In one aspect, the UE can transfer new information capability information to the network by first sending a new capacity indicator to indicate that the UE has new capacity information to send and that the UE can send the information. This new capacity indicator can be executed with any reservation bit in any Class Mark information element and can be sent in an initial message to the network. If the network supports the transfer of new capacity information and recognizes the new capacity indicator, then the network You can request the information or indicate who can receive the information. The UE can send new capacity information to the network when receiving the request or indication from the network. Figure 3 shows a design of a message flow message stream 300 for transferring new capacity information from the UE to the network. The UE may send a CM Service Request message (some other message) which may include an MS Information Item (IE) Class 2 (step 312). A reservation bit in this Class Mark information element (for example, bit 7 of octet 5 in Figure 2B) can be set to a binary one ('?') to indicate that the UE has new capacity information to send. The establishment of the binary one is different from the zero value that is used when the bit is reserved. Therefore, this binary one can be detected by any entity that has been programmed to look for it and can be recognized as an indication of the UE's ability to send more information. A BTS / BSC may receive this message from the UE and forward it to the MSC (step 314). The MSC can receive the message and respond with a CM Service Acceptance message (step 316), which can be forwarded by the BTS / BSC to the UE (step 318). The MSC can store the UE capabilities included in the MS information element Class 2 mark received from the UE (step 320). If the MSC supports the transfer of new capacity information and wishes to receive this information from the UE, then because the MSC has detected the capability of the UE to send this capacity information, the MSC can send a message of Capacity Request of the UE (some other message) to request the information (step 322). The BTS / BSC may receive this message from the MSC and forward it to the UE (step 324). The UE can receive the Capacity Request message from the UE and recognize that the MSC supports and wishes to transfer the new capacity information. The UE may then send the new capacity information in a UE Capacity Response message (or some other message) (step 326). The BTS / BSC can receive this message from the UE and forward it to the MSC (step 328). The MSC can receive the Capacity Response message from the UE and store the new capacity information included in the message (step 330). The MSC can control the operation of the UE based on the UE capabilities received in the initial CM Service Request message and the new / additional UE capabilities received in the message of the subsequent UE Capability Response. In general, the information in steps 322, 324, 326 and 328 can be sent in new messages not defined in current 3GPP Version 6, new information elements in existing messages, or new contents for existing information elements in existing messages, etc. In another design, the MSC receives the new capacity indicator from the UE and sends an indication (instead of a separate message) that the MSC can receive the new capacity information. This indication can be an indicator or a designated bit that can be included in any message sent to the UE, for example, the message of Service Acceptance CM in step 316. In the example shown in Figure 3, the messages are exchanged between the UE and the MSC through the BTS / BSC to transfer capacity information from the UE to the MSC. In general, the UE can transfer capacity information to any network entity designated to receive the capacity information. The UE can send different capacity information to different network entities. For example, the capacity information in MS Marks of class 1, 2 and 3 can be sent to different network entities. In the design described above, the UE initially sends the MS Classification Mark 2 information element with the new capacity indicator to an MSC. The Techniques can also be used for other Class Mark information elements. In another design, the UE initially sends the Class 3 MS Mark information element with the new capacity flag set to indicate that the UE has new / additional capacity information that is not transferable in this information element. This new capacity indicator can be executed with the extension bit or some other new bit or new bit field in the MS information element. Class 3 mark. The network can receive the new capacity indicator and can send a request or an indication (for example, in a Class Mark Query message) to request new capacity information from the UE. The UE may then send the new capacity information to the network in a new information element included in a message, a Class Mark Change message. As an alternative, the network may send a request or an indication (eg, in a Class Mark Query message) to request new capacity information from the UE, even if the MS information element Class 3 Mark. it is not modified to support a new capacity indicator from the UE. In this case, the UE can ignore the network request if the UE does not support the new capacity information.

In the following description, a "legacy" UE is a UE that does not support the transfer of new capacity information using the techniques described herein. For example, a UE that supports current 3GPP Version 6 or an earlier version of 3GPP specifications. A "legacy" network entity is a network entity that does not support the transfer of new capacity information, for example, a network entity that supports a current or previous 3GPP version. It is assumed that an UE supports the transfer of new capacity information and, therefore, is a "new" UE unless it is indicated as a legacy UE. Similarly, it is assumed that a network entity supports the transfer of new capacity information, and is therefore a "new" network entity, unless it is indicated as a legacy network entity. The new capacity indicator can be executed with any reservation bit that is ignored by the legacy network entities, for example, legacy MSC. This reserve bit can be used to indicate the following: 1. The UE has new / additional capacity information that is not transferable in a class-marking information element, and 2. The UE has the capability to transfer the new / additional capacity information. This reserve bit can be set to (i) a binary value of one ("1") to indicate that the UE has new capacity information to send or (ii) a binary value of zero ("0") to indicate that The UE does not have any new capacity information to send. The new network entities could correctly interpret this reservation bit. The use of the reserve bit to execute the new capacity indicator is backwards compatible with current and previous 3GPP versions and does not adversely impact the operation of the legacy network and legacy UE entities. The legacy UEs can set this reserve bit to zero ("0") according to the GSM specifications. The new and legacy network entities will correctly interpret this reservation bit and know that these legacy UEs do not have new capacity information to send. The new network entities would not request new capacity information from the legacy UEs because this reserve bit would not be set to one ("1"). New UEs can set this reserve bit to one ("1") as long as these UEs have new capacity information to send. The legacy network entities would ignore the establishment of one of the reserve bit, they would not request that these UEs Send your new capabilities, and you would not receive messages that carry the new capabilities. A new network entity (for example, a new MSC) can detect a one ("1") for the reservation bit used as the new capacity indicator from a new UE. This network entity may send a new message (for example, the message of Capacity Request of the UE in Figure 3, a new message of Mobility Management (MM), etc.) or possibly an existing message (for example, a existing MM message) to the UE. This message or an information element in this message may request the UE to send its new capacity information. The UE can then respond with a new message (e.g., the Capacity Response message of the UE in Figure 3, a new MM message, etc.) or an existing message (e.g., an existing MM message). This message may contain one or more information elements carrying new capabilities supported by the UE. In general, a network entity may send a request message (e.g., as shown in Figure 3) or an indication to transmit the following: 1. The network entity has received the new capacity indicator from the UE , Y 2. The network entity can and wants to receive the new capacity / additional information from the UE. The UE can send the new capacity indicator in any information element, such as those for the MS Brands of Classes 1, 2 and 3, to the network. The new capacity indicator allows the network to have immediate knowledge, at the time of receiving the information element, that the UE has new capacity information to send. The network can then request this new capacity information from the UE before invoking or using any service that may depend on the new capabilities of the UE. A message containing the new capacity indicator from the UE can carry additional information. Similarly, a message sent by the network to request new capacity information from the UE may also carry additional information. For example, the request message from the network may include additional network capabilities, for example, capabilities not defined in the current 3GPP version and not supported by the legacy UEs. Message exchange can also be used to negotiate some features and capabilities between the network and in the UE. For example, the network can indicate features that it supports and that the UE would like to support for the current session or service that is being invoked. The UE may indicate some or all of the features it is willing to support. In another aspect, the network transmits that it supports the transfer of new capacity information from the UE. The UE can then send new capacity information at any time to the network, without having to send the new capacity indicator. Figure 4 shows a design of a message flow 400 for transferring new capacity information from the UE. The UE may receive an indication that the network supports the transfer of new capacity information (step 410). This indication may be an indicator that is transmitted over the network, for example, in a Transmission Control Channel (BCCH) in GSM or in a System Information message in UMTS. This indication can be transmitted through a unicast message, for example, a Location Request message sent to the UE. The UE may send a CM Service Request message (or some other message) which may include the Class 2 Mark MS information element (step 412). Because the UE knows that the network supports the New capacity information transfer, the UE does not need to send the new capacity indicator. A BTS / BSC can receive the message from the UE and forward it to an MSC (step 414). The MSC can receive the message and respond with a CM Service Acceptance message (step 416), which can be forwarded by the BTS / BSC to the UE (step 418). The MSC can store the UE capabilities included in the class mark information element (step 420). The UE may also send the new capacity information in a UE Capacity Report message (or some other message) (step 426). The BTS / BSC may receive this message from the UE and forward it to the MSC (step 428). The MSC can receive the UE Capacity Report message and store the new capacity information included in the message (step 430). The MSC can control the UE information based on the UE capabilities received in the initial CM Service Request message and the new / additional UE capabilities received in the subsequent UE Capability message. In still another aspect, the UE may send new capacity information in a new message or an existing message without sending the new capacity indicator to inform the network and / or without receiving a indication that the network supports the transfer of new capacity information. The UE can simply assume that the network supports the transfer of new capacity information without receiving an explicit indication of the network. The message containing the new capacity information may be sent in a manner to avoid or reduce the likelihood of problems with legacy network entities. For example, new capacity information may be included in an optional information element in an outbound message. A legacy network entity that does not support the optional information element can simply ignore it. The UE can send new capacity information to the network according to the latest version supported by both the UE and the network. In 3GPP and 3GPP2, each new version is backwards compatible with all previous versions and may include additional features and capabilities not supported by previous versions. For example, a new version can support new messages, new information elements, new parameter values, new protocols, new interfaces, etc. The UE and the network can validly exchange messages based on the latest version supported by both entities. The UE can receive information in the version supported by the network. For example, from a transmission message sent by the network to all the UEs or a unicast message sent directly to the UE. The UE can then determine the latest version supported by both entities. Alternatively, the UE can send the version supported by the UE to the network. The network can then determine the latest version supported by both entities. In any case, the UE can transfer the capacity information according to the latest version supported by both entities. For example, the UE can transfer new capacity information using the design shown in Figure 3 or 4 for 3GGP version 7 or using other message flows for another 3GPP version. In general, new capacity information can include any information that is not transferable in existing information elements, for example, as defined in current 3GPP version 6. Different new capacity information may be associated with different elements of brand information of class. For example, the information element of MS Mark of Class 1 may carry information destined for a base station, the information element of MS Mark of Class 2 may carry information intended for the network (for example, an MSC), and the element of MS information Class 3 mark can carry information destined for the base station and / or network. The new capacity information destined for the base station can be sent in conjunction with the MS information element Class 1 or 3 mark. The new capacity information destined for the network can be sent in conjunction with the MS information element. Class 2 or 3 mark. The new capacity information sent in conjunction with the Class 2 Mark MS information element may include any or a combination of the following: New location capabilities supported by the UE; and • Extended support for privacy, for example, the EU's ability to display more information regarding a client that only has the location of the UE. The new capacity information sent in conjunction with the MS Brand information element of Class 1 or 3 may include the following: · Positioning methods supported by the EU; • Variations of positioning methods supported by the UE, for example, assisted by UE, based on UE, conventional and / or others; · Specific measurement capabilities supported by the UE, such as carrier phase measurements or bearer measurements or multiple frequency code, fine time attendance measurements, and / or others; and Specific options for each positioning method supported by the UE, such as assistance data elements supported by the UE, or support for various optional elements within the assistance data or other elements. The UE can support several positioning methods based on the Global Positioning System of the United States (GPS), the European Galileo System, and the Russian GLONASS System. For example, the UE can support UE-assisted GPS, UE-based GPS, stand-alone GPS, EU-assisted Galileo, UE-based Galileo, stand-alone Galileo, UE-assisted GLONASS, UE-based GLONASS, stand-alone GLONASS, etc. Capacity information can also transmit improvements, (for example, methods to provide long-term orbit data) to GPS-assisted positioning methods, assisted by Galileo, and assisted by GLONASS. The list of capabilities that the UE can transmit to the network can be large and can change over time. The UE can operate on GSM, GPRS, GERAN Iu, UMTS and / or other circuit and packet-based modes, as defined by 3GPP. The UE can send new information capacity to the network in different ways for different modes. The transmission of the new positioning capability information for different modes is described below. For GSM mode, the UE may send positioning capability information to a BSC in an MS information element Class 3 mark included in a RR Class Mark Change message. The BSC may resend the information element within a BSSMAP Class Mark Update message to an MSC. When the MSC later requests the location of the UE, the MSC may include the Class 3 MS Mark information element in a BSSMAP Execution Location Request message sent to the BSC. The BSC may then forward this information element in a BSSAP-LE Execution Location message to a Mobile In-Service Location Center (SMLC) that supports positioning for the UE. The UE may also include the Class 3 MS Mark information element in messages supporting the transfer from UMTS or GERAN Iu mode to the GMS mode. To allow the transfer of UMTS to GSM later, the UE may send the MS Class 3 mark information element to an RNC in a Radio Access Capability information element.

Inter-RAT UE included in a Complete RRC Connection Establishment message. To enable the transfer of the GERAN mode Iu to GSM later, the UE may send the MS information element Class 3 mark to a BSC in an information element of A / Gb Radio Access Capability GERAN MS included in a Complete RRC Connection Establishment message. The information element of MS Mark of Class 3 can then be transferred in different messages related to the transfer between the RNC and BSC when the transfer occurs later. A reservation bit in the MS information element Class 3 mark can be used as the new capacity or mark indicator to indicate additional positioning capabilities. The new capacity indicator can be transmitted to the RNC, BSC and MSC in a transparent way. A 5-bit MS positioning method capability field existing in the Class 3 MS Mark information element can be omitted in this case if the UE is aware that the network is a new network, which can help avoid the exclusion of other information from this information element (which may be necessary in order to comply with the 14-octet limitation for MS Class Mark 3 information element). A SMLC can receive the new capacity indicator from the UE (for example, when the BSC forwards the MS information element Class 3 mark to the SMLC as part of a location request) and can use the Radio Resource LCS Protocol signaling 3GPP (RRLP) to request new capacity information from the UE in a manner that is transparent to the BSC, SGSN and MSC. The SMLC may send to the UE a new RRLP message or an existing RRLP message (e.g., a RRLP Measuring Position Request message or an RRLP Support Data message) with a request for all positioning capabilities of the UE. The UE may then return its positioning capabilities in another new RRLP message or an existing RRLP message (e.g., a RRLP Measurement Response Response message). The returned capacity information may include existing capabilities if they have previously been excluded from the MS information element Class 3 mark. A pair of new messages may be added (eg, the SMLC request and the UE response) and / or the request / response may be carried within the new information element in existing RRLP messages. The transfer of the new capacity or brand indicator from the UE to the SMLC through one or more entities (for example, the BSC) and the Subsequent transfer of new capacity information from the UE to the SMLC using new or existing RRLP messages does not need to be visible to other entities (for example, the BSC or MSC) and therefore may not have new development impacts for them. In addition, the SMLC may transmit to the UE in the RRLP Request message its own positioning capability information and Quality of Service (QoS) information for the imminent position request, and the UE may indicate the SMLC in the RRLP Response message. any necessary positioning assistance data in addition to its positioning capabilities. Alternatively, the UE can transmit its new and existing positioning capabilities to the BSC and RNC using new information elements and possibly new messages. For example, an existing Class Mark Query Mask information element included in a Class Mark Query message sent from the BSC to the UE to request UE capabilities has two reserve bits. One of these reservation bits can be used to request a new Class Mark Change message from the UE. If the UE supports the new message, then the UE can send new capacity information in the new message to the BSC. When the location of the UE is requested, the BSC you can send the new capacity information to the SMLC either in an extension for an existing LCS capacity information element or a new information element included in a BSSAP-LE Execution Location message. For GPRS mode, the UE can send its positioning capabilities directly to an SGSN in a PS LCS Capability information element included in either a GPRS MM Attachment Request message or a GPRS Routing Area Update Request message MM. When the SGSN needs to request the location of the UE, the SGSN may include the PS LCS Capability information element in a BSSGP Execution Location Request message sent to the BSC. The BSC may transfer this information element within an LCS Capacity information element included in a BSSAP-LE Execution Location Request message sent to the SMLC. A reservation bit in the PS LCS Capacity information element can be used as the new capacity or mark indicator to indicate additional positioning capability information for the UE. The UE can then transfer the new capacity information to the SMLC directly and transparently to other network entities through an RRLP message exchange, as described above. previously for GSM mode. For the GERAN Iu mode, the UE can send its positioning capabilities to a BSC in an information element of Positioning Capability MS, which is part of a GERAN Iu Mode Radio Access Capability information element included in a Completion message RRC Connection Establishment. When the location of the UE is needed, the BSC can transfer the positioning capabilities of the UE to the SMLC by mapping the capacity indicators to those supported in an LCS Capacity information element included in a BSSAP-LE Execution Location Request message, for example, in the same way as for the GPRS mode. The UE may also send the MS Positioning Capability information element in a Complete RRC Connection Establishment message to an RNC for UMTS access. The UE may also send this information element in a GERAN Iu Mode Mark Change Mark message to a BSC for GSM access and to later support the transfer to a BSC supporting the GERAN Iu mode. A spare bit in the MS Positioning Capability information element can be used as the new capacity or mark indicator to indicate additional positioning capability information for the EU. The new capacity indicator may be transferred to the SMLC, transparently to other network entities, to allow the SMLC to obtain the additional positioning capability information from the UE using an RRLP message exchange, for example, as described for GSM and GPRS modes. Alternatively, a new information element may be added to the GERAN Iu Radio Access Capability information element included in a Complete RRC Connection Establishment message sent by the UE to the BSC during initial access and to other BSCs and RNCs during the transference. The content of the new information element may be transmitted to the SMLC in another new information element or in an extension of the existing LCS Capacity information element included in a BSSAP-LE Execution Location Request message. For UMTS mode, the UE may send its Positioning Capabilities to an RNC in an UE Positioning Capability information element contained in an EU Radio Access Capability information element included in a Complete RRC Connection Establishment message. When a SAS-centric positioning is used, the RNC can transfer the positioning capabilities UE to SAS in a UE Positioning Capability information element included in a PCAP Position Initiation Request message. The UE may also send its positioning capabilities to a BSC that supports GSM in a UTRAN Radio Access Capability information element of the UE included in a GSM UTRAN Class Mark Change message. The UE can also send its positioning capabilities to a BSC that supports the GERAN Iu mode in a Complete RRC Connection Establishment message. In both cases, the BSC can then transfer the positioning capabilities of the UE to an RNC in various messages related to transfer. The UE Positioning Capability information element does not have some reserve bit for new positioning capabilities because non-extensible ASN.l coding is used for this information element. New positioning capabilities can be added to the Complete RRC Connection Establishment message using a new parameter, for example, an ASN.l UE-Radio Access Capability-v7xyext parameter defined for 3GPP Version 7. A new capacity or brand flag can be added (for example, to parameter UE-Radio Access Capability-v7xyext) and can be transmitted first to the RNC, and then to the SAS in case SAS-centric positioning is used. For SAS-centric positioning, the SAS may request additional capacity information from the RNC, which in turn may request this information from the UE. For RNC-centric positioning, only the RNC can request additional capacity information from the UE. Alternatively, the UE can transmit its new positioning capabilities in a new information element to the RNC, which can then forward the information element to the SAS if required. The various messages for GSM, GPRS, GERAN Iu and UMTS modes are described in TS 24.008, TS 44.018 and other 3GPP documents. In the designs described above, the UE can receive an indication that the network supports the transfer of new capacity information, prior to sending this information to the network. These designs can avoid a scenario in which the UE sends the new capacity information to a legacy network that does not support the transfer of new capacity information, which may result in other problems as a result. For clarity, the techniques have been described specifically for the transfer of information from new capacity that is not transferable in class brand information elements used in GSM and UMTS networks. The techniques can also be used to transfer capacity information between the UEs and other networks, for example, CDMA networks, WLANs, local area networks (LAN), wired line data networks, the Internet, and so on. The techniques can also be used to transfer any type of information from one entity to another entity in a communications network. Figure 5 shows a design of a process 500 for transferring new capacity information. A first message having a first indicator set to indicate additional information for sending and not transferable in the first message, may be sent initially (block 512). A second indicator indicating the support of the transfer of additional information can be received (block 514). The additional information may then be sent in a second message in response to receipt of the second indicator (block 516). The process 500 can be executed by a UE. In this case, the UE may send the first indicator in the first message to a wireless network and may receive the second indicator from the network. The first message can be a CM Service Request message, a CM Re-Request Request message, a Location Update Request message, a Location Response message, a Class Mark Change message, an Attachment Request message, a Routing Area Update Request message, a Complete Connection Establishment message, and so on. The first indicator can be a reservation bit in an information element included in the first message, for example, an information element for the Mobile Station Brand of Class 1, 2 or 3. The second indicator can be transmitted by a third message received from the network to request the additional information, an indicator that indicates the support of the transfer of the additional information, and so on. The additional information may comprise new capacity information for location capabilities, positioning capabilities, notification capabilities, other capabilities for the UE, or a combination thereof. The process 500 can also be executed through a network entity, for example, to transmit network capacity information to the UE. The network entity may send the first message to the UE and may receive the second flag from the UE. The process 500 can also be executed through a network entity to initiate the transfer of new capacity information from the UE to another network entity, as discussed above. In general, the network may require sending the capacity and / or other information to the UE. Alternatively or additionally, the UE may require sending capacity and / or other information to the network. Existing information elements and / or messages used to transfer capacity and / or other information may not be expandable to include new information. In this case, a reservation or currently unused bit, an indicator, a value, or some other indication in an information element or a message can be used as the first indicator to indicate that the sending entity (for example, the UE or the network) has additional information to send to the receiving entity. The receiving entity, if it has the capacity to recognize this first indicator, can then send the second indicator back to the sending entity to request the transfer of the additional information. The second indicator can be sent in a new or existing information element included in a new or existing message. The sending entity can send the additional information in a new or existing information element included in a new or existing message.

Figure 6 shows a design of a process 600 executed by a UE to transfer new capacity information. The UE can receive from a wireless network an indication of the support of the transfer of additional non-transferable information in a first information element, for example, an information element for MS Mark of Class 1, 2 or 3 (block 612). The UE can receive this indication through a transmission message, a unicast message, and so on. The UE may then send the additional information in a second information element to the wireless network in response to reception of the indication (block 614). The UE can send a simple message with the second information element to the wireless network. In this case, the second information element may include information normally transmitted in the first information element, as well as the additional information. Alternatively, the UE may send a first message with the first information element and a second message with the second information element to the wireless network. In any case, the additional information may comprise new capacity information for the UE and may cover any of the capabilities listed above. Figure 7 shows a block diagram of the UE 150, a base station 710, and a network entity 720. The base station 710 may correspond to a BTS / BSC, a Node B / RNC, an access point, and so on. The network entity 720 may correspond to an MSC, an SGSN, a PDSN, a PDG, and so on. For simplicity, Figure 7 shows only a controller / processor 712, a memory 714, a transceiver 716, and a communication unit (Com) for the base station 710, only a controller / processor 722, a memory 724, and a unit communication 726 for the network entity 720, and only one controller / processor 752, a memory 754, and a transceiver 756 for the UE 150. In general, each entity may include any number of processors, controllers, memories, transceivers, units of communication, etc. The UE 150 can support communication with one or more wireless networks, for example, GSM, UMTS, CDMA, WLAN, and so on. The UE 150 can also receive and process signals from one or more satellite positioning systems, for example, GPS, Galileo, GLONASS, and so on. In the downlink, the base station 710 transmits traffic, signaling and possibly pilot data to the UEs within its coverage area. These various types of data are processed by the processor 712 and conditioned by the transceiver 716 to generate a downlink signal, which is transmitted through an antenna. At UE 150, downlink signals from one or more base stations are received through an antenna, conditioned by transceiver 756, and processed by processor 752 to obtain various types of information. The memories 714 and 754 store program and data codes for the base station 710 and the UE 150, respectively. The processor 752 may execute the actions for the UE in FIGS. 3 and 4 and may execute the process 500 in FIG. 5, the process 600 in FIG. 6 and / or other processes. In the uplink, UE 150 may transmit traffic, signaling and possibly pilot data to one or more base stations. These various types of data are processed by the processor 752 and conditioned by the transceiver 756 to generate an uplink signal, which is transmitted through the antenna UE. At the base station 710, the uplink signals from the UE 150 and other UEs are received and conditioned by the transceiver 716 and further processed by the processor 712 to obtain various types of information from the UEs. The base station 710 can establish communication with the network entity 720 through the communication unit 718. Within network entity 720, processor 722 executes processing for the techniques described above. For example, the processor 722 may execute the actions associated with the MSC in Figures 3 and 4. The memory 724 stores program and data codes for the network entity 720 and may also store UE capabilities. The communication unit 726 allows the network entity 720 to establish communication with the base station 710 and / or other network entities. The techniques described herein can be executed through various means. For example, these techniques can be executed in hardware, wired microprogram, software, or a combination thereof. For a hardware execution, the processing units used to execute the techniques may be performed within one or more specific application integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field-programmable gate arrays (FPGA), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, a computer, or a combination thereof.

For a wired microprogram execution and / or software, the techniques can be executed with modules (for example, procedures, functions, etc.) that execute the functions described here. The wired microprogramming instructions and / or software can be stored in a memory (for example, memory 714, 724 or 754 in Figure 7) and can be executed through a processor (for example, processor 712, 722 or 752) . The memory can be executed inside the processor or outside the processor. Wired microprogramming instructions and / or software may also be stored in another medium readable by the processor, such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), memory programmable read only (PROM), electrically erasable PROM (EEFROM), FLASH memory, compact disc (CD), optical or magnetic data storage device, and so on. An apparatus that executes the techniques described herein can be an autonomous unit or can be part of a device. The device can be (i) a stand-alone integrated circuit (IC), (ii) a set of one or more ICs that can include memory ICs for storing data and / or instructions, (iii) an ASIC such as a station modem Mobile (MSM), (iv) a module that can be incorporate within other devices, (v) a cell phone, wireless device, hearing aid, or mobile unit, (vi) and so on. The prior description of the invention is provided to enable any person skilled in the art to make or use the description. Various modifications to the description will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the description. Therefore, it is not intended that the description be limited to the examples described here but that you will be accorded the broadest scope consistent with the principles and novel features described herein.

Claims (26)

NOVELTY OF THE INVENTION Having described the present invention, it is considered as a novelty and, therefore, the content of the following is claimed as a priority: CLAIMS

1. - An apparatus comprising: a processor configured to send a first message having a first indicator set to indicate additional information to be sent and not transferable in the first message, to receive a second indicator indicating the support of transfer of the additional information, and to send the additional information in a second message in response to the reception of the second indicator; and a memory coupled to the processor.

2. The apparatus according to claim 1, characterized in that the first indicator is a reservation bit in an information element included in the first message.

3. The apparatus according to claim 1, characterized in that the first indicator is a reserve bit in an element of

Information for the Mobile Station Brand of Class 1, 2 or 3 included in the first message. . - The apparatus according to claim 1, characterized in that the processor is configured to receive a third message requesting additional information and providing service as the second indicator.

5. - The apparatus according to claim 1, characterized in that the processor is configured to receive an indicator indicating the support of transfer of additional information and serving as the second indicator.

6. - The apparatus according to claim 1, characterized in that the first message is a CM Service Request message, a CM Reset Request message, a Location Update Request message, a Location Response message, a Class Mark Change message, an Attachment Request message, a Routing Area Update Request message or a Complete Connection Establishment message.

7. - The apparatus according to claim 1, characterized in that the additional information comprises new capacity information for a user equipment (UE).

8. - The apparatus according to claim 1, characterized in that the additional information comprises information for location capabilities, positioning capabilities, notification capabilities, or a combination thereof, for a user equipment (UE).

9. - The apparatus according to claim 1, characterized in that the first message is sent to a wireless network and the second indicator is received from the wireless network.

10. - The apparatus according to claim 1, characterized in that the first message is sent to a user equipment (UE) and the second indicator is received from the UE.

11. An apparatus comprising: a processor configured to set a reservation bit in a Mobile Station Class Mark information element to indicate new capacity information to be sent and not transferable in the information element, to send the element of Classroom Mobile Station information in a first message to a wireless network, to receive an indication that the wireless network supports the transfer of new capacity information, and to send the new capacity information in a second message to

wireless network in response to receiving the indication; and a memory coupled to the processor.

12. - A method comprising: sending a first message having a first indicator set to indicate additional information to be sent and not transferable in the first message; receive a second indicator that indicates the transfer support of the additional information; and send the additional information in a second message in response to the reception of the second indicator.

13. - The method according to claim 12, characterized in that the reception of the second indicator comprises receiving a third message requesting the additional information and serving as the second indicator.

14. - The method according to claim 12, characterized in that the first indicator is a reservation bit in an information element for the Mobile Station Brand Class 1, 2 or 3 included in the first message.

15. - The method according to claim 12, characterized in that the additional information comprises information for capabilities of

location, positioning capabilities, notification capabilities, or a combination thereof, for a user equipment (UE).

16. An apparatus comprising: means for sending a first message having a first indicator set to indicate additional information to be sent and not transferable in the first message; means for receiving a second indicator indicating the support of the transfer of the additional information; and means for sending the additional information in a second message in response to receipt of the second indicator.

17. The apparatus according to claim 16, characterized in that the means for receiving the second indicator comprise means for receiving a third message requesting additional information and serving as the second indicator.

18. A processor-readable medium for storing instructions for: sending a first message having a first indicator set to indicate additional information to be sent and not transferable in the first message; receive a second indicator indicating the

support for the transfer of additional information; and send the additional information in a second message in response to the reception of the second indicator.

19. The processor-readable medium according to claim 19, characterized in that it also serves to store instructions for: receiving a third message requesting additional information and serving as the second indicator.

20. - An apparatus comprising: a processor configured to receive from a wireless network an indication of the support of transferring additional non-transferable information in a first information element, and to send the additional information in a second information element to the network wireless in response to reception of the indication; and a memory coupled to the processor.

21. - The apparatus according to claim 20, characterized in that the processor is configured to send a first message with the first information element to the wireless network, and to send a second message with the second element of information.

information to the wireless network.

22. - The apparatus according to claim 20, characterized in that the processor is configured to send a message with the second information element to the wireless network, the second information element includes information in the first information element and additional information .

23. - The apparatus according to claim 20, characterized in that the first information element is for the Mobile Station Brand Class 1, 2 or 3.

24. The apparatus according to claim 20, characterized in that the indication of the Additional information transfer support is received through a transmission message.

25. - The apparatus according to claim 20, characterized in that the indication of support for transfer of additional information is received through a unicast message.

26. The apparatus according to claim 20, characterized in that the additional information comprises new capacity information for a user equipment (UE). 27.- A method that includes: receiving from a wireless network a

indication of the support for the transfer of additional non-transferable information in a first information element; and sending the additional information in a second information element to the wireless network in response to receipt of the indication. 28. - The method according to claim 27, characterized in that sending the additional information comprises: sending a first message with the first information element to the wireless network, and sending a second message with the second information element to the wireless network. 29. - The method according to claim 27, characterized in that the sending of the additional information comprises sending a message with the second information element to the wireless network, the second information element includes information in the first information element and the Additional Information. 30. - An apparatus comprising: means for receiving from a wireless network an indication of the support of transferring additional non-transferable information in a first information element; Y

means for sending the additional information in a second information element to the wireless network in response to receipt of the indication. 31. - The apparatus according to claim 30, characterized in that the means for sending the additional information comprise: means for sending a first message with the first information element to the wireless network; and means for sending a second message with the second information element to the wireless network. 32. - The apparatus according to claim 30, characterized in that the means for sending the additional information comprise means for sending a message with the second information element to the wireless network, the second information element includes information in the first information element. information and additional information. 33. - A processor-readable medium for storing instructions for: receiving from a wireless network an indication of the support for transferring additional non-transferable information in a first information element; and send the additional information in a second information element to the wireless network in response

upon receipt of the indication. 34. - The processor-readable medium according to claim 33, further comprising storing instructions for: sending a first message with the first information element to the wireless network; and sending a second message with the second information element to the wireless network. 35. - The processor-readable medium according to claim 33, further comprising storing instructions for: sending a message with the second information element to the wireless network, the second information element includes information in the first information element and the additional information.