KR20100084555A - Methods for provisioning mobile stations and wireless communications with mobile stations located within femtocells - Google Patents

Abstract

A method for wireless communications with mobile stations located within a femtocell is described. The method includes registering a femtocell with an IMS core network to receive IMS services for one or more mobile stations located within the femtocell, and separately registering the mobile station with an application server to provide additional services to the mobile station located within the femtocell. The additional services may be CDMA services. Also, registering the femtocell with the IMS core network may include transmitting femtocell registration information that does not include information regarding the mobile station to the IMS core network to request IMS services for the mobile station.

Description

METHODS FOR PROVISIONING MOBILE STATIONS AND WIRELESS COMMUNICATIONS WITH MOBILE STATIONS LOCATED WITHIN FEMTOCELLS} Mobile stations and methods for provisioning wireless communications with mobile stations located within femtocells

Priority statement

This patent application is incorporated by reference in 35 U.S.C. Patent No. 61 / 000,575, filed Oct. 26, 2007, the entire contents of which are hereby incorporated by reference. Claim priority under §119 (e).

The present invention relates to methods for provisioning wireless communications with mobile stations and mobile stations located within femtocells.

Femto base stations are basically installed indoors (eg, in a home or office) and are equipped with cables, DSL, on-premise fiber optic links, or similar IP backhaul technology. It is a low cost and low power base station transceiver connected to the Internet via. This connection is used to integrate the femto base station with the core operator's core network.

A femto base station serves in a geographic area known as a femtocell over a single carrier or channel. In a wireless network comprising femtocells, upon entering the femtocell, the mobile station is responsible for the current 3GPP2 CDMA2000 EVDO standards (eg, the 3GPP2 CDMA2000 EVDO standard "cdma2000 High Rate Packet Data Air Interface Specification", 3GPP2 C.S0024-B). Receive broadcast overhead messages in accordance with well-known standards, such as Ver. 2.0 (March 2007), and the like.

When CDMA mobile stations are connected to an IP Multimedia Subsystem (IMS) via a line connection (e.g., a CDMA femtocell), the IMS is a Visited Mobile Switching Center (V) in the CDMA Mobility Network Model. Emulate the MSC / Visitor Location Register (VLR). In the CDMA mobility network model, the V-MSC / VLR does not provision subscriber data associated with each user capable of receiving the service. Instead, the V-MSC / VLR registers with the Home Location Register (HLR) and dynamically retrieves subscriber data needed to provide services to CDMA users currently served by the V-MSC / VLR. .

However, the IMS is based on a wired model, in which case users of the IMS must be pre-provisioned as subscribers on the IMS before they are even granted basic access. Conflict between provisioning strategies for IMS and CDMA networks becomes a problem when using IMS as a V-MSC / VLR.

This issue with provisioning strategies will also apply to UMTS users connected to UMTS femtocells.

Typically, the solution to a provisioning strategy conflict operates under the assumption that a pre-provisioned subscriber record exists on the IMS for each CDMA user authorized to access through a given CDMA femtocell. This is often envisioned as a semi-automated provisioning process based on the location of a CDMA user on an Access Control List (ACL) or Authorized User List (AUL) associated with each femtocell. However, this approach has at least three problems.

The first problem is referred to herein as a "coffeeshop" or "public" femtocell that does not have an ACL of users who are granted access. In this case, if there is no ACL created for the femtocell, it is impossible to trigger an HSS population of IMS subscriber records for CDMA users of such coffee shops or public femtocells.

Another problem is that service providers typically have provided feedback that per-user IMS subscriber records are not acceptable to them. Service providers hope that femtocell systems can operate with dynamic data (eg, only VLR downloads) and do not rely on pre-provisioned data for any user.

