Telephone numbers

七年级上册英语Unit 1单元教案一、单元教材分析本单元围绕“结交新朋友”使学生学会打招呼和介绍自己、询问他人姓名的基本句型：“What’s your/his/her name？My/His/Her name is…”; 通过学习区分"First/last name”，了解有关姓名的文化知识；通过查询电话号码“What’s your/her/his phone number？”，学习数字1~9，同时也进一步促进学生之间的相互了解；通过以上几个方面的学习，使学生在轻松、愉快的学习氛围中熟识新伙伴。

本单元与第二单元衔接紧密：由课堂内的打招呼、自我介绍到课外、校外相互了解。

由特殊疑问句的学习到一般疑问句的学习，使学生将书本知识运用到实际生活中。

二、单元学情分析本单元的主题是熟识新伙伴，同时引导学生采用Practicing, Listening for specific information和Role playing的学习策略，学习一些新词汇，掌握一些重点句型，在小组合作学习的过程中，进一步促进学生之间的相互了解。

三、单元教学建议本单元可综合运用讲授式、启发式、自主学习、合作学习等各种策略，提供大量的学习资源，通过老师向学生进行的自我介绍，同学自我介绍传句子比赛，自我查资料表演，自制明信片等的活动，使学生能够学到知识，又增加了他们的学习的乐趣。

来培养学生的自主学习的能力及表达能力和逻辑思维能力。

采用Practicing, Listening for specific information和Role playing的学习策略，利用教学图片或制作多媒体课件来展开课堂Pair work, Group work的口语交际活动，询问他人姓名、查询电话号码，了解有关姓名的文化知识。

Section A 1 (1a-2d)一、教学目标：1.能掌握以下单词：name nice meet his and her your能掌握以下句型：①—Hi. My name’s Gina.—I’m Jenny. Nice to meet you!②—What’s your/his/her name?—My/His/H er name is…③—Are you…?—Yes, I am. / No, I'm not.④—Is he/she…?—Yes, she/he is. / No, she/he isn’t.2. 能了解以下语法：your, his, her等形容词性物主代词的简单用法；What’s=what is I’m=I am name’s=name is等缩写形式。

