Method and system for character display in user equipment
By introducing additional signaling bits or language indicators between the user equipment and the network, the problem of user equipment not being able to correctly display network names while roaming, ensuring that the operator name is displayed in a user-understandable form, and handling special characters display error.
Patent Information
- Application Number
- CN202080074384.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-10-24
- Filing Date
- 2020-10-12
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-10-12
AI Technical Summary
User equipment may not be able to correctly display network names while roaming, especially in the case of language mismatch, resulting in users not being able to understand operator names, and the prior art has problems with handling non-roaming scenarios and special characters.
By introducing additional signaling bits or language indicators between the user device and the network, allowing the user device to select a supported character set and skip unsupported characters, or setting language preferences on the user device to determine how to display ambiguity characters, Make sure the network name is displayed in a user-understandable form.
It effectively solves the language matching problem of user equipment displaying network names in roaming and non-roaming scenarios, ensures that users can read the operator name correctly, and avoids display errors due to special characters.
Smart Images

Figure CN114902641B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to displaying characters on a user equipment (UE), and in one embodiment to displaying characters related to a network to which the user equipment is connected. Background Art
[0002] User equipment typically displays to the user the name of the network operator, also referred to as the "operator", corresponding to the cell in which the user is camped. If the user wishes to make a call or use data, this allows the user to know the name of the operator it will be using.
[0003] Specifically, when a UE is connected to a public land mobile network (PLMN), the PLMN typically provides network name information to the UE. The UE then typically displays the name of the network on which the UE resides on a display screen. This may be in idle mode or connected mode. One way in which network name information can be provided to the UE is called a network identity and time zone (NITZ) feature, which the network sends via a text string encoding for the network name. The encoding may be performed according to the Global System for Mobile Communications (GSM) default alphabet or according to the International Organization for Standardization / International Electrotechnical Commission (ISO / IEC) standard 10646, which specifies a universal character set (UCS).
[0004] Problems may arise when a user who uses a first language in one country roams to another country where a different language is used. The home / visited PLMN may provide the network name in a message to the device for display by the UE. However, if the language set by the user on the device is different from the language of the visited PLMN, the phone may display the network name to the user in a language that the user cannot understand, or may attempt to display the network name corresponding to certain characters that are not supported on that UE. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] The present disclosure will be better understood with reference to the accompanying drawings, in which:
[0006] Figure 1 is a block diagram of an example network architecture that can be used with the embodiments described herein;
[0007] Figure 2 is a data flow diagram illustrating network signaling including an extra bit to provide an indication for character skipping;
[0008] Figure 3 is a block diagram illustrating an example message having an additional bit for providing an indication for character skipping;
[0009] Figure 4 is a data flow diagram illustrating network signaling including providing a plurality of signaling fields having a language indicator;
[0010] Figure 5 yes Figure 4 A block diagram of signaling fields of a message of the type shown in FIG. 1 , providing the signaling fields and a language indicator for each signaling field;
[0011] Figure 6 is a block diagram illustrating an example information element having multiple signaling fields with a language discriminator;
[0012] Figure 7 is a data flow diagram illustrating signaling between a network element and a user equipment, wherein the user equipment provides a language indication to the network element;
[0013] Figure 8 is a block diagram illustrating example information elements used when a network element is aware of the language of a man-machine interface (MMI) of a user equipment;
[0014] Fig. 9 is a block diagram of an example user device that can be used with embodiments of the present disclosure; and
[0015] Fig.10 is a block diagram of simplified network elements that can be used with embodiments of the present disclosure. DETAILED DESCRIPTION
[0016] The present disclosure provides a method at a user device, the method comprising receiving an identified tag string at the user device, the string also comprising an indication bit; based on the indication bit, performing one of the following: determining whether the user device supports one or more tags in the tag string and skipping display of characters corresponding to unsupported tags; or displaying all tags in the tag string. In some other embodiments, a language profiler is used to select a tag string to be displayed or a language profiler is provided to a network element and a complete tag string received from the network element is used based on the provided language profiler.
[0017] As used herein, the term "user equipment" or "UE" may mean any mobile device, mobile station and may refer to mobile devices such as any mobile phone, personal digital assistant, handheld or laptop computer and similar devices with telecommunication capabilities, all of which may be used interchangeably. Such a UE may consist of a device and its associated removable memory module, such as but not limited to a universal integrated circuit card (UICC) including a subscriber identity module (SIM) application, a universal user identity module (USIM) application or a removable user identity module (R-UIM) application. Alternatively, such a UE may consist of the device itself without such a module.
[0018] As provided above, the UE may need to display characters such as the network name to the user. According to the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 22.101, "Service Aspects; Service Principles", v.17.0.0, September 2019, three network name display features are provided. These three display features, from highest to lowest priority, are:
[0019] a. The PLMN name stored in the USIM of the device associated with the PLMN identity, including the operator's mobile country code (MCC) and mobile network code (MNC);
[0020] b. PLMN name received in signaling from the network via the NITZ feature; and
[0021] c. The PLMN name stored in the Mobile Equipment (ME) and associated with the operator's PLMN identity.
[0022] In this way, a wireless network or radio access network can provide network information to a connected UE using one of a plurality of schemes. The network information can be displayed on the UE to provide information about the network to the user of the UE, such as the network name, country name, a graphic representing the network, and / or other relevant information.
[0023] Given the three options provided in the 3GPP TS 22.101 standard, if the UE supports more than one feature for displaying network information, the UE may use the feature with the highest priority and ignore the remaining features. Typically, USIM information has the highest priority, and therefore information may be obtained from the USIM first.
[0024] Information from the NITZ has the second highest priority and the UE may attempt to use this information if USIM information is not available.
[0025] The ME information has the third priority and therefore the UE may attempt to use this information if the other two features are not available or supported.
[0026] In some cases, such as when using the NITZ feature, the network may send network information to the UE that cannot be properly displayed on the UE. For example, the UE may be connected to a wireless network that sends a string of characters indicating the network name to the UE in a format that is not supported or cannot be properly displayed on the UE. Typically, in such a situation, the UE may display erroneous or garbled characters, such as jumbled characters, which do not provide useful information to the user of the UE.
[0027] In some other cases, when a user is roaming, information may be displayed to the user in a language that the user does not understand. For example, if a user from North America roams to China, displaying the operator name in Chinese characters may not provide the user with information about the operator if the user cannot read Chinese characters. Similarly, if a user from China roams to North America, displaying Latin characters on the user's device may not provide sufficient information to the Chinese user.
[0028] Various attempts have been made to address some of the above issues. In U.S. Patent No. 8,515,422, "Displaying Characters and Images Based On Support," dated August 20, 2013, the patent relates to skipping non-displayable tags. Specifically, if the characters in a network text string are "junk" characters, the patent teaches skipping these characters when displaying the operator text string.
[0029] In one case, the UE may receive characters in two different languages and not display or skip characters in the language that is not set on the UE. In this case, the solution uses the MMI configured on the UE to select the language to be displayed. The MMI is the menu that the user uses to control the device to set the device language.
[0030] Such a solution was further adopted into the 3GPP IS 22.101 specification. In particular, version 10 of the standard states:
[0031] For PLMN names provided by NITZ, operators using non-Latin characters in local languages (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) can include network names in Latin characters in addition to local language characters.
[0032] For the PLMN name provided by NITZ, a roaming UE shall skip displaying the non-Latin characters if the language for the non-Latin characters(s) does not match the language of the UE's MMI. If this would result in no Latin characters remaining in the PLMN name, the UE shall skip displaying the PLMN name provided by NITZ; the PLMN name stored in the ME has the next priority instead.
[0033] The above allows a user of a UE with an MMI using Latin characters to roam into China and see the network name displayed in Latin characters. The Chinese network operator would include both the Chinese and Latin network names in the message sent to the UE, and the UE would skip or not display the Chinese characters because in this case they would not match the English language in the MMI.
[0034] Another problem with displaying network names is character ambiguity. As used herein, the terms "ambiguity," "ambiguity," and the like may refer to a single character code that may be decoded to different characters in different languages. An ambiguous character is a character encoded by an ambiguous character code. An unambiguous character code is a character code that represents only a single character with a single code.
[0035] Because the GSM default alphabet does not allow encoding of certain languages as defined in 3GPP TS 23.038 "Alphabets and Language-Specific Information" (v.15.0.0, June 2018), another encoding scheme is reused for NITZ, as defined in ISO / IEC 10646. Although the following discussion focuses on ambiguities that may arise in the ISO / IEC 10646 standard, the present disclosure is not limited to this encoding scheme, and therefore, this encoding scheme should only be considered as an example and the embodiments described below may be applicable to other situations.
[0036] While the ISO / IEC 10646 encoding scheme does allow for encoding of characters from Asian languages, there is some ambiguity as to which Asian language characters are represented by a particular hexadecimal code.
[0037] In particular, reference is now made to Table 1 below.
[0038]
[0039] Table 1: Ambiguities in coded characters
[0040] In Table 1, the "X" symbol in the table indicates that the hexadecimal code in the corresponding row represents the symbol of the language in the corresponding column. As can be seen in Table 1, hexadecimal code 6811 can represent both simplified Chinese characters and traditional Chinese characters. Similarly, hexadecimal code 6812 can represent simplified Chinese characters, traditional Chinese characters, or Korean characters.
[0041] Hex code 688C can represent a simplified Chinese character, a traditional Chinese character, a Korean character, or a Vietnamese character. Similar examples exist in encoding sets.
[0042] Due to these ambiguities, the UE may sometimes be unable to determine the appropriate characters that should be used when a network name is provided to the UE, and the UE may display incorrect characters. For example, if the UE receives hexadecimal code 6812, the UE may display Chinese characters when it intended to display Korean characters, or vice versa.
[0043] The ambiguity of the encoded characters is based on the following languages: Chinese, Japanese, Korean, and Vietnamese ("CJKV"). A solution to this is provided in U.S. Patent No. 9,026,087, "Solving Character Display Ambiguities," dated May 5, 2015. The patent teaches parsing based on other information provided by the network, such as a mobile country code, a mobile network code, a routing area identity (RAI) or a location area identity (LAI), and other such information. For example, if MCC information is used, then Table 2 below shows an MCC to CJKV ideographic language mapping table, which represents Table 10.5.93a of 3GPP TS24.008, "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3," v.16.2.0, September 2019, standard. The same table also appears in 3GPP TS 24.301, “Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3,” v.16.2.0, September 2019, for Long Term Evolution (LTE) networks, and in 3GPP TS 24.501, “Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3,” v.16.2.0, September 2019, for fifth generation (5G) core networks.
[0044]
[0045]
[0046] Table 2: MCC to CJKV
[0047] However, even with these solutions, there are certain issues regarding character display. In particular, the current text in 3GPP TS22.101 forces the UE to display the network name in Latin in some cases. For example, a user roaming from Japan to China would display the network name in Latin characters on their UE. Specifically, in this case, the Chinese network operator has included the network name in both Latin characters and Chinese. However, the UE roaming from Japan to China would skip the Chinese characters based on the current standard and display the network name in Latin characters that the Japanese user might not understand.
[0048] A general solution to this would be to allow symmetric functionality similar to that previously introduced in 3GPP TS 22.101. As previously mentioned, the desired result is that a roaming UE will only display characters corresponding to the language type of the MMI. In this distinction, the distinction is between the Latin language type (which will be considered as a universal language) and all other non-Latin languages. By considering Latin languages as a language, a UE roaming from the UK to France will still display network names in French, for example, and if this results in no remaining alphabetic characters for the language type of the MMI, then the NITZ string is not used, but the ME display feature is used instead. In this case, a UE roaming from China to Japan would skip Japanese characters but would also skip Latin characters. Since there are no Japanese characters to display, the UE would skip using the NITZ string for display and would use the ME display feature instead. Such a ME display feature may include the use of Japanese characters.
[0049] In summary, if the UE roams from China to the United States, for example, the UE will skip the Latin characters. Since no other alphabetic characters will be displayed in NITZ, the UE will skip the NITZ display characters and use the ME information instead for display.
[0050] Another problem that may arise is with regard to non-roaming scenarios. If the operator in China sends the name in Chinese and Latin, the home user from that operator will display the network name in Chinese and Latin to the local user, because the skip solution that is currently standard in 3GPP TS 22.101 does not apply to non-roaming situations. One solution to this is to extend the skip characters to non-roaming UEs. In this way, the Chinese home user will only see the Chinese characters displayed for her home operator. This will also cater to the case where a user in one country has the language of the phone set to another language because the user's native language is different from the country where the user lives.
[0051] However, skipping characters can cause problems even if such characters do not form part of the native language character set. For example, in Korea, the name of an operator is "SKTelecom". This is written as "SK The name includes the letters "SK" which have no Korean character translation. Operators using mixed Latin / non-Latin characters (such as SK Telecom) may send network names such as "SK Telecom", followed by "SK Telecom" in Chinese. A UE roaming from a Latin country would correctly display "SK Telecom". A UE roaming from China would skip the Latin and Korean characters and correctly display the network name in Chinese. However, if the skipping idea is extended to non-roaming UEs, a local Korean UE would display " ", because it will skip the characters "SK" as they are considered Latin. This will look a bit strange to local users.
[0052] The same problem occurs for a UE roaming to Korea and having its language set to Korean.The above applies even if the downlink information from the network includes a field or information element (IE) for the language indicator.
[0053] In particular, if the character encoding allows encoding of speech for each character, the UE will skip those alphabetic characters instead of fields that are considered to be part of a different language. If the UE detects that some characters in a received field are from a language different from that of the UE's MMI, the UE may erroneously assume that the behavior related to the language of these characters applies.
[0054] For example, a UE with a Korean MMI may incorrectly skip the characters "SK" which are encoded in Latin characters within a field. ISO / IEC 10646 encoding is done in such a way that typically each character is encoded independently in its associated language. Using the code of the character or the code range of the character, the UE can, for example, assess that the character is actually Latin. The example of the SK Telecom problem above highlights the fact that a solution is often needed that will address requirements for mixed languages.
[0055] Furthermore, even if the "skip character" solution is removed from the 3GPP standard, additional solutions may still be needed to address the above issues. This is because user devices may be using a different language than the operator, both in the home network and when roaming, and will see network names displayed in a language that users of such devices may not understand.
[0056] Furthermore, the above solution works well under the assumption that what is indicated or displayed is the local name of the network. In other words, it is the home name in the local language that the user understands. However, in the case where the user is roaming or the user's language is different from the language of the local operator, then new problems arise and different solutions may be required.
[0057] Additionally, in some cases the UE may indicate a language preference to the network, which in turn will result in the NITZ message being sent in the language of the MMI for display by the UE. However, in this case, the mutual priority of this feature and the other three features described above is not defined with respect to displaying the network name and possibly also taking into account whether the UE is roaming.
[0058] Furthermore, the interplay between providing language preference and resolving CJKV ambiguity is currently undefined.
[0059] In addition, another problem is that for some Latin or non-Latin network names, these names may include some special characters, including space "", dash "-", or ampersand "&". According to ISO 10646 encoding, special characters are not actually regarded as Latin characters. Therefore, if the operator indicates, for example, "AT&T", a roaming UE from China to the United States will skip Latin characters, but will display the characters "&", "", "-", which may annoy the user.
[0060] Based on all these problems, the embodiments described below provide various solutions. In some embodiments, the solution is built on the skipping undesirable character solution. In some other embodiments, language indicators can be provided for various signaling fields, and the UE can display the characters corresponding to the signaling fields based on the MMI and skip the display of the characters embedded in other signaling fields. In a further embodiment, the UE can send an uplink message with an indication of the language of the MMI set by the user, and conversely receive a downlink message in the language of the MMI of the UE. In this example, the UE can use the language of the MMI to determine how to display ambiguous characters. Each of these embodiments is described in more detail below.
[0061] The above describes three sources of network names, namely USIM, NITZ and ME. Among them, USIM and ME are effectively provided by the user's home operator, making NITZ the only mechanism by which the access operator can provide information directly to the UE. In this regard, the following embodiments use the NITZ mechanism for network names. However, this is not meant to be limiting, and those skilled in the art will recognize that the various embodiments described herein can also be used with other signaling mechanisms and are therefore not limited to NITZ.
[0062] Example Architecture
[0063] Now to Figure 1 Reference is made to , which shows a simplified network diagram according to the present disclosure. Figure 1 In the example, user equipment 110 communicates with the network. Figure 1 In a simplified embodiment, the network includes a radio access network 120 (including but not limited to a base station, a Node B, an evolved Node B (eNB) or a next generation Node B (gNB)) and a core network 122, which includes a home subscriber server (HSS) / home location registry (HLR) or a visited location registry (VLR) 124, depending on whether the radio access network is a home network or a visited network of the UE 110.
[0064] If the radio access network 120 is a visited network, the UE 110 may attempt to connect to the visited network and authenticate with it. This is done by sending an identity (such as the UE's home network IMSI) through the VLR 124, which then communicates with the HSS / HLR 140 over the network using an interface such as the GLa interface and obtains the authentication information described above. Figure 1 The challenge and response are then used to authenticate the UE 110.
[0065] Otherwise, if network 120 is a home network, authentication and attachment are completed using HSS / HLR 124.
[0066] The data may then be routed from UE 110 through network 120 and core network 122 to Internet 150 (or to any other data network).
[0067] Signaling above skipping undesired characters
[0068] According to one embodiment of the present disclosure, as an exception to the 3GPP TS 22.101 requirement, information can be introduced in the signaling to indicate that character sets are prohibited from being skipped. This will allow users to avoid skipping some Latin characters that are naturally part of the network name when the MMI is non-Latin.
[0069] Therefore, Figure 2 For reference. Figure 2 In the embodiment of FIG. 4 , the network element 210 communicates with the UE 212 .
[0070] The network element may send signaling, shown with message 220, to UE 212. In this case, the signaling may be any signaling between the network element and the UE, and may include information elements, control signaling, and other signaling.
[0071] In some embodiments, the signaling in message 220 may include additional bits. Figure 3 , the message 310 includes conventional signaling bits 320 and additional bits 322. The additional bits 322 may mean in some cases:
[0072] 0-no information;
[0073] 1-Ignore Skips the requirements of 3GPP TS 22.101.
[0074] While the above is one example, other wordings are possible.
[0075] In this case, when the UE receives the signaling in message 220 or message 310, the UE can check the additional bit and base its behavior on this additional bit. In particular, if the additional bit indicates zero, the UE can implement the requirements of 3GPP TS 22.101 and ignore Latin characters. On the contrary, if the bit indicates one, the UE can combine non-Latin characters with Latin characters and display all of these characters.
[0076] In addition to or instead of Figure 2 and Figure 3 The meaning of the additional bits in the above examples comes from Figure 3 The additional bit 322 may mean:
[0077] 0-no information;
[0078] 1 - Skip character set(s) even if 3GPP TS 22.101 requires that the set be displayed.
[0079] The above alternative meanings for the bits can be used for symmetric problems so that, for example, it can be used when a Japanese mobile user roams into China.
[0080] Although the above Figure 2 and Figure 3 Various embodiments of the invention may be applied to any message displayed at the UE, but in some embodiments, the applicability of the information may be based on each display feature. For example, an embodiment may be applied to a NITZ display only in some cases.
[0081] In other words, the UE should consider one or more Latin characters as Korean characters if they are from another language based on the bits defined above. For example, in the SK telecom case above, the UE should consider Latin characters as Korean characters during the skip requirement process. This does not affect the fact that Latin characters (if displayed) are displayed in Latin. In other words, such Latin characters have no translation.
[0082] Therefore, the meaning of the information bits can be interpreted as:
[0083] 0 - No information
[0084] 1- Treat this character as Korean in "skip process".
[0085] In the above case, a bit of information may need to be associated with each character, and Figure 3 Embodiments of may be adapted to have multiple additional bits. Thus, a string may require a predetermined number of bits to convey a character and additional bits for each character to indicate how the character should be processed.
[0086] However, this alternative may require a large number of bits to encode all non-Latin languages. While this may be acceptable in some cases, in other cases, this increased number of bits may be problematic. In this case, another solution may be: the additional bits 322 may be:
[0087] 0-no information;
[0088] 1- Treat all Latin characters in this IE as the same language as the non-Latin language characters(s) included in this IE.
[0089] As will be apparent to those skilled in the art, the above is based on the first assumption that the network operator includes only characters from one non-Latin language in the IE. Therefore, instead of IE, other assumptions or granularities may be considered, such as using signaling fields. In one example, an ASN.1 field may be used.
[0090] Signaling bits such as those described above may be implemented in multiple downlink messages. Examples include: for 2G or 3G (3GPP TS 24.008): Mobility Management (MM) Information Message, General Packet Radio Service (GPRS) Mobility Management (GMM) Information Message, Temporary Mobile Subscriber Identity (TMSI) REALLOCATION COMMAND Message, IDENTITY REQUEST Message, LOCATION UPDATING ACCEPT Message, ATTACH ACCEPT Message. For Long Term Evolution / Enhanced Packet Core (LTE / EPC) (3GPP TS 24.301): Enhanced Packet Service (EPS) Mobility Management (EMM) Information Message, GUTIREALLOCATION COMMAND Message, AUTHENTICATION REQUEST Message, SECURITY MODE COMMAND Message, IDENTITY REQUEST Message, DETACH ACCEPT Message, DETACH REQUEST Message, TRACKING AREA UPDATE ACCEPT Message, TRACKING AREA UPDATE REJECT Message. For 5G core network (TS24.501): CONFIGURATION UPDATE COMMAND message, REGISTRATION ACCEPT message, DEREGISTRATION REQUEST message, REGISTRATION REJECT message, IDENTITY REQUEST message, AUTHENTICATION REQUEST message. Other messages may also be used.
[0091] In some other cases, a new downlink message may be created for the purpose of such signaling.
[0092] Furthermore, although the above embodiments are described with respect to a 3GPP system, according to the present disclosure, the embodiments are not limited to such a 3GPP system and may be reapplied to other systems, including but not limited to Wi-Fi, WiMAX, IEEE802.11, Hotspot 2.0, etc. Furthermore, even if the examples in the present disclosure provide a network name, the message need not be related to the network name.
[0093] In some other embodiments, the changes may be performed without signaling, for example, in one case the 3GPP TS 22.101 specification may be changed (as shown in bold) to:
[0094] "For PLMN names provided by NITZ, operators using non-Latin characters in local languages (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) may include Latin characters in addition to local language characters.
[0095] The network name of the symbol.
[0096] For the PLMN name provided by NITZ, if the language for the non-Latin character(s) does not match the language of the UE's MMI, the roaming UE SHOULD skip displaying the non-Latin characters. In doing so, if non-Latin character(s) are received, the UE SHOULD treat all Latin characters in the network name of the NITZ as being from the same language as the non-Latin character(s). If this would result in no Latin characters remaining in the PLMN name, the UE SHOULD skip displaying the PLMN name provided by NITZ; the PLMN name stored in the ME has next priority."
[0097] In an alternative embodiment, the 3GPP TS 22.101 specification may be changed to:
[0098] “For PLMN names provided by NITZ, operators using non-Latin characters in local languages (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) may include network names in Latin characters in addition to local language characters.
[0099] For the PLMN name provided by NITZ, if the language for the non-Latin character(s) does not match the language of the UE's MMI, the roaming UE SHOULD skip displaying the non-Latin characters. In doing so, if non-Latin character(s) are received, the UE SHOULD treat all Latin characters sent in the same information element as the non-Latin character(s) as being from the same language as the non-Latin character(s). If this would result in no Latin characters remaining in the PLMN name, the UE SHOULD skip displaying the PLMN name provided by NITZ; the PLMN name stored in the ME has next priority."
[0100] According to the above changes shown in bold, all Latin characters in a NITZ network name or information element will be treated as the same language as the rest of the characters.
[0101] In addition to the above, one problem may be that some network names, whether in Latin or non-Latin, may include special characters such as space "", dash "-" or ampersand "&". According to ISO 10646 encoding, special characters are not actually considered Latin characters. Therefore, if the operator indicates, for example, "AT&T", the above requirements will result in the display of the characters "&", "", or "-" in the case where the UE roams from China to the United States, because the phone will skip the Latin characters, but such special characters will still be displayed. Such a result may be annoying to the user. Therefore, 3GPP IS 22.101 can be modified as follows:
[0102] "For the PLMN name provided by NITZ, a roaming UE SHOULD skip displaying the non-Latin characters if the language for the non-Latin characters(s) does not match the language of the UE's MMI. In doing so, any non-alphabetic characters received between characters(s) of the same language SHOULD be treated as characters(s) from that language. If this would result in no Latin characters remaining in the PLMN name, the UE SHOULD skip displaying the PLMN name provided by NITZ; the PLMN name stored in the ME has the next priority."
[0103] In addition, instead of 3GPP IS 22.101, requirements can be added to other technical standards, such as 3GPP TS24.008. For example, new requirements can be introduced in message encoding or IE encoding. The new requirements can be read in another language example as:
[0104] "All characters (even non-alphabetic characters) in this IE are treated as Korean alphabet characters"
[0105] Another example assumes that a language discriminator is added to 3GPP TS 24.008 signaling. For example, the language discriminator can be applied to each new IE in the MM / GMM information message, or to a new downlink message that is introduced. Then the new requirement added to 3GPP TS 24.008 can be rewritten as:
[0106] "All characters in this IE (even non-alphabetic characters or characters from a different language) are treated as alphabetic characters from the same language rather than as language discriminators"
[0107] Other wording or example solutions are possible.
[0108] The above will therefore solve both the aforementioned non-language character skipping problem and the aforementioned Latin / Korean problem.
[0109] Provides language indicator to signaling fields
[0110] In a further embodiment, the network element may send different signaling fields to the UE. Figure 4 For reference, a network element 410 is in communication with a UE 412. Figure 4 In the example of , message 420 provides one or more signaling fields, each of which is identified by a language indicator. The UE may select a signaling field corresponding to a language indicator corresponding to a language set in the MMI of the UE.
[0111] Specifically, Figure 5 For reference, a plurality of signaling fields 510 are shown, each with its own language indicator 512. The UE may then display the characters corresponding to the signaling field corresponding to the device's MMI and skip display of characters embedded in other signal fields.
[0112] Therefore, according to Figure 4 and Figure 5 In an embodiment, a selection is performed between characters received in different signaling fields, but all characters in the signaling field will be displayed on the UE. This includes characters containing character encodings reflecting other languages or non-alphabetic characters. If there is no signaling field corresponding to the language of the MMI by using a language indicator corresponding to each signaling field, the UE does not use the corresponding display feature and uses the next one in the priority list.
[0113] In one specific example, the UE may utilize a new feature, referred to herein as "NITZ2" or "Network Name 2." If the language indicator selected for such a field includes the language of the UE's MMI, then the network name from that field may be used for display.
[0114] Conversely, if no such field is present, the UE shall not use the feature but shall use the ME Display feature according to the priority list.
[0115] The NITZ2 display feature may be located at a different priority point in the priority of display features used by the device. In one embodiment, the new display feature may be located between the USIM and ME displays, as is currently the case for NITZ, but before the current NITZ. In other words, the display features from highest priority to lowest priority may be:
[0116] 1. USIM network name display;
[0117] 2. New display features such as NITZ2;
[0118] 3. NITZ network name display;
[0119] 4.ME network name is displayed.
[0120] However, other priorities are possible. For example, in one alternative, when the UE is not roaming, NITZ may have a higher priority than the new display feature. Conversely, when the UE is roaming, NITZ2 may have a higher priority than NITZ. In another alternative, when the UE is not roaming, NITZ may have a lower priority than the new display feature; when the UE is roaming, NITZ2 may have a lower priority than NITZ.
[0121] Furthermore, in some cases, new display features may only be used when the user is roaming.
[0122] In some other cases, the priority of the new display feature can be selected by the user and / or signaled by the network. If both the user and the network can choose, the user selection can take precedence over the network selection, and vice versa.
[0123] If the network is selecting, then in one example, the network may provide a two-bit field parameter to the UE. This field may take a decimal value of 1 to 4, indicating the relative priority of the NITZ2 feature compared to other priorities. For example, "1" may indicate that the NITZ2 feature will have the highest priority above the USIM. "2" would mean that the priority would fall between the USIM and NITZ. "3" would mean that the priority would fall between NITZ and ME. "4" would indicate the lowest priority below ME.
[0124] exist Figure 4 and Figure 5In the embodiments of the present invention, the term "signaling field" is used as a general term. Such a signaling field can be, for example, an information element within a message, or a field within an information element within a message. In other words, one information element can include more than one signaling field.
[0125] Furthermore, in some cases, this field may be an ASN.1 field or a CSN.1 field within the message.
[0126] In some cases, the information may be provided to the device via a L3 signaling solution such as 3GPP TS 24.008, 3GPP TS 24.301, or 3GPP TS 24.501.
[0127] In some other cases, the information may be provided to the UE / USIM via an Open Mobile Alliance (OMA) Device Management (DM) or SIM Toolkit application.
[0128] Thus, based on the above, embodiments may be used between two signaling fields provided by two different display features. For example, this may be applicable between a network name provided by NITZ and one or more network names provided by a new display feature such as NITZ2. In one example, the UE will display the network name from NITZ2 instead of the network name from NITZ, because the network name from NITZ2 is in the language of the MMI, while the network name from the already existing NITZ may not be in the language of the MMI.
[0129] In another example, the selection of whether to use NITZ or NITZ2 can be a condition. Specifically, if the new display feature contains the network name in the language of the MMI, the new display feature may take precedence over NITZ. Otherwise, NITZ will take precedence over NITZ2. In another example, if the new display feature contains the network name in the language of the MMI, the new display feature may take precedence over other display features, such as USIM features.
[0130] In another example, if NITZ2 does not include the network name for the language of the MMI, then NITZ2 is completely skipped or not used in all display features.
[0131] In yet another embodiment, NITZ2 priority is affected among already existing display features, depending on whether NITZ2 contains a network name in the language of the MMI.
[0132] Furthermore, in some cases the concept of whether the UE is roaming or not may be added, thereby affecting the overall priority of new display features and potentially affecting the priority of existing NITZs.
[0133] Furthermore, regarding the “CJKV ambiguity”, in one embodiment, the UE uses the language indicated by the language indicator and which should correspond to the language of the MMI, since only the corresponding network name is associated with NITZ2. Thus, the ambiguity is resolved.
[0134] The above can be implemented in various signaling solutions. Various change requests can be made in the standard. For example, the message can be but is not limited to: for 2G or 3G (3GPP TS 24.008): Mobility Management (MM) Information Message, General Packet Radio Service (GPRS) Mobility Management (GMM) Information Message, Temporary Mobile Subscriber Identity (TMSI) REALLOCATION COMMAND Message, IDENTITY REQUEST Message, LOCATION UPDATING ACCEPT Message, ATTACH ACCEPT Message. For Long Term Evolution / Enhanced Packet Core (LTE / EPC) (3GPP TS 24.301): Enhanced Packet Service (EPS) Mobility Management (EMM) Information Message, GUTI REALLOCATION COMMAND Message, AUTHENTICATION REQUEST Message, SECURITY MODE COMMAND Message, IDENTITY REQUEST Message, DETACH ACCEPT Message, DETACHREQUEST Message, TRACKING AREA UPDATE ACCEPT Message, TRACKING AREA UPDATE REJECT Message. For 5G core network (TS 24.501): CONFIGURATION UPDATE COMMAND message, REGISTRATION ACCEPT message, DEREGISTRATION REQUEST message, REGISTRATION REJECT message, IDENTITY REQUEST message, AUTHENTICATION REQUEST message. Other messages may also be used.
[0135] In some other cases, a new downlink message may be created for the purpose of such signaling.
[0136] Furthermore, although the above embodiments are described with respect to a 3GPP system, according to the present disclosure, the embodiments are not limited to such a 3GPP system and may be reapplied to other systems, including but not limited to Wi-Fi, WiMAX, IEEE802.11, Hotspot 2.0, etc. Furthermore, even if the examples in the present disclosure provide a network name, the message need not be related to the network name.
[0137] An example of changes that may be made to 3GPP TS 24.008 is shown in the following Appendix A with respect to the bolded portion. Those skilled in the art should note that such changes will also cover LTE and 5G, since the information elements in LTE and 5G, i.e., 3GPP TS 24.301 and 3GPP TS 24.501, will also point to the information elements defined in 3GPP TS 24.008.
[0138] The bold items can be added as shown in the example in Appendix A. That is, the full network name for network2 and the abbreviated network name for network2.
[0139] As further seen in Appendix A, full network names and abbreviated network names are defined, as well as a definition of which network name to use based on the language discriminator 2.
[0140] In the changes to Appendix A, new information elements are provided, such as Figure 6 as shown in .
[0141] Additionally, changes may be made to 3GPP TS 24.301 as shown below in Appendix B. As seen in Appendix B, new additions to the standard are shown in bold and are similar to those described above.
[0142] Additionally, changes may be made to 3GPP TS 24.501, which are shown in bold below in Annex C. Such changes are similar to those described above with respect to Annex A or Annex B.
[0143] Additionally, changes to 3GPP TS 22.101 for country / PLMN indications are shown below with respect to Appendix D. In particular, the changes are shown in bold and introduce NITZ2.
[0144] The UE indicates the language of the MMI to the network
[0145] In another embodiment of the present disclosure, the UE may send an uplink message to the network to provide an indication of the language of the MMI, which language is set or has been set by the user on the UE. This is done to address the problem of language misunderstanding. In turn, a downlink message may be provided to the UE, wherein the UE receives a text string for the UE to display in the language of the UE's MMI.
[0146] Furthermore, the embodiments described below provide additional features to this concept.
[0147] In the current case, if the UE receives a message including a text string containing one or more ambiguous characters, the UE can use the language of the MMI to determine how to display the ambiguous characters. This is different from existing solutions in which the UE uses the language of the country where the MCC is located received from the network in the PLMN ID.
[0148] In particular, now Figure 7 For reference. Figure 7 In the embodiment of FIG. , the network element 710 communicates with the UE 712.
[0149] exist Figure 7 In the case of a language of the MMI of such UE, the UE 712 provides a message 720 indicating the language of the MMI of such UE. In response, the signaling in the message 730 includes information of the language of the MMI.
[0150] If the message 730 includes ambiguous characters, the UE 712 uses the language of the MMI to determine how to display the ambiguous characters, as shown at block 740 .
[0151] The feature priority of the information in message 730 can be processed similarly to the above. In particular, the feature priority can be set anywhere between the existing three priority levels and can be set by the user or the network. If the priority is set by the network, the priority can be based on a two-bit field provided by the network to indicate where the priority should be.
[0152] In some other cases, the priority may be predetermined or may be set based on whether the UE is roaming.
[0153] Other examples will be apparent to those skilled in the art based on this disclosure.
[0154] In addition, the solution of the embodiment above skipping characters in the first embodiment described above can be implemented in this embodiment. In the case of this embodiment, the wording may be slightly different in various standards. For example, a new requirement can be added to 3GPP TS24.008, which can be rewritten as follows:
[0155] "Treat all characters in this IE (even non-alphabetic characters or characters from a different language) as alphabetic characters of the language from the MMI"
[0156] Other wording or example solutions are possible.
[0157] To resolve "CJKV ambiguity", for the relevant ambiguous characters, in one example embodiment, the UE may use the language of the UE's MMI, which should correspond to the language used by the network for the network name field.
[0158] The above can be achieved through various changes. For example, Appendix E shows in bold an example change to the 3GPP TS 22.101 specification that includes character skipping. In this example, PLNNs provided by NITZ2 should be displayed in full, even if such names include non-alphabetic characters or characters encoded in a language different from the MMI.
[0159] With respect to Appendix F below, another example is provided in bold. In this example, the character skipping previously introduced into the 3GPP TS 22.101 specification in 2019 has been removed. Instead, NITZ2 is indicated to take precedence over NITZ, and all characters provided should be considered to be in the language of the indicated MMI.
[0160] Furthermore, in this embodiment, the changes to 3GPP TS 24.301 may be the same as those provided in Appendix B.
[0161] Similarly, in this embodiment, the changes to 3GPP TS 24.501 may be the same as those provided in Appendix C.
[0162] 3GPP TS 24.008 may be modified to include the network name 2, as shown in bold in Appendix G below. In this modification, a new information element is provided, as disclosed in the present disclosure Figure 8 as shown in .
[0163] The above thus provides for displaying characters in a language appropriate to the user of the user device.
[0164] Any user device can be used to implement the above. Fig. 9 An example user device is shown.
[0165] UE 900 may be a two-way wireless communication device with voice and data communication capabilities. Depending on the specific functionality provided, a UE may be referred to as, for example, a data messaging device, a two-way pager, a wireless email device, a cellular phone with data messaging capabilities, a wireless Internet device, a wireless device, a mobile device or a data communication device, an Internet of Things endpoint.
[0166] In the case of enabling UE 900 to perform two-way communication, it can incorporate a communication subsystem 911, which includes a receiver 912 and a transmitter 914, as well as associated components such as one or more antenna elements 916 and 918, a local oscillator (LO) 913, and a processing module such as a digital signal processor (DSP) 920. Although not shown, the communication subsystem 911 may include additional components. For example, the UE 900 may include multiple receivers 912 and / or transmitters 914 to allow simultaneous radio activities. In addition, it will be apparent to those skilled in the art of communications that the specific design of the communication subsystem 911 will depend on the communication network in which the device is intended to operate.
[0167] The network access requirements will also vary depending on the type of network 919. In some networks, network access is associated with a subscriber or user of the UE 900. The UE may require one or more smart cards, such as a UICC, to operate on the network. The smart card interface 944 is typically similar to a card slot into which a smart card can be inserted and ejected. The smart card may have a memory and store a number of key configurations 951 and other information 953, such as identification and subscriber related information.
[0168] When the required network registration or activation procedures have been completed, UE 900 may send and receive communication signals over network 919. Fig. 9 As illustrated in FIG. 9 , the network 919 may be comprised of multiple base stations that communicate with the UE.
[0169] The signal received by the antenna 916 through the communication network 919 is input to the receiver 912, which can perform common receiver functions such as signal amplification, down conversion, filtering, channel selection, etc. The A / D conversion of the received signal allows more complex communication functions such as demodulation and decoding to be performed in the DSP 920. In a similar manner, the signal to be transmitted is processed by the DSP 920, for example, including modulation and encoding, and then input to the transmitter 914 for digital-to-analog conversion, up conversion, filtering, amplification and transmission through the communication network 919 via the antenna 918. The DSP 920 not only processes the communication signal, but also provides receiver and transmitter control. For example, the gain of the communication signal applied to the receiver 912 and the transmitter 914 can be adaptively controlled by the automatic gain control algorithm implemented in the DSP 920.
[0170] UE 900 typically includes a processor 938 that controls the overall operation of the device. Communication functions, including data and voice communications, are performed through the communication subsystem 911. The processor 938 also interacts with other device subsystems, such as a display 922, a flash memory 924, a random access memory (RAM) 926, an auxiliary input / output (I / O) subsystem 928, a serial port 930, one or more keyboards or keypads 932, a speaker 934, a microphone 936, other communication subsystems 940 such as a short-range communication subsystem, and any other device subsystems generally designated as 942. The serial port 930 may include a USB port or other ports known to those skilled in the art.
[0171] Fig. 9 Some of the subsystems shown in the figure perform communication-related functions, while other subsystems may provide "resident" or on-device functions. It is noteworthy that some subsystems, such as keyboard 932 and display 922, for example, may be used for communication-related functions, such as entering a text message for transmission over a communication network, and for device-resident functions, such as a calculator or a task list.
[0172] Operating system software used by the processor 938 may be stored in a persistent repository such as the flash memory 924, which may alternatively be a read-only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or portions thereof, may be temporarily loaded into a volatile memory such as the RAM 926. Received communication signals may also be stored in the RAM 926.
[0173] As shown, the flash memory 924 can be divided into different areas for computer programs 958 and program data storage 950, 952, 954 and 956. These different storage types indicate that each program can allocate a portion of the flash memory 924 for its own data storage requirements. The processor 938, in addition to its operating system functions, can also implement the execution of software applications on the UE. A set of predetermined applications that control basic operations, such as at least data and voice communication applications, will usually be installed on the UE 900 during manufacturing. Other applications can be installed subsequently or dynamically.
[0174] The application and software may be stored on any computer-readable storage medium. The computer-readable storage medium may be a tangible or transient / non-transient medium, such as an optical storage (e.g., CD, DVD, etc.), a magnetic storage (e.g., a tape), or other storage known in the art.
[0175] In the data communication mode, received signals such as text messages or web page downloads will be processed by the communication subsystem 911 and input to the processor 938, which can further process the received signals for output to the display 922, or alternatively to the auxiliary I / O device 928.
[0176] In conjunction with the display 922 and possible auxiliary I / O devices 928, the user of the UE 900 can also compose data items such as email messages, for example using the keyboard 932, which can be a full alphanumeric keyboard or a telephone-type keypad, etc. In some other cases, the keyboard 932 can be a virtual keyboard on the display 922. Such composed items can then be transmitted over the communication network through the communication subsystem 911.
[0177] For voice communications, the overall operation of the UE 900 is similar, except that received signals will typically be output to the speaker 934 and signals for transmission will be generated by the microphone 936. Alternative voice or audio I / O subsystems, such as a voice message recording subsystem, may also be implemented on the UE 900. Although voice or audio signal output is typically accomplished primarily through the speaker 934, the display 922 may also be used to provide an indication of the identity of the calling party, the duration of the voice call, or other voice call related information.
[0178] Fig. 9 The serial port 930 in the UE 900 can be used for a variety of purposes, including synchronization with a user's desktop computer (not shown), enabling the user to set preferences through an external device or software application, and extending the capabilities of the UE 900 by providing information or software downloads to the UE 900 rather than through a wireless communication network. For example, an alternative download path can be used to load encryption keys onto the device through a direct and therefore reliable and trusted connection, thereby enabling secure device communications. As will be appreciated by those skilled in the art, the serial port 930 can also be used to connect the UE to a computer to act as a modem, or can be used to charge the device.
[0179] Other communication subsystems 940, such as a short-range communication subsystem, are additional optional components that can provide communication between UE 900 and different systems or devices, which are not necessarily similar devices. For example, subsystem 940 may include an infrared device and associated circuits and components or a Bluetooth TM Communications modules to provide communications with similarly enabled systems and devices. Subsystem 940 may also include non-cellular communications, such as WiFi or WiMAX.
[0180] In addition, the network elements mentioned and shown in this article may be any network element or a part of any network element, including various network servers. Fig.10 For reference, a general example network element is shown.
[0181] exist Fig.10 In the embodiment, the network element 1010 includes a processor 1020 and a communication subsystem 1030, wherein the processor 1020 and the communication subsystem 1030 cooperate to execute the method of the above embodiment.
[0182] Processor 1020 is configured to execute programmable logic that may be stored on network element 1010 along with data and Fig.10 In the example of FIG. 1040 , the memory 1040 is shown as a memory 1040. The memory 1040 can be any tangible storage medium.
[0183] Alternatively or in addition to memory 1040 , network element 1010 may also access data or programmable logic from an external storage medium, such as through communication subsystem 1030 .
[0184] Communications subsystem 1030 allows network element 1010 to communicate with other network elements.
[0185] In one embodiment, communications between the various elements of network element 1010 may be through internal bus 1050. However, other forms of communications are possible.
[0186] The structure, features, accessories, and alternatives of the specific embodiments described herein and shown in the drawings are intended to be generally applicable to all teachings of the present disclosure, including all embodiments described herein and illustrated, as long as they are compatible. In other words, unless so indicated, the structure, features, accessories, and alternatives of a specific embodiment are not intended to be limited to only that specific embodiment.
[0187] Furthermore, those skilled in the art will appreciate additional features and advantages of the present disclosure.
[0188] The embodiments described herein are examples of structures, systems or methods with elements corresponding to the elements of the technology of the present application. This written description can enable those skilled in the art to make and use embodiments with alternative elements corresponding to the elements of the technology of the present application. Therefore, the intended scope of the technology of the present application includes other structures, systems or methods that are not different from the technology of the present application as described herein, and also includes other structures, systems or methods that are not essentially different from the technology of the present application as described herein.
[0189] Appendix A - Examples of changes to 3GPP TS 24.008
[0190] 9.2.15a MM Information
[0191] This message is sent by the network to the mobile station to provide the mobile station with subscriber specific information. See Table 9.2.18 / 3GPP TS 24.008.
[0192] Message type: MM INFORMATION
[0193] Meaning: Dual
[0194] Direction: Network to mobile station
[0195] Table 9.2.18 / 3GPP TS 24.008 MM INFORMATION message content
[0196]
[0197] 9.2.15a.1 Full name of the network
[0198] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the "full name of the network" that the network wishes the mobile station to associate with the MCC and MNC contained in the location area identifier of the cell to which the mobile station sends its channel request message.
[0199] 9.2.15a.2 Abbreviated name of the network
[0200] This IE may be sent by the network. If sent, the content of this IE indicates the "abbreviated name of the network" that the network wishes the mobile station to associate with the MCC and MNC contained in the location area identifier of the cell to which the mobile station sends its channel request message.
[0201] 9.2.15a.3 Local Time Zone
[0202] This IE may be sent by the network. The mobile station should assume that this time zone applies to the location area of the cell to which the Channel Request message is sent.
[0203] If the local time zone has been adjusted for daylight saving time, the network should indicate this by including IE Network Daylight Saving Time.
[0204] 9.2.15a.4 Universal Time and Local Time Zone
[0205] This IE may be sent by the network. The mobile station should assume that this time zone applies to the location area of the cell to which the channel request message is sent. The mobile station should not assume that the time information is accurate.
[0206] If the local time zone has been adjusted for daylight saving time, the network should indicate this by including IE Network Daylight Saving Time.
[0207] 9.2.15a.5 LSA Identity
[0208] This IE may be sent by the network. The content of this IE indicates the LSA identity of the serving cell.
[0209] 9.2.15a.6 Network Daylight Saving Time
[0210] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the value that has been used to adjust the local time zone.
[0211] 9.2.15a.7 Full name of the network 2
[0212] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the "full name of the network" that the network wishes the mobile station to associate with the MCC and MNC contained in the location area identifier of the cell to which the mobile station sends its channel request message.
[0213] 9.2.15a.8 Abbreviated name of network 2
[0214] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the "abbreviated name of the network" that the network wishes the mobile station to associate with the MCC and MNC contained in the location area identifier of the cell to which the mobile station sends its channel request message. (...)
[0216] abcd network name 2
[0217] The purpose of this information element is to convey a text string to the mobile station in addition to the text string provided in the information element Network Name.
[0218] The encoding of the Network Name 2 information element is shown in Figure x1.y1.z1 / 3GPP TS 24.008 and Table x2.y2.z2 / 3GPP TS 24.008.
[0219] For the purposes of the network name display requirements specified in Annex A.3 of 3GPP TS 22.101 [8], the MS shall treat all characters associated with a language discriminator (even non-language characters or characters with encodings indicating a different language) as alphabetic characters from the language of the language discriminator.
[0220] If encoding scheme UCS2 is used and Chinese-Japanese-Korean-Vietnamese (CJKV) ideographs as defined in ISO / IEC 10646
[72] are received in a text string, the MS shall use [Alt1: corresponding language indicator][Alt2: language of the MMI] to determine the language used for those CJKV ideographs.
[0221] NOTE: This is due to the language ambiguity of CJKV ideographs in UCS2, i.e. the same hex code can be mapped to different character displays, depending on the language being used. The encoding of CJKV ideographs does not itself allow identification of the CJKV ideograph language.
[0222] Network Name 2 is a Type 4 information element with a minimum length of 3 octets. Apart from the length limit given by the maximum number of octets in an L3 message (see 3GPP TS 44.006
[19] ), no upper limit on the length is specified.
[0223] Figure x1.y1.z1 / 3GPP TS 24.008 Network Name 2 Information Element - For this figure, see Figure 6 .
[0224] Table x2.y2.z2 / 3GPP TS 24.008 Network Name 2 Information Elements
[0225]
[0226]
[0227] Appendix B - Examples of changes to 3GPP TS 24.301
[0228] 8.2.13 EMM Information
[0229] 8.2.13.1 Message definition
[0230] This message is sent by the network at any time during EMM context establishment to send certain information to the UE. See Table 8.2.13.1.
[0231] Message type: EMM message
[0232] Meaning: Local
[0233] Direction: Network to UE
[0234] Table 8.2.13.1: EMM information message content
[0235] IEI Information Elements Type / Reference exist Format length Protocol Discriminator Protocol Discriminator 9.2 M V 1 / 2 Security Header Type Security Header Type 9.3.1 M V 1 / 2 EMM Information Message Type Message Type 9.8 M V 1 43 The full name of the network Network Name 9.9.3.24 O TLV 3-n 45 Abbreviated name of the network Network Name 9.9.3.24 O TLV 3-n 46 Local time zone Time zone 9.9.3.29 O TLV 2 47 Universal Time and Local Time Zone Time Zone and Time 9.9.3.30 O TLV 8 49 Internet Daylight Saving Time Daylight Saving Time 9.9.3.6 O TLV 3 tbd Full name of the network2 Network Name 2A3.b3.c3.d O TLV 3-n tbd Abbreviated name of the network2 Network Name 2A3.b3.c3.d O TLV 3-n
[0236] 8.2.13.2 Full name of the network
[0237] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the "full name of the network" that the network wants the UE to associate with the MCC and MNC contained in the last visited tracking area identity.
[0238] 8.2.13.3 Abbreviated name of the network
[0239] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the "abbreviated name of the network" that the network wishes the UE to associate with the MCC and MNC contained in the last visited tracking area identity.
[0240] 8.2.13.4 Local Time Zone
[0241] This IE may be sent by the network. The UE shall assume that this time zone applies to the tracking area of the current cell and also to the tracking area list if available in the UE.
[0242] Note: The time information may not be accurate, especially when the TAI list includes tracking areas belonging to different time zones.
[0243] If the local time zone has been adjusted for daylight saving time, the network SHOULD indicate this by including a Network Daylight Saving Time IE.
[0244] 8.2.13.5 Universal Time and Local Time Zone
[0245] This IE may be sent by the network. The UE shall assume that this time zone applies to the tracking area the UE is currently in and to the tracking area list if available in the UE. The UE shall not assume that the time information is accurate.
[0246] Note: The time information may not be accurate, especially when the TAI list includes tracking areas belonging to different time zones.
[0247] If the local time zone has been adjusted for daylight saving time, the network SHOULD indicate this by including a Network Daylight Saving Time IE.
[0248] 8.2.13.6 Network Daylight Saving Time
[0249] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the value that has been used to adjust the local time zone.
[0250] 8.2.13.7 Full name of the network 2
[0251] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the "full name of the network" that the network wants the UE to associate with the MCC and MNC contained in the last visited tracking area identity.
[0252] 8.2.13.8 Abbreviated name of network 2
[0253] This IE may be sent by the network. If this IE is sent, the content of this IE indicates the "abbreviated name of the network" that the network wishes the UE to associate with the MCC and MNC contained in the last visited tracking area identity.
[0254] (……)
[0255] 9.9.3.24 Network Name 2
[0256] See subclauses abcd in 3GPP TS 24.008
[13] .
[0257] Appendix C - Example changes to 3GPP TS 24.501
[0258] 8.2.19 Configuration Update Command
[0259] 8.2.19.1 Message Definition
[0260] Configuration Update Command The message is sent by AMF to UE. See Table 8.2.19.1.1.
[0261] Message Type: Configuration Update Command
[0262] Meaning: Dual
[0263] Direction: Network to UE
[0264] Table 8.2.19.1.1: Configuration Update Command Message content
[0265]
[0266]
[0267] 8.2.19.2 Configuration Update Indication
[0268] If the AMF needs to request a confirmation or registration procedure to the UE, the AMF shall include this IE.
[0269] 8.2.19.3 5G-GUTI
[0270] This IE may be included to assign the new 5G GUTI to the UE.
[0271] 8.2.19.4 TAI List
[0272] This IE may be included to assign a new TAI list to the UE.
[0273] 8.2.19.5 Allowed NSSAI
[0274] This IE may be included to assign new allowed NSSAIs to the UE.
[0275] 8.2.19.6 List of service areas
[0276] This IE may be included to assign a new service area list to the UE.
[0277] 8.2.19.7 Full name of the network
[0278] This IE may be included to assign a new network complete name to the UE.
[0279] 8.2.19.8 Abbreviated name of the network
[0280] This IE may be included to assign a new network abbreviation name to the UE.
[0281] 8.2.19.9 Local Time Zone
[0282] This IE may be included to assign a new local time zone to the UE.
[0283] 8.2.19.10 Universal Time and Local Time Zone
[0284] This IE may be included to assign a new universal time and local time zone to the UE.
[0285] 8.2.19.11 Network Daylight Saving Time
[0286] This IE may be included to assign the new network daylight saving time to the UE.
[0287] 8.2.19.12 LADN Information
[0288] This IE may be included to assign new LADN information to the UE or to delete LADN information on the UE side.
[0289] 8.2.19.13 MICO Instructions
[0290] This IE may be included to request the UE to renegotiate the MICO mode.
[0291] 8.2.19.14 Network Slice Indication
[0292] This IE should be included if the user's network slice subscription changes in UDM.
[0293] 8.2.19.15 Configured NSSAI
[0294] The AMF shall include this IE when the AMF needs to provide the UE with the newly configured NSSAI for the current PLMN.
[0295] 8.2.19.16 Rejected NSSAI
[0296] The network may include this IE to inform the UE of an S-NSSAI that was previously sent to the UE in an allowed NSSAI but is now considered rejected by the network.
[0297] 8.2.19.17 Operator-defined access category definitions
[0298] This IE may be included to assign a new operator-defined access class definition to the UE or to delete an operator-defined access class definition on the UE side.
[0299] 8.2.19.18 SMS instructions
[0300] This IE may be included to indicate that the UE's ability to use SMS over NAS has changed. 8.2.19.19
[0302] This IE may be included to assign a new T3447 value to the UE.
[0303] 8.2.19.20 The full name of the network
[0304] This IE may be included to assign a new network complete name to the UE.
[0305] 8.2.19.21 Abbreviated name of the network
[0306] This IE may be included to assign a new network abbreviation name to the UE. (...)
[0308] A2.b2.c2.d2 Network Name 2
[0309] See subclauses abcd in 3GPP TS 24.008
[12] .
[0310] Appendix D - Example changes to 3GPP TS 22.101
[0311] A.3 Country / PLMN indication
[0312] The Country / PLMN indicator shows in which PLMN the UE is currently registered. This indicator is necessary so that the user knows when "roaming" occurs and that the choice of PLMN is correct. Both the Country and the PLMN will be indicated. When more than one visited PLMN is available in a given area, such information will be indicated.
[0313] The PLMN name is:
[0314] - stored in the ME and associated with the MCC+MNC combination received on the broadcast channel;
[0315] 10-NITZ / NITZ2 (see 22.042
[17] ) (in this case it overwrites the name stored in ME);
[0316] - stored in the USIM in text and / or graphic format and associated to the MCC+MNC combination and optionally the LAI, received on a broadcast channel (in this case it overwrites the name stored in the UE and - if present - the NITZ name).
[0317] It should be possible to store at least 10 PLMN identities (MCC+MNC combination and optionally LAI) on the USIM, for which the same PLMN name should be displayed.
[0318] The PLMN name stored in the USIM has the highest priority, followed by the PLMN name provided by NITZ / NITZ2. The PLMN name stored in the ME has the lowest priority.
[0319] If the PLMN name stored in the USIM is not available in text format and the UE is unable to display the graphical format, the PLMN name provided by NITZ / NITZ2 has the highest priority and the PLMN name stored in the ME has the next priority.
[0320] For PLMN names provided by NITZ, operators using non-Latin characters in local languages (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) can include network names in Latin characters in addition to local language characters. For PLMN names provided by NITZ2, operators can include network names in non-Latin characters from non-local languages.
[0321] For PLMN names provided by NITZ, if for (multiple) The language of the characters does not match the language of the UE's MMI (Latin is considered as one language), then UE should skip displaying characters. NITZ2 takes precedence over NITZ. For a PLMN name provided by NITZ2, the UE shall only display the network name indicated in the language of the MMI; in this process, for this network name, non-language characters or characters encoded in another language are [alt1: still displayed][alt2: characters considered to be in the language of the MMI]. If this results in no remaining If the PLMN name is not alphabetic, the UE shall skip displaying the PLMN name provided by NITZ2 / NITZ; the PLMN name stored in the ME has the next priority.
[0322] Appendix E - Example changes to 3GPP TS 22.101
[0323] A.3 Country / PLMN indication
[0324] The Country / PLMN indicator shows in which PLMN the UE is currently registered. This indicator is necessary so that the user knows when "roaming" occurs and that the choice of PLMN is correct. Both the Country and the PLMN will be indicated. When more than one visited PLMN is available in a given area, such information will be indicated.
[0325] The PLMN name is:
[0326] - stored in the ME and associated with the MCC+MNC combination received on the broadcast channel;
[0327] - NITZ / NITZ2 (see 22.042
[17] ) (in this case it overrides the name stored in ME);
[0328] - stored in the USIM in text and / or graphic format and associated to the MCC+MNC combination and optionally the LAI, received on a broadcast channel (in this case it overwrites the name stored in the UE and - if present - the NITZ / NITZ2 name).
[0329] It should be possible to store at least 10 PLMN identities (MCC+MNC combination and optionally LAI) on the USIM, for which the same PLMN name should be displayed.
[0330] The PLMN name stored in the USIM has the highest priority, followed by the PLMN name provided by NITZ / NITZ2. The PLMN name stored in the ME has the lowest priority.
[0331] If the PLMN name stored in the USIM is not available in text format and the UE is unable to display the graphical format, the PLMN name provided by NITZ / NITZ2 has the highest priority and the PLMN name stored in the ME has the next priority.
[0332] For PLMN names provided by NITZ, operators using non-Latin characters in local languages (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) may include the network name in Latin characters in addition to the local language characters. For PLMN names provided by NITZ2, operators may include the network name in the language of the UE's MMI.
[0333] For PLMN names provided by NITZ, if for (multiple) The language of the characters does not match the language of the UE's MMI (Latin is considered a language), then UE should skip displaying characters. NITZ2 takes precedence over NITZ. For PLMN names provided by NITZ2, the UE shall display all provided characters as indicated by the language of the MMI (even non-alphabetic characters or characters encoded in a different language than the MMI). If this results in no remaining characters in the PLMN name for NITZ / NITZ2 character, the UE shall skip displaying the PLMN name provided by NITZ / NITZ2; the PLMN name stored in the ME has the next priority.
[0334] Appendix F - Example changes to 3GPP TS 22.101
[0335] A.3 Country / PLMN indication
[0336] The Country / PLMN indicator shows in which PLMN the UE is currently registered. This indicator is necessary so that the user knows when "roaming" occurs and that the choice of PLMN is correct. Both the Country and the PLMN will be indicated. When more than one visited PLMN is available in a given area, such information will be indicated.
[0337] The PLMN name is:
[0338] - stored in the ME and associated with the MCC+MNC combination received on the broadcast channel;
[0339] - NITZ / NITZ2 (see 22.042
[17] ) (in this case it overrides the name stored in ME);
[0340] - stored in the USIM in text and / or graphic format and associated to the MCC+MNC combination and optionally the LAI, received on a broadcast channel (in this case it overwrites the name stored in the UE and - if present - the NITZ / NITZ2 name).
[0341] It should be possible to store at least 10 PLMN identities (MCC+MNC combination and optionally LAI) on the USIM, for which the same PLMN name should be displayed.
[0342] The PLMN name stored in the USIM has the highest priority, followed by the PLMN name provided by NITZ / NITZ2. The PLMN name stored in the ME has the lowest priority.
[0343] If the PLMN name stored in the USIM is not available in text format and the UE is unable to display the graphical format, the PLMN name provided by NITZ / NITZ2 has the highest priority and the PLMN name stored in the ME has the next priority.
[0344] For PLMN names provided by NITZ, Operators can include National language characters For PLMN names provided by NITZ2, the operator may include the network name in the language of the UE's MMI. Since NITZ2 includes the network name in the language of the MMI, the PLMN names provided by NITZ2 take precedence over NITZ (when NITZ2 is available, the UE does not display the network name provided by NITZ). For PLMN names provided by NITZ2, the UE shall display all provided characters as indicated by the language of the MMI (even non-alphabetic characters or characters with different language codes).
[0345]
[0346] Appendix G - 3GPP TS 24.QQ8 Change Examples
[0347] 10.5.3.5a Network Name
[0348] The purpose of this information element is to convey a text string to the mobile station.
[0349] The network name information element is encoded as Fig.10 .5.80 / 3GPP TS 24.008 and Table 10.5.94 / 3GPP TS24.008.
[0350] If encoding scheme UCS2 is used and Chinese-Japanese-Korean-Vietnamese (CJKV) ideographs as defined in ISO / IEC 10646
[72] are received in a text string, the MS shall use the MCC of the PLMN from which it received the Network Name information element to determine the language used for those CJKV ideographs as specified in Table 10.5.93a / 3GPP TS 24.008:
[0351] Table 10.5.93a / 3GPP TS 24.008: MCC to CJKV ideographic language mapping table
[0352] MCC(s) Country Language (C, J, K, or V) 460,461 Chinese mainland Chinese-G 466 Taiwan Chinese-T 454 Hong Kong, China Chinese-T 455 Macao, China Chinese-T 440,441 Japan J(Kanji) 450,467 South Korea K(Hanja) 452 Vietnam V(Chunom)
[0353] NOTE: This is due to the language ambiguity of CJKV ideographs in UCS2, i.e. the same hex code can be mapped to different character displays, depending on the language being used. The encoding of CJKV ideographs does not itself allow identification of the CJKV ideograph language.
[0354] (…)
[0355] abcd network name 2
[0356] The purpose of this information element is to convey a text string to the mobile station.
[0357] The encoding of the Network Name 2 information element is shown in Figure x1.y2.z1 / 3GPP TS 24.008 and Table x2.y2.z2 / 3GPP TS 24.008.
[0358] If encoding scheme UCS2 is used and Chinese-Japanese-Korean-Vietnamese (CJKV) ideographs as defined in ISO / IEC 10646
[72] are received in a text string, the MS shall use the language of the MMI to determine the language used for those CJKV ideographs.
[0359] NOTE: This is due to the language ambiguity of CJKV ideographs in UCS2, i.e. the same hex code can be mapped to different character displays, depending on the language being used. The encoding of CJKV ideographs does not itself allow identification of the CJKV ideograph language.
[0360] Network Name 2 is a Type 4 information element with a minimum length of 3 octets. Apart from the length limit given by the maximum number of octets in an L3 message (see 3GPP TS 44.006
[19] ), no upper limit on the length is specified.
[0361] For 3GPP TS 24.008 Network Name 2 information element, see Figure 8
[0362] Table 10.5.94 / 3GPP TS 24.008 Network Name 2 Information Elements
[0363]
[0364]
Claims
1. A method at a user equipment, the method comprising: receiving, at the user equipment, a tag string, the string further comprising an indicator bit; Based on the indicator bit, do one of the following: determining whether the user device supports one or more tags in the tag string and skipping display of characters corresponding to unsupported tags; or Displays all tags within the tag string. 2 . The method according to claim 1 , wherein the string comprises a plurality of indicator bits, each indicator bit corresponding to a tag in the tag string and indicating whether the tag needs to be displayed or skipped.
3. The method of claim 1, wherein the string is received in at least one of: an information element and a control signal.
4. The method of claim 3, wherein the character string is received in at least one of a mobility management (MM) information message, a general packet radio service (GPRS) mobility management (GMM) information message, a temporary mobile subscriber identity (TMSI) REALLOCATION COMMAND message, an IDENTITY REQUEST message, a LOCATION UPDATING ACCEPT message, an ATTACH ACCEPT message, an enhanced packet service (EPS) mobility management (EMM) information message, a GUTIREALLOCATION COMMAND message, an AUTHENTICATION REQUEST message, a SECURITY MODE COMMAND message, an IDENTITY REQUEST message, a DETACH ACCEPT message, a DETACH REQUEST message, a TRACKING AREA UPDATE ACCEPT message, a TRACKING AREA UPDATE REJECT message, a CONFIGURATION UPDATE COMMAND message, a REGISTRATION ACCEPT message, a DEREGISTRATION REQUEST message, a REGISTRATION REJECT message, an IDENTITY REQUEST message, and an AUTHENTICATION REQUEST message.
5. The method of claim 1, wherein the indicator bit further indicates that At least one tag in the tag string is deemed to belong to a language in a human-machine interface on the user device. The method of claim 5 , wherein a plurality of indicator bits are received in the tag string, each indicator bit corresponding to a tag in the tag string.
7. The method of claim 5, wherein a single indicator bit is received in the token string, the single indicator bit indicating that all tokens in the token string should be considered to belong to the language. The method of claim 5 , wherein the at least one token is a non-alphabetic character.
9. The method of claim 1, wherein the user device uses a language in a human-machine interface on the user device and the indicator bit to determine a mark to be displayed on the user device.
10. The method of claim 1, wherein the tag string corresponds to a name of a public land mobile network to which the user equipment is connected.
11. A user equipment, comprising: processor; as well as Communication subsystem, The user equipment is configured as follows: receiving, at the user equipment, a tag string, the string further comprising an indicator bit; Based on the indicator bit, do one of the following: determining whether the user device supports one or more tags in the tag string and skipping display of characters corresponding to unsupported tags; or Displays all tags within the tag string. 12 . The user equipment according to claim 11 , wherein the string comprises a plurality of indicator bits, each indicator bit corresponding to a tag in the tag string and indicating whether the tag needs to be displayed or skipped.
13. The user device according to claim 11, wherein the character string is between At least one of the following is received: information element and control signal.
14. The user equipment of claim 13, wherein the character string is received in at least one of a mobility management (MM) information message, a general packet radio service (GPRS) mobility management (GMM) information message, a temporary mobile subscriber identity (TMSI) REALLOCATION COMMAND message, an IDENTITY REQUEST message, a LOCATION UPDATING ACCEPT message, an ATTACH ACCEPT message, an enhanced packet service (EPS) mobility management (EMM) information message, a GUTIREALLOCATION COMMAND message, an AUTHENTICATION REQUEST message, a SECURITY MODE COMMAND message, an IDENTITY REQUEST message, a DETACH ACCEPT message, a DETACH REQUEST message, a TRACKING AREA UPDATE ACCEPT message, a TRACKING AREA UPDATE REJECT message, a CONFIGURATION UPDATE COMMAND message, a REGISTRATION ACCEPT message, a DEREGISTRATION REQUEST message, a REGISTRATION REJECT message, an IDENTITY REQUEST message, and an AUTHENTICATION REQUEST message.
15. The user device of claim 11, wherein the indicator bit further indicates that at least one token in the token string is regarded as belonging to a language in a human-machine interface on the user device.
16. The user equipment of claim 15, wherein a plurality of indicator bits are received in the tag string, each indicator bit corresponding to a tag in the tag string.
17. The user device of claim 15, wherein a single indicator bit is received in the tag string, the single indicator bit indicating that all tags in the tag string should be considered to belong to the language.
18. The user device of claim 15, wherein the at least one indicium is a non-alphabetic character.
19. The user device of claim 11, wherein the user device uses a language in a human-machine interface on the user device and the indicator bit to determine a mark to be displayed on the user device.
20. The user equipment of claim 11, wherein the tag string corresponds to a name of a public land mobile network to which the user equipment is connected.
21. A non-transitory computer readable medium for storing instruction codes, which, when executed by a processor of a user device, cause the user device to: receiving, at the user equipment, a tag string, the string further comprising an indicator bit; Based on the indicator bit, do one of the following: determining whether the user device supports one or more tags in the tag string and skipping display of characters corresponding to unsupported tags; or Displays all tags within the tag string.