Another problem is that pre-provisioning solutions generally require access of CDMA users to CDMA service provider back-office provisioning systems. Since service providers prevent other service providers from accessing their back-office provisioning systems, there is a problem of supporting CDMA users from another service provider on a femtocell served by a particular service provider. For example, if a given femtocell is connected to a Verizon wireless IMS and back-office system network, the pre-provisioning process will be blocked due to the inability to access Sprint or Alltel back-office provisioning systems from the Verizon system. It will be impossible for Sprint or Alltel users to receive service on the femtocell.

It is an object of the present invention to provide methods for provisioning wireless communications with mobile stations located in mobile stations and femtocells.

Example embodiments relate to methods for provisioning wireless communications with mobile stations and mobile stations located within femtocells.

The method for wireless communications includes registering a femtocell with an IMS core network to receive IMS services for at least one mobile station located within the femtocell; And separately registering the mobile station with an application server to provide additional services to mobile stations located within the femtocell. Additional services are CDMA services.

Registering the femtocell with the IMS core network includes sending femtocell registration information to the IMS core network to request IMS services for mobile stations located within the femtocell. The femtocell registration information does not include information about the mobile station.

The method also includes receiving authentication keys from the IMS core network; Preparing an authentication response based on the received authentication keys and the stored femtocell information; And sending an authentication response prepared for receiving IMS services to the IMS core network.

The method also includes receiving a global random key from the IMS core network once the femtocell is registered; Obtaining a challenge using the received key and time value; Sending the challenge to the mobile station; And providing services to the mobile station in response to the transmitted challenge.

Registering the mobile station separately with the application server includes receiving an authentication response to the global challenge from the mobile station; Generating a first SIP message associated with the mobile station based on the authentication response; Sending the first SIP message to an IMS core network to register a mobile station for additional services; Receiving a second SIP message from an IMS core network; And providing the mobile station with information regarding registration for additional services.

The first SIP message includes at least one of an electronic serial number of the mobile station, a mobile identification number of the mobile station, a random number, and a time value. The second SIP message includes a mobile directory number for the mobile station.

The method also includes receiving a call setup request from a mobile station that includes a called party number (CpDN); Generating a SIP message comprising CpDN and mobile station information; And sending the generated SIP message to the IMS core network to notify the IMS core network of the call request. The SIP message includes information associated with the mobile station in its sub address. The information associated with the mobile station also includes at least one of a mobile identification number, an electronic serial number, and a mobile directory number.

The method also includes receiving a paging request from the IMS core network and a SIP message comprising at least one of a mobile identification number and a mobile directory number; Paging to the mobile station based on the SIP message containing the paging request; Receiving a paging response from the mobile station; And providing the paging response to the IMS core network.

Another method for wireless communications includes receiving registration information for IMS services from a femtocell; Generating a global random key; And transmitting the global random key to the femtocell. The registration information does not include information about the mobile station located in the femtocell. The global random key is used to send a challenge to a mobile station located within the femtocell.

The method also includes receiving mobile station information from a femtocell's user agent to register the mobile station for CDMA services; Authenticating the mobile station based on the mobile station information; Registering with a home location register (HLR) as a visited location register (VLR); Receiving a VLR profile from the HLR based on the mobile station information; And communicating with the mobile station as a VLR. The mobile station information includes at least one of an electronic serial number, a mobile identification number, a random number received by the mobile station, an authentication response generated by the mobile station, and a time value. The time value is associated with a time of day and is used to determine if the random number is valid.

This method treats a femtocell as an endpoint for IMS services and CDMA services provided to mobile stations located within the femtocell.

The method also includes receiving a message comprising mobile station information and a called party number; Authenticating the mobile station based on the mobile station information; Once the mobile station is authenticated, generating an authentication request message that includes the mobile station information; Sending an authentication request to the HLR; And providing, by the mobile station, a second SIP message comprising the mobile directory number to establish a communication path with the called station associated with the called number.

According to this method, authenticating a mobile station comprises inputting a global random key and time value into a function to generate a random number; And verifying that the generated random number is within an acceptable range.