Network Working Group H. Schulzrinne Request for Comments: 3966 Columbia University Obsoletes: 2806 December 2004 Category: Standards TrackThe tel URI for Telephone NumbersStatus of this MemoThis document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions forimprovements. Please refer to the current edition of the "InternetOfficial Protocol Standards" (STD 1) for the standardization stateand status of this protocol. Distribution of this memo is unlimited. Copyright NoticeCopyright (C) The Internet Society (2004).AbstractThis document specifies the URI (Uniform Resource Identifier) scheme "tel". The "tel" URI describes resources identified by telephonenumbers. This document obsoletes RFC 2806.Table of Contents1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 22. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 43. URI Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . 44. URI Comparisons . . . . . . . . . . . . . . . . . . . . . . . 65. Phone Numbers and Their Context . . . . . . . . . . . . . . . 6 5.1. Phone Numbers. . . . . . . . . . . . . . . . . . . . . 6 5.1.1. Separators in Phone Numbers . . . . . . . . . . 7 5.1.2. Alphabetic Characters Corresponding to Digits . 7 5.1.3. Alphabetic, *, and # Characters as Identifiers. 7 5.1.4. Global Numbers. . . . . . . . . . . . . . . . . 7 5.1.5. Local Numbers . . . . . . . . . . . . . . . . . 8 5.2. ISDN Subaddresses. . . . . . . . . . . . . . . . . . . 9 5.3. Phone Extensions . . . . . . . . . . . . . . . . . . . 105.4. Other Parameters . . . . . . . . . . . . . . . . . . . 106. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 107. Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1. Why Not Just Put Telephone Numbers in SIP URIs?. . . . 11 7.2. Why Not Distinguish between Call Types?. . . . . . . . 11 7.3. Why tel. . . . . . . . . . . . . . . . . . . . . . . . 11 7.4. Do Not Confuse Numbers with How They Are Dialed. . . . 11 Schulzrinne Standards Track [Page 1]8. Usage of Telephone URIs in HTML . . . . . . . . . . . . . . . 119. Use of "tel" URIs with SIP (Informative). . . . . . . . . . . 1210. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 1411. Security Considerations . . . . . . . . . . . . . . . . . . . 1412. Changes Since RFC 2806. . . . . . . . . . . . . . . . . . . . 1413. References. . . . . . . . . . . . . . . . . . . . . . . . . . 15 13.1. Normative References . . . . . . . . . . . . . . . . . 15 13.2. Informative References . . . . . . . . . . . . . . . . 16 Author’s Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 171. IntroductionThis document defines the URI scheme "tel", which describes resources identified by telephone numbers. A telephone number is a string ofdecimal digits that uniquely indicates the network termination point. The number contains the information necessary to route the call tothis point. (This definition is derived from [E.164] but encompasses both public and private numbers.)The termination point of the "tel" URI telephone number is notrestricted. It can be in the public telephone network, a privatetelephone network, or the Internet. It can be fixed or wireless and address a fixed wired, mobile, or nomadic terminal. The terminaladdressed can support any electronic communication service (ECS),including voice, data, and fax. The URI can refer to resourcesidentified by a telephone number, including but not limited tooriginators or targets of a telephone call.The "tel" URI is a globally unique identifier ("name") only; it does not describe the steps necessary to reach a particular number anddoes not imply dialling semantics. Furthermore, it does not refer to a specific physical device, only to a telephone number.As commonly understood, telephone numbers comprise two related butdistinct concepts: a canonical address-of-record and a dial string.We define the concepts below:Address-of-record or identifier: The telephone number is understoodhere as the canonical address-of-record or identifier for atermination point within a specific network. For the publicnetwork, these numbers follow the rules in E.164 [E.164], whileprivate numbers follow the rules of the owner of the privatenumbering plan. Subscribers publish these identifiers so thatthey can be reached, regardless of the location of the caller.(Naturally, not all numbers are reachable from everywhere, for a Schulzrinne Standards Track [Page 2]variety of technical and local policy reasons. Also, a singletermination point may be reachable from different networks and may have multiple identifiers.)Dial string: "Dial strings" are the actual numbers, symbols, andpauses entered by a user to place a phone call. A dial string is consumed by one or more network entities and understood in thecontext of the configuration of these entities. It is used togenerate an address-of-record or identifier (in the sensedescribed above) so that a call can be routed. Dial strings mayrequire prepended digits to exit the private branch exchange (PBX) the end system is connected to, and they may include post-dialdual-tone multi-frequency (DTMF) signaling that could control aninteractive voice response (IVR) system or reach an extension.Dial strings are beyond the scope of this document.Both approaches can be expressed as a URI. For dial strings, thisURI is passed to an entity that can reproduce the actions specifiedin the dial string. For example, in an analog phone system, a dialer translates the dial string into a sequence of actions such as waiting for dial tone, sending DTMF digits, pausing, and generating post-dial DTMF digits after the callee picks up. In an integrated servicesdigital network (ISDN) or ISDN user part (ISUP) environment, thesignaling elements that receive protocol messages containing the dial string perform the appropriate protocol actions. As noted, thisapproach is beyond the scope of this specification.The approach described here has the URI specify the telephone number as an identifier, which can be either globally unique or only validwithin a local context. The dialling application is aware of thelocal context, knowing, for example, whether special digits need tobe dialed to seize an outside line; whether network, pulse, or tonedialling is needed; and what tones indicate call progress. Thedialling application then converts the telephone number into a dialsequence and performs the necessary signaling actions. The dialerdoes not have to be a user application as found in traditionaldesktop operating systems but could well be part of an IP-to-PSTNgateway.To reach a telephone number from a phone on a PBX, for example, theuser of that phone has to know how to convert the telephone numberidentifier into a dial string appropriate for that phone. Thetelephone number itself does not convey what needs to be done for aparticular terminal. Instructions may include dialling "9" beforeplacing a call or prepending "00" to reach a number in a foreigncountry. The phone may also need to strip area and country codes. Schulzrinne Standards Track [Page 3]The identifier approach described in this document has thedisadvantage that certain services, such as electronic banking orvoicemail, cannot be specified in a "tel" URI.The notation for phone numbers in this document is similar to that in RFC 3191 [RFC3191] and RFC 3192 [RFC3192]. However, the syntaxdiffers as this document describes URIs whereas RFC 3191 and RFC 3192 specify electronic mail addresses. RFC 3191 and RFC 3192 use "/" to indicate parameters (qualifiers). Since URIs use the forward slashto describe path hierarchy, the URI scheme described here uses thesemicolon, in keeping with Session Initiation Protocol (SIP) URIconventions [RFC3261].The "tel" URI can be used as a request URI in SIP [RFC3261] requests. The SIP specification also inherits the ’subscriber’ part of thesyntax as part of the ’user element’ in the SIP URI. Other protocols may also use this URI scheme.The "tel" URI does not specify the call type, such as voice, fax, or data call, and does not provide the connection parameters for a data call. The type and parameters are assumed to be negotiated eitherin-band by the telephone device or through a signaling protocol such as SIP.This document obsoletes RFC 2806.2. TerminologyIn this document, the key words "MUST", "MUST NOT", "REQUIRED","SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",and "OPTIONAL" are to be interpreted as described in BCP 14, RFC2119, [RFC2119] and indicate requirement levels for compliantimplementations.3. URI SyntaxThe URI is defined using the ABNF (augmented Backus-Naur form)described in RFC 2234 [RFC2234] and uses elements from the coredefinitions (appendix A of RFC 2234).The syntax definition follows RFC 2396 [RFC2396], indicating theactual characters contained in the URI. If the reserved characters"+", ";", "=", and "?" are used as delimiters between components ofthe "tel" URI, they MUST NOT be percent encoded. These charactersMUST be percent encoded if they appear in tel URI parameter values. Schulzrinne Standards Track [Page 4]Characters other than those in the "reserved" and "unsafe" sets (see RFC 2396 [RFC2396]) are equivalent to their "% HEX HEX" percentencoding.The "tel" URI has the following syntax:telephone-uri = "tel:" telephone-subscribertelephone-subscriber = global-number / local-numberglobal-number = global-number-digits *parlocal-number = local-number-digits *par context *parpar = parameter / extension / isdn-subaddressisdn-subaddress = ";isub=" 1*uricextension = ";ext=" 1*phonedigitcontext = ";phone-context=" descriptordescriptor = domainname / global-number-digitsglobal-number-digits = "+" *phonedigit DIGIT *phonedigitlocal-number-digits =*phonedigit-hex (HEXDIG / "*" / "#")*phonedigit-hexdomainname = *( domainlabel "." ) toplabel [ "." ]domainlabel = alphanum/ alphanum *( alphanum / "-" ) alphanumtoplabel = ALPHA / ALPHA *( alphanum / "-" ) alphanumparameter = ";" pname ["=" pvalue ]pname = 1*( alphanum / "-" )pvalue = 1*paramcharparamchar = param-unreserved / unreserved / pct-encodedunreserved = alphanum / markmark = "-" / "_" / "." / "!" / "˜" / "*" /"’" / "(" / ")"pct-encoded = "%" HEXDIG HEXDIGparam-unreserved = "[" / "]" / "/" / ":" / "&" / "+" / "$"phonedigit = DIGIT / [ visual-separator ]phonedigit-hex = HEXDIG / "*" / "#" / [ visual-separator ]visual-separator = "-" / "." / "(" / ")"alphanum = ALPHA / DIGITreserved = ";" / "/" / "?" / ":" / "@" / "&" /"=" / "+" / "$" / ","uric = reserved / unreserved / pct-encodedEach parameter name ("pname"), the ISDN subaddress, the ’extension’, and the ’context’ MUST NOT appear more than once. The ’isdn-subaddress’ or ’extension’ MUST appear first, if present, followed by the ’context’ parameter, if present, followed by any other parameters in lexicographical order.This simplifies comparison when the "tel" URI is comparedcharacter by character, such as in SIP URIs [RFC3261].Schulzrinne Standards Track [Page 5]4. URI ComparisonsTwo "tel" URIs are equivalent according to the following rules:o Both must be either a ’local-number’ or a ’global-number’, i.e.,start with a ’+’.o The ’global-number-digits’ and the ’local-number-digits’ must beequal, after removing all visual separators.o For mandatory additional parameters (section 5.4) and the ’phone- context’ and ’extension’ parameters defined in this document, the ’phone-context’ parameter value is compared as a host name if itis a ’domainname’ or digit by digit if it is ’global-number-digits’. The latter is compared after removing all ’visual-separator’ characters.o Parameters are compared according to ’pname’, regardless of theorder they appeared in the URI. If one URI has a parameter namenot found in the other, the two URIs are not equal.o URI comparisons are case-insensitive.All parameter names and values SHOULD use lower-case characters, astel URIs may be used within contexts where comparisons are casesensitive.Section 19.1.4 in the SIP specification [RFC3261] discusses one such case.5. Phone Numbers and Their Context5.1. Phone NumbersThe ’telephone-subscriber’ part of the URI indicates the number. The phone number can be represented in either global (E.164) or localnotation. All phone numbers MUST use the global form unless theycannot be represented as such. Numbers from private numbering plans, emergency ("911", "112"), and some directory-assistance numbers(e.g., "411") and other "service codes" (numbers of the form N11 inthe United States) cannot be represented in global (E.164) form andneed to be represented as a local number with a context. Localnumbers MUST be tagged with a ’phone-context’ (section 5.1.5).Implementations MUST NOT assume that telephone numbers have amaximum, minimum, or fixed length, or that they always begin with or contain certain digits.Schulzrinne Standards Track [Page 6]5.1.1. Separators in Phone NumbersPhone numbers MAY contain visual separators. Visual separators(’visual-separator’) merely aid readability and are not used for URI comparison or placing a call.Although it complicates comparisons, this specification retainsvisual separators in order to follow the spirit of RFC 2396[RFC2396], which remarks that "A URI often needs to be remembered by people, and it is easier for people to remember a URI when itconsists of meaningful components". Also, ISBN URNs documented inRFC 3187 [RFC3187] use visual separators in a manner similar to this specification.However, even though ITU-T E.123 [E.123] recommends the use of space characters as visual separators in printed telephone numbers, "tel"URIs MUST NOT use spaces in visual separators to avoid excessiveescaping.5.1.2. Alphabetic Characters Corresponding to DigitsIn some countries, it is common to write phone numbers withalphabetic characters corresponding to certain numbers on thetelephone keypad. The URI format does not support this notation, as the mapping from alphabetic characters to digits is not completelyuniform internationally, although there are standards [E.161][T1.703] addressing this issue.5.1.3. Alphabetic, *, and # Characters as IdentifiersAs called and calling terminal numbers (TNs) are encoded in BCD inISUP, six additional values per digit can be encoded, sometimesrepresented as the hexadecimal characters A through F. Similarly,DTMF allows for the encoding of the symbols *, #, and A through D.However, in accordance with E.164, these may not be included inglobal numbers. Their meaning in local numbers is not defined here, but they are not prohibited.5.1.4. Global NumbersGlobally unique numbers are identified by the leading "+" character. Global numbers MUST be composed with the country (CC) and national(NSN) numbers as specified in E.123 [E.123] and E.164 [E.164].Globally unique numbers are unambiguous everywhere in the world andSHOULD be used.Schulzrinne Standards Track [Page 7]5.1.5. Local NumbersLocal numbers are unique only within a certain geographical area or a certain part of the telephone network, e.g., a private branchexchange (PBX), a state or province, a particular local exchangecarrier, or a particular country. URIs with local phone numbersshould only appear in environments where all local entities cansuccessfully set up the call by passing the number to the diallingsoftware. Digits needed for accessing an outside line, for example, are not included in local numbers. Local numbers SHOULD NOT be used unless there is no way to represent the number as a global number.Local numbers SHOULD NOT be used for several reasons. Local numbers require that the originator and recipient are configuredappropriately so that they can insert and recognize the correctcontext descriptors. Since there is no algorithm to pick the samedescriptor independently, labelling numbers with their contextincreases the chances of misconfiguration so that valid identifiersare rejected by mistake. The algorithm to select descriptors waschosen so that accidental collisions would be rare, but they cannotbe ruled out.Local numbers MUST have a ’phone-context’ parameter that identifiesthe scope of their validity. The parameter MUST be chosen toidentify the local context within which the number is uniqueunambiguously. Thus, the combination of the descriptor in the’phone-context’ parameter and local number is again globally unique. The parameter value is defined by the assignee of the local number.It does NOT indicate a prefix that turns the local number into aglobal (E.164) number.There are two ways to label the context: via a global number or any number of its leading digits (e.g., "+33") and via a domain name,e.g., "". The choice between the two is left tothe "owner" of the local number and is governed by whether there is a global number or domain name that is a valid identifier for aparticular local number.The domain name does not have to resolve to any actual host but MUST be under the administrative control of the entity managing the local phone context.A global number context consists of the initial digits of a validglobal number. All global numbers with these initial digits must be assigned to the same organization, and no such matching number can be used by any other organization. For example, +49-6151-16 would be a suitable context for the Technical University of Darmstadt, as ituses all numbers starting with those digits. If such an initial Schulzrinne Standards Track [Page 8]string of digits does not exist, the organization SHOULD use thelowest number of the global number range assigned to it. (This canoccur if two organizations share the same decimal block of numbers.For example, assume an organization owns the number range +1-212-555-0100 through +1-212-555-0149. +1-212-555-1 would not be a valid global number context, but +1-212-555-0100 would work.) It is notrequired that local numbers within the context actually begin withthe chosen set of initial numbers.A context consisting of the initial digits of a global number doesnot imply that adding these to the local number will generate a valid E.164 number. It might do so by coincidence, but this cannot berelied upon. (For example, "911" should be labeled with the context "+1", but "+1-911" is not a valid E.164 number.)National freephone numbers do not need a context, even though theyare not necessarily reachable from outside a particular country code or numbering plan. Recall that "tel" URIs are identifiers; it issufficient that a global number is unique, but it is not requiredthat it be reachable from everywhere.Even non-freephone numbers may be out of date or may not bereachable from a particular location. For example, premiumservices such as "900" numbers in the North American numberingplan are often not dialable from outside the particular countrycode.The two label types were chosen so that, in almost all cases, alocal administrator can pick an identifier that is reasonablydescriptive and does not require a new IANA-managed assignednumber. It is up to the administrator to assign an appropriateidentifier and to use it consistently. Often, an organization can choose among several different identifiers.If the recipient of a "tel" URI uses it simply for identification,the receiver does not need to know anything about the contextdescriptor. It simply treats it as one part of a globally uniqueidentifier, with the other being the local number. If a recipient of the URI intends to place a call to the local number, it MUSTunderstand the context and be able to place calls within thatcontext.5.2. ISDN SubaddressesA phone number MAY also contain an ’isdn-subaddress’ parameter thatindicates an ISDN subaddress.Schulzrinne Standards Track [Page 9]ISDN subaddresses typically contain International Alphabet 5 (IA5[T.50]) characters but may contain any octet value.5.3. Phone ExtensionsPhone extensions identify stations behind a non-ISDN PBX and arefunctionally roughly equivalent to ISDN subaddresses. They areidentified with the ’extension’ parameter. At most, one of the’isdn-subaddress’ and ’extension’ parameters can appear in a "tel"URI, i.e., they cannot appear both at the same time.5.4. Other ParametersFuture protocol extensions to this URI scheme may add otherparameters (’parameter’ in the ABNF). Such parameters can be either mandatory or optional. Mandatory parameters start with "m-". Animplementation MAY ignore optional parameters and MUST NOT use theURI if it contains unknown mandatory parameters. The "m-" prefixcannot be added to parameters that were already registered (except to create a new, logically distinct parameter). The "phone-context"parameter in this document is mandatory, and "isub" and "ext" areoptional.New mandatory parameters must be described in a standards-track RFC, but an informational RFC is sufficient for optional parameters.For example, ’parameter’ parameters can be used to storeapplication-specific additional data about the phone number, itsintended use, or any conversions that have been applied to thenumber.Entities that forward protocol requests containing "tel" URIs withoptional parameters MUST NOT delete or modify parameters they do not understand.6. Examplestel:+1-201-555-0123: This URI points to a phone number in the United States. The hyphens are included to make the number more humanreadable; they separate country, area code and subscriber number. tel:7042;phone-context=: The URI describes a local phonenumber valid within the context "".tel:863-1234;phone-context=+1-914-555: The URI describes a localphone number that is valid within a particular phone prefix. Schulzrinne Standards Track [Page 10]7. Rationale7.1. Why Not Just Put Telephone Numbers in SIP URIs?The "tel" URI describes a service, reaching a telephone number, that is independent of the means of doing so, be it via a SIP-to-PSTNgateway, a direct SIP call via E.164 number ("ENUM") translation[RFC3761], some other signaling protocols such as H.323, or atraditional circuit-switched call initiated on the client side via,say, the Telephony Application Programming Interface (TAPI). Thus,in spirit, it is closer to the URN schemes that also leave theresolution to an external mechanism. The same "tel" URI may gettranslated to any number of other URIs in the process of setting upthe call.7.2. Why Not Distinguish between Call Types?Signaling protocols such as SIP allow negotiating the call type andparameters, making the very basic indication within the URI schememoot. Also, since the call type can change frequently, any suchindication in a URI is likely to be out of date. If such designation is desired for a device that directly places calls without asignaling protocol such as SIP, mechanisms such as the "type"attribute for the "A" element in HTML may be more appropriate.7.3. Why "tel"?"tel" was chosen because it is widely recognized that none of theother suggestions appeared appropriate. "Callto" was discardedbecause URI schemes locate a resource and do not specify an action to be taken. "Telephone" and "phone" were considered too long and noteasily recognized internationally.7.4. Do Not Confuse Numbers with How They Are DialedAs an example, in many countries the E.164 number "+1-212-555-3141"will be dialed as 00-1-212-555-3141, where the leading "00" is aprefix for international calls. (In general, a "+" symbol in E.164indicates that an international prefix is required.)8. Usage of Telephone URIs in HTMLLinks using the "tel" URI SHOULD enclose the telephone number so that users can easily predict the action taken when following the linkDial <a href="tel:+1-212-555-0101">+1-212-555-0101</a> forassistance.Schulzrinne Standards Track [Page 11]instead ofDial <a href="tel:+1-212-555-0101">this number</a> for assistance.On a public HTML page, the telephone number in the URI SHOULD always be in the global form, even if the text of the link uses some localformat:Telephone (if dialling in the United States):<a href="tel:+1-201-555-0111">(201) 555-0111</a>or evenFor having RFCs read aloud, call <ahref="tel:+1-555-438-3732">1-555-IETF-RFC</a>.9. Use of "tel" URIs with SIP (Informative)SIP can use the "tel" URI anywhere a URI is allowed, for example as a Request-URI, along with "sip" and "sips" URIs. For brevity, we will imply "sips" URIs when talking about SIP URIs. Both "tel" and SIPURIs can contain telephone numbers. In SIP URIs, they appear as the user part, i.e., before the @ symbol (section 19.1.6 in [RFC3261]).Unless a SIP UA connects directly to a PSTN gateway, one of the SIPproxy servers has to translate the "tel" URI to a SIP URI, with thehost part of that URI pointing to a gateway. Typically, the outbound proxy server, as the first proxy server visited by a call request,performs this translation. A proxy server can translate all "tel"URIs to the same SIP host name or select a different gateway fordifferent "tel" prefixes, based, for example, on information learned from TRIP [RFC3219]. However, a proxy server could also delegatethis translation task to any other proxy server, as proxy servers are free to apply whatever routing logic they desire. For local numbers, the proxy MUST NOT translate "tel" URIs whose contexts it does notunderstand.As noted earlier, all phone numbers MUST use the global form unlessthey cannot be represented as such. If the local-number format isused, it MUST be qualified by the ’phone-context’ parameter.Effectively, the combination of local number and phone context makes the "tel" URI globally unique.Although web pages, vCard business cards, address books, anddirectories can easily contain global "tel" URIs, users on twelve-button (IP) phones cannot dial such numbers directly and aretypically accustomed to dialling shorter strings, e.g., for PBXextensions or local numbers. These so-called dial strings (section Schulzrinne Standards Track [Page 12]。