The method also includes receiving a routing request that includes a mobile identification number of the mobile station; Associating a temporary local directory number with a mobile station; triggering generation of a SIP message and transmission to a femto user agent associated with the mobile station; receiving a response to the SIP message; based on the response And if the mobile station is authenticated, acting as a VLR during the establishment of a traffic channel between the mobile station and the mobile station initiating the call to the mobile station located within the femtocell. The message includes the mobile identification number of the mobile station in the sub address.

Authenticating the mobile station comprises inputting a global random key and time value into a function to generate a random number; And verifying that the generated random number is within an acceptable range.

A method for IP Multimedia Subsystem (IMS) communication includes transmitting femtocell registration information to an IMS core network to request IMS services for a mobile station located within a femtocell. According to this method, the femtocell registration information does not include information about the mobile station. For example, the femtocell registration information may include only information about the femtocell.

The above features and advantages of the exemplary embodiments and other features and advantages will become more apparent upon a review of the following detailed description of the specification with reference to the accompanying drawings.

1 illustrates an exemplary wireless communication system.
FIG. 2 is a signal flow diagram illustrating IMS registration / authentication performed by a femto user agent (UA) when a femtocell is powered up. FIG.
3 is a signal flow diagram illustrating registration for a CDMA mobile station located within a femtocell.
4 is a signal flow diagram illustrating messages and operations transmitted in connection with a call initiated by a mobile station located within a femtocell.
5 is a signal flow diagram illustrating messages and operations transmitted in connection with a call directed to a mobile station located within a femtocell.

In the following description, for purposes of explanation, not limitation, certain details, such as specific architectures, interfaces, techniques, and the like, are described to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the teachings of the present invention may be practiced in other descriptive embodiments that depart from the specific details described in connection with FIGS. In some cases, detailed descriptions of well-known devices, circuits, and methods have been omitted from the present application in order not to obscure the description of the invention in unnecessary detail. All principles, aspects, and embodiments of the present invention, as well as specific examples thereof, are intended to include both structural and functional equivalents of the present invention. In addition, such equivalents include both currently known equivalents as well as future developed equivalents.

Example embodiments are discussed herein as being implemented in a suitable computing environment. Although not required, example embodiments will be described in general context, computer-executable instructions, such as program modules or functional processes, executed by one or more computer processors or CPUs. Generally, program modules or functional processes include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. do. The program modules and functional processes discussed herein may be implemented using existing hardware in existing communication networks. For example, the program modules and functional processes discussed herein can be implemented using existing hardware such as a femto base station, an application server in an IMS, and the like.

In the following description, unless illustrative embodiments are indicated otherwise, they are described with reference to symbolic representations of actions and operations in the form of signal flow diagrams, for example, performed by one or more processors. As such, it will be understood that such acts and operations, sometimes referred to as computer-implemented, include manipulation by a processor of electrical signals representing data in a structured form. This operation transforms the data or maintains the data at the locations of the computer's memory system, which reconfigures or alters the operation of the computer in a manner well understood by those skilled in the art.

1 illustrates portions of a telecommunications system 10 in which the example embodiments described below may be implemented. The telecommunication system 10 includes a CDMA mobile station 100, a femtocell 200, an IMS 300, a CDMA network 400, and a PSTN 500. The femtocell 200 refers to the coverage area supported by the femtocell base station router, and the femtocell base station router includes a user agent (femto UA) 210. In the following, the term femtocell is used interchangeably with a base station of a femtocell and / or a base station router of a femtocell. IMS 300 is an IMS packet network 310, CSCF 320, an application server (AS), MGCF / MGW 340, herein referred to as MAP Femto Interworking Function (MFIF) 330. ), And a home serving system (HSS) 350. CDMA network 400 includes MSC 410 and HLR / AuC 420.

1 shows only a single mobile station 100. However, it will be appreciated that femtocell 200 provides communication services to any number of mobile stations. As described herein, a mobile station may be, for example, a cellular telephone carrying a voice and / or data, a portable computer, a pocket computer, a portable computer, a personal digital assistant (PDA), a mobile vehicle mounted in a vehicle. Refers to the device.

The example embodiments described below relate primarily to the methods performed by femto UA 210 and MFIF 330. Methods of wireless communication including a femto UA 210 including IMS subscriptions that proceed with conventional authentication and registration when the femtocell is powered up are described below. CDMA mobile stations 100 are treated as “guests” by femto UA 210, and femto UA 210 communicates with IMS 300 on behalf of each CDMA mobile station 100. In the methods for wireless communication described below, registration / authentication associated with IMS services is separate and different from registration / authentication associated with CDMA services.

2 is a signal flow diagram illustrating IMS registration / authentication performed by femto UA 210 when a femtocell is powered up. HSS 350 stores a femto UA subscription containing authentication secret data and receives services from IMS 300 which includes femtocell 200 providing a connection to MFIF 330. Note that it stores the IMS authentication data used to provide an appropriate authentication response.

Referring to FIG. 2, activation A1 of femtocell 200 is shown as beginning the registration process for femto UA 210 associated with IMS services to be provided to mobile stations 100 located within femtocell 200. It is. The femto UA 210 initiates registration with the IMS 300 by generating a Session Initiation Protocol (SIP) registration message (REGISTER). The femto UA 210 sends a registration message to the CSCF 320 (M1). As shown in FIG. 2, the registration message includes information identified in the "From", "To", and "Contact" fields. This information is only related to femto UA 210 and does not include information related to mobile stations 100 located within femtocell 200.

The CSCF 320 receiving the registration message queries the HSS 350 for authentication data for the femto UA 210 (A2). The CSCF 320 generates authentication information based on the information received in the response of the HSS 350 to the query. Authentication information generated or used by the CSCF 320 is well-known, for example, authentication key agreement (AKA), random number (RAND), authentication token (AUTN), integrity It may include an identity key (IK) and a cipher key (CK). The CSCF 320 communicates authentication information indicating that user authentication is required to the femto UA 210 in the SIP 401 message (M2).

In response to receiving the SIP 401 message, the femto UA 210 sends a second registration message to the CSCF 320 (M3). The second registration message includes an authentication response. The authentication response is a series of which some are provided to femto UA 210 as part of each authentication event and some are known to both IMS 300 and femto UA 210 and are not passed during the authentication event. The output of the authentication algorithm with the inputs of.

CSCF 320 processes a second registration message that includes an authentication response to verify the credentials of femto UA 210. As described above, a femto UA subscription containing authentication secret data is provisioned in the IMS 300, and the femto UA 210 stores the IMS authentication data. As such, the HSS 350 or CSCF 320 can use this information to verify the credentials of the femto UA 210. If femto UA 210 is verified, CSCF 320 queries HSS 350 for the user profile and downloads the user profile associated with femto UA 210 from HSS 350 (A3). The user profile downloaded from the HSS 350 is associated with the femto UA 210 and does not include information about the mobile stations 100 located within the femtocell 200. The user profile includes filter criterions that indicate which application servers to include on each call type and an IMS registration validity time value (IMS registration validity value to unregister femto UA in case no re-registration occurs). time value).

In essence, femto UA 210 is requesting approval to deliver IMS services to mobile stations 100 located within femtocell 200.

Once the femto UA 210 is verified and the user profile is downloaded, the CSCF 320 generates a SIP 200 OK message indicating that the femto UA 210 has been verified, and registers with the MFIF 320 for registration with the femto UA 210. Send a SIP 200 OK message to the femto UA 210 (M4). When indicated within the filter criteria downloaded for the femto UA 210, the CSCF 320 also generates a third party registration message and sends the third party registration message registration status information for the femto UA 210. M3 is transmitted to the MFIF 330 for providing to the third party application server, that is, the MFIF 330 (M5). The MFIF 330 responds to the third party registration message with a SIP 200 OK response (M6).