新课标初中英语教材篇一：新人教版英语七年级上册教材(word版)Unit 1 My name’s Gina.Language Goals: Introduce yourself；Greet people； Ask for and give telephone number语言目标：介绍自己；问候他人；询问和告知电话号码1aWrite English words for thethings in the picture.写出图中物品的英文名称。

1b Listen and number the conversations［1-3］.听录音，为对话编号。

□A: What’s your name? □A: Good morning! □A: Hi. My name’s Gina.B: Alan. B: I’m Cindy. B: I’m Jenny. Nice to meet you!A: Hello, Alan. I’m Ms Brown. B: Hello, Cindy. I’m Dale.A: Nice to meet you, too. A: Nice to meet you!1c Practice the conversations above with your partner. Then greet your classmates. 练习上面的对话，然后问候你的同学。

2a Listen to the conversations and number the pictures [1—4].听对话，为图片编号。

2b再听一遍录音，圈出你听到的名字。

2c Practice the conversations in pairs.A: Hello! What’s your name A: What’s his name?B: My name’s… B: His name is…A: I’m… A: And what’s her name?B: Nice to meet you! B: Her name is…2d Role play the conversation. 分角色表演对话Linda: Good afternoon! My name’s Linda.Are you Helen?Helen: Yes, I am. Nice to meet you, Linda.Linda: Nice to meet you, too. What’s hername?Helen: She’s Jane.Linda: Is he Jack?Helen: No, he isn’t. His name’s Mike.3a Put the words in order to make conversations. Then practice them.调整词序，组成对话并练习。

电话号码的英语说法电话号码的英语说法phone numbertelephone code电话号码相关英语表达联系电话号码 contact phone number紧急电话号码 emergency telephone number电话号码格式化 phoneformatter我的电话号码 my phone number查找一个电话号码 looking up a phone number移动电话号码 mobile telephone number电话号码的英语例句 1. do you have an address and phone number for him?你有他的地址和电话号码么?2. you know you can phone me — here's my mother'snumber.你可以给我打电话——给你，这是我母亲的电话号码。

3. have you moved yet? pls advise address, phone no.你已经搬了吗?请告知地址和电话号码。

4. she suddenly realized that wim was reciting kirk's telephone number.她突然意识到威姆正在念的是柯克的电话号码。

5. please give a daytime telephone number.请留一个日间的电话号码。

6. sarah sat down and dialled a number.萨拉坐下来拨了一个电话号码。

7. i left my phone number with several people.我把电话号码留给了几个人。

8. clearly state your address and telephone number.清楚地报上你的地址和电话号码。

9. my number is 414-3925.我的电话号码是414-3925。

雅思听力笔记之电话号码热1Ms.Jr2010-02-18 21:20熟练记下对方的电话号码是生活、工作在英语国家必备的一项survial skill，因此是IELTS 考试的考点，考生一定要熟练掌握。