The MFIF 330 also generates a global random key (Global_RAND_Key) in response to receiving the third party registration message (A4). The global random key may be a 64-bit key, for example. In addition, the MFIF 330 generates a SIP message and transmits the generated key of the generated SIP message to the CSCF 320 (M7). It is typically noted that IMS authentication will be performed with femto specific keys provisioned in HSS and femto rather than the randomly generated or selected global random keys described above.

CSCF 320 forwards the SIP message containing the generated key to femto UA 210 (M8). The femto UA 210 processes the received message and sends a SIP 200 OK response to the CSCF 320 (M9).

The femto UA 210 also extracts a global random key from the message and obtains a random number (RAND) based on time and key using a standard hashing algorithm such as SHA-1, for example. (A5). The femto UA 210 then broadcasts a random number (RAND) to an overhead message train (OMT) (A6).

CSCF 320 delivers a SIP 200 OK message to notify MFIF 330 of the completion of registration of femto UA 210 with MFIF 330 (M10).

Thus, mobile stations 100 can receive the broadcasted random number (RAND) and can request IMS services through femto UA 210 as "guests" of femto UA 210. It is noted that the registration process described above does not require that information about the mobile stations 100 be provided to the IMS 300. As such, the exemplary embodiment described above does not suffer from the problems of the prior arts described in the background section of this specification.

3 is a signal flow diagram illustrating registration for a user of a CDMA mobile station 100 located within a femtocell 200. The signal flow diagram of FIG. 3 shows communications between mobile station 100, femto UA 210, CSCF 320, MFIF 330, and HLR / AuC 420.

It is assumed that the femto UA 210 shown in FIG. 3 has already been registered with the IMS 300. For example, femto UA 210 may have been registered using the registration method described above with respect to FIG. 2. In addition, femto UA 210 is broadcasting a Global Challenge (RAND).

Referring to FIG. 3, the mobile station 100 receives the Global Challenge (RAND) and begins the CDMA registration process with the femto UA 210 (A1). The mobile station 100 executes the CDMA CAVE authentication algorithm and sends an authentication response (AUTHR) to the femto UA 210 to start CDMA registration (M1). Note that since CDMA CAVE algorithms are well-known, they are not discussed herein for brevity.

Femto UA 210 receives the AUTHR and generates a SIP message. The SIP message includes location update information including a mobile identification number (MIN), an electronic serial number (ESN), an AUTHR, a random number (RAND), and a parameter for transmitting time (RANDC). In particular, time is used as an input for generating a RAND, and RANDC is an existing parameter for passing time. MIN and ESN are numbers associated with mobile station 100 and are not associated with femto UA 210. The generated SIP message is sent to the CSCF 320 (M2).

CSCF 320 forwards the SIP message to MFIF 330 based on the address identifying MFIF 330 (M3). The MFIF 330 processes the received message and sends a SIP 202 message to the CSCF 320 indicating that the SIP 202 message has been accepted (M4). The CSCF 320 sends a SIP 202 message to the femto UA 210 (M5).

With continued reference to FIG. 3, the MFIF 330 verifies that the RAND is correct for the specified inputs of the global random key and time and that the time used in the RAND generation is within an acceptable interval. MFIF 330 also performs authentication and registration with HLR / AuC 420. This authentication and registration allows the MFIF 330 to act as a VLR. In particular, the MFIF 330 generates an ANSI-41 MAP message including an authentication request (AUTHREQ) and transmits the ANSI-41 MAP message to the HLR / AuC 420 (M6). The authentication request includes a mobile identification number (MIM), an AUTHR generated by the mobile station 100, and a RAND. In response to receiving this information, the HLR / AuC 420 prepares and transmits a MAP message including an authentication request return result (M7).