统计资料显示: V18, V22, V24, V26, V33, V36， V38, V39,V41等version中都以不同的出现方式考了电话场景。

在这个场景中，主要的考试形式是填空，即要求正确地听出和写出电话号码。

下面结合考题详细讲述其考试技巧。

（1）基本训练。

电话号码是由0~9这十个数字组成的，因此考生一定要对这十个数字的念法非常熟悉。

许多听力教材提供了数字的训练音带，大家找一本合适自己的进行练习即可。

当训练到一定程度后，建议进行“自言自语”式的训练，即自己快速地、无意识地说一些数字，边说边记，以此来训练对数字的敏感能力，这是最关键的一步。

（2）“0”在英语中有许多表示方法，如zero，nought, null, nil, nothing等，应该注意的是：英国英语与美国英语在念法上有所不同，在TOEFL考试中，“0”常念作“zero”，但在IELTS考试中“0”常念作“nought”（V35的section 4）；而在电话号码中“0” 读作字母”Oh”,就像在单词“go”中的发音。

（3）读电话号码总的规则是：国家代号、地区代号和具体号码分开来读，比如中国北京的一个电话读作86，10，87654321，对于一个特定地区的电话，一般来说只有7位或8位。

7位的号码，读的时候前三位一组连在一起，后四位一组连在一起，中间有一个停顿，比如6254598读作six two five，four five nine eight；8位的号码，可以四个一组来读，考生可参看本节后面的一些典型例句。

（4）两个相同数字或三个相同的数字可以用double或triple来代替，比如2246555可以读作double two four，six triple five。

英语作文电话号码表达Title: The Importance and Structure of Telephone Numbers in Modern Communication.In the fast-paced world of modern communication, telephone numbers serve as the lifelines connecting individuals, businesses, and organizations across vast distances. These sequences of digits, often taken for granted, play a crucial role in facilitating prompt and efficient communication. This essay delves into the significance of telephone numbers, their structure, and the evolving role they play in today's interconnected world.The significance of telephone numbers lies in their universality and convenience. Regardless of location, language, or culture, the format and purpose of a telephone number remain the same: to establish a direct line of communication between two parties. This universality is enhanced by the fact that telephone numbers are easily memorable and can be quickly accessed through variousdevices, such as smartphones, tablets, and computers.The structure of a telephone number follows a specific format, which varies depending on the country or region. In most cases, telephone numbers are composed of a combination of digits, grouped into sections to enhance readability and ease of recall. For instance, in the United States and Canada, telephone numbers typically consist of a three-digit area code, followed by a three-digit prefix, and then a four-digit line number. This format is widely recognized and easily recognizable, making it simple for users to dial the desired number.The evolving role of telephone numbers in modern communication is marked by the integration of new technologies and the emergence of alternative communication methods. With the advent of the internet and mobile phones, telephone numbers have expanded beyond their traditional role as just voice communication tools. Now, they are often associated with email addresses, social media profiles, and online accounts, providing a seamless link betweendifferent platforms and modes of communication.Additionally, telephone numbers have become a crucial component of online identity and security. In many cases, they are used as verification tools to confirm the identity of users, such as in banking transactions or online purchases. The unique nature of telephone numbers makesthem effective identifiers, ensuring that only the rightful owner can access sensitive information or perform critical actions.Moreover, telephone numbers play a pivotal role in emergency response systems. In times of crisis or emergency, individuals can dial emergency services numbers, such as911 in the United States, to seek immediate assistance. These numbers are typically prioritized by telephoneservice providers, ensuring that emergency calls are connected quickly and efficiently.In conclusion, telephone numbers are an integral partof modern communication, serving as the backbone of voice calls, text messages, and online interactions. Their universality, convenience, and evolving role in newtechnologies underscore their importance in today's interconnected world. As communication methods continue to evolve, telephone numbers will remain a crucial component, facilitating seamless communication between individuals and organizations across the globe.。