The registration notification REGNOT will be generated between the MFIF 330 and the HLR / AuC 420 (M8 and M9). Following this registration notification, the MFIF 330 receives the VLR profile data from the HLR / AuC 420 and stores this VLR profile data in itself 330 (A2). The VLR profile data includes information about the mobile station 100, such as the mobile DN for the user, as well as service activation status and origination restrictions.

The MFIF 330 generates a SIP message and forwards the SIP message to the CSCF 320 to notify the femto UA 210 of the success or failure of the authentication and registration process (M10). If authentication and registration was successful, the MFIF 330 also includes a mobile directory number (MDN) for the CDMA mobile station 100. CSCF 320 forwards the SIP message to femto UA 210 (M11). The femto UA 210 provides a location update response to the mobile station 100 (M12) and responds to the CSCF 320 with a SIP 200 OK message (M13). CSCF 320 provides a SIP 200 OK message to MFIF 330 to complete registration for mobile station 100 with MFIF 330 (M14).

As described above with respect to FIG. 3, registration to receive CDMA services includes providing the MFIF 330 with information and authentication events associated with the CDMA mobile station 100 while the IMS described with respect to FIG. 2. Registration for the services only involves providing the IMS 300 with information related to the femto UA 210. Information associated with CDMA mobile station 100 provided during registration for CDMA services includes, for example, ESN, MIN, AUTHR.

2 and 3 above relate to a method for registration for IMS services and CDMA services, respectively. 4 and 5 relate to call origination and call incoming methods, respectively.

4, femto UA 210 is broadcasting a Global Challenge (RAND) to mobile stations 100 in femtocell 200. Femto-to-PSTN call origination begins with the user of the mobile station 100 dialing a number (A1). A setup message comprising the called dialed number (DN) and AUTHR is sent from the mobile station 100 to the femto UA 210 (M1). The femto UA 210 generates a SIP INVITE message that includes information related to the mobile station 100 such as MIN, ESN, CdPN, authentication parameters, and the like. As such, femto UA 210 is considered by the IMS 300 as the call originator (ie, endpoint). However, femto UA 210 includes the mobile identity (MDN or MIN) in the sub-address header of the SIP INVITE message.

The SIP INVITE message is sent to the CSCF 320 (M2). The filtering criteria of the CSCF 320 will cause the SIP INVITE message to be forwarded to the MFIF 330 (M3). MFIF 330 may authenticate mobile station 100 based on information associated with mobile station 100. If the mobile station 100 is authenticated, the MFIF 330 allows the call to continue, replacing the femto UA 210 information of the fields used to identify the caller with the mobile station 100 information, and the originating normal IMS call. Proceed to control and routing. MFIF 300 verifies that the RAND is correct for the specified inputs of the global random key and time and that the time used in the RAND generation is within an acceptable interval. Based on this processing, MFIF 330 generates an ANSI-41 MAP message and sends the ANSI-41 MAP message to HLR / AuC 420 (M4). The MAP message includes an authentication request with the MIN, AUTHR, and RAND of the mobile station 100. The HLR / AuC 420 generates a MAP authentication request result in response to the MAP message received from the MFIF 330 and transmits the MAP authentication request result to the MFIF 330 (M5). In addition, the MFIF 330 generates a SIP INVITE message that includes the MDN of the mobile station 100 and sends the SIP INVITE message to the CSCF 320 (M6). In one alternative embodiment, the call is allowed to continue without waiting for the result of the authentication request from the HLR / AuC 420.

In response to receiving the SIP INVITE message from the MFIF 330, the CSCF 320 sends the SIP INVITE message to the MGCF / MGW 340 (M7).

The MGCW / MGW 340 sends the SIP 183 Session Progress message back to the CSCF 320 (M8), and the CSCF 320 sends the SIP 183 Session Progress message to the MFIF 330 to send the SIP 183 session. Respond to the session progress message (M9). The MFIF 330 sends a SIP 183 session progress message to the CSCF 320 (M10), and the CSCF 320 sends a SIP 183 session progress message to the femto UA 210 (M11).