number和numbers的用法“哎呀，这个 number 和 numbers 到底咋用啊？”好啦，那咱就来好好讲讲 number 和 numbers 的用法。

Number 作为名词，最常见的意思就是“数字”“号码”“数量”等。

比如说，“What's your phone number?”（你的电话号码是多少？）这里的 number 就是指号码。

再比如，“The number of students in our class is 50.”（我们班的学生数量是 50。

）这里就是指数量。

Numbers 呢，它其实就是 number 的复数形式。

当我们要表示多个数字、号码或数量的时候，就用 numbers。

比如说，“I have a lot of phone numbers.”（我有很多电话号码。

）或者“There are large numbers of books in the library.”（图书馆里有大量的书。

）咱举个实际例子哈，比如说你在整理文件，你可以说“There are a number of files to be sorted.”（有一些文件要整理），这里用 a number of 表示“一些”“许多”。

如果文件很多很多，你就可以说“There are large numbers of files to be sorted.”（有大量的文件要整理）。

再比如说，你和朋友聊天说到各自的兴趣爱好，你可以说“I have a number of hobbies, such as reading and traveling.”（我有一些爱好，比如阅读和旅行。

）而如果你们在讨论一个群体的兴趣爱好，就可以说“There are different numbers of hobbies among different people.”（不同的人有不同数量的爱好。

）在数学里，我们经常会说“There are several numbers in this equat ion.”（在这个等式中有几个数字。

学习用英语询问电话号码和表,表述及问答学习用英语询问电话号码和表,表述及问答如下：
John, what is your phone number?
约翰，你的电话号码是多少？
It's 123-456-789.
是123-456-789。

John, can you tell me your number, please?
约翰，你能告诉我你的电话号码吗？
Sure. It's 123-456-789.
当然是123-456-789。

John, would you mind telling me your number, please?
约翰，请告诉我你的电话号码好吗？
Not at all. It's 123-456-789.
一点也不。

是123-456-789。

询问电话号码的说法如下:
Hello, may I have your telephone number, please?
您好，请问方便提供一下你的电话号码给我吗?
Could you tell me your phone number?
能告诉我你的联系方式吗?
Can I have your number, please?
可以把你电话号码给我吗?
Would you give me your phone number，please?
可以把你电话号码给我吗?（这句比较适用于陌生或客户委婉地问）。