In response to the SIP 183 session progress message, femto UA 210 returns the interworking PRACK to MGCF / MGW 340 at any time. The MGCF / MGW 340 responds with a SIP 200 OK confirmation, and a bearer path for the ringback tone between the mobile station 100 and the MGCF / MGW 340 is generated (VP1).

With continued reference to FIG. 4, the called mobile station associated with the DN is informed of an incoming call (A2). When the user of the called mobile station answers (A3), an answer indication is provided to the mobile station 100, and a voice call is established (VP2). Once the mobile station 100 in the femtocell 200 disconnects the call (A4), a release is sent from the mobile station 100 to the femto UA 210 (M12), and the SIP session is available at any time for the MGCF / MGW. It is released again at 340.

5 illustrates communications between mobile station 100, femto UA 210, CSCF 320, MFIF 330, MGCF / MGW 340, HLR / AuC 420, and MSC 410. In FIG. 5, the PSTN user dials the number and originates a call routed to the MSC (A1). In this example, the number is a dialed number (DN) associated with the mobile station 100 currently located within the femtocell 200. It is noted that the mobile station 100 is registered as being served by the MFIF 300 of the IMS 300 as described above in connection with FIGS. 2 and 3.

In response to receiving a call routed to MSC 410, MSC 410 attempts to locate the mobile station 100 associated with the DN. In particular, the MSC 410 generates an ANSI-41 MAP message and transmits the ANSI-41 MAP message to the HLR / AuC 420 (M1). The MAP message is a location request. The HLR / AuC 420 determines which mobile station 100 is associated with the DN and sends a routing request containing the MIN of the mobile station 100 to the MFIF 300 as the current visited MSC (M2).

The MFIF 330 assigns a temporary local directory number (TLDN) for the mobile station 100 identified by the MIN and associates the TLDN with data for the identified mobile station 100 (A2). The MFIF 330 also provides the TLDN to the HLR / AuC 420 (M3). HLR / AuC 420 provides the TLDN to MSC 410 (M4), and MSC 410 routes the call to MGCF / MGW 340 using the TLDN as the callee address (M5).

MGCF / MGW 340 generates a SIP INVITE message and sends the SIP INVITE message to MFIF 330 via CSCF 320 based on TLDN (M6 and M7). The TLDN is included in the Callee Address field, collectively referred to as the "Request URI" of the SIP INVITE message.

In response to receiving the SIP INVITE message, the MFIF 330 translates the TLDN into associated femto UA 210 and CDMA mobile station 100 addresses (A3). In particular, MFIF 330 generates different SIP INVITE messages. In this SIP INVITE message, the TLDN contained in the "Request URI" field (ie, destination address) is replaced with the femto UA 210 address. The SIP INVITE message also includes a sub-address "To" field with information about the mobile station 100, such as MDN or MIN.

The SIP INVITE message generated by the MFIF 330 is sent to the CSCF 320 (M8). CSCF 320 forwards this SIP INVITE message to femto UA 210 (M9). The SIP INVITE message includes the MDN or MIN of the mobile station 100.

The femto UA 210 receives the SIP INVITE message and pages the mobile station 100 based on the MDN or MIN included in the sub-address of the received SIP INVITE message (M10). The mobile station 100 responds to the page with a response including the AUTHR (M11). In response to the previously received SIP INVITE, femto UA 210 sends a SIP 180 session progress message to CSCF 320 that includes authentication information, such as the time used to generate AUTHR, RAND, and RAND (M12). CSCF 320 provides the SIP 180 session progress message to MFIF 330 (M13).

With continued reference to FIG. 5, the MFIF 330 may perform authentication of the mobile station 100. If the mobile station 100 is authenticated, the MAP message is provided to the HLR / AuC 420 (M14). The MAP message is an AUTHREQ including the MIN of the mobile station 100, the AUTHR provided by the mobile station 100, and a random number (RAND). The HLR / AuC 420 returns the result to the MFIF 330 (M15).

Those skilled in the art will recognize that various session progression and PRACK messages are transmitted between femto UA 210, CSCF 320, MFIF 330, MGCF / MGW 340, HLR / AuC 420, and MSC 410. something to do. Following session progress and PRACK messages, the ringback tone initiating the call is provided to the user by the MGCF / MGW 340 (VP1) and the called mobile station 100 located within the femtocell 200 is notified of the call. .

Assuming that the user of the called mobile station 100 answers the call (A4), an answer indication is sent from the mobile station 100 to the femto UA 210 (M16). In response to the call answer, 200 OK (answer to INVITE) messages and acknowledgment (ACK) signals are established to establish a voice path between the called mobile station 100 and the caller (VP2) femto UA 210, CSCF. 320, MFIF 330, MGCF / MGW 340, HLR / AuC 420, and MSC 410. 5 shows that a message indicating that the call was answered is sent from MGCF / MGW 340 and MSC 410 (M17), and a voice path has been established between the MSC 410 and mobile station 100 (VP2). Display. Once the femto UA 210 user disconnects the call (A5), release messages (BYE / 200 OK-BYE) and (M18) are sent and the established voice path is released.

Having described the exemplary embodiments, it will be apparent that the exemplary embodiments can be varied in various ways. Such changes are not to be regarded as a departure from the teachings of the present application, and all such modifications are intended to be included within the scope of the present application.

10: telecommunications system 100: CDMA mobile station
200: femtocell 210: femto UA
300: IP multimedia subsystem 310: IMS packet network
320: CSCF
330: MAP femto interworking function 340: MGCF / MGW
350: home serving system 400: CDMA network
410: MSC 420: HLR / AuC
500: PSTN

Claims (10)

In the wireless communication method:
Registering the femtocell (200) with the IMS core network (300) to receive IMS services for at least one mobile station (100) located in the femtocell; And
Registering the mobile station separately with an application server (330) to provide additional services to the mobile station located within the femtocell. The method of claim 1,
The additional services are CDMA services. The method of claim 1,
Registering the femtocell to the IMS core network includes:
Transmitting femtocell registration information to the IMS core network to request IMS services for a mobile station located within the femtocell, wherein the femtocell registration information does not include information about the mobile station. Wireless communication method. The method of claim 3, wherein
Receiving authentication keys from the IMS core network;
Preparing an authentication response based on the received authentication keys and the stored femtocell information; And
Sending the prepared authentication response to the IMS core network to receive IMS services. The method of claim 4, wherein
Receiving a global random key from the IMS core network once the femtocell is registered;
Obtaining a challenge using the received key and time value;
Transmitting the challenge to the mobile station; And
Providing services to the mobile station in response to the transmitted challenge. The method of claim 1,
Registering the mobile station separately with the application server includes:
Receiving an authentication response to the global challenge from the mobile station;
Generating a first SIP message associated with the mobile station based on the authentication response;
Sending the first SIP message to the IMS core network to register the mobile station for the additional services;
Receiving a second SIP message from the IMS core network; And
Providing the mobile station with information regarding registration for additional services. The method according to claim 6,
The first SIP message includes at least one of an electronic serial number of the mobile station, a mobile identification number, a random number, and a time value of the mobile station, and the second SIP message includes a mobile directory number for the mobile station; Wireless communication method. The method of claim 1,
Receiving a call setup request from the mobile station that includes a called party number (CpDN);
Generating a SIP message comprising the CpDN and mobile station information; And
Sending the generated SIP message to the IMS core network to notify the IMS core network of the call request. The method of claim 8,
The SIP message comprises information associated with the mobile station in a sub address of the SIP message. The method of claim 9,
Wherein the information associated with the mobile station comprises at least one of a mobile identification number, an electronic serial number, and a mobile directory number.

Images